Error trying amplify mock "Stream Arn must be specified"

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
16.16.0
Amplify CLI Version
10.2.1
What operating system are you using?
Mac Monterey 12.4
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
I run amplify mock and fails with "Stream Arn must be specified"

Expected behavior
The amplify mock does not fail, perhaps this should be a question issue instead.
What is expected from me to do in this case? What's the Stream Arn and how/where I can specify it?
Reproduction steps
Have a schema with several indexes, run amplify mock adding/removing one index at once per table until the whole initial mock process succeed, then I got the error described above.
GraphQL schema(s)

# TODO: Split this file in coherent modular files after the issue below has been addressed
# https://github.com/aws-amplify/amplify-category-api/issues/711
# in the mean time heavily comment on each section to make it easier to understand

# SOL 2.0

# The following link explains the priority for auth rules https://docs.amplify.aws/lib/datastore/setup-auth-rules/q/platform/js/#multiple-authorization-types-priority-order

# Relationships insights
# =====================
# TIP: Use `amplify codegen models` to check model types before push to cloud
# [1] Querying @hasMany side of the relationship is not yet supported by DataStore https://github.com/aws-amplify/amplify-js/discussions/9499
# [2] A model with @hasOne relationship will be deleted when the related model is deleted
# [3] When querying models you can't get Children of children, be aware if querying scenarios require it and shape relations accordingly
# ...More on the README.md

# A representation of a user on its 'participant' role, id will match the Profile.id
type Participant
  @model
  @auth(
    rules: [
      { allow: private }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  # use same id than Profile to make easier the lookups
  id: ID!
  profileID: ID!
  profile: Profile @hasOne(fields: ["profileID"])
  skills: [Skill] @manyToMany(relationName: "SkillParticipantConnection")
  projects: [Project] @manyToMany(relationName: "ProjectParticipantConnection")
  posts: [Post] @hasMany(indexName: "byParticipant", fields: ["id"])
  # see relationship insights [1]
  # checkups: [Checkup] @hasMany
}

# A representation of a user on its 'verifier' role, id will match the Profile.id
type Verifier
  @model
  @auth(
    rules: [
      { allow: private, operations: [read] }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  # use same id than Profile to make easier the lookups
  id: ID!
  profileID: ID!
  profile: Profile @hasOne(fields: ["profileID"])
  skills: [Skill] @manyToMany(relationName: "SkillVerifierConnection")
  # see relationship insights [1]
  # checkups: [Checkup] @hasMany
}

type Organiser
  @model
  @auth(
    rules: [
      { allow: private }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  # use same id than Profile to make easier the lookups
  id: ID!
  profileID: ID!
  profile: Profile @hasOne(fields: ["profileID"])
  projects: [Project] @manyToMany(relationName: "ProjectOrganiserConnection")
}

# Represents a domain knowledge
type Field
  @model
  @auth(
    rules: [
      { allow: private, operations: [read] }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  name: String!
  image: String!
  description: String!
  # see relationship insights [1]
  # skills: [Skill] @hasMany(indexName: "byField", fields: ["id"])
}

# A user ability to participate into a project or to being able to verify certain domain
type Skill
  @model
  @auth(
    rules: [
      { allow: private, operations: [read] }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  # see relationship insights [1]
  # fieldID: ID! @index(name: "byField", sortKeyFields: ["level"])
  fieldID: ID!
  priceID: ID
  productID: ID
  level: Int @default(value: "0")
  criteria: String!
  field: Field @hasOne(fields: ["fieldID"])
  verifiers: [Verifier] @manyToMany(relationName: "SkillVerifierConnection")
  participants: [Participant] @manyToMany(relationName: "SkillParticipantConnection")
  # Allow optional to permit the ability to generate and relate product/price after skill creation
  price: Price @hasOne(fields: ["priceID"])
  product: Product @hasOne(fields: ["productID"])
}

# A transaction object that held the lifecycle of a verification process
type Checkup
  @model
  @auth(
    rules: [
      { allow: private }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  skillID: ID
  participantID: ID!
  verifierID: ID
  orderID: ID
  priceID: ID!
  productID: ID!
  skill: Skill @hasOne(fields: ["skillID"])
  participant: Participant! @hasOne(fields: ["participantID"])
  verifier: Verifier @hasOne(fields: ["verifierID"])
  content: String
  feedback: String
  status: CheckupStatus! @default(value: "PENDING")
  order: Order @hasOne(fields: ["orderID"])
  price: Price! @hasOne(fields: ["priceID"])
  product: Product! @hasOne(fields: ["productID"])
}

# The different states a checkup can be in
enum CheckupStatus {
  # The checkup payment is being processed
  SETTLING
  # There is a checkup available but is not ready to be reviewed
  PENDING
  # The skill is assigned but the verifier is not yet assigned
  SENT
  # The verifier is assigned but the feedback is not yet given
  ASSIGNED
  # The feedback is given and the checkup is completed
  ACCEPTED
  REJECTED
}

# The actual projects that people can work on
type Project
  @model
  @auth(
    rules: [
      { allow: private }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  name: String!
  description: String!
  location: String!
  problem: String!
  solution: String!
  launchPlan: String!
  status: ProjectStatus! @default(value: "DRAFT")
  tags: [Tag] @manyToMany(relationName: "ProjectTagConnection")
  organisers: [Organiser] @manyToMany(relationName: "ProjectOrganiserConnection")
  participants: [Participant]
    @manyToMany(relationName: "ProjectParticipantConnection")
  posts: [Post] @hasMany(indexName: "byProject", fields: ["id"])
}

enum ProjectStatus {
  DRAFT
  REVIEW
  PUBLISHED
  COMPLETED
  ARCHIVED
}

# Allow to classify projects among others models
type Tag
  @model
  @auth(
    rules: [
      { allow: private }
      # This allow lambda to make CRUD operations
      { allow: private, provider: iam }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  name: String!
  image: String!
  projects: [Project] @manyToMany(relationName: "ProjectTagConnection")
  # Tag with lower number will be shown first
  priority: Int @default(value: "1000")
}

type Membership
  @model
  @auth(
    rules: [
      { allow: private }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  profileID: ID!
  trackingID: ID!
  stripeSubscriptionID: ID
  status: MembershipStatus! @default(value: "INACTIVE")
  profile: Profile @belongsTo(fields: ["profileID"])
}

enum MembershipStatus {
  ACTIVE
  INACTIVE
}

# SOL 1.0

# Allow to describe the lifecycle of a user purchase
enum OrderStatus {
  PENDING
  PROCESSING
  SUCCEEDED
  PAYMENT_FAILED
}

# Define the type of items that can be sell at Sol
enum ProductType {
  VERIFICATION
  MEMBERSHIP
}

# Wether the price is mean to be paid in subscription or not
enum PriceType {
  one_time
  recurring
}

enum CognitoGroup {
  admin
  user
  guest
  participant
  verifier
}

enum ReputationTargetType {
  POST
  PROFILE
}

enum ReputationType {
  LOVE
  CRED
}

# A model to represent project updates through time in a form of a short tweet like post
# project will use open graph to fetch image preview, if a url not provided
# the image will be the one provided by the 'image' field if neither is provided
# there is no image preview
type Post
  @model
  @auth(
    rules: [
      { allow: public, operations: [read], provider: apiKey }
      { allow: private, operations: [read] }
      { allow: owner }
      {
        allow: groups
        groups: ["Admins"]
        operations: [read, create, update, delete]
      }
    ]
  ) {
  id: ID!
  owner: String
    @auth(
      rules: [
        { allow: owner, operations: [read, delete] }
        { allow: public, operations: [read], provider: apiKey }
      ]
    )
  url: String
  openGraphData: AWSJSON
  image: String
  content: String!
  authorID: ID! @index(name: "byParticipant")
  author: Participant @belongsTo(fields: ["authorID"])
  projectID: ID! @index(name: "byProject")
  project: Project! @belongsTo(fields: ["projectID"])
  totalLove: Int @default(value: "0")
  totalCred: Int @default(value: "0")
}

type Profile
  @model
  @auth(
    rules: [
      { allow: public, operations: [read], provider: apiKey }
      { allow: owner }
      { allow: private, operations: [read] }
    ]
  ) {
  id: ID!
  owner: String
    @auth(
      rules: [
        { allow: owner, operations: [read, delete] }
        { allow: public, operations: [read], provider: apiKey }
      ]
    )
  bio: String
  companies: [Company] @manyToMany(relationName: "ProfileCompanyConnection")
  email: String!
  familyName: String
  languages: [String]
  links: [String]
  locale: String
  name: String
  picture: String
  preferredUsername: String!
  professions: [Profession] @manyToMany(relationName: "ProfileProfessionConnection")
  totalLove: Int @default(value: "0")
  totalCred: Int @default(value: "0")
  membershipID: ID
  membership: Membership @hasOne(fields: ["membershipID"])
}

type Company
  @model
  @auth(
    rules: [
      { allow: private, operations: [create, read, update] }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  name: String!
  slug: String
  profiles: [Profile] @manyToMany(relationName: "ProfileCompanyConnection")
}

type Profession
  @model
  @auth(
    rules: [
      { allow: private, operations: [create, read, update] }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  name: String!
  slug: String
  profiles: [Profile] @manyToMany(relationName: "ProfileProfessionConnection")
}

## Stores a Creator's private stripe info
type StripeProfile
  @model
  @auth(
    rules: [
      { allow: owner }
      # TODO: avoid the need of the public read auth as this models intent to be private.
      # subcriptions: { level: off } while remove the subscriptions queries, yields error such as
      # "Connection failed: {"errors":[{"message":"Validation error of type FieldUndefined: Field 'onUpdateStripeProfile' in type 'Subscription' is undefined @ 'onUpdateStripeProfile'"}]}"
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  owner: String
    @auth(
      rules: [
        { allow: owner, operations: [read, delete] }
        { allow: public, operations: [read], provider: apiKey }
      ]
    )
  solUserID: ID!
  stripeAccessID: ID!
  stripeUserID: ID!
}

## Used to store private information for a given user
## Publically shared info must go into Profile
type Vault
  @model
  @auth(
    rules: [
      { allow: owner }
      # TODO: avoid the need of the public read auth as this models intent to be private.
      # subcriptions: { level: off } while remove the subscriptions queries, yields error such as
      # "Connection failed: {"errors":[{"message":"Validation error of type FieldUndefined: Field 'onUpdateStripeProfile' in type 'Subscription' is undefined @ 'onUpdateStripeProfile'"}]}"
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  owner: String
    @auth(
      rules: [
        { allow: owner, operations: [read, delete] }
        { allow: public, operations: [read], provider: apiKey }
      ]
    )
  userID: ID!
  # TODO: move this attr to StripeProfile but we need to update lambda functions first
  stripeCustomerID: ID!
}

# Store all user's created products
type Product
  @model
  @auth(
    rules: [
      { allow: private, operations: [create, read] }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  title: String!
  description: String
  image: String
  active: Boolean
  type: ProductType!
  metadata: AWSJSON
  prices: [Price] @hasMany
  stripeProductID: ID!
  # Allows to send payments after the product is being bought to the user that created the product
  makerID: ID
  maker: Profile @hasOne(fields: ["makerID"])
}

# Allow each product to have different pricing options. Emulates Stripe product/price model
# https://stripe.com/docs/products-prices/how-products-and-prices-work#what-is-a-price
type Price
  @model
  @auth(
    rules: [
      { allow: private, operations: [create, read] }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  amount: Float!
  metadata: AWSJSON
  type: PriceType!
  stripePriceID: ID!
  productID: ID!
  product: Product! @belongsTo
}

type Reputation
  @model
  @auth(
    rules: [
      { allow: private, operations: [create, read] }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  targetID: ID!
  targetType: ReputationTargetType!
  profileID: ID!
  type: ReputationType!
  value: Int!
}

# Keep the record of all orders created by a user within the system
type Order
  @model
  @auth(
    rules: [
      { allow: private, operations: [create, read] }
      { allow: public, operations: [read], provider: apiKey }
    ]
  ) {
  id: ID!
  productID: ID!
  priceID: ID!
  buyerID: ID!
  sellerID: ID!
  status: OrderStatus!
  trackingID: ID!
  stripePriceID: ID!
  stripeProductID: ID!
  metadata: AWSJSON
}

Project Identifier
976fd779f41a5b0cbe838e291735690e
Log output

# Put your logs below this line

Additional information
No response

Hi @duranmla, could you try to update to the latest amplify version and delete the 'amplify/mock-data', 'amplify/mock-api-resources' folders. I had similar issue and resolved it that way as I think there was a corrupted file.

I would love to work with latest version but I can't due to https://github.com/aws-amplify/amplify-cli/issues/9508#issuecomment-1283655867 and https://github.com/aws-amplify/amplify-codegen/issues/509 whenever I am able to go to latest I will try again.

Still worth to try the proposed without updating to latest version.

Please re-open if you're still experiencing the issue.


inference lack module

+1

Thanks for pointing out this bug. I have fixed this. Please update your code with this repo.
However, You can also comment this line for the reason that the PartialConv2d is not used by default.


Update keyboard-and-mouse-hid-client-drivers.md

Add some info about HidClass shown on picture

Thanks again!


Express Route IPv6 changes #924393

Hydra Specs PR: https://github.com/Azure/hydra-specs-pr/pull/1393

Description

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

[* ] I have read the contribution guidelines.
[ *] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] 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

[ ] 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.
[ ] 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.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@vinayada1,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Note: The ExpressRoute.Tests.csproj is broken. Ran out of options on how to fix it to make it compile. The IPv6 changes have added a new parameter to the Remove API and due to this the existing remove tests fail. It needs re-recording of tests which cannot be done due to the broken .csproj file.

https://github.com/Azure/azure-sdk-for-net/issues/3382


Invalid renames should say why they failed

Invalid renames are already rejected, but if possible they should say why, too.
Currently, for VSCode at least, an info box saying "No result." pops up, and thats it. I was unintentionally trying to rename something to a keyword, but it took a few minutes to figure out that I was doing something wrong, not rust-analyzer.

Don't know off hand how this should be handled according to the protocol, but the entry point into this functionality is here:
https://github.com/rust-analyzer/rust-analyzer/blob/b495e56b0d3f7a72494d002a69440563e8394574/crates/rust-analyzer/src/main_loop/handlers.rs#L496-L536


Create dataset ester

uid: ester
type: processed
description:

name: ESTER Evaluation de Systemes de Transcription enrichie d’Emissions Radiophoniques

description: The ESTER Corpus is a subset of the ESTER Evaluation Package (catalogue ref. ELRA-E0021), which was produced within the French national project ESTER (Evaluation of Broadcast News enriched transcription systems), as part of the Technolangue programme funded by the French Ministry of Research and New Technologies (MRNT). The ESTER project enabled to carry out a campaign for the evaluation of Broadcast News enriched transcription systems using French data.
This corpus includes the material that was used for the ESTER evaluation campaign, excluding the textual data (available in this catalogue and referenced ELRA-W0015 and ELRA-W0023):

About 100 hours of orthographically transcribed news broadcast, including annotations of named entities.
The evaluation tools allow to evaluation each task defined above.
Two guides and manuals were produced and are provided in the package distributed by ELDA :
o Guide for the annotation of named entities
o Specifications and evaluation protocol

An extra corpus of 1,700 hours of non-transcribed radio broadcast news recordings can also be provided upon request, on hard disk, as an adding to this package at a cost of 100 Euro (plus shipment fee).

homepage: http://www.lrec-conf.org/proceedings/lrec2006/pdf/646_pdf.pdf

validated: True

languages:

language_names:

French

language_comments:
language_locations:

Northern Africa
Western Europe
France
Morocco

validated: False

custodian:

name: French Ministry of Research and New Technologies
in_catalogue:
type: A government organization
location: France
contact_name: Valérie Mapelli
contact_email<EMAIL_ADDRESS>contact_submitter: False
additional: http://www.technolangue.net/article.php3?id_article=60
validated: False

availability:

procurement:

for_download: Yes - after signing a user agreement
download_url: http://catalog.elra.info/en-us/repository/browse/ELRA-S0241/
download_email:

licensing:

has_licenses: Yes
license_text: http://www.elra.info/media/filer_public/2015/04/13/enduser_150325.pdf
license_properties:

non-commercial use

license_list:

other: Other license

pii:

has_pii: Yes
generic_pii_likely: very likely
generic_pii_list:

names
dates (birth, death, etc.)

numeric_pii_likely: unlikely
numeric_pii_list:
sensitive_pii_likely: very likely
sensitive_pii_list:

political opinions
religious or philosophical beliefs

no_pii_justification_class:
no_pii_justification_text:

validated: False

processed_from_primary:

from_primary: Taken from primary source
primary_availability: Yes - their documentation/homepage/description is available
primary_license: Unclear / I don't know
primary_types:

radio

validated: False
from_primary_entries:

media:

category:

audiovisual
text

text_format:
audiovisual_format:
image_format:
database_format:
text_is_transcribed: Yes - audiovisual
instance_type: hours
instance_count: 1K<n<10K
instance_size: 100<n<10,000
validated: False

fname: ester.json

Transcripts at:

https://huggingface.co/datasets/bigscience/ester1_text
https://huggingface.co/datasets/bigscience/ester2_text

#self-assign

Done! LM repo: https://huggingface.co/datasets/bigscience-catalogue-lm-data/lm_fr_ester
Had issues (FileNotFoundError) referencing the data files from the bigscience repo, so I uploaded the data to the repo as well.

Thanks @mariosasko


Add ability to search by clicking or dropping a pin on the map

Add ability to search by clicking or dropping a pin on the map.
This came from Jeremiah, who is working with City of Phoenix.  They have noted that it would be nice to be able to click or drop a pin on the map to search.
We could approach this similar to how we have it implemented in configurable locator.

Duplicate of #219


Vector2Extensions

I did same for Vector2

Codespaces has a known issue where I can't publish an actual code review due to permissions on a forked repository.
https://github.com/microsoft/vscode-pull-request-github/issues/5325
So, I can just add some comments here.

In the Add method, this Vector3 should be this Vector2
I think the method name Remove might convey the meaning of total removal (as in setting the value to zero).  A better name would be the symmetrical word for Add, which is Subtract.  However, either naming convention could also cause some issues with clarity, as the User from the outside may be unsure if they need to supply a positive or negative number without looking at the code.
The best approach is delete the Remove method, and just keep the Add method as was done with the Vector3 extension class - the User of the method can then choose for themselves if they want to add a negative or positive amount.
There are 2 typos in the last method.  InRangeOff should be InRangeOf and curret should be current

Thanks for your contribution, always nice to see it grow!

Oh i didn't noticed this typos,
and maybe instead Add/Substract it should be named Modify?

Modify is an ok suggestion, but again will cause some ambiguity with the With method name - it's not immediately clear to the User what the modification will be - replacement, addition, or something else?  Ideally you want the extension methods to read like an English sentence.
I want a new Vector2.zero with x: 1
I want a a new Vector2.up but add y:-1
It's easy to infer what's going to happen in both those cases without looking at the code. I think it's ok to leave the naming convention the same as in the Vector3 extensions class and use the Add method name - plus it's already an established convention in videos.

One more comment:
In the <summary of the Add and With methods, remove the reference to the z param

Perfect, looks great


Add whitelisted ip address for all the publishers

Signed-off-by: Jukka Laitinen<EMAIL_ADDRESS>

We can probably take this in?
This seems to help to decrease meta traffic in mesh network.


sdl: double tap by touchpad on titlebar doesn't maximize window in GNOME Wayland

Describe the bug
sdl, wayland: double tap on titlebar doesn't maximize freerdp window.
To Reproduce
Steps to reproduce the behavior:

Boot Linux with GNOME in Wayland session
sdl-freerdp /v:ip /dynamic-resolution
Double tap by touchpad on freerdp titlebar to maximize the window
It doesn't maximize, the cursor change looks like the window wants to be moved instead
For maximizing window only triple tap works

Expected behavior
The window should be maximized by double-tap
Application details

FreeRDP version 3.1.1-dev0 (f6a208f75)
sdl-freerdp /v:ip /dynamic-resolution
Output of xfreerdp /buildconfig

This is FreeRDP version 3.1.1-dev0 (f6a208f75)
Build configuration: BUILD_TESTING=OFF WINPR_HAVE_AIO_H=1 WINPR_HAVE_EXECINFO_BACKTRACE=1 WINPR_HAVE_EXECINFO_BACKTRACE_SYMBOLS=1 WINPR_HAVE_EXECINFO_BACKTRACE_SYMBOLS_FD=1 WINPR_HAVE_EXECINFO_HEADER=1 WINPR_HAVE_FCNTL_H=1 WINPR_HAVE_GETLOGIN_R=1 WINPR_HAVE_GETPWUID_R=1 WINPR_HAVE_INTTYPES_H=1 WINPR_HAVE_POLL_H=1 WINPR_HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 WINPR_HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIBS= WINPR_HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL=1 WINPR_HAVE_STDBOOL_H=1 WINPR_HAVE_STDINT_H=1 WINPR_HAVE_STRNDUP=1 WINPR_HAVE_SYSLOG_H=1 WINPR_HAVE_SYS_EVENTFD_H=1 WINPR_HAVE_SYS_FILIO_H= WINPR_HAVE_SYS_SELECT_H=1 WINPR_HAVE_SYS_SOCKIO_H= WINPR_HAVE_SYS_TIMERFD_H=1 WINPR_HAVE_TM_GMTOFF=1 WINPR_HAVE_UNISTD_H=1 WINPR_HAVE_UNWIND_H=1 WITH_AAD=ON WITH_ADD_PLUGIN_TO_RPATH=OFF WITH_ALSA=ON WITH_BINARY_VERSIONING=OFF WITH_CAIRO=OFF WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CLIENT_SDL=ON WITH_CLIENT_SDL_AVAILABLE=1 WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_CODECS=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_EVENTS=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SCHANNEL=OFF WITH_DEBUG_SDL_EVENTS=OFF WITH_DEBUG_SDL_KBD_EVENTS=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_URBDRC=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_DSP_FFMPEG=ON WITH_DSP_FFMPEG_AVAILABLE=1 WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=ON WITH_FREERDP_DEPRECATED=OFF WITH_FREERDP_DEPRECATED_COMMANDLINE=OFF WITH_FUSE=ON WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_ICU=ON WITH_INTERNAL_MD4=OFF WITH_INTERNAL_MD5=OFF WITH_INTERNAL_RC4=OFF WITH_IPP=OFF WITH_JPEG=ON WITH_KRB5=ON WITH_KRB5_NO_NTLM_FALLBACK=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBRESSL=OFF WITH_LODEPNG=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_NATIVE_SSPI=OFF WITH_NEON=OFF WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSC_PKCS11_LINKED=OFF WITH_OPENSSL=ON WITH_OPUS=OFF WITH_OSS=ON WITH_PCSC=ON WITH_PKCS11=ON WITH_PLATFORM_SERVER=ON WITH_POLL=ON WITH_PROFILER=OFF WITH_PROXY=ON WITH_PROXY_APP=ON WITH_PROXY_EMULATE_SMARTCARD=OFF WITH_PROXY_MODULES=ON WITH_PULSE=ON WITH_RDTK=ON WITH_SAMPLE=ON WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SDL_IMAGE_DIALOGS=OFF WITH_SDL_LINK_SHARED=ON WITH_SERVER=ON WITH_SERVER_CHANNELS=ON WITH_SERVER_INTERFACE=ON WITH_SHADOW=ON WITH_SMARTCARD_EMULATE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SMARTCARD_PCSC=ON WITH_SOXR=OFF WITH_SSE2=OFF WITH_SWSCALE=ON WITH_SYSTEMD=ON WITH_THIRD_PARTY=OFF WITH_UNICODE_BUILTIN=OFF WITH_URIPARSER=OFF WITH_VAAPI=OFF WITH_VAAPI_AVAILABLE=1 WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_VERBOSE_WINPR_ASSERT=ON WITH_VIDEO_FFMPEG=ON WITH_VIDEO_FFMPEG_AVAILABLE=1 WITH_WAYLAND=ON WITH_WEBVIEW=ON WITH_WEBVIEW_QT=OFF WITH_WINPR_DEPRECATED=OFF WITH_WINPR_TOOLS=ON WITH_WIN_CONSOLE=ON WITH_X11=ON WITH_XCURSOR=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XV=ON
Build type:          Release
CFLAGS:              -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wall -Wpedantic -Wno-padded -Wno-cast-align -Wno-declaration-after-statement -fPIC -Wall -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -fno-omit-frame-pointer
Compiler:            GNU, 13.2.1
Target architecture: x64

Environment (please complete the following information):

OS: Linux
Version/Distribution: Arch, GNOME 45, Wayland session
Architecture: [amd64, arm]: amd64

Additional context
For context and discussion on similar problem read here https://gitlab.gnome.org/GNOME/mutter/-/issues/2669

title bar is managed by sdl2, nothing we can change here.


Add expiration height to contract sort

Description
Currently, contracts can be sorted by "timeline" (negotiationHeight) or status. Add an additional sort option for expiration height; the sort field is expirationHeight. An additional column on the graph for blocks remaining might be useful too.

Version
No response
What operating system are you running (e.g. Ubuntu 22.04, macOS, Windows 11)?
No response
Anything else?
No response

Closed by #67


Remove redundant null checks from Stats class.

This change should have been included in #468.

Coverage remained the same at 77.314% when pulling b501ede28d0a0b8c61dc65649c9dde6af59ba76e on sebright:redundant-null-check into 1b497401e1450154c4aca9eb4412481f8da87866 on census-instrumentation:master.

Thanks!

Codecov Report

Merging #613 into master will increase coverage by 0.06%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #613      +/-   ##
============================================
+ Coverage     75.36%   75.42%   +0.06%
  Complexity      703      703
============================================
  Files           128      128
  Lines          3328     3328
  Branches        308      308
============================================
+ Hits           2508     2510       +2
  Misses          755      755
+ Partials         65       63       -2

Impacted Files
Coverage Δ
Complexity Δ

core/src/main/java/io/opencensus/stats/Stats.java
93.33% <100%> (+13.33%)
4 <2> (ø)
:arrow_down:

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 1b49740...b501ede. Read the comment docs.


Calling se3.aba returns "random"/unstable values

Hi folks,
I designed a 8 DOF quadruped URDF model and try to use pinocchio for it's simulation (the URDF model is here). When I call se3.aba(...) after loading the URDF and creating the model/data, the returned acceloration is not stable and sometimes is nan:
# Script test.py

import pinocchio as se3
from pinocchio.utils import zero

import numpy as np
np.set_printoptions(precision=2, linewidth=160, suppress=True)

model = se3.buildModelFromUrdf('quadroped.urdf', se3.JointModelFreeFlyer())
data = model.createData()
q, dq, tau = zero(15), zero(14), zero(8)
q[6] = 1. # Unitquarternion

print(se3.aba(model, data, q, dq, tau))

jviereck@xeno-ci:~/dev$ python test.py
[[      0.  ]
 [  -3529.11]
 [     -9.81]
 [ -17252.29]
 [      0.  ]
 [  -7351.28]
 [  39102.24]
 [ -22063.81]
 [ 493649.48]
 [-498318.67]
 [  39102.24]
 [ -22063.81]
 [  50600.19]
 [ -33674.3 ]]
jviereck@xeno-ci:~/dev$ python test.py
[[  0.  ]
 [ -0.09]
 [ -9.81]
 [ -0.43]
 [  0.  ]
 [ -0.18]
 [  0.98]
 [ -0.55]
 [ 12.34]
 [-12.46]
 [  0.98]
 [ -0.55]
 [  1.27]
 [ -0.84]]

My best guess is some data was not prepared/computed before calling se3.aba(...). However, from looking at the python-bindings docstring, I don't see any hint what should be called first.
Any idea?
Best,
\jv

I am sorry, I reopened the issue because I do not get your same behaviour on code containing a similar error.
I do not see any other problems in your code. May you try to follow my advice above and tell me what you obtain?

Ok, I am now using the urdf you attached, and I get your same behaviour. I close the issue again. Hope my suggestion solves your problem.

This lines will solve the problem:
import pinocchio as se3
from pinocchio.utils import zero

import numpy as np
np.set_printoptions(precision=2, linewidth=160, suppress=True)

model = se3.buildModelFromUrdf('quadroped.urdf', se3.JointModelFreeFlyer())
data = model.createData()
q, dq, tau = zero(model.nq), zero(model.nv), zero(model.nv)

# The free flyer has an idenitity placement
q[:7] = np.matrix(se3.utils.se3ToXYZQUAT(se3.SE3.Identity())).T

# or if you want to pick a random configuration
lb = model.lowerPositionLimit # lower bound from the URDF
lb[:3] = -1e3 # Translation part
lb[3:7] = -1. # Quaternion part

ub = model.upperPositionLimit # upper bound from the URDF
ub[:3] = 1e3 # Translation part
ub[3:7] = 1. # Quaternion part

q = se3.randomConfiguration(model,lb,ub) # pick between two bounds

print(se3.aba(model, data, q, dq, tau))
print data.ddq

I also added some additional lines to allow you to exploit Pinocchio in depth (the clear documentation of the project is ongoing).

So, @jviereck, as you can see @jcarpent  is using model.nq and model.nv. In general, this is the recommended way to use Pinocchio, rather than hard-coding 15 and 14.
Then he is showing you how to create a random configuration, but you do not need it.
Notice the line
q[:7] = np.matrix(se3.utils.se3ToXYZQUAT(se3.SE3.Identity())).T
In @jcarpent 's code, it is useless, since it is overwritten later. But in your code, you may want to use this line instead of q[6] = 1. to be more robust to errors in the index.

hi folks,

I think the problem is in tau=zero(8).
For the moment in Pinocchio all joints must be given a corresponding joint torque, INCLUDING those of the base.

Spot on - this was the issue and after changing it to tau = zero(model.nv), the problem disappeared.
Thanks a lot for the quick replies & help!


.auth with no accesstoken and no secrettoken

hello guys,
just wondering if its possible to use auth().oauth() no accesstoken and no secrettoken
at the moment our services are okay to be used without those thats why specification says that we do not need them
any info/advice will be really appreciated

@gamestheory In current implementation you can leave the fields blank
Example:
 auth().oauth("Consumer Key", "Consumer Secret", "", "").

this will make request without Access Token and Token Secret


Feature/inline diff

Support rendering of inline diffs
Related PR: https://github.com/adamgruber/mochawesome/pull/167
Related issue: https://github.com/adamgruber/mochawesome/issues/160

Thanks for this @adamgruber.  Looks great!


Italic angle widget

Do not yet merge this. This is still work in progress.

I just added javascript to make it update the image overlays. Text alignment in the images is still bad, but it is kind of usable at this point.


Newsletters: add 130 (2021-01-06)

Happy 2021!

[ ] @harding update releases/RCs on Tuesday; ensure 0.21.0rc4 is actually uploaded
[x] @bitschmidty Bitcoin Core #19137 and Bitcoin Core #20365
[x] @jnewbery Bitcoin Core #20599
[x] @jonatack Bitcoin Core GUI #162
[x] @dongcarl Rust Bitcoin #499 and possibly related PRs.  This will be our first mention of Rust Bitcoin!

@harding Not too sure how to describe the GUI Peers window (some people call it the tab window) and the peer details area/window. Opted to not set off header names with quotes or backticks for sobriety/not clutter things up; feel free to change.

@harding Not too sure how to describe the GUI Peers window (some people call it the tab window) and the peer details area/window. Opted to not set off header names with quotes or backticks for sobriety/not clutter things up; feel free to change.

Added 20599. Great newsletter so far! Thanks @harding and @jonatack.

Added 20599. Great newsletter so far! Thanks @harding and @jonatack.

Pushed edits (thanks @jonatack and @jnewbery!) and reviewed the merge summaries (thanks @jonatack, @jnewbery, @dongcarl, and @bitschmidty!), with just a few small edits.

Pushed edits (thanks @jonatack and @jnewbery!) and reviewed the merge summaries (thanks @jonatack, @jnewbery, @dongcarl, and @bitschmidty!), with just a few small edits.

Squashed and merged. Great start to the year team. Really enjoying all the different contributors in addition to the new repo coverage!

Squashed and merged. Great start to the year team. Really enjoying all the different contributors in addition to the new repo coverage!


Starting Wetty from API with Custom Port is Confusing

The API docs indicate that serverPort can be set in the start call of wetty:
https://github.com/butlerx/wetty/blob/8191de94b7fa430fac80993d428c4a0f50b7a0f5/docs/API.md
The only way I could get it to start with a custom server port was to do the following:
var serverPort = 10000
wetty.start(ssh, { base:"/wetty/", port: serverPort, host:"<IP_ADDRESS>" })

This doesn't seem to correlate with the docs as I had to reverse engineer this from the index.js generated in the node_modules to get it to work.
Did I miss something obvious?

Also wanted to bring up that ssh.key isn't documented in the API.md but does work as well.

thanks for pointing this out. I had neglected the docs for a few api changes. The Api docs have been used with the changes required.


readable dash.all.min.js

Hi,
I was wondering if you could share a readable version of //pensieve/video_server/dash.all.min.js so I could make some modifications to the Pensieve player.
Thanks!

After you install the grunt dependencies (https://github.com/hongzimao/pensieve/blob/master/dash_client/README.md), you can edit the dash.js source code. For example, we updated the ABR algorithm used by the dash player by modifying this file: https://github.com/hongzimao/pensieve/blob/master/dash.js/src/streaming/controllers/AbrController.js.
After you make your edits to the source code, you will have to recompile the code to generate a new dash.all.min.js file. To do this, run ./compile.sh in the pensieve/dash.js directory.

Thanks! I will try this out.

I installed the grunt dependencies as documented in the README, and but when I run ./compile.sh in //pensieve/dash.js, I get the warning "Cannot find module 'browserify-derequire'", and the rest of the pipeline fails.
I tried installing grunt-browserify and browserify-derequire through npm, but I'm getting the same error. It seems like the browserify-derequire package has out-of-date dependencies (https://github.com/rse/browserify-derequire).
I'd appreciate it if you could give me some pointers to resolve this issue. Thanks!

We didn't hit this package installation before. Did you use python setup.py?

Yes, I ran setup.py in the //pensieve root directory. It doesn't seem to install any grunt packages, but I did install all dependencies in the dash.js source code README (https://github.com/hongzimao/pensieve/blob/master/dash_client/README.md), linked above.

I ran into a similar set of issues. I tried a few different installations in the sense that I installed many packages individually as I saw errors. I installed grunt separately, grunt-cli separately, jsdoc separately (it seems like the jsdoc-plugin is no longer the right package for higher versions of grunt), the jasmine-istanbul package, etc. I'm not entirely sure what solved it because I struggled to replicate this myself a second time, but I eventually got it to compile. Also, if it helps, the compiled dash.all.min.js will be found in dash.js/build/temp/. Sorry for not being more specific.

Thanks a lot Vibhaa. Hope this helps @arjunvb!

Thanks @vibhaa, @hongzimao. I also had to manually separately install grunt, grunt-cli, jasmine-istanbul, and several other packages. I also had to modify settings in .jshintc and .jscsrc so the existing source code met passed lint and code style checks.
I've been stuck at the browserify stage (https://github.com/hongzimao/pensieve/blob/master/dash.js/Gruntfile.js#L244). It's saying the 'browserify-derequire' module is not found even though I've installed with npm. I'm seeing a similar issue for the 'babelify' package as well. Did you ever have an issue with either of these two packages?
Thanks for your help.

@hongzimao, I got it to compile successfully! I'm not too sure what the problem was, but, to resolve the 'browserify-derequire' module issue, I went back and re-installed the dependencies listed in the README. It's possible something failed earlier that I didn't catch, but installing 'browserify-derequire' didn't help. To get the rest of it to work, I had to do several other package installs, as @vibhaa noted above.
Here's a summary of the issues I ran into when compiling dash.js from source:

Lint and code style checks failed due to warnings (e.g. variable defined but not used). I modified settings in .jshintc and .jscsrc to suppress these warnings so they didn't interfere with the rest of the compilation.
For any module that's not found, I ran npm install <module name> and re-started the compile script.
The uglify task failed several times due to memory issues. To fix this, I increased the allocated memory, by updating line 2 in compile.sh as follows: grunt --config Gruntfile.js --force --max-old-space-size=16384

Thanks!


Dlib C++ lib

add Dlib C++ lib please

@RabsRincon if you can add it it will be awsome!

Next site update will include this: headers only, available through #include <dlib/error.h> etc

It's now on the live site.


[Info Site] Add "Общи условия" and link it in the support page

When going through the support page you encounter "Съгласявам се с Общите условия" but there are no "Общи условия" links. This is linked to https://github.com/daritelska-platforma/frontend/issues/94

The page is implemented and linked in 'Support' form:
https://podkrepi.bg/terms-of-service

We can close this issues.


Errors with string_view since update to 1.81.0

When updating to boost 1.81.0, I faced some compile errors in my code along with deprecation warnings
BOOST_BEAST_USE_STD_STRING_VIEW is deprecated, use BOOST_NO_CXX17_HDR_STRING_VIEW instead

This links to #2451.
Looking into that, it looks like beast now uses always boost::core::string_view which seems to be a separate string_view implementation (with some implicit converstions to std::string_view). As it's in details, it's not documented.
Loosing the ability to directly use std::string_view looks like a step back to me. Some things that used to work don't work anymore, like implicitly assigning a string_view to a std::filesystem::path. Obviously this is nothing that can't be worked around, but this illustrates why having multiple string_view implementations isn't necessarily a good idea.
The deprecation warning seems also a bit misleading. BOOST_NO_CXX17_HDR_STRING_VIEW  seems to do the opposite to BOOST_BEAST_USE_STD_STRING_VIEW (eg. completely switch off conversions to std::string_view).
Please correct me if I got something wrong.
Would you consider bringing back the option to use std::string_view?

The idea was to unify this, because otherwise it gets weird. With the header set, boost::core::string_view can interact with std::string_view, but it doesn't work the other way.
The problem is not only that beast is a C++11 library and std::string_view C++17, it's also that the standard versions tend to become stale; e.g. boost::system::error_code now has a few nifty features not available with std::error_code. This is why there was an effort to unify towards the boost types.
I am surprised std::filesystem::path can't be constructed from a boost::core::string_view, tbh.
@vinniefalco what do you think?

I see your point about the standard libraries becoming stale from the point of view of the library author. For the specific case of std::string_view , if it's missing important features and there are plans to have bring a improved version, this is understandable. In other cases, having boost::core::string_view defined as a type alias of std::string_view when targeting C++17 or higher is going to give a better user experience (both to interact with other libraries and in the debugger).
As a library user targeting C++20, I prefer using the standard library where possible and see the boost libraries as one source of libraries to provide me the features I need (here mostly networking); similar to any other library on github. I that sense I would prefer if boost's effort for fallback implementations for old C++ standards and improved versions of existing standard library code were in a separate project. I understand this is personal opinion and doesn't align with the general direction of the boost project.
Btw, asio and beast are great!

@vinniefalco what do you think?

I prefer not to have the API/ABI of the library change based on a macro.

Feel free to close the issue, unless you think it's worth keeping it open for one of the following points:

Deprecation warning is misleading (a better message would be something like BOOST_BEAST_USE_STD_STRING_VIEW is deprecated, boost::core::string_view is always used
Beast uses undocumented private type std::core::string_view (in boost/core/detail/string_view.hpp) in it's public interface.
Cannot construct std::filesystem::path from a boost::core::string_view (this is an issue that belongs to boost/core)

About 2) I saw #110, saying:
Also, it would be a good idea to mention that boost::core::string_view is not intended to be
used by users (hence it is in detail) and is supposed to be used by Boost library writers.

and following the link there, I saw some comment in an older version of the source file
Unlike `boost::string_view`, `boost::core::string_view` has implicit
conversions from and to `std::string_view`, which allows Boost libraries that
support C++11/C++14 to use it in interfaces without forcing users to forgo the
use of `std::string_view` in their code.

Previously, I was using beast::string_view in my code when interfacing to beast for consistency. I changed all the beast::string_view in my code to std::string_view and this fixed the compile errors. I guess the missing documentation and description of the design rationale of boost::core::string_view is not ideal.

With this change and the deprecation of to_string() - snapcast fails to compile.
https://github.com/badaix/snapcast/blob/e30a9f335badc81e743c61ceda6ef2dfc698573b/server/control_session_http.cpp#L127-L185
is the fix to cast static_cast<std::string>(sv)?
Or is there a better way to fix this?
https://www.learncpp.com/cpp-tutorial/introduction-to-stdstring_view/

The documentation needs to be updated, sorry for this confusion!

Thanks Vinnie and Klemens for all your work. Unfortunately I'm a bit too far away from the code to be able to send a PR for the doc.


fix fix the float output of regression test

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Image Resizer exchanges last 2 numerals eg: 45 x 675 actually sizes to 45 x 657

Microsoft PowerToys version
0.31.2
Running as admin

[X] Yes

Area(s) with issue?
Image Resizer
Steps to reproduce
Resize and image of 1200 x 675 pixels with a resizer set to resize anything to 1200 x 675. Everythign will SAY 675, but after you size it, you will find it was resized to 657, not 675.
✔ Expected Behavior
Resizer used on  1541 x 866 image to resize the image to 1200 x 675
❌ Actual Behavior
I used Image resizer on an 1 1541 x 866 image to resize it to 1200 x 675. Sent it to my blog publisher, who rejected it for not being 675 in height. Looked at tool, it says 675. Created a new custom size to resize to 1200 x 675. Done. Resized with that "new" setting. Still got and actual 1200 x 657 (view properties).
Other Software
No response

Nevermind. It just so happens that it will resize 1581 x 866 perfectly to 1200 x 657 with any resizer I use and convert proportionately...so what I thought was a nasty little bug is nothing at all.


Subscription stuck with state: Initialising connection

I have this code:

    final websocketLink = WebSocketLink(
      subscriptionUri,
      config: SocketClientConfig(
        autoReconnect: true,
        delayBetweenReconnectionAttempts: const Duration(seconds: 2),
        initialPayload: () {
          return authTokenService.addAuthHeader(EnvVariables.currentHost);
        },
      ),
      subProtocol: GraphQLProtocol.graphqlTransportWs,
    );

    link = Link.split(
      (request) => request.isSubscription,
      websocketLink,
      link,
    );

but subscription stuck with state:  Initialising connection and no messages are comming through.
It would useful to have documentation (at least me - could not find it) or if you guys could share any possible reasons for this.
Without this i canno tmove my app to new backend which uses new protocol :(
p.s. I even reduced it to:
    final websocketLink = WebSocketLink(
      subscriptionUri,
      subProtocol: GraphQLProtocol.graphqlTransportWs,
    );

    link = Link.split(
      (request) => request.isSubscription,
      websocketLink,
      link,
    );
  }

by removing auth but result is the same....

mh could you please provide a reproduced with this API https://api.chat.graphql-flutter.dev/graphql

@vincenzopalazzo i have similar issue with url sandbox ou have provided.
It is quite difficult to provide reproducable code because it is quite a lot happening inside an app but could we agree that you  provide working example (it should have been in documentation which not exists yet) and if it works then i can

double check everything comapring to yours
dig deeper for possible reason
I will paste here either reproducable example or solution for other which you can include to documentation troubleshooting.

How about that?

@vytautas-pranskunas- you can  check the PRs and also provide a review for it, for this reason the PR are opened

But this is already merged... don't you have tests?
So you would not be providing working example right?
How you can be sure of it works of you b do not have working example?

How you can be sure of it works of you b do not have working example?

I told already, check the PR https://github.com/zino-hofmann/graphql-flutter/pull/1204 to the the example

Hmm I am confused a little bit... when i navigate to branch "chat_example" under examples i see only starwars example... https://github.com/zino-hofmann/graphql-flutter/tree/macros/flutter_chat_example

For this reason, reproduction is needed when someone submits an issue!
Regarding the log message I will have a better solution to trace the library with https://github.com/zino-hofmann/graphql-flutter/pull/1207

So at the end what you want me to do? :) ignore message or?

PRs are welcome!

I see. However it would be much quicker for author (you) to fix this one because the time i need to get into this package for such small issue will be 10x times comparing to author. If there is a bigger issue then i do not mind.

➜  graphql-flutter git:(main) git grep "Initialising connection"
packages/graphql/lib/src/links/websocket_link/websocket_client.dart:      print('Initialising connection');

Just that, 10 seconds for everyone not just for me, if you make a PR please follow https://zino-hofmann.github.io/graphql-flutter/docs/dev/MAINTAINERS.html

Heh, this is 10s you are right, but what I was talking about it is not about the message it slef but about possibility that thi smessage is just intermediate state! like:
Disconnected
Initializing
Connected
So in order to understand this i need to get into the code and this is time consuming thing ;)

however, few lines bellow there is a line with:
_connectionStateController.add(SocketConnectionState.connected);

mabe we need to add another message there
print('Connected to websocket');

PR is added: https://github.com/zino-hofmann/graphql-flutter/pull/1309


Can't install a Visual Studio 2022 error code 110

Operating System: Windows 11 Pro
Can't install .NET Multi-Platform AP UI for Visual Studio Community. Unknown error, journals shows code 110.

It would be better to use the report a problem feature inside VS to report this:
https://developercommunity.visualstudio.com/VisualStudio/report#:~:text=How to report a problem for Visual Studio,email with a link for the submitted problem.
That way the issue is routed to the appropriate team.


LimitToUser doesn't work if NSUserName is not lowercase

https://github.com/SAP/macOS-enterprise-privileges/blob/4ab3d190cc827f059e3779a5a09d2921c71b4459/source/Privileges/AppDelegate.m#L370
In an environment where the NSUserName value is not all lowercase, the LimitToUser feature doesn't work, because the input from the config profile automatically gets lower-cased. The case normalization would need to happen on both sides being compared, or better, should do a case-insensitive comparison. Something like:
(limitToUser && !([limitToUser caseInsensitiveCompare:_currentUser] == NSOrderedSame))
I wasn't able to test above, due to issues with the linking in the Xcode project I encountered.

Thanks. This will be fixed in the next release of Privileges.

Thanks, Marc! Great to hear!


Add github actions

It should be quite easy to add some github actions to run the tests on each commit/PR and deploy the files to github pages, if the build was successful. This would guarantee that contributions don't break tests and that people can simply test the VM directly in the browser without having to manually compile it.

I believe that some of @jamesdiacono recent improvement to the automated test infrastructure should make this easier. I'd love to see an automatically-update github-hosted uFork VM debugger instance.

I was recently trying to get github pages to work, but they don't set the wasm mime type properly, so I need to work around that somehow. I'll check how trunk or wasm-pack loads the wasm, because I know they work on pages.
I can testing for that too, so that only fully tested code gets pushed to pages.


[#348] Add Makefile to build commands

Close #348

What happened 👀
A Makefile is added to simplify app setup and runs.
Insight 📝
The following commands can be run through the Makefile:

make db/migrate
make db/rollback
make db/wait-for-postgres
make db/seed
make env/setup
make env/teardown
make dev
make install_dependencies
make test
make test/docker
make generate-sprite
make codebase
make codebase/fix

Proof Of Work 📹

@tyrro do you have plan to complete this PR? If yes, may you let me know when? :) Thanks!

@tyrro do you have plan to complete this PR? If yes, may you let me know when? :) Thanks!

It's a bit late but it's ready for review now, Thanks 😅


Update to latest WinUI 2.3 release package

Description

Updates the WinUI Nuget package version to latest 2.3 release.
Motivation and Context

Several PRs (#279, #274) are targeting different versions of WinUI. Lets snap to the latest release version.
How Has This Been Tested?

Manual
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

:shipit:


Multiple scheme permissions issue

React-Native version : 0.57.
Platform: iOS
Device: Simulator & Device
OS version : 12.1
react-native-permissions version 1.1.1
Devtools: Xcode

Hello,
I'm having issues requesting permissions on the production scheme of my app.
When I'm using the Debug scheme everything works fine and I get the Debug App in the Settings screen, only when I'm in production nothing appears and when requesting the permissions. Nothing is happening.
I'm wondering if this has to do with the fact that I have multiple scheme using multiple bundle id for the same app?
Any ideas?

I have the same problem. Everything is working in the development environment but crashes in production. With some data from the report, I found that the problem is in getPermissionStatus function.

I figured out that in my case the problem was that I was linking the library libReactNativePermissions.a only for debug scheme and forgot to link it in other schemas

My issue is that I wasn't properly asking for the permissions when the state was undetermined.


chore: do not depend on CategoryTheory in Module.Injective

The category-theoretic results can be split between Mathlib/Algebra/Category/Grp/Injective.lean and Mathlib/Algebra/Category/ModuleCat/Injective.lean instead, with no changes to downstream proofs.

Thanks!
bors merge


dist tags

npm publish --tag my-tag
latest is default tag
allows betas
reference @boennemann's blog post

Hey @ashleygwilliams,
thanks for referencing it here, the post is public now :)
https://medium.com/greenkeeper-blog/one-simple-trick-for-javascript-package-maintainers-to-avoid-breaking-their-user-s-software-and-to-6edf06dc5617


Composed names are still broken

test.eo:
+alias main

[x] > test
  main.foo > @
    x

main.eo:
[] > main
  [x] > foo
    div. > @
      42
      x

Output:
RESULT BY AnFaR:
	\perp at {x=NONE}
RESULT BY AnOdin:
	Odin is not able to analyze the code, due to:
	Could not set locator for non-existent object with name "main"

Why is this a problem? Could you specify the expected behaviour?
Yes, Polystat does not currently support imports via +alias. We are working on it in https://github.com/polystat/odin/issues/15, but for now, please submit code with inlined imports.
However, this does not mean that Polystat is "broken", it is a known limitation.

@fizruk
Thanks for answer.


JS Threads Service: Core API

Fixed with https://github.com/textileio/js-threads/tree/master/packages/service


Migrate away from Ringpop use in cadence

Overview
Cadence uses ringpop for discovery of services, maintaining a hash ring to map workflows/task lists to shards. For this purpose ringpop has generally worked well - except for some issues when hosts have shown high CPU usage. Ringpop though is deprecated - with no support or new features. Given this we would like to move away from Ringpop

Remove dependency from a deprecated library
GRPC - Ringpop has a tchannel dependency and adding grpc support will require adding new features to Ringpop
Better debugging of issues when they happen

At the same time there are a number of good things about gossip based discovery that we ideally do not want to lose when moving off Ringpop

Time to detection of hosts going down is of primary importance and Ringpop can detect failures quickly on the order of 1-2 seconds

False positives are ok as the consistent store ensures correctness

No dependency on an external consistent store like zookeeper, etcd, cassandra etc
Scalable to 100s/1000s of hosts

Options
We have 3 different classes of options to replace Ringpop
Use a gossip based solution

Resurrect/rewrite ringpop to adding the visibility features we require and adding grpc support when necessary. GRPC would likely turn into a full overhaul of ringpop and mean we take ownership of Ringpop going forward
Use an alternative like serf that is more widely used and has support from hashicorp

Membership library on top of our persistence layer
This maybe a good option to provide for general open source customers to run things out of the box

Simple algorithms registering members and having a leader create a topology will not scale to our future requirements
If run on the same cluster, membership and persistence will affect each other, so need to think about isolation here

Standard service discovery mechanisms
We can use standard service discovery mechanism built on top of Zookeeper/etcd/consul etc. These systems are widely used for membership and shard allocation purposes. They would give us perfect membership at the cost of availability as they are CP systems
Choice
Given the general requirements and our experience with Ringpop, using a gossip based solution seems to be the right path forward as the

Membership library on top of persistence layer will not scale
Zookeeper/etcd/consul give perfect consistency at cost of availability. The major downside is that this would be an additional external dependency
Gossip based methods work well as consistency issues are handled by the persistence layer and having multiple owners of a shard is not a correctness issue - the reason for the original choice of Ringpop

Among the two possible gossip solutions, serf seems like a good path to take. Serf is supported, used in all of hashicorp’s products (nomad/consul) and generally feature complete. We would need to do some work to bring serf into Cadence server

Add ability to bootstrap from persistence

Nodes when up will register themselves with persistence periodically (10 mins)
When nodes come up they look for a list of nodes registered and try to join a ring. If none exist they just end up starting the ring

Add ability to use UNS/DNS for initial discovery

This seems to be possible by adding support for a new transport using the Transport interface

Hashring support - Serf only provides a memberlist that is constantly updated. We need to add a membership layer to map keys to members by building some form of hashring on top of the memberlist.

Prototype
An initial prototype of using Serf for our membership monitor is available in #1743. This pulls in serf and runs our integration tests using a newly implemented serf monitor by using a static configuration.

Hi, I found this ticket while searching for information about Ringpop's deprecation. Is there any related documentation about what happened and why Ringpop is no longer being supported? Does it have a fundamental problem or some lesson, or was it just no longer interesting to develop?


Definition for ST7735 0.9" 160x80

hi, I want try use this display, where is display definition?
O need definition for IDE and for hardware (D51)
Thanks

@mmoskal

Please ask the question in forum.makecode.com

Only 160x128 displays are supported.


stack maps?

I remember reading that Go functions must provide a stack map,
to inform the garbage collector on which stack locations contain pointers.
Does the Assembler.MakeFunc() create a stack map for functions?
I guess generating a reduced stack map only for input and output parameters would still be quite useful.

https://github.com/golang/go/issues/20123

yes, no stackmap
no morestack
call other function

all these things needs to be added


chore: migrate app insights instance to log analytics workspace-based instance

migrate to LAW app insights
migrate to Bicep

Deployment test: https://dev.azure.com/tapioone/tapio/_build/results?buildId=139349&view=results


feat(frontend): implement OAuth authentication

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Refer to https://github.com/risingwavelabs/risingwave/issues/11440.
Support to authenticate with OAuth token acquired from cloud.
The basic workflow can be tested as follows:
# create a new user test with OAuth authentication
echo 'create user test with oauth' | psql -h localhost -p 4566 -d dev -U root
# password here is actually OAuth token, and would be passed with plaintext
psql -h localhost -p 4566 -d dev -U test

The url of JWKS server can be set with
alter system set oauth_jwks_url to 'xxx://yyy.zzz';

kid and alg are required in the header of JWT, and kid is also required in the JWKs returned by the JWKS server.

Checklist

[x] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[x] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.
New system parameter:

Config
Description
Mutable
Type
Default

oauth_jwks_url
Url to get JSON Web Key Set(JWKS) for oauth authentication.
true
String
https://auth-static.confluent.io/jwks

Good Job! Have you tested it with @xuhui-lu ?

Not yet. Waiting for @xuhui-lu to provide a test jwks server and jwt.

Hi @Rossil2012 , I resolved all comments and pushed some commits directly in this PR. Please help to verify if on your local setup. Let's merge it and cherry-pick to release 1.7 if it works.

Hi @Rossil2012 , I resolved all comments and pushed some commits directly in this PR. Please help to verify if on your local setup. Let's merge it and cherry-pick to release 1.7 if it works.

Wow, thank you! However, in order to support per-user oauth configuration, @xuhui-lu and I determined to add a new syntax like create user u with oauth (jwks_url = 'xxx', user_id = 'xxx'). This way we can enable a more flexible check on the claims decoded from jwt, and community users can build their own oauth authentication workflow by specifying static config in user creation and dynamically check them in jwt header. I will release the details in the introduction later. The system params will not be used then🤣.

Hi @Rossil2012 , I resolved all comments and pushed some commits directly in this PR. Please help to verify if on your local setup. Let's merge it and cherry-pick to release 1.7 if it works.

Wow, thank you! However, in order to support per-user oauth configuration, @xuhui-lu and I determined to add a new syntax like create user u with oauth (jwks_url = 'xxx', user_id = 'xxx'). This way we can enable a more flexible check on the claims decoded from jwt, and community users can build their own oauth authentication workflow by specifying static config in user creation and dynamically check them in jwt header. I will release the details in the introduction later. The system params will not be used then🤣.

So IIUC the current implementation is not considered as a stable or final one, right? Is that so urgent that this should be released in 1.7? I would suggest to wait for 1.8 which IIRC will be frozen in recent days.

Hi @Rossil2012 , I resolved all comments and pushed some commits directly in this PR. Please help to verify if on your local setup. Let's merge it and cherry-pick to release 1.7 if it works.

Wow, thank you! However, in order to support per-user oauth configuration, @xuhui-lu and I determined to add a new syntax like create user u with oauth (jwks_url = 'xxx', user_id = 'xxx'). This way we can enable a more flexible check on the claims decoded from jwt, and community users can build their own oauth authentication workflow by specifying static config in user creation and dynamically check them in jwt header. I will release the details in the introduction later. The system params will not be used then🤣.

So IIUC the current implementation is not considered as a stable or final one, right? Is that so urgent that this should be released in 1.7? I would suggest to wait for 1.8 which IIRC will be frozen in recent days.

This feature may be urgent for cloud, cc @xuhui-lu.

Hi @Rossil2012 , I resolved all comments and pushed some commits directly in this PR. Please help to verify if on your local setup. Let's merge it and cherry-pick to release 1.7 if it works.

Wow, thank you! However, in order to support per-user oauth configuration, @xuhui-lu and I determined to add a new syntax like create user u with oauth (jwks_url = 'xxx', user_id = 'xxx'). This way we can enable a more flexible check on the claims decoded from jwt, and community users can build their own oauth authentication workflow by specifying static config in user creation and dynamically check them in jwt header. I will release the details in the introduction later. The system params will not be used then🤣.

So IIUC the current implementation is not considered as a stable or final one, right? Is that so urgent that this should be released in 1.7? I would suggest to wait for 1.8 which IIRC will be frozen in recent days.

This is related to a page revamp recently proposed by yingjun. We need this feature to remove the password for accessing cloud web console.


Improve error when build fails

Currently this happens:
2019/11/13 14:27:12 Updating vulnerability database...
2019/11/13 14:27:12 Updating php-security-advisories data...
2019/11/13 14:27:12 error in php-security-advisories update: failed to update compose vulnerabilities: batch update failed: error in batch update: failed to walk compose advisories: lstat /Users/simar/Library/Caches/trivy-db/php-security-advisories: no such file or directory
➜

The error could be improved as it stands, it's not quite clear what's going on.

Hi! I'd like to work on this for hacktoberfest. Could anyone tell me what the error should ideally convey?


Continuous Delivery via OLM

We were working on a system to deliver Hive builds continuously to stage, and ultimately prod environments that would look as follows:

Job runs on every merge to master.
Checkout hive.git master.
Build an image and publish to registry with git shorthash as the version. (i.e. quay.io/dgoodwin/hive:5f9f2d45)
Run script to generate operator bundle:
Copy CRD definitions in.
Generate CSV from a template:
1. Extract RBAC rules from our normal Role yaml files and embed.
1. Extract Deployment spec from our normal Deployment yaml file and embed.
1. Set version to git shorthash.
1. Replace image with new image built above.
1. Update CSV name to hive-operator-shorthash.
1. Update package file to reference above CSV name.

We would then want the stage environment to automatically install new releases as they became available. Prod would possibly be manually triggered, but it's worth noting that not every iteration that goes to stage would go to prod.
We do not know anything about past CSVs or what version we're replacing.
It looks like there are several problems we're going to hit with this.

To upgrade, we need all previous CSV versions in the bundle. Under the above scheme there is no persistent data store for CSVs.
We do not know what shorthash the previous build was, more state that would need to be maintained somehow.
If a CSV can only reference one version it replaces, and not all versions go to prod, it sounds like prod might easily become un-upgradable. Stage went from A -> B -> C -> D, Prod is still in A, D is deemed ready for prod but it replaces C, not A.

Is what we're trying to accomplish possible today? Are there better approaches or workarounds?

Thinking about this some more, we could use the registry itself as the persistent data store.
During CD jobs we could

generate new CSV and copy CRDs into new bundle dir.
lookup latest bundle version, we will need to bump it, and parallel processes may be trying to do this, when the second one goes to publish new bundle it will fail as the first claimed the new bundle version number. this should kill the job and cause a retry.
download latest bundle yaml.
extract package data from latest bundle.
set new CSV "replaces" to the current CSV in package data for our channel.
extract all past CSVs from latest bundle and copy to new bundle dir.
extract any CRDs in latest bundle that are no longer present in new bundle. (presumably old CRDs must remain in the bundle for old CSVs (edge case))
publish new bundle dir, now with all past CSVs, each referencing correct "replaces".

Would any part of this functionality fit in operator-courier? Some kind of operator-courier update-bundle command?

Thanks for writing this up @dgoodwin!
Based on your requirements/environment, there might be several reasonable options:

As you outlined, generate a new operator bundle (CSV, CRDs) for your latest version
Put that bundle into a catalog by itself
Update staging with that small catalog
Remove previous staging version and install latest from the new catalog

or, if you have kubectl access to your staging cluster:

Same as above, but pull the hash of the currently running CSV and reference it in the replaces field
Don't need to remove the old version, publishing the new small catalog will update the staging operator

or, if you want keep a record of everything you've done:

Once you have a bundle, add it to a catalog and push the catalog to an image registry
During CI, pull down the previous version of that catalog image, and add a layer to it to add your latest version on top (you'll hit layer limits unless you do squashing as well, but if you use quay you can have quay do that for you)
Push the new catalog back to the registry and reference it in your staging cluster. OLM will update the operator and you'll have a catalog with old versions.
Depending on how frequently you're doing this, you may want to prune older versions. You could aggressively prune everything but (latest - 1) each time you build a catalog.

As your second comment suggests, you can do similar things by looping courier / appregistry into your workflow, but you will need marketplace running for that.

Would any part of this functionality fit in operator-courier? Some kind of operator-courier update-bundle command?

Maybe - it also overlaps a little with operator-sdk's olm tooling.

We ended up building up registry image that maps each version to the next in the CI job. Closing for now.


Account for offset when multiplying models symbolically

Codecov Report

Merging #967 (7ae5654) into main (43fa430) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #967   +/-   ##
=======================================
  Coverage   84.06%   84.07%
=======================================
  Files          81       81
  Lines        6910     6912    +2
=======================================
+ Hits         5809     5811    +2
  Misses       1101     1101

Impacted Files
Coverage Δ

dimod/binary/binary_quadratic_model.py
91.71% <100.00%> (+<0.01%)
:arrow_up:

dimod/quadratic/quadratic_model.py
93.00% <100.00%> (+0.01%)
: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 43fa430...7ae5654. Read the comment docs.


Presenter not applied

As the title states; if any presenter has been defined, it won't get applied when returning models using Datatables.
I tried to apply the presenter on each item in a Collection:
$blocks = Block::all()
$blocks->transform(function($model) { return AutoPresenter::decorate($model); });

return Datatables::of($blocks)->make(true);

but unfortunately an error is thrown stating that the presenter doesn't support array access:
Cannot use object of type BlockPresenter as array in yajra/Datatables/Engine/CollectionEngine.php:233.
Probably converting the source code of laravel-datatables using object-relational retrieval of attributes will solve this...

Haven't tried Presenter on this package but I think it's only applicable on Eloquent? Can you try using Book::get() instead of Book::all(). Also, another way to decorate the output is by using league\fractal. Function to use is setTransformer('App\Transformer\DataTransformer').

Thanks for your reply. Presenters get applied to Eloquent models bound to views, paginator instances and Collections consisting of Eloquent models.
get() and all() both won't get "presented" when returned by Datatables.
Fractal will probably work, but aren't we just setting the same logic in two different places? It seems rather odd to me..

can you please provide the specific presenter package you are using. For Collection to work, it requires a Collection object and I think the transform method converts it to another object. I think you should turn it back to collection like:
$blocks = Block::all()
$blocks->transform(function($model) { return AutoPresenter::decorate($model); });
$data = new Collection($blocks);

return Datatables::of($data)->make(true);

@Propaganistas I guess you are using laravel-auto-presenter. I've checked the package and it seems that the decorators is just listening on view content.rendering event which causes the decorator to fail (not triggered) because we are not using View to display the datatables output. We are using JsonResponse here because the package is an API for Datatables.
A workaround that I can think of for this to work is by overriding the toArray on your model and perform the decorations. But I'm checking the presenter package. I might me missing some things and I think it's a good feature to support it.

@Propaganistas laravel-auto-presenter is indeed not working on RESTful/API approach and presenter does not work because we do not render a view. https://github.com/laravel-auto-presenter/laravel-auto-presenter/issues/69

@GrahamCampbell
Not sure what you mean. If you're not rendering a view, we can't automatically present your models for you. There's nothing special or magic about laravel. It's just php code.

You can however, manually present your models using our facade, or by dependency injecting our presenter decorator class.

In this case, I suggest you use the fractal approach and create your own Transformer. But I'm accepting PR in case you have some idea on how to integrate the presenter package.


Add Assist: Add lifetime to type

struct Example {
    ex: &i32
}

into
struct Example<'a> {
    ex: &'a i32
}

I will take that point

I will take that point


Powertoys run cuts off input or uses previous input (19157)

Summary of the Pull Request
Updated code to disable using the enter key to activate the selected item in the results if new PT run search has started. This prevents the enter key from activating stales results.
PR Checklist

[X] Closes: #19157
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments
IsTemporaryDisabled is set to true when new search starts.
IsTemporaryDisabled is set to false (enable  to acivate selected item) when the new results are added to the result list.
Validation Steps Performed
You can test this by exacerbating the issue, by increasing the "search delay" to a very high number.

I am converting this to draft for a little more discussion.
I think the issue is pretty clear, but way to address has a few possible solutions.
The real issue seems to be due to the non-uniform nature of the results. The types of results are:

Real-time and deterministic (like Calculator, Web Search)
Real-time and nondeterministic (like Time and Date)
Non-real-time, nondeterministic (all the others that do a real search, and results)

People that use the "Real-time" results are getting tripped up by the "search delay", because
Clearly "Real-time" plugins and "delay search" don't play well together, and that makes sense.
So, the main choice is what to do with existing results, at the moment AFTER the user starts typing, and BEFORE the new results have been generated. (Of course only applies when Delay Search is enabled).

Leave the results 100% as they are. This is what we do now. The issue this causes is... a user can start a search, and hit enter before the new results are in, and it can/will activate an "irrelevant" item, because it won't be in the results for the current query.
Hide the last results when typing starts.
Leave the results, but deselect all, so <enter> cannot activate a stale result.

#3 feels the pretty good to me.
@jaimecbernardo, @htcfreek ?

Hi @jefflord
Thanks for contributing this fix.
I think that after the users starts typing, the current results get deselected already with your PR, right?
So I think the question here is what to do when there's results for the current query but we're still waiting on delayed execution results. I think in that case leaving the current behavior as it is should work fine, since it's not like pressing Enter will trigger an "old results" from a previous query.
Does this make sense or did I understand the question wrong?

@jaimecbernardo I think this is ready for review?

Overall experience with this change is better. However, I feel like Delay search option becomes obsolete with delaying only delayed plugins

I don't know that I agree, and some chosen class names might be making this more unclear.
Please correct me if I am wrong on these.

The "delay search" really is throttle. This means it's job is to prevent the user's blast typing from producing unnecessary load on the system. Some plugins (like calc, web search, url hander, etc...) don't need this and is bad for them.
IDelayedExecutionPlugin really means "I am a potentially show/heavy plugin, please be aware". And so in this case, a throttle is important.

If the above are correct, that means we should only apply the throttle to IDelayedExecutionPlugin(s). which is what I tried to do.

@jefflord
https://github.com/microsoft/PowerToys/blob/main/doc/devdocs/modules/launcher/architecture.md

@jefflord https://github.com/microsoft/PowerToys/blob/main/doc/devdocs/modules/launcher/architecture.md

Awesome, I will read.

Overall experience with this change is better. However, I feel like Delay search option becomes obsolete with delaying only delayed plugins

I don't know that I agree, and some chosen class names might be making this more unclear. It almost makes sense... only delay the delayed search plugs, right? Though I am sure you could make the case that some non-IDelayedExecutionPlugin need to be throttled, well, if that's the case, convert them to IDelayedExecutionPlugin(s).

Please correct me if I am wrong on these.

The "delay search" really is throttle. This means it's job is to prevent the user's blast typing from producing unnecessary load on the system. Some plugins (like calc, web search, url hander, etc...) don't need this and is bad for them.
IDelayedExecutionPlugin really means "I am a potentially show/heavy plugin, please be aware". And so in this case, a throttle is important.
If the above are correct, that means we should only apply the throttle to IDelayedExecutionPlugin(s). which is what I tried to do.

Ok, Delay search option makes sense to stay I guess, as it makes PTRun less CPU consuming when needed. However, let's rephrase the description of the option as with as it is now users might expect that it'll delay everything

let's rephrase the description of the option as with as it is now users might expect that it'll delay everything

100% agree, something needs to be updated.
Here's my question, why is it called "IDelayedExecutionPlugin" if it's not always (but instead optionally) delayed? It seems like this should always be on, and we just need a settings for the value. A value of zero would effectively disable it.
If I had a time machine (or we can do this now).

Kill PowerLauncher_SearchQueryResultsWithDelay. It's should always be on.
Set the default for PowerLauncher_SearchInputDelayMs to be 50ms

If we don't get to "make it right, right now", a suggestion would be this:

In any case @stefansjfw should this change be a new issue/PR, linked to this?

Actually, search throttle is supposed to throttle the search for every plugin.
It acts like a "wait for more input" before searching. Does this PR change that?

The actual need for search throttle is also thought of for slower computers that get choppy when they need to update the UI, leaving a unpleasant and jumpy experience when inserting input, so I think it should still affect every plugin.
For some context:
https://github.com/microsoft/PowerToys/issues/11176
and
https://github.com/microsoft/PowerToys/pull/18290

I did a quick test using a fixed 20% ratio (instead of a new setting). So, at the default 150ms for the delay, that would be 150ms throttle for the delayed plugins and 30ms throttle for non-delayed plugins.
It feels like a really good middle ground.
Even with a monster 250ms throttle, that's just 50ms for the fast plugins, feels almost instant.

Took another look at this :)
I think this is shaping up very nicely. Thanks for your work here and all the testing.
I guess it might make sense to set two values from settings, then. Something like leave the current field for the "non-delayed" execution plugins and adding a new one for the "delayed" execution plugins.
I think it's OK with having default values with 30ms to 150ms or 50ms to 150ms.
How do you feel about this @jefflord

Yes @jaimecbernardo, I agree a setting for each would be best, even though there is more to document/understand.
However, I feel like it's a good time to bite the bullet here and relabel these more accurately. I say this because if we're have to make it more complicated right now, we should take the opportunity to make it clearer.
What do you think about this version?

The word "throttle" jives with the icon more than the word "delay".

@jefflord
This is more of a "debounce" than a "throttle", but I think users will understand "throttle" better. I'm OK with it.
Regarding fast and slow plugins, I feel like that's not exactly what they are.
Here's what I'm thinking better describes them. What do you think?
Search throttle
Wait for more input before searching. This reduces interface jumpiness and system load.
Immediate plugins
Throttle the plugins that make the UI wait for their results by this amount. Recommended: 30-50 ms
Background execution plugin
Throttle the plugins that execute in the background by this amount. Recommended: 100-150 ms

@jaimecbernardo
I think you nailed it. Yes, debounce is more correct. (We can take that up with the System.Reactive team LOL). We could avoid it all by calling it something whacky/made up like "Input Smoothing". The rest is also perfect. Immediate/Background is good. I like it because it makes a lot of sense for "Immediate" plugins like calculator/date/etc...
I think we're there and would be happy with what you sent, but if you don't mind one more review pass on this? Whatever you comeback with will be good with me I am sure.
Input Smoothing
Wait for more input before searching. This reduces interface jumpiness and system load.

Immediate plugins
Effects the plugins that make the UI wait for their results by this amount. Recommended: 30-50 ms

Background execution plugin
Effects the plugins that execute in the background by this amount. Recommended: 100-150 ms

@jefflord ,
"Effects" should be replaced with "Affects" (effects is a noun while affects is a verb)
Other than that, it looks good to me. Thank you! ;)


WCO buttons not aligned

I am running from Electron 19 branch, out of sources and see this:

Btw why is WCO disabled when running out of sources?
//cc @deepak1556

WCO is disabled out of sources since you are likely to open dev tools and there is this issue https://github.com/electron/electron/issues/34129

@deepak1556 looks to be on the electron side =>

Yes we have a slight pixel buffer underneath the controls to account for window border, but even within the bounds of the controls, the restore down icon is quite off

Upstream issue https://github.com/electron/electron/issues/35038

WCO is disabled out of sources since you are likely to open dev tools and there is this issue electron/electron#34129

@sbatten now that #161027 has merged can WCO be permitted when running out of sources?

There's still https://github.com/microsoft/vscode/issues/159813, but manually enabling the setting in Code-OSS should be fine.

@rzhao271 I tried enabling it in my Code-OSS settings but it didn't seem to work. The sentence from @sbatten that I quoted make me think it had been hardwired off in Code-OSS. I haven't searched the codebase yet though.

Verification steps:

Enable the WCO by enabling the window.experimental.windowControlsOverlay.enabled setting.
Restart VS Code when prompted and confirm that the restore button is aligned with the minimize and close buttons.


Fritzbox Wifi as Switch

Description:
Please be kind. It is my first OpenSource Pull request.
**Pull request in home-assistant.io with documentation (if applicable): https://github.com/home-assistant/home-assistant.io/pull/7935
Example entry for configuration.yaml (if applicable):
switch:
   - platform: fritzbox_wifi
     host: 192.168.XXX.XXX
     password: "YOURPASSWORD"
     name: "NAME_OF_THE_SWITCH_SHOW_UP_IN_HA"
     interface: 3

Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

This has nothing to do with the plugin i think, but how can i fix it:
SKIPPED:  py35: InterpreterNotFound: python3.5 (ok i can install Python 3.5&3.6&3.8 with homebrew)
SKIPPED:  py36: InterpreterNotFound: python3.6
  py37: commands succeeded
SKIPPED:  py38: InterpreterNotFound: python3.8
ERROR:   lint: commands failed
ERROR:   pylint: could not install deps [-r/Users/user/Documents/GitHub/home-assistant/requirements_all.txt, -r/Users/user/Documents/GitHub/home-assistant/requirements_test.txt, -c/Users/user/Documents/GitHub/home-assistant/homeassistant/package_constraints.txt]; v = InvocationError('/usr/bin/env LANG=C.UTF-8 pip install -r/Users/user/Documents/GitHub/home-assistant/requirements_all.txt -r/Users/user/Documents/GitHub/home-assistant/requirements_test.txt -c/Users/user/Documents/GitHub/home-assistant/homeassistant/package_constraints.txt (see /Users/user/Documents/GitHub/home-assistant/.tox/pylint/log/pylint-1.log)', 1)
ERROR:   typing: commands failed
  cov: commands succeeded

P.S. Not sure how to fix this. Running a mac

[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

Hi @BitTourette,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

@BitTourette: I would really like this component. If you need any help with the PR, let me know!

This PR seems to have gone stale. Closing it.

Sry... was a bit bussy... will do this tomorrow

@BitTourette Will you still work on this? I would really like to see this feature land in HA and I may have some time this week to do the requested code changes...


Feat/breadcrumbs

:tada: This PR is included in version 1.1.0-develop.22 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


cross owner copying not yet implemented error

I am attempting to use conda-build-all to upload to our internal anaconda server and am getting the following traceback.
Traceback (most recent call last):
  File "/tmp/root/ramdisk/mc/bin/conda-build-all", line 9, in <module>
    load_entry_point('conda-build-all==0.8.1.dev14', 'console_scripts', 'conda-build-all')()
  File "/tmp/root/ramdisk/mc/lib/python3.5/site-packages/conda_build_all-0.8.1.dev14-py3.5.egg/conda_build_all/cli.py", line 85, in main
    b.main()
  File "/tmp/root/ramdisk/mc/lib/python3.5/site-packages/conda_build_all-0.8.1.dev14-py3.5.egg/conda_build_all/builder.py", line 208, in main
    self.post_build(meta, built_dist_location, was_built)
  File "/tmp/root/ramdisk/mc/lib/python3.5/site-packages/conda_build_all-0.8.1.dev14-py3.5.egg/conda_build_all/builder.py", line 225, in post_build
    artefact_destination.make_available(meta, built_dist_location, was_built)
  File "/tmp/root/ramdisk/mc/lib/python3.5/site-packages/conda_build_all-0.8.1.dev14-py3.5.egg/conda_build_all/artefact_destination.py", line 119, in make_available
    raise NotImplementedError('cross owner copying not yet implemented.')
NotImplementedError: cross owner copying not yet implemented.

I am executing conda-build-all with
$ conda-build-all ../staged-recipes-dev/ --upload-channels nsls2-dev --inspect-channels nsls2-dev --matrix-conditions "python >=3.5"

I'm not convinced that I am trying to copy across owners which makes this error all the more puzzling. Additionally puzzling is that this is failing on different packages each time I run the aforementioned conda-build-all command.
Have you seen this before?
So I did a bit of investigation after I wrote the stuff above, but before I posted the issue.  Updating to conda-build master seems to fix this problem.  I will go ahead and post this and then close it immediately, mostly for posterity's sake.

So this is actually due to a logic bug in artefact_destination.py.  I'll submit a PR to fix it

Good detective work @ericdill :mag:


[2.0.1][Fix-7284] [api] Fix the missing project information in the process instance timeout alarm

Purpose of the pull request

cherry-pick #7298
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

test:


spicy_add_analyzer: Do not use SCRIPTS

The SCRIPTS parameter for spicy_add_analyzer() is not functional, so rendering it into CMakeLists.txt is confusing [1]. Remove it.
These scripts are installed via zkg.meta's script_dir here in the template.
[1] https://github.com/zeek/cmake/issues/97

The CMakeLists.txt is also reused for packet and file analyzers which don't have dpd.sig anyhow.


position of element also changes size

The component has a very strange behavior when entering the top/left styles to set the position. Instead of the position, the size also changes debendend on the values of the top: xx%/left: xx% styles.
For all other elements of the picture element such as state-icon, state-label, image, ... you set the position with top/left and set the size with transform: scale(0.2,0.2)
This behavior also results in very strange values for  top: xx%/left: xx% compared to the other elements.
Example here a state-label and the cover-icon-element will be positiones at a similar place on the picture:
  - type: custom:cover-icon-element
    entity: cover.k13_003_wohnzimmer_rollladen_links_03
    title: Rollladen Links
    opacity: 0.08
    tap_action:
      action: more-info
    style:
      top: '-8%'
      left: 3%
      color: black
      transform: scale(0.2,0.2)
  - type: state-label
    title: Rollladen Links
    tap_action:
      action: more-info
    entity: cover.k13_003_wohnzimmer_rollladen_links_03
    style:
      top: 22%
      left: 34%
      color: black

To get an approximately same position of the cover-icon-element you even have to move the top position to the negative.
On the same picture element I have another  cover-icon-element on an other position. To have the same zize, it needs compleetly different scaling factor to have this shown with the same size as the element on the other position.
  - type: custom:cover-icon-element
    entity: cover.k13_001_wohnzimmer_rollladen_fenster_01
    title: Rollladen Fenster
    opacity: 0.08
    tap_action:
      action: more-info
    style:
      top: 56%
      left: 86%
      color: black
      transform: scale(0.8,0.8) rotate(-90deg)

I can reproduce this as well, and I also have to account for this behavior when placing this element in the picture-element card. Not quite sure why it behaves like that 🤔


Poor formatting for super parameters in IntelliJ

In a file in a package that has the super_parameters experiment enabled, paste the following:
class A {
  A(int x);
}
class B extends A {
  B(super.x);

Then type a } at the end of the file (I was on the next line when I tested this).
The constructor declaration will be poorly formatted so that each token is on a separate line.

@jwren

Thank you for the bug report @bwilkerson -- I can't seem to configure such a project myself, I am getting both a message that I need to enable super-parameters, and that it isn't supported, this is with the latest built from head at the end of last week:
"warning: The option 'super_parameters' isn't supported by 'language'. (unsupported_option_with_legal_values at [console_dart] analysis_options.yaml:18)"
and
"error: This requires the 'super-parameters' language feature to be enabled. (experiment_not_enabled at [console_dart] bin/bar.dart:5)"
My analysis options file includes:
analyzer:
  language:
    super-parameters: true

CC @alexander-doroshko

Experiments aren't enabled under the language key, but under the enable-experiment key.
I verified that I can reproduce it using a package in which the pubspec.yaml includes:
environment:
  sdk: '>=2.17.0-dev <3.0.0'

and the analysis_options.yaml contains:
analyzer:
  enable-experiment:
    - enhanced-enums
    - named-arguments-anywhere
    - super-parameters

It's possible that my IntelliJ / plugin is too old:
IntelliJ IDEA 2021.2.4 (Community Edition)
Build #IC-212.5712.43, built on December 21, 2021
Runtime version: 11.0.13+8-b1504.49 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 12.2.1
GC: ParNew, ConcurrentMarkSweep
Memory: 1981M
Cores: 8
Registry: dart.server.additional.arguments=--port=10010 --instrumentation-log-file=/Users/brianwilkerson/temp/serverLog/instrumentation.log, debugger.watches.in.variables=false, dart.server.vm.options=--observe=8181 --enable-vm-service --pause_isolates_on_unhandled_exceptions=true --disable-service-auth-codes, max.suggested.heap.size=4096
Non-Bundled Plugins: Dart (212.5632)
Kotlin: 212-1.5.10-release-IJ5712.43