Fix sawtooth transaction list command bug

Before this PR, "sawtooth_xo", or "mktplace.transactions.market_place" etc TransactionFamilies loaded, when using "sawtooth transaction list" command, it would crash. Throws "update = trans_info["Update"] KeyError: 'Update'" error. This PR fixes the bug.

@boydjohnson I updated this PR, please review.


click twice on anchor remove the active state

step 1: click on anchor (active added)
step 2: click again on the same anchor (active toggle)
https://gadzan.github.io/generatoc/demo/

Thanks, I have fixed the issue, pls try 😉

Great :) Thanks!


What is the flow of the incident

Hi All,
Just wanted to know the flow of the incident, what happens when we create the incident and how to implement the escalation matrix for the incident.
From the flow means, as soon as an incident is created, create a slack channel, then email the commander like that, where we can define all of this.
I am not able to identify it from the docs, I am checking this:- https://netflix.github.io/dispatch/docs/administration

Hi, @tarunmittal24 the flow itself is largely not configurable (i.e. the given order of things happening). What you can configure is if a certain resource is created. For example, if you disable the slack plugin no incident conversation will be created.
If you have not already I'd also encourage you to take a look at our original blog post:
https://netflixtechblog.com/introducing-dispatch-da4b8a2a8072
Some of the specifics are out of date but the overall methodology hasn't really changed.


[SOLVED - update deployed] Depreciated notice

Hi there, I'm a brand new user of your CMS. Just downloaded and set up a playground.
I got this error:
Deprecated: Non-static method wCMS::_updateOtherFiles() should not be called statically on line 37.
Changing line 13 to read:
public static function _updateOtherFiles() {
This appears to have fixed the problem without breaking anything else.

Hello embdashbuck, welcome and thanks for reporting this. Push is fixed to all WonderCMS users, log out and log back in to see the notification for the update.
Cheers!


Provide a latest vanity release.

Name of the Distribution
All
Version of the Distribution
Stable and Preview
Package Types

[X] Deb
[X] RPM
[X] Tar.gz
[ ] Snap - Stop! Please file your issue in PowerShell-Snap instead.

Processor Architecture
All
.NET Core Support

[X] The version and architecture of the Distribution is supported by .NET Core.

Distribution Requirements

[X] The version of the Distribution is supported for at least one year.
[X] The version of the Distribution is not an interim release or equivalent.

Exemption Justification
This refers to all releases.
Progress

[ ] An issue has been filed to create a Docker image in PowerShell-Docker

For PowerShell Team ONLY

[ ] Docker image created
[ ] Docker image published
[ ] Distribution tested
[ ] Update packages.microsoft.com deployment
[ ] Lifecycle updated
[ ] Documentation Updated

This is for documentation like https://en.opensuse.org/PowerShell#Install_Dependencies, where it cannot be feasibly updated every time PowerShell releases a new version. Precedent exists for such vanity links, especially within GitHub Releases.

It's a bit confusing that you've framed your issue as a distribution request and that the issue's title talks about a release.
That said, it would indeed be useful to have abstract download links that refer to whatever release is current at the time, using a format such as:
https://aka.ms/powershell-release/download/{release-type}/{os}/{arch}[/{option}]

where:

{release-type} is one of: lts, stable, preview, and perhaps even daily
{os} is win, osx, ...
{arch} is x64, arm64, ...
an optional {option} segment to target special binaries such as the ones whose release file names contain fxDependent and msixbundle

which could automatically be translated into the corresponding specific binary file name as listed at https://github.com/PowerShell/PowerShell/releases

You are able to use the https://github.com/PowerShell/PowerShell/releases/tag/v<VERSION>/<SPECIFIC PACKAGE> to get to the release you may need, i.e https://github.com/PowerShell/PowerShell/releases/download/v7.3.7/powershell-7.3.7-1.cm.x86_64.rpm. Does that meet your scenarios?

We also have  https://aka.ms/PowerShell-Release?tag=v<VERSION> that takes you to the releases page.

@StevenBucher98, assuming I understand the intent of this issue correctly:

It is about direct download links that can be used in installation commands - https://aka.ms/PowerShell-Release?tag=v<VERSION> links aren't direct download links, but my suggestion above was to use a https://aka.ms/powershell-release prefix for the yet-to-be-implemented vanity links.

NOT having to specify an explicit version number is precisely what motivated the issue: instead, abstract identifiers should dynamically refer to whatever release is the current one in the specified channel (LTS, stable, preview, daily).

That way, published installation instructions (such as the ones linked to in the initial post for openSUSE) that currently contain explicit version numbers wouldn't need updating with every new release (or wouldn't become obsolete).

See my previous comment for details on how this might be implemented.

Gotcha missed the "latest" part of the issue, unfortunately we don't have that at the moment but would be good to have in the future, I'll see if there is some kind of automation we can use to set this up but may be tricky to do with our currently release pipelines

Whilst vanity urls for downloading releases would be great for those that want/need to have their own installation mechanisms, personally I think that we should be raising better awareness of the various install-powershell scripts in the tools folder in this repo. As not only can they remove the need for custom install mechanisms they can take care of all dependency issues too & reduce admin overheads too.
Which kinda helps with this ask too, albeit in a different way entirely & as it also helps take care of installation too & whilst aren't officially documented (yet) as install methods, perhaps @StevenBucher98 we can look at getting them documented properly and not just in the repo.
Especially as the https://aka.ms/install-powershell.ps1 script & it's counter part of the install-powershell.sh script are already available via https://aka.ms/install-powershell.sh
Also I've added some additional updates in this PR to the install-powershell.ps1 script (which yes needs some form of PowerShell installed already to run) & have blogged a bit about some of this in Installing PowerShell Side by Side for testing purposes which may be of help going forward/
Also as a complete aside I just tested on the latest OpenSUSE Leap 15.5 WSL distro & I was able to get pwsh installed using this oneliner bash <(wget -O - https://raw.githubusercontent.com/PowerShell/PowerShell/master/tools/installpsh-suse.sh)  (from the installpsh-suse.sh script in the tools folder)
Once PowerShell was installed I was then run the following to get the Preview release (same as how I had blogged above)
Invoke-Expression "& {$(Invoke-RestMethod https://raw.githubusercontent.com/kilasuit/PowerShell/update-install-powershell-script/tools/install-powershell.ps1)} -Preview"
Then run this to install the LTS release too
Invoke-Expression "& {$(Invoke-RestMethod https://raw.githubusercontent.com/kilasuit/PowerShell/update-install-powershell-script/tools/install-powershell.ps1)} -LTS" to install the LTS release too
(as I noted in my blog post - this https://raw.githubusercontent.com/kilasuit/PowerShell/update-install-powershell-script/tools/install-powershell.ps1 is just until the above linked PR is merged.
@RokeJulianLockhart does all of the above help you in the meantime prior to there being an available vanity url sometime in the future?

No, because they're not RPMs. Unlike on Windows, most Linux users aren't used to running discrete installers with non-obvious behaviour. Installing with an RPM integrates with the system package management solutions.
Thanks though.

hi @RokeJulianLockhart :
I have maintained a powershell installation shell script, you may like it:

Enable ssh winrm simultaneously
Simultaneously enable root + password login.
This is not safe, a shutdown script is provided.
https://gitee.com/chuanjiao10/kasini3000_agent_linux

kasini3000 is a Better Powershell Batch Operation and Maintenance Framework than Ansible

I recommend having deb and rpm for each distribution and architecture in https://packages.microsoft.com/
Then if you install the repository configuration you get the appropriate version with dependencies using the existing apt or yum commands.
This does have problems, for instance there is a conflict between the dotnet provided by the base ubuntu repository and that provided by https://packages.microsoft.com/.


Documentation: Automate infra views (Read Only)

User Story
In order to release automate infra views end user documentation required with following context:

What is automate infra views
Uses of automate infra views
Steps to perform by user to connect with chef server.
How are the data/info user can access for read only views release.

Covered in #4826


Move removal of uncaughtException handler into end callback

And only attach it initially within start. Since self.uncaught is a bound function, "removing" it immediately before adding it only prevents the same instance from leaking multiple handles - it still allows multiple runners to leak handles forever, even when those runners runs have ended (resulting in an issue akin to #4144).
Description of the Change
Essentially, it seems like mocha 8 regressed #4144, but the test added in #4147 didn't seem to catch it, I'm guessing because now the process of of attaching the handlers during .run was deferred in some fashion by another change.

Sounds like @weswigham won't have time to work on this, so I can pick it up unless someone beats me to it.

@weswigham I think v8.2.1 corrected a similar problem... I'm going to give it a shot against typescript.

ref: microsoft/typescript#41403 microsoft/typescript#41404


Added a noise volume slider and statistics for today

To address issue: https://github.com/lazy-guy/tomodoro/issues/1

Also addressed https://github.com/lazy-guy/tomodoro/issues/3

This seems to work perfectly. Thanks for the changes.
Merging.


Dang thing doesn't seem to know what a namespace is

The following lil script
require 'bundler/setup'
require 'papercraft'

module Namespaced
  Title = ->(title) { h1 title }
end

layout = Papercraft.html { |title|
  html5 {
    head { Namespaced::Title(title) }
  }
}

puts layout.render("Title content")

Yields this:
dazmin@Desmonds-MacBook-Pro ~ % ruby example.rb
example.rb:11:in `block (3 levels) in <main>': undefined method `Title' for Namespaced:Module (NoMethodError)
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/tags.rb:33:in `instance_eval'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/tags.rb:33:in `head'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/tags.rb:171:in `method_missing'
        from example.rb:11:in `block (2 levels) in '
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/tags.rb:33:in `instance_eval'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/tags.rb:33:in `html'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/tags.rb:171:in `method_missing'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/html.rb:28:in `html5'
        from example.rb:10:in `block in '
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/template.rb:123:in `instance_exec'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/template.rb:123:in `block in render'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/renderer.rb:88:in `instance_eval'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/renderer.rb:88:in `initialize'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/tags.rb:52:in `initialize'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/template.rb:121:in `new'
        from /Users/dazmin/.local/share/rubies/ruby-3.1.1/lib/ruby/gems/3.1.0/gems/papercraft-0.24/lib/papercraft/template.rb:121:in `render'
        from example.rb:15:in `'
dazmin@Desmonds-MacBook-Pro ~ %

Then we got this:
require 'bundler/setup'
require 'papercraft'

module Namespaced
  Title = ->(title) { h1 title }

  Layout = Papercraft.html { |title|
      html5 {
        head { Title(title) }
      }
    }
end

puts Namespaced::Layout.render("Title content")

Which gives:
<!DOCTYPE html><Title>Title content</Title>

Which I think is a different problem?
Yeah, so I think the problems are:

You can't use a namespaced constant.
You can't use a constant in the same namespace as you unless you're chillin in the root namespace.

I tried to trace what was going on, but when I tucked into the gem it was quickly clear that you are playing this game on another level than me.

Papercraft does not currently support namespaced constants as components.


Uncaught Validation Exception

Describe the bug
When validating a response, AJV can throw (an uncaught) exception, causing Prism to hang. We've been using examples and we're seeing an unhandled promise rejection from the AJV validate used here
~We've also noticed the error appears slightly differently depending on if I run Prism from an npm global package:~
<Error from 3.2.1 Redacted, 3.2.2 gives the same error message shown below>
~But, if we build from source, we get an error in a different spot. But we were able to at least see that it was a validation error.~
Here's the exception we're seeing:
(node:53106) UnhandledPromiseRejectionWarning: TypeError: Cannot assign to read only property 'areaCode' of object '#<Object>'
    at validate (eval at localCompile (/Users/andrew.bell/workspace/prism/node_modules/ajv/lib/compile/index.js:120:26), <anonymous>:3:29309)
    at pipeable_1.pipe.O.mapNullable.validate (/Users/andrew.bell/workspace/prism/packages/http/src/validator/validators/utils.ts:39:7)
    at /Users/andrew.bell/workspace/prism/node_modules/fp-ts/lib/Option.js:356:77
    at Object.pipe (/Users/andrew.bell/workspace/prism/node_modules/fp-ts/lib/pipeable.js:13:26)
    at Object.exports.validateAgainstSchema (/Users/andrew.bell/workspace/prism/packages/http/src/validator/validators/utils.ts:36:3)
    at pipeable_1.pipe.O.fold (/Users/andrew.bell/workspace/prism/packages/http/src/validator/validators/body.ts:111:19)
    at /Users/andrew.bell/workspace/prism/node_modules/fp-ts/lib/Option.js:87:49
    at Object.pipe (/Users/andrew.bell/workspace/prism/node_modules/fp-ts/lib/pipeable.js:13:23)
    at pipeable_1.pipe.O.fold (/Users/andrew.bell/workspace/prism/packages/http/src/validator/validators/body.ts:105:11)
    at /Users/andrew.bell/workspace/prism/node_modules/fp-ts/lib/Option.js:87:60

In both situations, an HTTP response is not returned, and the server hangs.
To Reproduce
~Unfortunately, I have not been able to reproduce this externally. I'm unsure what is different about our spec that would cause this behavior.~ See below for example spec
Expected behavior
Exception to be caught and added to the list of validation errors.
Environment (remove any that are not applicable):

Library version: 3.2.2
OS: OSX Mojave 10.14.6

Additional context
I took a very amateur shot at fixing by wrapping the validate call with an O.tryCatch. This prevented Prism from hanging, but (understandably) doesn't add the validation error. Added here
Thank you for taking a look! If you have any suggestions for implementation, I can take a shot at a fix.

@AndrewBell Would it be possible to share with us the offending document?

Unfortunately it's very large and full of IP. I've been trying to re-create a 'petstore' example, but haven't had any luck. I'll try to see if I can't recreate, if not maybe someone else runs into this too.

Thanks for your patience, I was able to extract a failing example. You'll see at the end areaCode. The int is rightly invalid (schema defines as a string), but when I try to get a mocked response for this endpoint, Prism hangs. If I correct it to a String, it works fine.
Still seeing the same error as above, although I'll note that once I upgraded my npm version of prism, it no longer gave me the target.split error, and instead returns the same Cannot assign to read only property 'areaCode' of object '#<Object>' as I see when building and running from source.
openapi: 3.0.2
info:
  contact:
    email<EMAIL_ADDRESS>  title: "Example API"
  version: 1.0.0
paths:
  /v1/addresses:
    get:
      description: 'A description'
      operationId: v1.getAddresses
      responses:
        200:
          $ref: '#/components/responses/GetAddressesOk'
components:
  responses:
    GetAddressesOk:
      content:
        application/json:
          examples:
            Phone:
              description: Stubbed response containing only Phone type Addresses
              value:
                results:
                - $ref: '#/components/examples/Phone'
          schema:
            properties:
              results:
                items:
                  discriminator:
                    propertyName: addressType
                  oneOf:
                  - $ref: '#/components/schemas/PhoneNumber'
                type: array
            required:
            - results
            type: object
      description: Successful operation
  schemas:
    AddressType:
      description: 'Address Type'
      enum:
      - PHONE_NUMBER
      - EMAIL_ADDRESS
      - POSTAL_ADDRESS
      type: string
    Address:
      description: A set of information used to locate someone or something
      properties:
        addressType:
          allOf:
          - $ref: '#/components/schemas/AddressType'
          description: The type of address
        id:
          description: 'The unique identifier of the address.'
          format: uuid
          readOnly: true
          type: string
    PhoneNumber:
      allOf:
      - $ref: '#/components/schemas/Address'
      - properties:
          areaCode:
            type: string
          phoneNumber:
            type: string
        required:
        - phoneNumber
        type: object
      description: The sequence of digits used to connect to a specific telephone
  examples:
    Phone:
      id: 3face8ee-0000-0000-0000-d4d75640cefc
      addressType: PHONE_NUMBER
      phoneType: MOBILE
      # Comment/Uncomment below to trigger exception
      areaCode: 206 # Invalid property - causes Prism to hang
      # areaCode: "206" # Valid property - Prism behaves as expected
      phoneNumber: "2064147850"

Ok I think I've been able to identify the problem; ajv is trying to overwrite the source object with something. Most likely it's trying to coerce the 206 from number to string because of the schema definition. We should handle this gracefully.

@AndrewBell #905 should fix it. Can you pull the branch down and try it out?

That did the trick, I confirmed with both the shared example and the problem spec. I can see the errors coming through on the header as well. Thanks for the quick turnaround, and let me know if there's anything else I can do to help!

Keep using Prism :trollface:


Update README screenshots + text (after design is implemented)

After the redesign is implemented we need to:

[ ] Update text in README
[ ] Update the screenshots in the README

That way we have consistent text/images for the README and published site.

Blocked until we have the final design implemented.


Upgrade jacoco-maven-plugin 0.8.11 -> 0.8.12

This PR contains the following updates:

Package
Type
Update
Change

jacoco-maven-plugin (source)
build
patch
0.8.11 -> 0.8.12

Release Notes

jacoco/jacoco (jacoco-maven-plugin)
v0.8.12: 0.8.12
Compare Source
New Features

JaCoCo now officially supports Java 22 (GitHub #1596).
Experimental support for Java 23 class files (GitHub #1553).

Fixed bugs

Branches added by the Kotlin compiler for functions with default arguments and having more than 32 parameters are filtered out during generation of report (GitHub #1556).
Branch added by the Kotlin compiler version 1.5.0 and above for reading from lateinit property is filtered out during generation of report (GitHub #1568).

Non-functional Changes

JaCoCo now depends on ASM 9.7 (GitHub #1600).

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade jacoco-maven-plugin 0.8.11 -> 0.8.12

See:
- https://github.com/jacoco/jacoco/releases/tag/v0.8.12
- https://github.com/jacoco/jacoco/compare/v0.8.11...v0.8.12


Network SDK with API version 2018-05-01

Based on: https://github.com/Azure/azure-rest-api-specs/pull/3089

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

hi @dsgouda please review new major SDK version. Address all the comments for me so I can help with the fixes


Add Homebrew packaging instructions

Also had to change azure-multiapi-storage from 0.1.3 to 0.1.4 as 0.1.3 was a bad source distribution that was fixed in 0.1.4.

Only merge this once https://github.com/Homebrew/homebrew-core/pull/17344 has been merged as then we know the Homebrew instructions are good.

@derekbekoe - Once this is merged, please ping me so that I can update the install instructions page.


npm issues on PRs

Description of the issue
I saw this on two PRs today:
https://github.com/quantumlib/Cirq/runs/3011265236
https://github.com/quantumlib/Cirq/pull/4004/checks?check_run_id=3011531826
Run check/npm ci
npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>

npm ERR!

It is probably related to https://github.com/actions/setup-node/issues/268

@95-martin-orion Can this issue be closed now?


exception behavior on latest frida

deadloop in original method invoke。

i found the cause is frida 14 and frida 12 has diffrent behavior in method invoke logic in js. example
xxx.fun.implementation = function() {}
//after this
xxx.fun();  // will call hooked method in frida14 and call original method in frida12

maybe that's why deadloop happend. sorry for english, i will track at https://github.com/frida/frida-java-bridge/issues/202

i found the cause is frida 14 and frida 12 has diffrent behavior in method invoke logic in js. example
xxx.fun.implementation = function() {}
//after this
xxx.fun();  // will call hooked method in frida14 and call original method in frida12

maybe that's why deadloop happend. sorry for english, i will track at https://github.com/frida/frida-java-bridge/issues/202


Can not make install success

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

$ go version
go version go1.15.6 darwin/amd64

What go env you are?

$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/miasto/Library/Caches/go-build"
GOENV="/Users/miasto/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/miasto/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/miasto/go"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/miasto/go/src/github.com/gojp/goreportcard/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/gl/8npwgrx17s1cw983_3lgjyqw0000gn/T/go-build109703931=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

$ go get github.com/gojp/goreportcard
$ cd $GOPATH/src/github.com/gojp/goreportcard
$ make install

What did you expect to see?
no error and build successed
What did you see instead?

./scripts/make-install.sh
go: github.com/alecthomas/gometalinter upgrade => v3.0.0+incompatible
go: finding module for package gopkg.in/alecthomas/kingpin.v3-unstable
go: finding module for package github.com/google/shlex
go: found github.com/google/shlex in github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510
go: found gopkg.in/alecthomas/kingpin.v3-unstable in gopkg.in/alecthomas/kingpin.v3-unstable v3.0.0-20191105091915-95d230a53780
go: finding module for package github.com/alecthomas/units
go: finding module for package github.com/nicksnyder/go-i18n/i18n
go: found github.com/alecthomas/units in github.com/alecthomas/units v0.0.0-20201120081800-1786d5ef83d4
go: found github.com/nicksnyder/go-i18n/i18n in github.com/nicksnyder/go-i18n v1.10.1
# github.com/alecthomas/gometalinter
../../../../pkg/mod/github.com/alecthomas/gometalinter@v3.0.0+incompatible/main.go:36:94: cannot use loadConfig (type func(*kingpin.Application, *kingpin.ParseElement, *kingpin.ParseContext) error) as type kingpin.Action in argument to app.cmdMixin.flagGroup.Flag("config", "Load JSON configuration from file.").Envar("GOMETALINTER_CONFIG").Action
../../../../pkg/mod/github.com/alecthomas/gometalinter@v3.0.0+incompatible/main.go:38:100: cannot use disableAction (type func(*kingpin.Application, *kingpin.ParseElement, *kingpin.ParseContext) error) as type kingpin.Action in argument to app.cmdMixin.flagGroup.Flag("disable", "Disable previously enabled linters.").PlaceHolder("LINTER").Short('D').Action
../../../../pkg/mod/github.com/alecthomas/gometalinter@v3.0.0+incompatible/main.go:39:99: cannot use enableAction (type func(*kingpin.Application, *kingpin.ParseElement, *kingpin.ParseContext) error) as type kingpin.Action in argument to app.cmdMixin.flagGroup.Flag("enable", "Enable previously disabled linters.").PlaceHolder("LINTER").Short('E').Action
../../../../pkg/mod/github.com/alecthomas/gometalinter@v3.0.0+incompatible/main.go:40:83: cannot use cliLinterOverrides (type func(*kingpin.Application, *kingpin.ParseElement, *kingpin.ParseContext) error) as type kingpin.Action in argument to app.cmdMixin.flagGroup.Flag("linter", "Define a linter.").PlaceHolder("NAME:COMMAND:PATTERN").Action
../../../../pkg/mod/github.com/alecthomas/gometalinter@v3.0.0+incompatible/main.go:43:56: cannot use disableAllAction (type func(*kingpin.Application, *kingpin.ParseElement, *kingpin.ParseContext) error) as type kingpin.Action in argument to app.cmdMixin.flagGroup.Flag("disable-all", "Disable all linters.").Action
../../../../pkg/mod/github.com/alecthomas/gometalinter@v3.0.0+incompatible/main.go:44:54: cannot use enableAllAction (type func(*kingpin.Application, *kingpin.ParseElement, *kingpin.ParseContext) error) as type kingpin.Action in argument to app.cmdMixin.flagGroup.Flag("enable-all", "Enable all linters.").Action
../../../../pkg/mod/github.com/alecthomas/gometalinter@v3.0.0+incompatible/main.go:200:12: cannot use loadDefaultConfig (type func(*kingpin.Application, *kingpin.ParseElement, *kingpin.ParseContext) error) as type kingpin.Action in argument to app.Action
./scripts/make-install.sh: line 4: gometalinter: command not found
make: *** [install] Error 127

had similar issue, This Stackoverflow answer solves it
maybe we need to add this to documentation on setup

had similar issue, This Stackoverflow answer solves it
maybe we need to add this to documentation on setup

@JonSnow47 I think this is fixed with a recent change pinning gometalinter to a version that works. Let me know if it's still broken for you.

Feel free to reopen if this doesn't work still.

@JonSnow47 I think this is fixed with a recent change pinning gometalinter to a version that works. Let me know if it's still broken for you.

It's works.


Improved TypeScript types & type tests, for better type inference

A scaled down version of #118, only updating the itty-router.d.ts file:
Summary of type changes:

Router<Request, Methods> -> Router<{ methodExtension: Methods }>
Request defaults to the current global Request, any extension can be made via declaration merging

This significantly improves the type behavior, and eliminates the need to specify the Request on individual route handlers

Additional features:

Auto-inference of type params /some/:path/:id? -> req.params is { path: string, id?: string | undefined } without any additional work
Auto-inference of the appropriate HTTP method on the req.method property
Ability to supply the handler args Router<{ handlerArgs: [Env, ExecutionContext] }>, which means they'll be typed correctly both on .handle, and on all route handlers automatically
Ability to enforce the return-type of the handler via Router<{ handlerReturn: Response }>

Used to catch cases where you are accidentally returning something unexpected, typically you'd want Response | void if you support passthrough handlers, but it defaults to any to match current behavior

Nothing Cloudflare specific in the types, added test cases to ensure the proper behavior of the Request is as expected when the @cloudflare/workers-types are in the global scope
Adds a ton of positive & negative test-assertions for the expected types

I'm in the middle of a massive overhaul, bringing extras into core, with a full rewrite in TS... I need to tease this issue/PR back apart to see how to proceed, but no matter what, I'd like to be able to merge something so you end up on the contributors list :)
I'll let you know if I need it dialed back so we can get your name on the board... stay tuned!

I'm gonna close this for now, as v3 is out (with a complete TS overhaul), but feel free to reopen to discuss further, or hop on Discord (ideally) to continue the conversation there! :)


Look into content-type for python gRPC library

It currently adds a +proto which is in-spec but unsupported by google

This was the service not being deployed


Ctrl+A is globally hijacked by the transfer window

Ctrl+A is hijacked by the transfer window when open.
Does not appear to apply to the recall window.
Repro Steps:

Open the Waapi Transfer Window
Transfer something to Wwise
Attempt to Ctrl+A in another application (try notepad for example)
Note that Waapi Transfer window still accepts Ctrl+A commands
Note that upon closing Transfer Window, Ctrl+A works again in other applications

https://github.com/karltechno/Reaper-Waapi-Transfer/commit/ea4e2b5255678ba01d069da5c881a613b9b54f7d Fixed in this commit.


Execution speed is much slower than CPU in MacBook Pro?

In my MacBook Pro(Mid 2015), Execution speed in AMD Radeon R9 M370X Compute Engine is much slower than CPU(2.5 GHz Intel Core i7). Is this normal?

GPU:

python multilayer_perceptron.py
Extracting /tmp/data/train-images-idx3-ubyte.gz
Extracting /tmp/data/train-labels-idx1-ubyte.gz
Extracting /tmp/data/t10k-images-idx3-ubyte.gz
Extracting /tmp/data/t10k-labels-idx1-ubyte.gz
OpenCL platform: Apple
OpenCL device: AMD Radeon R9 M370X Compute Engine
I tensorflow/core/common_runtime/gpu/gpu_device.cc:989] Found device 0 with properties:
name: AMD Radeon R9 M370X Compute Engine
major: -1 minor: -1 memoryClockRate (GHz) 800
pciBusID 0000.0000
Total memory: 2.00GiB
Free memory: 512.00MiB
I tensorflow/core/common_runtime/gpu/gpu_device.cc:877] cannot enable peer access from device ordinal 0 to device ordinal 0
I tensorflow/core/common_runtime/gpu/gpu_device.cc:1011] DMA: 0
I tensorflow/core/common_runtime/gpu/gpu_device.cc:1021] 0:   N
I tensorflow/core/common_runtime/gpu/gpu_device.cc:1083] Creating TensorFlow device (/gpu:0) -> (device: 0, name: AMD Radeon R9 M370X Compute Engine, pci bus id: 0000.0000)
cl_driver DeviceAllocate 327155712
Epoch: 0001 cost=<PHONE_NUMBER>81
Epoch: 0002 cost= 41.912425166
Epoch: 0003 cost= 26.223643868
Optimization Finished!
Accuracy: 0.913713
epoch_times [14.012919187545776, 12.755515336990356, 12.597593069076538]
average_epoch_times= 12.676554203 kernel_compile_time 1.33636498451

real	0m42.142s
user	0m31.954s
sys	0m18.096s
CPU:
QiangdeMacBook-Pro:3_NeuralNetworks elife$ time python multilayer_perceptron.py
Extracting /tmp/data/train-images-idx3-ubyte.gz
Extracting /tmp/data/train-labels-idx1-ubyte.gz
Extracting /tmp/data/t10k-images-idx3-ubyte.gz
Extracting /tmp/data/t10k-labels-idx1-ubyte.gz
2017-10-16 15:53:15.945534: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.2 instructions, but these are available on your machine and could speed up CPU computations.
2017-10-16 15:53:15.945553: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX instructions, but these are available on your machine and could speed up CPU computations.
2017-10-16 15:53:15.945568: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX2 instructions, but these are available on your machine and could speed up CPU computations.
2017-10-16 15:53:15.945572: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use FMA instructions, but these are available on your machine and could speed up CPU computations.
Epoch: 0001 cost=333.116085219
Epoch: 0002 cost=97.091073028
Epoch: 0003 cost=71.633393175
Epoch: 0004 cost=58.102855900
Epoch: 0005 cost=48.550296390
Epoch: 0006 cost=43.879424709
Epoch: 0007 cost=38.416489090
Epoch: 0008 cost=35.230118899
Epoch: 0009 cost=32.181227765
Epoch: 0010 cost=30.920996809
Epoch: 0011 cost=28.272015703
Epoch: 0012 cost=26.596986358
Epoch: 0013 cost=25.029801500
Epoch: 0014 cost=23.558648788
Epoch: 0015 cost=22.414703977
Optimization Finished!
Accuracy: 0.8971
real	0m32.758s
user	2m15.099s
sys	0m10.327s

Bitcoin mining
Data courtesy CompuBench
Radeon R9 M370X Mac
111.14 mHash/s
CompuBench 1.5 (Bitcoin mining)
Data courtesy CompuBench
Core i7 4870HQ
30.62 mHash/s

Face detection
Data courtesy CompuBench
Radeon R9 M370X Mac
25.65 mPixels/s
CompuBench 1.5 (Face detection)
Core i7 4870HQ
18.08 mPixels/s

It is. Since all convolutions are running on the CPU currently. I never quite got around to attaching https://github.com/hughperkins/coriander-dnn to tf-coriander, so convolutions are on the cpu currently. If someone has a moment, would be good to get that working. Happy to provide guidance, meet in Google Hangouts etc, if anyone wants to take a look at that.

@hughperkins, I'm open to try as i'm working to get a 560 running on high sierra via gpu


[GDScript 2.0] [regression] Godot hangs while parsing complex match expression

Godot version
master #fb176d5f6e6dc2b43c630a041a8ab7d737173ec4
System information
manjaro linux
Issue description
following script:
var y
func foo(x):
	match x:
		1 + 1:
			pass
		[1,2,[1,{1:2,2:var z,..,}]]:
			pass
		1 if true else 2:
			pass
		1 or 2 and 1:
			pass
		1 < 2:
			pass
		1 | 1:
			pass
		1 >> 1:
			pass
		1, 2 or 3, 4:
			pass
		_:
			pass

causes Godot hanging, while it was working fine in Godot 3.x
Steps to reproduce
compile
Minimal reproduction project
No response

Sounds related to #50865


Error with directories

Thanks for this, it looks really good.
All was working in VSCode for me, until I moved my `.puml files into a sub directory (named v2.0.0), and then renamed the subfolder. I saw an error like this:
><EMAIL_ADDRESS>watch C:\Users\**\source\repos\**-doc-architecture-roadmap
> node index.js

[13:05:45] Generating C:\Users\**\source\repos\**-doc-architecture-roadmap\diagrams\1.2 Overview .png
[13:05:45] Generating C:\Users\**\source\repos\**-doc-architecture-roadmap\diagrams\1.2 Overview Alpha.2.png
[13:05:45] Generating C:\Users\**\source\repos\**-doc-architecture-roadmap\diagrams\1.2.png
[13:05:45] Generating C:\Users\**\source\repos\**-doc-architecture-roadmap\diagrams\v2.png
[13:05:45] Generating C:\Users\**\source\repos\**-doc-architecture-roadmap\diagrams\v1.1.png
[13:06:45] Generating C:\Users\**\source\repos\**-doc-architecture-roadmap\docs\v2.0.0.png
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: EISDIR: illegal operation on a directory, read
Emitted 'error' event at:
    at lazyFs.read (internal/fs/streams.js:165:12)
    at FSReqWrap.wrapper [as oncomplete] (fs.js:462:17)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>watch: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>watch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\**\AppData\Roaming\npm-cache\_logs\2020-10-27T13_06_45_858Z-debug.log
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command npm run watch" terminated with exit code: 1.

In an earlier version of the comment it sounded like you'd also found a fix. Is that something you could submit as a pull request?

Resolved by #3.


Configure separate token-credentials-id for use with buildchain

Adding a new configuration option to specify in branch.yaml config, like:
buildchain_config:
  git:
    repository: incubator-kie-kogito-pipelines
    file_path: .ci/pull-request-config.yaml
    # the new one
    token_credentials_id: a-token

It will be used in Jenkinsfile.buildchain which is used across repositories.

apache/incubator-kie-kogito-pipelines#1103
apache/incubator-kie-drools#5546

apache/incubator-kie-optaplanner#2999

Applied on all configurations.


[SPARK-49409][CONNECT] Adjust the default value of CONNECT_SESSION_PLAN_CACHE_SIZE

What changes were proposed in this pull request?

Set the default value of CONNECT_SESSION_PLAN_CACHE_SIZE to 16 which was previously 5.
Why are the changes needed?

There is a rare use case where a data frame is built from multiple dependent data frames, and while creating the last dependent data frame, all the other dependent data frames are invalidated from the plan cache, causing them to be analysed again. For this particular case, the performance of creating the data frame was improved from 41 minutes to 1 minute.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Performance test.
Was this patch authored or co-authored using generative AI tooling?

No.

Merging to master


Pub/Sub: add shared-config and fix lint

Fixes #3433

Lint
#
# pubsub/streaming-analytics
#

[ERROR] src/main/java/com/examples/pubsub/streaming/PubSubToGCS.java:[17] (whitespace) EmptyLineSeparator: 'import' should be separated from previous statement.
[ERROR] src/main/java/com/examples/pubsub/streaming/PubSubToGCS.java:[31,14] (naming) AbbreviationAsWordInName: Abbreviation in name 'PubSubToGCS' must contain no more than '2' consecutive capital letters.
[ERROR] src/main/java/com/examples/pubsub/streaming/PubSubToGCS.java:[36,20] (naming) AbbreviationAsWordInName: Abbreviation in name 'PubSubToGCSOptions' must contain no more than '2' consecutive capital letters.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1:check (default-cli) on project pubsub-streaming: You have 3 Checkstyle violations. -> [Help 1]


"dotnet new fusee" doesn't handle dashes correctly

When using "dotnet new fusee" in a directory with dashes (e.g. Fusee-Test), the resulting launch.json will contain "Fusee_Test.dll" in the args field for the Fusee Player. The dll will build to "Fusee-Test.dll".

https://github.com/dotnet/templating/issues/1168


Creating fraction in an exponent produces additional symbols

To Reproduce
Steps to reproduce the behavior:

Type x
Type ^
Type 1
Type /
Additional symbols are appered.

Expected behavior
There are no any additional symbols.
Screenshots

I think the problem is here:
if (current.AtomIndex == _insertionIndex.AtomIndex) {

and here
MathList.RemoveAtoms(
              new MathListRange(current, _insertionIndex.AtomIndex - current.AtomIndex));

It looks a bit complicated. Isn't enough to use numerator.Count?
if (numerator.Count == 0) {

MathList.RemoveAtoms(new MathListRange(current, numerator.Count));

Cross-link to corresponding issue in MathEditor: https://github.com/kostub/MathEditor/issues/18


Controller specs

In this Milestone, I made the following additions ➕ ➕ 🟢

Set up tests on User and Post controllers.

Added request spec for Users controller
Added request spec for Posts controller
Fixed Linter errors🧰

I appreciate your efforts, @thecodechaser 🙏🏿


[SECURITY] Credential leak vector

#224 introduces a potential vector for credentials to be leaked via HTTP basic authentication.
In order

Accidentally submitted prior to completing the description. In order to ensure that users are emailed the full description, I have re-submitted this issue as #230.


Re-add docs for rust-lang/rust

Docs were removed in #408, but I think it is worthwhile to not assign everything to Mark.
This is somewhat blocked on #409 to work correctly.

@GuillaumeGomez Are you OK with being added here?
@JohnTitor Would you be willing to be added to the list for docs?

I don't have a ton of bandwidth, but I can always reassign within a day or two if I can't get to it.

@JohnTitor Would you be willing to be added to the list for docs?

I'm happy to!

Sounds good to me as well!


Core June Beta Release

I think we want #5681 for this release as well, and it might be good to also Beta the #5676 (if we want and if it is ready at least for the Beta).
I wouldn't mind #5691 either.
#5680, #5682, and #5662 are nice to haves, but they likely won't be ready for this release (including that they most likely were not planned for this release).

I support shipping core with what's in main from eod yesterday rather than rushing the design conversations. And we'd continue with the open PRs after the June release milestone, once they are good and ready.


create function to determine whether a dataset can be visualized

This would make sense to be a function within MinervaModel.js that inspects the minerva metadata, as @kotfic suggested.
The line if dataset.geoJsonAvailable in dataPanel.jade should be changed to call this new function.

See: https://github.com/Kitware/minerva/blob/master/web_external/js/MinervaModel.js#L12-L26


allow providing plural translations as array in translation file

after merging this, one is able to define the plural translation as an array.
after merging this, one is able to have the delimiter as part of the translation in plural cases.
this pull request does not break bc.
thx :)

Codecov Report

Merging #7 into master will increase coverage by 0.19%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master       #7      +/-   ##
============================================
+ Coverage     69.49%   69.68%   +0.19%
- Complexity      224      225       +1
============================================
  Files             3        3
  Lines           318      320       +2
============================================
+ Hits            221      223       +2
  Misses           97       97

Impacted Files
Coverage Δ
Complexity Δ

src/Translate.php
67.37% <100%> (+0.23%)
198 <0> (+1)
:arrow_up:

Continue to review full report at Codecov.

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

awesome. thank you!
<3


EVERYONE use https://github.com/joonhocho/react-native-google-sign-in repo, this one not working with cocoapods

Everyone use https://github.com/joonhocho/react-native-google-sign-in repo, this one not working with cocoapods.
For example if you want to use https://github.com/react-community/react-native-maps and this repo at the same time in your project it's not possible.
Tested with this:
https://github.com/joonhocho/react-native-google-sign-in
Everything works good!

What to do if I have already used react-native-google-signin and now want to move to react-native-google-sign-in?


I can't see my favorite galleries

I can't see my favorite galleries

My phone:
— Samsumg Galaxy S4
— Android 4.2.2
— Armv7

Also have this problem.

Same... Very irritating.


Kisscartoon is now kimcartoon

kimcartoon.me is the new address

Any chance @wileyyugioh will save us guys??
 I've tried it with kisscartoon.io AND kimcartoon.me and neither work.

He's currently waiting on selenium with headless chrome to be released.

I think I'm going to put development on hold for a while. Kissanime is making it very troublesome to download videos, and with all the site developments such as the sketchy ads and video hosts using even more obfuscation, I'm not sure how stable the program will be even if it were to use a headless browser.


Solution for "Catch Error!" not working with forEach

it's probably a noob question, but why does this solution not work for the "catch error" excercise
function *upper (items) {
  items.forEach(function(item) {
    try {
      yield item.toUpperCase()
    } catch(e) {
      yield null
    }
  })
}

var bad_items = ['a', 'B', 1, 'c'];

for (var item of upper(bad_items)) {
  console.log(item);
}

Hi @kitwalker12, this is reasonable question and short answer is:
"You can use yield only inside first level of generators/iterators, nor in callbacks or other functions".
This is pretty similar question on stack overflow: Why won't yield return from within a .map callback?
You can find more clarifications there or ask here if it's still unclear.

thanks @isRuslan . explanation about the default iteration behavior was helpful.


Characterization: seconds or micro-seconds?

Here is the documentation of t1_circuits:
    Generates circuit for T1 measurement.
    Each circuit consists of an X gate, followed by a sequence of identity
    gates.

    Args:
       num_of_gates (list of integers): the number of identity gates in each
                                        circuit. Must be in an increasing
                                        order.
       gate_time (float): time in micro-seconds of running a single gate.
       qubits (list of integers): indices of the qubits whose T1 are
       to be measured.

    Returns:
       A list of QuantumCircuit
       xdata: a list of delay times in seconds

While gate_time is in micro-seconds, the unit of delay time is xdata are said to be seconds. I assume that this is incorrect, for xdata? The implementation itself does not convert between units.

Yes, the gate_time should just say "time for running a single gate" and xdata should be "a list of delay times in the same units as gate_time"


Signing Server: Health-Check OTP modal integration

Task Description
Previously we were doing health check for Signing Server without OTP, which is not the correct way.
We now want the user to punch in the OTP while performing health check(right after they press the next button).
The backend and the frontend mech changes for the same have been made. Only the OTP modal needs to be integrated on this screen in order to supply the entered OTP to the checkSignerHealth mechnamis.
https://github.com/bithyve/bitcoin-keeper/assets/17980466/63aa5448-fd6d-4902-9f35-709a60ed154d

Verified this issue on keeper app v 1.1.14(317)


debian-12 x86_32 workers fail due to old capnproto version

An example of a failing build can be seen at
https://ocaml.ci.dev/github/ocurrent/docker-base-images/commit/d91f3800a8897fd11753fd312f5ea11f240363bd/variant/debian-12-4.14_x86_32_opam-2.1/-/refs/pull/274/head
The relvent error is
# *** Uncaught exception ***
# kj/filesystem-disk-unix.c++:305: failed: ::fstat(fd, &stats): Value too large for defined data type

@benmandrew noted that this is the same problem discussed at
https://github.com/mirage/capnp-rpc/issues/273
@mtelvers pointed out that the problem here is simply that package repo for
debian 12 has not updated to use the fixed capnproto version (e.g., 1.0.2)
https://tracker.debian.org/pkg/capnproto .
I'm trying to get that update moved along, but in the meantime I believe we can
fix this by installing the latest release
in our images before running CI on them. Iiuc, https://github.com/ocurrent/ocaml-ci/pull/894 would have fixed the problem while waiting for the upstream updates, but it was closed because

it is preferable to not add patched system libraries in the CI

as per https://github.com/ocurrent/ocaml-ci/pull/894#issuecomment-1808344120
However, at this point a proper release is out, and in my view it is preferable to special case install of a package rather than to leave builds red, so I will prep a PR following that example but using the latest install.

Thanks to the debian IRC, TIL:

package versions are frozen for every debian stable release, so unless the fix can be backported non-destructively to 0.9.2, bookworm will not get it

So if we want to continue support this build target,our (non-exclusive) options are:

Install the latest version in our CI pipeline
Work towards, and wait for, a backport to 0.9.2

However, we have now been letting this build fail for months, iiuc, and it seems like everything is moving along ok. So maybe the best option is:

Just remove the tests for debian-12 on x86_32.

WDYT, @mtelvers?

These tests only fail for projects which use capnproto as that is the outdated package.  Therefore, I do not think we should disable the test as it will work on most projects.

Thanks, @mtelvers! Your comment here and discussion in slack helped me realize I mistook the scope of CIs effected by this error (I thought it was a problem with service infra running, rather than just a problem with the CI for our infra -- didin't look at the context of the failure enough obviously :)).
After discussion with Mark, I think the next place to look would be at the depext package: we can either install a workable version of capnproto (if its permissable to bypass the package manager) put an OS/arch conflict.

I've checked with the opam repo maintainers to be sure, and (Kate) confirmed there is no way to bypass the distro package manager in depext. So I think really our only option is either figuring how to ignore this target in our CI or how to get this dependency installed on the target.

Once deployed, #932 should remove the specious build failures, but the underlying problem persists. So I'm leaving this issue open to note the problem, even tho we don't have a clear way forward.

Not sure why it took me so long to hit on this solution, but for any project where this is an issue, just mark it as unavailable on debian-12 on x86_32 as per https://github.com/ocurrent/ocurrent-deployer/pull/223/commits/b60799f2acae3ee47e5c152c45cdcbf243d1d2d1
I think we wouldn't want this in the capnp package itself, because users can use the lib on that target with no problems so long as they install a more recent version of capnp first.


URLSync, handling both foreign ? and # params

When you go to http://algolia.github.io/instantsearch.js/?param=value#anchor,
the URL sync will lose the anchor (transform it in a param).

ah yes indeed we need to handle this case


Update CHANGELOG.md

Removal of all past node-postgres version change information, and note that we are in prerelease with version 0.9.0. No details added as this is the first release.

Should we include the initial differences between node-postgres and vertica-nodejs in this document (or another document in this repo), or should we keep that list of changes on the internal wiki for now?

We can just remove this file and track changes in https://github.com/vertica/vertica-nodejs/releases. See python client for example.

Should we include the initial differences between node-postgres and vertica-nodejs in this document (or another document in this repo), or should we keep that list of changes on the internal wiki for now?

I would say no. This isn't intended to be a next step from node-postgres, this is just our first release. There is no baseline, the differences that we describe would just be vertica-specific changes for the most part which instead is just whats going to be described in the usage/readme, etc.

We can just remove this file and track changes in https://github.com/vertica/vertica-nodejs/releases Github release note. See python client for example.
From https://zellwk.com/blog/publish-to-npm/:

This means publishing a package involves many steps. At the very least, you need to:
1.Run tests (if there are any)
2.Update version in package.json according to Semver
3.Create a git tag according to Semver
4.Push the package to Github
5.Push the package to npm
6.Create release notes for every update

I think that is the right thing to do. I've deleted this file instead of modifying it. We'll use github releases moving forward.


Intermittent 502 errors when accessing container behind Application Gateway

We are hosting a container based on this image in a VM in Azure. In front of the VM is Applicaton Gateway. Occasionally we get 502 Bad Gateway. For testing purpose we removed application code from the image and left just simple  static index.html file (Hello World) like in following Dockerfile.
To isolate the problem we tried packet capturing. That shows that every http request reaches the host but sometimes container just does not reply. Approximately 2/3 of requests get HTTP 200 response while 1/3 lack response. When that occurs App Gateway resets TCP connection and sends 502 to the client. When next request comes, App Gateway initiates a new 3-way handshake, establishes a connection and container responds with HTTP 200 again. Then after a while container does not respond and the whole circle repeats. Do you have any idea why container is not responding? Can you help me troubleshoot this issue?
When deployed directly to the IIS in host the application works well.
We've done detailed checks of App Gateway settings together with MS support engineers. Everything is done right.
Dockerfile:
#escape = `
FROM mcr.microsoft.com/dotnet/framework/aspnet:4.7.2-windowsservercore-ltsc2019
WORKDIR c:\prep
SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue'; $verbosePreference='Continue';"]
RUN Add-WindowsFeature WAS,WAS-Process-Model,  Web-Windows-Auth,Web-Digest-Auth, Web-Basic-Auth,WAS-Config-APIs, Web-Net-Ext45,NET-WCF-HTTP-Activation45,Web-Http-Redirect
COPY index.html c:\inetpub\wwwroot\index.html
EXPOSE 80

@shirhatti is there any update?

No idea. I'm closing this issue. Feel free to re-open if this issue persists.


ping/pong: received pong data frame is discarded

The received pong data is always None
pong_waiter = await ws.ping(data=custome_ping_data())
print(await pong_waiter)  # always None

It's because handler of OP_PONG always set result of the ping future to None:
https://github.com/aaugustin/websockets/blob/c4a4b6f45af607431c5707d56420bbaf471bbb6e/src/websockets/legacy/protocol.py#L1131
elif frame.opcode == OP_PONG:
    if frame.data in self.pings:
        # Sending a pong for only the most recent ping is legal.
        # Acknowledge all previous pings too in that case.
        ping_id = None
        ping_ids = []
        for ping_id, ping in self.pings.items():
            ping_ids.append(ping_id)
            if not ping.done():
                ping.set_result(None)
            if ping_id == frame.data:
                break

It could be something like this:
ping.set_result(frame.data if ping_id == frame.data else None)

So caller can check ping data in pong result if needed.
Yes if we put await pong_waiter right after ping() it's exactly same data that we send in ping, but this is not always the case.

That's a valid improvement request. I didn't expect demand for this — it took 9 years to get this request — but I don't see much harm in implementing it. It will be a backwards incompatible change.

+1
I also would like to see this :)
I think this is even mandatory to add latency ( https://github.com/aaugustin/websockets/issues/1195 ) , because eg. one could send the current timestamp as data and when receiving the pong calculate with this how long it took (or put any other data in ping that helps to identify when you sent this ping)
Do you have an ETA on when this may be added to the released version?

I tried to implement this and ran into a complication. WebSocketCommonProtocol.ping() accepts either str of bytes. If it receives a str, it encodes it to bytes.
If we want to return the payload of the pong that answered this ping to the user, then all options look bad :-(
(1) Always return bytes.
Then we have an asymmetry if the user does await ws.ping("<str>"). They receive the same value as bytes, UTF-8 encoded.
(2) Magically decode to str when it's UTF-8, else keep bytes.
I'm doing this in the logs. It isn't reliable. Since pings are usually short, too often, a binary string is accidentally valid UTF-8 and treated as a string. That might be acceptable in logs; definitely not in the public API.
(3) Memorize the type that was passed in and return str or bytes accordingly.
Unfortunately, this doesn't work in general. Example:

in a client, the user does await ws.ping("<str>")
websockets does await ws.ping(b"bytes") — the keepalive mechanism does this
the server chooses to answer only the second ping — this is explicitly allowed by the RFC
we get b"bytes" as the payload of the pong answering the "<str>" ping, and we cannot always return a str

(4) Like (3), but return None when a ping is acknowledged by a later pong, so there's no type mismatch.
This is the original suggestion (ping.set_result(frame.data if ping_id == frame.data else None)) but I'm a unclear on the justification ("So caller can check ping data in pong result if needed."). Could you clarify the use case?
I believe that this API breaks the Principle Of Least Astonishment i.e. "99.99% of the time, I get back the content of my ping, and in 0.01% of cases I get None; WTF?"

Not sure if this is what you mean with 2) , but ws4py does it like this:
https://github.com/Lawouach/WebSocket-for-Python/blob/a3e6d157b7bb1da1009e66aa750170f1c07aa143/ws4py/messaging.py#L12
(putting the bytes into PongControlMessage which I can do str(pong) to get the string.)
The usecase is the latency measurement as I wrote in my previous comment. With ws4py I simply put a timestamp into the "ping" and then receive the very same timestamp in the "pong" from the server. To find out how long the the whole process took, I simply can substract this timestamp from the current one, done ( and save this value in self.latency)

I just added a built-in solution to measure latency in #1195. For this use case, no further changes are needed.

Upon further thought, my initial answer was incorrect. If you need the payload that was sent in the ping when you receive a pong, the obvious solution is:
my_payload = "here's a cool payload!"
pong_waiter = await ws.ping(my_payload)
await pong_waiter
# here you still have `my_payload` available in a local variable

This embraces the coroutine-based design of websockets.

Now, if you don't want to do that, you can always fallback to the lower-level option of working with futures and callbacks. Here's one solution, among many others possibilities:

import functools

def do_something_on_pong(payload):
    ...

my_payload = "here's a cool payload!"
pong_waiter = await ws.ping(my_payload)
pong_waiter.add_done_callback(
    functools.partial(do_something_on_pong, my_payload))

If you wanted to implement latency measurement with this pattern in the current release of websockets (where it isn't built in), you could do this:

import time

def record_latency(ws, ping_sent_at):
    pong_rcvd_at = time.perf_counter()
    ws.latency = pong_rcvd_at - ping_sent_at

ping_sent_at = time.perf_counter()
pong_waiter = await ws.ping()
pong_waiter.add_done_callback(
    functools.partial(record_latency, ws, ping_sent_at))

(I didn't test that code but it shouldn't be too far from working code!)


Allow Ruby server interceptor to access response

These changes allow ruby ServerInterceptor to get access to response after the request is done. Currently, the behaviour is inconsistent as ClientInterceptor can access the response, while the server one receives nil. For our scenario it will allow making logging interceptor that can log responses.
@yashykt

@apolcyn did you have a chance to review this PR?

Why there is no response, it has been 7 month for a couple of lines of code


What are the DEPLOY files for?

Summary
I'm trying to Dockerize DNN, and in a perfect world I'd be able to just have the site come up running out of the box rather than coming up with the installation screen.
Extended description
What does the DEPLOY file do?  If I set up web.config with the appropriate connection strings, will it just run the installation or something?

I was told that they where for Web Platform Installer, but I have never used them...

That’s interesting and it looks like webPI is at least somewhat configurable using DSC. I’m already using DSC (courtesy @solthoth @kenmaglio) to configure IIS, so I wonder if this could be extended.

@fsiler I have a feeling, this is not 'issue ready'. May I sugggest we close this issue and start a discussion on https://dnncommunity.org/forums? Hopefully, you'll find more insights from others and/or come up with ideas this request should meet

I agree, closing this until we can make it an actionable issue.


Add a CyclomaticComplexityChecker option to ignore "case" keyword

It's a common case for complex domains and libraries (such as scalastyle) to have long lists of cases in match clauses, splitting them doesn't really simplify the code.

In this case you can always ignore the checker for this method, using // scalastyle:ignore or //scalastyle:on or off. Is this acceptable?

What's the rationale for discouraging long lists of case statements? Is this intentional or incidental to how the cyclomatic complexity checker is implemented? If intentional, what's the recommended alternative approach?
Turning off ScalaStyle for each large match statement is only a workaround, one that not only puts an extra burden on the writer, but also hides other potential issues in that block.


TypeError: ext.toLowerCase is not a function

Please use the template provided below, when reporting bugs:
Expected Behavior
nyc mocha runs without error
Observed Behavior
/../node_modules/nyc/index.js:71
    return ext.toLowerCase()
               ^

TypeError: ext.toLowerCase is not a function
    at /.../node_modules/nyc/index.js:71:16
    at Array.map (<anonymous>)
    at new NYC (/.../node_modules/nyc/index.js:69:62)
    at Object.<anonymous> (/.../node_modules/nyc/bin/nyc.js:36:14)
    at Module._compile (module.js:635:30)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)
    at Function.Module.runMain (module.js:676:10)

in index.js, i added a console.error, as follows:
this.extensions = arrify(config.extension).concat('.js').map(function (ext) {
    console.error('!!!!!!!!!!!', ext, config.extension, arrify(config.extension))
    return ext.toLowerCase()
})

and the output is
!!!!!!!!!!! true true [ true ]

Bonus Points! Code (or Repository) that Reproduces Issue
https://travis-ci.org/ibm-functions/shell/jobs/298318311
Forensic Information
Operating System: the operating system you observed the issue on.
both macOS and travis-ubuntu
Environment Information: information about your project's environment, see instructions below:

run the following script:

sh -c 'node --version; npm --version; npm ls' > output.txt

share a gist with the contents of output.txt.
https://gist.github.com/starpit/eca38d075e8f5cf34600735506e1c16f

@starpit it looks to me like nyc is being loaded with config that has extensions = true; reading through your codebase, it looks like you configure nyc programmatically in a few places, I would print out the config at this time, and see what it looks like.
My guess is something like this is somehow happening: Nyc({extensions: true}).

fwiw, in my case it was this:
NODE_ENV=test nyc -reporter=lcov mocha ./tests/test-helper.js --opts ./tests/mocha.opts'

(notice the single dash with reporter)
by changing this to --reporter it fixed the problem for me
NODE_ENV=test nyc --reporter=lcov mocha ./tests/test-helper.js --opts ./tests/mocha.opts'


Add Cache-Control support

Add a new :cache_control option for setting the Cache-Control header when redirecting to allow the caching of the redirect to be…controlled. This can be especially important with 301 redirects which some browsers cache indefinitely.
This is based on the work of @Aupajo in #41. I've altered it slightly to remove the Fixnum form which required a type check, and to avoid setting a default value, which would break backwards compatibility. I am open to setting a default value in a future release, but I'd like to see this proven before switching that on.

Thanks, @tylerhunt. Compromise seems very reasonable to me. Happy to test any pre-release that goes out.


Improve GitHub Actions for pull requests

See https://github.com/Senzing/community-roadmap/issues/71

Pull requests:

https://github.com/Senzing/g2search/pull/26


Apply Superset query as data source for a chart.

We would like to be able to define SQL queries in superset and use the output of the query as a data set that can be visualized in  a chart. According to this article it should be possible.
However, from experience "if you run the query, you get an Explore button that seems to lead to an option for saving as a "virtual data set" - but when I tried saving it, I got an error"
Acceptance Criteria:

[ ] Superset users can create virtual datasets from SQL queries without error.

resolved : )


Misplacement of words in 'Troubleshooting - Metric category is not supported'

When deploying a diagnostic setting, you receive an error message, similar to Metric category 'xxxx' is not supported. You may receive this error even though a previous your deployment succeeded.

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

ID: 89743709-c3fa-9ce1-55fb-e9b7f6d2dba9
Version Independent ID: a4c9f0b7-5dde-d60c-1110-3ca53d904d61
Content: Create diagnostic settings to send Azure Monitor platform metrics and logs to different destinations - Azure Monitor
Content Source: articles/azure-monitor/essentials/diagnostic-settings.md
Service: azure-monitor
Sub-service: essentials
GitHub Login: @rboucher
Microsoft Alias: robb

@saadsaiyed Thanks for your comment. We will review the issue and get back to you shortly.

@saadsaiyed Thanks for the feedback! I have fixed the referenced change, and the change should reflect on the document once approved by content author. We will now proceed to close this thread. If there are further questions regarding this matter, please revert and we will gladly continue the discussion.


Feature Request: Order syllabi for each course in reverse-chronological order

Right now, syllabi are populated in alphabetical order:

Closing as this has been fixed in the upcoming re-architecture of the website. Snippet:


Crash when I cat a file

On windows, I tried cat attached txt file and it crashed.
protonmail_gray.txt

The only thing I can see with this which might cause issues is that it's missing a newline at the end of the file. That shouldn't crash anything, but would you mind adding a newline to the end of the file, just to troubleshoot where the issue is coming from?
Also, just to make sure: When you say 'it crashed', you're talking about Alacritty? Or are you talking about cat?

I tried with missing newline and Alacritty still crashes, the window suddenly disap
protonmail_gray.txt
pear.

Does cat work with any other file? It looks like there should be nothing special about the new version of the file you've sent. No special characters, escape sequences or missing newlines.

tags.txt
This file works fine, it's… really strange ^^'

@Geobert When starting Alacritty from a different instance of Alacritty, is there any error output?

Unfortunately, no :(

I can't test on Windows, but it looks like Alacritty chooses to close down itself. It probably shouldn't be super complicated to figure out why that is, but it would require some debugging.
Maybe @zacps can take a look at this? Would be interesting to see if this can be reproduced first.

I suppose on your system, it does not crash?

Hi. @chrisduerr, I noticed both protonmail_gray.txt start with Byte Order Mark EF BB BF.
Is it problem?

Good catch @PrsPrsBK I've changed the encoding and it does not crash any more!

@Geobert It does not crash on my system, since I'm running Linux. But great catch @PrsPrsBK.

@Geobert It's nice!
@chrisduerr I had bad experiences due to BOM.
I see, it need to see cat's  output (if exists). thanks.

I can't seem to reproduce this?
Under bash (WSL):
$ cat protonmail_gray.txt
.conversation.read {
 background: #dddddd;!important
}

.conversation {
background: #dddddd;!important
}

#conversation-view .frame, #pm_main {
 background: #dddddd;!important
 }

.composer-container, .squire-container {
background-color: #dddddd;!important

Under cmd (using type):
F:\Downloads\Temp>type protonmail_gray.txt
´╗┐.conversation.read {
 background: #dddddd;!important
}

.conversation {
background: #dddddd;!important
}

#conversation-view .frame, #pm_main {
 background: #dddddd;!important
 }

.composer-container, .squire-container {
background-color: #dddddd;!important
}

ala.log
I got a panick message this time :D

@Geobert If you could run this with RUST_BACKTRACE=1, that would be really helpful. Like this the full backtrace is unfortunately not shown.

Of course!
J:\Downloads>thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', libcore\option.rs:345:21
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: winpty_spawn_config_new
  15: BaseThreadInitThunk
  16: RtlUserThreadStart

@Geobert Unfortunately it looks like the backtraces aren't available in the version of Alacritty you're running. If you could try running it in debug mode (cargo run instead of cargo run --release), the full backtrace should be available.

I was running the bin from appveyor. I tried a compilation, but it fails:
--- stderr
thread 'main' panicked at 'Unable to find libclang: "couldn\'t find any of [\'clang.dll\', \'libclang.dll\'], set the LIBCLANG_PATH environment variable to a path where one of these files can be found (skipped: [])"', libcore\result.rs:945:5

@Geobert Alacrity requires Clang for Windows builds. This is listed in INSTALL.md
@chrisduerr I think it might be a panic because of an exception raised in winpty.

I was able to reproduce this today with latest master (commit 4380d0864b1098909bdcfec132b866c34924517e), here is a backtrace:
$ RUST_BACKTRACE=1 ./target/debug/alacritty.exe
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', libcore\option.rs:345:21
stack backtrace:
   0: std::sys::windows::backtrace::set_frames
             at C:\projects\rust\src\libstd\sys\windows\backtrace\mod.rs:104
   1: std::sys::windows::backtrace::set_frames
             at C:\projects\rust\src\libstd\sys\windows\backtrace\mod.rs:104
   2: std::sys_common::backtrace::_print
             at C:\projects\rust\src\libstd\sys_common\backtrace.rs:71
   3: std::sys_common::backtrace::_print
             at C:\projects\rust\src\libstd\sys_common\backtrace.rs:71
   4: std::panicking::default_hook::{{closure}}
             at C:\projects\rust\src\libstd\panicking.rs:211
   5: std::panicking::default_hook
             at C:\projects\rust\src\libstd\panicking.rs:227
   6: std::panicking::rust_panic_with_hook
             at C:\projects\rust\src\libstd\panicking.rs:475
   7: std::panicking::continue_panic_fmt
             at C:\projects\rust\src\libstd\panicking.rs:390
   8: std::panicking::rust_begin_panic
             at C:\projects\rust\src\libstd\panicking.rs:325
   9: core::panicking::panic_fmt
             at C:\projects\rust\src\libcore\panicking.rs:77
  10: core::panicking::panic
             at C:\projects\rust\src\libcore\panicking.rs:52
  11: core::option::Option<(usize, stb_truetype::{{impl}}::glyph_shape_positive_contours::FlagData)*>::unwrap<(usize, stb_truetype::{{impl}}::glyph_shape_positive_contours::FlagData)*>
             at C:\projects\rust\src\libcore\macros.rs:20
  12: stb_truetype::FontInfo<rusttype::SharedBytes>::glyph_shape_positive_contours<rusttype::SharedBytes>
             at C:\Users\Martin\.cargo\registry\src\github.com-1ecc6299db9ec823\stb_truetype-0.2.4\src\lib.rs:911
  13: stb_truetype::FontInfo<rusttype::SharedBytes>::get_glyph_shape<rusttype::SharedBytes>
             at C:\Users\Martin\.cargo\registry\src\github.com-1ecc6299db9ec823\stb_truetype-0.2.4\src\lib.rs:655
  14: rusttype::PositionedGlyph::draw<closure>
             at C:\Users\Martin\.cargo\registry\src\github.com-1ecc6299db9ec823\rusttype-0.4.3\src\lib.rs:786
  15: font::rusttype::{{impl}}::get_glyph
             at .\font\src\rusttype\mod.rs:122
  16: alacritty::renderer::{{impl}}::get::{{closure}}<alacritty::renderer::RenderApi>
             at .\src\renderer\mod.rs:280
  17: std::collections::hash::map::Entry<font::GlyphKey, alacritty::renderer::Glyph>::or_insert_with<font::GlyphKey,alacritty::renderer::Glyph,closure>
             at C:\projects\rust\src\libstd\collections\hash\map.rs:2120
  18: alacritty::renderer::GlyphCache::get<alacritty::renderer::RenderApi>
             at .\src\renderer\mod.rs:277
  19: alacritty::renderer::RenderApi::render_cells<core::slice::Iter<alacritty::term::RenderableCell>>
             at .\src\renderer\mod.rs:896
  20: alacritty::display::{{impl}}::draw::{{closure}}
             at .\src\display.rs:380
  21: alacritty::renderer::QuadRenderer::with_api<closure,()>
             at .\src\renderer\mod.rs:689
  22: alacritty::display::Display::draw
             at .\src\display.rs:378
  23: alacritty::run
             at .\src\main.rs:261
  24: alacritty::main
             at .\src\main.rs:80
  25: std::rt::lang_start::{{closure}}<()>
             at C:\projects\rust\src\libstd\rt.rs:74
  26: std::rt::lang_start_internal::{{closure}}
             at C:\projects\rust\src\libstd\rt.rs:59
  27: std::rt::lang_start_internal::{{closure}}
             at C:\projects\rust\src\libstd\rt.rs:59
  28: panic_unwind::__rust_maybe_catch_panic
             at C:\projects\rust\src\libpanic_unwind\lib.rs:105
  29: std::panicking::try
             at C:\projects\rust\src\libstd\panicking.rs:289
  30: std::panicking::try
             at C:\projects\rust\src\libstd\panicking.rs:289
  31: std::panicking::try
             at C:\projects\rust\src\libstd\panicking.rs:289
  32: std::rt::lang_start<()>
             at C:\projects\rust\src\libstd\rt.rs:74
  33: main
  34: invoke_main
             at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:78
  35: invoke_main
             at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:78
  36: BaseThreadInitThunk
  37: RtlUserThreadStart

It seems like there is a glyph, or we would have bailed on src/font/rusttype/mod.rs#103, but trying to draw it fails for some reason.
What font are you using?

The font is the default (I don't have a config file). It happens to be Consolas, here is the font from config printed:
Font { normal: FontDescription { family: "Consolas", style: None }, italic: FontDescription { family: "Consolas", style: None }, bold: FontDescription { family: "Consolas", style: None }, size: Size(22), offset: Delta { x: 0, y: 0 }, glyph_offset: Delta { x: 0, y: 0 }, use_thin_strokes: false, scale_with_dpi: true }

The panic occurs for get_glyph of
GlyphKey { c: '\u{feff}', font_key: FontKey { token: 3 }, size: Size(22) }

so this confirms it's caused by the BOM.

I've created an issue in stb_truetype-rs at https://gitlab.redox-os.org/redox-os/stb_truetype-rs/issues/19

The same thing happens when using less and cat, with files generated by Visual Studio (.csproj, nuget.config, etc)

@jabagawee Thanks for the info. I've pushed a PR to bump the version here: https://github.com/jwilm/alacritty/pull/1904.
Testing appreciated!

It works for me now. Thanks!


⚠ Bofrost.de has degraded performance

In c261c84, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1418 ms

Resolved: Bofrost.de performance has improved in 1fe846b after 7 minutes.


Known issue: db not found when slow queries are accessed after db creation

For 3.7, the fix may get delayed to 3.7.7!

Will be fixed in v3.7.6


Update project dependencies [ONGOING]

Run yarn audit to determine security vulnerabilities and yarn outdated to determine packages which need to updated. Major releases should be investigated. Create a separate branch off develop to investigate upgraded packages.
Check NodeJS versions periodically to make sure we don't get out of date (security purposes).

Closing as can raise individual ticket for each maintenance release


Unify to a Single Python File

Why are we nesting a single file in a single folder? That seems... excessive.
We should just move towards replacing the pycev/ folder with the single pycev.py file.

Created #17
I took a look at the imports in the unit test files as well and they should ideally work.

Thank you again, @sreekeshiyer, for your efforts here! This has been completed, and I'm closing this out, now.


add upgrade argument for pip install

fix for some version mismatches for superset dependencies

Thanks for the PR, but I won't merge this on account it makes the Dockerfile non-deterministic.
By that I mean that subsequent builds on the same Dockerfile should produce identical images (as closely as is possible, anyway). Adding the --upgrade flag undoes that by letting pip mess with the pegged versions. It'd be better to resolve conflicts as they crop up.

but what about the apt update... isn't that the same problem?

Yes, you are correct. I'm less concerned about that because those libraries will be pegged to the OS and move more slowly than pips, generally.


ResourceBundle injection in FXPerspective

Hi Andy,
It seems that resource bundle is never injected the first time a FXPerspective is accessed.
Indeed, in case of FXPerspective, resource bundle injection is done at line 253 of org.jacpfx.rcp.handler.PerspectiveHandlerImpl.initComponent(Message<Event, Object>, Perspective<Node, EventHandler<Event>, Event, Object>) (calling org.jacpfx.rcp.util.FXUtil.performResourceInjection(Injectable, JacpContext<EventHandler<Event>, Object>) which will use the resource bundle associated to the context) while the association of the resource bundle to the context will only be done at line 255 of org.jacpfx.rcp.handler.PerspectiveHandlerImpl.initComponent(Message<Event, Object>, Perspective<Node, EventHandler<Event>, Event, Object>) by the call to org.jacpfx.rcp.handler.PerspectiveHandlerImpl.handlePerspectiveInitialization(Perspective<Node, EventHandler<Event>, Event, Object>).
Current workaround consists in getting the resource bundle from the context directly or in using the resource bundle provided as argument of the method annotated by @PostConstruct.
Note that everything works well for managed fragments.
Thanks in advance!
Cheers,
Jean.

Hi.... can you provide the version of JacpFX (2.1-RC3 ?)
Andy

Sorry. It is 2.1-RC3.
Jean.

OK... so I pushed RC4 to maven central. I had very little time to test, hopefully nothing is broken... at least the UnitTests were fine ;-)
So let me know if both bugs are gone and thank you for your help.
Andy

Fixed by 2.1-RC4.
Thanks!
Jean.


[HUDI-5373] Different fileids are assigned to the same bucket

Change Logs
final String bucketId = partition  + bucketNum;
partition =30 bucketNum=11
bucketId = 3011
partition =301 bucketNum=1
bucketId = 3011
Different fileids are assigned to the same bucketId
Impact
NA
Risk level (write none, low medium or high below)
low
Documentation Update
NA
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@danny0405 Please review the code for me


Geosearch commands go to the master node

Bug Report
Current Behavior
geosearch commands go to master node even if read intention ReadFrom.REPLICA is specified.
Input Code

Start simple master/replica redis setup with docker-compose
Connect to both redis nodes and run MONITOR command to see commands coming to nodes
Run java code
Observe that geosearch command goes to primary node and get replica node

# docker-compose.yaml
version: "3.9"
services:
  redis-master:
    image: "redis"
    ports:
      - "6379:6379"
    expose:
      - "6379"
  redis-replica:
    image: "redis"
    ports:
      - '6380:6379'
    command: redis-server --slaveof redis-master 6379

// Main.java
package org.example;

import io.lettuce.core.*;
import io.lettuce.core.codec.StringCodec;
import io.lettuce.core.masterreplica.MasterReplica;
import io.lettuce.core.masterreplica.StatefulRedisMasterReplicaConnection;

import java.util.List;

public class Main {
    public static void main(String[] args) {
        RedisURI masterUri = RedisURI.create("redis://localhost:6379");
        RedisURI replicaUri = RedisURI.create("redis://localhost:6380");

        RedisClient client = RedisClient.create();
        List<RedisURI> nodes = List.of(masterUri, replicaUri);
        StatefulRedisMasterReplicaConnection<String, String> connection = MasterReplica.connect(client, StringCodec.UTF8, nodes);

        connection.setReadFrom(ReadFrom.REPLICA);
        connection.sync().get("key");
        connection.sync().geosearch("another-key", GeoSearch.fromCoordinates(0.0, 0.0), GeoSearch.byRadius(1.0, GeoArgs.Unit.km));
    }
}

Expected behavior/code
geosearch commands should go to replica node when read intention ReadFrom.REPLICA is specified as the command (https://redis.io/commands/geosearch/) is only reading.
Environment

Lettuce version: Tested with 6.3.0.RELEASE but I believe other versions are affected too
Redis version: 7.2.3

Possible Solution
Add geosearch to the list of read_only commands similar to https://github.com/lettuce-io/lettuce-core/pull/2198 did for smismember. I can open a PR to do that.

The same goes for FCALL_RO.  My use case requires these to be spread among ReadFrom.ALL but currently they only go to masters.


fn splat_dc: Cleanup and make safer

Part of #815.

We can do this safely with zerocopy, safely transmuting to const N: usize = RAV1D_PICTURE_ALIGNMENT / mem::size_of::<uN>() and [uN; N] (where uN is u8 or u16) and calling .fill([uN; dc]).

I'm not following here. Could you provide a code example of what you're thinking of? I see how we could e.g. in bpc == 8, width > 4 case do [dc as u8; 8] instead of the multiplication with dcN to get the same effect, but I don't follow how we could use zerocopy to make this any safer than it already is.

We can do this safely with zerocopy, safely transmuting to const N: usize = RAV1D_PICTURE_ALIGNMENT / mem::size_of::<uN>() and [uN; N] (where uN is u8 or u16) and calling .fill([uN; dc]).

I'm not following here. Could you provide a code example of what you're thinking of? I see how we could e.g. in bpc == 8, width > 4 case do [dc as u8; 8] instead of the multiplication with dcN to get the same effect, but I don't follow how we could use zerocopy to make this any safer than it already is.

Sure.  Can we merge this first?


using 6.3.0 switching between pages very slow

I'm submitting a ...
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior
when switching between pages of the datatable with multiple page, theres a big delay.
Was this a problem before? Could it be the version of angular?

Table version: 0.7.x
6.3.0

Angular version: 2.0.x
2.4.0

Browser: [all ]

Language: [TypeScript ]

A few quick questions to narrow this down:

Is your app running in production mode?
Does your grid have a large number of columns?

@adammedford just tried it production... its like a different world. ye, its very smooth in prod, closing this. Thanks :)

Glad it worked out for you. Something to keep in mind though:
Outside of production mode Angular 2 has a lot of redundant logic that second guesses your application's logic to try and uncover unintended side-effects. As a result, you shouldn't be developing in Production mode with this datatable just because it makes things run smoother because Angular's debug mode checks are ultimately there to help you.
To give you an example of what this will catch:
Say you've got a component that outputs an event every time some property changes. Your app (for the purposes of this example) listens to that event and inputs the new value to the same component that emitted it. What's next? That component emits an event signaling that value has changed - triggering an infinite loop. It seems like a contrived scenario but its an easy mistake to make. In debug mode Angular will notice this value changed between change detection runs and throw a fatal error so you know exactly where to look. In production mode, there is no telling how long you'd spend trying to get the same information.

The main cause is ng-reflect
In Angular2, I set useDebug: false to disabled it.
However, in Angular4 that's deprecated: https://github.com/angular/angular/issues/9707#issuecomment-289046682
So not sure how to turn-off ng-reflect anymore.

Check out this - https://github.com/swimlane/ngx-datatable/blob/master/demo/polyfills.ts#L17


Type safe distinction between Caret and Index (?)

[Inspiration] I like the idea of expressing by type “that’s a [caret], that’s an index.”

The idea is interesting, but it adds a too much complexity relative to the complexity of the project. It might be better as a separate and reusable collections module thingy, dunno.


i can't install react-native-vector-icons

i have this error when i wanna install:
`environment:First Hernan$ npm install react-native-vector-icons --save
<EMAIL_ADDRESS>/Users/Hernan/Desktop/carpeta/reactnative/First
└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm ERR! code 1`
Please help!

Hey, tell react-native-elements to loosen their peerDependency requirements.

@Brhernann RNE is doing a release later this week with a fix for this. Follow progress here: https://github.com/react-native-training/react-native-elements/issues/434

thanks!

Getting same error:
npm WARN<EMAIL_ADDRESS>requires a peer of react-native-vector-ico
<EMAIL_ADDRESS>but none was installed.

Closing this issue as it's related to third party libraries and not actionable for me.


Move getSourceString to String Utils

This commit is a non-functional change.
It moves the getSourceString function into its own string_utils module.
Additionally, a new string_utils test is added to check the functionality.
Lastly, it moves the test files into a new sub-directory named /test.
Tested: Locally

Ran the test file and verified new tests pass
Ran all tests in the /test directory and verified they all pass.

Example output
$ node node_modules/ava/cli.js test/string_utils.test.js

  6 passed

and all tests:
$ node node_modules/ava/cli.js test/*.test.js

  18 passed

@thedavidmeister Updated with docblock.

could we move tests to a subfolder?  This flat nonstructure was already too big even before their arrival.

@tonyofbyteball lol, i specifically made the test files flat to mimic the existing structure.
Would you be able to document how you want this repo to be structured to make it easier for us to follow?

@tonyofbyteball @thedavidmeister I put both existing tests into a new /test sub-directory. Let me know if this is not what you have in mind.

Rebased onto #46 to use ava for tests.

Would you be able to document how you want this repo to be structured to make it easier for us to follow?

moving tests to a subdir is already an improvement.  I don't see how the rest could be organized significantly better, creating subdirs for a 1 or 2 of files wouldn't make much sense.


How secondary/new phone is handled?

What is missing
How to handle people with 2 phones or people buying a new phone.
Why should it be included
I have two phones (one for work and a private one) and now ask myself what would happen if I install the app on both phones, as I don't carry both with me all the time. Would I be able to use the app on both phones and in case of a positive test result send a warning from both devices?
Another example that might need to trigger 2 warnings from one test: People buying a new phone. In case the local data can't be migrated from one device to another, it would be required to send the warning from both devices if the switch just recently happened.
I'm aware these are edge cases, but would be interesting in your opinion.
Where should it be included
Scoping document and solution architecture.

These are great questions. My gut feeling tells me that specific support for such situations may be deferred until a later version. However, it would probably be a good idea to estimate early how frequently the described cases occur and what impact they may have on the success and reliability of the system.
Perhaps some recommendations could be included in end user documentation as long as there are no technical solutions: What should I do if I use multiple devices? What should I do when I get a new device?

If you would let people confirm their positive test on two phones (e.g. work and private) and upload both sets of diagnosis keys, you would create another issue: In situations where both phones have been carried along, other people would have been (from the framework's perspective) exposed to two different people, who have later tested positive. This would probably result in a higher calculated risk.
Our current assumption for the first version was:

1 Person --> 1 Phone --> 1 App
1 Test --> 1 QR-Code -> 1 Test Result --> 1 Upload (actually two if you count in the key of the current day, which is still valid - but that's a different story)

We are absolutely aware that this does not cover 100% of the cases.

Thanks again for brining up these questions. I hope that @tklingbeil 's answer is sufficient for now. We'll keep this issue in mind, but for the first release, the assumptions above are our guiding principles.

We'll keep this issue in mind, but for the first release, the assumptions above are our guiding principles.

Then please tag this issue accordingly ("keep in mind").

This issue is closed, however for cross-reference, please see https://www.coronawarn.app/en/faq/#test_multiple_devices
How do I share a positive test result on multiple devices?
"If you have more than one smartphone (e.g. work and private), we recommend that you install the CWA on your private device first. Also, when scanning QR codes and sharing a positive result, we recommend that you first use your private device. If you additionally want to share a positive result via your company device or any other additional smartphone, this can be done via a so-called TeleTAN. By contacting +49<PHONE_NUMBER> with a positive test result, you will receive a 10-digit TAN with which the test result can also be registered in the app. Please note: The TAN number is only valid for one hour."

Also the question about a new device is answered in https://www.coronawarn.app/en/faq/#new_device
What do I have to consider when switching to a new device?
A backup of the old random IDs is unfortunately not possible, because the Exposure Notification API of Apple/Google does not allow the export of this data. To still be informed about possible risk encounters, we recommend that you keep a close view of the risk status on the old device for at least 14 days after you install the Corona Alert app on the new device. Please note the following instructions:

Your old device must be able to perform regular checks for possible encounters. Therefore, leave the device permanently turned on and permanently connected to the Internet.
Keep the old device in a stationary location, e.g., in a specific place in your apartment. If possible, place the device in listening or visual range so that you are alerted early by a notification of the app.
Actively access the Corona-Warn-App on the old device at least once a day and check your risk status there.
If you are tested for COVID-19 during these 14 days, enter the QR code on your new device. If the test result is positive, you should share the test result on both devices. For sharing a test result on multiple devices, please note this FAQ entry.

After 14 days, your old device will no longer contain any relevant entries for risk assessment. You don't need to pay any further attention to the risk status on this device and can remove the Corona-Warn-App there.


WIP: Update to latest Miniscript

I need that for revaultd, but want Miniscript to publish a new version (hopefully with my fix) before merging this.

Rebased on #33


[BUG]: There is no indication of if the query is being processed or not

How are you running AnythingLLM?
AnythingLLM desktop app
What happened?
Hello, When agent is invoked, some complex queries can take even 20 to 30 seconds and during this time, the chat windows gives no indication that something is happening in the background and I should wait for the result. Looking at this, one can think it has failed. Please either add in the chat that "agent is currently working on your query....." or something like that so users are aware the processing is happening in the background.

Are there known steps to reproduce?
No response

This is not a bug - this would be a feature request!

There should probably be a loading indicator. I don't know if this can be streamed...currently it's not being streamed so a user might not understand that it is running when everything else is streamed.


HOW TO STORE THE UDP CONTENT WHEN STREAMING ONE UDP TO ANOTHER UDP?

@lelegard
tsp -v -m --synchronous-log -I ip <IP_ADDRESS>:5000 -P regulate --pcr-synchronous -O ip -l <IP_ADDRESS> <IP_ADDRESS>:1234
this is my udp to udp conversion.
i want to store the output udp content in STORE.TS in ts file or any other idea please give me.
if its possible means tell me the how to store when streaming udp to udp content.
thank you in advance.

Are you crazy @udhayNuk
Read the User guide .

Hello.
Does file plugin not work in your case, i.e. ... -P file STORE.TS ...?

@AlfonZ42
i have already this method.
but i want any another method.

I'm not sure what you mean.
Are you saying that you have tried the file plugin, it worked, but you want to do one thing via two different methods?
Or are you saying you have already tried the file plugin but it doesn't work for what you wan to achieve? In which case could you please describe what is not working for your case?

@AlfonZ42
i have tried it has been working i want another method.

The file plugin, as recommended by @AlfonZ42, is the method.
That being said, TSDuck is open source and you may invent and implement any other method for your own usage.

Read the User guide


feat: also move sub bullet points of completed tasks

I plan to add a feature when you move completed tasks that checks if the next line(s) of a completed task are indented & start with a -. If that is the cases I would also move those lines. Would you accept such a pull request? 🙂

I believe that works already?

I tested it with the following file:
- [x] todo 2
	- inline
	- inline2
- [ ] todo 3

## Log
- [x] todo1

what I would have expected was:
- [ ] todo 3

## Log
- [x] todo 2
	- inline
	- inline2
- [x] todo1

but currently executing "move all completed task" leads to the following result:
	- inline
	- inline2
- [ ] todo 3

## Log
- [x] todo 2
- [x] todo1

Ok it looks like a classic: "tabs" vs "spaces" issue 😃 If I use 4 space to indent it works.


Fix issue

Pull Request Type
What kind of change does this PR introduce?
[x ] Solved an issue/task
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
Issue Number:
1005
What is the new behavior?
Calculator

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


fixes runtime errors

I forgot to commit those two strs sorry :(

I wonder why this is not a problem for me... maybe a different pydantic build?