text:
file does not match the corresponding path on disk - File does not exist

I'm reporting a bug.

What is the current behavior?
When I change files (recompiled in a linked package), webpack chokes with
Error in ./src/index.js
Module not found: [CaseSensitivePathsPlugin] `some file.js` does not match the corresponding path on disk - File does not exist.

 @ ./src/index.js 29:16-36

What is the expected behavior?
I'd expect webpack to just happily restart.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
I'm using webpack 1.13.2 and server 1.16.1.
I filed this issue with the app I'm working on at https://github.com/vega/vega-editor/issues/129.

It is may not be a webpack issue, did you try restarting webpack-dev-server? if yes is it woking after that?

Yes, it works after restarting but webpack chokes again once files change
again.
On Fri, Jun 16, 2017, 11:32 Ram Yadlapalli notifications@github.com wrote:

It is may not be a webpack issue, did you try restarting
webpack-dev-server? if yes is it woking after that?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/5073#issuecomment-309101273,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAj86rAVIhSC7-h9pw0WosNi8pEvxphgks5sEsongaJpZM4N8BQF
.

So it could be an issue with webpack-dev-server.

is there a fix for this issue that domoritz is referring to?

File an issue for the CaseSensitivePathsPlugin.

I am having the same issue with React. I created an app using create-react-app, and am not using webpack to compile. I have tried renaming the React node package, deleting it, reinstalling it, and the same error continues. Therefore, maybe it isn't a webpack issue? Using node v8.9.1, React v16.2.0

Problem related to CaseSensitivePathsPlugin. Close in favor https://github.com/Urthen/case-sensitive-paths-webpack-plugin/issues/22

check the pass of remote and your local system be same if you have capital S in Src path change it to small.
Error in ./src/index.js

./src/Pages/PlayQuiz.js
Module not found: C:\Users\abc\project\client\src\Components\Comments.js does not match the corresponding path on disk components.
@Farbod29  I got the same error on my project when I run.
anyone help or suggest something what shall I do?

File an issue for the CaseSensitivePathsPlugin.

I just renamed the folder and it worked. Thanks :)

The issue for me was I accidentally capitalized the package name after from in the import statement.

If you're using create-react-app and Visual Studio Code and you're seeing this bug after changing the casing on a filename, this timeless solution worked for me...

Restart your dev server (eg. ctrl + C ... yarn start)

Restart Visual Studio Code

Tried all the solutions on this thread and nothing works. Only thing I can think of is npm vs yarn as someone already mentioned. : (

./src/Card.js
Cannot find file: 'index.js' does not match the corresponding name on disk: '.\node_modules\React\react'.
can someone help with this

Hallo,
any hints how I can solve this issue with localhost? I cannot open my react app
thanks
Failed to compile
./src/index.js
Cannot find file: 'index.js' does not match the corresponding name on disk: './node_modules/React/react'.

@irenapopova in your webpack config file are you using externals? I had the same issue and noticed I had:
externals: {
    react: 'React',
    'react-dom': 'ReactDOM',
  },

because my target library is commonjs2 I needed to change it to the following:
externals: {
    react: 'react',
    'react-dom': 'react-dom',
  },

if your using multiple targets you should refer to Webpack Externals

some one should help me with this
./src/App.js
Cannot find file: 'search.js' does not match the corresponding name on disk: '.\src\Components\components'.

I had the same issue. It was because I used small case in folder name in my import statement. When in fact it should have been upper case.
Replaced "import Layout from './component/MainLayout'; to
"import Layout from './Component/MainLayout'; worked for me.

Thanks alot
On Fri, Aug 23, 2019, 5:31 PM vasireddybharath notifications@github.com
wrote:

I had the same issue. It was because I used small case in folder name in
my import statement. When in fact it should have been upper case.
Replaced "import Layout from './component/MainLayout'; to
"import Layout from './Component/MainLayout'; worked for me.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/webpack/webpack/issues/5073?email_source=notifications&email_token=AKOAXXQ7G43FNW63TYZTAKLQGAGE5A5CNFSM4DPQCQC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5AWKOI#issuecomment-524379449,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKOAXXWJCMX5TVVLFJ23FBDQGAGE5ANCNFSM4DPQCQCQ
.

I had the same issue. It was because I used small case in folder name in my import statement. When in fact it should have been upper case.
Replaced "import Layout from './component/MainLayout'; to
"import Layout from './Component/MainLayout'; worked for me.

This worked for me. Thanks

npm install --save-dev case-sensitive-paths-webpack-plugin
It should do the trick

This worked for me. Thanks.

https://stackoverflow.com/questions/55149843/error-cannot-find-file-index-js-does-not-match-the-corresponding-name-on-dis fixed the problem with my build.  Basically it's:
import React from "react" and not
import React from "React"

Problem related to CaseSensitivePathsPlugin. Close in favor Urthen/case-sensitive-paths-webpack-plugin#22

This worked for me as well, I pulled a project which was not mine and the folder was in a different case 'capitalized' and the code was using 'smallcase', renaming the folder fixed it to me, thanks

I was having this issue too once I unlinked and then re-relinked all the npm packages involved I stopped getting the error.

So the issue is because you are not importing correctly. Like in my case it was :
import {Dropdown} from '**react-Bootstrap**'
I corrected it to
import {Dropdown} from '**react-bootstrap**'
Since import statement are case sensitive

For me the problem was that I was importing by mistake something like
import { MyComponent } from "../components/MyComponent/MyComponent";
but in the component I was just exporting the class as default ( export default MyComponent )
So I had to switch to
import MyComponent from "../components/MyComponent/MyComponent";
Is pretty dumb, I know, but maybe this can help other too

I had similar problem but changing the file name work for me.

What worked for me as to Restart npm start and there move the file missing out of the folder and back, then it compiled fine.

myComponent.ts:
const MyComponent = {...}
If importing from "index.ts", make sure u export with lower case.
index.ts:
export * from "/myComponent";

This mostly an issue with CaseSensitivePathsPlugin. Be sure your file name is capital case instead of small case.
if you import MyComponent from "../components/MyComponent" be sure your file name is MyComponent in not myComponent

all your review are worthless to me 😪

I just transferred my code to a new laptop and now I'm getting this error.  The code ran fine on the other laptop.  If I change the case of one file name, I just get an error with another file.
I now get the error with files in the node_modules folder.

On Windows this can be due to a name conflict, namely two files in the same directory having the same name but in a different case.

This mostly an issue with CaseSensitivePathsPlugin. Be sure your file name is capital case instead of small case. if you import MyComponent from "../components/MyComponent" be sure your file name is MyComponent in not myComponent or vice versa

Really helpful, Thank you...

Quand j'essaye d'executer ça m'afficher ""Module not found: Error: Cannot find file: 'Cart.css' does not match the corresponding name on disk: '.\src\styles\Styles'."

i had the same issue because instead of Login.css i was calling login.cs

If anybody is still having this error 2023 like me:
the folder was corrupt causing an error, so delete it and make a new one to fix the issue.

authors: Adhithyashine Berci-Ionut Blac-Panda Charles-Chiakwa EmmaREKS Farbod29 FlorianCassayre Guste NikulGoyani369 Oyatullo RamYadlapalli ajhool danfoust dbslone devlopernabin domoritz evilebottnawi frunox irenapopova jcrommar kahlilashanti kameshk61 kyle-west llezhava medhatdawoud oseisaac raydot rovertnet sangar3 sarianpour shanytc sokra subhash00 tomtom92 vasireddybharath

repo: webpack/webpack


text:
An ability to interrupt running compile process

Is there a way to interrupt current compilation when new changes are coming? So it wouldn't wait for it to end before starts a new compilation process?
Do you want to request a feature or report a bug?
Feature

What is the current behavior?
It starts building new changes only after the current build is finished
If the current behavior is a bug, please provide the steps to reproduce.
Not a bug, I believe.

What is the expected behavior?
It interrupts the current build if present, and starts a new one
If this is a feature request, what is motivation or use case for changing the behavior?
If your bundle is really big, it usually takes a lot of time to compile. Adding an ability to interrupt the current compilation process if there's new changes to build will significantly increase the speed.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
webpack@2, macos@10.11.6, node@^6

It's difficult to interrupt the process without corrupting the cache or leaving async task hanging around...

@sokra thanks! while googling around and asking everyone about that, i got the gist that i'm doing something really wrong :)
so i just created a vendor chunk to separate it from my code, x5 speed increase.
Thanks!

source: gharchive/issue

authors: ilyadoroshin sokra

license: MIT

license_type: permissive

license_source: github-api


text:
Dynamic async import not working

Bug report

What is the current behavior?
When you look at the minimal reproduction link you can see the Icon.vue. There I built my dynamic component, where the dynamic svgs get loaded.
The svgs can only be loaded with a svg-loader. You can see my implementation in the vue.config.js.
The build runs without errors and creates a .js file for every chunk - perfect.
When I try to import the model in another vue project and use the component, the following error appears and the icon will not be loaded.
It parses the file right but it can't be found.
If the current behavior is a bug, please provide the steps to reproduce.

clone repo above
put some svgs into assets/fa/light
build the project using yarn build
creating a link using yarn link
create a new vue project (e.g. vue create <projectname>)
link the project using yarn link 'v-icon'
import the component using import icon from 'v-icon'
in the templates section write <icon name="trash"></icon> while 'trash' is one of the icon names you added before
serve the app using yarn serve
watch the error appearing

Failed to resolve async component: function(){return n("2eab")("./".concat(i,".svg"))}
Reason: Error: Loading chunk 11 failed.
(missing: http://localhost:8080/v-icon.umd.min.11.js)

Repository:
https://gitlab.com/patcher56/v-icon/tree/master
What is the expected behavior?
It should load the requested icon dynamically

Other relevant information:
webpack version:  4.15.1
Node.js version: 10.9
Operating System: macOS
Additional tools: vuejs @vue/cli

I already tried to push the issue in the vue repository
vuejs/vue#8678

Yes. I put some icon into the assets/fa/light folder and built the package.
After that it creates the v-icon.umd.min.js and for every icon a v-icon.umd.min..js file
It also creates a demo.html. If I view this demo.html, everything works.
It only doesn't work when importing the package in an existing project.
To your question: I don't believe that the v-icon.umd.min.11.js exists in the root directory. The v-icon-package is an imported package. Therefore I believe, the files do not exist somewhere in the root directory..

Seems like your publicPath configuration is incorrect.

Have the same issue with React application.

Any ideas?

authors: Patcher56 igordymbovskyi sokra


text:
Terminal progress on multiple lines if line wraps

Bug report

What is the current behavior?
When the terminal is small enough so that the line of progress would wrap, it will create a new line instead of overwriting the current line of progress.
This works fine if the terminal is wide enough to fit the entire line on a single row without wrapping.
If the current behavior is a bug, please provide the steps to reproduce.
I'm getting this issue with angular cli:

create a new angular project npm install -g @angular/cli and ng new test
make the terminal small enough so that text wraps to a new line
run ng serve to get a progress output
observe that the progress is output on multiple lines

make the terminal large enough so that text does NOT wrap to a new line
run ng serve to get a progress output
observe that the progress did not output on multiple lines but overwrote the current line of progress

What is the expected behavior?
Progress reported should always overwrite the current line instead of creating a new line if the line would wrap multiple lines.

Other relevant information:
webpack version:  4.3 I believe is what Angular uses.
Node.js version: 12.3.1 (also occurs on v11)
Operating System: Windows 10, build: 17763.259
Additional tools: angular cli
I can reproduce this in VS Code and Powershell directly.
I have reported this on VS Code, https://github.com/microsoft/vscode/issues/74695 they say the issue is not them, I have tried with conpty on and off.
I also reported it on angular cli: https://github.com/angular/angular-cli/issues/14623 they also say the issue is not them.

Please create minimum reproducible test repo, looks something wrong in your environment

@evilebottnawi,
This issue occurs on my repo here https://github.com/quick-foot/vision.
It's almost a bare bones Angular 8 app.
My VS Code settings:
{
    "editor.fontSize": 12,
    "editor.lineHeight": 23,
    "editor.detectIndentation": true,
    "editor.minimap.enabled": false,
    "editor.roundedSelection": false,
    "html.autoClosingTags": false,
    "terminal.integrated.fontSize": 13,
    "terminal.integrated.cursorStyle": "line",
    "workbench.startupEditor": "none",
    "workbench.statusBar.feedback.visible": false,
    "workbench.panel.defaultLocation": "right",
    "debug.toolBarLocation": "docked",
    "explorer.openEditors.visible": 0,
    "telemetry.enableTelemetry": false,
    "telemetry.enableCrashReporter": false,
    "highlight-matching-tag.highlightSelfClosing": true,
    "git.confirmSync": false,
    "gitlens.blame.heatmap.enabled": false,
    "gitlens.codeLens.enabled": false,
    "window.titleBarStyle": "custom",
    "editor.accessibilitySupport": "off",
    "typescript.updateImportsOnFileMove.enabled": "never",
    "javascript.updateImportsOnFileMove.enabled": "never",
    "npm-intellisense.packageSubfoldersIntellisense": true,
    "npm.enableScriptExplorer": true,
    "highlight-matching-tag.styles": {
        "opening": {
            "full": {
                "custom": {
                    "backgroundColor": "rgba(220, 220, 220, 0.15)"
                }
            },
            "left": {
                "custom": {
                    "borderWidth": "0px"
                }
            },
            "right": {
                "custom": {
                    "borderWidth": "0px"
                }
            }
        }
    },
    "git.autofetch": true,
    "eslint.validate": [
        "javascript",
        {
            "language": "typescript",
            "autoFix": true
        }
    ],
    "terminal.integrated.shell.windows": "C:\\\\Windows\\\\System32\\\\WindowsPowerShell\\\\v1.0\\\\powershell.exe",
    "terminal.external.windowsExec": "C:\\\\Windows\\\\System32\\\\WindowsPowerShell\\\\v1.0\\\\powershell.exe",
    "vsicons.presets.foldersAllDefaultIcon": true,
    "workbench.iconTheme": "vscode-icons",
    "vsicons.projectDetection.disableDetect": true,
    "terminal.integrated.windowsAllowConptyTasks": true
}

Workspace settings:
{
    "search.exclude": {
        "**/node_modules": true,
        "**/build": true,
        "**/coverage/**/*": true
    },
    "[yaml]": {
        "editor.tabSize": 4
    },
    "files.insertFinalNewline": true,
    "files.trimTrailingWhitespace": true,
    "editor.formatOnSave": true,
    "editor.tabSize": 4,
    "editor.detectIndentation": false,
    "editor.codeActionsOnSave": {
        "source.fixAll.tslint": true
    },
    "editor.defaultFormatter": "esbenp.prettier-vscode",
    "html.format.wrapAttributes": "force-aligned",
    "html.format.wrapLineLength": 100,
    "html.format.endWithNewline": true,
    "tslint.alwaysShowRuleFailuresAsWarnings": false,
    "prettier.singleQuote": true,
    "prettier.tabWidth": 4,
    "prettier.printWidth": 100,
    "prettier.proseWrap": "always",
    "prettier.htmlWhitespaceSensitivity": "ignore",
    "prettier.disableLanguages": ["html", "angular"],
    "prettier.tslintIntegration": true,
    "typescript.tsdk": "node_modules\\typescript\\lib"
}

Send a PR

I've got a PR open to trim progress text to stderr.columns if it exists, which should fix the problem

authors: Bkucera ChristopherKiss evilebottnawi sokra


text:
fix: add /#PURE/ to generated JSON.parse() call in JsonGenerator

When importing JSON files in webpack, in non trivial cases, the JSON payloads will be accidentally included in the final bundle even when it's actually not used. To help the dead code elimination, this PR just adds /*#__PURE__*/ to JSON.parse(..), which is definitely "pure" and when the return value is unused it should be dropped by, say, Terser.
This is the reproduction repo of the issue: https://github.com/naruaway-sandbox/webpack-json-import-tree-shake-demo and it also explains more details. I confirmed that this PR fixes the issue.
Summary

🤖 Generated by Copilot at 2053d2d
Add a comment to mark JSON.parse as pure in JsonGenerator.js. This helps webpack to tree-shake unused JSON modules.
Details

🤖 Generated by Copilot at 2053d2d

Add /*#__PURE__*/ comment before JSON.parse calls to mark them as side-effect-free (link,                            F0

@naruaway

source: gharchive/pull-request

authors: alexander-akait naruaway


text:
Fix typo in hot plugins: "Propably" => "Probably"

Also added periods to the disabled messages, since the rest of the messages have them.

Thanks

authors: mendenhallmagic sokra


text:
Buttons lack a visually distinct focus state

There’s no apparent focus state on any of the buttons in the application.

Just fetched version 1.1.2 beta and there’s still no focus state on any buttons? There’s still definitely a hover state, but keyboard navigation remains impossible.

Hi @ticky, ah yes thanks for following up with it.. we're going to take another pass at this. You're trying to tab through the menu buttons, right?

Tabbing through the menu buttons and the main “open” button in the home screen, yes!

The buttons now have a tab focus in 1.6.1

authors: ikreymer m4rk3r ticky

repo: webrecorder/webrecorder-player


text:
Closing mdns agent

I use the library with many open/close, and I get mdns storms where the webrtc library searches for other nodes over the network in a very aggressive manner.
This has been proposed by @r-byondlabs, and might very well be the problem: if I open/close many connections, and the mdns-agents are not cleaned up, there might be many requests.
Fixes #616

Cargo fmt warning

Here you go. With my version of cargo-fmt, it also changes the formatting of two other files. Let me know if that's OK.
I tested it on my setup, and the mdns-storms seem to be effectively gone, which is great!
I also added devbox and a pre-commit hook here: #637 . I'm a recent devbox-convert and really think it improves the contributor experience a lot.

authors: ineiti rainliu

repo: webrtc-rs/webrtc


text:
mvn install fail

I'm running commands below:
cd ~/KITE/KITE-AppRTC-Test
c all

It fails with:
[INFO] Scanning for projects...
Downloading from central: https://repo.maven.apache.org/maven2/org/webrtc/kite/kite-base/2.0.7/kite-base-2.0.7.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'version' contains an expression but should be a constant. @ line 14, column 12
[FATAL] Non-resolvable parent POM for org.webrtc.kite:kite-framework:${kite.framework.version}: Could not find artifact org.webrtc.kite:kite-base:pom:2.0.7 in central (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 6, column 11
[WARNING] 'version' contains an expression but should be a constant. @ line 14, column 12
[FATAL] Non-resolvable parent POM for org.webrtc.kite:kite-engine:${kite.version}: Failure to find org.webrtc.kite:kite-base:pom:2.0.7 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 6, column 11
[FATAL] Non-resolvable parent POM for org.webrtc.kite:example-test:0.0.1: Failure to find org.webrtc.kite:kite-base:pom:2.0.7 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 8, column 11
[WARNING] 'version' contains an expression but should be a constant. @ line 16, column 12
[FATAL] Non-resolvable parent POM for org.webrtc.kite:apprtc-test:${kite.apprtc.version}: Failure to find org.webrtc.kite:kite-base:pom:2.0.7 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 8, column 11
[FATAL] Non-resolvable parent POM for org.webrtc.kite:wpt-test:0.2.2: Failure to find org.webrtc.kite:kite-base:pom:2.0.7 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 37, column 11
 @
[ERROR] The build could not read 5 projects -> [Help 1]
[ERROR]
[ERROR]   The project org.webrtc.kite:kite-framework:${kite.framework.version} (/root/KITE/KITE-Framework/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.webrtc.kite:kite-framework:${kite.framework.version}: Could not find artifact org.webrtc.kite:kite-base:pom:2.0.7 in central (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 6, column 11 -> [Help 2]
[ERROR]
[ERROR]   The project org.webrtc.kite:kite-engine:${kite.version} (/root/KITE/KITE-Engine/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.webrtc.kite:kite-engine:${kite.version}: Failure to find org.webrtc.kite:kite-base:pom:2.0.7 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 6, column 11 -> [Help 2]
[ERROR]
[ERROR]   The project org.webrtc.kite:example-test:0.0.1 (/root/KITE/KITE-Example-Test/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.webrtc.kite:example-test:0.0.1: Failure to find org.webrtc.kite:kite-base:pom:2.0.7 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 8, column 11 -> [Help 2]
[ERROR]
[ERROR]   The project org.webrtc.kite:apprtc-test:${kite.apprtc.version} (/root/KITE/KITE-AppRTC-Test/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.webrtc.kite:apprtc-test:${kite.apprtc.version}: Failure to find org.webrtc.kite:kite-base:pom:2.0.7 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 8, column 11 -> [Help 2]
[ERROR]
[ERROR]   The project org.webrtc.kite:wpt-test:0.2.2 (/root/KITE/KITE-WPT-Test/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.webrtc.kite:wpt-test:0.2.2: Failure to find org.webrtc.kite:kite-base:pom:2.0.7 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 37, column 11 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

And I can't find org.webrtc.kite:kite-base artifact on maven central.

Hi,
Thanks for your report. This is due to a mismatch of the version in the pom file. We will push a commit to fix it asap.
You can try changing the version in KITE/pom.xml to 2.0.7 to compile it in the mean time:

It works, thanks!

authors: Piasy namvuCosmo

repo: webrtc/KITE

license_source: bigquery


text:
🛑 The Good Cyclist is down

In 9817004, The Good Cyclist (https://thegoodcyclist.iwview.com) was down:

HTTP code: 521
Response time: 132 ms

Resolved: The Good Cyclist is back up in b889bdc after 419 days, 7 hours, 9 minutes.

repo: webworldview/uptime


text:
🛑 DragonBoat Times is down

In 76a3d97, DragonBoat Times (https://www.dragonboattimes.com) was down:

HTTP code: 521
Response time: 139 ms

Resolved: DragonBoat Times is back up in 8dded26 after 8 minutes.


text:
fix: Fix the problem of null judgment error

Description
In the current null and nnull judgments, undefined will be erroneously judged to be true.
Adjusted the judgment logic, the judgment rules of null and nnull return true or false according to whether the value is nil.
And complements the logic of recursive judgment.

CI failed

@self-transition fixed

IsNil adds an extra check for undefined, so do you need to add a unit test for it?
I'm also wondering if the previous _.get call returns undefined if a non-existent key is passed in. and if that's what's expected in this case.

IsNil adds an extra check for undefined, so do you need to add a unit test for it?
I'm also wondering if the previous _.get call returns undefined if a non-existent key is passed in. and if that's what's expected in this case.

I have adjusted the judgment logic based on your response.
Checks if path is a direct property of object before judge conditions, and added the relevant unit tests.
PTAL

authors: huangjunjia self-transition


text:
feat: added wechaty plugin

Wechaty.use
[ ] Bug Fix
[x] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Checklist

[ ] Commit Messages follow the Conventional Commits pattern

A feature commit message is prefixed "feat:"
A bugfix commit message is prefixed "fix:"

[ ] Tests for the changes have been added

Description
https://github.com/wechaty/wechaty/issues/1939
We can discuss it here.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

As the discussion here: https://github.com/wechaty/wechaty/issues/1939
I made few changes of the demo code. Just want to make sure you are agree with it.
So I can continue on the rest
1. I would like to call it Plugin instead of MiddleWare
In my opinion, middleware is alway dealing with the input/output.  Middleware A deal with it, and then decide to handover to Middleware B. But we are not doing that. We just installed it, and then it do works for you. It's more like a Plugin.
I think a MiddleWare is something like this:
Wechaty.use({ message: function (message: string, next: (message: string) => void) {
  if (message.indexOf('hi') > -1) {
     next();
  }
})

So that's the reason I change the name to Plugin. and implement it like this.
2. I would prefer to use a abstract class as a Plugin instead of a plugin function.
// 1. Plugin function
const MyPlugin = function (options: any) {
  return function(this: Wechaty) {
    this.on('join-room', () => console.log('joined'));
  }
}
Wechaty.use(MyPlugin({a: 1}));

// 2. Plugin Class
Class MyPlugin {
  constructor(options) { this.options = options }
  install(bot: Wechaty) {
    bot.on('join-room', () => console.log('joined'));
  }
}
Wechaty.use(new MyPlugin({a: 1}));

Basically it does the same thing. but more readable, and easier to understand.
3. I would prefer the use function in Class instead of Instance.
Which is:
Wechaty.use(new MyPlugin());

but I made it both support the Class and the instance. also support the Array
Wechaty.use(new CommonPlugin());

const bot = new Wechaty();
bot.use([ new MyOwnPlugin(), new MyAnotherPlugin() ]);

Hi @Gcaufy ,
Thank you for the design of our powerful Middleware/Plugin system for Wechaty!
I have read your questions and also the source code in the PR, I believe we are in the right way to archive our goal.
Here's my reply for your 3 questions:

Call it Plugin instead of MiddleWare

I have no preference between those two names because I feel they are all fit our design.
I agree with you that the middleware mostly they are chaining for doing something together, but in our system, it does not. But the name of "Middleware" sounds more fashionable.
And the name of "Plugin" is more classic, simple, and clean, so they are all good.
Please feel free to make your decision about selecting the name, and I'll support your final choice!

Plugin Interface: an abstract class, or a plugin function?

My opinion for the Interface is not to use a Class because it looks too heavy.
I'd like to purpose the following design, to archive the same goals:
export type WechatyPlugin = (...options: any[]) => (wechaty: Wechaty) => void

const kickPlugin: WechatyPlugin = (managedRoomTopic: string) => wechaty => {
  wechaty.on('message', message => {
    ...
  })
}

wechaty.use(kickPlugin('My Room Topic'))

As my personal feeling, the above Functional design will be shorter and clearer than the Class design from yours.
So I'd like to purpose that our Plugin interface would be better to be defined as a Functional Interface.

to define use() as a Class static method instead of the Instance method

Could you please explain it with more examples about why you want to design like that?
I feel it will be more clear and simple if we only provide a use() method for the Wechaty instance so that every instance is separated by default.

I'll also add some comments to the PR code, and please feel free to let me know what you think.
Thank you for your design and questions again, and I hope you have a great weekend!

Here are the conclusions, just want to make sure I'm not missing anything.

Use the name 'Plugin' (keep it)
Use both Wehcaty.use and wechaty.use (keep it)
Remove the installed plugins property. (need changes)
Change plugin to Functional style. (need changes)

btw. I probably need to work this in this weekend.

Everything looks good, thank you very much @Gcaufy !
I have one concern about the this for our Plugin function, I have left my comment as suggesting to use an explicit wechaty arg instead of the this, the reason is as the following:

In my experience in the past years, there are lots of developers who do not understand what this is in the JS function.
They will be very confused about the this and want to know how to use it, like the following screenshot, which was posted in the past week in our developers' home WeChat room:

I personally like to use this, and this is the current design of the event listener callback functions in Wechaty.
However, according to what the above screenshot shows out, I'd like to suggest that we use a wechaty arg to archive that, to make it easier to understand for all developers.

Everything looks good, thank you very much @Gcaufy !
I have one concern about the this for our Plugin function, I have left my comment as suggesting to use an explicit wechaty arg instead of the this, the reason is as the following:
In my experience in the past years, there are lots of developers who do not understand what this is in the JS function.

I don't like this either. One of the reason to use Class style is to avoid using this.

kindly ping @Gcaufy
I believe that after we change the this to (wechaty: Wechaty) and a few variable names, this PR is ready for merge.
I cannot be waiting to use this great new feature!

Changes:

Renamed:  globalPlugins -> globalPluginList
Fix this in pluign
Test case updated. use extends Wechaty
A bug fix: when use extends, Wechaty.globalPluginList is wrong.

Thanks to this great Plugin system, it will greatly improve the Wechaty ecosystem by letting everyone writing a powerful plugin to archive their needs with ease!
This feature will be available from Wechaty version 0.39.19

authors: Gcaufy huan

repo: wechaty/wechaty


text:
ARCT-154 DONT MERGE. Use the current protocol when making the evercookie request.

Remove flash/shockwave method of storing cookie (its generating errors
on chrome).

DONT MERGE. This modification will be tested and deployed with the 9.7 patch.

I'm not sure if we should remove the flash, can you verify it always has issues and what is causing it? I'm not able to get the issue currently

@chancedowns I added back the path helpers and removed the reference to the JS routes object.
Added back the flash cookie.

authors: chancedowns csigg

repo: weddingwire/evercookie

license: mit


text:
js文件无法打包内部模块

在.js文件里require核心模块，比如
var mtop = require('@weex-module/mtop');

打包后，输出错误

在单独的.js文件里，目前没法直接require一个核心模块，需要用一些比较hack的方法，如下：
var modal
__weex_define__('@weex-component/toast', [], function(__weex_require__) {
    modal = __weex_require__('@weex-module/modal')
})

module.exports = function(msg) {
    modal.toast({message: msg})
}

authors: terrykingcha young-cowboy

repo: weexteam/weex-loader


text:
Doesn't work for me

Hi,
I have a fork https://github.com/Toryalai1/Arcade-IremM92_MiSTer and did everything according to your instructions but it doesn' work. Did I miss anything? I did the check and it showed me successfully the pull.yml

It seems to have worked. Please be patient as each repo is scheduled to run about twice a day.

repo: wei/pull


text:
This application's bundle identifier does not match its code signing identifier

Summary
Getting "This application's bundle identifier does not match its code signing identifier
" error while running the application. Installed the framework using carthage.
Steps to Reproduce
Install framework using Carthage and build the application

How did you add the framework?
What ZIPFoundation/Carhage/Xcode versions are you using?
Did you manually drag ZIPFoundation.framework to the "Embedded Binaries" section of your main app's target settings?
Maybe this helps: https://stackoverflow.com/a/34652134/100848
Another thing you could try is to integrate the framework via cartage update --no-build and manually add the ZIPFoundation.xcodeproj to your workspace.

authors: weichsel yaalisri

repo: weichsel/ZIPFoundation


text:
能否使用较小公共数据集作为您readme中的数据准备部分

您自述文件中给出的 ScanNet v2 数据集需要 1.2T 存储空间，您可以发布一个使用较小的数据集作为数据准备部分的自述文件吗，如S3DIS数据集，谢谢谢谢，祝您生活愉快！

你不需要下载完整的ScanNetV2，只需要下载我readme中的几种类型文件(可以在脚本文件中指定下载类型)，大约9个G

你不需要下载完整的ScanNetV2，只需要下载我readme中的几种类型文件（可以在文件中下载类型），大约9个G

谢谢谢谢！

authors: OkLetsGoi weiguangzhao

repo: weiguangzhao/PBNet


text:
Input from simulations

Hi Daniel,
I'm trying to use MAGIC on simulated data from msprime, but I'm not sure how I should input the data. Is the easiest way to directly write out an MSMC-style SNP file and a bed mask that includes the whole simulated region? Or should I output a VCF and go from there?
Thanks!
Arun

Hi Arun,
I see that I forgot to document this part. The ms2msmc.py script converts
ms-style output to MSMC input format. Then you can either make a fake
coverage file (just a whole bunch of lines of "80", or whatever your
minimum window size is) and use windower.py, or use this attached script
window_msN.py instead. window_msN.py is just if you want the distribution
of pairwise distances in your simulated sample, so you'd have to tweak it
if you're looking at a different tree property.
I hope that helps. I'm traveling right now, but I can get back to you with
more specifics when I get a chance if it would be helpful.
Best,
Daniel
On Tue, May 22, 2018 at 9:43 PM, Arun Durvasula notifications@github.com
wrote:

Hi Daniel,
I'm trying to use MAGIC on simulated data from msprime, but I'm not sure
how I should input the data. Is the easiest way to directly write out an
MSMC-style SNP file and a bed mask that includes the whole simulated
region? Or should I output a VCF and go from there?
Thanks!
Arun
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/weissmanlab/magic/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIdKQFos4D-hDxFtxN0vVu3D08C6XBVhks5t1FxjgaJpZM4UJMRa
.

Thanks Daniel! I ended up writing a little function to do this in python since I'm using msprime to simulate sequence data. I have some questions about the output as well, but I will open another issue to keep things organized.

Hello Daniel and Arun,
I came across this thread also looking for a way to run MAGIC on ms-simulated data, because the documentation on this is indeed lacking. Where can I find this window_msN.py script that generates the coverage files?
Thanks a lot,
Armando.

Hi Armando,
I just uploaded it to the repository. I still need to document everything though.
Best,
Daniel

Thanks Daniel, that is very helpful.

authors: arredondos arundurvasula weissman

repo: weissmanlab/magic


text:
Swagger documentation doesn't list our full range of licenses

Look at https://api.wellcomecollection.org/catalogue/v2/swagger.json
{
  "name": "locations.license",
  "in": "query",
  "description": "Filter the images by license.",
  "schema": {
    "type": "string",
    "enum": [
      "cc-by",
      "cc-by-nc",
      "cc-by-nc-nd",
      "cc-0",
      "pdm",
      "copyright-not-cleared"
    ]
  }
},

and
{
  "name": "items.locations.license",
  "in": "query",
  "description": "Filter the work by license.",
  "schema": {
    "type": "string",
    "enum": [
      "cc-by",
      "cc-by-nc",
      "cc-by-nc-nd",
      "cc-0",
      "pdm",
      "copyright-not-cleared"
    ]
  }
},

It misses e.g. ogl and pdm

This got fixed in https://github.com/wellcomecollection/catalogue-pipeline/pull/1584

repo: wellcomecollection/platform


text:
docs: Add some notes on the relater architecture

Is there anything important we think I’ve forgotten?
Resolves #1630.

This is a masterpiece! Nice.

authors: alexwlchan kenoir

repo: wellcometrust/platform


text:
Simplify ZipFileDownloadFlow

What is this PR trying to achieve?
Make the ZipFileDownloadFlow simpler to understand, by removing some Akka stream constructs.
Who is this change for?
@kenoir who wants to fix an issue with zip downloads in this object.

Replaced by https://github.com/wellcometrust/platform/pull/3186


text:
To reproduce the on-device (Android, int8) RTF decrease in wenet paper

Hello Guys!
Now, I want to reproduce the wenet paper's RTF benchmark data for on-device (Android, int8).

RTF benchmark is on Table 3 in paper https://arxiv.org/pdf/2102.01547.pdf

The problem is,

with the wenet/bin/export_jit.py, we can produce a 8-bit quantized model without mobile optimization!

and run it on device with wenet/runtime/android project
Without the mobile optimization, we can only have a RTF increase on Android device running!

To reproduce the RTF of the paper on mobile phone,

I think we need to use the torch.utils.mobile_optimizer when converting the model
and save it with _save_for_lite_interpreter function.
and maybe more?

How can I overcome this situation?
Can I have some codes or scripts for on-device quantized and mobile_optimized model build?
And to have the RTF, we may need corresponding runtime/core c++ code for decoding the model on-device!
Please help us to enjoy the wenet in this real world~
If you could give me any advice, it would be very appreciated!
Thanks a lot^^

Thanks for your detailed questions,

aishell1's model?

Currently, we are testing with a LibriSpeech model.

model config: conf/train_conformer_bidecoder_large.yaml

4 cores Qualcomm Snapdragon 865 with 8G memory?

device: Samsung Gallaxy S9 (SM-960N) 64GB

release mode?

arm64-v8a

offline decoding with decoder_main in adb shell?

Yes, I run the 'decoder_main' program with adb shell.

Currently, I managed to build the 'decoder_main' program for my Android device.
And the program testing is working good for my quantized version of the model.
But, to improve the RTF performance, I need to optimize the model for the device!
It's difficult for me to devise a "PyTorch mobile" optimization code for the wenet model!
(I'm studying on this topic - https://pytorch.org/mobile/home/ )
And I think that "wenet repository would be better to have a baseline code for the PyTorch mobile optimization".
Thanks a lot!

From my study on the "PyTorch Quantization" (https://pytorch.org/docs/stable/quantization.html),
With my conformer model,

I realized that **dynamic quantization"" can increase the execution RTF and latency.

Now I will try to use a static quantization, and check whether the model runtime RTF is reduced!
Thanks all~

..


text:
check input.size() > 0 before comparison

when input.size() is 0, CHECK_EQ(input.size(), time_stamp.size()); causes crash.
before comparison, make sure input.size() is not empty

You mean CHECK_EQ(0, 0) crash?

You mean CHECK_EQ(0, 0) crash?

No, I noticed input.size will be 0 and time_stamp.size will be a non-zero positive number and cause crash

Could help to figure out why the time_stamp is not zero?

Sure. I could debug further but this stopped the crash. I will see if I can pinpoint why the values are not equal

closing this, as problem seems to be resolved in latest code

Is there a conclusion to this question?
@robin1001 @eschmidbauer

Is there a conclusion to this question? I also got this crash @robin1001 @eschmidbauer

i have not been able to reproduce it in the latest code but i suspect it was related to sending "bad" data to the decoder.

Thanks for your reply.

Is there a conclusion to this question? I also got this crash @robin1001 @eschmidbauer

i have not been able to reproduce it in the latest code but i suspect it was related to sending "bad" data to the decoder.

Thanks for your reply.

@robin1001 I got this error even in the latest version of wenet. But the input data is just recording from Android device, I didn't save them and can't reproduce the error, I think it's should be caused by abnormal data.
So before comparison, I also make sure input.size() is not empty as  @eschmidbauer did.

same problem:
asr_decoder.cc:143] Check failed: input.size() == time_stamp.size() (0 vs. 9)

same problem in latest code: asr_decoder.cc:143] Check failed: input.size() == time_stamp.size() (0 vs. 9)

Have you figured it out?

same problem in latest code: asr_decoder.cc:143] Check failed: input.size() == time_stamp.size() (0 vs. 9)

Have you figured it out?

I'm working on it.

When the endpint is triggered, the next chunk we don't have enough feature  for model->forward ，
and then we have hyp vector which has empty vector , and times.size() == 0, const std::vector& time_stamp = times[0] is a undefined behavior

authors: Mddct eschmidbauer murphypei robin1001


text:
25-b-stochastic-raytracing 完成一切调试

你们检查一下，如果没问题就接受pr吧
覆盖率的图在readme里面

emm来来回回改了几次

这次是最终版了.

测试覆盖率不到百分百，如 Vector3 里面的def dot(self,target) ，还有很多，你自己可以 加上 --cov-report=html生成HTML文件查看具体的哪里没测

authors: chiellini tofar


text:
Unpickling Error: invalid load key, '\xdc'.

While using train.lmdb and valid.lmdb from the shapenet_car folder in the mentioned Google Drive link, the line 'dataflow.LMDBSerializer.load(lmdb_path, shuffle=False)' throws 'Unpickling Error: invalid load key, '\xdc'. I also tried downloading the lmdb files multiple times to check if the lmdb is not corrupted.
<ipython-input-1-8968eb1dd6e2>` in lmdb_dataflow(lmdb_path, batch_size, input_size, output_size, is_training, test_speed)

     69
     70 def lmdb_dataflow(lmdb_path, batch_size, input_size, output_size, is_training, test_speed=False):
---> 71     df = dataflow.LMDBSerializer.load(lmdb_path, shuffle=False)
     72     size = df.size()
     73     if is_training:

~/py3.7/lib/python3.7/site-packages/tensorpack/dataflow/serialize.py in load(path, shuffle)
    112             and run deserialization as a mapper in parallel.
    113         """
--> 114         df = LMDBData(path, shuffle=shuffle)
    115         return MapData(df, LMDBSerializer._deserialize_lmdb)
    116

~/py3.7/lib/python3.7/site-packages/tensorpack/dataflow/format.py in __init__(self, lmdb_path, shuffle, keys)
     88         self._open_lmdb()
     89         self._size = self._txn.stat()['entries']
---> 90         self._set_keys(keys)
     91         logger.info("Found {} entries in {}".format(self._size, self._lmdb_path))
     92

~/py3.7/lib/python3.7/site-packages/tensorpack/dataflow/format.py in _set_keys(self, keys)
    108         self.keys = self._txn.get(b'__keys__')
    109         if self.keys is not None:
--> 110             self.keys = loads(self.keys)
    111             self._size -= 1     # delete this item
    112

~/py3.7/lib/python3.7/site-packages/tensorpack/utils/serialize.py in loads(buf)
     91             bytes
     92         """
---> 93         return pickle.loads(buf)
     94
     95

UnpicklingError: invalid load key, '\xdc'.

This was due to the version of tensorpack. It should be 0.8.9 (as mentioned in the requirements.txt), else the LMDBSerializer.load throws this error.

repo: wentaoyuan/pcn


text:
Support ingestion to default partition

fix #221

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: wepay/kafka-connect-bigquery


text:
Add .рус (.xn--p1acf) parser: whois server whois.nic.рус (whois.nic.рус)

Domain Name: xxx.xn--p1acf
Unicode Name: ???.???
Domain ID: xxx
WHOIS Server: whois.nic.xn--p1acf
Updated Date: 2017-07-01T21:02:01.453Z
Creation Date: 2016-08-01T20:02:01.335Z
Registry Expiry Date: 2018-08-01T20:02:01.524Z
Domain Status: ok https://icann.org/epp#ok
Registrar: xxx
Registrar IANA ID: xxx
Registrar Abuse Phone: xxx
Registrar Abuse Email: xxx
Registrar URL: xxx
Registrant ID: xxx
Registrant Name: xxx
Registrant Organization: xxx
Registrant Street: xxx
Registrant City: xxx
Registrant State/Province: xxx
Registrant Postal Code: xxx
Registrant Country: XX
Registrant Phone: xxx
Registrant Email: xxx
Admin ID: xxx
Admin Name: xxx
Admin Organization: xxx
Admin Street: xxx
Admin City: xxx
Admin State/Province: xxx
Admin Postal Code: xxx
Admin Country: XX
Admin Phone: xxx
Admin Email: xxx
Billing ID: xxx
Billing Name: xxx
Billing Organization: xxx
Billing Street: xxx
Billing City: xxx
Billing State/Province: xxx
Billing Postal Code: xxx
Billing Country: XX
Billing Phone: xxx
Billing Email: xxx
Tech ID: xxx
Tech Name: xxx
Tech Organization: xxx
Tech Street: xxx
Tech City: xxx
Tech State/Province: xxx
Tech Postal Code: xxx
Tech Country: XX
Tech Phone: xxx
Tech Email: xxx
Name Server: xxx
Name Server: xxx
DNSSEC: unsigned
>>> Last update of WHOIS database: 2018-05-27T22:07:09.790Z <<<

TERMS OF USE: You are not authorized to access or query our WHOIS database through the use of electronic processes that are high-volume and automated.  THis WHOIS database is provided by as a service to the internet community.

The data is for information purposes only. We do not guarantee its accuracy. By submitting a WHOIS query, you agree to abide by the following terms of use: You agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes that apply to CoCCA it's members (or CoCCA or member computer systems). The compilation, repackaging, dissemination or other use of this Data is expressly prohibited.

Feel free to provide a PR.

authors: Vanav weppos

repo: weppos/whois-parser


text:
chore: release 1.2.113

:robot: I have created a release *beep* *boop*
1.2.113 (2022-06-08)
Bug Fixes

helm: unable to recognize "": no matches for kind "..." in version "..." errors when base64 kubeconfig used (90678ec)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v1.2.113 :sunflower:

repo: werf/werf


text:
codemirror-textlintパッケージ化

Depの数を考えてブランチはfeat/7189-add-japanese-rulesから生やしました

動作確認済み

本体側から間違ったRuleを渡した場合のLoggerも正常に動きました

production 向けに足りないものがいくつかあります

build script の追加
packages/app/docker/Dockerfile の修正

authors: stevenfukase yuki-takei

repo: weseek/growi


text:
Update sbt-bloop to 1.5.16

About this PR
📦 Updates ch.epfl.scala:sbt-bloop from 1.4.8-19-4d9f966b to 1.5.16
📜 GitHub Release Notes
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 = "ch.epfl.scala", artifactId = "sbt-bloop" } ]

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

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

Superseded by #124.

repo: weso/document


text:
🛑 Gifts from Devon is down

In 699ecc1, Gifts from Devon (https://www.giftsfromdevon.co.uk) was down:

HTTP code: 525
Response time: 11481 ms

Resolved: Gifts from Devon is back up in 3a7713a.


text:
你好，有社区或者交流群吗

你好，有社区或者交流群吗？使用addax插件时遇到一些问题，mysql的读没有问题，可是oracle和execl都一直报错： Code:[Framework-03], Description:[Addax 引擎配置错误，该问题通常是由于Addax 安装错误引起，请联系您的运维解决 .].。我从4.0.2试到4.0.5都不行。
Originally posted by @llyxd in https://github.com/wgzhao/Addax/issues/360#issuecomment-940709463

目前没有创建其他社区或者交流群

github本身就是社区，可以通过创建 issue 或者在 disussions 上讨论相关问题
交流群往往变成了广告群，其技术交流的质量并不高，而且不容易沉底内容以及外部搜索。

您遇到报错，可以把运行的完整日志贴出来（不要截图）

现在没有其他社区或者交流群

github讨论就是社区，可以通过创建问题或者在讨论上相关问题
交流群往往外部了广告群，其技术交流的质量并不高，也不容易沉底内容以及搜索。

你遇到了报错，可以把运行的完整日志贴出来（不要截图）

好的好的。谢谢！我把日志贴在评论区了。

excelreader里面的path路径的指定规则是什么。我看文档上没细说，不知道 是不是路径问题。我把excel文件放在了tmp目录下，工具包也是在tmp目录下。
{
"job": {
"setting": {
"speed": {
"channel": 1,
"bytes": -1
}
},
"content": [
{
"reader": {
"name": "excelreader",
"parameter": {
"path": ["/tmp/"],--这里尝试过/tmp       /tmp/excelreader.json
"header": true,
"skipRows": 0
}
},
"writer": {
"parameter": {
"print": true
},
"name": "streamwriter"
}
}
]
}
}

authors: llyxd wgzhao

repo: wgzhao/Addax


text:
Separate system services in directories

Instead of listing all Services in the docker-compose.yml, each services as his own docker-compose.yml file.
Services can be enabled and disabled, individually.
Allows to add new Services in the DDE-System.

good idea, thanks! please improve the update guide before we can merge this!

@rugbymauri can be merged!

Nice work @rugbymauri !
Only thing that's missing for me, is functionality to define default services that should be started on a project basis.
If you e.g need to use  memcached, redis, postgres and mailhog for a project, you would have to run 6 commands before the system and application are up and running.
Maybe a global user-configuration would be sufficient, to at least start the most used services :thinking: .
@tuxes3 what's your opinion?

What about introducing a ddefile which when present lists all needed services? While executing up dde checks for these services. This prerequisites that all services are defined in the system directory.
Most project will use the current default. Therefore if the ddefile is not implemented the 6 commands will only be executed once. Even if we implement the ddefile we will all need to execute this 6 commands. As you also first need to update each project.

It's fundamentally a sound idea to structure services in such a way that the DDE system starts only those needed, rather than launching everything simultaneously. However, splitting them into multiple Docker-Compose files, each containing just one service, seems overly complex. A more effective approach would be to use Docker Compose's "Profile" feature (refer to Docker Compose Profiles). This feature allows assigning specific profiles to individual services, and only selected profiles are started. Consequently, a docker-compose up without specifying a service doesn't automatically start all containers. Additionally, I suggest creating a .dde.yml file in the respective project directories, which contains information about the required services. When executing dde up, this file would be read, and the relevant services would be initiated. This approach would also simplify documentation, as it eliminates the need to list individually which DDE services need to be started for optimal project development. In Pull Request #64, I've started implementing such a .dde.yml file.

i refactored the PR. now, instead of creating/removing a file in the services/conf.d directory the services enabled are stored in the data/dde.yml file
enjoy

repo: whatwedo/dde


text:
Specify loading metadata

In the old spec this was useful as a way to share information about a module between loader hooks (SystemJS for example had a load.metadata object).  You can maintain your own hashtable for this but this is inherently less shareable.  It was also nice just for the simplicity of every hook having the same signature (except normalize).
Was this intentionally removed for a particular reason or was it just not thought to be needed?

@matthewp as far as I'm aware, a private metadata object will still be part of the spec as a final argument to the hooks, it just hasn't been written in yet.

That's good, I still think load is a nicer signature than N arguments depending on the hook.

@guybedford In #24 you suggested that it'd be nice for the resolve hook to get passed the metadata, and for the metadata to be passed in to the resolve method but I'm not sure I understand how client code could actually make use of this, given that only one metadata object can win, and that can only be determined after resolution completes. What are the uses of a preallocated-but-possibly-discarded metadata object being passed in to resolve?

@dherman consider that the majority of understanding about a module occurs in resolve - as part of performing normalizations lots of metadata / state gets put together in the process, that is basically what we want to be available to the subsequent hooks. The metadata is discarded and useless if it wasn't the first to resolve to the given name, but the metadata that remains stops us from having to maintain a custom metadata cache or reprocess on fetch.

Agree with @guybedford here, metadata is important for normalization.  Plugin detection happens at this step, for example.

@matthewp I talked with @guybedford on IM about this. I think I understand what you want: the ability to take information you gleaned from the name (and may have stripped out of the normalized name) and save it for later in the loading process. But passing in an object that may be the wrong object is not a good mechanism for achieving this. I will try to come up with something that avoids unnecessarily allocating objects and handing misleading objects to the resolve hook.

That might be a sign that resolve is doing too much. Maybe we should split it up into 2 separate hooks.... I think I have good names for them already. :-)

If you don't need the unresolved name, then why aren't you just doing this work in the locate hook?

There is no locate hook.

LOL -- I meant the fetch hook :)

IOW, there are two different possible issues here. One is that you might just want to conceptually tease out two different steps, with no real increase in power -- and that would suggest bringing back the locate hook.
But the other is that you're actually wanting to save metadata based on information that you erase from the non-normalized name -- and for that, a locate hook wouldn't help you, because it only receives the normalized name. This use case is a bit fishy, since different non-normalized names might resolve to the same normalized name but have conflicting metadata from the erased parts, but I can see it happening in practice
For example, you could have a plugin mechanism where "es6!foo" and "es7!foo" both resolve to "/foo.js" but they are requesting conflicting plugins. Now, the plugin system could choose to enforce consistency by treating that as an error. (IMO this is a flaw in the AMD plugin system -- you should configure that stuff in one place, rather than having to repeat yourself everywhere and try not to have conflicts.) So while this isn't to my taste, I can imagine it happening.
Is that the kind of power you're wanting? Am I wrong that the locate hook wouldn't actually help you?

I think maybe you're thinking about functions within a hook as competing with each other when in reality they form a chain where each does it's own little small part and then calls the parent, and so on.  Yes, at any point within the chain a function could exit out.  But that is the exception, in my experience.

I think you're missing something important. It's only a linear chain after resolve. The resolve hook is a "fan-in" to a chain.
"./foo.js"  "foo"  "../../../foo.js"
     \        |        /
      \       |       /
   resolve resolve resolve
        \     |     /
         \    |    /
          \   |   /
           \  |  /
            \ | /
             \|/
              |
            fetch
              |
          translate
              |
         instantiate
              |

I'm talking within the same hook. Consider:
Reflect.loader.import("es7!./foo");

The addJs extension adds a .js to the name.
The plugin extension will split on !, load the es7 module (which itself will go through resolve and become /.es7.js).
The plugin will receive ./foo.js and do its own thing. Maybe all es7 implementations are under a /es7 folder so it resolves to /es7/foo.js.

These 3 steps are not competing with each other. There is no "winner".
I agree that if there were a locate hook there would be no need for metadata within normalize. The plugin extension would add its metadata in the front of the locate step.

I think we're talking past each other...

I'm talking within the same hook. ... These 3 steps are not competing with each other. There is no "winner".

Hm, but that's not what I was talking about. The "winner" I'm referring to is where you have three different calls to resolve, one for "es7!foo", one for "es7!../foo.js", and one for "es7!../../../foo.js", each of which resolves to the same thing: "/es7/foo.js". For each call to resolve, a distinct metadata object is passed in. But only one of those metadata objects actually ends up being the metadata object that gets propagated to the rest of the chain. The others are setting properties on an object that disappears into the ether.

I agree that if there were a locate hook there would be no need for metadata within normalize. The plugin extension would add its metadata in the front of the locate step.

That's the opposite of what I was saying: the locate step does not add any interesting power here. If you would do this work in the locate step, why not just do it in the fetch step?

But only one of those metadata objects actually ends up being the metadata object that gets propagated to the rest of the chain. The others are setting properties on an object that disappears into the ether.

Yes, we agree here, this is not desirable, which is why normalize never had a load object I imagine.

That's the opposite of what I was saying: the locate step does not add any interesting power here. If you would do this work in the locate step, why not just do it in the fetch step?

Because by the time we've gotten to fetch we've lost the interesting bits about the module :)  It's no longer a name with contextual meaning. It's too late to try and add these back to a newly provided metadata object unless you maintain your own separate hash table inside resolve.
So yes, I understand where our thinking diverged now, and I'll answer your appropriate question:

But the other is that you're actually wanting to save metadata based on information that you erase from the non-normalized name -- and for that, a locate hook wouldn't help you, because it only receives the normalized name.

The parts that are erased aren't the parts you want to save metadata about. In the case of plugins that will still be part of the normalized name. Typically normalize functions will add to the name but not remove parts (relative paths are the only exception I can think of).

Sorry I'm still confused... :( On the one hand you're saying there's no loss of information when normalizing, but on the other hand you're saying that you've lost information required for contextualization. Also, where you say "we agree here" it sounds like you're agreeing you don't want the metadata object passed in to resolve, and yet I thought you're arguing it should be?
Maybe if you could give me a more concrete example of what specific kinds of data you want to store I'll understand better?

So, under the old spec there were 2 hooks, normalize and locate. Normalize produced a fully normalized name.  The new spec only has resolve which produces a url.  I'm saying that under the old spec there was no loss of information because of module names. We don't have module names now.
With normalize/locate you could do something like:
import jquery from "jquery";

This normalizes like:
jquery -> jquery@2.2.2#dist/jquery

The fully normalized name is jquery@2.2.2#dist/jquery
Notice there is no erasing of information as you were worried about before.  The locate step will do:
jquery@2.2.2#dist/jquery -> http://localhost/my/app/node_modules/jquery/dist/jquery.js

With resolve it will just be:
jquery -> http://localhost/my/app/node_modules/jquery/dist/jquery.js

To keep each piece of the information that happened after normalization I need to maintain my own hash table because it is gone by the time we get to fetch.
Now, you might say that resolve can include this information
http://localhost/my/app/node_modules/jquery/dist/jquery.js&jquery@2.2.2#jquery/dist

And then fetch can split this information off... but I don't think this is a good solution to the problem.

Note there are also use cases where it can be useful to provide metadata directly into the import function as well:
System.import('file.js', { moduleFormat: 'CommonJS' });

The alternative to the above is declarative configuration entirely, which also works, but without a canonical form to allow declarative configuration this becomes harder.

Update
[[Metadata]] is an internal slot on ModuleStatus objects (registry entries), but as today, there is no way to set them, and no way to inspect them, we could easily add that if we figure this is important.
The two camps are:
1 - in user-land, you can have a map to store meta information about the modules you own.
2 - if the metadata can be used cross hooks (when doing AOP), it is hard to pass it around. Also inspection, and other goodies that will analyze the dep graph can access some metadata as well.
If we decide to support metadata definition in user-land, we will have to define how set/get it.

Now, the metadata support becomes mandatory to support whatwg's script type="module" tag.
Quoted from #148

Looking through whatwg module spec and I think that the module-script assumes per-module-script-tree information. For example, nonce is propagated through the module script tree fetching.
However, in the current loader spec, it seems that BrowserLoader's @@fetch hook just takes the entry and the key. So the above information seems discarded through the pipeline.

And the metadata must be propagated throught the pipeline. So (2) is necessary since the metadata is used cross hooks.

The easiest way is, just passing the metadata throughout the pipeline along with entry.

this is going to be very tricky because we don't know what to share.

For whatwg <script type="module">,  it seems that,

a settings object (It should be aded to fetch request)
a destination (Currently, this is always "script")
a cryptographic nonce (It should be added to fetch request)
a parser state ( (It should be aded to fetch request)
a credentials mode (It should be aded to fetch request)
a module map settings object
an ancestor list
a referrer (Currently, this is always "client")
a top-level module fetch flag

need to be shared in the module-script-tree.
https://html.spec.whatwg.org/multipage/webappapis.html#fetch-a-module-script-tree

a destination (Currently, this is always "script")

Sometimes it is "worker" or "sharedworker"

a referrer (Currently, this is always "client")

For non-top-level fetches it is the referring module script's base URL

In general I would caution against paying too much attention to the model in whatwg/loader. It is still speculative and per #147 may undergo significant changes. The model in HTML is the one that is ready for implementations.

Sometimes it is "worker" or "sharedworker"

For non-top-level fetches it is the referring module script's base URL

Oops! Super nice, thanks!

In general I would caution against paying too much attention to the model in whatwg/loader. It is still speculative and per #147 may undergo significant changes. The model in HTML is the one that is ready for implementations.

Yeah, so we need to design the simplified loader spec that cares about this issue (per-module-script-tree-scope-metadata).
Without this, the new simplified loader spec cannot enjoy the script type="module" ...

authors: Constellation caridy dherman domenic guybedford matthewp

repo: whatwg/loader


text:
Gotham BoldGreen color indistinguishable from background [mintty]

This color causes visualization to be impossible:
BoldGreen        = 8,   31,  45

Notice that there are entries between xzcmp and xzegrep

Hey @fmv1992, this has been discussed in https://github.com/whatyouhide/gotham-contrib/issues/10#issuecomment-157022098. I would really appreciate some help on this as I don't have much time to invest into it :)

Closing this for inactivity.

repo: whatyouhide/gotham-contrib


text:
Usage of tooltip formatter : onClick stops working on data refresh

What I am trying to achieve
I need to show/hide tooltip based on some logic. As per highcharts documentation, the correct way is to use a formatter function returning the text or false. For this, I need both: this.point.x provided by highcharts and this.props.data which is passed to the chart instance.
I also have a need to update the chart data on some user action.
** Where I am stuck **
The onClick of Series data stops when I use the formatter function.
I forked the sandbox you had created for issue #70 to reproduce the problem. https://codesandbox.io/s/922kn8wy6r
I cannot bind the "formatter" function to the Chart instance, as I need the this.point.x in the formatter function.
What I have tried so far

Creating the function in render() method of the chart --> this interferes with the onClick behavior of series.
Passing the function as props from the container.
Higher Order function to create this function --> I am pretty sure I am doing it wrong.
Using the Highcharts callback. I can get to the tooltip by: chart.tooltip, but I do not see the "formatter" option anywhere underneath it.

Any advice or hint would be appreciated. Also open to contributing a fix if required, but would need some handholding.

Hi @Dubes, you just need to watch out where you are using arrow functions, as they change the this scope to be the outer scope - in React's case, the component's scope.
By using a normal function, it will keep the this to the original scope that Highcharts sets, allowing you to use this.point.x as expected.
I've updated you code here: https://codesandbox.io/s/k7mr4ovq3

Thanks for the hint about the arrow function. It is the scope where I am stuck, the equality check in the example would eventually come from props, both of which belong in different scopes.
 formatter = function() {
    // the 1 will come from "props.toolTipEnabledFor"
    return this.point.x === 1 ? "Yeah" : false;
  `};

I tried with a higher order function, but it works only in constructor... not when I call it on react lifecycle or passing the function via props.
https://codesandbox.io/s/llzzl17jnz

Well good news and bad news.
Good news, you can use both props, and the Highcharts tooltip formatter scope together, using your makeFormatterFunction, see here: https://codesandbox.io/s/m38pnvvv78
Bad news, seems the events which I dynamically added are removed when a series updates see here, so I'll need to add a fix for that.

Just published version 2.2.0 which include a fix for this bug.
You can see the example is fixed here which is using the same code as the previous CodeSandbox.

That was quick!!! thanks a lot!

authors: Dubes whawker

repo: whawker/react-jsx-highcharts


text:
Update broken credits URL

Update credits URL to point to latest version from Internet Archive, as current URL is returning an error (curl http://theoldschooldevops.com/2008/02/09/bash-ini-parser/ -> 您要找的资源已被删除、已更名或暂时不可用 -> The resource you are looking for has been deleted, renamed, or temporarily unavailable).

Oh dear, it looks like the domain has expired and/or been taken over.
Thanks for the archive link @brandongalbraith!

authors: brandongalbraith whereisaaron

repo: whereisaaron/get-aws-profile-bash


text:
Remove the Patron Dependency.

Patron is not compatible with JRuby, using the default
Faraday adapter (net/http) makes the gem compatible
with MRI and JRuby while keeping the option of using
Patron if you set the adapter manually.

I'm happy to merge in this PR but could you also update the reference to Patron in README.md.

Actually, don't worry about the README I'll do that - I'll put a changelog section in the README.

Thanks!

authors: andyjeffries djpate

repo: whichdigital/active-rest-client


text:
Attempt to get length of null array on NfcManager.start()

Hi,
When I run NfcManager.start(), an error occurs saying "Attempt to get length of null array" and pointing to your NfcManager.java line 70. It indicates that invoke function does not accept null param. FYI, I tested on multiple Android devices, with and without a callback function as NfcManager.start() param.
So, I changed NfcManager.java line 70 callback.invoke param to a string and it works (callback.invoke("null"); instead of callback.invoke(null);). I know that it is not a solution at all, so I just notice you about it because I don't have time to fix it and to send you a pull request.
Regards.

the same issue, did you find solution?

As I said in my previous message, I had to replace :
callback.invoke(null);
by
callback.invoke("null");
here https://github.com/whitedogg13/react-native-nfc-manager/blob/master/android/src/main/java/community/revteltech/nfc/NfcManager.java#L70
This makes it work but it is a temporary solution because we should not edit node_modules packages.

I found solution.
add in android->app->src->AndroidMainfest.xml premission to nfc

<uses-permission android:name="android.permission.NFC" />

Yes, I already did this but this didn't solve the problem for me.

Hi both, sorry for the late response.
I have recognized the issue and pushed a fix. Really thanks for reporting the issue!

Thank you very much ! It works great !

authors: adirzoari haroal whitedogg13


text:
[documentation] create a place to keep track of model performace

Prerequisites
Please answer the following question for yourself before submitting an issue.

[X] I checked to make sure that this issue has not been filed already.

1. The entire URL of the documentation with the issue
https://github.com/tensorflow/models/tree/master/official/...
2. Describe the issue
Need to create a place to track the performance of the models

Some potential areas:

Use the github wiki of this repo
Use teams create a file

I would prefer if we use approach 1 actually.

Seems like we have something on teams already. https://teams.microsoft.com/l/entity/com.microsoft.teamspace.tab.wiki/tab::4178c63b-cdc8-4cf9-b024-9a94a8e90726?context={"subEntityId"%3A"{\"pageId\"%3A79%2C\"origin\"%3A2}"%2C"channelId"%3A"19%3A17fbff01e2fb487e8eafee20fe0c7e44%40thread.skype"}&tenantId=c8f93db5-3fa2-4e75-ace4-73e95a19c107
Lets clean this up and see which one is still and see if it is possible to store the configuration file etc so we can reproduce the results. @CabooseExia  @rehohoho

repo: whizzmobility/models


text:
Delay with the optitrack estimated position

Dear Dr. Whoenig,
We're working with an Optitrack and crazy flies (with your library crazyflie_ros).
While observing the optitrack's pose estimation, through ''rostopic echo /crazyflie8/vrpn_client_node/crazyflie8/pose'', we definitely identify a delay. This delay makes the position loop very unstable.
Any advice on this issue?
Thank you,  Yoni.

How is your optitrack computer connected to the machine that is running crazyflie_ros? I highly recommend using a wired connection and not WiFi.
Additionally, I recommend using NatNet instead of VRPN for (slightly) lower latency. For example, you can use https://github.com/whoenig/motioncapture_ros instead of vrpn_client_ros.

Dear Dr. Whoenig,
Thank you for your prompt answer. I will try it asap.
Another issue that we're having is with the latest version of the crazyflie.
We've just purchased a crazyflie 2.1 and tried to operate it with crazyflie_ros. For some reason, the motors are moving slowly and the drone doesn't take off. Do we need to do a firmware update? To which version?
Thank you,   Yoni.

Any newer official firmware should be fine. Which "operation mode" are you using? I don't recommend using the external position controller in crazyflie_controller (neither for CF2.0 nor CF2.1) - this might need re-tuning for CF2.1. Instead, use one of the on-board position controllers (PID or mellinger).

Ok,  thank you very much.

authors: mandelyoni whoenig


text:
Fix test

#153
发一个 PR 让 travis 跑合并之后的测试，这个分支的测试没出现问题。
没通过的测试记录：

https://travis-ci.org/whtsky/WeRoBot/builds/151252830
https://travis-ci.org/whtsky/WeRoBot/builds/151460836

A new inspection was created.

The inspection completed: No new issues

A new inspection was created.

Current coverage is 73.75% (diff: 100%)

Merging #154 into develop will not change coverage

@@            develop       #154   diff @@
==========================================
  Files            28         28
  Lines           987        987
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            728        728
  Misses          259        259
  Partials          0          0

Powered by Codecov. Last update 11c63ba...5b2990f

The inspection completed: No new issues

A new inspection was created.

The inspection completed: No new issues

repo: whtsky/WeRoBot


text:
系统错误

系统错误，请清理后重试: type:invalid_request_error code:invalid_api_key

是不是 openai 的key 到期了？

才换的key呢

是不是openai的key到了期了？

是的。解决了。感谢师傅。

repo: whyiyhw/chatgpt-wechat


text:
更新4月10日下午镜像后，手动不能添加cookie。

[qinglong] 你好
今天下午更新了最新的镜像，目前手动无法添加cookie。显示NOT FOUND
尝试替换之前备份的cookie.sh  进入面板 没有cookie显示。右上角仍然显示 NOT FOUND。只是面板不显示但其实添加成功。还可以运行脚本任务。

替换了之前的cookie.sh后，cookie其实成功添加的。但是面板不显示

rebuild 下

面板已经从新rebuild过了，全部删除镜像容器，映射目录也全部删除 从新拉去镜像。依旧如此。不知道是哪里的问题。

docker run -dit
-v /opt/docker/qinglong/config:/ql/config
-v /opt/docker/qinglong/log:/ql/log
-v /opt/docker/qinglong/db:/ql/db
-v /opt/docker/qinglong/scripts:/ql/scripts
-p 5777:5700
-e ENABLE_HANGUP=true
-e ENABLE_WEB_PANEL=true
--name qinglong
--hostname qinglong
--restart always
--network bridge
whyour/qinglong:latest

解决了 ，我从新清除了一下chrome的cookie。

清理完浏览器的cookie，一切正常了

还有个解决办法就是，删除cookie。sh的文件，然后重启面板，可以暂时解决，当然ck要重新添加，所以建议备份，这样方便下次一次性添加全部ck，但是问题还是会存在的，不能根治，所以，大佬看看是什么原因导致的

清理完浏览器的cookie，一切正常了

应该是你刷新页面就行了，rebuild完要刷新页面

还有个解决办法就是，删除cookie。sh的文件，然后重启面板，可以暂时解决，当然ck要重新添加，所以建议备份，这样方便下次一次性添加全部ck，但是问题还是会存在的，不能根治，所以，大佬看看是什么原因导致的

ck现在是数据库存储，和cookie.sh 没关系，要映射db目录，你看看频道的指南

还有个解决办法就是，删除cookie。sh的文件，然后重启面板，可以暂时解决，当然ck要重新添加，所以建议备份，这样方便下次一次性添加全部ck，但是问题还是会存在的，不能根治，所以，大佬看看是什么原因导致的

ck现在是数据库存储，和cookie.sh 没关系，要映射db目录，你看看频道的指南

我是路由器docker，直接看日志，启动容器没问题，但是找不到或获取不到ck。sh文件，不存在文件权限的问题，就是因为获取不到ck，sh文件，导致面板启动不来，解决办法就是路由器ssh登录删除ck。sh文件，不用重建，然后重启容器就行了，

authors: cno888888 reviveymj whyour

repo: whyour/qinglong


text:
Wolfgangkarall anchors bugfix

Adapt the test suite to make better use of the anchoring idea from Wolfgang

@wolfgangkarall I wanted to change the test setup for some tme already, but never got around to it. This was a good reason :)
Any comments to merge this in favor of #94?

repo: whyscream/postfix-grok-patterns


text:
🛑 Übersicht 🇬🇧 (en) is down

In 3e21ef9, Übersicht 🇬🇧 (en) (https://holiday-lescala.com/en/homes/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Übersicht 🇬🇧 (en) is back up in 81680f5 after 7 minutes.

repo: whytspace/upptime-holiday-lescala


text:
Logic:

I know it might sound stupid, but, how do i run it on Windows 10?
I have WSL and other extras in order to run these types of thing but i can't find the exe
Any type of help will be appreciated

You can run the editor in the browser by visiting https://ciphereditor.com/. The Electron desktop app version is not ready, yet. But it will arrive in the future. Is this what you were looking for?

I'll close this issue for now. If you still need help, please comment below.

authors: ffraenz karazal

repo: wierkstudio/ciphereditor


text:
Doesn't work on Firefox 50.1.0

Stickyfill doesn't work on Firefox 50.1.0. :(
Works on Chrome 55.0.2883.87m, Opera 42.0.2393.137, Edge 38.14393.0.0.

Stickyfill doesn't do anything in Firefox because Firefox supports position: sticky natively. If some sticky block doesn't work in a browser that supports it natively it's a sign you did something wrong (or a bug in a browser which I doubt).

Firefox doesn't support sticky table cells, see: Firefox bug.
The Readme says "~works with table cells~ disabled until Firefox makes a native implementation", which sort of confuses me. If Firefox doesn't support sticky table cells yet, isn't that why we'd use a polyfill?

@jguffey there’s no way to detect if sticky table cells are supported in a particular browser (as far as I know). So for now the polyfill sticks with the lowest denominator, which is FF implementation.

authors: OzgurGorgulu jguffey wilddeer

repo: wilddeer/stickyfill


text:
[18.x][WFCORE-5530] Add encryption support to FilesystemSecurityRealm

https://issues.redhat.com/browse/WFCORE-5530
Upstream: https://github.com/wildfly/wildfly-core/pull/4983

Core - Full Integration Build 11091 outcome was FAILURE using a merge of 7191cd9bbe9dd8009dd8de68da754e3920ccf8ab
Summary: Compilation error: Compiler (new) Build time: 00:02:36

@ashpan @fjuma This now has a merge conflict.

Core - Full Integration Build 11099 outcome was FAILURE using a merge of c11bf42cfefb5f572139c69eb60e7f48169ec933
Summary: Compilation error: Compiler Build time: 00:02:23

Core - Full Integration Build 11000 outcome was FAILURE using a merge of c11bf42cfefb5f572139c69eb60e7f48169ec933
Summary: Compilation error: Compiler Build time: 00:04:22

@bstansberry Fixed the merge conflict

Thanks @Ashpan. I expect we will integrate the needed WildFly Core release on Monday.

/retest

authors: Ashpan bstansberry wildfly-ci

repo: wildfly/wildfly-core


text:
High Cpu usage  of iohook in the electron . Currently it is going upto 50-80%

Expected Behaviour:
iohook should not increase CPU usage that much Currently it goes up to 80%. It should not downgrade the performance
Current Behavior
After some time of usage(like mouse move and mouseclick)  sometimes it goes till 70-80%
The code i am using
export const initActiveScreenListener = (mainWindow) => {
  let activeDisplay = screen.getPrimaryDisplay();
  const onMouseClick = () => {
    const currentDisplay = screen.getDisplayNearestPoint(
      screen.getCursorScreenPoint()
    );
    if (activeDisplay.id !== currentDisplay.id) {
      activeDisplay = currentDisplay;
      mainWindow.webContents.send(ACTIVE_SCREEN_CHANGED, { ...activeDisplay });
    }
  };
  const displayRemoved = (_, removedDisplay) => {
    if (removedDisplay.id === activeDisplay.id) {
      activeDisplay = screen.getPrimaryDisplay();
      mainWindow.webContents.send(ACTIVE_SCREEN_CHANGED, { ...activeDisplay });
    }
  };
  const debouncedClick = debounce(onMouseClick, 0);
  ioHook.on('mouseclick', debouncedClick);
  ioHook.on('mouseup', debouncedClick);
  screen.on(DISPLAY_REMOVED, displayRemoved);
  ioHook.start();
};

IOHook Version:0.9.3
electron : 12.0.4
node: 14.0
Operating System and version (desktop or mobile): Windows 10

any update on the behaviour? deciding whether to use it or not for a new project.

The issue was multiple event listeners were created every time I reload the app.
So make sure you clear event listeners before registering again.

The issue was multiple event listeners were created every time I reload the app. So make sure you clear event listeners before registering again.

Got it! thank you for the input :)
This issue can be marked as resolved

repo: wilix-team/iohook


text:
For each event add a client identification.

When you use the $un function, it removes all the handlers registered on an event.
But if you want to remove just a particular handler on an event, you can't.
With this evolution when you register a handler, you can specify the associate client.
Example:
ws.$on({event: "$close", client: "client1"}, function() {} );
ws.$on({event: "$close", client: "client2"}, function() {} );
And when you want to unregister this handler, you can do the same.
ws.$un({event: "$close", client: "client1"});
The handler of "client2" is still working.

+1 for the feature (didn't test the code)

authors: LeleDev cdupetit

repo: wilk/ng-websocket


text:
kde plots fail when limits cut into posterior bulk

Changing limits in a way that cuts the posterior bulk messes with kde plots (see image below).
This was first encountered in #104, although unrelated to the fix therein. This might also be related to #95 and #99.
MWE:
ns = NestedSamples(root="./tests/example_data/pc")
ns.limits['x0'] = (0, 5)
ns.plot_2d(['x0', 'x1', 'x2']);

As mentioned in #99, a possible solution might be to separate xmin and xmax into compression/kde limits and plotting limits.

Another way would be to apply xmin and xmax limits, and then compress the remaining samples (rather than the opposite order as is currently done).

How would either case affect the behaviour at the boundary?

Fixed by #212 and #216.
ns = read_chains(root="./tests/example_data/pc")
fig, axes = ns.plot_2d(['x0', 'x1', 'x2']);
axes.iloc[0, 0].set_xlim(0, 1)

authors: lukashergt williamjameshandley

repo: williamjameshandley/anesthetic


text:
Various updates and transaction log files support

Hello.
This pull request features various updates to the code of the primary file parser. The list of most important updates is:

The REGFBlock now has the recovery_required() method instead of the validate() method. This allows a library user to distinguish between 'header and data recovery required' and 'data recovery required' situations.
The REGFBlock also has the new clustering_factor(), file_type(), is_primary_file(), is_old_transaction_log_file(), is_new_transaction_log_file(), file_format() methods.
The NKRecord's has_classname() method now relies on the class name length instead of the class name offset (according to Joachim Metz: "The class name offset can also be 0 if not set. Seen in combination with a class name size of 0").
The NKRecord's is_root() method in now checking the bit mask 0x4 instead of a common value (0x2C).
The HBINBlock's last_hbin_offset() method is now replaced with the hbins_size() method, because the corresponding field contains the size of all hbins, not the offset of the last hbin. The has_next() method was modified to use the hbins_size().

Also, the support for the transaction log files (new format) has been implemented (the RegistryLog class). This is the must-have, because recent versions of Windows (Windows 8.1, Windows Server 2012 R2, and Windows 10) don't write all changes to the primary file immediately, but keep them in transaction log files up to an hour (by default). See the Flush strategies in the Windows registry.
The RegistryLog class accepts a file-like object of a primary file (and reads 512 bytes from it) and a file-like object or a file path of a transaction log file (and reads it in full). The class offers the is_eligible_log() method to check if a transaction log file can be applied and the recover_hive() method to apply log entries to a file-like object of a primary file. For the dual-logging scheme, the class offers the recover_hive_continue(), is_starting_log() methods to be used to perform the recovery in the same way as Windows does.
Also, the TransactionLogFiles.py script has been included along with five test cases. This script is an example of how to implement the recovery in the Windows way.
Further things to consider:

A forensic examiner might want to apply log entries step by step in order to examine old consistent states of a hive. Currently, all eligible log entries are applied at once.
Reading the whole transaction log file isn't good, because this file can be larger than a primary file.

Nice work, will add a few comments.

@msuhanov: First, thank you for your thorough research into the registry behavior, and then turning the lessons into a well designed patch!
I am very excited to merge the transaction log support into python-registry. This will be a major new capability. I'll respond to any issues I see inline, and we can work to get the PR merged soon.

@msuhanov i went through the code and really like what i see. i made some comments about coding style that are mainly suggestions. if you disagree with any, let me know, and i can probably can be persuaded.
i would like to hear thoughts about adding write support to python-registry (for the log recovery). i think it should be very clear to a user if the source file will be changed, but perhaps this should happen at a higher level (eg. in the script their using, or a higher level interface). @NiKiZe @msuhanov thoughts?

The write only happen if recover_hive() is called? so it should be documented that this does a write.
Another secure way to do this would be to have a readonly parameter set in the constrcutor, but I don't think that would make sense in this case?

I have started implementing your suggestions. Hopefully I will address all of them soon.

@msuhanov sorry for the delay! github didn't give me any notification that you had updated the code, or i would have reviewed much sooner.
the changes you made look really good. im excited to merge them. please fix the namedtuple usage, and we'll be on our way!

I hope that the named tuple is used correctly now.

Looks great! Thanks again!

authors: NiKiZe msuhanov williballenthin

repo: williballenthin/python-registry


text:
Seeing memory leak under normal usage.

Hi, we're using image proxy in a docker container, running on our on-premise Kubernetes environment.
When trying it out in a load test for the same image, we see memory use going up, and then our system killing the process eventually when it takes up too much memory. This happens very quickly when we have somewhat of a reasonable load on it. Our docker image is practically the same as https://hub.docker.com/r/willnorris/imageproxy/~/dockerfile/ except that we start it with a domain whitelist. Our configuration with which it is started is CMD /go/bin/imageproxy -addr 0.0.0.0:80 -whitelist (... list of our domains )
We simply GET /400x,q80/https://cmgtcontent.ahold.com.kpnis.nl/cmgtcontent/media//001746500/000/001746560_001_superhero_BBQ_170523_(1).jpg. After about 20_000 requests the docker instance reaches its memory limit, after which it is killed.
Under no usage, it stays at its normal ~30 MB.

Interesting.  And just to ask a dumb question which you sort of already answered, but I'll ask anyway... you're not using the in-memory cache right?  (by passing -cache memory) 😄

We didn't pass any additional caching options, Memory is default right? Anyway, we're only pulling the same image with the same parameters, I'd expect the in-memory cache to fill up if I were requesting many different images, but this is just the same image over and over.

Hi,
we faced the same problem. Although we tried three different cache providers it did not worked well for us and it was killing the machine. We tried in-memory, S3 and file cache. We did some tests and even for one single link with same parameters we get (we think) somehow non-cached image and with each request the memory went higher and higher resulting in the proxy beeing killed requesting the same URL for approx 30 times in a row.
We saw the image was properly saved to cache (tested on S3 and file systems) but it was not loaded. For every reload of the image the image was resaved to cache.
After those tests, we configured nginx proxy cache, and the server went from beeing constantly overwhelmed and killed twice a day to almost zero utilization. Weird... :)

Memory is default right?

Default is no caching at all.
Based on @Shimmi's additional info, this definitely sounds like an issue.  I'll try to look into it.

okay, I'm pretty sure I've figured out what is going on here.  The short answer is that transformation was being performed on already cached images, resulting in a bunch of extra memory allocations and CPU usage.  A fix will be pushed shortly.
A slightly longer explanation is below.
HTTP Caching
First, some background which you probably already know.  There are two main ways of doing caching in HTTP.  The Expires and Cache-Control headers allow the server to specify the lifetime of a resource such that a client can continue to use a cached copy for a specified amount of time.  If the client already has the resource cached and it hasn't expired, then no additional round trips are needed at all to use the resource.
The Etag and Last-Modified headers allow a client that has a cached version of a resource to check with the server to see if a new version is available.  This always requires an additional round trip to the server, but assuming there have been no changes, the server can simply respond with a 304 status code, which instructs the client to use their cached copy.  There's no need to send the resource over the wire again.
httpcache
Imageproxy uses the gregjones/httpcache package to handle caching.  For connections between imageproxy and remote servers, httpcache takes care of everything for us, including both flavors of caching mentioned above.  It enforces all the right validation checks, sends etags to the server when needed, etc.  If the server responds with a 304, then httpcache will return its cached copy with a 200 status.  Unless you inspect the X-From-Cache header, there's no way to know if the response came from the cache or the remote server.
For "downstream" connections (those between the browser and imageproxy), we reuse the same caching headers as the upstream resource.  That is, we use the same values for Expires, Cache-Control, Etag, and Last-Modified.  For Expires and Cache-Control, this means that clients can just keep using their cached versions without talking to us again.  But for Etag and Last-Modified, we need to handle those requests and respond with a 304 status when appropriate.  Currently, this is happening here.
So, for a remote image (like this one) that serves an Etag and Last-Modified header but not an Expires or Cache-Control header, then the flow looks something like:

Check for transformed image in cache

found it in the cache, but it doesn't have an Expires or Cache-Control, so we need to check to see if the original image has been updated

Check for original (non-transformed) image in cache

found it in the cache, but it doesn't have an Expires or Cache-Control, so we need to check with the server to see if it's been updated

Refetch the remote image, including the etag and last-modified values in the request

remote image hasn't been updated (got a 304 response from remote server), so use the cached versions

Transform the image as requested
Check if the original request contained etag or last-modified data

one or both match, so we can return a 304 response

Steps 1-3 still need to happen to make sure the remote image hasn't changed, but steps 4 and 5 should be flipped.  That was just an oversight on my part when I originally implemented this and never noticed.  We were still returning a 304 response, so from the client's perspective everything looks fine.  But inside the server, we're doing a transformation in step 4 that isn't needed.
Anyway, like I said... fix will be pushed shortly.  I'll leave this bug open until you confirm that the new version seems to have fixed the problem for you.

oh, also meant to add that I was able to easily replicate imageproxy using hundreds of megs of memory when requesting the same cached image thousands of times (rakyll/hey is great for testing this by the way).  After the forthcoming fix, it stayed constant at 65mb even with 20,000 requests.

@willnorris Many thanks! That was fast :)
I've tested it and can confirm the memory consumption is OK for me.
But we are still facing big CPU load and the images beeing re-modified (tested with the file cache).
Hitting F5 for the same URL image for 30x times resulted in high CPU load:

Also the file in file cache is beeing modified with every new request:

Behaviour, I would expect is if the source image or URL parameters does not change, the image proxy should simply take the image from the cache and do not touch it again. Not sure what causes this...

okay, I'm going to close this as having fixed the original reported problem, the memory leak.  Please open a new issue to focus on the high CPU load, and I'll try to investigate.
As for the cached file being rewritten, that will end up needing to be fixed in the httpcache package.    I'd suggest opening a bug there, and I'll try and take a look at what would be involved in fixing it.

authors: Shimmi SkPhilipp willnorris

repo: willnorris/imageproxy


text:
Formatting for SASS

The extension is perfect and has helped a lot!
But it could have an adjustment to Sass's language.
When it is applied to Variael it always applies ";" This works for SCSS but not for pure Sass.
My suggestion would be not to apply ";" when in Sass.

regards

Thanks for opening the issue @carlosfachini
I would love it if you could raise a PR, else give me some time as I am busy with some other tasks. 🙇🏽

authors: carlosfachini phoenisx

repo: willofindie/vscode-cssvar


text:
fish-shell not working

fishShell: https://github.com/fish-shell/fish-shell/
oh-my-fish: https://github.com/bpinto/oh-my-fish
~/.config/fish/config.fish
. $(brew --prefix php-version)/php-version.sh

fish: Illegal command name 'COLOR_NORMAL=$(tput sgr0)'
/usr/local/Cellar/php-version/0.10.4/php-version.sh (line 10):   COLOR_NORMAL=$(tput sgr0)
                                                                 ^
in . (source) call of file '/usr/local/Cellar/php-version/0.10.4/php-version.sh',
    called on standard input,

fish: Illegal command name 'COLOR_REVERSE=$(tput smso)'
/usr/local/Cellar/php-version/0.10.4/php-version.sh (line 11):   COLOR_REVERSE=$(tput smso)
                                                                 ^
in . (source) call of file '/usr/local/Cellar/php-version/0.10.4/php-version.sh',
    called on standard input,

fish: Illegal command name '[[ -n $(command -v brew) ]]'
/usr/local/Cellar/php-version/0.10.4/php-version.sh (line 25):   if [[ -n $(command -v brew) ]]; then
                                                                    ^
in . (source) call of file '/usr/local/Cellar/php-version/0.10.4/php-version.sh',
    called on standard input,

Rewrite in Go so works everywhere pls. 💯

After evaluating go-lang I've decided I have no long-term interest in that language. If I re-write this, it will likely be done with rust.

SEE: https://github.com/wilmoore/php-version/issues/56

I keep hearing people like Rust. I should probably read about it.
I ended up going with phpbrew out of impatience, but this might be a good project to play around with Rust (assuming you aren't already a master of it). :}

The more important bit of info is that I haven't done PHP work in several years and I don't plan to change that. That being said, php-version is a simple program and I do like solving these types of problem so I'll likely get around to it at some point.

Yeah, I feel ya. I wish I could live in ES6+ Node forever but WordPress gonna WordPress.

authors: corysimmons denji wilmoore

repo: wilmoore/php-version


text:
最大长度限制200字符

提个bug哈，双击编辑框，只能输入200个字符。打开开发者模式显示如下：

太棒了

repo: windily-cloud/obsidian-AGtable


text:
Open the browser if your service has a load balancer

Hello @maiamcc, @yuindustries,
Please review the following commits I made in branch nicks/lb:
7568aff34aae951042fce8ce0f144fb5db55b5a9 (2018-08-29 14:49:44 -0400)
Open the browser if your service has a load balancer

i think the long-term behavior should be something like
"by default, Tilt runs in auto-browser mode, where it tries to detect the best endpoint to open a browser"
and that you can override the auto behavior in the tiltfile, like
composite_service(my_services, browser="auto")
or
composite_service(my_services, browser="name-of-service")

I see that @maiamcc has reviewed the code, but I'll chime in that in my testing this works well and feels like a definite improvement.

authors: nicks yuindustries

repo: windmilleng/tilt