2.6.2 Release Notes Extension for VSTS - Cannot bind argument to parameter 'Message' because it is null.

VSTS Extension you are using
Release Notes Extension
Where are you running it?
VSTS
Version of Extension/Task
2.6.2
Expected behavior and actual behavior
Expected: Extension task runs without error
Actual: Error message
Steps to reproduce the problem
Build setup: Build Agent installed on local build machine to run Continuous Integration tests.
After MSBuild completes I have the Generate Release Notes task start with
OutputFile: $(BUILD.STAGINGDIRECTORY)/releasenotes.md
Inline Template Location with this template:
_#Release notes for build $defname
Build Number  : $($build.buildnumber)
Build started : $("{0:dd/MM/yy HH:mm:ss}" -f [datetime]$build.startTime)
Source Branch : $($build.sourceBranch)
###Associated work items
@@WILOOP@@

$($widetail.fields.'System.WorkItemType') $($widetail.id) [Assigned by: $($widetail.fields.'System.AssignedTo')]     $($widetail.fields.'System.Title')
@@WILOOP@@
###Associated change sets/commits
@@CSLOOP@@
ID $($csdetail.changesetid)$($csdetail.commitid) $($csdetail.comment)
@@CSLOOP@@_

I have default credentials checked.
I receive the following message when it runs:
2017-03-23T18:58:32.4298505Z ##[section]Starting: Generate release notes
2017-03-23T18:58:32.4428594Z Preparing task execution handler.
2017-03-23T18:58:32.7748425Z Executing the powershell script: C:\agent_work_tasks\GenerateReleaseNotes_661bc005-61be-430f-b994-065bf08c0f39\2.6.2\GenerateReleaseNotes.ps1
2017-03-23T18:58:32.7748425Z Build Number  : $($build.buildnumber)
2017-03-23T18:58:32.7748425Z Build started : $("{0:dd/MM/yy HH:mm:ss}" -f [datetime]$build.startTime)
2017-03-23T18:58:32.7748425Z Source Branch : $($build.sourceBranch)
2017-03-23T18:58:32.7748425Z ###Associated work items
2017-03-23T18:58:32.7748425Z @@WILOOP@@
2017-03-23T18:58:32.7748425Z * $($widetail.fields.'System.WorkItemType') $($widetail.id) [Assigned by: $($widetail.fields.'System.AssignedTo')]     $($widetail.fields.'System.Title')
2017-03-23T18:58:32.7748425Z @@WILOOP@@
2017-03-23T18:58:32.7748425Z ###Associated change sets/commits
2017-03-23T18:58:32.7748425Z @@CSLOOP@@
2017-03-23T18:58:32.7748425Z * ID $($csdetail.changesetid)$($csdetail.commitid) $($csdetail.comment)
2017-03-23T18:58:32.7748425Z @@CSLOOP@@)
2017-03-23T18:58:33.8308569Z ##[error]System.ArgumentException: Invalid JSON primitive: .
2017-03-23T18:58:33.8308569Z    at System.Web.Script.Serialization.JavaScriptObjectDeserializer.DeserializePrimitiveObject()
2017-03-23T18:58:33.8308569Z    at System.Web.Script.Serialization.JavaScriptObjectDeserializer.DeserializeInternal(Int32 depth)
2017-03-23T18:58:33.8308569Z    at System.Web.Script.Serialization.JavaScriptObjectDeserializer.BasicDeserialize(String input, Int32 depthLimit, JavaScriptSerializer serializer)
2017-03-23T18:58:33.8308569Z    at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize(JavaScriptSerializer serializer, String input, Type type, Int32 depthLimit)
2017-03-23T18:58:33.8308569Z    at Microsoft.PowerShell.Commands.JsonObject.ConvertFromJson(String input, ErrorRecord& error)
2017-03-23T18:58:33.8308569Z    at Microsoft.PowerShell.Commands.ConvertFromJsonCommand.ProcessRecord()
2017-03-23T18:58:33.8308569Z    at System.Management.Automation.CommandProcessor.ProcessRecord()
2017-03-23T18:58:33.8908587Z ##[warning]Unable to get associated work items, most likely cause is the build has been deleted
2017-03-23T18:58:33.8928680Z ##[warning]Invalid JSON primitive: .
2017-03-23T18:58:33.9478600Z ##[warning]Unable to get details of changeset/commit, most likely cause is the build has been deleted
2017-03-23T18:58:33.9478600Z ##[warning]Invalid JSON primitive: .
2017-03-23T18:58:34.0278835Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Message' because it is null.
2017-03-23T18:58:34.0278835Z    at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
2017-03-23T18:58:34.0288638Z    at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
2017-03-23T18:58:34.0288638Z    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-03-23T18:58:34.0288638Z    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-03-23T18:58:34.0288638Z    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-03-23T18:58:34.0288638Z    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-03-23T18:58:34.0778677Z ##[error]PowerShell script completed with 2 errors.
2017-03-23T18:58:34.0788654Z ##[section]Finishing: Generate release notes

You are not getting back valid JSON from the API - Why?
It thinks the build is delete 'Unable to get associated work items, most likely cause is the build has been deleted' - again why?

OK a few things to look at

On the build variable set the system.debug variable to true - this gives a more detailed error log
Try with the use default credentials parameter on the task set to false

Hi Richard,
I messed around with the settings and got it working.
This works with
Default Credentials Off
Primary Artifact Off
Release Only Off
do you still want the logs for it?

No if you are working that is great

Im getting this error:
cannot process [Release completed $("{0:dd/MM/yy HH:mm:ss}" -f [datetime]$release.modifiedOn) ]
After running debug mode on the same bug I am having about message being 'null'

@AppleEducate are you using the task in a build or a release?
Reason I ask the $release variable is only set in a release. If in a build use a build specific sample from the templates in this repo.
If the problems persist please log it as a new issue with a detailed debug log (set the build variable system.debug = true), it can get confusing when a new issue is logged against an old one.

I am using this in a release. I have tried using in a build too and am getting the same error. I am using the default template. I will contine to troubleshoot and submit a new issue if I cannot resolve. Thank you
Rody Davis Jr.
Full Stack Mobile Developer
Github | Website | Appstore | LinkedIn
Twitter | Facebook | YouTube
On Mar 1, 2018, 1:44 PM -0500, Richard Fennell<EMAIL_ADDRESS>wrote:

@AppleEducate are you using the task in a build or a release?
Reason I ask the $release variable is only set in a release. If in a build use a build specific sample from the templates in this repo.
If the problems persist please log it as a new issue with a detailed debug log (set the build variable system.debug = true), it can get confusing when a new issue is logged against an old one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Create All-About-Groups.md

Added All-about-groups.md file to document the different types of Groups available in Office 365.
Please use this template to ensure easier processing of your pull request
Category

[ ] Content fix
[x] New article

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.

Contents of the Pull Request
Added one page, All-about-groups.md

Docs Build status updates of commit 0e99a46:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/All-About-Groups.md
:warning:Warning
View
Details

Community/All-About-Groups.md

Line 23, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/hybrid/whatis-azure-ad-connect' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 23, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/groups-create-rule' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 29, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#available-roles' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 32, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-groups-create-azure-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 34, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/groups-settings-v2-cmdlets' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 38, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/licensing-groups-assign' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 44, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoft-365/admin/create-groups/office-365-groups' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 50, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoft-365/solutions/manage-creation-of-groups?view=o365-worldwide' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 78, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/sharepoint/dev/features/groupify/groupify-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a8d5d09:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/All-About-Groups.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Not bad for a rookie, @ToddKlindt. I'll take a pass through and fix the formatting stuff.

Not bad for a rookie, @ToddKlindt. I'll take a pass through and fix the formatting stuff.

I had a good teacher.


x/tools/gopls: autocompletion for dependencies not working in Emacs

What version of Go are you using (go version)?

$ go version
go version go1.15.6 linux/amd64

Does this issue reproduce with the latest release?
Yes, with Go, gopls and Emacs latest versions available for my architecture and distribution, the issue described below is reproducible.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/manuel/.cache/go-build"
GOENV="/home/manuel/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/manuel/workbench/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/manuel/workbench/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.15"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.15/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build414655594=/tmp/go-build -gno-record-gcc-switches"

Emacs environment:
GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.23, cairo version 1.16.0) of 2020-11-08, modified by Debian

$ gopls version
golang.org/x/tools/gopls v0.6.0
<EMAIL_ADDRESS>h1:vD171EDBkyUVyp9B45IYXklV/VEfbHgX0FKw0Q0dO30=

What did you do?
I was redirected to create a new issue from #36165 and, as suggested by @stamblerre I also installed the latest version of gopls.
With my $GOPATH set, I open a file in a buffer in my Emacs setup with LSP server and go-mode as stated here and with no specific settings for lsp. The issue I come across is missing autocompletion for external packages (that is, dependencies declared in go.mod and installed with go get), at the same time, the editor highlights the import of external packages as errors, as well as any use of the imports within the file.
Below, an (edited -- removed references to private repo) extract of the output
lsp-log buffer
Command "gopls" is present on the path.
Command "gopls" is present on the path.
Found the following clients for /home/manuel/workbench/go/src/github.com/EDITED/api/handle_checkout.go: (server-id gopls, priority 0)
The following clients were selected based on priority: (server-id gopls, priority 0)
2020/12/29 10:34:50 go env for /home/manuel
(root /home/manuel)
(go version go version go1.15.6 linux/amd64)
(valid build configuration = false)
(build flags: [])
GOMODCACHE=/home/manuel/workbench/go/pkg/mod
GONOPROXY=
GOPRIVATE=
GONOSUMDB=
GOPATH=/home/manuel/workbench/go
GOINSECURE=
GOROOT=/usr/lib/go-1.15
GOCACHE=/home/manuel/.cache/go-build
GOMOD=
GOPROXY=https://proxy.golang.org,direct
GOSUMDB=sum.golang.org
GO111MODULE=
GOFLAGS=
2020/12/29 10:34:50 go/packages.Load
snapshot=0
directory=/home/manuel
query=[./ builtin]
packages=2
2020/12/29 10:34:50 go/packages.Load
snapshot=0
directory=/home/manuel
query=[./]
packages=1
2020/12/29 10:34:50 go/packages.Load
snapshot=1
directory=/home/manuel
query=[file=/home/manuel/workbench/go/src/github.com/EDITED/api/handle_checkout.go]
packages=1
2020/12/29 10:34:50 go/packages.Load
snapshot=1
package_path="github.com/EDITED/api"
files=[/home/manuel/workbench/go/src/github.com/EDITED/api/api.go /home/manuel/workbench/go/src/github.com/EDITED/api/handle_checkout.go /home/manuel/workbench/go/src/github.com/EDITED/api/handle_webhook.go /home/manuel/workbench/go/src/github.com/EDITED/api/routes.go]
2020/12/29 10:34:50 go/packages.Load
snapshot=1
package_path="github.com/EDITED/api"
files=[/home/manuel/workbench/go/src/github.com/EDITED/api/api.go /home/manuel/workbench/go/src/github.com/EDITED/api/handle_checkout.go /home/manuel/workbench/go/src/github.com/EDITED/api/handle_webhook.go /home/manuel/workbench/go/src/github.com/EDITED/api/routes.go]
2020/12/29 10:34:50 go/packages.Load
snapshot=1
directory=/home/manuel
query=[file=/home/manuel/workbench/go/src/github.com/EDITED/api/handle_checkout.go]
packages=1
2020/12/29 10:34:50 github.com/EDITED/lib/server/middleware/opencensus: no dep handle for contrib.go.opencensus.io/exporter/stackdriver/propagation: no metadata for contrib.go.opencensus.io/exporter/stackdriver/propagation
snapshot=1
2020/12/29 10:34:50 github.com/EDITED/lib/server/middleware/opencensus: no dep handle for go.opencensus.io/plugin/ochttp: no metadata for go.opencensus.io/plugin/ochttp
snapshot=1
2020/12/29 10:34:50 github.com/EDITED/lib/server/middleware/opencensus: no dep handle for go.opencensus.io/trace: no metadata for go.opencensus.io/trace
snapshot=1
2020/12/29 10:34:50 github.com/EDITED/lib/server/middleware/opencensus: no dep handle for go.opencensus.io/trace/propagation: no metadata for go.opencensus.io/trace/propagation
snapshot=1
2020/12/29 10:34:50 github.com/EDITED/lib/server/middleware/opencensus: no dep handle for contrib.go.opencensus.io/exporter/stackdriver: no metadata for contrib.go.opencensus.io/exporter/stackdriver
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/swaggo/http-swagger: no metadata for github.com/swaggo/http-swagger
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/alecthomas/template: no metadata for github.com/alecthomas/template
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/swaggo/http-swagger: no metadata for github.com/swaggo/http-swagger
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/alecthomas/template: no metadata for github.com/alecthomas/template
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72: no metadata for github.com/stripe/stripe-go/v72
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/customer: no metadata for github.com/stripe/stripe-go/v72/customer
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for contrib.go.opencensus.io/exporter/stackdriver/propagation: no metadata for contrib.go.opencensus.io/exporter/stackdriver/propagation
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for go.opencensus.io/plugin/ochttp: no metadata for go.opencensus.io/plugin/ochttp
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/webhook: no metadata for github.com/stripe/stripe-go/v72/webhook
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/taxrate: no metadata for github.com/stripe/stripe-go/v72/taxrate
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/checkout/session: no metadata for github.com/stripe/stripe-go/v72/checkout/session
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/price: no metadata for github.com/stripe/stripe-go/v72/price
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72: no metadata for github.com/stripe/stripe-go/v72
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/checkout/session: no metadata for github.com/stripe/stripe-go/v72/checkout/session
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for contrib.go.opencensus.io/exporter/stackdriver/propagation: no metadata for contrib.go.opencensus.io/exporter/stackdriver/propagation
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/customer: no metadata for github.com/stripe/stripe-go/v72/customer
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/price: no metadata for github.com/stripe/stripe-go/v72/price
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/taxrate: no metadata for github.com/stripe/stripe-go/v72/taxrate
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for go.opencensus.io/plugin/ochttp: no metadata for go.opencensus.io/plugin/ochttp
snapshot=1
2020/12/29 10:34:50 github.com/EDITED: no dep handle for github.com/stripe/stripe-go/v72/webhook: no metadata for github.com/stripe/stripe-go/v72/webhook
snapshot=1
2020/12/29 10:34:51 errors loading workspace: You are outside of a module and outside of $GOPATH/src.
If you are using modules, please open your editor to a directory in your module.
If you believe this warning is incorrect, please file an issue: https://github.com/golang/go/issues/new.
snapshot=1
directory=file:///home/manuel
2020/12/29 10:35:20 background imports cache refresh starting
2020/12/29 10:35:20 background refresh finished after 34.49514ms

NOTE: The above log is running latest gopls, the log posted in my last comment in #36165 was extracted when running "gopls build in $GOPATH mode" (i.e.: installed like go get golang.org/x/tools/gopls).
Additional information in the
*Messages* buffer
Loading /etc/emacs/site-start.d/00debian.el (source)...done
Loading /etc/emacs/site-start.d/50autoconf.el (source)...done
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...
Loading debian-ispell...
Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)...done
Loading debian-ispell...done
Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...done
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...done
Loading /etc/emacs/site-start.d/50figlet.el (source)...done
Loading /etc/emacs/site-start.d/50mu4e.el (source)...done
Wrote /home/manuel/.emacs.d/config.el [83 times]
Tangled 83 code blocks from config.org
Loading /home/manuel/.emacs.d/config.el (source)...done
Loaded /home/manuel/.emacs.d/config.el
Starting Emacs daemon.
When done with this frame, type C-x 5 0
[yas] Prepared just-in-time loading of snippets successfully.
LSP :: Connected to [gopls:761133 status:starting].
LSP :: gopls:761133 initialized successfully
LSP :: gopls setting "codelens" is deprecated, use "codelenses" instead

### What did you expect to see?
Autocompletion working for external packages, that is, in Emacs, M-x completion-at-point should return completions for dependencies.
What did you see instead?
M-x completion-at-point returns nothing when attempting to complete external packages, as opposed to, e.g. running M-x completion-at-point over fmt.Er, which returns fmt.Errorf(format string, a ...interface{})

It sounds like you're using modules, but gopls isn't finding a go.mod file in your workspace. Please make sure to open Emacs with your workspace root configured to your module root (the directory containing the go.mod file).

Indeed I am using modules. I am not sure what do you mean with "opening Emacs with the workspace root configured to the module root". I include below the structure of the repo, which is based on a "monorepo" structure (several services hanging from the root folder + lib and other tooling, with go.mod at the root).
.
├── core
│   ├── api
│   │   ├── ...
│   ├── app
│   │   ├── ...
│   ├── db
│   │   ├── ...
│   ├── Dockerfile
│   ├── main.go
│   ├── Makefile
│   ├── README.md
│   ├── scripts
│   ├── ...
├── docker-compose.yml
├── go.mod
├── go.sum
├── lib
│   └── server
│       ├── ...
├── Makefile
│   ...

The logs shown on my previous comment are tied to opening a file from ./core/api.

The ./core/api workspace folder should work as long as there is only 1 go.mod file in the workspace, but to be sure, I would open the directory containing the go.mod file. I'm not sure exactly how to configure your workspace folder, but I believe you should have seen a prompt, and if not, there may be a command you can run to set it.

Wow, this took me quite a while.
The key thing here being the "workspace". It turns out I had to add my projects to a "workspace". I got the hint for doing this from the Keybindings available for lsp-mode in Emacs, so not a problem of the tooling, but rather PEBCAK 😃
Thanks for the help!


Adding Polish language

Adding polish translations.

This is awesome, thank you for the contribution @danieltechdev !


Missing antialiasing on boxes

I am not sure if this is a wrong setting or an issue. I could not find anything on the documentation or stackoverflow regarding this.
I am on Mac OS Sierra, tested on puppeter version 0.11 and 0.12 alpha. In 0.12 the div edges were better rendered but still no antialiasing, which does not look very good. I attached screenshots and example code:
const puppeteer = require('puppeteer');

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  await page.goto('file:///Users/manuel/dev/raviteq/url2img/index.html');
  await page.screenshot({
    path: 'example.png',
    clip: {
      x:0,
      y:0,
      width: 300,
      height: 250
    }
  });

  await browser.close();
})();

Original html file:
index.html.zip
Original rendered image with puppeteer:

Zoom in into edge:

Result rendered in standard google chrome:

We run with --disable-gpu enabled by default on the launched Chrome instances. With that in mind, this looks expected to me depending on how exactly the boxes get rendered.

I understand. How can I override this setting, and also, why would the software renderer not support antialiasing, is it a chrome limitation?

Currently you can't override this from what I can tell. I think if we switch to the chrome-launcher package (which as I recall is being looked into) then it should be possible to enable GPU stuff.
As to why it isn't supported, that isn't something I'm able to answer. Perhaps someone from the team can provide some detailed information on that one.

https://github.com/GoogleChrome/puppeteer/issues/872 will allow overriding default flags.

Thanks Eric, closing as a dupe of #872.


include object metadata in conclusion of multi-part upload

Adds the inserted object metadata to the Ok side of the multi-part object upload return type. This allows for client-side validation that the written checksum is correct.

Thanks for your contribution. I will merge when the CI is fixed.

👍 this is ready for another CI run.


[Candidate 2v2 Frontier Rails ZH v1] Tech Buildings have custom rotations that decrease visibility on flag

Observed behavior
Tech Buildings have custom rotations that decrease visibility on flag.
Expected behavior
Tech Buildings use default rotation or custom rotations that provide high visibility on flag.
Screenshots

I'll adjust them


Update to Result 1.0

Updated the Result library to its 1.0.0 release

Thanks for the PR. I merged it in! :star2:

Great! Thank you very much!


Prettier.nvim doesn't work

I've generated a vscode extension code with yo and saw prettier didn't work.
I tried adding a .prettierrc file, running :Prettier but nothing works.
It seems NullLs does run but simply doesn't write the file.
I tried also restarting prettierd.
My configuration
Ignore all the helper functions I created as they are unused.
https://github.com/dlvhdr/dotfiles/blob/26266aef5cb4738c52f6c4c72d4326f794512dc1/.config/nvim/lua/dlvhdr/lsp/servers/null-ls.lua#L1
NullLsInfo

NullLsLog
[TRACE Sun Aug 14 21:34:22 2022] .../site/pack/packer/start/null-ls.nvim/lua/null-ls/rpc.lua:121: received LSP request for method shutdown
[TRACE Sun Aug 14 21:34:22 2022] .../site/pack/packer/start/null-ls.nvim/lua/null-ls/rpc.lua:146: received LSP notification for method exit

LspInfo

Seems to be working with prettier, but that's super slow.
Checking why prettierd doesn't work now.

This should be fixed now. This was the root cause: https://github.com/fsouza/prettierd/issues/237
Prettier CLI options are not supported by prettierd. So for now, prettier options passed to prettier.setup({}) won't be used with prettierd.


Remove extra forward slash from the command.

$DOCKER run --name $AGENT --rm -it ${DOCKER_OPTS} \   --network=${DOCKER_NET} \   -p <IP_ADDRESS>:$AGENT_PORT_RANGE:$AGENT_PORT_RANGE \   -v "/$(pwd)/../logs:/home/indy/logs" \   $DOCKER_ENV \   faber-alice-demo $AGENT_MODULE --port $AGENT_PORT $ARGS
Issue/Error -

Trying to detect ngrok service endpoint
jq not found
<IP_ADDRESS>
docker: Error response from daemon: Mounts denied:
The path //Users/shivammutreja/advance_security/aries-cloudagent-python/demo/../logs
is not shared from OS X and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> File Sharing.
See https://docs.docker.com/docker-for-mac/osxfs/#namespaces for more info.

Probable solution - In the aforementioned command $(pwd) will already return the path with a forward slash in the front. This means there is no need for an extra forward slash in the front.

https://github.com/hyperledger/aries-cloudagent-python/pull/740


Load test rabbitmq fix on dev.

Without a purge endpoint, this will require systems.

Load tested on QA


Navigation buttons are missing

Hi, thanks for the wonderful theme, I like it a lot, I use it in my blog https://onmyway133.github.io/. It works perfectly until yesterday. Now the navigation buttons are missing but my yml file remains unchanged https://github.com/onmyway133/onmyway133.github.io/blob/master/_config.yml
How to remedy this? Thanks

Thanks for the kind words @onmyway133! The reason for the issue is due to some breaking changes in the theme. I've made a pull request to your blog to fix the navigation


cannot register the dll

Regsvr32 says: "The specified module could not be found."
DependencyWalker says that:
Ucrtbased.dll
EfsCode.dll
Dmenterprisediagnostics.dll
Emclient.dll
wc_storage.dll
wpaxholder.dll
Cannot be found…
I have X86 and x64 C++ redistributable installed. Still no show...

Apparently ucrtbased.dll is the debug version of ucrtbase.dll.


db tests broken using native mocha & node

db tests broken using native mocha & node
current work around runs tests in a bash script

No QA needed.


App crash

GitHub Source build
I had to delete the test folder in Android Studio.
The app does not ask for permission to access the location, which causes the crash.

FATAL EXCEPTION: main
Process: com.mob.lee.fastair, PID: 31432
java.lang.IllegalArgumentException: Permission launcher is null,you should call registerPermission first
at com.mob.lee.fastair.viewmodel.AppViewModel.withPermission(AppViewModel.kt:68)
at com.mob.lee.fastair.fragment.DiscoverFragment.setting(DiscoverFragment.kt:62)
at com.mob.lee.fastair.base.AppFragment.onViewCreated(AppFragment.kt:52)
at androidx.fragment.app.Fragment.performViewCreated(Fragment.java:3019)
at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:551)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:261)
at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1840)
at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1764)
at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1701)
at androidx.fragment.app.FragmentManager$4.run(FragmentManager.java:488)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7386)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)

Considering that it goes out after I compile it, it probably loads the file lists. How about limiting the list of visible files to 20 pieces. And then by pressing the 'load more' button

GitHub Source build
I had to delete the test folder in Android Studio. The app does not ask for permission to access the location, which causes the crash.
FATAL EXCEPTION: main Process: com.mob.lee.fastair, PID: 31432 java.lang.IllegalArgumentException: Permission launcher is null,you should call registerPermission first at com.mob.lee.fastair.viewmodel.AppViewModel.withPermission(AppViewModel.kt:68) at com.mob.lee.fastair.fragment.DiscoverFragment.setting(DiscoverFragment.kt:62) at com.mob.lee.fastair.base.AppFragment.onViewCreated(AppFragment.kt:52) at androidx.fragment.app.Fragment.performViewCreated(Fragment.java:3019) at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:551) at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:261) at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1840) at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1764) at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1701) at androidx.fragment.app.FragmentManager$4.run(FragmentManager.java:488) at android.os.Handler.handleCallback(Handler.java:883) at android.os.Handler.dispatchMessage(Handler.java:100) at android.os.Looper.loop(Looper.java:214) at android.app.ActivityThread.main(ActivityThread.java:7386) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)

This should have nothing to do with folder. This is a code design error. I think I can update it.

Considering that it goes out after I compile it, it probably loads the file lists. How about limiting the list of visible files to 20 pieces. And then by pressing the 'load more' button

According to my design, it should support 5000 records, here this is a value I set casually that should be designed based on the current system memory share. Or "load more",just like what you said.

Good. Thank you.

It takes a little bit of time, and I can only optimize it out of work

I have absolutely everything bad, something, I chose 10_000, the minimum threshold, t.to. below it falls. after giving permission to access memory.
After switching the tab, I click on the selection of one element and that’s it. It’s worth it. Even tabs do not switch.
And yes, and I also noticed that sometimes the "select all" button is lost.  And shows "unselected all" and vice versa.
:-)


Loading state for tables

For Tables

I would also be fine with closing this as the delay should be pretty short. Maybe instead we could improve that delay

Fine for meOn 28 Feb 2023 22:41, Moritz Hedtke @.***> wrote:
I would also be fine with closing this as the delay should be pretty short. Maybe instead we could improve that delay
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


1.8.6-p420 build failed on Ubuntu 10.4 Lucid Lynx

$ rbenv install 1.8.6-p420
Downloading http://ftp.ruby-lang.org/pub/ruby/1.8/ruby-1.8.6-p420.tar.gz...
Installing ruby-1.8.6-p420...

BUILD FAILED

Inspect or clean up the working tree at /tmp/ruby-build.20111107212352.8310
Results logged to /tmp/ruby-build.20111107212352.8310.log

Last 10 log lines:
/usr/bin/gcc -g -O2  -DRUBY_EXPORT -D_GNU_SOURCE=1  -L. -L'/home/ingmar/.rbenv/versions/1.8.6-p420/lib'  -rdynamic -Wl,-export-dynamic   main.o  libruby-static.a -lrt -ldl -lcrypt -lm   -o miniruby
rbconfig.rb updated
compiling Win32API
compiling bigdecimal
make[1]: Entering directory `/tmp/ruby-build.20111107212352.8310/ruby-1.8.6-p420/ext/bigdecimal'
mkdir -p ../../.ext/i686-linux
make[1]: *** read jobs pipe: No such file or directory.  Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `/tmp/ruby-build.20111107212352.8310/ruby-1.8.6-p420/ext/bigdecimal'
make: *** [all] Error 1

It's been suggested that this is a bug in the Ruby Makefiles, but all I know is that omitting '-j 2' from the make call solves the problem for me.

Because I racked my head over this for much longer than was necessary, id like to point out to anyone that the instructions above for compiling 1.8.x work great with one downside:
You will not be able to install anything > 1.8.x using rbenv if you have installed openssl 0.9.8 from source because /usr/local will take precedence during compiling even if you remove it from your PATH before running rbenv. So be sure to install higher versions first and come back to 1.8.x after if you need these to coexist on the same machine. There might be some extra options to the compile to make rbenv not pass on /usr/loca/* in the PATH but im not sure what it is if there is one.

Hi @warmwaffles. Had this issue with Jenkins. :)

Just recently @bhardin?

Yes. Rebuilding.


Added trigger any descriptor update manipulation

The TriggerDescriptorUpdate manipulation requires specifying the descriptor that is to be updated. However, for most descriptor types, there are devices that do not support updating them. Also, to the best of my knowledge, there are no type of descriptor that exists in every Mdib and can be always be updated.
Hence, when the goal is to trigger a DescriptorManipulationReport with parts of type UPT, then the only way to find a descriptor in the Mdib, which can be updated is trial and error. However, trial and error would involve calling the TriggerDescriptorUpdate manipulation quite often, which is burdensome when the manipulation has to be performed manually.
Hence, we introduce a new manipulation TriggerAnyDescriptorUpdate which essentially does the same as TriggerDescriptorUpdate, but does not require the caller to specify the descriptor. Rather, it chooses the descriptor itself - and as long as the device has descriptos that can be updated, it should of course choose one of them.
Checklist
The following aspects have been respected by the author of this pull request, confirmed by both pull request assignee and reviewer:

Changelog update (necessity checked and entry added or not added respectively)

[x] Pull Request Assignee
[ ] Reviewer

README update (necessity checked and entry added or not added respectively)

[x] Pull Request Assignee
[ ] Reviewer

cant the manipulation "TriggerReport" with ReportType REPORT_TYPE_DESCRIPTION_MODIFICATION_REPORT be used instead?

cant the manipulation "TriggerReport" with ReportType REPORT_TYPE_DESCRIPTION_MODIFICATION_REPORT be used instead?

If "TriggerReport" with with ReportType REPORT_TYPE_DESCRIPTION_MODIFICATION_REPORT is used, you would get a DescriptionModificationReport, but no guarantee that it would contain a ReportPart with ModificationType UPT.


Introduce a usage guide for the CoC

I think the CoC requires a kind of usage guide. It is from a high-level perspective good, but missing details on the operational level. E.g. for TAGs/WGs and other projects, it isn't done by simply saying "we follow the CNCF CoC".
To highlight some issues:

Let us assume for example that within a TAG someone uses that violet emoji that looks like Kubernetes but is actually a religious sign. Someone could be offended. Rather than to motivate that person to speak up or address it at the chairs, following the CoC this would be addressed at the CoC Committee. I believe that's impractical.
A project that is not officially under the CNCF but says it follows the CNCF CoC. Escalations would still be addressed at the CoC Committee

In my opinion, it is obvious that if I have an issue and see that the CoC is violated, I first talk to the responsible person for this violation, or if I feel better about it, I address it with the chairs or leads. And if this doesn't help, then I would go to the CoC Committee. However, this is a solution outlined by each group differently, which we currently saw can lead to discussions.
It would be a solution to address this in a How To Use CoC Guide for example.
As a reference who does this well, we could highlight TAG Security - https://github.com/cncf/tag-security/blob/main/CODE-OF-CONDUCT.md
It could also be relevant for this issue: https://github.com/cncf/toc/issues/936
A final question: is it intended that on an operational level a TAG or project outlines how to handle reporting for their engagement?

Hi @mkorbi! Thanks for the feedback.
When you say a "usage guide" who would be the intended audience for this? The general community contributing to a project? Project/TAG/community leaders who want to positively influence their communities? Folks who are in moderation roles (such as those with moderation abilities on mailing lists/Slack/Zoom) who might need to respond and escalate things up to a CoCC body? CoCC members themselves as they respond to incidents?

Hey @cblecker
thinking about it, it is a little bit of both. My intention is actually more on the projects, TAGs, SIGs side, in terms of - what else I have to do to ensure the CoC and how I use it. For me, it misses simple things like:

talk to the people first if you have a problem
approach the responsible person of the group
if it is a general issue, address it in the next meeting
if nothing of this helped or you prefer to address it to someone else, then reach to the COC committee

The CoC is simple.
But it doesn't cover "all cases", it doesn't encourage in my opinion to solve issues proactively (and it doesn't have to), or explain how any workgroup/project has to handle it.

@mkorbi, thanks for your suggestion. I discussed with the working group Co-Chairs, and they've asked me to prepare an initial draft of a usage guide. I'll post it to the working group repo when it's ready, and of course would welcome your feedback and comments on it.

@joannalee333 I'm looking forward to it and I would be happy to provide my feedback if any needed

cc


Parsing 2 page PDF file taking a long time.

I am new to LlamaIndex and LlamaParse
I am using below code to parse PDF file:
def main():
load_dotenv()
nest_asyncio.apply()
LLAMA_CLOUD_API_KEY = os.getenv("LLAMA_CLOUD_API_KEY")
#setup parser
parser = LlamaParse(
    api_key=LLAMA_CLOUD_API_KEY,
    result_type="markdown",
    verbose=True,
)

documents = parser.load_data("./data/Oracle-SEC-Filing.pdf")
print(documents)

It takes more than 15 minutes and still has not finished parsing. What am I doing wrong? The pdf is a 2 page PDF attached here.
Oracle-SEC-Filing.pdf

#83 seems to be the same issue


Fix for Windows machine. Added optional parameter 'password' for secret-cli commands.

Changes proposed in this pull request.
Check List

[ ] All test passed
[ ] Added test to ensure to fix/ensure properly.

@sureshg : Please review the code.

@sureshg : Updated CLI for AuthDomain changes to support new systems like Tekton and MS. Please review.
This PR also includes changes for which is a fix for Windows machine issue.


Java ContentType detection does not work at all

Java function Files.probeContentType does not work on any image.
Java Implementation looks like this in sun.nio.fs.LinuxFileSystemProvider
@Override
    FileTypeDetector getFileTypeDetector() {
        Path userMimeTypes = Paths.get(AccessController.doPrivileged(
            new GetPropertyAction("user.home")), ".mime.types");
        Path etcMimeTypes = Paths.get("/etc/mime.types");

        return chain(new GnomeFileTypeDetector(),
                     new MimeTypesFileTypeDetector(userMimeTypes),
                     new MimeTypesFileTypeDetector(etcMimeTypes),
                     new MagicFileTypeDetector());
    }

None of those detectors seem to work. Adding custom /etc/mime.types does not seem to bring anything. libmagic seems to be required for the last detector, but even after installing libmagic1 and libmagic-mgc content type is not detected.

@kromit https://bugs.openjdk.java.net/browse/JDK-8162624
so it seems libmagic have been dropped .

also looking at https://bugs.openjdk.java.net/browse/JDK-8129633 it seems gnome vfs dependent code was removed from JDK

I have re-do your test :
root@16ec0ff97e87:/# docker run -it adoptopenjdk/openjdk8:latest bash
root@16ec0ff97e87:/# apt-get update && apt-get install vim
root@16ec0ff97e87:/# touch image.jpg
root@16ec0ff97e87:/# touch sample.pdf
root@16ec0ff97e87:/# cat Test.java
import java.nio.file.Files;
import java.nio.file.Paths;
public class Test{
public static void main(String[] args) throws Exception{
 System.out.print(Files.probeContentType(Paths.get("/sample.pdf")));
System.out.print(Files.probeContentType(Paths.get("/image.jpg")));
}
}

and I ran it :
root@16ec0ff97e87:/# java Test
application/pdfimage/jpegroot@16ec0ff97e87:/#

so at least file name based detection should work.
In my image :
java -version
openjdk version "1.8.0_222"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_222-b10)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.222-b10, mixed mode

@kromit can you check which java version are you using ?
In short :

on images I have tested types detection works (Simple one)
I do not know which libraries are needed to make it working for other providers, but in case you need it you should customize docker image for you need.

I do not think we would make any fat images targeting this particular case, especially as :

those detectors are using custom native libraries
it seems to be buggy in nature, that is why (https://bugs.openjdk.java.net/browse/JDK-8188228?focusedCommentId=14160633&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14160633) The default FileTypeDetector shipped with the JDK should be as simple as possible, ideally work consistently across platforms. It is easy to configure to use alternative implementations and that would be the way to deploy a FileTypeDetector that uses libmagic.

Temporarily I have problems with docker pulling new images, so cannot check directly the one you have used (adoptopenjdk:8-jdk-hotspot), so please let me know which java version is there. The problem in this is the only thing which concerns me.

I just checked on image you are using :
grzesiek@zenbook   ~  docker run -it adoptopenjdk:8-jdk-hotspot bash                                           18:51:59 
root@2ca5034ad3d2:/# apt-get update && apt-get install vim
root@2ca5034ad3d2:/# touch image.jpg
root@2ca5034ad3d2:/# touch sample.pdf
root@2ca5034ad3d2:/# vim Test.java
root@2ca5034ad3d2:/# javac Test.java
root@2ca5034ad3d2:/# java Test
application/pdfimage/jpeg

Closing due to inactivity.


Seems Github Actions' Artifacts ain't quite ready for us

Specifically, this comment in our README won't fly, at least not for free -
https://github.com/Vlsir/Hdl21Schematics#installing-the-schematic-editor

Hdl21 schematics use GitHub Actions for per-build CI testing. This includes building the editor VsCode Extension and the desktop app for each supported platform: MacOS, Windows, and Ubuntu Linux (note https://github.com/Vlsir/Hdl21Schematics/issues/18).
Note that GitHub Actions builds each on x86-architecture hardware. Other architectures - notably ARM64-based Macs - can instead be built from source. (And it's not hard!)
Pre-built editors are downloadable from the artifacts section of each GitHub Action run:

Turns out they do allow free "artifact uploads"... but not much. 500 MB / month, according to this page, as of this writing:
https://docs.github.com/en/billing/managing-billing-for-github-packages/about-billing-for-github-packages
Now, it seems to actually grant a bit more than that. The screenshot of uploaded artifacts in that very same passage says that the app-bundle for its commit was 673 MB - so more than the limit to even upload one:

Whatever the actual limit is - maybe the 2GB or 10GB listed elsewhere in that table - we hit it in just a few commits.

What to Do
Umbrella options:

Find another home for artifact storage
Don't try to upload so much stuff

Under option (1) I'm all ears; I know there are plenty such providers out there, but don't have any particular preference/ affinity for, or experience with, any of them. Primary criteria: (1) must be 110% easy, both to produce from CI and to download, and (2) must be free (or, more accurately, not paid by this project's authors).
Under option (2):

Maybe just upload artifacts for tagged commits/ releases
Maybe upload the VsCode Extension more often than the OS-native desktop apps

It makes sense that the former would be much smaller. The desktop apps need the whole node runtime, electron libraries, whatever OS-specific stuff they use, etc. The VsCode Extension would just contain (I expect?) our code and its dependencies; all that other stuff is part of the VsCode application itself.
That said - it's concerning that the packaged VsCode Extension for recent (maybe all) CI-side builds is only about 200 KB. When I build it locally, I get a result artifact that is more like 14MB:
$ ll hdl21-schematics-vscode-0.0.1.vsix
-rw-r--r--  1 dan  staff    14M Dec 11 13:41 hdl21-schematics-vscode-0.0.1.vsix

Perhaps that is relying on more "stuff" from the build environment than we realized.

For Now
Gotta at least get this out of the README as a recommended method of installation.

05a0868 has the easy part, temporarily removing the GH Artifacts from the README documentation.

hmm, yeah, figuring out why the "app" is >600MB will be important.  Maybe have it stored somewhere else instead.  I believe Matthias has Klayout set up to upload to Dropbox.
For some of my projects, I've had them set up to release toGitHub Releases for all tagged releases.  GitHub actions can include the generated artifacts as part of a draft release.

You could also reduce the lifetime of artifacts.

Seconding upload to VS Code Marketplace, this is a very convenient method.

Totally agree!


fix(batch): Improve batch verifier async, correctness, and performance

Motivation
Zebra's tower-batch has some async performance issues, and contains some buggy and risky code.
We should replace it with more robust code.
Close #4738
Close #4740
Close #4729 (by using a channel that never lags)
Close #4728 (by removing the log entirely)
API Reference
tokio::spawn_blocking():
https://docs.rs/tokio/latest/tokio/task/fn.spawn_blocking.html
Solution
Improve tower-batch async fairness:

Prefer the batch timer if there are also new batch requests
Allow other tasks to run after each batch
Label each batch worker with the verifier's type in tokio-console

Improve error handling in tower-batch:

Check batch worker tasks for panics and task termination
Rename Handle to ErrorHandle, and fix up some docs

Improve channel limit handling in tower-batch:

Use a new channel for each batch
Use tokio's PollSemaphore instead of an outdated Semaphore impl

Improve channel limit handling in zebra-consensus:

Replace batch verifier broadcast channels with watch channels

Run all verifier cryptography on blocking CPU-bound threads

Run batch verification on blocking tokio threads
Run fallback verification on blocking tokio threads
Make flush and drop behaviour consistent for all verifiers
Switch batch verifier tests to the multi-threaded runtime

Related fixes:

Fix a bug in the v5_with_sapling_spends test (but it's still missing NU5 test vectors)

Review
This is blocking halo2 batch verification, so it would be good to get it in soon.
This might fix some bugs we're seeing during syncing.
Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] CI passes

I'm running a full sync here, to see if these fixes help:
https://github.com/ZcashFoundation/zebra/actions/runs/2619584632

I'm running checkpoint and tip syncs here, to check if this PR fixes some sync bugs we're seeing on main:
https://github.com/ZcashFoundation/zebra/actions/runs/2646938611

And here's a tip and checkpoint sync without larger batch queues (they might be causing some issues):
https://github.com/ZcashFoundation/zebra/actions/runs/2646961635

Here's a tip and checkpoint sync run, to see if this PR fixes the sync hangs we're seeing on main:
(I removed some changes from this PR that were buggy.)
https://github.com/ZcashFoundation/zebra/actions/runs/2646994181

I admin-merged this separately from PR #4776, just in case we need to debug them as separate commits.


Mat/Par: Add users to KeyCloak Security group for PROD Launch

User Story
“As a UX test facilitator I want to add the following users to the Mat/Par KeyCloak group created in ticket #1471 so I can get these HRSC service reps into the 'hidden' Mat/Par PROD form before the workshop on January 4th 2024.”
Tasks
Please add the following people to the security group
developed in ticket #1471
https://bcgov.sharepoint.com/:x:/r/teams/03991/Shared Documents/Maternity and Parental Leave/HRSC Reps to add to MatPar KC group.xlsx?d=w4cdcef96f3b74806b9aac9730f2cee58&csf=1&web=1&e=cSeVCh
Acceptance Criteria
the attached 3 users can access the Mat/Par form in PROD before we release to all employees

@Stella-Archer
I have added all 3 users from the attached excel sheet in mat/pat form group on production.

Ronda has confirmed the new user can access the Mat/Par form in PROD thanks @bhumin-fw
PO approved and closing this ticket


[Barreleye VERSION_ID="v1.99.0-123-gfc7788a-dirty"] obmc-console-client: obmc console client failed to start

Explanation of the issue:
obmc-console-client: Can't connect to console server: Connection refused

Start manually : login to BMC and run obmc-console-client

Start connect using SOL port :    ssh -p 2200<EMAIL_ADDRESS>

Expected Behavior:
Expected to get console logs when powered off and on the BMC system
Actual Behavior:
obmc-console-client command execution failed
obmc-console-client: Can't connect to console server: Connection refused
Recreation Steps:

Log in to BMC and execute "obmc-console-client"

power off and on BMC System and observe  the logs generated from "obmc-console-client"

Specifications:
BMC Version
root@barreleye:~# cat /etc/os-release
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="v1.99.0-123"
VERSION_ID="v1.99.0-123-gfc7788a-dirty"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) v1.99.0-123"
BUILD_ID="v1.99.0"
System Type: Barreleye
Operating System Details:
Linux beye5 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

@anoo1 @jk-ozlabs  anything you are aware of SOL failure recently ?

There is already opened defect one for this... so this is pretty known issue now.. closing here
Refer
https://github.com/openbmc/openbmc/issues/585
https://github.com/openbmc/obmc-console/issues/7


add Firebase?

They share a lot of dependencies,
Currently, we are using both Firebase and GoogleMLKit. it would be difficult without Firebase support here
Do you have any ideas?

@aelam Of course considered about Firebase. See https://github.com/d-date/google-mlkit-swiftpm/blob/main/Example/Package/Package.swift

@aelam As you can see my Package.swift, common dependencies are come from SwiftPM.
https://github.com/d-date/google-mlkit-swiftpm/blob/main/Package.swift
My article might be help you (Sorry about written in Japanese)
https://zenn.dev/d_date/articles/cd4ce3b2b5c29d

thank you! it looks great
thanks for your hard work
BTW maybe change the package name to GoogleMLKit should be OK? without swifpm suffix

@aelam It's OK but have no effect for everywhere. If you want, it's welcome to PR.


WIP: Update interplanetary examples

Before my talk at PyConSK I made some improvements to the examples, and anticipated the use of Astropy ephemerides functions. Some more work is still needed - I'm leaving this open for some days, and won't merge until #131 is fixed and a cleaner API is created.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #155   +/-   ##
=======================================
  Coverage   81.07%   81.07%
=======================================
  Files          24       24
  Lines         930      930
  Branches       72       72
=======================================
  Hits          754      754
  Misses        155      155
  Partials       21       21

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 ad8ced3...5349830. Read the comment docs.


Test sandwiched waypoint

Cleanup nesting
e2e tests: use inpod mode more
Assert access logs
wip
better logs
WIP admin tasks
wip
fix
Revert "WIP admin tasks"
fix
re-enable
cleanup
more cleanup, need to undo the prefix
Revert "Cleanup nesting"
Add more tests
Malicious calls test
mismatch test
policy test
vip test
cleanups
fmt
Fix and test sandwiched waypoint

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

In response to a cherrypick label: #973 failed to apply on top of branch "release-1.22":
Applying: Test sandwich waypoints
Using index info to reconstruct a base tree...
M	src/proxy/outbound.rs
M	src/test_helpers/linux.rs
M	src/test_helpers/tcp.rs
M	tests/namespaced.rs
Falling back to patching base and 3-way merge...
Auto-merging tests/namespaced.rs
CONFLICT (content): Merge conflict in tests/namespaced.rs
Auto-merging src/test_helpers/tcp.rs
Auto-merging src/test_helpers/linux.rs
CONFLICT (content): Merge conflict in src/test_helpers/linux.rs
Auto-merging src/proxy/outbound.rs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Test sandwich waypoints
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #976

/cherry-pick release-1.22

@bleggett: new pull request created: #984

In response to this:

/cherry-pick release-1.22

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Magnet power use issues.

Forge:

Forge<IP_ADDRESS>8

Mods loaded:

EnderIO-1.7.10-<IP_ADDRESS>9_beta
EnderCore-1.7.10-<IP_ADDRESS>_alpha
Baubles-1.7.10-<IP_ADDRESS>
CodeChickenLib-1.7.10-<IP_ADDRESS>
CodeChickenCore-1.7.10-<IP_ADDRESS>
NotEnoughItems-1.7.10-<IP_ADDRESS>

EnderIO Configuration:

B:magnetAllowInBaublesSlot=true
B:magnetAllowDeactivatedInBaublesSlot=true

Game type:

SSP (not tested on a remote server)

The issues:

An inactive magnet will work and use power when put into a baubles slot.

An active magnet in the hotbar, or in the normal inventory when B:magnetAllowInMainInventory=true, uses twice the power that it should. 2x whatever I:magnetPowerUsePerTickRF is set to. This is not contingent on B:magnetAllowInBaublesSlot=true and B:magnetAllowDeactivatedInBaublesSlot=true

I'm reporting these issues together because they seem like they could be related to the same code.

This has been fixed in build 400 of EnderIO now available on the CI server.


Account is broken after using API

Hi, I made a bot which never sends any message. (just receiving)
After some works, I noticed that my account is broken.
My messages are not delivered to opponents at all even there's no error.
This is weird because I sent messages from official LINE clients (both desktop and mobile).
Everything except sending works fine.
Is this a ban?
Does anybody experienced same issue?

If this is a ban, What's the best delay between fetchOp calls

I have faced this problem too.
I think Naver uses some technique to detect bots's behavior even they don't send out any messages.

@moonoiza yes, its ban. Or you can just change that header

@lintangtimur Could you please give me more info which headers should be changed ? I have tried changing some auth headers like version , device name before but it didn't work.

yep when you connect with old config header u get ban so u can read but if you send message, only you will see it and u cant join new channel either

In my case, I requested deprecated APIs. and it perfectly works even if deprecated.
It's pretty dangerous to create a public app with these kinds of unofficial line APIs. LINE keep changing their protocols, but unofficial API doesn't

In my case, I requested deprecated APIs. and it perfectly works even if deprecated.
It's pretty dangerous to create a public app with these kinds of unofficial line APIs. LINE keep changing their protocols, but unofficial API doesn't

it might be dangerous but you have acces to more stuff than the official bot :P lol


Fix noarch build error

make -f Makefile.unx arch=noarch test fail .
It report "function undefine " error . This is a fix .
And add test case to guarantee it .

@gbtucker , please review

So we never had a noarch version because we don't have base functions for all units.  It's not so much that it didn't work.  Are you trying to enable something in particular?

So we never had a noarch version because we don't have base functions for all units. It's not so much that it didn't work. Are you trying to enable something in particular?
I am try to do some performance comparison. Assembly version vs C version . So I build it with noarch version.

For non-x86 architecture , the case looks like noarch . I think it should be useful to make sure ISA-L_crypto can work on non-x86 architecture.


Added experimental tvOS and watchOS support

@muxi I guess it was because watch apps must be coupled with iOS apps so together they take longer. Also could you help rerun the sanity checks?

I removed the example builds for tv and watch with frameworks, so now Basic Tests ObjC Examples  takes about 65 minutes.

@muxi What about the remote Podspec for !ProtoCompiler and Boring-SSL? Do we update those to include watchos at some point? Currently we are modifying locally and tell the podfile to use the local copy.

Are you talking about src/objective-c/Podfile? BoringSSL-GRPC has to be remote I think because it is not in the BoringSSL directory. ProtoCompiler is also downloading from online, not local. So these two are ok to be remote podspecs.

#19819, #19669

Are you talking about src/objective-c/Podfile? BoringSSL-GRPC has to be remote I think because it is not in the BoringSSL directory. ProtoCompiler is also downloading from online, not local. So these two are ok to be remote podspecs.

I mean adding watchos.deployment_target to the remote podspecs for the next release.


Put some limits for Receipts

Limit the number of characters allowed for description
Limit the number of characters allowed for store name?
Limit the number of Receipts put to a one page of invoice

Solved in commit 4e139cb


Hook Chaining

Summary
Hook Chaining is a proposed feature for Hooks which allows:

Multiple Hooks to execute on a single account.
Foreign Hooks (from different accounts) to run with the account owner's permission before or after or instead of the account's own Hook.

Motivation
To help prevent users re-uploading the same Hook over and over at great expense to themselves and the ledger.
To allow complex multi-hook logic to be processed on the same account.
Solution
As above
Paths Not Taken
Originally we had intended to require users to recompile a multiude of hooks into a single hook to be installed on their account. However this needlessly multiplies complexity and storage requirements and, ultimately, cost.

Implemented in hooks v2


Documenation and Tooling: Constraining Architectures

Currently figuring out https://github.com/haproxy/haproxy/issues/1035
It could be an issue with the used ARM-Architecture but not for sure. @wtarreau saw the difference between the host and container architecture.
Reading the docs here https://lxd.readthedocs.io/en/latest/architectures/ it doesn't seem to be an issue but apparently I do not know.
As it would have be a no-brainer to use the arm64 version instead of the armhf version to rule out this bug possibility, it would have been great if LXD could complain during "lxc launch". And also a hint in the docs can be useful if different architectures are really an issue.
What do you think?

So are you saying that lxc launch ubuntu:20.04 got you an armhf container instead of arm64?

So are you saying that lxc launch ubuntu:20.04 got you an armhf container instead of arm64?

Running armhf containers on arm64 host can indeed be a bit funny because of how the kernel reports this as armv8l.
The Ubuntu kernel has a custom patch which lets you set compat_uts_machine=armv7l on the kernel command line to override that name to armv7l, avoiding such issues. But that's very much an Ubuntu specific hack so something better suited for distro documentation than for LXD's.

Running armhf containers on arm64 host can indeed be a bit funny because of how the kernel reports this as armv8l.
The Ubuntu kernel has a custom patch which lets you set compat_uts_machine=armv7l on the kernel command line to override that name to armv7l, avoiding such issues. But that's very much an Ubuntu specific hack so something better suited for distro documentation than for LXD's.

To be honest, not quite. I used
lxc launch ubuntu:20.04/armhf

So, now I realize that it might just work without the architecture spec but I still think it might be good idea to warn users of that they might try something "funny" here :-D
Don't remember where I copied it from but  back then it seems like as if the /armhf should be there.

To be honest, not quite. I used
lxc launch ubuntu:20.04/armhf

So, now I realize that it might just work without the architecture spec but I still think it might be good idea to warn users of that they might try something "funny" here :-D
Don't remember where I copied it from but  back then it seems like as if the /armhf should be there.

@stgraber Just to understand this bit here correctly because I am not familiar with it: you are saying that haproxy should be able to handle armhf regardless of the underlying hardware, right?

@stgraber Just to understand this bit here correctly because I am not familiar with it: you are saying that haproxy should be able to handle armhf regardless of the underlying hardware, right?

Yeah, if all that makes it crash is seeing armv8l from the kernel rather than armv7l, then that definitely seems like a bug in the application.
If that's not the issue, then the problem could be that haproxy was built with some hardware extensions enabled which somehow aren't present on the 32bit API of the raspberry pi. This certainly can happen and isn't limited to Arm either. You can get into the same kind of problem on Intel by building with a compiler that uses the most recent CPU extensions and then attempt to run the binary on an older CPU. Everything will behave up until the time where the affected instruction is called, at which point the program will crash.

Yeah, if all that makes it crash is seeing armv8l from the kernel rather than armv7l, then that definitely seems like a bug in the application.
If that's not the issue, then the problem could be that haproxy was built with some hardware extensions enabled which somehow aren't present on the 32bit API of the raspberry pi. This certainly can happen and isn't limited to Arm either. You can get into the same kind of problem on Intel by building with a compiler that uses the most recent CPU extensions and then attempt to run the binary on an older CPU. Everything will behave up until the time where the affected instruction is called, at which point the program will crash.

@stgraber indeed, it took us some time to understand that it was a 32-bit binary running on a 64-bit host, and I agree with you that normally it should work flawlessly. What puzzles me is that the user receives a SIGBUS making me think about something like an alignment issue, while this is the regular binary from the package used by default on native ARM machines (and I could double-check that it does work fine on armv8 with the compat libs). Initially I thought he was building it himself and that gcc there could have advertised some __ARM_foo features that wouldn't work fine, but given that it's the standard armhf package, I'm a bit puzzled for now.
I'm wondering if it's possible that something differs there. The user does nothing fancy and (except for openssl which doesn't seem to be directly related) the single request he's doing doesn't pass through any fancy lib. Strangely he cannot get any core, nor get gdb to work from this environment, and doesn't even have any kernel message announcing the death cause, so that obviously doesn't help.
I know we do have some optimizations for unaligned data that are enabled when the  platform supports them (and this one does advertise them). For now we don't know more. We're still investigating. I'm fine with passing you more info once we figure the cause. Conversely any debugging hint from your about this environment is welcome :-)  I'm trying to setup one for the first time on a machine here, I'll see if I manage to do it right.

@stgraber indeed, it took us some time to understand that it was a 32-bit binary running on a 64-bit host, and I agree with you that normally it should work flawlessly. What puzzles me is that the user receives a SIGBUS making me think about something like an alignment issue, while this is the regular binary from the package used by default on native ARM machines (and I could double-check that it does work fine on armv8 with the compat libs). Initially I thought he was building it himself and that gcc there could have advertised some __ARM_foo features that wouldn't work fine, but given that it's the standard armhf package, I'm a bit puzzled for now.
I'm wondering if it's possible that something differs there. The user does nothing fancy and (except for openssl which doesn't seem to be directly related) the single request he's doing doesn't pass through any fancy lib. Strangely he cannot get any core, nor get gdb to work from this environment, and doesn't even have any kernel message announcing the death cause, so that obviously doesn't help.
I know we do have some optimizations for unaligned data that are enabled when the  platform supports them (and this one does advertise them). For now we don't know more. We're still investigating. I'm fine with passing you more info once we figure the cause. Conversely any debugging hint from your about this environment is welcome :-)  I'm trying to setup one for the first time on a machine here, I'll see if I manage to do it right.

@wtarreau @srkunze do you have a pretty short reproducer for the issue?
I have access to rpi4 and a variety of other arm64 platforms so would be interesting if I could reproduce it on rpi4 and then see if the same happens on APM/Ampere silicon. I'm always a bit wary of the rpi because of odd architectural limitation in the past, though I must say that the rpi4 seems like a pretty solid aarch64 platform (minus it still using u-boot...)

@wtarreau @srkunze do you have a pretty short reproducer for the issue?
I have access to rpi4 and a variety of other arm64 platforms so would be interesting if I could reproduce it on rpi4 and then see if the same happens on APM/Ampere silicon. I'm always a bit wary of the rpi because of odd architectural limitation in the past, though I must say that the rpi4 seems like a pretty solid aarch64 platform (minus it still using u-boot...)

So the first visible thing in his image is that just issuing gdb --args /bin/id then run loops forever inside ld-linux.so. So I conclude that at this point there's something fishy in this setup, even though I have no idea whether it's related to the combination of archs or just a software bug somewhere. I'll let @srkunze provide all the details to avoid saying stupidities.
And I agree with you that rpi always looks suspicious :-) With this said, the rpi4 uses regular A72 cores and usually works without surprises (at least with a correct power supply and micro-SD).

So the first visible thing in his image is that just issuing gdb --args /bin/id then run loops forever inside ld-linux.so. So I conclude that at this point there's something fishy in this setup, even though I have no idea whether it's related to the combination of archs or just a software bug somewhere. I'll let @srkunze provide all the details to avoid saying stupidities.
And I agree with you that rpi always looks suspicious :-) With this said, the rpi4 uses regular A72 cores and usually works without surprises (at least with a correct power supply and micro-SD).

Here we go:
- buy a raspi
- install ubuntu 20.04 arm64

root@raspi:~# apt install lxd
root@raspi:~# lxc launch ubuntu:20.04/armhf haproxy

root@raspi:~# lxc shell haproxy
root@haproxy:~# apt install gdb

Checks for the setup
root@raspi:~# uname -a
Linux raspi 5.4.0-1026-raspi #29-Ubuntu SMP PREEMPT Mon Dec 14 17:01:16 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

root@raspi:~# lxc shell haproxy
root@haproxy:~# uname -a
Linux haproxy 5.4.0-1026-raspi #29-Ubuntu SMP PREEMPT Mon Dec 14 17:01:16 UTC 2020 armv8l armv8l armv8l GNU/Linux

Here we go:
- buy a raspi
- install ubuntu 20.04 arm64

root@raspi:~# apt install lxd
root@raspi:~# lxc launch ubuntu:20.04/armhf haproxy

root@raspi:~# lxc shell haproxy
root@haproxy:~# apt install gdb

Checks for the setup
root@raspi:~# uname -a
Linux raspi 5.4.0-1026-raspi #29-Ubuntu SMP PREEMPT Mon Dec 14 17:01:16 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

root@raspi:~# lxc shell haproxy
root@haproxy:~# uname -a
Linux haproxy 5.4.0-1026-raspi #29-Ubuntu SMP PREEMPT Mon Dec 14 17:01:16 UTC 2020 armv8l armv8l armv8l GNU/Linux

@stgraber I finally nailed the crash issue down. It's interesting. Some code we embed (xxhash) is built to support unaligned accesses when __ARM_FEATURE_UNALIGNED is set. But on armv5-7, 64-bit unaligned accesses with the LDRD instruction are not permitted, however they are emulated by the kernel.
But the arm64 kernels do not implement the alignment emulation since armv8 processors surpport all types of unaligned accesses. However when they execute code in compatibility mode, they still cause an alignment exception, without any code in the kernel to catch them. As such it could be argued that the real difference is the kernel, and that there's no 100% guarantee that a 32-bit program will run fine on a 64-bit kernel.
I've proposed a patch to xxhash to use a separate condition for 64-bit unaligned accesses.
Thus there's no issue with LXC but next time you get a similar report you might have one more clue where to look :-)

@stgraber I finally nailed the crash issue down. It's interesting. Some code we embed (xxhash) is built to support unaligned accesses when __ARM_FEATURE_UNALIGNED is set. But on armv5-7, 64-bit unaligned accesses with the LDRD instruction are not permitted, however they are emulated by the kernel.
But the arm64 kernels do not implement the alignment emulation since armv8 processors surpport all types of unaligned accesses. However when they execute code in compatibility mode, they still cause an alignment exception, without any code in the kernel to catch them. As such it could be argued that the real difference is the kernel, and that there's no 100% guarantee that a 32-bit program will run fine on a 64-bit kernel.
I've proposed a patch to xxhash to use a separate condition for 64-bit unaligned accesses.
Thus there's no issue with LXC but next time you get a similar report you might have one more clue where to look :-)

Thanks for getting to the bottom of this!
I wonder if it would be worth a kernel patch to catch such unaligned access from the 32bit personality and emulate the normal Linux behavior for 32bit arm. That would take care of such issues and quite possibly of some other weird issues folks have been running into :)

Thanks for getting to the bottom of this!
I wonder if it would be worth a kernel patch to catch such unaligned access from the 32bit personality and emulate the normal Linux behavior for 32bit arm. That would take care of such issues and quite possibly of some other weird issues folks have been running into :)

Yes I think it would be worth doing, but I predict that it could be a bit controversial to add support for alignment traps on a platform that theoriticaly always supports unaligned accesses. Also I remember there was not that much love for this feature for ARMv5 as there, by default, unaligned accesses would simply return crap instead of being emulated. You had to manually enable alignment traps at boot.

Yes I think it would be worth doing, but I predict that it could be a bit controversial to add support for alignment traps on a platform that theoriticaly always supports unaligned accesses. Also I remember there was not that much love for this feature for ARMv5 as there, by default, unaligned accesses would simply return crap instead of being emulated. You had to manually enable alignment traps at boot.

Also big kudos from my side! +1
Just one noob question: is this something that will sort itself out in time? If not, I would also favor a kernel solution here.
From a user's perspective, it is massively frustrating (I can tell you that) and I was lucky that @wtarreau was so patient with me to get me to that point where we found out that the gdb is broken on armhf-on-arm64 systems. I usually trust these tools and do not question their functional integrity.

Also big kudos from my side! +1
Just one noob question: is this something that will sort itself out in time? If not, I would also favor a kernel solution here.
From a user's perspective, it is massively frustrating (I can tell you that) and I was lucky that @wtarreau was so patient with me to get me to that point where we found out that the gdb is broken on armhf-on-arm64 systems. I usually trust these tools and do not question their functional integrity.

The unaligned access issue is almost addressed. I'm going to merge the patch into haproxy's copy of xxhash and passed it to Yann already for xxhash. It's uncertain whether latest versions need it or not, as this optimization is sensitive to the code structure and compiler version (I couldn't reproduce it on more recent versions nor with an older compiler).
The gdb issue is another one and could take more time as it needs to be studied by whoever knows this kernel area best.
Regarding your trust of tools, the important rule is never to trust anything, starting with your own code. Bugs are everywhere and everything not completely observable is suspicious. You can only reason in probabilities to help narrow an issue faster, but no observed proof means no certainty nor direct conclusion.

The unaligned access issue is almost addressed. I'm going to merge the patch into haproxy's copy of xxhash and passed it to Yann already for xxhash. It's uncertain whether latest versions need it or not, as this optimization is sensitive to the code structure and compiler version (I couldn't reproduce it on more recent versions nor with an older compiler).
The gdb issue is another one and could take more time as it needs to be studied by whoever knows this kernel area best.
Regarding your trust of tools, the important rule is never to trust anything, starting with your own code. Bugs are everywhere and everything not completely observable is suspicious. You can only reason in probabilities to help narrow an issue faster, but no observed proof means no certainty nor direct conclusion.

The gdb issue is another one

I researched the gdb bug database and found: https://sourceware.org/bugzilla/show_bug.cgi?id=25215
Do you think it's the same?

It's possibly the same, yes.


Add Splunk logo

Added @xmulligan who handles the various checks on adding logos :)

This message came from Splunk's legal team when I got permission for INI to include their logo. I don't think the brand guidelines matter here (Exhibit B), but do let me know if you need that. Thanks, Ed & Bill!

Splunk Inc. grants Inclusive Naming Initiative (the "Company") permission to use the Splunk trademarks and logo in the attached Exhibit A. The permission is only for use by the Company on their website listing Splunk as a participating organization.
The Splunk trademarks and logo may only be used for the above-identified purpose in line with our brand guidelines (Exhibit B) and shall not be used in any manner without further prior approval. Splunk may revoke the permission at any time, in its sole discretion, if the use is not in compliance with the usage requirements of this authorization.
Splunk is the exclusive owner of all right, title, and interest in the Splunk name, trademarks, logos, trade dress, software and user interfaces, and the Company’s use shall inure to Splunk's benefit.

Thanks @wordsmeanstuff ! If you can add a contact email, I'm happy to have it merged

Hey Bill, awesome! I'll serve as the point of contact for now between INI and legal/PR, so please use<EMAIL_ADDRESS>

I'm gonna merge this now and let's talk about blog posts now that KubeCon is over!


Move Subscribe to extern component

Hi,
happy hacktoberfest, this is my take on issue #40. I moved the Subscribe Section to  a seperate component. Since it uses in-component-styles may some css classes are doubled, so another issue can be to solve this. I have not much experience with in-component-styles because most projects I still stick to the "old" way with seperate files (and because the use of sass/less).
I also fixed the error property on the semantic ui form. It takes a bool to show the error Message.
let me know if something is missing or should be corrected, I'll happy to do that.
I hat looked into the issues linked in #40, but one is already closed and the other for styling suggestions, well I quite like like it looks now and I'm sadly not a design geek and have no better idea of styling. May the footer background color should match more the way the top/header look like, that purple tone. :)
regards,
Sebastian

@HerrVoennchen thank you for the work, we are reviewing your changes

@HerrVoennchen Thanks for your contribution.


App is crashing if link is resolved when flutter engine is not attached

Stacktrace
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'void io.flutter.plugin.common.MethodChannel.invokeMethod(java.lang.String, java.lang.Object)' on a null object reference
       at com.singular.flutter_sdk.SingularSDK$1$1.run(SingularSDK.java:240)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:233)
       at android.app.ActivityThread.main(ActivityThread.java:8068)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:631)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:978)

Observered in sdk version - 1.0.8
Potential Cause
A Runnable is being posted onto the UIThreadHandler when link is resolved. This could be unnecessary if the SingularLinkHandler.onResolved(linkParams) is invoked in the main thread and could be the root cause.
uiThreadHandler.post(new Runnable() {
  @Override
  public void run() {
    channel.invokeMethod("singularLinksHandlerName",linkParams); // NULL POINTER HERE!!! Due to NULL `channel`
  }
});

Potential Fix
If SingularLinkHandler.onResolved(linkParams) is expected to be only called in main thread and only after the flutter engine is attached, then we can just remove the uiThreadHandler.post() and directly invoke the method on the channel
If the link can be resolved from a background thread,
Then we'll need to do two things:

Check if the channel is not null before invoking channel.invokeMethod("singularLinksHandlerName",linkParams)
If the channel is null, then queue this operation up and wait until the flutter engine is attached to invoke pending operations

thx @okmanideep for raising this issue. we will address it in our upcoming release.

No longer happening in the new SDK version 1.0.12.
Thank you 🙏


Support extracting/sending correlation IDs from/to Kinesis analytics

This is a Feature Proposal
Description
Right now the correlation IDs middleware doesn't recognize Kinesis analytics events as it's structured slightly differently to Kinesis.
We should add support for Kinesis analytics as both incoming as well as outgoing event source.

cc @tomlloyd-dazn


Why session Load failed?

I'm trying the session load,save in androguard.
I read the doc and just copy and paste the session part with few modifications.
However I got

It is sure that in input apk file and the ag file is exists and not empty file. But maybe something else wrong...

Currently the session is not working as expected due to different reasons.
The load functionality has been removed and the entire "session approach" needs to be implemented from scratch, while setting clear expectations.


Error on rate limit reached

On line 48 of wrapper.py, the variable data gets set to {'error': 'rate limiter reached'} if you exceed the rate limit. Line 49 can't deal with that and raises "KeyError: 'data'". This was quite uninformative when I didn't know I reached my rate limit yet, and I had to do some debugging to see what happened.

Fixed in version 4.5


Added CollectionView.safeScrollToItem(at:, at scrollPosition: , animated:)

Added a method to safely scroll to some untrusted IndexPath in a CollectionView. This method has similar behavior to its TableView equivalent, the only difference is that it checks the index path for negative items and sections as well. PR updating the Table View method incoming soon.
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 5.0.
[x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[x] I have added a changelog entry describing my changes.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 580 tests, with 0 failures (0 unexpected) in 10.625 (12.626) seconds

:book:
tvOS: Executed 555 tests, with 0 failures (0 unexpected) in 2.040 (2.522) seconds

:book:
macOS: Executed 418 tests, with 0 failures (0 unexpected) in 0.928 (1.221) seconds

  Generated by :no_entry_sign: Danger


Halt Spark executor when encountering unrecoverable CUDA errors

Signed-off-by: sperlingxx<EMAIL_ADDRESS>Closes #5029
Following #5118, this PR detects unrecoverable (fatal) CUDA errors through the cuDF utility, which applys a more comprehensive way to determine whether a CUDA error is fatal or not.

build

build

build

build

Please retarget for 22.08

Hi @tgravescs, I retargeted to branch-22.08 and I removed the message scraping codes for double-check, since cuDF can fully take care of the fatal error detection with https://github.com/rapidsai/cudf/pull/10884.

build


WIP: Migrate secrets manager integration to aws sdkv2

:loudspeaker: Type of change

[ ] Bugfix
[ ] New feature
[X] Enhancement
[ ] Refactoring

:scroll: Description
This PR will migrate Secrets Manger to use AWS SDK V2 - #58. Also it will push changes from #54.
:bulb: Motivation and Context
This change is required for the Secrets manager integration to use AWS SDK V2
The related issues are #56 and #58.
:green_heart: How did you test it?
Added tests for migrated classes.
:pencil: Checklist

[ ] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated reference documentation to reflect the change
[ ] All tests passing
[X] No breaking changes

:crystal_ball: Next steps
Need guidance from @maciejwalkowiak , @MatejNedic to proceed forward with migrating the spring-cloud-starter-aws-secrets-manager-config module.

@arunkpatra please rebase against 3.0.x as credentials and region is already merged.

Closing this PR. Will submit a fresh PR. Thanks @maciejwalkowiak for the assistance on this one.


Full screen swipe back

This pull request adds option to make it possible to start swipe back gesture from within the whole activity via setFullScreenSwipeEnabled(boolean) function.
Swiping left and right works correctly but I was unable to make it work with swipe bottom or top as these weren't working even without my changes.

Any luck for top and bottom full swipe edges ??

This library doesn't seem to be maintained anymore but I'll look into fixing that in my fork later.

@Tunous
i would be glad if you can fix it !!!
Thank you

I got the initial fix ready here: https://github.com/Tunous/SwipeBackLayout/pull/1.
But it still needs some work as there are issues with status and navigation bar.


Localization

First of all, that's an awesome project, I really liked it.
What you think about internacionalization? Would you like to receive a pull request enabling this feature? If you agree with this, I'm able to help and develop.

The capabilities for localization are already there.
I think the best way to go about translating is to have a .js file for each language in the src folder, where we'd overwrite flatpickr.init.prototype.l10n.
I definitely need help translating flatpickr into languages other than English and Russian.
Feel free to make a pull request with flatpickr.l10n.your-native-language.js

Hello!
This a great project, congratulations! I have only one doubt about it.
I'm trying to change the language of the calendar just reading the documentation, but doesn't work in my environment. I'm not using webpack as well. It is possible the usage with only my simple gulpfile.js?
Best regards!


Make whois server changeable

I implemented this feature however, the output format is different depending on the server, so parse errors often occur.