text:
Mapping Standards to specific well outside of std.toml

Hi Kale,
I have a std.toml file that currently defines standards as:
[block.12x1.H1]
standard = true

[block.1x1]
'H1,H7'.chitobiose = 50
'H2,H8'.chitobiose = 25
'H3,H9'.chitobiose = 12.5
'H4,H10'.chitobiose = 6.25
'H5,H11'.chitobiose = 3.125
'H6,H12'.chitobiose = 0

For most experiments, I can use:
[meta]
include = 'std.toml'

However, if the standards are in a different position (B1 instead of H1), is there a way to map these standards to a new position without having to edit the original std.toml file?

Good question, but unfortunately there is no way to do this at the moment.  I'm open to adding this feature, though.  The trick would be thinking of a good syntax.  Some options that come to mind:

Only specify one well, implying that A1 in the included file will be shifted to the given coordinate.  This is succinct, but maybe unclear, and gives no way to shift up or to the left (e.g. H1 to B1):
[meta]
include_at.B1 = 'std.toml'

Specify which well in the included file (e.g. H1) will be shifted to which well in the current layout (e.g. B1).  This is more explicit, but maybe unnecessarily verbose.  It also requires quoted keys, which I prefer to avoid.  Not sure I'm crazy about the arrow syntax, either:
[meta]
include_at.'H1->B1' = 'std.toml'

Allow meta.include entries to be dictionaries (or lists of dictionaries).  This is even more explicit and more verbose.  It's also more extensible, allowing for the possibility of specifying the shift in different ways (e.g. using indices instead of well names?), or adding more include options later:
[meta.include]
path = 'std.toml'
shift = 'H1 to B1'

Right now the 3rd option sounds the best to me, but I'll need to give it some time to see if I can think of anything else.  Let me know if you have any thoughts, too!

Good question, but unfortunately there is no way to do this at the moment.  I'm open to adding this feature, though.  The trick would be thinking of a good syntax.  Some options that come to mind:

Only specify one well, implying that A1 in the included file will be shifted to the given coordinate.  This is succinct, but maybe unclear, and gives no way to shift up or to the left (e.g. H1 to B1):
[meta]
include_at.B1 = 'std.toml'

Specify which well in the included file (e.g. H1) will be shifted to which well in the current layout (e.g. B1).  This is more explicit, but maybe unnecessarily verbose.  It also requires quoted keys, which I prefer to avoid.  Not sure I'm crazy about the arrow syntax, either:
[meta]
include_at.'H1->B1' = 'std.toml'

Allow meta.include entries to be dictionaries (or lists of dictionaries).  This is even more explicit and more verbose.  It's also more extensible, allowing for the possibility of specifying the shift in different ways (e.g. using indices instead of well names?), or adding more include options later:
[meta.include]
path = 'std.toml'
shift = 'H1 to B1'

Right now the 3rd option sounds the best to me, but I'll need to give it some time to see if I can think of anything else.  Let me know if you have any thoughts, too!

Hi Kale,
The 3rd option looks best to me. I think being more verbose will help ensure that someone does not accidentally shift to the wrong well.
Looking forward to this feature!
Cheers,
Robbie
Roberto Efraín Díaz
Pronouns: He, him, his
TETRAD Ph.D. Student
Fraser Lab
University of California, San Francisco
NSF GRFP Fellow
Honorary IMSD Fellow
Twitter @robbiediaz_ucsf

From: Kale Kundert @.>
Sent: Wednesday, January 27, 2021 6:44 PM
To: kalekundert/wellmap @.>
Cc: Diaz, Roberto @.>; Author @.>
Subject: Re: [kalekundert/wellmap] Mapping Standards to specific well outside of std.toml (#16)
Good question, but unfortunately there is no way to do this at the moment. I'm open to adding this feature, though. The trick would be thinking of a good syntax. Some options that come to mind:

Only specify one well, implying that A1 in the included file will be shifted to the given coordinate. This is succinct, but maybe unclear, and gives no way to shift up or to the left (e.g. H1 to B1):

[meta]
include_at.B1 = 'std.toml'

Specify which well in the included file (e.g. H1) will be shifted to which well in the current layout (e.g. B1). This is more explicit, but maybe unnecessarily verbose. It also requires quoted keys, which I prefer to avoid. Not sure I'm crazy about the arrow syntax, either:

[meta]
include_at.'H1->B1' = 'std.toml'

Allow meta.include entries to be dictionaries (or lists of dictionaries). This is even more explicit and more verbose. It's also more extensible, allowing for the possibility of specifying the shift in different ways (e.g. using indices instead of well names?), or adding more include options later:

[meta.include]
path = 'std.toml'
shift = 'H1 to B1'
Right now the 3rd option sounds the best to me, but I'll need to give it some time to see if I can think of anything else. Let me know if you have any thoughts, too!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kalekundert_wellmap_issues_16-23issuecomment-2D768757441&d=DwMCaQ&c=iORugZls2LlYyCAZRB3XLg&r=eAELcAFrRp6r1EemXaVYV9j3zZLT8F2X1m7NCuam9ik&m=jC7fV1tToAfSwPSdRpxrhW-eY4daeax_aygsNxAp-H0&s=37ItqnX2JSbp4BzGoCo1d2k7ce0w9gBKn5vnPMHQkI4&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AHWJIEHE4G5L54HTUURPH73S4DFP7ANCNFSM4WWCWQNQ&d=DwMCaQ&c=iORugZls2LlYyCAZRB3XLg&r=eAELcAFrRp6r1EemXaVYV9j3zZLT8F2X1m7NCuam9ik&m=jC7fV1tToAfSwPSdRpxrhW-eY4daeax_aygsNxAp-H0&s=2u_f71yw7Og7Z9JALTDknCGjqhxp7FNxWYQVnBesI1Y&e=.

Hi Robbie,
Sorry it's been a while.  I looked briefly into making this change, and unfortunately it's going to take a lot of work.  I still want to do it, but I probably won't get to it in the near future.

Hi Kale,
No worries. I understand how busy everything else can get. There’s no urgency on my end to implement this new feature.
Thanks for making wellmap and for maintaining it. It’s been really helpful to some of my recent work.
Cheers,
Robbie
Roberto Efraín (Robbie) Díaz
Pronouns: He, him, his
TETRAD Ph.D. Candidate, Fraser Lab
University of California, San Francisco
HHMI Gilliam Fellow
NSF GRFP Fellow
Honorary IMSD Fellow
Twitter @robbiediaz_
Sent from my iPhone
El abr. 29, 2021, a la(s) 06:00, Kale Kundert @.***> escribió:
 Hi Robbie, Sorry it's been a while. I looked briefly into making this change, and unfortunately it's going to take a lot of work. I still want to do it, but I probably won't get to it in the near future. — You are receiving this because ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Hi Robbie,
Sorry it's been a while. I looked briefly into making this change, and unfortunately it's going to take a lot of work. I still want to do it, but I probably won't get to it in the near future.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/kalekundert/wellmap/issues/16*issuecomment-829216885__;Iw!!LQC6Cpwp!7kHXujXxIVxp638qqx_owE70aImNsVAfmt1tq9EDyDiCK57mYOKv40E73aXcj2nujMNy$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AHWJIEFLPUAZ7XSKASO5PE3TLFJ47ANCNFSM4WWCWQNQ__;!!LQC6Cpwp!7kHXujXxIVxp638qqx_owE70aImNsVAfmt1tq9EDyDiCK57mYOKv40E73aXcj9XXSHDS$.

repo: kalekundert/wellmap


text:
Compatibility with Shaarli 0.10.2

Hi,
You theme is the best one I've found, do you plan to update it for the latest version of Shaarli (0.10.2)?
BR

looks like he will, but does not have enough time
https://github.com/kalvn/Shaarli-Material/issues/81

I will, definitely. But I have very little time for this for the moment, so probably not before a few weeks/months.

I actually had some time to spend on this lately. I you want to follow the progress, you can have a look at branch feature/update-010.
It is absolutely NOT YET ready for production so don't use it for now.
I already adapted most of pages. One of the last to work on is that new thumbnails sync page.

Thumbnail update page added.
Now I'll just make sure nothing is broken and I'll prepare the release.

source: gharchive/issue

authors: kalvn nicolasdanelon nothing-fr

repo: kalvn/Shaarli-Material

license: mit

license_type: permissive

license_source: bigquery


text:
Update Snapshot release configuration

This pull request updates the snapshot release configuration by adding a new snapshot configuration in the .changeset/config.json file.

Summary by CodeRabbit

New Features

Introduced a new snapshot release configuration to improve version management with prereleaseTemplate and useCalculatedVersion.

/snapshot-release

/snapshot-release

/snapshot-release

source: gharchive/pull-request

repo: kamiazya/web-csv-toolbox

license: MIT

license_source: github-api


text:
can not connect by dbeaver and datagrip.

when connect this server by datagrip or dbeaver, there is a error mean server version is not existed
so that i tried to add server version field:
// ParameterStatus for server_version
  const serverVersionParam = new GrowableOffsetBuffer();
  serverVersionParam.write("S");
  serverVersionParam.write("server_version");
  serverVersionParam.write("15.0");

  // ReadyForQuery
  const readyForQuery = new GrowableOffsetBuffer();
  readyForQuery.write("Z");
  readyForQuery.writeUint32BE(5);
  readyForQuery.write("I");

  return Buffer.concat([
    authOk.toBuffer(),
    backendKeyData.toBuffer(),
    serverVersionParam.toBuffer(),
    readyForQuery.toBuffer(),
  ]);

but it still has error,

i have no idea for this. sigh...

ParameterStatus requires uint32 on its second position to indicate length of the message - https://www.postgresql.org/docs/current/protocol-message-formats.html#PROTOCOL-MESSAGE-FORMATS-PARAMETERSTATUS so the code should say something like
// ParameterStatus
const param = "server_version15.0";
const parameterStatus = new GrowableOffsetBuffer();
parameterStatus.write("S");
parameterStatus.writeUint32BE(4 + param.length);
parameterStatus.write(param);

From my quick test this in itself doesn't solve the issue though, and I don't have much spare time to debug now (probably will in the future though).
All those params should be ignored by the frontend if missing/malformed anyway, so it's also kind of issue with DBeaver itself as well.
https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-ASYNC

Accordingly, a frontend should simply ignore ParameterStatus for parameters that it does not understand or care about.

https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-START-UP

This message informs the frontend about the current (initial) setting of backend parameters, such as client_encoding or DateStyle. The frontend can ignore this message, or record the settings for its future use; see Section 55.2.7 for more details. The frontend should not respond to this message, but should continue listening for a ReadyForQuery message.

@kamilogorek i have tried this code
function createStartupMessageReponse(): Buffer {
  // AuthenticationOk
  const authOk = new GrowableOffsetBuffer();
  authOk.write("R");
  authOk.writeUint32BE(8);
  authOk.writeUint32BE(0);

  // BackendKeyData
  const backendKeyData = new GrowableOffsetBuffer();
  backendKeyData.write("K");
  backendKeyData.writeUint32BE(12);
  backendKeyData.writeUint32BE(1);
  backendKeyData.writeUint32BE(2);

  // ParameterStatus
  const param = "server_version15.0";
  const parameterStatus = new GrowableOffsetBuffer();
  parameterStatus.write("S");
  parameterStatus.writeUint32BE(4 + param.length);
  parameterStatus.write(param);

  // ReadyForQuery
  const readyForQuery = new GrowableOffsetBuffer();
  readyForQuery.write("Z");
  readyForQuery.writeUint32BE(5);
  readyForQuery.write("I");

  return Buffer.concat([
    authOk.toBuffer(),
    backendKeyData.toBuffer(),
    parameterStatus.toBuffer(),
    readyForQuery.toBuffer(),
  ]);
}

on datagrip it still the same error.  can not establish session

Fixed in https://github.com/kamilogorek/pglite-server/releases/tag/v0.1.3
I forgot that strings in this protocol are null-terminated :)

Thanks for your work!!!

Thanks for your work!!!

Failed
  Copy Search Error Troubleshooting
DBMS: PostgreSQL (ver. pglite)  Case sensitivity: plain=lower, delimited=exact Driver: PostgreSQL JDBC Driver (ver. 42.6.0, JDBC4.2)
Ping: 9 ms  [0A000] ClientInfo property not supported.
but on datagrip it still can not connect.  anyway it's enough   Thank you~

There's a chance that datagrip requires a valid version instead of mocked value. If you want to play around locally, just swap pglite string with 15.0.0 or some other value and see if that works for you/

i have tried replace version pglite to 15.0.0 and datagrid actually can be connected. but can't display any database or schema.
showing this error
could not open directory "/usr/share/zon. Cannot open cursor: the statement was not executed or it has not returned curs
but dbeaver did works. not a big problem

and I want to know, can i get the username, password or some other params, when client connect to this server?
so that i can make some db request dispatch. for example dispatch this request to another port pglite

authors: jueinin kamilogorek

repo: kamilogorek/pglite-server


text:
Command::getMonologBridge()

https://github.com/kamilsk/TinkoffCurrencyAnalyst/commit/e2b3276387aa7416a83502d829062c537c1fd525#diff-15f897c8944546c1af467bd8fd153c45R50

mistake project https://github.com/kamilsk/CilexServiceProviders/issues/102

repo: kamilsk/Common


text:
Feature/simple functions

Unstageのファイルの影響でエラーが発生しないように修正
Go言語のコマンドの入出力先を標準出力に明示的に指定

LGTM 👍

authors: chaspy kamontia

repo: kamontia/git-fixup


text:
[BUG] We dont actually need to spin a MySQL tools pod in MySQL test

Describe the bug
In current implementation of MySQL deployment config we run the commands from that MySQL pod using that tools pod. This can be eliminated if we use -p to provide the password to MySQL installation.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Was fixed by this
https://github.com/kanisterio/kanister/commit/57811b824e076004d53a6988d6875614b62f96ca

repo: kanisterio/kanister


text:
Publishing helper modules seperately?

Have you considered publishing the jdict and jstrutils  modules as separate nimble packages?  I think they are very universal and I would like to import them in other projects.

I my opinion they are a bit too tiny to live on their own (~30 LOC in total), and justify an explicit dependency. I wouldn't mind having just a dependency on Karax for now.

I think I might move them to Nim's stdlib instead. Any objections?

Also, jsrutils misses following:
proc `&`*(s: float): cstring {.importcpp: "((#)+'')", nodecl.}

You may want to add it in the same time.

Seems like this didn't make it into stdlib. I'm going to close this for now due to inactivity. Please feel free to re-open and comment if you want to discuss further!

authors: AjBreidenbach Araq bluenote10 geotre pnuzhdin

repo: karaxnim/karax


text:
[Feature Request]: Merge Default Keymap Settings with User Overrides

It looks like when we provide custom keymaps to neoscroll in the setup function, all of the default settings are lost, whereas I would expect that all defaults would persist unless explicitly overridden.
I think it would be a nice feature if we could just provide overrides where desired and keep everything else in the default keymap settings as is.
For instance, I don't want to see smooth scrolling for these keymaps (zt, zz, zb), but I do want to see smoothed scrolling for these keymaps (<C-u>, <C-d>, <C-b>, <C-f>, <C-y>, <C-e>)
require("neoscroll").setup({
  easing_function = "quadratic",
  mappings = {
    ["zt"] = "zt",
    ["zz"] = "zz",
    ["zb"] = "zb",
  },
})

Here is what I'm currently seeing when providing a subset of overrides (all defaults are lost and I do not see smooth scrolling for the keybinds I did not explicitly override):
https://github.com/user-attachments/assets/0a0d6fd6-613f-4e50-857e-b0d646637bd4
Here is what I see when providing no overrides (defaults are persisted and I see smooth scrolling):
https://github.com/user-attachments/assets/b0683f65-af71-47bf-b59e-d513aa887eec

Have you even read the README or the docs (:help neoscroll-setup()) before posting? I put time an effort writing them and they both literally tell you how to do that.
Quoting from the README:

You can map a smaller set of default mappings:
require('neoscroll').setup({ mappings = {'<C-u>', '<C-d>', '<C-b>', '<C-f>'} })

Quoting from the docs:

Example disabling <C-y> and <C-e> default mappings:
require('neoscroll').setup({
 mappings = {'<C-u>', '<C-d>', '<C-b>', '<C-f>', 'zt', 'zz', 'zb'}
})

mappings (
type: table,
default: {'<C-u>', '<C-d>', '<C-b>', '<C-f>', '<C-y>', '<C-e>', 'zt', 'zz', 'zb'}
)
All the keys defined in this option will be mapped to their corresponding
default scrolling animation. To no map any key pass an empty table ({}).

So for your particular case just do:
require("neoscroll").setup({
  easing_function = "quadratic",
  mappings = {'<C-u>', '<C-d>', '<C-b>', '<C-f>', '<C-y>', '<C-e>'},
})

Your current config doesn't work because you are not passing a list but a table with keys and values to mappings.

Apologies - that was my mistake for not reading :help neoscroll-setup() first. I had read the README but I guess the API was just a little confusing to me. Makes sense now. Appreciate the help


text:
Error: Different Canonical Packages for, not check on vendor folder

$ govendor fetch +e
Error: Different Canonical Packages for golang.org/x/sys/unix
        github.com/nuveo/config.core/vendor/golang.org/x/sys/unix
        github.com/nuveo/prest/vendor/golang.org/x/sys/unix

github.com/kardianos/govendor/context.(*Context).Alter
        /private/tmp/govendor-20170217-92715-xn87mb/govendor-1.0.8/src/github.com/kardianos/govendor/context/modify.go:692
github.com/kardianos/govendor/run.(*runner).Modify
        /private/tmp/govendor-20170217-92715-xn87mb/govendor-1.0.8/src/github.com/kardianos/govendor/run/modify.go:152
github.com/kardianos/govendor/run.(*runner).run
        /private/tmp/govendor-20170217-92715-xn87mb/govendor-1.0.8/src/github.com/kardianos/govendor/run/run.go:83
github.com/kardianos/govendor/run.Run
        /private/tmp/govendor-20170217-92715-xn87mb/govendor-1.0.8/src/github.com/kardianos/govendor/run/run.go:41
main.main
        /private/tmp/govendor-20170217-92715-xn87mb/govendor-1.0.8/main.go:35
runtime.main
        /usr/local/Cellar/go/1.8/libexec/src/runtime/proc.go:185
runtime.goexit
        /usr/local/Cellar/go/1.8/libexec/src/runtime/asm_amd64.s:2197

I encountered a similar problem, maybe my fix can help others:
Error: Different Canonical Packages for github.com/davecgh/go-spew/spew
	github.com/davecgh/go-spew/spew
	github.com/davecgh/go-spew/spew
      ... stacktrace...
	/usr/local/Cellar/go/1.7.3/libexec/src/runtime/asm_amd64.s:2086

That file DOES NOT EXIST on my system! I've got 1.8.0 now.
Rebuilding govendor with go get -u github.com/kardianos/govendor resolved the issue.

any idea what the problem is? i have the same issue.

After "fighting" a lot with this issue I decided to change the architecture of my software (was wrong), read more here[1]
[1] https://github.com/prest/prest/issues/190

how to deal with it? it's confused me.
i use govendor update local package, it also show the same error;
local package updated.

I has removed sub paths from vendor path and installed dependencies again:
govendor sync
govendor fetch +vendor

It helped me

authors: Arnold1 avelino mnvx therealplato windrainw

repo: kardianos/govendor


text:
Allow stream as option

Add opts.stream so user can handle errors, end of stream, etc. easier.

nice

authors: joehand karissa

repo: karissa/hyperdiscovery


text:
restartOnFileChange doesn't work after run completes normally

I just upgraded to 0.13.11 and tried the restartOnFileChange option out for the first time.
An excerpt from my karma.conf.js is:
  autoWatch: true,
  singleRun: false,
  restartOnFileChange: true
}

When I kick off a test run, and then quickly edit/save a watched file;  I see that the current run is cancelled and a new run starts, as per the docs.
I can repeat this process any number of times; with the same results each time (current run is cancelled, new run starts).
However, if I let the current run continue all the way through to completion;  then make a change to a watched file, a new run will start, but it doesn't run any tests.
Example console output is below.  It shows:

the end of a successful run (Finished in 39.126 secs, 1325 tests completed)
a change detected in the file foo.js
another run triggered, but with 0 tests completed:

Finished in 39.136 secs / 1.009 secs

SUMMARY:
✔ 1325 tests completed
19 10 2015 16:42:45.754:INFO [watcher]: Changed file "foo.js".

Finished in 0.002 secs / 0 secs

SUMMARY:
✔ 0 tests completed

I have the same problem

Also got this issue. It does not seem random and reproduces every time then |restartOnFileChange| is true

gulp test-chrome-extension
(node:676) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
[07:49:33] Using gulpfile C:\Workspace\market\gulpfile.js
[07:49:33] Starting 'test-chrome-extension'...
03 07 2016 07:49:34.134:WARN [karma]: No captured browser, open http://localhost:9876/
03 07 2016 07:49:34.146:INFO [karma]: Karma v1.1.0 server started at http://localhost:9876/
03 07 2016 07:49:34.147:INFO [launcher]: Launching browser Chrome with unlimited concurrency
03 07 2016 07:49:34.174:INFO [launcher]: Starting browser Chrome
03 07 2016 07:49:35.591:INFO [Chrome 51.0.2704 (Windows 8.1 0.0.0)]: Connected on socket /#a7QsDyM3ifDa2XX5AAAA with id 25769336
Chrome 51.0.2704 (Windows 8.1 0.0.0): Executed 1 of 1 SUCCESS (0.01 secs / 0.001 secs)
03 07 2016 07:49:42.460:INFO [watcher]: Changed file "C:/Workspace/market/dist/chrome-extension/1.0.0/application/chrome/module/test-suite/tools.spec.js".
03 07 2016 07:52:29.802:INFO [watcher]: Changed file "C:/Workspace/market/dist/chrome-extension/1.0.0/application/chrome/module/test-suite/tools.spec.js".

... and no running tests

I have similar issues with this option.  Tests run the first time, but when changing a file one of two things will happen, no tests will run, or no tests will run and the browser disconnects.
It looks like, after a file change, tests are being executed before any files are served.  Here is a comparison with DEBUG logging and also logging all karma.Server events.  I've added my own headers to help delineate successive file change and re-runs.
Test
I have a minimal test:
describe('restartOnFileChange', () => {
  it('skips tests after the first run', () => {
    (true).should.equal(true)
  })
})

With restartOnFileChange: true
I have enabled DEBUG logging here.  I have also added karma.Server logs that simply log every event that karma.Server() is emitting (karma.Server: browser_start, etc):
#############################################################################
#                                                                           #
#                                 FIRST RUN                                 #
#              All is well, files are requested, then tests run.            #
#############################################################################
11 11 2016 11:52:56.658:DEBUG [config]: No config file specified.
11 11 2016 11:52:56.663:DEBUG [plugin]: Loading karma-* from /PROJECT/node_modules
11 11 2016 11:52:56.665:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-coverage.
11 11 2016 11:52:56.772:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-mocha.
11 11 2016 11:52:56.774:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-mocha-reporter.
11 11 2016 11:52:56.775:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-phantomjs-launcher.
11 11 2016 11:52:56.779:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-webpack-with-fast-source-maps.
11 11 2016 11:52:56.871:DEBUG [web-server]: Instantiating middleware
11 11 2016 11:52:56.872:DEBUG [reporter]: Trying to load reporter: mocha
11 11 2016 11:52:56.874:DEBUG [reporter]: Trying to load color-version of reporter: mocha (mocha_color)
11 11 2016 11:52:56.874:DEBUG [reporter]: Couldn't load color-version.
11 11 2016 11:52:56.874:DEBUG [reporter]: Trying to load reporter: coverage
11 11 2016 11:52:56.875:DEBUG [reporter]: Trying to load color-version of reporter: coverage (coverage_color)
11 11 2016 11:52:56.875:DEBUG [reporter]: Couldn't load color-version.
11 11 2016 11:53:02.088:DEBUG [karma]: List of files has changed, trying to execute
11 11 2016 11:53:02.089:WARN [karma]: No captured browser, open http://localhost:9876/
11 11 2016 11:53:02.092:DEBUG [watcher]: Watching "/PROJECT/lib/test/main.test.js"
11 11 2016 11:53:02.097:INFO [karma]: Karma v1.3.0 server started at http://localhost:9876/
karma.Server: listening
11 11 2016 11:53:02.097:INFO [launcher]: Launching browser PhantomJS with unlimited concurrency
11 11 2016 11:53:02.150:INFO [launcher]: Starting browser PhantomJS
11 11 2016 11:53:02.150:DEBUG [temp-dir]: Creating temp dir at /var/folders/sl/0sdljlvx2h54p0zfc6xwlq3r0000gn/T/karma-46680807
11 11 2016 11:53:02.153:DEBUG [launcher]: /PROJECT/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs /var/folders/sl/0sdljlvx2h54p0zfc6xwlq3r0000gn/T/karma-46680807/capture.js
11 11 2016 11:53:02.802:DEBUG [web-server]: serving: /PROJECT/node_modules/karma/static/client.html
11 11 2016 11:53:02.810:DEBUG [web-server]: serving: /PROJECT/node_modules/karma/static/karma.js
11 11 2016 11:53:02.844:DEBUG [karma]: A browser has connected on socket /#ngqKXJPyANov64juAAAA
11 11 2016 11:53:02.847:DEBUG [web-server]: upgrade /socket.io/?EIO=3&transport=websocket&sid=ngqKXJPyANov64juAAAA
11 11 2016 11:53:02.867:INFO [PhantomJS 2.1.1 (Mac OS X 0.0.0)]: Connected on socket /#ngqKXJPyANov64juAAAA with id 46680807
karma.Server: browser_register
11 11 2016 11:53:02.868:DEBUG [launcher]: PhantomJS (id 46680807) captured in 0.771 secs
11 11 2016 11:53:02.868:DEBUG [karma]: All browsers are ready, executing
11 11 2016 11:53:02.868:DEBUG [karma]: Captured 1 browsers
karma.Server: run_start

START:
11 11 2016 11:53:02.872:DEBUG [phantomjs.launcher]:

11 11 2016 11:53:02.873:DEBUG [middleware:karma]: custom files null null
11 11 2016 11:53:02.873:DEBUG [middleware:karma]: Serving static request /context.html
11 11 2016 11:53:02.874:DEBUG [web-server]: serving: /PROJECT/node_modules/karma/static/context.html
11 11 2016 11:53:02.876:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/node_modules/mocha/mocha.css?68699fe2e12cd4578e48892d46c27fe84ee09b09 /
11 11 2016 11:53:02.876:DEBUG [middleware:source-files]: Fetching /PROJECT/node_modules/mocha/mocha.css
11 11 2016 11:53:02.876:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/mocha/mocha.css
11 11 2016 11:53:02.877:DEBUG [web-server]: serving: /PROJECT/node_modules/karma/static/context.js
11 11 2016 11:53:02.877:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/node_modules/mocha/mocha.js?bc2b9e2e7b386b405368c9247d419c9a1d2718c8 /
11 11 2016 11:53:02.877:DEBUG [middleware:source-files]: Fetching /PROJECT/node_modules/mocha/mocha.js
11 11 2016 11:53:02.878:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/node_modules/karma-mocha/lib/adapter.js?e8826109cf50b958ee4bd667517729ffdd4de363 /
11 11 2016 11:53:02.878:DEBUG [middleware:source-files]: Fetching /PROJECT/node_modules/karma-mocha/lib/adapter.js
11 11 2016 11:53:02.878:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/lib/test/main.test.js?28190b21b2bd15e90f78cc70ec7104bc4c32672c /
11 11 2016 11:53:02.878:DEBUG [middleware:source-files]: Fetching /PROJECT/lib/test/main.test.js
11 11 2016 11:53:02.878:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/mocha/mocha.js
11 11 2016 11:53:02.881:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/karma-mocha/lib/adapter.js
11 11 2016 11:53:02.881:DEBUG [web-server]: serving (cached): /PROJECT/lib/test/main.test.js
karma.Server: browser_start
  restartOnFileChange
    ✔ skips tests after the first run
karma.Server: browser_complete
karma.Server: run_complete

Finished in 0.01 secs / 0.004 secs

SUMMARY:
✔ 1 test completed

#############################################################################
#                                                                           #
#                         CHANGED FILE - SECOND RUN                         #
#           0 tests run immediately, without fetching any files.            #
#                                                                           #
#############################################################################
11 11 2016 11:53:14.344:DEBUG [karma]: List of files has changed, trying to execute
11 11 2016 11:53:14.344:DEBUG [karma]: All browsers are ready, executing
11 11 2016 11:53:14.344:DEBUG [karma]: Captured 1 browsers
karma.Server: run_start

================================================================================

START:
karma.Server: browser_complete
11 11 2016 11:53:14.346:DEBUG [phantomjs.launcher]:

karma.Server: run_complete

Finished in 0.001 secs / 0 secs

SUMMARY:
✔ 0 tests completed

#############################################################################
#                                                                           #
#                          CHANGED FILE - THIRD RUN                         #
#              0 tests run immediately, THEN, after run_complete,           #
#                web-server tries to fetch files and times out.             #
#                                                                           #
#############################################################################
11 11 2016 11:53:22.937:DEBUG [karma]: List of files has changed, trying to execute
11 11 2016 11:53:22.937:DEBUG [karma]: All browsers are ready, executing
11 11 2016 11:53:22.937:DEBUG [karma]: Captured 1 browsers
karma.Server: run_start

================================================================================

START:
karma.Server: browser_complete
11 11 2016 11:53:22.940:DEBUG [phantomjs.launcher]:

karma.Server: run_complete

Finished in 0.003 secs / 0 secs

SUMMARY:
✔ 0 tests completed

11 11 2016 11:53:22.942:DEBUG [middleware:karma]: Serving static request /context.html
11 11 2016 11:53:22.943:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/karma/static/context.html
11 11 2016 11:53:22.943:DEBUG [coverage]: Writing coverage to /PROJECT/coverage/PhantomJS 2.1.1 (Mac OS X 0.0.0)
11 11 2016 11:53:22.946:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/karma/static/context.js
11 11 2016 11:53:22.946:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/lib/test/main.test.js?a30b0747dc8cdfcc026c5f4713221372d6764ad7 /
11 11 2016 11:53:22.946:DEBUG [middleware:source-files]: Fetching /PROJECT/lib/test/main.test.js
11 11 2016 11:53:22.946:DEBUG [web-server]: serving (cached): /PROJECT/lib/test/main.test.js
karma.Server: browser_start
11 11 2016 11:53:33.110:WARN [PhantomJS 2.1.1 (Mac OS X 0.0.0)]: Disconnected (1 times), because no message in 10000 ms.
karma.Server: browser_error
PhantomJS 2.1.1 (Mac OS X 0.0.0) ERROR
    Disconnected, because no message in 10000 ms.
karma.Server: browser_complete

With restartOnFileChange: false
Notice on change that files are requested/fetched/served before tests are executed.
#############################################################################
#                                                                           #
#                                 FIRST RUN                                 #
#                                                                           #
#############################################################################
11 11 2016 12:01:09.610:DEBUG [config]: No config file specified.
11 11 2016 12:01:09.616:DEBUG [plugin]: Loading karma-* from /PROJECT/node_modules
11 11 2016 12:01:09.617:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-coverage.
11 11 2016 12:01:09.730:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-mocha.
11 11 2016 12:01:09.731:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-mocha-reporter.
11 11 2016 12:01:09.733:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-phantomjs-launcher.
11 11 2016 12:01:09.736:DEBUG [plugin]: Loading plugin /PROJECT/node_modules/karma-webpack-with-fast-source-maps.
11 11 2016 12:01:09.830:DEBUG [web-server]: Instantiating middleware
11 11 2016 12:01:09.831:DEBUG [reporter]: Trying to load reporter: mocha
11 11 2016 12:01:09.833:DEBUG [reporter]: Trying to load color-version of reporter: mocha (mocha_color)
11 11 2016 12:01:09.833:DEBUG [reporter]: Couldn't load color-version.
11 11 2016 12:01:09.833:DEBUG [reporter]: Trying to load reporter: coverage
11 11 2016 12:01:09.833:DEBUG [reporter]: Trying to load color-version of reporter: coverage (coverage_color)
11 11 2016 12:01:09.833:DEBUG [reporter]: Couldn't load color-version.
11 11 2016 12:01:15.095:DEBUG [karma]: List of files has changed, trying to execute
11 11 2016 12:01:15.095:WARN [karma]: No captured browser, open http://localhost:9876/
11 11 2016 12:01:15.098:DEBUG [watcher]: Watching "/PROJECT/lib/test/main.test.js"
11 11 2016 12:01:15.103:INFO [karma]: Karma v1.3.0 server started at http://localhost:9876/
karma.Server: listening
11 11 2016 12:01:15.103:INFO [launcher]: Launching browser PhantomJS with unlimited concurrency
11 11 2016 12:01:15.160:INFO [launcher]: Starting browser PhantomJS
11 11 2016 12:01:15.160:DEBUG [temp-dir]: Creating temp dir at /var/folders/sl/0sdljlvx2h54p0zfc6xwlq3r0000gn/T/karma-46312919
11 11 2016 12:01:15.162:DEBUG [launcher]: /PROJECT/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs /var/folders/sl/0sdljlvx2h54p0zfc6xwlq3r0000gn/T/karma-46312919/capture.js
11 11 2016 12:01:15.808:DEBUG [web-server]: serving: /PROJECT/node_modules/karma/static/client.html
11 11 2016 12:01:15.816:DEBUG [web-server]: serving: /PROJECT/node_modules/karma/static/karma.js
11 11 2016 12:01:15.852:DEBUG [karma]: A browser has connected on socket /#tIoQRCxsuT_SQOahAAAA
11 11 2016 12:01:15.855:DEBUG [web-server]: upgrade /socket.io/?EIO=3&transport=websocket&sid=tIoQRCxsuT_SQOahAAAA
11 11 2016 12:01:15.881:INFO [PhantomJS 2.1.1 (Mac OS X 0.0.0)]: Connected on socket /#tIoQRCxsuT_SQOahAAAA with id 46312919
karma.Server: browser_register
11 11 2016 12:01:15.881:DEBUG [launcher]: PhantomJS (id 46312919) captured in 0.777 secs
11 11 2016 12:01:15.882:DEBUG [karma]: All browsers are ready, executing
11 11 2016 12:01:15.882:DEBUG [karma]: Captured 1 browsers
karma.Server: run_start

START:
11 11 2016 12:01:15.886:DEBUG [phantomjs.launcher]:

11 11 2016 12:01:15.887:DEBUG [middleware:karma]: custom files null null
11 11 2016 12:01:15.887:DEBUG [middleware:karma]: Serving static request /context.html
11 11 2016 12:01:15.888:DEBUG [web-server]: serving: /PROJECT/node_modules/karma/static/context.html
11 11 2016 12:01:15.890:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/node_modules/mocha/mocha.css?68699fe2e12cd4578e48892d46c27fe84ee09b09 /
11 11 2016 12:01:15.890:DEBUG [middleware:source-files]: Fetching /PROJECT/node_modules/mocha/mocha.css
11 11 2016 12:01:15.891:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/mocha/mocha.css
11 11 2016 12:01:15.891:DEBUG [web-server]: serving: /PROJECT/node_modules/karma/static/context.js
11 11 2016 12:01:15.892:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/node_modules/mocha/mocha.js?bc2b9e2e7b386b405368c9247d419c9a1d2718c8 /
11 11 2016 12:01:15.892:DEBUG [middleware:source-files]: Fetching /PROJECT/node_modules/mocha/mocha.js
11 11 2016 12:01:15.892:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/node_modules/karma-mocha/lib/adapter.js?e8826109cf50b958ee4bd667517729ffdd4de363 /
11 11 2016 12:01:15.892:DEBUG [middleware:source-files]: Fetching /PROJECT/node_modules/karma-mocha/lib/adapter.js
11 11 2016 12:01:15.893:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/lib/test/main.test.js?5e91226ec1f799a8de02c2be606edfde22e8089e /
11 11 2016 12:01:15.893:DEBUG [middleware:source-files]: Fetching /PROJECT/lib/test/main.test.js
11 11 2016 12:01:15.894:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/mocha/mocha.js
11 11 2016 12:01:15.897:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/karma-mocha/lib/adapter.js
11 11 2016 12:01:15.897:DEBUG [web-server]: serving (cached): /PROJECT/lib/test/main.test.js
karma.Server: browser_start
  restartOnFileChange
    ✔ skips tests after the first run
karma.Server: browser_complete
karma.Server: run_complete

Finished in 0.012 secs / 0.005 secs

SUMMARY:
✔ 1 test completed

#############################################################################
#                                                                           #
#                         CHANGED FILE - SECOND RUN                         #
#             Successfully executes tests, after fetching files.            #
#                                                                           #
#############################################################################
11 11 2016 12:01:21.555:DEBUG [karma]: List of files has changed, trying to execute
11 11 2016 12:01:21.555:DEBUG [karma]: All browsers are ready, executing
11 11 2016 12:01:21.555:DEBUG [karma]: Captured 1 browsers
karma.Server: run_start

================================================================================

START:
11 11 2016 12:01:21.556:DEBUG [phantomjs.launcher]:

11 11 2016 12:01:21.557:DEBUG [middleware:karma]: custom files null null
11 11 2016 12:01:21.557:DEBUG [middleware:karma]: Serving static request /context.html
11 11 2016 12:01:21.557:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/karma/static/context.html
11 11 2016 12:01:21.559:DEBUG [web-server]: serving (cached): /PROJECT/node_modules/karma/static/context.js
11 11 2016 12:01:21.559:DEBUG [middleware:source-files]: Requesting /absolute/PROJECT/lib/test/main.test.js?eba96cf44a39ff7d29d003ec963558d0f4535ac6 /
11 11 2016 12:01:21.559:DEBUG [middleware:source-files]: Fetching /PROJECT/lib/test/main.test.js
11 11 2016 12:01:21.560:DEBUG [web-server]: serving (cached): /PROJECT/lib/test/main.test.js
karma.Server: browser_start
  restartOnFileChange
    ✔ skips tests after the first run
karma.Server: browser_complete
karma.Server: run_complete

Finished in 0.007 secs / 0.004 secs

SUMMARY:
✔ 1 test completed

Still failing.

Let me put here a comment on how this issue happens.
I'll try to find time in next several weeks to fix the issue and make a PR, but in case if someone is faster - you're welcome. Please ping me if you start to work on this.
Step by step what happens (karma 2.0.4) and why the issue appears:

File changes.

lib/server.js line 304 : file_list_modified event is handled

lib/server.js line 306 : the handler checks config.restartOnFileChange (this one is  true in our case)

lib/server.js line 307 : Server emits STOP event

lib/server.js line 309 : Server.executor.schedule() -> lib/executor.js line 34: capturedBrowsers.setAllToExecuting() -> lib/browser_collection.js line 36: set browser state to EXECUTING

static/karma.js line 235 : STOP event (emitted in step 4) is handled

static/karma.js line 236 : karma.complete method is called

static/karma.js line 204: karma emits COMPLETE event to the socket

lib/browser.js line 255 : COMPLETE event (emitted in step 8) is handled wtih onComplete function

lib/browser.js line 117 : onComplete method set the browser state to READY

Now the tests are started normally,lib/browser.js onStart method creates a new Result (line 101), and stores the total count of the specs to run....

Each spec is completed and the lib/browser.js has a notification about it in onResult (line 185). But in case if the browser state is READY, the onResult method just ignores that result:
see lib/browser.js lines 190-193 comment:

// ignore - probably results from last run (after server disconnecting)
    if (this.isReady()) {
      return
    }

So, once the restartOnFileChange config is set to TRUE, on the second run all the spec results are ignored, and the number of executed specs will be always 0.

authors: Nr9 alexander-ossur levithomason nobuti scottohara solo-md

repo: karma-runner/karma


text:
TypeError: Cannot read property 'isValidUTF8' of undefined

Expected behaviour
The test runner runs successfully.
Actual behaviour
An error is thrown when running karma start karma.conf.js --single-run in an Angular 2.4.7 project.
17 07 2017 14:37:25.450:INFO [karma]: Karma v1.7.0 server started at http://0.0.0.0:9876/
17 07 2017 14:37:25.450:INFO [launcher]: Launching browser Chrome with unlimited concurrency
17 07 2017 14:37:25.457:INFO [launcher]: Starting browser Chrome
17 07 2017 14:37:26.898:ERROR [karma]: TypeError: Cannot read property 'isValidUTF8' of undefined
    at /Users/kevinsalter/code/esportspools/resources/assets/site/node_modules/karma/node_modules/ws/lib/Receiver.js:532:28
    at /Users/kevinsalter/code/esportspools/resources/assets/site/node_modules/karma/node_modules/ws/lib/Receiver.js:368:7
    at /Users/kevinsalter/code/esportspools/resources/assets/site/node_modules/karma/node_modules/ws/lib/PerMessageDeflate.js:249:5
    at afterWrite (_stream_writable.js:385:3)
    at onwrite (_stream_writable.js:376:7)
    at WritableState.onwrite (_stream_writable.js:90:5)
    at afterTransform (_stream_transform.js:79:3)
    at TransformState.afterTransform (_stream_transform.js:54:12)
    at Zlib.callback (zlib.js:639:5)

Environment Details
Here are all packages in package.json of the project
"dependencies": {
    "@angular/common": "2.4.7",
    "@angular/compiler": "2.4.7",
    "@angular/core": "2.4.7",
    "@angular/forms": "2.4.7",
    "@angular/http": "2.4.7",
    "@angular/platform-browser": "2.4.7",
    "@angular/platform-browser-dynamic": "2.4.7",
    "@angular/router": "3.4.7",
    "@angular/upgrade": "2.4.7",
    "@ng-bootstrap/ng-bootstrap": "1.0.0-alpha.14",
    "angular2-swiper": "0.8.1",
    "core-js": "2.4.1",
    "intl": "1.2.5",
    "ng2-lazyload-image": "2.4.0",
    "reflect-metadata": "0.1.10",
    "rxjs": "5.4.0",
    "swiper": "3.4.2",
    "systemjs": "0.19.39",
    "ui-cropper": "1.0.4",
    "zone.js": "0.7.8"
  },
  "devDependencies": {
    "@types/core-js": "0.9.36",
    "@types/jasmine": "2.5.51",
    "@types/lodash": "4.14.51",
    "@types/node": "4.2.11",
    "apache-server-configs": "2.14.0",
    "awesome-typescript-loader": "3.1.3",
    "clean-webpack-plugin": "0.1.16",
    "concurrently": "3.4.0",
    "connect-modrewrite": "0.8.5",
    "grunt": "0.4.5",
    "grunt-autoprefixer": "1.0.1",
    "grunt-concurrent": "0.5.0",
    "grunt-contrib-clean": "0.6.0",
    "grunt-contrib-concat": "0.5.1",
    "grunt-contrib-connect": "0.8.0",
    "grunt-contrib-copy": "0.5.0",
    "grunt-contrib-cssmin": "0.10.0",
    "grunt-contrib-htmlmin": "0.4.0",
    "grunt-contrib-imagemin": "0.8.1",
    "grunt-contrib-jshint": "0.10.0",
    "grunt-contrib-less": "1.4.1",
    "grunt-contrib-uglify": "0.9.2",
    "grunt-contrib-watch": "0.6.1",
    "grunt-mocha": "0.4.15",
    "grunt-modernizr": "0.5.2",
    "grunt-newer": "0.7.0",
    "grunt-ng-annotate": "2.0.2",
    "grunt-rev": "0.1.0",
    "grunt-svg-sprite": "1.3.7",
    "grunt-svgmin": "0.4.0",
    "grunt-systemjs-builder": "0.2.7",
    "grunt-ts": "5.5.1",
    "grunt-usemin": "2.6.2",
    "grunt-wiredep": "1.9.0",
    "jasmine-core": "2.6.3",
    "jit-grunt": "0.9.1",
    "jshint-stylish": "0.4.0",
    "karma": "1.7.0",
    "karma-chrome-launcher": "2.1.1",
    "karma-cli": "1.0.1",
    "karma-htmlfile-reporter": "0.3.5",
    "karma-jasmine": "1.1.0",
    "karma-jasmine-html-reporter": "0.2.2",
    "load-grunt-tasks": "0.4.0",
    "localforage": "1.5.0",
    "lodash": "4.17.4",
    "ng2-file-upload": "1.2.1",
    "spawn-sync": "1.0.15",
    "time-grunt": "0.4.0",
    "typescript": "2.1.6",
    "webpack": "2.6.1",
    "webpack-livereload-plugin": "0.9.0",
    "webpack-merge": "1.1.2"
  },

Karma version: 1.7.0
I'm using the following plugins in karma.config.js

plugins: [
            require('karma-jasmine'),
            require('karma-chrome-launcher'),
            require('karma-jasmine-html-reporter'), // click "Debug" in browser to see it
            require('karma-htmlfile-reporter') // crashing w/ strange socket error
        ],

Steps to reproduce the behaviour

run karma start karma.conf.js --single-run

could this be pushed to version 1 as well?

authors: amir-arad kevinsalter


text:
Karma won't exit if more exit listeners are added to the server

Expected behaviour
Karma quits normally
Actual behaviour
Karma does not quit
Environment Details

Karma version (output of karma --version): 1.7.0

Steps to reproduce the behaviour
// set up tests server
function TestServer(logger, /* server */ karmaServer) {
    const server = http.createServer();
    enableDestory(server);
    server.listen(5555);
    karmaServer.on('exit', () => {
        server.destroy();
    });
}
TestServer.$inject = ['logger', 'server'];

But Karma won't quit, although the TestServer does get destroyed.

I've figured it out, have to use done callback:
karmaServer.on('exit', (done) => {
    server.on('close', done);
    server.destroy();
});


text:
Autowatch stopped working

Expected behaviour
running from command line using ng test with configuration file having autowatch set to true and restartOnFileChange also set to true, when changing a spec file the karma test runner would re-run the tests.
Actual behaviour
It runs the tests once on start up and then does nothing more, even if you change a spec file and save the changes
Environment Details
config file
module.exports = function (config) {   config.set({     basePath: '',     frameworks: ['jasmine', '@angular-devkit/build-angular'],     plugins: [       require('karma-jasmine'),       require('karma-chrome-launcher'),       require('karma-jasmine-html-reporter'),       require('karma-coverage-istanbul-reporter'),       require('@angular-devkit/build-angular/plugins/karma')     ],     client: {       clearContext: false // leave Jasmine Spec Runner output visible in browser     },     coverageIstanbulReporter: {       dir: require('path').join(__dirname, '../coverage/bpmgroup'),       reports: ['html', 'lcovonly', 'text-summary'],       fixWebpackSourcePaths: true     },     reporters: ['progress', 'kjhtml'],     port: 9876,     colors: true,     //logLevel: config.LOG_INFO,     logLevel: config.DEBUG,     autoWatch: true,     browsers: ['Chrome'],     singleRun: false,     restartOnFileChange: true   }); };

Karma version (output of karma --version): Command 'karma' not found, however Karma v4.1.0 server is reported by ng.
Relevant part of your karma.config.js file
autoWatch: true,   browsers: ['Chrome'],   singleRun: false,   restartOnFileChange: true

Steps to reproduce the behaviour

Write spec
Run ng test
change spec and save file

Our watcher works so I have no idea why yours does not.

You can try --logLevel=debug to verify that your watcher is loaded.

I've tried this with the freshly generated Angular CLI application and tests are indeed re-run after editing a spec file. Your error is likely a misconfiguration or environment-specific. In either case we can't really do anything to resolve it without being able to reproduce it. Please open a new issue providing a minimal reproduction of this behaviour if you still experience the problem.

authors: devoto13 johnjbarton thebpmgroup


text:
Read JSON as raw

Is there a way to read JSON from post request with headers Transfer-Encoding : chunked?
Like from uwebsockets.js

The Request.json() method is an optimized version of the uWebsockets.js implementation.
You can also consume the raw data using Request.on() since Request is a ReadableStream.

thanks for the reply.
actually with headers Transfer-Encoding : chunked, the Request.json(), Request.text(), Request.buffer() , Request.raw() returns null .
i end up using new Server().uws_instance.post() and then read the json data their.

Ohhh I see what you are talking about now. Yeah, currently hyper-express looks for a content-length to pre-allocate a body Buffer for performance reasons. I didn't know Transfer-Encoding chunked is supported now by uWS, should certainly be a feature worth adding to support in future.

Hey, support for chunked transfer requests has been added in the recent v6.15.2 versison.


text:
Anonymization

For the paper submission, we need to:

[ ] create a separate branch that we will link on http://anonymous.4open.science/
[ ] remove any traces of quintd datasets
[ ] anonymize LLM eval config files (which are also tied to our previous experiments)
[ ] remove the mentions of us from the About page
[ ] remove the Github link in the navbar

I created the branch called anonymized. The branch is not anonymized yet (but it should be).
I also linked the branch with this anonymous repository: https://anonymous.4open.science/r/factgenie/.
The anonymous repository is updated every ~1 hour from the anonymized branch, so it should be enough to update the branch to update the anonymous repository.

repo: kasnerz/factgenie


text:
Add the ability to configure the client id and client secret using environment variables for the OpenShift connector.

Change Overview
Add the ability to configure the client id and client secret using environment variables for the OpenShift connector.
Pull request type
Please check the type of change your PR introduces:

[x] :sunflower: Feature
[x] :robot: Test

Release Note Needed?

[x] Not Required

Issues

K10-5084

Test Plan

[x] Unit test

Thanks @vkamra .
Closing this one.
Created PR upstream - https://github.com/dexidp/dex/pull/1801

repo: kastenhq/dex