proposal: cmd/compile: go:readonly comment directive for body-less functions

Proposal Details
Add go:readonly comment directive for body-less functions indicating the following arguments and any pointers exclusively accessed through a readonly argument wont be modified:
// writeBlocks will update vector (read-hash-write) and read extra and bytes.
//
//go:nescape
//go:readonly extra, bytes
func writeBlocks(vector *[4]uint64, extra *[32]byte, bytes []byte)

The point of this is to hook up with 925d2fb36c8e4c9c0e6e240a1621db36c34e5d31 this would allow []byte(str) conversions to be elided when the byte string is passed as a readonly argument to an assembly optimized subroutine.
github.com/cespare/xxhash implements Sum64String(string) uint64 and (*Digest).WriteString(string) using unsafe which allows to skip the allocation either by using (*strings.Reader).WriteTo or io.WriteString.
Other hashing libraries such as crypto do not implement this optimization, this could allow to implement this using compiler optimizations rather than duplicating APIs for []byte and string. (*note: this assume you are using a devirtualized hash.Hash or a concrete hasher implementation, which is now possible and not unrealistic, particularly for h := sha256.New(); h.Write([]byte(str)) patterns)
In the future this could improve register allocation in some rare edge cases so I don't expect this to be implemented.
Other stronger compilers like GCC and LLVM might already implement such logic in their register allocators, then work in gofrontend could be much easier (as I assume this would amount to setting up metadata flags on the function call nodes passed to gcc or llvm) so who knows.

The body-less function is allowed to read from memory, which is arguably a side effect when using -race altho I don't think very many body-less functions implement any kind of race tracking.

For slices the body-less function would assume to not be allowed to write past capacity.
If some memory is accessible through an unknown and a readonly pointer the function is allowed to write to it:
//go:readonly b
func doSomething(a, b []byte)

func f() {
 var x [64]byte
 doSomething(x[:32:32], x[:])
}

Here the compiler would be allowed to assume only the last 32 bytes of the x array are readonly (I except compilers to not implement this or to assume x maybe completely overwritten).

If a pointer to a pointer is readonly then both memory are readonly:
type s struct{
 v *int
}

//go:readonly a
func doSomething(a *s)

func f() {
 var x int // here the compiler is allowed to assume `x` will never be modified by `doSomething`
 doSomething(&S{&x})
}

Note: this apply transitively to any amount of level.

Combining the two edge cases above, if a pointer to a pointer is accessible both through unknown and readonly paths, the body-less function may modify it:
type s struct{
 v *int
}

//go:readonly b
func doSomething(a, b *s)

func f() {
 var x int // x maybe modified through a
 doSomething(&S{&x}, &S{&x})
}

The body-less function is assumed to maybe write to anything part of the global scope:
var x int

//go:readonly a
func doSomething(a *int)

func f() {
 doSomething(&x) // doSomething is allowed to modify x
}

AFAIK go directives are not part of the language spec (https://go.dev/ref/spec), it is an internal detail of the go compiler.

This proposal seems to aim in providing a general mechanism to optimize Go code, I'm not sure if a directive is the proper way to achieve it.

@mauri870 go:noescape has a similar goal and already exists.
I'm not doing a language spec proposal I can submit CL and debate there if that what should be done.

This would be useful for functions with a body as well, and for those the compiler can check the read-only property. Although this is starting to feel like const in C..

@bjorndm this would be a different proposal, the compiler can already read body-full functions and recover the constness of arguments passed in.

I just wrote https://go-review.googlesource.com/c/go/+/637936 and I think it is valuable to allow functions to say they wont read or write to global state.
I'm not sure how it should look tho.
I can think of //go:readonly * for disallowing any observable writes but this is inflexible.


Added algolia search to streaming docs site

Adding algolia search to the streaming docs. Filtering based on a new projects facet from the crawler.

Looks good overall. Thanks for adding the real time search with Algolia docsearch. Can you please update the PR description with one or two line of sentence with images maybe? Mainly how does the UI looks like after we build the docs locally! Thanks!

@karan6181 - let me know if this is OK


Add documentation for authentication

This PR adds documentation that explains the ScalarDL authentication mechanism and how to use it properly.
To @reddikih,
Please take a look and try both DS and HMAC based on the doc to see if it works.
To all,
feel free to ask questions. Based on feedback, I will update the doc.

@supl Updated the doc based on your feedback. PTAL again!

@josh-wong Thank you for taking a deep look at the doc!
I applied most of your suggestions, but left comments/questions to some of the suggestions.
PTAL!

@jnmt @reddikih @josh-wong
Thank you for valuable feedback.
I think I addressed the points you mentioned.
PTAL again!

@josh-wong Thanks! Addressed in 535df7d.

I'm merging it, but let me know if you find other issues.


🐛 Bug Report: Error when registering custom actions/new actions in new backend.

📜 Description
Unable to successfully register custom actions or Roadie's HTTP requests actions after installing their plugin.
👍 Expected behavior
Register the custom action/plugin's actions.
👎 Actual Behavior with Screenshots
C:\Users\name\appName\node_modules@backstage\backend-app-api\src\wiring\BackstageBackend.ts:69
[1]   if ('$$type' in feature) {
[1]       ^
[1]
[1]
[1] TypeError: Cannot use 'in' operator to search for '$$type' in undefined
[1]     at unwrapFeature (C:\Users\GDhima\platform2\node_modules@backstage\backend-app-api\src\wiring\BackstageBackend.ts:69:7)
[1]     at  (C:\Users\GDhima\platform2\node_modules@backstage\backend-app-api\src\wiring\BackstageBackend.ts:35:47)
[1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
👟 Reproduction steps

Create a custom action by using Backstage CLI.
Register it to the backend (or at least try to)
Run yarn dev

📃 Provide the context for the Bug.
C:\Users\name\appName\node_modules@backstage\backend-app-api\src\wiring\BackstageBackend.ts:69
[1]   if ('$$type' in feature) {
[1]       ^
[1]
[1]
[1] TypeError: Cannot use 'in' operator to search for '$$type' in undefined
[1]     at unwrapFeature (C:\Users\name\appName\node_modules@backstage\backend-app-api\src\wiring\BackstageBackend.ts:69:7)
[1]     at  (C:\Users\name\appName\node_modules@backstage\backend-app-api\src\wiring\BackstageBackend.ts:35:47)
[1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

I created a custom action by using the yarn backstage-cli new command, in which I chose the scaffolder-module option. It generated a example scaffolder action, a backend module that registers the action in the scaffolder and the export index files. I made sure to register the action in backend by including:
"backend.add(import('backstage-plugin-scaffolder-backend-module-<custom-action-name>'));" in packages/backend/src/index.ts
When I execute yarn dev, it gives me the error shown on top. I have already added @backstage/plugin-scaffolder-node as a dependency. I also tried installing the HTTP request plugin by Roadie. It also gives me a similar error in that case:
"[1] C:\Users\name\appName\node_modules@backstage\backend-app-api\src\wiring\BackendInitializer.ts:105
[1]       throw new Error(
[1] Error: Failed to add feature, invalid type 'undefined'
[1]     at BackendInitializer.#addFeature (C:\name\appName\platform2\node_modules@backstage\backend-app-api\src\wiring\BackendInitializer.ts:105:13)
[1]     at BackendInitializer.#doStart (C:\Users\GDhima\platform2\node_modules@backstage\backend-app-api\src\wiring\BackendInitializer.ts:157:12)
[1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[1]     at BackendInitializer.start (C:\Users\name\appName\node_modules@backstage\backend-app-api\src\wiring\BackendInitializer.ts:150:5)
[1]     at BackstageBackend.start (C:\Users\name\appName\node_modules@backstage\backend-app-api\src\wiring\BackstageBackend.ts:42:11
)
"
🖥 Your Environment
node: v20.14.0
yarn: 1.22.4
cli:  0.26.11 (installed)
backstage:  1.28.0
Dependencies:
@backstage/app-defaults                                          1.5.6
@backstage/backend-app-api                                       0.7.9, 0.7.8
@backstage/backend-common                                        0.0.0-nightly-20240627021712, 0.13.5, 0.21.7, 0.23.2, 0.23.3
@backstage/backend-defaults                                      0.3.2
@backstage/backend-dev-utils                                     0.1.4
@backstage/backend-openapi-utils                                 0.0.0-nightly-20240627021712, 0.1.14
@backstage/backend-plugin-api                                    0.0.0-nightly-20240627021712, 0.6.21, 0.7.0
@backstage/backend-tasks                                         0.0.0-nightly-20240627021712, 0.5.26, 0.5.27
@backstage/catalog-client                                        1.6.5
@backstage/catalog-model                                         1.5.0
@backstage/cli-common                                            0.1.14
@backstage/cli-node                                              0.2.6, 0.2.7
@backstage/cli                                                   0.26.11, 0.26.9
@backstage/config-loader                                         1.8.1
@backstage/config                                                1.2.0
@backstage/core-app-api                                          1.14.1, 1.12.6
@backstage/core-compat-api                                       0.2.6
@backstage/core-components                                       0.14.8, 0.14.9-next.0
@backstage/core-plugin-api                                       1.9.3
@backstage/e2e-test-utils                                        0.1.1
@backstage/errors                                                1.2.4
@backstage/eslint-plugin                                         0.1.8
@backstage/frontend-plugin-api                                   0.6.6, 0.6.7-next.0
@backstage/integration-aws-node                                  0.1.12
@backstage/integration-react                                     1.1.28, 1.1.29-next.0
@backstage/integration                                           0.0.0-nightly-20240627021712, 1.13.0, 1.12.0, 1.13.0-next.0
@backstage/plugin-api-docs                                       0.11.6
@backstage/plugin-app-backend                                    0.3.69
@backstage/plugin-app-node                                       0.1.20
@backstage/plugin-auth-backend-module-atlassian-provider         0.2.1
@backstage/plugin-auth-backend-module-aws-alb-provider           0.1.12
@backstage/plugin-auth-backend-module-azure-easyauth-provider    0.1.3
@backstage/plugin-auth-backend-module-bitbucket-provider         0.1.3
@backstage/plugin-auth-backend-module-cloudflare-access-provider 0.1.3
@backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.15
@backstage/plugin-auth-backend-module-github-provider            0.1.17
@backstage/plugin-auth-backend-module-gitlab-provider            0.1.17
@backstage/plugin-auth-backend-module-google-provider            0.1.17
@backstage/plugin-auth-backend-module-guest-provider             0.1.6
@backstage/plugin-auth-backend-module-microsoft-provider         0.1.15
@backstage/plugin-auth-backend-module-oauth2-provider            0.2.1
@backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.1.13
@backstage/plugin-auth-backend-module-oidc-provider              0.2.1
@backstage/plugin-auth-backend-module-okta-provider              0.0.13
@backstage/plugin-auth-backend-module-onelogin-provider          0.1.1
@backstage/plugin-auth-backend                                   0.22.7
@backstage/plugin-auth-node                                      0.0.0-nightly-20240627021712, 0.4.17, 0.4.16
@backstage/plugin-auth-react                                     0.1.3
@backstage/plugin-bitbucket-cloud-common                         0.2.21
@backstage/plugin-catalog-backend-module-github-org              0.1.16
@backstage/plugin-catalog-backend-module-github                  0.6.4
@backstage/plugin-catalog-backend-module-logs                    0.0.0-nightly-20240625021714
@backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.19, 0.1.20
@backstage/plugin-catalog-backend                                0.0.0-nightly-20240627021712, 1.23.2
@backstage/plugin-catalog-common                                 1.0.24, 1.0.25
@backstage/plugin-catalog-graph                                  0.4.6
@backstage/plugin-catalog-import                                 0.12.0
@backstage/plugin-catalog-node                                   0.0.0-nightly-20240627021712, 1.12.3, 1.12.4
@backstage/plugin-catalog-react                                  1.12.1, 1.12.2-next.1
@backstage/plugin-catalog                                        1.21.0
@backstage/plugin-events-backend-module-github                   0.2.7
@backstage/plugin-events-backend                                 0.3.8
@backstage/plugin-events-node                                    0.0.0-nightly-20240627021712, 0.3.7
@backstage/plugin-org                                            0.6.26
@backstage/plugin-permission-backend-module-allow-all-policy     0.1.17
@backstage/plugin-permission-backend                             0.5.44
@backstage/plugin-permission-common                              0.7.14, 0.8.0
@backstage/plugin-permission-node                                0.0.0-nightly-20240627021712, 0.7.32, 0.8.0
@backstage/plugin-permission-react                               0.4.23
@backstage/plugin-proxy-backend                                  0.5.1
@backstage/plugin-scaffolder-backend-module-azure                0.1.13, 0.1.14
@backstage/plugin-scaffolder-backend-module-bitbucket-cloud      0.1.11, 0.1.12
@backstage/plugin-scaffolder-backend-module-bitbucket-server     0.1.11, 0.1.12
@backstage/plugin-scaffolder-backend-module-bitbucket            0.2.11, 0.2.12
@backstage/plugin-scaffolder-backend-module-cookiecutter         0.2.44
@backstage/plugin-scaffolder-backend-module-gerrit               0.1.13, 0.1.14
@backstage/plugin-scaffolder-backend-module-gitea                0.1.11, 0.1.12
@backstage/plugin-scaffolder-backend-module-github               0.3.2, 0.4.0
@backstage/plugin-scaffolder-backend-module-gitlab               0.4.3, 0.4.4
@backstage/plugin-scaffolder-backend                             1.22.11, 1.23.0
@backstage/plugin-scaffolder-common                              1.5.3, 1.5.4
@backstage/plugin-scaffolder-node                                0.4.8, 0.4.7
@backstage/plugin-scaffolder-react                               1.9.0
@backstage/plugin-scaffolder                                     1.21.0
@backstage/plugin-search-backend-module-catalog                  0.0.0-nightly-20240627021712, 0.1.27
@backstage/plugin-search-backend-module-techdocs                 0.1.25
@backstage/plugin-search-backend-node                            0.0.0-nightly-20240627021712, 1.2.26
@backstage/plugin-search-backend                                 1.5.12
@backstage/plugin-search-common                                  1.2.12, 1.2.13
@backstage/plugin-search-react                                   1.7.12
@backstage/plugin-search                                         1.4.12
@backstage/plugin-signals-react                                  0.0.4
@backstage/plugin-techdocs-backend                               1.10.7
@backstage/plugin-techdocs-module-addons-contrib                 1.1.11
@backstage/plugin-techdocs-node                                  1.12.6
@backstage/plugin-techdocs-react                                 1.2.5
@backstage/plugin-techdocs                                       1.10.6
@backstage/plugin-user-settings-common                           0.0.1
@backstage/plugin-user-settings                                  0.8.7
@backstage/release-manifests                                     0.0.11
@backstage/test-utils                                            1.5.6
@backstage/theme                                                 0.5.6
@backstage/types                                                 1.1.1
@backstage/version-bridge                                        1.0.8
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, I don't have time to work on this right now

Hi @ACEHiGH1, taking a quick look at the packages info you shared you have lots of duplicates as well as nightly versions. I would try cleaning that up as it's likely to be part of the problem.

It's also best to check if there are any TypeScript errors with yarn tsc, you'll want to track down and fix all of those before debugging runtime issues.

Hi @awanlin and @Rugvip . Thanks for the prompt reply. I cleaned all the nightly versions and most of the duplicates. It did not fix anything unfortunately. Regarding the Typescript errors, when I'm running yarn tsc, a mismatch arguments error comes up (as seen below). I'm new in TypeScript so any suggestions are helpful. Here's the error:
"
Argument of type 'Promise<typeof import("C:/Users/GDhima/platform2/plugins/scaffolder-backend-module-customaction/src/index")>' is not assignable to parameter of type 'BackendFeature | (() => BackendFeature) | Promise<{ default: BackendFeature | (() => BackendFeature); }>'.
Property 'default' is missing in type 'typeof import("C:/Users/GDhima/platform2/plugins/scaffolder-backend-module-customaction/src/index")' but required in type '{ default: BackendFeature| (() => BackendFeature); }'.
59 backend.add(import('backstage-plugin-scaffolder-backend-module-customaction'));

node_modules/@backstage/backend-app-api/dist/index.d.ts:446:9
446 default: BackendFeature | (() => BackendFeature);
~~~~~~~
'default' is declared here.
"

I have not changed anything at all from the action and backend module generated by Backstage CLI.

**example.ts**
"import { createTemplateAction } from '@backstage/plugin-scaffolder-node';

/**
* Creates an `acme:example` Scaffolder action.
*
* @remarks
*
* See {@link https://example.com/} for more information.
*
* @public
*/
export function createAcmeExampleAction() {
// For more information on how to define custom actions, see
// https://backstage.io/docs/features/software-templates/writing-custom-actions
return createTemplateAction<{
myParameter: string;
}>({
id: 'acme:example',
description: 'Runs Yeoman on an installed Yeoman generator',
schema: {
input: {
type: 'object',
required: ['myParameter'],
properties: {
myParameter: {
title: 'An example parameter',
description: 'This is the schema for our example parameter',
type: 'string',
},
},
},
},
async handler(ctx) {
[ctx.logger.info](https://ctx.logger.info/)(
`Running example template with parameters: ${ctx.input.myParameter}`,
);

await new Promise(resolve => setTimeout(resolve, 1000));
},
});
}"

and

**module.ts**
"
import { createBackendModule } from "@backstage/backend-plugin-api";
import { scaffolderActionsExtensionPoint } from '@backstage/plugin-scaffolder-node/alpha';
import { createAcmeExampleAction } from "./example";

/**
* A backend module that registers the action into the scaffolder
*/
export const scaffolderModule = createBackendModule({
moduleId: 'acme:example',
pluginId: 'scaffolder',
register({ registerInit }) {
registerInit({
deps: {
scaffolderActions: scaffolderActionsExtensionPoint
},
async init({ scaffolderActions}) {
scaffolderActions.addActions(createAcmeExampleAction());
}
});
},
})

"

And of course the index.ts files.

So, I changed  backend.add(import('backstage-plugin-scaffolder-backend-module-customaction')); to backend.add(import('backstage-plugin-scaffolder-backend-module-customaction/src/actions/example')); and it works fine now. I had the idea that the backend module would get re-exported all the way to main module ("backstage-plugin-scaffolder-backend-module-customaction", but doesn't look like it. Is this how we are intended to import the backend module?

@ACEHiGH1 not quite, that'll cause trouble in a production build. You'll want to make sure the module is manually exported as the default export from src/index.ts instead.

@Rugvip I was able to do the following changes and make it work locally.
** Project Structure:**
plugins/
├─ scaffolder-backend-module-teamcity/
│  ├─ node_modules/
│  ├─ src/
│  │  ├─ actions/
│  │  │  ├─ index.ts
│  │  │  ├─ startbuild.ts
│  │  ├─ module.ts
│  │  ├─ index.ts

**In the src/actions/index.ts file:**
`export { createStartTCBuildAction } from './startbuild';`

**In the src/module.ts file:**
`import { createBackendModule } from "@backstage/backend-plugin-api";
import { scaffolderActionsExtensionPoint  } from '@backstage/plugin-scaffolder-node/alpha';
import { createStartTCBuildAction } from "./actions";
import { coreServices } from '@backstage/backend-plugin-api';

/**
 * A backend module that registers the action into the scaffolder
 */
export const scaffolderModuleTeamCity = createBackendModule({
  moduleId: 'teamcity',
  pluginId: 'scaffolder',
  register({ registerInit }) {
    registerInit({
      deps: {
        scaffolderActions: scaffolderActionsExtensionPoint,
        config: coreServices.rootConfig
      },
      async init({ scaffolderActions, config}) {
        scaffolderActions.addActions(createStartTCBuildAction({config: config}));
      }
    });
  },
})
`

**In src/index.ts: **

`export * from './actions';
export { scaffolderModuleTeamCity as default } from './module';`

_// Importing the custom action modules in packages/backend/src/index.ts_

backend.add(import('backstage-plugin-scaffolder-backend-module-teamcity'));
backend.add(import('backstage-plugin-scaffolder-backend-module-github-custom'));

So this works in my local environment without any issues at all. However, I tried creating a Docker Image and running it and get the following import error message:
" Cannot find package 'backstage-plugin-scaffolder-backend-module-teamcity' imported from /app/packages/backe
nd/dist/index.cjs.js"
I can't seem to find the reason now why it is not correctly exporting the module. Any help is greatly appreciated.

Hi @ACEHiGH1, I have not read everything but could you be missing your package scope? This:
backend.add(import('backstage-plugin-scaffolder-backend-module-teamcity'));
backend.add(import('backstage-plugin-scaffolder-backend-module-github-custom'));

Should be this:
backend.add(import('@internal/backstage-plugin-scaffolder-backend-module-teamcity'));
backend.add(import('@internal/backstage-plugin-scaffolder-backend-module-github-custom'));

By default when you use yarn new it creates the packages inside the @interanl scope.

Hi @awanlin ,
First of all, thanks a lot for the help.
I wanted to create a custom action and used the yarn backstage-cli new command, in which I selected the :
scaffolder-module - An module exporting custom actions for @backstage/plugin-scaffolder-backend option. However, the packages created are not part of the @internal scope.
node_modules/
├─ @backstage/
├─ @azure/
├─ .../
├─ backstage-plugin-scaffolder-backend-module-teamcity/
When I switched over to this:
backend.add(import('@internal/backstage-plugin-scaffolder-backend-module-teamcity')); backend.add(import('@internal/backstage-plugin-scaffolder-backend-module-github-custom'));
Even locally it complains that it can't find the module
(Error: Cannot find module '@internal/backstage-plugin-scaffolder-backend-module-github-custom')
Here is my package.json file for one of the modules if it helps for anything:
{   "name": "backstage-plugin-scaffolder-backend-module-teamcity",   "description": "The teamcity module for @backstage/plugin-scaffolder-backend",   "version": "0.1.0",   "main": "src/index.ts",   "types": "src/index.ts",   "license": "Apache-2.0",   "private": true,   "publishConfig": {     "access": "public",     "main": "dist/index.cjs.js",     "types": "dist/index.d.ts"   },   "backstage": {     "role": "backend-plugin-module"   },   "scripts": {     "start": "backstage-cli package start",     "build": "backstage-cli package build",     "lint": "backstage-cli package lint",     "test": "backstage-cli package test",     "clean": "backstage-cli package clean",     "prepack": "backstage-cli package prepack",     "postpack": "backstage-cli package postpack"   },   "dependencies": {     "@backstage/plugin-scaffolder-node": "^0.4.8"   },   "devDependencies": {     "@backstage/backend-common": "^0.23.3",     "@backstage/cli": "^0.26.7"   },   "files": [     "dist"   ]

Ok, that's odd as it is the default: https://github.com/backstage/backstage/blob/edb89a2ee77b83ffe439383833021cc5cefaee5e/packages/create-app/templates/default-app/package.json.hbs#L25
You must have changed it at some point. That's the only thing that came to me when I spotted this.

What does packages/backend/package.json look like?

  "name": "backend",
  "version": "0.0.0",
  "main": "dist/index.cjs.js",
  "types": "src/index.ts",
  "private": true,
  "backstage": {
    "role": "backend"
  },
  "scripts": {
    "start": "backstage-cli package start",
    "build": "backstage-cli package build",
    "lint": "backstage-cli package lint",
    "test": "backstage-cli package test",
    "clean": "backstage-cli package clean",
    "build-image": "docker build ../.. -f Dockerfile --tag backstage"
  },
  "dependencies": {
    "@backstage/backend-common": "^0.23.3",
    "@backstage/backend-defaults": "^0.3.0",
    "@backstage/backend-tasks": "^0.5.24",
    "@backstage/config": "^1.2.0",
    "@backstage/plugin-app-backend": "^0.3.68",
    "@backstage/plugin-auth-backend": "^0.22.6",
    "@backstage/plugin-auth-backend-module-github-provider": "^0.1.16",
    "@backstage/plugin-auth-backend-module-guest-provider": "^0.1.5",
    "@backstage/plugin-auth-node": "^0.4.14",
    "@backstage/plugin-catalog-backend": "^1.23.2",
    "@backstage/plugin-catalog-backend-module-github": "^0.6.4",
    "@backstage/plugin-catalog-backend-module-github-org": "^0.1.16",
    "@backstage/plugin-catalog-backend-module-logs": "^0.0.1",
    "@backstage/plugin-catalog-backend-module-scaffolder-entity-model": "^0.1.17",
    "@backstage/plugin-events-backend": "^0.3.8",
    "@backstage/plugin-events-backend-module-github": "^0.2.7",
    "@backstage/plugin-permission-backend": "^0.5.43",
    "@backstage/plugin-permission-backend-module-allow-all-policy": "^0.1.16",
    "@backstage/plugin-permission-common": "^0.8.0",
    "@backstage/plugin-permission-node": "^0.8.0",
    "@backstage/plugin-proxy-backend": "^0.5.0",
    "@backstage/plugin-scaffolder-backend": "^1.22.9",
    "@backstage/plugin-scaffolder-backend-module-cookiecutter": "^0.2.44",
    "@backstage/plugin-scaffolder-backend-module-github": "^0.4.0",
    "@backstage/plugin-search-backend": "^1.5.10",
    "@backstage/plugin-search-backend-module-catalog": "^0.1.27",
    "@backstage/plugin-search-backend-module-techdocs": "^0.1.24",
    "@backstage/plugin-search-backend-node": "^1.2.26",
    "@backstage/plugin-techdocs-backend": "^1.10.6",
    "@backstage/plugin-scaffolder-node": "^0.4.8",
    "@mdude2314/backstage-plugin-scaffolder-git-actions": "^1.1.1",
    "app": "link:../app",
    "better-sqlite3": "^9.0.0",
    "node-gyp": "^10.0.0",
    "pg": "^8.11.3",
    "winston": "^3.2.1"
  },
  "devDependencies": {
    "@backstage/cli": "^0.26.7",
    "@types/express": "^4.17.6",
    "@types/express-serve-static-core": "^4.17.5",
    "@types/luxon": "^2.0.4"
  },
  "files": [
    "dist"
  ]
} ```

I would expect to see backstage-plugin-scaffolder-backend-module-teamcity and backstage-plugin-scaffolder-backend-module-github-custom listed under dependencies but they are not. I would add them.

That worked! Thank you so much!

That worked! Thank you so much!

Glad to hear that @ACEHiGH1, could we close this issue?

whats the solution i getting the same error upon running yarn dev
[0] Loaded config from app-config.yaml [0] <i> [webpack-dev-server] Project is running at: [0] <i> [webpack-dev-server] Loopback: http://localhost:3000/, http://[::1]:3000/ [0] <i> [webpack-dev-server] Content not from webpack is served from '/Users/./my-backstage-app/packages/app/public' directory [0] <i> [webpack-dev-server] 404s will fallback to '/index.html' [0] <i> [webpack-dev-middleware] wait until bundle finished: /catalog?filters%5Bkind%5D=component&filters%5Buser%5D=all [1] /Users/./my-backstage-app/node_modules/@backstage/backend-app-api/src/wiring/helpers.ts:23 [1]   if ('$$type' in feature) { [1]       ^ [1]  [1]  [1] TypeError: Cannot use 'in' operator to search for '$$type' in undefined [1]     at unwrapFeature (/Users/./my-backstage-app/node_modules/@backstage/backend-app-api/src/wiring/helpers.ts:23:7) [1]     at BackstageBackend.add (/Users/./my-backstage-app/node_modules/@backstage/backend-app-api/src/wiring/BackstageBackend.ts:33:29) [1]     at Object.<anonymous> (/Users/./my-backstage-app/packages/backend/src/index.ts:56:9) [1]     at Module._compile (node:internal/modules/cjs/loader:1358:14) [1]     at Module._compile (/Users/./my-backstage-app/node_modules/pirates/lib/index.js:117:24) [1]     at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) [1]     at Object.newLoader [as .ts] (/Users/./my-backstage-app/node_modules/pirates/lib/index.js:121:7) [1]     at Module.load (node:internal/modules/cjs/loader:1208:32) [1]     at Module._load (node:internal/modules/cjs/loader:1024:12) [1]     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12) [1]

@amrsa1 what's on the line that causes the error (packages/backend/src/index.ts:56)?
Have you checked the fixes people above have mentioned?
Does yarn tsc:full complete successfully?
Did you add any // @ts-ignore or similar that might be hiding actual problems?

Hello @freben Thanks for getting back to me.
Actually i didnt know about this command yarn tsc:full, i follow up with the errors and fixed them.
Now its working without issue.
Thanks!

That worked! Thank you so much!

Glad to hear that @ACEHiGH1, could we close this issue?

Sorry for the late response, I thought I had already answered. Yes, this issue can be closed.


Polkadot v0.9.25

Summary
Summary about this PR
Changelog

feat(xx): New Feature
fix(xx): Bug Fix
docs(xx): Documentation
perf(xx) Performance
refactor(xx) Refactor
style(xx) Styling
test(xx) Testing
chore(xx) chore
release(xx) release
chore(xx) chore
ci(xx) CI/CD
Build(xx) Build
test(xx) Testing
Other
Not for changelog (changelog entry is not required)

Related Issues
Fixes #issue
Test Plan
Unit Tests

add emergency for daos


After every spotify update when spotx is installed, spotify reverts to default (songs in playlists are not organized)

🧐 Have you read the FAQ and viewed similar issues?

[X] I have read the FAQ
[X] I have checked older issues, open and closed
[X] I did a clean install of SpotX as described in the FAQ

Сountry of your account
Slovakia
What is your Spotify Plan?
Free
Do you have Spicetify installed?
No
ℹ Computer information
- Spotify: Spotify for Windows
<IP_ADDRESS>2.g7a9200fe
- Windows: Windows 10 Pro 19043.1889
- PowerShell: 5.1.19041.1682

📝 Description
As I mentioned, when I install new spotify version and after I run SpotXBasic, it looks like it reverts everything to default.
ie: Playlists are not organized by date (which I had before running SpotXBasic)
📸 Screenshots
No response

Just disable auto update when install spotX and use the SpotX to update Spotify when new ver is available, this isn't a bug you know 😂 Maybe enhancement when Spotify update, SpotX runs with pre-used config.

fixed


settings 'slide' not working

Guidelines for posting a new issue
settings slide does nothing.
need to remove the setting from doc or add the function.
https://codesandbox.io/s/react-slick-settings-slide-not-working-how5h

I think it is related to https://github.com/akiran/react-slick/issues/1549.
And I certainly need this feature as I'm porting my application from jQuery to React and this is not working as expected.


refactor(gh-pages): refactoring of test media components

Refactor test components according the main approach

:tada: This PR is included in version 4.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Compilation failure on 1.83.0 release candidate (regression from 1.82.0)

Reported on the mailing list:
#include "boost/stl_interfaces/iterator_interface.hpp"
#include "boost/range/iterator_range.hpp"

struct basic_input_iter
   : boost::stl_interfaces::iterator_interface<
#if !BOOST_STL_INTERFACES_USE_DEDUCED_THIS
         basic_input_iter,
#endif
         std::input_iterator_tag, int>
{
   basic_input_iter() : it_(nullptr) {}
   basic_input_iter(int * it) : it_(it) {}

   int & operator*() const noexcept { return *it_; }
   basic_input_iter & operator++() noexcept
   {
       ++it_;
       return *this;
   }
   friend bool operator==(basic_input_iter lhs, basic_input_iter rhs) noexcept
   {
       return lhs.it_ == rhs.it_;
   }

   using base_type = boost::stl_interfaces::iterator_interface<
#if !BOOST_STL_INTERFACES_USE_DEDUCED_THIS
       basic_input_iter,
#endif
       std::input_iterator_tag, int>;
   using base_type::operator++;

private:
   int * it_;
};

auto make_range() {
 static int si;
 return boost::make_iterator_range(
     basic_input_iter(&si),
     basic_input_iter(&si + 1));
}

This fails to compile with the following errors:
g++ -Wall -Wstrict-aliasing=0 -Wno-unused-local-typedefs -Werror=return-type   -static-libgcc -static-libasan -static-libstdc++ -static-libubsan -std=gnu++20  -O3 -flto -pthread -Iintermediate/linux64/obj/linux64__test__iter_test  Iintermediate/linux64/libs/boost/install/include -DELDWOOD_EXTENSION_BOOST -c -o intermediate/linux64/obj/linux64__test__iter_test/eldwood/test/iter.cpp.o intermediate/linux64/obj/linux64__test__iter_test/eldwood/test/iter.cpp
In file included from intermediate/linux64/libs/boost/install/include/boost/iterator/iterator_facade.hpp:13,
from intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:27,
from intermediate/linux64/libs/boost/install/include/boost/range/iterator_range.hpp:13,
from intermediate/linux64/obj/linux64__test__iter_test/eldwood/test/iter.cpp:2:
intermediate/linux64/libs/boost/install/include/boost/iterator/iterator_categories.hpp: In instantiation of ‘struct boost::iterators::iterator_traversal<basic_input_iter>’:
intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:158:5:   required from ‘struct boost::iterator_range_detail::pure_iterator_traversal<basic_input_iter>’
intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:434:15:   required from ‘class boost::iterator_range<basic_input_iter>’
intermediate/linux64/obj/linux64__test__iter_test/eldwood/test/iter.cpp:40:36:   required from here
intermediate/linux64/libs/boost/install/include/boost/iterator/iterator_categories.hpp:118:8: error: no type named ‘iterator_category’ in ‘struct std::iterator_traits<basic_input_iter>’
118 | struct iterator_traversal
|        ^~~~~~~~~~~~~~~~~~
intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp: In instantiation of ‘struct boost::iterator_range_detail::pure_iterator_traversal<basic_input_iter>’:
intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:434:15:   required from ‘class boost::iterator_range<basic_input_iter>’
intermediate/linux64/obj/linux64__test__iter_test/eldwood/test/iter.cpp:40:36:   required from here
intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:158:5: error: no type named ‘type’ in ‘struct boost::iterators::iterator_traversal<basic_input_iter>’
158 |     traversal_t;
|     ^~~~~~~~~~~
In file included from intermediate/linux64/libs/boost/install/include/boost/utility/enable_if.hpp:15,
from intermediate/linux64/libs/boost/install/include/boost/range/has_range_iterator.hpp:21,
from intermediate/linux64/libs/boost/install/include/boost/range/difference_type.hpp:21,
from intermediate/linux64/libs/boost/install/include/boost/range/size_type.hpp:19,
from intermediate/linux64/libs/boost/install/include/boost/range/size.hpp:21,
from intermediate/linux64/libs/boost/install/include/boost/range/functions.hpp:20,
from intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:38:
intermediate/linux64/libs/boost/install/include/boost/core/enable_if.hpp: In instantiation of ‘struct boost::enable_if<boost::iterator_range<basic_input_iter>::is_compatible_range, void>’:
intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:489:13:   required by substitution of ‘template boost::iterator_range<basic_input_iter>::iterator_range(const SinglePassRange&, typename boost::enable_if<is_compatible_range, void>::type*) [with SinglePassRange = basic_input_iter]’
intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:758:20:   required from ‘boost::iterator_range boost::make_iterator_range(IteratorT, IteratorT) [with IteratorT = basic_input_iter]’
intermediate/linux64/obj/linux64__test__iter_test/eldwood/test/iter.cpp:40:36:   required from here
intermediate/linux64/libs/boost/install/include/boost/core/enable_if.hpp:41:10: error: ‘value’ is not a member of ‘boost::iterator_range<basic_input_iter>::is_compatible_range’
41 |   struct enable_if : public enable_if_c<Cond::value, T> {};
|          ^~~~~~~~~
intermediate/linux64/libs/boost/install/include/boost/core/enable_if.hpp: In instantiation of ‘struct boost::enable_if<boost::iterator_range<basic_input_iter>::is_compatible_range<basic_input_iter>, void>’:
intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:500:13:   required by substitution of ‘template boost::iterator_range<basic_input_iter>::iterator_range(SinglePassRange&, typename boost::enable_if<is_compatible_range, void>::type*) [with SinglePassRange = basic_input_iter]’
intermediate/linux64/libs/boost/install/include/boost/range/iterator_range_core.hpp:758:20:   required from ‘boost::iterator_range boost::make_iterator_range(IteratorT, IteratorT) [with IteratorT = basic_input_iter]’
intermediate/linux64/obj/linux64__test__iter_test/eldwood/test/iter.cpp:40:36:   required from here
intermediate/linux64/libs/boost/install/include/boost/core/enable_if.hpp:41:10: error: ‘value’ is not a member of ‘boost::iterator_range<basic_input_iter>::is_compatible_range<basic_input_iter>’
Build failed.

Joaquín M López Muñoz wrote:
Looks like the iterator_concept -> iterator_category mapping used here is incomplete
The mapping is copied verbatim from zip_transform_view as spelled out at:
https://eel.is/c++draft/range.zip.transform.iterator#1
I guess this is ok for zip_transform_view, but the description of the mapping explicitly says
"The member typedef-name iterator::iterator_category is defined if and only if Base models forward_range."
Note the "if and only if", implying that if Base only models input_range then iterator::iterator_category
is not defined.
FWIW, the attached patch makes the snippet compile. It simply adds and input_iterator_tag -> input_iterator_tag
case to the mapping algorithm.
iterator_interface.hpp.patch

Looks like it came from this commit: https://github.com/boostorg/stl_interfaces/commit/21e03e70130c65bb5335a15ea5d49fe0b08efbea

Zach says: Hey, Marshall.   I'm on vacation and didn't even have my phone on yesterday.  It looks like "Works as designed"  to me.  The design changed so that iterators are not compatible with pre 20 interfaces, based on LWG and LEWG feedback.  The Boost library reflects that.  I can take a closer look this weekend to verify.


chartTypes with array as yAccessor/xAccessor ?

Charts, such as LineSeries do not allow "array" for yAccessor:
LineSeries.propTypes = {
yAccessor: PropTypes.func,
}

Is there a reason for that? I want to put a array of y-values into yAccessor of LineSeries, which does not work, because it only accepts a function.
A Line is shown with this ("d" is coming from ohlcv):
<Chart id={1} height={400} yExtents={[d => [d.high, d.low]]}>
<CandlestickSeries />
// this works
<LineSeries yAccessor={d=> d.close} />
..
</Chart>

But with this, no line is shown:
<Chart id={1} height={400} yExtents={[d => [d.high, d.low]]}>
<CandlestickSeries />
// this does not work: line is not shown, no error log
// a function returning a array of values (e.g. [11.91, 11.96,..]
<LineSeries yAccessor={() => Object.values(myseries.points).map(o => o.y)} />
..
</Chart>

where "myseries.points" consists of objects with x (time) and y (for yAccessor):
points: [
    {
        x:<PHONE_NUMBER>000,
        y: 11.91
    },...]

Is there a generic indicator where the source can be provided instead of calculated?
For example, I can create ema50 with this and provide a accessor:
	```

const ema50 = ema()
.options({ windowSize: 50 })
.merge((d, c) => {d.ema50 = c;})
.accessor(d => d.ema50);

However, I already have the data from the backend, so no need to calculate ema50, no need to use ema-Indicator. I need something like this:

const ema50 = indicator() // generic indicator
.source(myseries.points) // source already available, this consists of x and y values
.options({ windowSize: 50 })
.merge((d, c) => {d.ema50 = c;})
.accessor(d => d.ema50);

with this, I can use my ema50:

<Chart id={1} height={400} yExtents={[d => [d.high, d.low], ema50.accessor()]}>

..

Or is there a easier way?

I guess, there is no need for that, because yAccessor accepts a function. With this, any values can be returned.


Configure referenceDB request timeout

When window fuzzer is run for longer durations with Presto as reference DB, it is
observed that some queries do not reach Presto for validation and they fail in
velox with the following error message:
W20240418 13:15:48.194890 1896311 AggregationFuzzerBase.cpp:470] Query failed in the reference DB

This appears to be because the default timeout of 1000ms for the http requests
made to Presto is lower and increasing this to a higher value, such as 5000ms,
fixes the issue (thanks for the fix @kgpai). This PR makes the request timeout used
by the cpr::Get request in PrestoQueryRunner a program argument to
velox_window_fuzzer_test  and velox_aggregation_fuzzer_test, so it can be
configured as necessary.

@aditi-pandit, @kgpai, could you please help review this PR?


How to get pre-trained PLOG?

Hi Author！ How can we get the pre-trained PLOG weights file？Thank you very much!

@tom68-ll Hello, did you manage to get the pre-trained PLOG weights file? or did you end up training it yourself?


Reduce size of docker file

Detailed Description
The current docker file is ~ 600MB - docker hub.
It would be great to reduce this if possible.
Context
Good to keep docker files
Possible Implementation
Perhaps dont isntlal packages that are used. Might have to do someting in nowcasting_dataset

Moved this issue here as the forecast docker size proberly wont reduce that much. But we should aim to keep this api nice and light-weight


[Docs] merge zihao tutorial notebooks

Merge https://github.com/TommyZihao/MMGeneration_Tutorials into our repo.

Merge these notebooks will increase our repo's size by 23.6MB. @LeoXing1996


Isolate Apps to disable them whenever needed

Summary
Isolate apps so whenever we need, we can disable them and do the least effect on the rest of the user agent.
Ticket Link
https://mattermost.atlassian.net/browse/MM-32239
Related Pull Requests
None
Screenshots
None

Regarding components/suggestion/command_provider/command_provider.tsx do you think now is the right time to isolate, or should we wait for the changes that are supposed to be coming soon?

Regarding components/suggestion/command_provider/command_provider.tsx do you think now is the right time to isolate, or should we wait for the changes that are supposed to be coming soon?


Can this work support 3 channels RGB image?

Hi Y,
I should work for RGB as long as you modify the code for three channels.


Update deps, especially autoprefixer

Can we update the deps for this project?  Does cssnano still depend on autoprefixer?  If so, can you push to autoprefixer@8?  The Bootstrap package.json file has a browserslist key that has filters that only work in autoprefixer@>7.
Since I'm using parcel-bundler (depends on cssnano), I get weird errors in the build.

@ben-eb do you need help maintaining? I can definitely do this.

Even with the local browserslist updated in cssnano it requires postcss-merge-rules which has caniuse-api at such a low version that browserslist is at version 1 in that package, and is causing my build to fail. I am trying to use browserslist new extends config extends browserslist-config-mycompany. Only workaround I can use for now is switching to csso :(

Echoing @Zashy, I arrived at this issue after trying Browerslist extends in package.json:
"browserslist": [
  "extends browserslist-config-google/modern"
],

... with optimize-css-assets-webpack-plugin and cssnano (browserslist@1.7.7).

extends support was added in Browserslist 2.5

Arrived after ejecting from create-react-app and trying alt-* and >= in browserslist of package.json
Turns out webpack's css-loader depends on this package, actually pretty annoying not to be able to use the minimize option with browserslists v2+ configs in package.json, please someone fix this ?

@maksugr a lot of deps already updated right now

@evilebottnawi I see this in the master branch
❯◯ all-contributors-cli          latest  4.8.1   ❯  4.11.2  https://github.com/jfmengels
/all-contributors-cli#readme
 ◯ babel-plugin-module-resolver  latest  2.7.1   ❯  3.1.1   https://github.com/tleunen/b
abel-plugin-module-resolver#readme
 ◯ camelcase                     latest  4.1.0   ❯  5.0.0   https://github.com/sindresor
hus/camelcase#readme
 ◯ coveralls                     latest  2.13.3  ❯  3.0.1   https://github.com/nickmerwi
n/node-coveralls#readme
 ◯ eslint                        latest  3.19.0  ❯  4.19.1  https://eslint.org
 ◯ eslint-plugin-babel           latest  3.3.0   ❯  5.1.0   https://github.com/babel/esl
int-plugin-babel#readme
 ◯ gh-pages                      latest  0.11.0  ❯  1.2.0   https://github.com/tschaub/g
h-pages
 ◯ nyc                           latest  11.9.0  ❯  12.0.2  https://github.com/istanbulj
s/nyc#readme
 ◯ remark                        latest  7.0.1   ❯  9.0.0   http://remark.js.org
 ◯ remark-cli                    latest  3.0.1   ❯  5.0.0   http://remark.js.org
 ◯ remark-html                   latest  6.0.1   ❯  7.0.0   https://github.com/wooorm/re
mark-html#readme
 ◯ remark-toc                    latest  4.0.1   ❯  5.0.0   https://github.com/remarkjs/
remark-toc#readme
 ◯ tomlify-j0.4                  latest  2.2.1   ❯  3.0.0   https://github.com/jakwings/
tomlify-j0.4
 ◯ unist-util-remove             latest  0.2.1   ❯  1.0.1   https://github.com/syntax-tr
ee/unist-util-remove#readme

@maksugr it is dev deps, also they require node@6 minimum

@evilebottmawi and don’t you want to update them?

@maksugr already do it:

https://github.com/ben-eb/cssnano/pull/499
Drop node@4
Update all deps


[WIP] Refactor cross chain transfer.

:white_check_mark: Build AElf <IP_ADDRESS>70 completed (commit https://github.com/AElfProject/AElf/commit/8fcb0b85e3 by @shiwk)

:white_check_mark: Build AElf <IP_ADDRESS>75 completed (commit https://github.com/AElfProject/AElf/commit/111063c9f8 by @rosona)


Trailing Commas user-controller.js

I was curious if anyone has issues running the app with the trailing commas in users-controller.js? If so I have a branch with the fixes, but I was checking first because it seemed like something others may not have issues with in order to run the app. There are three of them in the controller in various locations.
In order to reproduce I am running npm run dev script and I am seeing the errors show as Syntax Error from nodemon.
Here are my specs:
NodeJS - v6.5.0
NPM - 5.7.1
MacBook Pro
OS X El Capitan

It seems like this is an issue with the version of NodeJS being used. I started using v8.5.0 and everything worked as expected. Maybe there should be a minimum requirements of NodeJS version in the README.md?

@someyoungideas sorry I didn't get to this sooner, what I would like to do is specify our engine in the package.json we started the project on node v8.9.0 and this is something I need to add for the deployment pipeline anyways. If you want to add this and the debug script in your PR #299 that would be great.
Thanks

Closing after merge of #299 PR


Add actual gasPrice to synthetic transaction receipts

Description:
This PR modifies eth_getTransactionReceipt function in order to add effectiveGasPrice for synthetic transactions (HTS), Contract Create or Contract Call.
Related issue(s):  https://github.com/hashgraph/hedera-json-rpc-relay/issues/1736
Notes for reviewer:
Hash of a test transaction in testnet:
0xd624d50e109c51d3765c3ade221797b6003b5b0dd0063c49fad5add8f04ffcc6
Checklist

[ ] Tested (unit, integration, etc.)

Codecov Report
Patch coverage: 66.66% and project coverage change: -0.90% :warning:

Comparison is base (5c991dc) 77.75% compared to head (4292dc5) 76.86%.

:exclamation: Current head 4292dc5 differs from pull request most recent head 05b74f7. Consider uploading reports for the commit 05b74f7 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1743      +/-   ##
==========================================
- Coverage   77.75%   76.86%   -0.90%
==========================================
  Files          26       39      +13
  Lines        2329     2922     +593
  Branches      478      588     +110
==========================================
+ Hits         1811     2246     +435
- Misses        376      496     +120
- Partials      142      180      +38

Files Changed
Coverage Δ

packages/relay/src/lib/eth.ts
85.71% <66.66%> (-0.08%)
:arrow_down:

... and 14 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@Nana-EC
Hello :)
I have added the two tests you asked for.
Please have a look and comment on them.
Hopefully all your recommendations are addressed.
P.S.
(the previous push was just a test one. I am sorry for the spam)


feat: set fade to false for feature banner

The fade property on the Reactstrap Alert component causes the alert
to fade in when it is rendered. This may make for a slightly smoother
experience when an alert pops up due to an error submitting a form, for
example. However, it is not as nice of an experience for static
components which are always rendered on the page, such as the feature
banner, since it causes them to take longer to render. It also causes
jarring behavior when swapping out some elements in the page while
leaving the feature banner unchanged.
Before
https://user-images.githubusercontent.com/16616853/118706771-996aee80-b7ce-11eb-9133-5b573382c50d.mov
After
https://user-images.githubusercontent.com/16616853/118706744-92dc7700-b7ce-11eb-9f66-332bf9baf59d.mov

 Business hours setup UI


Error when running for the first time

I get the following error when I run for the first time:
Traceback (most recent call last):
File "C:\Program Files\Sublime Text 3\sublime_plugin.py", line 574, in run_
return self.run(edit)
File "C:\Users\Chris\AppData\Roaming\Sublime Text 3\Packages\CodeFormatter\CodeFormatter.py", line 79, in run
formatter = Formatter(self.view, file_name, syntax, saving)
File "C:\Users\Chris\AppData\Roaming\Sublime Text 3\Packages\CodeFormatter\codeformatter\formatter.py", line 59, in init
if ("syntaxes" in opts and opts["syntaxes"]):
TypeError: argument of type 'NoneType' is not iterable

I will check. Thank you for submitting

Can you show me your CF settings?

I have the same error. What is CF ?

CodeFormatter. I'm not by my home computer atm, so I can't send over my settings yet.

this the content of CodeFormatter.sublime-settings http://pastebin.com/LnDgddVv

solved by restarting Sublime. All good. (and re-verified by uninstalling/install it)

I tried restarting, but it didn't fix my problem.
On Thu, Mar 31, 2016 at 12:05 PM, ticapix<EMAIL_ADDRESS>wrote:

solved by restarting Sublime. All good. (and re-verified by
uninstalling/install it)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/akalongman/sublimetext-codeformatter/issues/208#issuecomment-204001474

As @catsclaw, restarting didn't fix this for me.  Windows 7 64bit


jetbrains.phpstorm: 2017.1.4 -> 2017.2.1

Motivation for this change
phpstorm 2017.2 is out for a while and required for development for newer versions of typescript (> 2.5)
Things done

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

[X] NixOS
[ ] macOS
[ ] Linux

[ ] 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"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

I updated automatically also the other jetbrain products using pkgs/applications/editors/jetbrains/update.pl

that didn't update phpstorm - phpstorm is still at 2017.1.4
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/editors/jetbrains/default.nix

Indeed I had to updated the update-channel for the script to catch it: 6dae73f552f299e4be792a8f526dda98f427149e


Cannot edit

Hi @mmoreshead
Wiki is now back (yay!) but I cannot edit - I had no problem editing it before.
Can you have a look please?
Here's the error in case you need it:
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in one of the groups: Administrators, approved, staff, regional, affiliate, community.
Thanks!

Approved, let me know if it's not working (because that would mean it's something else).


feat: skip caching uncompressed pages if they are large

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
This PR skips caching uncompressed pages for a column in a row group if it has multiple uncompressed pages. Since caching uncompressed pages for this column may be memory inefficient and decompressing all pages may be slower than only decompress pages on demand.
It also prints more information to logs and explain outputs.
Checklist

[ ] I have written the necessary rustdoc comments.
[ ] I have added the necessary unit tests and integration tests.
[ ] This PR requires documentation updates.

@coderabbitai summary


fix to create user or idp by cluster id

when we tried to create idp or user we got the following error:
11:34:16  ods-ci-logger: INFO     CMD: ocm --v=0 create idp -c mods-master -t htpasswd -n htpasswd-cluster-admin --username htpasswd-cluster-admin-user --password ****
11:34:16  Error: Failed to get cluster 'mods-master': There are 2 subscriptions with cluster identifier or name 'mods-master'
11:34:16
11:34:16  ods-ci-logger: INFO     CMD: ocm --v=0 create user htpasswd-cluster-admin-user --cluster mods-master --group=cluster-admins
11:34:16  Error: Failed to get cluster 'mods-master': There are 2 subscriptions with cluster identifier or name 'mods-master'

Thanks @kobihk for the PR. Could you do a test run on Jenkins with these changes before merging. LGTM otherwise

LGTM, just for the reference - note that this is technically a followup of #1056.
There are still some linter errors, probably from the time we didn't enforce this. Could you please update too? In a separate commit would be the best so that we don't mix these, but depends on you.

LGTM, just for the reference - note that this is technically a followup of #1056.
There are still some linter errors, probably from the time we didn't enforce this. Could you please update too? In a separate commit would be the best so that we don't mix these, but depends on you.

I fixed it already how do I retrigger the linter test?

I fixed it already how do I retrigger the linter test?

It is re-triggerred automatically once you push the changes. Problem is what Jiri shared above.

@kobihk Can you please elaborate what is the fix ?
I can see mainly changes in the format of strings, but I don't see what is the flag/value for ocm cli that was changed ?


[SC] Allow structs through private method param validator

Closes #2711

All SC + integration tests passing


New feature notification

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?
Add feature of notifications

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Is there any issue related to this PR in other repository? (such as dojot/dojot)
This PR is connected to dojot/dojot#952.

Other information:

I will apply autofix from codefactor in my own repository


Dashboard shows Blank

Expected behavior
Dashboard is showing Blank because of some angular Error.Am new in Developing Please instruct me step by step if anything i need to do up and running this error
Actual behavior
Step to reproduce

Hi @ziyadsv , thanks for trying Mixcore. Could you help start the installation process again with the "develop" branch here: https://github.com/mixcore/mix.core/tree/develop
And please refer this build guide here: https://docs.mixcore.org/docs/introduction#build-run
Feel free let us know if you still facing any issues.

Can confirm this is still an issue in v1.0.0-alpha.2 tag and also develop branch

@Smilefounder @nhathoang989
I think this issue needs to be re-opened as it is still an issue in the latest dev versions.

Issue is fixed

@ziyadsv which branch are you building from?

Thanks @ziyadsv for your confirmation.
@skywalkerisnull could you help share with me the steps and can you open the chrome dev console then screen capture any issues there.

I went to redo it this morning on the develop branch and could not build the develop:
docker-compose build
db uses an image, skipping
Building web
Step 1/18 : FROM node:10.16.3 AS node-env
 ---> a68faf70e589
Step 2/18 : WORKDIR /app
 ---> Using cache
 ---> 3e1059be2072
Step 3/18 : COPY src/. ./
 ---> 6d98f1b3f06d
Step 4/18 : WORKDIR /app/portal-app
 ---> Running in c7b498117115
Removing intermediate container c7b498117115
 ---> 90bff64c9f42
Step 5/18 : RUN npm install
 ---> Running in 08ff752a22a1
npm WARN saveError ENOENT: no such file or directory, open '/app/portal-app/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/app/portal-app/package.json'
npm WARN portal-app No description
npm WARN portal-app No repository field.
npm WARN portal-app No README data
npm WARN portal-app No license field.

up to date in 1.342s
found 0 vulnerabilities

Removing intermediate container 08ff752a22a1
 ---> bb9e82439123
Step 6/18 : RUN npm install gulp-cli -g
 ---> Running in c1cad486d437
/usr/local/bin/gulp -> /usr/local/lib/node_modules/gulp-cli/bin/gulp.js
+<EMAIL_ADDRESS>added 237 packages from 156 contributors in 23.072s
Removing intermediate container c1cad486d437
 ---> 1a415cb1ce4f
Step 7/18 : RUN npm install gulp -D
 ---> Running in d4d507f44d00
npm WARN saveError ENOENT: no such file or directory, open '/app/portal-app/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/app/portal-app/package.json'
npm WARN portal-app No description
npm WARN portal-app No repository field.
npm WARN portal-app No README data
npm WARN portal-app No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+<EMAIL_ADDRESS>added 316 packages from 217 contributors and audited 6512 packages in 34.067s
found 0 vulnerabilities

Removing intermediate container d4d507f44d00
 ---> bdc34d1b8cc4
Step 8/18 : RUN gulp build
 ---> Running in 8ee7e65f534b
[00:17:50] No gulpfile found
ERROR: Service 'web' failed to build: The command '/bin/sh -c gulp build' returned a non-zero code: 1

Hi @skywalkerisnull really thanks for the information. I didn't aware that you are using docker. Recently, we just split portal to separate repo here https://github.com/mixcore/mix.spa.portal
However, I haven't setup the docket with new structure yet. Let me revise this week and keep you posted ASAP.
For now, you can use develop branch without build mix.spa.portal. as the latest code from portal has been built and commit to develop branch.


PS5ish 4.4.0

Meanwhile, thanks for the latest PS5ish update, there are some things that have not yet been optimally corrected, on the home screen the text "cerca" and "impostazioni" are not yet centered correctly I attach images.
The animation when starting the theme is not correct, it starts asynchronously, I am attaching videos.
The name of the PSstore icon is poorly localized in Italian, it must not be "Pagina del negozio" but "PlayStation Store", thanks again for your work

https://user-images.githubusercontent.com/93041304/145025212-8cf10e9d-df1a-4aea-a541-9562c9d7524a.mp4

I cannot get the labels for Search or Settings to centre anymore than they are. It will break too many things.
Your into issue is easily sorted, set the intro length in the DKG Theme Modifier to be the same or 1 second longer than your video intro.


cannot install the latest version via npm

try
npm install<EMAIL_ADDRESS>got
version not found<EMAIL_ADDRESS>while
npm install flex-sdk
got
<EMAIL_ADDRESS>Could you try to fix it? Possibly would require you to re-publish again

Could it be: "npm install<EMAIL_ADDRESS>as it could be seen in [README] (https://github.com/JamesMGreene/node-flex-sdk#release-history) ?

npm ERR! notarget No compatible version found<EMAIL_ADDRESS><4.7.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["4.5.0-0","4.1.0-0","4.0.0-0","3.6.0-0","3.5.0-0","3.4.1-0","3.4.0-0","3.3.0-0","3.2.0-0","3.1.0-0","3.0.1-0","3.0.0-6","3.0.0-5","3.0.0-4","3.0.0-3","3.0.0-2","3.0.0-1","3.0.0-0","3.5.0"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

not working

npm ERR! node v6.3.1
npm ERR! npm  v3.10.5

npm ERR! No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
npm ERR! 4.5.1-0, 4.5.0-0, 4.1.0-0, 4.0.0-0, 3.6.0-0, 3.5.0, 3.5.0-0, 3.4.1-0, 3.4.0-0, 3.3.0-0, 3.2.0-0, 3.1.0-0, 3.0.1-0, 3.0.0-6, 3.0.0-5, 3.0.0-4, 3.0.0-3, 3.0.0-2, 3.0.0-1, 3.0.0-0

I had tried npm install<EMAIL_ADDRESS>--save-dev and it succeed, but failed if i did npm install<EMAIL_ADDRESS>or npm install<EMAIL_ADDRESS>Anyone can solve this problem?


Add ValueOverMaxSize to the whitelist of expected exceptions that get re-raised

This is a follow-up to #612, which doesn't currently behave as expected.
When actually using the Server instance as intended through the request interface, the Dalli::ValueOverMaxSize error was getting swallowed by the final rescue => ex branch since it wasn't added to the cases of whitelisted exceptions to re-raise.
Because of the way test_server.rb is written (using send to test private methods directly), there's unfortunately not really a good way to fix the tests to red/green this without serious refactoring.

Thanks for circling back on this and resolving the issue.

@petergoldstein Thank you! :heart: :heart: :heart_eyes_cat: :heart:


Cuda out of Memory

Hi,
I tried to run the code using 1050ti, but I get this error:
File "E:\UGATIT-PyTorch-master2\ugatit_pytorch\model.py", line 31, in forward
out = self.rho.expand(x.shape[0], -1, -1, -1) * out_in + (1 - self.rho.expand(x.shape[0], -1, -1, -1)) * out_ln
RuntimeError: CUDA out of memory. Tried to allocate 20.00 MiB (GPU 0; 4.00 GiB total capacity; 3.44 GiB already allocated; 0 bytes free; 3.50 GiB reserved in total by PyTorch)
Is there any way to solve this issue?

Hi,
I tried to run the code using 1050ti, but I get this error:
File "E:\UGATIT-PyTorch-master2\ugatit_pytorch\model.py", line 31, in forward out = self.rho.expand(x.shape[0], -1, -1, -1) * out_in + (1 - self.rho.expand(x.shape[0], -1, -1, -1)) * out_ln RuntimeError: CUDA out of memory. Tried to allocate 20.00 MiB (GPU 0; 4.00 GiB total capacity; 3.44 GiB already allocated; 0 bytes free; 3.50 GiB reserved in total by PyTorch)
Is there any way to solve this issue?

@sinagh72
Hi, i'm not an expert. but i think you need more powerful(more gpu memory) gpu on your pc, because forward pass need a  lot of resources.
I think, one of more usefull solution is just training on multiple gpu's, but of course you need multiple gpu's to do that.


Is it possible to disable xcpretty in scan?

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I am having a problem with my iOS project that code coverage data from UI tests is not reported. I have tried using Slather and directly with Codecov, as well as just looking locally, and no data is reported for UI tests. There is an issue reported in xcov, as well as an issue reported in Codecov that discuss this further. I'm wanting to keep using Fastlane, and want to try disabling xcpretty to see if I can get proper results. I can disable it fine with gym, but cannot figure it out with scan. Thanks!

Hi @benjaminsnorris right now that's not possible in scan but it'd be an interesting PR. Would you be interested in contributing to our repo? We'd love that 👍

@benjaminsnorris Could you use the output_style option with raw? Looking at the code, this should eliminate the use of xcpretty.
https://github.com/fastlane/fastlane/blob/0e54a6ddd734e4dc04546f3d0cffff59d48700ca/scan/lib/scan/test_command_generator.rb#L62-L92

Sorry, I should have come back to this. I did some manual tests and found that the underlying issue of UI test code coverage is not solved by disabling scan, so this fell completely off my radar.

Thanks for following up! Going to close this issue as it seems to have been a red herring resolved. Feel free to continue conversation if necessary! 🐙


Trash "row" should accommodate any number of cards

Trash "row” height should be allowed to expand to accommodate a large number of cards.

Done.


chore: sunset unused ChildAccount type

✅ Checklist

[ ] npx changeset was attached. (not needed)
[x] Covered by automatic tests. if it builds, it should be good.
[x] Impact of the changes: none (unused)

📝 Description
We introduced the concept of ChildAccount back in 2020 on the first implementation of Tezos which had this concept of KT Accounts. These not being strictly a token, but a "sub account of tezos", it made sense at the time to diverge from the Token Account.
Since the JS rework of tezos (2021?) as well as Tezos' sunset of kt accounts (delegation now directly happens on the main account), we no longer needed to support KT Accounts. However that type was still forgotten in our type model and became tech debt.
We can now remove it, this makes possible simplifications in the future, you can notably observe that the type SubAccount is now strictly equivalent to TokenAccount.
❓ Context

JIRA or GitHub link: https://ledgerhq.atlassian.net/browse/LIVE-11884

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

@hedi-edelbloute was we discussed in DM too: ChildAccount are sunset since 2021, unfortunately we just forgot this tech debt in the past, but i'm almost certain that our UI have not survived the successive rework and will not support out of the box this idea from the past. It would be easier to just reintroduce the concept whenever you re-need it in the future, but i think we have to sunset what is unused first.


Uncaught TypeError: Illegal invocation

This works:
dom.document.documentElement.asInstanceOf[js.Dynamic].webkitRequestFullScreen()

while this does not:
val a = dom.document.documentElement.asInstanceOf[js.Dynamic].webkitRequestFullScreen
a()

This behavior is not consistent.

I do not have a WebKit-powered browser to do the test, but I am convinced that the behavior you observe is consistent with what JavaScript does. In JavaScript, doing
var f = x.m;
f();

is not the same as
x.m();

Since you are using js.Dynamic, you are deliberately opting for JS semantics. The behavior is therefore as-designed.
You can get a correct behavior like this:
val a = () => dom.document.documentElement.asInstanceOf[js.Dynamic].webkitRequestFullScreen()
a()

This makes sense, it really is a JavaScipt thing. I have soved it by choosing to pass the original method parent back into the call method, like this. I hope that this helps someone else.
a.call(dom.document.documentElement)
Thank you.


macOS: gcc workaround

Description
Bug fixing
Currently, due to changed brew link logic, gcc-8 is unlinking during gcc-9 installation.
Related issue:
Check list

[-] Related issue / work item is attached
[+] Tests are written (if applicable)

/azp run macos1013, macos1014, macos1015, macos110


Better support for punning

Punning is where the same URI is used for, say, both a Class and an Individual.
Currently, this is handled in owl2json by creating both an entry in "classes" and an entry in "individuals", with the same properties. However, some of these properties only apply to the Class, and some only apply to the Individual, so the current behaviour is wrong; it doesn't lose anything, but it adds properties where they should not be.
We can identify to which types the property applies by looking at the semantics of the property. For example, if the rdfs:domain of the property refers to a Class, the property should not be added to Individuals in the owl2json output.
The other side of this issue is that property might point to something that is punned. Does it refer to the Class or the Individual? Presumably we can look at the range of the property in a similar manner to above, but this would need to be done in json2neo because in the output of owl2json there is no unique identifier for each type of a punned entity (only the URI).

The other side of this issue is that property might point to something that is punned. Does it refer to the Class or the Individual? Presumably we can look at the range of the property in a similar manner to above, but this would need to be done in json2neo because in the output of owl2json there is no unique identifier for each type of a punned entity (only the URI).

This should really be done in owl2json. So we need to add unique IDs to entities in the owl2json output.

From discussion with @dosumis :
If you have a punned Class/Individual and there is a triple using an object property/data property (rather than an annotation), this would be legal on the Individual but not on the Class, so it should be only be rendered for the Individual (and vice versa). Simple triples using an object property/data property only belong on the individual. Otherwise they would need to be annotation properties.
rdf:type only belongs on the Individual.

We can't rely on the domain for this because the type of the object can actually be inferred by the domain (as it is in some of the owl2 primer examples). We can't have both the type of the object determine which properties to include by their domain AND the domain of the properties determining the type of the object as these are contradictory.
Rather need to look at simply whether they are ObjectProperties (i.e. relationships between individuals), DataProperties (values on individuals) or AnnotationProperties (annotations on anything).


触发器支持不等于和不包含

Codecov Report

Merging #967 (a5cdf8d) into v2.6.x_develop (800451d) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop     #967   +/-   ##
===============================================
  Coverage           60.74%   60.74%
===============================================
  Files                 467      467
  Lines               29845    29845
===============================================
  Hits                18130    18130
  Misses              11715    11715

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Docs needed: How to run EddieBot locally without docker

The readme currently explains how we are supposed to set up EddieBot locally using docker-compose. Unfortunately, some of us devs don't have docker-compose on our systems. So, it would be awesome if someone added some more docs on how we can run EddieBot locally without docker or docker-compose. Thank you! :slightly_smiling_face:

Hi @RaisinTen 😃, you have a totally valid point. I think we can add to the README the previous way of running locally because it still is a valid option I believe.
What you have to do is setup your .env like the docs say, but then you can simply run npm run start:local.

Thanks @RaisinTen , this should be possible to do without docker 👍 .
Thanks @BOLT04 for replying 👍


Make the VBS folder path changable

In some cases having the VBS under node_modules will make the application fail due to that changing the path of the VBS folder path is required

Sorry for the late late late attention to this PR.
Can you please explain why would you want an external VBS folder?

Dear Yaniv,
I was working with Electron, so the electron application couples all
dependencies in one file called app.asar, after coupling this files the
module couldn't locate the VBS files because they are compressed in one
file.
So the solution was that the VBS folder to go somewhere out of the modules
folder and to a shared location, thats why i needed an external VBS folder.
This problem is reproduced with multiple cases and reported as a bug for
some people
On Fri, Dec 1, 2017 at 4:30 AM, Yaniv Kessler<EMAIL_ADDRESS>wrote:

Sorry for the late late late attention to this PR.
Can you please explain why would you want an external VBS folder?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ironSource/node-regedit/pull/47#issuecomment-348383998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFtMbUAU-tDWff16aXXPXbeIy0CZ9dkJks5s72S_gaJpZM4PUMuq
.

@kessler Is this PR going to be merged soon? Otherwise, I will have to fork it, since I have the same Problem ( Error: Command failed: cscript.exe //Nologo PATH_TO_APP\resources\app.asar\node_modules\regedit\vbs\regList.wsf A HKLM\SOFTWARE)
@muminasaad could you further elaborate your fix, please? As I understand it:

Copy VBS folder from /node_modules/regedit to a different one (let's say /assets/vbs)
Add that vbs folder to the build includes if necessary (I am having this problem in electron-builder)
Reference the new vbs folder from the modified script
Is this correct?

@Taxel I requested the changes, but honestly I didn't check back. Let's see what @muminasaad has to say about my request. If he don't respond soon I'll try to merge it myself

@Taxel You understand perfectly.
you need to manually copy the vbs files to folder that can be accessed from cmd, then call the setExternalVBSLocation function to change the VBS files location.
@kessler  I dont understand what you mean with requesting the changes if can explain more i would be gratefull :)?

@muminasaad I see now I started the review but did not submit it, my bad! here you go

Published to npm in version 3.0.0


Rename toUnit to void

@saucam Nicely done. Congratulations on your first pull request here, and thank you for the contribution! 🙏


ALE reports "The type or namespace name 'x' does not exist..."

All using statements that do not belong to the System namespace get flagged in .NET Core projects, but not always. In one of my projects, this is an issue in all files except Startup.cs, but in a clean project created by dotnet new api, even Startup.cs is affected.

All projects build just fine, and this issue is not present when using Syntastic.

If this is happening with ALE and not with Syntastic, then it's probably one of the other ALE linters - you can see which ALE linters are enabled in the output of :ALEInfo
Try adding this to your .vimrc to set OmniSharp as the only linter for .cs files:
let g:ale_linters = {
\ 'cs': ['OmniSharp']
\}

Thanks for your reply, @nickspoons
Indeed, the problem was that ALE had the following linters enabled for .cs by default: ['mcs', 'mcsc', 'omnisharp']. Setting the linter to "omnisharp" only resolved the issue 🎉


Added the new field - category and categorized the post accordingly

This PR is in regards with Issue #135

Yes. Just noticed. Will work on it.

@Siddharth1006 Any updates on this PR? No rush.


Temporary change to allow users to force a target

This is a workaround to the adapter that allows a user to set OVMS_FORCE_TARGET_DEVICE in the builtInAdapter.env section. This is then written into the config for each model that the model server manages
This is needed right now because when on a node with an Nvidia GPU, OVMS does not always ensure that the model goes onto the right device.
The changes needed to the runtime are:
spec:
  builtInAdapter:
    env:
      - name: OVMS_FORCE_TARGET_DEVICE
        value: NVIDIA

Note, this actually accepts any value from https://github.com/openvinotoolkit/model_server/blob/main/docs/accelerators.md so it enables a lot of the interesting behavior OVMS is capable of
Same changes as https://github.com/red-hat-data-services/modelmesh-runtime-adapter/pull/3

@Xaenalt I have couple of questions.

is it for opendatahub only?

Do we need to put this into the release branch too?

sound like it is a temporary change so will you update this later?

Needs to go in 1.27 release by code freeze tomorrow.
This is temporary until the AUTO plugin supports Nvidia, but may be desired longer term to enable more of the functions of the target_device field. It may get restructured later on if that's the case

/cherry-pick release-v0.11.0-alpha


Cloned instance of template breaks subshop compatibility

PHP Version
7.4
Shopware Version
5.7.11
Actual behaviour
Hi,
I'm refering to this commit: https://github.com/FriendsOfShopware/FroshTemplateMail/commit/1dcc5594dc7c55d9aaa27a89c9a3f0de6db2995e
Cloning the instance breaks the subshop compatibility in our shop. The result is really strange. See example below.
I make an order in our German shop and the order mail is fine. I than make an order in our Dutch shop and I get an order mail with sender, subject and footer from the German shop. I than make an order in our German shop again and I get an order mail with sender, subject and footer from the Dutch shop. So the mail depends on the last existing order in Shopware. This also happens if the orders are made from diffrent persons on diffrent devices from diffrent networks.
What is the advantage here if the object is cloned? If I revert commit 1dcc559, than the mails are fine and I can't find any downsides.
Thank you for feedback in advance.
Expected behaviour
Mails are always sent in the right context
Steps to Reproduce?

Update Shopware from 5.6.7 to 5.7.11
Update FroshTemplateMail from 1.0.0 to 1.1.2
Order alternately in subshops

I observed that issue in 3 different shops with subshops, too. But I have no clue how that clone statement could produce such behavior. I thought about some kind of race condition as the reason for this bug 🤔

@larsbo I first thought it was due to the session management. I have no clue whats wrong with the clone statement either.
Could you please verify if removing the clone statement helps in your case, too?


[Minor]: Change a single letter in readme

I mean. if this is the food-server then..
dunno.

wait. it says rood-server. CRYING. just a second.


Add Participants template

Adds a proposed template to encourage users to fork the repo and practice their PR flow.

I think this looks good. Any objections?

I like this idea, but I'd prefer that we use markdown links.
Ex:
Corey McCarty

I like this idea, but I'd prefer that we use markdown links.
Ex:
[Corey McCarty](https://github.com/xanderyzwich) displays as
Corey McCarty

Updated @xanderyzwich thanks


feat: TLS implementation in gRPC sink

Implemented TLS support in gRPC sink.
also added 2 configurations for gRPC sink:-

SINK_GRPC_TLS_ENABLE → indicates whether the sink needs to be connected over TLS. Default value is false
SINK_GRPC_ROOT_CA → The ca-certificates of GOTO domain *.gojek.gcp

In the same MR, update firehose doc for this feature.


Add option to text property to avoid text normalization

In same cases I want to get the exact text that contains an element without the trimming and space normalization we do by default. https://github.com/san650/ember-cli-page-object/blob/754d7a1cd0c6337bb3cd590673b4b215ea3aaee2/test-support/page-object/queries/text.js#L74
It would be great to have a normalize: false option to avoid the normalization process
var page = create({
  pre: text('pre', { normalize: false })
});

...

andThen(function() {
  assert.equal(page.pre, '  hello world \n\n');
});

:+1:

@san650  https://github.com/san650/ember-cli-page-object/pull/161/files

Fixed by #161

Thanks @vvscode for contributing!


Add the AI-Lab to the official documentation page of Exasol company

https://docs.exasol.com/home.htm

at least: add a link to the Github repo

Eswar created https://exasol.atlassian.net/browse/DOC-3097

Documentation will be updated completely. closing as won't fix.


Packaging server resources

I want to package a resources directory for a server using a property in the same way that the server.xml, bootstrap.properties etc. can be specified. i.e.

This has been resolved by pull request #129.


Keep release-notes.txt in the nuget package, but remove it from content-dependencies

Fixes: #137

Will be part of v0.4.0.


Fix progress bar corner case

This PR fixes an error message ("RangeError: Invalid count value") encountered while running mops init on this repository. This was apparently caused by the local done variable being Infinity when total is zero and step is nonzero.

@rvanasa thanks!

Seem like the problem was in .repeat() with a negative argument


Add children prop to RadialGradient

Hi!
I found this missing prop while using your bindings, so I decided to contribute instead of patching the package locally.
These bindings are great, thanks for it!

Good catch!

12.1.6-0.63 is out with your patch :)

Thanks!


xADReplicationSiteLink (Fixes #191)

Pull Request (PR) description
Added the xADReplicationSiteLink resource which adds the ability to manage AD replication sites via DSC.
This Pull Request (PR) fixes the following issues

Fixes #191

Task list

[x] Added an entry under the Unreleased section of the change log in the README.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md.
[x] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #230 into dev will increase coverage by <1%.
The diff coverage is 84%.

@@         Coverage Diff          @@
##            dev   #230    +/-   ##
====================================
+ Coverage    82%    83%   +<1%
====================================
  Files        15     17     +2
  Lines      1333   1405    +72
  Branches     10     10
====================================
+ Hits       1106   1167    +61
- Misses      217    228    +11
  Partials     10     10

@anLopCodez just reaching out to let you know that let me know if I can help in any way. 🙂

@johlju thanks! I'm just going to rework some of the unit tests and then reopen the PR. :)

Cool! Looking forward to it! 🙂


Remove sizes from webmanifest link

closed via https://github.com/userquin/vite-pwa-vitepress-integration/commit/47f859f26d415b705103c605e16a55d96243814b


Upgrade to Gradle 5.3

Should fix issue #18 where gradle-execfork-plugin didn't work with Gradle 5.3
Does this seem sane to you @psxpaul ?

Hey, thanks for doing this! I'll get a new version published later today.

@psxpaul Thanks! Just note that this patch makes the plug-in incompatible with Gradle 5.2 and lower.


polish health check for integrated-test

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #1765 (94fbdbf) into master (39769bf) will decrease coverage by 0.17%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1765      +/-   ##
============================================
- Coverage     62.62%   62.45%   -0.18%
- Complexity     2390     2391       +1
============================================
  Files           482      482
  Lines         10318    10318
  Branches       1043     1043
============================================
- Hits           6462     6444      -18
- Misses         3341     3357      +16
- Partials        515      517       +2

Impacted Files
Coverage Δ

...che/shenyu/sync/data/http/HttpSyncDataService.java
65.04% <0.00%> (-16.51%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
58.94% <0.00%> (-5.27%)
:arrow_down:

...enyu/client/tars/TarsServiceBeanPostProcessor.java
58.10% <0.00%> (+5.40%)
:arrow_up:

Continue to review full report at Codecov.

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


Java8 unstick issue

I suspect that the code generation pattern for Unstick may have been too complicated for the specific constant sizes found in the java8 program failed.
This PR simplifies the pattern for predictive constant patterns.

we should introduce greater for true/false literal for IE, instead of using 1>0.

very good suggestion, will do in a subsequent PR as this one needs to be merged asap.

Jenkins Linux amd64 Build #15767 [push] Java8 unstick issue (#29... started at 18:51

Jenkins Linux ppc64le Build #14798 [push] Java8 unstick issue (#29... started at 20:05

Jenkins Linux s390x Build #15771 [push] Java8 unstick issue (#29... started at 19:53

Jenkins Linux amd64 Build #15767 [push] Java8 unstick issue (#29... passed after 1 hr 19 min

Jenkins Linux s390x Build #15771 [push] Java8 unstick issue (#29... passed after 1 hr 43 min

Jenkins Linux ppc64le Build #14798 [push] Java8 unstick issue (#29... passed after 2 hr 23 min


bug: invalid memory address or nil pointer

Describe the bug
configure --gobin="xxx"
When capturing go app, it reports panic: invalid memory address or nil pointer
To Reproduce
Steps to reproduce the behavior:

./ecapture tls -i enp0s5 -w pcapng.pcap --port=443 --gobin="xxxx"
runing go app
ecapture is stopped by panic

Expected behavior
support gobin completely
Screenshots

Linux Server/Android (please complete the following information):

Env: [run make env to get the environment variables]
OS: [Ubuntu 21.04]
Arch: [amd64]
Kernel Version: [5.15]
Version: [5.15.0-56-generic]

thanks .
but ecapture do not supported capture master key and capture decrypted network packets on gobin. only support capture plaintext on gobin.
maybe supported in the future.


News and Interests Not working and Microsoft Edge new tab content not loading

Hi,
I import some settings from this hardening project and I have been reset all the configurations and import my backup too. But, news and interests it's not working and also microsoft edge stable are not loading the new tab content.
Obs: Edge Canary loading the new tab but the stable didn't load, not sure why :( .
I reset the group policy too but I check the regedit and it seems that some settings it's not removed, could someone try to help me ? I read all the settings that I apply and I'm testing but this is the 2 problems that is taking time to find out. Maybe spotlight is related with this?

And here's the Edge Canary load the content

The hardening list I apply was
finding_list_bsi_sisyphus_windows_10_hd_machine.csv
finding_list_bsi_sisyphus_windows_10_hd_user.csv
finding_list_0x6d69636b_user.csv
finding_list_0x6d69636b_machine.csv
finding_list_cis_microsoft_windows_10_enterprise_2004_machine.csv
finding_list_cis_microsoft_windows_10_enterprise_2004_user.csv
finding_list_microsoft_windows_tls.csv
finding_list_microsoft_windows_tls_future.csv
finding_list_msft_security_baseline_edge_92_machine.csv

I do not recommend using different lists/standards such as my list, CIS and BSI SiSyPHuS on the same system. Sometimes the lists have different targets (e.g. PowerShell) and there may be undesirable side effects.
Now, I suspect it could be one of these user settings:

finding_list_bsi_sisyphus_windows_10_hd_user: ID 110
finding_list_0x6d69636b_user.csv: 4201

If it wasn't one of these settings, I would first find out if it was a machine or user setting. The easiest way to find out if it is a machine or user setting is to create a new profile, and if it works there, then it is a user setting. And then you have to narrow it down.

will create a new user and them check it out

create new user and the edge stable is working

I don't see the news and interest on taskbar, I will restart the computer to take a look on this.

Restart the computer and news and interests not appear in the new user profile created, I'm checking all the settings applied to find a possible cause for the issue.

The News and Interests has it's own config (which is not managed by any the lists yet), maybe it helps to check for this in the registry:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Feeds -> ShellFeedsTaskbarViewMode (2 = disabled)
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Feeds -> EnableFeeds (0 = disabled)

Just to let you know, I added now a setting to the list finding_list_0x6d69636b_machine, but I recommend to disable the setting. So if you use the newest version of the list, you have to correct the setting to 1 (ID 1761).

Check here and EnableFeeds I already change to 1 and ShellFeedsTaskbarViewMode is set to 0

Not sure if this error from Microsoft Store is related, but maybe it is

I'm looking all the settings that have been applied and try to figure out which one cause this issue

I have applied the following settings manually in gpedit.msc

finding_list_bsi_sisyphus_windows_10_hd_user: ID 110
finding_list_0x6d69636b_user.csv: 4201

Also I applied, Internet communication (HKCU and HKLM) and just let not configured the store option and windows update,RSS Feeds and other settings that I have in mind and it seems News and Interests working.
Obs: I make a clean installation of windows to find the cause of the issue, until now nothing. Need to see if the changes made in gpedit.msc will have a different effect in Regedit (using the same settings).


fix: stylelint to webpack error output

Hi!
This is an attempt to fix https://github.com/JaKXz/stylelint-webpack-plugin/issues/102

Remove chalk dep (not used anymore, stylelint already does the coloring)
Add instances of Error to the compilation errors/warnings arrays
Update tests

Closes https://github.com/JaKXz/stylelint-webpack-plugin/issues/102

Coverage decreased (-0.02%) to 98.718% when pulling 060c982ecfe0bfd0ba74e991da87e970dd115ec0 on crash7:fix-stylelint-webpack-error-output into 59904a2d30645c8b50a318d70654c10fc92363ff on JaKXz:master.

@JaKXz thanks for the review! :smile:
re: yarn.lock, chalk is still a dependecy of stylelint itself, that's why the lock is still the same

@JaKXz after a lot of digging, I found that the problem is not related with this plugin nor webpack :tada:
However I couldn't find the right way to create errors/warnings in the doc :disappointed:, I read some comments saying that it should be instances of Error and also checked what some loader plugins (eslint, babel) and found the same, but again, nothing in the docs. Probably because webpack itself supports both things: strings and Error: https://github.com/webpack/webpack/blob/master/lib/Stats.js#L162-L167
Well, turns out I'm also using friendly-errors-webpack-plugin, which inside expects the errors to be an instance of Error here
TL;DR: there isn't an error in the library, but this PR will make this plugin compatible with friendly-errors-webpack-plugin

@crash7 okay that makes sense. I guess I'll have to release this as a feature instead of a patch fix then, since it is new behaviour. Great digging!


Uncaught RuntimeException

I get this error after the command:
$ php seed.php
PHP Fatal error:  Uncaught RuntimeException: Elasticsearch-PHP requires cURL, or a custom HTTP handler. in /home/sy92/Documents/Elastic/Recipe_Search_PHP/examples-master/Search/recipe_search_php/vendor/elasticsearch/elasticsearch/src/Elasticsearch/ClientBuilder.php:185 Stack trace: #0 /home/sy92/Documents/Elastic/Recipe_Search_PHP/examples-master/Search/recipe_search_php/vendor/elasticsearch/elasticsearch/src/Elasticsearch/ClientBuilder.php(452): Elasticsearch\ClientBuilder::defaultHandler() #1 /home/sy92/Documents/Elastic/Recipe_Search_PHP/examples-master/Search/recipe_search_php/data/seed.php(17): Elasticsearch\ClientBuilder->build() #2 {main}   thrown in /home/sy92/Documents/Elastic/Recipe_Search_PHP/examples-master/Search/recipe_search_php/vendor/elasticsearch/elasticsearch/src/Elasticsearch/ClientBuilder.php on line 185

I have similar error:
Fatal error: Uncaught Elasticsearch\Common\Exceptions\BadRequest400Exception: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"The bulk request must be terminated by a newline [\n]"}],"type":"illegal_argument_exception","reason":"The bulk request must be terminated by a newline [\n]"},"status":400} in /Users/dimitaryanakiev/examples-master/Search/recipe_search_php/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php:610

macOS PHP 7.1.12

replace implode("\n", $batchLines); with  implode("\n", $batchLines) . "\n"
hope it will help someone :)

replace implode("\n", $batchLines); with implode("\n", $batchLines) . "\n"
hope it will help someone :)

This solved the issue for me, thank you!

replace implode("\n", $batchLines); with implode("\n", $batchLines) . "\n"
hope it will help someone :)

This solved the issue for me, thank you!

I'm facing the same problem, in which file did you change that line. Thanks in advance for your help.

replace implode("\n", $batchLines); with implode("\n", $batchLines) . "\n"
hope it will help someone :)

This solved the issue for me, thank you!

I'm facing the same problem, in which file did you change that line. Thanks in advance for your help.

seed.php should be the name of the file


delete _gid tracking cookie

When using the analytics.js variant, a _gid cookie is set too:

This PR adds this one to the array of cookie names to be deleted when user hits Reject.

Thanks! :)
I will release it soon.

great, thanks! And thanks for this plugin, lightweight, focused, unobtrusive, and simply does what it says it does, wonderful


Dependabot does not update package.json sometimes

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
yarn
Package manager version
3.3.0
Language version
18.13.0
Manifest location and content before the Dependabot update
/package.json
dependabot.yml content
dependabot.yml
Updated dependency
eslint from 8.31.0 to 8.32.0
prettier from 2.8.2 to 2.8.3
node-fetch from 2.6.7 to 2.6.8
vitest from 0.27.0 to 0.27.1
What you expected to see, versus what you actually saw
Expected: both the manifest (package.json) and lock file (yarn.lock) to be updated
Actual: the manifest file (package.json) was not updated, except for https://github.com/almeidx/translate/pull/63
PS: This has been happening for a while now, but I've been updating the manifest manually in each PR / updated dependencies manually myself
Native package manager behavior
Both the manifest (package.json) and lock file (yarn.lock) are updated
Images of the diff or a link to the PR, issue, or logs
https://github.com/almeidx/translate/pull/59
https://github.com/almeidx/translate/pull/61
https://github.com/almeidx/translate/pull/62
https://github.com/almeidx/translate/pull/64
Smallest manifest that reproduces the issue
No response

Hi @almeidx!
By default, in the case of libraries, Dependabot keeps the existing requirement in the manifest file (package.json here) if the version Dependabot wants to update to satisfies it. For example, in the case of vitest, the latest version (0.27.1) satisfies the requirement in the package.json file (^0.27.0). So, Dependabot keeps the existing requirement in place and only updates the lockfile.
This behavior is fully configurable though, I think the versioning strategy that fits your expectation would be the increase strategy. Have a look at https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file for more information!
I'll close this since I believe this is expected behavior but let me know if something does not square.