Fixing missing and/or inconsistent quoting in knife search documentation

Description
Fixing missing and/or inconsistent quoting in knife search documentation
Issues Resolved
No pre-existing issue(s)
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Thought DCO sign off wasn't needed for Obvious Fixes but will go through that


Notebook: Trust an entire directory of Notebooks

Issue Type: Bug
When working with many Notebooks in a single directory, it is cumbersome to keep clicking on the "Not Trusted" button to trust the Notebook. It would make the experience so much better if the user can trust the entire directory where the Notebooks live. This should be configurable at the user and workspace level.
Azure Data Studio version: azuredatastudio 1.14.1 (f9b968c1ae514a0d1210788629e1c69125857279, 2019-12-24T02:42:26.303Z)
OS version: Windows_NT x64 10.0.18363

We're still commenting on the PR, so moving to April release.


How to improve performance?

I have a 33MB corpus and I ran this command:
python3 train.py --data_file=data/creepypasta.txt --hidden_size=512 --num_layers=2 --num_unrollings=64 --dropout=0.5 --verbose=1

It outputs an additional +0.4% progress every 110 seconds or so, which indicates that it'll take more than a week to complete 25 epochs. How can I speed this up?

Hi, there are several things you could do to accelerate training: reduce the hidden size; reduce the number of layers; reduce the num_unrollings; reduce the dropout.
In general, I would suggest trying something simple first. For example, maybe
python3 train.py --data_file=data/creepypasta.txt --hidden_size=128 --num_layers=1 --num_unrollings=32 --dropout=0.0 --verbose=1
and then increase the complexity and regularization if the result is not good enough.


Fix 1.28 Prod Image Tags

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve


fix instance of new ComputationGraph

starting to get familiar with the pnp code, we got rid of this constructor

LGTM


User/Group Management Without SCIM

Leela & AWS Team,
While attempting to roll out AWS SSO, my organization is encountering a number of AWS SSO challenges that exist outside the current feature-set boundary of SSO Extensions for Enterprise.
The original Problem 2 from this issue has been moved to #46
This issue is about User/Group Management Without SCIM.
Assumptions:
Note: Not all of these assumptions must be true for a potential solution to have value.

Using External IdP (e.g. Okta) with AWS SSO.
The external IdP does not support SCIM, or SCIM is gated behind a license that your organization does not have.
Entering users and groups by hand in the AWS Management Console is too much administrative overhead, due to the sheer number of users/groups.
Okta's backend is an on-prem Active Directory (i.e., AD is the system of record for user accounts).
AWS has a Managed AD instance that receives a one-way user/group sync from on-prem AD using Microsoft Identity Manager.

Problem:

Without another solution, we would have to either (1) purchase a license supporting SCIM on the External IdP side, or (2) manually duplicate all user CRUD operations (new user, delete user, update user, change user group assignments) both on the AD side, and on the AWS SSO side.
SSO is supposed to reduce maintenance burden, or at the very worst, keep it the same - not increase it!
Purchasing can be a challenging prospect for some organizations, even if the money is technically available. Okta may not even be the only IdP that requires additional purchases for SCIM.

Ad-Hoc Automation Solution:

Developing a Python script (soon to be a cron schedule-driven Lambda)
Script reads users from Managed AD, extracting email, name fields, username, and memberOf (the multi-valued list of every group the user is a member of) and stores the user data in an in-memory data structure.
Script issues REST calls to the AWS SSO SCIM endpoint, at a minimum creating non-existent users/groups, but (ideally) also updating out of date information.

Example: User legally changes their name; joins or leaves AD groups.
Most common calls are GET and POST to /scim/v2/Users, /scim/v2/Groups - sometimes with filters. Code is fairly formulaic and intuitive if one understands the AWS SSO SCIM limitations as documented.

Possible Variations:

Getting the user list from a different source, e.g. from Okta API natively, or some other IdP or database.
Perhaps some organizations might only want to implement a subset of the users in AD, not all. The import process should provide a hook to allow arbitrary code to run and accept/reject a potential user import, or even include whitelist/blacklist functionality.

What Could SSO Extensions Do:

Implement some kind of extensible variation of my ad-hoc automation solution idea.
Take care of the AWS SSO SCIM operations (CRUD) and only require the user to provide a "data source" (where are you getting the users from?). Could bundle a few common data sources.
Leverage your excellent CodePipeline infrastructure to auto maintain the new functionalities.
Optionally support configuring the solution at runtime in S3 or via API.

Are these possible future directions for SSO Extensions? (Would you accept pull requests if I ever figure out the internals of SSO-Ex enough to directly implement this using SSO-Ex's existing infrastructure? Would you consider / are you already working on this yourself?)
Thanks for reading...

Hi @allquixotic ,
Many thanks for bringing these 2 issues to our attention. And, a special thanks for the very thorough rationale setting and the solution approach you've described here. This helps our team with exactly understanding the background for the ask.
After reading through both the problem statements, here's my first impressions. I/team will update here with other feedback as we discuss this internally next week.
Could I ask you to break down both the problems into 2 issues please? Given the scope of these issues, it would be more helpful to tackle them as individual issues. With this assumption, I am providing the updates here for the first problem statement.
Also, to answer your last question - no, we did not think of these pain points until now , thank you for bringing this to our attention. Yes, we always welcome collaboration from the community and accept PR's.
Problem Statement 1: User/Group management without SCIM

The business context, feasibility and the pain points described in this problem statement are clearly understood, and I agree that bridging this gap would be a very useful feature of the solution.

I am trying to break down this into logical components , and the model I could come up with is as follows:

Fast-Fed based SCIM middle-ware

perform all SSO user/group provisioning operations as SCIM operations supported by SSO SCIM API
implemented through API gateway + lambda (and have an S3 path as mirror alternative)
generic for any identity source customer has
needs updates when SSO SCIM API are updated

Connector modules for a beginner set of non SCIM identity sources

These would be fully packaged solutions that work for a non SCIM identity source and aim to handle user/group changes dynamically if feasible, and fall back to bulk scheduled mode otherwise
The connector modules look up data from the non SCIM identity source and transform this into a format acceptable by SCIM middle-ware
Managed AD would be a good first candidate to write a connector module

Utilities

These would include functional components that do schema validation, identity source integration, batching, parallelisation, logging, error handling

From an end user perspective, the flow would be as follows:

In the configuration file, they would set provisionSCIM to true
They would also set identitySource to one of the supported connectors we provide. for ex, ManagedAD
Depending on value in (2) , they would then fill in details specific to the identity source. This would include mode of import from identity source as well i.e. dynamic/bulk scheduled. If the value in (2) is not a supported source, then the user should mandatorily specify what interface they would choose for SCIM middle ware - API/S3.
They would then deploy the pipeline, which would either deploy the connector and start importing users/groups based on the mode the connector supports and the user choose in their config file (or) provide the user with S3/API interface details for SCIM middle ware. If the user choose a non supported connector, then they could script a mechanism that matches their identity source with the target set of that script being - make an API call / upload an object to S3.

What are your first thoughts on this?
Thanks,
Leela

Separated out the second problem to #46.

My comments are inline. Thank you for your hard work on this.

Hi @allquixotic ,
Many thanks for bringing these 2 issues to our attention. And, a special thanks for the very thorough rationale setting and the solution approach you've described here. This helps our team with exactly understanding the background for the ask.
After reading through both the problem statements, here's my first impressions. I/team will update here with other feedback as we discuss this internally next week.
Could I ask you to break down both the problems into 2 issues please? Given the scope of these issues, it would be more helpful to tackle them as individual issues. With this assumption, I am providing the updates here for the first problem statement.
Also, to answer your last question - no, we did not think of these pain points until now , thank you for bringing this to our attention. Yes, we always welcome collaboration from the community and accept PR's.
Problem Statement 1: User/Group management without SCIM
* The business context, feasibility and the pain points described in this problem statement are clearly understood, and I agree that bridging this gap would be a very useful feature of the solution.

* I am trying to break down this into logical components , and the model I could come up with is as follows:

1. [Fast-Fed](https://openid.net/specs/fastfed-scim-1_0-02.html#rfc.section.4) based SCIM middle-ware

* perform all SSO user/group provisioning operations as SCIM operations supported by [SSO SCIM API](https://docs.aws.amazon.com/singlesignon/latest/developerguide/supported-apis.html)

* implemented through API gateway + lambda (and have an S3 path as mirror alternative)

* generic for any identity source customer has

* needs updates when [SSO SCIM API](https://docs.aws.amazon.com/singlesignon/latest/developerguide/supported-apis.html) are updated

Agreed. Providing S3 and API driven management of the users will make it a most flexible solution, just like the current design patterns for permission sets and links.

2. `Connector` modules for a beginner set of non SCIM identity sources

* These would be fully packaged solutions that work for `a non SCIM identity source` and aim to handle user/group changes dynamically if feasible, and fall back to bulk scheduled mode otherwise

* The `connector` modules look up data from the non SCIM identity source and transform this into a format acceptable by SCIM middle-ware

* Managed AD would be a good first candidate to write a `connector` module

This is excellent.
The only thing I would add: to avoid weird conflicts, if the user enables a pre-packaged connector, the setting for using S3 or API driven for user and group management should probably be ignored. When a connector is enabled, to avoid weird conflicts and unexpected behavior, the SCIM middleware should always be set up for API access.
A user could, at their option, both use a connector and custom API calls to the SCIM middleware, but I'm not sure if that would have any weird corner cases that make it hard to manage on the SCIM middleware backend.
I have a hard time rationalizing in my head how the S3 approach would work in conjunction with a connector. Maybe if you can see how to resolve that design ambiguity, you could allow S3 to be used at the same time as a connector.
For my organization's purposes, we would just use the Managed AD connector, and we would not add our own code to call the SCIM middleware API, nor would we need additional user management in S3. We would treat our Managed AD as the single source of truth for SSO user and group management.

3. Utilities

* These would include functional components that do schema validation, identity source integration, batching, parallelisation, logging, error handling

* From an end user perspective, the flow would be as follows:

1. In the configuration file, they would set `provisionSCIM` to `true`

This is good so far..

2. They would also set `identitySource` to one of the supported connectors we provide. for ex, `ManagedAD`

Or none (or omit identitySource entirely)? :) My organization would use ManagedAD, but a flexible design will help the most organizations use this.

3. Depending on value in (2) , they would then fill in details specific to the identity source. This would include mode of import from identity source as well i.e. dynamic/bulk scheduled. If the value in (2) is not a supported source, then the user should mandatorily specify what interface they would choose for SCIM middle ware - API/S3.

Ah, this solves some of my earlier concerns.

4. They would then deploy the pipeline, which would either deploy the `connector` and start importing users/groups based on the mode the connector supports and the user choose in their config file (or) provide the user with S3/API interface details for SCIM middle ware. If the user choose a non supported connector, then they could script a mechanism that matches their identity source with the target set of that script being - make an API call / upload an object to S3.

Excellent. To follow existing design patterns, we'd want to introduce another option flag for preserving existing users who were manually created in AWS SSO but may not exist in the identitySource.  Something analogous to ImportCurrentSSOConfiguration, but applying to the identity source connector.

What are your first thoughts on this?
Thanks, Leela

One implementation concern I have... This may not actually require modifications to this design spec...
Our OrgMain account does not currently have network level access to our Managed AD. The Managed AD sits in a member account on a private VPC. Currently we have our entire SSO Extensions solution sitting in OrgMain in the same region.
I think if you put the SCIM middleware and the identity source connector into the target account (target being a technical term used in the design of SSO Extensions), we'll be able to change our SSO Extensions deployment so that the target account is the same account as the Managed AD. This is probably a better design for us long term, anyway, and it would solve the networking problem without needing a TGW from the member account back to OrgMain.

Hi @allquixotic ,
Regarding the account structure, while moving to the recommended multi account model is a good idea and should be done, this won't be a blocker however. I am planning to treat the account hosting Managed AD as a separate account and communicate through cross account/region SNS topics. This is the same design pattern implemented currently between OrgMain, SSO and target accounts.
Regarding the logical design and flow details, I am working with the rest of the team on a structure and will update here shortly.
Also, to set the correct timeline expectations,  we are currently working on another feature we've prioritised for 2 of our customers that would enable them to do a region switch with their AWS SSO. This is a stand-alone component of the solution that a customer could use to automate moving their permission sets and account assignments over to the new region. In terms of our current development, we are aiming to get this out in 3.1.0 in the next 2 weeks, and will focus on this enhancement as the next priority.
Hope these timelines work for you.
Thanks,
Leela

The other feature request I logged recently is actually more urgent than this one. The good news about this issue is that I've already written code that solves the immediate need for my organization, and can continue to customize it to suit my needs. It isn't as elegant as a baked-in solution with SSO Extensions, but it's better than nothing.

@fotinosk will update the solution design docs with the pattern he's building for SCIM support and link the docs here for reference.


Security Report<EMAIL_ADDRESS>

146 - Command Injection
Vulnerable: <1.10.2 - Patched: >=1.10.2 - Path<EMAIL_ADDRESS>><EMAIL_ADDRESS>How to fix
Update to version 1.10.2 or greater
https://nodesecurity.io/orgs/eggjs/projects/16be4d34-c7a2-4e01-9696-62a90742d571/71

FYI, there's a related PR at #2931

Going to close this as a duplicate of #2791, but feel free to take any additional discussion there -- in particular, if you can help us find any of the info mentioned in https://github.com/mochajs/mocha/pull/2930#issuecomment-315798341, that would help us resolve this.


DBZ-8199 Fix test to resolve database name from environment

https://issues.redhat.com/browse/DBZ-8199

/packit test --labels oracle

Oracle 19 XStream failure related to #5811, this PR was not based on that change.


go module dependency  changed back atomatically,  which i don't want

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

$ go version
go version go1.13.1 windows/amd64

Does this issue reproduce with the latest release?
1.13.1  YES
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\winjeg\AppData\Local\go-build
set GOENV=C:\Users\winjeg\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=D:\software\gosrc
set GOPRIVATE=
set GOPROXY=https://goproxy.io,direct
set GOROOT=D:\software\goinst
set GOSUMDB=off
set GOTMPDIR=
set GOTOOLDIR=D:\software\goinst\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=D:\projects\go\Devops\ops-base\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\winjeg\AppData\Local\Temp\go-build496850154=/tmp/go-build -gno-record-gcc-switche

What did you do?
Programmer

What did you expect to see?
when I change back to a lower version, using go get, it should not change back to the  former version.
What did you see instead?
every time i try to run or bulid my program,  the version of the dependency go-commons changed back, no matter how hard i tried.
I tried to clean up the gopath files as well.

Duplicate of #33284

Some transitive dependency in your module graph already requires the higher version. go mod graph can show you which one, and you can examine the output of go mod graph to find the path from your module to that requirement.

I tried to downgrade the version of the go-commons  package, it seemed ok.
I tried go mod graph | grep go-commons, it show no other dependency require a higher version of the package go-commons
I tried to run go build .,  the dependency just changed again.

A little help here, thanks.
ps:  can go build show which dependcy  is changed and why it is changed with exra args added ?

That probably means that the go command upgraded the module in order to provide some missing package for an import statement.

Actually, in your animation there is an error message that seems to describe the problem. Please attach failure messages and other relevant data as text rather than (especially animated!) images.

It't another project and the same result.
here is the whole thing...   even go mod why can change the dependency back

the output is somewhat strange, the issue below mentioned the same.
https://github.com/golang/go/issues/31351
I'll try to find a way to write down more detailed steps to reproduce the problem

Here is a demo project to prove it.
mkdir demo
cd demo
go mod init demo
touch main.go
go get github.com/winjeg/go-commons  # which will get the latest version 1.2.1

then you copy the following code into main.go
package main

import (
	"fmt"
	"github.com/winjeg/go-commons/uid"
)

func main() {
	fmt.Println(uid.UUIDShort())
}

then just run it use go run main.go
then you go back and get the older version @v0.0.1
go get -u<EMAIL_ADDRESS>
then you should notice the content of go.mod is already changed
and then you try go mod why -m github.com/winjeg/go-commons, you will get the follwing output
D:\projects\go\demo>go mod why -m github.com/winjeg/go-commons                                                          # github.com/winjeg/go-commons                                                                                (main module does not need module github.com/winjeg/go-commons)

go back and watch the file go.mod,  the file changed back to version 1.2.1 automatically

Well here's your trouble. You apparently moved the v0.0.1 tag.
Modules are (intentionally) immutable: the same version must always refer to the same bytes, forever, starting from when that version is first published.
With the default GOPROXY value, downloading v0.0.1 gives you the copy of that version that was initially published, which does not include the github.com/winjeg/go-commons/uid package. When you run go build, go mod tidy, or any other command that needs to load that package, the go command upgrades you to a version that includes that package — and the only released version that includes it is v1.2.1.
demo$ GOPROXY=direct go1.14beta1 mod download
<EMAIL_ADDRESS>verifying module: checksum mismatch
        downloaded: h1:z3edKP8Wq4tBAqxAbyJRBIAj4gVfOrmDop4Jt+aJYuE=
        sum.golang.org: h1:TlzoXb4plQwNaXXrYOjIFmij1pyC+l3f5snK8bMbmJI=

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

demo$ GOPROXY='' go1.14beta1 mod download

demo$ go list github.com/winjeg/go-commons/...
github.com/winjeg/go-commons/conf
github.com/winjeg/go-commons/httpclient
github.com/winjeg/go-commons/log
github.com/winjeg/go-commons/str

As far as I can tell, this is all working as designed. Module versions are immutable — don't expect to mutate them.

So, you cannot do a re-version unless you change the module name ?
What if the version you release is not good, or not released intensionally?
I encountered the same problem  with go-grpc, I also cannot downgrade to a lower version.
Can there be any workarounds except changing the modlue name ?

If there is a problem with a released version, then you can issue a patch release to fix the problem and upgrade to that.
In some cases it may take a fair amount of work to upgrade a bad dependency completely away, but we're working on improving those cases in the future; see #34189, #24031, and related issues.


Using stop keyword as object key causes parse errors

This brightscript code causes a parse error because the stop keyword is not being interpreted as an identifier.
sub GetObject()
    obj = {
        stop: function() as void

        end function
    }
    return obj
end sub

Great catch!  Pulling this into 0.13.0.


fix: prefix show

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

如果下拉选项没有内容供select选择此时 prefix插槽内容无法正确渲染


Accessors do not have the link to the source file

Here is a screen capture of an accessor:

The same content, but with the default theme:

As it can be seen, the source line information, present with the default theme, is missing with the yaf theme.

Examining the issue,
Thanks for reporting.


Build 7.2.0 alpha debian packages

Add support for building 7.2.0alphaX.

[x] Cannot install PEAR (and thus cannot install PECL)
[x] Ensure we can build our extensions on 7.2.0

Creates a php72 image and compiles the debian packages for 7.2.0alpha3.
We won't release the real php72 image until December when it's released.


RT 1.7 local_bgp_test.go , RT1.5 bgp_prefix_limit_test.go, RT1.4 bgp_graceful_restart_test.go

Hi,
RT1.7 local_bgp_test.go, RT1.3 bgp_prefix_limit_test.go:
We need to configure bgp peer group for any neighbor even if we are not  enabling any routing policy.

Added BGP Peer group config in both scripts.
Added network instance type to default in both scripts.
Resolves #823
Please review and approve.

RT1.4 bgp_graceful_restart_test.go :
If graceful restart is configured, LLGR is enabled by default.
Hence DUT keeps routing information until LLGR is expired.
We need to add wait time to make sure LLGR is expired to test forwarding capability after Graceful restart.
Thanks,
Prabha

Reopened after resolving conflicts.

@amrindrr , Please could you review and provide approval. Thank you.

Hi,
I am getting error in validating protobufs.
Error:
Run arduino/setup-protoc@v1
Error: API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.
Please could you let me know how to fix it ?
Thanks,
Prabha

could you split this PR for individual testcases.

could you split this PR for each test separately.

@singh-prem we can see the changes per file and other pull requests are also done with multiple files.
May i know if there is any specific reason for this request?

could you split this PR for each test separately.

@singh-prem we can see the changes per file and other pull requests are also done with multiple files. May i know if there is any specific reason for this request?

Oh its just for simplicity. We need to verify all these changes don't break the tests on our platform.  With larger content

could you split this PR for each test separately.

@singh-prem we can see the changes per file and other pull requests are also done with multiple files. May i know if there is any specific reason for this request?

oh its just for simplicity.


[1.9] Issue ClientConnectionEvent

Running EssentialCmds on the unsupported only 90% done 1.9 Branch of Sponge I get..
[16:18:34] [Netty Epoll Server IO #1/DEBUG] [mixin]: Mixing util.MixinPacketThreadUtil from mixins.common.core.json into net.minecraft.network.PacketThreadUtil$1
[16:18:34] [Server thread/ERROR] [Sponge]: Could not pass ClientConnectionEvent$Join$Impl to Plugin{id=io.github.hsyyid.essentialcmds, name=EssentialCmds, version=8.1.0-4760d4c, description=This plugin features many commands and useful features for server admins., source=mods/EssentialCmds-8.1.0.jar}
java.lang.NoSuchMethodError: org.spongepowered.api.entity.living.player.Player.setLocationSafely(Lorg/spongepowered/api/world/Location;)Z
	at io.github.hsyyid.essentialcmds.listeners.PlayerJoinListener.onPlayerJoin(PlayerJoinListener.java:87) ~[PlayerJoinListener.class:8.1.0]
	at org.spongepowered.common.event.listener.JoinListener_PlayerJoinListener_onPlayerJoin5.handle(Unknown Source) ~[?:?]
	at org.spongepowered.common.event.RegisteredListener.handle(RegisteredListener.java:86) ~[RegisteredListener.class:1.9-6.0.0-BETA-0]
	at org.spongepowered.common.event.SpongeEventManager.post(SpongeEventManager.java:258) [SpongeEventManager.class:1.9-6.0.0-BETA-0]
	at org.spongepowered.common.event.SpongeEventManager.post(SpongeEventManager.java:269) [SpongeEventManager.class:1.9-6.0.0-BETA-0]
	at org.spongepowered.common.SpongeImpl.postEvent(SpongeImpl.java:138) [SpongeImpl.class:1.9-6.0.0-BETA-0]
	at net.minecraft.server.management.PlayerList.initializeConnectionToPlayer(SourceFile:374) [mm.class:?]
	at net.minecraft.server.management.PlayerList.func_72355_a(SourceFile:144) [mm.class:?]
	at net.minecraft.server.network.NetHandlerLoginServer.func_147326_c(SourceFile:116) [md.class:?]
	at net.minecraft.server.network.NetHandlerLoginServer.func_73660_a(SourceFile:62) [md.class:?]
	at net.minecraft.network.NetworkManager.func_74428_b(SourceFile:232) [ek.class:?]
	at net.minecraft.network.NetworkSystem.func_151269_c(SourceFile:187) [ma.class:?]
	at net.minecraft.server.MinecraftServer.func_71190_q(SourceFile:193) [MinecraftServer.class:?]
	at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(SourceFile:339) [la.class:?]
	at net.minecraft.server.MinecraftServer.func_71217_p(SourceFile:553) [MinecraftServer.class:?]
	at net.minecraft.server.MinecraftServer.run(SourceFile:457) [MinecraftServer.class:?]
	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]

Full log can be found here..
http://theloveoflinux.com/logs/test/latest.log
I have sent you information about a test server with 1.9 if there's anything else you need, or need me to test let me know. Thanks

The api breaks. Do not use plugin that supports api 4 on api 5.

I know the API breaks, I am reporting it so he knows what's broke. The plugin for the most part works quite well on api 6. He mentioned he might make a branch for 1.9 so I thought I would report what I am seeing now so if he does he has something to work with.

This issue seems to be fixed on a new world with the latest Bleeding builds of Sponge from git.


ActionSheetDialog gasEstimateOutOfDate error?

Whether to call gasWidget or gasWidgetLegacy based on use1559Transactions？

There is no need to call GasEstimate OutOfDate when switching chain requests.

1


RDK-31068: HDMI Output HDCP Status Change Notification XiOne

Reason for change:
HDMI Output HDCP Status Change Notification XiOne
Thunder changes.
Test Procedure: None
Risks: Low
Change-Id: If1a59fd14d7829d64f10dbd91a667b19c55137c1
Signed-off-by:Anooj Cheriyan<EMAIL_ADDRESS>

Closing this outdated PR. Please submit this to the latest sprint branch if needed.


uniq: missing support for deprecated -f syntax

Similar to #2507. The -f <num> option to uniq has a deprecated syntax, -<num>. See https://www.gnu.org/software/coreutils/manual/html_node/uniq-invocation.html For example,
$ printf "a a\nb a\n" | uniq -1
a a

how did it go?
i'd like to try if no one is working on it

sure, please do :)

how did it go?
i'd like to try if no one is working on it

yes, go for it—I fully do not remember what I ended up doing haha

it works now :)


Runtime error trying your example

Hi tried your example but getting Object required error on
ReDim Values(Parsed("values").Count, 3)
When I look at Parsed in watch window I can see it exists as a dictionary (with only 6 elements, expected thousands)
Is it the code? Am I missing references?
Attached the file I try to load into VBA (excel 2010) maybe you can shed some light
Thanks
Planets.txt

Hi @Qinic, the example assumes the following format for the example json
{
  "values": [
    {"a": 1, "b": 2, "c": 3},
    {"a": 4, "b": 5, "c": 6},
    {"a": 7, "b": 8, "c": 9},
  ]
}

In your Planets.txt, there is no root values item, so the .Count call is failing. You could iterate through something like the following, Parsed("rst")("players").Count, or something similar.

Hi Tim,
ah I misunderstood the way this was parsing.
That makes sense, so I can either grabe certain array subs structures or
adapt the code to figure the structure out itself.
Anayway will play with this based on your input a bit and see how I best
ustelize it.
Thank you very much indeed.
Cheers
Qinic
On 26 May 2016 at 02:10, Tim Hall<EMAIL_ADDRESS>wrote:

Hi @Qinic https://github.com/Qinic, the example assumes the following
format for the example json
{
"values": [
{"a": 1, "b": 2, "c": 3},
{"a": 4, "b": 5, "c": 6},
{"a": 7, "b": 8, "c": 9},
]
}
In your Planets.txt, there is no root values item, so the .Count call is
failing. You could iterate through something like the following,
Parsed("rst")("players").Count, or something similar.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/VBA-tools/VBA-JSON/issues/29#issuecomment-221752060


Automated PR: Standardising Files

This PR will standardise the files we have with out agreed spec in sous-chefs/repo-management.
This repo has been identified by topic(s) of chef-cookbook

@ramereth so this looks good now. The only thing stopping us merging this is a Gem update with the new specs.
Any idea how we go about that?

@ramereth so this looks good now. The only thing stopping us merging this is a Gem update with the new specs.
Any idea how we go about that?

At one point @tas50 mentioned that gem might be better in Sous Chefs so we could do our own releases. I'd say the next step is to get that transferred and then also get access to doing releases.

Merging as is. And I'll put fixing the gem in my backlog

Released as: 6.0.0


[cli] Add automatic gas estimation, and move all CLI client commands to use it

Description
This PR adds automatic gas estimation support for all CLI client commands by default. Providing a specific gas budget is still possible through the --gas-budget option.
Note this also fixes a problem with the way CLI PTB tests are executed, which led to issues (cannot find test files).
Test Plan
Added new tests + existing tests.
cargo nextest run --test cli_tests

If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.
Type of Change (Check all that apply)

[ ] protocol change
[x] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes
The CLI client commands do not require to provide a --gas-budget value anymore, as it is automatically inferred through a dry run. It is still possible to provide one, if the user wants.

I like the change overall! Main thing I'd love to change before we land this is how the transactions are created.
Today, you are duplicating the logic involved in creating the TransactionData, once for the gas estimation and another time to actually run it. This is not great from a code repetition perspective, but it's also not good from an efficiency or consistency perspective. Some of these transaction building commands do a fair bit of work, talking to RPC to resolve ObjectIDs into ObjectRefs etc, you don't want to redo that work because it's not cheap, and in general you may get a different answer from run to run, and while that's usually going to mean the transaction execution will fail, we should still return a consistent response in that case (e.g. the transaction you dry ran is the same as the one that you executed).
The fix is to split the logic for generating transactions into three phases:
* Build the `TransactionKind` -- this is usually where most of the effort and consistency concerns go, and we can always do this once because the gas budget is not relevant for this part.

* Build the `TransactionData` for dry-run, from a clone of the `TransactionKind`.

* Build the `TransactionData` for execution, using the gas budget you got from dry-run, and execute it.

Agreed, I was quite unhappy with the way I did it. Will refactor!

Superseded by #17322


How to retrieve a local actor based on spawned name? #question

Hey guys I have this following concept. How can i retrieve the PID based on spawned name (i ve checked that ProccessRegistry..LocalPIDS returns process but cant do the job)?

#question

I think you can get it by calling actor.ProcessRegistry.GetLocal(...name...)

I used that but it doesn't work. Have you tried something similar?
On Thu, Nov 15, 2018, 8:09 PM Potter Dai<EMAIL_ADDRESS>wrote:

I think you can get it by calling
actor.ProcessRegistry.GetLocal(...name...)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AsynkronIT/protoactor-go/issues/258#issuecomment-439136523,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJusAyyIXg7fOxcUMSAlOjxVblmLATk9ks5uva3BgaJpZM4YgUP9
.

Oh, my bad. Actually if you just want the pid, you can simply create one by giving your name and your address
&actor.PID{Address, Name}
since PID is just something like url.

Well, I receive a Deadletter now.. pff so, what is supposed to do? for e.x if I create a actor  "MathewActor", I should be able to retrieve him using actor.ProcessRegistry.GetLocal("MathewActor")?

Yep, that's right, but typically you should not do that, using &actor.PID{Address, Name} is a better way to solve this.
If it returns DeadLetter, it means the actor is not spawned or is dead.
Did you spawn the actor?

Well, I Did spawned the router actor. Here is how I solved it, but i dont think is a proper way.
				proc, _ := actor.ProcessRegistry.GetLocal("$1/myRouter")
pid := &actor.PID{ 						Address: "nohost", 						Id:      "$1/myRouter", 					}
proc.SendUserMessage(pid, &DeriveMessage{Who: id.(string)})
@PotterDai  I believe that it would be better to add a new method ProcessRegistry.GetLocalActor which returns a PID.

@nikoszoisse
Hmmm.... this doesn't make sense that it works by this way
What happened if you use this:
pid := actor.NewLocalPID("$1/myRouter")
pid.Tell(&DeriveMessage{Who: id.(string)})

@nikoszoisse
I think I got what's wrong!
The default local address is "nonhost" instead of "nohost".
You can also use actor.NewLocalPID(....name..) to avoid the confusion.

Just tried what you said, That's correct!!! Thank you for your time!!
On 15 November 2018, at 22:09, Potter Dai<EMAIL_ADDRESS>wrote:
@nikoszoisse
The reason of deadletter is not because (p *Process) is not assigned, it will be automatically assigned if you call pid.Tell(...). The reason you got deadletter is because you didn't use the correct local address, which is "nonhost" instead of "nohost".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.￼
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/AsynkronIT/protoactor-go","title":"AsynkronIT/protoactor-go","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/AsynkronIT/protoactor-go"}},"updates":{"snippets":[{"icon":"PERSON","message":"@PotterDai in #258: @nikoszoisse \r\nThe reason of deadletter is not because (p *Process) is not assigned, it will be automatically assigned if you call pid.Tell(...). The reason you got deadletter is because you didn't use the correct local address, which is "nonhost" instead of "nohost"."}],"action":{"name":"View Issue","url":"https://github.com/AsynkronIT/protoactor-go/issues/258#issuecomment-439173805"}}} [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/AsynkronIT/protoactor-go/issues/258#issuecomment-439173805", "url": "https://github.com/AsynkronIT/protoactor-go/issues/258#issuecomment-439173805", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } }, { "@type": "MessageCard", "@context": "http://schema.org/extensions", "hideOriginalBody": "false", "originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB", "title": "Re: [AsynkronIT/protoactor-go] How to retrieve a local actor based on spawned name? #question (#258)", "sections": [ { "text": "", "activityTitle": "Potter Dai", "activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png", "activitySubtitle": "@PotterDai", "facts": [ ] } ], "potentialAction": [ { "name": "Add a comment", "@type": "ActionCard", "inputs": [ { "isMultiLine": true, "@type": "TextInput", "id": "IssueComment", "isRequired": false } ], "actions": [ { "name": "Comment", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n"commandName": "IssueComment",\n"repositoryFullName": "AsynkronIT/protoactor-go",\n"issueId": 258,\n"IssueComment": "{{IssueComment.value}}"\n}" } ] }, { "targets": [ { "os": "default", "uri": "https://github.com/AsynkronIT/protoactor-go/issues/258#issuecomment-439173805" } ], "@type": "OpenUri", "name": "View on GitHub" }, { "name": "Unsubscribe", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n"commandName": "MuteNotification",\n"threadId": 411124733\n}" } ], "themeColor": "26292E" } ]

@nikoszoisse
Haha, that's great! = )
I should have suggested you using actor.NewLocalPID(...) before, that will avoid all those local address hassles = )


Fix broken Kaniko build due to symlink

There are differences on how Docker builds the Dockerfile with a symlink and
how Kaniko operates on the same file. In contrast to Docker build, the COPY
command for Kaniko behaves more like a cp -R from to and therefore preserves
the symlink as a symlink. In Docker, during the build, the COPY resolves the
symlink to place it as a regular file from the build context into the layer.
This creates the problem, that a Dockerfile with a COPY statement against a
symlink is hard to maintain to be both supporting Docker builds and Kaniko.
With the current Dockerfile, a COPY command with Kaniko results in a broken
symlink, because it preserves it and after the copy the target path does not
exist due to the fact that it is a relative path in the repo.
Remove symlink from Git repo root.
Use symlink target helloworld/helloworld.go directly in root level Dockerfile.
Signed-off-by: Matthias Diester<EMAIL_ADDRESS>

Closing in favor of  https://github.com/IBM/CodeEngine/pull/10


Allow for users to download "suites" of scripts

Currently on the website, downloading scripts is simple—one download per script, and one script per download.
However, many of the scripts could be bundled together to form a "suite" of scripts. For instance, there are many scripts for moving dynamics/chords/staves/expressions/measure-numbers up/down. These all fall into the "move things vertically" category. Wouldn't it be nice for users to be able to download all of these with one click?
Or perhaps another example with a stronger case. Most of my unpublished scripts now are just slight variations on one idea. I have 14 scripts to change key signatures. I have another 12 or so for time signatures. I have 8 to change barlines. Etc.
I've resisted publishing these since that could flood our download page with a lot of noise. Want to search for a script related to key signatures? Too bad, you have 14 more scripts to wade through that are almost identical.
Now I have these scripts broken out since Keyboard Maestro makes it very quick and easy to select each of them. And if I were to combine these into a single script with a menu to select the specific key (for instance), now it's no better than Finale's key signature menu—and you lose out on the massive speed gains from the KM/Lua combo.
So if there was some way I could also publish these scripts but be able to group them into a suite of scripts with a single download button, that would allow others to get use out of my scripts while still making it easy to find scripts on the website.
No idea how to do this yet, but creating an issue in case anyone else has ideas or wants to help.

To me it seems like (taking your key signature scripts as examples) it should only be one script with parameters. RGP Lua has the ability to load the same script multiple times with different parameters defined in the prefix for each (as well as different menu, description, and undo text). So leveraging that seems like a possible solution. (This is pretty much why I added that feature.)
One way you could do it now is to package your script(s) along with all the configurations in a separate xml file and bundled with a separate copy of RGP Lua for a stand-alone menu item. But I don't like this approach because it encourages splattering copies of RGP Lua throughout the plugin directory.
Another possibility is to enhance RGP Lua to look for a config file in the same location as the script and add additional configurations there. Then each script could be bundled with all the different possible configurations for each option. Maybe it could be a lighter-weight format than xml. A simple delimited string per menu option could do it. Then all the user would need to do is download one script and one text file with menu options.

On further reflection, it might be be better to build into the plugindef function the ability to create multiple menu options with different parameters. Similar to the old Parameters feature of jwlua, but without any need for external setup.
What do you think?

Here is a proposed way of using the plugindef function. This example would combine all the pitch_entry_double_*.lua scripts into a single script. This uses an approach similar to jwlua's parameters feature. (I looked at reusing that, but I don't want to have to be compatible with how jwlua treats it.)
function plugindef()
    finaleplugin.RequireSelection = true
    finaleplugin.Author = "Nick Mazuk"
    finaleplugin.Copyright = "CC0 https://creativecommons.org/publicdomain/zero/1.0/"
    finaleplugin.Version = "1.0.2"
    finaleplugin.Date = "March 31, 2021"
    finaleplugin.CategoryTags = "Pitch"
    finaleplugin.AuthorURL = "https://nickmazuk.com"
    finaleplugin.AdditionalMenuOptions = [[
        Double third up
        Double octave down
        Double octave up
    ]]
    finaleplugin.AdditionalUndoText = [[
        Double third up
        Double octave down
        Double octave up
    ]]
    finaleplugin.AdditionalDescriptions = [[
        Double third up
        Double octave down
        Double octave up
    ]]
    finaleplugin.AdditionalPrefixes = [[
        diatonic_interval = 2
        diatonic_interval = -7
        diatonic_interval = 7
    ]]
    return "Double third down", "Double third down", "Doubles the current note a diatonic third lower"
end

diatonic_interval = diatonic_interval or -2

local transposition = require("library.transposition")
local note_entry = require("library.note_entry")

function pitch_entry_double()
    for entry in eachentrysaved(finenv.Region()) do
        local note_count = entry.Count
        local note_index = 0
        for note in each(entry) do
            note_index = note_index + 1
            if note_index > note_count then
                break
            end
            local new_note = note_entry.duplicate_note(note)
            if nil ~= new_note then
                transposition.diatonic_transpose(new_note, diatonic_interval)
            end
        end
    end
end

pitch_entry_double()

RGP Lua add a menu option for the main return value (in this case "Double third down"). It would then also add an additional menu option for each of the strings in finaleplugin.AdditionalMenuOptions.

I have pushed a working example of what I'm thinking of to the branch RGP-changes-for-rgplua-0.62. It works with the version of RGP Lua running on my dev box but is fully backwards compatible with previous versions. (By means of deprecating scripts that are no longer needed and marking them not to run with 0.62.)
Let me know what you think.

Ooh, I like that functionality. It also makes maintaining them easier since it's just one script, not 14!
For the finaleplugin.AdditionalPrefixes field, how would it work if there are multiple variables you'd like to change?
For reference, all my scripts I referenced in the original post are pre-RGP Lua.

The lua language treats line breaks the same as spaces, so you could write a prefix like:
param1 = 1 param2 = 3.5 param3 = "EVPU"

Or you could have the prefix parameter be an index into a configuration table.

Ok, that makes sense. So each line can be any arbitrary piece of Lua to setup the script.

Yes, that's the approach I was thinking of.

That works, and will dramatically simplify some of my scripts. I like it!
If a script needs many separate parameters, we may need to rethink this. Though one could argue that if you need to configure 10 different variables that they should really be separate scripts at that point.

I would create a configuration table at that point, if it really needed to be one script. Then the prefix could be a index into the table.
Or the prefix could be a string that names a require library that actually executed the script. The flexibility of this approach seems pretty high to me.

True, that's a really elegant way to do this.
Since it sounds like this is coming in v0.62, I'm going to go ahead and close this issue.

I'm reopening the issue to get feedback on one further issue. There are a number of plugin suites already in existence that can be collapsed into a single script using the new 0.62 feature. The question is what to do about the old scripts. Do we

delete them and expect users to use 0.62?
leave them alone but perhaps mark them not to load in 0.62+?
move them to a subfolder, e.g., /deprecated?
other ideas?

In the RGP-changes-for-rgplua-0.62 branch, I went with the second option, but honestly I think I prefer the third or the first to the second. The less code to maintain the better.

Good point.
I'd prefer the first option myself. Especially since RGP Lua is technically in beta, I think it's acceptable to make breaking changes for the scripts. Though for this, we should definitely mark the minimum plugin version in the plugindef and I should finish #122.

Ok. Another thing to consider is showing all the AdditionalDescriptions as well as the main description.

Ok. Another thing to consider is showing all the AdditionalDescriptions as well as the main description.

On the website? Possibly.
Are the returned values from the plugindef overwritten by finaleplugin.AdditionalMenuOptions, finaleplugin.AdditionalUndoText, and finaleplugin.AdditionalDescriptions? In other words, would we be able to rewrite the above example's plugindef as:
function plugindef()
    finaleplugin.RequireSelection = true
    finaleplugin.Author = "Nick Mazuk"
    finaleplugin.Copyright = "CC0 https://creativecommons.org/publicdomain/zero/1.0/"
    finaleplugin.Version = "1.0.2"
    finaleplugin.Date = "March 31, 2021"
    finaleplugin.CategoryTags = "Pitch"
    finaleplugin.AuthorURL = "https://nickmazuk.com"
    finaleplugin.AdditionalMenuOptions = [[
        Double third up
        Double octave down
        Double octave up
    ]]
    finaleplugin.AdditionalUndoText = [[
        Double third up
        Double octave down
        Double octave up
    ]]
    finaleplugin.AdditionalDescriptions = [[
        Double third up
        Double octave down
        Double octave up
    ]]
    finaleplugin.AdditionalPrefixes = [[
        diatonic_interval = 2
        diatonic_interval = -7
        diatonic_interval = 7
    ]]
    return "Double notes at interval", "Double notes at interval", "Doubles notes at specific intervals"
end

Then use Double notes at interval for the title on the website? Yet each script will have its own independent title?
If so, we may not need to show each additional description on the website. If that seems necessary for a specific script, the author can put that in the finaleplugin.Notes field.


Expectations 2.1.6 does not run in a Clojure-only project

This exception is produced:
Retrieving expectations-2.1.6.jar from https://clojars.org/repo/
Retrieving joda-time-2.9.3.jar from https://repo1.maven.org/maven2/
             clojure.lang.ExceptionInfo: java.io.FileNotFoundException: Could not locate cljs/analyzer__init.class or cljs/analyzer.clj on classpath., compiling:(expectations/platform.clj:1:1)
    data: {:file
           "/var/folders/p1/30gnjddx6p193frh670pl8nh0000gn/T/boot.user852945197313464727.clj",
           :line 185}
java.util.concurrent.ExecutionException: java.io.FileNotFoundException: Could not locate cljs/analyzer__init.class or cljs/analyzer.clj on classpath., compiling:(expectations/platform.clj:1:1)
clojure.lang.Compiler$CompilerException: java.io.FileNotFoundException: Could not locate cljs/analyzer__init.class or cljs/analyzer.clj on classpath., compiling:(expectations/platform.clj:1:1)
          java.io.FileNotFoundException: Could not locate cljs/analyzer__init.class or cljs/analyzer.clj on classpath.

@plexus any guesses?

FWIW, I verified with a clean project:
lein new testexp

Edit project.clj to look like this:
(defproject testexp "0.1.0-SNAPSHOT"
  :description "FIXME: write description"
  :url "http://example.com/FIXME"
  :license {:name "Eclipse Public License"
            :url "http://www.eclipse.org/legal/epl-v10.html"}
  :plugins [[lein-expectations "0.0.7"]]
  :dependencies [[org.clojure/clojure "1.8.0"]
                 [expectations "2.1.6"]])

and test/testexp/core_test.clj to look like this:
(ns testexp.core-test
  (:require [expectations :refer :all]
            [testexp.core :refer :all]))

(expect 0 1)

Should this line have cljs, not clj?
https://github.com/jaycfields/expectations/blob/master/src/cljc/expectations/platform.cljc#L4

I'm guessing yes, committed. I'll do another release. Let me read some docs to see how to snapshot, so we don't burn through release numbers unnecessarily.

2.1.7 is out there. I tried to release it as alpha, but I don't think that really worked.

Something about how you prepare the build isn't working: the expectations/platform.clj file in 2.1.7 still has:
(ns expectations.platform
  (:refer-clojure :exclude [bound? format ns-name])
  (:require       [clojure.pprint :as pprint]
                  [cljs.analyzer]

                               )
        (:import (clojure.lang Agent Atom Ref)))

hmm, I'm literally doing nothing but lein release (and lein release :alpha for the last one).
We may have to wait on European hours for @plexus tomorrow.

I tried to build the repo locally with lein jar to see if I can debug it but I get these errors:
Compiling 2 source files to /Developer/workspace/expectations/target/classes
/Developer/workspace/expectations/src/java/expectations/junit/ExpectationsTestRunner.java:3: error: package clojure.lang does not exist
import clojure.lang.RT;
                   ^
/Developer/workspace/expectations/src/java/expectations/junit/ExpectationsTestRunner.java:13: error: cannot find symbol
        RT.loadResourceScript("expectations/junit/runner.clj");
        ^
  symbol:   variable RT
  location: class ExpectationsTestRunner
/Developer/workspace/expectations/src/java/expectations/junit/ExpectationsTestRunner.java:14: error: cannot find symbol
        clojureRunner = (Runner) RT.var("expectations.junit.runner", "create-runner").invoke(source);
                                 ^
  symbol:   variable RT
  location: class ExpectationsTestRunner
3 errors
Compilation of Java sources(lein javac) failed.

Do I need something in my ~/.lein/profiles.clj to make this work?

You shouldn't. I have a basically blank laptop that I just ran it on and all was well.

I had to do lein javac; lein jar. I think part of the problem is that the JAR is getting created with old cljx output files in it.
I ran lein do clean, javac, jar and got a clean JAR that contained the cljc source (instead of the generated versions). When I lein install that and try to use it, I get a different exception:
Exception in thread "main" java.lang.ClassNotFoundException: cljs.analyzer, compiling:(expectations/platform.cljc:16:11)

And sure enough that line still refers to cljs.analyzer because of this function:
#?(:clj
   (defn expanding [n]
     (if (cljs?)
       `'~(cljs.analyzer/macroexpand-1 {} n)
       `'~(macroexpand-1 n))))

This was supposedly fixed by @plexus in #74 but clearly isn't. I also noticed that @magnars ran into the same problem I did with Java compilation when they tried to build from source.

I committed a complete guess if you want to give that a shot. If that doesn't work, we can always just ditch the cljs in that fn for now.

It doesn't look like your change passes lein test?

2.1.8 is out there now, and includes all of your changes from today.

Thanks. Confirmed 2.1.8 works in a Clojure-only project. I went ahead and updated boot-expectations to 1.0.8 to provide Expectations 2.1.8 by default. That also tests cleanly.

awesome, thx for all the help

sorry for the trouble!

No problem. My first opportunity to experiment with reader conditionals so it was time well spent :)


Short solution needed: "Convert Numpy array to bytes" (python-numpy)

Please help us write most modern and shortest code solution for this issue:
Convert Numpy array to bytes (technology: python-numpy)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Convert Numpy array to bytes


Update to JDOM2. Remove Axiom from dspace-api (replace with JDOM2)

References

Fixes dependabot security alert with JDOMv1: https://github.com/DSpace/DSpace/security/dependabot/1
Workaround for #8188 (as Axiom is fully removed from our codebase)

This seems to (temporarily?) solve the conflicts between Solr 8.11.1 and SWORDv2.  It appears that once Axiom is removed, this removes the immediate dependency conflict, and both Solr & SWORDv2 function properly.  That said, it may only be "temporary" until we stumble on the next dependency conflict with the SWORDv2 Java library.

Description
This PR updates much of our XML parsing code to use JDOMv2. Specifically:

Updates all JDOMv1 code to use JDOMv2
Removes all Axiom code, replacing with JDOMv2
Required also updating ROME libraries (for RSS/Atom feeds) to latest version, as it relies on JDOM as well. The prior version used JDOMv1, but I've upgraded to the latest ROME which uses JDOMv2.

Instructions for Reviewers

Review the code changes.  Many of the JDOMv1 -> JDOMv2 changes should be relatively easy to review
Test the arXiv and PubMed API import tools (likely easiest via the User Interface, by using the import feature on MyDSpace).  Ensure they still work with JDOMv2 (as previously these import plugins used Axiom)

I've restarted the builds in this PR to "kick" Codecov.  For some reason it never responded after the first build


Toolbar - navigation button hardly clickable

The button in top Toolbar is very hardly clickable. It uses size of drawable for click area, which is 24x24 dp for ic_back.xml. 48dp is probably recommended minimum for buttons.
Ideally the button uses entire toolbar height, and has predefined width, starting from leftmost pixels. The drawable icon may be whatever size it wishes, but clickable area should be large enough.
See visualization of current clickable area:

This was fixed by #45 // CC @nickbutcher

This has been fixed


Add new method to returna single network

Currently, all generated models are saved to a directory, requiring the user to find the directory and load any of the models they would like to look at. which for a single model can be an unnecessary burden for the user. To make things easier add a new method:
generate.model()
where it only generates a single model and returns the model as a string to the user, eg
antStr = generate.model (format='antimony')
sbmlStr = generate.model (format='sbml')
I imagine the default would be 'ant'. The arguments to model() will be the same as models() expect that n_models  = 1 and can't be changed to another value.

Can now be done with the generate.model method.


System.DllNotFoundException: dwrite.dll ---> System.ComponentModel.Win32Exception: Access is denied.

Type (choose one):

Bug

NPE version: (e.g. 5.x) (see Help -> about)
<IP_ADDRESS>
Installed from:
Microsoft Store

What is the current result?
The application does not run.
What is the expected result?
The application should run
Please post full exception details in case of an Exception (message, stacktrace, inner exceptions).
Stack trace from event logs:

Application: NuGetPackageExplorer.exe
CoreCLR Version: 4.6.27121.3
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException: The type initializer for 'System.Windows.Application' threw an exception. ---> System.TypeInitializationException: The type initializer for '<Module>' threw an exception. ---> <CrtImplementationDetails>.ModuleLoadException: The C++ module failed to load during appdomain initialization.
 ---> System.DllNotFoundException: dwrite.dll ---> System.ComponentModel.Win32Exception: Access is denied.
   --- End of inner exception stack trace ---
   at MS.Internal.NativeWPFDLLLoader.LoadDwrite()
   at CModuleInitialize.{ctor}(CModuleInitialize* , IntPtr cleaningUpFunc)
   at ?A0xf3e61052.CreateCModuleInitialize()
   at ?A0xf3e61052.??__E?A0xf3e61052@cmiStartupRunner@@YMXXZ()
   at _initterm_m((fnptr)* pfbegin, (fnptr)* pfend)
   at <CrtImplementationDetails>.LanguageSupport.InitializePerAppDomain(LanguageSupport* )
   at <CrtImplementationDetails>.LanguageSupport._Initialize(LanguageSupport* )
   at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
   --- End of inner exception stack trace ---
   at <CrtImplementationDetails>.ThrowModuleLoadException(String errorMessage, Exception innerException)
   at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
   at .cctor()
   --- End of inner exception stack trace ---
   at System.Windows.Application.ApplicationInit()
   at System.Windows.Application..cctor()
   --- End of inner exception stack trace ---
   at System.Windows.Application..ctor()
   at PackageExplorer.App..ctor() in D:\a\1\s\PackageExplorer\App.xaml.cs:line 25
   at PackageExplorer.App.Main()

Are there any workarounds? no
Is there a version in which it did work?
I get the same error in the zipped release of version <IP_ADDRESS>. I do not get the error when running version 4.6.26.
Is there a package on Nuget.org which shows the bug?
Bug is not related to a specific nuget package

Is this from the Store or Chocolatey?

Microsoft Store. I'm using Windows 10 Education (1809).

Okay, interesting, will look into it.

Digging, but can you try the chocolatey version?

Chocolately version (5.0.78) results in the same error.

Okay, thanks for the confirmation. That rules out vcredist-related issues.

I just tried this on a fresh installation of Win10 1809 x64 Education Edition, and both the Store version and the Chocolatey  one seems to launch without any problems for me.
Would you mind getting a Time Travel trace of the crash with Loader snaps enabled for NugetPackageExplorer.exe (preferably, the non-Appx version)?
You can install Windbg Preview from the Store  which has Time Travel capture functionality.
You'll need gflags.exe  to enable loader snaps - you'll find this option in the Image File tab. Make sure you are using 32-bit version of gflags.exe when targeting a 32-bit process for debugging.  Alternatively, you can do this manually by creating the following registry keys and values:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\nugetpackageexplorer.exe

Set REG_DWORD value GlobalFlag to 0x2.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\nugetpackageexplorer.exe

Set REG_DWORD value GlobalFlag to 0x2.

Remember to delete these registry keys after collecting the trace.


Set pre_start_required to false in get_device_plugin_options

Signed-off-by: johnsonshih<EMAIL_ADDRESS>What this PR does / why we need it:
Set pre_start_required to false in get_device_plugin_options to match the setting in register()
Special notes for your reviewer:
If applicable:

[ ] this PR has an associated PR with documentation in akri-docs
[ ] this PR contains unit tests
[ ] added code adheres to standard Rust formatting (cargo fmt)
[ ] code builds properly (cargo build)
[ ] code is free of common mistakes (cargo clippy)
[ ] all Akri tests succeed (cargo test)
[ ] inline documentation builds (cargo doc)
[ ] all commits pass the DCO bot check by being signed off -- see the failing DCO check for instructions on how to retroactively sign commits

@johnsonshih can you provide some context on why this change is desired?

@johnsonshih can you provide some context on why this change is desired and the anticipated impact?

We set pre_start_required to false when akri instance device plugin registers itself to kubelet but kubelet still calls get_device_plugin_options to decide if to call device plugin's pre_start_container()  In get_device_plugin_options(), we return true for pre_start_required so kubelet calls pre_start_container().  We don't expect the pre_start_container() to be called so we dump an error message and return empty option.  Since we don't want the pre_start_container() to be called, we should set pre_start_required to false in get_device_plugin_options().

/add-same-version-label


Inconsistent conditional result types (with more than one zone)

Description
I get same issue as #39 and #47 but for zone. It works with only one zone defined, adding a second zone in a simple configuration
Returns:

│ Error: Inconsistent conditional result types
│
│   on ..../modules/zones/main.tf line 2, in resource "aws_route53_zone" "this":
│    2:   for_each = var.create ? var.zones : tomap({})
│     ├────────────────
│     │ var.zones is object with 2 attributes
│
│ The true result value has the wrong type: element types must all match for
│ conversion to map.

Versions

Module version: 2.8.1

Terraform version: 1.2.2

Provider version(s): registry.terraform.io/hashicorp/aws v4.12.0

Reproduction Code
module "route53_hz_root" {
  source  = "terraform-aws-modules/route53/aws//modules/zones"
  version = "2.8.1"

  zones =  {
    "domain1.net" = {
      comment = "Production Base hosted zone"
      tags    = {
        "Environment" = "prod"
      }
    }
    "domain2.net" = {
      comment = "Production Base hosted zone"
      tags    = {
        "Environment" = "prod"
      }
    }
  }

  tags = {
    Terraform = "true"
  }
}

Steps to reproduce the behavior:
step1: apply this config with one zone:
module "route53_hz_root" {
  source  = "terraform-aws-modules/route53/aws//modules/zones"
  version = "2.8.1"

  zones =  {
    "domain1.net" = {
      comment = "Production Base hosted zone"
      tags    = {
        "Environment" = "prod"
      }
    }
  }

  tags = {
    Terraform = "true"
  }
}

step2: Then change as above (Reproduction Code) and apply.
Additional context
Probably also for zones will work the same solution as records: changing tomap({}) to {} will solve the issue.
Note: wrapping var.zone inside tomap({...}) allow to create hosted zones but this is not a clean solution. Not sure if tied to this issue but every change in any of the zone destroy and recreate every subzones based on root zones also if zone id remains the same.

This issue has been resolved in version 2.8.2 :tada:

I could not reproduce this issue with the provided steps but nevertheless I have fixed for_each in #74 . Please try the updated version - v2.8.2.

Hi @antonbabenko,
this worked for me. Thak you !


use Symfony HttpClient as client

This should solve issue #246

CI is wrong, HttpClient is fine with Symfony 3.4 too.
I'll change travis configuration to avoid failing

Not, it won't work with any project that requires symfony/symfony with a lower version.
Also, you're forcing this choice on the end user, cutting him off from the possibility to replace the client, or at least without the possibility of dropping that dependency.

I can't see any conflict between symfony/http-client and symfony/symfony.
About forcing the choice, you already did that when you required sdk. As mentioned in related issue, I'm for allowing the broader choice and not forcing user to any implementation, but it looks like "simplicity" is more important than choice

You're right, symfony/symfony will not conflict as it is. But we're still missing the necessary package to inject the client in the HTTPlug discovery process, right?

Latest version of php-http/discovery is able to discover it
(BTW, failing tests in travis look unrelated)

Latest version of php-http/discovery is able to discover it

Then you should lock against it (^1.7 seems to be the right version)

I fear that CI failures are not unrelated... It's halting on Symfony Request signature, which is NOT coming from 3.4, but 4.4:
https://travis-ci.org/getsentry/sentry-symfony/jobs/632285363#L776

Downgrading symfony/http-foundation (v4.4.2 => v4.4.0): Loading from cache

Can you try to run tests on a local environment? On mine, all tests are green 🤔

I see "changes requested" but without any note. Is there something left to do?

But you can replace this client too, I can't see any difference. The only difference is that this client is a Symfony component, so it's likely already required in a Symfony project.

No, you can't replace it as a dependency, in this way it will be always installed, you can only leave it unused; that is a problem if it creates a conflict with a third package, for example.
And, since Flex, you can no longer give that for granted as installed.

I don't get you, what is the reason that keeps you from replacing?

With sentry/sdk you have a meta package that you can replace in your composer.json to avoid installing the suggested transport altogether; with your approach, you do not have that meta package to replace anymore.

Closing as solved by #327


RSS Fix: Do not convert protocol relative URLs

closes #5567

Fixed an issue with protocol relative URLs in the RSS feed
Such URLs should be kept as-is and not prefixed with baseUrl
Added corresponding test to cover this case

Not sure why #5576 was closed? If you're having trouble, ask and we'll help!

Hi @ErisDS, I tried to use the _.startsWith(attributeValue, '//') as suggested by @halfdan, however it throws an error:
Error: Cannot find module 'lodash.startswith'
Therefore I switched to an alternative method as described in:
http://stackoverflow.com/a/4579228
Please check the new pull request and see if it's OK. Thank you.

Travis build URL: https://travis-ci.org/TryGhost/Ghost/builds/71443115

Tests are failing because we aren't using the latest version of lodash - which I'm updating in #5580.

Our version of lodash is now updated in master. If you rebase this branch against master, the startsWith function should work for you.

Thanks @ErisDS. Actually in my commit I used an alternative method to achieve it. Is that OK? Or do you still want me to change it to use the startsWith function?

Sorry, I missed that and had thought the other PR was needed. This looks good :+1:


Trouble closing and releasing a library with the plugin

When I after I publish my library to Nexus (using publishAllPublicationsToSonatypeRepository) and try to close the repo and release it using either closeAndReleaseSonatypeStagingRepository, closeAndReleaseStagingRepository, or closeSonatypeStagingRepository + releaseSonatypeStagingRepository, I always get this error:
No staging repository with name sonatype created

What could be the cause of this?
Thanks so much!
I'm using version 1.0.0 of the plugin, and this is my build.gradle.kts: https://gist.github.com/2dd5c1ef88fe5d1205e7c4954dbbb1a3

Looks like that's working, thanks!

I also believe I've found the problem: I was using a sonatype block in the nexusPublishing function, instead of using create("loottables") (loottables is my artifact ID).

sonatype should be fine. It defines a publishing repository (name) which you use in publishToNAME* tasks.

Yes, my bad.

Looks like that's working, thanks!

Glad it hear, closing.


Fix typo containing vulgar language

Changes

Fix typo containing vulgar language

Checks
By submitting your pull request for review, you agree to the following:

[x] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[x] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[x] To the best of my knowledge, all proposed changes are accurate.

Thanks for catching this!


[bug] build release with offlineInstaller failed, download MicrosoftEdgeWebView2RuntimeInstallerX64.exe got 404.

Describe the bug
date: 2023/07/21
link: https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/aa5fd9b3-dc11-4cbc-8343-a50f57b311e1/MicrosoftEdgeWebView2RuntimeInstallerX64.exe

yarn run v1.22.19
$ tauri info

[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 114.0.1823.67
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.70.0 (90c541806 2023-05-31)
    ✔ Cargo: 1.70.0 (ec8a8a0ca 2023-04-25)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.16.1
    - yarn: 1.22.19
    - npm: 9.5.1

[-] Packages
    - tauri [RUST]: 1.4.1
    - tauri-build [RUST]: 1.4.0
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.2
    - @tauri-apps/api [NPM]: 1.4.0
    - @tauri-apps/cli [NPM]: 1.4.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
Done in 11.32s.

Yes, It's ok now, Maybe It's my network problem... sorry, close it.

same issue

Hello, why am I still making this error

Hello, why am I still making this error

I have the same issue in Azure Pipelines.

same issue

How did solve you it


Cannot boot a Windows ISO image from cdrom using HAXM accelerator in QEMU

Running the following command:

qemu-system-x86_64 -accel hax -cdrom Windows2016.iso -m 4095M

Yields the following error message in the virtual machine:

CDBOOT: Couldn't find BOOTMGR

QEMU reports:

HAX is working and emulator runs in fast virt mode.

Running the same command with -accel tcg works as expected.
Qemu version:
QEMU emulator version 2.11.0
Intel HAXM version:
v6.2.1
Environment:
Intel Core i7-7820HQ
Virtualization in BIOS enabled
Windows 10 64-bit
Hyper-V disabled

I have the same issue and also am not able to boot an XP guest with haxm acceleration.

@nevilad Have you tried passing a sufficiently large guest memory size? E.g. try passing -m 1G.
This should make Windows 10 work with TCG, i.e. -accel tcg. Unfortunately, HAXM still doesn't support Windows 10 images.

Yes the problem was in memory size, using a higher value helped.
I have analyzed running Windows 10 under qemu+hax, and found this.

Running Windows 10 x86 fails with unhandled vmexit type 9, which stands for TSS switch.
At boot, APIC (advanced programmable interrupt controller) starts in compatibility mode and the processor in real mode. In this mode the processor reserves interrupt vectors from 0 to 6. APIC is mapped by early boot code to generate it's interrupts starting with vector 8. In protected mode, there are 32 processor reserved interrupt vectors, and APIC should be remapped to generate it's interrupts starting vector 32.
In windows 7 this occurs, but in windows 10 I don't see the remap process in the logs (write to ports 0x20 and 0x21). After switching to protected mode, the first APIC-generated timer interrupt, which has vector 8, is handled as a double fault. It's IDT descriptor is a task-gate descriptor, meaning that before executing the handler, the processor must switch tasks. This generates a vmexit and the VM stops. The double fault handler should show a bluescreen.
So there are 2 errors - absense of APIC remapping and absense of support of windows bluescreens. I implemented the code for handling task switches, but am unable to test it, since after switching another timer event occurs and it crashes.
I've tried to run it in TCG mode with qemu 2.12 x32 and 3.1 x64, and it hangs. Have somebody started it in TCG mode? I don't see these errors in qemu issues. I started it at a windows 10 host.
There is another strange thing - I expected that the loader in real mode prepares all needed data, switches to protected mode and continues. But there are a lot of entrys to\exits from protected mode, so maybe this is the problem.

Running Windows 10 x64 fails with a triple fault. The last executed instruction is a breakpoint instruction (CC opcode), it is running with IRQL HIGH_LEVEL, which is used to Machine checks and catastrophic errors. Seems that windows failed to do some checks and stopped in such a way. I was not able yet to find out what are these checks.
Short before the fault, windows begins to write\read CR8. I implemented handling of CR8 read\writes but it didn't help.
Qemu in TCG mode runs without errors.
The questions are:

was this really a concious decision to halt by the OS?
when so, why wasn't it a bluescreen, or there are errors in it's support too?
why is the error code triple fault, which means "delivery of double fault encountered an exception"?

VM exits when an interrupt is signaled by the hardware. HAXM does not redirect it to the OS handler. Is this OK?
I've tried to run windows10 x64 in TCG mode with qemu 2.12 x32 and 3.1 x64, and it hangs. Have somebody started it in TCG mode?

I was able to run it in TCG mode with changing the processor to core2Duo or Nehalem.


One to many relationships in both directions

Given these entities:
interface Department : Entity<Department> {
val id: Int
var name: String
var location: String
}
interface Employee : Entity<Employee> {
val id: Int?
 var name: String
 var job: String
 var manager: Employee?
var hireDate: LocalDate
 var salary: Long
 var department: Department
}

The Employee has a reference to the Department and I understand from the docs that when fetching Employees a join will be done to get the Department as well. What about the other way - can we have in Department a list of Employees?
interface Department : Entity<Department> {
val id: Int
var name: String
var location: String
var employees: List<Employee>
}

Right now I'm doing it by a findList{}.

大佬牛批，中文不容易搜到该问题，有木有啥论坛或者什么的可以供大家讨论🙈  @vincentlauvlwj

@gsy13213009 有问题可以直接在 GitHub issue 上提，论坛的话，我比较常上的是 Kotlin 中文社区的论坛，也可以在上面 @ 我 https://discuss.kotliner.cn/


function_clause when adding owner

When adding an owner to my hex package with the latest 6.6.0 rebar3_hex plugin and rebar3 3.11.1, I get a function_clause error adding an owner:
$ DEBUG=1 rebar3 hex owner add erl_cache<EMAIL_ADDRESS>===> Evaluating config script "rebar.config.script"
===> Load global config file /Users/nal/.config/rebar3/rebar.config
===> <IP_ADDRESS> satisfies the requirement for minimum OTP version 18
===> Expanded command sequence to be run: []
===> Provider: {default,do}
===> Expanded command sequence to be run: [{hex,owner}]
===> Provider: {hex,owner}
===> Uncaught error in rebar_core. Run with DEBUG=1 to see stacktrace or consult rebar3.crashdump
===> Uncaught error: function_clause
===> Stack trace to the error location:
[{hex_api_package_owner,add,
                        [#{api_key => undefined,api_organization => undefined,
                           api_repository => undefined,
                           api_url => <<"https://hex.pm/api">>,
                           http_adapter => r3_hex_http_httpc,
                           http_adapter_config => #{profile => rebar},
                           http_etag => undefined,
                           http_user_agent_fragment =>
                               <<"(rebar3/3.11.1) (httpc)">>,
                           name => <<"hexpm">>,
                           read_key => <<_>>,
                           repo_key => undefined,repo_name => <<"hexpm">>,
                           repo_organization => undefined,
                           repo_public_key =>
                               <<"-----BEGIN PUBLIC KEY-----\n____\n-----END PUBLIC KEY-----">>,
                           repo_url => <<"https://repo.hex.pm">>,
                           repo_verify => true,repo_verify_origin => true,
                           username =><EMAIL_ADDRESS>                           write_key =>
                               {<<_>>,
                                {<<_>>,
                                 <<_>>}}},
<EMAIL_ADDRESS>                        [{file,"/Users/nal/.cache/rebar3/plugins/hex_core/src/hex_api_package_owner.erl"},
                         {line,26}]},
 {rebar3_hex_owner,add,4,
                   [{file,"/Users/nal/.cache/rebar3/plugins/rebar3_hex/src/rebar3_hex_owner.erl"},
                    {line,69}]},
 {rebar3_hex_owner,handle_command,2,
                   [{file,"/Users/nal/.cache/rebar3/plugins/rebar3_hex/src/rebar3_hex_owner.erl"},
                    {line,42}]},
 {rebar_core,do,2,
             [{file,"/Users/nal/src/rebar3/src/rebar_core.erl"},{line,154}]},
 {rebar_prv_do,do_task,5,
               [{file,"/Users/nal/src/rebar3/src/rebar_prv_do.erl"},
                {line,87}]},
 {rebar_core,do,2,
             [{file,"/Users/nal/src/rebar3/src/rebar_core.erl"},{line,154}]},
 {rebar3,run_aux,2,[{file,"/Users/nal/src/rebar3/src/rebar3.erl"},{line,178}]},
 {rebar3,main,1,[{file,"/Users/nal/src/rebar3/src/rebar3.erl"},{line,66}]}]
===> When submitting a bug report, please include the output of `rebar3 report "your command"`

It seems like this is because the args are passed to hex_api_package_owner:add as strings, but that function, at least in hex_cor 0.5.0, expects binaries via guards.
Other info:
rebar3 plugins list:
$ DEBUG=1 rebar3 plugins list
===> Evaluating config script "rebar.config.script"
===> Load global config file /Users/nal/.config/rebar3/rebar.config
===> <IP_ADDRESS> satisfies the requirement for minimum OTP version 18
===> Expanded command sequence to be run: []
===> Provider: {default,do}
===> Expanded command sequence to be run: [{plugins,list}]
===> Provider: {plugins,list}
--- Global plugins ---
rebar3_hex (6.6.0)

rebar3 report output:
$ rebar3 report "rebar3 hex owner add erl_cache<EMAIL_ADDRESS>Rebar3 report
 version 3.11.1
 generated at 2019-06-17T16:24:36+00:00
=================
Please submit this along with your issue at https://github.com/erlang/rebar3/issues (and feel free to edit out private information, if any)
-----------------
Task: rebar3
Entered as:
  rebar3 hex owner add erl_cache<EMAIL_ADDRESS>-----------------
Operating System: x86_64-apple-darwin18.2.0
ERTS: Erlang/OTP 20 [erts-<IP_ADDRESS>] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [hipe] [kernel-poll:false]
Root Directory: /Users/nal/bin/kerl.d/<IP_ADDRESS>
Library directory: /Users/nal/bin/kerl.d/<IP_ADDRESS>/lib
-----------------
Loaded Applications:
bbmustache: 1.6.1
certifi: 2.5.1
cf: 0.2.2
common_test: 1.15.4
compiler: <IP_ADDRESS>
crypto: <IP_ADDRESS>
cth_readable: 1.4.4
dialyzer: 3.2.4
edoc: 0.9.2
erlware_commons: 1.3.1
eunit: 2.3.5
eunit_formatters: 0.5.0
getopt: 1.0.1
hipe: 3.17.1
inets: <IP_ADDRESS>
kernel: <IP_ADDRESS>
providers: 1.8.1
public_key: 1.5.2
relx: 3.32.1
sasl: 3.1.2
snmp: 5.2.11
ssl_verify_fun: 1.1.5
stdlib: <IP_ADDRESS>
syntax_tools: <IP_ADDRESS>
tools: 2.11.2

-----------------
Escript path: /Users/nal/bin/rebar3
Providers:
  app_discovery as clean compile compile cover ct cut deps dialyzer do docs edoc escriptize eunit get-deps help install install_deps key list lock new owner path pkgs publish release relup repo report repos retire revert search shell state tar tree unlock update upgrade upgrade upgrade user version xref

I believe I know what's causing this problem; I shall have a fix soon.

@nalundgaard what version of rebar3_hex are you using?

@starbelly I was pinned to the latest when I found this issue, 6.6.0.It seems that it also is broken in the same way from 6.0.0, from what I can see. I reverted to v2.5.0 and that solved my problem for now.


Callback when changed

Hi,
what is the best method to make a callback when a value has changed, to maybe make an ajax call to update my database?
Kind regards, Yuri

The input event is the way to go here.
I suggest updating your data in a form submit to reduce the number of ajax calls to your server. If your server can handle it you can update your data at every change by a user but that's your design choice.


Explore places within the city

As a user, I want Traveldiction to provide recommendations for different places within the city to explore and make the best out of the trip , as i am already visiting the city so i want to visit all the possible best places within in the city and make the most of my trip. .


Incorrect message shown @ landing

Install addon, create component with documentation, start app.
The documentation for the component is generated and sent in meta.json but the It looks like you haven't generated your app's documentation yet. message is displayed.

Fixed in v2.0.0 Release


Update pre-release version package as pre-release on NPM

The can package shows the pre-release as the latest on NPM

How do you do this?

Based on https://docs.npmjs.com/misc/semver#prerelease-tags we would do something like 2.3.0-alpha.11
Though it seems like we are doing it correctly.  Based on the comments at:
https://github.com/npm/node-semver/blob/master/semver.js#L62
https://github.com/npm/node-semver/blob/master/semver.js#L75
our releases should be considered pre-release.

I think it's a command line flag for npm publish

We will make sure that we do official pre-releases in the next minor/major version.


Unable to Connect to Pub/Sub

I am unable to connect to a Pub/Sub service. I've tried on three separate accounts, all with Pub/Sub enabled, and for each I get "Internal Error".
require "json"
project = ENV["PUBSUB_PROJECT"]
keyfile = JSON.parse File.read ENV["PUBSUB_KEYFILE"]

require "signet/oauth_2/client"
options = {
  token_credential_uri: "https://accounts.google.com/o/oauth2/token",
  audience: "https://accounts.google.com/o/oauth2/token",
  scope: ["https://www.googleapis.com/auth/pubsub",
          "https://www.googleapis.com/auth/cloud-platform"],
  issuer: keyfile["client_email"],
  signing_key: OpenSSL::PKey::RSA.new(keyfile["private_key"]) }
signet = Signet::OAuth2::Client.new options
signet.fetch_access_token!

require "google/api_client"
client = Google::APIClient.new application_name: "blowmage",
                               application_version: "1.0.0"
client.authorization = signet
pubsub = client.discovered_api "pubsub", "v1beta2"

client.execute api_method: pubsub.projects.topics.list,
               parameters: { project: "projects/#{project}" }

This returns a 500 response with the following JSON:
{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "internalError",
    "message": "Internal Error"
   }
  ],
  "code": 500,
  "message": "Internal Error"
 }
}

Am I missing something in this code? Is Pub/Sub v1beta2 known to work?

It looks like google_api_client is using the wrong URLs for connecting to Pub/Sub v1beta2. In my previous code example, you can inspect the API method's uri_template value to see the URL that it is using:
pubsub.projects.topics.list.uri_template.pattern #=> "https://www.googleapis.com/v1beta2/{+project}/topics"

The API call works when we monkey-patch that method to point to the URL that the documentation specifies:
t = pubsub.projects.topics.list.uri_template
def t.pattern
  "https://pubsub.googleapis.com/v1beta2/{+project}/topics"
end

client.execute api_method: pubsub.projects.topics.list,
               parameters: { project: "projects/#{project}" } #=> success!

This seems odd to me because the discovery JSON is clearly using "https://pubsub.googleapis.com/" and not "https://www.googleapis.com/". Is there something else going on in google_api_client that is causing this?

I compiled the gem locally and commit 1ed677b796afad92b5f232165912ab269c0b4b8a seems to have fixed this. Is work on using the discovery document's baseUrl/rootUrl completed? Any word on when a new version with this fix will be released?

Hey Mike, that commit should be ready to release but I'm not sure about when a new version will be released.
@tbetbetbe Can we release 0.8.6 to get the rootUrl fix released?

Hey remi! Long time! :)

Some more observations. pubsub.projects.subscriptions.acknowledge hits the URL
https://pubsub.googleapis.com/projects/#{project}/subscriptions/#{subscription_name}:acknowledge, but note the missing /v1beta2 from the URL in the documentation. The pattern in uri_template.pattern is "{+subscription}:acknowledge".
Compare to pubsub.projects.topics.list which hits the URL "https://pubsub.googleapis.com/v1beta2/projects/#{project}/topics" with the pattern in uri_template.pattern having the full URL "https://pubsub.googleapis.com/v1beta2/{+project}/topics".
I'm stuck on other issues ATM, but from what I've seen so far I would not expect the calls to pubsub.projects.subscriptions.acknowledge, pubsub.projects.subscriptions.pull, or pubsub.projects.topics.publish to work as is.

I only tested pubsub.projects.topics.list to start with.  Are you looking into fixes for these discovered methods?  Let me know if not and I'll dive in and we can make sure all discovered methods work.

I've got some other things taking my attention ATM, but I'll take a look at these discovered methods tomorrow morning. I would assume that using the discovery document's baseUrl instead of rootUrl would fix it.

Looks like its method_base.join(Addressable::URI.parse(@discovery_document['path'])) that's hurting us.
>> require "addressable/uri"
>> uri = Addressable::URI.parse "{+topic}:publish"
>> uri.scheme
=> "{+topic}"
>> uri.path
=> "publish"

Because "{+topic}:publish" has a scheme (thanks to its ":") it doesn't join with the method_base resulting in our uri_template being simply "{+topic}:publish" instead of the expected full "https://pubsub.googleapis.com/v1beta2/{+topic}:publish"
This seems fair, so I updated our method #uri_template builder to use method_base (eg. "https://pubsub.googleapis.com/v1beta2/") + "./" + @discovery_document['path']

Ah, that makes more sense. :)


CLOUD-52739 Read write capabilities for SSSD configs

@akanto plz review

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2219/


Alignement requirements quesiton.

Hi,
AFAIK, AESNI and potentially other primitives require that the encryption blocks are properly aligned. Are alignment requirements described/handled by rust-crypto? How would I go about making a best possible job for plain text, cipher destination, iv and everything else? Do they always have to be "block size" aligned or are there more nuances there?

Interesting.  It's unclear to me from the .asm or .c files if or how they handle this, but if so its built into the compiler's handling of the inline assembly for SSE instructions.  Appears Rust does not yet offer #[repr(align=16)], so nothing easy one can do from Rust.  It's probably worth adding tests to aesni.rs that try badly aligned keys, etc.


When importing PSSDiag output folder xel files with syntax errors cause ReadTrace to error and stop

Having a syntax error in a query recorded by a PSSDiag session causes the ReadTrace import of the xel files to crash if the syntax error is an unclosed quotation mark - ie a missing ' (single apostrophe)
A query like
Select Col1, Col2
From MyTable as t
Where t.Col1 like 'Jonathan
or
Select Col1, Col2
From MyTable as t
Where t.Col2 = 4 and (Col1 like 'Jonathan%)
causes Readtrace output as

04/14/20 15:57:38.230 [0X000003C4] Session: 63 Request: 0 Seq:<PHONE_NUMBER> [Error: 110003][State: 0][Abs Char: 313][Seq: 0] SYNTAX ERROR: String is missing proper closing quote near (Char Pos: 0x189 Byte Pos: 0x312)
… … … …
This is frequently caused by an embedded NULL, incorrect escaping, smart quotes or incorrect syntax from the original trace event.

SSMS can open the xel file without any errors and if you create a filter on the sql_statement column then you can search for "(Col1 like 'Jonathan" and the offending events are shown.
There seem to be 4 events recorded per query. When sorted by event_sequence they are:

name
message
transaction_id
result

error_reported
Incorrect syntax near 'jonathan'.
[tranid]
Null

error_reported
Unclosed quotation mark after the character string ') '.
[tranid]
Null

sql_batch_starting
Null
Null
Null

sql_batch_completed
Null
Null
Error

The Readtrace error causes the entire import to fail, regardless of how many records remain in the current file or other xel files exist to be imported.
It would be excellent if this sort of error (which seems to be known about as there is a ReadTrace message suggesting it) was written out to the log file (along with perhaps the event_sequence or the transaction_id so that it can be precisely found via SSMS) but further processing of the xel content continues without disturbance.

Hello @Jonathan-Quilter . Thank you for the issue.
This issue seems related to ReadTrace.exe (RML Utilities) and not SQLNexus technically.
What version of RML Utilities are you using on your system? (look at the details of ReadTrace.exe)
I wonder if you need to download the latest version of RML Utils.

Hi, thanks for the message.
Readtrace.exe in RMLUtils version is <IP_ADDRESS>

Thanks @Jonathan-Quilter   - looks like you have an up-dated version. We will work on reproducing this issue and report it to the folks who work on RML Utilities.
Unfortunately, for now I can offer workarounds to manually analyze the data via queries after you import the data into a table:

Obviously you have discovered that XEL files can be opened successfully in SSMS and from there you can export the XEL into a table

https://docs.microsoft.com/en-us/sql/relational-databases/extended-events/advanced-viewing-of-target-data-from-extended-events-in-sql-server

You can also use sys.fn_xe_file_target_read_file() to import into a table directly.
And at the bottom of this blog post you can find a sample on how to analyze via Xpath queries.

@Jonathan-Quilter , can you point out how you got this build installed? Did you install it via DEA  https://www.microsoft.com/en-us/download/details.aspx?id=54090?
We don't seem to be able to reproduce based on the description. We ran a query with an unclosed quote in the WHERE clause and the XEL imports fine. Can you provide a specific repro - perhaps there is a missing detail.
@prmadhes-msft FYI

Hi, I didn't build the server where I was running the analysis but I have asked my colleague and you are correct, the Readtrace.exe was installed via DEA.

Where is the RML Utilities repo so that I can log the bug there please?

RML Utilities is not open-source and not posted on Github. I have informed the engineer who maintains it about this issue. But after we tried several times to reproduce the crash with the latest version you have, we are unable to do so. If you have a SQL trace or specific steps that you can provide to recreate the problem, it would be very helpful to advance this forward.


Not hitting break points in Hazel code

Visual studio is not able to hit break points set in code in the Hazel project. It can hit breakpoints in the Sandbox app but not in the Engine.
This seems to be because the generated PDB file is not accessible to the running executable (Sandbox.exe) so it can not load the debugging symbols.
The simple solution is to add an additional post build command step to copy the file over. Something like:
("{COPY} ../bin/" .. outputdir .. "/Hazel/Hazel.pdb" .. " ../bin/" .. outputdir .. "/%{prj.name}")
to the premake5.lua file.
I would make a PR however in the repo's current state it will probably have the same issue as pointed out here. Both this new post command step and the original DLL copy should be moved to the Sandbox project section of the lua file. Because of this I'll just leave it as a suggestion for a future fix.

Closing since this has been resolved.


docs: update tetragon logos in docs where necessary

Fixes: #1623

Thanks a lot for doing this 🙏 , I have some comments though:

It would be great to replace all the favicons without the "Tetragon" text. Just the logo.
The aliasing sometimes looks completely off on the main logo in the top left corner, I'm not sure we use a SVG here but that could explain, maybe it's better to have a bitmap file like a png for this use case. It's not really problematic we can still fix this later.

Then nits: this one is not centered, and we would need to redo the main image or make it less big but that's maybe out of scope:

Got it! I'll replace the favicons with the logo containing just the shield. For the logo on top, I'll switch it to a png and see if it changes.
The hero logo needs to be reworked to fit the landing page and also the one on the getting started docs page too. I tried to adjust it with css but it just wouldn't centralize.

Got it! I'll replace the favicons with the logo containing just the shield. For the logo on top, I'll switch it to a png and see if it changes.

Thanks that's nice!

The hero logo needs to be reworked to fit the landing page and also the one on the getting started docs page too. I tried to adjust it with css but it just wouldn't centralize.

yeah don't spend time and worry about that we'll do that later :)


Unix socket for postgresql not supported

I wanted to connect to local postgres using a Unix socket. Unfortunately it doesn't seem to be supported.

Thanks. I'll look at this when I can, or if you'd like to open a PR it would probably be a tweak of this file: https://github.com/bitmagnet-io/bitmagnet/blob/main/internal/database/postgres/config.go

I was wrong. The socket can be used, but by pointing POSTGRES_HOST at the directory, not the socket itself.
So for example POSTGRES_HOST=/var/run/postgresql/ works fine. Maybe worth including in the docs.

Seconding that documenting that the socket is supported like this would be very useful. Connecting with a socket allows for local peer based authentication