conflict between structured filter styles and Bootstrap buttons

I do not recommend using both jQuery-UI style and Bootstrap at the same time.
I have another version of the structured-filer (which uses Bootstrap) as part of Evolutility-UI-jQuery.
https://github.com/evoluteur/evolutility-ui-jquery

Okay Thanks, I will try with another version.
On 11 June 2017 at 03:41, Olivier Giulieri<EMAIL_ADDRESS>wrote:

Closed #18 https://github.com/evoluteur/structured-filter/issues/18.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/evoluteur/structured-filter/issues/18#event-1118365592,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARbn9Stg5PhOXO0AZYXMQLTGP15lUkpOks5sCxR7gaJpZM4N2G4F
.

Can I use evolutility-ui-jquery for server side pagination for the
collection like backgrid?
On 12 June 2017 at 11:04, Abhishek Patil<EMAIL_ADDRESS>wrote:

Okay Thanks, I will try with another version.
On 11 June 2017 at 03:41, Olivier Giulieri<EMAIL_ADDRESS>wrote:

Closed #18 https://github.com/evoluteur/structured-filter/issues/18.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/evoluteur/structured-filter/issues/18#event-1118365592,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARbn9Stg5PhOXO0AZYXMQLTGP15lUkpOks5sCxR7gaJpZM4N2G4F
.

Sorry, it is not implemented. It is not difficult to do. I have it on Evolutility-UI-React.

Okay, Thanks for update Olivier. Currently, am using backbone, backgrid and
Structured filter. Which was working fine until I started to use "Bootstrap
Button.js". And Your evolutility-ui-jquerry is Awesome. It is exactly what
I need. The only problem is now is, I need pagination support like backgrid
also. Anyway, your work is awesome,  evolutility-ui-jquerry is awesome.
On 13 June 2017 at 09:43, Olivier Giulieri<EMAIL_ADDRESS>wrote:

Sorry, it is not implemented. It is not difficult to do. I have it on
Evolutility-UI-React.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/evoluteur/structured-filter/issues/18#issuecomment-308001825,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARbn9QJ8QN5FtG9TeQZ8x7IALovMSEG_ks5sDgxjgaJpZM4N2G4F
.

Hi Olivier
Hope you are doing good, I need your help, Can I add relative date type
option in date option. I have attached sample image below. Please find the
attached file and let me know.


docs: updated generate:readme command to use multi files per topic

Changes:

Used --multi flag on generate:readme for oclif to separate commands descriptions per topic.
The description of each commands now resides under the /docs folder while the main README file contains the TOC of each command topic.

:tada: This PR is included in version 2.5.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


[FR] Conext key for detecting if an editor is a markdown preview

Command markdown.showSource shows the source code of a markdown preview, how to write the When condition so that markdown.showSource only triggers when the active editor is indeed a markdown preview? If such a context key doesn't already exist, please consider adding one.

See How to detect if an editor is a markdown preview?.


Properties from merged references are ignored when using bundle

When merging references, redocly-cli bundle will ignore existing properties.
For example with 2 files:
id.yaml:
type: integer
format: int32
description: A generic ID used everywhere
example: 42

id_ro.yaml:
$ref: ./id.yaml
readOnly: true
description: A generic ID but that is specifically read only

The result will never include readOnly: true or the updated description.
To Reproduce
I've created a gist with a minimal working example and reproduction steps.

Given default settings
And the example.yaml (and referenced files) in the gist
Run the bundle command(s) found in the gist
(e.g. docker run --rm -v $PWD:/spec redocly/cli bundle example.yaml -o out-redocly-cli.yaml)
See ignored merged properties

Expected behavior
The duplicate properties defined after reference should appear in the resulting yaml file.
Logs
N/A
OpenAPI description
See the files supplied in the linked gist.
Only default configuration was used with the supplied yaml files.
Redocly Version(s)
1.4.0 as built in the docker image
Node.js Version(s)
v21.1.0 as built in the docker image
Additional context
I used the latest tagged docker image at the time I ran it. Image hash 3bcfba9186cf
Additional details and output can be found in the gist.

Hi @Gidgidonihah,
Could you check if using the allOf trick solves your issue?
allOf:
- $ref: ./id.yaml
readOnly: true
description: A generic ID but that is specifically read only

It does result in the readOnly: true being present.
That's a functional workaround that I hadn't thought about. That can get me moving forward easier than completely moving things around. So that's good.
But I don't think that should be a long-term solution. It feels like silently dropping them is the wrong thing to do.

But I don't think that should be a long-term solution.

I agree. The behaviour isn't obvious. I believe it stems from the difference in JSON Schema drafts:

Draft-specific info
In Draft 4-7, $ref behaves a little differently. When an object contains a $ref property, the object is considered a reference, not a schema. Therefore, any other properties you put in that object will not be treated as JSON Schema keywords and will be ignored by the validator. $ref can only be used where a schema is expected.

Both ideas are not valid though:
The spec (3.1.0) allows only for summary or description to be sibling to the $ref and allOf doesn't make sense with readOnly in the example (I understand it may impact the Redoc rendering but it doesn't change that it is illogical (I could update that article to add readOnly as an example of an illogical allOf -- because it's not an extension, it's a logical and.)
Separately though which should be checked is overriding the description within a reference that points to a reference with a sibling. We may have a bug with nested $ref where the inner one has a sibling description and it is not used.

@adamaltman the issue is still there though, as we don't properly resolve description either.
Regarding other keys, maybe it's worth introducing a rule that will warn if someone uses a property that will be ignored?
Moving further, the spec says that this restriction (only description and summary keys) only refers to the Reference Object and not to a Schema Object that contains $ref. So I'd assume that a resolved (using the allOf) part of a schema could be extended with any other allowed keys for composition.

Related issue: https://github.com/Redocly/redocly-cli/issues/1510


Problem injecting php

All editors have an issue injecting php.
The problem arises because of the fact phpparser has injection query for html.
Temporary fix ideas:

try to fork php, and create a php-only tree-sitter parser with no injection.
change the package.json to reflect

Instead of forking the repo and maintaining a separate copy of the original, the best thing to do would be to submit a PR to the original repo that splits into two different parsers, similar to the markdown parser in which two parsers live in the same repo:

Instead of forking the repo and maintaining a separate copy of the original, the best thing to do would be to submit a PR to the original repo that splits into two different parsers, similar to the markdown parser in which two parsers live in the same repo:

Very interesting @CalebDW.  Quick question 🤔, that doesn’t look like a submodule as well, are they maintaining two separate folders?
PHP is ever growing so the main branch would be changing frequently as the new versions come out. Wouldn’t that mean duplicate work for writing new php grammars inside two separate folders?
Now what I had in mind in terms of maintainability (which might not even be practical, as I am not really an expert in GitHub/git) was the following:

fork the branch, do all the necessary adjustment, changing the parser name and somehow remove the html injection  etc
The tree-sitter-php evolves on its own branch
whenever there is a new release we merge the main into the phpbase branch this way the php only version stays update meanwhile not doing any HTML injection etc.

@EmranMR,
No those are not submodules, and the common grammar between the two is in a folder the next level up. In the case of the PHP parser I've already split them up and will try to submit a draft PR to garner feedback from the project maintainers.
There's no duplicate work, the entire php grammer is in the php-only directory and the php grammer just parses the text and php sections and then injects those languages into the nodes

@EmranMR,
No those are not submodules, and the common grammar between the two is in a folder the next level up. In the case of the PHP parser I've already split them up and will try to submit a draft PR to garner feedback from the project maintainers.
There's no duplicate work, the entire php grammer is in the php-only directory and the php grammer just parses the text and php_only sections and then injects those languages into the nodes

Oh wow, you have already done all the work  + the PR!! 🎉🎉
Can’t wait to actually clone and try it out myself as well. Hopefully there are no issues and we get the merge soon 🤞 one of the roadblocks out the way, one step at a time.

@calebdw sorry for bothering you about this. It seems like split parser support has landed (many thanks for that effort), but I wasn't able to verify it on my local setup (I'm the author of EmranMR/tree-sitter-blade#51).
Judging from the code of tree-sitter-blade, I'm assuming treesitter won't build php_only parser right away during :TSInstall, since Makefile still uses php parser by default, is this correct or am I missing the plot entirely?

@stormherz no need to be sorry! There's an open PR to add the needed configs so that nvim-treesitter knows about php_only, but until that is merged you could always manually add it to treesitter

@calebdw thanks! totally forgot about that option. works like a charm, actually

@calebdw Amazing! thank you again for sorting that out!


Getting started

How to get started? What is the status? Is it usable yet?
Could you provide some kind of getting started like: http://wiki.ros.org/aubo_robot/Tutorials/Getting Started with a Aubo Robot

@reinzor
We are developing this tutorial, and you can temporarily refer to the start method of readme.md

Hi @zhaoyuRobotics , thanks fo rthe update. However, I am currently not actively using the Aubo robot anymore. I will close the issue.


Windows cannot find 'wakatime'. Make sure you've typed the name correctly, then try again.

When I try to save my project this error appears. Tested it with the command console typing "wakatime -h" and works fine as well as python and pip.

Usually this error appears when you do not have WakaTime installed (or installed properly).
If you run cmd (without the admin rights) and type in wakatime, are you getting this result?
usage: wakatime [-h] [--entity FILE] [--key API_KEY] [--write]
                [--plugin PLUGIN] [--time time] [--lineno INT]
                [--cursorpos INT] [--entity-type ENTITY_TYPE]
                [--category CATEGORY] [--proxy PROXY] [--no-ssl-verify]
                [--ssl-certs-file FILE] [--project PROJECT]
                [--alternate-project PROJECT] [--language LANGUAGE]
                [--local-file FILE] [--hostname HOSTNAME] [--disable-offline]
                [--hide-file-names] [--hide-project-names]
                [--hide-branch-names] [--exclude PATH]
                [--exclude-unknown-project] [--include PATH]
                [--include-only-with-project-file] [--extra-heartbeats]
                [--log-file FILE] [--api-url URL] [--timeout SECONDS]
                [--sync-offline-activity AMOUNT] [--today] [--config FILE]
                [--config-section SECTION] [--config-read KEY]
                [--config-write KEY VALUE] [--verbose] [--version]
wakatime: error: argument --entity is required

Also, what is your version of Python (python --version) and Pip (pip --version)?
In my case the versions are:
Python 3.9.4
and Pip 20.2.3
and everything is working.
If everything above fits, try restarting your computer, as that can sometimes magically fix things.
Please, give me a word if you were successful :) I'll try to research some more information about it in the meantime.

Restarting Fixed it!! I should of tried that sorry :P. Great plugin!!

Thank you :) I am glad it all works now ^^ Ill add this information to the readme.


React Native: Android Sample don't work

node: v10.1.0
react-native-cli: 2.0.1
react-native: 0.55.4
按照文档接入的 Android Sample，运行之后显示
Error while updating property 'backgroundColor' of a view managed by: GCanvasView

null

TextureView doesn't support displaying a background drawable

@diov fix: TextureView doesn't support displaying a background drawable since Android API 24
Since Alibaba feat: delete weex bridge & reactive bridge, here comes the @flyskywhy/react-native-gcanvas npm package.
After months work, @flyskywhy/react-native-gcanvas runs well on Android and iOS, fix several bugs and add feat: support drawImage() from require('some.png') on Android, iOS and Web described in Changelog.md, refactor with the detailed Example As Usage in README.md.
With Performance Test Result, and Convenient With Browser-like canvas APIs with the easily <canvas/> ported example react-native-particles-bg runs on Android, iOS and Web, @flyskywhy/react-native-gcanvas is the best choice for now :yum:


[Enhancement] Extra package.json in app folder

First of all, thanks for this great package.
Here's the issue, let's say if I am using this boilerplate to develop my own app, where should I put my own copyright message to my app? Would that be better if the default package.json file only contains all NPM dependencies for necessary packages for developing, building, etc., while leaving the main entry point to another package.json in app folder instead?
For instance, package.json would look like this, and the content of main.js would be in the app folder instead.
./package.json
{
  ...
  "start": "electron app/.",
  "start-dev": "NODE_ENV=development electron app/.",
  ...
}

./app/package.json
{
  "name"    : "your-app",
  "version" : "0.1.0",
  "main"    : "main.js"
}

In that case, it's easier to keep this boilerplate up-to-date, while it doesn't affect the app's own versioning as others develop that.

Hi!
I've seen a good example for this in https://github.com/szwacz/electron-boilerplate
An interesting side-effect is that I can get native modules easier with this approach, i.e. modules installed with npm install in /app seem to work with electron. I don't really understand why.
My use-case is pouchdb with leveldb. Even if I compile the code against electron headers, it doesn't seem to be working, pouch selects idb.
With the above boilerplate, it works, it finds and uses leveldb.

This should be closed, since this is being done in https://github.com/chentsulin/electron-react-boilerplate/pull/310

Sure, electron-builder is in our roadmap, so eventually this will be done.


[WFLY-9155] - [Migration operation] [Web to Undertow] truststore - ke…

…ystore-password does it really needs to be mandatory?
WFLY: https://issues.jboss.org/browse/WFLY-9155
(part of solution for: https://github.com/wildfly/wildfly-core/pull/2680)

@stuartwdouglas could you approve please?

Retest this please

Retest this please


Authorization scenarios and mechanisms analysis

Description
We need to get an overview of common authorization scenarios and mechanisms that exist today and will be implemented into the platform. Here are some movements happening where there are questions related to authorization.

Simplified integration for system owners: https://github.com/digdir/roadmap/issues/84

Client systems could be "fagsystemer", "sluttbrukersystemer", "leverandører" etc

"System users": https://github.com/Altinn/altinn-authentication/issues/200
App authorization

Required due to various internal operations and integrations, read more at  https://github.com/Altinn/altinn-decision-log/issues/28 and  https://github.com/Altinn/app-lib-dotnet/issues/813

Various upcoming features and integrations

User-controlled and parallel signing
BPMN service tasks, background work (Correspondence, Dialogporten)

Simplify and improve current integrations

eFormidling, PDF

Avoid token exchange in the future?

Has been discussed, will probably be handled through PEP

In scope

Map out the inbound flow and possible contexts
Map out the outbound flow (which tokens and mechanisms are used)
Start a design to better abstract authenticated state and context

Analysis
Mechanisms for authorization
These methods are supported through Altinn Authentication and Authorization through PEP and PDP.

User token (logged in through Altinn)

Authorized as: person
Access control: roles, instance delegations, dedicated XACML rules

Org token

Authorized as: org
Access control: dedicated XACML rules in app (i.e. [ORG])
Always exchanged to an Altinn token, we don't support Maskinporten directly (that would be done in PEP).
To get the right permissions, we have to use serviceowner scopes here, as that  gives us the urn:altinn:org claim in the resulting Altinn token

Systemuser

Authorized as: system user
Access control: roles, system user delegations (what actions the system user owner approves that the system can do on behalf of the system user owner)
A system user is a special Maskinporten client (in principle) using Rich Authorization Request (RAR) protocol to enrich Maskinporten tokens with Altinn system user details (systemuser_id, system_id)

App (WIP)

Authorized as: app within an org
Access control: XACML rule either manually written or injected (TBD)
Used by the app to perform certain actions independently of the current client/user
Altinn decision log item: https://github.com/Altinn/altinn-decision-log/issues/28

User flow
Log into tt02 manually, then navigate to an app

Log into tt02.altinn.no - altinnContext cookie is set (this is still A2 I think)

Some base64 stuff?

Choose party/reportee -  altinnContext and altinnReportee cookies are set (this is still A2 I think)
Go to Altinn 3 app URL directly - 302 redirect to platform.tt02.altinn.no/authentication/api/v1/authentication then back again

AltinnStudioRuntime is set by Authn API, it is a JWT, see below

Frontend renders party selection

Queries user, parties and current party (/profile/user, /parties, /authorization/parties/current)

Party selection invokes PUT /parties/{partyId}, AltinnPartyId cookie is set
App is rendered

JWT token claims:
{
  "nameid": "<int>",
  "urn:altinn:userid": "<int>",
  "urn:altinn:partyid": <int>,
  "urn:altinn:authenticatemethod": "<string>",
  "urn:altinn:authlevel": <int>
}

Q:

The partyid claim in the auth cookie can differ from altinnReportee and AltinnPartyId, how does this stay consistent?

Org flow

Authenticate with a Maskinporten client
Exchange the token through Altinn authentication
Resulting Altinn token functions as an org token (XACML must allow org actions)

JWT token claims
{
  "urn:altinn:org": "<string>",
  "urn:altinn:orgNumber": "<int>",
  "urn:altinn:authenticatemethod": "<string>",
  "urn:altinn:authlevel": <int>
}

System user flow
More details to come, but

Make system
Use supplier/system enrollment flow to register a system user (which includes delegations)
Supplier authenticates with a Maskinporten client including RAR grant
Resulting Maskinporten token can be used directly without exchange

Q:

Does it really not need to be exchanged?

JWT token
{
  "authorization_details": [
    {
      "type": "urn:altinn:systemuser",
      "systemuser_id": ["ID of system user"],
      "systemuser_org": {
        "authority": "iso6523-actorid-upis",
        "ID": "0192:Org no of the org owning the system user"
      },
      "system_id": "ID of the system in the system register"
    }
  ]
}

More details
An Altinn system user concept consists of the following entities

System user (systembruker)
System (system)
Supplier (leverandør) - the organization providing some automated Altinn-related service
Customer (kunde) - the organization using the service provided by the supplier
Maskinporten client - Maskinporten provides org-level identities meant for integrating across orgs

The customer owns the system user, and the permissions/delegations are owned by the system user.
The supplier owns the system, and the system owns the Maskinporten client.
The system owner concept/feature in Altinn 3 allows a system to impersonate a system user,
thereby enabling the system to perform operations in Altinn 3 as if it was the system user.
So the system "inherits" all delegations and roles assigned to the system user and can utilize these
by authenticating with Maskinporten using the system user RAR grant.
A key differentiator from the "org token" mechanism is that the system user can have roles similarly to a regular user.
A system user can be viewed as a virtual user owned by some customer/client organization.
App flow
TBD
Outbound authn/authz

Storage - user token + APIM subscription key

User token comes from IUserTokenProvider which in reality is either the AltinnStudioRuntime cookie or the auth header, so it needs the HTTP Context directly
APIM subscription key is used to disallow anything but GET depending on the subscription (to allow mutating operators only from apps running in app clusters)
Consists of ApplicationClient, InstanceClient, InstanceEventClient, ProcessClient, SignClient, TextClient, DataClient

Notifications - PlatformAccessToken
Altinn2MetadataApiClient - none
NetsClient - API key from configuration
Events - user token + PlatformAccessToken + APIM subscription key

Events subscription only uses APIM subscription key  + secret code (IEventsSecretCodeProvider)

Profile - user token + PlatformAccessToken + APIM subscription key
Maskinporten - Maskinporten token
Register - user token + PlatformAccessToken + APIM subscription key
Authentication - user token + APIM subscription key (used to refresh token)
Authorization - user token + APIM subscription key

Some operations use PEP and PDP directly through libraries

Azure
Key Vault - Entra client secret
PDF - user token (cluster local endpoint)

Conclusion
Work that needs to be done

Design an abstraction, something like IClientContext, that allows us to represent the authenticated state/context

Can represent users, orgs, systemusers and the app itself
How do we express outbound authn - when do we pass on the current context and when do we choose differently?
Formulate as ADR
Initial design in: https://github.com/Altinn/app-lib-dotnet/pull/880

Start using internal abstraction IClientContext where possible - which encapsulates the authenticated state

Not always possible - i.e. PEP APIs and our own public APIs
JwtTokenUtil
IUserTokenProvider
.User (match case, whole word)

Consider deprecating ClaimsPrincipalExtensions
Consider deprecating UserHelper
ClaimsPrincipal
Manually iterating claims, such as TelemetryEnrichingMiddleware

Consider creating shim/abstraction between us and public PEP APIs such as DecisionHelper

Review all usage of profile client, as system users don't have profiles
Get updated PlatformUser (part of InstanceEvent) that considers system users

Update GenerateProcessChangeEvent, InstanceEventExtensions

Frontend updates

Confirmation page
Receipt page
PDF
Authorization/user/profile/party related requests

Figure out if there is a migration path to use Maskinporten tokens directly (no exchange)

Closing as the main work is done, but will probably be extended and/or moved into docs somewhere


Running each strategy on a different sub-account

Add the ability to pass sub-account names from the strategy in order to trade them on separate sub-accounts.
This is primarily to make PnL calculations more manageable. Also provides isolation between strategies for better risk mitigation.

Nice- This means that each strategy will need adding to the model:
a) API-key (in ftx at least, these are sub account specific).
b) The name of the sub-account.
As we currently have only one strategy, this can be done now or later.

Would it be a bad idea to have API keys managed directly in the admin panel?


The TypeScript language service died 5 times right after it got started. The service will not be restarted.

Issue Type: Bug
Was just working on some JS when my intelliSense died. I restarted VS Code and it didn't last 2 minutes before dying again. Tried it on VS Code Insiders and it did the same thing.
I don't really know how to reproduce it since I was just doing normal JS things and using an node.js CLI tool
VS Code version: Code 1.60.0 (e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff, 2021-09-01T10:54:53.442Z)
OS version: Darwin x64 21.1.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-8100B CPU @ 3.60GHz (4 x 3600)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
13, 7, 5

Memory (System)
8.00GB (0.26GB free)

Process Argv
--crash-reporter-id f9a7647b-0469-4871-9faf-bf64b623704d

Screen Reader
no

VM
0%

macOS Version: 12.0 (Monterey) Beta (21A5506j)
VS Code Version: Version: 1.60.0 Commit: e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff Date: 2021-09-01T10:54:53.442Z (1 wk ago) Electron: 13.1.8 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Darwin x64 21.1.0
Extensions (84)

Extension
Author (truncated)
Version

better-comments
aar
2.1.0

html-snippets
abu
0.2.1

namespace
adr
1.1.2

Bookmarks
ale
13.2.1

project-manager
ale
12.4.0

copy-relative-path
ale
0.0.2

shaderlabvscodefree
aml
1.2.8

electron-snippets
ant
1.0.3

vscode-tailwindcss
bra
0.6.14

simple-react-snippets
bur
1.2.4

unity-code-snippets
cem
0.1.0

npm-intellisense
chr
1.4.0

bracket-pair-colorizer-2
Coe
0.2.1

dart-code
Dar
3.26.0

flutter
Dar
3.26.0

githistory
don
0.6.18

jquerysnippets
don
0.0.1

xml
Dot
2.5.1

gitlens
eam
11.6.0

vscode-html-css
ecm
1.10.2

EditorConfig
Edi
0.16.4

vscode-npm-script
eg2
0.3.22

eppz-code
epp
1.2.52

vsc-material-theme-icons
equ
2.2.0

prettier-vscode
esb
8.1.0

discode
eve
1.1.3

unity-dev-pack
fab
2.4.1

git-project-manager
fel
1.7.1

vscode-solution-explorer
fer
0.4.4

vscode-firefox-debug
fir
2.9.4

auto-close-tag
for
0.5.12

auto-rename-tag
for
0.1.8

unity-pack-vs-code
fra
0.0.4

auto-using
Fud
0.7.15

vscode-pull-request-github
Git
0.30.0

todo-tree
Gru
0.0.214

live-html-previewer
hdg
0.3.0

beautify
Hoo
1.5.0

minify
Hoo
0.4.3

applescript
idl
0.21.0

monkey-patch
ioc
0.1.15

sf-symbols
j-f
2.1.0

webpack
jer
2.2.0

vscode-csharp-snippets
jor
1.1.0

docomment
k--
0.1.20

vscode-codemetrics
kis
1.24.0

unity-code-snippets
kle
1.3.0

vscode-github
Kni
0.30.6

electron-debug
kod
18.11.1

unity-snippets-modified
lio
0.4.0

vscode-JS-CSS-HTML-formatter
lon
0.2.3

vscode-language-babel
mgm
0.0.35

fluent-icons
mig
0.0.12

vscode-nbt
Mis
0.6.2

vscode-filesize
mkx
3.1.0

prettify-json
moh
0.0.3

vscode-docker
ms-
1.16.1

csharp
ms-
1.23.15

python
ms-
2021.9.1230869389

vscode-pylance
ms-
2021.9.1

jupyter
ms-
2021.8.2041215044

jupyter-keymap
ms-
1.0.0

remote-containers
ms-
0.194.0

remote-ssh
ms-
0.65.7

remote-ssh-edit
ms-
0.65.7

remote-wsl
ms-
0.58.2

vscode-remote-extensionpack
ms-
0.21.0

azure-account
ms-
0.9.8

cpptools
ms-
1.6.0

vscode-typescript-next
ms-
4.5.20210913

vsliveshare
ms-
1.0.4836

vscode-react-native
msj
1.6.1

color-highlight
nau
2.5.0

vscode-streamdeck
nic
4.1.6

indent-rainbow
ode
8.0.0

minecraft-essentials-extension-pack
pah
1.0.1

vscode-versionlens
pfl
1.0.9

unity-toolbox
pix
1.0.6

material-icon-theme
PKi
4.10.0

material-product-icons
PKi
1.1.1

vscode-unitymeta
PTD
0.0.7

explorer-exclude-vscode-extension
Red
1.2.0

c-sharp-utilities
rev
0.3.2

LiveServer
rit
5.6.1

(5 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspyt653:30270858
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
pythonvspyt639:30300192
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805:30301674
pythonvspyt200:30340761
vscextlangct:30333562
binariesv615:30325510
vsccppwt:30364497
pythonvssor306:30344512
bridge0708:30335490
pygetstartedc2:30360494
bridge0723:30353136
pythonrunftest32:30365366
pythonf5test824:30361777
javagetstartedt:30364666
pythonvspyt187cf:30365362
pydsgsc2:30361791
vscus224cf:30358040
vssid140:30363603
vssur157:30365996

Log
[2021-09-13 18:45:14.341] [renderer1] [error] write EPIPE: Error: write EPIPE
    at afterWriteDispatched (internal/stream_base_commons.js:156:25)
    at writeGeneric (internal/stream_base_commons.js:147:3)
    at Socket._writeGeneric (net.js:785:11)
    at Socket._write (net.js:797:8)
    at writeOrBuffer (internal/streams/writable.js:358:12)
    at Socket.Writable.write (internal/streams/writable.js:303:10)
    at v.write (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:465297)
    at d.write (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:453678)
    at d.sendRequest (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:456093)
    at d.sendNextRequests (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:455874)
    at dispatchMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:454343)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:453377
    at c.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:66:1712)
    at m.onLengthData (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:464128)
    at Socket.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:463775)
    at Socket.emit (events.js:315:20)
    at Socket.EventEmitter.emit (domain.js:467:12)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)
[2021-09-13 18:48:26.718] [renderer1] [error] Could not create TS service. Service state:{"type":0}: Error: Could not create TS service. Service state:{"type":0}
    at w.service (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:492121)
    at w.executeImpl (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:500654)
    at w.executeAsync (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:500525)
    at new S (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:443896)
    at Function.executeGetErrRequest (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:444085)
    at b.sendPendingDiagnostics (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:448462)
    at t.Delayer.task (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:447802)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:507565
    [2021-09-13 18:54:53.526] [renderer1] [error] Could not create TS service. Service state:{"type":0}: Error: Could not create TS service. Service state:{"type":0}
    at w.service (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:492121)
    at w.executeImpl (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:500654)
    at w.execute (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:500184)
    at o.provideDocumentHighlights (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:363847)
    at w.provideDocumentHighlights (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:94:167276)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:94:192125
    at xe._withAdapter (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:94:187656)
    at xe.$provideDocumentHighlights (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:94:192103)
    at i._doInvokeHandler (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:13543)
    at i._invokeHandler (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:13227)
    at i._receiveRequest (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:11838)
    at i._receiveOneMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:10567)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:8663
    at c.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:66:1712)
    at l.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:15781)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:113:30187
    at c.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:66:1712)
    at l.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:15781)
    at r._receiveMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:21051)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:17929
    at c.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:66:1712)
    at v.acceptChunk (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:13142)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:12490
    at Socket.w (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:113:13350)
    at Socket.emit (events.js:315:20)
    at Socket.EventEmitter.emit (domain.js:467:12)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)
[2021-09-13 18:54:54.088] [renderer1] [error] Could not create TS service. Service state:{"type":0}: Error: Could not create TS service. Service state:{"type":0}
    at w.service (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:492121)
    at w.executeImpl (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:500654)
    at w.executeAsync (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:500525)
    at new S (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:443896)
    at Function.executeGetErrRequest (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:444085)
    at b.sendPendingDiagnostics (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:448462)
    at t.Delayer.task (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:447802)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:507565
[2021-09-13 18:54:55.227] [renderer1] [error] Could not create TS service. Service state:{"type":0}: Error: Could not create TS service. Service state:{"type":0}
    at w.service (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:492121)
    at w.executeImpl (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:500654)
    at w.execute (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:500184)
    at o.provideDocumentHighlights (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1:363847)
    at w.provideDocumentHighlights (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:94:167276)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:94:192125
    at xe._withAdapter (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:94:187656)
    at xe.$provideDocumentHighlights (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:94:192103)
    at i._doInvokeHandler (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:13543)
    at i._invokeHandler (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:13227)
    at i._receiveRequest (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:11838)
    at i._receiveOneMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:10567)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:98:8663
    at c.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:66:1712)
    at l.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:15781)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:113:30187
    at c.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:66:1712)
    at l.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:15781)
    at r._receiveMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:21051)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:17929
    at c.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:66:1712)
    at v.acceptChunk (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:13142)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:74:12490
    at Socket.w (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:113:13350)
    at Socket.emit (events.js:315:20)
    at Socket.EventEmitter.emit (domain.js:467:12)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)
    ```

Does this reproduce in the latest VS Code insiders build with all extensions disabled?
If so, please try collecting the TS Server log from the crashed instance:

Set "typescript.tsserver.log": "verbose"

Restart VS Code and reproduce the problem

Open the TypeScript section of the output panel

At the very top, find the first line that prints to path to the semantic error log file. It should look something like:
[Info  - 19:54:59.247] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20200213T104930/exthost55/vscode.typescript-language-features/tsserver-log-ZT2zau/tsserver.log

That file contains the typescript logs.

Look through that log file for the first error or stack trace you see. If you can share the log, I can also take a look to see if anything stands out

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

I've been running into something a little like this. Specifically when coding on https://github.com/elastic/kibana over a Remote-SSH connection.

I'll set "typescript.tsserver.log": "verbose" and see if anything interesting turns up.

One thing I noticed initially is that I seem to have two tsserver.js instances running:
[Info  - 06:00:02.86] Using tsserver from: /home/matschaffer/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/extensions/node_modules/typescript/lib/tsserver.js
[Info  - 06:00:02.88] <syntax> Log file: /home/matschaffer/.vscode-server/data/logs/20210915T055956/exthost1/vscode.typescript-language-features/tsserver-log-VXsl3n/tsserver.log
[Info  - 06:00:02.88] <syntax> Forking...
[Info  - 06:00:02.96] <syntax> Starting...
[Info  - 06:00:02.98] <semantic> Log file: /home/matschaffer/.vscode-server/data/logs/20210915T055956/exthost1/vscode.typescript-language-features/tsserver-log-hDNY3m/tsserver.log
[Info  - 06:00:02.98] <semantic> Forking...
[Info  - 06:00:02.105] <semantic> Starting...

$ ps wuax | grep lib/tsserver.js
matscha+   84950  0.9  0.1<PHONE_NUMBER>32 ?       Sl   06:00   0:02 /home/matschaffer/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/node --max-old-space-size=3072 /home/matschaffer/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/extensions/node_modules/typescript/lib/tsserver.js --serverMode partialSemantic --useInferredProjectPerProjectRoot --disableAutomaticTypingAcquisition --cancellationPipeName /tmp/vscode-typescript1001/7d449336a67e0f933dd1/tscancellation-3834cc85a5d59d2fcd6c.tmp* --logVerbosity verbose --logFile /home/matschaffer/.vscode-server/data/logs/20210915T055956/exthost1/vscode.typescript-language-features/tsserver-log-VXsl3n/tsserver.log --globalPlugins typescript-vscode-sh-plugin --pluginProbeLocations /home/matschaffer/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/extensions/typescript-language-features --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation
matscha+   84956 19.6  1.5 1586988 1049184 ?     Sl   06:00   0:45 /home/matschaffer/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/node --max-old-space-size=3072 /home/matschaffer/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/extensions/node_modules/typescript/lib/tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName /tmp/vscode-typescript1001/7d449336a67e0f933dd1/tscancellation-9f0ba43f70531ccc21d1.tmp* --logVerbosity verbose --logFile /home/matschaffer/.vscode-server/data/logs/20210915T055956/exthost1/vscode.typescript-language-features/tsserver-log-hDNY3m/tsserver.log --globalPlugins typescript-vscode-sh-plugin --pluginProbeLocations /home/matschaffer/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/extensions/typescript-language-features --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation

Is this expected?

@matschaffer Yes it is expected. If you are seeing crashes, please follow the steps to collect the logs and then open a new issue with them so we can investigate

Will do! I turned them on, restarted both vscode and killed the remote ssh server. Will post if/when I see it happen again with logs in hand this time. I don't think removing all extensions is feasible since I can't effectively use vscode for work without the extensions.

Hey @mjbvz it finally happened at the end of the day. I have the log but even zipped it's 4GB. Is there a microsoft upload server I could put them on for you?

It just happened to me, check if this isn't your issue: https://github.com/microsoft/vscode/issues/133515

Closing as we need logs/steps to reproduce from the original poster


wget failed to find libeay32.dll

Build.md needs to be updated with the solution to fix the issue with wget dependencies
https://github.com/AdoptOpenJDK/openjdk-systemtest/blob/master/openjdk.build/docs/build.md

@BhargaviMullapudi - As discussed please work on this issue

I don't see @BhargaviMullapudi as a member on GitHub?  If s/he can join then I'll add them to the team :-)

Fixed in https://github.com/AdoptOpenJDK/openjdk-systemtest/pull/39


RFC: selection rework

rendered

My knowledge of the editor is not as low level as you so I don't think I can have a relevant opinion about this, everything seems logical to me to be honest.
Just one remark, as far as I understand we don't support mixed selections so how selecting a chunk of text with a component would work? I cannot copy it for example to another document?

a text selection with a component in the middle would still contain that component
the definition of ranges doesn't change with this rfc.
In essence, a selection is just a range with some cool metadata, this just proposes another type of metadata


nixos/elastic-apm-server: init

Motivation for this change
I wanted to use elastic-apm-server together with a language-dependant agent.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

shas should be changed when https://github.com/NixOS/nixpkgs/pull/57992 gets merged.

Closing due to inactivity from author.


Question on util/transform_estimation.py est_quad_linear_robust()

Hi Chris,
Thank you for sharing the code!
I wonder which algorithm is using here for transformation estimation in the util/transform_estimation.py. Can you point out the reference?
Thanks!
Qiaojun

It's used in https://github.com/chrischoy/FCGF/blob/master/lib/trainer.py#L329.
Both transformation estimation and ContrastiveLossTrainer are kind of legacy code we do not use for training FCGFs.

Is the ContrastiveLossTrainer associated with the "Contrastive" mentioned in the Table 3 of the paper?
I see. I am just curious what algorithm it is using here transform_estimation.py. The build_linear_system(), and the solve_linear_system(). Do you still remember that?

Hi @FengQiaojun , I am reading FCGF's code recently. For me, this seems like an iterative re-weighted least square problem with Cauchy robust kernel and the parameter in the M-estimator is changed heuristically.
More specifically, we want to solve for $argmin_T \rho (Tx - y)$, where x is pts0 and y is pts1 as in the code and $\rho$ is Cauchy M-estimator (per Table1 in https://www.microsoft.com/en-us/research/wp-content/uploads/2016/11/RR-2676.pdf). In each Gauss-Newton iteration, the jacobian of $Tx-y$ (aka. variable A) is computed by parametrizing the rotation part of $T$ using Euler angle (ref. https://robotacademy.net.au/lesson/derivative-of-a-rotation-matrix/). In solve_linear_system() the normal equation $A^\top A x = A^\top b$ is solved to compute the delta transform, which will be eventually applied to the final estimated transformation.
However, I am still wondering why won't the authors simply pick a Kabsch algorithm. Will different choices of transformation fitting algorithm affect the registration recall metrics?

The method used in solve_linear_system is a simpler version of FGR. For the final registration recall, we use the original authors matlab code that uses RANSAC as I have explained in the evaluation section of the readme file.

Thank you so much for your clarification!


Populate the infobox when downloading videos from a playlist. 👾

Playlist download progress has been fixed, what remains is to populate the infobox with the information of a playlist which is being downloaded. 🚀

Can you tell me the location for infobox ?

Playlist download progress has been fixed, what remains is to populate the infobox with the information of a playlist which is being downloaded. rocket

Can you tell me the location for infobox ?


Add test to verify the extremely large min_rtt in adaptive concurrency

Signed-off-by: Junchao Lyu<EMAIL_ADDRESS>test the scenario for https://github.com/envoyproxy/envoy/issues/14997

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

It is tracked by https://github.com/envoyproxy/envoy/pull/15004


Issue #512: Test Automation Script for Control_Plane

Fixes #512
Description of the Solution
Ansible Script for Test Automation Script of control_plane
Suggested Reviewers
@lwilson @j0hnL

@all-contributors please add @nihalranjan-hpc for test, code


Migrations for new Guid property on Project, McPkg and CommPkg

Updatet constructor and test for Project

Add a testclass for the Project domain class in src/tests/Equinor.ProCoSys.IPO.Domain.Tests/AggregateModels/InvitationAggregate/ Use McPkgTests.cs as template, just Setup and Constructor_ShouldSetProperties() needed


created responsive version of website

Closes #1
🛠 Fixes Issue

Made the page mobile responsive.
Changed generator behaviour from flex to flex-wrap so that it will no longer be able to break the layout of page.
Moved menu design to only appear in case of mobile devices.
Change position behaviour from fixed to static (for mobile version only) to protect generator card from overlapping.

👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

Now website will maintain it's behaviour even if you add as many cards as you want.

In mobile version it will be displayed as one by one

did you also work on the modal responsiveness?
__
  Summary: :question: I have a question  |  Tags: Inefficient

You have set it to display none and it is not working. So, i leaved it as is it .
I currently don't have any idea how are you adding image processing feature to it (since it is written in typescript). Tell me something about it's  typescript part so that i could be able to fix it.

You have set it to display none and it is not working. So, i leaved it as is it .
I currently don't have any idea how are you adding image processing feature to it (since it is written in typescript). Tell me something about it's  typescript part so that i could be able to fix it.

just click on the card, and it opens a pop-up (also called a modal). I'm asking if that is mobile friendly


Compare source filter does not work

When making changes in local workspace, the compare source filter does not show the changes. Possibly related to https://github.com/IBM/vscode-ibmi-projectexplorer/issues/326
@edmundreinhardt @irfanshar

I suspect it is, let's release and test again

@william-xiang William, can you update Project Explorer to 2.6.2 so that Jonathan can test whether this issue is resolved

@jonnyz32  Can you please test this

Yep, this is working now. I'll close.


[Feat-757] Add eslint rule for const

@daniel-ilan Yes, I know, should I go over the variables and change them to const then?

Yes, I think


Fixed some minor translation problems

Clarified and fixed grammar of monster messages in English and fixed an inconsistent period.

OK, this should now be prepared for merge. Sorry for the last moment changes, noticed some things I'd missed on a fresh pass.

By the way, if you could clarify what boss attack  spoofing is, I could also give that a more appropriate translation.

I believe I ascertained what boss attack spoofing is and have provided a clearer translation for what I think it is with commit #24. If I understand correctly, it is forcing the monster in the company building to attack.

Alright, I have now reviewed absolutely all of the  text a few times and there should be nothing left out of place. Should be perfect.

OK, now it should be dusted and perfect.


feat：implement fence to ensure eventually consistency use datasource proxy mode

What would you like to be added:
通过数据源代理来实现防悬挂
Why is this needed:

@106umao


[core] Trim key field in reading, map it to value field

Purpose

The key-value storage (in primary-key table) are redundant.
Read key-value from storage may appear to fetch more fields than we need.
For example, the format of a row is:   _KEY_a, _KEY_b, _FIELD_SEQUENCE, _ROW_KIND, a, b, c, d, e, f, g
The column "a" and "b" have double read. A optimization is:

read before:    _KEY_a, _KEY_b, _FIELD_SEQUENCE, _ROW_KIND, a, b, c, d, e, f, g

read after:        a, b, _FIELD_SEQUENCE, _ROW_KIND, c, d, e, f, g

While reading, we find the a, b from value and fill them to key.

Tests

API and Format

Documentation

If these fields are not used when reading, can we store them when writing

If these fields are not used when reading, can we do not store them when writing

Correct, I am working on trimming them from writing.

+1


Add type-tests to ensure consistent public API expectations

While our tests are in typescript, we aren't type checking them (and there are errors 🙈 )
adding type-tests gets us usage coverage without actually running anything.

BUMP!
I want to fix #7 based on this PR (for writing tests)

ah! good thinkin!


equation in {{#include}} not rendered

Steps to reproduce:

src.md
## My equation
$$
E=mc^2
$$

ch1.md
# Chapter 1
{{#include src.md}}

SUMMARY.md
[original](./src.md)
[included](./ch1.md)

Any idea on how to solve this?
I have known this problem for a while. We had to work around it by not using #include.

Perhaps you should just rip a snapshot of the KaTeX code used to render the equations and put it among the output files, then insert into every page an #include referencing the local snapshot?

I don't think I understand what you are saying here. What is "a snapshot of the KaTeX code used to render the equations?"

A clientside fallback for "catching" edgecases that didn't get serverside-rendered by the preprocessor.
This is a horrible hack that the users might be okay with.

Speaking of which, what's wrong with mdbook-katex just ripping the css automatically anyways when the no-css flag is set?

What do you mean by "ripping the css?" Do you mean that we include the CSS in the binary and directly write it?

I don't think there are any license restrictions preventing you from just distributing the js and css snapshot in the output?

The problem about licenses would probably be on the fonts.

These should be for another issue.

I need to read the mdbook source code to see why #include is handled after external preprocessors. That would be the solution.

I found the solution:
[preprocessor.katex]
after = ["links"]

I will update the README.

@expikr, please validate whether this solution works.

works, thanks!

Great!

Is there any consideration preventing this from being made the default?

This is controlled by mdBook's behavior. By default, mdBook runs external preprocessors such as katex before its internal preprocessors such as links which handles #include. The after option can be used to specify the order.
Does that answer your concern?

Your proposal does not work to my knowledge, unfortunately. We can only have defaults if the option is for mdbook-katex, but in this case, the option is for mdBook.
Options are read by mdBook. mdBook then passes these options to preprocessors such as mdbook-katex, where mdbook-katex would read options such as block-delimiter, so we can have a default in mdbook-katex there.
after is an option handled by mdBook itself instead of mdbook-katex. mdBook uses after and before to decide the order it calls the preprocessors, which is beyond any preprocessors' control.
Is that clear?

Yes. Preprocessors can, in fact, only output book (content) not cfg (configuration) to mdBook.
mdBook has rather poor documentation on these topics, sadly. I had to read the mdBook source code to make some parts in mdbook-katex functioning.


JsonSerialize Exception because Result.Value is a throw

Hi, congratulations with lib, it's great. But a have a problem when try serialize my Result object.
My Scene:

I hope my exit is successful!
But, because "public bool IsFailed => Reasons.OfType().Any();", my 'Result.Value' is a throw, and Exception when a try serialize...

Thanks for your feedback.
My opinion to use third party classes at system boundaries:
I highly recommend that the Result class from FluentResults is only used internally in your application. This means that a custom result class as data transfer object is used at the system boundaries. With an custom Result class you can make the custom Result class and the api stable and your api is independend from fluentresults breaking changes. The logic to transform a fluentresults Result object to a custom Result object for your api should bei easy.
Then the dto is serialized and not the fluentresults object. Newtonsoft.Json or other serializer libs serialize all public properties. A fluentresults Result object has IsSuccess, IsFailed, Reasons, Successes, Errors properties and you definitly don't want that all properties are serialized (doublicate Data, ...).
Throwing an exception when you access Value and the result is a failed result is a safety net and works as designed. If the result contains an error then its an failed result and you should not call .Value. With the exception the developer see asap the wrong usage of the result pattern.
In your example you add in the last line an error with which you change the success result to a failed result. This behavoir is for me correct.
Is this helpful?

Perfect Michael, thank you.
I had a vision that 'Result.Ok()' was the success identifier, and the add-on.' WithFail()' not having the power of modification.
But with your explanation I understand that it takes a specific fit for my business.
Thank you so much for the explanation.


Add support for forcing update after executing command

Did you read the instructions?

[X] I have read the README, including the advanced debugging section.

The request
I have some blinds which has a special command setClosureAndOrientation. With this (using tahoma.execute_command) I can set the closure position and the tilt position in a single command. Setting the cover position with cover.set_cover_position and setting the tilt position with cover.set_cover_tilt_position immediately after that stops the moving cover and only the tile position set. So  setClosureAndOrientation is very usefull, no need to wait between the two commands. There is only one problem with this method: the state of cover entity is not updated immediatly after executing the setClosureAndOrientation. Using open cover, close cover, set cover position, etc. immediatly updates cover entity state. It should be good to add posibility to force update cover (tahoma) entity state after executing a custom command (maybe an optional parameter for execute_command service).
Which gateway / hub do you use?
Connexoon
Device model (optional)
No response
Device type (optional)
No response
Additional information
No response

Can you turn on debug logging and execute setClosureAndOrientation?
By the way, we didn't port this functionality to the core integration. Would this be a blocker for you to migrate?

Hi @iMicknl, logging turned on, log attached: home-assistant.log
If there will be a non core tahoma integration which has this functionality I would use that. It is very annoying that you have to wait for the cover to move into position before you can set the tilt position. Also very hard (need a lot of extra code to do it right) to write scripts/automations for that. As I mentioned you have to use delay between setting cover and tilt position. If you use short delays then the moving of tilt stops the moving of cover and the cover won't be in expected position. If you using long delays than you have to wait a lot for setting position. For example I have a blind which opens/closes in 61 seconds so I have to use 61 seconds delay in my automation to be sure it is moving to the expected position. If the cover is in correct position only the tilt should be rotated and don't need to wait for 61 seconds. It is a very bad user experience that you press a button on the dashboard which executes a script to set the cover and tilt position and nothing happens for 61 seconds. I know I could calculate the difference between the current position and the expected position and then calculate the delay time based on that but why should I do that if there is a setClosureAndOrientation command?
To be honest I don't know why there isn't a set_cover_and_tilt_position for base cover entity itself in the core to implement this functionality.

To be honest I don't know why there isn't a set_cover_and_tilt_position for base cover entity itself in the core to implement this functionality.

This would indeed be a blocker for us to implement this... However, this is a good example why the execute_command service is important.
I didn't have time to review your log yet, but I wonder why there are no real-time updates after your execute that specific command...

The set_cover_and_tilt_position could be optional (maybe with an addtional SUPPORTED_FEATURES flag) in that case won't be a blocker for you :)
Is there a plan to move execute_command service to core?


Commands do not work in single question mode

Testing #188542
Looks like they are not supported:

slash commands do work:

they just don't have any cool rendering/completions experience because it's using the quickinput box not the chat input box.
This needs https://github.com/microsoft/vscode/issues/35785 but likely the inputOnTop is just a better way to go as it has more features for free and is similar to this mode.

This mode no longer exists.


Immutable Str error

Problem or new feature
"Cannot modify an immutable Str (-)"
Not documented
Suggestions
Should be able to find this error message in the docs with a suggestion about how to address it.

Could you provide an example?
It seems to me that the error message corresponds to X::Assignment::RO which is documented - however, the type graph of it is a big fat 404.


The list of rankings is not current.

Websocket list of rankings is not current.
The problem could be the shared Socket updater in the PublicSock.ts file.

-> Bug never occured again after a reboot of the damaged container.


Building the project from source

Jetson Nano developer kit Specs:
Jetson Nano 4GB kit with 16GB Memory card.
L4T version 32.6.1 [JetPack 4.6]
Ubuntu 18.04.5
Errors:

I'm getting errors in the command "cmake ../"

In the step installpytorch.sh I'm getting Pytorch for Python 3.6 as shown in the screenshot below.

I tried to install pytorch for python 3.6 but it didn't complete because of memory issues.

Make commands also showed errors.

Please suggest some solution.
Thank you.

Hi Mohit, can you try running cmake again?  It should skip the dialogs this time

Hi Dustin,
I'm getting the same errors after running the cmake command.

From: mohitg0292 @.>
Sent: Saturday, December 3, 2022 7:54:59 PM
To: dusty-nv/jetson-inference @.>
Cc: Dustin Franklin @.>; Comment @.>
Subject: Re: [dusty-nv/jetson-inference] Building the project from source (Issue #1528)
Hi Dustin,
I'm getting the same errors after running the cmake command.
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-inference%2Fissues%2F1528%23issuecomment-1336290051&data=05|01|dustinf%40nvidia.com|470bcf74f1884ecf6bac08dad5922b82|43083d15727340c1b7db39efd9ccc17a|0|0|638057121157428176|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=k0DFqF27IY5W9BQLxT4NcgNKicc5AzgKNtym3LDxZTU%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGK4PKG4VYAMGCWPXZO3WLPTWHANCNFSM6AAAAAASS265RI&data=05|01|dustinf%40nvidia.com|470bcf74f1884ecf6bac08dad5922b82|43083d15727340c1b7db39efd9ccc17a|0|0|638057121157428176|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=9G8s8OKKmPw855L5%2FljI1Puc%2BK4cyrXy4dyzVcFYDCM%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>

Yes I ran the the command "cmake ../" from build directory. But it completed with errors which I put screenshot above.

OK, I see.  It appears that you do not have CUDA toolkit installed on your Jetson.  Did you use the SD card image or SDK Manager to flash it?
I believe you should able to do 'sudo apt-get install cuda-toolkit-*'

From: Dustin Franklin @.>
Sent: Saturday, December 3, 2022 7:57:59 PM
To: dusty-nv/jetson-inference @.>; dusty-nv/jetson-inference @.>
Cc: Comment @.>
Subject: Re: [dusty-nv/jetson-inference] Building the project from source (Issue #1528)
Did you run cmake ../ from the build directory and did it complete successfully?

From: mohitg0292 @.>
Sent: Saturday, December 3, 2022 7:54:59 PM
To: dusty-nv/jetson-inference @.>
Cc: Dustin Franklin @.>; Comment @.>
Subject: Re: [dusty-nv/jetson-inference] Building the project from source (Issue #1528)
Hi Dustin,
I'm getting the same errors after running the cmake command.
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-inference%2Fissues%2F1528%23issuecomment-1336290051&data=05|01|dustinf%40nvidia.com|470bcf74f1884ecf6bac08dad5922b82|43083d15727340c1b7db39efd9ccc17a|0|0|638057121157428176|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=k0DFqF27IY5W9BQLxT4NcgNKicc5AzgKNtym3LDxZTU%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGK4PKG4VYAMGCWPXZO3WLPTWHANCNFSM6AAAAAASS265RI&data=05|01|dustinf%40nvidia.com|470bcf74f1884ecf6bac08dad5922b82|43083d15727340c1b7db39efd9ccc17a|0|0|638057121157428176|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=9G8s8OKKmPw855L5%2FljI1Puc%2BK4cyrXy4dyzVcFYDCM%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>

I have just run the command and it's still running. I'm not sure how the image is loaded into SD card. Could you please share if there's a way to check if the Jetson Developer Kit image is loaded into the memory card?
Also is 16GB SD card enough?

16GB is small yes, so I would get a bigger one eventually

From: mohitg0292 @.>
Sent: Saturday, December 3, 2022 8:35:32 PM
To: dusty-nv/jetson-inference @.>
Cc: Dustin Franklin @.>; Comment @.>
Subject: Re: [dusty-nv/jetson-inference] Building the project from source (Issue #1528)
I have just run the command and it's still running. I'm not sure how the image is loaded into SD card. Could you please share if there's a way to check if the Jetson Developer Kit image is loaded into the memory card?
Also is 16GB SD card enough?
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdusty-nv%2Fjetson-inference%2Fissues%2F1528%23issuecomment-1336296565&data=05|01|dustinf%40nvidia.com|2a07a1b4773a49cf024208dad597d5a0|43083d15727340c1b7db39efd9ccc17a|0|0|638057145354470723|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=tkITug2WOdkCHhuR8xJSmzDZA8Ot3fhIlnkPOzFT9XE%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEGKYOHVCQCZH3GEKLTL3WLPYOJANCNFSM6AAAAAASS265RI&data=05|01|dustinf%40nvidia.com|2a07a1b4773a49cf024208dad597d5a0|43083d15727340c1b7db39efd9ccc17a|0|0|638057145354470723|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2FVI3LB8Yy4VWC%2FLsunbaicb4eYRqoxq8HlErD0nJr70%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>

The command you mentioned got incompleted because of space issues.

I would also increase the memory size as you suggested.

Hi!
So I just realized that the Ubuntu OS is installed in internal memory which is around 15GB. I'm not able to use SD card, it's not showing even with "df -Th" command. Not sure why.
Do you think this project can only be run in SD card? Because the internal memory got full by trying different methods to fix the errors and now even after removing the project, the memory is still full.
Mohit

I'm not able to use SD card, it's not showing even with "df -Th" command. Not sure why.

Hi @mohitg0292, I would try using the ubuntu GUI disk tool and make sure your SD card is formatted as ext3/ext4 and is setup to auto-mount.

Do you think this project can only be run in SD card? Because the internal memory got full by trying different methods to fix the errors and now even after removing the project, the memory is still full.

I've run it before in 16GB + JetPack, but yes JetPack already takes up a lot of space.

@mohitg0292 You can this guide from Nvidia on how to minimizing Jetson disk usage. Hope this helps.


Add develop branch to the Action trigger "pull_request"

Currently , we test only main branch on the pull_request trigger.
https://github.com/suikan4github/template_library/blob/4f2ad7c31142a970baa36e5eef9220eddb068208/.github/workflows/ctest.yml#L10-L11
Change it to test to the pull request on the develop.
pull_request:
   branches: [ main, develop ]

Merged to develop


Use Jade and Sass

Using these tools would allow us to compact our html and css code. This is an opinionated matter so I will leave this decision up to you.

Currently we do not use much HTML and CSS so this is almost useless. We will consider this when we move to Angular with many templates.


Update performance issue title

This will change the title. I will change the summary of the issue in the templates next. These are in the aspnet/benchmarks repository where the configuration for our scenarios is kept.


Panic on 403 response

Hi! Thank you for writing this; it's been both faster and pleasantly more stable than s3fs in my testing for my use case. One issue I've run into with goofys is that sometimes, while processing a 403 response, it panics for reasons that are not clear to me. I am using goofys with Digital Ocean Spaces, their new S3-compatible storage product, so it's possible it has a bug or is behaving in some weird way that goofys hasn't seen before because real S3 doesn't do it.
In any case though, it should probably handle the error gracefully and not panic :) and I figured you might be interested to see the logs / traceback so you can fix it if you like.
I've uploaded a debug log (with just --debug_s3) and the traceback in a gist. Let me know if any more info would be helpful!

how would I reproduce this? Do you know why it's returning 403 during UploadPart? (instead of CreateMultipartUpload)

Unfortunately I can't even reproduce it reliably :/ It happens when running youtube-dl against goofys. Feel free to close! Definitely not expecting a fix, just figured you might want to know. The 403 thing is very weird—it's possible its a Digital Ocean bug.

please reopen if it happens again


Y database

Hi,
I am trying to create the Y-database, but I have not been able to do so.
From the README in the Y-str-prep folder:

What should be in the < input motif repeats > file?
Do I use v5 for single repeats and v4 for batch lists of repeats?

Autosomal worked great :)
Best,
Martin

Hi Martin
Thanks for choosing the STRspy.
Answer to your question: you dont need to prepare Y-STR, the package will be updated soon with STR-Y database same as autosomal. But if you need immediate, do let me know, will try to send it to you.
Thanks
Rupesh

Hi again,
would it be possible for you to send me the Y-STR database?
Thanks for your time,
Martin

Hi @unique379r and @martinhaagmans, just wanted to ask if the Y-STR database is currently available?
Thanks,
M

@malmarri
It will be available soon with new publication. Along with improved and some new features of STRspy.

Hi @unique379r and @martinhaagmans, just wanted to ask if the Y-STR database is currently available?
Thanks, M

Not to me.

Hello,
Any updates on the Y-STR database?
It is still not available.


Adds Workflow Update to Samples

What was changed

Adds the Workflow Update to the sample's repo.
Why?

Because users will want to see how to use the new Update feature with Python.
Gracefully shut down the worker too.
Checklist

Closes

How was this tested:

You need the Temporal Python 1.4 or above.
Only works on the local dev server with the config setup.

Any docs updates needed?

Once this gets approved - I'll add something similar to the docs (and incorporate any additional feedback).

Looks like you may need to do a poe format. Also, hello/hello_update.py may be a better name than hello/hello_workflow_update.py to match signals, but this is fine too.


Why are they called "recommend" instead of "recommended"?

It seems in the case of the core set, "core" is being used as an adjective, implying it's the "core set of rules".
This makes the recommend set stand out to me as strange and a little awkward to say, as it is a verb rather than an adjective or even a noun. I would expect to say "the recommended set of rules" rather than "the recommend set of rules".
I'm assuming there was internal discussion around this decision, but was hoping to better understand.

I am in favor of the rename (I don’t have sufficient rights in this repository to check my name in the list above, though).

I don’t have sufficient rights in this repository to check my name in the list above, though

@kevmoo: can we fix that?

What am I doing?

What am I doing?

Adding @goderbauer to the dart-lang org? 🙏   (Will follow-up separately...)


Start Menu isn't working.

After using this script, I get an eror message, that my Start Menu isn't working, and even after restarting it won't work anymore

@payday2123
Please provide the following information:

Operating System version. Ex 1909, 20H2, 21H1, etc.
Confirm your computer meets the requirements listed in the readme
Screenshot/record the issue and post or a link to it here.

By any chance are you using a 3rd party start menu like StartMenu8, Classic Shell, or Start10?
We've tested the script quite a bit on different configurations. As far as messing with the start menu the script doesn't actually make many changes. It used to reset all pins on the start menu but no longer does that.
Currently all the script does with regards to the start menu is:

Block automatic app installations
Disables Bing in Windows Search
Disables Cloud Syncing of your Start Menu Layout
Disables Start Menu Suggestions
Disables Tracking of App Starts
Remove OneDrive Start Menu Entry

Nothing there really affects the start menu. I'm not lead to believe that it's the script that is the issue here.
Have you run any other scripts or made any changes yourself recently?

Since this issue was not able to be recreated in a lab and the submitter @payday2123  failed to submit additional details as requested, we are closing this issue.


Allow only explicit use of configuration

Description
As I see it there are two aspects of the config that make it harder to understand than we would like:

Things are dynamically added to the configuration.
The config it used to template certain configuration file in a way that is invisible to users.

These two factors make it hard to accomplish the next major feature of attaching the questions to the tasks. We need a way of cleaning saying this question belongs to these tasks. We don't want to have questions where it is not clear which tasks are using that part of the config. The first step to doing this is to remove the ability to add things to the config, which has a number of knock-on effects. The second is to force the creation of a specific dictionary that is used in templating other files, with each task that uses that feature being forced to reference the configuration and copy the variable to the templating dictionary.
In doing this I created two new classes, one for obtaining data assimilation window variable and another for templating JEDI config files. These are variables of the base class with delegation methods added to the base class. I cleaned up the base directory of the tasks leaving only the actual base classes.
This work will enable the next step of moving all the questions from the suites part of the code to the tasks part of the code.
Sorry for the large number of changes. I opted to unify the date in the headers of the files such that they don't change in the future.

@jardizzo can you trigger the nightly for this?


switch to use ic-wasm

Wait for https://github.com/dfinity/ic-wasm/pull/12 and https://github.com/dfinity/candid/pull/358 to be merged

It should work now that https://github.com/dfinity/ic-wasm/pull/12 is merged. I was referring to a local build path previously.


[AutoDiff upstream] Upstream @derivative attribute type-checking.

The @derivative attribute registers a function as a derivative of another
function-like declaration: a func, init, subscript, or var computed
property declaration.
The @derivative attribute also has an optional wrt: clause specifying the
parameters that are differentiated "with respect to", i.e. the differentiation
parameters. The differentiation parameters must conform to the Differentiable
protocol.
If the wrt: clause is unspecified, the differentiation parameters are inferred
to be all parameters that conform to Differentiable.
@derivative attribute type-checking verifies that the type of the derivative
function declaration is consistent with the type of the referenced original
declaration and the differentiation parameters.
Resolves TF-829.

Examples:
func sin(_ x: Float) -> Float { ... }

@derivative(of: sin)
func derivativeSin(_ x: Float) -> (value: Float, differential: (Float) -> Float) {
    (sin(x), { dx in dx * cos(x) })
}

public protocol ElementaryFunctions {
    static func log(_ x: Self) -> Self
    ...
}

public extension ElementaryFunctions
where Self: Differentiable & FloatingPoint, Self == Self.TangentVector {
    @inlinable
    @derivative(of: log)
    static func derivativeLog(_ x: Self) -> (value: Self, differential: (Self) -> Self) {
        (log(x), { dx in (1 / x) * dx })
    }
}

The differentiable programming manifesto has more information and examples.

Note: this code is upstreamed from tensorflow branch. Some functions are intentionally not static (fileprivate) because they have users in other files on tensorflow branch.
Known issues are referenced in comments:

TF-874: Simplify type calculation helpers.
TF-1042: Remove DerivativeAttrs cache from ASTContext.

We would like to upstream code and continue development on master, if that's acceptable!
cc @rxwei @marcrasi @bgogul

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 9e09105b81d903fbd295276318f12a5b6bb2e063

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 9e09105b81d903fbd295276318f12a5b6bb2e063

Build failed
Swift Test Linux Platform
Git Sha - 9e09105b81d903fbd295276318f12a5b6bb2e063

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 2a63ab75deda7746d89015f616443793cdc1aa13

Build failed
Swift Test OS X Platform
Git Sha - 2a63ab75deda7746d89015f616443793cdc1aa13

@swift-ci Please test macOS

Merging to unblock progress on upstreaming AutoDiff. Happy to address additional feedback later!

This broke the VS2019 build:
https://compnerd.visualstudio.com/windows-swift/_build/results?buildId=18893&view=logs&j=b9e62f99-1a98-5ed7-01d2-f4794231ed79&t=9d1c7fdf-e7ea-5e83-bbfd-5e0708569c31&l=3865


Instance detail monitoring

Closes #
Update import file name
Changelog
New

{{new thing}}

Changed
changing the import from InstanceMonitoringCard to InstanceMonitoring
Removed

{{removed thing}}

Thank you for your quick fix @chrsfshr! Could you rebase your change to latest master? Thanks alot!

:tada: This PR is included in version 2.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Top and Bottom Lable on a Graph Item.

What problem does this feature solve?
You should be able to add Top and Bottom Label to a graph item, or is there already an existing option besides making 2 items.
What does the proposed API look like?

Hello?

This would be a great feature!
series.label = array of label objects, so you can position each individually & have formatter for each.
I have a chart which uses graphics.text for top & bottom "labels", but absolute positioning is a nightmare with horizontal stacked bar graph and variable length data set (especially at smaller sets!).

yeah i have done it with 2 circles


ruby head [x86_64-darwin17] - OpenSSL versions

ruby 2.6.0dev (2018-10-16 trunk 65090) [x86_64-darwin17] is being built with OpenSSL 1.1.1, but it is running with 1.1.0h.  See:
https://travis-ci.org/MSP-Greg/travis-ruby/jobs/442399213#L388-L401

Probably due to the differences between the macOS image that builds the archive and the one which uses it. Is this actually causing a problem?

@BanzaiMan
Yes, that would be the cause.  As to causing a problem, I haven't tried to look for one.  I'm also a windows type, so I can't test locally.  A few thoughts:

Has it been tested with the test-all & test-spec openssl, net, & open-uri tests?
Are all the Ruby openssl constants determined at runtime?  1.1.1 has TLSv1.3, 1.1.0 does not.  1.1.1 may also have more older API's removed.
A few gems (EventMachine & Puma) build with the OpenSSL package.  I did the PR that added some MacOS versions to the Puma Travis matrix, but I didn't include trunk.  There are issues there with trunk in general.  EventMachine does not test any MacOS versions.
I'm not really a c type, so I'm not sure what issues are involved.  There is a difference between forward & backward compatibility...

For the most part, I just wanted to point it out.  Ok to close.
Thanks, Greg

@BanzaiMan
Just noticed that ruby 2.6.0dev (2018-11-05 trunk 65547) [x86_64-darwin17] showing 1.1.0h for both.
Thanks, Greg


stylesheet wont change background  atom 1.34.0

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
when changing the editor background in the stylesheet it doesnt change, but when you do the exact same in the inspector (in the same element) it works...
Steps to Reproduce
this wallpaper will be on any macOS NEWER than el capitan. if you run linux, change the wallpaper to something diffrent.

open the user stylesheet
paste this in the otherwise stock stylesheet:.flexbox-repaint-hack  {
background:  url("/Library/Destop Pictures/Sierra.jpg");
}
presss cmd + s
4 see nothing happen
5 open the inspector, and go to .flexbox.repaint-hack
6 get the part where you added the flexbox paint (will only contain background url)
7 copy and paste the background property and value
8 inherit/disable the copied background property
9 paste the copied property, and tadaaa! it works...

Expected behavior: [What you expect to happen]
change the wallpaper
Actual behavior: [What actually happens]
nothing
Reproduces how often: [What percentage of the time does it reproduce?]
100% of the time
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
1.34.0
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.
i tested this with an clean install

Thanks for reaching out - not sure why that's happening but this seems like a better question for the official message board or the Atom Slack:

https://discuss.atom.io
http://atom-slack.herokuapp.com/

On Discuss and in the Atom Slack team, there are a bunch of helpful community members that should be willing to point you in the right direction.
I searched around and also found that there's a community package that lets you set the background image:
https://atom.io/packages/editor-background
And I gave it a quick try and it seems to work.


Status?

Just curious on the status of this, it seems like it stalled over a year ago...

It reached stage 4 and is part of ES2018.

The proposal has been merged into ECMA262 since https://github.com/tc39/ecma262/commit/b564aa94785aa5651342b02980380bf06ab44d59

@tracker1 The publication edition can be found at https://github.com/tc39/proposals/blob/master/finished-proposals.md.


Big performance regression between 0.31 and 0.32

Calling the Metadata_metadata runtime function of the latest Westend runtime with wasmi 0.31 takes around 750ms.
Calling the same runtime function with wasmi 0.32 takes around 4.5 seconds in CompilationMode::Eager. With CompilationMode::Lazy, it's around 5 to 7 seconds.

Take this with a grain of salt, but I wouldn't be surprised if this was the "runtime inefficiencies" in the "rare case" that you mention in https://github.com/paritytech/wasmi/pull/860
The way Metadata_metadata is implemented in Rust is that there's a trait implementation on tons of structs of the runtime code, and Metadata_metadata calls a function on this trait implementation of every single struct.
For this reason, I suspect that Metadata_metadata calls tons of small functions that are spread out everywhere within the Wasm.

@tomaka Thanks for reporting!
Calling many very small functions is the worst case situation for the Wasmi (register) implementation. Wasmi (stack) actually performs better for many small function calls. Aggressive inlining could maybe help if this indeed is the problem so it is worth a try if possible. The linked relaxed br+cmp encoding shouldn't play a big role here since it isn't used for calls. It would be great if you could get the Wasm input into a minimize example that has similar performance behaviors but I suppose this is going to be very tricky to extract.

@tomaka The exact Wasm blob that was used and ideally a trace of executed instructions might be helpful if you have them.

runtime.hex.txt
Here's the runtime.

I just noticed that the given westend.wasm binary was apparently not properly optimized using wasm-opt. I was under the assumption that Polkadot runtimes are always optimized with this tool since it really improves performance and especially binary size quite a bit.
5.9M Jan 31 13:18 westend.opt.wasm
7.5M Jan 31 13:14 westend.wasm

It could be worth a try to see if this westend.opt.wasm does not have this performance issue with Wasmi. The reason for this is that Wasmi relies on proper optimizations to run at full speed since (unlike for example Wasmtime) it cannot do its own proper optimizations due to its linear time compilation promise.

While inspecting the westend.wat file I saw this:
(func $memcpy (;8628;) (type 5) (param i32 i32 i32) (result i32)
  local.get 0
  local.get 1
  local.get 2
  call $_ZN17compiler_builtins3mem6memcpy17h7c9cbc967e51fdc6E
)
(func $memset (;8629;) (type 5) (param i32 i32 i32) (result i32)
  local.get 0
  local.get 1
  local.get 2
  call $_ZN17compiler_builtins3mem6memset17h7a0db38d43a2ca78E
)

Which indicates to me that the Westend runtime is compiled without the Wasm bulk-memory proposal although it has been evaluated in the past that this may yield serious performance improvements: https://github.com/paritytech/polkadot-sdk/issues/36
Especially for Wasmi being an interpreter the speed-ups gained could be even way more massive since the built-in memcpy and memset instructions in bulk-memory are not themselves interpreted but run natively via Wasmi. So we should test if enabling bulk-memory Wasm proposal fixes the performance issues reported in this issue.
cc @tomaka

After a relatively long investigation and a lot of DMs, this turned out to be caused by debug-assertions = true in the Cargo.toml.
Disabling debug assertions is critical in order to get decent performances.


Create 404 Page

Right now we redirect to the landing, should we create a 404 page instead. @Morrisai @miguelmoraleda ?

It could be a question when creating the project, if a not found page is desired.


Provide option to disable drag and drop in Editor

Sometimes users could drop a file in the editor unintentionally. Could we have an option to disable drag-and-drop in the editor, in parity with File Explorer (e.g., there is an option to disable drag-and-drop for file explorer)?

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

Just to elaborate on a specific scenario, we see students frequently drag a file from their Downloads folder to a codespace's Editor, not realizing the file hasn't actually been uploaded to their codespace, and not realizing any changes they make are actually saved locally, as @bpasero noted in https://github.com/microsoft/vscode/issues/175267#issuecomment-1442854532.
When students then return to their codespace after some time, they often wonder what happened to the file, as they don't see it in their codespace's Explorer, at which point they might have deleted it from their Downloads folder, too.
Using the HTML local file system API is surely a handy feature for some users, but for first-year students using Codespaces, we'd ideally disable to avoid the confusion. Thanks!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I keep dragging bits of the UI everywhere when trying to change from file explorer to source control view. Would love to turn that off!

Would love that one too. It is too sensitive and often you do something you dont want to do (same thing in the explorer)


migrations generated are empty

when I run this command:
dotnet ef migrations add MaxLengthOnNames
it generates an empty migration (Up and Down functions are exist but nothing inside them)
should I write the migration code for creating the tables? or it will be automatically generated?

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

ID: 912ebaa6-721f-c8b3-7b3a-7f16d4c24360
Version Independent ID: b6135ff6-897f-c5fa-c61d-d9fad4ee9acd
Content: Tutorial: Create a complex data model - ASP.NET MVC with EF Core
Content Source: aspnetcore/data/ef-mvc/complex-data-model.md
Product: aspnet-core
Technology: aspnetcore-data
GitHub Login: @tdykstra
Microsoft Alias: riande

I don't see anything in the model changes that would change the schema. Keep working, we'll look at this on the next doc sweep. cc @tdykstra

If you're using SQLite, there won't be any changes,

I found the problem, I did not add the DbSet inside the Context Class, that's why the tool did not recognize the change

Had a problem like that. Decided to look at the completed version of the project which helped. I accidently declared an extra new IWebHost  that didn’t have an name of “host”.
And because the using statement in the Main() method of my program file was expecting "host" it skipped the using statement that allowed the database to be seeded. Deleted that line.


negative and postive regulation required for GO:1905634

GO:1905634 | regulation of protein localization to chromatin
tks

reference ?

I didn't think we needed another since we have the regulation term already ;)  but I'm curating
PMID:29899453
Title | A Cdk9-PP1 switch regulates the elongation-termination transition of RNA polymerase II.
Authors | Parua PK, Booth GT, Sansó M, Benjamin B, Tanny JC, Lis JT, Fisher RP

@ValWood - If by this:

I didn't think we needed another since we have the regulation term already ;) but I'm curating

you meant you didn't think you need to specify the reference because it was already on the regulation term, please ALWAYS specify the reference so that the editor who works on your ticket doesn't have to guess what is appropriate. It makes it easier & faster for us to do your ticket. If Pascale hadn't already asked for the reference, I wouldn't have done this ticket today.


Allow cast to get function sig from local ABI

Component
Cast
Describe the feature you would like
I have a contract where I hid some functions from the public interface for brevity, but I do have defined in a separate interface (that is not inherited by the contract).
I see that cast can get the fn sig from etherscan (which is very cool), but for my use case it'd be really powerful to also scan local ABI in out/ or specify e.g. --abi IHiddenInterface to derive the fn sig locally. This would be really helpful for complex struct params that are not so easy to type out.
Additional context
No response

Isn't this already possible under forge inspect methodIdentifiers?

ah thank you, yes methodIdentifiers works great didn't know about that one. is there a way to get the return values it expects too though, for formatting the response properly?

Can you expand on what you're trying to do? The return values are part of the ABI which can be found in the artifact or with forge inspect IHiddenInterface abi

@mds1 yes for sure, primarily I am trying to call a getter that returns a complex struct:
➜  seadrop git:(v2) ✗ cast call 0x232e97b08266510de8f43f179fd0efbfe2910975 "getPublicDrop(uint256)(uint80,uint80,uint40,uint40,bool,address,uint24,uint24,uint16,uint16,uint16)" 0 --rpc-url $MAINNET_RPC_URL
115000000000000000
115000000000000000
1688065200
1688670000
true
0x0000000000000000000000000000000000000000
1
20
10000
10000
500

I haven't found an easy way to get the formatted return value for the (uint80,uint80,uint40,uint40,bool,address,uint24,uint24,uint16,uint16,uint16) part, or something cool like:
cast call 0x232e97b08266510de8f43f179fd0efbfe2910975 $(forge inspect IERC1155SeaDrop methodIdentifiers getPublicDrop) 0 --rpc-url $MAINNET_RPC_URL
where the methodIdentifier would also contain the return values. Maybe something like this exists you can point me to? Regardless not a huge priority, moreso a unique challenge since my public interface on etherscan isn't exhaustive of everything it supports.

this was a narrow need of mine for a certain type of contracts i was developing, closing since it probably isn't needed for most others and not worth prioritizing. thanks for always listening!


Error: incorrect header check

What Happened?
Hello, when I integrated bailian embeddings, the mail carrier tool returned "Error: incorrect header check". I set Content-Encoding: gzip, Accept-Encoding: gzip, but it still reported an error. What is the reason for this?
What Should Have Happened?
No response
Relevant Code Snippet
No response
Your Twitter/LinkedIn
No response

Hi @wyn20140226 can you please share the failing code snippet here or on Discord? (I'm on vru.shank) - can take a look and suggest!

Hi @wyn20140226 checking in!