text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/24130

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/25035

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/25176

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/25745

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/25991

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26212

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26588

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26828

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26839

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26850

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27936

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27936

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28271

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28271

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/29133

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/29452

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/30197

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/30774

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/32516

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/38916

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/38974

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/39398

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/41335

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/42575

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/45388

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/45611

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/45881

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/49174

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/49332

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/49333

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/49732

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/49798

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/49815

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/50003

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/50238

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/53650

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/53651

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/53652

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/54156

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/54309

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/54312

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/55624

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/55623

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/55625

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/55626

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/57456

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/57465

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/57467

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/57470

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/57471

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/57986

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58029

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58064

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58473

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58474

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58520

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58540

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58589

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58590

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58667

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58840

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58879

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/60220

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/60343

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/60375

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/60374

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/60379

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61065

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61578

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61579

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61582

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61679

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/62084

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/62650

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63801

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63821

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/66429

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/66432

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/66433

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/68006

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/68009

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73565

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73572

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73599

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73602

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73616

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73658

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73916

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/75255

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73607

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/75884

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/76303

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/76632

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77235

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77237

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77238

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77236

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77443

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77445

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77447

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/78253

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/78263

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/78416

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/78437

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/78828

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/80052

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/80923

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/80943

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/81977

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/82331

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/82515

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/82516

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/85996

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86001

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86003

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86002

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87178

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87259

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87260

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87508

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87894

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87895

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88001

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88463

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88743

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88744

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88911

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88915

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/89411

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/89515

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/89516

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/90882

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/91441

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/91443

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/93081

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/93082

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/93593

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/93597

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/93609

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/93612

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94092

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94097

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94240

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94620

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94629

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94631

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94933

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95014

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95015

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95049

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95064

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95334

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/96329

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/96330

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/97291

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98287

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/99649

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/99892

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/99896

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/100306

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/100305

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/101051

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/103587

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/103591

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/103594

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/103589

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/103958

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104087

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104102

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104149

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104163

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104215

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104243

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104820

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104822

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105053

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105061

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105062

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105128

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105179

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105779

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105784

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106069

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106105

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106144

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106218

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106225

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106287

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106368

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106410

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106423

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106426

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106455

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106505

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106648

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106805

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106814

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106813

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106829

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106840

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106984

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107005

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107019

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107026

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107078

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107100

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107237

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107660

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107669

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107743

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107762

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107763

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107835

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107925

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107927

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108027

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108046

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108047

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108163

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108405

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108406

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108505

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108580

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108609

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/108736


text:
Add real, imag, conj for ITensors

Define real, imag, conj for ITensors
Unit tests for blocksparse complex operations
Dense ITensor complex operation tests
Complex operation unit tests for Diag ITensors

Closes #504

Great, thanks!

source: gharchive/pull-request

authors: emstoudenmire mtfishman

license_type: permissive

license_source: github-api


text:
🛑 Website is down

In e8f8abf, Website (https://pt.ivao.aero/portal) was down:

HTTP code: 500
Response time: 1104 ms

Resolved: Website is back up in 8e12465.

source: gharchive/issue

repo: IVAO-Portugal/status-page

license: MIT


text:
🛑 Website is down

In 36d1c8b, Website (https://pt.ivao.aero/portal) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Website is back up in bcb3a05.


text:
🛑 API is down

In c5a8a46, API ($API_ENDPOINT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: API is back up in 556c601 after 1 minute.


text:
Update install_generator.rb

Fixes IcaliaLabs/tailwindcss-rails#2

Thank you so mouch for this! Merging and compiling for the new version

authors: kurenn mitchwd

repo: IcaliaLabs/tailwindcss-rails


text:
icinga-php-library (>=0.9.0) required by icinga db but none available

can only find 0.8.1 and nightly snapshot (which btw. won't work very well)

(which btw. won't work very well)

What does that mean? You can only use the snapshot, so it'd be very useful to know what doesn't work.

With snapshot I get the following error in icinga:
Uncaught ArgumentCountError: Too few arguments to function ipl\Orm\Resolver::__construct(), 0 passed in /usr/share/icingaweb2/modules/icingadb/library/Icingadb/Redis/VolatileStateResults.php on line 62 and exactly 1 expected in /usr/share/icinga-php/ipl/vendor/ipl/orm/src/Resolver.php:55 Stack trace: #0 /usr/share/icingaweb2/modules/icingadb/library/Icingadb/Redis/VolatileStateResults.php(62): ipl\Orm\Resolver->__construct() #1 /usr/share/icingaweb2/modules/icingadb/library/Icingadb/Redis/VolatileStateResults.php(46): Icinga\Module\Icingadb\Redis\VolatileStateResults->applyRedisUpdates() #2 /usr/share/icingaweb2/modules/icingadb/library/Icingadb/Common/BaseItemList.php(87): Icinga\Module\Icingadb\Redis\VolatileStateResults->rewind() #3 /usr/share/icingaweb2/modules/icingadb/library/Icingadb/Widget/ItemList/StateList.php(20): Icinga\Module\Icingadb\Common\BaseItemList->assemble() #4 /usr/share/icinga-php/ipl/vendor/ipl/html/src/HtmlDocument.php(295): Icinga\Module\Icingadb\Widget\ItemList\StateList->assemble()

You came here because Icinga DB Web asks for icinga-php-library in version 0.9.0. This can only be the case if you're using the master git branch of it. None of our packages for Icinga DB Web are recent enough. So I guess, pulling the master branch should solve your problem.

Then probably the debian repositories are outdated mentioned at https://icinga.com/docs/icinga-db/latest/doc/02-Installation/. icinga-bullseye-testing (last updated 2022/02/01) contains rc1, icinga-bullseye (2022/04/28) contains rc2 and icinga-bullseye-snapshots messed up whole installation.
Now installed master branch from scratch and snapshot branch from icinga-php-library, but still problems:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'service_state.previous_soft_state' in 'field list'
seems to be an icingadb problem, field missing in upgrade sql files also.
Fatal error : Declaration of Icinga\Module\Director\Dashboard\Dashboard::count() must be compatible with ipl\Html\HtmlDocument::count(): int in /usr/share/icingaweb2/modules/director/library/Director/Dashboard/Dashboard.php on line
seems to be related to this project

I really don't know what's going on here, but your installation seems to be messed up somehow. The error you'll get in the Director can only happen if you have a version of icinga-php-library that's not been released yet (e.g. snapshot/nightly), but is still outdated. The recent build of snapshot/nightly shouldn't show the same error.
Yet, Icinga DB Web is obviously outdated (Doesn't work with snapshot/nightly, whether recent or not) but you think it requires version 0.9.0 of icinga-php-library. How did you came to this conclusion? Did the packages install it automatically? Then, I'm afraid, you should keep away from the packages as they're then broken.
Though, I wouldn't recommend the packages anyway. They don't represent the current state of development and are heavily outdated. The repository icinga-bullseye-testing may have been updated at 2022/02/01, but the packages were definitely not. They're from November last year.
What I'd recommend is to directly check out the git master of Icinga DB and Web as well as the snapshot/nightly branch of icinga-php-library and icinga-php-thirdparty. Or to use the icinga docker images. (The :master tag of course)

Thats what I did before getting the last Director related error. Removed debian packages, installed master from Icinga DB (compiled from source with go), Icinga DB Web and snapshots from ipl and third-party:

Icinga 2 | 2.13.3-1
Icingaweb 2 | 2.10.1
Icinga DB | v1.0.0-rc2-dev
Icinga DB Web | 1.0.0-rc2
Director | 1.9.1 / master
icinga-php-thirdparty | 0.11.0-dev
icinga-php-library | 0.9.0-dev

running all on Debian 11 with PHP 7.4.28.

just cloned again and now it works. For whatever reason git checkout / pull didn't update code correctly ...

Glad to hear :)

authors: nilmerg wrufeger

repo: Icinga/icinga-php-library


text:
Make unicam_isp_capture possible to vflip and hflip

Check list

[x] I wrote CHANGELOG.md if the pull request adds/modifies features.

Summary
We have made unicam_isp_capture possible to vflip and hflip.
We confirmed with imx219 and ov5647 sensors.

すみませんコンフリクト解消したら approve 取れてしまったのでもう一度お願いします :pray:

repo: Idein/actfw-core


text:
Add a parameter for the cancel delay in FrameLoader

#40

looks like this one built fine, no?

It builds fine indeed, let me know if you want to keep a clear history, I can rebase those two commits into one.

looks good, thanks!

authors: aubm brockallen

repo: IdentityModel/oidc-token-manager

license_source: bigquery


text:
Implementing ASP.NET Identity support

As the Quickstart for ASP.NET Identity implementation seems to be deprecated, what is the reccomended way to implement it now?

It's not deprecated. Just not updated to ASP.NET Core v3 yet.

Oh, ok. Thanks!

authors: haugan leastprivilege


text:
RequestedClaimTypes  in IProfileService.GetProfileDataAsync not including IdentityResourceClaims

I have created my own ProfileService concrete, based on the built in one.
context.RequestedClaimTypes does not include any related claims from IdentityResourceClaims table, but it does have the IdentityResource from the specified scopes in context.RequestedResources.ParsedScopes.  I would think it should be included in RequestedClaimTypes, otherwise is there any way to get these from the context? Or would I need to do my own db query?
Is this example - "app_perms" is the scope (identity resource) and "app" is the claim (in the IdentityResourceClaims table)
        protected virtual async Task GetProfileDataAsync(ProfileDataRequestContext context, IdentityUser user)
        {
            if (context.RequestedResources.ParsedScopes.Any(x => x.ParsedName == "app_perms") || context.RequestedClaimTypes.Contains("app"))
            {
                // add some test app claims
                context.IssuedClaims.Add(new Claim("app", "App1"));
                context.IssuedClaims.Add(new Claim("app", "App2"));
            }
        }

thanks

It's been a while, but I'm fairly sure you can see which scopes are associated to which claims directly under resources. RequestedClaimTypes are likely just that, see 5.5 here https://openid.net/specs/openid-connect-core-1_0.html#ClaimsParameter

thank you - yes actually I can find it here:
context.RequestedResources.Resources.IdentityResources.Any(x => x.UserClaims.ContainsIgnoreCaseTrim("role"))


text:
Font doesn't change

Font doesn't change.
For example changing the font size, font family, etc in the properties, it do applies in the design view but when the code runs it ain't apply the changes in the form.

The font is set in the constructor, you can overwrite the component and remove this feature.

If you want to replace all fonts
materialSkinManager = MaterialSkinManager.Instance;
...
materialSkinManager.ROBOTO_MEDIUM_10 = new Font("font name", 10);
materialSkinManager.ROBOTO_MEDIUM_11 = new Font("font name", 11);
materialSkinManager.ROBOTO_MEDIUM_12 = new Font("font name", 12);
materialSkinManager.ROBOTO_REGULAR_11 = new Font("font name", 11);

if i want to change only one control font
how can i do that?
i can't change any thing in material skin open Source because
When I open it in Visual Studio is full of errors

@VahidEra I am looking for same thing, How you managed to get it done ?

I encountered the same problem

Well I found a solution from the internet in VB language
Dim pfc As New PrivateFontCollection
pfc.AddFontFile(Application.StartupPath & "\fnts\Roboto-Light.ttf") 'Your font location, make sure the font is in "*.ttf" format
Label1.Font = New Font(pfc.Families(0), 16)

ROBOTO_MEDIUM_11
el ROBOTO_ ... De donde lo sacas?

How can this be disabled?

This is also my problem!

authors: Ali4ootan AngelPM98 LiteOnE VahidEra anirugu avarantes chpecson leonelunderscore shDiego shannonfonseka

repo: IgnaceMaes/MaterialSkin

license: mit


text:
igPivotGrid - capture rows, columns filters or measures

In case of igPivotGrid, when user sets rows / columns / filters / measures etc. Is there a way to capture and apply previously saved settings of pivot grids?
I am looking for ability to save and retrieve pivot configuration done by user. Is this functionality supported by igPivotGrid? If yes, please guide me on this.
I am setting my igPivotGrid with xmlaDataSource like this-
import {Component, Inject, ElementRef, EventEmitter, HostListener} from '@angular/core';
import {IgPivotDataSelectorComponent, IgPivotGridComponent} from "igniteui-angular2";

declare var jQuery: any;

@Component({
  selector: 'my-app',
  //template: '
My First Angular 2 App
'
  template: `

Test User Settings:
 <button (click)="test()">Test</button>

        <ig-pivot-grid [widgetId]="gridId" [options]="optsGrid" >
        </ig-pivot-grid>

        <ig-pivot-data-selector [widgetId]="selectorId" [options]="optsSelector" >
        </ig-pivot-data-selector>

  `,
  directives: [ IgPivotDataSelectorComponent, IgPivotGridComponent]
})

export class AppComponent {
  private optsGrid: IgPivotGrid;
	private optsSelector: IgPivotDataSelector;
	private selectorId: string;
	private gridId: string;
	private data: any;

constructor() {

  this.data =  new jQuery.ig.OlapXmlaDataSource({
			serverUrl: 'http://servername/olap/msmdpump.dll',
      catalog: 'XYZ',
      cube:'ABC'
		});

      this.selectorId = "dataSelector";
      this.gridId = "pivotGrid";

      this.optsGrid = {
        dataSource: this.data,
        height: "100%",
        width: "100%"
      };

      this.optsSelector = {
        dataSource: this.data,
        height: "100%",
        width: "100%"
      };
  }

  test(){
    var test1 = this.data.getMeasure();
    console.log('getMeasure: ' + test1);

    var test2 = this.data.getMeasureList();
    console.log('getMeasure: ' + test2);
  }
}

In test method, I get NULL for both getMeasure and getMeasureList. Am I doing something wrong here?  I want to capture setting done by user like selected rows, columns filters or measures. How to achieve this with igPivotGrid?

Could you please respond on this?

This is been pending from week. Could you please respond on this?

@sanket360 This is an open source repository and we have no commitment to respond to, or to fix issues within a given timeframe. We've been very prompt in responding to the issues you have created. If you expect an answer within a certain timeframe, then you can use your Ignite UI license to open a support ticket with us.
https://www.infragistics.com/my-account/submit-support-request

To restore the state/set new filters/columns/measures of the igPivotGrid you need to recreate it.
Store it's full options var obj = $.extend(true, {}, $("#pivotGrid").igPivotGrid("option"))
Destroy it $("#pivotGrid").igPivotGrid("destroy")
Recreate it $("#pivotGrid").igPivotGrid(obj). And into the recreation part different filters/columns/measures can be applied

After using this statement-
var obj = $.extend(true, {}, $("#pivotGrid").igPivotGrid("option"))
How do I read filters/columns/measures of the igPivotGrid from obj variable?
If I try like this-
var obj = $.extend(true, {}, $("#pivotGrid").igPivotGrid("option"))
    console.log('obj.option ' + this.obj.option);
    console.log('obj.options ' + this.obj.options);
    console.log('obj.getMeasure ' + this.obj.getMeasure);
    console.log('obj.getMeasureList ' + this.obj.getMeasureList);
    console.log('obj.getDimension ' + this.obj.getDimension);

it gives me undefined for all 5 lines.

$("#pivotGrid").igPivotGrid("option") - This will give you the entire igPivotGrid configuration options
If you want specifically the filters/columns and measures you need to extract those from the dataSource of the pivotgrid since they are properties of the data source:
$("#pivotGrid").igPivotGrid("option", "dataSource").columnAxis()
$("#pivotGrid").igPivotGrid("option", "dataSource").filters()
$("#pivotGrid").igPivotGrid("option", "dataSource").measures()
or even getMeasure(), getMeasureList() and getDimension() the ones you specified

I tried to capture like this-
    console.log('getMeasure(): ' + $("#pivotGrid").igPivotGrid("option", "dataSource").getMeasure());
    console.log('getMeasureList(): ' + $("#pivotGrid").igPivotGrid("option", "dataSource").getMeasureList());
    console.log('getDimension(): ' + $("#pivotGrid").igPivotGrid("option", "dataSource").getDimension());

But all 3 are null.
Am I missing anything here?

Ok, I'll assume you are using http://igniteui.github.io/igniteui-angular2/samples/igPivotGrid-FlatDataSource/igPivotGrid-FlatDataSource.html sample and answer based on it, because it also returns null on all of the calls you described.

$("#pivotGrid").igPivotGrid("option", "dataSource").getMeasure() -> returns null, because it requires an argument, in order to get the measure you want, you have to pass it. For this sample it should be:
$("#pivotGrid").igPivotGrid("option", "dataSource").getMeasure("[Measures].[UnitsSold]"). More info here - http://www.igniteui.com/help/api/2016.1/ig.OlapFlatDataSource#methods:getMeasure

$("#pivotGrid").igPivotGrid("option", "dataSource").getMeasureList() -> returns null, because into the sample, there is only one measure specifed and $.ig.MeasureList is not going to assembled for only one measure, measures should more than one. You can see this
into the description of the API method getMeasureList() - http://www.igniteui.com/help/api/2016.1/ig.OlapFlatDataSource#methods:getMeasureList
You can review the other sample for the igPivotGrid http://igniteui.github.io/igniteui-angular2/samples/igPivotGrid-XmlaDataSource/igPivotGrid-XmlaDataSource.html and see that there is two measures and you can take advantage getMeasureList() there

$("#pivotGrid").igPivotGrid("option", "dataSource").getDimension() -> returns null, because it also requires an argument the name of the dimension. For example:
$("#pivotGrid").igPivotGrid("option", "dataSource").getDimension("[Date]"). More info here http://www.igniteui.com/help/api/2016.1/ig.OlapFlatDataSource#methods:getDimension

No, I am using OlapXmlaDataSource

This doesn't matter. The rules still apply.
I used this data:
this.data = new jQuery.ig.OlapXmlaDataSource({
  serverUrl: 'http://sampledata.infragistics.com/olap/msmdpump.dll',
  catalog: 'Adventure Works DW Standard Edition',
  cube: 'Adventure Works',
});

I've dragged from the pivotDataSelector two measures, one Column and one Row and here's the output:

ok thanks and how do I use measures?
If I do this
console.log('measures: ' + $("#pivotGrid").igPivotGrid("option", "dataSource").measures());
This gives me object like shown in above screenshot.
How do I read properties of measures like- name, uniquename etc?

measures() is returning an array of objects of type $.ig.Measure.
You can inspect the $.ig.Measure methods to see how to get use of it.

great thanks :+1:

authors: dkamburov kdinev sanket360


text:
Экстрапараметры записи как отдельная таблица

Надо отказаться от полей типа saved_from и тому подобных в метаинформации и вынести это в отдельную таблицу. Соответственно, JSON в metainfo не хранить.

Соответственно - надо будет изменить схему данных для metainfo

repo: IgorZyktin/omoide


text:
Cannot follow documentation example in version 2.1.0

Hi,
I'm following this example from the documentation but I cannot find the type RefinedTypeOps in latest version of the library:
opaque type Temperature = Double :| Positive
object Temperature extends RefinedTypeOps[Temperature]
All imports are also included.
Scala environment: JVM
Scala version: 3.3.0
Iron version: 2.1.0
Am I doing something wrong? Thanks!

Hi.
This feature will be included in the next release (probably coming this month or early July). I am currently working on this section in branch docs/rework-documentation.
As far as I can tell, you're doing it right. If you want to test it you can use the latest nightly.
Currently, you have on Scaladex the API docs for each version but not the "static" documentation (guides, getting started etc...). Might be worth an issue.
Did I answer your question?

Totally yes, that's just the answer I needed.
Thanks for answering so quickly.

authors: Iltotore etorres

repo: Iltotore/iron


text:
How to

Hello, how do I use lezhin downloader java? I already make a folder that consists of java downloader, chromedriver, and config.ini. but it seems I can't access it

Hi.
Did you see pre-requirements in the readme?
If you don't install JRE(or JDK)8+, you can't run the downloader.
If you completely prepared, just open cmd and input the command with arguments.

I don't understand how to use it either. I installed JRE and chrome driver, put everything in the same folder and then put java -jar lezhin-comics-downloader 2.6.2 -l=en> -n=tempters -r=~7 in the command, and it says it is unable to access jarfile lezhin-comics-downloader 2.6.2.

@Chidichi
Can you refer to #8?
I think this issue and yours is the same.

I already succeed with installing java and downloading some comic. And I would like to download "Painter of the Night" in Lezhin EN version... But it seems the downloader can't download the comic.

@sashakeista
Did you see the following error?
Error: Unable to access jarfile lezhin-comics-downloader.jar

Then, you should go to the directory where downloader.jar, chromedriver and config.ini are.

It isn't. It's this one

authors: Chidichi ImSejin sashakeista

repo: ImSejin/lezhin-comics-downloader


text:
Calendar does not scale appropriately on mobile Safari

The calendar cuts off and can't be rescaled when I access the page with my iPhone which makes the calendar essentially unusable on my phone. I believe I'm using the latest OS update.

Fixed in v2

authors: saranadeau vyedin

repo: IndivisibleSomerville/website


text:
Import AES 256 private key

I'm just wondering if there's any function I could call to import AES256 to TPM SLB 9670.
Since this TPM doesn't support generating AES256 itself, so would it make sense to import the AES256 key generated outside of it? Then PKCS#11 program (e.g. python, c/c++ PKCS#11 API) could retrieve the private key from it.
Thanks.

The example is not available here, but you should be able to do so using the C_CreateObject to create an CKO_DATA object. You may place the AES key in the CKA_VALUE field. CKA_VALUE fields are encrypted for CKO_DATA objects

Thanks for your reply, it is possible to import the private through pkcs11-tool?
For example,
https://github.com/OpenSC/OpenSC/issues/2477
As we are looking for a way to meet the AVS (Amazon Voice Services) requirement which needed AES256 token stored in SLB 9670.
Thanks.

Try the following:
$ alias tpm2pkcs11-tool='pkcs11-tool --module /usr/local/lib/libtpm2_pkcs11.so'
$ tpm2pkcs11-tool --slot 1 --generate-random 32 > data.write
$ tpm2pkcs11-tool --slot 1 --write-object data.write --type data --application-label data_00 --label data_00 --login --pin userpin --private
$ tpm2pkcs11-tool --slot 1 --read-object --type data --login --pin userpin --label data_00 > data.read
$ diff data.write data.read

Appreciate your help, will try out and update soon. Thanks! =)

Thanks, the tutorial works as it successfully imported the data object. Would it be possible if I import it as an AES256 private key?
For example,
tpm2pkcs11-tool --slot 1 --write-object data.write **--type privkey**  --label data_00 --login --pin userpin --private **--sensitive**

What you are looking for is --type secrkey (i.e., CKO_SECRET_KEY) for symmetric key; however, I believe it is not supported by tpm2-pkcs11 library, you may check here, the C_CreateObject only supports CKO_PUBLIC_KEY+CKK_RSA, CKO_DATA, and CKO_CERTIFICATE.

In addition, check here, the tpm2-pkcs11 library has no support for symmetric key operation.

I remember I use a command before and its works, it can generate the private key in slot 1 with the command below.
./tpm2_ptool.py addkey --algorithm=aes128 --label=avs --userpin=123456 --key-label=avskey --path=/opt/tpm2-pkcs11/

tpm2_ptool.py from https://github.com/tpm2-software/tpm2-pkcs11/tree/master/tools

But it doesn't work when I changed the --algorithm field to aes256 (Seems like hardware limitation?).
It is possible it is a hardware instead of software (tpm2-pkcs11) limitation. By the way, I'm using SLB 9670.
Thanks!

You are correct, SLB 9670 does not support AES operation. To answer why ./tpm2_ptool.py may work, this is because you can create AES key, but there is no way to use it. Because EncryptDecrypt command code is not supported.

Hmm, I see, that's funny haha... that means SLB 9670 could support the required operations (AES related).
Thanks for the command, i tried to run it,
root@cobra:~# tpm2_getcap algorithms rsa:   value:      0x1   asymmetric: 1   symmetric:  0   hash:       0   object:     1   reserved:   0x0   signing:    0   encrypting: 0   method:     0 sha1:   value:      0x4   asymmetric: 0   symmetric:  0   hash:       1   object:     0   reserved:   0x0   signing:    0   encrypting: 0   method:     0 hmac:   value:      0x5   asymmetric: 0   symmetric:  0   hash:       1   object:     0   reserved:   0x0   signing:    1   encrypting: 0   method:     0 aes:   value:      0x6   asymmetric: 0   symmetric:  1   hash:       0   object:     0   reserved:   0x0   signing:    0   encrypting: 0   method:     0

Seems like there is one output related to AES. Not really sure what it means though.

Do you manage to know if there is any Infineon TPM product that would provide AES key generation/operations with PKCS#11 compliance?
Thanks!

The algorithm AES is there for internal use, but not available for external use. The new OPTIGA™ TPM SLB 9672 supports it.

Ok, noted with thanks, I think I can close the case now, thanks for your explanations!

authors: tianxun-ng wxleong


text:
🛑 Amiya IN is down

In 5899402, Amiya IN ($URL) was down:

HTTP code: 502
Response time: 3673 ms

Resolved: Amiya IN is back up in 9211f26.


text:
Eno core : specifications

Business case
🇬🇧
Rewrite the Enocore to ensure its maintainability.
Enhance specification document at the request of some users (who could use this output format of Eno in their own process)
🇫🇷
Révision du format spécifications (en fonction des besoins des utilisateurs dont EEC)
Refonte du coeur d'Eno en java : https://github.com/InseeFr/Eno/blob/v3-develop/docs/fr/Refonte.md
Stack
DDI
Pogues
Eno

[ ] https://github.com/InseeFr/Eno/issues/470 (EEC) - waiting for feedback)
[ ] https://github.com/InseeFr/Eno/issues/492 (mode)
[ ] https://github.com/InseeFr/Eno/issues/493 (externes)

Lunatic
Progress
Release date
End 2024

Voir son avenir

repo: InseeFr/Bowie


text:
Investigate "Mesh: Compacting Memory Management for C/C++ Applications"

https://arxiv.org/abs/1902.04738v1

https://github.com/plasma-umass/mesh

This article was mentioned in cpp reddit channel too: https://www.reddit.com/r/cpp/comments/arhfnw/mesh_compacting_memory_management_for_cc/

Found via hackernews thread :)
https://news.ycombinator.com/item?id=19182779

authors: gdevenyi phcerdan

repo: InsightSoftwareConsortium/ITK


text:
Update VXL library to the latest upstream master

Updating VXL to incorporate changes from vxl/vxl#729
@seanm

PR Checklist

[ ] :no_entry_sign: Makes breaking changes
[ ] :no_entry_sign: Makes design changes
[ ] :no_entry_sign: Adds the License notice to new files.
[ ] :no_entry_sign: Adds Python wrapping.
[ ] :no_entry_sign: Adds tests and baseline comparison (quantitative).
[ ] :no_entry_sign: Adds test data.
[ ] :no_entry_sign: Adds Examples to ITKExamples
[ ] :no_entry_sign: Adds Documentation.

Refer to the ITK Software Guide for
further development details if necessary.

Great, thanks!

Failing test output:
-----------------------------------------------------------------------------
Start Testing test_symmetric_eigensystem:
-----------------------------------------------------------------------------
V'*D*V - S = -1.42109e-14 -8.88178e-16 -2.4869e-14 1.77636e-15 -1.68754e-14 -1.42109e-14
0 -8.88178e-15 1.33227e-15 -8.43769e-15 6.21725e-15 1.13798e-15
-2.4869e-14 1.77636e-15 -3.55271e-15 -1.11022e-14 -8.52096e-15 -7.10543e-15
1.77636e-15 -8.43769e-15 -1.28786e-14 8.88178e-15 -1.04361e-14 -3.9968e-15
-1.59872e-14 6.21725e-15 -8.52096e-15 -1.04361e-14 4.88498e-15 -1.15463e-14
-1.06581e-14 6.93889e-16 -7.10543e-15 -3.9968e-15 -1.15463e-14 2.13163e-14

residual = 6.50281e-14
 Test 001: recompose residual                                    -->  should be 0, is 6.50281e-14,   PASSED
Eigenvalues: 0.170864 2.16934 3.79272 15.435 24.6083 78.2994
V'*D*V - C = 0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 1.11022e-16 0 -4.44089e-16
0 0 0 0 0 0
0 0 0 -4.44089e-16 0 1.11022e-16

residual = 6.47366e-16
 Test 002: recompose residual                                    -->  should be 0, is 6.47366e-16,   PASSED
Eigenvalues: -2 -1 0 0 0 2
Testing random system:
evals: 3.49113 13.6528 30.1636 47.9597 54.3172 190.044
 Test 003: Eigenvalue increases                                  -->   PASSED
 Test 004: Eigenvalue increases                                  -->   PASSED
 Test 005: Eigenvalue increases                                  -->   PASSED
 Test 006: Eigenvalue increases                                  -->   PASSED
 Test 007: Eigenvalue increases                                  -->   PASSED
Eigenvals: 1 1 1
 Test 008: Correct eigenvalues for I                             -->   PASSED
Fixed Time: 56   netlib time: 54
 Test 009: Specialised version is faster                         --> **FAILED**
max_dsq: 4.77266e-27  mean_dsq: 2.40789e-29
 Test 010: Specialised version gives similar results             -->   PASSED
 Test 011: Numerically difficult values are ok v1                -->  should be 4199, is 4199, difference 1.81899e-12,   PASSED
 Test 012: Numerically difficult values are ok v2                -->  should be 4199, is 4199, difference 1.81899e-12,   PASSED
 Test 013: Numerically difficult values are ok v3                -->  should be 4801, is 4801, difference 4.54747e-12,   PASSED
-----------------------------------------------------------------------------
test_symmetric_eigensystem Test Summary: 12 tests succeeded, 1 test failed		*****
-----------------------------------------------------------------------------

I just looked at that.  It is a terribly written test for timing that is very unstable.  The timing of the algorithm being tested is corrupted by other variables.
Should timing tests like this be included in vxl?  It seems too fragile.

Should timing tests like this be included in vxl? It seems too fragile.

We have had similar issues with VXL timing tests in the pass -- +1 for excluding or removing them or adding a generous tolerance.

See #1480 for updated version.

authors: hjmjohnson seanm thewtex vfonov


text:
DOC: updated comment for ITK_FUTURE_LEGACY_REMOVE

Changed ITKv5 to ITKv6 in cmake comment for ITK_FUTURE_LEGACY_REMOVE.

Maybe
"Completely remove compilation of code which will become deprecated by default in a future major release"
or
"Completely remove compilation of code which will become deprecated by default in the future major release"

I think the current wording is right. With each major release, we remove deprecated things, and promote "future deprecated" into currently deprecated. I don't remember whether we made some exceptions for things which were deprecated soon before a major version switch.

authors: dzenanz issakomi


text:
IGListStackedSectionController to respect children insets

New issue checklist

[x] I have reviewed the README and documentation
[x] I have searched existing issues and this is not a duplicate

General information

IGListKit version: 2.1.0
tvos version(s): 10.1
CocoaPods/Carthage version: 1.2.0
Xcode version: 8.2.1

Issue
IGListStackedSectionController encapsulates child section controllers.
If insets were set for each separate child section controllers,
insets of the child section controllers are not applied.
Instead, the set inset of IGListStackedSectionController is the only visible change.
Child section controller's insets are not changed, so layout is not desirable.

@ninokierulf Dup with #448

authors: ninokierulf zhubofei

repo: Instagram/IGListKit


text:
server side authorization fails when using oauth2 module

The traceback and steps to reproduce this bug are here: https://gist.github.com/bharadwaj6/e64e1e782f8883e8f42b

Thank you for reporting this issue and appreciate your patience. We've  notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

repo: Instagram/python-instagram


text:
画像データの非公開化

やること

instances.db から、画像データを空欄にした上で公開する。

当初にそうしていたが、その作業を忘れて公開してしまったため、現在に至る。
公開済みのものは履歴に残っちゃってどうしようもない。

理由

画像データを格納することは著作権上懸念があるため。

[cef405d] やった。

repo: InstanceTicker/InstanceTicker


text:
ReadByQuery Child Object

Please see the xml for Customer object and my code but I'm getting error. How to resolve this? Thanks !
<DISPLAYCONTACT.MAILADDRESS.COUNTRYCODE>US</DISPLAYCONTACT.MAILADDRESS.COUNTRYCODE>

I want to get result through LocationId
EqualToString xmlquery = new EqualToString()
            {
                Field = "DISPLAYCONTACT.MAILADDRESS.COUNTRYCODE",
                Value = "US", // Entity ID
            };
ReadByQuery queryCustomer = new ReadByQuery()
            {
                ObjectName = "CUSTOMER",
                PageSize=5,
                Query = xmlquery,
            };

@letoncse , what is the error you are observing?

Closing this issue, please reopen this issue if it is still a problem :)

authors: dylan-holt-sage letoncse

repo: Intacct/intacct-sdk-net


text:
IGAPP-317: Add appleId to build config

ALREADY REVIEWED! No need to review again, sorry for that. Accidentally merged the PR already, but as this would complicate reviewing the IGAPP-309 PR, I reverted it.

As mentioned above: ALREADY REVIEWED! No need to review again, sorry for that. Accidentally merged the PR already, but as this would complicate reviewing the IGAPP-309 PR, I reverted it.

repo: Integreat/integreat-app


text:
Game crashes when switching rooms

Currently sometimes when switching rooms the game crashes.
Accroding to error logs this is due to directly calling QueueFree() instead of using CallDefered()
E 0:00:01:0964   NativeCalls.cs:6311 @ Godot.Variant Godot.NativeCalls.godot_icall_2_701(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name): This function can't be used during the in/out signal.
  <C++ Error>    Condition "locked" is true.
  <C++ Source>   scene/2d/area_2d.cpp:328 @ _clear_monitoring()
  <Stack Trace>  NativeCalls.cs:6311 @ Godot.Variant Godot.NativeCalls.godot_icall_2_701(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name)
                 GodotObject.cs:622 @ Godot.Variant Godot.GodotObject.Call(Godot.StringName, Godot.Variant[])
                 GodotObject.cs:270 @ void Godot.GodotObject.Free()
                 DungeonHandler.cs:38 @ void DungeonHandler.LoadRoom(string, Direction)
                 DungeonHandler.cs:72 @ void DungeonHandler.OnPlayerEnteredDoor(string, Direction)
                 RoomExit_ScriptSignals.generated.cs:40 @ void RoomExit.RaiseGodotClassSignalCallbacks(Godot.NativeInterop.godot_string_name&, Godot.NativeInterop.NativeVariantPtrArgs)
                 ScriptManagerBridge.cs:386 @ void Godot.Bridge.ScriptManagerBridge.RaiseEventSignal(nint, Godot.NativeInterop.godot_string_name*, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_bool*)
                 Godot.NativeInterop.NativeFuncs.generated.cs:361 @ Godot.NativeInterop.godot_variant Godot.NativeInterop.NativeFuncs.godotsharp_method_bind_call(nint, nint, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_variant_call_error&)
                 NativeCalls.cs:6254 @ int Godot.NativeCalls.godot_icall_2_699(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name)
                 GodotObject.cs:606 @ Godot.Error Godot.GodotObject.EmitSignal(Godot.StringName, Godot.Variant[])
                 RoomExit.cs:35 @ void RoomExit.OnBodyEntered(Godot.Node)
                 Area2D.cs:651 @ void Godot.Area2D.BodyEnteredTrampoline(object, Godot.NativeInterop.NativeVariantPtrArgs, Godot.NativeInterop.godot_variant&)
                 DelegateUtils.cs:62 @ void Godot.DelegateUtils.InvokeWithVariantArgs(nint, System.Void*, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_variant*)

E 0:00:01:0965   NativeCalls.cs:6311 @ Godot.Variant Godot.NativeCalls.godot_icall_2_701(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name): Removing a CollisionObject node during a physics callback is not allowed and will cause undesired behavior. Remove with call_deferred() instead.
  <C++ Source>   scene/2d/collision_object_2d.cpp:98 @ _notification()
  <Stack Trace>  NativeCalls.cs:6311 @ Godot.Variant Godot.NativeCalls.godot_icall_2_701(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name)
                 GodotObject.cs:622 @ Godot.Variant Godot.GodotObject.Call(Godot.StringName, Godot.Variant[])
                 GodotObject.cs:270 @ void Godot.GodotObject.Free()
                 DungeonHandler.cs:38 @ void DungeonHandler.LoadRoom(string, Direction)
                 DungeonHandler.cs:72 @ void DungeonHandler.OnPlayerEnteredDoor(string, Direction)
                 RoomExit_ScriptSignals.generated.cs:40 @ void RoomExit.RaiseGodotClassSignalCallbacks(Godot.NativeInterop.godot_string_name&, Godot.NativeInterop.NativeVariantPtrArgs)
                 ScriptManagerBridge.cs:386 @ void Godot.Bridge.ScriptManagerBridge.RaiseEventSignal(nint, Godot.NativeInterop.godot_string_name*, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_bool*)
                 Godot.NativeInterop.NativeFuncs.generated.cs:361 @ Godot.NativeInterop.godot_variant Godot.NativeInterop.NativeFuncs.godotsharp_method_bind_call(nint, nint, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_variant_call_error&)
                 NativeCalls.cs:6254 @ int Godot.NativeCalls.godot_icall_2_699(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name)
                 GodotObject.cs:606 @ Godot.Error Godot.GodotObject.EmitSignal(Godot.StringName, Godot.Variant[])
                 RoomExit.cs:35 @ void RoomExit.OnBodyEntered(Godot.Node)
                 Area2D.cs:651 @ void Godot.Area2D.BodyEnteredTrampoline(object, Godot.NativeInterop.NativeVariantPtrArgs, Godot.NativeInterop.godot_variant&)
                 DelegateUtils.cs:62 @ void Godot.DelegateUtils.InvokeWithVariantArgs(nint, System.Void*, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_variant*)

E 0:00:01:0969   NativeCalls.cs:6311 @ Godot.Variant Godot.NativeCalls.godot_icall_2_701(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name): Object <Object#59978548473> was freed or unreferenced while a signal is being emitted from it. Try connecting to the signal using 'CONNECT_DEFERRED' flag, or use queue_free() to free the object (if this object is a Node) to avoid this error and potential crashes.
  <C++ Source>   core/object/object.cpp:2006 @ ~Object()
  <Stack Trace>  NativeCalls.cs:6311 @ Godot.Variant Godot.NativeCalls.godot_icall_2_701(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name)
                 GodotObject.cs:622 @ Godot.Variant Godot.GodotObject.Call(Godot.StringName, Godot.Variant[])
                 GodotObject.cs:270 @ void Godot.GodotObject.Free()
                 DungeonHandler.cs:38 @ void DungeonHandler.LoadRoom(string, Direction)
                 DungeonHandler.cs:72 @ void DungeonHandler.OnPlayerEnteredDoor(string, Direction)
                 RoomExit_ScriptSignals.generated.cs:40 @ void RoomExit.RaiseGodotClassSignalCallbacks(Godot.NativeInterop.godot_string_name&, Godot.NativeInterop.NativeVariantPtrArgs)
                 ScriptManagerBridge.cs:386 @ void Godot.Bridge.ScriptManagerBridge.RaiseEventSignal(nint, Godot.NativeInterop.godot_string_name*, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_bool*)
                 Godot.NativeInterop.NativeFuncs.generated.cs:361 @ Godot.NativeInterop.godot_variant Godot.NativeInterop.NativeFuncs.godotsharp_method_bind_call(nint, nint, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_variant_call_error&)
                 NativeCalls.cs:6254 @ int Godot.NativeCalls.godot_icall_2_699(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name)
                 GodotObject.cs:606 @ Godot.Error Godot.GodotObject.EmitSignal(Godot.StringName, Godot.Variant[])
                 RoomExit.cs:35 @ void RoomExit.OnBodyEntered(Godot.Node)
                 Area2D.cs:651 @ void Godot.Area2D.BodyEnteredTrampoline(object, Godot.NativeInterop.NativeVariantPtrArgs, Godot.NativeInterop.godot_variant&)
                 DelegateUtils.cs:62 @ void Godot.DelegateUtils.InvokeWithVariantArgs(nint, System.Void*, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_variant*)

E 0:00:01:0975   NativeCalls.cs:6156 @ void Godot.NativeCalls.godot_icall_3_690(nint, nint, nint, Godot.NativeInterop.godot_bool, int): Can't change this state while flushing queries. Use call_deferred() or set_deferred() to change monitoring state instead.
  <C++ Error>    Condition "area->get_space() && flushing_queries" is true.
  <C++ Source>   servers/physics_2d/godot_physics_server_2d.cpp:355 @ area_set_shape_disabled()
  <Stack Trace>  NativeCalls.cs:6156 @ void Godot.NativeCalls.godot_icall_3_690(nint, nint, nint, Godot.NativeInterop.godot_bool, int)
                 Node.cs:689 @ void Godot.Node.AddChild(Godot.Node, bool, Godot.Node+InternalMode)
                 DungeonHandler.cs:43 @ void DungeonHandler.LoadRoom(string, Direction)
                 DungeonHandler.cs:72 @ void DungeonHandler.OnPlayerEnteredDoor(string, Direction)
                 RoomExit_ScriptSignals.generated.cs:40 @ void RoomExit.RaiseGodotClassSignalCallbacks(Godot.NativeInterop.godot_string_name&, Godot.NativeInterop.NativeVariantPtrArgs)
                 ScriptManagerBridge.cs:386 @ void Godot.Bridge.ScriptManagerBridge.RaiseEventSignal(nint, Godot.NativeInterop.godot_string_name*, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_bool*)
                 Godot.NativeInterop.NativeFuncs.generated.cs:361 @ Godot.NativeInterop.godot_variant Godot.NativeInterop.NativeFuncs.godotsharp_method_bind_call(nint, nint, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_variant_call_error&)
                 NativeCalls.cs:6254 @ int Godot.NativeCalls.godot_icall_2_699(nint, nint, Godot.NativeInterop.godot_string_name, Godot.Variant[], Godot.NativeInterop.godot_string_name)
                 GodotObject.cs:606 @ Godot.Error Godot.GodotObject.EmitSignal(Godot.StringName, Godot.Variant[])
                 RoomExit.cs:35 @ void RoomExit.OnBodyEntered(Godot.Node)
                 Area2D.cs:651 @ void Godot.Area2D.BodyEnteredTrampoline(object, Godot.NativeInterop.NativeVariantPtrArgs, Godot.NativeInterop.godot_variant&)
                 DelegateUtils.cs:62 @ void Godot.DelegateUtils.InvokeWithVariantArgs(nint, System.Void*, Godot.NativeInterop.godot_variant**, int, Godot.NativeInterop.godot_variant*)

has been fixed

repo: IntegrierBar/FPComputerGames


text:
Null value in Btree and bitmap index cause exception

writeBasedOnDataType do not support write null value, which is used in bitmap and btree index writing.
Possible solutions:

find some way to write null
ignore null in the multi hash map when building tree schema, any one search for null can find that at the beginning of rowIdList.

I prefer solution 2.
BTW, current writing will cause pattern matching for every value it writes, which is inefficient. we should pass the datatype as parameter to eliminate this pattern match in writeBasedOnDataType.

closed by #438

authors: adrian-wang linhong-intel

repo: Intel-bigdata/OAP


text:
Fix dictionary digesting

The dictionary option was not working correctly because "string_escape" encoding does not exist in python3.

Thanks for the patch! Would it make sense to use utf-8 instead of latin1?

No problem :)
utf-8 converts bytes only up to \x7f, and 'latin-1' is a one-to-one conversion (python3 nonsense):
In [22]: b'\x80\xff'.decode('utf-8')
---------------------------------------------------------------------------
UnicodeDecodeError                        Traceback (most recent call last)
<ipython-input-22-2857e4ca95c7> in <module>
----> 1 b'\x80\xff'.decode('utf-8')

UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 0: invalid start byte

In [23]: b'\x80\xff'.decode('latin-1')
Out[23]: '\x80ÿ'

Huh. Would have thought it to be the other way around. Thanks!

Why do we even need such "dictionary" format if the first step taken is to throw out element names? = is not needed as well as " around the string. The only useful thing is # comments. What if we just use following format?
abc\ndef\t
\xFE\xFFab\x61ca\x62a
#this string is commented out
\# this string is not commented out, first two chars are "# "

Dictionary is then parsed like this
dictionary = [line for line in open('dict', 'rb').read().split(b'\n') if not line.startswith(b'#')]
dictionary = [line if not line.startswith(rb'\#') else line[1:] for line in dictionary]    # special case, first char is #
dictionary = [codecs.escape_decode(line)[0] for line in dictionary]    # process escape sequences like \n and \xAB

which gives
>>> dictionary
[b'abc\ndef\t', b'\xfe\xffabacaba', b'# this string is not commented out, first two chars are "# "']

The best reason to keep it that way is to be compatible with the original AFL dictionary format and AFL derivatives.
It's a strong point, and as a user of kAFL and AFL, I would prefer it to stay that way.
The reasoning behind the element name is for documenting each entry (from AFL's manual):
The alphanumeric name is ignored and can be omitted, although it is a convenient way to document the meaning of a particular token.

Makes sense, I didn't think about using names as documentation.

authors: Kristal-g il-steffen vient

repo: IntelLabs/kAFL


text:
Labview-D405

|---------------------------------|------------------------------------------- |
| Camera Model                       | { D405 } |
| Firmware Version                   | 05.14.00.00 |
| Operating System & Version |   Win 10 |
| Platform                                 | PC  |
| SDK Version                            |  V2.53.1                      |
| Language                            |  {labview }                          |
| Segment			| others                          |
Issue Description
Dear friends, I have encountered this problem when using D405, please help to find out what the problem is, thank you.
I can successfully get the image from the example

|---------------------------------|------------------------------------------- |
But I can't get the image in labview.(The labview library I use is RealSense for Labview ver.2.33）

|---------------------------------|------------------------------------------- |
This is my test vi, please take a look（I modified the example "RealSense_HelloWorld_PointCloud.vi" mainly by removing the advanced configuration）

|---------------------------------|-------------------------------------------
Hope to get your help as soon as possible, thank you.

Hi @CJA-JIANG  Official support for the D405 camera model was introduced in SDK 2.51.1.  So whilst 2.53.1 can detect and use the camera, 2.33.1 will not be able to detect it.
I tested the D405 in the 2.33.1 version of the RealSense Viewer tool and confirmed that it was not detectable.

Hi @CJA-JIANG Official support for the D405 camera model was introduced in SDK 2.51.1. So whilst 2.53.1 can detect and use the camera, 2.33.1 will not be able to detect it.
I tested the D405 in the 2.33.1 version of the RealSense Viewer tool and confirmed that it was not detectable.
|---------------------------------|------------------------------------------- |
Hi @MartyG-RealSense
I have replaced realsense2.dll in RealSense for Labview ver. 2.33.0 with realsense2.dll in SDK 2.51.1, but it does not work.

There was a similar issue at https://github.com/IntelRealSense/librealsense/issues/7920 when using D455 with the LabVIEW wrapper, as its most recent update uses SDK 2.33.0 and D455 support was not introduced until SDK 2.38.0.  The RealSense user in that case copied the more modern realsense2.dll file to the LabVIEW folder and updated their camera firmware driver and it worked for them.
If you are using SDK 2.53.1 then you could copy the realsense2.dll from 2.53.1 and make sure that your camera firmware driver version is 5.14.0.0.
On Windows a pre-made dll can be obtained by installing version 2,53,1 of the full RealSense SDK using the Intel.RealSense.SDK-WIN10 installer file first.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.53.1

Afterwards, go to the computer location below and copy the realsense2.dll file from this folder into the LabVIEW folder.
C: > Program Files (x86) > Intel RealSense SDK 2.0 > bin > x64

Currently only the 2.51.1 and 2.53.1 SDKS support D405. I updated realsense2.dll to the labview folder several times and updated the firmware, and finally I could capture the image. But now there is a new problem, the color image is still not there, is there something wrong with my option?

On the D405 camera model there is not an RGB sensor, as RGB is obtained from the depth sensor instead.  Programs such as video chat applications that are designed to detect the RGB sensor may therefore not work as the D405 does not have an RGB camera driver, only a depth driver.

A strange situation occurred. The day before yesterday, D405 was able to get images using labview normally. However, when I tested it again today, it could not get images without modifying the program, and it still prompted Frame Timeout.
I tried to degrade the firmware, but it didn't work. I can't degrade the firmware now.

When will there be another appropriate SDK update?

How many times did you attempt to downgrade the firmware driver please?  RealSense cameras have a limit of 20 firmware downgrades, after which the camera can only be upgraded to a newer firmware version than the currently installed one for the rest of the camera's lifetime.
There is not a date available for the next RealSense SDK or firmware driver release, though the in-development version of the SDK that will become the next release can be found on the SDK's development GitHub branch.
https://github.com/IntelRealSense/librealsense/tree/development

I was able to get depth images as well as color images.
I'm using the following configuration
realsense2.dll：V2.51.1
firmware driver version ： 5.14.0.0
The color diagram cannot be obtained for the following reasons：

The index of a deep stream cannot be the same as that of a color stream, which will result in a different frame rate and an error.

Do you have the option to manually set depth to a frame rate of 60-90 instead of 30-60?  If you do, does doing this give left-color the same frame rate?

Hi @CJA-JIANG  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.

Hi @CJA-JIANG  A user of D405 with LabVIEW at https://github.com/IntelRealSense/librealsense/issues/12093#issuecomment-1675228924 managed to get it to work.

authors: CJA-JIANG MartyG-RealSense

repo: IntelRealSense/librealsense


text:
How can I get pointclouds as numpy object?

Required Info

Camera Model
D400

Operating System & Version
Linux  Ubuntu 16

Kernel Version (Linux Only)
4.10.17

Platform
PC

SDK Version
2.0

Python Version
3.5

I want to get pointcloud as a numpy object.
I supposed that the pointcloud can be obtained as below,
pc = rs.pointcloud()
points = rs.points()
pipe = rs.pipeline()
pipe.start()

frames = pipe.wait_for_frames()
depth = frames.get_depth_frame()
color = frames.get_color_frame()

pc.map_to(color)
points = pc.calculate(depth)
points_data = points.get_data()
np_points = np.asanyarray(points_data)

print(np_points)

but this code returns an empty list.
I checked that the points are successfully obtained by using export_ply_example.py.
Do you have any ideas to solve it?

You need to take the points not data of the points.
np_points = np.asanyarray(points)

You should use get_vertices:
pc = rs.pointcloud()
pc.map_to(color)
points = pc.calculate(depth)
vtx = np.asanyarray(points.get_vertices())
tex = np.asanyarray(points.get_texture_coordinates())

@zivsha
Thank you so much! It successfully worked.


text:
c#-wrapper - Frame did not arrive in time!

Required Info

Camera Model
D435

Firmware Version
05.08.15.00

Operating System & Version
Win10

Kernel Version (Linux Only)
-

Platform
PC

SDK Version
2.0

Issue Description
While debugging the cs-tutorial-1-depth-tutorial from the c#-wrapper an exception appears after some seconds. See:
System.Exception
HResult=0x80131500
Message=Frame did not arrive in time!
rs2_wait_for_frame(queue:000000001D8C0520)
Source=
StackTrace:

[Realsense Customer Engineering Team Comment]
hi @Tkong1,
could you please tell if RealSense Viewer also have this issue on your PC or only the C#-wrapper sample?
thanks.

hi @RealSense-Customer-Engineering ,
in RealSense Viewer after some seconds also an exception appears:
Oops, something went wrong!
RealSense error calling:
Unknown in rs2_close(sensor:000002568359BD60): profile not found
But the Error appears not always.

[Realsense Customer Engineering Team Comment]
hi @Tkong1,
since Realsense Viewer have issue, I think we should fix this before we move to C# wrapper issue..
would like to confirm before realsense viewer report error, do you see the D435 depth stream?
please also confirm your cable is USB3 certified.
thanks.

[Realsense Customer Engineering Team Comment]
hi @Tkong1,
do you still have this issue with latest release now?

[Realsense Customer Engineering Team Comment]
let me close this ticket here, please feel free to open new ticket if any follow question.


text:
How can I generate a .PLY file from XYZ coordinate data ?

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D400

Firmware Version
05.11.10.00

Operating System & Version
Win 10

Platform
PC

SDK Version
2.23

Language
C#

Segment
others

Issue Description
Hi, I'm new in coding and Realsense.
I know that there's an example call ExportToPLY and it use depth image as input. Because I do segmentation on my depth frame, I have to convert .ply file by myself from my 2-D ushort array.
There's "x, y, z" data of each pixel in my 2-D ushort array. I want to convert these xyz data to a .ply file. I know that there's a header in the .ply file. But it seems that not only the vertex elements, I also have to get the face elements to generate the .ply file.
So my question is how to get the face elements from x, y, z data or depth image?
Thankful!!

I've found another way to get my .ply data.


text:
Can not get IMU data on Android using D435i

Camera Model  : D435i
Firmware Version: 5.12.1
Platform : Android
librealsense SDK: build 2.31.0
I am trying to get IMU data using D435i camera on android and i get below  error
2019-12-26 14:28:01.323 7311-7377/? I/librs: Motion Module - no intrinsic calibration, Depth Module V2 intrinsic invalidated : Accel !
2019-12-26 14:28:01.324 7311-7377/? I/chatty: uid=10299(com.samsung.id8.caneapp) identical 3 lines
2019-12-26 14:28:01.330 7311-7377/? I/librs: Motion Module - no intrinsic calibration, Depth Module V2 intrinsic invalidated : Accel !
2019-12-26 14:28:01.346 7311-7377/? I/librs: Motion Module - no intrinsic calibration, Depth Module V2 intrinsic invalidated : Accel !
2019-12-26 14:28:01.350 7311-7377/? I/librs: Motion Module - no intrinsic calibration, Depth Module V2 intrinsic invalidated : Accel !
2019-12-26 14:28:01.352 7311-7311/? E/CaneApp: streaming, error: this profile is not extendable to MOTION
2019-12-26 14:28:01.352 7311-7311/? D/InputMethodManager: prepareNavigationBarInfo() DecorView@e341840[MainActivity]
2019-12-26 14:28:01.352 7311-7311/? D/InputMethodManager: getNavigationBarColor() -855310
2019-12-26 14:28:01.352 7311-7311/? V/InputMethodManager: Starting input: tba=com.samsung.id8.caneapp ic=null mNaviBarColor -855310 mIsGetNaviBarColorSuccess true , NavVisible : true , NavTrans : false
2019-12-26 14:28:01.352 7311-7311/? D/InputMethodManager: startInputInner - Id : 0
2019-12-26 14:28:01.356 7311-7377/? I/librs: Motion Module - no intrinsic calibration, Depth Module V2 intrinsic invalidated : Accel !
2019-12-26 14:28:01.361 7311-7377/? I/librs: Motion Module - no intrinsic calibration, Depth Module V2 intrinsic invalidated : Accel !
2019-12-26 14:28:01.362 7311-7377/? I/librs: Motion Module - no intrinsic calibration, Depth Module V2 intrinsic invalidated : Accel !

Apologies that you did not receive a response to your question before now.
The ability to access IMU data with a D435i on Android was added in RealSense SDK version 2.26.0 in August 2019, so you should have been able to access it with the SDK version 2.31.0 that you were using in December 2019.
https://github.com/IntelRealSense/librealsense/pull/4605
Are you still experiencing this problem please with the current RealSense SDK version, or can this case be closed?  Thanks!


text:
D455 motion Module not streaming realsense viewer

Required Info

Camera Model
D455

Firmware Version
05.12.07.100

Operating System & Version
Linux (FriendlyDesktop)

Kernel Version (Linux Only)
4.4.179

Platform
NanoPi NEO4

SDK Version
2.38.1

Language
C++

Segment
Robot

Issue Description
I've been trying to get the motion data from the d455, and struggling. I tried using Realsense Viewer to see if I can use that for motion data, however, turning on the motion stream doesn't seem to change the Pitch, roll and yaw of the camera regardless of rotation. Furthermore,  as well as some calibration errors. How do I resolve this?

Hi @noblegasses   You should switch the RealSense Viewer into 2D mode with the 2D option in the top corner of the Viewer to view the gyro and accel data of the Motion Module.
Are you able to view the Motion Module data successfully if you switch the Viewer to 2D mode please?

If you believe that you are getting ncorrect values for roll, pitch and yaw from the IMU, you may find the discussion in the link below useful.
https://github.com/IntelRealSense/librealsense/issues/4391

Required Info
Camera Model	D455
Firmware Version	05.12.07.100
Operating System & Version	Linux (FriendlyDesktop)
Kernel Version (Linux Only)	4.4.179
Platform	NanoPi NEO4
SDK Version	2.38.1
Language	C++
Segment	Robot
Issue Description
I've been trying to get the motion data from the d455, and struggling. I tried using Realsense Viewer to see if I can use that for motion data, however, turning on the motion stream doesn't seem to change the Pitch, roll and yaw of the camera regardless of rotation. Furthermore, as well as some calibration errors. How do I resolve this?

Hi ！I test the code below with a 75FPS, could you show your result? Thanks very much!
Test Program
// include the librealsense C++ header file
#include <librealsense2/rs.hpp>

#include <opencv2/opencv.hpp>

#include <chrono>

using namespace std;
using namespace cv;

int main()
try
{
    //Contruct a pipeline which abstracts the device
    rs2::pipeline pipe;

    //Create a configuration for configuring the pipeline with a non default profile
    rs2::config cfg;
    //Add desired streams to configuration
    cfg.enable_stream(RS2_STREAM_COLOR, 480, 270, RS2_FORMAT_BGR8, 90);

    //Instruct pipeline to start streaming with the requested configuration
    pipe.start(cfg);

    //Sensor Settings
    auto sensor1 = pipe.get_active_profile().get_device().query_sensors()[1];
    sensor1.set_option(RS2_OPTION_ENABLE_AUTO_EXPOSURE, 1);
    auto sensor2 = pipe.get_active_profile().get_device().query_sensors()[1];
    sensor2.set_option(RS2_OPTION_AUTO_EXPOSURE_PRIORITY, 0);

    // Display in a GUI
    const auto window_name = "Display Video";
    namedWindow(window_name, WINDOW_AUTOSIZE);

    //用于计时
    //show time
    auto start = chrono::system_clock::now();
    int frame = 0;

    while (waitKey(1) < 0 && getWindowProperty(window_name, WND_PROP_AUTOSIZE) >= 0)
    {
        rs2::frameset data = pipe.wait_for_frames(); // Wait for next set of frames from the camera

        //获取彩色图像帧
        rs2::frame color = data.get_color_frame();

        //保存彩色图像
        Mat image(Size(480, 270), CV_8UC3, (void *)color.get_data(), Mat::AUTO_STEP);

        // Update the window with new data
        imshow(window_name, image);

        frame++;
        //one loop end
        auto end = chrono::system_clock::now();
        auto duration = chrono::duration_cast<chrono::microseconds>(end - start);
        double timecost = double(duration.count()) * chrono::microseconds::period::num / chrono::microseconds::period::den;

        cout << frame / timecost << " FPS" << endl;
    }

    return 0;
}
catch (Exception ex)
{
    cout << "Error!!!" << endl;
    cerr << ex.msg << endl;
}

Hi @FrankCreen    Please post your question as a new issue using the New Issue button at the link below and do not post it on multiple D455 cases if the question is unrelated to that case.   Thank you.
https://github.com/IntelRealSense/librealsense/issues/

Hi,
thanks, the 2d view solves my issue. this might require opening a separate issue, but how do I stream this data in c++ or python? the pose stream seems to fail, as does storing the accel and gyro streams in frames.

Hi @noblegasses   You could take a look at the SDK's rs-motion C++ example program.
https://github.com/IntelRealSense/librealsense/tree/master/examples/motion
If you plan to stream depth, color and IMU simultaneously then putting IMU on one pipeline and depth and color on the other can improve performance.  The link below has a Python example script for this:
https://github.com/IntelRealSense/librealsense/issues/5628#issuecomment-575943238

Hi @noblegasses   Do you require further assistance with this case, please?   Thanks!

my apologies, I don't require any further help at this time. I simply forgot to close the issue. Thanks!

No apologies needed - thanks very much for the update!

authors: FrankCreen MartyG-RealSense noblegasses


text:
Education & External activities are not passed returned by API

Education & External activities are not returned when requested through the API. All activities should, however, be returned. The source property should be set accordingly, which is now always inter-actief.

source needs to be the organising party, so Inter-Actief for IA-activities, and for example OVSoftware for a company event by OVSoftware.

authors: Kurocon SebastiaandenBoer

repo: Inter-Actief/amelie


text:
.bgeo output files not working with houdini or vray

The .bgeo output Files are not readable for Houdini or Vray.
Houdini error message:
Expected array object (near byte offset 32, line 1, column 33)
Backend IO
Vray error message:
ply2vrmesh (Converter for .obj or .bgeo to .vrmesh)
error: Error reading file: [VUtils::BGeoInterface::readFile] 2: Error reading .bgeo file: Magic number not found
[0h 0m 0.0s] [5 MB] error: [VUtils::BGeoInterface::readFile] 2: Error reading .bgeo file: Magic number not found

At the moment my Workaround is to use Splashsurf to generate .obj's and then convert them to .vrmesh
I tried already to change the library, but the error is still the samen. But maybe i did it not in right way.
Is there an internal surface reconstruction in Splishsplash?

Is there an internal surface reconstruction in Splishsplash?

No. splashsurf is the surface reconstruction which we just develop.


text:
Some properties of TUIO Objects and Cursors are missing data.

In both Tuio 1.1 and 2.0, objects and cursors are not returning data for a few properties.
TuioContainer misses data in Velocity, Speed, Acceleration, RotationSpeed, and RotationAcceleration properties.
TuioCursor misses data in Pressure, PressureSpeed, PressureAcceleration, Shear, and TypeUserId properties.
Note: Some properties I mentioned here are only in TUIO 2.0.
I see that the above-mentioned data is calculated in the Tuio Server running in the Capore API Box and is being sent to the TUIO clients. Looking at the code, I infer that the TUIO client is not receiving the data.
Also, I would like to know if pressure is supported by Interactive Scape displays.

Hey @sathish-mountvisual
I fixed the missing properties for Tuio 1.1. there was a bug in the time calculation. For Tuio 2.0 it is not working yet properly. Could you test it for Tuio 1.1 with this branch here? Thank you

@eqbic, I tested your branch.
All the Tuio11 property values that I get are perfect.

And it would be a good idea to set the calculated properties like Velocity, Speed, Acceleration, etc to zero when the object is removed.
If not, then the Tuio11 data that's passed on through OnRemoved() will have values from the previous frame.

I noticed an issue in Tuio11Object.
dt calculation uses StartTime instead of CurrentTime.

authors: eqbic sathish-mountvisual

repo: InteractiveScapeGmbH/TuioNet


text:
[feature] how to set num_workers to speed loading dataset?

When I run NPROC_PER_NODE=8 xtuner train llama2_7b_qlora_moss_sft_all_e2_gpu8, the speed of loading moss data is slow:
708it [00:02, 355.86it/s]09/11 13:02:29 - mmengine - INFO - Loading MOSS SFT data...
555779it [36:16, 237.63it/s]

So sorry for that, but at present, we do not support parallel processing of MOSS dataset.
However, this long time processing (about 1 hour) only needs to be done one time. After the first processing, the cache will be automatically saved to the dataset path, and will be automatically loaded and used in the future.

authors: LZHgrla amulil

repo: InternLM/xtuner


text:
[FR] - Support aarch64-linux in Nix Flake

External
Area
Regarding the build system outputs
Describe the feature you'd like
I would like to build cardano-cli on aarch64-linux via the nix flake.
I use aarch64-linux in a virtual machine on my mac and raspberry pi is also aarch64-linux.
Here's what I would like to do:
nix build github:intersectmbo/cardano-node#packages.aarch64-linux.cardano-cli
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I think you can build it on aarch64-linux but as far I know not via the nix flake.
If I'm missing something please let me know.

Related comment and PR: https://github.com/IntersectMBO/cardano-cli/pull/686#issuecomment-2033090278

I use aarch64-linux in a virtual machine

Do you need to build on aarch64-linux natively, or a cross-compilation to aarch64-linux would
be sufficient? We have a PR enabling cross-compilation. Does that work for you: https://github.com/IntersectMBO/cardano-cli/pull/819 ?

I need it natively. I want to use my raspi 5 as an airgaped machine. I have nix installed on it and when cardano-cli has a new update I could move the files of this repository via a usb stick on my pi and compile the new version. If someone has a better alternative to work around this I'll would love to hear it.
Using nix build blablabla is way easier for me then manually installing all sorts of tools because of my visual impairment.

Reopening because #819 introduced production of aarch64-linux binaries (via cross compilation), but it's still not supported by the flake (which is what this issue is about).

authors: carbolymer sempruijs smelc

repo: IntersectMBO/cardano-cli