text:
[#3784] Support hostname verification when using OpenSSLEngine

Motivation:
At the moment hostname verification is not supported with OpenSSLEngine.
Modifications:
Allow to create OpenSslEngine with peerHost and peerPort informations.
Result:
hostname verification is supported now.

@trustin @Scottmitch please check...
@ejona86 this should fix your issue. Please check

Wow. That looks easy. I was worried that it was going to be really painful to fix.
I'll give it a test run. Thanks!

@ejona86 me too :)

:'( It didn't work.
I am running Java 1.8.0 u31. I tested JDK vs OpenSSL with identical code and just changed whether libssl.so.10 was in the LD_LIBRARY_PATH (since I'm on Ubuntu). Without libssl.so.10 (so JDK provider) I see "CertificateException: No subject alternative DNS name matching ..." (full stack trace below). With libssl.so.10 (so OpenSSL provider) I connect without issue, even though I purposefully am providing the wrong hostname.
The code I'm testing with provides the hostname and port to newEngine and then sets the "EndpointIdentificationAlgorithm" to "HTTPS" as an SSLParameter.
Just by looking at the source, my current thought is that it doesn't work because OpenSslEngine.OpenSslSession doesn't implement ExtendedSSLSession. X509TrustManagerImpl uses an SNI getter to get the hostname for verification (called from checkTrusted). I'll see if I can find time to play with this idea some on Monday.
The full stacktrace when using JDK (which is working, because it should fail). Note how it is the X509TrustManager failing the connection:
WARNING: An exception was thrown by io.grpc.transport.netty.Http2Negotiator$1$1.operationComplete()
java.util.concurrent.ExecutionException: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        at io.netty.util.concurrent.AbstractFuture.get(AbstractFuture.java:37)
        at io.grpc.transport.netty.Http2Negotiator$1$1.operationComplete(Http2Negotiator.java:148)
        at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:680)
        at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:603)
        at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:563)
        at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:424)
        at io.netty.handler.ssl.SslHandler.notifyHandshakeFailure(SslHandler.java:1286)
        at io.netty.handler.ssl.SslHandler.setHandshakeFailure(SslHandler.java:1281)
        at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1063)
        at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:944)
        at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:327)
        at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:230)
        at io.netty.channel.ChannelHandlerInvokerUtil.invokeChannelReadNow(ChannelHandlerInvokerUtil.java:83)
        at io.netty.channel.DefaultChannelHandlerInvoker.invokeChannelRead(DefaultChannelHandlerInvoker.java:153)
        at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:157)
        at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:946)
        at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:127)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:510)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:467)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:381)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:353)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:703)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1409)
        at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535)
        at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:813)
        at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
        at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
        at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1140)
        at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1004)
        ... 16 more
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        at sun.security.ssl.Alerts.getSSLException(Alerts.java:203)
        at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1728)
        at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:304)
        at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1552)
        at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
        at sun.security.ssl.Handshaker.processLoop(Handshaker.java:957)
        at sun.security.ssl.Handshaker$1.run(Handshaker.java:897)
        at sun.security.ssl.Handshaker$1.run(Handshaker.java:894)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1347)
        at io.netty.handler.ssl.SslHandler.runDelegatedTasks(SslHandler.java:1174)
        at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1026)
        ... 16 more
Caused by: java.security.cert.CertificateException: No subject alternative DNS name matching foo.test.google.r found.
        at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:191)
        at sun.security.util.HostnameChecker.match(HostnameChecker.java:93)
        at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:455)
        at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:436)
        at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:252)
        at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:136)
        at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1539)
        ... 24 more

Will check in detail. Thanks for the details !

Am 16.05.2015 um 18:04 schrieb Eric Anderson notifications@github.com:
:'( It didn't work.
I am running Java 1.8.0 u31. I tested JDK vs OpenSSL with identical code and just changed whether libssl.so.10 was in the LD_LIBRARY_PATH (since I'm on Ubuntu). Without libssl.so.10 (so JDK provider) I see "CertificateException: No subject alternative DNS name matching ..." (full stack trace below). With libssl.so.10 (so OpenSSL provider) I connect without issue, even though I purposefully am providing the wrong hostname.
The code I'm testing with provides the hostname and port to newEngine and then sets the "EndpointIdentificationAlgorithm" to "HTTPS" as an SSLParameter.
Just by looking at the source, my current thought is that it doesn't work because OpenSslEngine.OpenSslSession doesn't implement ExtendedSSLSession. X509TrustManagerImpl uses an SNI getter to get the hostname for verification (called from checkTrusted). I'll see if I can find time to play with this idea some on Monday.
The full stacktrace when using JDK (which is working, because it should fail). Note how it is the X509TrustManager failing the connection:
WARNING: An exception was thrown by io.grpc.transport.netty.Http2Negotiator$1$1.operationComplete()
java.util.concurrent.ExecutionException: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
at io.netty.util.concurrent.AbstractFuture.get(AbstractFuture.java:37)
at io.grpc.transport.netty.Http2Negotiator$1$1.operationComplete(Http2Negotiator.java:148)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:680)
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:603)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:563)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:424)
at io.netty.handler.ssl.SslHandler.notifyHandshakeFailure(SslHandler.java:1286)
at io.netty.handler.ssl.SslHandler.setHandshakeFailure(SslHandler.java:1281)
at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1063)
at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:944)
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:327)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:230)
at io.netty.channel.ChannelHandlerInvokerUtil.invokeChannelReadNow(ChannelHandlerInvokerUtil.java:83)
at io.netty.channel.DefaultChannelHandlerInvoker.invokeChannelRead(DefaultChannelHandlerInvoker.java:153)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:157)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:946)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:127)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:510)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:467)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:381)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:353)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:703)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1409)
at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535)
at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:813)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1140)
at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1004)
... 16 more
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
at sun.security.ssl.Alerts.getSSLException(Alerts.java:203)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1728)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:304)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1552)
at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:957)
at sun.security.ssl.Handshaker$1.run(Handshaker.java:897)
at sun.security.ssl.Handshaker$1.run(Handshaker.java:894)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1347)
at io.netty.handler.ssl.SslHandler.runDelegatedTasks(SslHandler.java:1174)
at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1026)
... 16 more
Caused by: java.security.cert.CertificateException: No subject alternative DNS name matching foo.test.google.r found.
at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:191)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:93)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:455)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:436)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:252)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:136)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1539)
... 24 more
—
Reply to this email directly or view it on GitHub.

I got it working!
I added to OpenSslEngine, and it started working:
    @Override
    public javax.net.ssl.SSLParameters getSSLParameters() {
        javax.net.ssl.SSLParameters parms = super.getSSLParameters();
        // hack
        parms.setEndpointIdentificationAlgorithm("HTTPS");
        return parms;
    }

That's because the SSLParameters are re-created every time. So you just need to override setSSLParameters to copy the value of getEndpointIdentificationAlgorithm, and then set it within getSSLParameters. The default should be null.
The SNI stuff isn't actually necessary, because it will fallback to using peerHost.

Hmm... But wouldn't this only work for https?

Am 16.05.2015 um 19:33 schrieb Eric Anderson notifications@github.com:
I got it working!
I added to OpenSslEngine, and it started working:
@Override
public javax.net.ssl.SSLParameters getSSLParameters() {
    javax.net.ssl.SSLParameters parms = super.getSSLParameters();
    // hack
    parms.setEndpointIdentificationAlgorithm("HTTPS");
    return parms;
}

That's because the SSLParameters are re-created every time. So you just need to override setSSLParameters to copy the value of getEndpointIdentificationAlgorithm, and then set it within getSSLParameters. The default should be null.
The SNI stuff isn't actually necessary, because it will fallback to using peerHost.
—
Reply to this email directly or view it on GitHub.

The application is the one that will call setEndpointIdentificationAlgorithm with "HTTPS". The SslEngine just needs to remember the value set with setSSLParameters(..) and return it in getSSLParameters().

"HTTPS" is the algorithm developed for https, but can be used for other protocols. The only alternative supported by Java is LDAPS. For Java, the only difference is whether the wildcard can be anywhere or only in the leftmost part of the name (so *.foo.com vs foo.*.com).

@ejona86 thanks for the tip! Can you check if it works now for you ?

I just tested it out, and it works great!
Thanks a ton!

Awesome!

Am 17.05.2015 um 23:00 schrieb Eric Anderson notifications@github.com:
I just tested it out, and it works great!
Thanks a ton!
—
Reply to this email directly or view it on GitHub.

@ejona86 @normanmaurer woot! great job, guys!! :)
Is it ready to be cherry-picked?

@netkins build

Cherry-picked into 4.0 (b02f52a680820c3180eea12fb3e1e30961e8b307), 4.1 (b9342577963833080a0009249a1813e8e9e3664c) and master (2a0f9377ef954baa058481bd8692b1130bf58b89) .
@nmittler so yes :)

authors: ejona86 nmittler normanmaurer


text:
Fixed a typo [testEquansIgnoreCase() --> testEqualsIgnoreCase()]

Fixed a typo in the test name.

Thanks! Cherry-picked int 4.1 and master.

source: gharchive/pull-request

authors: MediumOne trustin

repo: netty/netty

license_type: permissive

license_source: github-api


text:
Enable configuring available processors

Motivation:
In cases when an application is running in a container or is otherwise constrained to the number of processors that it is using, the JVM invocation Runtime#availableProcessors will not return the constrained value but rather the number of processors available to the virtual machine. Netty uses this number in sizing various resources. Additionally, some applications will constrain the number of threads that they are using independenly of the number of processors available on the system. Thus, applications should have a way to globally configure the number of processors.
Modifications:
Rather than invoking Runtime#availableProcessors, Netty should rely on a method that enables configuration when the JVM is started or by the application. This commit exposes a new class NettyRuntime for enabling such configuraiton. This value can only be set once. Its default value is Runtime#availableProcessors so that there is no visible change to existing applications, but enables configuring either a system property or configuring during application startup (e.g., based on settings used to configure the application).
Additionally, we introduce the usage of forbidden-apis to prevent future uses of Runtime#availableProcessors from creeping. Future work should enable the bundled signatures and clean up uses of deprecated and other forbidden methods.
Result:
Netty can be configured to not use the underlying number of processors, but rather the constrained number of processors.

The build failure in the PR CI build has nothing to do with this PR.

@jasontedor - Agreed build failure seems unrelated. Seems like timeouts maybe too aggressive for build servers. I will submit a PR to relax these timeouts.

The test failure here has nothing to do with my change.

@jasontedor let me check for the ci error

@jasontedor I rebased your patch locally here and resolved the conflicts and it compiles without a problem. Please rebase as well

@normanmaurer I've rebased and squashed.

@jasontedor the test-failure we saw here is fixed by https://github.com/netty/netty/pull/6651

Thanks @normanmaurer.

@trustin fine with you ?

Thanks @Scottmitch. I've responded to your feedback. Let me know when I should squash again.

Thanks @Scottmitch, I've squashed.

Cherry-picked into 4.1 (98beb777f81f092aa0fddf49ed08b426b2c72f01) and 4.0 (f9309bdfa9ddf880b2bff38b4ad9f1d5a8ad7146).
@jasontedor thanks a lot and sorry it took so long ...

Thank you @normanmaurer @Scottmitch, I'm glad we arrived at a solution that satisfies all of us. Thank for the discussion and helpful reviews.

sorry it took so long ...

No apology necessary here, it's on me that it stalled as long as it did.

authors: Scottmitch jasontedor normanmaurer


text:
Check both whether IPv4 is only stack or IPv4 is preferred when setti…

…ng up DnsNameResolver.
This is a straw-man's proposal related to #9044. The javadoc seems to indicate checking LOCALHOST is LOCALHOST6 or 4 is the way to determine whether IPv6 stack is available.
Motivation:
DNS resolution should not return IPv6 addresses in the following cases

IPv4 is preferred
IPv4 is the only available stack

Otherwise, client code may end up trying to connect to addresses that it is not possible to do so.
Modification:
Check both whether IPv6 stack is available or not in addition to IPv4 preference when setting up DNS resolver.
Result:
Fixes https://github.com/line/armeria/issues/1146 in a better way than #7875

@anuraaga I still think we need #7875 in any case as otherwise it the behaviour is just not correct and inconsistent. That said we should also do something similar to what you did here. I need to think about if what you did here can be done in a "better way" tho.

So to make it short I think my fix is more correct... I you only support IPv4 and you a host only returns AAAA records it is completely fine to fail when try to connect to these. Otherwise with my PR you will try A first.

I agree the other PR is also needed - it fixes the behavior on IPv4 + IPv6 machines. This one is needed for the behavior on IPv4 machines to match the JDK default behavior (I presume matching JDK behavior is a goal of the library so it can be a drop-in replacement).
On an IPv4-only machine, InetAddress.getAllByName("ipv6.google.com") gives
Exception in thread "main" java.net.UnknownHostException: ipv6.google.com: Name or service not known
        at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
        at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)
        at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)
        at java.net.InetAddress.getAllByName0(InetAddress.java:1277)
        at java.net.InetAddress.getAllByName(InetAddress.java:1193)
        at java.net.InetAddress.getAllByName(InetAddress.java:1127)
        at DnsTest.main(DnsTest.java:5)

This PR does the same as JDK, checking the presence of an IPv6 stack and disabling all related functionality if it's not there.

@anuraaga agree we should do something about it.
I think this method is a better way to check if ipv6 is supported at all:
    private static boolean anyInterfaceSupportIpV6() {
        try {
            Enumeration<NetworkInterface> interfaces = NetworkInterface.getNetworkInterfaces();
            while (interfaces.hasMoreElements()) {
                NetworkInterface iface = interfaces.nextElement();
                Enumeration<InetAddress> addresses = iface.getInetAddresses();
                while (addresses.hasMoreElements()) {
                    if (addresses.nextElement() instanceof Inet6Address) {
                        return true;
                    }
                }
            }
        } catch (SocketException ignore) {
            // ignore
        }
        return false;
    }

WDYT ? If this sounds good I will open a new PR based on this one as a replacement for this one

@anuraaga please check https://github.com/netty/netty/pull/9048 as an alternative way to detect if IPv6 can be used or not.

Fixed by https://github.com/netty/netty/pull/9048

authors: anuraaga normanmaurer


text:
Handle the limit file size for upload/download

The missing option for handling the limit file size for upload/download to protect exception on memory overload/overflow.
Please update to this:

server.yml
#this limit upload/download file size
maxTransferFileSize: 1000000
Project: https://github.com/networknt/light-4j/tree/master/server

Class ServerConfig.java
int maxTransferFileSize;
Class Server.java
.setServerOption(UndertowOptions.MAX_ENTITY_SIZE, serverConfig.getMaxTransferFileSize())
.setServerOption(UndertowOptions.MULTIPART_MAX_ENTITY_SIZE, 10*serverConfig.getMaxTransferFileSize())

To make it backward compatible, I have added it to the ServerOption to set the default value if it doesn't exist in the server.yml like other seldom-used options. Thanks a lot for the code you put into the issue. I should have asked you to submit a PR :) The credit goes to you, my friend.

 Handle the limit file size for upload/download light-4j  master

 Add Multipart request body & Multipart response support light-4j master

source: gharchive/issue

authors: PeterKieu stevehu


text:
Create Helm charts deployment

NSM is installed by applying the deployment bundles, cluster configurations from:
https://github.com/networkservicemesh/networkservicemesh/tree/master/k8s/conf
We would like to explore the possibilities of wrapping these in Helm charts.
I would suggest getting inspiration from the split of deployment targets here:
https://github.com/networkservicemesh/networkservicemesh/blob/master/.k8s.mk#L18
It will be great if we can switch the registry server and the image tag when invoking the Helm deployment. So bu default I download networkservicemesh/nsmd which will default to registry-1.docker.io/networkservicemesh/nsmd:latest I want to be able to change this to my.home.registry.local:5000/networkservicemesh/nsmd:myfeature
Note: at the first iteration we want Helm as a deployment option, not as a replacement of the current deployment machinery.

Also... I think that we can use this to move away from a lot of our make machinery ... helm should be able to replace all of the *-deploy cases :)

Closed by #825

We have the first pass here. Let's close and consider reopening if needed later.

authors: edwarnicke nickolaev

repo: networkservicemesh/networkservicemesh

license_source: bigquery


text:
Fix format of docstrings, update API doc to add dividers for clarity

Simple fixes to documentation. No code changes, just a cleaner API reference. Removes unnecessary indents in module docstrings to fix RST build

No code changes, merging

repo: neuraloperator/neuraloperator

license: MIT


text:
[BUG] Have to use GRAPH_PORT GRAPH_PORT_HOST

Is there an existing issue for this?

[x] I have searched the existing issues

Expected Behavior
At the moment, we're using NB_GRAPH_PORT_HOST to construct the Query URL. However the API is in a docker network with the graph and will therefore have to send requests to the graph on the graph's internal port NB_GRAPH_PORT.
https://github.com/neurobagel/api/blob/2a6fc31bc4bc11ee767860d294fc076f7d9c2e73/app/api/utility.py#L26-L36
We have to change these lines and the corresponding docker-compose file so that we expose and use NB_GRAPH_PORT instead.
Current Behavior
No response
Error message
No response
Environment
No response
How to reproduce
No response
Anything else?
We should also document in our internal docs that within a docker network services talk to each other on their internal port number, and not the one that is exposed to the host.

Note: This breaks down if the API that's running is not in the same Docker network as the graph, i.e. if you have locally spun up an API using Python. In this scenario, you need to specify the HOST port in the query URL, not the CONTAINER port.

for reference:

from https://docs.docker.com/network/drivers/bridge/#connect-a-container-to-a-user-defined-bridge
So in other words: within the same docker network, no action is required for the ports of container A to be visible to container B. That implicitly also means: no action can be taken so that port 1 on container A is mapped to a different port number for container B.
See also

from https://docs.docker.com/network/
This is different from how we expose ports from individual containers to the host using the --publish flag. There we can map a container port to a different port number on the host.

authors: alyssadai surchs

repo: neurobagel/api


text:
link to docs in docs page

http://docs.neurodata.io/nddocs/cs.html
there is a placeholder already.
then people will be able to find it without having to remember which letters are caps 👍

Done.

authors: alexbaden jovo

repo: neurodata/ndviz


text:
Inconsistency between: Dice score and Dice loss

We often observe inconsistency between the Validation Dice loss during training and the Dice score on the testing set.
This inconsistency is mainly visible on the MS lesion dataset.
A very probable reason is the different way these two functions are dealing with empty GT and empty pred.
--> Dice loss returns 1 (thanks of the smooth param): https://github.com/neuropoly/ivado-medical-imaging/blob/master/ivadomed/losses.py#L12
--> Dice score returns np.nan: https://github.com/neuropoly/ivado-medical-imaging/blob/master/ivadomed/metrics.py#L64
A naive solution would be to call dice_score in dice_loss --> but the optimiser would not appreciate to receive np.nan (this is the reason why the two functions have been separated until now).
Any thoughts? :-)

Closed with #188

repo: neuropoly/ivado-medical-imaging


text:
MacOS: Can't create session for user  - X server could not be started

I'm on macOS Ventura 13.1 and am following the build guide here: https://github.com/neutrinolabs/xrdp/wiki/Building-on-OSX-(not-official)
Client is mstsc on Windows 10.
Getting the following issue after entering valid credentials for the main admin user on the macOS (this is the only user on the system):

Can't create session for user  - X server could not be started

I suspected it was because XQuartz wasn't running, so I ran that explicitly (such that the X11 logo appears) both with and without sudo but this did not work.
The guide was followed and the only difference is that I needed to explicitly run sudo xrdp-sesman.

Hi @Daniel-Khodabakhsh
We can't offer support for MacOS in these forums I'm afraid as none of the core team have a Mac available.
See #2194 (pinned issue) for how you can get help with this.

repo: neutrinolabs/xrdp


text:
Validators

Short description of the changes:

Long description of the changes:

Check list for the pull request

[ ] I have read the [CONTRIBUTING]
[ ] I have read the [CODE_OF_CONDUCT]
[ ] I have added tests for my changes
[ ] I have updated the documentation accordingly

Check list for the reviewer

[ ] I have read the [CONTRIBUTING]
[ ] I have verified the proposed changes
[ ] best software practices

[ ] all internal functions have an underbar, as is python standard
[ ] clearly named variables (better to be verbose in variable names)
[ ] code comments explaining the intent of code blocks

[ ] All the tests are passing
[ ] The documentation is up to date
[ ] code comments added when explaining intent

Manual test for the reviewer

References

Codecov Report
Attention: Patch coverage is 78.99160% with 25 lines in your changes missing coverage. Please review.

Project coverage is 92.13%. Comparing base (36bd3a5) to head (44de9ac).

Files with missing lines
Patch %
Lines

src/hyspecppt/hppt/hppt_view.py
78.81%
25 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             next      #16      +/-   ##
==========================================
- Coverage   95.95%   92.13%   -3.83%
==========================================
  Files           9        9
  Lines         371      483     +112
==========================================
+ Hits          356      445      +89
- Misses         15       38      +23

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: AndreiSavici codecov-commenter

repo: neutrons/hyspecppt


text:
Identify first note in phrase properly

This fails if the note offset of the first note for subsequent phrases is smaller than the cutoff value for phrase lengths.  It thus becomes very evident for long phrase lengths.

Fixed by 32cc60135a21a13fb1da478b2720e95aa934164b.

repo: newlandsvalley/purescript-abc-melody


text:
選択したファイルのDocumentフォルダへのコピー時フォルダ名を指定できるよう修正

https://github.com/newn-team/standfm/issues/9626 の対応のための修正
前提として現状tmpフォルダに保存してしまうと保存してから1分たったあと自動的に削除されてしまう
そのためDocumentフォルダに保存するようにしたが、Documentフォルダに保存するときは、自動的にハッシュ値のようなフォルダの中に格納されてしまい扱いづらい

扱いづらい理由としては、Documentフォルダ内のデータは自動的に削除されないので明示的に削除する必要があるが、削除時にフォルダ名指定で削除できたほうが楽だと思ったため

よって、格納されるフォルダ名を呼び出し側から指定できるように修正した。（DocumentDirNameオプションを追加した）

before（自動的にフォルダ名が指定されてしまう）:

after（externalというフォルダ名を指定）:

@kitoko552
こちらお手すきでご確認お願いします:pray:

そのためDocumentフォルダに保存するようにしたが、

Documentフォルダは何かしらユーザが作ったデータを置くべきディレクトリで、ユーザに見えてしまうディレクトリですし、作ったり消したりするのに向いていない場所だと思ってます。
なので、Libraryディレクトリ内のCachesディレクトリか、Libraryディレクトリ内に自分で作るサブディレクトリ内かのどちらかの方がいいのではと思っています。
僕の理解だと前者と後者の違いは、前者はアプリが起動していないタイミングでシステムが稀にデータを勝手に消すことがある（良くも悪くも）、後者は完全にこちらが管理しなければいけない、という違いのはずです。

In iOS 5.0 and later, the system may delete the Caches directory on rare occasions when the system is very low on disk space. This will never occur while an app is running.

詳しくはこのドキュメントを読むといいと思います。
https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html

@kitoko552
ありがとうございます！今回の場合だとアプリが起動していないタイミングであれば削除していいファイルのはずなので、Library内のCacheディレクトリに保存するのが良さそうですね。修正します:pray:

@kitoko552
Library/Cachesディレクトリに保存するようにしました。すでにDocumentPicker側にcachesDirecotoryに保存するためのオプションがあったのでそれを利用していますが、Documentと同様にディレクトリ名が自動で割り振られてしまうので外から指定する変更は必要でしたので、このPRはマージしたいです。
js側の呼び出し例↓
      const res = await DocumentPicker.pick({
        copyTo: 'cachesDirectory',
        copyDestDirName: 'RNDocumentPicker/externalData',
        type: [DocumentPicker.types.audio],
      })

pick時のファイル構造↓

repo: newn-team/react-native-document-picker


text:
search-as-primary-CTA JIRA-ID-CXPUI-4

Description
JIRA Ticket: https://newrelic.atlassian.net/browse/CXPUI-4
Previous, Search bar was below the guided install
Now, search bar is in banner below the text and also removed the view button
Reviewer Notes
If there are links or steps needed to test this work, add them here.
Related Issue(s) / Ticket(s)
If there are any related GitHub Issues or JIRA tickets, add links to them here.

issue

Screenshot(s)
OLD:

NEW:

Use Conventional Commits
Please help the maintainers by leveraging the following conventional commit
standards in your pull request title and commit messages.
Use chore

for minor changes / additions / corrections to content.
for minor changes / additions / corrections to images.
for minor non-functional changes / additions to github actions, github templates, package or config updates, etc

git commit -m "chore: adjusting config and content"

Use fix

for minor functional corrections to code.

git commit -m "fix: typo and prop error in the code of conduct"

Use feat

for major functional changes or additions to code.

git commit -m "feat(media): creating a video landing page"

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

Done changes in Incorrect repository

repo: newrelic/developer-website


text:
JFR standalone without a separate process

We want to make it very easy for our existing customers using the Java agent to turn on Real Time Profiling (RTP), provide more options to deploy in container environments, reduce pre-reqs (& align to majority of our customers’ environments) ….
There is a progression of work that will first simplify deployment of RTP for NR Java agent customers and then for customers that opt not to use the Java agent due to performance reasons but want to get the low-overhead insights available from RTP. Each step provides incremental value, and we can opt to stop at any point:

JFRD to be compatible with Java 8
JFR as an extension to the agent - single process, streamline configuration
JFR to be used as a standalone without a separate process

Acceptance Criteria

JFRD can be deployed like the Java agent - without requiring a separate process - for customers that do not want to use Java agent
No measurable performance degradation vs previous JFRd standalone installation
Flamegraphs will work for this standalone JFR deployment deployment option

Aha! Link: https://newrelic.aha.io/features/JAVA-259

Comment added by Kevyn Ford in Aha! - View
Engineering tasks on track and expecting to complete in April as planned. This will be incorporated into the agent 7.0.0 release, which will be in May (no sooner than 30 days from the public notice on Java 7 EOL given as part of the 6.5.0 release.

repo: newrelic/newrelic-jfr-core


text:
Fill out remaining details of readme specific to implementation

Summary
Get the readme production ready near end of project with appropriate details.

lets add details with the queries and how to setup the dashboard/charts.
we don't normally do this but i'm thinking explaining all of it might be a good idea.
transaction naming: here's the parts and why
segment/span naming: here's the parts and wny
metrics: here's the parts and why
here's how you use the metrics to create what you want to see, whatever.
if we get filtering in, we'll also want to capture that.

also list out known supported frameworks and whether or not expected to mostly work with typically unsupported frameworks.


text:
React native 0.72

Description
After upgrading the RN version to the latest 0.72 Android build stated field
Steps to Reproduce
[NOTE]: # Just try to install newrelic react native wrapper on react native 072
Additional context
I found a conversation about this and under this tread suggesting to update newrelic agent gradle version to
com.newrelic.agent.android:agent-gradle-plugin:7.+ but it not working for me because I'm using React native
https://forum.newrelic.com/s/hubtopic/aAX8W00000005vhWAA/android-sdk-blocks-project-updates-to-gradle-800
Your Environment
package.json
"react-native": "^0.72.0",
"newrelic-react-native-agent": "^1.2.1",

Terminal output
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Could not create task ':app:transformClassesWithNewrelicTransformForAlphaDebug'.
   > Cannot use @TaskAction annotation on method IncrementalTransformTask.transform() because interface org.gradle.api.tasks.incremental.IncrementalTaskInputs is not a valid parameter to an action method.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 12s
error Failed to install the app. Command failed with exit code 1: ./gradlew tasks FAILURE: Build failed with an exception. * What went wrong:
A problem occurred configuring project ':app'.
> Could not create task ':app:transformClassesWithNewrelicTransformForAlphaDebug'. > Cannot use @TaskAction annotation on method IncrementalTransformTask.transform() because interface org.gradle.api.tasks.incremental.IncrementalTaskInputs is not a valid parameter to an action method. * Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights. * Get more help at https://help.gradle.org BUILD FAILED in 12s
> Task :gradle-plugin:pluginDescriptors
> Task :gradle-plugin:processResources
> Task :gradle-plugin:compileKotlin
> Task :gradle-plugin:compileJava NO-SOURCE
> Task :gradle-plugin:classes
> Task :gradle-plugin:jar
> Task :gradle-plugin:inspectClassesForKotlinIC > Configure project :app
WARNING:API 'android.registerTransform' is obsolete.
It will be removed in version 8.0 of the Android Gradle plugin.
The Transform API is removed to improve build performance. Projects that use the
Transform API force the Android Gradle plugin to use a less optimized flow for the
build that can result in large regressions in build times. It’s also difficult to
use the Transform API and combine it with other Gradle features; the replacement
APIs aim to make it easier to extend the build without introducing performance or
correctness issues. There is no single replacement for the Transform API—there are new, targeted
APIs for each use case. All the replacement APIs are in the
`androidComponents {}` block. The Transform API uses incremental APIs deprecated since Gradle 7.5. Please add
`android.experimental.legacyTransform.forceNonIncremental=true` to
`gradle.properties` to fix this issue. Note that this will run transforms
non-incrementally and may have a build performance impact.
For more information, see https://developer.android.com/studio/releases/gradle-plugin-api-updates#transform-api.
To determine what is calling android.registerTransform, use -Pandroid.debug.obsoleteApi=true on the command line to display more information. Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. See https://docs.gradle.org/8.0.1/userguide/command_line_interface.html#sec:command_line_warnings
5 actionable tasks: 5 executed.

@abgaryanharutyun We are aware of this issue, and we are currently awaiting the release of our Android Agent to address it.

Cool thanks for the update @ndesai-newrelic, can I know a rough estimation about the release?

@abgaryanharutyun we will release this next month.

This is an issue indeed, but seems to be working fine, using a v.7 agent. (latest GA release)
Following this guideline helps setting it up.

@adrianv-synergy this is related AGP 8 and it should be working with latest android release. we will update our react native agent soon.

@adrianv-synergy @abgaryanharutyun it is fixed in latest release.

repo: newrelic/newrelic-react-native-agent


text:
Events timestamp appears to be the reporting timestamp and not the actual event timestamp

Description
This comes from the forums: Latest() not returning the actual latest
I’m trying to create a NRQL query that returns the latest node status in a k8s cluster based on the NodeReady and NodeNotReady events.
The closest I got to that is:
SELECT latest(event.reason) from InfrastructureEvent where event.reason in (‘NodeNotReady’,‘NodeReady’) facet event.involvedObject.name since 356 days ago
But sometimes it returns “NodeNotReady” for nodes that are actually ready and if I query the node specific data I can see the latest event.reason is indeed “NodeReady” when sorted by event.lastTimestamp.
I’m attaching a few screenshots filtered for a specific node that was showing this behavior a few minutes ago. I’ve highlighted some areas that I think will help clarify the issue.
If for some reason the screenshots don't show up here, please check the forum post where I shared them originally.
Query showing the “NodeNotReady” result for a node that is Ready:

Another query showing the NodeReady and NodeNotReady events for that same node with default sorting. Note that the two most recent events have the same timestamp but their event.lastTimetamp differs:

And the same query sorted by event.lastTimestamp desc:

Steps to Reproduce
I executed the query on two clusters and both returned "NodeNotReady" for some nodes that had a more recent "NodeReady" event. This appears to be related to how the timestamp for the events is handled when reporting them.
Expected Behaviour
The latest() event should be the one that happened last.
Relevant Logs / Console output
Screenshots are available in the forum: Latest() not returning the actual latest
Your Environment
Openshift 3.11.248
infrastructure-k8s:1.26.2
k8s-events-forwarder:1.12.0

Thanks for reporting this @fgimenezm
I wanted to add that the infra agent added support for integrations to overwrite the default timestamp (https://github.com/newrelic/infrastructure-agent/pull/29) so this might require an update to send the proper value.

@josemore , I'm new to Go language but I'm guessing this could be done around here
or maybe here
Or perhaps at the sink itself somewhere in the HandleEvent method here
What do you recommend?

Hi @josemore, @fgimenezm, I've double-posted this in the forum chat as well - I'm wondering if the issue is actually that New Relic timestamps only record up to the second, rather than millisecond? We send logs to Elasticsearch and the logs for kube-events look like this for one example:
Elasticsearch timestamp     New Relic Event log
Jan 6, 2021 @ 09:53:04.229	time="2021-01-06T09:53:04Z" ... ,\"reason\":\"Starting\", ...
Jan 6, 2021 @ 09:53:04.159	time="2021-01-06T09:53:04Z" ... ,\"reason\":\"NodeNotSchedulable\", ...
Jan 6, 2021 @ 09:53:04.158	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeReady\", ...
Jan 6, 2021 @ 09:53:04.158	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasNoDiskPressure\", ...
Jan 6, 2021 @ 09:53:04.158	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasSufficientPID\", ...
Jan 6, 2021 @ 09:53:04.158	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasSufficientMemory\", ...
Jan 6, 2021 @ 09:53:04.147	time="2021-01-06T09:53:04Z" ... \"reason\":\"Rebooted\", ...
Jan 6, 2021 @ 09:53:04.147	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeAllocatableEnforced\", ...
Jan 6, 2021 @ 09:53:04.145	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasNoDiskPressure\", ...
Jan 6, 2021 @ 09:53:04.145	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasSufficientMemory\", ...
Jan 6, 2021 @ 09:53:04.145	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasSufficientPID\", ...
Jan 6, 2021 @ 09:53:04.145	time="2021-01-06T09:53:04Z" ... \"reason\":\"Starting\", ...
Jan 6, 2021 @ 09:53:04.134	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeNotReady\", ...
Jan 6, 2021 @ 09:51:19.617	time="2021-01-06T09:51:19Z" ... \"reason\":\"NodeNotSchedulable\", ...

The NodeReady event is recorded at 09:53:04.158 while the NodeNotReady event is at 09:53:04.134 - milliseconds’ difference. It seems to me that this detail is lost in New Relic so presumably the latest() of the two would randomly be either one or the other. In this case I get “NodeNotReady” as the latest(), similarly to the original poster.
If my reasoning is correct, would it possible to get the millisecond resolution too? I guess one way might be to insert the unix timestamp as another attribute/column if the existing set up is not possible.
Many thanks
Mel

Hi @josemore, @fgimenezm, I've double-posted this in the forum chat as well - I'm wondering if the issue is actually that New Relic timestamps only record up to the second, rather than millisecond? We send logs to Elasticsearch and the logs for kube-events look like this for one example:
Elasticsearch timestamp     New Relic Event log
Jan 6, 2021 @ 09:53:04.229	time="2021-01-06T09:53:04Z" ... ,\"reason\":\"Starting\", ...
Jan 6, 2021 @ 09:53:04.159	time="2021-01-06T09:53:04Z" ... ,\"reason\":\"NodeNotSchedulable\", ...
Jan 6, 2021 @ 09:53:04.158	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeReady\", ...
Jan 6, 2021 @ 09:53:04.158	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasNoDiskPressure\", ...
Jan 6, 2021 @ 09:53:04.158	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasSufficientPID\", ...
Jan 6, 2021 @ 09:53:04.158	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasSufficientMemory\", ...
Jan 6, 2021 @ 09:53:04.147	time="2021-01-06T09:53:04Z" ... \"reason\":\"Rebooted\", ...
Jan 6, 2021 @ 09:53:04.147	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeAllocatableEnforced\", ...
Jan 6, 2021 @ 09:53:04.145	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasNoDiskPressure\", ...
Jan 6, 2021 @ 09:53:04.145	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasSufficientMemory\", ...
Jan 6, 2021 @ 09:53:04.145	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeHasSufficientPID\", ...
Jan 6, 2021 @ 09:53:04.145	time="2021-01-06T09:53:04Z" ... \"reason\":\"Starting\", ...
Jan 6, 2021 @ 09:53:04.134	time="2021-01-06T09:53:04Z" ... \"reason\":\"NodeNotReady\", ...
Jan 6, 2021 @ 09:51:19.617	time="2021-01-06T09:51:19Z" ... \"reason\":\"NodeNotSchedulable\", ...

The NodeReady event is recorded at 09:53:04.158 while the NodeNotReady event is at 09:53:04.134 - milliseconds’ difference. It seems to me that this detail is lost in New Relic so presumably the latest() of the two would randomly be either one or the other. In this case I get “NodeNotReady” as the latest(), similarly to the original poster.
If my reasoning is correct, would it possible to get the millisecond resolution too? I guess one way might be to insert the unix timestamp as another attribute/column if the existing set up is not possible.
Many thanks
Mel

Closing this issue as stale. Please reopen this issue and PR when you are ready to retake a look at it.
Thank you for your contribution!

authors: davidgit fgimenezm josemore weemel

repo: newrelic/nri-kube-events


text:
On mobile, the global nav (top 40ish pixels) experience is different from developer.newrelic.com

The open source site needs to match the developer site experience.

cc: @danielgolden

This should be fixed with our global header component implementation.

authors: jpvajda tangollama

repo: newrelic/opensource-website


text:
Turn platform-specific strprintf crates into mods

strprintf crate needs platform-dependent printf formats for things like std::uint64_t, so I put them into two crates (for 32- and 64-bit platforms respectively), and I switch between the two using #[cfg(...)] macros. However, there is no real reason to have them in crates rather than modules; if anything, crates hurt, because they're very small but compiled separately, taking up the link time.
Will merge in three days if no-one stops me for a review.

Coverage remained the same at 39.247% when pulling c5546b831ee552804e3b008024c57e50bc0c903e on feature/no-pointless-crates into c01acf47142637b8959036585bc30eaf28c30052 on master.

Coverage remained the same at 39.247% when pulling c5546b831ee552804e3b008024c57e50bc0c903e on feature/no-pointless-crates into c01acf47142637b8959036585bc30eaf28c30052 on master.

authors: Minoru coveralls

repo: newsboat/newsboat


text:
Suggestion: Agency Alphabetically

Hi, FOIA Lawya Team,
Thanks so much for all your work on this interface. Love it!
A small suggestion: Is it possible to list the agency names alphabetically or autofill them? The more FOIA we upload, the longer and messier the agency list becomes. (This might also apply to the list of requestors, too).
Many thanks,
Melissa Segura

That's a great idea. Sorting them alphabetically is easy and I'll try to
get to it soon.
If any members of the community want to take on autofill or autocompleting
agency names, it'd be a great first pull request 😀
@melissasegura -- you mention wanting requestor names sorted/autofill too.
Can you tell me more about your use case?
If each user has their own username and logs their own FOIAs, that field
should default to the user's own username. (And I imagined it would be rare
that one user would be entering FOIAs filed by another user.) Is this
feature maybe broken?
In any case, sorting that field should likewise be easy.
Jeremy B. Merrill
Sent from my mobile device
On Aug 31, 2017 4:09 PM, "MelissaSegura" notifications@github.com wrote:
Hi, FOIA Lawya Team,
Thanks so much for all your work on this interface. Love it!
A small suggestion: Is it possible to list the agency names alphabetically
or autofill them? The more FOIA we upload, the longer and messier the
agency list becomes. (This might also apply to the list of requestors, too).
Many thanks,
Melissa Segura
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/newsdev/foialawya/issues/12, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhdmjcZb67glmh4dTcLTSbD9caHYekHks5sdxLwgaJpZM4PJV_Q
.

Thanks so much, Jeremy!
You're totally right. FOIA Lawya defaults to my name when tracking my FOIAs. I wouldn't want to change that for a second. I was just wondering if it might be wise of list the requestors, the names, in alphabetical order, in the event I'm working with someone else on a project. For example, I might be working with Dan Wagner on investigating Jeff Sessions. Seeing what he's FOIAed is awesome. I can see the day that more and more people contribute to FOIA Lawya, the harder it will be to find Dan's name if it's not ordered in anyway. Does that make sense?
Again, just a suggestion.
Thanks,
Melissa

Hi Melissa,
I'm ecstatic to hear suggestions from users; ecstatic that folks are using FOIA Lawya. (You're at BuzzFeed, yes?)
I may have misunderstood earlier. Are we talking about the list of requests on the front page (that lists all the requests in the organization) or the lists of requestors and agencies on the page where you go to add a FOIA?

I am indeed at BuzzFeed!
If I had to choose, I'd definitely say that alphabetizing the list of
agencies that appear on the "track my FOIA" page would be the top priority.
If I were being greedy, the second, separate request would be to
alphabetize the list of requestors (aka, the person filling out the tracked
FOIA)
Does that make sense?
Many thanks!
Melissa Segura
On Fri, Sep 1, 2017 at 7:56 AM, Jeremy B. Merrill notifications@github.com
wrote:

Hi Melissa,
I'm ecstatic to hear suggestions from users; ecstatic that folks are using
FOIA Lawya. (You're at BuzzFeed, yes?)
I may have misunderstood earlier. Are we talking about the list of
requests on the front page (that lists all the requests in the
organization) or the lists of requestors and agencies on the page where you
go to add a FOIA?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/newsdev/foialawya/issues/12#issuecomment-326586800,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeD4PZ4r3ST8am0pJIdCJAgG88F_QLwjks5seA0JgaJpZM4PJV_Q
.

--
Melissa Segura
https://www.buzzfeed.com/melissasegura/detective-guevaras-witnesses?utm_term=.hw3mmb1Ang#.hqk881zDY4
| BuzzFeed News | Reporter | (505) 670-1683 | @MelissaDSegura
111 East 18th St., NY, NY 10003

Hi Melissa,
I think they're both doable (and super easy, I'm pretty sure). I just wanted to make sure that we're talking about the list of requestors _on the "track my FOIA page".

Yes, sir! Thanks much!
On Fri, Sep 1, 2017 at 1:19 PM Jeremy B. Merrill notifications@github.com
wrote:

Hi Melissa,
I think they're both doable (and super easy, I'm pretty sure). I just
wanted to make sure that we're talking about the list of requestors _on the
"track my FOIA page".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/newsdev/foialawya/issues/12#issuecomment-326663354,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeD4PR2DZdxkb5hZgGpfdStB8PAb1Tceks5seFjDgaJpZM4PJV_Q
.

--
Melissa Segura
https://www.buzzfeed.com/melissasegura/detective-guevaras-witnesses?utm_term=.hw3mmb1Ang#.hqk881zDY4
| BuzzFeed News | Reporter | (505) 670-1683 | @MelissaDSegura
111 East 18th St., NY, NY 10003

Totez!

@MelissaSegura Got a preference between sorting on first name or last name (for the requestors)?

I decided to sort by first name, since last name didn't look sorted when I tested it. But if you think last name fits better, let me know, I'm all ears.
This is fixed 9df383e, so you should be able to update your installation and get this fix.

authors: MelissaSegura jeremybmerrill

repo: newsdev/foialawya


text:
Add NEP-45 Draft (#45)

Checklist:

[x] I have read the NEP Guideline document.
[x] I have checked my NEP Draft is ready.

Changes

I have read the CLA Document and I hereby sign the CLA

repo: newtonproject/NEPs


text:
Ignore security groups in device reconcile

When the security group ID changes on for example, a SG ID deletion, it triggers a peer config change and redeploys the peerings.
This patch creates a method that will ignores the two device fields, Revision and SecurityGroupId by setting them to a temporary constant and then does a reflect to check for a diff.
The bug is described further in #1146

This may not be the right approach, if there are plans for the revision field to be used for any change tracking in device reconciliation.

The rpm job failure will be fixed by #1156

authors: nerdalert russellb

repo: nexodus-io/nexodus


text:
[인수 테스트] 1단계 - 지하철역 인수 테스트 작성

안녕하세요 한솔님! 지하철역 목록 조회, 지하철역 삭제 인수 테스트 작성했습니다.
중복되는 코드가 있어 StationPrepare라는 지하철역 인수 테스트 준비 클래스를 만들어서 중복을 제거했습니다.
이번 단계도 잘 부탁드립니다 😄

피드백 감사합니다! 2단계 미션에서 적용해보도록 하겠습니다 👍

repo: next-step/atdd-subway-map


text:
[Mission4. 그럴듯한 서비스 만들기] 1단계 - 서비스 구성하기

안녕하세요. 황준일 리뷰어님! 🙇
미션 네번째를 담당하시게 되어 반갑습니다!! 😃 😃 😃
부족한 실력이지만, 고쳐야할 부분이나 개선해야 될 부분이 있다면 말씀주시기 바랍니다!! 🙇
오늘도 좋은 하루되세요!! ☀

황준일 리뷰어님 안녕하세요. 🙇
지난 리뷰를 반영하여 적용했습니다.
변경 사항 먼저 말씀 드린 후 구현할 내용 적어두겠습니다 ❗

변경 사항

외부망 EC2 인스턴스 중 public-b을 중지상태로 전환했습니다.
보안 그룹 정책 : 대역망 전체가 아닌 해당 아이피에서 인바운드할 수 있도록 적용했습니다.
DNS 적용 했습니다. http://infla.gregolee.kro.kr:8080/

구현 내용

[x] 4.구현

[x] 4-1.VPC 생성

[x] 4-1-1.CIDR은 C class(x.x.x.x/24)로 생성. 이 때, 다른 사람과 겹치지 않게 생성

[x] 4-2.Subnet 생성

[x] 4-2-1.외부망으로 사용할 Subnet : 64개씩 2개 (AZ를 다르게 구성)
[x] 4-2-2.내부망으로 사용할 Subnet : 32개씩 1개
[x] 4-2-3.관리용으로 사용할 Subnet : 32개씩 1개

[x] 4-3.Internet Gateway 연결
[x] 4-4.Route Table 생성
[x] 4-5.Security Group 설정

[x] 4-5-1.외부망

[x] 4-5-1-1.전체 대역 : 8080 포트 오픈
[x] 4-5-1-2.관리망 : 22번 포트 오픈

[x] 4-5-2.내부망

[x] 4-5-2-1.외부망 : 3306 포트 오픈
[x] 4-5-2-2.관리망 : 22번 포트 오픈

[x] 4-5-3.관리망

[x] 4-5-3-1.자신의 공인 IP : 22번 포트 오픈

[x] 4-6.서버 생성

[x] 4-6-1.외부망에 웹 서비스용도의 EC2 생성
[x] 4-6-2.내부망에 데이터베이스용도의 EC2 생성
[x] 4-6-3.관리망에 베스쳔 서버용도의 EC2 생성
[x] 4-6-4.베스쳔 서버에 Session Timeout 600s 설정
[x] 4-6-5.베스쳔 서버에 Command 감사로그 설정

[x] 4-7.웹 애플리케이션 배포

[x] 4-7-1.외부망에 웹 애플리케이션을 배포
[x] 4-7-2.DNS 설정

좋은 리뷰 감사합니다! 👍 🙇
좋은 하루되세요!! ☀

repo: next-step/infra-subway-deploy


text:
feat(knex): add standalone SQL adapter

Smaller more well-maintained replacement for the TypeORM adapter for v4, rewritten to match the simplified adapter API.
The easiest ORM we found was knex, so this adapter will use that under the hood.
A separate MongoDB adapter can be found at #193

Closing in favor of https://github.com/nextauthjs/adapters/pull/185 after discussion.

repo: nextauthjs/adapters

license: ISC


text:
Inclusion of the carbon footprint of cached processes

This is to discuss how to present the carbon footprint of cached processes.
Simple example: 3 processes [P1] [P2] [P3]

First run of the pipeline, all three are run
Second run of the pipeline, cached [P1] is used, [P2] and [P3] are run

When presenting the carbon footprint of run (2), we can either:

Take the carbon footprint of [P1] for run (1) and add the carbon footprints of [P2] and [P3] from run (2).
Or only add the carbon footprints of [P2] and [P3] and ignore the impact of [P1].

Option 1 gives a better estimate of the total carbon footprint of the pipeline if we were to run it again from start to finish on new data let's say. But option 2 gives a more accurate estimate of the true carbon footprint of running step (2). And if adding run (1) + run (2), option 2 should be used (otherwise the footprint of [P1] would get double counted even though it was only run once).
It seems to depend a lot on what users want to do with this information, so perhaps best to give both information in the report so that users can decide what to do?

Yes, I also think both would be useful in the future

authors: Llannelongue skrakau


text:
:render-fn errors in book.clj aren't detected on CI

Discovered this when dev/nextjournal/clerk/emmy.cljs wasn't on the classpath when building the book

This has been fixed with #687.

authors: borkdude mk

repo: nextjournal/clerk


text:
🛑 Nextpost.tech is down

In a348b2d, Nextpost.tech (https://nextpost.tech) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nextpost.tech is back up in 1a4ccd0 after 10 minutes.

repo: nextpost-tech/status


text:
[BUG] - Table: minWidth and other column props not recognized

NextUI Version
2.1.13
Describe the bug
Some of the column properties, e.g. minWidth, are not applied
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Apply any value for minWidth
Expected behavior
Property should be applied to styles
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Chrome

align doesn't work either. Can you add that detail to this bug? 🙏

TableColumn properties (align, width, maxWidth...) are not working here neither.
Version:
"@nextui-org/react": "^2.2.9",
"next": "14.0.4",

TableColumn properties (align, width, maxWidth...) are not working here neither.
Version:
"@nextui-org/react": "^2.2.9",
"next": "14.0.4",

.

TableColumn properties (align, width, maxWidth...) are not working here neither.
Version:
"@nextui-org/react": "^2.2.9",
"next": "14.0.4",

    "next": "^14.1.0",     "@nextui-org/react": "^2.2.9",
Same here.  Work-arounding it by adding length to the column header name for now.

Same here, doesn't even work in the examples in the docs:

any news on this?

I am having the same issue here. Are there any temporary workarounds available? I need to set the width of my column.

I am having the same issue here. Are there any temporary workarounds available? I need to set the width and alignment of my column.

i have solved it with .... i am using tailwind

I am using tailwind as well and solved the alignment issue with the className "text-right"

Any news about this issue?

Any updates?

You can try adding an element inside  and apply your desired styles to that element. This approach might achieve a similar effect.
<TableColumn >
Name
</TableColumn>

I am new to next-ui, even an autogenerated project via nextui init does not work properly.
maxWidth and justify don't work in the Navbar of the autogenerated project.
Version: NextUI CLI v0.3.4

I am using tailwind as well and solved the alignment issue with the className "text-right"

I am having the same issue here. Are there any temporary workarounds available? I need to set the width and alignment of my column.

i have solved it with <TableColumn className='min-w-48'> .... i am using tailwind

Of course you can solve it with tailwind. You can also solve it with css.
You could just not use nextui at all and do everything on your own. But the point is that the nextui functionality that should work does not work, and should be fixed.
Getting the solution that worked for you out is a good thing regardless, I'm not trying to be toxic here, but this is still an issue with nexui that needs to be dealt with.

authors: EtherealData LagoonProject LeoLin4258 PabloOliveiraSantos Ribosom THE-SIMPLE-MARK captainkapnap duchoan6814 happydayxxl kasulk matteogilioli rayaqin stx-chris ygd

repo: nextui-org/nextui


text:
fix:The dynamic size value is returned

[LEVEL]/[COMPONENT]
TASK:
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Only
[ ] Refactor

Description, Motivation and Context

Screenshots - Animations

Hi! @DiegoContrerasA I appreciate your contribution but the border size can't be the same as the Avatar size because when the user puts a custom size like "40px" then the border size will be "40px"

authors: DiegoContrerasA jrgarciadev


text:
Remove lib folder to get ready for v2.13.1 template merge

Description of feature
Remove lib folder to get ready for v2.13.1 template merge

Done in #391

repo: nf-core/chipseq


text:
KeyError: 'X' at Tiddit stage

Description of the bug
At the stage of Tiddit the error message "KeyError: 'X'" is given. Googeling another part of the error message "Converting SIF file to temporary sandbox..." indicates the error might be associated with Singularity. Tried to run with Docker instead and got the same error message. I also tried with two different genomes NA12877 an NA12878.
Longer version of error msg below:
Command error:
INFO:    Converting SIF file to temporary sandbox...
[M::main_ropebwt2] inserted 71301846 symbols in 4.725 sec, 12.905 CPU sec
[M::main_ropebwt2] constructed FM-index in 4.906 sec, 13.085 CPU sec
[M::main_ropebwt2] symbol counts: ($, A, C, G, T, N) = (471044, 20304876, 15110525, 15110525, 20304876, 0)
[M::main_ropebwt2] rld: (tot, $, A, C, G, T, N) = (71301846, 471044, 20304876, 15110525, 15110525, 20304876, 0)
[M::main] Version: r187
[M::main] CMD: ropebwt2 -dNCr 12877_tiddit/clips.fa
[M::main] Real time: 5.210 sec; CPU: 13.362 sec
[M::fm6_unitig] choose prime 123457
[M::main] Version: r178
[M::main] CMD: fermi2 assemble -t 1 -l 81 -
[M::main] Real time: 54.849 sec; CPU: 49.669 sec
LIBRARY STATISTICS
Pair orientation = Forward-Reverse
Average Read length = 150.26575474936982
Average insert size = 992.4905793403768
Stdev insert size = 4681.7813985210305
99.95 percentile insert size = 66860.0
Collecting signals on contig: 21
Collecting signals on contig: MT
('total', 1228.4005160331726)
Writing signals to file
extracted signals in:
-1320.0913121700287
calculated coverage in:
0.4158134460449219
Clip read assembly in:
245.58833026885986
Traceback (most recent call last):
File "/usr/local/bin/tiddit", line 11, in
sys.exit(main())
File "/usr/local/lib/python3.10/site-packages/tiddit/main.py", line 161, in main
sv_clusters=tiddit_cluster.main(prefix,contigs,contig_length,samples,library["mp"],args.e,args.l,max_ins_len,args.min_contig,args.skip_assembly)
File "tiddit/tiddit_cluster.pyx", line 112, in tiddit.tiddit_cluster.main
KeyError: 'X'
INFO:    Cleaning up image...
Command used and terminal output
nextflow run nf-core/raredisease -revision 1.0.0  \
 -profile singularity \
 -params-file ../raredisease/workflow/GRCh37_params.yaml \
 --input samplesheetNA12877.csv \
 --outdir out_NA12877 \
 --genome GRCh37 \
 --save_reference \
 --skip_snv_annotation \
 --skip_sv_annotation \
 --skip_mt_analysis \
 --max_time 12.day \
 --max_cpus 30 \
 --max_memory 128.GB \
 -resume

Relevant files
relevant_files_issuereport.zip
System information
Nextflow version: 22.10.6
Hardware: HPC
Executor: Local
Container engine: Singularity
OS: CentOS Linux
Version of nf-core/raredisease: v1.0.0

@hrydbeck : Is the SV calling with tiddit that is giving problems? If so, then it might be worth trying to disable it. I think it could be done by adding
        ext.when = { false }

around here:
https://github.com/nf-core/raredisease/blob/fdfb4a7c169b4ff3a0c5e76f85420ae6e84ec6d9/conf/modules/call_sv_tiddit.config#L19
As far as I can tell, the raredisease-pipeline should still be doing SV calling with Manta. Perhaps @ramprasadn can confirm that?

I've notified Jesper Eisfeldt about this tiddit-related issue. Perhaps he can shed some light on this issue.

Thank you again asp82. I did the edit you suggested, but got the same error message. I am not sure how to know that I am using the local edited repository. I am now running on a downloaded version 1.0.0 and using the "nextflow run main.nf ...". I assume that should make sure that I am running the from the local edited version. In that case the suggested editing doesnt seem to disable Tiddit. Thanks for helping and reaching out to people who could have interest and skills in resolving the issue. I will be away for the next two weeks.

@hrydbeck : I think Jesper Eisfeldt of Tiddit might be interested in obtaining a copy of some data with which to reproduce the above-mentioned "bug" (it might be more of a data issue).

Should we move this issue to TIDDIT repo? What do you guys think?

The problem was that I set the "fasta" parameters as it is set in "test one sample", just copied the entry.
When I removed the fasta entry below from my parameter yaml file the problem disappeared
fasta: 'https://raw.githubusercontent.com/nf-core/test-datasets/raredisease/reference/reference.fasta'
Thank you the help Jesper Eisfeldt.

authors: asp8200 hrydbeck ramprasadn

repo: nf-core/raredisease