fix for not including tleap summary message as an error

@ajsilveira : Apologies that this PR was never reviewed! Next time, could you file an issue reporting the problem and then tag the issue in a PR so we know what the problem was and what the solution ended up being?
I've rolled this into #274


xone driver

The ability to upgrade xone driver or upgrade to the latest, with the latest xone driver my Xbox Gamesir Controller Audio port works, is there a way to upgrade or install the xone driver that uses dkms

idk if you want to test this out also, i change the file system to ext4 and i no longer get the steam hanging or very long reboots or startups, i notice btrfs gave me problems with apex sometimes, but ext4 fixed it so far ill test some more.

is there a way to install xone driver or can we get the latest xone driver as an option?

i saw akmods can instal xonedo
[xonedo](https://github.com/BoukeHaarsma23/xonedo/) - xbox one controller USB wired/RF driver modified to work along-side xpad (akmod from [ublue-os/akmods copr](https://copr.fedorainfracloud.org/coprs/ublue-os/akmods/))
how do i run this, its kinda confusing

xone is provided by ublue-os/akmods which just builds https://github.com/BoukeHaarsma23/xonedo/
so it will be reliant on when that updates since we rely on xpad working alongside xone.
Considering the last commit was last week and this issue is from April i would guess your controllers audio port should work now?

Ok I'll try when I reinstall

sry this reply took very long, the audio still doesn't work, and my original or gamsire controller doesn't light up, so I know the come driver is not being used

xone is provided by ublue-os/akmods which just builds https://github.com/BoukeHaarsma23/xonedo/
so it will be reliant on when that updates since we rely on xpad working alongside xone.
Considering the last commit was last week and this issue is from April i would guess your controllers audio port should work now?

I decided to install another is to test out the xonedo drivers and my audio from controller is working, so I dont think you are using the latest version of xonedo.

Ok I'll go check now

rpm -q xone-kmod-common
xone-kmod-common-0.0.git.115.fdbb71f1-1.fc40.noarch
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:89f8cd6c041242f31da8362ad97637fc68fa88515b83aef69e70c4f3d0854de7
Version: 40.20240624.0 (2024-06-24T17:13:00Z)
LayeredPackages: goverlay
LocalPackages: lact-0.5.4-0.x86_64
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:3c8f282ad7eb9c1feb1aecb37a17e455131171dc30cd69d704a93d783cfee6aa
Version: 40.20240624.0 (2024-06-24T16:39:32Z)
LayeredPackages: goverlay
LocalPackages: lact-0.5.4-0.x86_64

yeah that is the newest xonedo, last build was 29 days ago and last commit was 39 days ago

Maybe it's not active

Maybe it's not active

connect the controller to bluetooth and lsmod | grep xone

Gamsir controller don't have bluetooth it's cable and cable doesn't have audio support

Maybe it's not active

connect the controller to bluetooth and lsmod | grep xone

https://www.amazon.com/GameSir-Controller-Xbox-Windows-Joysticks-X/dp/B0C7GW9F88/ref=sr_1_3?crid=1MJXRSDJFKT5M&dib=eyJ2IjoiMSJ9.9kvKD-L2H7SyGR1cb51jEkmMH-suXj8oRZYQ6ZSRpxWwQgvUVyzbX87cBR1LQfDjNzlna8e_o8hbWDbPw8BcCOSOlV2IK_czS2VSxBSA8PkamOkhMRHnTZuzUN8AomYRge4mB7Dqnvr9VYC65vnEx3WknApFLJpKkovmXBiffmnocGjre6EFO-mhBDpPg_v_yBy0S1JH3GSBW7b0sBvNp1MNtYoS5pKLXOo_pO2WxVQ.BdOVNBmJeFOzkBO-q6SUPIwdMLM5ys8WaAzsEhS-cSQ&dib_tag=se&keywords=gamesir+g7+se+xbox+controller&qid=1719445124&sprefix=gamesir+se%2Caps%2C182&sr=8-3

This is expected behavior, our xone driver has the USB support removed from it. This allows it to coexist with xpad. If we didn't do that we would lose support for a ton of wired controllers that people commonly use.

Checked with the team, its caused by our xone having the wired component removed, because it would break a ton of controllers that only xpad supports.
It is not something we can support since it will be the choice of breaking almost everyones controllers or get working audio over wired xbox controllers (and it can not be made an ujust toggle as xone and xonedo cannot exist on the same system).

ok

@KyleGospo Is there a recommended work around for those of us with a wired xbox style controller?

The only work around if you must have this feature is to make a custom image. We can't ship this because it breaks far more controllers than it fixes.

That's what I thought. Thanks for the confirmation.


Add support for helm options like wait, skip-crds, timeout, etc

User Story
As a user I would like to control behaviour of helm operations(Install, Upgrade, Delete, etc) via helm options like wait, skip-crds, timeout, waitForJobs, etc.
Detailed Description
As a user, if I want to see HelmChartProxy/HRP status deployed only when all pods are in Ready/Running state, this is not possible unless we specify wait=true option in install config.
We need to be able to define helm options in HelmChartProxy(which can be later propagated to HRP) like -
apiVersion: addons.cluster.x-k8s.io/v1alpha1
kind: HelmChartProxy
metadata:
  name: mychart
spec:
  clusterSelector:
    matchLabels:
      myChart: enabled
  repoURL: repo-url
  chartName: mychart
  options:
     wait: true
     timeout: 10m
     install:
        noHooks: true
     upgrade:
        force: true

We can specify common options as a part of option and operation specific options in their corresponding fields like install, upgrade, etc. It'll also save us from hardcoding values in code.
Following are the options available with helm CLI, we can pick and choose the required ones and add support for those in HCP/HRP in phased manner.
Usage:
  helm install [NAME] [CHART] [flags]

Flags:
      --atomic                                     if set, the installation process deletes the installation on failure. The --wait flag will be set automatically if --atomic is used
      --ca-file string                             verify certificates of HTTPS-enabled servers using this CA bundle
      --cert-file string                           identify HTTPS client using this SSL certificate file
      --create-namespace                           create the release namespace if not present
      --dependency-update                          update dependencies if they are missing before installing the chart
      --description string                         add a custom description
      --devel                                      use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored
      --disable-openapi-validation                 if set, the installation process will not validate rendered templates against the Kubernetes OpenAPI Schema
      --dry-run                                    simulate an install
  -g, --generate-name                              generate the name (and omit the NAME parameter)
  -h, --help                                       help for install
      --insecure-skip-tls-verify                   skip tls certificate checks for the chart download
      --key-file string                            identify HTTPS client using this SSL key file
      --keyring string                             location of public keys used for verification (default "/Users/manoj.surudwad/.gnupg/pubring.gpg")
      --name-template string                       specify template used to name the release
      --no-hooks                                   prevent hooks from running during install
  -o, --output format                              prints the output in the specified format. Allowed values: table, json, yaml (default table)
      --pass-credentials                           pass credentials to all domains
      --password string                            chart repository password where to locate the requested chart
      --post-renderer postRendererString           the path to an executable to be used for post rendering. If it exists in $PATH, the binary will be used, otherwise it will try to look for the executable at the given path
      --post-renderer-args postRendererArgsSlice   an argument to the post-renderer (can specify multiple) (default [])
      --render-subchart-notes                      if set, render subchart notes along with the parent
      --replace                                    re-use the given name, only if that name is a deleted release which remains in the history. This is unsafe in production
      --repo string                                chart repository url where to locate the requested chart
      --set stringArray                            set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
      --set-file stringArray                       set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
      --set-json stringArray                       set JSON values on the command line (can specify multiple or separate values with commas: key1=jsonval1,key2=jsonval2)
      --set-string stringArray                     set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
      --skip-crds                                  if set, no CRDs will be installed. By default, CRDs are installed if not already present
      --timeout duration                           time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
      --username string                            chart repository username where to locate the requested chart
  -f, --values strings                             specify values in a YAML file or a URL (can specify multiple)
      --verify                                     verify the package before using it
      --version string                             specify a version constraint for the chart version to use. This constraint can be a specific tag (e.g. 1.1.1) or it may reference a valid range (e.g. ^2.0.0). If this is not specified, the latest version is used
      --wait                                       if set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a Deployment, StatefulSet, or ReplicaSet are in a ready state before marking the release as successful. It will wait for as long as --timeout
      --wait-for-jobs                              if set and --wait enabled, will wait until all Jobs have been completed before marking the release as successful. It will wait for as long as --timeout

Usage:
  helm upgrade [RELEASE] [CHART] [flags]

Flags:
      --atomic                                     if set, upgrade process rolls back changes made in case of failed upgrade. The --wait flag will be set automatically if --atomic is used
      --ca-file string                             verify certificates of HTTPS-enabled servers using this CA bundle
      --cert-file string                           identify HTTPS client using this SSL certificate file
      --cleanup-on-fail                            allow deletion of new resources created in this upgrade when upgrade fails
      --create-namespace                           if --install is set, create the release namespace if not present
      --dependency-update                          update dependencies if they are missing before installing the chart
      --description string                         add a custom description
      --devel                                      use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored
      --disable-openapi-validation                 if set, the upgrade process will not validate rendered templates against the Kubernetes OpenAPI Schema
      --dry-run                                    simulate an upgrade
      --force                                      force resource updates through a replacement strategy
  -h, --help                                       help for upgrade
      --history-max int                            limit the maximum number of revisions saved per release. Use 0 for no limit (default 10)
      --insecure-skip-tls-verify                   skip tls certificate checks for the chart download
  -i, --install                                    if a release by this name doesn't already exist, run an install
      --key-file string                            identify HTTPS client using this SSL key file
      --keyring string                             location of public keys used for verification (default "/Users/manoj.surudwad/.gnupg/pubring.gpg")
      --no-hooks                                   disable pre/post upgrade hooks
  -o, --output format                              prints the output in the specified format. Allowed values: table, json, yaml (default table)
      --pass-credentials                           pass credentials to all domains
      --password string                            chart repository password where to locate the requested chart
      --post-renderer postRendererString           the path to an executable to be used for post rendering. If it exists in $PATH, the binary will be used, otherwise it will try to look for the executable at the given path
      --post-renderer-args postRendererArgsSlice   an argument to the post-renderer (can specify multiple) (default [])
      --render-subchart-notes                      if set, render subchart notes along with the parent
      --repo string                                chart repository url where to locate the requested chart
      --reset-values                               when upgrading, reset the values to the ones built into the chart
      --reuse-values                               when upgrading, reuse the last release's values and merge in any overrides from the command line via --set and -f. If '--reset-values' is specified, this is ignored
      --set stringArray                            set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
      --set-file stringArray                       set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
      --set-json stringArray                       set JSON values on the command line (can specify multiple or separate values with commas: key1=jsonval1,key2=jsonval2)
      --set-string stringArray                     set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
      --skip-crds                                  if set, no CRDs will be installed when an upgrade is performed with install flag enabled. By default, CRDs are installed if not already present, when an upgrade is performed with install flag enabled
      --timeout duration                           time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
      --username string                            chart repository username where to locate the requested chart
  -f, --values strings                             specify values in a YAML file or a URL (can specify multiple)
      --verify                                     verify the package before using it
      --version string                             specify a version constraint for the chart version to use. This constraint can be a specific tag (e.g. 1.1.1) or it may reference a valid range (e.g. ^2.0.0). If this is not specified, the latest version is used
      --wait                                       if set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a Deployment, StatefulSet, or ReplicaSet are in a ready state before marking the release as successful. It will wait for as long as --timeout
      --wait-for-jobs                              if set and --wait enabled, will wait until all Jobs have been completed before marking the release as successful. It will wait for as long as --timeout

/kind feature

/triage accepted

Sounds like a great addition! Would you like me to pick up this issue?

If it's okay with you, I can take this up. Do we have an agreement on CRD structure specified in description? If you've any suggestion, please do. I'm thinking of adding support for essential helm options only in phase-1, later we can keep adding support for other ones. Let me know.

I think that CRD structure makes sense. A couple things to consider:

Do we want to support options specifying a filename like --cert-file at the moment? I think we'd probably have to reference a secret or something in that case.
What type did you have in mind for spec.options? Do you intend to add a variable for every option since we know what all the possible fields are. Or we could make it a string like valuesTemplate that we parse at runtime.

Yes, we'll need a secret reference. At the moment, I'm skipping these auth related params for first phase. We can add these once 1st PR merges with operation specific params.
I'm thinking of struct type with variable for every helm option. If we make it a string like valuesTemplate then, we would be loosing on strict schema checks that we get with openAPI schema and we will need extra parsing & validation logic to verify all the fields.

Sounds good, I think we can leave off the options that require a file path as a parameter for now go with a struct type for each of the options.


cannot use huge server

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/wowchemy/wowchemy-hugo-themes/issues?q=is%3Aissue
[X] This issue is not a question, feature request, or anything other than a bug report directly related to Wowchemy. Please post those things on Discord: https://discord.gg/z8wNYzb

Description
$ hugo server
hugo: downloading modules …
go<EMAIL_ADDRESS>invalid version: git ls-remote -q origin in C:\Users\AKON_W~1\AppData\Local\Temp\hugo_cache\modules\filecache\modules\pkg\mod\cache\vcs\0c88995f39c54fe356dd74460b6359b56b0fb376c52289c9656c86270b2c006d: exit status 128:
fatal: unable to access 'https://github.com/wowchemy/wowchemy-hugo-themes/': Recv failure: Connection was reset
go<EMAIL_ADDRESS>invalid version: git ls-remote -q origin in C:\Users\AKON_W~1\AppData\Local\Temp\hugo_cache\modules\filecache\modules\pkg\mod\cache\vcs\0c88995f39c54fe356dd74460b6359b56b0fb376c52289c9656c86270b2c006d: exit status 128:
fatal: unable to access 'https://github.com/wowchemy/wowchemy-hugo-themes/': Recv failure: Connection was reset
go<EMAIL_ADDRESS>invalid version: git ls-remote -q origin in C:\Users\AKON_W~1\AppData\Local\Temp\hugo_cache\modules\filecache\modules\pkg\mod\cache\vcs\0c88995f39c54fe356dd74460b6359b56b0fb376c52289c9656c86270b2c006d: exit status 128:
fatal: unable to access 'https://github.com/wowchemy/wowchemy-hugo-themes/': Recv failure: Connection was reset
go<EMAIL_ADDRESS>invalid version: git ls-remote -q origin in C:\Users\AKON_W~1\AppData\Local\Temp\hugo_cache\modules\filecache\modules\pkg\mod\cache\vcs\0c88995f39c54fe356dd74460b6359b56b0fb376c52289c9656c86270b2c006d: exit status 128:
fatal: unable to access 'https://github.com/wowchemy/wowchemy-hugo-themes/': Recv failure: Connection was reset
hugo: collected modules in 40847 ms
Error: failed to download modules: failed to execute 'go [mod download]': failed to execute binary "go" with args [mod download]: go<EMAIL_ADDRESS>invalid version: git ls-remote -q origin in C:\Users\AKON_W~1\AppData\Local\Temp\hugo_cache\modules\filecache\modules\pkg\mod\cache\vcs\0c88995f39c54fe356dd74460b6359b56b0fb376c52289c9656c86270b2c006d: exit status 128:
fatal: unable to access 'https://github.com/wowchemy/wowchemy-hugo-themes/': Recv failure: Connection was reset
go<EMAIL_ADDRESS>invalid version: git ls-remote -q origin in C:\Users\AKON_W~1\AppData\Local\Temp\hugo_cache\modules\filecache\modules\pkg\mod\cache\vcs\0c88995f39c54fe356dd74460b6359b56b0fb376c52289c9656c86270b2c006d: exit status 128:
fatal: unable to access 'https://github.com/wowchemy/wowchemy-hugo-themes/': Recv failure: Connection was reset
go<EMAIL_ADDRESS>invalid version: git ls-remote -q origin in C:\Users\AKON_W~1\AppData\Local\Temp\hugo_cache\modules\filecache\modules\pkg\mod\cache\vcs\0c88995f39c54fe356dd74460b6359b56b0fb376c52289c9656c86270b2c006d: exit status 128:
fatal: unable to access 'https://github.com/wowchemy/wowchemy-hugo-themes/': Recv failure: Connection was reset
go<EMAIL_ADDRESS>invalid version: git ls-remote -q origin in C:\Users\AKON_W~1\AppData\Local\Temp\hugo_cache\modules\filecache\modules\pkg\mod\cache\vcs\0c88995f39c54fe356dd74460b6359b56b0fb376c52289c9656c86270b2c006d: exit status 128:
fatal: unable to access 'https://github.com/wowchemy/wowchemy-hugo-themes/': Recv failure: Connection was reset
*errors.errorString
Reproduction Link
https://wowchemy.com/hugo-themes/
Steps to Reproduce

...
Expected Result
use hugo server
Actual Result
cannot use hugo server and hugo
What Hugo Module versions does your site use?
module github.com/wowchemy/starter-hugo-academic
go 1.15
require (
github.com/wowchemy/wowchemy-hugo-themes/modules/wowchemy-plugin-netlify v1.0.0 // indirect
github.com/wowchemy/wowchemy-hugo-themes/modules/wowchemy-plugin-netlify-cms v1.0.0 // indirect
github.com/wowchemy/wowchemy-hugo-themes/modules/wowchemy-plugin-reveal v1.0.0 // indirect
github.com/wowchemy/wowchemy-hugo-themes/modules/wowchemy/v5 v5.7.1-0.20221127215619-58b270a3e103
)
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
Which Wowchemy template are you using?
academic resume
What version of Hugo are you using?
hugo v0.111.3-5d4eb5154e1fed125ca8e9b5a0315c4180dab192+extended windows/amd64 BuildDate=2023-03-12T11:40:50Z VendorInfo=gohugoio

在中国
If you are in China without VPN, Hugo can fail to download modules from GitHub.
To resolve this, you can try adding a proxy to the module section of your config/_defaults/config.yaml:
module:
proxy: https://goproxy.cn


Use Protobuf for DRT

Changes DRT to use Protobuf, rather than the undocumented JSON format, for communicating isAuthorized and validate requests from Rust to Lean.
Adds a new DRT target testing that various structures properly roundtrip from AST to Protobuf and back.
Updates the Lean Cli executable to expect Protobuf-encoded inputs for isAuthorized and validate (still expects JSON for other targets, like validateEntities and validateRequest).
Removes tests for the Lean Cli executable, which used hardcoded JSON inputs.  Tests for protobuf functionality, with protobuf inputs, were added in #485 (although they don't test the Cli specifically).

Integration-tests CI failure is due (at least in part) to needing cedar-policy/cedar#1365


fix typo

i went ahead and rebased this on top of main. please check i carried everything over.
from my side looks good.


[impeller] impellerc crashes when compiling uint uniform

repro:
#version 310 es

layout(location = 0) uniform uint foo;
layout(location = 0) out vec4 fragColor;

void main() {}

however changing uint -> int works
cc @zanderso

Actually this happens if a uint appears anywhere in a program, including uint constants (suffixed with u)

Looks like int and uint aren't really supported in SKSL. Though that shouldn't limit anyone who wants to use them in impeller. Will leave this open since hard crashing is still a bug.

@ds84182 Could you share any logs here please?

@zanderso I don't get any log output from impellerc, most likely because I'm on Windows.

@jonahwilliams was this among the crashes you fixed?

No, this crash is different. on macOS:
[ERROR:flutter/fml/backtrace.cc(108)] Caught signal SIGABRT during program
execution.
Frame 0: 0x104158f0c
std::_LIBCPP_ABI_NAMESPACE::__shared_ptr_emplace<>::~__shared_ptr_emplace()
Frame 1: 0x104393dec spirv_cross::join<>()
Frame 2: 0x1043914a8 spirv_cross::CompilerGLSL::variable_decl()
Frame 3: 0x1043925f4 spirv_cross::CompilerGLSL::variable_decl()
Frame 4: 0x1041600b0 impeller::compiler::CompilerSkSL::emit_uniform()
Frame 5: 0x104160bdc impeller::compiler::CompilerSkSL::emit_uniform_resources()
Frame 6: 0x10415f4cc impeller::compiler::CompilerSkSL::emit_resources()
Frame 7: 0x10415edb0 impeller::compiler::CompilerSkSL::compile()
Frame 8: 0x10411c13c impeller::compiler::Compiler::Compiler()
Frame 9: 0x104118fd0 impeller::compiler::Main()
Frame 10: 0x10411a37c main
Frame 11: 0x10550908c start

Might just be the SPIRV_CROSS_THROW from the glsl compiler and instead we need to exit earlier. Needs some investigation


Fix for mobile screen

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

Use Case
It should be fixed to improve experienece on all devices
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor
[X] I want to work on this issue

Hi https://github.singodiyashubham87
I’d like to take up this task: Fix for mobile screen #505
I’m confident I can complete it and contribute to the project.
Could you please assign it to me? I’ll make sure to deliver by the deadline and follow the project’s guidelines closely. If there are any specific requirements or preferences, feel free to let me know.
Looking forward to your approval!
Thanks,
@naitikhoriya1


Add event capturing into PostHog

Summary
Added feature to allow PostHog to capture access events for user behavior analysis.
This feature can be enabled using environment variables.
Changes

Added PostHog initializing component to app/providers.tsx .
Added event capturing component to app/posthog-page-view.tsx .
Inserted components implemented above into app/layout.tsx .

Testing
Normal case - Enable event capturing

Set environment variables

NEXT_PUBLIC_ENABLE_POSTHOG : true (enables event capturing)
NEXT_PUBLIC_POSTHOG_HOST : PostHog test project url
NEXT_PUBLIC_POSTHOG_KEY : PostHog test project key

Start up development environment ( bun dev ) and access some pages.
Result: Verified that the event was recorded in PostHog.

Normal case - Disable event capturing

Set environment variables

NEXT_PUBLIC_ENABLE_POSTHOG : false or remove definition (disables event capturing)
NEXT_PUBLIC_POSTHOG_HOST : PostHog test project url
NEXT_PUBLIC_POSTHOG_KEY : PostHog test project key

Start up development environment ( bun dev ) and access some pages.
Result: Verified that the event was not recorded in PostHog.

Error case

Set environment variables

NEXT_PUBLIC_ENABLE_POSTHOG : true (enables event capturing)
NEXT_PUBLIC_POSTHOG_HOST : Wrong PostHog test project url or remove definition
NEXT_PUBLIC_POSTHOG_KEY : Wrong PostHog test project key or remove definition

Start up development environment ( bun dev ) and access some pages.
Result: Although an error is displayed on the browser console (not in app), confirmed that the application runs normally.

Other Information

I referred to PostHog's Next.js implementation guide.
If an error occurs related to event capture, the error is reported to Sentry without affecting the operation of the application.

thank you!


Leak in BGR->RGB conversion

In the issue #3872, @riataman reported:

The issue with the memory leak in the raspberry pi is easily demonstrated by running /examples/camera/main.py in the raspberry pi running the latest raspbian jessie.
The memory leaks very fast and in my system with a Logitech C920 the memory would be completely gonne in less than a minute.
I found that if I change here: https://github.com/kivy/kivy/blob/master/kivy/core/camera/camera_opencv.py#L137 The format from bgr to rgb then the memory leak is fixed. But the colors are all wrong.

I guess we have a leak in the bgr->rgb conversion.

I found this: https://groups.google.com/forum/#!msg/cython-users/CwtU_jYADgM/660O2JJuO54J claiming that cython may had internal memory leaks.
I also found that there was some manual deref going on at some point: https://github.com/kivy/kivy/commit/3b0931415869ba94fa2cf1e849b448979c1d1f02 but was later removed: https://github.com/kivy/kivy/commit/7f5158545b6b141d65017e1550f83bafb0d81759 (putting the same deref back again crashes for me).
I had kivy build with cython 0.23. I'm trying to build with 0.25.2 to see if that changes anything.

The leak is still present after building with cython 0.25.2

Maybe related to/fixed by #5664, though it's not clear why the BGR conversion is involved. Please re-test if possible


Not able to add existing accounts when deploying Conformity stack

Environments:
Existing AWS Control Tower enabled multi-accounts environment, Subscribed to the Conformity through AWS Market place, Sign in to our AWS Control Tower management account as an administrator, launched the AWS CloudFormation template. The stack was created successfully.
Issue
Existing accounts are not shown in our Conformity service. Looked through CloudWatch logs, and discovered errors in adding account.
Error log 1: In the main management account:
[INFO]	2021-07-10T11:58:05.992Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Event received by handler: {'InvokeAction': 'configure_account', 'account_id': '123456789515'}
[INFO]	2021-07-10T11:58:05.992Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	function name: trend-micro-cloud-one-confor-LifecycleEventHandler-4j63YSPDjNpx invoked arn: arn:aws:lambda:ap-southeast-2:123456789515:function:trend-micro-cloud-one-confor-LifecycleEventHandler-4j63YSPDjNpx
[INFO]	2021-07-10T11:58:06.024Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Found credentials in environment variables.
[INFO]	2021-07-10T11:58:06.977Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Create Connector Object
[INFO]	2021-07-10T11:58:06.977Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Create role in target account
[INFO]	2021-07-10T11:58:06.980Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Retrieving session for operation
[INFO]	2021-07-10T11:58:07.809Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	currently executing in<PHONE_NUMBER>15; called account is<PHONE_NUMBER>15
[INFO]	2021-07-10T11:58:08.014Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Target account is Control Tower Management; returning local credentials session
[INFO]	2021-07-10T11:58:08.038Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Found credentials in environment variables.
[INFO]	2021-07-10T11:58:08.909Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Creating role CloudOneConformityConnectorRole and policy CloudOneConformityConnectorPolicy in account<PHONE_NUMBER>15
[INFO]	2021-07-10T11:58:08.910Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Creating role...
[INFO]	2021-07-10T11:58:09.167Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	http status for call to /organisation/external-id was: 403 with response: b'{     "Message": "User is not authorized to access this resource with an explicit deny" }'
[ERROR]	2021-07-10T11:58:09.168Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Failed to create role: 'data'
[ERROR]	2021-07-10T11:58:09.172Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Failed to configure account<PHONE_NUMBER>15 with exception: 'data'
[INFO]	2021-07-10T11:58:29.194Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Add account to Cloud One Conformity
[INFO]	2021-07-10T11:58:29.401Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	http status for call to /accounts was: 403 with response: b'{     "Message": "User is not authorized to access this resource with an explicit deny" }'
[INFO]	2021-07-10T11:58:29.404Z	38c1c6ea-9ac2-455d-ab4c-2ea6b7cfc48b	Done
Error log 2: In the non-management account:
[INFO]	2021-07-10T11:58:05.854Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Event received by handler: {'InvokeAction': 'configure_account', 'account_id': '123456789137'}
[INFO]	2021-07-10T11:58:05.854Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	function name: trend-micro-cloud-one-confor-LifecycleEventHandler-4j63YSPDjNpx invoked arn: arn:aws:lambda:ap-southeast-2:123456789515:function:trend-micro-cloud-one-confor-LifecycleEventHandler-4j63YSPDjNpx
[INFO]	2021-07-10T11:58:05.889Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Found credentials in environment variables.
[INFO]	2021-07-10T11:58:06.885Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Create Connector Object
[INFO]	2021-07-10T11:58:06.885Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Create role in target account
[INFO]	2021-07-10T11:58:06.888Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Retrieving session for operation
[INFO]	2021-07-10T11:58:07.700Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	currently executing in<PHONE_NUMBER>15; called account is<PHONE_NUMBER>37
[INFO]	2021-07-10T11:58:08.345Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Assumed session for<PHONE_NUMBER>37 - AWSControlTowerExecution.
[INFO]	2021-07-10T11:58:09.238Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Creating role CloudOneConformityConnectorRole and policy CloudOneConformityConnectorPolicy in account<PHONE_NUMBER>37
[INFO]	2021-07-10T11:58:09.238Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Creating role...
[INFO]	2021-07-10T11:58:09.440Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	http status for call to /organisation/external-id was: 403 with response: b'{     "Message": "User is not authorized to access this resource with an explicit deny" }'
[ERROR]	2021-07-10T11:58:09.440Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Failed to create role: 'data'
[ERROR]	2021-07-10T11:58:09.443Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Failed to configure account<PHONE_NUMBER>37 with exception: 'data'
[INFO]	2021-07-10T11:58:29.464Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Add account to Cloud One Conformity
[INFO]	2021-07-10T11:58:29.601Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	http status for call to /accounts was: 403 with response: b'{     "Message": "User is not authorized to access this resource with an explicit deny" }'
[INFO]	2021-07-10T11:58:29.603Z	a069d539-4dd5-4ec2-9b90-ac7ead5e4c2e	Done
Same error when Creating role CloudOneConformityConnectorRole and policy CloudOneConformityConnectorPolicy in account.
Doubled checked all accounts that the AWSControlTowerExecution roles do have full AWS admin permissions.
Note: Part of the account number has been changed for privacy reason.

Since the message indicated explicit deny. It error looks like an SCP(Service Control Policy) in your AWS Organization is denying iam:CreateRole. Please check your SCPs.

Thanks for your reply, @kkvinjam
I double checked SCPs and don't think this is caused by iam:CreateRole related policies. My reasons are:

The error message is about "http status for call to /organisation/external-id", with 403 forbidden, although this is part of creating role CloudOneConformityConnectorRole. But it was not creating a role.
The environment is a newly established AWS Control Tower setup, with standard guardrails. Nothing custom has been deployed. This solution is designed for Control Tower Integration, isn't it?
Tested with root account, with the same error.
The only iam:CreateRole related policy part is:
    {     "Condition": {       "ArnNotLike": {         "aws:PrincipalArn": [           "arn:aws:iam::*:role/AWSControlTowerExecution",           "arn:aws:iam::*:role/stacksets-exec-*"         ]       }     },     "Action": [       "iam:AttachRolePolicy",       "iam:CreateRole",       "iam:DeleteRole",       "iam:DeleteRolePermissionsBoundary",       "iam:DeleteRolePolicy",       "iam:DetachRolePolicy",       "iam:PutRolePermissionsBoundary",       "iam:PutRolePolicy",       "iam:UpdateAssumeRolePolicy",       "iam:UpdateRole",       "iam:UpdateRoleDescription"     ],     "Resource": [       "arn:aws:iam::*:role/aws-controltower-*",       "arn:aws:iam::*:role/*AWSControlTower*",       "arn:aws:iam::*:role/stacksets-exec-*"     ],     "Effect": "Deny",     "Sid": "GRIAMROLEPOLICY"   }

To be created role's name is CloudOneConformityConnectorRole, that doesn't match to the resource in the policy.
I think I have missed something. But triple checked deployment guide, I cannot locate anything wrong in my steps.
Hope someone knows what it is happening. Thanks!

Hey @xu-lei-richard just stumbled across your post, when you are getting denies on retrieving the org external ID it typically is because of either of the following: 1. Invalid API Key, or 2. your conformity region isn't set correctly in the stack. All Conformity accounts accessed via Cloud One are in the us-west-2 region, where standalone accounts can be either in ap-southeast-2 (Sydney), eu-west-1 (Ireland), us-west-2 as per cloud one.

Thanks @TomRyan-321 I think it could be the issue. Our account uses ap-southeast-2. I will test again.


Algorithms: Princeton vs. Stanford Courses

Firstly: Thanks for all the work you guys put into this project. It helps me a lot and is greatly appreciated!
I was about to start the Algorithms course on Langunita and saw that there is a course that there is a similar course (at least in terms of name) by Princeton on Coursea. I understand that the Princeton one was replaced by the Stanford one only because the second part of the former was offline for a long time. This is no longer the case (I just enrolled in Princeton's Algorithm's Part II to test it out: https://www.coursera.org/learn/algorithms-part2).
Given that both are available again, are there any reasons to chose one over the other purely from a content and didactical point of view? I went throught the topics covered by each, but frankly most of that stuff doesn't mean anything to me, so any insight from someone further ahead or someone who knows both of them would be great.

Did you find the answer? I've the same question

Apologies for the short response: The Princeton course emphasizes writing your own implementation of the algorithms. The Stanford course emphasizes analyzing algorithms to understand their complexity. Both are well regarded.

Apologies for the short response: The Princeton course emphasizes writing your own implementation of the algorithms. The Stanford course emphasizes analyzing algorithms to understand their complexity. Both are well regarded.

Don't you need both? and to what extent that Stanford helps in analyzing the complexity better than Princeton?
I didn't take Stanford but I finished Princeton I & II.


It says missing sd dirctry

It says missing sd directory
How do i fix it

Try to restart the app and ensure you gave it file system permissions.


Fix: unifying .spec spelling in concepts

same problem like #8542

/assign @Bradamant3

/lgtm
/approve


Updated CONTRIBUTING.md

Fixed broken GitHub link to Firebase Quickstarts for Android

I’ve signed it!
Regards,
Vathsav

On 03-Jun-2016, at 12:05 PM, googlebot<EMAIL_ADDRESS>wrote:
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.
If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data https://cla.developers.google.com/clas and verify that your email is set on your git commits https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the company's name.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/firebase/quickstart-android/pull/35#issuecomment-223502037, or mute the thread https://github.com/notifications/unsubscribe/AGkiXn_U4HHHsE7usongmDAMqmv36HxYks5qH8spgaJpZM4ItPj4.

@vathsav nice catch, thanks!

@samtstern Anytime! 👍


review Imgur TOS

just a quick look to see if there's any issues with incorporating CC licenses: https://imgur.com/tos
maybe next week sometime? i'm talking to them Mon but can surface TOS later

Just read them and added a bit to your doc. Ping me if you have questions!

Please re-review the NC clause (and anything else) and add specific rec to engagement doc: https://docs.google.com/a/creativecommons.org/document/d/1nX5sXeYJ49c_kHuoUvtsgTy4LNsISCPUOwPjplaQeqc/edit.

Hi Sarah - can you do this early next week? I am going to be checking in with Tim then...

yes!


Use double literals, don't cast integer or float literals to double.

Describe your PR, what does it fix/add?
It fixes me getting distracted all the time i see this.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
And if you don't know, now you know!
(btw. should be included in the splash "music reference / quote section")
Is it ready for merging, or does it need work?
This is ready

thanks


Feature/jtai module option cachekey

Add option to module manager for giving the config cache a custom key to save with
Unit test assertion for new config key
Fix a few return docblock comments

I need a CLA from jtai before I can merge this -- Evan, can you reach out to him?

Reviewed, merged, and pushed to master.


Link to French homepage is wrong

It points to https://theblog.helix-demo.xyz/fr/  instead of https://theblog.helix-demo.xyz/ms/fr/

Fixed with #122

Fixed with #122


some 'unescaped left brace in regex' fixes to suppress perl-5.22 warnings

This is already done in the biber DEV branch.

sorry, i only checked master.  but: what about  lib/Biber/Input/file/bibtex.pm (ln. 762) ??

Yes, that's also done in DEV.


remove API delays from builder

The arbitrary API delays introduced by a84b3f243fcc4b4b46bfebe8aa2edcdd80a1fe90 can be removed. The Discover API gateway errors have been fixed.

[ ] revert API request worker count to 8
[ ] remove the fetch_json() delay args (and param, if we want to be optimistic)

cc @nayib-jose-gloria


[SPARK-17721][MLlib] Backport PR

Backport PR of changes relevant to mllib only, but otherwise identical to #15296
@jkbradley

Can one of the admins verify this patch?

Jenkins add to whitelist

Test build #66168 has started for PR 15311 at commit dcdf578.

Test build #66168 has finished for PR 15311 at commit dcdf578.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66168/
Test PASSed.

LGTM, merging with branch-1.6 and branch-1.5
Thanks @bwahlgreen !

Actually, before I merge, could you please update the PR title to match the other PR's title, but with a [backport] tag?

+1 on updating the title. The current title doesn't really explain what the pr is.

there 😄

Perfect, thanks!  Merging now

Since this is a backport, you'll need to close this manually. Thanks!


z-up vs y-up

Three uses a default of y-up as does this library currently. This requires a rotation where +z = south, -z = north. This is not intuitive. However rotating all objects isn't either.
From the current readme:

Going to close for now, please reopen with further discussion if necessary.


Summarising rule

Thank you so much for creating this fantastic tool! This saves so much time!
A small feature request: I'd like to create a new rule (or modify an existing) to summarise all the compilation steps at the end. In principal arara already does this by printing
(PDFLaTeX) PDFLaTeX engine
(Biber) The Biber reference management software
(PDFLaTeX) PDFLaTeX engine
(PDFLaTeX) PDFLaTeX engine

but when using arara --verbose to see the log file, these messages are hidden in between. What I would like to do is print them at the end of arara when the total elapsed time gets displayed. Is this somehow possible?
In case it makes a difference, I am using arara 4.0 (could not wait to play with all these nice toys :)

Hello! :wink:
Thanks for the kind words!
To be honest, I am quite reticent to add new features now, specially when version 4.0 is not even officially released. I need to take a look at my code and see if there's a way to include this feature without significant changes in the underlying engine. I will report back when I have a more reliable coverage. :wink:
There's a way to achieve something along those lines without dissecting the bowels of this parrot (as to amuse John Cleese, it's not dead). Version 4.0 has something called session, in which you can use it to exchange data from rule to rule. The default behaviour is to provide hermetic rules, that is, rules that are sealed, encapsulated (what happens in Vegas, stay in Vegas). However, there's a rule method named getSession() in which we can manipulate persistent data, in the sense of keeping awareness after the rule pines for the fjords.
Here's a modified pdftex.yaml rule:
- name: PDFTeX engine
  command: >
    @{
        if (!getSession().exists('tasks')) {
            getSession().insert('tasks',[]);
        }
        getSession().obtain('tasks').add('I just ran PDFTeX on ' + file);
        return getCommand('pdftex', interaction, draft, shell, synctex, options, file)
    }

The first conditional is required to initialize the tasks entry (think of a session as a map, in which you put and retrieve things based on an key). The line after the conditional adds the reference to what's being done at the moment.
Now, let us write a summarize.yaml rule:
!config
identifier: summarize
name: Summarize
authors:
- Paulo Cereda
commands:
- name: Summarizes the execution
  command: >
    @{
        if (!getSession().exists('tasks')) {
            getSession().insert('tasks',[]);
        }
        tasks = getSession().obtain('tasks');
        text = 'These are the tasks arara ran in a couple of seconds ago:
';
        foreach (task : tasks) {
            text = text + '- ' + task + '
';
        }
        showMessage(2, 'Summary', text);
        return true;
     }
arguments: []

The idea here is to get the current execution and display in a message box (another feature of version 4.0). It's possible to use a common Java output method to print the message to the terminal, but it will mess the layout greatly (or maybe it's just my OCD being triggered). A sample test file:
% arara: pdftex
% arara: pdftex
% arara: summarize
Hello world!
\bye

And the execution:

Another approach is to use one of the internal libraries used by arara and write the data to a separate .log file. Let us check a modified summarize.yaml:
!config
# Arara, the cool TeX automation tool
# Copyright (c) 2012, Paulo Roberto Massa Cereda
# All rights reserved.
#
# This rule is part of arara.
identifier: summarize
name: Summarize
authors:
- Paulo Cereda
commands:
- name: Summarizes the execution
  command: >
    @{
        if (!getSession().exists('tasks')) {
            getSession().insert('tasks',[]);
        }
        tasks = getSession().obtain('tasks');
        org.apache.commons.io.FileUtils.writeLines(new java.io.File('execution.log'), tasks);
        return true;
     }
arguments: []

When running arara:
[paulo@cambridge target] $ java -jar arara.jar test.tex
  __ _ _ __ __ _ _ __ __ _
 / _` | '__/ _` | '__/ _` |
| (_| | | | (_| | | | (_| |
 \__,_|_|  \__,_|_|  \__,_|

Processing 'test.tex' (size: 70 bytes, last modified: 08/30/2016
17:55:27), please wait.

(PDFTeX) PDFTeX engine .................................. SUCCESS
(PDFTeX) PDFTeX engine .................................. SUCCESS
(Summarize) Summarizes the execution .................... SUCCESS

Total: 0.47 seconds
[paulo@cambridge target] $ cat execution.log
I just ran PDFTeX on test.tex
I just ran PDFTeX on test.tex

It's not exactly what you want, but we are half way there. :wink:
Cheerio!

 This is does exactly what I want!
For me this is the final nail in latexmk's coffin and I am switching completely to arara! I don't know how you do it, but arara is significantly faster performing the same operations.
An afterthought: Not important, but is there an easy way to catch the result of the rules, e.g. .................................. SUCCESS?

That you can probably do what you want via some shell piping at that point 😉 grep comes to mind.
By the way, that is an awesome picture 😄

@vermiculus Thanks for the idea, it works! arara --log provides all the necessary information for grepping.


Make huge example

Hi,
I haven't found any large example in github yet. Only this project use serenity-js

https://github.com/jan-molak/serenity-js-example
https://github.com/jan-molak/serenity-js-fast-track-demo
https://github.com/serenity-js/tutorial-journey-planner
https://github.com/serenity-js/tutorial-cross-app-testing
https://github.com/serenity-js/tutorial-from-scripts-to-serenity

I want to see, how handle serenity (and screenplay pattern) this subject in a large example.

authentication/authorization
basic pages (user settings, blog etc..)
advanced pages (search, wizzard)
multiple environments (rest resources)
component test like datepicker, dropdown, datable, forms etc..

Hey @tamascsaba!
The basic building blocks are demonstrated here, and you should be able to use them to assemble more complex tasks.
I agree that some more advanced examples would be useful though. I'll be adding them to the serenity-js.org website, and if you come up with your own examples I'd be more than happy to include them in the community section.

I've just created two seed projects to help you get started:

Serenity/JS Cucumber seed
Mocha seed

More examples to follow!

:+1: :)

@jan-molak  , I tried that Serenity/JS Cucumber seed project. I am new to Protractor. Please want to know why it's does not open the browser when it's running? thanks


bug: error recovery within a bit_string_literal

Did you check existing issues?

[X] I have read all the tree-sitter docs if it relates to using the parser
[X] I have searched the existing issues of tree-sitter-vhdl

Tree-Sitter CLI Version, if relevant (output of tree-sitter --version)
No response
Describe the bug
It seems the error recovery within a bit_string_literal is not working as I would expect, see screenshot. When removing one of the quotation marks, the error recovery goes haywire.

Steps To Reproduce/Bad Parse Tree
Install the treesitter as usual, open a vhdl file with e.g. a std_logic_vector type and initialise it with a bit_string_literal, e.g. 32x"babecafe". Remove a quotation mark.
Expected Behavior/Parse Tree
Recover successfully after an error within a bit_string_literal.
Repro
No response

On it...

By the way -- I'm also fixing a case where an identifier is called, for example "integ".  It start with "in", and is part of "integer", and the scanner gets confused and returns "keyword IN"

I think it's better now...?

Yes, working as expected now. Thanks! Closing.

@SethGower
The commit above points to a branch that does not exist...  You might want to point it towards develop instead.  Just remember to copy over the new highlights.scm as well.

@jpt13653903 thanks, i caught that and fixed it. That commit was supposed to reference the discussion, not this issue (which didn't exist yet). Not sure what happened

@jpt13653903 thanks, i caught that and fixed it. That commit was supposed to reference the discussion, not this issue (which didn't exist yet). Not sure what happened

Issue 4 on the old fork is the discussion you're after.  The numbers got jumbled when I detached the fork by creating a new repo.  You're looking for issue #2 in this repo.  My apologies for the confusion -- pity one cannot easily detach a fork without first deleting (or moving, in my case) the old fork and then creating a new repo.
And then GitHub got the times mixed up when it saw: "O, there's a commit that references this issue, better link it", but the 2-week old commit got linked 5 days ago, causing even more confusion 🤦


RemoteWriteBehind false alarm when all series dropped via relabel config

What did you do?
We tried recently to play around with dropping some metrics that appear to be gathered independently of the scrape phase, such as up, and scrape_duration_seconds. As in, these metrics will get remote-written even if a relabel config in the scrape phase is set up to drop them.
So for this scenario, we configured Prometheus with appropriate write_relabel_configs in place to drop those metrics, and also triggered a scenario where 0 other samples would be gathered from scrape_config sources, due to e.g. auth revocation on the target side.
What did you expect to see?
It seems like it would be nice to be able to have a timestamp which appropriately accounts for series which make it past relabeling, since if all series end up getting dropped due to write relabeling, then naturally remote writing is not falling behind, there's just nothing new to process.
What did you see instead? Under which circumstances?
We found that if 0 other samples are gathered for a processing cycle, we see that prometheus_remote_storage_highest_timestamp_in_seconds from here continues to increase, while prometheus_remote_storage_queue_highest_sent_timestamp_seconds from here remains the same.
This results in our RemoteWriteBehind alert firing, based in part on the difference between these two series over time, which comes from this mixin alert
Digging around the areas of code above, it seems like this is almost expected. as far as I can tell, prometheus_remote_storage_highest_timestamp_in_seconds is tracking the highest timestamp that enters the remote write system at all, before anything such as relabel configs are evaluated. thus it seems that the internal info metrics like up continue to come into the remote write system and update prometheus_remote_storage_highest_timestamp_in_seconds, before relabeling drops them.
System information
No response
Prometheus version
No response
Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

I agree with your analysis.
I don't think it will be trivial to fix.  The logic to drop samples is here, intentionally well ahead of the logic to send over remote-write.
So, if your config is dropping some samples and letting others through, and remote-write is stuck, the timestamps on dropped samples can be expected to be be ahead of sent ones.  This will defeat the alert.
However, once all queues fill up the relabeling part will also stall, so the alert would fire.  Under reasonable scenarios this will not take too long.
Another approach would be to detect the case where all series have been dropped, and blank prometheus_remote_storage_highest_timestamp_in_seconds so it does not trigger the alert.


unsubscribe() successful, but the callback unsubscribed_info.was_error is true

I moved up to release 1.5, although had to change all the callbacks. That came to pass, and all seems well except this:
When calling unsubscribe(), the lockable logger I passed to wampcc was able to log:
LOG 20171110-19:22:53.081567 14684  INFO unsubscribed, subscription_id 28, request_id 3 ...
But upon examining the callback arg struct unsubscribed_info, I found its was_error member was set to true.
I'm sure the previous wampcc version that I had used for a long time had its was_error member set to the right value, though the struct had a different name.

Yep ... I'm able to reproduce. Seems like bug. Will fix soon.

fixed on master branch, commit fcb79e5fcf4eae375c08733a395697df124d859f

Another minor thing - my compiler (GCC 5.4) made a little noise about this:
... include/wampcc/wamp_session.h:94:28: warning: missing initializer for member 'wampcc::auth_provider::user_secret' [-Wmissing-field-initializers]            nullptr, nullptr };
It can be made to go away by one's adding one more , nullptr before }; at the end.

Fix confirmed

added your suggestion to resolve compiler warning.


Refactor integration tests.

Started with #416, but ended up changing all integration tests.
Thats a questionable decision on my behalf but hear me out - my idea is not to change one style to another but rather clarify intention for tests. Previously we were passing testing.T to a lot of functions, ones were checking data and ones were Fataling in case of errors. Which was really hardening reading through tests and complicating writing new ones since it was not clear what will happen with testing.T in each method. And in each point of time you was not able to tell exactly will test execution flow will be affected or not. That particular problem caused bug in genesis test, which in case of Fatal, while waiting for consensus, led to cleanup function not being returned and not being called. In result database was corrupted and this is how i found it.
So I propose this way:

Passing testing.T is totally fine but only if it validates i.e. checks data
all error cases which needs to prevent tests from execution need to be handled in tests itself, only exception may be helper functions either really generic (like FailTest introduced in this pr) or specific for some set of tests

ADDITIONAL
I also simplified a lot concurrency used in methods which "wait" for some event.
And fixed some tests (reward and stake ones).
I removed insufficient funds tests, since we won't proceed to next round now with such transactions - they just won't be accepted by other nodes during tx sync.
I more or less unified all timeouts for wait methods.
Merkle root for tests is changed since I added rewards into genesis for test wallet2 in order to fix reward test.
Tests seems to be both more stable and faster now.
NOTE:
I'm going to change ALL
if !assert.NoError(b, err) {
	return
}

with
FailTest(t, err)

@a-urth I rebased this PR on top of master, because there is significant change on syncing due to introduction of SyncManager.

@hasyimibhar yes, syncing changed a lot, but it should've not affect tests that much. when i was checking it only WaitForSync should've change.

@hasyimibhar @iwasaki-kenta all test problems are resolved, this is may be reviewed and merged


Pandoc haskell filter

Pandoc filters are primarily written in Haskell or Lua. The first version of the rustic-doc filter was written in Haskell. The first comments I received were that I should port the filter to lua, to make it easier for contributors as lua was seen as an easier language than Haskell. I listened to the advice and ported it to lua, but in hindsight, it was a mistake.
The lua filter is way messier and harder to interpret, and it has made working in the filter rather painful. This PR is restoring the old Haskell filter, and making some related changes along the way.

Pandoc is now installed automatically. Recently some issues related to versioning were discovered (particularly on debian based distros), and by installing our own local version of pandoc we know everyone has a compatible version. Pandoc is tiny enough and entirely self-contained, so I'm just placing the binary next to the other required resources. This also ensures compatibility with the filter.
To make distribution simple, I added the 38 MB Haskell binary to git. I previously used github releases to distribute it, and I'm fine with doing that or something else entirely - I know some wince at the thought of tracking binaries.
Despite not being touched for 1.5 years, the Haskell filter generates better-looking org documents than the Lua filter ever did.

To make distribution simple, I added the 38 MB Haskell binary to git. I previously used github releases to distribute it, and I'm fine with doing that or something else entirely - I know some wince at the thought of tracking binaries.

Is it a static binary ? I'm concerned if it will work on all distributions.

To make distribution simple, I added the 38 MB Haskell binary to git. I previously used github releases to distribute it, and I'm fine with doing that or something else entirely - I know some wince at the thought of tracking binaries.

Is it a static binary ? I'm concerned if it will work on all distributions.

It should be, except for glibc, which I painfully realized last night before going to bed.  It seems possible to statically link musl instead though, I will look into it as that part is essential.

It seems possible to statically link musl instead though, I will look into it as that part is essential.

One option is to use this project to build musl based executable: https://github.com/fpco/alpine-haskell-stack
But it seems it still doesn't support GHC 8.10.7 (since you are using Stackage LTS 18.23), but supports 8.10.6. But I believe adding support for 8.10.7 shouldn't be hard.

To make distribution simple, I added the 38 MB Haskell binary to git. I previously used github releases to distribute it, and I'm fine with doing that or something else entirely - I know some wince at the thought of tracking binaries.

Yeah, I think distributing it via github releases would be probably better. :-)

It seems possible to statically link musl instead though, I will look into it as that part is essential.

One option is to use this project to build musl based executable: https://github.com/fpco/alpine-haskell-stack
But it seems it still doesn't support GHC 8.10.7 (since you are using Stackage LTS 18.23), but supports 8.10.6. But I believe adding support for 8.10.7 shouldn't be hard.

We can use different versions of GHC, so no worries there. I'll try tonight/in the coming days.

As I was looking at this I found https://github.com/rust-lang/rust/issues/76578
Seems like this started just a month or two after I began working on rustic-doc. Using JSON would be a much more robust solution.

I gave it a try this week and kind of ran into issues, listed here: https://www.reddit.com/r/haskell/comments/siktmp/building_a_standalone_haskell_binary_with/
The most straightforward way now seems to be to do it properly and distribute it as a flatpak, but I'm hesitant to introduce more steps to the installation process.

I haven't looked the error message in detail, but if you are looking for an example - here is a Dockerfile I create to create static binary of Haskell's tldr program: https://github.com/psibi/tldr-hs/blob/master/Dockerfile Do you face the same issue if you try the same method ?

I haven't looked the error message in detail, but if you are looking for an example - here is a Dockerfile I create to create static binary of Haskell's tldr program: https://github.com/psibi/tldr-hs/blob/master/Dockerfile Do you face the same issue if you try the same method ?

That seems like a much more robust solution. How do you run it? When I clone the repo and write
docker build -t tldr . I get
Getting project config file from STACK_YAML environment
/app/tldr.cabal was modified manually. Ignoring /app/package.yaml in favor of the cabal file.
If you want to use the package.yaml file instead of the cabal file,
then please delete the cabal file.
No setup information found for ghc-8.10.7 on your platform.
This probably means a GHC bindist has not yet been added for OS key 'linux64-ncurses6'.
Supported versions: ghc-7.10.3, ghc-8.0.1, ghc-8.0.2, ghc-8.2.1, ghc-8.2.2
``

@samhedin You can see that the CI script builds the image: https://github.com/psibi/tldr-hs/blob/master/.azure/azure-linux-musl.yml#L16
And finally it produces a musl based binary here: https://github.com/psibi/tldr-hs/releases/tag/v0.9.2

As you may have noticed, my energy and time for this come sporadically. The reason is that I don't use Rust anymore, and haven't for a very long time.
Closing this for now.


Spring Cloud Config: Bootstrap context not loading profile-specific property files for binding

Might be related to https://github.com/spring-cloud/spring-cloud-config/issues/1974, though I could not replicate that issue with the latest 3.1 RC.
Setup

Spring Boot 2.6.0
Spring Cloud Config 3.1 RC1
Apache Maven 3.8.x
OpenJDK 11

Overview
I have a multi-module Apache Maven project that is set up with the following modules:

bootstrap: contains a PropertySourceLocator for BootstrapConfiguration, defined in spring.factories file.
starter: depends on bootstrap, and it's a (servlet-based) web application
reference: deploys the starter application using the Maven Cargo plugin, deploying into an Apache Tomcat 9.0.55

Runtime

The starter module declares a configuration class, annotated with @PropertySource("wa.properties"). This wa.properties on the classpath of the starter module has a setting: cas.authn.syncope.name=Starter
The starter module has a ServletInitializer that sets the spring.config.name property to "wa" when building the spring application.
The reference module only has a wa-embedded.properties file on the classpath with a setting: cas.authn.syncope.name=Embedded
The reference module starts with the spring activated profiles: embedded,all

Note: the cas.authn.syncope.name is bound to a Java POJO, CasConfigurationProperties, that is annotated with @ConfigurationProperties("cas").
Observation
The following bean in the application exists, simplified for this post:
@Bean
@ConditionalOnMissingBean(name = "something")
@RefreshScope(proxyMode = ScopedProxyMode.DEFAULT)
public Something something(ApplicationContext ctx, CasConfigurationProperties cas) {
	...
}

If I look at the contents of cas.getAuthn().getSyncope().getName()), it shows: "Starter"
If I look at ctx.getEnvironment().getProperty("cas.authn.syncope.name"), it shows "Embedded".

In other words, property binding used during the bootstrapping process does not match the actual environment for the application's context.
Analysis

It appears that when the bootstrap application context is created, wa-embedded.properties, a profile-specific property is not read. In fact, the only property source that is used for binding is wa.properties as part of "localProperties", which I believe comes from @PropertySource("wa.properties"). Nothing else is read or found.

Then, property binding takes place binding CasConfigurationProperties and cas.authn.syncope.name initialized from @PropertySource("wa.properties"). The value of this property is set to Starter.

Then, the application servlet context is initialized and its environment is post-processed with profiles and the appropriate listener and Spring beans are created. In particular, this bean:

@Bean
@ConditionalOnMissingBean(name = "something")
@RefreshScope(proxyMode = ScopedProxyMode.DEFAULT)
public Something something(ApplicationContext ctx, CasConfigurationProperties cas) {
	...
}

...shows that ctx is the actual application context with an environment that is post-processed via all profiles and shows ctx.getEnvironment().getProperty("cas.authn.syncope.name") as "Embedded".
However, CasConfigurationProperties was processed using the Bootstrap context only, and its equivalent property shows "Starter".
...which means the bean would be created using the wrong values in CasConfigurationProperties.
Research
This setup works OK using Spring Boot 2.5.6 and Spring Cloud 3.0.5. I don't think anything in Spring Boot has changed that would affect this, but I do see a number of differences in Cloud between 3.0 and 3.1.
Sample
Working on it. I am not sure I can create a reproducer to adequately showcase this, but I will try.

We will wait for your sample

Here is a reproducer:
https://github.com/mmoayyed/cloud-config-reproducer
Please note that this is a stripped-down version of the Apache Syncope codebase: https://github.com/apache/syncope. I removed all the other components to make sure the project setup is as lean as it can be, though I suppose it's not quite ideal. That said, the setup is should be very simple.
Once you clone the repository,

From the root, run mvn clean install -PskipTests
cd into fit/wa-reference and run mvn -Pdebug

You can tail the logs via tail fit/wa-reference/target/log
The project setup matches the issue description. The project is deployed into Apache Tomcat 9.0.55 via the cargo plugin. Remote debugging is available via port 8001. The application is launched using the embedded and all profiles, and the spring.config.name is set to wa.
The app should be reading wa.properties file, and wa-embedded.properties file. The latter should replace values and overwrite what is found in the former. That is not the case, and is the heart of this issue.
When it's up (Ignore exceptions related to Syncope registration during startup), you should be able to go to: http://localhost:9080/syncope-wa/
...and see this output:
{
  configName: "DefaultSyncopeAuthModuleEmbedded",
  handlerNames: "DefaultSyncopeAuthModuleWAStarter", // problem!
  envName: "DefaultSyncopeAuthModuleEmbedded"
}

The controller that outputs this data demonstrates the issue, and is as follows:
    @RestController("cas")
    public static class MyController {
        @Autowired
        private CasConfigurationProperties properties;

        @Autowired
        @Qualifier("syncopeAuthenticationHandlers")
        private BeanContainer<AuthenticationHandler> syncopeAuthenticationHandlers;

        @Autowired
        private ConfigurableApplicationContext applicationContext;

        @GetMapping(produces = "application/json")
        public Map value() {
            var map = new LinkedHashMap<>();
            map.put("configName", properties.getAuthn().getSyncope().getName());
            map.put("handlerNames", syncopeAuthenticationHandlers.toList().stream().map(h -> h.getName()).collect(Collectors.joining()));
            map.put("envName", applicationContext.getEnvironment().getProperty("cas.authn.syncope.name"));
            return map;
        }
    }

The handlerNames field is fetched from the syncopeAuthenticationHandlers bean. This bean is initialized during the bootstrap process, with only the properties that do come from wa.properties. wa-embedded.properties which is a property file for a specific embedded profile is not used when syncopeAuthenticationHandlers bean is created.
The syncopeAuthenticationHandlers is part of the "cas-server-support-syncope-authentication` module. It's defined as such:
    @ConditionalOnMissingBean(name = "syncopeAuthenticationHandlers")
    @Bean
    @RefreshScope(proxyMode = ScopedProxyMode.DEFAULT)
    public BeanContainer<AuthenticationHandler> syncopeAuthenticationHandlers(
        final CasConfigurationProperties casProperties, // configuration binding...
        final ConfigurableApplicationContext applicationContext,
        @Qualifier("syncopePrincipalFactory")
        final PrincipalFactory syncopePrincipalFactory,
        @Qualifier("syncopePasswordPolicyConfiguration")
        final PasswordPolicyContext syncopePasswordPolicyConfiguration,
        @Qualifier(ServicesManager.BEAN_NAME)
        final ServicesManager servicesManager) {

        val syncope = casProperties.getAuthn().getSyncope();
        val handlers = Splitter.on(",").splitToList(syncope.getDomain())
            .stream()
            .map(domain -> {
                // here, syncope.getName() does not point to the value in the property profile...
                // This should come from wa-embedded.properties.
                // Instead, it always comes from the wa.properties
                val h = new SyncopeAuthenticationHandler(syncope.getName(), servicesManager,
                    syncopePrincipalFactory, syncope.getUrl(), domain.trim());
                h.setState(syncope.getState());
                h.setPasswordEncoder(PasswordEncoderUtils.newPasswordEncoder(syncope.getPasswordEncoder(), applicationContext));
                h.setPasswordPolicyConfiguration(syncopePasswordPolicyConfiguration);
                val predicate = CoreAuthenticationUtils.newCredentialSelectionPredicate(syncope.getCredentialCriteria());
                h.setCredentialSelectionPredicate(predicate);
                val transformer = PrincipalNameTransformerUtils.newPrincipalNameTransformer(syncope.getPrincipalTransformation());
                h.setPrincipalNameTransformer(transformer);
                return h;
            })
            .map(AuthenticationHandler.class::cast)
            .collect(Collectors.toList());
        return BeanContainer.of(handlers);
    }

Expectation
The endpoint should always produce DefaultSyncopeAuthModuleEmbedded as the value for all 3 fields. This is the current behavior with Spring Boot 2.5.7 and Spring Cloud 3.0.5.

I see 3.1.0 is now released and will try to determine if I can reproduce the same issue with the latest release.

I'm guessing you will but let us know

Tried again with Cloud 3.1.0 and Spring Boot 2.6.1. Same issue.

Ran a few more experiments:

If I rename the wa-embedded.properties file to bootstrap-embedded.properties, no difference. The file is not read/used for property binding.

I can confirm this using the same Controller:
    @RestController("cas")
    public static class MyController {
        @Autowired
        private CasConfigurationProperties properties;

        @Autowired
        @Qualifier("syncopeAuthenticationHandlers")
        private BeanContainer<AuthenticationHandler> syncopeAuthenticationHandlers;

        @Autowired
        private ConfigurableApplicationContext applicationContext;

        @GetMapping(produces = "application/json")
        public Map value() {
            var map = new LinkedHashMap<>();
            map.put("configName", properties.getAuthn().getSyncope().getName());
            map.put("handlerNames", syncopeAuthenticationHandlers.toList().stream().map(h -> h.getName()).collect(Collectors.joining()));
            map.put("envName", applicationContext.getEnvironment().getProperty("cas.authn.syncope.name"));
            return map;
        }
    }

Same output as before.

If I rename the wa-embedded.properties file to bootstrap.properties, then the output changes. This time I get:

{
configName: "DefaultSyncopeAuthModuleWAStarter",
handlerNames: "DefaultSyncopeAuthModuleEmbedded",
envName: "DefaultSyncopeAuthModuleWAStarter"
}

This time, handlerNames is initialized correctly using bootstrapping process and bootstrap.properties. However, the other two fields are wrong. Now, the application context's environment does not match the bootstrap properties in the environment.

If I change the configName to "wa" using spring.cloud.bootstrap.name=wa
Then I get:

And then the endpoint shows the following:
{
configName: "DefaultSyncopeAuthModuleEmbedded",
handlerNames: "DefaultSyncopeAuthModuleEmbedded",
envName: "DefaultSyncopeAuthModuleEmbedded"
}

...which is correct.

Has anything changed in this area in 3.1.x?
Should StandardConfigDataLocationResolver also consider spring.config.name when it's looking at configuration names? It appears to be only be aware of spring.cloud.bootstrap.name which by default only looks at bootstrap.

I'll have to do some more testing with everything else, but it seems to be some sort of regression[?]

To clarify, the configName is picked up from the bootstrap listener:

and then it's used by the StandardConfigDataLocationResolver which is created here:

I have a similar problem with Spring Boot version 2.6.4 and Spring Cloud Config version 2021.0.1
I found a workaround as adding a configuration as:
spring:
    profiles.active: dev
    cloud:
        config:
            profile: ${spring.profiles.active}

In the ConfigServicePropertySourceLocator class, when trying to get the profiles, it reads them from properties and this properties only looks either spring.clod.config.profile OR spring.profiles, it does not check the active profiles.
This is why adding the above lines temporarily solves the problem

If you could try Spring Cloud 2021.0.8-SNAPSHOT we have made some changes regarding profiles and activation.
See https://docs.spring.io/spring-cloud-commons/docs/3.1.7-SNAPSHOT/reference/html/#application-context-hierarchies

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Should not warn if control flow reaches closing } of main

Since C99, if the return type of main is compatible with int and control flow reaches the closing }, then main implicitly returns 0. GCC and clang issue no warnings.
Skipping the warning is easy enough, but how should we handle the AST - it looks like .implicit_return nodes don't have any associated data. Should we have a separate node type for implicit_main_return?

Skipping the warning is easy enough, but how should we handle the AST - it looks like .implicit_return nodes don't have any associated data. Should we have a separate node type for implicit_main_return?

implicit_return also doesn't use any of the fields in Node.data so it would be easy to add a bool there.

Just a zero, it's in section <IP_ADDRESS>.3
If the return type of the main function is a type compatible with int, a return from the
initial call to the main function is equivalent to calling the exit function with the value
returned by the main function as its argument; reaching the } that terminates the
main function returns a value of 0. If the return type is not compatible with int, the
termination status returned to the host environment is unspecified.

Just a zero, it's in section <IP_ADDRESS>.3

Huh, I guess I was mixing it up with some other gotcha. Do we then actually need to differentiate between this and a regular implicit_return, they should be perfectly identical in every way except that one didn't give an error.

So just always treat implicit_return as if it's returning an integer 0? I think that would work.

So just always treat implicit_return as if it's returning an integer 0? I think that would work.

Looks like I was also mixing up implicit_return and default_init_expr or something... Ok, I think adding a return_zero field to Node.Data used by implicit_return is a good way to go here.


New atoms for OEMol purpose get -1 index

This PR is done. All it does is assign an "index" of -1 for the atoms that we add to make an OEMol. This doesn't impact anything else, but will make it easy for @juliebehr to distinguish these atoms when making an atom map between protein residues.

Yay!

Ok, I'm going to merge this to get out of the way.

Thanks!


Add remove student cmd

Codecov Report

Merging #58 (3e88a53) into master (eecaca4) will decrease coverage by 0.99%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #58      +/-   ##
============================================
- Coverage     47.64%   46.64%   -1.00%
  Complexity      432      432
============================================
  Files           102      104       +2
  Lines          2101     2146      +45
  Branches        233      243      +10
============================================
  Hits           1001     1001
- Misses         1058     1103      +45
  Partials         42       42

Impacted Files
Coverage Δ

...u/address/logic/commands/RemoveStudentCommand.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
68.00% <0.00%> (-2.84%)
:arrow_down:

...dress/logic/parser/RemoveStudentCommandParser.java
0.00% <0.00%> (ø)

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 eecaca4...3e88a53. Read the comment docs.


Extension management does not work when on Ubuntu installed from snap

Issue Type: Bug

sudo snap install code --classic
code
Open extension management. Observe:
3.1. "recommended" list is empty
3.2. marketplace search does not work (the blue line above the search just keeps running forever)
3.3. there's a "clock" mark on the "extensions" icon in the left bar
3.4. no updates for extensions are pulled
3.5. extensions can be deleted, but they do not disappear from the extension list, the only indication is that the "cog" icon for them stops to work
3.6. Even "Install from VSIX..." functionality fails to work (no error is displayed).

Workaround:

Uninstall the snap, dowlnoad a .deb from the VS Code website, install the .deb
Everything works - existing extensions can be updated, installing new extensions from the marketplace works.

I have seen no network requests or relevant console errors in Developer Tools; no messages from code --verbose output seemed relevant.
My hunch is it has to do something with snap permissions, possibly garbled by upgrading Ubuntu from the previous version.
VS Code version: Code 1.46.0 (a5d1cc28bb5da32ec67e86cc50f84c67cc690321, 2020-06-10T08:59:04.923Z)
OS version: Linux x64 5.5.0-050500-lowlatency snap

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1666)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
15.52GB (1.06GB free)

Process Argv
. --no-sandbox

Screen Reader
no

VM
0%

DESKTOP_SESSION
xubuntu

XDG_CURRENT_DESKTOP
XFCE

XDG_SESSION_DESKTOP
xubuntu

XDG_SESSION_TYPE
x11

Extensions (17)

Extension
Author (truncated)
Version

vscode-css-formatter
aes
1.0.1

vscode-hie-server
ala
0.0.40

vscode-bazel
Baz
0.3.0

better-toml
bun
0.3.2

bazel-code
Dev
0.1.9

vscode-wasm
dts
1.3.1

gitlens
eam
10.2.2

lex-flex-yacc-bison
fau
0.0.3

Go
gol
0.14.4

language-haskell
jus
3.2.1

restructuredtext
lex
128.0.0

rust-analyzer
mat
0.2.199

vscode-docker
ms-
1.2.1

python
ms-
2020.5.86806

cpptools
ms-
0.28.3

slim
sia
0.1.2

change-case
wma
1.0.0

(1 theme extensions excluded)

Please share the logs from the following locations
- Help -> Toggle Developer Tools -> Console
- View -> Command Pallette... -> Toggle Shared Process -> Console
- View -> Open View… -> Log (Shared)
- View -> Open View… -> Log (Window)

It's the same for me, but installing extension from the command line code --install-extension xyz.xyz is working.

@sandy081

Please share the logs from the following locations

Help -> Toggle Developer Tools -> Console

/snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:264 [Extension Host] activating extension
/snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:264 [Extension Host] starting language server
/snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:264 [Extension Host] updateCustomBrowseConfiguration
/snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:264 [Extension Host] (node:19626) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
t.log @ /snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:264
/snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:264 [Extension Host] (node:19626) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
t.log @ /snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:264

View -> Command Pallette... -> Toggle Shared Process -> Console

empty

View -> Open View… -> Log (Shared)

doesn't exist

View -> Open View… -> Log (Window)

doesn't exist
However a Log(Extension Host) exist which shows
[2020-06-17 15:57:38.390] [exthost] [info] extension host started
[2020-06-17 15:57:38.418] [exthost] [info] ExtensionService#_doActivateExtension vscode.configuration-editing {"startup":false,"extensionId":{"value":"vscode.configuration-editing","_lower":"vscode.configuration-editing"},"activationEvent":"onLanguage:jsonc"}
[2020-06-17 15:57:38.418] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/configuration-editing/dist/extension
[2020-06-17 15:57:38.421] [exthost] [info] ExtensionService#_doActivateExtension vscode.json-language-features {"startup":false,"extensionId":{"value":"vscode.json-language-features","_lower":"vscode.json-language-features"},"activationEvent":"onLanguage:jsonc"}
[2020-06-17 15:57:38.421] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/json-language-features/client/dist/jsonMain
[2020-06-17 15:57:38.434] [exthost] [info] ExtensionService#_doActivateExtension vscode.typescript-language-features {"startup":false,"extensionId":{"value":"vscode.typescript-language-features","_lower":"vscode.typescript-language-features"},"activationEvent":"onLanguage:jsonc"}
[2020-06-17 15:57:38.434] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/typescript-language-features/dist/extension
[2020-06-17 15:57:38.443] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"extensionId":{"value":"vscode.debug-auto-launch","_lower":"vscode.debug-auto-launch"},"activationEvent":"*"}
[2020-06-17 15:57:38.443] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/debug-auto-launch/dist/extension
[2020-06-17 15:57:38.444] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"extensionId":{"value":"vscode.emmet","_lower":"vscode.emmet"},"activationEvent":"*"}
[2020-06-17 15:57:38.444] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/emmet/dist/extension
[2020-06-17 15:57:38.454] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":{"value":"vscode.github","_lower":"vscode.github"},"activationEvent":"*"}
[2020-06-17 15:57:38.454] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/git/dist/main
[2020-06-17 15:57:38.466] [exthost] [info] ExtensionService#_doActivateExtension vscode.github-authentication {"startup":true,"extensionId":{"value":"vscode.github-authentication","_lower":"vscode.github-authentication"},"activationEvent":"*"}
[2020-06-17 15:57:38.466] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/github-authentication/dist/extension.js
[2020-06-17 15:57:38.471] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"extensionId":{"value":"vscode.merge-conflict","_lower":"vscode.merge-conflict"},"activationEvent":"*"}
[2020-06-17 15:57:38.471] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/merge-conflict/dist/extension
[2020-06-17 15:57:38.472] [exthost] [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication {"startup":true,"extensionId":{"value":"vscode.microsoft-authentication","_lower":"vscode.microsoft-authentication"},"activationEvent":"*"}
[2020-06-17 15:57:38.472] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/microsoft-authentication/dist/extension.js
[2020-06-17 15:57:38.479] [exthost] [info] ExtensionService#_doActivateExtension vscode.search-result {"startup":true,"extensionId":{"value":"vscode.search-result","_lower":"vscode.search-result"},"activationEvent":"*"}
[2020-06-17 15:57:38.480] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/search-result/dist/extension.js
[2020-06-17 15:57:38.480] [exthost] [info] ExtensionService#_doActivateExtension eamodio.gitlens {"startup":true,"extensionId":{"value":"eamodio.gitlens","_lower":"eamodio.gitlens"},"activationEvent":"*"}
[2020-06-17 15:57:38.480] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/mat/.vscode/extensions/eamodio.gitlens-10.2.1/dist/extension
[2020-06-17 15:57:38.495] [exthost] [info] ExtensionService#_doActivateExtension Gruntfuggly.todo-tree {"startup":true,"extensionId":{"value":"Gruntfuggly.todo-tree","_lower":"gruntfuggly.todo-tree"},"activationEvent":"*"}
[2020-06-17 15:57:38.495] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/mat/.vscode/extensions/gruntfuggly.todo-tree-0.0.169/extension
[2020-06-17 15:57:38.615] [exthost] [info] ExtensionService#_doActivateExtension hbenl.vscode-test-explorer {"startup":true,"extensionId":{"value":"hbenl.vscode-test-explorer","_lower":"hbenl.vscode-test-explorer"},"activationEvent":"*"}
[2020-06-17 15:57:38.615] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/mat/.vscode/extensions/hbenl.vscode-test-explorer-2.17.0/out/main.js
[2020-06-17 15:57:38.623] [exthost] [info] ExtensionService#_doActivateExtension mhutchie.git-graph {"startup":true,"extensionId":{"value":"mhutchie.git-graph","_lower":"mhutchie.git-graph"},"activationEvent":"*"}
[2020-06-17 15:57:38.623] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/mat/.vscode/extensions/mhutchie.git-graph-1.21.0/out/extension.js
[2020-06-17 15:57:38.632] [exthost] [info] ExtensionService#_doActivateExtension SirTori.indenticator {"startup":true,"extensionId":{"value":"SirTori.indenticator","_lower":"sirtori.indenticator"},"activationEvent":"*"}
[2020-06-17 15:57:38.632] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/mat/.vscode/extensions/sirtori.indenticator-0.6.0/out/src/extension
[2020-06-17 15:57:38.634] [exthost] [info] ExtensionService#_doActivateExtension vscode.npm {"startup":true,"extensionId":{"value":"vscode.npm","_lower":"vscode.npm"},"activationEvent":"workspaceContains:package.json"}
[2020-06-17 15:57:38.634] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/npm/dist/main
[2020-06-17 15:57:38.638] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.cpptools {"startup":true,"extensionId":{"value":"maddouri.cmake-tools-helper","_lower":"maddouri.cmake-tools-helper"},"activationEvent":"workspaceContains:CMakeLists.txt"}
[2020-06-17 15:57:38.638] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/mat/.vscode/extensions/ms-vscode.cpptools-0.26.3/dist/main
[2020-06-17 15:57:38.697] [exthost] [info] ExtensionService#_doActivateExtension twxs.cmake {"startup":true,"extensionId":{"value":"maddouri.cmake-tools-helper","_lower":"maddouri.cmake-tools-helper"},"activationEvent":"workspaceContains:CMakeLists.txt"}
[2020-06-17 15:57:38.697] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/mat/.vscode/extensions/twxs.cmake-0.0.17/out/extension
[2020-06-17 15:57:39.203] [exthost] [info] ExtensionService#_doActivateExtension vscode.github {"startup":true,"extensionId":{"value":"vscode.github","_lower":"vscode.github"},"activationEvent":"*"}
[2020-06-17 15:57:39.203] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/github/dist/extension.js
[2020-06-17 15:57:39.454] [exthost] [info] eager extensions activated

Please share the logs from the following locations

Help -> Toggle Developer Tools -> Console

/snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:5063 Overwriting grammar scope name to file mapping for scope source.regexp.python.
Old grammar file: file:///snap/code/34/usr/share/code/resources/app/extensions/python/syntaxes/MagicRegExp.tmLanguage.json.
New grammar file: file:///home/rainman/.vscode/extensions/devondcarew.bazel-code-0.1.9/syntax/MagicRegExp.tmLanguage.json
register @ /snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:5063
/snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:5063 Overwriting grammar scope name to file mapping for scope source.rust.
Old grammar file: file:///snap/code/34/usr/share/code/resources/app/extensions/rust/syntaxes/rust.tmLanguage.json.
New grammar file: file:///home/rainman/.vscode/extensions/matklad.rust-analyzer-0.2.199/rust.tmGrammar.json
register @ /snap/code/34/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:5063

and no new messages when opening the extensions screen

View -> Command Pallette... -> Toggle Shared Process -> Console

empty

View -> Open View… -> Log (Shared)

[2020-06-17 17:19:00.716] [sharedprocess] [info] main {"machineId":"80c5520241e401c5cecd7b45986b0f1b331f6ac97f807c13fd15e69ff6492839","windowId":2}
[2020-06-17 17:19:40.728] [sharedprocess] [info] Starting to clean up unused language packs.

View -> Open View… -> Log (Window)

doesn't exist, but there's Log(Main):
[2020-06-17 17:18:57.048] [main] [info] update#setState idle
[2020-06-17 17:19:27.058] [main] [info] update#setState checking for updates
[2020-06-17 17:19:27.062] [main] [info] update#setState idle

Also there is  Log(Extension Host):
[2020-06-17 17:18:58.919] [exthost] [info] extension host started
[2020-06-17 17:18:58.941] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"extensionId":{"value":"vscode.debug-auto-launch","_lower":"vscode.debug-auto-launch"},"activationEvent":"*"}
[2020-06-17 17:18:58.941] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/debug-auto-launch/dist/extension
[2020-06-17 17:18:58.944] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"extensionId":{"value":"vscode.emmet","_lower":"vscode.emmet"},"activationEvent":"*"}
[2020-06-17 17:18:58.944] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/emmet/dist/extension
[2020-06-17 17:18:58.955] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":{"value":"vscode.github","_lower":"vscode.github"},"activationEvent":"*"}
[2020-06-17 17:18:58.955] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/git/dist/main
[2020-06-17 17:18:58.991] [exthost] [info] ExtensionService#_doActivateExtension vscode.github-authentication {"startup":true,"extensionId":{"value":"vscode.github-authentication","_lower":"vscode.github-authentication"},"activationEvent":"*"}
[2020-06-17 17:18:58.991] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/github-authentication/dist/extension.js
[2020-06-17 17:18:58.994] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"extensionId":{"value":"vscode.merge-conflict","_lower":"vscode.merge-conflict"},"activationEvent":"*"}
[2020-06-17 17:18:58.994] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/merge-conflict/dist/extension
[2020-06-17 17:18:58.995] [exthost] [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication {"startup":true,"extensionId":{"value":"vscode.microsoft-authentication","_lower":"vscode.microsoft-authentication"},"activationEvent":"*"}
[2020-06-17 17:18:58.995] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/microsoft-authentication/dist/extension.js
[2020-06-17 17:18:59.004] [exthost] [info] ExtensionService#_doActivateExtension vscode.search-result {"startup":true,"extensionId":{"value":"vscode.search-result","_lower":"vscode.search-result"},"activationEvent":"*"}
[2020-06-17 17:18:59.004] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/search-result/dist/extension.js
[2020-06-17 17:18:59.005] [exthost] [info] ExtensionService#_doActivateExtension eamodio.gitlens {"startup":true,"extensionId":{"value":"eamodio.gitlens","_lower":"eamodio.gitlens"},"activationEvent":"*"}
[2020-06-17 17:18:59.005] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/rainman/.vscode/extensions/eamodio.gitlens-10.2.2/dist/extension
[2020-06-17 17:18:59.052] [exthost] [info] ExtensionService#_doActivateExtension vscode.npm {"startup":true,"extensionId":{"value":"vscode.npm","_lower":"vscode.npm"},"activationEvent":"workspaceContains:package.json"}
[2020-06-17 17:18:59.052] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/npm/dist/main
[2020-06-17 17:18:59.146] [exthost] [info] ExtensionService#_doActivateExtension vscode.github {"startup":true,"extensionId":{"value":"vscode.github","_lower":"vscode.github"},"activationEvent":"*"}
[2020-06-17 17:18:59.146] [exthost] [info] ExtensionService#loadCommonJSModule file:///snap/code/34/usr/share/code/resources/app/extensions/github/dist/extension.js
[2020-06-17 17:18:59.259] [exthost] [info] ExtensionService#_doActivateExtension golang.Go {"startup":true,"extensionId":{"value":"golang.Go","_lower":"golang.go"},"activationEvent":"workspaceContains:**/*.go"}
[2020-06-17 17:18:59.259] [exthost] [info] ExtensionService#loadCommonJSModule file:///home/rainman/.vscode/extensions/golang.go-0.14.4/out/src/goMain
[2020-06-17 17:18:59.472] [exthost] [info] eager extensions activated

I am really no clue what's happening here
@joaomoreno seems it works with deb package but not with snap. Any clue?

Similar to https://github.com/microsoft/vscode/issues/86583. @kyegupov Do you mind going through that issue and seeing if you find anything relevant to you?

@joaomoreno I have looked a #86583, but it doesn't apply to me directly: I don't use imwheel and the shared-process seems to be running (I can see it in the process explorer).


[Feature Request] make el-step component's property'description'render by v-html instead of {{}}

Existing Component
是
Component Name
el-step
Description
in my case, i want to break line ,but i can not put an  tag into the content, it make my content very messy

Use the description slot: https://jsfiddle.net/1ry1kjnm/


Bring Rect in line with System.Drawing.Rectangle

Since Rect is just a copy/paste of Rectangle, aside from slightly different ToString behavior, it's a prime candidate for removal.
To make removal smoother, I'm going to approach it in two stages. First, I'll make the behaviors it exhibits that are different from System.Drawing.Rectangle the same as in that type. That will require fixing unit tests, since the ToString output is heavily relied upon in many tests.
Once everything is working, the type can be renamed, to make the solution-wide change to Rectangle. Then the type can be deleted and a reference added to System.Drawing.Rectangle as a type alias (rather than the entire namespace) to swap them in-place.

Also, citing the "don't be weird" tenet for the project, I'm relocating it to the Terminal.Gui.Drawing namespace.