NTR: circRNA

See https://github.com/geneontology/go-ontology/issues/13302
It looks like GO is proposing to treat this as a subtype of SO:0000234 ! mRNA

FlyBase has very recently annotated circ_mRNAs for 2 gene models (mbl and Pde8). We are hoping that implementation of new circRNA terms can be moved up the priority list.
We would like to point out an advantage of the second option described above: provides an appropriate term ('circRNA') when it is not known whether it is coding or non-coding.
In addition to the transcript level terms, it would be helpful to have 'gene_with.....' or similar term(s) at the gene level.

Hi guys,
The terms circular_ncRNA has been assigned ID SO:0002291 and circular_mRNA has been assigned ID SO:0002292. As usual, the SO Browser should be updated with these terms within about 24 hours.
Thanks,
Dave


build fail (looser throw specifier in EnvWrapper)

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

No.

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

Linux Fedora 17

TensorFlow installed from (source or binary):

Trying to build from source.

TensorFlow version (use command below):

1.3

Python version:

2.7

Bazel version (if compiling from source):

0.5.4

CUDA/cuDNN version:

Disabled.

GPU model and memory:

Disabled.

Exact command to reproduce:

bazel build
Describe the problem
I'm trying to compile tensorflow from source, don't modify anything, simply following the instructions on the webpage:
built bazel 0.5.4 from source
git clone
git checkout origin/1.3
./configure     # all answers are the defaults
bazel build --verbose_failures --config=opt //tensorflow/tools/pip_package:build_pip_package
The above fails with with a looser throw specifier error in core/platform/env.h
The versions of the various tools involved:
openjdk 1.8.0
bazel 0.5.4
python 2.7
gcc 4.7.2
libstdc++ 4.7.2
The problem is reproducible on my box.
Source code / logs
The precise failure from the bazel build is this:
>
>
> ERROR: /home/fetch/tensorflow/tensorflow/core/BUILD:1244:1: C++ compilation of rule '//tensorflow/core:lib_internal' failed (Exit 1): gcc failed: error executing command
>   (cd /home/fetch/.cache/bazel/_bazel_fetch/7ef242de6c5f89b75c729448096cd3bb/execroot/org_tensorflow && \
>   exec env - \
>     LD_LIBRARY_PATH=/usr/lib64:/usr/lib64/openmpi/lib \
>     PATH=/opt/obuildfactory/jdk-1.8.0-openjdk-x86_64/bin:/usr/lib/jvm/java-1.7.0-openjdk-<IP_ADDRESS>.x86_64/bin:/usr/lib64/openmpi/bin:/home/fetch/opt/bin:/home/fetch/bin:/usr/lib64/openmpi/bin:/home/fetch/opt/bin:/home/fetch/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin \
>     PWD=/proc/self/cwd \
>     PYTHON_BIN_PATH=/bin/python \
>     PYTHON_LIB_PATH=/usr/lib/python2.7/site-packages \
>     TF_NEED_CUDA=0 \
>     TF_NEED_OPENCL=0 \
>   /bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -B/bin -B/usr/bin -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-march=native' '-std=c++0x' '-march=native' -MD -MF bazel-out/local-opt/bin/tensorflow/core/_objs/lib_internal/tensorflow/core/platform/default/tracing.pic.d '-frandom-seed=bazel-out/local-opt/bin/tensorflow/core/_objs/lib_internal/tensorflow/core/platform/default/tracing.pic.o' -fPIC -DEIGEN_MPL2_ONLY -DSNAPPY -iquote . -iquote bazel-out/local-opt/genfiles -iquote external/bazel_tools -iquote bazel-out/local-opt/genfiles/external/bazel_tools -iquote external/protobuf -iquote bazel-out/local-opt/genfiles/external/protobuf -iquote external/eigen_archive -iquote bazel-out/local-opt/genfiles/external/eigen_archive -iquote external/local_config_sycl -iquote bazel-out/local-opt/genfiles/external/local_config_sycl -iquote external/gif_archive -iquote bazel-out/local-opt/genfiles/external/gif_archive -iquote external/jpeg -iquote bazel-out/local-opt/genfiles/external/jpeg -iquote external/com_googlesource_code_re2 -iquote bazel-out/local-opt/genfiles/external/com_googlesource_code_re2 -iquote external/farmhash_archive -iquote bazel-out/local-opt/genfiles/external/farmhash_archive -iquote external/fft2d -iquote bazel-out/local-opt/genfiles/external/fft2d -iquote external/highwayhash -iquote bazel-out/local-opt/genfiles/external/highwayhash -iquote external/png_archive -iquote bazel-out/local-opt/genfiles/external/png_archive -iquote external/zlib_archive -iquote bazel-out/local-opt/genfiles/external/zlib_archive -iquote external/snappy -iquote bazel-out/local-opt/genfiles/external/snappy -isystem external/bazel_tools/tools/cpp/gcc3 -isystem external/protobuf/src -isystem bazel-out/local-opt/genfiles/external/protobuf/src -isystem external/eigen_archive -isystem bazel-out/local-opt/genfiles/external/eigen_archive -isystem external/gif_archive/lib -isystem bazel-out/local-opt/genfiles/external/gif_archive/lib -isystem external/farmhash_archive/src -isystem bazel-out/local-opt/genfiles/external/farmhash_archive/src -isystem external/png_archive -isystem bazel-out/local-opt/genfiles/external/png_archive -isystem external/zlib_archive -isystem bazel-out/local-opt/genfiles/external/zlib_archive -DEIGEN_AVOID_STL_ARRAY -Iexternal/gemmlowp -Wno-sign-compare -fno-exceptions -msse3 -pthread -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c tensorflow/core/platform/default/tracing.cc -o bazel-out/local-opt/bin/tensorflow/core/_objs/lib_internal/tensorflow/core/platform/default/tracing.pic.o).
> In file included from ./tensorflow/core/lib/core/threadpool.h:21:0,
>                  from ./tensorflow/core/platform/default/tracing_impl.h:25,
>                  from ./tensorflow/core/platform/tracing.h:266,
>                  from tensorflow/core/platform/default/tracing.cc:16:
> ./tensorflow/core/platform/env.h:295:11: error: looser throw specifier for 'virtual tensorflow::EnvWrapper::~EnvWrapper()'
> ./tensorflow/core/platform/env.h:50:11: error:   overriding 'virtual tensorflow::Env::~Env() noexcept (true)'
> tensorflow/core/platform/default/tracing.cc:32:19: warning: 'tensorflow::port::dummy' defined but not used [-Wunused-variable]
> Target //tensorflow/tools/pip_package:build_pip_package failed to build
> INFO: Elapsed time: 418.721s, Critical Path: 19.37s
>

I forgot to mention the glibc version so everything together again:
openjdk 1.8.0
bazel 0.5.4
python 2.7
gcc 4.7.2
libstdc++ 4.7.2
glibc 2.15

I guess we're missing the noexcept in the EnvWrapper. Do you mind sending a PR?

I'd be happy to help but I'm not familiar with C++ at all (only C) and it does look like to me to be a C++ specific error.

Just to see if anything changed lately I tried compiling the current master (commit 32ffc5a81eee8c39bbe71536212a773b1ffd4eb2) and it still fails:
gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -B/usr/lib64/ccache -B/usr/bin -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-march=native' '-std=c++0x' '-march=native' -MD -MF bazel-out/local-opt/bin/external/grpc/_objs/grpc++_base_unsecure/external/grpc/src/cpp/client/generic_stub.pic.d '-frandom-seed=bazel-out/local-opt/bin/external/grpc/_objs/grpc++_base_unsecure/external/grpc/src/cpp/client/generic_stub.pic.o' -fPIC -iquote external/grpc -iquote bazel-out/local-opt/genfiles/external/grpc -iquote external/bazel_tools -iquote bazel-out/local-opt/genfiles/external/bazel_tools -iquote external/zlib_archive -iquote bazel-out/local-opt/genfiles/external/zlib_archive -iquote external/boringssl -iquote bazel-out/local-opt/genfiles/external/boringssl -isystem external/grpc/include -isystem bazel-out/local-opt/genfiles/external/grpc/include -isystem external/bazel_tools/tools/cpp/gcc3 -isystem external/zlib_archive -isystem bazel-out/local-opt/genfiles/external/zlib_archive -isystem external/boringssl/src/include -isystem bazel-out/local-opt/genfiles/external/boringssl/src/include -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c external/grpc/src/cpp/client/generic_stub.cc -o bazel-out/local-opt/bin/external/grpc/_objs/grpc++_base_unsecure/external/grpc/src/cpp/client/generic_stub.pic.o).
In file included from external/grpc/include/grpc++/support/async_stream.h:22:0,
                 from external/grpc/include/grpc++/generic/generic_stub.h:22,
                 from external/grpc/src/cpp/client/generic_stub.cc:19:
external/grpc/include/grpc++/impl/codegen/async_stream.h:271:30: error: '<::' cannot begin a template-argument list [-fpermissive]
external/grpc/include/grpc++/impl/codegen/async_stream.h:271:30: note: '<:' is an alternate spelling for '['. Insert whitespace between '<' and '::'
external/grpc/include/grpc++/impl/codegen/async_stream.h:271:30: note: (if you use '-fpermissive' G++ will accept your code)
external/grpc/include/grpc++/impl/codegen/async_stream.h:275:30: error: '<::' cannot begin a template-argument list [-fpermissive]
external/grpc/include/grpc++/impl/codegen/async_stream.h:275:30: note: '<:' is an alternate spelling for '['. Insert whitespace between '<' and '::'
external/grpc/include/grpc++/impl/codegen/async_stream.h:277:30: error: '<::' cannot begin a template-argument list [-fpermissive]
external/grpc/include/grpc++/impl/codegen/async_stream.h:277:30: note: '<:' is an alternate spelling for '['. Insert whitespace between '<' and '::'
external/grpc/include/grpc++/impl/codegen/async_stream.h:280:30: error: '<::' cannot begin a template-argument list [-fpermissive]
external/grpc/include/grpc++/impl/codegen/async_stream.h:280:30: note: '<:' is an alternate spelling for '['. Insert whitespace between '<' and '::'

The setup is still the same (versions of libraries, etc) and I left all questions to ./configure the default.

Is it about which version of the C++ standard is supported by the compiler?

Well, let me ask a well-defined question: which version of the C++ standard do you guys write the code for? C++03, C++11, C+14?

@gunan do you know what the problem might be? I cannot reproduce, but the gcc version @fetchinson is using is older then the one that comes with Ubuntu 14.04 (4.7.2 vs 4.8.4). Other tool versions might be different as well

You need a compiler that supports c++11, anything earlier wont work.
Looks like for full c++11, you need at least GCC 4.8.1:
https://gcc.gnu.org/projects/cxx-status.html#cxx11


Remove unused package

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.0%) to 97.397%

Totals

Change from base Build<PHONE_NUMBER>:
-0.0%

Covered Lines:
449

Relevant Lines:
461

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
449

Relevant Lines:
461

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
449

Relevant Lines:
461

💛  - Coveralls


[WIP] cgroupv2 support

Closes #138.
Goals:

don't get rid of cgroupv1 support
add support for cgroupv2 for all existing metrics pulled out of cgroups
update both the direct cgroup walking logic and the ctrstats code paths

Design:
Details can be found at https://github.com/kubernetes-sigs/usage-metrics-collector/issues/138#issuecomment-2287165401
Summary of changes:

cgroup tree is now unified, no need to specify separate paths for cpu, cpuacct, memory, etc.
CPU:

cpuacct is gone
All cpu metrics can be gathered from cpu.stat file
cgroupv2 cpu metrics are now in microseconds, not nanoseconds

Memory:

An accurate measure of current memory usage is available at memory.current (unlike memory.usage_in_bytes on v1 which was an estimate)
We can now get all OOM information out of memory.events
If we need RSS, we can use anon field out of memory.stat file

For UMC, we need to update both the cgroup-walking code (this PR) and the ctrstats code that uses the CRI library (possibly a follow-up PR)

Taking this out of draft so CI runs.
I was able to get the basic cgroupv2 integration test (copied from the "basic" test) to mostly pass. There was a little bit of weirdness in the output values that I am not sure if I should just update the test case for or if there's an actual problem.
I noticed min.slice on cgroupv1 had a -1 value in the input samples. This did not work with cgroupv2 so I changed those results to 0s, but the test data isn't quite as expected. I'm not sure if there is a special meaning to the -1 CPU usage on cgroupv1.
Otherwise, this should not break any cgroupv1 functionality. I will work on ctrstats next but that should be more of a trivial change, so if folks want to take a look at this now, it should be ready for initial review.
I will also edit my first comment with the dictionary for updating v1 to v2.

/retest-required
flake #126

/triage accepted

/retest-required
flake https://github.com/kubernetes-sigs/usage-metrics-collector/issues/126

/retest-required


Headless Experimental

I'm attempting to use the HeadlessExperimental domain via Puppeteer, but I'm having a hard time getting it to work. I've seen a lot of threads about rendering video from Puppeteer, so I'm sure others will be interested in this.
[headless/devtools] Add BeginFrameControl via DevTools
I realize it's a new feature, not yet supported by Puppeteer, but I'd like to start working with it now.
The stable release of Puppeteer (1.9.0) is running chromium revision 594312, but it looks like the HeadlessExperimental wasn't patched in until 612061, which isn't included in any of the current chromium releases. I'll have to try using a later revision, but I doubt that will completely solve the issue.
It looks like I would need to be able to set options when I call browser.newPage() in order to enable BeginFrameControl (as indicated by the error message below). Also, there is a note in the patch that says it needs to be set at creation time.

Currently, the BeginFrameControl is only supported in headless mode
and can only be enabled at target creation time.

My request is to include options in the call to browser.newPage(), in order to create a page that supports using the headless experimental domain. Of course I can submit a PR, but I need to understand how the internals for that would work. Any advice will be much appreciated.
I'm guessing the change would end up on Browser.js#L174, but I'm unclear on what the format would be.
Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.9.0
Platform / OS version: debian:jessie-slim
Node.js version: 8

What steps will reproduce the problem?
Please include code that reproduces the issue.
    const browser = await puppeteer.launch({...})
    const page = await browser.newPage()
    await cdp.send('HeadlessExperimental.enable')
    const frameData = await cdp.send('HeadlessExperimental.beginFrame', {screenshot: {}})

What is the expected result?
Get some frame data back
What happens instead?
Borks on HeadlessExperimental.beginFrame
content-generator-api-0  | Error: Protocol error (HeadlessExperimental.beginFrame):
Command is only supported if BeginFrameControl is enabled.

For visibility, I've also posted on StackOverflow: https://stackoverflow.com/questions/52806059/headlessexperimental-in-puppeteer

You might want to move this to the DevTools protocol repo: https://github.com/ChromeDevTools/devtools-protocol
You can send whatever cdp commands you want with target.createCDPSession()
const session = await browser.target().createCDPSession();
await session.send('Target.createTarget', {/*whatever options you want*/});

That being said, it is called HeadlessExperimental for a reason. It is almost certainly a waste of time trying to use it before it is finished.

Well, when it becomes stable, I'd like to have an integration with Puppeteer beyond using cdp session to send arbitrary commands. I know it's early for that, but wanted to tinker with it.

@positlabs The beginframecontrol API is very far from getting out of experiment; it's also very hard to use properly without looking into the chromium codebase to understand what is what.
I don't think we'll want this in pptr in any foreseeable future - there are no plans to implement this in headful, so there's no debugging story around it. The right thing to do would be to create another library for this instead of getting this into Puppeteer.

well, in pupy 5.3 you can do this, just by passing args to lauch, my config with chrome stable (not chromium - havnt cheked this, but should work also)
this improved perfomance by 170% for me on pages with video content with different chrome profiles on one server run in parallel
                    '--enable-begin-frame-control'; <--- no need to pass enable frame control on create.target
                    '--enable-surface-synchronization';
                    '--run-all-compositor-stages-before-draw';
                    '--disable-threaded-animation';
                    '--disable-threaded-scrolling';
                    '--disable-checker-imaging';
                    '--disable-gpu';
                    '--disable-gpu-compositing';
                    '--disable-gpu-shader-disk-cache';
                    '--enable-widevine-cdm';

function to render frames on demand from node script
async function renderSingleFrame(client) {
var timer_start = await performance.now();
var timer_end ;
let renderFrameResult;
try {

    renderFrameResult = await client.send('HeadlessExperimental.beginFrame', {
        interval: 60, // read docs on this
        noDisplayUpdates: false
    });

    timer_end = await performance.now();

    log('renderSingleFrame succcess ' + ((timer_end - timer_start) / 1000).toFixed(2) + " seconds.");

} catch (e) {

    timer_end = await performance.now();
    log('renderSingleFrame error ' + ((timer_end - timer_start) / 1000).toFixed(2) + " seconds.");

}

//log('end rendering frame');

return true;

}
call it on demand like below , it will render screen and process js events
renderSingleFrame(client)
where client is
const client = await page.target().createCDPSession(); //you define after creating page
BUT you have to deal with page.mouse and page.click functions, write custom code cause they dont work and crazy lag with native functions
smth like with
//fps implementation
async function fps_move_mouse ( x, y, page ) {
log (`fps_move_mouse x:${x} y ${y}`);
let t_start, t_end, t_total;
let _x = page.mouse._x;
let _y = page.mouse._y;
let steps = await getRandomInt(1, 6);
let _keyboard = page._keyboard;

log (`current x=${_x} y=${y} target x=${x} y=${y} steps=${steps}`);
const fromX = _x, fromY = _y;

for (let i = 1; i <= steps; i++) {
    t_start = await performance.now();

//key stuff
await Promise.race([
Promise.all([
page._client.send('Input.dispatchMouseEvent', {
type: 'mouseMoved',
button: 'none',
x: fromX + (x - fromX) * (i / steps),
y: fromY + (y - fromY) * (i / steps),
modifiers: _keyboard._modifiers,
}),
renderSingleFrame(page._client)
        ]),
       Promise.delay(2000, 'failed')
    ]);

    t_end = await performance.now();
    t_total = await ((t_end - t_start) / 1000).toFixed(2);
    log(`mouse move: step ${i} takes ${t_total}`);

}
return true;

}

Since it's till experimental, had to wrap it up into a plugin: https://github.com/alexey-pelykh/puppeteer-capture


building from source

I'm looking into building oxford_asl from source, to ensure it matches our system and is compiled optimally.
To build the latest release (v3.9.6) from the source tarball obtained via https://github.com/ibme-qubic/oxford_asl/releases, I had to apply the patch below to get it working.
One thing I'm still wondering about though: using the standard cmake; make; make install procedure, I only seem to be getting a part of the binaries/scripts that are mentioned, i.e. there's no basil, epi_reg, fabber_asl, etc.
Is there any documentation available on how these binaries/scripts can be obtained as well?
Please consider including these changes to allow building from source outside of the cloned Git repository more easily in the future?
Note: this patch does assume that you provide correct values via -DGIT_SHA1='...' -DGIT_DATE='...' to the cmake command.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 7568fc4..3b844be 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -50,22 +50,27 @@ target_link_libraries(asl_file ${LIBS})
 include_directories(AFTER ${NEWMAT_INCLUDE_DIR} ${FSL_INCLUDE_DIR} ${FSL_EXT_INCLUDE_DIR})

 # Extract GIT revision for versioning
+if(NOT GIT_SHA1)
 execute_process(COMMAND
   git describe --dirty
   WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}"
   OUTPUT_VARIABLE GIT_SHA1
   ERROR_QUIET OUTPUT_STRIP_TRAILING_WHITESPACE)
+endif(NOT GIT_SHA1)

+if(NOT GIT_DATE)
 execute_process(COMMAND
   git log -1 --format=%ad --date=local
   WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}"
   OUTPUT_VARIABLE GIT_DATE
   ERROR_QUIET OUTPUT_STRIP_TRAILING_WHITESPACE)
+endif(NOT GIT_DATE)

 configure_file(oxford_asl.in oxford_asl @ONLY)
 configure_file(asl_calib.in asl_calib @ONLY)
 configure_file(asl_reg.in asl_reg @ONLY)
 configure_file(quasil.in quasil @ONLY)
+configure_file(readoptions.cc.in readoptions.cc @ONLY)

 INSTALL(PROGRAMS ${CMAKE_CURRENT_BINARY_DIR}/oxford_asl
   ${CMAKE_CURRENT_BINARY_DIR}/asl_calib
diff --git a/readoptions.cc b/readoptions.cc.in
similarity index 95%
rename from readoptions.cc
rename to readoptions.cc.in
index fffc055..ea06e35 100644
--- a/readoptions.cc
+++ b/readoptions.cc.in
@@ -48,7 +48,7 @@ bool ReadOptions::parse_command_line(int argc, char **argv)
     }
     else if (version.value())
     {
-        cout << GIT_SHA1 << " (" << GIT_DATE << ")" << endl;
+        cout << "@GIT_SHA1@" << " (" << "@GIT_DATE@" << ")" << endl;
         return false;
     }
     else if (!options.check_compulsory_arguments())

Hi, apologies for the lack of response, I have not been getting GitHub notifications and a number of issues have been raised here without me realising.
If you are still struggling with this let me know and I'll get some info back to you about building the code from source. However updated versions of all the oxford_asl tools are available in FSL 6.0.1 and later so in most cases it's not necessary to build from source.

Closing historical issue


Assertion in test_kdtree failed

After small modifications regarding linking to Eigen and Tensorflow I was able to compile code and run tests. However there is a lot of lines like one below that are suggesting that something is not right.

Generated points...
/home/jbialas/Projects/tf_kdtree/src/kdtree.hpp:310: void TreeTraversal<T, dims>::moveToLeftChild() [with T = double; unsigned char dims = (unsigned char)'']: block: [20,4,0], thread: [0,0,0] Assertion current_level < partition_info->levels failed.

I am using GCC-11.3.0 with CUDA 11.8.
I am linking with system Eigen 3.4.0, Assimp 5.2.5 and Tensorflow 2.10.0
I will be happy to provide more information and even provide some contribution if that will help, but maybe this is just a simple fix.

Thanks for reporting this problem. I just retried building the library from the ground up and also noticed that it's not compatible with the current master branch of Eigen. I'll fix the library to Eigen 3.4 to avoid these errors in the future.
I can not however reproduce the error you mentioned, also in Debug compilation. Do you also have trouble with the CPU implementation or did you modify any other parts? It seems the assertion only fails in CUDA.
Here's my configuration:

GCC 9.4
CUDA 11.2
(Tensorflow 2.10)

test_kdtree actually does not use python iirc and is purely for testing the C++ implementation.

I was able to test following setups
CUDA 11.2 + GCC9 - OK
CUDA 11.3 + GCC9 - TEST FAIL
CUDA 11.4 + GCC9 - TEST FAIL
CUDA 11.8 + GCC11 - TEST FAIL
I don't have working GCC10 right now, but I think this is not a GCC's fault. I have analyzed logs from compilation for first two cases and there is a lot warnings for the 11.2 while less with 11.3. Lot of them seem to be harmless
/usr/include/tensorflow/Eigen/src/Core/Reshaped.h(139): warning:
__host__ annotation is ignored on a function("ReshapedImpl")
that is explicitly defaulted on its first declaration

However there are warnings that are more serious and they are still warnings
/home/jbialas/Projects/tf_kdtree/src/kdtree.hpp(313): warning:
calling a __host__ function("T1 TreeTraversal<float, (unsigned char)1>
::compLeftLeafInd<unsigned int, unsigned int> (T1, T2)")
from a __host__ __device__ function("TreeTraversal<float, (unsigned char)1>
::getLeftLeaf const") is not allowed

It is even more interesting that this specific warning is not present for 11.2 build but appears in build log from 11.3.
On the other hand there are few warnings like one below that suggest something bad might happen
warning: dynamic initialization is not supported for a function-scope
static __shared__ variable within a __device__/__global__ function

And again I don't know if for some reason from any version of CUDA this might cause some issues, but there is nothing more that can indicate problems with the code.
Any hints what could be done to diagnose cause of a problem in case of CUDA 11.3 and newer?

Thanks for the thorough analysis. I can confirm that I run into the same problem with CUDA 11.4. I found a few hints online that higher versions of CUDA break the compatibility with Eigen, but no pointers what causes the problem or how to fix it.
Since Eigen is only used for some functions in the CUDA kernels (subtraction, and squared norm mostly), I think it's worth considering a simple replacement.

I found a solution, and it is not related to Eigen.
I have analyzed warnings provided by nvcc and there were a lot of them mentioning that some functions can not be called from device context. This was odd as there were nothing illegal with them (in my opinion). I noticed that even though I have add --expt-relaxed-constexpr flag to CUDA_NVCC_FLAGS, couple templated functions were still reported as problematic. Turns out it was enough to mark them explicitly CUDA_HOSTDEV`.
I will provide a fix as a PR if you don't mind.

That would be really great! If you make the branch editable, I could merge in the Eigen fix and some minor changes.

Fixed in #2. Thank you for your contribution!


Support HTTPS on Linux and Windows

Description
Fails https cert copy on Manjaro Linux on Raspberry Pi4.
Steps to reproduce
ran nitro init...
Updating hosts file (you might be prompted for your password)
[sudo] password for matt:
Adding sites to hosts file…
  … modifying hosts file ✓
  … getting certificate for Nitro… ✓
Installing certificate (you might be prompted for your password)
mv: cannot move '/tmp/nitro-cert304261744' to '/usr/local/share/ca-certificates/nitro.crt': No such file or directory
Unable to automatically add certificate

To install the certificate, run the following command:
  sudo mv /tmp/nitro-cert304261744 /usr/local/share/ca-certificates/nitro.crt
  sudo update-ca-certificates
Nitro is ready! 🚀
[matt@pi4 .nitro]$ sudo mv /tmp/nitro-cert304261744 /usr/local/share/ca-certificates/nitro.crt
mv: cannot move '/tmp/nitro-cert304261744' to '/usr/local/share/ca-certificates/nitro.crt': No such file or directory
[matt@pi4 share]$ sudo update-ca-certificates
sudo: update-ca-certificates: command not found

/tmp/nitro-cert304261744 does exist, but /usr/local/share/ca-certificates does not and i'm thinking the destination directory isn't being made via the above command.
I've made it myself and moved the cert - so that's there now, but the suggested update-ca-certificates isn't a utility ?
Additional info

Nitro version: 2beta3

Not sure I'm following you, but there is no such package in the Manjaro or any Arch based distro - update-ca-certificates appears to be Ubuntu specific.
https://wiki.archlinux.org/index.php/User:Grawity/Adding_a_trusted_CA_certificate

On Arch based Linux it appears the nitro.crt should be stored at /etc/ca-certificates/trust-source/anchors and then the utility should be run as sudo update-ca-trust
This appears to have run correctly - though I've not tested an actual Nitro project yet...

Alright, I might have to make this tricky to support multiple distros...
Can you provide the output of lsb_release --description?
On Ubuntu based devices it outputs the following:
$ lsb_release --description
Description:	Ubuntu 20.04.2 LTS

I might be able to write a "finder" interface for the linux distro based on the description to make the commands more automatic..
I should probably be more clear on the errors (e.g. path does not exists (but we are prompting for root permissions so we could make those directories)...

[matt@pi4 test]$ lsb_release --description
Description:	Manjaro ARM Linux

I'm a little surprised it doesn't reference Arch, but then I'd also have expected yours to reference Debian.
And yes I found it odd it couldn't make those directories via a sudo mv but I believe that might be an optional flag, or just an issue with where it was trying to make the path. Either way, that was the wrong path for Arch based distros, and I didn't have an issue moving it with sudo mv nitro.crt /etc/ca-certificates/trust-source/anchors

@MattWilcox I don't have Manjaro but I'm fairly confident in the changes to the trust command mentioned above. Here is a linux arm build (marked as beta 3) but will be the next beta with the changes to certificate installation.
nitro_linux_arm64.tar.gz

@MattWilcox beta 5 is out with changes to the certificate installation on linux machines. Closing this out. Thank you for the report!


Will not download 1080p version of the file

I set it to download the highest video quality and it only downloads the 720p version even though 1080p is available, as I was able to verify it with Ant video downloader.
The course I was trying to download is this:
https://www.udemy.com/course/crash-course-electronics-and-pcb-design/

Yes I am aware that Udeler is only able to download 720p videos.  I will keep this issue open until I fix it.

@FaisalUmair great tool! Keep up the excellent work! Do you have any update on this issue?

Im having this issue as well

Same here

As of 1.8.2 this appears to be working. During debugging I noticed that a lot of the videos but not all in a course were 720p. I console printed the video list and some were 1080p. Set the quality to max and started watching and when it got to the 1080p videos the quality icon changed and the downloaded video was 1080p. If you change the settings you need to restart the app. I also set it to 480p and restarted the program and all the videos downloaded as 480p. So at least mine appears to be working fine.

Hmm, definitely not working for me in 1.8.2, everything is still capped at 720p.  I have tried both 1080p and Max and I did restart the app each time after changing and saving the setting.


Input type TYPE_TEXT_VARIATION_EMAIL_ADDRESS but keyboard doesn't show @ character

[x] I have verified there are no duplicate active or recent bugs, questions, or requests
[x] I have verified that I am using the latest version of Material Dialogs.
[x] I have given my issue a non-generic title.
[x] I have read over the documentation (before asking questions on how to do something).

Include the following:

Material Dialogs version: <IP_ADDRESS>
Device OS version: 7.10
Device Manufacturer: Samsung
Device Name: Galaxy S7

Also, please wrap Java with correct syntax highlighting.
System.out.println("Hello, world!");

Reproduction Steps

Create a dialog has EditText with .inputType(InputType.TYPE_TEXT_VARIATION_EMAIL_ADDRESS)

Expected Result
When that dialog is shown and EditText is focused, the keyboard should has @ character to allow user input the email quickly.
Actual Result
No @ character in the keyboard.

Well, this isn't an issue with this library. The flags you provide are passed directly to the EditText, it's all Android framework stuff.

You may need to include the TYPE_CLASS_TEXT flag as seen here.

Thanks @afollestad . I follow your guide to combine .inputType(InputType.TYPE_CLASS_TEXT | InputType.TYPE_TEXT_VARIATION_EMAIL_ADDRESS) and now it works as expected. Thanks for your support.


Cedar Script creates applications in one space only  and its not spread across the spaces.

From the general setup,Each batch will have 20 different applications of different sizes, comprising of  25 Instances created in each space.
For a batch of 10, We have 200 applications getting created which should be spread across the 10 Spaces.
However, All the 200 applications are getting created in One Space alone – that in the first space..The rest of the spaces doesn’t have any.
Can you please clarify this scenario?
Thanks and Regards,
Kesavan

Hi, @K7king,
The Diego team hasn't made any changes to this release in quite some time, so I would be surprised if it suddenly stopped working as intended. Could you please provide the manifest you're using (with credentials redacted!) and the output from running ./cedar_script from /var/vcap/jobs/cedar/bin?
Thanks,
Eric, CF Diego PM

Closing due to inactivity. If you still have questions, or can provide reproduction steps, please feel free to open a new issue.
Best,
Eric

Dear Eric,
We have found the issue. The Approute Pattern was pointing to "http" so that the api was unreachable and gave timedout error  and hence the scirpt was unable to deploy on other spaces.We changed to "https"and  for our case a certificate issue was there and fixed it. Now its working fine.
Thanks for your kind response.
Best Regards,
Kesavan.


Port multipart goodness to to 0.18.x branch

:D

seems to pass all tests, but trying it on a small client I cannot get it to run properly, so I'm double checking first if there is a problem

Bugs have been fixed, and tested with postman. See notes on #1728.

@rossabaker mostly that the #1728 version doesnt deprecate the other stuff for the sake of MiMa, it straight up deletes the old version.

Yeah, it's going to have to to get rid of that dependency.  I am pro-deprecation until it exerts drag, like pulling in a new dependency.
Okay, merging this one, will roll forward, and will use #1728 as a guideline if the merge is ugly.


Delete mfxscd.h

Please fix buildbot/build-gcc-8.1.0.
Is gcc-8.1.0 a POR for mss2018_r2?

The build failure is:
/localdisk/bb/worker/build-gcc-8_1_0/build_dir/repos/MediaSDK/samples/sample_plugins/vpp_plugin/include/mfx_multi_vpp.h:30:65: error: ‘*<unknown>.MFXVideoMultiVPP::<anonymous>.MFXVideoVPP::m_session’ is used uninitialized in this function [-Werror=uninitialized]
     MFXVideoMultiVPP(mfxSession session) : MFXVideoVPP(m_session)

It is not related to Oleg's change. It is just building mss2018_r2 with gcc-8. We have fixed build issues for gcc-8 in the master, this one inclusively. Looks like these changes were not ported. I believe, we need to port them, better to have compilers supported on the key branches.

GCC 8.1 support not targeted for this branch


Agent does not work with RackApp on Ruby 2.7

The new relic agent does not work together with RackApp on ruby 2.7.
Description
After upgrading to Ruby 2.7 our App did not start anymore in production env. After digging around it seems that one of the ruby 2.7 fixes splats an argument and the RackApp argument is 'converted' to a hash. RackApp then calls serialize on the argument expecting it would be a custom RackApp class, but instead it is a hash. This results in undefined method 'serializer' for #<Hash:0x00007fa43fb8c758> (NoMethodError) and the app does not start.
Because we have no problems running this combination in Ruby 2.6 I think the problem is the splat here int the Ruby 2.7 path:
https://github.com/newrelic/newrelic-ruby-agent/blob/dev/lib/new_relic/agent/instrumentation/middleware_proxy.rb#L30-L40
Expected Behavior
No NoMethodError when using the ruby agent and Rack App in the same app. The agent should not change arguments to rack apps (in this case it should not convert it to a hash).
Troubleshooting or [NR Diag]
Traceback from test app.
rails s
=> Booting Puma
=> Rails <IP_ADDRESS> application starting in production
=> Run `rails server --help` for more startup options
Exiting
Traceback (most recent call last):
	96: from bin/rails:9:in `<main>'
	95: from [...]/.rvm/gems/ruby-2.7.2/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
	94: from [...]/.rvm/gems/ruby-2.7.2/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `load_dependency'
	93: from [...]/.rvm/gems/ruby-2.7.2/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `block in require'
	92: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	91: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	90: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	89: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	88: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	87: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/commands.rb:18:in `<main>'
	86: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/command.rb:46:in `invoke'
	85: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/command/base.rb:69:in `perform'
	84: from [...]/.rvm/gems/ruby-2.7.2/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
	83: from [...]/.rvm/gems/ruby-2.7.2/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
	82: from [...]/.rvm/gems/ruby-2.7.2/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
	81: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:138:in `perform'
	80: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:138:in `tap'
	79: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:147:in `block in perform'
	78: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:39:in `start'
	77: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/server.rb:311:in `start'
	76: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/server.rb:379:in `handle_profiling'
	75: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/server.rb:312:in `block in start'
	74: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/server.rb:422:in `wrapped_app'
	73: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/server.rb:249:in `app'
	72: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/server.rb:349:in `build_app_and_options_from_config'
	71: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/builder.rb:66:in `parse_file'
	70: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/builder.rb:105:in `load_file'
	69: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/builder.rb:116:in `new_from_string'
	68: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/builder.rb:116:in `eval'
	67: from config.ru:3:in `block in <main>'
	66: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:53:in `require_relative'
	65: from [...]/.rvm/gems/ruby-2.7.2/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require'
	64: from [...]/.rvm/gems/ruby-2.7.2/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `load_dependency'
	63: from [...]/.rvm/gems/ruby-2.7.2/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `block in require'
	62: from [...]/.rvm/gems/ruby-2.7.2/gems/zeitwerk-2.4.0/lib/zeitwerk/kernel.rb:34:in `require'
	61: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	60: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	59: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	58: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	57: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	56: from [...]/workspace/nr-rackapp-test/config/environment.rb:5:in `<main>'
	55: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/application.rb:363:in `initialize!'
	54: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:60:in `run_initializers'
	53: from [...]/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0/tsort.rb:205:in `tsort_each'
	52: from [...]/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0/tsort.rb:226:in `tsort_each'
	51: from [...]/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0/tsort.rb:347:in `each_strongly_connected_component'
	50: from [...]/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0/tsort.rb:347:in `call'
	49: from [...]/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0/tsort.rb:347:in `each'
	48: from [...]/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0/tsort.rb:349:in `block in each_strongly_connected_component'
	47: from [...]/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0/tsort.rb:431:in `each_strongly_connected_component_from'
	46: from [...]/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
	45: from [...]/.rvm/rubies/ruby-2.7.2/lib/ruby/2.7.0/tsort.rb:228:in `block in tsort_each'
	44: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:61:in `block in run_initializers'
	43: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:32:in `run'
	42: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:32:in `instance_exec'
	41: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/application/finisher.rb:184:in `block in <module:Finisher>'
	40: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/application/routes_reloader.rb:10:in `execute'
	39: from [...]/.rvm/gems/ruby-2.7.2/gems/activesupport-<IP_ADDRESS>/lib/active_support/file_update_checker.rb:83:in `execute'
	38: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/application/routes_reloader.rb:29:in `block in updater'
	37: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/application/routes_reloader.rb:20:in `reload!'
	36: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/application/routes_reloader.rb:40:in `load_paths'
	35: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/application/routes_reloader.rb:40:in `each'
	34: from [...]/.rvm/gems/ruby-2.7.2/gems/railties-<IP_ADDRESS>/lib/rails/application/routes_reloader.rb:40:in `block in load_paths'
	33: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:59:in `load'
	32: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:59:in `load'
	31: from [...]/workspace/nr-rackapp-test/config/routes.rb:3:in `<main>'
	30: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:53:in `require_relative'
	29: from [...]/.rvm/gems/ruby-2.7.2/gems/zeitwerk-2.4.0/lib/zeitwerk/kernel.rb:34:in `require'
	28: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	27: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	26: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	25: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	24: from [...]/.rvm/gems/ruby-2.7.2/gems/bootsnap-1.4.9/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	23: from [...]/workspace/nr-rackapp-test/lib/hello_world.rb:5:in `<main>'
	22: from [...]/workspace/nr-rackapp-test/lib/hello_world.rb:7:in `<class:HelloWorld>'
	21: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/singleton_methods/http_methods.rb:6:in `get'
	20: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/singleton_methods/route_handling.rb:23:in `add_route'
	19: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/router.rb:25:in `register_endpoint!'
	18: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/router.rb:83:in `compile_endpoint!'
	17: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/router/tree.rb:17:in `add'
	16: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/router/tree/branch.rb:8:in `set'
	15: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/router/tree/leaf.rb:15:in `set'
	14: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/router/tree/leaf.rb:35:in `save_endpoint'
	13: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/router/tree/leaf.rb:44:in `split_save_to_extnames'
	12: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/router/tree/vein.rb:5:in `set'
	11: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/router/tree/vein.rb:23:in `create_app'
	10: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/endpoint.rb:34:in `to_app'
	 9: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/endpoint/builder.rb:10:in `to_app'
	 8: from [...]/.rvm/gems/ruby-2.7.2/gems/newrelic_rpm-6.13.1/lib/new_relic/agent/instrumentation/rack.rb:138:in `to_app_with_newrelic_deferred_dependency_detection'
	 7: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/builder.rb:235:in `to_app'
	 6: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/builder.rb:235:in `inject'
	 5: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/builder.rb:235:in `each'
	 4: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/builder.rb:235:in `block in to_app'
	 3: from [...]/.rvm/gems/ruby-2.7.2/gems/rack-2.2.3/lib/rack/builder.rb:158:in `block in use'
	 2: from [...]/.rvm/gems/ruby-2.7.2/gems/newrelic_rpm-6.13.1/lib/new_relic/agent/instrumentation/middleware_proxy.rb:37:in `new'
	 1: from [...]/.rvm/gems/ruby-2.7.2/gems/newrelic_rpm-6.13.1/lib/new_relic/agent/instrumentation/middleware_proxy.rb:37:in `new'
[...]/.rvm/gems/ruby-2.7.2/gems/rack-app-7.6.4/lib/rack/app/middlewares/configuration.rb:8:in `initialize': undefined method `serializer' for #<Hash:0x00007fa43fb8c758> (NoMethodError)

Steps to Reproduce
Simple Rails Test App.
New Rails App, just added RackApp with a dummy endpoint (hello_world.rb) and then added the agent. Without agent the app works, with agent the app crashes.
https://github.com/mitnal/nr-rackapp-test
Clone test rails app, bundle, and just run rails s.
In our real app the problem only occurred in production env (I think because of the agent configuration) but the test app also crashes in development. If not try: RAILS_ENV=production rails s.
Your Environment
ruby 2.7.2p137
rails (<IP_ADDRESS>)
newrelic_rpm (6.13.1)
rack-app (7.6.4)
rack (2.2.3)
I can reproduce this problem locally on my Mac and also on Heroku so it should be OS independent.

Hello, @mitnal
I really appreciate the linked repo for reproducing this issue, and I can confirm that I am seeing the same issue when using newrelic on it. The secion of code for the 2.7 kwarg warnings that you pointed out does seem to be related to the problem based on my testing. This is related to some of our other upcoming work in our bug smash. I linked it to that milestone so we can take a closer look into this issue.
Thank you for bringing this to our attention

I came across this issue when I ran into similar issues, objects being converted to plain hashes.
However, we were already running ruby-2.7.0 and nr-<IP_ADDRESS>4. The issue started when upgrading nr to at least <IP_ADDRESS>5. The issue remains on ruby-2.7.2.
diff

When adapting the agent for Ruby 2.7, we were over-zealous in making changes to support Ruby 2.7.  Rack, and therefore, RackApp do not pass keyword arguments, so it was unnecessary change to double-splat the last argument in the rack instrumentation.
I believe this is fixed and I verified the fix against a simple RackApp across all the Rubies, but would definitely appreciate feedback from anyone (@mastermatt or @mitnal) affected.  If you have time to test, here's how you can do so:
Update your Gemfile to:
gem 'newrelic_rpm',
  git: 'https://github.com/newrelic/newrelic-ruby-agent.git',
  branch: '486_rack_app_fix'

and bundle install and give it a whirl.  If this resolves your issues and does not generate deprecation warnings in Ruby 2.7, then we're good to go.

Hi @mwlang this works without problems in our production and the test app. Thanks.
If I reactivated the deprecation warnings correctly on 2.7.2 then there are no deprecation warnings 😉.

@mitnal thank you for verifying the changes work.


1.7.10

Version of Boardwalk:1.7.10
Version of Android:4.4.4
Device model:sm_t116Nu
Description of the problem:my minecraft loading

I want my minecraft fast


As a user, I would like to have the ability to choose which kernel is used during local pipeline execution

When a pipeline is executed it appears that the kernel that's specified in the notebook spec is used to run the notebook. Now sure how likely this is but could there be a use case where a user might want to choose a different kernel during pipeline execution?
 Based on that, if you want to change to a different kernel, please change ad save that via the jupyterlab ui.


Fix new lint reported after https://dart-review.googlesource.com/c/sdk/+/350920

Analyzing flutter...

   info • The value of the argument is redundant because it matches the default value • dev/integration_tests/release_smoke_test/lib/main.dart:18:77 • avoid_redundant_argument_values

It looks like this was fixed by https://github.com/flutter/flutter/pull/143253. Closing as fixed.


increase number of rows pandas will print to 1000, issue 259

fixes #259

I have looked at the staging output to confirm the desired effect (long tables are printed). For example: https://oscovida.github.io/staging/260/html/Argentina.html


Create an online app that uses bubblewrap to generate APK

Should we create a containerized web app the generates the APK from an online PWA using the bubblewrap CLI tool

Have you checked https://www.pwabuilder.com/? Their APK generation is powered by Bubblewrap.

Oop then it might be helpful to mention that in the documentation that can help initial developers

Sounds like a good idea. I think it's worth creating a section on the docs about GUI tools powered by Bubblewrap. @jgw96 FYI

BTW currently it doesn't work https://github.com/pwa-builder/CloudAPK/issues/20

Thanks for filing that. Added some details to the issue.

Hey, sorry about the APK not working. Something must have busted over the weekend. We'll have it back up shortly. I'll post here when it's up.

Hello all! Thanks for the ping @andreban . As Judah said, looks like our service went down over the weekend. I am currently looking into this.

@andreban where do you think the best location to add this information might be.
Just first thoughts
Should we set up a GitHub page that tells about bubble wrap?

@amanintech We can add a GUI Tools section to README.md. Creating a Github page would be great too, as we could host tsdocs for the core library too.

Awesome let's do that. Will be throwing some initial templates.

I almost forgot about this one. @andreban  can you please assign this to me ?

@amanintech done, thanks for this!


Small bug with the flamethrower

When I shoot with the flamethrower it flicks a lot in the enemy's view (my friend told me this was happening because I wasn't even noticing)
Config: https://www.mediafire.com/file/0oxqtqj7w9cgsxb/N.fw/file

ok

ok

are u aimbotting with the flame thrower or are you manually shooting with the flamethrower.

are u aimbotting with the flame thrower or are you manually shooting with the flamethrower.

i was using aimbot

yeah the flamethrower doesn't have pSilent so ofc u flick.


Error during local installation

Describe the bug
Executing the installation script using
curl -sSfL https://lstn.dev/get | sh -s -- -b /usr/local/bin
returns
install: /usr/local/bin//lstn: Permission denied

Please include:

v0.3.1
macos/arm64

Steps to reproduce the behavior
Execute the command for local installation on macOS.
Expected vs actual behavior
Should install the binary in /usr/local/bin/lstn instead of
install: /usr/local/bin//lstn
Looks like an extra '/' is being appended before lstn
Logs
listendev/lstn info checking GitHub for latest tag
listendev/lstn info found version: 0.3.1 for v0.3.1/macos/arm64
install: /usr/local/bin//lstn: Permission denied

You need root privileges (sudo).

@jadoonf you need to give root privileges to the process installing it, not the one downloading it. :)

curl -sSfL https://lstn.dev/get -o install.sh
chmod +x install.sh
sudo ./install.sh -b /usr/local/bin

Works! Updated the docs accordingly.

@leodido do we intend on converting this into a one liner? and cleaning up the install.sh script post install?

If you look at other projects you'll notice they also use the one-liner we currently have in the README.
This is because we assume the user has privileges for the destination directory. Also installation with privileges (eg., curl | sudo sh) is universally considered bad practice nowadays. Thus, I'd avoid having it (or something similar) in the README.
But feel free to change it if you feel so. Closing this for now.


Separate rendering process in two parts

At the moment, we have a render process that is a one pass process. All features are converted each time when the map is drawn in their native counterparts (LineString is converted each time the map is drawn in a SKPath). This costs much time.
In other projects, this part is divided in two parts: rendering and drawing. In rendering the map is layouted, features are converted to their native counterparts, it is determined which parts are drawn. This is only needed once. After that, the feature could be drawn often to the screen.
So it would be good to have this distinguishing between these two parts: rendering and drawing.

The RasterizingTileProvider creates an SkPicture at the moment the file is fetched. In that case a two step solution would not add anything. Do you also see it like that, or do I mis anything?
Could you refer to an example project that has this distinction?

At the moment, we have a render process that is a one pass process. All features are converted each time when the map is drawn in their native counterparts (LineString is converted each time the map is drawn in a SKPath). This costs much time.

You say every time, but is it not just te first time it comes into view and after that the cached version in RenderedGeometry is used? Nevertheless, it should not happen at all during drawing.

I can not put much time into this discussion at the moment but think it is important so I just want to say a few things.
Googling on 'distinction drawing rendering graphics' does not produce a lot of results but I think it is good to distinguish between the two principles and to use distinguishing terminology. Perhaps painting could be used instead of drawing though.
Rendering
Create a platform specific resource.
SKPath path = ToSKPath(feature, style);

Drawing or Painting
Draw/Paint the platform specific resource to the canvas.
canvas.DrawPath(path, paint);

I have a slight preference for paint right now because draw is a more general term than paint. Also, we currently use draw 1271 times in our code, and paint 262 times (searching  without match case and without whole word in cs files). In skia the event is also called PaintSurface (but yes, the calls themselves are called '.DrawXxxx' so there is something to say for both). But if you (@charlenni) and @inforithmics prefer draw we just go for that. Other opinions also welcome.
No rendering in the draw/paint loop
With that terminology in mind I can say I agree with the idea that there should be no rendering in the draw/paint loop. This could be in our design guidelines.
How should it work?
In the 'Rastering tile layer' PR of @inforithmics the tile is transformed to an SkPicture in the fetch thread, directly after fetching. So this abides to the guideline, but there are probably many other options to arrange this. This is something to discuss here. Unfortunately I did not put any thinking into this yet 🤔

@charlenni This is an area where I don't have much expertise. But I like the General idea. I think this is the way how Games are rendered so that no artifacts appear on displaying the Image. And the UI Thread is much faster displaying the image, the rendering is done on background threads.  But for me at the nts migration is more important. But when Nts migration is done this should be the next Task. Because it improves the General responsivenes of Mapsui, especially on slower devices.

@pauldendulk For me, it isn't so urgent and if you don't have time, then let postpone this. But we should have this in mind, because it could be a great speed improvement. E.g. animations should profit from this. And surely all static layers.

I like this approach. It is good to have to have the long term goals in the back of our minds. Although this could be relevant in the near future. I added it to the guidelines https://github.com/Mapsui/Mapsui/blob/master/docfx/documentation/contributors-guidelines.md#no-rendering-in-the-drawpaint-loop


Header parsing panic kills chain runtime

Crate
Hermes ibc_relayer v0.7
Summary of Bug
When running hermes ibc_relayers between Osmosis and Cosmoshub, packet worker stop after panic.
Log of the error can be found at this link:
https://pastebin.com/uGDZSFjU
config file can be provided if needed.
on gaiad side, no logs exept this line at hermes startup :
9:49AM ERR Failed to read request err="websocket: close 1006 (abnormal closure): unexpected EOF" module=rpc-server protocol=websocket remote={"IP":"<IP_ADDRESS>","Port":43862,"Zone":""}
9:49AM ERR error while stopping connection error="already stopped" module=rpc-server protocol=websocket

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Thank you for flagging this issue! We're investigating it and would appreciate if you could share your config.toml file.

Hi, this is my config for hermes right now
https://pastebin.com/Pbca30tz


[FEATURE] Add Drop-Down Menu for Skills Section

Description
Overview:
Implementing a drop-down menu for skill selection improves user experience, boosts efficiency, and minimizes errors in the skills section of the resume project.
Proposed Solution:
Implement a drop-down menu displaying predefined skills, allowing users to easily select their skills. Update the UI for a visually appealing and consistent design.
Screenshots
No response
Additional information
Tasks:

Utilize APIs, whether public or custom-made, to compile a comprehensive and professional list of relevant skills.
Create a drop-down menu component for skill selection.
Update UI to accommodate the drop-down menu.

Expected Benefits:

Improved user experience and reduced errors.
Consistent formatting for professional presentation.
Scalability for adding more skills in the future.

I also want to work upon this issue. Thank you.

I also want to work upon this issue. Thank you.

I have a genuine interest in this issue, which is why I brought it up. I have been given the assignment and I am actively working on it now. Thank you.


[Vendor] Update go-ldap to v3.0.3

go get -u had an issue with it, this fix it :)

Codecov Report

Merging #13163 into master will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13163   +/-   ##
=======================================
  Coverage   42.08%   42.09%
=======================================
  Files         681      681
  Lines       75121    75121
=======================================
+ Hits        31613    31619    +6
+ Misses      38357    38352    -5
+ Partials     5151     5150    -1

Impacted Files
Coverage Δ

modules/auth/ldap/ldap.go
46.81% <ø> (ø)

modules/queue/unique_queue_disk_channel.go
53.84% <0.00%> (-1.54%)
:arrow_down:

modules/git/repo.go
46.70% <0.00%> (-0.51%)
:arrow_down:

services/pull/pull.go
40.78% <0.00%> (ø)

modules/git/utils.go
77.04% <0.00%> (+3.27%)
:arrow_up:

modules/charset/charset.go
75.28% <0.00%> (+4.49%)
:arrow_up:

modules/util/timer.go
85.71% <0.00%> (+42.85%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 25f7e1c...f34757e. Read the comment docs.

@techknowlogick somehow missed that ... now it works as it should :)


Tap-macro with double quotes

When using a tap-macro with a double quotes symbol, the associated letter is transformed into uppercase. For example, #(a ") will be converted to A ".
To reproduce:
#(a ")

In the terminal with this tap-macro config #(a ") will print A" initially. Afterward, it will function normally without uppercase transformation.

Address it by delaying the characters that are on the shift layer.


[IOTDB-2346] Select INTO Reports NPE for time series containing binary values of NULL

See IOTDB-2346 for more details.

Coverage decreased (-0.02%) to 67.62% when pulling 332187eeeb09c24958262e4bf28fde836ed5a148 on iotdb-2346 into 9baeae3f5cd7b5037607e7e49cbc0a763ff17cb3 on master.


update proj4

Original report by Reimar Bauer (Bitbucket: ReimarBauer, GitHub: ReimarBauer).

we should go to
proj4 6.0.0

for 2.0 we removed the proj4 dependency


Allow to send events as announce to the channel

This PR introduces the option to send events as notice in logstash-output-irc.
The default remains sending as messages.

hey, any updates on the PR?

Hi, any updates?

@makefu I don't know if anyone is currently a maintainer on this Logstash plugin.

@jordansissel That is quite unfortunate, how does this package then become part of the upstream logstash available plugin list?

it has been almost 1 year now, any update?

neat, thanks!


Create conversations_pt-BR.json

Extend conversations to suppotr portuguese language

Thank you, this is an awesome addition. I will review and merge this as soon as I can.

This looks great! Thank you for contributing this!


Create sample exercises for User study

Expected Behavior
Create tasks for user study which will be used in sample pipelines. Using this task, we will ask user to define a new pipeline.
Actual Behavior
do not exists.
Steps to Reproduce the Problem
none
Additional Info
Create tasks for user study.
As of now, things on top of my list are

[ ] Build with kaniko and push task
[ ] Make task
[ ] Integration Test Task
[ ] Deploy Task

/assign @tejal29

Done. Pushed on branch https://github.com/tejal29/build-pipeline/tree/add_user_study/cuj/docs


elasticsearch 1.6.2 (new formula)

Elasticsearch 1.6.2 -- note the branch on my fork is called elasticsearch16-2; I can change that if that convention matters. I've tested this one with 1.6.2 and brew install homebrew/versions/elasticsearch16.
One question -- is this being done redundantly wherein the cellar install ends up being /usr/local/Cellar/elasticsearch16/1.6.2 ; this seems wrong but also is in line with the output from brew install homebrew/versions/elasticsearch14 (which installs, similarly, to /usr/local/Cellar/elasticsearch14/1.4.5); neither of which can guarantee the user's symlinks are safely in place.
So 2 additional notes:

I put it in as a PR since it will function as-is currently, but I'm also amenable to adding the checksums for other os x versions (guidance would be appreciated). In the meantime, my guess is this would be useful to start.

If anyone has thoughts on whether it makes more sense to utilize the previously-included-as-canonical version of elasticsearch (1.6.0 was in the main homebrew formulae), as opposed to this one (the stable release, 1.6.2), I'm eager to hear your thoughts!

brew install homebrew/versions/elasticsearch16
==> Installing elasticsearch16 from homebrew/homebrew-versions
==> Downloading https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.6.2.tar.gz
######################################################################## 100.0%
==> Caveats
Data:    /usr/local/var/elasticsearch/elasticsearch_patricknavarromahoney/
Logs:    /usr/local/var/log/elasticsearch/elasticsearch_patricknavarromahoney.log
Plugins: /usr/local/var/lib/elasticsearch/plugins/
Config:  /usr/local/etc/elasticsearch/

To reload homebrew/versions/elasticsearch16 after an upgrade:
  launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.elasticsearch16.plist
  launchctl load ~/Library/LaunchAgents/homebrew.mxcl.elasticsearch16.plist
Or, if you don't want/need launchctl, you can just run:
  elasticsearch --config=/usr/local/opt/elasticsearch16/config/elasticsearch.yml
==> Summary
🍺  /usr/local/Cellar/elasticsearch16/1.6.2: 34 files, 30M, built in 11 seconds

note the branch on my fork is called elasticsearch16-2; I can change that if that convention matters

I frequently name my branches after songs; feel free to call your branches whatever you like, within reason :smile:.

One question -- is this being done redundantly wherein the cellar install ends up being

Everything gets installed into HOMEBREW_CELLAR/name/version/*. This is standard for the whole of Homebrew.

neither of which can guarantee the user's symlinks are safely in place.

I don't quite get the question here?

If anyone has thoughts on whether it makes more sense to utilize the previously-included-as-canonical version of elasticsearch

Given we've called this elasticsearch16 rather than elasticsearch160 it should always be the latest release on that branch, which is in line with the expectation of the other elasticsearch formula in Versions here. If 1.6.2 is the latest 1.6.x that's great.

Very cool! I just saw this, and I appreciate you explaining. Good point re the convention/rule you outline makes it easier for folks to stay consistent with that, and not have that mess of data folders and config symlinked-to-the-lib (->sneaky and hard-to-diagnose bugs e.g. things that would be inconsistently linked/accessed, potentially running configs for wrong versions).
I'll refactor this PR later today, based on the notes you've left here! Thanks


After restart of floto-server it does not obtain correct container states

But each subsequent command works properly

Seems to be fixed in 2.x branch


feat(multithread): add rayon & par_iter for multithreaded execution

Description
This is a feature-gated implementation of multi-threading for this project. This utilizes rayon for performing multi-threading.
This PR is raised against #128.
Reasoning
Following are some of the decisions taken while building the solution. Feel free to comment on any of them, as I might have missed something during the process.

Reason for using #[cfg(...)]

In the current implementation of the code, all the smart pointers used aren't thread-safe. This being the case, thread-safety wasn't a requirement for the implementation as these pointers are much more performant than their thread-safe alternatives Rc<T> -> Arc<T>. While some might require multithreading others might want to go with the legacy implementation and I all the smart pointers are made to be thread-safe this could hamper the performance of the legacy implementation. This is avoided by using #[cfg(... gates on variables and arguments.

Reason for TargetDirPool

Adding multi-threading to the entire implementation isn't difficult the main problem is to tackle the locking mechanism that cargo has in place. In order to do so multiple target directories were created and they were assigned for execution, as well as reused to take advantage of caching

Reason for rayon

While using the traditional multi-threading model was always into consideration, rayon had some added benefits. Being lightweight and guaranteeing data-race freedom, with the added benefit of having great abstraction.

Ignored tests: 2

Here I have ignored 2 test cases as the order of the output was not what was expected in the assertion. I wasn't able to implement tests to replace them. Please, feel free to modify them as necessary

Thanks for the PR!

I would prefer to make this an option that can be opt-in with an environment variable or CLI option, rather than a feature flag. If the user needs to reinstall cargo-hack to try parallelized cargo-hack, that would be a pain.
What does the output from parallelized cargo-hack look like? I'm concerned that if warnings/errors from different threads are alternately displayed, the messages may not be readable to the user.

I agree with what you are presenting, I actually started working on the second issue that you suggested, a little while before raising this PR, but sadly I wasn't able to include those changes in this PR at the moment. However, I am working on it and will add those changes to this branch. Speaking about the first issue that you mentioned, I was also trying to achieve the same, but to achieve the current performance on the binary, some of the functionality used cannot support multi-threading, I do acknowledge that this tradeoff had to be made but, wasn't able to test how much a performance bottleneck is caused by using Atomically safe wrappers.
I'll try to benchmark it in the meantime, but theoretically, that will cause some performance bottleneck if the application is not running on the multithreaded mode as that is the intention of that change. Still, I'll try to find other ways to achieve something similar or to find a workaround for the feature-gated solution.
Thanks for the feedback

performance bottleneck

I haven't measured this, but

As for Rc -> Arc, the number of clones is not very large and I think it should not cause problems.
As for the TargetDirPool, that's not a problem, since we don't need to access it if parallelization is not enabled.
Mutex for Progress may cause a performance bottleneck because the lock is held even during outputting commands.
However, the only field that changes after parallelization in Progress is count, so instead of using Mutex entire Progress, using Arc<AtomicUsize> on count and using fetch_add(1, Relaxed) to increment counter should probably be enough to lower its cost.

Hello! I was wondering about this kind of functionality and came across this pr. I'm curious about it's status? I'm sure it would be super useful for projects with larger sets of features(where cargo-hack is needed the most!).

Hey @Pat-Lafon, I wasn't able to pick up on the comments left by @taiki-e, but I am planning to pick it up as soon as possible. I was able to come up with a solution to unify the logs that the application will emit. But, haven't implemented it in this branch just yet. Will try to pick it up in the very near future.

Closing per https://github.com/taiki-e/cargo-hack/issues/128#issuecomment-2517805940.
Thanks anyway for the PR!


Toggle Fullscreen (Feature Request)

I can see that there is a checkbox for starting the executable in full screen, but there does not seem to be a way to toggle between windowed and full screen.
F-11 and Alt-Enter do not work.

You'd have to do that in nodejs. There's nothing I can do from my side, but look here for more info: https://github.com/nwjs/nw.js/wiki/Window#windowtogglefullscreen


Update ovs-cni image path to use NPWG registry

Replace quay.io/kubevirt/ovs-cni-plugin
with ghcr.io/k8snetworkplumbingwg/ovs-cni-plugin

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5175

Relevant Lines:
13050

💛  - Coveralls


GPS status updates and logging on screen off

Questions
Hi, thanks for this amazing plugin! I have 2 questions:

Is there a way to get GPS status updates? Like GPS turned on and off, getting and losing fix?
is there a way to continue logging also with the device screen off? On newer Android devices it quite limited and requires some tweaking. I am testing the logging of a line on the map and everytime I turn the screen on, the GPS stops and when i turn it on, the current position is updated at once, connecting the positions with a straight line.

Thanks for any help!

I apologize, I just noticed that point 2 is handled in issue #53 .
Will add my appreciation there :-)

@moovida to my knowledge this is not supported by the default mobile platforms. The only updates we can (and do) provide is if the location services are being turned on or off.
Information regarding GPS status are not provided by the SDKs supplied by Apple and Google so we have no (official) way to get this information unfortunately.


SMS VERIFICATION

anyone know how to enable this?

@plutotechnology please follow the issue template when following issues.  If you have a general Firebase question and not an issue with this repository I suggest trying StackOverflow.


default image

how can i set defaul image ? thanks

What do you mean by default image?
You can set a default image as you would typically do in a <img> tag by setting the src attribute, which will be replaced later by the lazy loaded image URL.
<img src="https://example.com/default.jpg" data-src="https://example.com/cute_kitten.jpg">


feat: connection upgrades

The header fixes in #22 (ie restoring the upgrades) make things like WebSocket connections successfully pass through the proxy. However, the responses of the client were still not correct which this PR adds.
Closes #11

I like web sockets (commenting to tack this pr)


#67 Adjust an expectation in NioDatagramConnectorExIT to avoid a sporadi...

...c test failure due to timing. Also made some minor cosmetic fixes to Sslv3Test.

Coverage increased (+0.01%) to 46.14% when pulling bf8740f5e3541483a4936efd51ce84c8995409bc on cmebarrow:issue_67 into 2813f3e7b461e1f425281e2d4797ddfa34a404db on kaazing:develop.

The Travis build passed on Oracle jdk but failed on open jdk due to what looks like a system level error:
'''''
[ERROR] Failed to execute goal org.kaazing:k3po-maven-plugin:2.0.0-alpha-8:start (default) on project gateway: Execution default of goal org.kaazing:k3po-maven-plugin:2.0.0-alpha-8:start failed: Plugin org.kaazing:k3po-maven-plugin:2.0.0-alpha-8 or one of its dependencies could not be resolved: Could not transfer artifact junit:junit:jar:4.12 from/to central (https://repo.maven.apache.org/maven2): Failed to transfer file: https://repo.maven.apache.org/maven2/junit/junit/4.12/junit-4.12.jar. Return code is: 502 , ReasonPhrase:Bad Gateway. -> [Help 1]
'''''

I've restarted the failed job on travis CI


OBS Plugin Issues

This may be a feature request as well as a bug, I'm unsure if it's all one issue or not

Whenever I manually connect the MD plugin to OBS, it'll ask for my password. I enter it, it tells me I'm wrong, then asks again and it works fine the second time (this also happens if I have no password enabled). It then continues displaying on the sidebar that MD is disconnected even though the button functions all work as if it is. This is odd, but didn't see anyone mention it yet.

It's requiring a manual connection every time I close MD or OBS. It'd be awesome if there was some sort of auto-connect like I've noticed the Voicemeter plugin has. I'm not sure if this lack of function is related to the bug above, but either way, figured I should at least mention it since it's related. As of now it's usable, but definitely more clunky than I feel it's intended to be.

Other than that, I'm loving the new version so far and wish the contributing devs luck going forward <3

It is better to post this issue on the plugin repo.


Use HMAC SHA-256 with configurable amount of rounds to generate seed

With this change coinb.in uses the same mechanism to generate seed from a passphrase like https://bip32.org: 50000 rounds of HMAC SHA-256 encryption.
The amount of rounds is configurable and the value 0 results in the same mechanism as before for compatibility. The generated seed is also shown in WIF format, which is also with bitcoin-cli compatible. It is possible now to generate the same wallet using bitcoin-cli sethdseed true <seed_wif> command in bitcoin core.
To be really fully compatible with bitcoin-cli, the fix in #228 pull request is also required.

Nice work.


Add ability to use package resources as data source

Currently pykwalify library doesn't provide an easy way to override where resources are located and all named resources must be reachable by open function. This disallows a user to open them with custom names or using package resources including API provided by Python 3.7 and backported to earlier versions.
To provide this posibility I suggest:

add ability to supply dict containing some required data such as custom types, external resources, etc
replace all open() calls by an overridable function as a parameter or by a custom class method

What API resources provided in python 3.7 are you talking about? I do not know what you mean by that.
How would adding the ability to point a specific open() help? Most times the normal open method is good enough, the issue is more with the arguments to the open function like encoding for example. If i still have to handle the arguments into the method from inside pykwalify, the overriden open function would provide little value. If you can elaborate in more detail on this, please do.
One bad thing about the additional dict into the class, is that it will be very hard to map it to cli arguments or similar. You either have to configure pykwalify through some settings file for that to even be a viable solution for most users. Some of this functionality is already in place with custom data into the class for some features, and some stuff is already present for config file.

The CLI interface could be the same, I'm talking only about programmable interface as in most cases developers would use your library as a library, not as a tool. One of major usage of it as I see is to check incoming data from a network against defined API schemas.
Python 3.7 added brand new rewrited importlib.resources package allowing a developer to access any resource inside packages. There's many advantages over existing implementation. All information you can read here

I will not implement this feature. I will leave it up to the user of this lib to sort out the fetching and loading of data into the Core class. The Core class now can take so many different types of objects and data when building itself that it should be easy enough to make your own usage of resources when using this in lib mode.


cover operations on non existent schemas and tables

Closes #58

Coverage increased (+0.3%) to 91.768% when pulling 2e2290af74d051cfcd8ff1f871bdcfe82f616327 on Improve-Error-handling-in-Frontend-of-Storage into 3e2982c4f8925f7980406b4706aeeef7555020aa on master.


https://help.github.com/articles/signing-commits-with-gpg/

[ ] Have you followed the [contributing guidelines](https://github.com/github/o

pensource.guide/blob/master/CONTRIBUTING.md)?
[ ] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

🙂

#1261


Cant extract Mario Kart 8 Update 2.0.0 nsp

I am on windows using NSTool v1.6.3,
This is the command I am using:
nstool.exe -k prod.keys --fstree "MK8 UPDATE 2.0.0.nsp"

This is thew error I get
[nn::hac::PartitionFsMetaGenerator ERROR] sPfsFile entry had unexpected data offset.

That error occurs when the NSP underlaying PFS0 structure wasn't correct.
What tool was that NSP generated with?

This should be fixed in v1.6.4.
Please download a copy from the release page.
https://github.com/jakcron/nstool/releases/tag/v1.6.4

Thanks!


I made a similar extension using Do Not Merge WIP as a starting point

Hello there 🙂
This is not really an issue or a question, I just wanted to let you know that I recently made an extension called No Merge Today. I used Do Not Merge WIP as a starting point since I've never built a Chrome extension before. So, thank you for that!
I also was able to solve a couple of scenarios that Do Not Merge WIP does not handle. Most notably the case where you reach the pull request page by client-side navigation, instead of a full-page reload (Do Not Merge WIP won't trigger in this case, No Merge Today will). A simple way of testing this scenario is to, having Do Not Merge WIP enabled, navigate to https://github.com/rafaeleyng/no-merge-today/pulls and then click on the PR 2 there. It shouldn't trigger the content script that blocks the button. But after a reload while being on the PR page, it triggers.
I also used mutation observer to react more quickly to DOM changes (instead of relying on a setInterval), and message passing to react immediately to configuration changes in the action popup.
I hope this can be useful 👋

Thank you for your sharing! I'm glad to hear that :smile_cat:


activeItem observer is not working

Hi,
"activeItem" will be set if a row is selected?
If yes, I am using below snippet but activeItem observer is not working. Could you please check?
`<px-data-grid
selection-mode="single"
active-item="{{activeItem}}"
table-data="{{repos}}"
hide-action-menu = "true"
columns='[[coloums]]'
        ></px-data-grid>`

properties:
activeItem:{
observer: '_activeItemChanged'
},
        _activeItemChanged(item){
            console.log("item changed");
        }

or window.addEventListener('selected-items-changed', (e) => this.handleKick(e));
window.addEventListener('active-item-changed', (e) => this.handleKick(e)); are also not working.

A few things to note:

Selected and active items are different. I'l handle selected in this answer, since it seems like that is the thing you're looking for
You need to listen to sub-property changes on the selectedItems property to be notified of changes when items are added. See the Polymer docs
You can't add event listeners to the window for *-changed events. Those events don't bubble. You need to add event listeners directly to the px-data-grid node.

Here's demo code showing how to listen to selectedItems changing: https://glitch.com/edit/#!/glimmer-eyeliner?path=public/src/data-grid-demo.html:59:76
Here's that code running, open your console and select a few items to see the console.log result: https://glimmer-eyeliner.glitch.me/

Thank you David but in our case selection mode is none so the above approach wont work. When I use vaadin grid active items it works as expected. Could you please suggest what is the best approach to handle row click event if the selection mode is none?
Reason why we are using  selection mode is none is to match with wireframes.

Hey @davidrleonard we are running into this problem as well, we are trying to capture the last clicked item, but activeItem is always null, active-item-changed is never being fired, and it appears that vaadin-grid's activeItem functionality isn't working, since on selection-mode='none', clicking a row should still set it to active, but nothing of the sort is happening.


测试文章 - 去不了日本的刑警安大君 | HunterOntario Blog

https://newpoliceman.github.io/2018/11/20/测试文章/
Every failure is leading towards success.

沙发


exit_store_metadata_in_osv3: pass oauth url to get token if use_auth

Sometimes a weird error occured on slow envs and long builds:
2016-03-14 12:34:12,385 - atomic_reactor.plugin - INFO - running plugin instance with args: '{u'url': u'https://<IP_ADDRESS>:8443/', u'verify_ssl': False, u'use_auth': True}'
2016-03-14 12:34:12,386 - atomic_reactor.plugins.store_metadata_in_osv3 - INFO - build id = atomic-reactor-dockerfile-test-master-11
2016-03-14 12:34:13,493 - osbs.core - ERROR - [401] 'Location' header is missing in response, cannot retrieve token
2016-03-14 12:34:13,726 - atomic_reactor.plugin - DEBUG - Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/atomic_reactor-1.6.3-py2.7.egg/atomic_reactor/plugin.py", line 203, in run
    plugin_response = plugin_instance.run()
  File "/usr/lib/python2.7/site-packages/atomic_reactor-1.6.3-py2.7.egg/atomic_reactor/plugins/exit_store_metadata_in_osv3.py", line 166, in run
    osbs.set_annotations_on_build(build_id, labels, **kwargs)
  File "/usr/lib/python2.7/site-packages/osbs/api.py", line 39, in catch_exceptions
    raise OsbsException(cause=ex, traceback=sys.exc_info()[2])
OsbsException: ValueError(u'Token was not retrieved successfully.',)

Original traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/osbs/api.py", line 28, in catch_exceptions
    return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/osbs/api.py", line 315, in set_annotations_on_build
    return self.os.set_annotations_on_build(build_id, annotations, namespace=namespace)
  File "/usr/lib/python2.7/site-packages/osbs/core.py", line 328, in set_annotations_on_build
    build_json = self._get(url).json()
  File "/usr/lib/python2.7/site-packages/osbs/core.py", line 85, in _get
    headers, kwargs = self._request_args(with_auth, **kwargs)
  File "/usr/lib/python2.7/site-packages/osbs/core.py", line 77, in _request_args
    raise ValueError("Token was not retrieved successfully.")
ValueError(u'Token was not retrieved successfully.',)

2016-03-14 12:34:13,733 - atomic_reactor.plugin - WARNING - plugin 'store_metadata_in_osv3' raised an exception: OsbsException caused by ValueError(u'Token was not retrieved successfully.',)

This PR will make sure that store_metadata_in_osv3 plugin gets an auth token if use_auth is True

Oops, seems to be a misconfigured server, sorry


Upgrade from logback to log4j2 for logging backend

History:
2001: log4j 1.0 released.
2002: java.util.logging released (in JDK 1.4).
2006: slf4j 1.0 released. It is a frontend only.
2011: logback 1.0 released. It is a backend only.
2014: log4j2 2.0 released.
We should migrate to log4j2 as it is the newest hotness.

Switching to log4j2 will allow us to get timestamps in nanosecond precision.

This didn't age well!


TTS bug after installing new voices for Windows

Hi, I tested the software and everything seemed to work fine.
After a while I decided to install new voices for Windows. After a little research I came across this guide, and did as instructed there.
The new voices work fine from the Windows TTS configuration screen, but when trying to test it from EDDI, the whole process freezes. Even the original default voice (Anna) doesn't work.
I'm running Windows 7 64-bit. The Speech Platform selected is 64-bit, and the voices don't have a 64/32-bit selection.
Thank you very much for this awesome (and free!) software.

Hi,
I did exactly the same thing, the same guide and the same voices and I have (surprisingly :)) the same problem.
In fact, when I launch EDDI (even without having one of the new voices selected for EDDI), the program says nothing and is not even in the volume mixer. Also, EDDI proceeds to use 100% of my CPU, which is not normal (I have a fairly high-end CPU).
I also have Windows 7 x64.
EDDI was great while it worked (and I'm blaming the TTS problems on Microsoft), so thanks for the program anyway :)

Uninstall the voices and delete their registry files (be sure to keep Anna).

Some of the Microsoft voices appear to have bugs which results in SSML speech putting them in to a loop.  There is an option on the 'Text-to-speech' tab that allows you to turn of SSML speech, or you could use purchase a voice form a commercial company (e.g. Ivona) that is better-behaved.


Rust and WebAssembly Working Group Meeting #49

Our next meeting will be Thursday, August 1st at 17:00 UTC.
Add agenda items here: https://paper.dropbox.com/doc/RustWebAssembly-WG-dcXi5F7Bqlvg10zd7dKve
As usual, we'll be holding open office hours, so if you have any questions about Rust and WebAssembly, feel free to add a bullet point to the agenda!
We use Zoom for video meetings, so make sure you've downloaded the client! (It's free, but you have to sign up.) Here is our meeting room: https://zoom.us/j/715879536
Anyone interested in Rust and WebAssembly is invited to join! Yes, that includes you!

Reminder: this is starting in 40 minutes!

Thanks!


[BSO] Thanksgiving 2021 Collection log counts for overall progress when it shouldnt

🐛 Bug Report
As with every other CL in the Discontinued tab, they do not count for overall log completion due to being well, discontinued items. The Thanksgiving2021 log does count for overall log, unlike other ones such as Hween 2021. Can see in the image that titles of both logs are different.

Fixed


Retab & compactify the sbt-datatype definitions

The diff says +563/−975.
But if you drop the whitespace changes it's actually +137/−549, so I'd recommend reviewing that diff:
https://github.com/sbt/zinc/pull/197/files?w=1


Add public apis analyzer

See https://github.com/dotnet/Open-XML-SDK/pull/1640 for a verification that this is the right set of APIs for "shipped"


Conda updates

Looking at you, https://github.com/quantopian/zipline/issues/1161.

Coverage decreased (-0.06%) to 85.71% when pulling 0c71aaa6ad52f6d5ab07e201b7ee2a883088e933 on conda-updates into f5ff9d8514cd9616e904276b2152b78d395ad39b on master.


No zip files in SkylineTester.zip

commented out inclusion of zip files in SkylineTester.zip to decrease its size from 600MB to 100MB

Just the function parameter is fine. I just don't want to see the code
commented out, and leave it with an obvious path to re-implementing the
feature.
On Tue, Feb 14, 2023 at 12:26 PM Matt Chambers @.***>
wrote:

@.**** commented on this pull request.
In pwiz_tools/Skyline/SkylineTester/CreateZipInstallerWindow.cs
https://github.com/ProteoWizard/pwiz/pull/2499#discussion_r1106335273:

                 // Add test zip files.

               var zipFilesList = new List<string>();

               /*var zipFilesList = new List<string>();

OK. Do you want me to implement the UI, or just add the function param?
—
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/pull/2499#discussion_r1106335273,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYBWUDC7LO24R2NVZDTKG3WXPS7RANCNFSM6AAAAAAU36KCGE
.
You are receiving this because your review was requested.Message ID:
@.***>


Feature Request: improving description and examples for ngMocks.get

ngMocks.get description too vague
Currently ngMocks.get description could be understood to only concerns structural directives or services but it can also be used for components or common directives
declarations word is not enough precise.
Consequently we may be tempted to use ngMocks.findInstance which mention components, directives and so on but in some cases we could have false positive (because debugElement or css selector is missing or present in childs), and ngMocks.get is more accurate (we don't want to go through childs).
Proposed solution
I would urpose the following patch which add all of those precisions
Additional context
docs(get)__update_description_and_add_examples_to_get_component,_directive_or_service.patch.txt

Hi @Dji75,
for windows you need gitbash. I'll update docs about that.
Regarding you change - could you do it right on github? on the related docs page you can click "Edit this page" at the bottom of the page: https://ng-mocks.sudo.eu/api/ngMocks/get.

Hi @Dji75, this issue I'm going to close with the updated CONTRIBUTING.md, please open a PR with the updated documentation via Edit this page, or ping me here if you want to discuss whatever first.

v14.3.1 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.

You're right git bash works better than cmder for unix-like scripts ;)
Thanks for your feedbacks @satanTime.
Here is the corresponding PR: https://github.com/help-me-mom/ng-mocks/pull/3899


Improvement in Footer

Please assign me this issue. I would like to contribute in it under hacktoberfest.

Hello Sumit, Can you please assign me this issue. I want to contribute in it under hacktoberfest.

Hi Rishika, Can you please assign me this issue. I would like to contribute in it under hacktoberfest.

Please work on another issue. I am working on this issue


Pickupable Vehicles

Would be a nice feature, when the player can pickup his vehicle and replace in another place.
Now i have only seen the option to destroy the vehicle.

Was intentional, but I'll think to add it as an option configurable by the server owner

Of course, would be a solution.

It is a little bit strange, when you can pickup your Heli, Nautilus and so on, but not the Automobiles.


[FRG] Formatter functions do not support return

This may be intentional, but it doesn't seem to fit the pattern of other places in the system.
Currently, it seems like formatter functions in bands require that you use the callback() to return the value.
Works
structure.formatterFunctions['percent'] = "callback(`${value}%`);";

Does Not Work
structure.formatterFunctions['percent'] = "return `${value}%`;";

This is intentional, the report engine has a lot of "extra" code now because of sync vs async and trying to do the right thing.    In some cases this has creates some major complexity and we don't want any extra complexity in the massive number of loops band calls handle, if we can avoid it...
I would like to over time simplify the engine to be always fully async and eliminate all the sync paths, which should make things be a lot more standard.     Which basically means anything that calls into user code must be callback based to allow the user to do their own async path before running the callback with the result.   In fact if I get the opportunity to rewrite it; I'd be using things like promises, async/await, and generators to simplify the code base greatly.  :-)

Unless there is a really compelling reason to add sync support here, I would rather not.  :grinning:

Love it! I actually like the consistency. I can work with callbacks until
we get promises. Thanks!
On Mon, Mar 9, 2020, 5:20 PM Nathanael Anderson<EMAIL_ADDRESS>wrote:

This is intentional, the report engine has a lot of "extra" code now
because of sync vs async and trying to do the right thing. In some cases
this has creates some major complexity and we don't want any extra
complexity in the massive number of loops band calls handle, if we can
avoid it...
I would like to over time simplify the engine to be always fully async and
eliminate all the sync paths, which should make things be a lot more
standard. Which basically means anything that calls into user code must be
callback based to allow the user to do their own async path before running
the callback with the result. In fact if I get the opportunity to rewrite
it; I'd be using things like promises, async/await, and generators to
simplify the code base greatly. :-)
Unless there is a really compelling reason to add sync support here, I
would rather not. 😀
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NathanaelA/fluentreports/issues/163?email_source=notifications&email_token=AABPKX6QE2AJLQRCJ46IFETRGVTR7A5CNFSM4LESC2V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOJI2QQ#issuecomment-596806978,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABPKX5E54C7SJZGXWK53Z3RGVTR7ANCNFSM4LESC2VQ
.


Function Specification

Develop a specification for functions in the MDF.

Function element of MDF specified in: https://github.com/ModECI/MDF/tree/main/docs#function
and standard functions listed here: https://github.com/ModECI/MDF/blob/main/docs/MDF_function_specifications.md