text:
Add JustList: {JustList name}

Before submission deletes this line:
THIS IS NOT A TOKEN LISTING REQUEST FORM. IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[ ] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Sorry, your issue will be closed as you did not submit your information in the correct format.Please resubmit.


text:
添加JustList: {JustList name}

提交之前请删除下面的话:
如果您没按照要求提交正确的JustList样式，您的issue将会被删除
您提交的JustList json格式必须满足下面链接中定义的例子格式
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
检查清单

[ ] 我已知晓此issue不是提交token而是提交JustList
[ ] 我已经测试粘贴JustList URL到justswap.org的添加列表中并能够正常展示.
[ ] 我已知晓提交的issue不能确保通过并且提交的JustList不确保能在jsutlists网站中显示.

请提供以下的信息
JustList的json URL必须以HTTPS开头.
JustList URL:
JustList 名称:
JustList 提交者的网站或主页:

Please submit the correct information, invalid information will cause the issue to close

source: gharchive/issue

repo: justswaporg/justlists

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 Journals is down

In b065011, Journals (https://tecnoscientifica.com/journal/tasp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Journals is back up in b60dcd3.

repo: justudin/tsp-status


text:
Don't auto pull & push when adding recipients

When adding a recipients gopass decrypts & encrypts all files one after another. This is ok when running locally. Sadly this gets really slow if auto pull & push is enabled, because gopass does a git pull & git push after finishing every single file.
Workaround:
gopass config autopull false
gopass config autopush false
gopass recipients add (--store pluto) 1234ZXCV...
gopass config autopull true
gopass config autopush true

It would be awesome to disable this behavior by default if a recipients is being added.
This isn't super important, just nice to have.

Yes, I agree. Noticed that as well. Maybe we can implement a work around for 1.3 and a proper fix when we revamp the config handling in 1.4 (or later).

authors: dominikschulz metalmatze

repo: justwatchcom/gopass

license: mit

license_source: bigquery


text:
Always lint, vet, and fmt code

Hello, @justyntemme! I found this project from your post on Reddit. I thought I would offer a few pieces of advice by filing a couple of issues. Feel free to follow or close them as you see fit.
The thing I would immediately say is to ensure your editor is always running gofmt (or better yet goimports) every time you save your code. The beauty of gofmt is that the entire Go community can have unified code style without bikeshedding over things like brace placement. As the proverb goes

Gofmt's style is no one's favorite, yet gofmt is everyone's favorite.

Additionally there are a few issues brought up by golint. Your editor should also be configured to run this on save and report the results.
Finally even though it doesn't report anything you should also be running go vet on save.
Cheers!

Thanks for stopping by! I will be reading through the issues today and seeing if i can't knock a few out. Appreciate you writing this up.

I would recomend fatih/vim-go for coding go in Vim.
It can be configured to auto-fmt and even auto-import packages.

I have used vim-go previously just have yet to set it up on my new install. Great tool for working with go and can get packages from within vim without ever leaving your file.

authors: jcbwlkr justyntemme loffa

repo: justyntemme/goMonitor


text:
FunctionContextExtensions.cs

First, thank you so much for putting this example out there. Very helpful.
You may already be aware but with a new update of the SDK reflection isn't necessary anymore in FunctionContextExtensions.cs:
public static void SetHttpResponseStatusCode(
            this FunctionContext context,
            HttpStatusCode statusCode)
{

  var httpReqData = context.GetHttpRequestDataAsync().GetAwaiter().GetResult();

  if (httpReqData != null)
  {
    var newResponse = httpReqData.CreateResponse();
    newResponse.StatusCode = statusCode;
    // Update invocation result.
    context.GetInvocationResult().Value = newResponse;
  }

return;
}

The above should be a drop in replacement for your original code w/ reflection. azure-functions-dotnet-worker issue/comment. You will need to upgrade the SDK to Version 1.8.0-preview3.

Nice! Will be updating the sample as soon as I have the chance. 😁

Hi , When we expect this version 1.8.0-preview3 will get release. please let us know at least expected date

authors: jassent juunas11 ngajbhiy


text:
:recycle: major refactoring

I'll document the changes tomorrow - a bit too tired now :upside_down_face:
Long story short -> used more traits & structs to provide more flexibility (& less duplicate code) yay! :tada:
-- did not add support for aarch64/arm (as I currently do not have access to my ARM testing device)

I can assist with the ARM64 testing if you need.

Would be very useful! @varon
It should be safe to look into adding support for ARM/Aarch64 for ints & uints  from #21 (after this merge)

I'll fix the u32 AVX2 regression in PR #21

source: gharchive/pull-request

authors: jvdd varon

repo: jvdd/argminmax


text:
support OS X

I've been playing with this lovely module and its great.
problem is that it doesn't work on mac.
it seems like the call to modprobe ifb fails because it doesn't exist on mac.
as far as my understanding, tc does work on mac and there must be a small different in initiation process

Supporting macOS is not an easy job, I'm only using this module on redhat so i'm not really interested on investigating it, but if you do, open a pull request and I'll merge it.

repo: jvictorsoto/tc-wrapper


text:
Update the Windows configuration file

While working on #1617, I've noticed that the configuration file on Windows is missing some major changes which have been made to the other configuration files.
The Windows configuration should be updated to incorporate all missing fields and documentation reworks.
Since this is non-trivial I think it's best to do this in a separate PR rather than incorporating it into the unrelated #1617.

Hi, can I do it?

@gnumoksha Of course! Feel free to let me know here or on IRC if you have any questions.

Since this issue has been open for a while and there was noone actively working on it, I've decided to resolve it myself in #1718.

Reopening because of https://github.com/jwilm/alacritty/pull/1723

authors: chrisduerr gnumoksha zacps

repo: jwilm/alacritty


text:
Launch a login shell by default on Linux

Alacritty did not launch a login shell by default on Linux contrary to
what is claimed by the comments in the configuration file. As a result,
bash does not read /etc/profile file leading to an inconsistent
environment compared to those with other terminals.
This commit simply extends what has been done by PR #1856 referenced by
issue #1071.

This does not seem to be the defualt behavior on gnome-terminal. The following should print 0 if it is a login shell.
$ shopt -q login_shell; echo $?
1

You are right, it is different between my system and other pristine systems (I wrongly assumed it was the same).
I was misled because I always use tmux inside my terminals and tmux launch shells as login shells for new windows. Without tmux, my other installed terminals (gnome-terminal, terminator) also launch login shells but I should have configured them long time ago and I forgot that (so it does not match anymore their default configuration).
My questions now are:

Should MacOS and linux alacritty terminals' behavior be consistent?
If not, why is it different on MacOS? (out of curiosity, I have no Mac)
If yes, I could reword the commit description removing the part about other terminals' behavior.
If this PR is not the right thing to do, I could close it and make another one fixing the comment about default login shells in alacritty.conf (line 366).

Should MacOS and linux alacritty terminals' behavior be consistent?

No, the reason why --login is explicitly required on macOS is because otherwise the environment will be messed up and the locale is not set correctly. Linux does not have this issue.

If this PR is not the right thing to do, I could close it and make another one fixing the comment about default login shells in alacritty.conf

I don't think it's necessary to open a new PR, but that seems reasonable. The current docs are probably incorrect because there has been some refactorings in the past, Alacritty will not use bash by default on Linux at all for example.

Alacritty will not use bash by default on Linux at all for example

I missed that point.
I have reverted my change and fixed the docs about default shell. I am unsure about how format the description of the linux default shell since it is not a "static" default value.
When and if OK, I will squash the commits and rename the title of the PR.

When and if OK, I will squash the commits and rename the title of the PR.

No need to, I squash and fix the commit message of every PR when merging anyways.

Requested changes applied.

authors: NickeZ chrisduerr gentooboontoo


text:
i enters Vim insert mode from Jupyter command mode

This addresses #70.

@wmayner I forgot that the interrupt shortcut is I,I so like vim, jupyterlab waits a while to resolve this shortcut. Raises the question if we should remap the interrupt shortcut?

I prefer using Ctrl + c as the interrupt hotkey, similar to the command line. But that's a personal preference, and I'm also hesitant to remap jupyterlab defaults. It's a shame though, since i is so fundamental to using Vim.
At least if we add the command, users can remap as they see fit. Perhaps we can just add the command for now and defer the binding to a later PR?

I just realized I was actually wrong about the original functionality: in jupyter-vim-binding, i would only enter Vim command mode. So in fact your initial suggestion was totally right if the goal is to duplicate the jupyter-vim-binding functionality, and all I need to is override the default bindings in jupyterlab.

Perhaps we could use Ctrl + I as a binding to go directly into Vim insert mode, and leave it up to users to override the I + I binding if they want. Ctrl + I doesn't seem to interfere with jupyterlab bindings.

This sounds like a good compromise to me, thanks for the suggestion. I'll merge this in now. Sometime in the next few days I'll cut a new release.

authors: jwkvam wmayner

repo: jwkvam/jupyterlab-vim


text:
Cleeng as a separate module

Acceptance criteria
Cleeng is an optional module, which is by default off
Documention on how to enable Cleeng integration
Solution directions
Some ideas that came per mail:
Include an Cleeng module during the build
Lazyloading of the Cleeng module based on parameter
As a plug-in from a remote repository

This path has been started with v3 / v4 allowing jwp or cleeng integrations

repo: jwplayer/ott-web-app


text:
Fix Issue with Authenticated Proxies in Scrapy

This pull request addresses an issue in Scrapy where authenticated proxies fail to connect.
Scrapy's proxy middleware automatically processes the HTTP Proxy-Authorization header, which needs special handling for authenticated proxies. To resolve this, special handling for authenticated proxies has been implemented, ensuring that the Proxy-Authorization header is correctly set in the request headers. The changes include:

Added logic to handle Proxy-Authorization in the handler.py file.
Ensured that the Proxy-Authorization header is properly set for proxy requests requiring user authentication.

These changes will fix the connection issues with authenticated proxies

Thanks!

repo: jxlil/scrapy-impersonate


text:
🛑 le Zata is down

In 13b59c0, le Zata (http://zata.free.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: le Zata is back up in 6bb7f69 after 15 minutes.

repo: jyhem/upptime-jyhem


text:
npm install failed! does anybody has ideas what's wrong with it

hi ! i try to build jquery-validation with nodejs in Version 6.9.4 'Boron' (LTS)(WIN7 64bit)
but it failed and then i try the Version 7.4.0  it failed to build either, the log is below .and i want to consult how to solve this problem
0 info it worked if it ends with ok
1 verbose cli [ 'D:\Program Files\nodejs\node.exe',
1 verbose cli   'D:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli   'install' ]
2 info using npm@3.10.10
3 info using node@v6.9.4
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly install normalizeTree
8 silly loadCurrentTree Finishing
9 silly loadIdealTree Starting
10 silly install loadIdealTree
11 silly cloneCurrentTree Starting
12 silly install cloneCurrentTreeToIdealTree
13 silly cloneCurrentTree Finishing
14 silly loadShrinkwrap Starting
15 silly install loadShrinkwrap
16 silly loadShrinkwrap Finishing
17 silly loadAllDepsIntoIdealTree Starting
18 silly install loadAllDepsIntoIdealTree
19 silly loadAllDepsIntoIdealTree Finishing
20 silly loadIdealTree Finishing
21 silly currentTree jquery-validation@1.16.1-pre
21 silly currentTree +-- abbrev@1.0.9
21 silly currentTree +-- acorn@3.3.0
21 silly currentTree +-- align-text@0.1.4
21 silly currentTree +-- alter@0.2.0
21 silly currentTree +-- amdefine@1.0.1
21 silly currentTree +-- ansi-regex@2.1.1
21 silly currentTree +-- ansi-styles@2.2.1
21 silly currentTree +-- archiver-utils@0.3.0
21 silly currentTree | -- glob@6.0.4 21 silly currentTree +-- archiver@0.21.0 21 silly currentTree | -- glob@6.0.4
21 silly currentTree +-- argparse@1.0.9
21 silly currentTree +-- array-find-index@1.0.2
21 silly currentTree +-- asn1@0.2.3
21 silly currentTree +-- assert-plus@0.2.0
21 silly currentTree +-- ast-traverse@0.1.1
21 silly currentTree +-- ast-types@0.9.4
21 silly currentTree +-- async@1.5.2
21 silly currentTree +-- asynckit@0.4.0
21 silly currentTree +-- aws-sign2@0.6.0
21 silly currentTree +-- aws4@1.5.0
21 silly currentTree +-- babel-core@5.8.38
21 silly currentTree | +-- debug@2.6.0
21 silly currentTree | +-- minimatch@2.0.10
21 silly currentTree | +-- ms@0.7.2
21 silly currentTree | +-- path-exists@1.0.0
21 silly currentTree | -- repeating@1.1.3 21 silly currentTree +-- babel-jscs@2.0.5 21 silly currentTree +-- babel-plugin-constant-folding@1.0.1 21 silly currentTree +-- babel-plugin-dead-code-elimination@1.0.2 21 silly currentTree +-- babel-plugin-eval@1.0.1 21 silly currentTree +-- babel-plugin-inline-environment-variables@1.0.1 21 silly currentTree +-- babel-plugin-jscript@1.0.4 21 silly currentTree +-- babel-plugin-member-expression-literals@1.0.1 21 silly currentTree +-- babel-plugin-property-literals@1.0.1 21 silly currentTree +-- babel-plugin-proto-to-assign@1.0.4 21 silly currentTree +-- babel-plugin-react-constant-elements@1.0.3 21 silly currentTree +-- babel-plugin-react-display-name@1.0.3 21 silly currentTree +-- babel-plugin-remove-console@1.0.1 21 silly currentTree +-- babel-plugin-remove-debugger@1.0.1 21 silly currentTree +-- babel-plugin-runtime@1.0.7 21 silly currentTree +-- babel-plugin-undeclared-variables-check@1.0.2 21 silly currentTree +-- babel-plugin-undefined-to-void@1.1.6 21 silly currentTree +-- babylon@5.8.38 21 silly currentTree +-- balanced-match@0.4.2 21 silly currentTree +-- bcrypt-pbkdf@1.0.0 21 silly currentTree +-- bl@1.2.0 21 silly currentTree +-- bluebird@2.11.0 21 silly currentTree +-- body-parser@1.14.2 21 silly currentTree | +-- debug@2.2.0 21 silly currentTree | +-- iconv-lite@0.4.13 21 silly currentTree | -- qs@5.2.0
21 silly currentTree +-- boom@2.10.1
21 silly currentTree +-- brace-expansion@1.1.6
21 silly currentTree +-- breakable@1.0.0
21 silly currentTree +-- browserify-zlib@0.1.4
21 silly currentTree +-- buffer-crc32@0.2.13
21 silly currentTree +-- builtin-modules@1.1.1
21 silly currentTree +-- bytes@2.2.0
21 silly currentTree +-- camelcase-keys@2.1.0
21 silly currentTree +-- camelcase@2.1.1
21 silly currentTree +-- caseless@0.11.0
21 silly currentTree +-- center-align@0.1.3
21 silly currentTree +-- chalk@1.1.3
21 silly currentTree +-- cli-table@0.3.1
21 silly currentTree | -- colors@1.0.3 21 silly currentTree +-- cli@1.0.1 21 silly currentTree | -- glob@7.1.1
21 silly currentTree +-- cliui@2.1.0
21 silly currentTree +-- coffee-script@1.10.0
21 silly currentTree +-- colors@1.1.2
21 silly currentTree +-- combined-stream@1.0.5
21 silly currentTree +-- commander@2.9.0
21 silly currentTree +-- comment-parser@0.3.1
21 silly currentTree +-- commitplease@2.3.1
21 silly currentTree +-- commoner@0.10.8
21 silly currentTree | +-- esprima@3.1.3
21 silly currentTree | +-- glob@5.0.15
21 silly currentTree | -- recast@0.11.20 21 silly currentTree +-- compress-commons@0.4.2 21 silly currentTree +-- concat-map@0.0.1 21 silly currentTree +-- concat-stream@1.5.0 21 silly currentTree +-- console-browserify@1.1.0 21 silly currentTree +-- content-type@1.0.2 21 silly currentTree +-- convert-source-map@1.3.0 21 silly currentTree +-- core-js@1.2.7 21 silly currentTree +-- core-util-is@1.0.2 21 silly currentTree +-- crc32-stream@0.4.0 21 silly currentTree +-- cryptiles@2.0.5 21 silly currentTree +-- currently-unhandled@0.4.1 21 silly currentTree +-- cycle@1.0.3 21 silly currentTree +-- d@0.1.1 21 silly currentTree +-- dashdash@1.14.1 21 silly currentTree | -- assert-plus@1.0.0
21 silly currentTree +-- date-now@0.1.4
21 silly currentTree +-- dateformat@1.0.12
21 silly currentTree +-- debug@0.7.4
21 silly currentTree +-- decamelize@1.2.0
21 silly currentTree +-- deep-equal@1.0.1
21 silly currentTree +-- defined@1.0.0
21 silly currentTree +-- defs@1.1.1
21 silly currentTree | +-- camelcase@1.2.1
21 silly currentTree | +-- esprima-fb@15001.1001.0-dev-harmony-fb
21 silly currentTree | +-- window-size@0.1.4
21 silly currentTree | -- yargs@3.27.0 21 silly currentTree +-- delayed-stream@1.0.0 21 silly currentTree +-- depd@1.1.0 21 silly currentTree +-- detect-indent@3.0.1 21 silly currentTree | -- repeating@1.1.3
21 silly currentTree +-- detective@4.3.2
21 silly currentTree +-- dom-serializer@0.1.0
21 silly currentTree | +-- domelementtype@1.1.3
21 silly currentTree | -- entities@1.1.1 21 silly currentTree +-- domelementtype@1.3.0 21 silly currentTree +-- domhandler@2.3.0 21 silly currentTree +-- domutils@1.5.1 21 silly currentTree +-- ecc-jsbn@0.1.1 21 silly currentTree +-- ee-first@1.1.1 21 silly currentTree +-- end-of-stream@1.1.0 21 silly currentTree | -- once@1.3.3
21 silly currentTree +-- entities@1.0.0
21 silly currentTree +-- error-ex@1.3.0
21 silly currentTree +-- es5-ext@0.10.12
21 silly currentTree +-- es6-iterator@2.0.0
21 silly currentTree +-- es6-map@0.1.4
21 silly currentTree +-- es6-promise@4.0.5
21 silly currentTree +-- es6-set@0.1.4
21 silly currentTree +-- es6-symbol@3.1.0
21 silly currentTree +-- es6-weak-map@2.0.1
21 silly currentTree +-- escape-string-regexp@1.0.5
21 silly currentTree +-- escope@3.6.0
21 silly currentTree +-- esprima@2.7.3
21 silly currentTree +-- esrecurse@4.1.0
21 silly currentTree | -- estraverse@4.1.1 21 silly currentTree +-- estraverse@4.2.0 21 silly currentTree +-- esutils@2.0.2 21 silly currentTree +-- event-emitter@0.3.4 21 silly currentTree +-- eventemitter2@0.4.14 21 silly currentTree +-- exit@0.1.2 21 silly currentTree +-- extend@3.0.0 21 silly currentTree +-- extract-zip@1.5.0 21 silly currentTree +-- extsprintf@1.0.2 21 silly currentTree +-- eyes@0.1.8 21 silly currentTree +-- faye-websocket@0.10.0 21 silly currentTree +-- fd-slicer@1.0.1 21 silly currentTree +-- figures@1.7.0 21 silly currentTree +-- file-sync-cmp@0.1.1 21 silly currentTree +-- find-up@1.1.2 21 silly currentTree +-- findup-sync@0.3.0 21 silly currentTree | -- glob@5.0.15
21 silly currentTree +-- forever-agent@0.6.1
21 silly currentTree +-- form-data@2.1.2
21 silly currentTree +-- fs-extra@1.0.0
21 silly currentTree +-- fs-readdir-recursive@0.1.2
21 silly currentTree +-- fs.realpath@1.0.0
21 silly currentTree +-- gaze@1.1.2
21 silly currentTree +-- generate-function@2.0.0
21 silly currentTree +-- generate-object-property@1.2.0
21 silly currentTree +-- get-stdin@4.0.1
21 silly currentTree +-- getobject@0.1.0
21 silly currentTree +-- getpass@0.1.6
21 silly currentTree | -- assert-plus@1.0.0 21 silly currentTree +-- glob@7.0.6 21 silly currentTree +-- globals@6.4.1 21 silly currentTree +-- globule@1.1.0 21 silly currentTree | +-- glob@7.1.1 21 silly currentTree | -- lodash@4.16.6
21 silly currentTree +-- graceful-fs@4.1.11
21 silly currentTree +-- graceful-readlink@1.0.1
21 silly currentTree +-- grunt-contrib-compress@1.2.0
21 silly currentTree | -- lodash@4.17.4 21 silly currentTree +-- grunt-contrib-concat@1.0.1 21 silly currentTree +-- grunt-contrib-copy@1.0.0 21 silly currentTree +-- grunt-contrib-jshint@1.0.0 21 silly currentTree +-- grunt-contrib-qunit@1.2.0 21 silly currentTree +-- grunt-contrib-uglify@1.0.1 21 silly currentTree | -- lodash@4.17.4
21 silly currentTree +-- grunt-contrib-watch@1.0.0
21 silly currentTree +-- grunt-jscs@2.8.0
21 silly currentTree | -- lodash@4.6.1 21 silly currentTree +-- grunt-known-options@1.1.0 21 silly currentTree +-- grunt-legacy-log-utils@1.0.0 21 silly currentTree | -- lodash@4.3.0
21 silly currentTree +-- grunt-legacy-log@1.0.0
21 silly currentTree +-- grunt-legacy-util@1.0.0
21 silly currentTree | -- lodash@4.3.0 21 silly currentTree +-- grunt-lib-phantomjs@1.1.0 21 silly currentTree | -- rimraf@2.5.4
21 silly currentTree +-- grunt-text-replace@0.4.0
21 silly currentTree +-- grunt@1.0.1
21 silly currentTree | -- grunt-cli@1.2.0 21 silly currentTree +-- gzip-size@1.0.0 21 silly currentTree +-- har-validator@2.0.6 21 silly currentTree +-- has-ansi@2.0.0 21 silly currentTree +-- has-color@0.1.7 21 silly currentTree +-- hasha@2.2.0 21 silly currentTree +-- hawk@3.1.3 21 silly currentTree +-- hoek@2.16.3 21 silly currentTree +-- home-or-tmp@1.0.0 21 silly currentTree +-- hooker@0.2.3 21 silly currentTree +-- hosted-git-info@2.1.5 21 silly currentTree +-- htmlparser2@3.8.3 21 silly currentTree | -- readable-stream@1.1.14
21 silly currentTree +-- http-errors@1.3.1
21 silly currentTree +-- http-signature@1.1.1
21 silly currentTree +-- i@0.3.5
21 silly currentTree +-- iconv-lite@0.4.15
21 silly currentTree +-- indent-string@2.1.0
21 silly currentTree +-- inflight@1.0.6
21 silly currentTree +-- inherit@2.2.6
21 silly currentTree +-- inherits@2.0.3
21 silly currentTree +-- invert-kv@1.0.0
21 silly currentTree +-- is-arrayish@0.2.1
21 silly currentTree +-- is-buffer@1.1.4
21 silly currentTree +-- is-builtin-module@1.0.0
21 silly currentTree +-- is-finite@1.0.2
21 silly currentTree +-- is-integer@1.0.6
21 silly currentTree +-- is-my-json-valid@2.15.0
21 silly currentTree +-- is-property@1.0.2
21 silly currentTree +-- is-stream@1.1.0
21 silly currentTree +-- is-typedarray@1.0.0
21 silly currentTree +-- is-utf8@0.2.1
21 silly currentTree +-- isarray@0.0.1
21 silly currentTree +-- isexe@1.1.2
21 silly currentTree +-- isstream@0.1.2
21 silly currentTree +-- jodid25519@1.0.2
21 silly currentTree +-- jquery@3.1.1
21 silly currentTree +-- js-tokens@1.0.1
21 silly currentTree +-- js-yaml@3.5.5
21 silly currentTree +-- jsbn@0.1.0
21 silly currentTree +-- jscs-jsdoc@1.3.2
21 silly currentTree +-- jscs-preset-wikimedia@1.0.0
21 silly currentTree +-- jscs@2.11.0
21 silly currentTree | +-- glob@5.0.15
21 silly currentTree | -- js-yaml@3.4.6 21 silly currentTree +-- jsdoctypeparser@1.2.0 21 silly currentTree +-- jsesc@0.5.0 21 silly currentTree +-- jshint@2.9.4 21 silly currentTree | -- lodash@3.7.0
21 silly currentTree +-- json-schema@0.2.3
21 silly currentTree +-- json-stringify-safe@5.0.1
21 silly currentTree +-- json5@0.4.0
21 silly currentTree +-- jsonfile@2.4.0
21 silly currentTree +-- jsonlint@1.6.2
21 silly currentTree +-- jsonpointer@4.0.1
21 silly currentTree +-- jsprim@1.3.1
21 silly currentTree +-- JSV@4.0.2
21 silly currentTree +-- kew@0.7.0
21 silly currentTree +-- kind-of@3.1.0
21 silly currentTree +-- klaw@1.3.1
21 silly currentTree +-- lazy-cache@1.0.4
21 silly currentTree +-- lazystream@0.1.0
21 silly currentTree | -- readable-stream@1.0.34 21 silly currentTree +-- lcid@1.0.0 21 silly currentTree +-- leven@1.0.2 21 silly currentTree +-- livereload-js@2.2.2 21 silly currentTree +-- load-json-file@1.1.0 21 silly currentTree +-- lodash._baseassign@3.2.0 21 silly currentTree +-- lodash._basecopy@3.0.1 21 silly currentTree +-- lodash._bindcallback@3.0.1 21 silly currentTree +-- lodash._createassigner@3.1.1 21 silly currentTree +-- lodash._getnative@3.9.1 21 silly currentTree +-- lodash._isiterateecall@3.0.9 21 silly currentTree +-- lodash.assign@3.2.0 21 silly currentTree +-- lodash.isarguments@3.1.0 21 silly currentTree +-- lodash.isarray@3.0.4 21 silly currentTree +-- lodash.keys@3.1.2 21 silly currentTree +-- lodash.restparam@3.6.1 21 silly currentTree +-- lodash@3.10.1 21 silly currentTree +-- longest@1.0.1 21 silly currentTree +-- loud-rejection@1.6.0 21 silly currentTree +-- map-obj@1.0.1 21 silly currentTree +-- maxmin@1.1.0 21 silly currentTree | -- pretty-bytes@1.0.4
21 silly currentTree +-- media-typer@0.3.0
21 silly currentTree +-- meow@3.7.0
21 silly currentTree +-- mime-db@1.26.0
21 silly currentTree +-- mime-types@2.1.14
21 silly currentTree +-- minimatch@3.0.3
21 silly currentTree +-- minimist@1.2.0
21 silly currentTree +-- mkdirp@0.5.0
21 silly currentTree | -- minimist@0.0.8 21 silly currentTree +-- mout@0.12.0 21 silly currentTree +-- ms@0.7.1 21 silly currentTree +-- mute-stream@0.0.7 21 silly currentTree +-- natural-compare@1.2.2 21 silly currentTree +-- ncp@0.4.2 21 silly currentTree +-- node-int64@0.4.0 21 silly currentTree +-- nomnom@1.8.1 21 silly currentTree | +-- ansi-styles@1.0.0 21 silly currentTree | +-- chalk@0.4.0 21 silly currentTree | -- strip-ansi@0.1.1
21 silly currentTree +-- nopt@3.0.6
21 silly currentTree +-- normalize-package-data@2.3.5
21 silly currentTree +-- normalize-path@2.0.1
21 silly currentTree +-- number-is-nan@1.0.1
21 silly currentTree +-- oauth-sign@0.8.2
21 silly currentTree +-- object-assign@4.1.1
21 silly currentTree +-- on-finished@2.3.0
21 silly currentTree +-- once@1.4.0
21 silly currentTree +-- os-locale@1.4.0
21 silly currentTree +-- os-tmpdir@1.0.2
21 silly currentTree +-- output-file-sync@1.1.2
21 silly currentTree | +-- minimist@0.0.8
21 silly currentTree | -- mkdirp@0.5.1 21 silly currentTree +-- package@1.0.1 21 silly currentTree +-- pako@0.2.9 21 silly currentTree +-- parse-json@2.2.0 21 silly currentTree +-- parseurl@1.3.1 21 silly currentTree +-- path-exists@2.1.0 21 silly currentTree +-- path-is-absolute@1.0.1 21 silly currentTree +-- path-type@1.1.0 21 silly currentTree +-- pathval@0.1.1 21 silly currentTree +-- pend@1.2.0 21 silly currentTree +-- phantomjs-prebuilt@2.1.14 21 silly currentTree +-- pify@2.3.0 21 silly currentTree +-- pinkie-promise@2.0.1 21 silly currentTree +-- pinkie@2.0.4 21 silly currentTree +-- pkginfo@0.4.0 21 silly currentTree +-- pretty-bytes@3.0.1 21 silly currentTree +-- private@0.1.6 21 silly currentTree +-- process-nextick-args@1.0.7 21 silly currentTree +-- progress@1.1.8 21 silly currentTree +-- prompt@0.2.14 21 silly currentTree +-- punycode@1.4.1 21 silly currentTree +-- q@1.4.1 21 silly currentTree +-- qs@6.3.0 21 silly currentTree +-- qunitjs@2.0.0 21 silly currentTree +-- raw-body@2.1.7 21 silly currentTree | +-- bytes@2.4.0 21 silly currentTree | -- iconv-lite@0.4.13
21 silly currentTree +-- read-pkg-up@1.0.1
21 silly currentTree +-- read-pkg@1.1.0
21 silly currentTree +-- read@1.0.7
21 silly currentTree +-- readable-stream@2.0.6
21 silly currentTree | -- isarray@1.0.0 21 silly currentTree +-- recast@0.10.33 21 silly currentTree | +-- ast-types@0.8.12 21 silly currentTree | -- esprima-fb@15001.1001.0-dev-harmony-fb
21 silly currentTree +-- redent@1.0.0
21 silly currentTree +-- regenerate@1.3.2
21 silly currentTree +-- regenerator@0.8.40
21 silly currentTree | -- esprima-fb@15001.1001.0-dev-harmony-fb 21 silly currentTree +-- regexpu@1.3.0 21 silly currentTree +-- regjsgen@0.2.0 21 silly currentTree +-- regjsparser@0.1.5 21 silly currentTree +-- repeat-string@1.6.1 21 silly currentTree +-- repeating@2.0.1 21 silly currentTree +-- request-progress@2.0.1 21 silly currentTree +-- request@2.79.0 21 silly currentTree +-- reserved-words@0.1.1 21 silly currentTree +-- resolve@1.1.7 21 silly currentTree +-- revalidator@0.1.8 21 silly currentTree +-- right-align@0.1.3 21 silly currentTree +-- rimraf@2.2.8 21 silly currentTree +-- semver@5.3.0 21 silly currentTree +-- shebang-regex@1.0.0 21 silly currentTree +-- shelljs@0.3.0 21 silly currentTree +-- signal-exit@3.0.2 21 silly currentTree +-- simple-fmt@0.1.0 21 silly currentTree +-- simple-is@0.2.0 21 silly currentTree +-- slash@1.0.0 21 silly currentTree +-- sntp@1.0.9 21 silly currentTree +-- source-map-support@0.2.10 21 silly currentTree | -- source-map@0.1.32
21 silly currentTree +-- source-map@0.5.6
21 silly currentTree +-- spdx-correct@1.0.2
21 silly currentTree +-- spdx-expression-parse@1.0.4
21 silly currentTree +-- spdx-license-ids@1.2.2
21 silly currentTree +-- sprintf-js@1.0.3
21 silly currentTree +-- sshpk@1.10.2
21 silly currentTree | -- assert-plus@1.0.0 21 silly currentTree +-- stable@0.1.5 21 silly currentTree +-- stack-trace@0.0.9 21 silly currentTree +-- statuses@1.3.1 21 silly currentTree +-- stream-buffers@2.2.0 21 silly currentTree +-- string_decoder@0.10.31 21 silly currentTree +-- stringmap@0.2.2 21 silly currentTree +-- stringset@0.2.1 21 silly currentTree +-- stringstream@0.0.5 21 silly currentTree +-- strip-ansi@3.0.1 21 silly currentTree +-- strip-bom@2.0.0 21 silly currentTree +-- strip-indent@1.0.1 21 silly currentTree +-- strip-json-comments@1.0.4 21 silly currentTree +-- supports-color@2.0.0 21 silly currentTree +-- tar-stream@1.3.2 21 silly currentTree +-- temporary@0.0.8 21 silly currentTree +-- throttleit@1.0.0 21 silly currentTree +-- through@2.3.8 21 silly currentTree +-- tiny-lr@0.2.1 21 silly currentTree | +-- debug@2.2.0 21 silly currentTree | -- qs@5.1.0
21 silly currentTree +-- to-double-quotes@2.0.0
21 silly currentTree +-- to-fast-properties@1.0.2
21 silly currentTree +-- to-single-quotes@2.0.1
21 silly currentTree +-- tough-cookie@2.3.2
21 silly currentTree +-- trim-newlines@1.0.0
21 silly currentTree +-- trim-right@1.0.1
21 silly currentTree +-- try-resolve@1.0.1
21 silly currentTree +-- tryor@0.1.2
21 silly currentTree +-- tunnel-agent@0.4.3
21 silly currentTree +-- tweetnacl@0.14.5
21 silly currentTree +-- type-is@1.6.14
21 silly currentTree +-- typedarray@0.0.6
21 silly currentTree +-- uglify-js@2.6.4
21 silly currentTree | -- async@0.2.10 21 silly currentTree +-- uglify-to-browserify@1.0.2 21 silly currentTree +-- underscore.string@3.2.3 21 silly currentTree +-- underscore@1.6.0 21 silly currentTree +-- unpipe@1.0.0 21 silly currentTree +-- uri-path@1.0.0 21 silly currentTree +-- user-home@1.1.1 21 silly currentTree +-- util-deprecate@1.0.2 21 silly currentTree +-- utile@0.2.1 21 silly currentTree | -- async@0.2.10
21 silly currentTree +-- uuid@3.0.1
21 silly currentTree +-- validate-npm-package-license@3.0.1
21 silly currentTree +-- verror@1.3.6
21 silly currentTree +-- vow-fs@0.3.6
21 silly currentTree | -- uuid@2.0.3 21 silly currentTree +-- vow-queue@0.4.2 21 silly currentTree +-- vow@0.4.13 21 silly currentTree +-- websocket-driver@0.6.5 21 silly currentTree +-- websocket-extensions@0.1.1 21 silly currentTree +-- which@1.2.12 21 silly currentTree +-- window-size@0.1.0 21 silly currentTree +-- winston@0.8.3 21 silly currentTree | +-- async@0.2.10 21 silly currentTree | +-- colors@0.6.2 21 silly currentTree | -- pkginfo@0.3.1
21 silly currentTree +-- wordwrap@0.0.2
21 silly currentTree +-- wrappy@1.0.2
21 silly currentTree +-- xmlbuilder@3.1.0
21 silly currentTree +-- xtend@4.0.1
21 silly currentTree +-- y18n@3.2.1
21 silly currentTree +-- yargs@3.10.0
21 silly currentTree | -- camelcase@1.2.1 21 silly currentTree +-- yauzl@2.4.1 21 silly currentTree -- zip-stream@0.8.0
22 silly idealTree jquery-validation@1.16.1-pre
22 silly idealTree +-- abbrev@1.0.9
22 silly idealTree +-- acorn@3.3.0
22 silly idealTree +-- align-text@0.1.4
22 silly idealTree +-- alter@0.2.0
22 silly idealTree +-- amdefine@1.0.1
22 silly idealTree +-- ansi-regex@2.1.1
22 silly idealTree +-- ansi-styles@2.2.1
22 silly idealTree +-- archiver-utils@0.3.0
22 silly idealTree | -- glob@6.0.4 22 silly idealTree +-- archiver@0.21.0 22 silly idealTree | -- glob@6.0.4
22 silly idealTree +-- argparse@1.0.9
22 silly idealTree +-- array-find-index@1.0.2
22 silly idealTree +-- asn1@0.2.3
22 silly idealTree +-- assert-plus@0.2.0
22 silly idealTree +-- ast-traverse@0.1.1
22 silly idealTree +-- ast-types@0.9.4
22 silly idealTree +-- async@1.5.2
22 silly idealTree +-- asynckit@0.4.0
22 silly idealTree +-- aws-sign2@0.6.0
22 silly idealTree +-- aws4@1.5.0
22 silly idealTree +-- babel-core@5.8.38
22 silly idealTree | +-- debug@2.6.0
22 silly idealTree | +-- minimatch@2.0.10
22 silly idealTree | +-- ms@0.7.2
22 silly idealTree | +-- path-exists@1.0.0
22 silly idealTree | -- repeating@1.1.3 22 silly idealTree +-- babel-jscs@2.0.5 22 silly idealTree +-- babel-plugin-constant-folding@1.0.1 22 silly idealTree +-- babel-plugin-dead-code-elimination@1.0.2 22 silly idealTree +-- babel-plugin-eval@1.0.1 22 silly idealTree +-- babel-plugin-inline-environment-variables@1.0.1 22 silly idealTree +-- babel-plugin-jscript@1.0.4 22 silly idealTree +-- babel-plugin-member-expression-literals@1.0.1 22 silly idealTree +-- babel-plugin-property-literals@1.0.1 22 silly idealTree +-- babel-plugin-proto-to-assign@1.0.4 22 silly idealTree +-- babel-plugin-react-constant-elements@1.0.3 22 silly idealTree +-- babel-plugin-react-display-name@1.0.3 22 silly idealTree +-- babel-plugin-remove-console@1.0.1 22 silly idealTree +-- babel-plugin-remove-debugger@1.0.1 22 silly idealTree +-- babel-plugin-runtime@1.0.7 22 silly idealTree +-- babel-plugin-undeclared-variables-check@1.0.2 22 silly idealTree +-- babel-plugin-undefined-to-void@1.1.6 22 silly idealTree +-- babylon@5.8.38 22 silly idealTree +-- balanced-match@0.4.2 22 silly idealTree +-- bcrypt-pbkdf@1.0.0 22 silly idealTree +-- bl@1.2.0 22 silly idealTree +-- bluebird@2.11.0 22 silly idealTree +-- body-parser@1.14.2 22 silly idealTree | +-- debug@2.2.0 22 silly idealTree | +-- iconv-lite@0.4.13 22 silly idealTree | -- qs@5.2.0
22 silly idealTree +-- boom@2.10.1
22 silly idealTree +-- brace-expansion@1.1.6
22 silly idealTree +-- breakable@1.0.0
22 silly idealTree +-- browserify-zlib@0.1.4
22 silly idealTree +-- buffer-crc32@0.2.13
22 silly idealTree +-- builtin-modules@1.1.1
22 silly idealTree +-- bytes@2.2.0
22 silly idealTree +-- camelcase-keys@2.1.0
22 silly idealTree +-- camelcase@2.1.1
22 silly idealTree +-- caseless@0.11.0
22 silly idealTree +-- center-align@0.1.3
22 silly idealTree +-- chalk@1.1.3
22 silly idealTree +-- cli-table@0.3.1
22 silly idealTree | -- colors@1.0.3 22 silly idealTree +-- cli@1.0.1 22 silly idealTree | -- glob@7.1.1
22 silly idealTree +-- cliui@2.1.0
22 silly idealTree +-- coffee-script@1.10.0
22 silly idealTree +-- colors@1.1.2
22 silly idealTree +-- combined-stream@1.0.5
22 silly idealTree +-- commander@2.9.0
22 silly idealTree +-- comment-parser@0.3.1
22 silly idealTree +-- commitplease@2.3.1
22 silly idealTree +-- commoner@0.10.8
22 silly idealTree | +-- esprima@3.1.3
22 silly idealTree | +-- glob@5.0.15
22 silly idealTree | -- recast@0.11.20 22 silly idealTree +-- compress-commons@0.4.2 22 silly idealTree +-- concat-map@0.0.1 22 silly idealTree +-- concat-stream@1.5.0 22 silly idealTree +-- console-browserify@1.1.0 22 silly idealTree +-- content-type@1.0.2 22 silly idealTree +-- convert-source-map@1.3.0 22 silly idealTree +-- core-js@1.2.7 22 silly idealTree +-- core-util-is@1.0.2 22 silly idealTree +-- crc32-stream@0.4.0 22 silly idealTree +-- cryptiles@2.0.5 22 silly idealTree +-- currently-unhandled@0.4.1 22 silly idealTree +-- cycle@1.0.3 22 silly idealTree +-- d@0.1.1 22 silly idealTree +-- dashdash@1.14.1 22 silly idealTree | -- assert-plus@1.0.0
22 silly idealTree +-- date-now@0.1.4
22 silly idealTree +-- dateformat@1.0.12
22 silly idealTree +-- debug@0.7.4
22 silly idealTree +-- decamelize@1.2.0
22 silly idealTree +-- deep-equal@1.0.1
22 silly idealTree +-- defined@1.0.0
22 silly idealTree +-- defs@1.1.1
22 silly idealTree | +-- camelcase@1.2.1
22 silly idealTree | +-- esprima-fb@15001.1001.0-dev-harmony-fb
22 silly idealTree | +-- window-size@0.1.4
22 silly idealTree | -- yargs@3.27.0 22 silly idealTree +-- delayed-stream@1.0.0 22 silly idealTree +-- depd@1.1.0 22 silly idealTree +-- detect-indent@3.0.1 22 silly idealTree | -- repeating@1.1.3
22 silly idealTree +-- detective@4.3.2
22 silly idealTree +-- dom-serializer@0.1.0
22 silly idealTree | +-- domelementtype@1.1.3
22 silly idealTree | -- entities@1.1.1 22 silly idealTree +-- domelementtype@1.3.0 22 silly idealTree +-- domhandler@2.3.0 22 silly idealTree +-- domutils@1.5.1 22 silly idealTree +-- ecc-jsbn@0.1.1 22 silly idealTree +-- ee-first@1.1.1 22 silly idealTree +-- end-of-stream@1.1.0 22 silly idealTree | -- once@1.3.3
22 silly idealTree +-- entities@1.0.0
22 silly idealTree +-- error-ex@1.3.0
22 silly idealTree +-- es5-ext@0.10.12
22 silly idealTree +-- es6-iterator@2.0.0
22 silly idealTree +-- es6-map@0.1.4
22 silly idealTree +-- es6-promise@4.0.5
22 silly idealTree +-- es6-set@0.1.4
22 silly idealTree +-- es6-symbol@3.1.0
22 silly idealTree +-- es6-weak-map@2.0.1
22 silly idealTree +-- escape-string-regexp@1.0.5
22 silly idealTree +-- escope@3.6.0
22 silly idealTree +-- esprima@2.7.3
22 silly idealTree +-- esrecurse@4.1.0
22 silly idealTree | -- estraverse@4.1.1 22 silly idealTree +-- estraverse@4.2.0 22 silly idealTree +-- esutils@2.0.2 22 silly idealTree +-- event-emitter@0.3.4 22 silly idealTree +-- eventemitter2@0.4.14 22 silly idealTree +-- exit@0.1.2 22 silly idealTree +-- extend@3.0.0 22 silly idealTree +-- extract-zip@1.5.0 22 silly idealTree +-- extsprintf@1.0.2 22 silly idealTree +-- eyes@0.1.8 22 silly idealTree +-- faye-websocket@0.10.0 22 silly idealTree +-- fd-slicer@1.0.1 22 silly idealTree +-- figures@1.7.0 22 silly idealTree +-- file-sync-cmp@0.1.1 22 silly idealTree +-- find-up@1.1.2 22 silly idealTree +-- findup-sync@0.3.0 22 silly idealTree | -- glob@5.0.15
22 silly idealTree +-- forever-agent@0.6.1
22 silly idealTree +-- form-data@2.1.2
22 silly idealTree +-- fs-extra@1.0.0
22 silly idealTree +-- fs-readdir-recursive@0.1.2
22 silly idealTree +-- fs.realpath@1.0.0
22 silly idealTree +-- gaze@1.1.2
22 silly idealTree +-- generate-function@2.0.0
22 silly idealTree +-- generate-object-property@1.2.0
22 silly idealTree +-- get-stdin@4.0.1
22 silly idealTree +-- getobject@0.1.0
22 silly idealTree +-- getpass@0.1.6
22 silly idealTree | -- assert-plus@1.0.0 22 silly idealTree +-- glob@7.0.6 22 silly idealTree +-- globals@6.4.1 22 silly idealTree +-- globule@1.1.0 22 silly idealTree | +-- glob@7.1.1 22 silly idealTree | -- lodash@4.16.6
22 silly idealTree +-- graceful-fs@4.1.11
22 silly idealTree +-- graceful-readlink@1.0.1
22 silly idealTree +-- grunt-contrib-compress@1.2.0
22 silly idealTree | -- lodash@4.17.4 22 silly idealTree +-- grunt-contrib-concat@1.0.1 22 silly idealTree +-- grunt-contrib-copy@1.0.0 22 silly idealTree +-- grunt-contrib-jshint@1.0.0 22 silly idealTree +-- grunt-contrib-qunit@1.2.0 22 silly idealTree +-- grunt-contrib-uglify@1.0.1 22 silly idealTree | -- lodash@4.17.4
22 silly idealTree +-- grunt-contrib-watch@1.0.0
22 silly idealTree +-- grunt-jscs@2.8.0
22 silly idealTree | -- lodash@4.6.1 22 silly idealTree +-- grunt-known-options@1.1.0 22 silly idealTree +-- grunt-legacy-log-utils@1.0.0 22 silly idealTree | -- lodash@4.3.0
22 silly idealTree +-- grunt-legacy-log@1.0.0
22 silly idealTree +-- grunt-legacy-util@1.0.0
22 silly idealTree | -- lodash@4.3.0 22 silly idealTree +-- grunt-lib-phantomjs@1.1.0 22 silly idealTree | -- rimraf@2.5.4
22 silly idealTree +-- grunt-text-replace@0.4.0
22 silly idealTree +-- grunt@1.0.1
22 silly idealTree | -- grunt-cli@1.2.0 22 silly idealTree +-- gzip-size@1.0.0 22 silly idealTree +-- har-validator@2.0.6 22 silly idealTree +-- has-ansi@2.0.0 22 silly idealTree +-- has-color@0.1.7 22 silly idealTree +-- hasha@2.2.0 22 silly idealTree +-- hawk@3.1.3 22 silly idealTree +-- hoek@2.16.3 22 silly idealTree +-- home-or-tmp@1.0.0 22 silly idealTree +-- hooker@0.2.3 22 silly idealTree +-- hosted-git-info@2.1.5 22 silly idealTree +-- htmlparser2@3.8.3 22 silly idealTree | -- readable-stream@1.1.14
22 silly idealTree +-- http-errors@1.3.1
22 silly idealTree +-- http-signature@1.1.1
22 silly idealTree +-- i@0.3.5
22 silly idealTree +-- iconv-lite@0.4.15
22 silly idealTree +-- indent-string@2.1.0
22 silly idealTree +-- inflight@1.0.6
22 silly idealTree +-- inherit@2.2.6
22 silly idealTree +-- inherits@2.0.3
22 silly idealTree +-- invert-kv@1.0.0
22 silly idealTree +-- is-arrayish@0.2.1
22 silly idealTree +-- is-buffer@1.1.4
22 silly idealTree +-- is-builtin-module@1.0.0
22 silly idealTree +-- is-finite@1.0.2
22 silly idealTree +-- is-integer@1.0.6
22 silly idealTree +-- is-my-json-valid@2.15.0
22 silly idealTree +-- is-property@1.0.2
22 silly idealTree +-- is-stream@1.1.0
22 silly idealTree +-- is-typedarray@1.0.0
22 silly idealTree +-- is-utf8@0.2.1
22 silly idealTree +-- isarray@0.0.1
22 silly idealTree +-- isexe@1.1.2
22 silly idealTree +-- isstream@0.1.2
22 silly idealTree +-- jodid25519@1.0.2
22 silly idealTree +-- jquery@3.1.1
22 silly idealTree +-- js-tokens@1.0.1
22 silly idealTree +-- js-yaml@3.5.5
22 silly idealTree +-- jsbn@0.1.0
22 silly idealTree +-- jscs-jsdoc@1.3.2
22 silly idealTree +-- jscs-preset-wikimedia@1.0.0
22 silly idealTree +-- jscs@2.11.0
22 silly idealTree | +-- glob@5.0.15
22 silly idealTree | -- js-yaml@3.4.6 22 silly idealTree +-- jsdoctypeparser@1.2.0 22 silly idealTree +-- jsesc@0.5.0 22 silly idealTree +-- jshint@2.9.4 22 silly idealTree | -- lodash@3.7.0
22 silly idealTree +-- json-schema@0.2.3
22 silly idealTree +-- json-stringify-safe@5.0.1
22 silly idealTree +-- json5@0.4.0
22 silly idealTree +-- jsonfile@2.4.0
22 silly idealTree +-- jsonlint@1.6.2
22 silly idealTree +-- jsonpointer@4.0.1
22 silly idealTree +-- jsprim@1.3.1
22 silly idealTree +-- JSV@4.0.2
22 silly idealTree +-- kew@0.7.0
22 silly idealTree +-- kind-of@3.1.0
22 silly idealTree +-- klaw@1.3.1
22 silly idealTree +-- lazy-cache@1.0.4
22 silly idealTree +-- lazystream@0.1.0
22 silly idealTree | -- readable-stream@1.0.34 22 silly idealTree +-- lcid@1.0.0 22 silly idealTree +-- leven@1.0.2 22 silly idealTree +-- livereload-js@2.2.2 22 silly idealTree +-- load-json-file@1.1.0 22 silly idealTree +-- lodash._baseassign@3.2.0 22 silly idealTree +-- lodash._basecopy@3.0.1 22 silly idealTree +-- lodash._bindcallback@3.0.1 22 silly idealTree +-- lodash._createassigner@3.1.1 22 silly idealTree +-- lodash._getnative@3.9.1 22 silly idealTree +-- lodash._isiterateecall@3.0.9 22 silly idealTree +-- lodash.assign@3.2.0 22 silly idealTree +-- lodash.isarguments@3.1.0 22 silly idealTree +-- lodash.isarray@3.0.4 22 silly idealTree +-- lodash.keys@3.1.2 22 silly idealTree +-- lodash.restparam@3.6.1 22 silly idealTree +-- lodash@3.10.1 22 silly idealTree +-- longest@1.0.1 22 silly idealTree +-- loud-rejection@1.6.0 22 silly idealTree +-- map-obj@1.0.1 22 silly idealTree +-- maxmin@1.1.0 22 silly idealTree | -- pretty-bytes@1.0.4
22 silly idealTree +-- media-typer@0.3.0
22 silly idealTree +-- meow@3.7.0
22 silly idealTree +-- mime-db@1.26.0
22 silly idealTree +-- mime-types@2.1.14
22 silly idealTree +-- minimatch@3.0.3
22 silly idealTree +-- minimist@1.2.0
22 silly idealTree +-- mkdirp@0.5.0
22 silly idealTree | -- minimist@0.0.8 22 silly idealTree +-- mout@0.12.0 22 silly idealTree +-- ms@0.7.1 22 silly idealTree +-- mute-stream@0.0.7 22 silly idealTree +-- natural-compare@1.2.2 22 silly idealTree +-- ncp@0.4.2 22 silly idealTree +-- node-int64@0.4.0 22 silly idealTree +-- nomnom@1.8.1 22 silly idealTree | +-- ansi-styles@1.0.0 22 silly idealTree | +-- chalk@0.4.0 22 silly idealTree | -- strip-ansi@0.1.1
22 silly idealTree +-- nopt@3.0.6
22 silly idealTree +-- normalize-package-data@2.3.5
22 silly idealTree +-- normalize-path@2.0.1
22 silly idealTree +-- number-is-nan@1.0.1
22 silly idealTree +-- oauth-sign@0.8.2
22 silly idealTree +-- object-assign@4.1.1
22 silly idealTree +-- on-finished@2.3.0
22 silly idealTree +-- once@1.4.0
22 silly idealTree +-- os-locale@1.4.0
22 silly idealTree +-- os-tmpdir@1.0.2
22 silly idealTree +-- output-file-sync@1.1.2
22 silly idealTree | +-- minimist@0.0.8
22 silly idealTree | -- mkdirp@0.5.1 22 silly idealTree +-- package@1.0.1 22 silly idealTree +-- pako@0.2.9 22 silly idealTree +-- parse-json@2.2.0 22 silly idealTree +-- parseurl@1.3.1 22 silly idealTree +-- path-exists@2.1.0 22 silly idealTree +-- path-is-absolute@1.0.1 22 silly idealTree +-- path-type@1.1.0 22 silly idealTree +-- pathval@0.1.1 22 silly idealTree +-- pend@1.2.0 22 silly idealTree +-- phantomjs-prebuilt@2.1.14 22 silly idealTree +-- pify@2.3.0 22 silly idealTree +-- pinkie-promise@2.0.1 22 silly idealTree +-- pinkie@2.0.4 22 silly idealTree +-- pkginfo@0.4.0 22 silly idealTree +-- pretty-bytes@3.0.1 22 silly idealTree +-- private@0.1.6 22 silly idealTree +-- process-nextick-args@1.0.7 22 silly idealTree +-- progress@1.1.8 22 silly idealTree +-- prompt@0.2.14 22 silly idealTree +-- punycode@1.4.1 22 silly idealTree +-- q@1.4.1 22 silly idealTree +-- qs@6.3.0 22 silly idealTree +-- qunitjs@2.0.0 22 silly idealTree +-- raw-body@2.1.7 22 silly idealTree | +-- bytes@2.4.0 22 silly idealTree | -- iconv-lite@0.4.13
22 silly idealTree +-- read-pkg-up@1.0.1
22 silly idealTree +-- read-pkg@1.1.0
22 silly idealTree +-- read@1.0.7
22 silly idealTree +-- readable-stream@2.0.6
22 silly idealTree | -- isarray@1.0.0 22 silly idealTree +-- recast@0.10.33 22 silly idealTree | +-- ast-types@0.8.12 22 silly idealTree | -- esprima-fb@15001.1001.0-dev-harmony-fb
22 silly idealTree +-- redent@1.0.0
22 silly idealTree +-- regenerate@1.3.2
22 silly idealTree +-- regenerator@0.8.40
22 silly idealTree | -- esprima-fb@15001.1001.0-dev-harmony-fb 22 silly idealTree +-- regexpu@1.3.0 22 silly idealTree +-- regjsgen@0.2.0 22 silly idealTree +-- regjsparser@0.1.5 22 silly idealTree +-- repeat-string@1.6.1 22 silly idealTree +-- repeating@2.0.1 22 silly idealTree +-- request-progress@2.0.1 22 silly idealTree +-- request@2.79.0 22 silly idealTree +-- reserved-words@0.1.1 22 silly idealTree +-- resolve@1.1.7 22 silly idealTree +-- revalidator@0.1.8 22 silly idealTree +-- right-align@0.1.3 22 silly idealTree +-- rimraf@2.2.8 22 silly idealTree +-- semver@5.3.0 22 silly idealTree +-- shebang-regex@1.0.0 22 silly idealTree +-- shelljs@0.3.0 22 silly idealTree +-- signal-exit@3.0.2 22 silly idealTree +-- simple-fmt@0.1.0 22 silly idealTree +-- simple-is@0.2.0 22 silly idealTree +-- slash@1.0.0 22 silly idealTree +-- sntp@1.0.9 22 silly idealTree +-- source-map-support@0.2.10 22 silly idealTree | -- source-map@0.1.32
22 silly idealTree +-- source-map@0.5.6
22 silly idealTree +-- spdx-correct@1.0.2
22 silly idealTree +-- spdx-expression-parse@1.0.4
22 silly idealTree +-- spdx-license-ids@1.2.2
22 silly idealTree +-- sprintf-js@1.0.3
22 silly idealTree +-- sshpk@1.10.2
22 silly idealTree | -- assert-plus@1.0.0 22 silly idealTree +-- stable@0.1.5 22 silly idealTree +-- stack-trace@0.0.9 22 silly idealTree +-- statuses@1.3.1 22 silly idealTree +-- stream-buffers@2.2.0 22 silly idealTree +-- string_decoder@0.10.31 22 silly idealTree +-- stringmap@0.2.2 22 silly idealTree +-- stringset@0.2.1 22 silly idealTree +-- stringstream@0.0.5 22 silly idealTree +-- strip-ansi@3.0.1 22 silly idealTree +-- strip-bom@2.0.0 22 silly idealTree +-- strip-indent@1.0.1 22 silly idealTree +-- strip-json-comments@1.0.4 22 silly idealTree +-- supports-color@2.0.0 22 silly idealTree +-- tar-stream@1.3.2 22 silly idealTree +-- temporary@0.0.8 22 silly idealTree +-- throttleit@1.0.0 22 silly idealTree +-- through@2.3.8 22 silly idealTree +-- tiny-lr@0.2.1 22 silly idealTree | +-- debug@2.2.0 22 silly idealTree | -- qs@5.1.0
22 silly idealTree +-- to-double-quotes@2.0.0
22 silly idealTree +-- to-fast-properties@1.0.2
22 silly idealTree +-- to-single-quotes@2.0.1
22 silly idealTree +-- tough-cookie@2.3.2
22 silly idealTree +-- trim-newlines@1.0.0
22 silly idealTree +-- trim-right@1.0.1
22 silly idealTree +-- try-resolve@1.0.1
22 silly idealTree +-- tryor@0.1.2
22 silly idealTree +-- tunnel-agent@0.4.3
22 silly idealTree +-- tweetnacl@0.14.5
22 silly idealTree +-- type-is@1.6.14
22 silly idealTree +-- typedarray@0.0.6
22 silly idealTree +-- uglify-js@2.6.4
22 silly idealTree | -- async@0.2.10 22 silly idealTree +-- uglify-to-browserify@1.0.2 22 silly idealTree +-- underscore.string@3.2.3 22 silly idealTree +-- underscore@1.6.0 22 silly idealTree +-- unpipe@1.0.0 22 silly idealTree +-- uri-path@1.0.0 22 silly idealTree +-- user-home@1.1.1 22 silly idealTree +-- util-deprecate@1.0.2 22 silly idealTree +-- utile@0.2.1 22 silly idealTree | -- async@0.2.10
22 silly idealTree +-- uuid@3.0.1
22 silly idealTree +-- validate-npm-package-license@3.0.1
22 silly idealTree +-- verror@1.3.6
22 silly idealTree +-- vow-fs@0.3.6
22 silly idealTree | -- uuid@2.0.3 22 silly idealTree +-- vow-queue@0.4.2 22 silly idealTree +-- vow@0.4.13 22 silly idealTree +-- websocket-driver@0.6.5 22 silly idealTree +-- websocket-extensions@0.1.1 22 silly idealTree +-- which@1.2.12 22 silly idealTree +-- window-size@0.1.0 22 silly idealTree +-- winston@0.8.3 22 silly idealTree | +-- async@0.2.10 22 silly idealTree | +-- colors@0.6.2 22 silly idealTree | -- pkginfo@0.3.1
22 silly idealTree +-- wordwrap@0.0.2
22 silly idealTree +-- wrappy@1.0.2
22 silly idealTree +-- xmlbuilder@3.1.0
22 silly idealTree +-- xtend@4.0.1
22 silly idealTree +-- y18n@3.2.1
22 silly idealTree +-- yargs@3.10.0
22 silly idealTree | -- camelcase@1.2.1 22 silly idealTree +-- yauzl@2.4.1 22 silly idealTree -- zip-stream@0.8.0
23 silly generateActionsToTake Starting
24 silly install generateActionsToTake
25 silly generateActionsToTake Finishing
26 silly diffTrees action count 0
27 silly decomposeActions action count 0
28 silly runTopLevelLifecycles Starting
29 silly install runPreinstallTopLevelLifecycles
30 silly preinstall jquery-validation@1.16.1-pre F:\jquery-validation-master\jquery-validation-30fbe731
31 info lifecycle jquery-validation@1.16.1-pre~preinstall: jquery-validation@1.16.1-pre
32 silly lifecycle jquery-validation@1.16.1-pre~preinstall: no script for preinstall, continuing
33 silly executeActions Starting
34 silly install executeActions
35 silly doSerial global-install 0
36 silly doParallel fetch 0
37 verbose correctMkdir C:\Users\Administrator\AppData\Roaming\npm-cache_locks correctMkdir not in flight; initializing
38 verbose lock using C:\Users\Administrator\AppData\Roaming\npm-cache_locks\staging-83d6b1df005558ea.lock for F:\jquery-validation-master\node_modules.staging
39 silly doParallel extract 0
40 silly doParallel preinstall 0
41 silly doReverseSerial remove 0
42 silly doSerial move 0
43 silly doSerial finalize 0
44 silly doSerial build 0
45 silly doSerial global-link 0
46 silly doParallel update-linked 0
47 silly doSerial install 0
48 silly doSerial postinstall 0
49 verbose unlock done using C:\Users\Administrator\AppData\Roaming\npm-cache_locks\staging-83d6b1df005558ea.lock for F:\jquery-validation-master\node_modules.staging
50 silly executeActions Finishing
51 silly rollbackFailedOptional Starting
52 silly rollbackFailedOptional Finishing
53 silly install runPostinstallTopLevelLifecycles
54 silly build jquery-validation@1.16.1-pre
55 info linkStuff jquery-validation@1.16.1-pre
56 silly linkStuff jquery-validation@1.16.1-pre has F:\ as its parent node_modules
57 verbose linkBins jquery-validation@1.16.1-pre
58 verbose linkMans jquery-validation@1.16.1-pre
59 silly install jquery-validation@1.16.1-pre F:\jquery-validation-master\jquery-validation-30fbe731
60 info lifecycle jquery-validation@1.16.1-pre~install: jquery-validation@1.16.1-pre
61 silly lifecycle jquery-validation@1.16.1-pre~install: no script for install, continuing
62 silly postinstall jquery-validation@1.16.1-pre F:\jquery-validation-master\jquery-validation-30fbe731
63 info lifecycle jquery-validation@1.16.1-pre~postinstall: jquery-validation@1.16.1-pre
64 silly lifecycle jquery-validation@1.16.1-pre~postinstall: no script for postinstall, continuing
65 silly prepublish jquery-validation@1.16.1-pre F:\jquery-validation-master\jquery-validation-30fbe731
66 info lifecycle jquery-validation@1.16.1-pre~prepublish: jquery-validation@1.16.1-pre
67 verbose lifecycle jquery-validation@1.16.1-pre~prepublish: unsafe-perm in lifecycle true
68 verbose lifecycle jquery-validation@1.16.1-pre~prepublish: PATH: D:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;F:\jquery-validation-master\node_modules.bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;D:\Program Files\Java\jdk1.8.0_112\bin;D:\Program Files\apache-maven-3.3.9\bin;D:\Program Files\nodejs;C:\Users\Administrator\AppData\Roaming\npm
69 verbose lifecycle jquery-validation@1.16.1-pre~prepublish: CWD: F:\jquery-validation-master
70 silly lifecycle jquery-validation@1.16.1-pre~prepublish: Args: [ '/d /s /c', 'grunt' ]
71 silly lifecycle jquery-validation@1.16.1-pre~prepublish: Returned: code: 3  signal: null
72 info lifecycle jquery-validation@1.16.1-pre~prepublish: Failed to exec prepublish script
73 verbose stack Error: jquery-validation@1.16.1-pre prepublish: grunt
73 verbose stack Exit status 3
73 verbose stack     at EventEmitter. (D:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
73 verbose stack     at emitTwo (events.js:106:13)
73 verbose stack     at EventEmitter.emit (events.js:191:7)
73 verbose stack     at ChildProcess. (D:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
73 verbose stack     at emitTwo (events.js:106:13)
73 verbose stack     at ChildProcess.emit (events.js:191:7)
73 verbose stack     at maybeClose (internal/child_process.js:877:16)
73 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
74 verbose pkgid jquery-validation@1.16.1-pre
75 verbose cwd F:\jquery-validation-master
76 error Windows_NT 6.1.7601
77 error argv "D:\Program Files\nodejs\node.exe" "D:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
78 error node v6.9.4
79 error npm  v3.10.10
80 error code ELIFECYCLE
81 error jquery-validation@1.16.1-pre prepublish: grunt
81 error Exit status 3
82 error Failed at the jquery-validation@1.16.1-pre prepublish script 'grunt'.
82 error Make sure you have the latest version of node.js and npm installed.
82 error If you do, this is most likely a problem with the jquery-validation package,
82 error not with npm itself.
82 error Tell the author that this fails on your system:
82 error     grunt
82 error You can get information on how to open an issue for this project with:
82 error     npm bugs jquery-validation
82 error Or if that isn't available, you can get their info via:
82 error     npm owner ls jquery-validation
82 error There is likely additional logging output above.
83 verbose exit [ 1, true ]

No idea here.

repo: jzaefferer/jquery-validation


text:
merge from template-arlac77-github

.github/workflows/ci.yml

chore: add actions/checkout@v4.1.2 (jobs.test-node.steps.uses)
chore: add actions/checkout@v4.1.2 (jobs.test-browser.steps.uses)
chore: add actions/checkout@v4.1.2 (jobs.release.steps.uses)

.github/workflows/codeql_analysis.yml

chore: add actions/checkout@v4.1.2 (jobs.analyze.steps.uses)

.github/workflows/update_package_lock.yml

chore: add actions/checkout@v4.1.2 (jobs.update_package_lock.steps.uses)

.github/workflows/update_readme_api.yml

chore: add actions/checkout@v4.1.2 (jobs.update_readme_api.steps.uses)

Pull Request Test Coverage Report for Build 8249959625
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 8246619941:
0.0%

Covered Lines:
95

Relevant Lines:
95

💛  - Coveralls


text:
Change indentation options for flattening Yaml aliases

before

after

LGTM!


text:
Invalid rpath with macos shared libs

it doesn't find cargs.dylib maybe need to add search path of the @executable_path

Sorry it works well now after cleaning the build folder and rebuild.


text:
implement --node-annotation

Is your feature request related to a problem? Please describe.
TLDR: k3s has --node-label=k=v already, it would be nice to have --node-annotation=k=v also.
My use case is actually still in the Rancher ecosystem; I'm setting up Longhorn and I'd like the nodes to be able to specify which disks they have. I need to add a label of
node.longhorn.io/create-default-disk: 'config'

And an annotation with a value of
node.longhorn.io/default-disks-config: '[{"path":"/mnt/HDD1","allowScheduling":true},{"path":"/mnt/HDD2","allowScheduling":true}]'

I can do the label with --node-label=node.longhorn.io/create-default-disk=config but there's no --node-annotation.
Describe the solution you'd like
--node-annotation=key=value

Describe alternatives you've considered
Presently I'm applying the annotations out-of-band in our provisioning process but it would be great to not need to do that.

This has been requested and denied upstream: https://github.com/kubernetes/kubernetes/issues/60832

Fair enough.

authors: brandond iameli


text:
apiserver egress proxy attempts to use tunnel for connections to hostnetwork pods in agent mode

From @paulsd in https://github.com/k3s-io/k3s/pull/6829

With egress-selector-mode: agent (the default), and egress.X.io/cluster: true node labels (also a default), if any Pods are running with hostNetwork: true (and therefore use the Node IP), then the API Server will attempt to use agent tunnels to communicate with those Pods, but tunnel authorization will fail, resulting in connection failures.

Validated on master branch with commit 21560155
Environment Details

Infrastructure

[ ] Cloud
[ ] Hosted

Node(s) CPU architecture, OS, and Version:

Linux ip-172-31-45-8 5.15.0-1026-aws #30-Ubuntu SMP Wed Nov 23 14:15:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
PRETTY_NAME="Ubuntu 22.04.1 LTS"

Cluster Configuration:

1 server

Config.yaml:

# config1.yaml - default
write-kubeconfig-mode: 644
token: summer
cluster-init: true

# config2.yaml - disabled
write-kubeconfig-mode: 644
token: summer
cluster-init: true
egress-selector-mode: disabled

# config3.yaml - cluster
write-kubeconfig-mode: 644
token: summer
cluster-init: true
egress-selector-mode: cluster

# config4.yaml - pod
write-kubeconfig-mode: 644
token: summer
cluster-init: true
egress-selector-mode: pod

Additional files

hostport.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-hostport-deployment
spec:
  selector:
    matchLabels:
      app: test-hostport-app
  replicas: 6
  template:
    metadata:
      labels:
        app: test-hostport-app
    spec:
      containers:
      - name: test-hostport
        image: ranchertest/mytestcontainer:unprivileged
        ports:
        - containerPort: 8080
          hostPort: 8080

Testing Steps

Copy config.yaml

$ sudo mkdir -p /etc/rancher/k3s && sudo cp config.yaml /etc/rancher/k3s

Install k3s
Check node label: kubectl get nodes -o yaml | grep -i label -A 15

Validation Results:

k3s version used for validation:

k3s version v1.26.1+k3s-21560155 (21560155)
go version go1.19.5

Observed NO label with egress.k3s.io/cluster on default and disabled mode

$ kubectl get nodes -o yaml | grep -i label -A 15
    labels:
      beta.kubernetes.io/arch: amd64
      beta.kubernetes.io/instance-type: k3s
      beta.kubernetes.io/os: linux
      kubernetes.io/arch: amd64
      kubernetes.io/hostname: ip-172-31-45-8
      kubernetes.io/os: linux
      node-role.kubernetes.io/control-plane: "true"
      node-role.kubernetes.io/etcd: "true"
      node-role.kubernetes.io/master: "true"
      node.kubernetes.io/instance-type: k3s
    name: ip-172-31-45-8
    resourceVersion: "714"
    uid: ce995590-d5d7-4dd0-9a8c-f43350cd65a4
  spec:
    podCIDR: 10.42.0.0/24

Observed label egress.k3s.io/cluster: "true" with cluster and pod mode

$ kubectl get nodes -o yaml | grep -i label -A 15
    labels:
      beta.kubernetes.io/arch: amd64
      beta.kubernetes.io/instance-type: k3s
      beta.kubernetes.io/os: linux
      egress.k3s.io/cluster: "true"
      kubernetes.io/arch: amd64
      kubernetes.io/hostname: ip-172-31-45-8
      kubernetes.io/os: linux
      node-role.kubernetes.io/control-plane: "true"
      node-role.kubernetes.io/etcd: "true"
      node-role.kubernetes.io/master: "true"
      node.kubernetes.io/instance-type: k3s
    name: ip-172-31-45-8
    resourceVersion: "1342"
    uid: bd6604b9-a78c-413e-a7db-6a1e75688fea
  spec:

Deployed hostport.yaml and validated connectivity

$ curl <node-ip>:8080/name.html
nginx-hostport-deployment-c5b858567-56qjl

authors: brandond mdrahman-suse


text:
Updating release docs

Just filling out the release docs a bit.
Signed-off-by: matttrach matttrach@gmail.com

so I squashed all of my updates into a single commit, hopefully this makes it easier to review


text:
Add Stranger Things

Checklist for submitting a pull request to Movies For Hackers:

[X] I have carefully read and comply with the Contributing Guidelines of this repo.
[X] I have searched the PRs of this repo and believe that this is not a duplicate.

Title: Stranger Things

Link: http://www.imdb.com/title/tt4574334/

Genre: Drama/Fantasy/Horror

Rating: 8.9/10

Description: When a young boy disappears, his mother, a police chief, and his friends must confront terrifying forces in order to get him back.

I like stranger things but other than being really 80s, I don't see the connection. I say no.

It's a family show about ghosts from a hole in the wall. It has nothing to do with hacking or tech even remotely.

authors: j-roc jwithington snshn


text:
operator [R] flink-kubernetes-operator (1.0.1 1.2.0)

Signed-off-by: James Busche jbusche@us.ibm.com
Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

authors: framework-automation jbusche


text:
operator susql-operator (0.0.3)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

authors: framework-automation trent-s


text:
Race condition for multiple concurrent backups

Description
When recovering from #859 multiple backup pods are started simultaneously. This itself is not a problem. However, when finishing the backup an error is thrown.
Additional Context
I believe this is cosmetic as the restic repository appears to be intact. As such this should be safe to ignore?
Logs
2023-05-25T06:54:40Z ERROR k8up.restic.restic cannot sync snapshots to the cluster {"error": "snapshots.k8up.io \"c0ba34a1\" already exists"}
github.com/k8up-io/k8up/v2/restic/cli.(*Restic).sendSnapshotList
 /home/runner/work/k8up/k8up/restic/cli/backup.go:118
github.com/k8up-io/k8up/v2/restic/cli.(*Restic).Backup
 /home/runner/work/k8up/k8up/restic/cli/backup.go:46
github.com/k8up-io/k8up/v2/cmd/restic.doBackup
 /home/runner/work/k8up/k8up/cmd/restic/main.go:234
github.com/k8up-io/k8up/v2/cmd/restic.run
 /home/runner/work/k8up/k8up/cmd/restic/main.go:129
github.com/k8up-io/k8up/v2/cmd/restic.resticMain
 /home/runner/work/k8up/k8up/cmd/restic/main.go:113
github.com/urfave/cli/v2.(*Command).Run
 /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/command.go:271
github.com/urfave/cli/v2.(*Command).Run
 /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/command.go:264
github.com/urfave/cli/v2.(*App).RunContext
 /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/app.go:333
github.com/urfave/cli/v2.(*App).Run
 /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.23.7/app.go:310
main.main
 /home/runner/work/k8up/k8up/cmd/k8up/main.go:30
runtime.main
 /opt/hostedtoolcache/go/1.19.9/x64/src/runtime/proc.go:250

Expected Behavior
No stacktrace is thrown.
Steps To Reproduce

Have downtime for a schedule
Recover from the downtime
Observer that multiple backup jobs&pods are started
See the error in all pods that finish after the first one.

Version of K8up
2,7,1/4.2.2
Version of Kubernetes
v1.26.4+k3s1
Distribution of Kubernetes
k3s

Yeah this seems to be a race condition if multiple backups want to write the same snapshot CR on the cluster. The repository is safe though, this is a cosmetic issue.
But just to be sure if it really is cosmetic: can you do a kubectl get snapshots | grep c0ba34a1  in that namespace to see if it's really there?

@Kidswiss I can confirm that the snapshot is present. A such this is a cosmetic issue.

Great! So we can just discard logging those already exists errors.

Personally, I would log a warning but not show a stacktrace like done at the moment. It is indeed an event that should be visible IMHO.

Thus aldo happen during restic init for new backups. Two keys are created. If I init the repository separately, it works.

authors: Kidswiss SchoolGuy mzehrer


text:
Long lines are wrapped hard when a draft is opened for editing

Steps to reproduce:

Create a new draft and enter a long line (150 characters or so)
Save the draft and verify (for example with thunderbird) that the line is still one line, without any line-break
Open the draft again for editing in k9mail, append another word to that line and save the draft.
The line will have (unwanted) line-breaks now

And after a few edits+save you will have a draft with several lines, although you never entered any line-break. This is quite a mess and annoying to correct.
I also noticed, that some lines were indented by one blank after editing a draft with thunderbird. Not sure yet, how to cleanly reproduce it. Looked to me like \n\r maybe becomes \n or something like this. What contradicts this thesis is that I even saw the first line being prepended by a blank.

Duplicate of #5702
The fix is included in K-9 Mail 5.904.


text:
domain level filtering possible issue

when adding the domains does it do filtering such as *.bamgrid.com or do you have to put analytics.clients.bamgrid.com in the rules file?  Great script btw. Love the flexibility for my Merlin powered Asus router.?
Sorry not a question. Hopefully you will give an answer and I am not bothering you too much.

Currently, the script doesn't support wildcards.
It uses nslookup command to fetch the IPs and that command doesn't support wildcards.
I don't think there is a simple way to do it, but please do let me know if you can think of one.

repo: kabadisha/host-based-vpn-routing


text:
Parsing bug

Unexpected completion year mismatch for string "1-я треть-конец XIX в., 1879 г.". Local parser: undefined, Geosemantica 1879. This is a bug, please report it.
Unexpected completion year mismatch for string "конец 50-х г. XX в.". Local parser: undefined, Geosemantica 10. This is a bug, please report it.
Unexpected completion year mismatch for string "начало 30-х гг. XX в.". Local parser: undefined, Geosemantica 10. This is a bug, please report it.
Unexpected completion year mismatch for string "конец 70-х гг. XX в.". Local parser: undefined, Geosemantica 10. This is a bug, please report it.

✅ конец 50-х г. XX в.
✅ начало 30-х гг. XX в.
✅ конец 70-х гг. XX в.
🤔 1-я треть-конец XIX в. (not sure how to parse)

authors: arthur-kislitsin kachkaev


text:
How to mount Google Cloud Storage in fstab

Hi!
I can mount a bucket from Google Cloud Storage using goosfy command line this way:
goofys -f --profile google --endpoint https://storage.googleapis.com my_bucket /home/ronaldo/my_bucket
The credentials are defined in .aws/credentials
Then, when I try this line in fstab:
goofys#my_bucket /home/ronaldo/my_bucket            fuse    _netdev,--profile=google,--endpoint=https://storage.googleapis.com  0  0
I get the following error:
2021/01/12 17:42:46.174382 main.FATAL Unable to mount file system, see syslog for details
And in  Syslog:
Jan 12 17:42:45 ronaldo /usr/bin/goofys[24171]: s3.ERROR code=NoCredentialProviders msg=no valid providers in chain. Deprecated.#012#011For verbose messaging see aws.Config.CredentialsChainVerboseErrors, err=
Jan 12 17:42:45 ronaldo /usr/bin/goofys[24171]: main.ERROR Unable to access 'my_bucket': NoCredentialProviders: no valid providers in chain. Deprecated.#012#011For verbose messaging see aws.Config.CredentialsChainVerboseErrors
Jan 12 17:42:45 ronaldo /usr/bin/goofys[24171]: main.FATAL Mounting file system: Mount: initialization failed

Exporting home for root user as described in #242 worke for me. Thanks!

Exporting home for root user as described in #242 worke for me. Thanks!

repo: kahing/goofys


text:
希望区分 Int32（Integer） 和 Int64（Long）

文档的具体地址?
/
你认为有问题的文档内容
全部
你期望的结果?
希望区分 Int32（Integer） 和 Int64（Long）

此外还有别的可以优化的内容：

列出 Array 里的类型，例如 Array - Item Type: User 或者直接像 Java 一样 Array
和 Array 一样，把 Map 的 Key 和 Value 的类型也列出来
将一些特殊的 String 类型返回列出来，比如 UUID，Date

目前不说明的话，所有的int都是int32

authors: Taskeren buptlsp

repo: kaiheila/api-docs


text:
Napkon groovy

Frist try of a pull request for groovy scripts specimen and observation.

Anpassungen wurden zuvor im Master durchgeführt.

authors: kairosmike seboekphilipp


text:
create project for uniting core projects

create project for uniting core projects
project name: com.kksk.assembly

https://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html


text:
Handle classes for subwidgets in MultiWidget

Hi!
issue
In one of websites developed by me and my friends we use SplitDateTimeField with SplitDateTimeWidget. This widget is a subclass of MultiWidget. We add datepicker and timepicker classes in respective subwidgets of SplitDateTimeWidget via attrs attribute. Our problem was, that those classes hadn't been in fact added to rendered inputs.
I observed that function add_input_classes modifies attrs attribute of the widget associated with processed field. When this widget is subclassed from MultiWidget, then attrs from MultiWidget are modified and they override attrs in all of its subwidgets.
solution
This PR is an attempt to avoid classes modification on MultiWidgets by going recursively to subwidgets to perform modification there. It can handle nested MultiWidgets as well. Therefore subwidget's classes aren't overridden by MultiWidgets classes.
@kalwalkden feel free to review this PR and leave comments.
PS
I've got PEP8 autoformatting enabled, so there may also be some stylistic changes.

@kalwalkden We hope you'll share with us your thoughts of this PR.

repo: kalwalkden/django-materializecss-form


text:
Provide router release with semantic version

Hey!
It would be immensely helpful, when running the Hive Router in production, to have a semantic version for it's release artifact. Currently releases are provided either as latest or an arbitrary commit hash from the packages/libraries/router directory. This makes it hard to assess the criticality and impact of an update. It also makes it harder to switch from Apollo Router to your fork, because I don't know what commit hash corresponds to Apollo's assigned version of their Router.
I'm specifically interested into the binary release from https://apollo-router.theguild.workers.dev/<target>/<latest or commit-hash>, because I want to build the Docker image myself with a different base. But I think also for your released Docker image it would make sense.
I would expect that

I can download the binary from: https://apollo-router.theguild.workers.dev/linux/v1.51.0
Unpacking and running ./router --version would show v1.51.0 as well

Personally, I feel proxying the upstream version that Apollo has assigned would be best, but I don't know the reasoning for the commit hashes.
Thank you!

Only found the duplicate after creation, sorry: https://github.com/kamilkisiela/graphql-hive/issues/3314

repo: kamilkisiela/graphql-hive


text:
Replace loader action function

#256
Things to discuss
Apart from replacing action/loader function types with action/loader args, I've also managed to get rid of type errors that are occurring due to the different types coming from useLoaderData itself, such as <SerializeObject> or <UndefinedToOptional>
I don't know if we strictly want useLoaderData<typeof loader> thing but it causes a lot of headaches, we should whether do it as useLoaderData() as LoaderData or something like this
useLoaderData() as {
    user: Awaited<ReturnType<typeof getUser>>;
  };

what do you think?

We decided to hold off of changing loader/action types for until after the release of pano mvp.

authors: ikadgzl usirin

repo: kamp-us/monorepo


text:
Can IE11 be supported any more?

Hi , I'm using driver.js@1.3.1 in my project, I found it can not work on IE11, and this problem has been mentioned in here. But I still wanna use new ablilties in latest version, so will IE11 be supported any more?
Hope for applies, Thx.

Can you post the exact error message from the browser console? I still on v0.98 and also need IE11 support.
One solution could be to generate your own minified version with a transpiler like webpack using options to restrict to IE11 feature set.

Can you post the exact error message from the browser console? I am still using driver.js v0.98 and also need IE11 support, hesitating to make the switch to v1.x.
One solution could be to generate your own minified version by using vite options to restrict to IE11 feature set. Try changing vite.config.ts line 18 from target: "ES2019" to target: "IE11". Then rebuild the minified file by running npm run build. That could work if no polyfills are needed.

Thank you for your reply. There's no error message on the browser console, but my page became white. Your advise seems working in TS, but my project didn't use it. Babel-polyfill(ver6.26.0) doesn't make driver.js work in my project as well.

authors: Lordrian mlisowsk


text:
Uncaught error: "cd */: No such file or directory"

Reproducer:
bash-4.3$ mkdir git
bash-4.3$ cd git
bash-4.3$ git init
Initialized empty Git repository in /Users/joe/git/.git/
bash-4.3$ mkdir 1
bash-4.3$ cd 1
bash-4.3$ git standup
/usr/local/bin/git-standup: line 120: cd: */: No such file or directory
bash-4.3$

What version are you using? I get no error:
bash-3.2$ mkdir git
bash-3.2$ cd git
bash-3.2$ git init
Initialized empty Git repository in /Users/natzimmermann/git/.git/
bash-3.2$ mkdir 1
bash-3.2$ cd 1
bash-3.2$ git standup
bash-3.2$

It was 2.1.7, but it seems to have gone away. I'll let you know if I see it happen again. Thanks for looking into it.

authors: ilovezfs ntzm

repo: kamranahmedse/git-standup


text:
Update recommended org ID for CIOs that have closed

The charity register updates when a charity closes, but when that charity is a CIO, Companies House doesn't update accordingly to show that the charity has closed.
This means that FTC recommends using the GB-COH-CE****** org ID, instead of the GB-CHC. However the charity number org ID is still the primary and best identifier for that organisation, and so the method for recommending the best org IDs for CIOs should be amended.

Example of this one: https://findthatcharity.uk/orgid/GB-COH-CE017114

Although some records on companies house do seem to be marked as closed - not sure what needs to happen for the closure to be updated, potentially there's a time lag?

authors: KDuerden drkane

repo: kanedata/find-that-charity


text:
Testing rotationnet

Can I test the model by using only one view of an object?

Yes, you can obtain the scores of category and pose for one view by modifying line 373 from "output = output.view( -1, nview * nview, num_classes )" to "output = output.view( -1, nview, num_classes )". Also, please comment out line 135-137.

Thanks!

Hello . Did you test successfully on  single image inference?

authors: JAKD9 baibizhe kanezaki ozgraslan

repo: kanezaki/pytorch-rotationnet


text:
example chat breaks if someone posts the same emote twice

the second screenshot was the msg that broke the example.
testes with multiple emotes. sending a singular emote would work without problems though.

putting text in between the sprites also kill it

found out this breaks it aswell

Fixed with 12af59d.
Problem was that the static image parser made problems aka was not saving the converted spriteframes.

authors: kanimaru merlinseela

repo: kanimaru/twitcher


text:
ParallaxRecyclerAdapter implements RecyclerAdapterMethods

Wouldn't it be more appropriate if instead of having a method that asks for the implementation, to have them overriden?
I mean, instead of this:
ParallaxRecyclerAdapter<String> adapter = new ParallaxRecyclerAdapter<>(content);
adapter.implementRecyclerAdapterMethods(new ParallaxRecyclerAdapter.RecyclerAdapterMethods() {
    // implemented methods
}

This:
ParallaxRecyclerAdapter<String> adapter = new ParallaxRecyclerAdapter<>(content) {
    // implemented methods
}

You're suggesting an abstract class?

Yes

Added in last commit

There are some caveats in my opinion.
Why is ViewHolder inherited? It's not adding anything.
The class also enforces to use a list and methods of handling the items, which I think goes beyond the scope of this library, which may be to provide header and parallax effect.
Consider the PR in #31

The class doesn't enforce to set other listeners/methods than the original ones of the recycler adapter.
It's meant to be simple and easy to implement

Yeah it simple, but:

Enforces to use a list.
Handles adding items, removing items, getting and setting in a list, which I think it's ok for a project (and commonly used in adapters), but not for a library which is supposed to be generic
ViewHolder class adds nothing
It messes with item on click listener, which is out of the adapter's responsibilities
Also I think the header must be mandatory, not optional, otherwise the library doesn't make sense

Enforcing it to use a list just makes it simpler. If you need a more advanced and generic library this is not the place.
My viewholder adds as much as your two HeaderViewHolder and ItemViewHolder.
If you don't use setOnClickEvent then there is no mess.
The header being mandatory disallows people with adapters that already have an header to remove it.

repo: kanytu/android-parallax-recyclerview


text:
remoteproc link might change

Consider using the udev rule created links for consistency.

@jadonk yes I definitely agree. I see /dev/remoteproc/j7* are symlinks to /sys/class/remoteproc/remoteproc*, is there something similar for the trace buffer in /sys/kernel/debug?

authors: jadonk kaofishy


text:
Migrating to standalone canvas api gem

@edshadi @nikolasavic
This is the main portion of PR https://github.com/kaplan-advance/integrations/pull/27 - I moved a bunch of code into a standalone gem for canvas api requests.  I'd love to do some refactoring on it overall along with some pairing with someone.... It could do with some cleanup and thought.
Either way, this code once merged enables the other PR to work.

@cdimartino looks good to me, seems to be missing tests (I'd argue probably not required now), but eventually it would be nice to release this as an open source project.

Absolutely agree.  I'd love to spend a day or so architecting this properly and speccing it out with tests.  This was a first stab at pulling it out of an existing integration into a standalone gem.

authors: cdimartino edshadi

repo: kaplan-advance/canvas-api


text:
Dialog being read twice

Each dialog is being read by TTT twice, didn't happen yesterday, perhaps a small glitch that isn't consistent.

That typically happens when you have NPC dialogue checked in channel settings tab in the plugin settings.
Try turning unchecking that box and see if that helps. This is usually caused by the plugin reading dialogue posted in the chat and also reading the on screen dialogue box.

Has that always happened? It's supposed to track the last NPC text so that the chat handler can skip it.

It's been around as long as I can remember. I assume the chat handler has been catching most of them, but they must make it through sometimes.
Maybe differences of punctuations, or text continuing on a second text box.

It's been around as long as I can remember. I assume the chat handler has been catching most of them, but they must make it through sometimes.
Maybe differences of punctuations, or text continuing on a second text box.

I got a separate bug report about this in Discord saying the same thing, but it should have been fixed ever since #40 was closed. I thought this was something new 😵💫

I got a separate bug report about this in Discord saying the same thing, but it should have been fixed ever since #40 was closed. I thought this was something new 😵💫

TBH I used the addon for a few weeks without it happening, updated to the newest version, didn't change any settings, and it started doing it.  Even with 'cancel voice if new lines start' enabled it still happens, I can cancel the dialog and sometimes still get double voice.

TBH I used the addon for a few weeks without it happening, updated to the newest version, didn't change any settings, and it started doing it.  Even with 'cancel voice if new lines start' enabled it still happens, I can cancel the dialog and sometimes still get double voice.

And that option I mentioned earlier was already unselected?

I am having the same problem with some of my text, specifically green NPC dialogue in combat instances. My friend was helping me go through the settings and I found multiple instances of the NPC Dialogue option checked. If I uncheck the top one, the bottom one also unchecks. If I try to uncheck the bottom one, nothing happens. There are also multiple instances of NPC Announcement in that list. If I click on either instance of NPC Announcement, both toggle.

The duplicate options are fixed in the testing versions I think, that's just because Dalamud added them at some point and TTT combines that with its own list. That part shouldn't be causing issues since the settings are synchronized.

authors: ABlingManPlays Citrus333 johnysandels karashiiro

repo: karashiiro/TextToTalk


text:
Passing parameters in while calling feature file in runner class

Hi,
I am creating test automation framework from scratch. My requirement is I should be able to create testdata dynamically from database query and pass it into feature file. It is going to be data driven framework as I will take testdata from excel every time put it in my query parameter, run query,create test data and pass to feature file. In feature file it will be passed in SOAP API request. I tried to search in all blogs about how to pass data externally while running feature file but did not get any information. I read all stack overflow and blogs but it has all information on passing data within feature file which I am not looking into.
IMPORTANT: If you have a general question please use Stack Overflow instead where Karate has a dedicated "tag": https://stackoverflow.com/questions/tagged/karate
If you are sure you have found a bug, please make sure you follow the instructions here: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue

@hetalvasavada if you have really "read all stack overflow and blogs" then you are not going to find anything new, so maybe you should assume that Karate is not the right fit for you.
I can provide you 2 recommended links:

https://github.com/intuit/karate#data-driven-features
https://stackoverflow.com/a/58378161/143475

If the 2 links above don't give you any pointers, then please look for some other framework. and please don't ask questions here, use stack overflow

How do you parameterize the read function in karate?
For example:

def expected = read(".../testcase.json")
def expected = read(".../")

@BoakyeE please ask such questions on stack overflow: https://stackoverflow.com/questions/tagged/karate

authors: BoakyeE hetalvasavada ptrthomas

repo: karatelabs/karate


text:
Getting XML Response while passing Json Payload

Hi Team,
I am passing input payload as Json and getting Json in response from Postman, but when i tried the same with karate i.e
while passing Json as payload request the response generated is in XMl format.
Is there any this we can do to get this in Json response itself.
As a work around converted the xml to json but curious to know if i am doing anything wrong here.
@ptrthomas could you please help out here
https://stackoverflow.com/questions/tagged/karate

@nngrjg follow this process exactly as described to re-open please: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue

Thanks, but i could share the project as this is completely internal.
Any other way to get support.

@nngrjg use stack overflow. that said I'm pretty sure the solution you need is here: https://github.com/karatelabs/karate/issues/388#issuecomment-386845749

i tried using the accept header but, my issue is that i am expecting json response but getting in xml

@nngrjg I don't think anyone here can help you. all the best !

authors: nngrjg ptrthomas


text:
[Improvement] Rename "request" keyword ?

I have noticed that Karate uses the request keyword in POST and PUT requests in order to refer to the payload.
Given url 'http://localhost:8097/user/create'
And request { id: '1234' , name: 'John Smith'}
When method POST
Then status 200

The word request is not very  "natural "
Wouldn't be better to replace request by payload, body or data ?

@harmin-parra yes I've thought about it. but I think it's fine, 90% of the time, you don't worry about headers, or cookies and you care only about the body. you are the first ever to bring this up in 7 years by the way :)
the JS API introduced recently does a more "coder friendly" design F Y I: https://github.com/karatelabs/karate/wiki/Karate-JavaScript-Mocks
closing as won't fix

authors: harmin-parra ptrthomas


text:
Scattergory patch 1

patch vdom.nim with scheme for recognizing svg and mathML nodes;
set global variables for default svg and mathML namespaces

Is this intended to be a part of #256 @scattergory? Can you unify the change to one PR?

Yeah, I will make a unified PR.

Closing this one too as it has been superseded by #261

authors: geotre scattergory

repo: karaxnim/karax


text:
How to update easily?

I am not familiar with Docker. Is it sufficient to update this project by first cloning the repository with git clone and then building the Docker images with docker-compose --build?
It seems if I remove the directory first without docker-compose down then the docker can not be kill forever

I built a ready-to-use image: https://github.com/wy580477/chatgpt_telegram_bot
You can just pull my image to keep up new changes.

I don't why author doesn't offer a ready-to-use image.
I built one myself with alpine base-image and sqlite database instead of mongo:
https://github.com/wy580477/chatgpt_telegram_bot

Command docker-compose up --build first takes down running docker containers and then setups new ones

if you already have the git repo in the folder remember to also do a git pull before the docker-compose command

You can use docker-compose up --build to only build the newest image (if you have changed code) or then use docker-compose up -d to build and then run the image. If you are not familiar with docker platform, run it with setup python:3.8, mongodb. Run docker-compose down in the folder containing docker-compose.yml to down all service-container declared in this file.


text:
[Question] Can you access preprocessor errors programatically?

I'm running karma programatically through the Server API and was wondering if there was a good way catch preprocessor errors when they occur.
Right now, if a preprocessor (babel for example) fails, I'll just see a message logged from Karma, but the server will still start up.
I'd like to be able to cancel the whole process, or at least catch the error when it occurs. I tried tracing my way through the source, and couldn't exactly understand what happens when a preprocessor invokes it's callback with an error: https://github.com/karma-runner/karma/blob/master/lib/preprocessor.js#L26
Any advice?

Still curious about this one

You should be able to catch an event with the error. It is emitted here:
https://github.com/karma-runner/karma/blob/master/lib/preprocessor.js#L64

I did a little more digging today, and from my understanding, that line will emit errors due to a preprocessor failing to start up, but will not emit an error that the preprocessor itself reports. For example when a there is a syntax error in one of the files babel is trying to preprocess and that error is thrown in on this line:
https://github.com/babel/karma-babel-preprocessor/blob/master/lib/index.js#L24
If I'm reading the code well enough, when tracing this example the error would turn into a rejected promise on this line:
https://github.com/karma-runner/karma/blob/master/lib/file-list.js#L186
Falling through to the next rejection handler, which occurs back in the Server on this line:
https://github.com/karma-runner/karma/blob/master/lib/server.js#L192
However, since afterPreprocess takes no error argument, that error is effectively lost. I was thinking it would be nice if the server had the option to abort if a preprocessor error like this occurred. Perhaps, something like the following:
  var afterPreprocess = function () {
    if (config.autoWatch) {
      self._injector.invoke(watcher.watch)
    }

    webServer.listen(config.port, function () {
      self.log.info('Karma v%s server started at %s//%s:%s%s', constant.VERSION,
        config.protocol, config.hostname, config.port, config.urlRoot)

      self.emit('listening', config.port)
      if (config.browsers && config.browsers.length) {
        self._injector.invoke(launcher.launch, launcher).forEach(function (browserLauncher) {
          singleRunDoneBrowsers[browserLauncher.id] = false
        })
      }
      var noLoadErrors = self.loadErrors.length
      if (noLoadErrors > 0) {
        self.log.error('Found %d load error%s', noLoadErrors, noLoadErrors === 1 ? '' : 's')
        process.kill(process.pid, 'SIGINT')
      }
    })
  }

  /*
   * Propsal
   */
  var handlePreprocessError = function(err) {
    if (config.failOnPreprocessError) {
      throw err; // or handle more gracefully
    } else {
      afterPreprocess()
    }

  fileList.refresh().then(afterPreprocess, handlePreprocessError)

I also understand that my current use-case causing me to run into this problem is somewhat non-traditional, so I'm not sure if this would be worth implementing.
Thanks for your time!

Thank you for the digging. I like your proposal, but I would make the default to log the error as a warning and then call afterPrepocess so it is always surfaced and not swallowed like it is right now.

Is throwing the error the right move, or would you propose a more graceful tactic?

I just realised, that you could simply add it to self.loadErrors.
The current behaviour is to exit the process if any occur, so we don't actually need to make this configurable and just exit.

Oh excellent! I'll open a PR soon

@dignifiedquire - it looks like self.loadErrors is designed to capture a specific type of initialization error:
// lib/server.js
self.on('load_error', function (type, name) {
self.log.debug('Registered a load error of type %s with name %s', type, name)
self.loadErrors.push([type, name])

// lib/launcher.js
try {
  var browser = injector.createChild([locals], ['launcher:' + name]).get('launcher:' + name)
} catch (e) {
  // ...
  emitter.emit('load_error', 'launcher', name)
}

// lib/plugin.js
try {
  modules.push(require(name))
} catch (e) {
  // ...
  emitter.emit('load_error', 'plug_in', name) // load_error
}

// lib/preprocessor.js
try {
  p = injector.get('preprocessor:' + name)
} catch (e) {
  // ...
  emitter.emit('load_error', 'preprocessor', name) // load_error
}

Knowing this, it feels like a hack to use self.loadErrors for preprocess-specific errors, especially when I would ideally like to be able to access the error programmatically. I'm still a fan of either the proposal above, or creating another event-type for preprocessor-specific errors:
// lib/preprocessor.js
var createNextProcessor = function (preprocessors, file, done) {
  var emitter = injector.get('emitter'); // proposed
  return function nextPreprocessor (error, content) {
    // ...
    if (error) {
      file.content = null
      file.contentPath = null
      emitter.emit('preprocess_error', error) // proposed
      return done(error)
    }
   // ...
}

This event could be listened to anywhere, including the Server.
Thoughts?

Bump @dignifiedquire

authors: danthareja dignifiedquire

repo: karma-runner/karma