Python 3.4 incompatible ErrorReturnCode constructor

The initialization of sh.ErrorReturnCode with stdout or stderr as None does not work with Python 3.4,
because the str type in 3.4 has no function decode.
sh.ErrorReturnCode('test', None, None)
Traceback (most recent call last):
File "", line 1, in
File "/home/pfuchs/env/lis1/lib/python3.4/site-packages/sh.py", line 196, in init
(full_cmd, exc_stdout.decode(DEFAULT_ENCODING, "replace"),
AttributeError: 'str' object has no attribute 'decode'

Thanks for reporting

@PerFuchs do you remember how you were triggering this error?

I guess this line: ´sh.ErrorReturnCode('test', None, None)´ should be enough to trigger it.
Sorry, would try myself again, but I will not have a Linux until next month.

Ok thanks.  I guess I am wondering then why you were instantiating ErrorReturnCode on its own?  I thought the original issue was that somewhere in sh.py, we were passing in None, but if it is just in user code, I would say "don't do that" :)

Alright, I will check when I have access to my code again. Thanks for your time.

No problem, just re-open when ready

Being back from my holidays I had time to read up about this ticket in my code.
I tried to instantiate ErrorReturnCode on its own to mock a failed sh.Command in a test. To do so I wanted to raise a ErrorReturnCode myself. However I wasn't able to find suitable inputs for the parameter stdout and stderr.  Your code in ErrorReturnCode.__init__  has an if statement to handle None as input for stdout and stderr. That implied for me that None is a possible input, but this doesn't work in Python 3.4. Traceback is:
 Traceback (most recent call last):   File "<input>", line 1, in <module>   File "/home/pfuchs/env/lis2/lib/python3.4/site-packages/sh.py", line 196, in __init__     (full_cmd, exc_stdout.decode(DEFAULT_ENCODING, "replace"), AttributeError: 'str' object has no attribute 'decode'
Could you advise a better way to mock a failed sh.Command than raising sh.ErrorReturnCode myself?
What would be a valid input for ErrorReturnCode stdout and stderr?
Since your code implies None is a valid input, which is not working in reality, that might be an issue in your code as well.

The short answer is no, there doesn't seem to be another way to mock a command that raises ErrorReturnCode.  I will try to make it easier for the next release though.

That sounds good. What could I actually pass to the constructor? sys.stdout and sys.stderr lead to an error on my machinge, because the are unsubscriptable.

@PerFuchs sorry it's taken so long to get back to this.  Just use empty strings.  It's going to be the way to instantiate ErrorReturnCode manually going forward

That works for me, just got rid of some ugly lines in our testing code. Thanks a lot, highly appreciate it. After you told me, it feels like I should have had this idea ;)


Update to operator-sdk 1.11 on older branches

I have no idea if this is okay or not, but I observed that this is different from the master branch and prevents me from using operator-sdk run bundle from CI automation when working from this branch. I'm opening this PR just to test the change and discuss whether it's safe or not.

test

I would almost be surprised if this works at all. I abandoned this due to the number of external changes required to get everything operational again, and since we're probably not going to be doing a lot of feature development here, I didn't see the value in continuing on this effort.
The one potential thing that might make this worthwhile is that make bundle becomes much simpler under this model than with how we use operator-sdk 0.19.4 (and obviously more in line with how other Operators are now built).

I would almost be surprised if this works at all. I abandoned this due to the number of external changes required to get everything operational again, and since we're probably not going to be doing a lot of feature development here, I didn't see the value in continuing on this effort.
The one potential thing that might make this worthwhile is that make bundle becomes much simpler under this model than with how we use operator-sdk 0.19.4 (and obviously more in line with how other Operators are now built).

Disregard this comment. For some reason I thought this was a re-opening of my operator-sdk migration work. That is not the case at all.


CUDA Errors

I keep receiving some CUDA errors at random times during training.  The errors that I get are usually the following:
RuntimeError: CUDA error: misaligned address

RuntimeError: CUDA error: an illegal memory access was encountered

I am using Pytorch=1.9.1 with CudaToolkit 1.11.1 so I am unsure what the issue is?

this does not give me enough information, could you post your full log here?


Fix CSS duplicate semicolon on completion

Closes microsoft/vscode#82726

Sorry this is not the right fix. When you have cases like:
.foo {
  col| ;
}
.foo {
  co|: ;
}

These all comes without semicolonPosition. It only comes with a complete declaration.
I'll fix this myself. Thanks for trying to help out!

No problem!
I've been digging through trying to understand the codebase.
I look forward to see your fix!

The fix is in https://github.com/microsoft/vscode-css-languageservice/commit/a4c26e58d69ac3ff554e31cf6abcfd4ce81edcf7, if you are interested.


Add attribute to signal that a binding supports function level retry

Issue describing the changes in this PR
#1442 and #1050 would require this change first. We do not want to generate retry policy info and populate function metadata incorrectly for types that do not support function level retry. This table shows which trigger types support function-level retries.
Design doc.
Pull request checklist

[x] My changes do not require documentation changes

[ ] Otherwise: Documentation issue linked to PR

[x] My changes should not be added to the release notes for the next release

[x] Otherwise: I've added my notes to release_notes.md

[x] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[x] I have added all required tests (Unit tests, E2E tests)

Blocking on design discussion topics noted in #1442

Package version bump is missing from all impacted packages. Are you going to have another PR for that?

Bumped all but cosmos for now since that is in preview.


The package may have incorrect main/module/exports specified in its package.json

Describe the bug
I am importing our custom UI library, which is an NPM package that has the following defined in its package.json.
    "main": "dist/index.js",
    "module": "dist/index.modern.js",

When I run the build I get an error pointing me toward this package.json
>  NX   Failed to resolve entry for package "@our-custom/ui-components". The package may have incorrect main/module/exports specified in its package.json.

When I adjust the module to point to the index.js everything works fine and as expected
    "main": "dist/index.js",
    "module": "dist/index.js",

The difference between the index.js and index.modern.js is that the index.modern.js is not transpiled, so it has imports, consts etc.
Reproduction
Cannot provide it at the moment
Steps to reproduce
No response
System Info
System:
    OS: Linux 5.15 Ubuntu 20.04.5 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz
    Memory: 17.47 GB / 31.00 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.14.0 - ~/.volta/tools/image/node/16.14.0/bin/node
    Yarn: 3.4.1 - ~/.volta/tools/image/yarn/1.22.19/bin/yarn
    npm: 8.3.1 - ~/.volta/tools/image/node/16.14.0/bin/npm
  Browsers:
    Chrome: 110.0.5481.177
    Firefox: 110.0.1
  npmPackages:
    @vitejs/plugin-react: ^3.0.0 => 3.1.0
    vite: ^4.0.1 => 4.1.4

### Used Package Manager

yarn

### Logs

_No response_

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitejs/vite/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitejs.dev/guide).
- [X] Check that there isn't [already an issue](https://github.com/vitejs/vite/issues) that reports the same bug to avoid creating a duplicate.
- [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to [vuejs/core](https://github.com/vuejs/core) instead.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vitejs.dev/).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

A minimal reproduction is needed to address this issue.

I've experienced a similar issue recently at work. (forgive me as i'm mostly backend these days)
We have an internal UI library that we import to various react projects which use webpack. I started a new project in wails.io which uses vite. We were getting this exact error for our UI library The package may have incorrect main/module/exports specified in its package.json when doing simple imports import { BTN } from '@company/uilib'
We also had both a main & module entry in the package.json. From what we could tell, vite was preferring the module entry, whereas the projects running webpack seemed to prefer main. Our solution was just to remove module from the ui lib's package.json, this seemed to satisfy all our build systems.
Additionally, our UI library is targeting umd.

@fi3ework my preferred solution would be for Vite to recognize the ESM (modern) version that it is accessing from the module property in package.json, which it, currently does not.
Removing the module property or setting it to return the legacy code, although it would suffice, is not really the point here or possible in some cases.
It is there so that the tools that expect it, as @fi3ework suggests, could use it.

Vite recognizes module field (link) and also could handle ESM imports and ES5 syntax. So a reproduction is needed to address the specific issue.


Iio/i2c: config pinmuing before load I2C devices

On some platforms(Galileo/Edison), these GPIO pins must be configured before using I2C bus
This patch perform the pin mux configuration before loading I2C device drivers
Signed-off-by: Yong Li<EMAIL_ADDRESS>

@bdilly please help to review

Indentation is wrong, run tools/check-style.py before sending patches.
As for the pinmux, check with @mbelluzzo

Just by the commit, it doesn't look like the right place to set the mux on Soletta. I would like to check the full context before confirm this but I'm not in my desk right now.

You have a typo in your commit: "pinmuing" . Could you fix that?

After a little discussing with @edersondisouza about the usage context of this code, we both agree that is indeed the right place to setup the mux. Just take inline comment into consideration.


Assert failure when opening a trace file

I get the exact same error as in #10:
$ memtrace-viewer typeInferenceLocalTest-domain.ctf
Processing typeInferenceLocalTest-domain.ctf...
(monitor.ml.Error "Assert_failure src/location_codec.ml:27:17"
 ("Raised at Memtrace__Location_codec.Mtf_table.swap in file \"src/location_codec.ml\", line 27, characters 17-29"
  "Called from Memtrace__Location_codec.Mtf_table.decode in file \"src/location_codec.ml\", line 59, characters 6-16"
  "Called from Memtrace__Location_codec.Reader.get_location.(fun) in file \"src/location_codec.ml\", line 177, characters 8-143"
  "Called from Stdlib__List.init in file \"list.ml\", line 64, characters 25-28"
  "Called from Memtrace__Location_codec.Reader.get_location in file \"src/location_codec.ml\", line 150, characters 15-1023"
  "Called from Memtrace__Trace.iter.iter_events_of_packet in file \"src/trace.ml\", line 694, characters 24-71"
  "Called from Memtrace__Trace.iter.iter_packets in file \"src/trace.ml\", line 738, characters 8-50"
  "Called from Memtrace_viewer_native__Raw_trace.iter in file \"server/src/raw_trace.ml\", line 89, characters 2-217"
  "Called from Memtrace_viewer_native__Filtered_trace.iter_and_return_interpreter in file \"server/src/filtered_trace.ml\", line 762, characters 2-117"
  "Called from Memtrace_viewer_native__Filtered_trace.iter in file \"server/src/filtered_trace.ml\" (inlined), line 768, characters 20-82"
  "Called from Memtrace_viewer_native__Graph.full_graph_and_max_time in file \"server/src/graph.ml\", line 12, characters 2-521"
  "Called from Memtrace_viewer_native__Graph.build in file \"server/src/graph.ml\", line 57, characters 29-59"
  "Called from Memtrace_viewer_native__User_state.Env.of_trace in file \"server/src/user_state.ml\", line 38, characters 16-66"
  "Called from Memtrace_viewer_native.main in file \"server/src/memtrace_viewer_native.ml\", line 66, characters 12-41"))

but I’m able to provide a trace file:
trace.tar.gz

Thanks, we've also just seen an occurrence of this internally, so hopefully between these two traces we can work it out.

Thanks for the trace! Having looked at it, this looks like it was indeed the issue that was fixed in janestreet/memtrace#23, so I'm closing for now. Please do re-open if you find that doesn't help

It does not appear to me that https://github.com/janestreet/memtrace/pull/23 fixed the issue, at least for this case. I checked out https://github.com/janestreet/memtrace/commit/c86e4fe3e8308e86f066d6c00e4dbc69003ec381 in a fresh opam switch, ran opam install ., and then got the following output using the trace provided in this issue:
$ memtrace_identify typeInferenceLocalTest-domain.ctf
Trace file typeInferenceLocalTest-domain.ctf (109 kB)
   of /home/olivier/hacking_days/pyre-check/source/_build/default/interprocedural_analyses/type_inference/test/typeInferenceLocalTest.exe
   at Fri Jul 26 16:23:56 2024 UTC
   on host oliv-thinkpad (64-bit), pid 3640882, sample rate 1.0e-06
   with OCaml GC params caml_runtime_parameters not implemented: 0
   with context: my program
Trace statistics:
Fatal error: exception File "src/location_codec.ml", line 27, characters 17-23: Assertion failed

I noticed this because I also have a trace failing with this error on memtrace-viewer, even when it's built with the latest master version of memtrace.

Nevermind. I misunderstood the fix, and assumed that it was to address issues on the consumption side of a trace, not the creation side. I switched to using the master version of memtrace to create traces and I no longer have this problem. Thanks!


matrix-synapse: 1.30 -> 1.32.1

Motivation for this change
Closes #118864
https://github.com/matrix-org/synapse/releases/tag/v1.31.0
https://github.com/matrix-org/synapse/releases/tag/v1.32.0
Note: from this release onwards at least Postgres 9.6 and Python 3.6 is needed.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

WARNING: We've identified a load issue with Prometheus metrics in this release; we encourage you to wait for 1.32.1 which should be published tomorrow (April 21st).

Yeah, didn't intend to merge it tonight :)

https://github.com/matrix-org/synapse/blob/develop/CHANGES.md

This release fixes a regression in Synapse 1.32.0 that caused connected Prometheus instances to become unstable.
However, as this release is still subject to the LoggingContext change in 1.32.0, it is recommended to remain on or downgrade to 1.31.0.

Thanks for noticing, apparently this was realized after my latest update here :)
Wondering if applying https://github.com/matrix-org/synapse/commit/d9bd62f9d1a6238b3f485caee07f9fd399b27134 would be sufficient here.

1.32.2 is out. Seems to fix the problem. Just deployed it to my instance and it seems fine.


Implementing ExceptionHandler In Ionic2

I'd like to implement an ExceptionHandler in my Ionic2 app, but can't find any documentation or examples.
I followed the instructions on http://stackoverflow.com/a/39189175/385730, but the provider does not seem to be working.
Other discussions suggest its possible using Angular2's https://angular.io/docs/js/latest/api/core/index/ExceptionHandler-class.html.
How do you implement ExceptionHandler in Ionic2?

Hello! Thanks for opening an issue with us! As this seems like more of a support question i will urge that you ask this question on our forum. Thanks for using Ionic!

For those who stumble onto this issue, here is the forum post https://forum.ionicframework.com/t/implementing-exceptionhandler-in-ionic2/63196 with the question.


-DDEBUG allows switching between two incompatible class layouts in a public header file

SymbolId.h, one of the public headers, uses DEBUG preprocessor define to switch between two binary-incompatible class layouts and sizes by optionally adding a data field to a class.
As a result, a program compiled with -DDEBUG which uses SymbolId.h and UHDM compiled without -DDEBUG will crash.
This has been a minor issue in systemverilog-plugin, as Yosys sets -DDEBUG when ENABLE_DEBUG is set.
Moreover, seems like the DEBUG define is not set by CMake when UHDM (or, more precisely, Surelog) is compiled with -DCMAKE_BUILD_TYPE=Debug. -DCMAKE_CXX_FLAGS='-DDEBUG=1' makes everything work fine.

I wonder whether #if defined(DEBUG) can be removed, as the relevant feature can be already controlled with a more unique SYMBOLID_DEBUG_ENABLED.
Another option would be to generate SymbolId.h with hardcoded option depending on whether UHDM has been compiled with it or not.

@hzeller, please suggest.

@hs-apotell this concerns you.

It is highly bug-prone if the layout of objects is changed depending on how the something happens to be compiled.
So I suggest to remove the #ifdef sections with debug information in this class. Are there other places like that as well ? Then these also.
If this is still needed for local debugging @hs-apotell , I suggest for now to keep the change in a local patch that you can apply to your environment when needed, but remove it from the version on github to not trip users further.
If the debugging feature is needed outside the core developer circles, we then can still see if we find a less intrusive solution.


[ERR] Cassandra error: connection refused

I retried the whole installation for Kong and it all went well.
But now I get the following:
$ kong start
[INFO] Using configuration: /etc/kong/kong.yml
[INFO] Kong version.......0.3.2
       Proxy HTTP port....8000
       Proxy HTTPS port...8443
       Admin API port.....8001
       dnsmasq port.......8053
       Database...........cassandra keepalive=60000 hosts=localhost port=9042 timeout=1000 keyspace=kong
[INFO] Connecting to the database...
[ERR] Cassandra error: connection refused

I am totally new with kong, and haven't changed the /etc/kong/kong.yml from the defaults.
Can anyone help me with what I am doing wrong?

Usually this errors happens when Kong cannot communicate with Cassandra. By default the configuration expects Cassandra to be running on <IP_ADDRESS> on the default 9042 port. Did you also install and start Cassandra on <IP_ADDRESS>?
If you did't install Cassandra, one option is to install it, and another option is to use kongdb.org to provision a testing Cassandra instance (remember to change the connection settings in kong.yml with the right values).

I have really no idea how to setup or use Cassandra.
But I have used the default configurations.
Then I tried to start Cassandra with the following methods:
forge@kong:~$ sudo service cassandra start
forge@kong:~$ sudo service cassandra restart
 * Restarting Cassandra cassandra                                                                                [ OK ]
forge@kong:~$ sudo service cassandra stop
forge@kong:~$ sudo service cassandra start

But still I get:
$ kong start
[INFO] Using configuration: /etc/kong/kong.yml
[INFO] Kong version.......0.3.2
       Proxy HTTP port....8000
       Proxy HTTPS port...8443
       Admin API port.....8001
       dnsmasq port.......8053
       Database...........cassandra keepalive=60000 hosts=localhost port=9042 timeout=1000 keyspace=kong
[INFO] Connecting to the database...
[ERR] Cassandra error: connection refused

NOTE: Sometimes when restarting Cassandra I get this:
$ sudo service cassandra restart
 * Restarting Cassandra cassandra
start-stop-daemon: warning: failed to kill 21417: No such process

And even when using the Kongdb settings from kongdb.org I get an error:
$ kong start
[INFO] Using configuration: /etc/kong/kong.yml
[INFO] Kong version.......0.3.2
       Proxy HTTP port....8000
       Proxy HTTPS port...8443
       Admin API port.....8001
       dnsmasq port.......8053
       Database...........cassandra keepalive=60000 hosts=ec2-54-172-252-55.compute-1.amazonaws.com port=32824 timeout=2000 keyspace=kong
[INFO] Connecting to the database...
[ERR] Cassandra error: connection refused

I found a stack overflow with the issue, and wondered if that could have anything to do with it.
So I found rpc_address: localhost and rpc_port: 9160 in /etc/cassandra/cassandra.yaml.
Could it maybe be that the server blocks that port for some reason?
I also tried to check if it was actually listining to the port 9042, but seems not to, since I get nothing from $ cat /etc/services | grep 9042.
Also a good knowledge note is that my server has a public and a private IP and a firewall installed.

My bad, that above command is not supposed to return any input.
But $ sudo netstat -anp | grep 9042and $ sudo lsof -i | grep 9042 also returns empty.

@marktopper What OS are you using?

Linux 14.04

To check if cassandra is running you can execute:
$ cqlsh

Which is the shell client of Cassandra. If Cassandra is running on <IP_ADDRESS>, you should see something like:
Connected to Test Cluster at <IP_ADDRESS>:9042.
[cqlsh 5.0.1 | Cassandra 2.1.3 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh>

I followed this to get it installed: https://gist.github.com/marktopper/b9c45b1b7c1f7e03030e

Running cqlsh returns:
Connection error: Could not connect to localhost:9160

Can you try with:
cqlsh <IP_ADDRESS> 9042

Also, are you using Cassandra version >= 2.1.7 ?

$ cqlsh <IP_ADDRESS> 9042
Connection error: Could not connect to <IP_ADDRESS>:9042

Which makes be believe Cassandra didn't start for some reason. Can you try to execute:
ps aux | grep cassandra

Ohh. Seems to be Cassandra v. Version: 2.0.11.
I will get it updated and get back.

If you still need the other informations.
$ ps aux | grep cassandra
forge    22250  0.0  0.1  11740   940 pts/0    S+   10:59   0:00 grep --color=auto cassandra

Upgraded to Cassandra Version: 2.1.8

Okay run:
$ cassandra

Wait for it to start and then:
$ cqlsh <IP_ADDRESS> 9042

$ cassandra
forge@kong:~$ 05:03:12,627 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/etc/cassandra/logback.xml]
05:03:12,766 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
05:03:12,779 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will scan for changes in [[/etc/cassandra/logback.xml]] every 60 seconds.
05:03:12,779 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Adding ReconfigureOnChangeFilter as a turbo filter
05:03:12,797 |-INFO in ch.qos.logback.classic.joran.action.JMXConfiguratorAction - begin
05:03:12,876 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
05:03:12,881 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
05:03:12,967 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@18dba48d - Will use zip compression
05:03:13,005 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
05:03:13,096 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: /var/log/cassandra/system.log
05:03:13,096 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [/var/log/cassandra/system.log]
05:03:13,106 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - openFile(/var/log/cassandra/system.log,true) call failed. java.io.FileNotFoundException: /var/log/cassandra/system.log (Permission denied)
	at java.io.FileNotFoundException: /var/log/cassandra/system.log (Permission denied)
	at 	at java.io.FileOutputStream.open(Native Method)
	at 	at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
	at 	at ch.qos.logback.core.recovery.ResilientFileOutputStream.<init>(ResilientFileOutputStream.java:28)
	at 	at ch.qos.logback.core.FileAppender.openFile(FileAppender.java:150)
	at 	at ch.qos.logback.core.FileAppender.start(FileAppender.java:108)
	at 	at ch.qos.logback.core.rolling.RollingFileAppender.start(RollingFileAppender.java:86)
	at 	at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
	at 	at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:317)
	at 	at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:196)
	at 	at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:182)
	at 	at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62)
	at 	at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:149)
	at 	at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:135)
	at 	at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:99)
	at 	at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:49)
	at 	at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75)
	at 	at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
	at 	at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85)
	at 	at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
	at 	at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128)
	at 	at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107)
	at 	at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295)
	at 	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269)
	at 	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
	at 	at org.apache.cassandra.service.CassandraDaemon.<clinit>(CassandraDaemon.java:73)
05:03:13,106 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
05:03:13,114 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
05:03:13,126 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
05:03:13,137 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
05:03:13,137 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[ROOT]
05:03:13,138 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]
05:03:13,139 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.thinkaurelius.thrift] to ERROR
05:03:13,139 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
05:03:13,139 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@4e58c0be - Registering current configuration as safe fallback point

INFO  09:03:13 Hostname: kong
INFO  09:03:13 Loading settings from file:/etc/cassandra/cassandra.yaml
INFO  09:03:13 Node configuration:[authenticator=AllowAllAuthenticator; authorizer=AllowAllAuthorizer; auto_snapshot=true; batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024; cas_contention_timeout_in_ms=1000; client_encryption_options=<REDACTED>; cluster_name=Test Cluster; column_index_size_in_kb=64; commit_failure_policy=stop; commitlog_directory=/var/lib/cassandra/commitlog; commitlog_segment_size_in_mb=32; commitlog_sync=periodic; commitlog_sync_period_in_ms=10000; compaction_large_partition_warning_threshold_mb=100; compaction_throughput_mb_per_sec=16; concurrent_counter_writes=32; concurrent_reads=32; concurrent_writes=32; counter_cache_save_period=7200; counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; cross_node_timeout=false; data_file_directories=[/var/lib/cassandra/data]; disk_failure_policy=stop; dynamic_snitch_badness_threshold=0.1; dynamic_snitch_reset_interval_in_ms=600000; dynamic_snitch_update_interval_in_ms=100; endpoint_snitch=SimpleSnitch; hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024; incremental_backups=false; index_summary_capacity_in_mb=null; index_summary_resize_interval_in_minutes=60; inter_dc_tcp_nodelay=false; internode_compression=all; key_cache_save_period=14400; key_cache_size_in_mb=null; listen_address=localhost; max_hint_window_in_ms=10800000; max_hints_delivery_threads=2; memtable_allocation_type=heap_buffers; native_transport_port=9042; num_tokens=256; partitioner=org.apache.cassandra.dht.Murmur3Partitioner; permissions_validity_in_ms=2000; range_request_timeout_in_ms=10000; read_request_timeout_in_ms=5000; request_scheduler=org.apache.cassandra.scheduler.NoScheduler; request_timeout_in_ms=10000; row_cache_save_period=0; row_cache_size_in_mb=0; rpc_address=localhost; rpc_keepalive=true; rpc_port=9160; rpc_server_type=sync; saved_caches_directory=/var/lib/cassandra/saved_caches; seed_provider=[{class_name=org.apache.cassandra.locator.SimpleSeedProvider, parameters=[{seeds=<IP_ADDRESS>}]}]; server_encryption_options=<REDACTED>; snapshot_before_compaction=false; ssl_storage_port=7001; sstable_preemptive_open_interval_in_mb=50; start_native_transport=true; start_rpc=true; storage_port=7000; thrift_framed_transport_size_in_mb=15; tombstone_failure_threshold=100000; tombstone_warn_threshold=1000; trickle_fsync=false; trickle_fsync_interval_in_kb=10240; truncate_request_timeout_in_ms=60000; write_request_timeout_in_ms=2000]
INFO  09:03:13 DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap
INFO  09:03:13 Global memtable on-heap threshold is enabled at 59MB
INFO  09:03:13 Global memtable off-heap threshold is enabled at 59MB
INFO  09:03:14 Loading settings from file:/etc/cassandra/cassandra.yaml
INFO  09:03:14 Node configuration:[authenticator=AllowAllAuthenticator; authorizer=AllowAllAuthorizer; auto_snapshot=true; batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024; cas_contention_timeout_in_ms=1000; client_encryption_options=<REDACTED>; cluster_name=Test Cluster; column_index_size_in_kb=64; commit_failure_policy=stop; commitlog_directory=/var/lib/cassandra/commitlog; commitlog_segment_size_in_mb=32; commitlog_sync=periodic; commitlog_sync_period_in_ms=10000; compaction_large_partition_warning_threshold_mb=100; compaction_throughput_mb_per_sec=16; concurrent_counter_writes=32; concurrent_reads=32; concurrent_writes=32; counter_cache_save_period=7200; counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; cross_node_timeout=false; data_file_directories=[/var/lib/cassandra/data]; disk_failure_policy=stop; dynamic_snitch_badness_threshold=0.1; dynamic_snitch_reset_interval_in_ms=600000; dynamic_snitch_update_interval_in_ms=100; endpoint_snitch=SimpleSnitch; hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024; incremental_backups=false; index_summary_capacity_in_mb=null; index_summary_resize_interval_in_minutes=60; inter_dc_tcp_nodelay=false; internode_compression=all; key_cache_save_period=14400; key_cache_size_in_mb=null; listen_address=localhost; max_hint_window_in_ms=10800000; max_hints_delivery_threads=2; memtable_allocation_type=heap_buffers; native_transport_port=9042; num_tokens=256; partitioner=org.apache.cassandra.dht.Murmur3Partitioner; permissions_validity_in_ms=2000; range_request_timeout_in_ms=10000; read_request_timeout_in_ms=5000; request_scheduler=org.apache.cassandra.scheduler.NoScheduler; request_timeout_in_ms=10000; row_cache_save_period=0; row_cache_size_in_mb=0; rpc_address=localhost; rpc_keepalive=true; rpc_port=9160; rpc_server_type=sync; saved_caches_directory=/var/lib/cassandra/saved_caches; seed_provider=[{class_name=org.apache.cassandra.locator.SimpleSeedProvider, parameters=[{seeds=<IP_ADDRESS>}]}]; server_encryption_options=<REDACTED>; snapshot_before_compaction=false; ssl_storage_port=7001; sstable_preemptive_open_interval_in_mb=50; start_native_transport=true; start_rpc=true; storage_port=7000; thrift_framed_transport_size_in_mb=15; tombstone_failure_threshold=100000; tombstone_warn_threshold=1000; trickle_fsync=false; trickle_fsync_interval_in_kb=10240; truncate_request_timeout_in_ms=60000; write_request_timeout_in_ms=2000]
INFO  09:03:14 JVM vendor/version: Java HotSpot(TM) 64-Bit Server VM/1.7.0_80
INFO  09:03:14 Heap size: 250544128/251592704
INFO  09:03:14 Code Cache Non-heap memory: init = 2555904(2496K) used = 712128(695K) committed = 2555904(2496K) max = 50331648(49152K)
INFO  09:03:14 Eden Space Heap memory: init = 51249152(50048K) used = 51249152(50048K) committed = 51249152(50048K) max = 51249152(50048K)
INFO  09:03:14 Survivor Space Heap memory: init = 6356992(6208K) used = 6356992(6208K) committed = 6356992(6208K) max = 6356992(6208K)
INFO  09:03:14 CMS Old Gen Heap memory: init = 192937984(188416K) used = 1043616(1019K) committed = 192937984(188416K) max = 193986560(189440K)
INFO  09:03:14 CMS Perm Gen Non-heap memory: init = 21757952(21248K) used = 15567520(15202K) committed = 21757952(21248K) max = 85983232(83968K)
INFO  09:03:14 Classpath: /etc/cassandra:/usr/share/cassandra/lib/ST4-4.0.8.jar:/usr/share/cassandra/lib/airline-0.6.jar:/usr/share/cassandra/lib/antlr-runtime-3.5.2.jar:/usr/share/cassandra/lib/commons-cli-1.1.jar:/usr/share/cassandra/lib/commons-codec-1.2.jar:/usr/share/cassandra/lib/commons-lang3-3.1.jar:/usr/share/cassandra/lib/commons-math3-3.2.jar:/usr/share/cassandra/lib/compress-lzf-0.8.4.jar:/usr/share/cassandra/lib/concurrentlinkedhashmap-lru-1.4.jar:/usr/share/cassandra/lib/disruptor-3.0.1.jar:/usr/share/cassandra/lib/guava-16.0.jar:/usr/share/cassandra/lib/high-scale-lib-1.0.6.jar:/usr/share/cassandra/lib/jackson-core-asl-1.9.2.jar:/usr/share/cassandra/lib/jackson-mapper-asl-1.9.2.jar:/usr/share/cassandra/lib/jamm-0.3.0.jar:/usr/share/cassandra/lib/javax.inject.jar:/usr/share/cassandra/lib/jbcrypt-0.3m.jar:/usr/share/cassandra/lib/jline-1.0.jar:/usr/share/cassandra/lib/jna-4.0.0.jar:/usr/share/cassandra/lib/json-simple-1.1.jar:/usr/share/cassandra/lib/libthrift-0.9.2.jar:/usr/share/cassandra/lib/logback-classic-1.1.2.jar:/usr/share/cassandra/lib/logback-core-1.1.2.jar:/usr/share/cassandra/lib/lz4-1.2.0.jar:/usr/share/cassandra/lib/metrics-core-2.2.0.jar:/usr/share/cassandra/lib/netty-all-4.0.23.Final.jar:/usr/share/cassandra/lib/reporter-config-2.1.0.jar:/usr/share/cassandra/lib/slf4j-api-1.7.2.jar:/usr/share/cassandra/lib/snakeyaml-1.11.jar:/usr/share/cassandra/lib/snappy-java-<IP_ADDRESS>.jar:/usr/share/cassandra/lib/stream-2.5.2.jar:/usr/share/cassandra/lib/super-csv-2.1.0.jar:/usr/share/cassandra/lib/thrift-server-0.3.7.jar:/usr/share/cassandra/apache-cassandra-2.1.8.jar:/usr/share/cassandra/apache-cassandra-thrift-2.1.8.jar:/usr/share/cassandra/apache-cassandra.jar:/usr/share/cassandra/cassandra-driver-core-<IP_ADDRESS>.jar:/usr/share/cassandra/netty-3.9.0.Final.jar:/usr/share/cassandra/stress.jar::/usr/share/cassandra/lib/jamm-0.3.0.jar
WARN  09:03:14 Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Cassandra as root.
WARN  09:03:14 JMX is not enabled to receive remote connections. Please see cassandra-env.sh for more info.
ERROR 09:03:14 Directory /var/lib/cassandra/data doesn't exist
ERROR 09:03:14 Has no permission to create /var/lib/cassandra/data directory

$ cqlsh <IP_ADDRESS> 9042
Connection error: ('Unable to connect to any servers', {'<IP_ADDRESS>': error(111, "Tried connecting to [('<IP_ADDRESS>', 9042)]. Last error: Connection refused")})

Noticed the following:
WARN  09:02:31 Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Cassandra as root.
WARN  09:02:31 JMX is not enabled to receive remote connections. Please see cassandra-env.sh for more info.
ERROR 09:02:31 Directory /var/lib/cassandra/data doesn't exist
ERROR 09:02:31 Has no permission to create /var/lib/cassandra/data directory

And
05:03:13,106 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - openFile(/var/log/cassandra/system.log,true) call failed. java.io.FileNotFoundException: /var/log/cassandra/system.log (Permission denied)

Should I run it with sudo?

Yes please.

forge@kong:~$ sudo cassandra
forge@kong:~$ INFO  09:05:03 Hostname: kong
INFO  09:05:03 Loading settings from file:/etc/cassandra/cassandra.yaml
INFO  09:05:04 Node configuration:[authenticator=AllowAllAuthenticator; authorizer=AllowAllAuthorizer; auto_snapshot=true; batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024; cas_contention_timeout_in_ms=1000; client_encryption_options=<REDACTED>; cluster_name=Test Cluster; column_index_size_in_kb=64; commit_failure_policy=stop; commitlog_directory=/var/lib/cassandra/commitlog; commitlog_segment_size_in_mb=32; commitlog_sync=periodic; commitlog_sync_period_in_ms=10000; compaction_large_partition_warning_threshold_mb=100; compaction_throughput_mb_per_sec=16; concurrent_counter_writes=32; concurrent_reads=32; concurrent_writes=32; counter_cache_save_period=7200; counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; cross_node_timeout=false; data_file_directories=[/var/lib/cassandra/data]; disk_failure_policy=stop; dynamic_snitch_badness_threshold=0.1; dynamic_snitch_reset_interval_in_ms=600000; dynamic_snitch_update_interval_in_ms=100; endpoint_snitch=SimpleSnitch; hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024; incremental_backups=false; index_summary_capacity_in_mb=null; index_summary_resize_interval_in_minutes=60; inter_dc_tcp_nodelay=false; internode_compression=all; key_cache_save_period=14400; key_cache_size_in_mb=null; listen_address=localhost; max_hint_window_in_ms=10800000; max_hints_delivery_threads=2; memtable_allocation_type=heap_buffers; native_transport_port=9042; num_tokens=256; partitioner=org.apache.cassandra.dht.Murmur3Partitioner; permissions_validity_in_ms=2000; range_request_timeout_in_ms=10000; read_request_timeout_in_ms=5000; request_scheduler=org.apache.cassandra.scheduler.NoScheduler; request_timeout_in_ms=10000; row_cache_save_period=0; row_cache_size_in_mb=0; rpc_address=localhost; rpc_keepalive=true; rpc_port=9160; rpc_server_type=sync; saved_caches_directory=/var/lib/cassandra/saved_caches; seed_provider=[{class_name=org.apache.cassandra.locator.SimpleSeedProvider, parameters=[{seeds=<IP_ADDRESS>}]}]; server_encryption_options=<REDACTED>; snapshot_before_compaction=false; ssl_storage_port=7001; sstable_preemptive_open_interval_in_mb=50; start_native_transport=true; start_rpc=true; storage_port=7000; thrift_framed_transport_size_in_mb=15; tombstone_failure_threshold=100000; tombstone_warn_threshold=1000; trickle_fsync=false; trickle_fsync_interval_in_kb=10240; truncate_request_timeout_in_ms=60000; write_request_timeout_in_ms=2000]
INFO  09:05:04 DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap
INFO  09:05:04 Global memtable on-heap threshold is enabled at 59MB
INFO  09:05:04 Global memtable off-heap threshold is enabled at 59MB
INFO  09:05:04 Loading settings from file:/etc/cassandra/cassandra.yaml
INFO  09:05:04 Node configuration:[authenticator=AllowAllAuthenticator; authorizer=AllowAllAuthorizer; auto_snapshot=true; batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024; cas_contention_timeout_in_ms=1000; client_encryption_options=<REDACTED>; cluster_name=Test Cluster; column_index_size_in_kb=64; commit_failure_policy=stop; commitlog_directory=/var/lib/cassandra/commitlog; commitlog_segment_size_in_mb=32; commitlog_sync=periodic; commitlog_sync_period_in_ms=10000; compaction_large_partition_warning_threshold_mb=100; compaction_throughput_mb_per_sec=16; concurrent_counter_writes=32; concurrent_reads=32; concurrent_writes=32; counter_cache_save_period=7200; counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; cross_node_timeout=false; data_file_directories=[/var/lib/cassandra/data]; disk_failure_policy=stop; dynamic_snitch_badness_threshold=0.1; dynamic_snitch_reset_interval_in_ms=600000; dynamic_snitch_update_interval_in_ms=100; endpoint_snitch=SimpleSnitch; hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024; incremental_backups=false; index_summary_capacity_in_mb=null; index_summary_resize_interval_in_minutes=60; inter_dc_tcp_nodelay=false; internode_compression=all; key_cache_save_period=14400; key_cache_size_in_mb=null; listen_address=localhost; max_hint_window_in_ms=10800000; max_hints_delivery_threads=2; memtable_allocation_type=heap_buffers; native_transport_port=9042; num_tokens=256; partitioner=org.apache.cassandra.dht.Murmur3Partitioner; permissions_validity_in_ms=2000; range_request_timeout_in_ms=10000; read_request_timeout_in_ms=5000; request_scheduler=org.apache.cassandra.scheduler.NoScheduler; request_timeout_in_ms=10000; row_cache_save_period=0; row_cache_size_in_mb=0; rpc_address=localhost; rpc_keepalive=true; rpc_port=9160; rpc_server_type=sync; saved_caches_directory=/var/lib/cassandra/saved_caches; seed_provider=[{class_name=org.apache.cassandra.locator.SimpleSeedProvider, parameters=[{seeds=<IP_ADDRESS>}]}]; server_encryption_options=<REDACTED>; snapshot_before_compaction=false; ssl_storage_port=7001; sstable_preemptive_open_interval_in_mb=50; start_native_transport=true; start_rpc=true; storage_port=7000; thrift_framed_transport_size_in_mb=15; tombstone_failure_threshold=100000; tombstone_warn_threshold=1000; trickle_fsync=false; trickle_fsync_interval_in_kb=10240; truncate_request_timeout_in_ms=60000; write_request_timeout_in_ms=2000]
INFO  09:05:04 JVM vendor/version: Java HotSpot(TM) 64-Bit Server VM/1.7.0_80
INFO  09:05:04 Heap size: 250544128/251592704
INFO  09:05:04 Code Cache Non-heap memory: init = 2555904(2496K) used = 710080(693K) committed = 2555904(2496K) max = 50331648(49152K)
INFO  09:05:04 Eden Space Heap memory: init = 51249152(50048K) used = 51249152(50048K) committed = 51249152(50048K) max = 51249152(50048K)
INFO  09:05:04 Survivor Space Heap memory: init = 6356992(6208K) used = 6356992(6208K) committed = 6356992(6208K) max = 6356992(6208K)
INFO  09:05:04 CMS Old Gen Heap memory: init = 192937984(188416K) used = 1050144(1025K) committed = 192937984(188416K) max = 193986560(189440K)
INFO  09:05:04 CMS Perm Gen Non-heap memory: init = 21757952(21248K) used = 15571264(15206K) committed = 21757952(21248K) max = 85983232(83968K)
INFO  09:05:04 Classpath: /etc/cassandra:/usr/share/cassandra/lib/ST4-4.0.8.jar:/usr/share/cassandra/lib/airline-0.6.jar:/usr/share/cassandra/lib/antlr-runtime-3.5.2.jar:/usr/share/cassandra/lib/commons-cli-1.1.jar:/usr/share/cassandra/lib/commons-codec-1.2.jar:/usr/share/cassandra/lib/commons-lang3-3.1.jar:/usr/share/cassandra/lib/commons-math3-3.2.jar:/usr/share/cassandra/lib/compress-lzf-0.8.4.jar:/usr/share/cassandra/lib/concurrentlinkedhashmap-lru-1.4.jar:/usr/share/cassandra/lib/disruptor-3.0.1.jar:/usr/share/cassandra/lib/guava-16.0.jar:/usr/share/cassandra/lib/high-scale-lib-1.0.6.jar:/usr/share/cassandra/lib/jackson-core-asl-1.9.2.jar:/usr/share/cassandra/lib/jackson-mapper-asl-1.9.2.jar:/usr/share/cassandra/lib/jamm-0.3.0.jar:/usr/share/cassandra/lib/javax.inject.jar:/usr/share/cassandra/lib/jbcrypt-0.3m.jar:/usr/share/cassandra/lib/jline-1.0.jar:/usr/share/cassandra/lib/jna-4.0.0.jar:/usr/share/cassandra/lib/json-simple-1.1.jar:/usr/share/cassandra/lib/libthrift-0.9.2.jar:/usr/share/cassandra/lib/logback-classic-1.1.2.jar:/usr/share/cassandra/lib/logback-core-1.1.2.jar:/usr/share/cassandra/lib/lz4-1.2.0.jar:/usr/share/cassandra/lib/metrics-core-2.2.0.jar:/usr/share/cassandra/lib/netty-all-4.0.23.Final.jar:/usr/share/cassandra/lib/reporter-config-2.1.0.jar:/usr/share/cassandra/lib/slf4j-api-1.7.2.jar:/usr/share/cassandra/lib/snakeyaml-1.11.jar:/usr/share/cassandra/lib/snappy-java-<IP_ADDRESS>.jar:/usr/share/cassandra/lib/stream-2.5.2.jar:/usr/share/cassandra/lib/super-csv-2.1.0.jar:/usr/share/cassandra/lib/thrift-server-0.3.7.jar:/usr/share/cassandra/apache-cassandra-2.1.8.jar:/usr/share/cassandra/apache-cassandra-thrift-2.1.8.jar:/usr/share/cassandra/apache-cassandra.jar:/usr/share/cassandra/cassandra-driver-core-<IP_ADDRESS>.jar:/usr/share/cassandra/netty-3.9.0.Final.jar:/usr/share/cassandra/stress.jar::/usr/share/cassandra/lib/jamm-0.3.0.jar

forge@kong:~$ cqlsh <IP_ADDRESS> 9042
Connection error: ('Unable to connect to any servers', {'<IP_ADDRESS>': error(111, "Tried connecting to [('<IP_ADDRESS>', 9042)]. Last error: Connection refused")})
forge@kong:~$ sudo cqlsh <IP_ADDRESS> 9042
Connection error: ('Unable to connect to any servers', {'<IP_ADDRESS>': error(111, "Tried connecting to [('<IP_ADDRESS>', 9042)]. Last error: Connection refused")})

It may take a while for Cassandra to start. Can you run sudo cassandra, wait 30 seconds, and then run cqlsh <IP_ADDRESS> 9042 ?

I will give it a try and wait for a while.
Thanks so far for your time, will keep you updated.

Tried running sudo cassandra and waited 10 minutes before running cqlsh <IP_ADDRESS> 9042.
But still without luck.
You got any other ideas?
forge@kong:~$ sudo cassandra
forge@kong:~$ INFO  09:08:50 Hostname: kong
INFO  09:08:50 Loading settings from file:/etc/cassandra/cassandra.yaml
INFO  09:08:50 Node configuration:[authenticator=AllowAllAuthenticator; authorizer=AllowAllAuthorizer; auto_snapshot=true; batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024; cas_contention_timeout_in_ms=1000; client_encryption_options=<REDACTED>; cluster_name=Test Cluster; column_index_size_in_kb=64; commit_failure_policy=stop; commitlog_directory=/var/lib/cassandra/commitlog; commitlog_segment_size_in_mb=32; commitlog_sync=periodic; commitlog_sync_period_in_ms=10000; compaction_large_partition_warning_threshold_mb=100; compaction_throughput_mb_per_sec=16; concurrent_counter_writes=32; concurrent_reads=32; concurrent_writes=32; counter_cache_save_period=7200; counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; cross_node_timeout=false; data_file_directories=[/var/lib/cassandra/data]; disk_failure_policy=stop; dynamic_snitch_badness_threshold=0.1; dynamic_snitch_reset_interval_in_ms=600000; dynamic_snitch_update_interval_in_ms=100; endpoint_snitch=SimpleSnitch; hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024; incremental_backups=false; index_summary_capacity_in_mb=null; index_summary_resize_interval_in_minutes=60; inter_dc_tcp_nodelay=false; internode_compression=all; key_cache_save_period=14400; key_cache_size_in_mb=null; listen_address=localhost; max_hint_window_in_ms=10800000; max_hints_delivery_threads=2; memtable_allocation_type=heap_buffers; native_transport_port=9042; num_tokens=256; partitioner=org.apache.cassandra.dht.Murmur3Partitioner; permissions_validity_in_ms=2000; range_request_timeout_in_ms=10000; read_request_timeout_in_ms=5000; request_scheduler=org.apache.cassandra.scheduler.NoScheduler; request_timeout_in_ms=10000; row_cache_save_period=0; row_cache_size_in_mb=0; rpc_address=localhost; rpc_keepalive=true; rpc_port=9160; rpc_server_type=sync; saved_caches_directory=/var/lib/cassandra/saved_caches; seed_provider=[{class_name=org.apache.cassandra.locator.SimpleSeedProvider, parameters=[{seeds=<IP_ADDRESS>}]}]; server_encryption_options=<REDACTED>; snapshot_before_compaction=false; ssl_storage_port=7001; sstable_preemptive_open_interval_in_mb=50; start_native_transport=true; start_rpc=true; storage_port=7000; thrift_framed_transport_size_in_mb=15; tombstone_failure_threshold=100000; tombstone_warn_threshold=1000; trickle_fsync=false; trickle_fsync_interval_in_kb=10240; truncate_request_timeout_in_ms=60000; write_request_timeout_in_ms=2000]
INFO  09:08:51 DiskAccessMode 'auto' determined to be mmap, indexAccessMode is mmap
INFO  09:08:51 Global memtable on-heap threshold is enabled at 59MB
INFO  09:08:51 Global memtable off-heap threshold is enabled at 59MB
INFO  09:08:51 Loading settings from file:/etc/cassandra/cassandra.yaml
INFO  09:08:51 Node configuration:[authenticator=AllowAllAuthenticator; authorizer=AllowAllAuthorizer; auto_snapshot=true; batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024; cas_contention_timeout_in_ms=1000; client_encryption_options=<REDACTED>; cluster_name=Test Cluster; column_index_size_in_kb=64; commit_failure_policy=stop; commitlog_directory=/var/lib/cassandra/commitlog; commitlog_segment_size_in_mb=32; commitlog_sync=periodic; commitlog_sync_period_in_ms=10000; compaction_large_partition_warning_threshold_mb=100; compaction_throughput_mb_per_sec=16; concurrent_counter_writes=32; concurrent_reads=32; concurrent_writes=32; counter_cache_save_period=7200; counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=5000; cross_node_timeout=false; data_file_directories=[/var/lib/cassandra/data]; disk_failure_policy=stop; dynamic_snitch_badness_threshold=0.1; dynamic_snitch_reset_interval_in_ms=600000; dynamic_snitch_update_interval_in_ms=100; endpoint_snitch=SimpleSnitch; hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024; incremental_backups=false; index_summary_capacity_in_mb=null; index_summary_resize_interval_in_minutes=60; inter_dc_tcp_nodelay=false; internode_compression=all; key_cache_save_period=14400; key_cache_size_in_mb=null; listen_address=localhost; max_hint_window_in_ms=10800000; max_hints_delivery_threads=2; memtable_allocation_type=heap_buffers; native_transport_port=9042; num_tokens=256; partitioner=org.apache.cassandra.dht.Murmur3Partitioner; permissions_validity_in_ms=2000; range_request_timeout_in_ms=10000; read_request_timeout_in_ms=5000; request_scheduler=org.apache.cassandra.scheduler.NoScheduler; request_timeout_in_ms=10000; row_cache_save_period=0; row_cache_size_in_mb=0; rpc_address=localhost; rpc_keepalive=true; rpc_port=9160; rpc_server_type=sync; saved_caches_directory=/var/lib/cassandra/saved_caches; seed_provider=[{class_name=org.apache.cassandra.locator.SimpleSeedProvider, parameters=[{seeds=<IP_ADDRESS>}]}]; server_encryption_options=<REDACTED>; snapshot_before_compaction=false; ssl_storage_port=7001; sstable_preemptive_open_interval_in_mb=50; start_native_transport=true; start_rpc=true; storage_port=7000; thrift_framed_transport_size_in_mb=15; tombstone_failure_threshold=100000; tombstone_warn_threshold=1000; trickle_fsync=false; trickle_fsync_interval_in_kb=10240; truncate_request_timeout_in_ms=60000; write_request_timeout_in_ms=2000]
INFO  09:08:51 JVM vendor/version: Java HotSpot(TM) 64-Bit Server VM/1.7.0_80
INFO  09:08:51 Heap size: 250544128/251592704
INFO  09:08:51 Code Cache Non-heap memory: init = 2555904(2496K) used = 724096(707K) committed = 2555904(2496K) max = 50331648(49152K)
INFO  09:08:51 Eden Space Heap memory: init = 51249152(50048K) used = 51249152(50048K) committed = 51249152(50048K) max = 51249152(50048K)
INFO  09:08:51 Survivor Space Heap memory: init = 6356992(6208K) used = 6356984(6207K) committed = 6356992(6208K) max = 6356992(6208K)
INFO  09:08:51 CMS Old Gen Heap memory: init = 192937984(188416K) used = 1047632(1023K) committed = 192937984(188416K) max = 193986560(189440K)
INFO  09:08:51 CMS Perm Gen Non-heap memory: init = 21757952(21248K) used = 15557416(15192K) committed = 21757952(21248K) max = 85983232(83968K)
INFO  09:08:51 Classpath: /etc/cassandra:/usr/share/cassandra/lib/ST4-4.0.8.jar:/usr/share/cassandra/lib/airline-0.6.jar:/usr/share/cassandra/lib/antlr-runtime-3.5.2.jar:/usr/share/cassandra/lib/commons-cli-1.1.jar:/usr/share/cassandra/lib/commons-codec-1.2.jar:/usr/share/cassandra/lib/commons-lang3-3.1.jar:/usr/share/cassandra/lib/commons-math3-3.2.jar:/usr/share/cassandra/lib/compress-lzf-0.8.4.jar:/usr/share/cassandra/lib/concurrentlinkedhashmap-lru-1.4.jar:/usr/share/cassandra/lib/disruptor-3.0.1.jar:/usr/share/cassandra/lib/guava-16.0.jar:/usr/share/cassandra/lib/high-scale-lib-1.0.6.jar:/usr/share/cassandra/lib/jackson-core-asl-1.9.2.jar:/usr/share/cassandra/lib/jackson-mapper-asl-1.9.2.jar:/usr/share/cassandra/lib/jamm-0.3.0.jar:/usr/share/cassandra/lib/javax.inject.jar:/usr/share/cassandra/lib/jbcrypt-0.3m.jar:/usr/share/cassandra/lib/jline-1.0.jar:/usr/share/cassandra/lib/jna-4.0.0.jar:/usr/share/cassandra/lib/json-simple-1.1.jar:/usr/share/cassandra/lib/libthrift-0.9.2.jar:/usr/share/cassandra/lib/logback-classic-1.1.2.jar:/usr/share/cassandra/lib/logback-core-1.1.2.jar:/usr/share/cassandra/lib/lz4-1.2.0.jar:/usr/share/cassandra/lib/metrics-core-2.2.0.jar:/usr/share/cassandra/lib/netty-all-4.0.23.Final.jar:/usr/share/cassandra/lib/reporter-config-2.1.0.jar:/usr/share/cassandra/lib/slf4j-api-1.7.2.jar:/usr/share/cassandra/lib/snakeyaml-1.11.jar:/usr/share/cassandra/lib/snappy-java-<IP_ADDRESS>.jar:/usr/share/cassandra/lib/stream-2.5.2.jar:/usr/share/cassandra/lib/super-csv-2.1.0.jar:/usr/share/cassandra/lib/thrift-server-0.3.7.jar:/usr/share/cassandra/apache-cassandra-2.1.8.jar:/usr/share/cassandra/apache-cassandra-thrift-2.1.8.jar:/usr/share/cassandra/apache-cassandra.jar:/usr/share/cassandra/cassandra-driver-core-<IP_ADDRESS>.jar:/usr/share/cassandra/netty-3.9.0.Final.jar:/usr/share/cassandra/stress.jar::/usr/share/cassandra/lib/jamm-0.3.0.jar

forge@kong:~$ cqlsh <IP_ADDRESS> 9042
Connection error: ('Unable to connect to any servers', {'<IP_ADDRESS>': error(111, "Tried connecting to [('<IP_ADDRESS>', 9042)]. Last error: Connection refused")})

Can you execute java -version?

$ java -version
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)

Okay so this is very weird. Let's try one more thing. In your Kong configuration can you use the following Cassandra properties:
cassandra:
  properties:
    hosts: ec2-52-7-33-160.compute-1.amazonaws.com
    port: 32809
    timeout: 2000
    keyspace: kong
    keepalive: 60000

Then I get
$ kong start
[INFO] Using configuration: /etc/kong/kong.yml
[INFO] Kong version.......0.3.2
       Proxy HTTP port....8000
       Proxy HTTPS port...8443
       Admin API port.....8001
       dnsmasq port.......8053
       Database...........cassandra keepalive=60000 hosts=ec2-52-7-33-160.compute-1.amazonaws.com port=32809 timeout=2000 keyspace=kong
[INFO] Connecting to the database...
[ERR] Permission denied /usr/local/kong/

Wait, with sudo kong start I get
[INFO] Using configuration: /etc/kong/kong.yml
[INFO] Kong version.......0.3.2
       Proxy HTTP port....8000
       Proxy HTTPS port...8443
       Admin API port.....8001
       dnsmasq port.......8053
       Database...........cassandra keepalive=60000 hosts=ec2-52-7-33-160.compute-1.amazonaws.com port=32809 timeout=2000 keyspace=kong
[INFO] Connecting to the database...
[INFO] dnsmasq started
[WARN] ulimit is currently set to "1024". For better performance set it to at least "4096" using "ulimit -n"
[OK] Started

So, it might be a error related to my Cassandra and not Kong.

More tests:
forge@kong:~$ cqlsh ec2-52-7-33-160.compute-1.amazonaws.com 32809
Connected to Test Cluster at ec2-52-7-33-160.compute-1.amazonaws.com:32809.
[cqlsh 5.0.1 | Cassandra 2.1.4 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh> exit;
forge@kong:~$ cqlsh <IP_ADDRESS> 9042
Connection error: ('Unable to connect to any servers', {'<IP_ADDRESS>': error(111, "Tried connecting to [('<IP_ADDRESS>', 9042)]. Last error: Connection refused")})

The local Cassandra installation seems to be broken somehow. It's 3am here, I will follow up tomorrow on this thread.

I will try to build another server and look for a guide for installation for Linux 14.04.
Sleep well and thanks for your time.

@marktopper any news?

@marktopper I wrote a guide for installing Kong on a base Ubuntu 14.04 image awhile back, it includes a section for getting Cassandra running locally. Here it is:
# Install Cassandra
wget http://apache.mirrors.tds.net/cassandra/2.1.5/apache-cassandra-2.1.5-bin.tar.gz
tar xvzf apache-cassandra-2.1.5-bin.tar.gz
./apache-cassandra-2.1.5/bin/cassandra

You could also put the bin directory in your path or make use of tools like init or upstart to start, stop and restart Cassandra as well as keep it running in case of reboots or crashes.

I will close this issue because it's specific to Cassandra and not Kong. But we can keep commenting on it to fix the problem.

I managed to get it to work.
It seemed like Cassandra was broken so I installed it this way:
https://gist.github.com/marktopper/57af0232db757971e5f7

Thanks for writing that Gist file, I will take it and put it on the getkong.org website just in case other people wonder how to install Cassandra.

:+1: Thanks to you as well.

Hi thefosk

How to configure my own Cassandra in kong.yml file

@muppudathis-tzl https://getkong.org/docs/0.6.x/configuration/#cassandra

Not ready to Connect to a Cassandra Remote Server? Contact to Cassandra Database Consulting and Support
The capacities of Cassandra database are astonishing in light of the fact that Cassandra can deal with vast measure of database with no multifaceted nature. In the mean time we get loads of inquiries and issues in regards to those clients who face issue with respect to Cassandra remote server since they are not ready to associate with Cassandra remote server. To dispose of these specialized hiccups we give full help by means of Cognegic's Cassandra Technical Support or Cassandra Database Support. Get in touch with us through this number 1-800-450-8670 and settle everything Cassandra related issues.
For More Info: https://cognegicsystems.com/
Contact Number: 1-800-450-8670
Email Address-<EMAIL_ADDRESS>Company’s Address- 507 Copper Square Drive Bethel Connecticut (USA) 06801


Windows fs__symlink creates invalid junctions when targeting soft directory links

Creating the following link under Windows results in a "File not found" error when trying to use it:
mkdir a
mklink /d b a
node -e fs.symlinkSync('b','c','junction')
Running
dir c
results in 'File Not Found'.
When using mklink instead of node to create link c, no errors occur:
rmdir c
mklink /j c b
The main difference between the link created by node (via libuv) and mklink can be seen from the output of fsutil.
For libuv the output of "fsutil reparsePoint query c" is
Reparse Tag Value : 0xa0000003
Tag value: Microsoft
Tag value: Name Surrogate
Tag value: Mount Point
Substitue Name offset: 0
Substitue Name length: 76
Print Name offset:     78
Print Name Length:     66
Substitute Name:       ??\C:\Users\Andreas\Documents\test\b
Print Name:            C:\Users\Andreas\Documents\test\b
For mklink it is
Reparse Tag Value : 0xa0000003
Tag value: Microsoft
Tag value: Name Surrogate
Tag value: Mount Point
Substitue Name offset: 0
Substitue Name length: 74
Print Name offset:     76
Print Name Length:     66
Substitute Name:       ??\C:\Users\Andreas\Documents\test\b
Print Name:            C:\Users\Andreas\Documents\test\b
Notice the trailing slash of substitute name in the libuv link. That trailing slash is added by fs__symlink in src/win/fs.c and doesn't appear to cause any problems when targeting actual directories, but for a soft directory link (mklink /d) it does not work. The soft link doesn't have to be the actual target but can be anywhere on the targeted path for the problem to exhibit.
Should the trailing slash be removed? What was its original purpose? There is no mention in the Windows API documentation that requiring it.

Version: 1.41.0
Platform: Windows, 10.0.19043 Build 19043
Node Version: v14.17.6

Your analysis sounds plausible, pull request welcome. I think the relevant code is around here (might also be about 20 lines lower):
https://github.com/libuv/libuv/blob/6564ccc90073296769ac17319bba3f3357005603/src/win/fs.c#L2419-L2433

It would we important to first establish why the trailing backslash was added in the first place.


Failed to instantiate module ng due to: TypeError: Cannot set property 'aHrefSanitizationWhitelist' of null when code migrating from 1.4.8 to 1.7.8

I am getting the error when I try to migrate from 1.4.8 to 1.7.8.  When I debugged it $$SanitizeUriProvider getting null when below method executed.
function instantiate(Type, locals, serviceName) {
// Check if Type is annotated and use just the given function at n-1 as parameter
// e.g. someModule.factory('greeter', ['$window', function(renamed$window) {}]);
var ctor = (isArray(Type) ? Type[Type.length - 1] : Type);
var args = injectionArgs(Type, locals, serviceName);
// Empty object at position 0 is ignored for invocation with new, but required.
args.unshift(null);
return new (Function.prototype.bind.apply(ctor, args))();
}
Please help me if any dependencies I missed in this scenario.
Below are my bower.json, package.json files.
Bower.json
{
"name": "test",
"authors": [
"Test",
"IT Development",
"testfds"
],
"license": "proprietary",
"dependencies": {
"angular": "1.7.8",
"angular-resource": "1.7.8",
"angular-route": "1.7.8",
"angular-bootstrap": "^1.0.0",
"ng-prettyjson": "^0.1.9",
"spin.js": "^2.0.1",
"angular-sanitize": "1.7.8",
"angular-spinner": "^0.6.1",
"angular-apimock": "^0.3.3",
"moment": "^2.19.2"
},
"resolutions": {
"angular": "1.7.8"
}
}
Package.json
"devDependencies": {
"angular-mocks": "1.7.8",
"chai": "^3.2.0",
"grunt": "^0.4.5",
"grunt-bowercopy": "^1.2.3",
"grunt-cli": "^0.1.13",
"grunt-contrib-clean": "^0.6.0",
"grunt-contrib-concat": "^0.5.1",
"grunt-contrib-connect": "^0.11.2",
"grunt-contrib-copy": "^0.8.0",
"grunt-contrib-jshint": "^0.11.3",
"grunt-contrib-less": "^1.0.1",
"grunt-contrib-uglify": "^0.9.1",
"grunt-contrib-watch": "^0.6.1",
"grunt-env": "^0.4.4",
"grunt-karma": "^0.12.0",
"karma-chai": "^0.1.0",
"karma-coverage": "^1.1.1",
"karma-junit-reporter": "^0.3.3",
"karma-mocha": "^0.2.0",
"karma-mocha-reporter": "^1.1.1",
"karma-phantomjs-launcher": "^0.2.1",
"karma-sinon": "^1.0.4",
"mocha": "^2.2.5",
"phantomjs": "^1.9.18",
"phantomjs-polyfill": "0.0.2",
"sinon": "^1.15.4"
}

This sounds like a general support question. Please, use one of the appropriate support channels for these types of questions.
GitHub issues are reserved for bug reports and feature requests.
Thx!


fix: set output with tag

#54  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rswanson and the rest of your teammates on  Graphite

Merge activity

Nov 5, 4:36 PM EST: A user started a stack merge that includes this pull request via Graphite.


Hugo minify generates sizing problem on multilingual switch

What happened?
Using the latest version of the theme, latest hugo on Netlify, when using the --minify option, this will generate a sizing problem, removing the space between the title and the language switch.
With --minify

On hugo server and without using --minify

This problem is also reported when analyzing the webpage with web.dev

This is fixed when modifying netlify.toml and removing the --minify option.
PS: My netlify.toml is modified to use the latest version of hugo + the latest version of go. This error is still happening on the default toml version.
Theme version
v2.3.1
Hugo version
v0.102.3
What browsers are you seeing the problem on?
Chrome
Relevant Hugo log output
10:50:01 PM: Build ready to start
10:50:03 PM: build-image version: d7b3dbfb0846505993c9a131894d1858074c90b4 (focal)
10:50:03 PM: build-image tag: v4.10.1
10:50:03 PM: buildbot version: 1c362ef848ac5e35535bdb572ebca893db28c8a0
10:50:03 PM: Fetching cached dependencies
10:50:03 PM: Starting to download cache of 135.9MB
10:50:04 PM: Finished downloading cache in 1.082591558s
10:50:04 PM: Starting to extract cache
10:50:05 PM: Finished extracting cache in 824.279799ms
10:50:05 PM: Finished fetching cache in 1.986041125s
10:50:05 PM: Starting to prepare the repo for build
10:50:05 PM: Preparing Git Reference refs/heads/main
10:50:06 PM: Parsing package.json dependencies
10:50:06 PM: Different build command detected, going to use the one specified in the Netlify configuration file: 'hugo mod get -u && hugo --gc --minify -b $URL' versus 'hugo mod get -u && hugo' in the Netlify UI
10:50:06 PM: Starting build script
10:50:06 PM: Installing dependencies
10:50:06 PM: Python version set to 2.7
10:50:06 PM: Started restoring cached node version
10:50:07 PM: Finished restoring cached node version
10:50:08 PM: v16.17.0 is already installed.
10:50:08 PM: Now using node v16.17.0 (npm v8.15.0)
10:50:08 PM: Started restoring cached build plugins
10:50:08 PM: Finished restoring cached build plugins
10:50:08 PM: Attempting ruby version 2.7.2, read from environment
10:50:09 PM: Using ruby version 2.7.2
10:50:09 PM: Using PHP version 8.0
10:50:09 PM: Installing Hugo 0.102.3
10:50:10 PM: hugo v0.102.3-b76146b129d7caa52417f8e914fc5b9271bf56fc+extended linux/amd64 BuildDate=2022-09-01T10:16:19Z VendorInfo=gohugoio
10:50:10 PM: Started restoring cached go cache
10:50:10 PM: Finished restoring cached go cache
10:50:10 PM: Installing Go version 1.19.1 (requested 1.19.1)
10:50:16 PM: unset GOOS;
10:50:16 PM: unset GOARCH;
10:50:16 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.19.1.linux.amd64';
10:50:16 PM: export PATH="/opt/buildhome/.gimme/versions/go1.19.1.linux.amd64/bin:${PATH}";
10:50:16 PM: go version >&2;
10:50:16 PM: export GIMME_ENV="/opt/buildhome/.gimme/env/go1.19.1.linux.amd64.env"
10:50:16 PM: go version go1.19.1 linux/amd64
10:50:16 PM: Installing missing commands
10:50:16 PM: Verify run directory
10:50:17 PM:
10:50:17 PM: ────────────────────────────────────────────────────────────────
10:50:17 PM:   Netlify Build
10:50:17 PM: ────────────────────────────────────────────────────────────────
10:50:17 PM:
10:50:17 PM: ❯ Version
10:50:17 PM:   @netlify/build 27.18.4
10:50:17 PM:
10:50:17 PM: ❯ Flags
10:50:17 PM:   baseRelDir: true
10:50:17 PM:   buildId: 632a6dc9a91c370008a14083
10:50:17 PM:   deployId: 632a6dc9a91c370008a14085
10:50:17 PM:
10:50:17 PM: ❯ Current directory
10:50:17 PM:   /opt/build/repo
10:50:17 PM:
10:50:17 PM: ❯ Config file
10:50:17 PM:   /opt/build/repo/netlify.toml
10:50:17 PM:
10:50:17 PM: ❯ Context
10:50:17 PM:   production
10:50:17 PM:
10:50:17 PM: ────────────────────────────────────────────────────────────────
10:50:17 PM:   1. build.command from netlify.toml
10:50:17 PM: ────────────────────────────────────────────────────────────────
10:50:17 PM:
10:50:17 PM: $ hugo mod get -u && hugo --gc --minify -b $URL
10:50:18 PM: Start building sites …
10:50:18 PM: hugo v0.102.3-b76146b129d7caa52417f8e914fc5b9271bf56fc+extended linux/amd64 BuildDate=2022-09-01T10:16:19Z VendorInfo=gohugoio
10:50:18 PM:                    | EN | ES
10:50:18 PM: -------------------+----+-----
10:50:18 PM:   Pages            | 12 |  8
10:50:18 PM:   Paginator pages  |  0 |  0
10:50:18 PM:   Non-page files   |  0 |  0
10:50:18 PM:   Static files     | 13 | 13
10:50:18 PM:   Processed images |  0 |  0
10:50:18 PM:   Aliases          |  3 |  1
10:50:18 PM:   Sitemaps         |  2 |  1
10:50:18 PM:   Cleaned          |  0 |  0
10:50:18 PM: Total in 70 ms
10:50:18 PM:
10:50:18 PM: (build.command completed in 364ms)
10:50:18 PM:
10:50:18 PM: ────────────────────────────────────────────────────────────────
10:50:18 PM:   2. Deploy site
10:50:18 PM: ────────────────────────────────────────────────────────────────
10:50:18 PM:
10:50:18 PM: Starting to deploy site from 'public'
10:50:18 PM: Creating deploy tree
10:50:18 PM: Creating deploy upload records
10:50:18 PM: 11 new files to upload
10:50:18 PM: 0 new functions to upload
10:50:18 PM: Site deploy was successfully initiated
10:50:18 PM:
10:50:18 PM: (Deploy site completed in 508ms)
10:50:18 PM:
10:50:18 PM: ────────────────────────────────────────────────────────────────
10:50:18 PM:   Netlify Build Complete
10:50:18 PM: ────────────────────────────────────────────────────────────────
10:50:18 PM:
10:50:18 PM: (Netlify Build completed in 893ms)
10:50:18 PM: Starting post processing
10:50:18 PM: Caching artifacts
10:50:18 PM: Started saving build plugins
10:50:18 PM: Finished saving build plugins
10:50:18 PM: Started saving pip cache
10:50:18 PM: Finished saving pip cache
10:50:18 PM: Started saving emacs cask dependencies
10:50:18 PM: Finished saving emacs cask dependencies
10:50:18 PM: Started saving maven dependencies
10:50:19 PM: Finished saving maven dependencies
10:50:19 PM: Started saving boot dependencies
10:50:19 PM: Post processing - HTML
10:50:19 PM: Finished saving boot dependencies
10:50:19 PM: Started saving rust rustup cache
10:50:19 PM: Finished saving rust rustup cache
10:50:19 PM: Started saving go dependencies
10:50:19 PM: Finished saving go dependencies
10:50:19 PM: Build script success
10:50:19 PM: Uploading Cache of size 152.7MB
10:50:19 PM: Post processing - header rules
10:50:19 PM: Post processing - redirect rules
10:50:20 PM: Post processing done
10:50:20 PM: Finished processing build request in 17.684004733s
10:50:22 PM: Site is live ✨

Thanks for the report. I'll address this in a future update.


End-to-end tests and Integrations

What
We are currently missing proper end-to-end/integration tests across our supported language stack. Primarily due to things like #528. We need to ensure we have representative coverage across the language stack.
Why
Without proper coverage, it is easy to miss things such as #582 - which rely on us not making a mistake in python bindings. We need to ensure we dog-food the API across all supported language stacks.
ACs

Stand-alone Integration tests, using only public API/infrastructure (no stubs) covering:

C++ host to BAL
Python host to BAL
C host to Python manager (limited to currently supported methods)

Closing in favour of direct tickets for real tasks. Since we wrote his we have better coverage through integrations.yml, but still a lot to do.


Remove referrals function

Our backend no longer supports this functionality. It was a mistake to have this present in docs. @jsaleigh

:+1:


Feature request: support for query parameterization

Rationale:https://www.owasp.org/index.php/LDAP_injection
search_options.filter could be vulnerable to untrusted input.  Depending on the application, obviously.

Got a good, complete sanitizer function handy? I'd include if I knew it was 100% correct, but am happy leaving sanitization up to the developer if not.

Included in 3.1.X


That took hours to run on travis.


real_gene_name is lost after merging two gef file

When I use st.io.read_gef to read a gef file, there is a genes attribute and under which there are gene_name and real_gene_name. The gene_name is actually Ensembl gene ID like 'ENSG00000000003' while the real_gene_name is gene symbol like 'TSPAN6'.
However, when I merge two gef file using MSData, the real_gene_name under ms_data.merged_data.genes becomes None.
Is this a bug or a feature? How can I get the gene symbols back?

Sorry, that is a bug, if you don't need the geneID, you can set the parameter gene_name_index to True when reading data via st.io.read_gef, the gene symbols will be used as gene_name under the attribute gene.

I'm using 1.3.1 but still have this bug

I'm using 1.3.1 but still have this bug

Sorry, that is a bug, if you don't need the geneID, you can set the parameter gene_name_index to True to set gene symbols as gene_name which is under the genes attribute.

Thank you for your clarification. Unfortunately I need both gene ID and gene symbol. Do you have any plan to fix it?

A new version will be released around the end of August, currently, you can do like the following codes to solve this problem
for data in ms_data.data_list:
    ms_data.merged_data.genes.var['real_gene_name'] = data.genes.var['real_gene_name']

A new version will be released around the end of August, currently, you can do like the following codes to solve this problem
for data in ms_data.data_list:
    ms_data.merged_data.genes.var['real_gene_name'] = data.genes.var['real_gene_name']

Adding these lines after ms_data.integrate() solves my problem, thank you!


[Toothpick] Device support form

Extension – Toothpick
Hope this helps ;)
Device brand and model
Sony WH-1000XM4
Device data
{
	"WH-1000XM4": {
		"device_address": "14:3F:A6:BC:78:F4",
		"device_firmwareVersion": "2.5.0",
		"device_minorType": "Headset",
		"device_productID": "0x0D58",
		"device_services": "0x800019 < HFP AVRCP A2DP ACL >",
		"device_vendorID": "0x054C",
		"device_connected": "true"
	}
}

It seemed to be recognized out of the box, but no fancy features like battery levels etc. Happy to help further if you need to debug anything, @VladCuciureanu.

Hey! Thanks for this submission. So, this device is mapped in the latest version but to explain the current situation a bit...
The BlueTooth api we have access to is kinda limited.
Some devices share battery levels along with the rest of the device's metadata, in which case we display them.
Otherwise, if the device sends the battery level via other methods, we have no current way to fetch them.
Sadly, for WH-1000XM4, the case is the latter.
I have a companion app planned, kind of like a bridge that would give this extension access to more functionalities, like fetching battery levels, toggling ANC, etc. But for now it's just that. A plan.
Either way, any submission is helpful and appreciated. Have a nice day! 🌻

If I remember ble correctly, you’ll have to actually go talk to a service advertised in the metadata over ble, right?

If I remember ble correctly, you’ll have to actually go talk to a service advertised in the metadata over ble, right?

Yep. Something like that


Feature: SAST tool run on PR should count more than those run after merge

See https://github.com/ossf/scorecard/issues/1031#issuecomment-969117938
(Additional long-term improvements are in https://github.com/ossf/scorecard/issues/966#issuecomment-915598041)
We would like to give more points to repos that run SAST before merging code, i.e. on pull_request event.

@evverx FYI

I'm not sure whether it's the right place to mention this issue with the checks analyzing PRs but since I've run into it mostly using the SAST check I think it would probably make sense to switch from the "n out of 30 PRs have something" approach to something that would account for glitches preventing status checks from being registered properly or weird results that GH API returns once in a while. Otherwise it seems even if projects where SASTs are run on PRs were rated higher they would most likely loose some points anyway due to what looks like transient GH issues.

For example, LGTM was run in https://github.com/libbpf/libbpf/pull/353 but GH API says that it wasn't.

One option would be to figure out whether LGTM is listed among the apps that can be triggered on pull requests with https://docs.github.com/en/rest/reference/checks#get-a-check-suite and if it's there and it is run in the majority of pull requests it should be safe to say that projects are analyzed with LTGM. I'm not sure about other apps though

I'm not sure whether it's the right place to mention this issue with the checks analyzing PRs but since I've run into it mostly using the SAST check I think it would probably make sense to switch from the "n out of 30 PRs have something" approach to something that would account for glitches preventing status checks from being registered properly or weird results that GH API returns once in a while. Otherwise it seems even if projects where SASTs are run on PRs were rated higher they would most likely loose some points anyway due to what looks like transient GH issues.

@josepalafox is this a known issue with GitHub APIs?

One option would be to figure out whether LGTM is listed among the apps that can be triggered on pull requests with https://docs.github.com/en/rest/reference/checks#get-a-check-suite and if it's there and it is run in the majority of pull requests it should be safe to say that projects are analyzed with LTGM. I'm not sure about other apps though

with this API, looks like we could get the last N pushes that have used it; and we'd need to map them to the last PRs. Is my understanding correct? That sound doable.
Are there limitation in terms of whom can use this API: GitHub Apps must have the checks:read permission on a private repository or pull access to a public repository to get check suites. OAuth Apps and authenticated users must have the repo scope to get check suites in a private repository. Is it accessible by non-apps?

summary:

tool configured (codeQl) and runs as cron => give some point (we already do this )
tool configured on each push => increase the score (we don't do this)
tool configured on pull request => increase score (we do this)

tool configured on each push => increase the score (we don't do this)

It should probably be "on every PR". systemd for example doesn't run SASTs on push events. It runs LGTM on PRs and CodeQL and Coverity once a day due their various limitations.

ah, right. Agreed.


[tracing] Update jaeger exporter version to 0.6.0. Update grpc-okhttp to 1.29.0.

Thank you very much @pujagani


proposal: x/crypto/bcrypt: make compatible with OpenBSD

Currently, the golang bcrypt implementation only allows for hash Generation using GenerateFromPassword which automatically generates the salt. The original OpenBSD implementation has the bcrypt_gensalt(u_int8_t log_rounds); and bcrypt(const char *key, const char *salt); functions. We already attempt to make the golang implementation compatible with the c implementation.
OpenBSD: https://nixdoc.net/man-pages/OpenBSD/man3/bcrypt.3.html
I propose we add equivalent functions to the OpenBSD ones to allow for interoperability. I have already made an equivalent for the bcrypt(const char *key, const char *salt); function, which you can find here

Are there any concrete use cases for this?
related #18737

I have one!
I wrote a wrapper around the Enzoic password API, which, as part of its API, requires the caller to compute a bcrypt hash with a given salt. https://www.enzoic.com/docs-credentials-api/#hash-based-credentials-step-3.
In order to implement the client in go, I had to fork the bcrypt package and add a function very similar to the one linked above.

@FiloSottile any opinions on adding GenerateFromPasswordAndSalt?

A few other notes on this:
It has been proposed before: #18737. The use-cases presented in that proposal did not inspire... confidence... that this API will be used responsibly.
I personally think having the option is valuable (although it's really going to be valuable for people doing weird things with password management, as my use-case above illustrates), but it certainly should be gated with some big warning signs that "you probably just want to use GenerateFromPassword, only provide your own salt if you're certain it's sufficiently random, etc etc".

/cc @FiloSottile

/cc @FiloSottile @katiehockman @rolandshoemaker

It seems like there are still pretty limited use cases for this functionality, API compatibility with OpenBSD is nice, but I'm not really sure what else it gets us beyond API parity.
This is a dangerous API to add, and if we have to add a large "this is dangerous, please use it only if you know what you're doing" warning, it seems more prudent to just not implement it in the first place.

thanks @rolandshoemaker

Based on the discussion above, this proposal seems like a likely decline.
— rsc for the proposal review group

Disappointing, but understandable. I suppose I'll have to maintain my little fork.

No change in consensus, so declined.
— rsc for the proposal review group


adding methods with decorator type does not exist

Any native feature?
Current solution.
https://stackoverflow.com/questions/48599889/typescript-adding-methods-with-decorator-type-does-not-exist

To expedite the triage process, we need everyone to follow the issue template and instructions.
When you clicked "Create New Issue", the issue form was pre-populated with a template and some instructions. We need you to read those instructions completely, follow them, and then fill in all the fields in that template.
We are not able to assist with issues that don't follow the template instructions as they represent a significantly larger amount of work compared to issues which are correctly specified. Thank you for understanding.


Update token server error test to not fail on retries

Instead of having the misconfigured token server test
fail after maxing out retries, only retry once then
return an error which will not retry.
Referenced by #19425

Investigating why this test now seems to fail when run with the rest of the DockerRegistrySuite tests.

CI is now passing. Updated to force multiple retries, when not run in isolation the test appears to sometimes skip the retry output. Not sure if there is a race since I was not able to root cause but doing multiple retries ensures that there is retry output.

ping @tonistiigi @aaronlehmann PTAL

LGTM

LGTM


newer character files failing

I have a recently created CHF file from 3.24.2 and drag/drop is giving an error saying it is an invalid file. Guessing the newer tattoo and other attribute values aren't accounted for.

I don't have PTU access so I can't really add more things to this. Once I do I can look into it.


React dnd can't find installed react

Hi, sorry if this is a noob question, I am just starting with React.
I am trying to use react-dnd (drag and drop) package and it seems not be able to find react?
npm WARN EPEERINVALID<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

I've updated to the latest gem from github, but its the same problem.
Not sure whats the right thing to do here.

Run this in the /client folder: npm i --save react
NPM dependencies are handled by package.json.


Support for Cloudlinux OS

Hello Nyr,
I've installed OpenVPN on my centos some weeks ago and everything working like a charm. Some days ago I converted my OS from centos to cloudlinux os (I'm also using my vps for hosting purpose) and I got that I can't add/remove OpenVPN's users anymore!!
You know, script does not work anymore for adding/removing users; but OpenVPN still working for current users like a charm.
May you please add a patch to support cloudlinux OS?
Thank you.

CloudLinux OS is not supported.
No idea where it breaks the script, but it is difficult to consider a fix because I am not able to easily get an installation of this commercial distribution to test.


Allow keyValueOverride to be dynamic

This allows keyValueOverride to be a dynamically generated string based on the value of the prop.
jsxToString(<Test prop1={'Hello'} />, { keyValueOverride: { prop1(value) { return value + ' World'; } }});
// <Test prop1='Hello World' />

@grommet I'm also thinking of adding a change to this PR that changes the string serialization from using single ' quotes to double " quotes, given that is the React convention.

thanks for your contribution!

In my project we use single quote for everything including JSX. Maybe you can create a separate pull request to add support for that as a configurable option?
jsxToString(<Test prop1={'Hello'} />, { doubleQuote: true }) ?

FYI, I've released jsx-to-string 1.0.2 with support for this.

Thanks for releasing this! We are currently working with a fork of this project but will work on getting the main version incorporated again. As far as the doubleQuote option, that sounds reasonable though I'm not sure when I'll get an opportunity to work on that.


Release the latest package on npm?

Users have been asking me to add theme here and I did.
Can you folks release the latest pkg on npm?
https://www.npmjs.com/package/prism-themes
It's outdated.

Yeah, that'd be great.
@mAAdhaTTah
But could we get #79 before that? It's just sitting there, all alone, rebased, and ready to merge.

Approved that. There's also #84 for screenshots, but there's some massaging to be done there.

Yes, but #84 is only a readme change, so I don't think that we need to delay the release.
Also, could please also merge #79. I'm not listed as a collaborator for this project, so I can't.

Done. Will release when I'm home.
The README change might be nice for npm but not a requirement.

Nice!

The README change might be nice for npm but not a requirement.

Exactly what I was thinking.
I'll review #84, so we can merge it then.

Published.


3D structure generation for big (> ~ 100 non-hydrogen atoms) molecules

As I'm working with natural glycans, I need to generate 3D coordinates of molecules containing up to 200 non-hydrogen atoms. However, both 3D structure generation algorithms (default and ETKDG) are not able to generate 3D coordinates for big molecules, e.g. hectane C100H202:
mol = Chem.AddHs(Chem.MolFromSmiles('C'*100))
AllChem.EmbedMolecule(mol, maxAttempts = 10000)
Out[15]: -1

It would be great, if this opportunity will appear in future versions.

For large molecules, it's a good idea to use the useRandomCoords keyword argument to EmbedMolecule():
AllChem.EmbedMolecule(mol, useRandomCoords=True)

On my linux box C100H202 embeds in about 2 seconds using random coords.
Note that the time required for embedding increases rapidly with molecular size - C200H402 takes about 17s.
Unless you plan a molecular mechanics minimization of the conformations, it's generally a good idea to use the ETKDG parameter set:
params = AllChem.ETKDG()
params.useRandomCoords=True
AllChem.EmbedMolecule(mol, params)

This takes a bit longer (4 seconds for the C100 case), but the conformations are significantly better.

Thank you very much for the prompt reply!


Fix sign in persistence issue

Fixing Persistence Issue in UserProfile

@MSFT-Heba,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Error creating environment

I'm trying to create conda environment on Ubuntu 16.04, it keeps giving this error:
Fetching package metadata ...............
ResolvePackageNotFound:
  - opencv3

Looks like you've resolved this already; closing out.


Yaml stages

Description
This is a planned change to onboard to yaml stages.
Customer Impact
Infra-structure change.
Regression?
No.
Risk
Low

Good catch @rainersigwald. I was missing a property on CIBuild.cmd. Added that. I am re-running the pipeline and will retry the test insertion.

The default channel for Livar's test branch is tied to the ".Net tools - validation" channel.
https://github.com/microsoft/msbuild @ refs/heads/yaml_stages -> .NET Tools - Validation
This is what causes the validation channel stage to trigger, and the dev channel stage to be skipped.

https://github.com/microsoft/msbuild/pull/4613/files#diff-64b68deede22be689a5c5a1dc02a7087R15-R16 configures the assets to be marked as validation assets, so they go into the arcade-validation feed.

The publish packages to azdo feed step get skipped as for now, all channels publish to an azure blob feed and not an azure devops artifacts feed.

You can see the actual publishing happening in the "add assets location" step: https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=2944334&view=logs&j=841c9107-1508-5744-5f38-ba9581e84f26&t=3d448e79-a526-559e-582a-2d42509f1233&l=96

Everything in that build looks normal

The default channel for Livar's test branch is tied to the ".Net tools - validation" channel.
https://github.com/microsoft/msbuild @ refs/heads/yaml_stages -> .NET Tools - Validation
This is what causes the validation channel stage to trigger, and the dev channel stage to be skipped.

Can you teach me to fish on this part? Where does this mapping live?

The default channel for Livar's test branch is tied to the ".Net tools - validation" channel.
https://github.com/microsoft/msbuild @ refs/heads/yaml_stages -> .NET Tools - Validation
This is what causes the validation channel stage to trigger, and the dev channel stage to be skipped.
Can you teach me to fish on this part? Where does this mapping live?

Sure! I just got it using darc
darc get-default-channels --source-repo msbuild
(410)  https://github.com/microsoft/msbuild @ refs/heads/yaml_stages -> .NET Tools - Validation
(25)   https://github.com/Microsoft/msbuild @ refs/heads/master -> .NET Core 3 Dev
(88)   https://github.com/Microsoft/msbuild @ refs/heads/vs16.0 -> .NET Core 3 Release

Ah, so a channel must exist and be defined (externally to the job itself) for the publish to work, and we have one defined for this branch and for master, and a stale one we should delete for 16.0? Ok.


Unable to play any music

Attempting to play anything on Chromium browsers brings up multiple Media Playback Error: An error occurred during media playback. per playlist I press play on and also one Unexpected Error: An unexpected error occurred. per song I attempt to play.

Same problem here, I been using the app on Chrome for a few days now and it just stopped working, I tried another PC other browsers and re-authorizing the app to my Apple ID however none of these work, the only thing that happens is that it ''loads'' the song forever but not even the gray loading bar appears

Thanks for the report @FurkanToprak and @Datsuke.
I just tested myself on Safari and Chrome on my Mac, and I don't have any issues. Can you provide some additional information:

Operating system
Country
Do song previews work when logged out?
Do you have the same issue with https://tools.applemusic.com/? There's a signin button when you open up a library or playlist
Are there are any errors in the Developer Tools console?

Windows 10 1809 on build 17763.316
Apple ID is from Mexico however connection is made through a VPN connected to the US
Google Chrome Version 72.0
Same issue with song previews
No issues while playing media through tools.applemusic
ncaught (in promise) UNKNOWN_ERROR: UNKNOWN_ERROR     at Function.MKError.serverError (https://js-cdn.music.apple.com/musickit/v1/musickit.js:1:25749)     at EncryptedSession.KeySession._handleLicenseResponse (https://js-cdn.music.apple.com/musickit/v1/musickit.js:1:104916)     at https://js-cdn.music.apple.com/musickit/v1/musickit.js:1:103100 MKError @ musickit.js:1 MKError.serverError @ musickit.js:1 KeySession._handleLicenseResponse @ musickit.js:1 (anonymous) @ musickit.js:1 Promise.then (async) KeySession.startLicenseSession @ musickit.js:1 t @ raven.js:376
this is all I get after clearing the console and making a request

Are you able to look at the network tab and see if there are requests failing? Looks like something is failing with MusicKit JS when it get the keys for the encrypted media session (cc/ @jaehess)

Same issue here!

I found a fix, deleting all localStorage data seems to have fixed it for me. I've been using this since it was launched so there may have been some old date there.

Thanks for sharing @msjyoo
@Datsuke can you try clearing all the local storage and seeing if it resolves the issue for you too?

@zachomedia It worked! once I deleted local storage and restarted Windows it worked again
thanks for replying our questions!

Thanks for sharing @msjyoo
@Datsuke, @FurkanToprak can you try clearing all the local storage and seeing if it resolves the issue for you too?

Thanks for the report @FurkanToprak and @Datsuke.
I just tested myself on Safari and Chrome on my Mac, and I don't have any issues. Can you provide some additional information:
Ubuntu 18.04
USA
Chromium Version 72.0.3626.121 (Official Build) snap (64-bit) (Worked on Firefox)
Everything except for playing worked.
No problems at tools.applemusic.com
No.
I couldn't fix it by reloading and ignoring cache content (shift + Reload) or by signing into different users. I'm not willing to clear local data, but that should be irrelevant as there should be a server-side fix to this ideally. I'm willing to give more info/collaborate as needed.

@FurkanToprak To clear localStorage data, you open DevTools on the website, and go to Stroage, right-click local storage tab, and select "Delete All".
It won't clear data for any of your other websites, and all Apple Music data would be stored with Apple anyway.

@msjyoo Yeah, I did that (and know that). Still hasn't worked for me.

@FurkanToprak Is this still an issue?

@zachomedia Yes. When I click on a song, album art, song title, etc. all changes correctly but Unexpected Error: An unexpected error occurred. occurs. Media playback error no longer occurs.

Hi. I am having a similar issue. The site works great on Firefox, but not on Chromium.
Problem:
When I access the website from Chromium, I get the message telling me to 'install or enable Encrypted Media Extensions in your browser'.
After this, playing any media throws: Media Playback Error: An error occurred during media playback.
What I've tried:
As far as I could tell, EME is already enabled in Chromium by default, and I could not find any way to enable or install it.
I have ensured that the setting for Protected Content (in Settings > Advanced > Content Settings > Protected Content) is already enabled, and I have already cleared all browsing data and restored settings to default. No dice.
Thank you so much. If you know how to enable EME in Chromium, or fix this error, please let me know.  Till then, I'll continue using this service in Firefox.
Some diagnostic information:
OS: Fedora 30 KDE
Chromium: Version 73.0.3683.86 (Developer Build) Fedora Project (64-bit)
Please let me know if there is any more information I can provide to help.
Might I just add, this is a great service and I really appreciate the work you've done!

@EkanshdeepGupta Chromium (the open source version of Chrome) does not have the encrypted media extensions included. I'm not sure how to obtain it on Fedora, but you'll be looking for the widevine package.

Oh. I did not know that. Thanks a lot, I will look if there is a way to do this and update accordingly (hopefully).

Works on firefox but not chromium. Issue closed.

Had the same issue, also on current Chromium on current arch linux, this was the console content:
Error with Feature-Policy header: Unrecognized feature: 'notifications'.
for-you:1 Error with Feature-Policy header: Unrecognized feature: 'push'.
for-you:1 Error with Feature-Policy header: Unrecognized feature: 'document-write'.
for-you:1 Error with Feature-Policy header: Unrecognized feature: 'image-compression'.
for-you:1 Error with Feature-Policy header: Unrecognized feature: 'legacy-image-formats'.
for-you:1 Error with Feature-Policy header: Unrecognized feature: 'max-downscaling-image'.
for-you:1 Error with Feature-Policy header: Unrecognized feature: 'unsized-media'.
for-you:1 Error with Feature-Policy header: Unrecognized feature: 'vertical-scroll'.
for-you:1 Error with Feature-Policy header: Unrecognized feature: 'animations'.
for-you:1 Uncaught (in promise) DOMException
console.js:35 PLAYBACK_ERROR DOMException
t. @ console.js:35
will checkout https://aur.archlinux.org/packages/chromium-widevine/ as a solution, hopefully others with the same error will find this the way I did.


Important technological features of LBRY

Toaster-Level Networking Integration (TLNI) and other features have been documented in order to draw more similarities between toasters and LBRY.

Sure

@ocornoc nice, but yeah, need the images uploaded somewhere else - I think those discord links are only temporary.

Yes... i approve the changes but please use spee.ch as one of LBRY Product

Uploading to Spee.ch rn

great deluded


Pass all props placed on Match

I'm currently using alpha.4 of react-router and using the Match component and thought that I could place props on it and they would transfer to the component prop:
<Match pattern={`${this.props.pathname}/:rad`}
       component={ViewComponent}
       open={this.state.open}
       showSource={() => this.showSource()}/>

so given that I thought that match would pass the props open and showSource to the ViewComponent. It did not however. A good workaround I found was to do the following:
<Match pattern={`${this.props.pathname}/:rad`}
        render={() => <ViewComponent open={this.state.open} showSource={() => this.showSource()}/>}/>

Basically use the render prop instead and place them on the component in that fashion.
Is there anyway that Match automatically place the props that we put on it as props to the component prop?
I may be over looking something completely 😅 .

You arrived at the correct solution. We may want to add props to Match, if we proxy them to your component, we'll break things: therefore, render prop.
You can wrap Match and pass along all props if you want. It's all Just React™
https://github.com/ReactTraining/react-router/issues/3826#issuecomment-246892331

I've just encountered this same desire - so far I have nine instances of <Match> and I have to use the render method on all of them because I need to pass props from the parent. It works fine, but render is a bit more complicated looking and verbose.
Perhaps something like <Match component={WelcomePage} componentProps={pageProps}>?

again, use composition https://github.com/ReactTraining/react-router/issues/3826#issuecomment-246892331

Thanks for the pointer - I appreciate the consideration but I generally stay away from "customizing" frameworks like this; I always end up regretting it, and the next dev will wonder why I didn't do it "the right way". I'll just continue using render.

Rendering a match in one component or another is not customizing anything, it's composition. Match's API is designed for this kind of composition, it's completely intentional for you wrap Match, as many of the examples in the repo already do 😊

I get and error when I try to use render for Match like this:
<Match  exactly pattern={${pathname}}  render={() => {        <Intro buttonClick={this.buttonClick} />  }}/>
Error: MatchProvider.render(): A valid React element (or null) must be returned.

Your arrow function with curly brackets does not return anything. Either include a return statement or, for an implicit return, wrap your return value in parentheses (or nothing at all it your code fits on one line).
<Match exactly pattern={${pathname}} render={() => <Intro buttonClick={this.buttonClick} /> }/>

Thanks for the help.


Replace istanbul with nyc

Simple switch from Istanbul to nyc for code coverage.

Coverage decreased (-0.2%) to 93.65% when pulling 8e9a1d8b5d386de68e1c5fc786cc722c9b2bacc4 on omh1280:coverage into 8daf4b9e66bc0ab45a0ede5a3df8d9f815c53054 on AnalyticalGraphicsInc:master.

Done!

Coverage decreased (-0.2%) to 93.65% when pulling c74e0e8c23887b2c0dba2e9bf1b3b28d1941bb71 on omh1280:coverage into 1db7d7161b188e78ca7e69cb676687610642529e on AnalyticalGraphicsInc:master.

Thanks.