text:
Service worker keeps showing 'trying to install' when using app.baseURL under injectManifest strategy

Minimal reproduction
https://github.com/cloydlau/reproduction.git
Keeps showing 'trying to install'

Comparison

✓ remove app.baseURL under generateSW strategy
✓ use app.baseURL under generateSW strategy
✓ remove app.baseURL or set app.baseURL to '/' under injectManifest strategy
✗ use app.baseURL under injectManifest strategy

"pnpm": {
  "overrides": {
    "vite-plugin-pwa": "^0.18.1"
  }
}

can solve it.

repo: vite-pwa/nuxt


text:
Support for outputting multiple formats

Is your feature request related to a problem? Please describe.
Some browsers don't support ES features. So for older browsers is needed system format.
But vite allows to specify only one format. I want to produce two outputs (one for modern browser, one for legacy browser)
Describe the solution you'd like
Change rollupOutputOptions from object to Array. Rollup supports it by default.

Duplicate of #554.

source: gharchive/issue

repo: vitejs/vite

license: MIT

license_type: permissive

license_source: github-api


text:
Pre-bundling is very slow when including ant-design-vue

Describe the bug
As the title says, when I include ant-design-vue, in my tests, it takes about 41.13s, which is very, very slow.

A reproducible project: https://github.com/rxliuli/vite-vue-perf-demo, in fact, I only refer to the Button component
import { createApp } from 'vue'
import App from './App.vue'
import 'ant-design-vue/dist/antd.css'
import { Button } from 'ant-design-vue'

console.log(Button)
createApp(App).mount('#app')

The log is obtained using the following command
pnpm vite --debug --force 2>&1 | tee vite.log

I observed that when the library contains a lot of code like import isPlainObject from 'lodash-es/isPlainObject';, vite goes to every file, which is very, very slow, as you can see from the log @ ant-design/icons-vue appears 104 times, while @ant-design/icons-svg appears 1578 times.
When I tried to rewrite import isPlainObject from 'lodash-es/isPlainObject'; to import { isPlainObject } from 'lodash-es'; using the esbuild plugin, the performance became acceptable (it only took a few seconds) .
My question now is, if there is such a dependency, can vite do some automatic optimizations, in fact echarts/maplibre-gl has a similar problem, or do I need to make separate PRs for these projects?
ref: https://github.com/vitejs/vite/discussions/7857#discussioncomment-3045849
Reproduction
https://github.com/rxliuli/vite-vue-perf-demo
System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz
    Memory: 38.26 GB / 63.87 GB
  Binaries:
    Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.18 - ~\AppData\Local\pnpm\yarn.CMD
    npm: 8.5.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @vitejs/plugin-vue: ^2.3.3 => 2.3.3
    vite: ^2.9.9 => 2.9.13

Used Package Manager
pnpm
Logs

Click to expand!
vite.log

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

On windows Vite v3 is f....king slow. I must to switch back to 2.x. Please do anything to reach the speed of 2.x!

On windows Vite v3 is f....king slow. I must to switch back to 2.x. Please do anything to reach the speed of 2.x!

🤣 But this issue is about vite 2.9.9, not 3.x

@bluwy I'm afraid this also seems to happen on Linux, see following reproduction: https://github.com/brillout/vps-antd-repo.
@rxliuli The culprit doesn't seem to be the pre-bundling scanner (you can inspect it by using the debug flag $ DEBUG=vite:deps vite).

But this issue is about vite 2.9.9, not 3.x

What @hemengke1997 means here is Vite 2 as well: the problem seems to affect both Vite 2 and Vite 3. (The reproduction above uses Vite 3.)

你换个包管理工具试试，我使用pnpm安装的依赖，在冷启动阶段长达1分钟多，我后来换成了npm，发现冷启动快多了，不知道什么问题，其中@ant-design/icons-vue 目前是被rollup全量处理的，可以看下这个issues：https://github.com/vueComponent/ant-design-vue/issues/5822

This issue doesn't seem to be resolved, currently, the cold start speed has been as high as 1min, and vite seems to be no longer available on large projects

problem is not resolved,still, does anyone has any fix for this?

+1 , please fix it .

this seem to occur on my end after adding port -p 5173.

My sveltekit environment
// package.json
{
  "name": "client",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "dev": "vite dev",
    "build": "vite build",
    "preview": "vite preview",
    "check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
    "check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch",
    "format": "prettier --plugin-search-dir . --write .",
    "codegen": "graphql-codegen --config codegen.yml"
  },
  "devDependencies": {
    "@graphql-codegen/cli": "2.15.0",
    "@graphql-codegen/typed-document-node": "^2.3.10",
    "@graphql-codegen/typescript": "2.8.3",
    "@graphql-codegen/typescript-operations": "^2.5.8",
    "@picocss/pico": "^1.5.6",
    "@sveltejs/adapter-auto": "^2.0.0",
    "@sveltejs/kit": "^1.5.0",
    "@types/three": "^0.146.0",
    "prettier": "^2.8.1",
    "sass": "^1.58.3",
    "bootstrap": "^5.2.3",
    "svelte": "^3.54.0",
    "svelte-check": "^3.0.1",
    "tslib": "^2.4.1",
    "typescript": "^4.9.3",
    "vite": "^4.0.0"
  },
  "dependencies": {
    "@urql/exchange-auth": "^1.0.0",
    "@urql/svelte": "^3.0.1",
    "graphql": "^16.6.0",
    "gsap": "^3.11.4",
    "jwt-decode": "^3.1.2",
    "three": "^0.147.0"
  },
  "type": "module"
}```

```jsonc
// vite.config.js
import { sveltekit } from "@sveltejs/kit/vite";
import path from "path";

/** @type {import('vite').UserConfig} */
const config = {
  plugins: [sveltekit()],
  optimizeDeps: {
    exclude: ["@urql/svelte"],
  },

  resolve: {
    alias: {
      $components: path.resolve("./src/components"),
      $lib: path.resolve("./src/lib"),
    },
  },
};

export default config;```

this seem to occur on my end after adding port -p 5173.

My sveltekit environment
// package.json
{
  "name": "client",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "dev": "vite dev",
    "build": "vite build",
    "preview": "vite preview",
    "check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
    "check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch",
    "format": "prettier --plugin-search-dir . --write .",
    "codegen": "graphql-codegen --config codegen.yml"
  },
  "devDependencies": {
    "@graphql-codegen/cli": "2.15.0",
    "@graphql-codegen/typed-document-node": "^2.3.10",
    "@graphql-codegen/typescript": "2.8.3",
    "@graphql-codegen/typescript-operations": "^2.5.8",
    "@picocss/pico": "^1.5.6",
    "@sveltejs/adapter-auto": "^2.0.0",
    "@sveltejs/kit": "^1.5.0",
    "@types/three": "^0.146.0",
    "prettier": "^2.8.1",
    "sass": "^1.58.3",
    "bootstrap": "^5.2.3",
    "svelte": "^3.54.0",
    "svelte-check": "^3.0.1",
    "tslib": "^2.4.1",
    "typescript": "^4.9.3",
    "vite": "^4.0.0"
  },
  "dependencies": {
    "@urql/exchange-auth": "^1.0.0",
    "@urql/svelte": "^3.0.1",
    "graphql": "^16.6.0",
    "gsap": "^3.11.4",
    "jwt-decode": "^3.1.2",
    "three": "^0.147.0"
  },
  "type": "module"
}

// vite.config.js
import { sveltekit } from "@sveltejs/kit/vite";
import path from "path";

/** @type {import('vite').UserConfig} */
const config = {
  plugins: [sveltekit()],
  optimizeDeps: {
    exclude: ["@urql/svelte"],
  },

  resolve: {
    alias: {
      $components: path.resolve("./src/components"),
      $lib: path.resolve("./src/lib"),
    },
  },
};

export default config;

I have no idea why, but this works for me

Hi, I found putting npm packages like @ant-design/icons into optimizeDeps really help. I guess the slow cold start is caused by this mentioned by docs.
optimizeDeps: {
		include: ['@ant-design/colors', '@ant-design/icons', 'lodash-es', '@reduxjs/toolkit', '@ant-design/icons/es/icons'],
	}

Hi @rxliuli
Maybe change your vite.config.ts into this can help https://github.com/vueComponent/ant-design-vue/blob/0a610d818f4583c8cec5afb8d3adb38720f708f4/site/vite.config.ts#L33

authors: IcanPressF Lantianyou Mr-SPM brillout core-admin hemengke1997 martonx rxliuli tastycrayon


text:
fix: prevent error on not set location href

Description
The current implementation of the function cleanScssBugUrl checks if the 'window' and 'location' globals are defined, and then replaces the prefix of the URL with the location href. However, in some cases, the 'location.href' value can be undefined, resulting in an error.
To resolve this issue, I've updated the code to use optional chaining (?.) to ensure that the 'replace' function only runs if 'location.href' is defined. This modification ensures that the function can handle cases where 'location.href' is undefined and prevents errors from being thrown.
This change has been tested and verified to work as expected.

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the PR Title Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Would you give more info about your environment that is triggering this bug? Interesting that we didn't got a report before.

Would you give more info about your environment that is triggering this bug? Interesting that we didn't get a report before.

Unfortunately i can't say too much about it. We use a proprietary package (https://bitmovin.com/). The code is encrypted and therefore the context is hard to see. i can only see in the code that the 'location' object is edited there: typeof location?location:{}}.

source: gharchive/pull-request

authors: mschakulat patak-dev


text:
NavBar for tablet and split screen view

Description
Just a small fix for the navigation bar when in split-screen or tablet view. Previously, the text was overlapping.
Screenshots
Before and After

@frouioui can you give a review?

repo: vitessio/arewefastyet


text:
Custom coverage reporters support

Clear and concise description of the problem
Context: I'm planning to create custom istanbul reporter based on official html reporter.
Problem 1: Custom reporters config error:
Currently vitest allow only official istanbul reporters

However we can override this by disabling typescript check for next line

... and this works pretty good because istanbul is using require() to handle this scenario https://github.com/istanbuljs/istanbuljs/blob/master/packages/istanbul-reports/index.js#L19
Problem 2: No possibility to replace coverage page in @vitest/ui

I would like to use report generated from custom reporter under @vitest/ui coverage page, but seems like currently it's not possible to do.
Suggested solution

Replace

type CoverageReporter = keyof ReportOptions;
// with
type CoverageReporter = keyof ReportOptions | string;

Add necessary logic with following option in vitest config:

export default defineConfig({
+ ui: {
+  enabled: true,
+  coverageReportProvider: 'custom-coverage-reporter' // default "html"
+ },
});

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I think this would be great feature. I'm not yet sure what would be the best way to handle the @vitest/ui part though.  Currently it's simply checking whether reporters includes html reporter.

I created a draft PR: https://github.com/vitest-dev/vitest/pull/4270 could someone take a look and see if this is the right direction?
Custom coverage reporter I'm planning to use: https://github.com/akcyp/coverage-pretty-html-reporter

I have successfully implemented a custom coverage report with Vitest Custom Coverage Provider, see repo: Vitest Monocart Coverage
What's the difference between Custom Coverage Provider and custom reporter support?

What's the difference between Custom Coverage Provider and custom reporter support?

Coverage providers are modules that integrate into Vitest's runtime and setup coverage support. They take care of instrumentation, coverage collection, source maps, etc. Check built-in providers @vitest/coverage-v8 and @vitest/coverage-istanbul for reference.
Coverage reporters are Istanbul compatible reporters. They take istanbul's coverage map and convert that into HTML, JSON, LCOV, Teamcity or any other formats. See built-in reporters from Istanbul for reference: https://github.com/istanbuljs/istanbuljs/tree/master/packages/istanbul-reports/lib.

Thanks for the answer  @AriPerkkio
Is it possible to support the native V8 coverage report? It can show the Bytes coverage directly, see here
for example:
export default defineConfig({
    test: {
        coverage: {
            enabled: true,
            provider: "v8",
            reporter: [
                ["v8-html", { outputDir: "./coverage-reports"} ]
            ]
        }
    }
});

When provider is V8, the v8-html could generate native V8 coverage report without converting to Istanbul.
Basically here is the idea:
// v8-html.js
export default class {
    constructor(options) {
        this.options = options.
        this.coverageList = [];
    }
    onClean() {
      // remove previous report in `this.options.outputDir`
    }
    onCoverageDataCollected(coverageData) {
      // add coverage data
      this.coverageList.push(coverageData);
    }
    onTestEnd() {
      // generate reports with all collected coverage data and save to `this.options.outputDir`
      // return a html link to Vitest UI report
      return reportHtmlPath;
    }
}

If it is implemented, I can easily integrate native V8 Reports with monocart-coverage-reports
Thanks

Is it possible to support the native V8 coverage report?

The @vitest/coverage-v8 provider does not expose the raw V8 Profiler.ScriptCoverage reports. As far as I know there are no published NPM packages that could remap ScriptCoverage to original sources. Vitest, Jest, Playwright and C8 are all converting the results with v8-to-istanbul. Then we can use istanbul-lib-source-maps to remap the coverage using source maps from Vite. Without remapping the coverage would only work for non-transpiled Javascript source files. Anything more complex will show invalid coverage. Due to this reason I don't think we will ever expose raw V8 reports.
With custom coverage provider you can do basically anything. You can collect the V8 coverage and process the raw files yourself as you see fit. Though you'll need to look into how to remap results with source-map or @jridgewell/trace-mapping packages.

What about using custom coverage reporter under @vitest/ui coverage page?

That's not yet supported but there's open PR for it: https://github.com/vitest-dev/vitest/pull/4270

authors: AriPerkkio akcyp cenfun

repo: vitest-dev/vitest


text:
TypeError: actual.match is not a function

Describe the bug
Pre 1.4.0 we were testing promises that were rejected with Error using:
await expect(rejectedPromise).rejects.toMatch(/invalid/);
but now it's throwing:
TypeError: actual.match is not a function
Using toThrow() instead fixes the issue.
I'm not sure if the error is expected but the message is not really helpful.
This is probably related to #5267.
Reproduction
v1.4.0
v1.3.1
System Info
System:
    OS: macOS 14.4.1
    CPU: (12) arm64 Apple M2 Pro
    Memory: 4.16 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.7.2 - /opt/homebrew/bin/node
    Yarn: 1.22.22 - /etc/profiles/per-user/*/bin/yarn
    npm: 10.5.0 - /opt/homebrew/bin/npm
    pnpm: 8.15.5 - /etc/profiles/per-user/*/bin/pnpm
    bun: 1.0.35 - /etc/profiles/per-user/*/bin/bun
  Browsers:
    Chrome: 123.0.6312.107
    Safari: 17.4.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

sorry, for some reason I didn't see #5428 is this possibly already fixed?

sorry, for some reason I didn't see #5428 is this possibly already fixed?
edit: The fix seems to be a more descriptive error, but for our case it is a breaking change since the test was passing in 1.3.1. Not sure if intended.

Yeah, this was fixed but not released yet. 1.5.0 should be released this week.

authors: ShooTeX sheremet-va


text:
Certificate error when running hetzner-k3s: "certificate has expired or is not yet valid"

I am experiencing a problem when trying to run hetzner-k3s using the following command:
hetzner-k3s create --config hetzner-k3s_cluster_config.yaml
In doing so, I receive an error related to an expired or invalid certificate. The full error message is shown below:
`=== Deploying Hetzner drivers ===
Creating secret for Hetzner Cloud token...
Unable to connect to the server: x509: certificate has expired or is not yet valid: current time 2023-03-20T09:21:54+01:00 is before 2023-03-20T08:22:07Z
Failed to create Hetzner Cloud secret:
Unable to connect to the server: x509: certificate has expired or is not yet valid: current time 2023-03-20T09:21:54+01:00 is before 2023-03-20T08:22:07Z
`
Steps to reproduce the problem:

Create a configuration file hetzner-k3s_cluster_config.yaml with the appropriate values.
Execute the command hetzner-k3s create --config hetzner-k3s_cluster_config.yaml.

Additional information:

Version of hetzner-k3s: 1.1.0
Operating system: Distributor ID: Ubuntu, Description: Ubuntu 22.04.1 LTS, Release: 22.04, Codename: jammy

I would appreciate any help in solving this problem.

Yes thanks, I didn't know where the problem came from. After updating the date everything was fine.


text:
🛑 Short Url Service is down

In 8651c6b, Short Url Service (https://go.vikshan.tech) was down:

HTTP code: 502
Response time: 97 ms

Resolved: Short Url Service is back up in 9f85959 after 15 minutes.

repo: vixshan/upptime


text:
Add better support for dynamically sized TabViews

Currently TabViews are mainly oriented towards static bindings and content, making it difficult to interface between tabs and the broader program, and vice versa.
What I'd like to see is

A clear way to create bindings into data contained within a tab, such as for example .thenSelected(Tab::some_data) and .thenSelectedIndex(Tab::some_data, Index).
Some way to direct Events to the currently selected tab within a tabview.
An integrated way to determine which tab in a TabView is currently open.

Some of this is possible to do with the .on_select() callback together with .with_selected(), though it isn't an ideal solution. For example, using the .on_select() callback to set a separate index variable instead of querying the TabView's own selected_index.

I'm not sure I understand what you mean by your first point. What do you mean by data contained within a tab? Typically your data should be in a model, probably further up the tree than the tabview.
Yes it's true that on_select and with_selected moves the managements of the tab index to your own data, but this is intentional as it gives you full control of the selected tab without needing messy events to sync with the internal tabview index.
If you could provide an example scenario of what you're trying to achieve I think that would help me understand what features you need me to add.

repo: vizia/vizia


text:
Update fork of the upstream cookbook

This builds upon the upstream form, adding Upstart init configuration for the twemproxy, plus adds licensing details and updated formatting, etc.

@vkhatri we needed the changes too, so I decided to fork your fork into our organisation and keep maintaining in onwards (as we need this to work too), thank you so much for your work! You are amazing! :+1:

repo: vkhatri/twemproxy

license_source: bigquery


text:
Data preprocessing

Dear author, I have encountered a lot of trouble in data preprocessing. Could you share the preprocessed data? I would appreciate it if I could.

Sorry, we cannot provide the data due to the privacy policy

authors: IceFireCloud cool-sheep


text:
Add columns(Object ... keyValuePairs) method to Row class

Extend com.github.vkorobkov.jfixtures.domain.Row class with a new method:
public Row columns(Object... keyValuePairs)

The usage of this method will be:
row.columns(
  "name", "Vlad",
  "age", 30,
  "hobby", "sleeping"
);

So the method should:

Elements order should be preserved and tested. So use LinkedHashMap internally
Check that keyValuePairs.length % 2 == 0, otherwise, it should throw IllegalArgumentException
Every odd(1, 3, ...) object is column name and should be checked with instanceof String, otherwise, an IllegalArgumentException should be thrown
Every even(2, 4, ...) object is a column value
Method should convert input array into Map<String, Object> and then should call com.github.vkorobkov.jfixtures.domain.Row#columns(Map<String, Object> toMerge) from https://github.com/vkorobkov/jfixtures/issues/153

PR https://github.com/vkorobkov/jfixtures/pull/158

https://github.com/vkorobkov/jfixtures/pull/158 merged

authors: rodionovsasha vkorobkov

repo: vkorobkov/jfixtures

license: mit


text:
Fix issue #111

program.name is already a function (or should I say that name is a method of the program object?), then it can't be used as a variable.
(program.name() outputs chromeos-apk in this case, for the sake of completeness.)
So, using commander, if you set the long option name to --ext-name, it gives you the property extName of the object program (that is not taken). (If I am right with the OOP lingo.)

Thanks!

repo: vladikoff/chromeos-apk


text:
Repository structure

[x] Need 1-2 page README file (dependencies, environment and requirements, howto, etc.)
[x] Do you use linter?
[x] Is it ok to commit __pycache__ to repo?
[x] Will be great to have CI, for example https://travis-ci.org/ it's easy to setup and free for open source projects

All troubles have solved, i used pylint as linter, deleted pycache, and signed up on travis ci

authors: tshemsedinov vladlinu

repo: vladlinu/Voicy


text:
Update dotnetcore branch with latest develop

Update the branch to the latest develop branch from cake official repo

Closing the PR as this is already merged and release a long time ago...

authors: phenixdotnet vlesierse

repo: vlesierse/cake


text:
The model to consider.
https://huggingface.co/fishaudio/fish-speech-1.4
the githup repo:
https://github.com/fishaudio/fish-speech
Part of this code architecture is a standard transformer . (embeds ? how to integrate) The other part is vgan - fsq  Using existing VLLM layers It seems difficult to support using existing VLLM layers.
https://github.com/fishaudio/fish-speech/blob/main/fish_speech/models/text2semantic/llama.py
https://github.com/fishaudio/fish-speech/blob/main/fish_speech/models/vqgan/modules/firefly.py
The closest model vllm already supports.
No response
What's your difficulty of supporting the model you want?
No response
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

The only issue  is the fish tts use FSQ, which output a tuple (int, int) for each step.
But unfortunately  this break the fundamental design of vllm: it hard code the output to a single INT
I request this  in https://github.com/vllm-project/vllm/issues/9006#issuecomment-2475332550
but seems no response so far...

@niuzheng168 chattts seems to have already integrated vllm and its faster than before. Can we leverage that code for fish? Or is the problem specific to the fish tts?

authors: cavities karndeb niuzheng168

repo: vllm-project/vllm


text:
How to configure which GPU to use

there is no config parameter to configure which GPU to use,it always to find GPU:0
I want to change the GPU number,what should i do ?
PS : i used os.environ["CUDA_VISIBLE_DEVICES"] = "3" but it also to run on GPU:0

Try using NVIDIA_VISIBLE_DEVICES.

I also need a "device_map" argv to config this like HF.
Not sure why there is no such argv...

You must set CUDA_VISIBLE_DEVICES=3 outside your script, setting it inside might be too late.


text:
[Misc] Split up pooling tasks

Part of #10674

cc @russellb re: the docs

@Isotr0py would be great if you could review this as well!


text:
[V1] Fix multimodal profiling

#11187 introduced a change that breaks #11210. The issue was previously missed because the two PRs were merged into main around the same time.

Closing as superseded by #11305

Closing as superseded by #11305

Oh neat! I didn't see that PR actually fixed this already.


text:
asn1c: Decoding long fixed-length OCTET STRING fails

Hey,
I've discovered an issue in decoding an APER-encoded long fixed-length OCTET STRING. The problem seems to be in the handling of the align bits for lengths > two octets. Commenting out that check (see last commit in the example below hides the issue). After looking at the appropriate section in X.691 I am unsure about the correct way of handling it though. I've compiled a small example here that shows the issue. It only decodes the message correctly with the changes mentioned above.
I am using the Mouse07410's asn1c fork for generating the code (but all other APER-enabled forks seem to have the same or similar code).
Would be nice if some of the experts could comment on this issue. Let me know if you need anything else.
Thanks
Andre

Unfortunately, your example is 2800+ files - infeasible to track.
Could you point at a specific line (or a few lines) in the asn1c code that appears to cause problems, and the exact fix that appears to remedy the situation?

@mouse07410 its in skeleton/OCTET_STRING.c  https://github.com/andrepuschmann/asn1c_test_mini/commit/6dce9f82e3dfd0a0160ecff3f9f1f86b053ef3f5
Page 27
https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-X.691-201508-I!!PDF-E&type=items
will look at it during the weekend

@ikarso thank you for looking into this. PER is not the easiest thing to get right. Your help would be greatly appreciated.
@andrepuschmann can you try branch 115 of my fork, and tell us if it exhibits the same problem?

Hi @andrepuschmann,
Are you sure that the sib1_payload_tx contains a valid message?
I was not able to decode it using wireshark, oss and marben online tools. It seems to be truncted

I trust OSS tools.

Hi @andrepuschmann,
From 3GPP TS 36.331 version 13.3.0 Release 13

Transfer syntax for RRC PDUs is derived from their ASN.1 definitions by use of Packed Encoding Rules, unaligned as specified in ITU-T Rec. X.691 [15].

Right now you are using aper_decode but you should use uper_decode instead. After changing it your test succeed.
./asn1test_mini
Buffer size:208
Consumed 160 bits.
BCCH-DL-SCH-Message-NB ::= {
    message: SystemInformationBlockType1-NB ::= {
        hyperSFN-MSB-r13: DD
        cellAccessRelatedInfo-r13: cellAccessRelatedInfo-r13 ::= {
            plmn-IdentityList-r13: PLMN-IdentityList-NB-r13 ::= {
                PLMN-IdentityInfo-NB-r13 ::= {
                    plmn-Identity-r13: PLMN-Identity ::= {
                        mcc: MCC ::= {
                            2
                            1
                            4
                        }
                        mnc: MNC ::= {
                            0
                            1
                        }
                    }
                    cellReservedForOperatorUse-r13: 1
                }
            }
            trackingAreaCode-r13: 02 18
            cellIdentity-r13: 14 37 43 E0
            cellBarred-r13: 1
            intraFreqReselection-r13: 0
        }
        cellSelectionInfo-r13: cellSelectionInfo-r13 ::= {
            q-RxLevMin-r13: -68
            q-QualMin-r13: -23
        }
        freqBandIndicator-r13: 20
        eutraControlRegionSize-r13: 2
        nrs-CRS-PowerOffset-r13: 4
        schedulingInfoList-r13: SchedulingInfoList-NB-r13 ::= {
            SchedulingInfo-NB-r13 ::= {
                si-Periodicity-r13: 3
                si-RepetitionPattern-r13: 1
                sib-MappingInfo-r13: SIB-MappingInfo-NB-r13 ::= {
                }
                si-TB-r13: 4
            }
            SchedulingInfo-NB-r13 ::= {
                si-Periodicity-r13: 5
                si-RepetitionPattern-r13: 1
                sib-MappingInfo-r13: SIB-MappingInfo-NB-r13 ::= {
                    0
                }
                si-TB-r13: 0
            }
        }
        si-WindowLength-r13: 4
        systemInfoValueTagList-r13: SystemInfoValueTagList-NB-r13 ::= {
            3
            2
        }
    }
}

Hi @velichkov,
very good catch! I must have overlooked that, thanks for spotting this stupid mistake I made. That's also why removing the code handling the alignment made it work ;-)
Thanks everyone

I mark the issue closed as also mainline asn1c decodes it correctly. Thanks again.

authors: andrepuschmann ikarso mouse07410 velichkov


text:
Update sbt-twirl to 1.6.0

About this PR
📦 Updates com.typesafe.sbt:sbt-twirl from 1.5.1 to 1.6.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.sbt", artifactId = "sbt-twirl" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.typesafe.sbt", artifactId = "sbt-twirl" }
}]

labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #144.


text:
Add comment not to use 'latest' in docs

Description
Add a comment to the docs explaining to the user not to use latest' as per request from @ciberkleid in #2977.
Hey @ciberkleid there's a few reasons we keep latest out of sync and only for development.
From @joshrosso  in #2977
Without going into all of them, the primary limitation is how our hosted-harbor instance caches the :latest tag at the CDN level. It leads to non-deterministic resolution of :latest as it can resolve to different underlying images depending on the region of the world you are in. For this reason and a few others, we highly recommend not using latest for resolving the TCE package reposioty.
From @ciberkleid in #2977
I would turn this into a documentation request... I think it would be helpful if the docs were explicit about discouraging the use of latest and providing info on where to verify what the latest version is. If other users are like me, the question will come up in their minds when they come to that section of the docs (point 2 above), so it would be good to have the answer there and save the user the doubt and discovery effort.
Location

Additional Context

@ciberkleid
Hi Cora
The version is kept dynamically up to date in multiple locations in the doc. Is the ask here to add a note in each of these locations to not use latest -as I think this could get clunky ?
The version (dynamic) appears in these topics:
Work with Packages
https://tanzucommunityedition.io/docs/latest/package-management/
Installing a Package in the Getting Started guide
https://tanzucommunityedition.io/docs/latest/getting-started/#installing-a-package
Tanzu Community Edition Installation in the Getting Started guide for Windows, Mac, and Linux
https://tanzucommunityedition.io/docs/latest/getting-started/#tanzu-community-edition-installation

Moving to icebox until we get follow-up. Thanks!

Hi, sorry... this got lost in my inbox :(
Yeah, I think it's very common to assume you can use latest and if we
cannot ensure that the image tagged latest is safe for use, then we
should make a concerted effort to be really clear about it.
On Fri, Mar 4, 2022 at 3:24 PM joshrosso @.***> wrote:

Moving to icebox until we get follow-up. Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/vmware-tanzu/community-edition/issues/2977#issuecomment-1059497242,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFAZ27T5XLFY7IHR4OJBLU6JWRBANCNFSM5NGSRSHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks @ciberkleid!
Would you be interested in making the contribution to our docs?
For now, we'll leave this as help wanted in hopes it'll get picked up from someone.
Thanks!

authors: ciberkleid joshrosso kcoriordan

repo: vmware-tanzu/community-edition


text:
Quick switcher filtering broken when not using Chrome

What steps did you take and what happened:
Ctrl+Enter (opens quick switcher)
begin typing .. the list shows no matches instantly and never returns any matches
What did you expect to happen:
Expect the list to filter to items matching what I type.
Environment:

Octant version (use octant version): master
Browser:

WORKS: Chrome Version 83.0.4103.61 (Official Build) (64-bit)
NO: Microsoft Edge 44.19631.1.0
NO: Chromium 81.0.4044.138 (Official Build) (64-bit)
NO: Firefox 76.0.1 (64-bit)

I can actually get the quick switcher to break in every browser just by using it a few times. I haven't identified the pattern that causes it yet and there is no useful info in the console.

This seems to have gone away for me.

repo: vmware-tanzu/octant


text:
WIP: Prototype to provide user-defined upsteam-to-downstream identity transformations/filters via Starlark functions

Why consider using Starlark for custom user-defined upsteam-to-downstream identity transformations/filters?

Starlark is implemented in Go by Google and they use it internally extensively for their build system, so we can expect it to be well supported. Google is also very conservative about allowing any language definition changes, so the language is stable.
The language is very well documented. See https://github.com/google/starlark-go/blob/master/doc/spec.md
Python-like syntax is understandable to any programmer, even to someone who has never used Python
Scripts can define functions, use “if” statements and “for” loops, use built-in types like string, tuple, dict, list, set, etc.
Starlark is simple and runs deterministically: no classes, no threads, no random numbers, no clock (can optionally expose the time lib), stable iteration order, etc.
Designed to be hard to write scripts which do not terminate (e.g. no while loops)
Effectively sandboxed, even though it runs in the same address space:

Scripts cannot do any IO
Can limit the number of abstract computation “steps” that are allowed (limiting CPU usage, roughly limiting time)
Can also cancel using a context (e.g. apply a timeout)
Cannot limit memory usage, unfortunately, but that seems okay for our use case where only administrators would write scripts

Starts interpreter and runs functions in several microseconds, so performance would be excellent
Safe to run many interpreters at the same time on the same loaded module/function (thread-safety is guaranteed)
Functions can be called from golang and passed arguments, including passing complex types (with attributes defined in Go) as arguments, and can get back return values
Libraries can be pre-defined and offered for use in the user-defined Starlark source, for example we could define common helper functions if we wanted
Can run scripts using a golang or a CLI, so could easily provide a simple test framework for script authors to be able to TDD their scripts if we wanted
Supports UTF-8 strings
The Starlark Print() method can be attached to our logging system to allow scripts to debug log

Release note:
TBD

Oops, I meant to base this branch on main. I'll close this and open a new PR.

repo: vmware-tanzu/pinniped


text:
Collapsed state vertical nav icons doesn't have textual representation

Clarity Version: 3.1.1
WCAG 2.1 Guideline:  3.3.2 (Labels or Instructions)
Test Environment:

Test URL: https://clarity.design/documentation/vertical-nav/basic-structure/project-pokemon
OS: Windows 10
User Agents/Assistive Technologies: Firefox 76.0
Screen reader: NVDA 2020.1

Steps to reproduce:

Open the test URL.
Go to the collapsible vertical nav which have icons, collapse that nav and check if user can see any tooltip for the focused clickable icon.

Expected result:

In collapsed state if the vertical nav shows the visual icons of the nav menu items then the icons should have tooltip for describing actual menu item in a single focus i.e tooltip should be displayed when overall icon is focused, so that all users can understand the purpose of navigation menu items clearly.
Also, ensure that visual tooltip matches the accessible name used in aria-label. Note: Tooltip should not be announced in expanded state to avoid redundant announcement of the menu item for screen reader users.
Implemented tooltips should be available with mouse hover as well as with keyboard interaction. Keyboard event handlers needs to be added in addition to the mouseover event handlers which trigger the tooltips.

Actual result:
Tooltip is missing for visual icons. So users might not be able to use the collapsed state icons effectively.
In addition to that, Expand (>>) or Collapse (<<)  Toggle Navigation Menu button  visual tooltip is different than the accessible label.
User Impact:
https://www.w3.org/TR/WCAG20-TECHS/F82.html

This could also be fixed by using .clr-sr-only for the routing link text when the nav is collapsed rather than using display:none.

Hi there, this is an automated message.
In an effort to dedupe and track accessibility reports consistently, this issue is being closed and tracked internally with our Accessibility team. It will still be triaged and addressed as part of ongoing work.

authors: chlane gkhadK gnomeontherun

repo: vmware/clarity


text:
为什么harbor 集群方案不在roadmap里面了

If you are reporting a problem, please make sure the following information are provided:
1)Version of docker engine and docker-compose
2)Config files of harbor, you can get them by packaging "Deploy/config" directory
3)Log files, you can get them by package the /var/log/harbor/

Which cluster plan is not in ROADMAP? Did you mean the HA features here: #327

No activity for a long time. Closing it for now. Please reopen if needed.

repo: vmware/harbor


text:
Document update-spaces-metadata

Is your feature request related to a problem? Please describe.
Initial support for cf-mgmt update-spaces-metadata was added for #171 / v1.0.26, but there does not appear to be any corresponding documentation for this command in the docs/ folder.
Describe the solution you'd like
The creation of documentation to support the cf-mgmt update-spaces-metadata command, describing what it does and its usage in a similar matter to the existing docs for e.g. cf-mgmt update-space-quotas
Describe alternatives you've considered
N/A
Additional context
I've been investigating space and org metadata, and was initially confused by cf-mgmt update-spaces as I was expecting it to handle updating space metadata as well, rather than only managing the allow_ssh property. Missing documentation meant I had to dive into the source code to discover how metadata updates are applied.

Hi and thank you for noticing the undocumented command. This is important for me to get documented. I'll ensure this gets addressed this month. Thank you for your patience - apologies for the lack of engagement on the issue.

authors: Petahhh crustst

repo: vmwarepivotallabs/cf-mgmt


text:
vn.Trader文件夹中的ctaAlgo文件夹中的ctaBacktesting.py中的crossStopOrder函数限价单和停止单混淆

#----------------------------------------------------------------------
def crossStopOrder(self):
"""基于最新数据撮合停止单"""
# 先确定会撮合成交的价格，这里和限价单规则相反
if self.mode == self.BAR_MODE:
buyCrossPrice = self.bar.high    # 若买入方向停止单价格低于该价格，则会成交
sellCrossPrice = self.bar.low    # 若卖出方向限价单价格高于该价格，则会成交
bestCrossPrice = self.bar.open   # 最优成交价，买入停止单不能低于，卖出停止单不能高于
else:
buyCrossPrice = self.tick.lastPrice
sellCrossPrice = self.tick.lastPrice
bestCrossPrice = self.tick.lastPrice
    # 遍历停止单字典中的所有停止单
    for stopOrderID, so in self.workingStopOrderDict.items():
        # 判断是否会成交
        buyCross = so.direction==DIRECTION_LONG and so.price<=buyCrossPrice
        sellCross = so.direction==DIRECTION_SHORT and so.price>=sellCrossPrice

        # 如果发生了成交
        if buyCross or sellCross:
            # 推送成交数据
            self.tradeCount += 1            # 成交编号自增1
            tradeID = str(self.tradeCount)
            trade = VtTradeData()
            trade.vtSymbol = so.vtSymbol
            trade.tradeID = tradeID
            trade.vtTradeID = tradeID

            if buyCross:
                self.strategy.pos += so.volume
                trade.price = max(bestCrossPrice, so.price)
            else:
                self.strategy.pos -= so.volume
                trade.price = min(bestCrossPrice, so.price)

            self.limitOrderCount += 1
            orderID = str(self.limitOrderCount)
            trade.orderID = orderID
            trade.vtOrderID = orderID

            trade.direction = so.direction
            trade.offset = so.offset
            trade.volume = so.volume
            trade.tradeTime = str(self.dt)
            trade.dt = self.dt
            self.strategy.onTrade(trade)

            self.tradeDict[tradeID] = trade

            # 推送委托数据
            so.status = STOPORDER_TRIGGERED

            order = VtOrderData()
            order.vtSymbol = so.vtSymbol
            order.symbol = so.vtSymbol
            order.orderID = orderID
            order.vtOrderID = orderID
            order.direction = so.direction
            order.offset = so.offset
            order.price = so.price
            order.totalVolume = so.volume
            order.tradedVolume = so.volume
            order.status = STATUS_ALLTRADED
            order.orderTime = trade.tradeTime
            self.strategy.onOrder(order)

            self.limitOrderDict[orderID] = order

            # 从字典中删除该限价单
            del self.workingStopOrderDict[stopOrderID]

以上是撮合停止单的函数，但是函数里面停止单成交后limitOrderCount 限价单计数器加1，又使用limitOrderDict限价单字典加入停止单的订单。这里的写法是不是错了？！如果没错，那么这样写很容易让人误解啊，本来限价单和停止单的概念就比较容易混淆，这里的变量命名让人看代码更容易混淆！

本地停止单在是盘中是一个运行在本地程序中的条件委托，当价格到达后会被立即触发并发出一个限价单，然后在市场上成交
回测中为了模拟和实盘相同的效果，所以需要采用你之前提出的逻辑

撮合限价单的函数主要是从workingLimitOrderDict里遍历，撮合成功后，就从workingLimitOrderDict里删除；
撮合停止单的函数主要是从workingStopOrderDict里遍历，撮合成功后，就从workingStopOrderDict里删除；函数里面停止单成交后limitOrderCount 限价单计数器加1，又使用limitOrderDict限价单字典加入停止单的订单，看起来目的只是保存触发停止单成交的委托报单。。。
LimitOrderDict和stopOrderDict目前看起来只是模拟和实盘相同的效果，起存档作用（相当于实盘里面的所有委托报单日志），并不会对回测结果有影响。。。

楼上正解

authors: akeyong vnpy zhangshuiyong

repo: vnpy/vnpy


text:
在编译测试和生产版本的CTP库的项目时候，出现的问题

环境

操作系统: 如Windows 10
Python版本: Python3.7
vn.py版本: master 分支 下载日期 2020110（下载日期）

Issue类型
Question
预期程序行为
我打算了解一下VNPY对CTP库的封装，对./vnpy/vnpy/api/ctp目录下的visual studio 项目进行重新编译，生成一个测试版本的CTP库和正式版本的CTP库。
实际程序行为
我整理出来了./vnpy/vnpy/api/ctp目录下的visual studio项目
依据 项目--》重定解决方案  ，将项目的Windows SDK版本制定到 10.0.17763.0
配置了 项目--> 属性--->  配置属性---> c/c++--->常规 ---> 附加包含目录 ,

旨在为vnpyc\include\pybind11\detail\common.h添加<Python.h>文件，

但是实际的编译结果确实这样的

我哪里出现错误，我应该如何解决这些问题？

在项目的配置中，请添加你的Python环境目录，包含Include Path和Reference Path等

authors: huluBrother vnpy


text:
acme server: eliminate annoying request logging

Motivation
Current architecture
on each acme server request: 11/06 15:36:37.576: ---: [router.Provide.func1:77]: acme server request: GET 167.235.218.152 10.0.0.2:41270 / /

Significant Problem (warm): annoying + DataDog cost

Technical design
eliminate logging

done already in #2749

repo: voedger/voedger


text:
MySql not working - shows "Failed to find or load the registered .Net Framework Data Provider." error

Hello,
i did all steps mention in "https://github.com/volkanceylan/serenity-guide/blob/master/mysql.md" this URL.
i am able to see tables in serenity code generator dialog and it generate all files as well.
but when i run it shows error  "Failed to find or load the registered .Net Framework Data Provider." please see attach screen show

facing issue in sqlErrorStore.cs file when it check SqlConnections.GetFactory(this.providerName);
Please let me know how to fix this issue?

Install provider in your project, check .net docs and provider docs.

I am getting similar error. I followed the guide https://github.com/volkanceylan/serenity-guide/blob/master/mysql.md
Error details in the screenshot:

Apparently, i needed to install MySQL connector for .NET
https://dev.mysql.com/downloads/connector/net/6.10.html

repo: volkanceylan/Serenity


text:
Serialport.list failure on openwrt (/bin/sh: /sbin/udevadm: not found)

Re: https://github.com/voodootikigod/node-serialport/blob/c670840c03ffdce56f52aa65ee0be8ee46313403/serialport.js#L586
Running the following from a Tessel 2:
var sp = require("serialport");

sp.list((error, ports) => {
  if (error) {
    console.log(error);
    return;
  }

  console.log(ports);
});

{ [Error: Command failed: /bin/sh -c /sbin/udevadm info --query=property -p $(/sbin/udevadm info -q path -n /dev/ttyS0)
/bin/sh: /sbin/udevadm: not found
/bin/sh: /sbin/udevadm: not found
]
  killed: false,
  code: 127,
  signal: null,
  cmd: '/bin/sh -c /sbin/udevadm info --query=property -p $(/sbin/udevadm info -q path -n /dev/ttyS0)' }

I'll keep digging, maybe I can find some useful info to help out with this.

The t2 doesn't seem to ship with it, but openwrt does.

If udevadm doesn't exist, then we need to make it exist.

This is the output after installing udev
[ { comName: 'ttyS0',
    manufacturer: undefined,
    serialNumber: undefined,
    pnpId: undefined,
    vendorId: '0xundefined',
    productId: '0xundefined' },
  { comName: 'ttyS1',
    manufacturer: undefined,
    serialNumber: undefined,
    pnpId: undefined,
    vendorId: '0xundefined',
    productId: '0xundefined' } ]

That was with nothing attached. This is with something attached:
[ { comName: 'ttyACM0',
    manufacturer: undefined,
    serialNumber: undefined,
    pnpId: undefined,
    vendorId: '0xundefined',
    productId: '0xundefined' },
  { comName: 'ttyS0',
    manufacturer: undefined,
    serialNumber: undefined,
    pnpId: undefined,
    vendorId: '0xundefined',
    productId: '0xundefined' },
  { comName: 'ttyS1',
    manufacturer: undefined,
    serialNumber: undefined,
    pnpId: undefined,
    vendorId: '0xundefined',
    productId: '0xundefined' } ]

I am running into the same issue.  Any instructions on getting udev on the t2?

authors: bbeers rwaldron

repo: voodootikigod/node-serialport


text:
Setup failed for porthutv: integration not found

Version of the custom_component
 v1.0.5
Configuration

## System Health

version | core-2021.6.2
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
virtualenv | false
python_version | 3.8.9
os_name | Linux
os_version | 5.4.83-v7
arch | armv7l
timezone | Europe/Budapest

Home Assistant Community Store

GitHub API | ok
-- | --
Github API Calls Remaining | 4873
Installed Version | 1.12.4
Stage | running
Available Repositories | 823
Installed Repositories | 18

Home Assistant Cloud

logged_in | true
-- | --
subscription_expiration | June 17, 2021, 2:00 AM
relayer_connected | true
remote_enabled | true
remote_connected | true
alexa_enabled | true
google_enabled | false
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | failed to load: timeout

Home Assistant Supervisor

host_os | Home Assistant OS 5.13
-- | --
update_channel | stable
supervisor_version | supervisor-2021.05.4
docker_version | 19.03.15
disk_total | 13.9 GB
disk_used | 8.7 GB
healthy | true
supported | true
board | rpi3
supervisor_api | ok
version_api | ok
installed_addons | Samba share (9.5.0), Duck DNS (1.12.5), Mosquitto broker (6.0.1), File editor (5.3.1), SSH & Web Terminal (8.2.3), MariaDB (2.3.0), WireGuard (0.5.1), Zigbee2mqtt Edge (edge), ESPHome (1.18.0), Simple Scheduler (0.22)

Lovelace

dashboards | 4
-- | --
resources | 8
views | 18
mode | storage

Describe the bug
A clear and concise description of what the bug is.
The integration fails to start, the entities are unavailable.
Debug log

Logger: homeassistant.setup
Source: setup.py:172
First occurred: 7:20:57 AM (1 occurrences)
Last logged: 7:20:57 AM

Setup failed for porthutv: Integration not found.

Thanks for reporting!
This issue was fixed in #15, please update to v1.0.6

Thank you.

repo: vorostamas/portHuTV-homeassistant


text:
"onhello rejected the promise" for the first time when leaving thruway running for a long time

I left Thruway running for about 12 hours with a client connected. When I came back, the connection was dead, so I tried reconnecting. Every time it failed and the following was displayed in the log:
[router 0 8347] 2016-05-27T14:00:08.0263060 error      [Thruway\Authentication\AuthenticationManager 8347] onhello rejected the promise

After restarting Thruway the issue went away.

@cristiano-di-buduo are you using MySQL to authenticate the user?

Yes I am. I'm using the Symfony ThruwayBundle and inject '@doctrine.orm.entity_manager' into the  user provider service.

I added the following to the UserProvider (before the loading of the User object):
$this->em->getConnection()->connect();

This will do nothing and return false if a connection is already there, otherwise it will reconnect and return true.
I'm hoping this will resolve it, I will know tomorrow and post my findings here.

An update to this story:
After 9+ hours I tried to connect a client to the still running router, this time with the forementioned modification.
$this->em->getConnection()->connect() returned false, which means the connection was still open, and the promise was rejected anyway. This makes me believe it's not a Doctrine related issue, or I'm not getting something.
Penny for your thoughts.

It's most likely related to the mysql connection timing out.

@davidwdan I can confirm your suspicion was correct. The culprit was the wait_timeout global variable of mySQL, which I set to 120 for debugging purposes.
The following snippet solved the problem (in part):
if(!$this->em->getConnection()->ping() || !$this->em->isOpen()) {
    $this->em = $this->registry->resetManager();
}

This effectively replaces the EntityManager with a new one that connects upon construction. But that only solved the problem in part, because: on my test page, i have connect/disconnect/subscribe etc. buttons. When I hit "connect" after the timeout occurs, the following is shown in the log:
[worker6667 0 5450] 2016-05-30T02:22:17.8871070 info       [Thruway\Transport\PawlTransportProvider 5450] Pawl has closed
[worker6667 0 5450] 2016-05-30T02:22:17.8872460 info       [Thruway\Transport\PawlTransportProvider 5450] Starting Transport
[worker6667 0 5450] 2016-05-30T02:22:17.8878940 info       [Thruway\Transport\PawlTransportProvider 5450] Could not connect: Connection refused
[worker6667 0 5450] 2016-05-30T02:22:20.1374270 info       [Thruway\Transport\PawlTransportProvider 5450] Starting Transport
[worker6667 0 5450] 2016-05-30T02:22:20.1394520 info       [Thruway\Transport\PawlTransportProvider 5450] Pawl has connected
[worker6667 0 5450] 2016-05-30T02:22:20.1406980 debug      [Thruway\Transport\PawlTransportProvider 5450] Received: [2,4629718147941435,{"authid":"anonymous","authmethod":"internalClient","authrole":"admin","authroles":["admin","authenticated_user"],"roles":{"broker":{"features":{"subscriber_blackwhite_listing":true,"publisher_exclusion":true,"subscriber_metaevents":true}},"dealer":{"features":{"caller_identification":true,"progressive_call_results":true}}}}]
[worker6667 0 5450] 2016-05-30T02:22:20.1407650 debug      [Thruway\Peer\Client 5450] Client onMessage: [Thruway\Message\WelcomeMessage]
2016-05-30T02:22:20.1407790 info       [Thruway\Peer\Client 5450] We have been welcomed...
[worker6667 0 5450] 2016-05-30T02:22:20.1422880 debug      [Thruway\Transport\PawlTransportProvider 5450] Received: [33,2038548241962965,3218057976925114]
2016-05-30T02:22:20.1423210 debug      [Thruway\Peer\Client 5450] Client onMessage: [Thruway\Message\SubscribedMessage]
[worker6667 0 5450] 2016-05-30T02:22:20.1424000 debug      [Thruway\Transport\PawlTransportProvider 5450] Received: [65,7202816656928196,2038313313028200]
[worker6667 0 5450] 2016-05-30T02:22:20.1424280 debug      [Thruway\Peer\Client 5450] Client onMessage: [Thruway\Message\RegisteredMessage]
2016-05-30T02:22:20.1424490 info       [Thruway\Role\Callee 5450] Setting registration_id for talk (0)

Where worker6667 is a @Worker process I have defined and talk() is a remote procedure within that process. The autobahn client responds with "connection lost". However, hitting "connect" a second time does result in a connection and everything works again. Any subsequent disconnect/connect presses no longer display anything in the log, until the mySQL connection times out again.
What causes the Pawl to close on a connection request? Why is the connection refused the first time? And why is talk() being registered again?

Shall I open another issue for this? I have no idea what's going on here...

There are two open issues about this on the thruwaybundle page:
https://github.com/voryx/ThruwayBundle/issues/46
https://github.com/voryx/ThruwayBundle/issues/66

Closing this issue due to inactivity.

authors: cristiano-di-buduo davidwdan mbonneau valepu

repo: voryx/Thruway


text:
readers: getline() -> tools::getline()

This is remove windows line endings, see
https://groups.google.com/g/votca/c/OSrrvJaYOqk/m/7UuSBJ0rAwAJ
for a related issue report.
Fix #613

@votca-bot copyright

@votca-bot format

repo: votca/csg


text:
stage rider table should store complete destination address

On the rider form, there would be a polling station address finder.
The complete destination address should be stored in the database
impacts node.js app and possibly sweeper app.

Obsolete, the form now has a pick up address and a drop off address field

repo: voteamerica/backend


text:
Matches drivers by org

Operator page drivers and matches tables show only rows for the logged-in operator's organisation, except in one situation
Schema inserts now specify a uuid for each default organization row (uuids are taken from existing rows)
Have fixed alter and grant statements parameters for submit_new_rider functions
Dev/test users given an org uuid

@dmilet I've merged this without a review as the db changes/patches are minor and don't need deployment. Any comments or refactors are welcome, though


text:
[FR] Persist zoom and pan in expanded view

Proposal Summary
While navigating samples in expanded view, the labels are shown on top-left, which is nice. However, when the mouse is on the image, they are shaded. The top-most one gets almost invisible.
Motivation

What is the use case for this feature?

Navigating samples in expanded view while easily reading their labels

Why is this use case valuable to support for FiftyOne users in general?

Seeing the labels is a highly valuable necessity when using the GUI.

Why is this use case valuable to support for your project(s) or
organization?

I will be able to follow the sample labels while navigating my samples in Fiftyone.

Why is it currently difficult to achieve this use case? (please be as
specific as possible about why related FiftyOne features and components are
insufficient)

I cannot see what is behind when the label is shaded with a black strip.
What areas of FiftyOne does this feature affect?

[x] App: FiftyOne application
[ ] Core: Core fiftyone Python library
[ ] Server: FiftyOne server

Details

Some minor UI tweaks are likely to solve this problem (according to @ehofesmann)

Willingness to contribute
The FiftyOne Community encourages new feature contributions. Would you or
another member of your organization be willing to contribute an implementation
of this feature?

[ ] Yes. I can contribute this feature independently.
[ ] Yes. I would be willing to contribute this feature with guidance from
the FiftyOne community.
[x] No. I cannot contribute this feature at this time.

https://user-images.githubusercontent.com/99868596/196111695-6e42bb70-683f-4887-b176-c1598ddc4ee8.mp4

Hi @oguz-hanoglu. Note that you can zoom out and so the label(s) are not covered.

Hi @benjaminpkane, zoom out is a valid but not practical solution. My use case is navigating the samples, for that I constantly press right arrow and analyze the outputs. To activate the right arrow, cursor needs to be on the image and this triggers shadow.

As a solution, zoom can persist when moved to next sample by right arrow.

As a solution, zoom can persist when moved to next sample by right arrow.

It's a good idea. I will investigate

This is still very much needed.
--- ChatGPT version below :)
This particular enhancement is still very much needed and I believe it could greatly improve the user experience of your tool. Its implementation could open up new possibilities in our workflow and further solidify FiftyOne as a leader in its field. I understand that your team might be occupied with other tasks, but I just wanted to emphasize the continued importance of this request. I'm looking forward to seeing this feature being added in a future release. Thank you very much for your consideration.

This is still very much needed. I believe it could greatly improve the user experience. Shading gets annoying when you have important data at the edges and zooming is cumbersome when you like to investigate changes in a specific region of interest.
I understand that the team might be occupied with other tasks, but I just wanted to emphasize the continued importance of this request. I'm looking forward to seeing this feature being added in a future release. Thank you very much for your consideration.

authors: benjaminpkane oguz-hanoglu


text:
Add el8 support for install_puppet_on

beaker has support for an el-8-* platform but the install_puppet_on function does not recognise this platform

@smortex want to recheck?

:+1:

authors: ekohl gcampbell12 smortex

repo: voxpupuli/beaker-puppet


text:
failed to download gpg key

I have the output of the error below,  module versions used,  and a workaround at the bottom.
This is on CentOS 6.4  and RHEL 6.4.
Should this work out of the box?
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns: Assuming you trust Michal Papis import the mpapis public key (downloading the signatures).
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns: GPG signature verification failed for '/usr/local/rvm/archives/rvm-1.26.11.tgz' - 'https://github.com/rvm/rvm/releases/download/1.26.11/1.26.11.tar.gz.asc'!
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns: try downloading the signatures:
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:     sudo gpg2 --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns: or if it fails:
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:     command curl -sSL https://rvm.io/mpapis.asc | sudo gpg2 --import -
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns: the key can be compared with:
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:     https://rvm.io/mpapis.asc
==> tca: Notice: /Stage[main]/Rvm::System/Exec[system-rvm]/returns:     https://keybase.io/mpapis
==> tca: Error: /usr/bin/curl -fsSL https://get.rvm.io | bash -s -- --version latest returned 2 instead of one of [0]
==> tca: Error: /Stage[main]/Rvm::System/Exec[system-rvm]/returns: change from notrun to 0 failed: /usr/bin/curl -fsSL https://get.rvm.io | bash -s -- --version latest returned 2 instead of one of [0]

Modules included:
mod 'gnupg',
    :git => 'git://github.com/n1tr0g/golja-gnupg.git',
    :ref => '67da08a' #When tagged: '1.2.3'
mod 'rvm',
    :git => 'git://github.com/maestrodev/puppet-rvm.git',
    :ref => 'v1.12.1'

exec { 'import_gpg_key':
  command => 'curl -sSL https://rvm.io/mpapis.asc | sudo gpg2 --import -',
  unless  => 'gpg --fingerprint | grep RVM',
}

class { '::rvm':
  gnupg_key_id => false
}

Exec['import_gpg_key'] ->
Class['rvm']

Bit me as well

I'm seeing this too... on Ubuntu 16.04.
Two comments:

On puppet 3.8.5, I need to add path => '/usr/bin:/bin' to Exec[import_gpg_key].
The workaround works for me, but only if I start from scratch.  Otherwise gpg --fingerprint | grep RVM succeeds and the import is not run.  Running the curl...-import - command outside of puppet and then rerunning puppet succeeds.  The output from gpg --fingerprint, however, is not changed by the running of the import command manually.

Yep, I also hit this issue.

Me too, on Ubuntu 14.04

I've hit this one, too. I looked into gpg module code:
  def add_key_from_key_server     command = "gpg --keyserver #{resource[:key_server]} --recv-keys #{resource[:key_id]}"     begin       output = Puppet::Util::Execution.execute(command,  :uid => user_id, :failonfail => true)     rescue Puppet::ExecutionFailure => e       raise Puppet::Error, "Key #{resource[:key_id]} does not exist on #{resource[:key_server]}"     end end
ANY error results in printing that error message, it's plain deceptive.
I've change it to
 def add_key_from_key_server     command = "gpg -v --homedir /root --keyserver #{resource[:key_server]} --recv-keys #{resource[:key_id]}"     Puppet::Util::Execution.execute(command, :failonfail => true, :combine => true)   end
in order to see what's really happening.
Anyway, since it would install key each puppet run as it is, I decided to get rid of it and go with one extra exec to install the key as needed.
I also noticed that the rvm module does not call for gnupg and it relies on the script to do that, I'm currently working on fixing that, I can't download a script and trust it to call for verification.

I'm going to close this based on its age. If you can still reproduce it, please reopen.

authors: Hoodoo Mirceaa brettswift cyberious ekohl joshuaspence rubys

repo: voxpupuli/puppet-rvm


text:
Update a few components of the website

Add a favicon
Update theme and Font Awesome
Point Ci at Travis, VPCI appears mostly broken

*  External link https://voxpupuli.org/favicon.ico failed: 404 No error
Didn't #44 fix this?

No, #44 only fixes it for posts and nav links, not any random asset. I'm working on that one next.

OK, that seems like the only non-problem, so here we go!


text:
Importing and exporting via scope.txt does not work

After executing reload, it will only display the loaded file and get stuck.

@Scorpiondeng I'm not sure to understand what's not working? once you reload from the scope file, are the file correctly marked in the explorer?

It has not been marked. I am running win11 system and I have tried it on several computers. After reload, all previous marks are cleared, and then there is no follow-up.

@Scorpiondeng Are you sure that the paths in the scope file are correct? The paths should be relative to the location of the scope file itself. Could you try to manually mark some file, "Export marked files to a file" from the context menu, unmark some of the files, and then reload the marks by running the "Reload marked files from scope file". Normally, all the marks should re-appear.

Yeah, I've also doubted this. So I tried Export, but nothing happened, no files were exported. I've also tried various different paths, all of which failed.

Ok, weird. Could you check if there is any error message displayed in the VSCode output? In the "Mark Files" and "Extension host"   outputs?

There is such a display when exporting, but there is no output when reloading. There is no output in "Extension host"

I guess it's probably a problem related to Windows, somehow. I'm only using Mac OS and linux machines, so it's harder for me to debug 😅 I'm gonna try to get access to a windows machine asap to try.

Thank you for your kind help

Has the issue been fixed? I’m still running into the same problem.
on v1.1.3

It's been fixed and so far everything is fine.

Got it. It’s working now. There was a format issue.

authors: Scorpiondeng X1pherW0lf vquelque


text:
Search parameter leads to task finishing instantly with HAnime

Fixed in latest commit: https://github.com/vrienstudios/anime-dl/commit/62370b323c5c7bd8aaf6e9ee8c24b84ccad46b9c

Fixed in latest commit: https://github.com/vrienstudios/anime-dl/commit/62370b323c5c7bd8aaf6e9ee8c24b84ccad46b9c

repo: vrienstudios/anime-dl


text:
Red alert on file - "Not synchronised: not a target file"

Abstract
The synchronisation hung up immediately after connecting.
Expected behaviour

Everything synchronised

Actually happened

Got a specific error on some files "Not synchronised: not a target file"

These altered files NOT synchronised, others OK

Screenshots

How to overcome this behavior? Creating an empty file doesn't help. Creating a brand new folder and move file there does. This happens in a single Obsidian folder (yet!).

Thank you for asking me! This alert indicates that the file were not synchronised, as you mentioned.
Have you configured some selector on the 🚦Selector pane? If so, please delete every rule once and check the behaviour again?
If not, something happened. please share me the report of your configuration! This can be created on the 🧰Hatch Pane.

authors: vrtmrz vsenn

repo: vrtmrz/obsidian-livesync


text:
Block edge 4.6.3

4.6.3 needs to be disabled:
3 clusters currently failing (12%),  2 gone ( 8%),and 18 successful (69%), out of 26 who attempted the update over 7d
Currently failing classification:
* Down nodes: 1
* Node pressure: 1
* SDN issue: 3

4.6.3 can be enabled again:
1 clusters currently failing ( 3%),  2 gone ( 6%),and 24 successful (77%), out of 31 who attempted the update over 7d
Currently failing classification:
* SDN issue: 1

repo: vrutkovs/cincinnati-graph-data


text:
Adding typescript support

The motivation for adding TypeScript support includes:

Improved recognition of custom element tags in .tsx files

Enhanced IntelliSense for component props, allowing for better auto-completion and code insights.

This would be a valuable enhancement for the library.

See #184

I failed to fix the element recognition issue with Vite. It can be fixed by changing the moduleResolution in the tsconfig, but I believe there’s a good reason why the Vite creators are using the current setting, so I wouldn’t modify it. But fortunately, the React wrapper makes this issue irrelevant.

authors: bendera veredcon

repo: vscode-elements/elements


text:
[Icon Request] Add icon for partials and misc(elanous) folders

[X] I'm sure this issue is not a duplicate.

[X] I'm submitting an icon request:

Type: Icon Request
Icon Name: partials & misc(elanous)
Sample original Icon: -
Extensions: -
Filenames: - (Its folder)
Language ids: -

Language Extensions:-

More info:-

Please see #650

repo: vscode-icons/vscode-icons


text:
Plugin breaks until another file is opened

I've been experiencing a long-running issue with this plugin where occasionally, it will just flat out stop working. hjkl don't even insert, I just can't do anything to modify the file at all until I open one or two more files and try moving in them and then go back to the previous file. Where do I start with debugging this issue?

https://github.com/vscode-neovim/vscode-neovim#-build

authors: blackboardd justinmk

repo: vscode-neovim/vscode-neovim


text:
Outlining an article involves headlines and bullet lists

I actually disagree.
It would really be nice to migrate bullets between sections as well. you need the outliner plugin to do this or to build a interface between the proposed external plugin.
Sections and bullets can naturally just be treated as higher levels of nesting as compared to bullets. a paragraph of text can just be treated kinda like a bullet.
Originally posted by @rapatel0 in https://github.com/vslinko/obsidian-outliner/discussions/53#discussioncomment-1139396
I'd like to support this thought of rapatel0. As in the MS Word world, an Outline of an article is something that would benefit note taking a lot.
With a mix of Heading and bullet point outlining, one could seamlessly

take bullet list,
order it, set nesting levels
then with the help of a keyboard shortcut change a bullet and all it's higher level entries to a heading.

That would leave the bullet points below either as writing prompts or as actual bullet lists

Thinking about the UX, it might be best to have a third mode (display, edit, outline). The new outline mode would:

Hide all paragraphs
Leave only the headings and bullets as a seamless hierarchy to indent/outdent

move all paragraphs between headings with it, once you switch back to edit or display mode.

Not sure how to deal with paragraph, list, paragraph sections.
P.S.: Thanks for a great plugin !

Sorry, I did not mean to open a new issue, just to comment on a discussion.

repo: vslinko/obsidian-outliner


text:
Add PSTModernizer

Project URL
https://github.com/PSPDFKit-labs/PSTModernizer
Description
Makes it easier to support older versions of iOS by fixing things and adding missing methods
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 or later
[ ] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Thank you so much, @naeemshaikh90. You've been a great help for us!

@lfarah glad to help you guys! These are my first contributions to open source community. :)

@naeemshaikh90 AwesomeiOS was also my first contribution to open source years ago. If you wanna dig more into open source, let me know and I can help you!😉

Ya sure I am looking forward to actively contribute on open source community.

repo: vsouza/awesome-ios


text:
feat: Creates and styles Toggle component

What's the purpose of this pull request?
This PR intends to create the Toggle using the Theming structure.
How does it work?
The component works as a input of type checkbox, but in the form of a toggle/switch control. For styling, uses local variables to parameterize the Toggle properties, then connects these scoped tokens to the global ones.
New global tokens:
None.
New local tokens for Toggle:
Default properties:

Local token
Default value/Global token linked

--fs-toggle-height
calc(var(--fs-control-min-height) / 1.75)

--fs-toggle-shadow
var(--fs-shadow)

--fs-toggle-bkg-color
var(--fs-control-bkg-default)

--fs-toggle-border-color
var(--fs-border-color-default)

--fs-toggle-border-radius
var(--fs-border-radius-default)

--fs-toggle-border-width
var(--fs-border-width-default)

--fs-toggle-transition-timing
var(--fs-transition-timing)

--fs-toggle-transition-property
var(--fs-transition-property)

--fs-toggle-transition-function
var(--fs-transition-function)

--fs-toggle-knob-radius
var(--fs-border-radius-small)

--fs-toggle-knob-shadow
var(--fs-shadow)

--fs-toggle-knob-bkg-color
var(--fs-color-primary-bkg)

--fs-toggle-knob-border-color
var(--fs-color-main-4)

--fs-toggle-knob-border-width
var(--fs-border-width-thick)

--fs-toggle-knob-icon-color
transparent

--fs-toggle-shadow-hover
var(--fs-shadow)

--fs-toggle-bkg-color-hover
var(--fs-color-primary-bkg-light)

--fs-toggle-border-color-hover
var(--fs-border-color-default-hover)

--fs-toggle-knob-bkg-color-hover
var(--fs-toggle-border-color-hover)

--fs-toggle-knob-border-color-hover
var(--fs-toggle-border-color-hover)

Checked:
-----------------------------------

--fs-toggle-checked-bkg-color
var(--fs-color-primary-bkg-active)

--fs-toggle-checked-border-color
var(--fs-border-color-default-active)

--fs-toggle-checked-bkg-color-hover
var(--fs-color-primary-bkg-hover)

--fs-toggle-checked-border-color-hover
var(--fs-toggle-checked-bkg-color-hover)

--fs-toggle-checked-knob-bkg-color
var(--fs-control-bkg-default)

--fs-toggle-checked-knob-border-color
var(--fs-toggle-checked-knob-bkg-color)

--fs-toggle-checked-knob-icon-color
var(--fs-toggle-checked-bkg-color)

--fs-toggle-checked-knob-icon-color-disabled
var(--fs-toggle-knob-icon-color)

--fs-toggle-checked-knob-icon-color-hover
var(--fs-toggle-checked-bkg-color-hover)

Disabled:
-----------------------------------

--fs-toggle-disabled-bkg-color
var(--fs-color-disabled-bkg)

--fs-toggle-disabled-border-color
var(--fs-border-color-default-disabled)

--fs-toggle-disabled-knob-bkg-color
var(--fs-color-neutral-5)

--fs-toggle-disabled-knob-border-color
var(--fs-toggle-disabled-knob-bkg-color)

--fs-toggle-disabled-knob-icon-color
var(--fs-toggle-disabled-bkg-color)

How to test it?
The Toggle component can be tested through Storybook and should look like the image below:

Checklist

[x] CHANGELOG entry added

Hey! Looks great! 🤩 I've just noticed that the style isn't work properly on the safari. Can you take a look pls?


text:
Added 'visible' field functionality for groups

Please check if the PR fulfills these requirements

[X] The commit message follows our guidelines
[X] 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: adding 'visible' field functionality for groups

What is the current behavior? (You can also link to an open issue here)
Currently visible field isn't processed

What is the new behavior (if this is a feature change)?
User can hide groups using groups[*].visible

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

Other information:
Should be docs added to the separate repo?

Coverage remained the same at 89.979% when pulling a144c2a699316eed4f80837e92725bcb881246a0 on devalexx:visible-field-for-groups into 721a4eebbde77040a1318e60aa9ef21229bbcf99 on vue-generators:master.

This seems to be a duplicate of https://github.com/vue-generators/vue-form-generator/pull/606.

Duplicate of #606

@zoul0813 @muschottkey
I know that there is a similar pull request. But this one has tests and doesn't duplicate existing function.
But of course it's up to you.

authors: coveralls devalexx muschottkey zoul0813

repo: vue-generators/vue-form-generator


text:
Memory leak when using reactive/ref in SSR mode

Version
3.2.31
Reproduction link
github.com/yeyan1996/vite-ssr
Steps to reproduce

download repository
using npm run serve to start the server
see reactiveMap in the dist/server/entry-server folder

What is expected?
reactiveMap should be empty in server SSR
What is actually happening?
reactiveMap is expanding

This issue is similar to #5208
In the beginning, I want to create a pr to fix it, but unlike computed, reactive(ref) may be used outside of setup (maybe in .ts file)
I didn't find any other variable to tell if it's currently server-rendered(maybe window === undefined?)
So is it possible to build a branch for SSR? (I see there is a  __SSR__ variable in the source code)
Or other solutions, thx

We'll need a bit more info to confirm that this is indeed a memory leak - reactiveMap is a WeakMap - which means an entry can be released if its key is no longer referenced anywhere.
Your console.log() may cause the console to iterate the WeakMap and thus prevent all keys to be released.
To show a memory leak, please provide a repro similar to that of #5208.

repo: vuejs/core


text:
 fails to render component that extends a runtime template component

Vue version
3.2.37
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-ksuhdx?file=src/components/HelloWorld.vue
Steps to reproduce

Run the app
Notice that nothing is rendered.
Comment out HelloWorld.vue line 13 and uncomment HelloWorld.vue line 14.
Notice that "I'm an SFC" now renders.

What is expected?
I have created a component extendedComponent that has the key extends to extend a compnent that uses a runtime template:
const baseComponentRuntimeTemplate = {
  template: `<p>I'm a component</p>`,
};

const extendedComponent = {
  extends: baseComponentRuntimeTemplate
};

And I am trying to render it with <component :is="extendedComponent"></component>.
I expected that this would render baseComponentRuntimeTemplate's template in the app.
What is actually happening?
Nothing renders.
System Info
No response
Any additional comments?
It seems to work fine when the base component is an SFC, but if the base component uses a runtime template, it does not work.
I created the reproduction link on StackBlitz because I needed to enable runtime compilation of templates.

BTW, you should markRaw for component.
export default {
  data() {
    return {
      component: markRaw(extendedComponent),
    };
  },
};


text:
Optional parameters not work in nested routes

Reproduction
https://codesandbox.io/s/strange-mccarthy-d3y4hy
Steps to reproduce the bug
import { createRouter, createWebHistory } from "vue-router";
import Home from "./views/Home.vue";
import About from "./views/About.vue";
import BasicLayout from "./views/BasicLayout.vue";

export const router = createRouter({
  history: createWebHistory(),
  routes: [
    {
      path: "/",
      component: BasicLayout,
      children: [
        {
          path: ":section(sec-\\w+)?",
          name: 'Home',
          component: Home
        }
      ]
    },
    { path: "/about", component: About }
  ]
});

The Home route not matched.
Expected behavior
Home route  need matched
Actual behavior
Home route  not matched
Additional information
No response

This happens because the child has a lower priority in terms of matching than the parent. In this scenario it doesn't make sense but it allows to match /dashboard instead of /dashboard/:p? in practice.
For your case to work, you can just add an alias of '' to the child route to fix this:

export const router = createRouter({
  history: createWebHistory(),
  routes: [
    {
      path: "/",
      component: BasicLayout,
      children: [
        {
          path: ":section(sec-\\w+)?",
          alias: "",
          component: Home,
        },
      ],
    },
    { path: "/about", component: About },
  ],
});

authors: ccqgithub posva

repo: vuejs/router


text:
Feature request: send keyboard input strings

Is your feature request related to a problem? Please describe.

Currently, we can set input values with input.setValue("arst") or although I am not sure it is supported, send keyboard input with e.g. input.trigger("keydown.a") for each character.

setValue is not natural as it is not what users do. See also https://github.com/vuejs/vue-test-utils/issues/960

Undefined behavior for inputs that have special characters - must be aware of implementation details - e.g. chip/tag inputs?

keydown must be called for each character and is undesirable for long strings

Describe the solution you'd like

What I am really looking for here is something closer to Selenium sendKeys. This is a more E2E type feature, but component tests are already encouraged to be mini-E2E tests, not relying on implementation details.
Describe alternatives you've considered

setValue, but this is unnatural and sketchy for chip inputs. Could work
Using very short strings via several trigger("keydown") calls
maybe something like

aysnc function sendKeys(s: string): Promise<void> {
  const chars = s.split();
  await Promise.resolveAll(chars.map(async char => await input.trigger(`keydown.${char}`)));
}

Additional context

I personally don't think we need such a specific feature, but maybe I'm not understandingg correctly your use-case.
What are you trying to test?

Can't say I'm the best at explaining my ideas. Let me give the user story instead.
I want to test interactions with a Vuetify VCombobox with chips. It is a text input where users type terms, then press tab or enter to turn the term into a chip. This allows them to input multiple freeform text terms, and they are delimited clearly in a modern way. Like a multi-select but with freeform text instead of pre-defined options.
Now, I do not know the implementation details of this component - although I could figure them out. But VTU advertises that good tests are black-box and should come from a user's perspective. Users do not set input values, they type keys.
I am basically worried that setting an input value won't trigger the correct events and such because it isn't how the thing was intended to be used. On the other hand I know that typing terms following by tab or enter does work.
So maybe I am being lazy, but I found myself wishing I could test by typing keys programmatically instead of setting input values. Years ago I used Selenium pretty heavily, and I recalled their sendKeys method where I can 'type arbitrary strings on a keyboard', e.g. sendKeys("search term 1\tsearch term 2\t").
What do you think about this idea?

I understand, but I'm not sure it's worth adding another API to VTU for this use case. You can already do what you want, although you indeed need a bit more code.
Maybe you should take a look at Vue Testing Libray, or Playwright or Cypress component testing support: they may be what you're looking for and they all use VTU under the hood.
Or you could make a plugin https://test-utils.vuejs.org/fr/guide/extending-vtu/plugins.html to extend VTU with a helper that does exactly what you want.

Sounds good. It would be something along the lines of the above for loop using trigger("keydown.a") right?

Maybe yes. You can also check how Vuetify tests VCombobox. If I remember correctly, they use VTU to do so, so it could be a good inspiration.

authors: aentwist cexbrayat

repo: vuejs/test-utils


text:
Vite Is Not Supported Non Browser Environment Like Electron

Do NOT ignore this template or your issue will have a very high chance to be closed without comment.

Describe the bug
I Use Electron Protocol To Run Application In Production Build. When Running Production Build Path Error Occur In index.html.
I Think This Error Is Because Of Protocol Not Work Like A Server It Uses File System. So, I Think The Fix Is Using
<script type="module" src="./_assets/index.98b5a788.js"></script>

instead of
<script type="module" src="/_assets/index.98b5a788.js"></script>

In `index.html. This Fix Will Not Break Running Build On A Server. Also Want To Fix Other Tags Like Link
Reproduction
https://github.com/bekalshenoy/vue-next-error
System Info

required vite version: 0.16.4
required Operating System: windows 10
required Node version: 14.2.0
Optional:

npm/yarn version
Installed vue version (from yarn.lock or package-lock.json)
Installed @vue/compiler-sfc version

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.

It’s not a bug if it’s by design...

repo: vuejs/vite


text:
unit test failing

Version
3.0.0-beta.6
Reproduction link
https://codesandbox.io/s/vue
Steps to reproduce
vue create myproject
Vue CLI v3.0.0-beta.6
? Please pick a preset: full (vue-router, vuex, sass, babel, pwa, eslint, unit-j
est, e2e-nightwatch)
select full
🎉  Successfully created project myproject.
cd myproject
What is expected?
vue-cli-service test passing without error
What is actually happening?
FAIL  tests/unit/HelloWorld.spec.js
● Test suite failed to run
  Plugin 0 specified in "/Users/yves/Developments/WIP/VUE.JS-vcli-3-beta/myproject/node_modules/@vue/babel-preset-app/index.js" provided an invalid property of "default" (While processing preset: "..../myproject/node_modules/@vue/babel-preset-app/index.js")

    at Plugin.init (node_modules/babel-jest/node_modules/babel-core/lib/transformation/plugin.js:131:13)
        at Array.map (<anonymous>)
        at Array.map (<anonymous>)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        10.668s
Ran all test suites.
ERROR  jest exited with code 1.
error Command failed with exit code 1.

`   yves@Yvess-Mac-mini myprojectTEST (master) $ rm -R node_modules
yves@Yvess-Mac-mini myprojectTEST (master) $ yarn install
yarn install v0.27.5
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
Done in 125.68s
yves@Yvess-Mac-mini myprojectTEST (master) $ yarn test
yarn test v0.27.5
$ vue-cli-service test
PASS  tests/unit/HelloWorld.spec.js (5.598s)
HelloWorld.vue
✓ renders props.msg when passed (27ms)
Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        11.26s
Ran all test suites.
Done in 21.44s.`
re-building node_modules solved the isseu ... I don't understand what happen ..  but at leats , it's testing fine ..   thanks for your prompt attention to it

just for info .. I compared the 2 package.json
the only difference I can see , is in the failing one  , using @vue/prettier in eslintConfig
  "eslintConfig": {     "root": true,     "extends": [       "plugin:vue/essential",       "@vue/prettier"     ]   },

This is still an issue, is there a solution?

I got the same exact same problem as well. Is it back? @erwin16 does this still work with updated packages?

Might be a false positive from my side. I have an app based on quasar that uses a plugin that generates this issue... Might be the quasar .babelrc's fault... My module that I am getting this error from builds fine.

This issue started when I switched to Vue CLI 3 beta 10 (with Babel 7 beta). Some other packages were using Babel 6. Manual update to Babel 7 in these packages fixed it.
Different Babel versions do not live together well.

The solution for me was switching back to using npm. Doing npm install instead of yarn install solved it..

Have the exact same problem. Not sure how to even find out what is wrong from this output. :(

Given the repro above, should this be reopened?  Also running into this.

@manico can you open a new issue with the repro steps? I believe that's what @LinusBorg asked for after it was closed. i'm also having the same issue, but would be best to start a new issue with your reproduction steps so it can get resolved.

It is the same case as the issue described here.
I did nothing special in this repository, so maybe this issue should be reopened.

On my local Windows machine the test are passing just fine but on CircleCI I get the following error:
Plugin 0 specified in "/home/circleci/repo/node_modules/@vue/babel-preset-app/index.js" provided an invalid property of "default" (While processing preset: "/home/circleci/repo/node_modules/@vue/babel-preset-app/index.js")
I am using 3.0.0-beta.15  and Node version 9.2.0

Same Here :S
 Plugin 0 specified in "../webapp/node_modules/@vue/babel-preset-app/index.js" provided an invalid property of "default" (While processing preset: "../webapp/node_modules/@vue/babel-preset-app/index.js")

      at Plugin.init (node_modules/@vue/cli-plugin-unit-jest/node_modules/babel-core/lib/transformation/plugin.js:131:13)
          at Array.map (<anonymous>)
          at Array.map (<anonymous>)

Node: 10.5 (also tried on 8.9.4)
3.0.0-rc3

same problem here with Vue-cli 3.0.0-rc.3
I am using this in a Monorepo with Lerna and Yarn Workspaces. Deleting all node_modules folders and doing lerna bootstrap did not work.

This issue is closed, and so far still no reproducion was provided.
Please open a new issue with reproduction

I tried a few different things:
const vueApp = (context, options) => {
  const preset = require('@vue/babel-preset-app')(context, options);
  preset.plugins[0] = preset.plugins[0].default;
  return preset;
};

module.exports = {
  presets: [
    vueApp,
    'typescript'
  ]
}

This gave the following error:
 Test suite failed to run

    Requires Babel "^7.0.0-0", but was loaded with "6.26.3". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel.

      at throwVersionError (node_modules/@babel/plugin-syntax-jsx/node_modules/@babel/helper-plugin-utils/lib/index.js:65:11)
      at Object.assertVersion (node_modules/@babel/plugin-syntax-jsx/node_modules/@babel/helper-plugin-utils/lib/index.js:13:11)
      at api (node_modules/@babel/plugin-syntax-jsx/lib/index.js:19:7)

I am using Node 9.11 and I notice ts-jest depends on babel-core 6.26.3
    "ts-jest": {
      "version": "22.4.6",
      "resolved": "https://registry.npmjs.org/ts-jest/-/ts-jest-22.4.6.tgz",
      "integrity": "sha512-kYQ6g1G1AU+bOO9rv+SSQXg4WTcni6Wx3AM48iHni0nP1vIuhdNRjKTE9Cxx36Ix/IOV7L85iKu07dgXJzH2pQ==",
      "dev": true,
      "requires": {
        "babel-core": "6.26.3",
        "babel-plugin-istanbul": "4.1.6",
        "babel-plugin-transform-es2015-modules-commonjs": "6.26.2",
        "babel-preset-jest": "22.4.4",
        "cpx": "1.5.0",
        "fs-extra": "6.0.0",
        "jest-config": "22.4.4",
        "lodash": "4.17.10",
        "pkg-dir": "2.0.0",
        "source-map-support": "0.5.6",
        "yargs": "11.1.0"
      },
  // ....

This is my current list of dependencies:

  "dependencies": {
    "register-service-worker": "^1.4.1",
    "vue": "^2.5.16",
    "vue-loader": "^15.2.4",
    "vue-router": "^3.0.1",
    "vuex": "^3.0.1"
  },
  "devDependencies": {
    "@babel/core": "^7.0.0-beta.47",
    "@babel/plugin-syntax-jsx": "^7.0.0-beta.52",
    "@babel/preset-typescript": "^7.0.0-beta.52",
    "@types/jest": "^22.2.3",
    "@vue/babel-preset-app": "^3.0.0-rc.3",
    "@vue/cli-plugin-babel": "^3.0.0-beta.15",
    "@vue/cli-plugin-e2e-nightwatch": "^3.0.0-beta.15",
    "@vue/cli-plugin-pwa": "^3.0.0-beta.15",
    "@vue/cli-plugin-typescript": "^3.0.0-beta.15",
    "@vue/cli-plugin-unit-jest": "^3.0.0-beta.15",
    "@vue/cli-service": "^3.0.0-beta.15",
    "@vue/test-utils": "^1.0.0-beta.20",
    "autoprefixer-loader": "^3.2.0",
    "babel-loader": "^7.1.5",
    "babel-preset-es2015": "^6.24.1",
    "css-loader": "^0.28.11",
    "file-loader": "^1.1.11",
    "node-sass": "^4.9.1",
    "sass-loader": "^7.0.3",
    "style-loader": "^0.21.0",
    "ts-jest": "^22.4.6",
    "vue-style-loader": "^4.1.0",
    "vue-template-compiler": "^2.5.16",
    "webpack": "^4.15.1",
    "webpack-cli": "^3.0.8",
    "webpack-dev-server": "^3.1.4",
    "webpack-serve": "^1.0.4"
  },

Will update when I find a solution.

Yeah to me it seems like jest-config latest (23.3.x) as of this post, does not work with @babel/etc ^7: https://github.com/facebook/jest/blob/v23.3.0/package.json
So typescript + jest is a no go with the latest vue-cli config.
Am I missing anything here?

I was also facing the same issue. I corrected it by simply nuking my node_modules and package.json, and then updating the devDependencies with the latest values spit out in a fresh project created via CLI... these being:
    "@vue/cli-plugin-babel": "^3.0.1",     "@vue/cli-plugin-eslint": "^3.0.1",     "@vue/cli-plugin-unit-jest": "^3.0.1",     "@vue/cli-service": "^3.0.1",     "@vue/eslint-config-airbnb": "^3.0.1",     "@vue/test-utils": "^1.0.0-beta.20",     "babel-core": "7.0.0-bridge.0",     "babel-jest": "^23.0.1",     "vue-template-compiler": "^2.5.17"

@haverchuck - thanks for sharing :) - "babel-core": "7.0.0-bridge.0" was not included by default at my side and adding it manually solved the issue.

remove: babel-core
and install: @babel/core
It works.

Nice @Max-0n, that worked for me.

authors: LinusBorg Max-0n christianvoigt codeHamster9 ejwaibel erichulburd erwin16 ghost haverchuck laurentpayot liron-navon manico skhavari xeor zdravkov znicholasbrown zugende

repo: vuejs/vue-cli


text:
Jest not working on Windows 10 network drives on new project

Version
4.1.1
Reproduction link
https://github.com/alexanderVu/windumbo
Environment info
Windows 10 1809

Steps to reproduce
Install vue cli on windows 10. Use pwa, vuex, router, unit tests (jest). Run npm run test:unit after installation.
Update: This issue happens only when project is on network drive. Using Windows on Parallels MacOS and shared folders create same issue.
What is expected?
The test shoud run.
What is actually happening?
vue-cli-service test:unit
● Validation Error:
Preset @vue/cli-plugin-unit-jest is invalid:
The "id" argument must be of type string. Received type object
TypeError [ERR_INVALID_ARG_TYPE]: The "id" argument must be of type string. Received type object
at validateString (internal/validators.js:107:11)
at Module.require (internal/modules/cjs/loader.js:659:3)
at require (internal/modules/cjs/helpers.js:16:16)
at setupPreset (Z:\Projects\windumbo\node_modules\jest-config\build\normalize.js:230:14)
at normalize (Z:\Projects\windumbo\node_modules\jest-config\build\normalize.js:554:15)
at readConfig (Z:\Projects\windumbo\node_modules\jest-config\build\index.js:163:46)
at readConfigs (Z:\Projects\windumbo\node_modules\jest-config\build\index.js:373:26)
at Z:\Projects\windumbo\node_modules@jest\core\build\cli\index.js:155:58
at Generator.next ()
at asyncGeneratorStep (Z:\Projects\windumbo\node_modules@jest\core\build\cli\index.js:108:24)
Configuration Documentation:
https://jestjs.io/docs/configuration.html
error Command failed with exit code 1.

Seems an upstream issue https://github.com/facebook/jest/issues/8763

authors: alexanderVu sodatea


text:
nested 的路由回退问题？

Version
3.0.3
Reproduction link
http://sample.com
Steps to reproduce
路由跳转：/jobs/ -> /posts/ -> /posts/1/ ，然后点击浏览器的返回按钮，页面会返回到 /jobs/ 而不是 /posts/。好像返回时，nested 的路由会被直接跳过？
What is expected?
期望是返回到 /posts/ 页面
What is actually happening?
返回到了 /jobs/ 页面

That's not a valid repro. Also please, write the issue in English.
Before opening a new issue, make sure to check  existing  issues as well :)

authors: hojas posva

repo: vuejs/vue-router


text:
Uncaught TypeError: Cannot read property 'to' of null

When I upgrade to vue-router@v0.7.8 and vue@1.0.14-csp (before is vue-router@0.7.7 and vue@1.0.13-csp), this error happened. It's in line 2533.
The code is here: https://github.com/lmk123/crx-selection-translate/blob/master/src/options/index.js#L37

Looks your transition target path is null. Can you provide some code or a jsFiddle that reproduces the issue?

@amirrustam The code is here: https://github.com/lmk123/crx-selection-translate/blob/master/src/options/index.js#L37
I will create a jsFiddle later.

I reproduces this error in jsFiddle: https://jsfiddle.net/lmk123/Lkohd5en/1/

Looks like with the update you can't specify a redirect route with a name. You have to provide a literal path string: https://jsfiddle.net/Lkohd5en/8/
Actually, the documentation doesn't specify that you can define redirects with route names. It explicitly states that redirects must be defined like so: { fromPath: toPath, ... }. Please read: http://vuejs.github.io/vue-router/en/api/redirect.html
However, since it was working in the previous version, then this is a breaking change. @yyx990803 is this expected behavior or an unexpected consequence of a change?


text:
Shorthand component imports

What problem does this feature solve?
Reduces time consuming boilerplate when using/importing Vue components.
What does the proposed API look like?
<script>
	export default {
		components: {
			Widget: '@/components/Widget.vue'
		}
	};
</script>

https://v2.svelte.dev/guide#shorthand-imports

Thanks for the proposal but this is too much magic. It could be implemented as a custom loader for webpack or a plugin but this is something that should go in userland

Vue is full of magic. What is the criteria used to decide if something is too much magic or not?

I think what he meant is that that would be putting too much responsibility on Vue, and it would be better handled by users in their code (easier to maintain, and avoid adding too much features to Vue, which could make it harder to move forward).

@franciscolourenco Svelte is a compiler and it actually transforms JavaScript code and modifies its original semantics. On the other hand, it has always been just plain JavaScript inside Vue components' <script> blocks. So I think your request would be better answered with a custom webpack loader, as @posva pointed out.

I didn't mean this should be implemented in Vue core. webpack-vue-loader or some plugin part of the vue-cli repository can be  be better places. The Vue org maintains some of these plugins but I don't have the best overview of all the projects and plugins. It still sounds like a useful API which reduces boilerplate and would be cool to see it as a standard option.

authors: Justineo franciscolourenco kinow posva

repo: vuejs/vue