Don't ask to publish to npm if the repository is marked as private

This closes #18
FYI: This PR needs to be squashed and possibly rebased depending on the order of PRs closed

this was already merged previously


pull requests will create a website preview

No this does not seem to work.

No this does not seem to work.

Correction: It does seem to work, just needs some time to build.

But a direct push (different commit) seems to have deleted it.


We aren't displaying a user box any more, so get rid of this

This is old code to suppress displaying the user part (login/logout) but we aren't displaying this during the installer any more.


StaticImage not rendering in iOS Safari/Chrome

Describe the bug
Image rendered using ImageStatic class doesn't render on iOS (Safari/Chrome) if it exceeds certain dimensions.
To Reproduce
Prerequisites: Use iOS 15 or later

Go to CodeSandbox

Expected behavior
An image should appear. You can zoom and pan the image.
Actual result
No image appears on iOS.
CodeSandbox
https://codesandbox.io/s/openlayers-7-ios-canvas-limit-exceeded-7pv3l2?file=/main.js
Other notes
In the developer console there's a warning like the following:

Canvas area exceeds the maximum limit (width * height > 16777216)

I updated the codesandbox example to do exactly that, yet the image didn't show up with<EMAIL_ADDRESS>However downgrading the codesandbox to<EMAIL_ADDRESS>made the problem go away. So it seems the issue was introduced in 7.3.0.

Probably https://github.com/openlayers/openlayers/pull/14444 ?

Yes, you are probably right @mediafreakch. The problem that #14444 solved could alternatively be solved by working with only the part of the image that the renderer currently needs, like e.g. the ImageWMS source. If someone feels up for such a change, a pull request would be welcome.

Will #14444 be rolled back? A bad performance is better than a broken feature... Otherwise we're stuck on 7.2.2 until this is resolved for iOS devices.

A rollback of #14444 will be part of the change that also makes it work on iOS.  Otherwise it's too much back and forth, because like you rely on having #14444 rolled back, others rely on #14444 being there.


Feature/qj move cloud drivers to multicloud 2.11

这个 PR 实现什么功能/修复什么问题:
将release/2.11云适配代码从pkg/util挪到pkg/multicloud
是否需要 backport 到之前的 release 分支:
NONE

/area region

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@4662b82). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #1977   +/-   ##
==============================================
  Coverage                ?   7.19%
==============================================
  Files                   ?     445
  Lines                   ?   69245
  Branches                ?       0
==============================================
  Hits                    ?    4985
  Misses                  ?   63848
  Partials                ?     412

Flag
Coverage Δ

#aFlag
7.19% <0%> (?)

Impacted Files
Coverage Δ

pkg/multicloud/aws/reservedinstance.go
0% <ø> (ø)

pkg/multicloud/aws/loadbalancerbackend.go
0% <ø> (ø)

pkg/multicloud/aws/snapshot.go
0% <ø> (ø)

pkg/multicloud/esxi/host.go
2.24% <ø> (ø)

pkg/multicloud/aws/loadbalancer.go
0% <ø> (ø)

pkg/compute/models/cloudsyncelb.go
0% <ø> (ø)

pkg/multicloud/aws/loadbalancerlistenerrule.go
0% <ø> (ø)

pkg/multicloud/aws/network.go
0% <ø> (ø)

pkg/multicloud/aws/loadbalancerlistener.go
0% <ø> (ø)

pkg/multicloud/esxi/hostnic.go
0% <ø> (ø)

... and 50 more

Continue to review full report at Codecov.

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


GD issue with output

The output() function is supposed to return the content of the image as a string.
https://github.com/imanee/imanee/blob/master/src/Imanee.php#L266.
As it's doing for the imagick driver.
The fix right now looks like something like this
ob_start();
imagejpeg($this->getResource(), null, 90);
$imageBlob = ob_get_contents();
ob_end_clean();
return $imageBlob

Should I make a pull request ?

Oh, that passed completely unnoticed to me. Yes please, I don't think there's another way to do it... Can you please send a PR?
Thank you @mikeSimonson !


Minor updates to Dropwizard example

Some simplification after #1290.
It's tempting to remove the package phase binding (and the command becomes ./mvnw clean compile jib:dockerBuild) too, but I guess that's fine.

@cricket007 for your interest.


Improve Card styles

Closes #8
Description
Improve Card styles
Current behavior (updates)
Very simple Card and also uses Grid
New behavior
Improved styles of Card and use Wrap
Is this a breaking change (Yes/No):
No

@taroj1205
please fix conflict


Updated Arm-LanguageServerVersion to 3.0.0-preview.19529.3

This includes an update to Microsoft.Azure.ARM.TemplateParser version to 1.0.5

Looking at failures...

Looks like I need to implement the scope work first.

Superseded


Home screen needs content

We need to put some content on the home screen to tell something about what tags app does, what it's capable of, and how you can be a part of it.

Suggestion from today's stream:  let's add a bit of markdown that can be configured for the application


Add flat modifiers to attacks

Is your feature request related to a problem? Please describe.
Sometimes when setting up an attack want to use a flat number instead of a skill
Describe the solution you'd like
Should be an alternative where you can just put in a number to you as the modifier instead of having to select a skill
Additional context
Suggested by @stanvdb on 22/10/2024
Checklist:

[x] I have searched the existing issues to ensure this feature has not already been requested.

I'm gonna grab this

OK, realised that we couldn't take the same approach as the damage mods this time, for a number of reasons, but the most obvious being that to do so would have been a complete refactor of the roll engine.
Instead I've given a couple of fields (one in the item details of activatable items with skill tests for global mods, and one in the roll configuration pop-ups for temporary ones) that allow the users to enter formula in a similar way to the damage override, only this will be an extension of what is already there. They'll still set the skill and attribute to use for the item's skill rolls as before and then this gets tacked on the end.
There is more to say on skill/attribute selection however as I allowed for skill ranks without an attribute, perhaps we should also allow attribute and no skill ranks? (Then the user can get full control of their roll formula, but also get some level of assisted setup)
But this bit is still a bit messy actually. Worth getting input and then sorting out alongside the sheets brush up in 0.3


api: generate merged descriptors when building protobufs

When we generate protobufs, descriptors outlining all messages and
services are merged into a single file that can be used to identify
unexpected changes to the API that may affect stability. We follow a
similar process to Go's stability guarantees using the protobuf
descriptors to identify changes before they become a problem.
Please see README.md for details.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

Do we want to do the same forlinux/runcopts/runc.proto and windows/hcsshimopts/hcsshim.proto?

Good question :man_shrugging:
In their own directory for now I guess.

@mlaventure Perhaps, these should be under the api directory. I'll them to the Protobuild.toml for now.

LGTM


Admin: Implement Github app

See details in Notion.
Task list:

[x] Implement Github redirect flow on admin server
[x] Implement Github webhooks on admin server
[x] Implement rill project connect command
[x] Implement MVP project management in admin

Closed by https://github.com/rilldata/rill-developer/pull/1842


When to use doc(hidden)

I think lazy_static does a nice job of this. How about a guideline to be mindful that formal rustdoc is supposed to include everything users need to use the crate fully, and nothing more. Okay to explain implementation details in prose (like lazy_static does) but they should not be real entries in the documentation.

Added in 24db1bb3f1560d83ba563e1b401dddb6b5070d62.


Which version support MathML ?

I test win launcher but it dose not support mathml .
https://code.google.com/p/epub-samples/downloads/detail?name=linear-algebra-20120306.epub&can=2&q=

Duplicate, and wrong repository:
https://github.com/readium/SDKLauncher-Windows/issues/8
@wzhsunn the ReadiumSDK application launchers on iOS, OSX and Android all support MathML via MathJax (as well as ReadiumJS "cloud reader" and Chrome extension). However, SDKLauncher-Windows is behind the other platforms due to lack of development resources for this particular C++ MFC implementation. Sorry for the inconvenience.

Thank you !


Create farroupilha.txt

Add farroupilha.ifrs.edu.br to the domain list.

@ebalbinot Pull request merged. Thank you!


Where does MSBuild look for implicit imports?

This says that the Sdk attribute/element is used "to create implicit Import statements that are added to the .proj file."  Where can I get more detail on how this works?  Based on the value of Sdk, what path and filename will MSBuild be importing?

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

ID: 9f2d4b23-f7b9-7f95-0690-7d528fb4b323
Version Independent ID: 2c45725e-2689-bfd3-001b-ea1f7043128a
Content: Project Element (MSBuild) - Visual Studio
Content Source: docs/msbuild/project-element-msbuild.md
Product: visual-studio-dev15
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

Hi, did you already find this topic? https://docs.microsoft.com/en-us/visualstudio/msbuild/how-to-use-project-sdk
There's a section on how the project SDKs are resolved. There are links to additional .NET topics for the Sdk element at the bottom of the page.

I hadn’t seen that page before.  Thanks; that’s very helpful.  I do wish there was more detail on SDK resolvers—how does the resolution process work? How does it decide which folder to look for sdk.props/targets?
But thanks for pointing me to this page.  It still has lots of useful information.

From: Mike Jones<EMAIL_ADDRESS>Sent: Friday, July 20, 2018 5:07:20 PM
To: MicrosoftDocs/visualstudio-docs
Cc: Jazzman; Author
Subject: Re: [MicrosoftDocs/visualstudio-docs] Where does MSBuild look for implicit imports? (#1225)
Hi, did you already find this topic? https://docs.microsoft.com/en-us/visualstudio/msbuild/how-to-use-project-sdkhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvisualstudio%2Fmsbuild%2Fhow-to-use-project-sdk&data=02|01||bf1d26050f9d474ae5cb08d5ee958cc3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636677248427153039&sdata=TcgWp9dtSPLQB5R5DGyeaB%2B%2BEIgDwimWcS0UCatSEgo%3D&reserved=0
There's a section on how the project SDKs are resolved. There are links to additional .NET topics for the Sdk element at the bottom of the page.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fvisualstudio-docs%2Fissues%2F1225%23issuecomment-406747944&data=02|01||bf1d26050f9d474ae5cb08d5ee958cc3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636677248427153039&sdata=0BWtbYg4lSefA4713BMoa6ludx10zn9zp7WTOnH1KZk%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANsoZf3IpAPt7PMEoCdW2clnoDwe2rgVks5uImKogaJpZM4VIa_5&data=02|01||bf1d26050f9d474ae5cb08d5ee958cc3|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636677248427153039&sdata=0GqPT9RbFuyNdZbYj6QUr29EWT8Gy680li8%2F14XkEaI%3D&reserved=0.


Image smaller than the container should not be upscaled when "fill" is set to false

When "fill" is set to false, image smaller than the container is upscaled.
With this commit, the small image is displayed in its original size in the container.

tnxs


[2.x] Use version of httpclient 4 from core's buildSrc/version.properties

Description
This PR solves for the issue in backwards compatibility tests seen in PRs like: https://github.com/opensearch-project/security/pull/2949
> Task :compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Could not resolve all dependencies for configuration ':compileClasspath'.
   > Conflict(s) found for the following module(s):
       - org.apache.httpcomponents:httpclient between versions 4.5.14 and 4.5.13
     Run with:
         --scan or
         :dependencyInsight --configuration compileClasspath --dependency org.apache.httpcomponents:httpclient
     to get more insight on how to solve the conflict.

Category (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Maintenance
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Manual backport for the core refactor change created: https://github.com/opensearch-project/security/pull/2953
Should I bundle this change into that PR?

Closing this PR and incorporating the changes its introducing into this PR: https://github.com/opensearch-project/security/pull/2953


Stopped reading barcodes after updating to API 23

Description of the problem:
I am testing this library for an app. Originally it was working fine under API 19 and 21, then after updating for my phone (Android M - 23 I believe - because I wanted quick run), the scanner will now "stare" and "blink" at barcodes and not return back to the  onActivityResult() callback. Barcodes are nice and clear on the display. Again, everything worked fine prior. There are no errors but I am attaching the log, if it can be helpful. The zx barcode scanner app works. I have other zx apps and they work fine, wanted to try something more lightweight.
04-06 18:07:30.825 15990-20199/com.example.lenny.testapp D/CameraInstance: Opening camera
04-06 18:07:30.827 15990-15990/com.example.lenny.testapp I/SensorManager: registerListenerImpl() [Sensor: LGE Accelerometer, Rate: 200000, SensorEventListener: android.view.OrientationEventListener$SensorEventListenerImpl@75ae631] by android.view.OrientationEventListener.enable():93
04-06 18:07:30.838 15990-15990/com.example.lenny.testapp D/PhoneWindow: notifyNavigationBarColor, color=0x: ff000000, token: android.view.ViewRootImplAO$WEx@141e484
04-06 18:07:30.857 15990-16495/com.example.lenny.testapp E/Surface: getSlotFromBufferLocked: unknown buffer: 0x9749dd30
04-06 18:07:30.857 15990-16495/com.example.lenny.testapp D/OpenGLRenderer: endAllActiveAnimators on 0x98c3c480 (RippleDrawable) with handle 0x8e13fb80
04-06 18:07:30.920 15990-15990/com.example.lenny.testapp V/ViewRootImpl: Contents drawing finished : com.example.lenny.testapp/com.journeyapps.barcodescanner.CaptureActivity
04-06 18:07:30.931 15990-15990/com.example.lenny.testapp I/Timeline: Timeline: Activity_idle id: android.os.BinderProxy@8e53dbb time:69072966
04-06 18:07:31.254 15990-20199/com.example.lenny.testapp D/CameraInstance: Configuring camera
04-06 18:07:31.254 15990-20199/com.example.lenny.testapp I/CameraManager: Camera Display Orientation: 0
04-06 18:07:31.258 15990-20199/com.example.lenny.testapp I/CameraManager: Initial camera parameters: ae-bracket-hdr=Off;ae-bracket-hdr-values=Off,AE-Bracket;af-bracket=af-bracket-off;af-bracket-values=af-bracket-off,af-bracket-on;antibanding=auto;antibanding-values=off,60hz,50hz,auto;auto-exposure=center-weighted;auto-exposure-lock=false;auto-exposure-lock-supported=true;auto-exposure-values=frame-average,center-weighted,spot-metering,smart-metering,center-weighted,spot-metering-adv,center-weighted-adv;auto-hdr-supported=true;auto-whitebalance-lock=false;auto-whitebalance-lock-supported=true;avtimer=disable;backlight-condition=low;brightness-step=1;camera-mode=0;capture-burst-exposures=0,10,-9;contrast=5;contrast-step=1;cto-face-detection=on;cto-face-detection-height=480;cto-face-detection-illuminance=0;cto-face-detection-multidirection=0;cto-face-detection-width=640;denoise=denoise-off;denoise-values=denoise-off,denoise-on;dis=disable;dis-values=enable,disable;effect=none;effect-values=none,mono,negative,solarize,sepia,posterize,whiteboard,blackboard,aqua,emboss,sketch,neon;exposure-compensation=0;exposure-compensation-step=0.166667;f-number=2.4;face-detection=off;face-detection-values=off,on;flash-mode=off;flash-mode-values=off,auto,on,torch;flash-status=off;flip-mode-values=off,flip-v,flip-h,flip-vh;focal-length=3.97;focus-areas=(0, 0, 0, 0, 0);focus-distances=0.100000,0.150000,0.170000;focus-mode=auto;focus-mode-values=auto,infinity,macro,continuous-video,continuous-picture,mw_continuous-picture;hfr-size-values=;histogram=disable;histogram-values=enable,disable;horizontal-view-angle=60.8;internal-restart=true;iso=auto;iso-values=auto,ISO_HJR,ISO100,ISO200,ISO400,ISO800,ISO1600,auto;jpeg-quality=97;jpeg-thumbnail-height=288;jpeg-thumbnail-quality=85;jpeg-thumbnail-size-values=512x288,480x288,256x154,432x288,384x240,320x320,320x240,176x144,0x0;jpeg-thumbnail-width=512;lensshade=enable;lensshade-values=enable,disable;lge-camera=0;long-shot=off;longshot-supported=true;luma-adaptation=3;luminance-condition=high;luminance-condition-for-video=high;max-brightness=6;max-contrast=10;max-exposure-compensation=12;max-exposure-time=2000000;max-focus-pos-index=60;max-num-detected-faces-hw=5;max-num-detected-faces-sw=5;max-num-focus-areas=1;max-num-metering-areas=5;max-saturation=10;max-sce-factor=100;max-sharpness=36;max-wb-cct=8000;max-zoom=90;mce=enable;mce-values=enable,disable;metering-areas=(0, 0, 0, 0, 0);min-brightness=0;min-contrast=0;min-exposure-compensation=-12;min-exposure-time=200;min-focus-pos-dac=1023;min-focus-pos-index=40;min-saturation=0;min-sce-factor=-100;min-sharpness=0;min-wb-cct=2000;multi-window-focus-area=(-280,-280,0,0,1),(-140,-420,140,-140,1),(0,-280,280,0,1),(-420,-140,-140,140,1),(-140,-140,140,140,1),(140,-140,420,140,1),(-280,0,0,280,1),(-140,140,140,420,1),(0,0,280,280,1),(-220,-220,220,220,1);multi-window-focus-zone-touch=(720,720,1000,1000,1),(860,580,1140,860,1),(1000,720,1280,1000,1),(580,860,860,1140,1),(860,860,1140,1140,1),(1140,860,1420,1140,1),(720,1000,1000,1420,1),(860,1140,1140,1420,1),(1000,1000,1280,1280,1);num-snaps-per-shutter=1;picture-format=jpeg;picture-format-values=jpeg,bayer-mipi-10bggr,bayer-ideal-qcom-10bggr,bayer-qcom-10bggr,yuv422sp;picture-size=1280x960;picture-size-values=4160x3120,4160x2340,4000x3000,3264x2448,3264x1840,3200x2400,2592x1944,2560x1920,2560x1600,2048x1536,1920x1080,1600x1200,1440x1080,1280x960,1280x768,1280x720,1024x768,800x600,800x480,720x480,640x480,352x288,320x240,176x144;preferred-preview-size-for-video=1920x1080;preview-flip=off;preview-format=yuv420sp;preview-format-values=yuv420sp,yuv420p,nv12-venus;preview-fps-range=5000,30000;preview-fps-range-values=(15000,15000),(5000,30000),(10000,30000),(30000,30000);preview-frame-rate=30;preview-frame-rate-values=5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30;preview-off=0;preview-size=1280x960;preview-size-values=2560x1440,1920x1440,1920x1080,1776x1080,1600x1200,1440x1080,1280x960,1280x800,1280x720,960x720,864x480,880x720,848x480,800x480,768x432,720x480,640x480,576x432,480x320,384x288,352x288,320x240,240x160,176x144;psv
04-06 18:07:31.258 15990-20199/com.example.lenny.testapp I/CameraConfiguration: Requesting focus mode value from among: [auto]
04-06 18:07:31.258 15990-20199/com.example.lenny.testapp I/CameraConfiguration: Supported focus mode values: [auto, infinity, macro, continuous-video, continuous-picture, mw_continuous-picture]
04-06 18:07:31.258 15990-20199/com.example.lenny.testapp I/CameraConfiguration: Can set focus mode to: auto
04-06 18:07:31.258 15990-20199/com.example.lenny.testapp I/CameraConfiguration: Focus mode already set to auto
04-06 18:07:31.258 15990-20199/com.example.lenny.testapp I/CameraConfiguration: Requesting flash mode value from among: [off]
04-06 18:07:31.258 15990-20199/com.example.lenny.testapp I/CameraConfiguration: Supported flash mode values: [off, auto, on, torch]
04-06 18:07:31.258 15990-20199/com.example.lenny.testapp I/CameraConfiguration: Can set flash mode to: off
04-06 18:07:31.258 15990-20199/com.example.lenny.testapp I/CameraConfiguration: Flash mode already set to off
04-06 18:07:31.265 15990-20199/com.example.lenny.testapp I/PreviewScalingStrategy: Viewfinder size: 2392x1440
04-06 18:07:31.266 15990-20199/com.example.lenny.testapp I/PreviewScalingStrategy: Preview in order of preference: [2560x1440, 1776x1080, 1920x1080, 1920x1440, 1600x1200, 1280x800, 1440x1080, 1280x720, 1280x960, 800x480, 960x720, 848x480, 864x480, 768x432, 720x480, 880x720, 640x480, 576x432, 480x320, 384x288, 352x288, 320x240, 240x160, 176x144]
04-06 18:07:31.266 15990-20199/com.example.lenny.testapp I/CameraManager: Final camera parameters: ae-bracket-hdr=Off;ae-bracket-hdr-values=Off,AE-Bracket;af-bracket=af-bracket-off;af-bracket-values=af-bracket-off,af-bracket-on;antibanding=auto;antibanding-values=off,60hz,50hz,auto;auto-exposure=center-weighted;auto-exposure-lock=false;auto-exposure-lock-supported=true;auto-exposure-values=frame-average,center-weighted,spot-metering,smart-metering,center-weighted,spot-metering-adv,center-weighted-adv;auto-hdr-supported=true;auto-whitebalance-lock=false;auto-whitebalance-lock-supported=true;avtimer=disable;backlight-condition=low;brightness-step=1;camera-mode=0;capture-burst-exposures=0,10,-9;contrast=5;contrast-step=1;cto-face-detection=on;cto-face-detection-height=480;cto-face-detection-illuminance=0;cto-face-detection-multidirection=0;cto-face-detection-width=640;denoise=denoise-off;denoise-values=denoise-off,denoise-on;dis=disable;dis-values=enable,disable;effect=none;effect-values=none,mono,negative,solarize,sepia,posterize,whiteboard,blackboard,aqua,emboss,sketch,neon;exposure-compensation=0;exposure-compensation-step=0.166667;f-number=2.4;face-detection=off;face-detection-values=off,on;flash-mode=off;flash-mode-values=off,auto,on,torch;flash-status=off;flip-mode-values=off,flip-v,flip-h,flip-vh;focal-length=3.97;focus-areas=(0, 0, 0, 0, 0);focus-distances=0.100000,0.150000,0.170000;focus-mode=auto;focus-mode-values=auto,infinity,macro,continuous-video,continuous-picture,mw_continuous-picture;hfr-size-values=;histogram=disable;histogram-values=enable,disable;horizontal-view-angle=60.8;internal-restart=true;iso=auto;iso-values=auto,ISO_HJR,ISO100,ISO200,ISO400,ISO800,ISO1600,auto;jpeg-quality=97;jpeg-thumbnail-height=288;jpeg-thumbnail-quality=85;jpeg-thumbnail-size-values=512x288,480x288,256x154,432x288,384x240,320x320,320x240,176x144,0x0;jpeg-thumbnail-width=512;lensshade=enable;lensshade-values=enable,disable;lge-camera=0;long-shot=off;longshot-supported=true;luma-adaptation=3;luminance-condition=high;luminance-condition-for-video=high;max-brightness=6;max-contrast=10;max-exposure-compensation=12;max-exposure-time=2000000;max-focus-pos-index=60;max-num-detected-faces-hw=5;max-num-detected-faces-sw=5;max-num-focus-areas=1;max-num-metering-areas=5;max-saturation=10;max-sce-factor=100;max-sharpness=36;max-wb-cct=8000;max-zoom=90;mce=enable;mce-values=enable,disable;metering-areas=(0, 0, 0, 0, 0);min-brightness=0;min-contrast=0;min-exposure-compensation=-12;min-exposure-time=200;min-focus-pos-dac=1023;min-focus-pos-index=40;min-saturation=0;min-sce-factor=-100;min-sharpness=0;min-wb-cct=2000;multi-window-focus-area=(-280,-280,0,0,1),(-140,-420,140,-140,1),(0,-280,280,0,1),(-420,-140,-140,140,1),(-140,-140,140,140,1),(140,-140,420,140,1),(-280,0,0,280,1),(-140,140,140,420,1),(0,0,280,280,1),(-220,-220,220,220,1);multi-window-focus-zone-touch=(720,720,1000,1000,1),(860,580,1140,860,1),(1000,720,1280,1000,1),(580,860,860,1140,1),(860,860,1140,1140,1),(1140,860,1420,1140,1),(720,1000,1000,1420,1),(860,1140,1140,1420,1),(1000,1000,1280,1280,1);num-snaps-per-shutter=1;picture-format=jpeg;picture-format-values=jpeg,bayer-mipi-10bggr,bayer-ideal-qcom-10bggr,bayer-qcom-10bggr,yuv422sp;picture-size=1280x960;picture-size-values=4160x3120,4160x2340,4000x3000,3264x2448,3264x1840,3200x2400,2592x1944,2560x1920,2560x1600,2048x1536,1920x1080,1600x1200,1440x1080,1280x960,1280x768,1280x720,1024x768,800x600,800x480,720x480,640x480,352x288,320x240,176x144;preferred-preview-size-for-video=1920x1080;preview-flip=off;preview-format=yuv420sp;preview-format-values=yuv420sp,yuv420p,nv12-venus;preview-fps-range=5000,30000;preview-fps-range-values=(15000,15000),(5000,30000),(10000,30000),(30000,30000);preview-frame-rate=30;preview-frame-rate-values=5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30;preview-off=0;preview-size-values=2560x1440,1920x1440,1920x1080,1776x1080,1600x1200,1440x1080,1280x960,1280x800,1280x720,960x720,864x480,880x720,848x480,800x480,768x432,720x480,640x480,576x432,480x320,384x288,352x288,320x240,240x160,176x144;psvt-mode=0;qc-camera-featu
04-06 18:07:31.273 15990-15990/com.example.lenny.testapp I/CenterCropStrategy: Preview: 2560x1440; Scaled: 2560x1440; Want: 2392x1440
04-06 18:07:31.298 15990-15990/com.example.lenny.testapp I/CameraPreview: Starting preview
04-06 18:07:31.298 15990-20199/com.example.lenny.testapp D/CameraInstance: Starting preview
04-06 18:07:31.367 15990-20199/com.example.lenny.testapp I/AutoFocusManager: Current focus mode 'auto'; use auto focus? true
04-06 18:08:20.388 15990-15998/com.example.lenny.testapp W/art: Suspending all threads took: 5.564ms
04-06 18:08:35.024 15990-15990/com.example.lenny.testapp I/ViewRootImpl: ViewRoot's KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_BACK, scanCode=0, metaState=0, flags=0x48, repeatCount=0, eventTime=69137049, downTime=69137049, deviceId=-1, source=0x101 } to com.android.internal.policy.PhoneWindow$DecorView{ee238a2 V.E...... R....... 0,0-2392,1440}
04-06 18:08:35.035 15990-15990/com.example.lenny.testapp I/AudioManagerEx: AudioManagerEx created
04-06 18:08:35.161 15990-15990/com.example.lenny.testapp I/ViewRootImpl: ViewRoot's KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=0, metaState=0, flags=0x48, repeatCount=0, eventTime=69137188, downTime=69137049, deviceId=-1, source=0x101 } to com.android.internal.policy.PhoneWindow$DecorView{ee238a2 V.E...... R....... 0,0-2392,1440}
04-06 18:08:35.173 15990-15990/com.example.lenny.testapp D/CameraPreview: pause()
04-06 18:08:35.173 15990-20199/com.example.lenny.testapp D/CameraInstance: Closing camera
04-06 18:08:35.174 15990-15990/com.example.lenny.testapp I/SensorManager: removeAllSensors() [Sensor: LGE Accelerometer] by android.view.OrientationEventListener.disable():108
04-06 18:08:35.531 15990-15990/com.example.lenny.testapp D/ViewAO: isWindowSplit called.. by aspectj
04-06 18:08:35.692 15990-16495/com.example.lenny.testapp E/Surface: getSlotFromBufferLocked: unknown buffer: 0x9749c1b0
04-06 18:08:35.702 15990-15990/com.example.lenny.testapp V/ViewRootImpl: Contents drawing finished : Toast
Which library version are you using? E.g. 3.2.0.
com.journeyapps:zxing-android-embedded:3.5.0
Which phone/tablet are you using, and which Android version does it run? (e.g. Samsung Galaxy S5,
Android 5.0)
LG G3/ Android M
Does the same happen on other devices or an emulator?
Didn't test.
Can you reproduce the issue in the sample project included with the library? If not, can you
provide your own sample project or sample code that produces this error?
I am using the sample code as pn the github page . I may try a fresh app.
 public void onClick(View v) {
                new IntentIntegrator(MainActivity.this).initiateScan();
            }

In the case of an error do you have a stack trace or adb logs?
See above

Barcodes work fine with that app.

I've also been having this problem both on an LG G2 and Motorola G3. Sometimes the app works fine and sometimes it just sits there forever trying to scan barcodes whilst scanning in continuous mode.
The ZXing barcode scanner works fine.

I did some more testing and the scanning is very unpredictable. I've also tried the dm77 library and in that case it just freezes (you can set a breakpoint in the the result, but otherwise unusable).
What works for me is:
1 -Google Vision, works perfectly in any direction, scans in milliseconds. Con is a large library is needed and if you are low on space it may not install. They also had some bad issues in the past, but the library seems stable.
2 -A pure port of ZXing - I believe this brings the intent into the app so they don't need to download barcode.
an example is:
https://github.com/tarun0/ZXing-Standalone-library
compile 'com.tarun0.zxing-standalone:zxing-standalone:1.0.0'
You can use that as is or follow directions to build yourself. You can also customize the scan activity to your liking.

Interesting, I wasn't aware of those alternatives.
Earlier I tried downloading and compiling this project myself and running the sample app it comes with. Everything works fine in continuous mode there but not in my app using the same library version. There is a chance I broke my app of course, I'm still investigating :).

I found some issues related to portrait mode with these libraries. Not 100% sure but that could be it. My client is in love with Google Vision though after trying both. It is pretty amazing, he claims better and faster than some 800$ data display scanners.

Closing old issues - please open a new issue if you still run into this.


Remove support for Visual Studio 2010

From https://github.com/Robot/robot/issues/55

This issue doesn't really apply to this project.


Correct return docstrings

[x] Closes #1234
[x] I am familiar with the contributing guidelines
[ ] Tests added
[ ] Updates entries to docs/sphinx/source/api.rst for API changes.
[ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Pull request is nearly complete and ready for detailed review.
[x] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

Column names were added as described in the issue.

Thanks @rockstaedt .  I don't think the other checklist items require any action.

Okay cool 👍🏼 I wasn't sure since it was my first pull request. Should I delete them then? @cwhanse

You can delete them, or mark them with strikethrough by putting ~~ at the beginning and end.


not possible to remove standard middleware when using Server::with_state()

In my case, I use Server::with_state(), which means I get the standard LogMiddleware.
However, I have a custom logging middleware to add more context for request logging (method, path, etc as structured arguments instead of a formatted string).
So I get doubled up log entries.
It feels like deciding to have state (DB pool in my case) and getting default middleware should be separate decisions, like with_logging(), with_cookies()?

Hi @leonbreedt, I've submitted a PR for this here https://github.com/http-rs/tide/pull/468, but like your proposition for with_logging() and with_cookies() better.
IMHO it would be good to have them completely out of the server creation and use them as a builder Server::with_state(...).with_logger().with_cookies(), or maybe even:
    let app = tide::new()
	.with_state(...)
	.with_logging()
	.with_cookies()

Hi @leonbreedt, I've submitted a PR for another issue regarding the default logging / cookies in nested servers here https://github.com/http-rs/tide/pull/468, but like your proposition for with_logging() and with_cookies() better :)
IMHO it would be good to have them completely out of the server creation and use them as a builder Server::with_state(...).with_logger().with_cookies(), or maybe even:
    let app = tide::new()
	.with_state(...)
	.with_logging()
	.with_cookies()

which would solve both of our problems :)


PostgreSQL extension bicep fails if run multiple times

Bicep version
v0.8.9
Describe the bug
We are trying to deploy the below bicep for provisioning a new PostgreSQL and add an extension. And this is executed using Azure DevOps. The code will run perfectly fine, when executed for the first time. But If executed more than once, the bicep will fail since the PostgreSQL configuration is already set.
resource postgresSQL 'Microsoft.DBforPostgreSQL/flexibleServers@2021-06-01' = {
  name: serverName
  location: location
  sku: {
    name: dbInstanceType
    tier: serverEdition
  }
  tags: {
    environmentType: environmentType
    environmentPrefix: environmentPrefix
    role: 'Postgres SQL accessed by Harp and Lute'
  }
  properties: {
    version: version
    administratorLogin: administratorLogin
    administratorLoginPassword: administratorLoginPassword
    highAvailability: {
      mode: haMode
    }
    storage: {
      storageSizeGB: skuSizeGB
    }
    backup: {
      backupRetentionDays: 7
      geoRedundantBackup: 'Disabled'
    }
    availabilityZone: availabilityZone
  }
}

resource postgresExtension 'Microsoft.DBforPostgreSQL/flexibleServers/configurations@2022-01-20-preview' = {
  name: 'azure.extensions'
  parent: postgresSQL
  properties: {
    value: 'UUID-OSSP'
    source: 'user-override'
  }
}

Error
{
"status": "Failed",
"error": {
"code": "InternalServerError",
"message": "An unexpected error occured while processing the request. Tracking ID: 'aa979cfd-dc1b-495e-94f3-a24a4cb4d407'"
}
}
To Reproduce
Execute the code more than once

For any InternalServerError (or idempotency issue where re-deployment fails), please open an Azure Support Ticket. I will also pass this on to the DBforPostgreSQL team.


Adaptative menu size improvement with adaptative spotlight radius

Adaptative menu size improvement with adaptative spotlight radius support

Spotlight radius will now be equal to the node rendered size  if no min|maxSpotlightRadius is specified.

Could you list out the improvements (new features, etc.) in the PR?

Description updated.

The previous PR seems to have an issue.  The menu contents are no longer properly placed.  They're off centre.  This doesn't seem to be fixed in this PR.

This PR creates another issue.  The menu size randomly changes:

My bad, sorry I had a typo and fixed it now.
The main goal of the PR is to have an adaptative spotlight radius based on the node rendered size as the nodes size may vary during time in my application so a static radius' didn't fit my needs.
I added an option to enable the adaptative spotlight radius for the node: adaptativeNodeSpotlightRadius.
Changelog:

Fix type for min|maxSpotlightRadius calculation (
Added an options to enable/disable the adaptative spotlight radius for the node (adaptativeNodeSpotlightRadius)
Added comments for better comprehension

Let me know if you still see errors.

Great.  It looks like the default demo is working fine.  Since your PRs have added a set of new features that aren't showcased by the existing demo, would you create a new demo that shows off these new features?

[ ] Create a demo-adaptive.html file.  Copy the existing demo and adjust the extension options and the stylesheet to show off how the new features are useful.  It could include nodes of different sizes or changing sizes.
[ ] Create a symlink to the new demo file under the pages directory so that the new demo gets deployed to gh-pages on release.

I’ll plan to review this tomorrow.  If there are no issues, I’ll just push a release.

On Oct 3, 2020, at 6:38 AM, Tristan Idoux<EMAIL_ADDRESS>wrote:
My bad, sorry I had a typo and fixed it now.
The main goal of the PR is to have an adaptative spotlight radius based on the node rendered size as the nodes size may vary during time in my application so a static radius' didn't fit my needs.
I added an option to enable the adaptative spotlight radius for the node: adaptativeNodeSpotlightRadius.
Changelog:
Fix type for min|maxSpotlightRadius calculation (
Added an options to enable/disable the adaptative spotlight radius for the node (adaptativeNodeSpotlightRadius)
Added comments for better comprehension
Let me know if you still see errors.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/cytoscape/cytoscape.js-cxtmenu/pull/106#issuecomment-703083203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHRO46SC5GZPW7NSBGPTW3SI35J3ANCNFSM4RYKC2GQ.

Great. It looks like the default demo is working fine. Since your PRs have added a set of new features that aren't showcased by the existing demo, would you create a new demo that shows off these new features?

[ ]  Create a demo-adaptive.html file.  Copy the existing demo and adjust the extension options and the stylesheet to show off how the new features are useful.  It could include nodes of different sizes or changing sizes.
[ ]  Create a symlink to the new demo file under the pages directory so that the new demo gets deployed to gh-pages on release.

@tristanidoux, have you had a chance to put together a small demo of your new features?

@maxkfranz Sorry, it's a crazy week at work. I will try to create a small demo this week-end.

@tristanidoux, great.  I'll set aside some time on Monday to release.  Thanks

@maxkfranz It should be good. I only created nodes of different sizes with adaptativeSpotlightRadius enabled or not to show the difference.
Let met know if it's enough or not.

It looks great.  A link from the readme would help people to find the live demo.
I'm noticing an issue with small nodes, but otherwise things look fine.  The arrow gets weird for small nodes:

Will try to look into the arrow and add a link in README as soon as possible.

OK, if the issue for the small spotlight looks too time consuming, then maybe we could just set a hard limit on the minimum size of the spotlight.  I think that would be good enough for now, and then we can just publish a release based on these improvements.

Fix indicator arrow for node size < indicatorSize defined in options
Linked adaptative spotlight radius features in README

Looks good.  Released as 3.3.0

Thanks again for the PR, @tristanidoux

@maxkfranz No problem, thanks for this extension 😄


What is alignment datasets？

Thank you for your contribution.
I have a question: what is alignment datasets？

Thank you for your contribution. I have a question: what is alignment datasets？

Sorry for causing confusion. At the early stage of this project, we aimed at collecting chatbot datasets which are typically used for align LLM to human preferance. That's how the name 'alignment dataset' comes. But as the scope of our project expanding, it  becomes not so appopriate.


Addresses most of my review comments

I am going to merge this, as the comments asking for changes no longer apply to this PR


Android notification forwards to App Settings instead of App

Describe the bug
In Android, when I click on the background-tracking notification, I'm forwarded to the app-settings, and not to the app itself (as in iOs)
To Reproduce
Steps to reproduce the behavior:

On Android, set up notifications for background tracking
Launch your app and whatever processes that uses the plugin.
Go in background mode
Click on the notification

Expected behavior
I go back to the app (not to the settings)
Smartphone (please complete the following information):

Device: Pixel 6
OS: Android 14

And thanks much for this plugin, it's great :-)

That happens when the notification icon is not correctly configured. Ensure you have configued the notification icon via Android Studio, details are in the README.

On 10 Jan 2024, at 9:39 pm, Jean Hautier @.***> wrote:
Describe the bug
In Android, when I click on the background-tracking notification, I'm forwarded to the app-settings, and not to the app itself (as in iOs)
To Reproduce
Steps to reproduce the behavior:
On Android, set up notifications for background tracking
Launch your app and whatever processes that uses the plugin.
Go in background mode
Click on the notification
Expected behavior
I go back to the app (not to the settings)
Smartphone (please complete the following information):
Device: Pixel 6
OS: Android 14
And thanks much for this plugin, it's great :-)
—
Reply to this email directly, view it on GitHub https://github.com/capacitor-community/background-geolocation/issues/110, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACLZQFJUM2AMKFQO7LODKDYNZVWBAVCNFSM6AAAAABBUR2MK6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3TIMBYGA4DIOA.
You are receiving this because you are subscribed to this thread.

I was referring to the comment preceding <string name="capacitor_background_geolocation_notification_icon">.


Display python error message when kernel dies

Fixes #7318

Codecov Report

Merging #7646 (06b2fa2) into main (5ea9ffc) will decrease coverage by 0%.
The diff coverage is 16%.

@@          Coverage Diff          @@
##            main   #7646   +/-   ##
=====================================
- Coverage     68%     68%   -1%
=====================================
  Files        363     363
  Lines      22546   22535   -11
  Branches    3430    3431    +1
=====================================
- Hits       15490   15478   -12
- Misses      5724    5725    +1
  Partials    1332    1332

Impacted Files
Coverage Δ

...tascience/jupyter/kernels/kernelCommandListener.ts
56% <0%> (-1%)
:arrow_down:

src/client/datascience/kernel-launcher/types.ts
59% <0%> (-5%)
:arrow_down:

...ent/datascience/jupyter/kernels/kernelExecution.ts
69% <100%> (+<1%)
:arrow_up:

...ent/datascience/jupyter/pythonVariableRequester.ts
47% <0%> (-6%)
:arrow_down:

.../kernel-launcher/localKnownPathKernelSpecFinder.ts
89% <0%> (-3%)
:arrow_down:

src/client/datascience/jupyter/kernels/kernel.ts
74% <0%> (-1%)
:arrow_down:

...client/datascience/commands/activeEditorContext.ts
91% <0%> (+<1%)
:arrow_up:

src/client/datascience/jupyter/kernels/helpers.ts
72% <0%> (+1%)
:arrow_up:

...lient/datascience/variablesView/notebookWatcher.ts
89% <0%> (+1%)
:arrow_up:

...client/datascience/kernel-launcher/kernelDaemon.ts
57% <0%> (+1%)
:arrow_up:

... and 1 more


User codes not being set

Home Assistant release with the issue:
0.75.3
Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian
Component/platform:
https://www.home-assistant.io/components/lock/
Description of problem:
Using the UI or developer tools I cannot set a user code on my smart lock (Yale Keyless Connected Smart Lock).
Upon entering a new code in hex format for example: \x31\x32\x33\x34\x35\x36\x37\x38\x00\x00 and pressing 'set usercode' the UI refreshes and the input returns the previous code stored in that slot. Pressing 'delete usercode' also produces the same outcome.
Traceback (if applicable):
2018-08-09 16:17:45.458 Info, Node055, Value::Set - COMMAND_CLASS_USER_CODE - Code 10: - 10 - 1 - 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x00 0x00
2018-08-09 16:17:45.458 Detail, Node055, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_USER_CODE
2018-08-09 16:17:45.458 Detail, Node055, Queuing (Send) UserCodeCmd_Set (Node=55): 0x01, 0x15, 0x00, 0x13, 0x37, 0x0e, 0x63, 0x01, 0x0a, 0x01, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x00, 0x00, 0x25, 0x6a, 0xee
2018-08-09 16:17:45.458 Detail, Node055, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_USER_CODE
2018-08-09 16:17:45.458 Detail, Node055, Queuing (Send) UserCodeCmd_Get (Node=55): 0x01, 0x0a, 0x00, 0x13, 0x37, 0x03, 0x63, 0x02, 0x0a, 0x25, 0x6b, 0xf7
2018-08-09 16:17:45.458 Detail,
2018-08-09 16:17:45.459 Info, Node055, Processing (Send) Nonce Request message (Callback ID=0x6a, Expected Reply=0x13)
2018-08-09 16:17:45.459 Info, Node055, Sending (Send) message (Callback ID=0x6a, Expected Reply=0x13) - Nonce_Get(UserCodeCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x37, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-08-09 16:17:45.464 Detail, Node055,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-08-09 16:17:45.465 Detail, Node055,   ZW_SEND_DATA delivered to Z-Wave stack
2018-08-09 16:17:46.736 Detail, Node055,   Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x80, 0x69
2018-08-09 16:17:46.737 Detail, Node055,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-08-09 16:17:46.737 Info, Node055, Request RTT 1277 Average Request RTT 741
2018-08-09 16:17:46.748 Detail, Node055,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x37, 0x0a, 0x98, 0x80, 0xb6, 0x3c, 0xf9, 0x12, 0x52, 0x9e, 0x90, 0x0d, 0xfe
2018-08-09 16:17:46.748 Info, Node055, Received SecurityCmd_NonceReport from node 55
2018-08-09 16:17:46.748 Info, Node055, Sending (Send) message (Callback ID=0x6c, Expected Reply=0x13) - UserCodeCmd_Set (Node=55): 0x01, 0x15, 0x00, 0x13, 0x37, 0x0e, 0x63, 0x01, 0x0a, 0x01, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x00, 0x00, 0x25, 0x6c, 0xe8
2018-08-09 16:17:46.758 Detail, Node055,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-08-09 16:17:46.758 Detail, Node055,   ZW_SEND_DATA delivered to Z-Wave stack
2018-08-09 16:17:46.780 Detail, Node055,   Received: 0x01, 0x07, 0x00, 0x13, 0x6c, 0x00, 0x00, 0x02, 0x85
2018-08-09 16:17:46.780 Detail, Node055,   ZW_SEND_DATA Request with callback ID 0x6c received (expected 0x6c)
2018-08-09 16:17:46.780 Info, Node055, Request RTT 1321 Average Request RTT 1031
2018-08-09 16:17:46.780 Detail,   Expected callbackId was received
2018-08-09 16:17:46.780 Detail,   Expected reply was received
2018-08-09 16:17:46.781 Detail,   Message transaction complete
2018-08-09 16:17:46.781 Detail,
2018-08-09 16:17:46.781 Detail, Node055, Removing current message
2018-08-09 16:17:46.781 Detail,
2018-08-09 16:17:46.781 Info, Node055, Processing (Send) Nonce Request message (Callback ID=0x6b, Expected Reply=0x04)
2018-08-09 16:17:46.781 Info, Node055, Sending (Send) message (Callback ID=0x6b, Expected Reply=0x04) - Nonce_Get(UserCodeCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x37, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-08-09 16:17:46.787 Detail, Node055,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-08-09 16:17:46.787 Detail, Node055,   ZW_SEND_DATA delivered to Z-Wave stack
2018-08-09 16:17:46.802 Detail, Node055,   Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x01, 0xe8
2018-08-09 16:17:46.803 Detail, Node055,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-08-09 16:17:46.803 Info, Node055, Request RTT 21 Average Request RTT 526
2018-08-09 16:17:46.814 Detail, Node055,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x37, 0x0a, 0x98, 0x80, 0x41, 0x41, 0xec, 0x62, 0xf4, 0xac, 0xf9, 0xcd, 0x2c
2018-08-09 16:17:46.814 Info, Node055, Received SecurityCmd_NonceReport from node 55
2018-08-09 16:17:46.814 Info, Node055, Sending (Send) message (Callback ID=0x6d, Expected Reply=0x04) - UserCodeCmd_Get (Node=55): 0x01, 0x0a, 0x00, 0x13, 0x37, 0x03, 0x63, 0x02, 0x0a, 0x25, 0x6d, 0xf1
2018-08-09 16:17:46.823 Detail, Node055,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-08-09 16:17:46.823 Detail, Node055,   ZW_SEND_DATA delivered to Z-Wave stack
2018-08-09 16:17:46.843 Detail, Node055,   Received: 0x01, 0x07, 0x00, 0x13, 0x6d, 0x00, 0x00, 0x02, 0x84
2018-08-09 16:17:46.844 Detail, Node055,   ZW_SEND_DATA Request with callback ID 0x6d received (expected 0x6d)
2018-08-09 16:17:46.844 Info, Node055, Request RTT 62 Average Request RTT 294
2018-08-09 16:17:46.844 Detail,   Expected callbackId was received
2018-08-09 16:17:46.881 Detail, Node055,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x37, 0x02, 0x98, 0x40, 0x1e
2018-08-09 16:17:46.881 Info, Node055, Received SecurityCmd_NonceGet from node 55
2018-08-09 16:17:46.881 Info, NONCES: 0xa1, 0x43, 0xbf, 0x09, 0xb8, 0x59, 0xdf, 0x48
2018-08-09 16:17:46.882 Info, NONCES: 0x8d, 0xac, 0xf5, 0x9f, 0xa3, 0x6e, 0x02, 0xfe
2018-08-09 16:17:46.882 Info, NONCES: 0x62, 0x01, 0xb2, 0xe3, 0x02, 0xe2, 0x2d, 0xa3
2018-08-09 16:17:46.882 Info, NONCES: 0x63, 0xf4, 0x2c, 0x30, 0x3f, 0x5c, 0xea, 0xa0
2018-08-09 16:17:46.882 Info, NONCES: 0xc9, 0x2d, 0x53, 0x55, 0xa3, 0x2e, 0x3e, 0x06
2018-08-09 16:17:46.882 Info, NONCES: 0xc7, 0x9f, 0x12, 0x76, 0x68, 0x75, 0x9a, 0xd5
2018-08-09 16:17:46.882 Info, NONCES: 0x90, 0x33, 0xcd, 0xac, 0x12, 0xf6, 0x79, 0x62
2018-08-09 16:17:46.882 Info, NONCES: 0xed, 0x16, 0xd2, 0xf7, 0x82, 0x01, 0x30, 0x49
2018-08-09 16:17:46.882 Info, Node055, Sending (Send) message (Callback ID=0x01, Expected Reply=0x04) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x37, 0x0a, 0x98, 0x80, 0xc9, 0x2d, 0x53, 0x55, 0xa3, 0x2e, 0x3e, 0x06, 0x05, 0x01, 0x8b:
2018-08-09 16:17:46.889 Detail, Node055,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-08-09 16:17:46.890 Detail, Node055,   ZW_SEND_DATA delivered to Z-Wave stack
2018-08-09 16:17:46.907 Detail, Node055,   Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x02, 0xe8
2018-08-09 16:17:46.907 Detail, Node055,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2018-08-09 16:17:46.907 Info, Node055, Request RTT 126 Average Request RTT 210
2018-08-09 16:17:46.930 Detail, Node055,   Received: 0x01, 0x23, 0x00, 0x04, 0x00, 0x37, 0x1d, 0x98, 0x81, 0x08, 0x2e, 0x19, 0x77, 0x4c, 0xe3, 0x69, 0x9a, 0xc4, 0x6d, 0x2c, 0xd2, 0x45, 0x53, 0x73, 0xf1, 0xef, 0x65, 0xc9, 0xe2, 0x6a, 0x75, 0x3f, 0x2e, 0xeb, 0xe7, 0xa8, 0x37
2018-08-09 16:17:46.930 Info, Raw: 0x98, 0x81, 0x08, 0x2e, 0x19, 0x77, 0x4c, 0xe3, 0x69, 0x9a, 0xc4, 0x6d, 0x2c, 0xd2, 0x45, 0x53, 0x73, 0xf1, 0xef, 0x65, 0xc9, 0xe2, 0x6a, 0x75, 0x3f, 0x2e, 0xeb, 0xe7, 0xa8, 0x37
2018-08-09 16:17:46.930 Detail, Node055, Decrypted Packet: 0x00, 0x63, 0x03, 0x0a, 0x01, 0x34, 0x32, 0x30, 0x38, 0x39
2018-08-09 16:17:46.930 Detail,
2018-08-09 16:17:46.930 Info, Node055, Response RTT 149 Average Response RTT 184
2018-08-09 16:17:46.931 Info, Node055, User Code Packet is 5
2018-08-09 16:17:46.931 Detail, Node055, Refreshed Value: old value=5f313f08, new value=61c91780, type=raw
2018-08-09 16:17:46.931 Detail, Node055, Changes to this value are not verified
2018-08-09 16:17:46.931 Info, Node055, Received User Code Report from node 55 for User Code 10 (Occupied)
2018-08-09 16:17:46.931 Detail, Node055,   Expected reply and command class was received
2018-08-09 16:17:46.931 Detail, Node055,   Message transaction complete
2018-08-09 16:17:46.931 Detail,
2018-08-09 16:17:46.931 Detail, Node055, Removing current message
2018-08-09 16:17:46.931 Detail, Node055, Notification: ValueChanged

You can't use null byttes in the usercode. Try without that. Per now it is only possible to clear usercodes on som type of locks. That is due to the ozw lib does not handle this correctly yet.

@turbokongen I don't think that's the issue as trying \x35\x37\x39\x37\x39\x35\x33\x35\x35\x38 still produces the same result.

What is your code length set to?  10 digits?  If you are trying to set a 4 digit code you should try
\x35\x37\x39\x37  = 5697 ascii
That has worked for me with schlage, but yale should be the same.


K8SPSMDB-764 psmdb release 1.13.0 fix operator image hash

Test name
Status

api-tests
passed


[HOLD for payment 2023-05-05] [$1000] Workspace list sorting order breaks if the name starts with lower case alphabet

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app
Open settings
Open workspaces
Add new workspace with first letter as small

Expected Result:
App should either auto capitalize first letter or should sort alphabetically considering both workspaces with capital first letter and workspaces with small first letter
Actual Result:
Sorting breaks if workspace list has both names with capital first letter and small first letter
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.2.94-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://user-images.githubusercontent.com/43996225/229863495-22a1bb11-ffc8-431f-bd8b-cb9a98d4965c.mp4
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680598452709389
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01230caf1a05f03e9c
Upwork Job ID:<PHONE_NUMBER>918076928
Last Price Increase: 2023-04-25

Triggered auto assignment to @JmillsExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@JmillsExpensify Eep! 4 days overdue now. Issues have feelings too...

@JmillsExpensify Eep! 4 days overdue now. Issues have feelings too...

@JmillsExpensify Eep! 4 days overdue now. Issues have feelings too...

Based on the discussion in Slack, I'm going to add the external label and get this issue moving again. Many apologies for the delay!

Job added to Upwork: https://www.upwork.com/jobs/~01230caf1a05f03e9c

Current assignee @JmillsExpensify is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)

Proposal
Please re-state the problem that we are trying to solve in this issue.
Workspace list sorting order breaks if the name starts with lower case alphabet
What is the root cause of that problem?
We are sorting workspace by the original name
https://github.com/Expensify/App/blob/56c27de50093a85c1c25ad5ac359b043c67ab96b/src/pages/workspace/WorkspacesListPage.js#L134
What changes do you think we should make in order to solve the problem?
We should change the workspace's name to lowercase before sorting like this
 .sortBy(policy => policy.title.toLowerCase())

Optional: For consistency, we also should update the same in here: https://github.com/Expensify/App/blob/56c27de50093a85c1c25ad5ac359b043c67ab96b/src/pages/settings/InitialSettingsPage.js#L154
What alternative solutions did you explore? (Optional)
NA
Result

Proposal
Please re-state the problem that we are trying to solve in this issue.
Workspace list sorting order breaks if the name starts with lower case alphabet chars.
What is the root cause of that problem?
Workspace render via this code block
https://github.com/Expensify/App/blob/aa1e2edee2625363bc445811a06ce47dd556061d/src/pages/workspace/WorkspacesListPage.js#L191-L193
We can see at line 192 there is not any sorting done on workspace list. This is the root cause of the problem.
What changes do you think we should make in order to solve the problem?
We have to sort workspace by title as shown below.
<ScrollView style={styles.flex1}>
   {_.map(_.sortBy(workspaces, value => value.title.toLowerCase()), (item, index) => this.getMenuItem(item, index))}
</ScrollView>

It will solve problem i.e. Sort workspace by title no matter capital or small letter in title. As shown in results.
What alternative solutions did you explore? (Optional)
None.

Results
https://user-images.githubusercontent.com/7823358/229872209-8515f7cf-e50d-4490-b127-e3e4fa420822.mov

Triggered auto assignment to @madmax330 (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Workspaces list sorting order incorrectly which places the workspaces with a small first letter at the bottom
What is the root cause of that problem?
Currently, the sort which is applied to the workspaces list is case-sensitive which causes this issue.
https://github.com/Expensify/App/blob/313c5757160561ce7f47254097e08d9a9c208dc9/src/pages/workspace/WorkspacesListPage.js#L134
What changes do you think we should make in order to solve the problem?
We should apply lowerCase(policy.title.toLowerCase()) to workspace title to make it case-insensitive while sorting the list.
https://github.com/Expensify/App/blob/313c5757160561ce7f47254097e08d9a9c208dc9/src/pages/workspace/WorkspacesListPage.js#L134

@eVoloshchak have you had a chance to look at the proposals? I think @dukenv0307's proposal is good, thoughts?

@dukenv0307's proposal looks good to me too
I can see a potential problem, we can't guarantee the same order regardless of the order of elements in the input array, if we have two workspaces with the same name but in a different case: ['Workspace1', 'workspace1'] and ['workspace1', 'Workspace1'] will be displayed differently.
@madmax330, is that important?
If not, I think we can proceed with @dukenv0307's soluton

@madmax330, what are your thoughts on this?

@eVoloshchak  I don't think we should worry about workspaces with the same name since 1. it's an edge case and 2. there's an easy fix which is to change the name of the workspace.
So we're good to move forward with @dukenv0307's proposal

@madmax330 Could you assign me to this issue officially so I can raise a PR to fix

@JmillsExpensify @madmax330 @eVoloshchak this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

📣 @dukenv0307 You have been assigned to this job by @madmax330!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

@eVoloshchak @madmax330 The PR is ready for review

Reviewing label has been removed, please complete the "BugZero Checklist".

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.3.7-3 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/18008

If no regressions arise, payment will be issued on 2023-05-05. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@eVoloshchak] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@eVoloshchak] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@eVoloshchak] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@eVoloshchak] Determine if we should create a regression test for this bug.
[ ] [@eVoloshchak] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ] [@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Alright, with the PR on production, let's summarize where we're at for payments. This PR is eligible for a 50% bonus, so that means we have the following.

Issue reporter: @dhanashree-sawant $250
Contributor: @dukenv0307 $1,500
Contributor+: @eVoloshchak $1,500

The Upwork link is here: https://www.upwork.com/jobs/~01230caf1a05f03e9c. @dukenv0307 would you mind applying or sharing your Upwork profile?

Then @eVoloshchak let's get the BZ checklist kicked off ahead of the regression period passing. Thank you all!

@JmillsExpensify I've applied, thanks!

The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/11784

The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/11784#issuecomment-1531908446

A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: I dpn't think additionlal steps are needed, it's a standart practise we're using throughout the app, it was just missed during the initial implementation of WorkspacesListPage

Determine if we should create a regression test for this bug.

Is it easy to test for this bug?

Yes

Is the bug related to an important user flow? (For example, adding a bank account)

No

Is it an impactful bug?

No
I think the regression test isn't necessary in this case, the bug has a very low impact

Thanks for all those. I agree with that and that a regression test doesn't seem necessary.

Then all contributors have been hired at this point, so we're down to waiting for the regression period to end in a couple of days. I'll pay out the relevant bonuses when issuing final payment. Stay tuned until then!

Still waiting on payment

All contributors paid out and no regression test required. Closing!


OpenSearch Creation in an existing VPC is failing

What happened?

How can we reproduce it?
I am trying to create an OpenSearch Domain in an existing VPC. I am using the one from the examples:
apiVersion: opensearchservice.aws.crossplane.io/v1alpha1
kind: Domain
metadata:
  name: sample2-domain
spec:
  forProvider:
    name: sample2-domain
    region: us-east-1
    ebsOptions:
      ebsEnabled: true
      volumeType: gp2
      volumeSize: 10
    clusterConfig:
      zoneAwarenessEnabled: true
      zoneAwarenessConfig:
        availabilityZoneCount: 2
      instanceCount: 2
    encryptionAtRestOptions:
      enabled: true
      kmsKeyIdRef:
        name: dev-key
    vpcOptions:
      securityGroupIdRefs:
        - name: sample-cluster-sg-2
      subnetIdRefs:
        - name: sample-subnet1
        - name: sample-subnet2
  writeConnectionSecretToRef:
    name: sample2-domain
    namespace: crossplane-system
  providerConfigRef:
    name: example

with my vpc subnet ids. Whenever I apply this, I get the following error:
cannot create Domain in AWS: ValidationException: Subnet must be specified for VPC domain
When I try to create a Domain without the VPC options, it creates the Domain on AWS.
Is there any other way to specify vpc id?
What environment did it happen in?
I am using Crossplane installed in a local Kubes cluster, and applying the Crossplane YAML using ArgoCD.
Crossplane version: crossplane/crossplane:v1.11.2
Kubernetes version:
{
  "clientVersion": {
    "major": "1",
    "minor": "25",
    "gitVersion": "v1.25.4",
    "gitCommit": "872a965c6c6526caa949f0c6ac028ef7aff3fb78",
    "gitTreeState": "clean",
    "buildDate": "2022-11-09T13:28:30Z",
    "goVersion": "go1.19.3",
    "compiler": "gc",
    "platform": "darwin/arm64"
  },
  "kustomizeVersion": "v4.5.7",
  "serverVersion": {
    "major": "1",
    "minor": "25",
    "gitVersion": "v1.25.2",
    "gitCommit": "5835544ca568b757a8ecae5c153f317e5736700e",
    "gitTreeState": "clean",
    "buildDate": "2022-09-21T14:27:13Z",
    "goVersion": "go1.19.1",
    "compiler": "gc",
    "platform": "linux/arm64"
  }
}

Is there a way to declare an existing VPC too?


ADDED new content on PRINT S.A.F. during Printing prompt

V2 Sample Student Activity Form.docx
V2 Sample Student Activity Form.pdf

the entries  of the materials

Note that you must follow the   " (   ) ___  Sound System "  LIke this one below
this is the original copy of reservation slip


Use equality operator instead of identity operator

Hot fix:
Change log:

Use equality operator in this case

No longer valid with updates regarding https://github.com/sennetconsortium/ingest-api/issues/300


Doesn't work in IE8 after release v2.4.1

All my tests started to fail after new release in IE8 with the following error:
Object doesn't support this property or method
  at /home/travis/build/driveback/digital-data-manager/node_modules/mocha/mocha.js:11671

Thats because at ~3 spots Object.keys was used directly rather than checking if the function is present or not.

Ugh.

Just load es5-shim until we fix it (very soon)

I have es5-shim, but it still doesn't work :)

do you have it for object.keys and [].forEach?

alright, testing this fix atm.

@boneskull why not use the polyfill for 2 methods so that it easy to remove later on when we end IE8 support?

@gyandeeps rather not add another dependency or monkey with other stuff right now.

@yurevichcv can you run your tests with this mocha.js file and tell me if you have better results in IE8?

@gyandeeps anyway, mocha contains a bunch of hand-rolled shims which need replacing.  it's a somewhat bigger job than you'd expect

I see. thanks

downloading an IE8 vm to try it myself

@boneskull Your changes work:
Before

After

v2.4.3 published


Failed to deserialize JSON

Hello,
On opening melodie after initial setup on Ubuntu 21.04, I've gotten this error:
Failed to deserialize value "[object Object]" for col tags: Unexpected token o in JSON at position 1.
Let me know if there are any log files I can grab. I'm not sure what file this error is referencing.

Hello, and thanks for the report!
Just to clarify: has it crashed on the first run, or after you changed some settings?
I would need you to share:

the version you're using
the log file content. You'll find it either:

~/snap/melodie/melodie/logs (if you run the snap version)
~/.config/melodie/melodie/logs (if you run the AppImage version)

There should be no sensitive data in there, but please check their content before posting them here.

Thanks for the precision, I've fixed my answers accordingly (for further readers).
I've looked at the db file you've shared, and all the tracks have correct tags. I'm a bit puzzled to be honest.
Are you facing the same issue after reseting Mélodie?

Yes indeed. You'll find some tips in the readme.
Would you mind trying the AppImage? You can download it here or from the releases page

Hi, Sorry to drop off the map for a while. I'm getting the same issue with the AppImage.


Add Book Detail component

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Generate blank document?

Is there an easy way to extract a minimal conforming "blank" document from Simple Schema?  If not, would anyone be interested in having such a capability?
My sense is that 90% of the use cases involve objects with only simple fields - strings, integers, etc - that have natural default values ("" for String, minValue for Number, etc).  Having this capability in the schema would take a lot of boilerplate out of writing "insertBlankDocument" functions.  Would like to gage interest before investing a lot of time making it happen.

Closing since this should be implemented as a separate package, but I've heard others request this so please post a link here if you do it.


Covariance matrix returned by ODR needs to be scaled by the residual variance

Originally reported on SO here.
import numpy as np
from scipy.odr import ODR, Model, RealData

def f(B, x):
    return B[0] + B[1]*x + B[2]*x**3

n = 100
sx = 0.3
sy = 2.0
B_real = [-2.3, 7.0, -4.0]
gen = np.random.RandomState(0)
x = np.linspace(-5, 5, n)
y = f(B_real, x)
x +=  gen.randn(n) * sx
y += gen.randn(n) * sy

model = Model(f)
data = RealData(x, y, sx=sx, sy=sy)
odr = ODR(data, model, beta0=[1., 0., 0.])
odr.set_job(fit_type=0)
output = odr.run()

output.pprint()
# Beta: [-2.56437069  6.97055557 -4.11430261]
# Beta Std Error: [ 0.48929313  0.66751299  0.14785663]
# Beta Covariance: [[ 0.2321291  -0.02974486  0.00394905]
#  [-0.02974486  0.43202691 -0.05337819]
#  [ 0.00394905 -0.05337819  0.02119693]]
# Residual Variance: 1.03135611652
# Inverse Condition #: 0.0768799779673
# Reason(s) for Halting:
#   Sum of squares convergence

print("           sd_beta: {}".format(output.sd_beta))
print("sqrt(diag(sd_cov)): {}".format(np.sqrt(np.diag(output.cov_beta))))
#            sd_beta: [ 0.48929313  0.66751299  0.14785663]
# sqrt(diag(sd_cov)): [ 0.48179778  0.65728754  0.14559166]

The discrepancy arises because __odrpack.c extracts cov_beta directly from the FORTRAN routine's work vector using the   vcv index. However, according to the ODRPACK documentation (p85):

WORK(VCVI) is the first element of a p × p array VCV containing the values of the covariance matrix of the parameters β prior to scaling by the residual variance, where  WORK(VCVI-1+I+(J-1)*(NP)) = VCV(I,J) = ̂σ⁻²V β(I, J) for I = 1,... ,p and J = 1,... ,p.

If we multiply the covariance matrix by the residual variance then we get the expected result:
print("                sd_beta: {}".format(output.sd_beta))
print("sqrt(diag(sd_cov * rv)): {}".format(
      np.sqrt(np.diag(output.cov_beta * output.res_var))))
#                 sd_beta: [ 0.48929313  0.66751299  0.14785663]
# sqrt(diag(sd_cov * rv)): [ 0.48929313  0.66751299  0.14785663]

I came across a related post on SO: https://stackoverflow.com/questions/62460399/comparison-of-curve-fit-and-scipy-odr-absolute-sigma
Trying to understand the results I compared ODR in ftype=2 mode (least squares) with scipy.optimize.curve_fit:
import numpy as np
from scipy.odr import ODR, Model, RealData

def f(B, x):
    return B[0] + B[1]*x + B[2]*x**3

n = 100
sx = 0.3
sy = 2.0
B_real = [-2.3, 7.0, -4.0]
gen = np.random.RandomState(0)
x = np.linspace(-5, 5, n)
y = f(B_real, x)
x +=  gen.randn(n) * sx
y += gen.randn(n) * sy

model = Model(f)
data = RealData(x, y, sx=sx, sy=sy)
odr = ODR(data, model, beta0=[1., 0., 0.])
odr.set_job(fit_type=2)
output = odr.run()

print("odr      : sd_beta: {}".format(output.sd_beta))
print("odr      : sqrt(diag(sd_cov)): {}".format(np.sqrt(np.diag(output.cov_beta))))

def func(x, a, b, c):
    return a + b*x + c*x**3

from scipy.optimize import curve_fit

popt, pcov = curve_fit(func, x, y, sigma=np.tile([sy], len(y)), absolute_sigma=True)
print("curve_fit: sqrt(diag(cov)): {}".format(np.sqrt(np.diag(pcov))))

and the output is
odr      : sd_beta: [3.95086679 3.33293371 0.1969002 ]
odr      : sqrt(diag(sd_cov)): [0.2018686  0.17029546 0.01006057]
curve_fit: sqrt(diag(cov)): [0.20186863 0.17029594 0.01006059]

So the unweighted covariance matrix returned by ODR is (almost) the same as that returned by curve_fit but sd_beta is obviously different.
What is the right way to get the error of the paremeters then?

@kurisutsukato Thank you for your comments.

What is the right way to get the error of the paremeters then?

In my understanding, the odr covariance is not scaled by residual variance, so curve_fit covariance is too.
However, it seems that sd_beta is scaled by residual variance, there is inconsistency.
I think sd_beta should be unscaled or sd_beta should be changed to scaled_sd_beta or something like that.
But both options might break backward compatibility.
So, I added an optional argument for scaled covariance matrix of ODR and I updated sd_beta doc which show it is scaled in #12207
Modifying  your code, we can check this easily.
import numpy as np

from scipy.odr import ODR, Model, RealData

def f(B, x):
    return B[0] + B[1] * x + B[2] * x ** 3

n = 100
sx = 0.3
sy = 2.0
B_real = [-2.3, 7.0, -4.0]
gen = np.random.RandomState(0)
x = np.linspace(-5, 5, n)
y = f(B_real, x)
x += gen.randn(n) * sx
y += gen.randn(n) * sy

model = Model(f)
data = RealData(x, y, sx=sx, sy=sy)
odr = ODR(data, model, beta0=[1., 0., 0.])
odr.set_job(fit_type=2)
output = odr.run()

print("odr      : sd_beta: {}".format(output.sd_beta))
print("odr(unscaled): sqrt(diag(sd_cov)): {}".format(
    np.sqrt(np.diag(output.cov_beta))))
print("odr(scaled): sqrt(diag(sd_cov * res_var)): {}".format(
    np.sqrt(np.diag(output.cov_beta * output.res_var))))

def func(x, a, b, c):
    return a + b * x + c * x ** 3

from scipy.optimize import curve_fit

popt, pcov = curve_fit(func, x, y, sigma=np.tile([sy], len(y)),
                       absolute_sigma=True)
print("curve_fit: sqrt(diag(cov)): {}".format(np.sqrt(np.diag(pcov))))

The output is
odr      : sd_beta: [3.9508668  3.33294797 0.19690089]
odr(unscaled): sqrt(diag(sd_cov)): [0.2018686  0.17029619 0.0100606 ]
odr(scaled): sqrt(diag(sd_cov * res_var)): [3.9508668  3.33294797 0.19690089]
curve_fit: sqrt(diag(cov)): [0.20186863 0.17029594 0.01006059]

@AtsushiSakai Thanks for looking into this.
What I was trying to say is, that I would expect that ODR's sd_beta is the same as sqrt(diag(cov)) returned by curve_fit, which is apparently not the case. But I found out that it depends on the absolute_sigma argument of curve_fit. Setting it to False makes sqrt(diag(cov)) coincide with ODR's sd_beta.
import numpy as np
from scipy.odr import ODR, Model, RealData
def f(B, x):
    return B[0] + B[1]*x + B[2]*x**3

n = 100
sx = 0.3
sy = 2.0
B_real = [-2.3, 7.0, -4.0]
gen = np.random.RandomState(0)
x = np.linspace(-5, 5, n)
y = f(B_real, x)
x += gen.randn(n) * sx
y += gen.randn(n) * sy
# since we are in leastsq mode all error is interpreted as error in y

model = Model(f)
data = Data(x, y)
odr = ODR(data, model, beta0=[1., 1., 1.])
odr.set_job(fit_type=2)
output = odr.run()
print(output.beta)
print("odr      : sd_beta: {}".format(output.sd_beta))
print("odr      : sqrt(diag(sd_cov)): {}".format(np.sqrt(np.diag(output.cov_beta))))

def func(x, a, b, c):
    return a + b*x + c*x**3

from scipy.optimize import curve_fit

popt, pcov = curve_fit(func, x, y, absolute_sigma=False)
print("curve_fit(absolute_sigma=False) sqrt(diag(cov)): {}".format(np.sqrt(np.diag(pcov))))
popt, pcov = curve_fit(func, x, y, absolute_sigma=True)
print("curve_fit(absolute_sigma=True) sqrt(diag(cov)): {}".format(np.sqrt(np.diag(pcov))))

yields
odr      : sd_beta: [3.95086651 3.33293698 0.19689997]
odr      : sqrt(diag(sd_cov)): [0.10093429 0.08514781 0.00503028]
curve_fit(absolute_sigma=False) sqrt(diag(cov)): [3.95086723 3.33294311 0.19690061]
curve_fit(absolute_sigma=True) sqrt(diag(cov)): [0.10093431 0.08514797 0.0050303 ]

Sorry for the noise.

@kurisutsukato Oh. OK. I misunderstood what you mean.

But I found out that it depends on the absolute_sigma argument

That's good.

From what I remember when I looked at measurement error model many years ago. I did not look at the ODR literature, the literature I was reading criticized ODR for this.
ODR treats lhs and rhs in the same way, i.e. all variables have measurement errors. The measurement error is assumed to be known.  (Similar to the curve_fit option of NOT scaling the cov by the residual variance.)
An alternative treatment is to have the "dependent" lhs variable taking the slack. That is, the measurement error of regressors is assumed to be known but not the measurement error of the dependent variable.
In this case, the residual variance includes the measurement error of the dependent random variable plus any left over variance from model approximation or model misspecifiction errors.
However, AFAIU that literature, it said that ODR is NOT doing this. So, multiplying by the residual variance is not in the design of ODR.
This does not mean it could not be added, but I never looked at the scipy ODR code.

The square root of the diagonals of "cov_beta" should be made equal to "sd_beta".  Whether ODR treats LHS and RHS the same way or not, there's no reason for cov_beta and sd_beta to be inconsistent with each other.
If we don't want to make this change because of backward compatibility, the docstring for cov_beta should explicitly say that it isn't multiplied by the residual variance.


Support deduping our NSUserActivity-based indexed Spotlight items

We've recently had requests that would allow partners to index their content with our BUO methods but continue to update the the metadata over time. The current production version of this implementation makes no effort to de-dupe across each BUO item because we previously found it impossible to do. I've experimented a bit this evening and found that weakRelatedUniqueIdentifier actually solves this without breaking our Spotlight implementation. Unfortunately, it appears that Apple only lets you update an item one single time. I tested many different mechanisms to get around this limitation, like setting the modification date and resigningCurrent before calling becomeCurrent. Nothing seems to work. Still, this is better than nothing.
Also, I updated the testbed to share the same keys as the Android one.
@jdee

Result of Integration 1
Duration: 7 minutes and 35 seconds
Result: Perfect build! All 184 tests passed. :+1:
Test Coverage: 60%

Apple only lets you change the information one time?  That seems like a very odd design choice on their part.
👍

I'll pass along the change of keys to Parul -- She'll need to update her testing run book.
Thanks for this. We are going to dig into other Spotlight issue as well this week.


Many to many relationships is failing to instantiate due to duplicate EntityManager.

Caused by:
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'postRepositoryWithBagRelationshipsImpl': Unsatisfied dependency expressed through field 'entityManager'; nested exception is org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type 'javax.persistence.EntityManager' available: more than one 'primary' bean found among candidates: [org.springframework.orm.jpa.SharedEntityManagerCreator#0, org.springframework.orm.jpa.SharedEntityManagerCreator#1]

Looks spring-native specific.
We are relying on spring-boot to create EntityManagers.
Reproducible at https://github.com/jhipster/generator-jhipster-native/tree/bag_relationships

I'm confused. If I recreate all my spring-native-examples with the main branch, and manually QA them, the only one that fails is postgres-webflux. It fails with this error:
org.springframework.core.codec.CodecException: Type definition error: [collection type; class java.util.HashSet,
contains [simple type, class java.lang.Object]]; nested exception is
com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Cannot construct instance of `java.util.HashSet`
(no Creators, like default constructor, exist): no default no-arguments constructor found

If I add java.util.HashSet.class as a type hint, it works.
With postgres-mvc, this type hint exists, and adding tags to a post works.

Nevermind, I was able to reproduce the issue with postgres-mvc. It only seems to happen in native mode, not in JVM mode.


Will you accept big change for viewdock data structure?

Two days ago a guy at Upwork asked me if I can fix all issues tagged "viewdock" in ProDBG project. I checked out if I can and have a question to maintainers of this project. Will you accept changes if I change data structures a bit and then fix those problems?
Current implementation seems to be pretty hacky and is not suited well for its task. Here what I mean:
Current Viewdock data structures seem to be unobvious. When empty Workspace is created, it looks like follows:
Workspace
    splits: Split
        left: None
        right: None
        left_docks: Container
            docks:
            rect: Rect
                x: 0
                y: 0
                width: 0
                height: 0
        right_docks: Container
            docks:
            rect: Rect
                x: 0
                y: 0
                width: 0
                height: 0
        ratio: 0
        direction: Full
        handle: SplitHandle(0)
        rect: Rect
            x: 0
            y: 0
            width: 0
            height: 0
    rect: Rect
        x: 0,
        y: 0,
        width: 1280,
        height: 780
    window_border: 4
    handle_counter: SplitHandle(0)

Though there is nothing in this workspace yet, it already contains a Split. Naturally Split should always contain two children splitted horizontally or vertically. In this example our split has "Full" direction and empty left_docks and right_docks containers to show it is not a split.
Workspace with single Dock in it looks like follows (unchanged info like Workspace.rect and  workspace.window_border is removed since they never change in following examples):
Workspace
    splits: Split
        left: None
        right: None
        left_docks: Container
            docks: Dock
                handle: DockHandle(0)
                plugin_name: ""
                plugin_data: None
                rect: Rect
                    x: 0
                    y: 0
                    width: 0
                    height: 0
            rect: Rect
                x: 0
                y: 0
                width: 1280
                height: 780
        right_docks: Container
            docks:
            rect: Rect
                x: 0
                y: 0
                width: 1280
                height: 780
        ratio: 1
        direction: Horizontal
        handle: SplitHandle(0)
        rect: Rect
            x: 0
            y: 0
            width: 1280
            height: 780
    handle_counter: SplitHandle(0)

Now we have horizontal split direction with ratio of 1 (which means all the space is given to left dock) and new dock is added as a left child of split.
Finally, when actual split is done, Workspace looks like
Workspace
    splits: Split
        left: None
        right: None
        left_docks: Container
            docks: Dock
                handle: DockHandle(0)
                plugin_name: ""
                plugin_data: None
                rect: Rect
                    x: 0
                    y: 0
                    width: 0
                    height: 0
            rect: Rect
                x: 0
                y: 0
                width: 1280
                height: 780
        right_docks: Container
            docks: Dock
                handle: DockHandle(1)
                plugin_name: ""
                plugin_data: None
                rect: Rect
                    x: 0
                    y: 0
                    width: 0
                    height: 0
            rect: Rect
                x: 0
                y: 780
                width: 1280
                height: 0
        ratio: 0.5
        direction: Horizontal
        handle: SplitHandle(0)
        rect: Rect
            x: 0
            y: 0
            width: 1280
            height: 780
    handle_counter: SplitHandle(1)

Now we have Docks in each part of split and meaningful split direction and ratio.
When new split happens, structure changes as follows:
Workspace
    splits: Split
        left: Some(SplitHandle(2))
        right: None
        left_docks: Container
            docks:
            rect: Rect
                x: 0
                y: 0
                width: 1280
                height: 390
        right_docks: Container
            docks: Dock
                handle: DockHandle(1)
                plugin_name: ""
                plugin_data: None
                rect: Rect
                    x: 0
                    y: 0
                    width: 0
                    height: 0
            rect: Rect
                x: 0
                y: 390
                width: 1280
                height: 390
        ratio: 0.5
        direction: Horizontal
        handle: SplitHandle(0)
        rect: Rect
            x: 0
            y: 0
            width: 1280
            height: 780
     Split
        left: None
        right: None
        left_docks: Container
            docks: Dock
                handle: DockHandle(2)
                plugin_name: ""
                plugin_data: None
                rect: Rect
                    x: 0
                    y: 0
                    width: 0
                    height: 0
            rect: Rect
                x: 0
                y: 0
                width: 0
                height: 0
        right_docks: Container
            docks: Dock
                handle: DockHandle(0)
                plugin_name: ""
                plugin_data: None
                rect: Rect
                    x: 0
                    y: 0
                    width: 0
                    height: 0
            rect: Rect
                x: 0
                y: 0
                width: 1280
                height: 390
        ratio: 0.5
        direction: Vertical
        handle: SplitHandle(2)
        rect: Rect
            x: 0
            y: 0
            width: 0
            height: 0
    handle_counter: SplitHandle(2)

First split's left property now points to another split. However, corresponding left_docks container is now empty.
What I don't like about this structure?

Split contains "special" states for several situations. Direction "Full", empty Containers, ratio of 0 or 1 and special  function to check for this states. It even says it is a hack:

pub fn no_split(&mut self, direction: Direction, dock_handle: DockHandle) -> bool {
    // hack!
    if self.direction == Direction::Full {
        self.direction = direction;
    }

    if self.is_left_zero_and_none() {
    ...

Split contains both left and left_docks properties. These are mutually exclusive: either you have child dock or another split but not both.

Instead I want to use structure like this. Empty workspace:
Workspace
    root_area: None
    rect: Rect
    window_border: 4

Workspace with single dock (rect and window_border are not shown):
Workspace
    root_area: Container

Workspace with two docks (single split):
Workspace
    root_area: Split
        direction: Horizontal(0.5)
        left: Container
        right: Container

Workspace with three docks:
Workspace
    root_area: Split
        direction: Horizontal(0.5)
        left: Split
            direction: Vertical(0.5)
            left: Container
            right: Container
        right: Container

And so on. In Rust these structures will look like:
pub struct Workspace {
    root_area: Option<Area>, // None for non-initialized Workspace
}

pub struct Container {
    // not changed
}

pub struct Split {
    pub left: Box<Area>,
    pub right: Box<Area>,
    pub direction: Direction,
    pub handle: SplitHandle,
    rect: Rect,
}

pub enum Direction {
    Horizontal(f32),
    Vertical(f32)
}

pub enum Area {
    Split(Split),
    Container(Container),
}

Will you accept these changes if I make a proper pull request? Or should I just try to apply more hacks to current data structure in order to make it work?
By the way, am I allowed to use tree-like structure with Box<> or Splits and Container should be kept in vectors and referenced only by their handles?

Hi,
These changes looks great so please go ahead and do them and you are allowed to use Box if you want of course. Just make sure to update the serialize code as well when you do these changes.


[WFLY-12268] ${maven.repository.url} in repository url is not evaluat…

…ed when org.jboss:jboss-parent is missing
Issue: https://issues.jboss.org/browse/WFLY-12268
Please make sure your PR meets the following requirements:

[ ] Pull Request title is properly formatted: [WFLY-XYZ] Subject or WFLY-XYZ Subject
[ ] Pull Request contains link to the JIRA issue(s)
[ ] Pull Request contains description of the issue(s)
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Attached commits represent units of work and are properly formatted

Changes in this PR:

Remove the property: maven.repository.url because it is not useful for evaluate jboss-parent as the repository url (Known Maven issue)
Added a profile: http and can be activated using property: -Dmaven.repository.protocol=http to switch to use http repository.

@bstansberry would you please review? Thanks :)

@wildfly/mergers-full can someone review, please? This is blocking downstream CI builds.

@wildfly/mergers-full test

command line @wildfly/mergers-full test

command line @wildfly/mergers-full test2

This is valid and I was bale to replicate this locally. We'll need a core PR as well. We should just remove the properties and use the URL specifically.

Created https://issues.jboss.org/browse/WFCORE-4564 for the WildFly core changes, I will fire PR after we have agreement on the profile part :)

@jamezp OK, Updated as required, please review again, thanks

PR for WildFly Core is: https://github.com/wildfly/wildfly-core/pull/3857

I'm closing this as we do want these properties for proxies. @gaol I'm putting an email together now explaining what we want to do here.


3.4.2 bug Cannot read property 'updateOn' of undefined

Hi mate, somethings not right with this latest release. I get this error. The tests seem to pass though. (congrats for getting travis to work! 🤠)
I think you need ngModelOptions defined in the directive isolation scope. Also it would be nice if it were optional.
Cannot read property 'updateOn' of undefined
    at new NgModelOptionsController (gallery.js:95745)

So I dont have much time to look at this at the moment.

@stephennancekivell I definitely tested without passing in ng-model-options and cannot replicate the problem. I may need more to go on to try and fix it.

Hi, yea thanks. It looks like its only on angular 1.5.

Fixed in commit 61469d5545074ff3695e0966aad7e932ed5d6546 and released in v3.4.3

Legend! Thanks mate, I owe you a beer.


Civet as a virtual lang via vscode rather than compiled

Adoption would be way higher if Civet was just a vscode plugin. The idea is that you can view any js/tsx/json file as Civet and when you write/code all it's doing is updating the js/ts/json file with the correct js/ts/json. We do this already for Markdown where we view the previewed version and any edits update the markdown file in-place.

I looked into this. it's basically really hard 😂 vscode doesn't provide enough APIs for this. You're forced to create your own editor

It might be possible with ts2civet and a lot of additions to the Civet LSP. We already do tons of compiling and source mapping so it might not be completely unachievable but it is a bit of work for sure.

awesome 🎉

ok I think this is possible now after some more research

https://volarjs.dev/
Might be interesting here. I already successfully used it to create my own civet extension. Also look up the vscode extension from astrojs, it's build with volarjs


TypeError: can only concatenate tuple (not "list") to tuple

When running Click v7.1.2 on Python 3.10.0, there is a TypeError exception on click/core.py, line 914:

TypeError: can only concatenate tuple (not "list") to tuple

Here's the stack:
Traceback (most recent call last):
  File "/var/www/project/manage.py", line 13, in <module>
    manager.run()
  File "/var/www/project/surge/manager/manager.py", line 60, in run
    return self.cli()
  File "/var/www/project/env/lib/python3.10/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/var/www/project/env/lib/python3.10/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/var/www/project/env/lib/python3.10/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/var/www/project/env/lib/python3.10/site-packages/click/core.py", line 1257, in invoke
    sub_ctx = cmd.make_context(cmd_name, args, parent=ctx)
  File "/var/www/project/env/lib/python3.10/site-packages/click/core.py", line 700, in make_context
    self.parse_args(ctx, args)
  File "/var/www/project/env/lib/python3.10/site-packages/click/core.py", line 1044, in parse_args
    parser = self.make_parser(ctx)
  File "/var/www/project/env/lib/python3.10/site-packages/click/core.py", line 965, in make_parser
    for param in self.get_params(ctx):
  File "/var/www/project/env/lib/python3.10/site-packages/click/core.py", line 914, in get_params
    rv = rv + [help_option]

Sorry for my late reply here, but I agree that I've created a Command directly so it's definitely an issue on my end ;)
Sorry for the troubles!


Cloud Server PAT authenticate error

I am using confluence server not cloud and based on the following link it was developed that we can create Personal Access Token which is similar to API token in confluence cloud to authenticate external application to be authenticated.
https://jira.atlassian.com/browse/CONFSERVER-57389
sphinx-build-confluence report
(system)
 platform: macOS-12.2-x86_64-i386-64bit
   python: 3.9.7 (default, Oct 13 2021, 06:45:31) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
   sphinx: 4.1.2
 requests: 2.25.1
  builder: 1.7.1

(configuration)
~default configuration~

(error loading configuration)
no documentation/missing configuration

I raised previously a question before regarding authentication with confluence in issue 610
I can curl confluence rest api with my PAT but I can't do it with sphinx if there is anything missing in config that I didn't follow but I get authentication error on the same PAT token with sphinx

# Configuration file for the Sphinx documentation builder.
#
# This file only contains a selection of the most common options. For a full
# list see the documentation:
# https://www.sphinx-doc.org/en/master/usage/configuration.html

# -- Path setup --------------------------------------------------------------

# If extensions (or modules to document with autodoc) are in another directory,
# add these directories to sys.path here. If the directory is relative to the
# documentation root, use os.path.abspath to make it absolute, like shown here.
#
import os
import sys
sys.path.insert(0, os.path.abspath('../..'))
sys.path.insert(0, os.path.abspath('..'))

# -- Project information -----------------------------------------------------

project = 'data_css_webtracking'
copyright = '2021, Amira Lotfy'
author = 'Amira Lotfy'

# The full version, including alpha/beta/rc tags
release = '1.0'

# -- General configuration ---------------------------------------------------

# Add any Sphinx extension module names here, as strings. They can be
# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
# ones.
extensions = [
    'sphinx.ext.autodoc',
    'sphinx.ext.napoleon',
    'sphinx.ext.intersphinx',
    'sphinx.ext.ifconfig',
    'sphinx.ext.viewcode',
    'sphinx.ext.githubpages',
    'sphinxcontrib.confluencebuilder']
latex_elements = {
# The paper size ('letterpaper' or 'a4paper').
    'papersize': 'letterpaper',
# The font size ('10pt', '11pt' or '12pt').
    'pointsize': '10pt',
# Additional stuff for the LaTeX preamble.
    'preamble': '',
# Latex figure (float) alignment
    'figure_align': 'htbp',
}

# Add any paths that contain templates here, relative to this directory.
templates_path = ['_templates']

# List of patterns, relative to source directory, that match files and
# directories to ignore when looking for source files.
# This pattern also affects html_static_path and html_extra_path.
exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']

# -- Options for HTML output -------------------------------------------------

# The theme to use for HTML and HTML Help pages.  See the documentation for
# a list of builtin themes.
#
html_theme = 'classic'

# Add any paths that contain custom static files (such as style sheets) here,
# relative to this directory. They are copied after the builtin static files,
# so a file named "default.css" will overwrite the builtin "default.css".
html_static_path = ['_static']

confluence_publish = True
confluence_space_key = "XX"
confluence_parent_page = 'XXXXX'
confluence_page_hierarchy = True
# confluence_ask_password = True
# (for confluence server)
confluence_server_url = 'https://confluence.example.com/'
confluence_server_user = "USER"
confluence_server_pass = 'TOKEN'

@AmiraLotfy, ah ~~ I honestly have only used/tested with the API tokens when they were first introduced on Cloud instances. There was an assumption that personal access tokens (PATs) would be handled in a similar manner (just accepting a token value). Upon further inspection, it appears to not be the case. It appears to use PATs, the Authorization header must be set with the token value.
Fortunately, using PATs is possible by manually setting the header option using the confluence_publish_headers configuration. To authenticate with a PAT do not set (or unset) confluence_server_user/confluence_server_pass, while using the following in a Sphinx configuration:
pat_token = 'MY_PAT_VALUE'
confluence_publish_headers = {
    'Authorization': 'Bearer ' + pat_token,
}

In the future, a confluence_publish_pat option will probably be introduced by this extension for convenience/clarity.

Thank you so much, I can use this workaround until the option is added in further release.

Changes have been added in #618 to improve users support for configuring personal access tokens (PATs). PATs (not to be confused with API tokens) will be able to configured by using the following:
confluence_publish_token = `my-token`

This change has been added into the main branch and should be made available next stable release (v1.8). Users wanting to use this option right away, the development version of this extension can be installed. Otherwise, the workaround mentioned above can be used for the interim.

v1.8 is now available on PyPI -- marking as closed.