text:
Mqtt cannot be used

Here's my procedure:
create-vite-app testvite

cd testvite

npm i

npm install mqtt

npm run dev

Program output:
[vite] Dep optimization failed with error:
Could not load url (imported by node_modules\mqtt\lib\connect\index.js): ENOENT: no such file or directory, open 'D:\VueProject\testvite\testvite\url'
{ [Error: Could not load url (imported by node_modules\mqtt\lib\connect\index.js): ENOENT: no such file or directory, open 'D:\VueProject\testvite\test
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'D:\\VueProject\\testvite\\testvite\\url',
  watchFiles:

This is a common problem with modules that aren't bundled or packaged correctly for the browser. You should be able to get it to work by importing the right file (which sometimes takes some digging).
Here's a working MQTT example: https://codesandbox.io/s/vite-issue-3045-ld276?file=/src/main.ts
Using the following config:
{
  resolve: {
    alias: {
      mqtt: "mqtt/dist/mqtt.js"
    }
  }
}

thanks

authors: nihalgonsalves yaolunmao


text:
[vite-plugin-svelte-kit] Package subpath './helpers/esm/asyncToGenerator.js' is not defined by "exports"

Describe the bug
vite 3.0.2 writes imports to bundle incorrectly, but vite2 works fine:
main.js
import _asyncToGenerator from "@babel/runtime-corejs3/helpers/esm/asyncToGenerator";
console.log(_asyncToGenerator);

build command:
vite build --ssr main.js

dist/main.mjs
import _asyncToGenerator from "@babel/runtime-corejs3/helpers/esm/asyncToGenerator.js";
console.log(_asyncToGenerator);

there should not be the .js extensions, because the direct paths is restricted by the @babel/runtime-corejs3/package.json
Reproduction
See this repo
System Info
System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
    Memory: 6.11 GB / 15.89 GB
  Binaries:
    Node: 16.15.1 - E:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.11.0 - E:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1023.0), Chromium (103.0.1264.62)
    Internet Explorer: 11.0.19041.906

Used Package Manager
pnpm
Logs
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 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.

I think it related with #8420
The error appears since the 3.0.0-alpha.8 version, because the 3.0.0-alpha.7 generates cjs module

Closing as I confirmed this is fixed in 4.1.0+.

source: gharchive/issue

authors: NikolayMakhonin sapphi-red

repo: vitejs/vite

license: MIT

license_type: permissive

license_source: github-api


text:
use the xlsx npm but got error

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

Describe the bug
when I add some npm to  package.json such as   xlsx(npm) or axios and so on， I run vite and then get some errors
the vite.config.js:
 import { createVuePlugin } from 'vite-plugin-vue2'
const etc = require('./config/index.js');

const config = {
  plugins: [createVuePlugin()],
  optimizeDeps:{
    include: ['vuex-router-sync', 'xlsx'],
    link: [],
    allowNodeBuiltins: ['koa', 'protobufjs', 'uuid', 'follow-redirects'],
    auto: true
  },
  proxy: {
    // string shorthand
    '/foo': `http://127.0.0.1:${etc.ServerPort}`,
    // with options
    '/api': {
      target: `http://127.0.0.1:${etc.ServerPort}`,
      changeOrigin: true,
      rewrite: path => path.replace(/^\/api/, '')
    }
  },

  port: 9876,
}

export default config

i have some questions:
I think optimizeDeps can help to change cjs to esm?   use include to add the npm(then it will formate the code and to cache code to optimize)    should npm be add into devDependencies? not into  dependencies?
if it will pre-build, why i got errors?
how to solve?
System Info

required vite version: ^1.0.0-rc.4
required Operating System: mac os
required Node version: 14.0.0
Optional:

npm/yarn version
Installed vue version (from yarn.lock or package-lock.json)
Installed @vue/compiler-sfc version :         "vue-template-compiler": "^2.5.17",

Logs (Optional if provided reproduction)

Run vite  --debug
logs:

[vite] Dep optimization failed with error:
The argument 'path' must be a string or Uint8Array without null bytes. Received '/Users/jeromychen/Documents/project/test/testproject/\x00/Users/jeromychen/Documents/project/test/testproject/node_modules/xlsx...
TypeError [ERR_INVALID_ARG_VALUE] [ERR_INVALID_ARG_VALUE]: The argument 'path' must be a string or Uint8Array without null bytes. Received '/Users/jeromychen/Documents/project/test/testproject/\x00/Users/jeromychen/Documents/project/test/testproject/node_modules/xlsx...
    at Object.statSync (fs.js:1031:10)
    at fileMtime (/Users/jeromychen/Documents/project/test/testproject/node_modules/@babel/core/lib/config/files/utils.js:42:28)
    at /Users/jeromychen/Documents/project/test/testproject/node_modules/@babel/core/lib/config/files/utils.js:30:43
    at CacheConfigurator.using (/Users/jeromychen/Documents/project/test/testproject/node_modules/@babel/core/lib/config/caching.js:236:17)
    at CacheConfigurator.invalidate (/Users/jeromychen/Documents/project/test/testproject/node_modules/@babel/core/lib/config/caching.js:254:17)
    at /Users/jeromychen/Documents/project/test/testproject/node_modules/@babel/core/lib/config/files/utils.js:30:26
    at Generator.next (<anonymous>)
    at Function.<anonymous> (/Users/jeromychen/Documents/project/test/testproject/node_modules/@babel/core/lib/gensync-utils/async.js:26:3)
    at Generator.next (<anonymous>)
    at evaluateSync (/Users/jeromychen/Documents/project/test/testproject/node_modules/gensync/index.js:244:28)
    at Function.sync (/Users/jeromychen/Documents/project/test/testproject/node_modules/gensync/index.js:84:14)
    at sync (/Users/jeromychen/Documents/project/test/testproject/node_modules/@babel/core/lib/gensync-utils/async.js:66:25)
    at sync (/Users/jeromychen/Documents/project/test/testproject/node_modules/gensync/index.js:177:19)
    at onFirstPause (/Users/jeromychen/Documents/project/test/testproject/node_modules/gensync/index.js:204:19)
    at Generator.next (<anonymous>)
    at cachedFunction (/Users/jeromychen/Documents/project/test/testproject/node_modules/@babel/core/lib/config/caching.js:68:46) {
  code: 'PLUGIN_ERROR',
  pluginCode: 'ERR_INVALID_ARG_VALUE',
  plugin: 'vite:transforms',
  hook: 'transform',
  id: '\x00/Users/jeromychen/Documents/project/test/testproject/node_modules/xlsx/jszip.js?commonjs-proxy',
  watchFiles: [

is this new feature need to develop?  (cjs transform into esm)

Fixed at https://github.com/vitejs/vite/pull/908.You can hava a try with new version.

Fixed at #908. You can hava a try with new version.

can vite transform cjs to esm auto?

Fixed at #908. You can hava a try with new version.

got the same error

Fixed at #908. You can hava a try with new version.

got the same error
how can I solve this question？

My bad,can you give an reproduction for this ?

https://github.com/Jeromy-L/test-vite
this one , thank you for help

My bad,can you give an reproduction for this ?
https://github.com/Jeromy-L/test-vite
this one , thank you for help

My bad,can you give an reproduction for this ?
i think it was cause by these code :
require('@rollup/plugin-commonjs')({             extensions: ['.js', '.cjs'] }),
which is in vite source code

Fixed at  https://github.com/underfin/vite-plugin-vue2/commit/97c0916ba3e4d0f1c4f1bb9b16f7c1c7d05a17d8

Fixed at underfin/vite-plugin-vue2@97c0916

i always get this error, isn't impotant？   can i ignore?
and why the path was  repeat "/Users/jeromychen/Documents/project/test/testproject"

Not encounter this. I miss something or you not update your repo code ?

I have another question,  I add the npm (signale） if it was added in dependencies no in devDependencies, will got the errors

but i have add into the allowNodeBuiltins array

and some npm (error message) wasn't in the project's package.json (dependencies)  ,   was  it require in some npm's  dependencies?
such as i want to use this npm  into dependencies no devDependencies, how can I solve?  i have add them into allowNodeBuiltins, but no solve.

and the error above that  repeat "/Users/jeromychen/Documents/project/test/testproject"  was not always reprodction ,wait some time

Not encounter this. I miss something or you not update your repo code ?

I'm not sure why you must add some koa package inside a web application, it looks very wired. If you must do that, you can add them into exclude inside optimizer option.

I'm not sure why you must add some koa package inside a web application, it looks very wired. If you must do that, you can add them into exclude inside optimizer option.

how can i do some before the html return ? such I want to get the userinfo by replace the html  before the html return (such as middleware?)

Not encounter this. I miss something or you not update your repo code ?

hi, I found that how to reproduct this error, the error would happen when you open sourcemap

add some breakpoints will get some errors

i hope you will give some help

authors: Jeromy-L underfin


text:
docs: improve wildcard host note

Description
https://github.com/vitejs/vite/pull/8543#discussion_r899873187
I didn't add an option to hide this note because it is not so long and there is no other option to hide messages.
If we are adding an option, I think we need to think of #1728 instead.
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[x] 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 Commit 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.

I think that this may end up confusing more users. There are a lot of details and warnings we could add. @sodatea would it be ok if we remove this warning from the CLI and document it in the docs as this PR is doing? As it was explained in the comment that triggered this issue, it will be normal in docker setups.

🤦♂ Seems no perfect solution here.
IMO we can remove the CLI output for now.
I guess Docker users may be already used to very verbose outputs, but we don't want to scare them with edge case warnings.
If there're still many people getting confused and open issues, then it's not an edge case, we can then add it back.

source: gharchive/pull-request

authors: patak-dev sapphi-red sodatea


text:
Mocking breaks when isolate: false, singleThread: true, v1.1.2

Describe the bug
Likely regression from https://github.com/vitest-dev/vitest/pull/4664, cc. @Dunqing
If two files are loading same file and the second one mocks that file, Vitest will throw Error: [vitest] Cannot mock "../src/basic.js" because it is already loaded. Did you import it in a setup file? error. Reproduction below has no setup files - just two test files importing same source file while second one mocks that file.
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-scpuyh?file=test%2Fsecond.test.ts,test%2Ffirst.test.ts
System Info
Stackblitz

Used Package Manager
pnpm
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.

Coverage tests are failing randomly, depending which file Vitest's cache decides to run first:
https://github.com/vitest-dev/vitest/blob/a73c1c2ca3a3ca93b317657b9328889434c36344/test/coverage-test/test/no-esbuild-transform.test.js#L1-L10

Not sure if it is a bug. If the file structure was a little bit different, there would've been a situation when mocking wouldn't have worked in Vitest 1.0 (before the error that catches such bugs/features was introduced):
https://stackblitz.com/edit/vitest-dev-vitest-gxiruo?file=src%2Fbasic2.ts,package.json,test%2Ffirst.test.ts,test%2Fsecond.test.ts

Right, if this is expected behaviour then maybe the error message should be different when it's caused by disabled isolation. Seeing error message that mentions setupFiles is a bit misleading in cases like the minimal repro.

Right, if this is expected behaviour then maybe the error message should be different when it's caused by disabled isolation. Seeing error message that mentions setupFiles is a bit misleading in cases like the minimal repro.

It is not possible to know why the error happens.

The possible causes could still be limited based on configurations. If there are no setupFiles, do not mention that. If isolation is disabled, maybe add that one there.

This should be fixed by #4905
This error is now thrown only for isolated environments.

@sheremet-va  hey mate, I have written hundreds of test cases mocking react's particular api's that's needed mocking. And now all those tests are getting failed with this error thrown:
Please, remove the import if you want static imports to be mocked, or clear module cache by calling "vi.resetModules()" before mocking if you are going to import the file again. See: https://vitest.dev/guide/common-errors.html#cannot-mock-mocked-file-js-because-it-is-already-loaded
I have tried the resetmodules solution but it did not work for me

We're having the same problem. In the v0 version of Vitest things work as expected. The latest version of Vite fails with this same error.

I have the same issue. Reproducing is easy. In my case creating a test file with a mock for top level imported module and disable isolation (singleFork or isolation: false) is enough to see the error. For just maxFork: 1 minFork. 1 it works but this time tests are 10x slower.

Please, provide reproductions when filing an issue. Any comment that basically means "+1" will be ignored.

I went into StackBlitz and attempted to recreate the issue to no avail. I spent some time in our codebase commenting out code until I narrowed down where it was happening. We have a complex web of dependencies and I noticed one function that was exported in a module that had a ton of different imports. I moved that function into a different module and the issue stopped happening.
If I had to guess, this issue occurs when there's a circular dependency between two modules that indirectly import the mocked module. Hopefully this helps as I won't be able to spend any more time on this. cc @sheremet-va

authors: AriPerkkio Tohid001 divmgl i-void sheremet-va

repo: vitest-dev/vitest


text:
1.5.1 Throws Unhandled Rejections TypeErrors in coverage-instanbul - 1.4.0 works fine

Describe the bug
I have a large suite of tests (1200) and it is totally fine with 1.4.0. As soon as I upgrade
"@vitest/browser": "1.5.1",
"@vitest/coverage-istanbul": "1.5.1",
"@vitest/ui": "1.5.1",

I get:
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 3 unhandled errors during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Failed to fetch dynamically imported module: http://localhost:5173/@id/@vitest/coverage-istanbul

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Failed to fetch dynamically imported module: http://localhost:5173/@id/@vitest/coverage-istanbul

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Failed to fetch dynamically imported module: http://localhost:5173/@id/@vitest/coverage-istanbul
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

### Reproduction

.

### System Info

```shell
System:
    OS: Linux 5.14 Rocky Linux 9.3 (Blue Onyx)
    CPU: (8) x64 AMD EPYC 7B13
    Memory: 14.14 GB / 31.09 GB
    Container: Yes
    Shell: 5.1.8 - /bin/bash
  Binaries:
    Node: 20.12.1 - ~/.asdf/installs/nodejs/20.12.1/bin/node
    npm: 10.5.0 - ~/.asdf/plugins/nodejs/shims/npm
  npmPackages:
    @vitejs/plugin-react: 4.2.1 => 4.2.1
    @vitest/browser: 1.5.1 => 1.5.1
    @vitest/coverage-istanbul: 1.5.1 => 1.5.1
    @vitest/ui: 1.5.1 => 1.5.1
    vite: 5.2.10 => 5.2.10
    vitest: 1.5.1 => 1.5.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.

Can you check if v1.5.0 works? Also just in case, can you test without coverage on v1.5.1?

1.5.0 started failing on all my snapshots.
1.5.2 (just released 4/25) works on all snapshots -  But dies with 1 error (exact same suite of tests)
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Failed to fetch dynamically imported module: http://localhost:5173/@id/@vitest/coverage-istanbul
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Coverage enabled false stops the error completely.

I'm unable to reproduce this. It works fine here: https://github.com/AriPerkkio/aria-live-capture/pull/191.
Without reproduction setup there is nothing we could do. I would recommend to check your package manager's lockfile. Make sure all Vitest packages have the same version.
$ pnpm test

> aria-live-capture@1.0.2 test /x/aria-live-capture
> vitest run

 RUN  v1.5.2 /x/aria-live-capture
      [Browser] Browser runner started at http://localhost:5173/
      Coverage enabled with istanbul

 ✓ |Browser| test/capture-announcements.test.ts (109)
 ✓ |Browser| test/utils.test.ts (56)

 Test Files  2 passed (2)
      Tests  164 passed | 1 todo (165)
   Start at  17:26:55
   Duration  613ms (transform 0ms, setup 10ms, collect 144ms, tests 23ms, environment 0ms, prepare 0ms)

 % Coverage report from istanbul
--------------------------|---------|----------|---------|---------|--------------------------------
File                      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--------------------------|---------|----------|---------|---------|--------------------------------
All files                 |   90.25 |     85.5 |   97.87 |    93.3 |
 capture-announcements.ts |   83.67 |     75.3 |   93.33 |   89.28 | 69,117,151-152,161-168,177,207
 config.ts                |     100 |      100 |     100 |     100 |
 dom-node-safe-guards.ts  |     100 |      100 |     100 |     100 |
 interceptors.ts          |   88.46 |    76.92 |     100 |   88.46 | 18,56,64
 queries.ts               |   95.23 |    94.44 |     100 |   97.36 | 38
 utils.ts                 |   96.87 |    93.75 |     100 |   98.18 | 127
--------------------------|---------|----------|---------|---------|--------------------------------

authors: AriPerkkio hi-ogawa httpete


text:
feat(utils): Produce valid snapshot names

Description
The previous version of loupe pulled within Vitest was not properly splitting strings to produce names of snapshots. The proposed PR bumps it and adds the relevant tests.
Fixes #5681
Note: I feel the lock has changed a bit more than what I would have expected. I updated it with pnpm@8.15.8 from a GitHub Codespace. I don't really get how to properly update it if it's not the right one.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[x] Ideally, include a test that fails without this PR but passes with it.
[x] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[x] Run the tests with pnpm test:ci.

Documentation

[x] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Looks good to me! Thank you! The lint error is also on main, two PRs merged too quickly 😄

authors: dubzzz sheremet-va


text:
docs have surprising call traces in outputs

Describe the bug
Here: https://bass-lang.org/stdlib.html#binding-with-port
This isn't exactly the output I would have expected for presenting that function:

Woops! I'll patch that up soon. :) Thanks. (It just needs to be quoted.)
I should probably tweak the docs to only allow errors where it expects there to be errors (e.g. when demonstrating backtraces).

I'll do it! 😃

authors: srenatus vito

repo: vito/bass


text:
Allow Mixins

I'm getting the error below and assume it is expected. I kind of need to use mixins. Can we put as feature request?
[SEVERE] floor_generator:floor_generator on lib/db/database.dart:
Entities and views are not allowed to inherit from mixins.

Hi! What's your use case for mixins in database entities?

I have entities that inherit from another generic class. The generic class allows me to access common fields across the board such as name & id. A few (a subset) of these entities share common fields that I would like to be able access in a sound manner (ensuring code linkage) in the same way I access the generic class. If I don't use mixins, I have no option but to get the fields by string, which can eventually break the code.
Example
class Animal{int getAge()}
class Dog extends Animal{}
class Cat extends Animal{}
class Bird extends Animal{}
I can:
print(Animal().getAge())
I cannot:
print(FlyingAnimal().getFlyingTime())
I believe I could use multiple levels of inheritance but haven't tried yet and not sure what is the rational to prevent the use of mixins as it would make more sense in my case to inject the methods I need. Another option is to add getters to a new generic Dao, but seems very entity/instance related to me.

I also used mixin in entity to apply EquatableMixin of equatable package. I know I can extends from Equatable class, but the use of EquatableMixin leaves the freedom to inherit from other classes.
It would be helpful if these limitations were stated in doc. I did not imagine that the application of a mixin, without fields, was not allowed.

I also used mixin in entity to apply

I also want to use Equatable library in my project just to not having to override == operator, hashCode and toString.

authors: BetterB0y Mabsten SUNbrightness idkq vitusortner

repo: vitusortner/floor


text:
Drop Python 3.9 support in favor of 3.12 and 3.13

I was able to update requirements.txt to work on Python 3.10-3.13. Unfortunately, the latest possible version of networkx that installs on Python 3.9 is 3.2.1, and a change in networkx 3.4 breaks our plot_topology function. I could add logic to determine the version of networkx and do different things depending on whether it is greater or less than 3.4, but that sounds unnecessarily complicated. Instead, I think it makes more sense to just bump the required Python version to 3.10 and networkx version to 3.4. For context, Python 3.9 reaches end-of-life in 2025-10, and big packages like Numpy and Scipy have already dropped support for it.
Other changes include:

Assorted pylint and mypy fixes
Change default multiprocessing start method to forkserver on Linux to fix python/cpython#110770 (default will be forkserver in Python 3.14 anyways)

By creating this pull request, I agree to the Contributor License
Agreement, which is available in CLA.md at the top level of this
repository.

Thanks @thalassemia! So is there topology graphing as it currently stands?

plot_topology works in the current release as long as you have networkx<3.4. I think those older versions of networkx should work on Python 3.10-3.13 as well. I don't think it is a good idea to cap the networkx version to address the issue with networkx 3.4+.

@thalassemia -- looks like there are still some 3.9-related tests hanging. Can you remove these from the GitHub actions?

I think those are required by some repository setting that I can't access. Instead of hanging they're just not being run. These docs might be helpful.

authors: eagmon thalassemia

repo: vivarium-collective/vivarium-core


text:
Add prop to render FormSection without Typography

Previously, only when passing a string into the title prop,
the title would be wrapped by a Typography.
The thought behind this, was that a generic style would be added to the
title-text by default and when a custom component (e.g. Typography) was
needed that could simply be passed into the title prop and the
generic Typography would not be rendered.
The issue with this method was, that when passing in a component that
simply returned a text (e.g. FormattedMessage), the title would not
have the generic style because the type was not a string.

alternative idea; renderTitle prop with default value (title) => <Typography>{title}</Typography>? Or is that too difficult to override. How often do you have to override it?

alternative idea; renderTitle prop with default value (title) => <Typography>{title}</Typography>? Or is that too difficult to override.

The reason I used a separate prop, was to stay consistent with material-ui: https://mui.com/api/list-item-text/#props

How often do you have to override it?

I don't think we use it very often, if at all 🤔

alternative idea; renderTitle prop with default value (title) => <Typography>{title}</Typography>? Or is that too difficult to override. How often do you have to override it?

Also I don't want to write a function every time I set a title:
<FormSection title={'MyTitle'}> vs <FormSection title={() => 'MyTitle'} />
And allowing React.Node and () => React.Node adds too much complexity imo...

authors: jamesricky nsams

repo: vivid-planet/comet-admin


text:
Changes file

Hi! This is really useful tool.
The change-log any kind will be very useful. To track what's going on and what a new release gives me.
Thanks

You can refer release notes for change logs - https://github.com/vividvilla/csvtotable/releases
In next release I will add a detailed change log for every release.

Sounds good, thanks

authors: melezhik vividvilla

repo: vividvilla/csvtotable

license: mit

license_source: bigquery


text:
Make Enter submit settings form

Similar to Delete File Confirmation modal - it would be nice if "Enter" submits the modal (like clicking "Done").

I feel like this maybe was worked on at some point, but it seems that it currently does not close the modal when you hit Enter.

repo: vizhub-core/vzcode


text:
Add deps.rs badge to README

I have noticed that many dependencies are outdated. Upgrading them requires migrating existing code. Relying on unmaintained versions is not an option.
This PR adds a deps.rs badge to the README to show the current status.

Happy to add this badge, but just note that some of the code changes required to update these dependencies is quite substantial. For example, the winit update brought a lot of API breaking changes that we're still trying to work through.

...some of the code changes required to update these dependencies is quite substantial.

Sure. I noticed this too. All this does not need to be fixed immediately. But we should be aware of it.
Keeping pace with the building blocks is essential, especially during the early phase. Those breaking changes might even affect architectural decisions. Ignoring them for too long could be fatal.

repo: vizia/vizia


text:
Possibilty to (force)reset app

Some 2 years ago a consultant entered 2 of our apps with authorization but we never started using Object Ninja.
At this point we would like to but for these apps we cannot, it would be great if these can be "reset" so we can start using it again.
On use we get:
"Cannot communicate with the back-end API. Your app authorization key may be missing or wrong, or your API key may be misconfigured."
On deauthorize we get:
"You cannot deauthorize app [appName] (in folder [folder]) because it is not authorized."
On authorize we get:
"Application [appName] (in folder [folder]) is already authorized. You must first deauthorize it if you want to authorize it again."

We have the same issue.
I think when you lost the API key it's not possible to access object ninja anymore.

authors: RaimondStokkel mbiesbrouck-esc

repo: vjekob/al-objid


text:
Windows unzipping appears to be broken again

Hello,
Currently I am unable to complete a fresh install of Filebeat 7.9.1 on Windows 10/Server 2019 using the basic default recipe.  Not sure if this is a duplicate of https://github.com/elastic/beats/issues/9259 but the output from the Chef run seems to indicate so.  Please let me know if I can provide more information:

Recipe: filebeat::default
  * filebeat_install[default] action create
    * remote_file[filebeat_package_file] action create
      - create new file C:\chef\cache/filebeat-7.9.1-windows-x86_64.zip
      - update content in file C:\chef\cache/filebeat-7.9.1-windows-x86_64.zip from none to a8716e
      (file sizes exceed 10000000 bytes, diff output suppressed)
    * directory[C:/opt/filebeat] action create
      - create new directory C:/opt/filebeat
    * windows_zipfile[C:/opt/filebeat] action unzip[2020-09-18T14:27:47-05:00] WARN: The windows_zipfile resource has been deprecated as Chef Infra Client 15.0 shipped with a new archive_file resource, which natively handles multiple archive formats. Please update any cookbooks using this resource to instead use the `archive_file` resource: https://docs.chef.io/resource_archive_file.html

      - unzip C:\chef\cache/filebeat-7.9.1-windows-x86_64.zip
      * ruby_block[Unzipping] action run

        ================================================================================
        Error executing action `run` on resource 'ruby_block[Unzipping]'
        ================================================================================

        Errno::EINVAL
        -------------
        Invalid argument @ rb_sysopen - C:/opt/filebeat/filebeat-7.9.1-windows-x86_64/module/

        Resource Declaration:
        ---------------------
        # In C:/chef/cache/cookbooks/windows/resources/zipfile.rb

         54:     ruby_block 'Unzipping' do
         55:       block do
         56:         Zip::File.open(cache_file_path) do |zip|
         57:           zip.each do |entry|
         58:             path = ::File.join(new_resource.path, entry.name)
         59:             FileUtils.mkdir_p(::File.dirname(path))
         60:             if new_resource.overwrite && ::File.exist?(path) && !::File.directory?(path)
         61:               FileUtils.rm(path)
         62:             end
         63:             zip.extract(entry, path) unless ::File.exist?(path)
         64:           end
         65:         end
         66:       end
         67:       action :run

        Compiled Resource:
        ------------------
        # Declared in C:/chef/cache/cookbooks/windows/resources/zipfile.rb:54:in `block (2 levels) in class_from_file'

        ruby_block("Unzipping") do
          action [:run]
          default_guard_interpreter :default
          declared_type :ruby_block
          cookbook_name "filebeat"
          block #<Proc:0x00000000073f61a8@C:/chef/cache/cookbooks/windows/resources/zipfile.rb:55>
          block_name "Unzipping"
        end

        System Info:
        ------------
        chef_version=14.12.9
        platform=windows
        platform_version=10.0.18363
        ruby=ruby 2.5.5p157 (2019-03-15 revision 67260) [x64-mingw32]
        program_name=C:/opscode/chef/bin/chef-client
        executable=C:/opscode/chef/bin/chef-client

      ================================================================================
      Error executing action `unzip` on resource 'windows_zipfile[C:/opt/filebeat]'
      ================================================================================

      Errno::EINVAL
      -------------
      ruby_block[Unzipping] (C:/chef/cache/cookbooks/windows/resources/zipfile.rb line 54) had an error: Errno::EINVAL: Invalid argument @ rb_sysopen - C:/opt/filebeat/filebeat-7.9.1-windows-x86_64/module/

      Resource Declaration:
      ---------------------
      # In C:/chef/cache/cookbooks/filebeat/resources/install.rb

       78:     windows_zipfile new_resource.windows_base_dir do
       79:       source package_file
       80:       action :unzip
       81: #      not_if { ::File.exist?(new_resource.conf_dir + '/install-service-filebeat.ps1') }
       82:       notifies :run, 'powershell_script[install filebeat as service]', :immediately
       83:     end
       84:

      Compiled Resource:
      ------------------
      # Declared in C:/chef/cache/cookbooks/filebeat/resources/install.rb:78:in `block in class_from_file'

      windows_zipfile("C:/opt/filebeat") do
        action [:unzip]
        default_guard_interpreter :default
        declared_type :windows_zipfile
        cookbook_name "filebeat"
        source "C:\\chef\\cache/filebeat-7.9.1-windows-x86_64.zip"
      end

      System Info:
      ------------
      chef_version=14.12.9
      platform=windows
      platform_version=10.0.18363
      ruby=ruby 2.5.5p157 (2019-03-15 revision 67260) [x64-mingw32]
      program_name=C:/opscode/chef/bin/chef-client
      executable=C:/opscode/chef/bin/chef-client

    ================================================================================
    Error executing action `create` on resource 'filebeat_install[default]'
    ================================================================================

    Errno::EINVAL
    -------------
    windows_zipfile[C:/opt/filebeat] (C:/chef/cache/cookbooks/filebeat/resources/install.rb line 78) had an error: Errno::EINVAL: ruby_block[Unzipping] (C:/chef/cache/cookbooks/windows/resources/zipfile.rb line 54) had an error: Errno::EINVAL: Invalid argument @ rb_sysopen - C:/opt/filebeat/filebeat-7.9.1-windows-x86_64/module/

    Resource Declaration:
    ---------------------
    # In C:/chef/cache/cookbooks/filebeat/recipes/default.rb

      7: filebeat_install 'default' do
      8:   version '7.9.1'
      9:   action :create
     10: end
     11:

    Compiled Resource:
    ------------------
    # Declared in C:/chef/cache/cookbooks/filebeat/recipes/default.rb:7:in `from_file'

    filebeat_install("default") do
      action [:create]
      updated true
      updated_by_last_action true
      default_guard_interpreter :default
      declared_type :filebeat_install
      cookbook_name "filebeat"
      recipe_name "default"
      version "7.9.1"
      conf_dir "C:/opt/filebeat/filebeat-7.9.1-windows-x86_64"
      prospectors_dir "C:/opt/filebeat/filebeat-7.9.1-windows-x86_64/conf.d"
      log_dir "C:/opt/filebeat/filebeat-7.9.1-windows-x86_64/logs"
    end

    System Info:
    ------------
    chef_version=14.12.9
    platform=windows
    platform_version=10.0.18363
    ruby=ruby 2.5.5p157 (2019-03-15 revision 67260) [x64-mingw32]
    program_name=C:/opscode/chef/bin/chef-client
    executable=C:/opscode/chef/bin/chef-client

Running handlers:
[2020-09-18T14:27:48-05:00] ERROR: Running exception handlers
Running handlers complete
[2020-09-18T14:27:48-05:00] ERROR: Exception handlers complete
Chef Client failed. 2 resources updated in 06 seconds
[2020-09-18T14:27:48-05:00] FATAL: Stacktrace dumped to C:/chef/cache/chef-stacktrace.out
[2020-09-18T14:27:48-05:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2020-09-18T14:27:48-05:00] FATAL: Errno::EINVAL: filebeat_install[default] (filebeat::default line 7) had an error: Errno::EINVAL: windows_zipfile[C:/opt/filebeat] (C:/chef/cache/cookbooks/filebeat/resources/install.rb line 78) had an error: Errno::EINVAL: ruby_block[Unzipping] (C:/chef/cache/cookbooks/windows/resources/zipfile.rb line 54) had an error: Errno::EINVAL: Invalid argument @ rb_sysopen - C:/opt/filebeat/filebeat-7.9.1-windows-x86_64/module/

If anyone stumbles across this issue, the root cause is in the Windows cookbook.  The "fix" can be found here:
https://github.com/chef-cookbooks/windows/issues/459#issuecomment-428303562

repo: vkhatri/chef-filebeat


text:
Build error

Not sure whether this is related to this plugin, but I'm getting  expressions are not allowed at the top level errors from a brand new library creation (via swift package init --type=library). The only content is boilerplate:
struct Rationals {
    var text = "Hello, World!"
}

Any ideas on what the problem might be?

Fixed - but not quite sure how.

This behavior sounds weird. If this this happens again, you can reopen this issue and I will have a deeper look.

authors: sbromberger vknabel


text:
[LAB] Week 1_Problem 1_이창섭

Problem
Week 1_Problem 1
Source Code
import torch
from random import random
from typing import Callable

##                        Problem 1                           ##
##                                                            ##
##         Arbitrary quadratic function will be given.        ##
## Return the optimal point(global minimum) of given function ##
##          Condition: highest order term is positive         ##
##                  Made by @jangyoujin0917                   ##
##                                                            ##

def solution(func: Callable, start_point: float) -> float: # DO NOT MODIFY FUNCTION NAME
    x = torch.tensor(start_point, requires_grad=True, dtype=torch.float32)
    grad = torch.tensor([1.0]*1)
    lr = 1e-6
    for i in range(10000):

        func(x).backward(grad, retain_graph=True)
        x.data = x.data - lr * x.grad.data

    return x ### IMPLEMENT FROM HERE

if __name__ == "__main__":
    def test_func(x): # function for testing;function for evaluation will be different.
        return x ** 2
    t = torch.tensor([10*random()], requires_grad=True, dtype=torch.float32)
    print(solution(test_func, t))

Description
return x.data
Output (Optional)
No response

This issue is closed now because of the lack of progress.

authors: Dongyeongkim Elemorld


text:
Remove Sampler copy stream

We don't really need an extra stream in sampler to still benefit from non-blocking execution. This will add 5-10 microseconds of overhead, which I think is an acceptable tradeoff for stronger consistency guarantees.
Supersedes https://github.com/vllm-project/vllm/pull/2190 and https://github.com/vllm-project/vllm/pull/2177
cc @esmeetu @ZiyueHuang

@esmeetu can you see if this fixes your issue?

@esmeetu can you see if this fixes your issue?

Yes. This is ok for me.

repo: vllm-project/vllm


text:
[Misc] p90 and p95 for serving benchmark

Similar to #3889 , we need more percentiles for serving benchmark.
Here are p99 latencies I get across 3 runs:
# p99 ttft, tpot, itl
532.92, 376.76, 583.86
740.69, 446.66, 622.48
597.21, 446.70, 603.08

And here are p95 and p90 ttfts I get:
# p95 ttft, tpot, itl
400.04, 334.96, 456.39
432.17, 402.84, 482.56
435.90, 398.58, 469.09

# p90 ttft, tpot, itl
332.99, 302.66, 426.95
318.51, 356.61, 453.11
340.88, 349.29, 429.15

============ Serving Benchmark Result ============
Successful requests:                     1000
Benchmark duration (s):                  128.37
Total input tokens:                      213987
Total generated tokens:                  199771
Request throughput (req/s):              7.79
Input token throughput (tok/s):          1666.99
Output token throughput (tok/s):         1556.25
---------------Time to First Token----------------
Mean TTFT (ms):                          157.75
Median TTFT (ms):                        118.73
P90 TTFT (ms):                           332.99
P95 TTFT (ms):                           400.04
P99 TTFT (ms):                           532.92
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms):                          218.36
Median TPOT (ms):                        223.08
P90 TPOT (ms):                           302.66
P95 TPOT (ms):                           334.96
P99 TPOT (ms):                           376.76
---------------Inter-token Latency----------------
Mean ITL (ms):                           193.60
Median ITL (ms):                         153.55
P90 ITL (ms):                            426.95
P95 ITL (ms):                            456.39
P99 ITL (ms):                            583.86
==================================================

============ Serving Benchmark Result ============
Successful requests:                     1000
Benchmark duration (s):                  133.89
Total input tokens:                      213987
Total generated tokens:                  199770
Request throughput (req/s):              7.47
Input token throughput (tok/s):          1598.24
Output token throughput (tok/s):         1492.06
---------------Time to First Token----------------
Mean TTFT (ms):                          164.40
Median TTFT (ms):                        120.63
P90 TTFT (ms):                           318.51
P95 TTFT (ms):                           432.17
P99 TTFT (ms):                           740.69
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms):                          239.02
Median TPOT (ms):                        235.90
P90 TPOT (ms):                           356.61
P95 TPOT (ms):                           402.84
P99 TPOT (ms):                           446.66
---------------Inter-token Latency----------------
Mean ITL (ms):                           207.69
Median ITL (ms):                         165.18
P90 ITL (ms):                            453.11
P95 ITL (ms):                            482.56
P99 ITL (ms):                            622.48
==================================================

============ Serving Benchmark Result ============
Successful requests:                     1000
Benchmark duration (s):                  131.26
Total input tokens:                      213987
Total generated tokens:                  199775
Request throughput (req/s):              7.62
Input token throughput (tok/s):          1630.27
Output token throughput (tok/s):         1522.00
---------------Time to First Token----------------
Mean TTFT (ms):                          166.36
Median TTFT (ms):                        118.69
P90 TTFT (ms):                           340.88
P95 TTFT (ms):                           435.90
P99 TTFT (ms):                           597.21
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms):                          232.90
Median TPOT (ms):                        228.07
P90 TPOT (ms):                           349.29
P95 TPOT (ms):                           398.58
P99 TPOT (ms):                           446.70
---------------Inter-token Latency----------------
Mean ITL (ms):                           201.46
Median ITL (ms):                         159.46
P90 ITL (ms):                            429.15
P95 ITL (ms):                            469.09
P99 ITL (ms):                            603.08
==================================================

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

I personally don't mind this change for the benchmark script itself (and I originally didn't add it because P99 is most use cases care about).
However, this change does affect the result parsing of our CI, so I will leave this PR to @KuntaiDu to review!

I personally don't mind this change for the benchmark script itself (and I originally didn't add it because P99 is most use cases care about).
However, this change does affect the result parsing of our CI, so I will leave this PR to @KuntaiDu to review!

Thanks for your response!
I'm currently working on some optimizations and have been using the benchmark script to evaluate the effectiveness. In my cases, P99 is unstable and usually doesn't show what's really going on with the performance.
I am glad to help update the result parsing. Is it related to the failed checks?


text:
Failure to decode extension Addition Group [[ .. ]] for ASN.1 PER bit aligned.

Hi
I am testing 0.9.28
I can generate LTE RRC decoder however all messages including extension Addition Group [[ ]]] fail decoding.
Error looks like
AD: Processing RRC_conn_setup.txt
AD: Decoding 39 bytes
AD: decode(0) consumed 0+0b (39), code 2
AD: Clean up partially decoded DL-CCCH-Message
AD: ofp 1, no=0, oo=0, dbl=0
RRC_conn_setup.txt: Decode failed past byte 0: Input processing error
Now if I replace the [[ ]] construct with equivalent ASN.1 syntax extensionAdditionGroup SEQUENCE {}, decoding is successful.
Issue is not blocking but annoying as I cannot directly work from 3GPP ASN.1 syntax.
Example: original 3GPP ASN.1 (decoding fails):
[[	-- DL configuration as well as configuration applicable for DL and UL
csi-RS-ConfigNZPToReleaseList-r11
CSI-RS-ConfigNZPToReleaseList-r11	OPTIONAL,		-- Need ON
csi-RS-ConfigNZPToAddModList-r11
CSI-RS-ConfigNZPToAddModList-r11	OPTIONAL,		-- Need ON
csi-RS-ConfigZPToReleaseList-r11
CSI-RS-ConfigZPToReleaseList-r11	OPTIONAL,		-- Need ON
csi-RS-ConfigZPToAddModList-r11	CSI-RS-ConfigZPToAddModList-r11	OPTIONAL,		-- Need ON
epdcch-Config-r11				EPDCCH-Config-r11				OPTIONAL,		-- Need ON
pdsch-ConfigDedicated-v1130		PDSCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
-- UL configuration
cqi-ReportConfig-v1130			CQI-ReportConfig-v1130			OPTIONAL,		-- Need ON
pucch-ConfigDedicated-v1130		PUCCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
pusch-ConfigDedicated-v1130		PUSCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
uplinkPowerControlDedicated-v1130
UplinkPowerControlDedicated-v1130	OPTIONAL		-- Need ON
]],
Modified 3GPP ASN.1 with equivalent construct (decoding works perfectly):
extensionAdditionGroup4 SEQUENCE {	-- DL configuration as well as configuration applicable for DL and UL
	csi-RS-ConfigNZPToReleaseList-r11
								CSI-RS-ConfigNZPToReleaseList-r11	OPTIONAL,		-- Need ON
	csi-RS-ConfigNZPToAddModList-r11
								CSI-RS-ConfigNZPToAddModList-r11	OPTIONAL,		-- Need ON
	csi-RS-ConfigZPToReleaseList-r11
								CSI-RS-ConfigZPToReleaseList-r11	OPTIONAL,		-- Need ON
	csi-RS-ConfigZPToAddModList-r11	CSI-RS-ConfigZPToAddModList-r11	OPTIONAL,		-- Need ON
	epdcch-Config-r11				EPDCCH-Config-r11				OPTIONAL,		-- Need ON
	pdsch-ConfigDedicated-v1130		PDSCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
-- UL configuration
	cqi-ReportConfig-v1130			CQI-ReportConfig-v1130			OPTIONAL,		-- Need ON
	pucch-ConfigDedicated-v1130		PUCCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
	pusch-ConfigDedicated-v1130		PUSCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
	uplinkPowerControlDedicated-v1130
								UplinkPowerControlDedicated-v1130	OPTIONAL		-- Need ON
},

Thank you very much for your help
Best regards
D. Bressanelli

@dbresan2, I submitted a pull request #238 to address this extension group [[...]] issue.

hi @brchiu ,
Good day. I met the same issue. And with the fix #238, I still failed to decode extension Addition Group [[ .. ]] of RRC.
I tried to decode LTE RRC DL_DCCH_Message 20 02 01 80 02 C2 00 08 20 C0 but return fail.
There is some issue in handling extension Addition Group
asn:
PhysicalConfigDedicated ::=		SEQUENCE {
pdsch-ConfigDedicated				PDSCH-ConfigDedicated			OPTIONAL,		-- Need ON
pucch-ConfigDedicated				PUCCH-ConfigDedicated			OPTIONAL,		-- Need ON
pusch-ConfigDedicated				PUSCH-ConfigDedicated			OPTIONAL,		-- Need ON
uplinkPowerControlDedicated			UplinkPowerControlDedicated		OPTIONAL,		-- Need ON
tpc-PDCCH-ConfigPUCCH				TPC-PDCCH-Config				OPTIONAL,		-- Need ON
tpc-PDCCH-ConfigPUSCH				TPC-PDCCH-Config				OPTIONAL,		-- Need ON
cqi-ReportConfig					CQI-ReportConfig				OPTIONAL,		-- Cond CQI-r8
soundingRS-UL-ConfigDedicated		SoundingRS-UL-ConfigDedicated	OPTIONAL,		-- Need ON
antennaInfo							CHOICE {
explicitValue						AntennaInfoDedicated,
defaultValue						NULL
}																	OPTIONAL,	-- Cond AI-r8
schedulingRequestConfig				SchedulingRequestConfig			OPTIONAL,		-- Need ON
...,
[[	cqi-ReportConfig-v920				CQI-ReportConfig-v920		OPTIONAL,		-- Cond CQI-r8
antennaInfo-v920					AntennaInfoDedicated-v920	OPTIONAL		-- Cond AI-r8
]],
[[	antennaInfo-r10					CHOICE {
explicitValue-r10				AntennaInfoDedicated-r10,
defaultValue					NULL
}																OPTIONAL,	-- Cond AI-r10
antennaInfoUL-r10				AntennaInfoUL-r10				OPTIONAL,		-- Need ON
cif-Presence-r10				BOOLEAN							OPTIONAL,		-- Need ON
log:
//read the extensions bitmap correctly but did not handle it as extensions as I see:
Extensions 12 present in PhysicalConfigDedicated (constr_SEQUENCE.c:1200)
[PER got 12<=38 bits => span 54 +5[14..40]:c2 (26) => 0x80] (asn_bit_data.c:132)
Read in extensions bitmap for PhysicalConfigDedicated of 12 bits (8..) (constr_SEQUENCE.c:1214)
[PER got  1<=12 bits => span 1 +0[1..12]:08 (11) => 0x0] (asn_bit_data.c:132)
[PER got  1<=11 bits => span 2 +0[2..12]:08 (10) => 0x0] (asn_bit_data.c:132)
[PER got  1<=10 bits => span 3 +0[3..12]:08 (9) => 0x0] (asn_bit_data.c:132)
[PER got  1<= 9 bits => span 4 +0[4..12]:08 (8) => 0x0] (asn_bit_data.c:132)
[PER got  1<= 8 bits => span 5 +0[5..12]:08 (7) => 0x1] (asn_bit_data.c:132)
Decoding member cif-Presence-r10 in PhysicalConfigDedicated (nil) (constr_SEQUENCE.c:1238)

hi @brchiu ,
After upgraded to the latest version.
I can decode extension Addition Group now.
Thanks.


text:
What can I do to make HTML_TOC support Simplified Chinese

HTML_TOC currently only supports English, but I need it to support Simplified Chinese, What can I do？

i was working with something similar, you could fork the project and modify the c library that works with the headers and add the chinesse characters... that would be painful, i would just add a post processor on ruby that adds the id tag to your headers,
	def md_generator(raw_text)
		renderer = ExtraRenderOptions.new(hard_wrap: true, with_toc_data: true)
		options = {
			fenced_code_blocks: true,
			tables: true,
			space_after_headers: true,
			strikethrough: true,
			footnotes: true,
			autolink: true,
			no_intra_emphasis: true
		}
		post_process(Redcarpet::Markdown.new(renderer, options).render(raw_text)).html_safe
	end
	def post_process(md_text)
		md_text.each_line do |line|
			#TODO: parse the title with maybe nokogiri
			title = "title parsed"
			line.gsub("
", "
'")
		end
	end

here some info about get the title http://readysteadycode.com/howto-extract-data-from-html-with-ruby
as a bonus, i'm getting my tocs with this code
	# deep is how many levels i want, h1, h2 and h3 would be 3
	def toc(deep)
		current_line = 0;
		prefix = ""
		output = %(## Table of Contents
\r\n\r\n)
		content.each_line do |line|
			forbidden_words = ['Table of contents', 'define', 'pragma']
			next if !line.start_with?("#") || forbidden_words.any? { |w| line =~ /#{w}/ } || line.split.first.count("#") > deep || line.split.first.count("#") != line.split.first.length
			if line.split.first.count("#") == 1
				current_line += 1
				prefix = "#{current_line}."
			else
				prefix = "*"
			end
			title = line.gsub("#", "").strip
			href = title.gsub('"', ' quot ').gsub("'", " 39 ").parameterize
			output+= "   " * (line.split.first.count("#")-1) + "#{prefix} [#{title}](\##{href})\r\n"
		end
		output+= "\r\n"
	end

.gsub('"', ' quot ').gsub("'", " 39 ") this part is because the c library that makes de tocs ids replace " and ' with quot and 39, hope this helps

Hi there,
Sorry I haven't given any answer sooner but waiting this bug to be fixed, you can implement a custom render object rather than doing some post-processing like you did @zerocool4u2. There's an example here : https://github.com/vmg/redcarpet/pull/539#issuecomment-245724637.
I'm going to give this a close as a duplicate of #538 hoping that I will be able to fix it soon, thanks anyway guys ! :-)

Thank you for your answer, I have rewritten the header method to solve this problem, but not very beautiful

repo: vmg/redcarpet


text:
rebase rules should be able to support "merging" of arrays

In some cases will want to create custom ServiceAccount whose secret's section is filled in with list of secrets. At the same time cluster is also adding array items (token secrets). There should be a way to rebase that results in a merge?

this behaviour is more pronounced in kapp-controller usage of kapp since reconciliation will be continuous causing unnecessary churn.

Explicitly: any process that relies on kapp diff to determine the need for processing experiences churn.
#191 is another example of this.

authors: cppforlife pivotaljohn

repo: vmware-tanzu/carvel-kapp


text:
Persist CSR PrivateKey across Host-Agent restarts

The private key generated for the create CSR workflow should be persisted in case of the host-agent restarts before we could create the newer kubeconfig.

Done as part of #541


text:
Fix: Read kubeconfig first even with --bootstrap-kubeconfig flag

What this PR does / why we need it:
In the exisitng implementation, If the user passes the --bootstrap-kubeconfig in repeated invocations of the agent in the same host, the code flow is to create CSR again, but the k8s API k8s.io/client-go/util/certificate/csr.RequestCertificate tries to use the existing CSR and it will fail due to Certificate Key mismatch.  With this PR, kubeconfig if existing as ~/.byoh/config will be used even with the --bootstrap-kubeconfig flag passed.
Which issue(s) this PR fixes :
Fixes #598

LGTM 👍


text:
Add ADOPTERS file

Signed-off-by: davidmirror-ops daespejo@vmware.com
What this PR does / why we need it: This PR will add an ADOPTERS file to showcase Octant adopters
Which issue(s) this PR fixes

Fixes #

Special notes for your reviewer:
Release note:
release-note

Latest commit is a revised and condensed version of the ADOPTERS file text. If it's approved, it will be used as the baseline to start adding content to it.

repo: vmware-tanzu/octant


text:
Content: Building a Kubernetes Platform - Announcing TCE for Developers

Summary of content
VMware Tanzu Community Edition gives developers another tool in their toolbox to learn and use Kubernetes to deploy their workloads.
Summary of audiences
Developers interested in learning or getting started with Kubernetes and adjacent tooling.
Level of content
Level of content as it pertains to the topic proposed. Delete those not applicable.

101: "Awareness / Exploration"

Contributor Checklist

[x] I have added a card to the GitHub Content Backlog and/or moved it to the proper column. See Content Prewriting and Ideation
[x] If contributing via Google Docs: I have added a link to my document to this issue, and set the document's Share settings to "Anyone on the internet with this link can comment".
[x] My content is drafted in accordance with existing style guides and best practices. See Drafting Content
[x] The front matter (metadata) is filled out completely (e.g. description, topics, tags, author, etc - as appropriate for the content type). See Drafting Content
[x] My content has been reviewed by my team for technical accuracy. See Editing Content
[x] My content has beed reviewed and edited by a copy editor. See Editing Content
[x] If applicable: My content has gone through a legal review (VMware Employees Only). See Editing Content
[x] If applicable: I have tested my content locally and everything passes. See Testing Content
[x] Optional: I have filled out the Social Media request form (optional) (VMware Employees Only). See Next Steps
[x] If applicable: I have created an author page and opened a pull request to get it added. See Next Steps

Reviewer Checklist

[x] Review if the content is a good fit for the Tanzu Developer Center. See Content Prewriting and Ideation
[x] There this GitHub issue has been added to the content backlog project
[x] Ensure with the author that the content has been reviewed for technical accuracy.
[x] Ensure with the author that the content has been through copy editing.
[x] If applicable: Ensure with the author that the content has been through Legal review.
[x] Review fit with the Tanzu Developer Center Style Guide and the VMware Style Guide (VMware Employees Only).
[x] Ensure the front matter is filled out correctly and completely.
[x] If applicable: Review additions to custom_dict.txt.
[x] Ensure with the author they have reviewed the staging site for correctness. The reviewer should review this too.
[x] If applicable: Review any new Team pages.
[x] Optional: Ensure the author has provided copy for Social Media distribution.\
[x] If contributing via Google Docs: Send the staging link to the author to review. The reviewer should review this too. Get the final 👍 from the author to push the content public.

Live link: https://tanzu.vmware.com/developer/blog/building-platforms-on-top-of-kubernetes/

repo: vmware-tanzu/tanzu-dev-portal


text:
Icon 'tag' does not paint with the CSS font color

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior
the code below should paint the 'tag' clarity-icon in white.
Actual behavior
the code below paints the 'tag' clarity-icon in black.
Reproduction of behavior
HTML:
<clr-icon shape='tag' class='my-icon'></clr-icon>
CSS:
.my-icon{   color: #fff }
See screenshot attached:

Environment details

Clarity version:
0.8.4

@clementcur, thanks for informing us about this bug. Some icons have fill attribute that's preventing the color style from taking effect.

SVG uses fill, not color.
That said, we can make the default 'fill: currentColor' and that should do what you want.
As a workaround until then please use 'fill: #fff' instead of color. Or in addition to it if you want.

Since this is working as designed, I removed the bug designation. It's more of an enhancement.

@mathisscott thx for the tip.
I tried out the fill attribute, but it still does not apply the fill color to that svg icon. Though it's working for some other icons, e.g. 'dashboard'.
So, it looks like the 'tag' icon fill value is ignored and always set to '#231f20'.

tags_icons.zip
hi @Shijir I found that my original .svg files were using #231f20 instead of #000000. So you can blame this one on me. 😞  I'm attaching the corrected files with the color set to #000000, in case that helps.

tag_single_icon.zip
This problem was found in the singular tag icon as well. Corrected svg files attached. Thanks Shijir!

@lil-kim it's okay. I have now unit tests that catch these kinds of overlooked parts. 😎

Thx for the prompt fix!

authors: Shijir clementcur lil-kim mathisscott

repo: vmware/clarity


text:
The built in SORT and FILTER do NOT support *ngFor

Select one ...  (check one with "x")
[X] bug
[ ] feature request
[ ] enhancement

Expected behavior
built in SORT and FILTER work well if use *ngFor to loop data in datagrid.
Actual behavior
built in SORT and FILTER DO NOT work if use *ngFor to loop data in datagrid.
We want to use *ngFor to support server backend pagination. Meanwhile, enabling the built in SORT and Filter is also required. But seems these two functions are conflict.
Reproduction of behavior

Include a link to the reproduction scenario you created by forking one of the Clarity Plunker Templates:

https://plnkr.co/edit/jMCyX9
Environment details

Angular version: 4.0.X

Clarity version: 0.9.X

OS and version: MAC 10.11.4

**Browser:**ALL

Can implement one custom sorter or filter to be compatible with *ngFor?

The best I can do is redirect you to our documentation on server-driven datagrids:

An important thing to note is that when the server does handle pagination, it needs to also deal with sorting and filtering, because all three are tightly coupled.

and

Since you don't have all the data available at once, you cannot use the smart iterator *clrDgItems: it would sort, filter and paginate a subset of the data that has already gone through all that. So all you need to do is to go back to a simple *ngFor, which we support.

*clrDgItemsfor server pagination makes absolutely no sense. You'd sort and filter the contents of a page, not the whole dataset.
Also, just like your other issues, your plunker isn't even working, it crashes when loading.

@youdz
I understand clearly about the differences between *clrDgItems and *ngFor as I have read the doc many times to find a proper solution.
What I mean is if we use *ngFor to support our server end pagination, is it possible to enable the column sort and filter with custom comparators and filters like 'clrDgField' does?

The meaning of page object in the State object is very confusion.
Object from:0 size:15 to:14
Or implement the filter function by ourselves as we currently do.

Additionally, if use *ngFor, an error may appear:
<clr-dg-row *ngFor="let user of users">
 VM1274 DatagridRow.ngfactory.js:695 ERROR Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'false'. Current value: 'true'.     at viewDebugError (VM591 core.umd.js:8618)     at expressionChangedAfterItHasBeenCheckedError (VM591 core.umd.js:8596)     at checkBindingNoChanges (VM591 core.umd.js:8760)     at checkNoChangesNodeInline (VM591 core.umd.js:12314)     at checkNoChangesNode (VM591 core.umd.js:12288)     at debugCheckNoChangesNode (VM591 core.umd.js:12907)     at debugCheckDirectivesFn (VM591 core.umd.js:12809)     at Object.View_DatagridRow_0.currVal_0 [as updateDirectives] (VM1274 DatagridRow.ngfactory.js:766)     at Object.debugUpdateDirectives [as updateDirectives] (VM591 core.umd.js:12791)     at checkNoChangesView (VM591 core.umd.js:12108)

I suggest to reopen this issue for discussing.

authors: steven-zou youdz


text:
fix(website): header docs in tablet view

Signed-off-by: Bogdan Bogdanov bbogdanov@vmware.com
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[x] clarity.design website / infrastructure changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

@hippee-lee  I thought that the do/dont component was bringing the issue but I found out that the angular component demos are written manually so this is what is needed for the headers to look okay on a tablet.

@hippee-lee  I thought that the do/dont component was bringing the issue but I found out that the angular component demos are written manually so this is what is needed for the headers to look okay on a tablet.


text:
Refactor member API

Completed by #2341 .

repo: vmware/harbor


text:
Clair conf change

1, update the interval of clair updater to 12 hours
2, update the interval for scan all to 2 hours

Coverage increased (+0.02%) to 54.703% when pulling c1bbcb5babff081828bae346f1863e8c0a14e4d4 on reasonerjt:clair-conf-change into 8a1b10ad7e81e8ff738e9857a7e72c2db22038f4 on vmware:master.

Coverage increased (+0.02%) to 54.703% when pulling c1bbcb5babff081828bae346f1863e8c0a14e4d4 on reasonerjt:clair-conf-change into 8a1b10ad7e81e8ff738e9857a7e72c2db22038f4 on vmware:master.

authors: coveralls reasonerjt


text:
Location sensor and permission mandatory for iOS 14 - Validated

HERALD on iOS 14 requires location sensor and user granting location permission to enable background BLE operation with other iOS and Android (all versions) devices.
Inserted comment in SensorArray to highlight this requirement.
No change to actual code.
Impact of location permission on iOS 14 was validated with the following combinations of devices

iPhone X iOS 14.2 with iPhone X iOS 14.1

Location disabled : Detection, RSSI, but no service, no read/write
Location enabled  : Fully functional

iPhone X iOS 14.2 with iPhone 6S iOS 12

Same behaviour

iPhone X iOS 14.2 with Pixel 2 Android 10

Same behaviour

iPhone X iOS 14.2 with Samsung J6 Android 9

Same behaviour

iPhone X iOS 14.2 with Samsung A20 Android 10

Same behaviour

iPhone X iOS 14.2 with iPhone X iOS 14.1 and Pixel 2 Android 10

Same behaviour

Enabling location permission by default.

Closed #35
Signed-off-by: c19x support@c19x.org

Note: Lack of this permission will affect all contact tracing protocols on iOS 14.2 including TraceTogether and GAEN.

repo: vmware/herald-for-ios


text:
Add a list of FileData objects to the Package class

Description
For situations where we know what files are associated with what package, we can add a list of files to the Package class.
To Do

Implement the list of FileData objects in the Package class
Write tests for the instance and methods

Super Issues
#480

@PrajwalM2212 Here is the issue you said you would work on.

repo: vmware/tern


text:
添加str_round_to函数

用于处理部分REST类接口，使用str作为委托价格、数量字段时，float数据小数点精度的问题

#2002

repo: vnpy/vnpy


text:
数据记录模块输出的时间模块还是不对

环境

操作系统: 如Windows 7
Anaconda版本: 如Anaconda 4.0.0 Python 2.7 32位
vn.py版本: 1.8

Issue类型
三选一：Bug
预期程序行为
数据记录日期正确
实际程序行为
超前的记录时间
{ "datetime" : ISODate("2018-03-18T09:00:00.600Z"),  "insertTime" : ISODate("2018-03-05T08:59:01.871Z"),  "symbol" : "i1805"}
{ "datetime" : ISODate("2018-03-18T09:00:01.100Z"),  "insertTime" : ISODate("2018-03-05T08:59:03.027Z"), "symbol" : "i1805"}
重现步骤
跑一下数据记录模块就出来。

datetime：交易所行情服务器切片时的时间戳
insertTime：本地将数据插入数据库时的时间戳
你说的错误指的是datetime落后于insertTime？这个可能是因为本地时钟和交易所比提前了导致的

不是上面所说的问题。
这个问题起始于当然修改CTP接口的日期，把晚盘日期修正为第二的日期。造成的。一直未能修改对。
本地时钟是OK的。

不是实盘数据吧，是不是simnow的问题

这个修改CTP接口日期的逻辑，是你自己添加的吗，还是vn.py现有系统里的？

不是我添加的。
是CTP-API中的 onRtnDepthMarketData 这个函数造成的：
这个函数在日期转换时，会遇到各种问题。这是之前的一个BUG。
大商所日期转换
    if tick.exchange is EXCHANGE_DCE:
        newTime = datetime.strptime(tick.time, '%H:%M:%S.%f').time()    # 最新tick时间戳

        # 如果新tick的时间小于夜盘分隔，且上一个tick的时间大于夜盘分隔，则意味着越过了12点
        if (self.tickTime and
            newTime < NIGHT_TRADING and
            self.tickTime > NIGHT_TRADING):
            self.tradingDt += timedelta(1)                          # 日期加1
            self.tradingDate = self.tradingDt.strftime('%Y%m%d')    # 生成新的日期字符串

        tick.date = self.tradingDate    # 使用本地维护的日期

        self.tickTime = newTime         # 更新上一个tick时间

这个好像真的是bug，假设是9:00，并且第二天早上盘前重启，
9:00<NIGHT_TRADING and 23:30>NIGHT_TRADING, tradingDt开始是今天的日期，那么+=timedelta(1)之后，日期就会叠加了。

所以判断过午夜日期增加的逻辑里，用：
newTime  < NIGHT_TRADING
就不太合适了，应该改成比如newTime < 1:00之类的？

发现了解决方案：
造成这个原因，是因为 self.tradingDt 使用了全局变量，导致每一个合约都会让这个会是 +1
修正方案：增加变量初始化：
self.tradingDt = datetime.now()
整体代码如下：
大商所日期转换
    if tick.exchange is EXCHANGE_DCE:
        newTime = datetime.strptime(tick.time, '%H:%M:%S.%f').time()    # 最新tick时间戳

        # 如果新tick的时间小于夜盘分隔，且上一个tick的时间大于夜盘分隔，则意味着越过了12点
        if (self.tickTime and
            newTime < NIGHT_TRADING and
            self.tickTime > NIGHT_TRADING):
            self.tradingDt = datetime.now()
            self.tradingDt += timedelta(1)                          # 日期加1
            self.tradingDate = self.tradingDt.strftime('%Y%m%d')    # 生成新的日期字符串

            print u'日期 +1 : ', self.tradingDate, tick.vtSymbol

        tick.date = self.tradingDate    # 使用本地维护的日期

        self.tickTime = newTime         # 更新上一个tick时间

shellMount的解决方案还是有问题吧

self.tradingDt 使用全局变量，逻辑是大商所跨越午夜12点时调整日期吧，不直接用self.tradingDt = datetime.now()局部变量应该是考虑到TICK时间和本地时间可能有出入，造成日期时间错位吧。这一前提是每天早盘手动开启录制程序而不是24小时运行。那是很多年以前，现在大商所都23：30之前结束，不再跨夜了，那这个逻辑就不必存在了。
2你直接取当前日期那为什么还要加1呢，那不是明显还是超前1天了？
.self.tradingDt = datetime.now()
self.tradingDt += timedelta(1)
=========
我想知道的是，，现在大商所都23：30之前结束，是不是这一段直接取消就可以了，大商所没有必要再单独处理？
如果怕大商所抽风再延长夜盘交易时间，要继续保存这一判断，那就要考虑全合约和连续24小时录制的情况：一是newTime还要小于日盘交易时间比如8：00，二是增加一个标记变量，不管多少合约只增加一次
不知是否正确，最好尽快更新

@jerrycgc
1, 我的处理方式：
now = datetime.now()
    # 大商所日期转换
    if tick.exchange is EXCHANGE_DCE:
        newTime = datetime.strptime(tick.time, '%H:%M:%S.%f').time()    # 最新tick时间戳

        # 如果新tick的时间小于夜盘分隔，且上一个tick的时间大于夜盘分隔，则意味着越过了12点
        if (self.tickTime and
            newTime < NIGHT_TRADING and
            self.tickTime > NIGHT_TRADING):
            self.tradingDt = now
            self.tradingDate = self.tradingDt.strftime('%Y%m%d')    # 生成新的日期字符串

        tick.date = self.tradingDate    # 使用本地维护的日期

        self.tickTime = newTime         # 更新上一个tick时间

    # 避免脏数据
    if not tick.date:
        return

    dt = datetime.strptime("%s %s" % (tick.date, tick.time), '%Y%m%d %H:%M:%S.%f')
    if abs((dt - now).total_seconds()) > 200 :
        return

    self.gateway.onTick(tick)

2，大商所是否23:30就结束了，这一点我不清楚，受知识所限，我平常并未了解很多的合约。
3，一是newTime还要小于日盘交易时间比如8：00。这个描述是一个误区，这个值尽可能小应该。比如为8点的情况，不能防止8点前出现人工重启的情况。

@ShellMount
我直接注释掉了这一段。查了一下资料，主要是大商所ACTIONDAY取的是交易日的日期即夜盘取第二天（周五取下周一），郑商所在TRADINGDAY跟其它交易所又有区别。以下代码运行良好，不知道你说的人工重启会有什么情况。tick.date可能为空吗？：
if tick.exchange is EXCHANGE_DCE:
newTime = datetime.strptime(tick.time, '%H:%M:%S.%f').time()    # 最新tick时间戳
        """
        # 如果新tick的时间小于夜盘分隔，且上一个tick的时间大于夜盘分隔，则意味着越过了12点
        if (self.tickTime and
            newTime < NIGHT_TRADING and
            self.tickTime > NIGHT_TRADING):
            self.tradingDt += timedelta(1)                          # 日期加1
            self.tradingDate = self.tradingDt.strftime('%Y%m%d')    # 生成新的日期字符串
        """

        #夜盘时间用本地日期
        if newTime > NIGHT_TRADING:
            tick.date = datetime.now().strftime('%Y%m%d')    # 使用本地维护的日期

        self.tickTime = newTime         # 更新上一个tick时间

@jerrycgc
如果不注释， 假设夜盘分界线 NIGHT_TRADING 设置为早上8:00
需要一个前提：如果大商所，早上交易到2:30
此时，在1:30分的时候，人为重启程序（或挂掉了，重新打开），
那么，这时候，日期仍然会增加1。
解决这个CASE的情况，是将 NIGHT_TRADING 设置得更小  如早上0点5分。

已修复

authors: KobeZhao ShellMount jerrycgc vnpy


text:
新版本取消了tcp了吗？

vnt-cli 启动时提示不支持tcp参数
Error Unrecognized option: 'tcp'

翻了commit变更记录，参数变到另一个上面了，  文档没更新

请问现在想用tcp协议的话，应该用什么参数？我用--tcp也是不行，谢谢

tcp协议移到-s中了，使用 -s tcp://服务器地址

authors: 1WuNeiGui muziling vnt-dev

repo: vnt-dev/vnt


text:
appdef: IFields interface enhacement

Tasks

Reduce IFields. Should be members only:

Field(FieldName) IField
FieldCount() int
Fields() iter.Seq2[int, IField]

All other members should be moved to procedures:

RefField(FieldName) IRefField
RefFieldCount() int
RefFields() iter.Seq2[int, IRefField]
UserFieldCount() int
UserFields() iter.Seq2[int, IField]

⛔ Rejected
Reason: Slower validation speed.
Validation of every row iterate it reference fields.
This iterator should be implemented inside IFields implementation to use short slice of reference fields. It can not to be generally implemented with iteration by all fields.

repo: voedger/voedger


text:
Mobile Browser can't collapsed control

When I selected layer, the control could not collapsed.
(Android 5.1.1, Chrome)

Hi @bestpika! Unfortunately I can't promise that I will be able to fix this soon. Have a lot on my plate now =( I think it's a good chance to contribute ;-)

may be delete this.
,_collapse: function (e) {     if (e.target === this._container) {       L.Control.Layers.prototype._collapse.apply(this, arguments)     }   }

authors: bestpika vogdb

repo: vogdb/SelectLayersControl


text:
Unable to import default validations and messageMap

I have not been able to import the default field validations and messageMap following the demo example.  I'm trying to do this from a typescript based React application.  Can you give an example that imports directly from the component using this rather than via the src/index.js file?

You can able to import the default field validations messages by using:
import { messageMap } from 'react-material-ui-form/dist/validation/index';
rest everything is same.
const customFormMsg = Object.assign(messageMap, {
isEmail: 'Please enter a valid email address',
isLength:'Must be 2-50 characters',
})
<MaterialUIForm onSubmit={this.submit} validation={{ messageMap: customFormMsg}}>

authors: brianhilst voletiswaroop

repo: voletiswaroop/react-material-ui-form


text:
Problems to install on IOJS

[23:06:07] henricavalcante@machine:~/git/henricavalcante/node-aiopv2/node_modules/johnny-five (master)
$ npm install serialport
|
> serialport@1.7.4 install /Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport
> node-pre-gyp install --fallback-to-build

  CXX(target) Release/obj.target/serialport/src/serialport.o
In file included from ../src/serialport.cpp:3:
In file included from ../src/serialport.h:5:
../node_modules/nan/nan.h:261:25: error: redefinition of '_NanEnsureLocal'
NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Local<T> val) {
                        ^
../node_modules/nan/nan.h:256:25: note: previous definition is here
NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Handle<T> val) {
                        ^
../node_modules/nan/nan.h:661:13: error: no member named 'smalloc' in namespace 'node'
    , node::smalloc::FreeCallback callback
      ~~~~~~^
../node_modules/nan/nan.h:672:12: error: no matching function for call to 'New'
    return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
           ^~~~~~~~~~~~~~~~~
/Users/henricavalcante/.node-gyp/3.2.0/include/node/node_buffer.h:31:40: note: candidate function not viable: no known conversion from 'uint32_t' (aka 'unsigned int') to
      'enum encoding' for 3rd argument
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
/Users/henricavalcante/.node-gyp/3.2.0/include/node/node_buffer.h:43:40: note: candidate function not viable: 2nd argument ('const char *') would lose const qualifier
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
/Users/henricavalcante/.node-gyp/3.2.0/include/node/node_buffer.h:28:40: note: candidate function not viable: requires 2 arguments, but 3 were provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, size_t length);
                                       ^
/Users/henricavalcante/.node-gyp/3.2.0/include/node/node_buffer.h:36:40: note: candidate function not viable: requires 5 arguments, but 3 were provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
In file included from ../src/serialport.cpp:3:
In file included from ../src/serialport.h:5:
../node_modules/nan/nan.h:676:12: error: no viable conversion from 'v8::MaybeLocal<v8::Object>' to 'v8::Local<v8::Object>'
    return node::Buffer::New(v8::Isolate::GetCurrent(), size);
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:210:7: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from
      'v8::MaybeLocal<v8::Object>' to 'const v8::Local<v8::Object> &' for 1st argument
class Local {
      ^
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:210:7: note: candidate constructor (the implicit move constructor) not viable: no known conversion from
      'v8::MaybeLocal<v8::Object>' to 'v8::Local<v8::Object> &&' for 1st argument
class Local {
      ^
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:214:13: note: candidate template ignored: could not match 'Local' against 'MaybeLocal'
  V8_INLINE Local(Local<S> that)
            ^
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:327:13: note: candidate template ignored: could not match 'S *' against 'v8::MaybeLocal<v8::Object>'
  V8_INLINE Local(S* that)
            ^
In file included from ../src/serialport.cpp:3:
In file included from ../src/serialport.h:5:
../node_modules/nan/nan.h:683:26: error: no member named 'Use' in namespace 'node::Buffer'
    return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
           ~~~~~~~~~~~~~~^
In file included from ../src/serialport.cpp:3:
In file included from ../src/serialport.h:5:
In file included from ../node_modules/nan/nan.h:24:
In file included from /Users/henricavalcante/.node-gyp/3.2.0/include/node/node.h:42:
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:221:5: error: assigning to 'v8::Primitive *volatile' from incompatible type 'v8::Value *'
    TYPE_CHECK(T, S);
    ^~~~~~~~~~~~~~~~
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
    *(static_cast<T* volatile*>(0)) = static_cast<S*>(0);      \
                                    ^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:414:12: note: in instantiation of function template specialization 'v8::Local<v8::Primitive>::Local<v8::Value>' requested here
    return NanEscapeScope(NanNew(v8::Undefined(v8::Isolate::GetCurrent())));
           ^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                             ^
In file included from ../src/serialport.cpp:3:
In file included from ../src/serialport.h:5:
In file included from ../node_modules/nan/nan.h:24:
In file included from /Users/henricavalcante/.node-gyp/3.2.0/include/node/node.h:42:
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:221:5: error: assigning to 'v8::Boolean *volatile' from incompatible type 'v8::Value *'
    TYPE_CHECK(T, S);
    ^~~~~~~~~~~~~~~~
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
    *(static_cast<T* volatile*>(0)) = static_cast<S*>(0);      \
                                    ^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:424:12: note: in instantiation of function template specialization 'v8::Local<v8::Boolean>::Local<v8::Value>' requested here
    return NanEscapeScope(NanNew(v8::True(v8::Isolate::GetCurrent())));
           ^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                             ^
In file included from ../src/serialport.cpp:3:
In file included from ../src/serialport.h:5:
In file included from ../node_modules/nan/nan.h:24:
In file included from /Users/henricavalcante/.node-gyp/3.2.0/include/node/node.h:42:
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:221:5: error: assigning to 'v8::Function *volatile' from incompatible type 'v8::Value *'
    TYPE_CHECK(T, S);
    ^~~~~~~~~~~~~~~~
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
    *(static_cast<T* volatile*>(0)) = static_cast<S*>(0);      \
                                    ^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:1514:12: note: in instantiation of function template specialization 'v8::Local<v8::Function>::Local<v8::Value>' requested here
    return NanEscapeScope(NanNew(handle)->Get(kCallbackIndex)
           ^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                             ^
In file included from ../src/serialport.cpp:3:
In file included from ../src/serialport.h:5:
In file included from ../node_modules/nan/nan.h:24:
In file included from /Users/henricavalcante/.node-gyp/3.2.0/include/node/node.h:42:
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:221:5: error: assigning to 'v8::Object *volatile' from incompatible type 'v8::Value *'
    TYPE_CHECK(T, S);
    ^~~~~~~~~~~~~~~~
/Users/henricavalcante/.node-gyp/3.2.0/include/node/v8.h:180:37: note: expanded from macro 'TYPE_CHECK'
    *(static_cast<T* volatile*>(0)) = static_cast<S*>(0);      \
                                    ^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:1632:12: note: in instantiation of function template specialization 'v8::Local<v8::Object>::Local<v8::Value>' requested here
    return NanEscapeScope(handle->Get(NanNew(key)).As<v8::Object>());
           ^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                             ^
9 errors generated.
make: *** [Release/obj.target/serialport/src/serialport.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "/usr/local/bin/iojs" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport/build/serialport/v1.7.4/Release/node-v45-darwin-x64/serialport.node" "--module_name=serialport" "--module_path=/Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport/build/serialport/v1.7.4/Release/node-v45-darwin-x64"
gyp ERR! cwd /Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport
gyp ERR! node -v v3.2.0
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/iojs /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport/build/serialport/v1.7.4/Release/node-v45-darwin-x64/serialport.node --module_name=serialport --module_path=/Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport/build/serialport/v1.7.4/Release/node-v45-darwin-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:764:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
node-pre-gyp ERR! System Darwin 14.5.0
node-pre-gyp ERR! command "/usr/local/bin/iojs" "/Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport
node-pre-gyp ERR! node -v v3.2.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.7
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/iojs /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport/build/serialport/v1.7.4/Release/node-v45-darwin-x64/serialport.node --module_name=serialport --module_path=/Users/henricavalcante/git/henricavalcante/node-aiopv2/node_modules/johnny-five/node_modules/serialport/build/serialport/v1.7.4/Release/node-v45-darwin-x64' (1)
npm WARN optional dep failed, continuing serialport@1.7.4

node-serialport is still depending on NAN v1 which is not compatible with latest io.js or upcoming node.js v4 releases.
Current node-serialport supports io.js up to v2.5
Few people already did NAN v2 patching in PRs #566 and #571

With the release of node.js 4.0.0 (the merger with iojs), resolving this has become an urgent matter.

Closing for #578

authors: henricavalcante imyller jacobrosenthal rwaldron

repo: voodootikigod/node-serialport