Can't find Flask server

I need to retrieve the Flask object to expose my application with Gunicorn. I tried with the get_flask_app method, but I got the following error:
[2023-06-12 17:21:18 +0200] [451] [INFO] Starting gunicorn 20.1.0
[2023-06-12 17:21:18 +0200] [451] [INFO] Listening at: http://<IP_ADDRESS>:8000 (451)
[2023-06-12 17:21:18 +0200] [451] [INFO] Using worker: sync
[2023-06-12 17:21:18 +0200] [452] [INFO] Booting worker with pid: 452
[2023-06-12 17:21:19 +0200] [452] [ERROR] Exception in worker process
Traceback (most recent call last):
  File "/home/taipy/venv/lib/python3.9/site-packages/gunicorn/arbiter.py", line 589, in spawn_worker
    worker.init_process()
  File "/home/taipy/venv/lib/python3.9/site-packages/gunicorn/workers/base.py", line 134, in init_process
    self.load_wsgi()
  File "/home/taipy/venv/lib/python3.9/site-packages/gunicorn/workers/base.py", line 146, in load_wsgi
    self.wsgi = self.app.wsgi()
  File "/home/taipy/venv/lib/python3.9/site-packages/gunicorn/app/base.py", line 67, in wsgi
    self.callable = self.load()
  File "/home/taipy/venv/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 58, in load
    return self.load_wsgiapp()
  File "/home/taipy/venv/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 48, in load_wsgiapp
    return util.import_app(self.app_uri)
  File "/home/taipy/venv/lib/python3.9/site-packages/gunicorn/util.py", line 359, in import_app
    mod = importlib.import_module(module)
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 790, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/home/taipy/app.py", line 3, in <module>
    app = tp.Gui(page="# Getting started with *Taipy*").get_flask_app()
  File "/home/taipy/venv/lib/python3.9/site-packages/taipy/gui/gui.py", line 1672, in get_flask_app
    return self._server.get_flask()

The application code:
import taipy as tp

app = tp.Gui(page="# Getting started with *Taipy*").get_flask_app()

My Taipy dependencies:
taipy==2.2.0
taipy-config==2.2.0
taipy-core==2.2.3
taipy-gui==2.2.1
taipy-rest==2.2.1

app = gui.run(run_server=False) returns the Flask instance


Add Chinese document

添加中文文档

Thanks for your contribution. Unfortunately, that's not something we can merge into the official repository as I have no way to check the accuracy of the translation.


Move ApiUserTokenService under the API namespace

Purpose or Intent
The Api in the name was a giveaway that this service belongs under the
main API namespace, and will simplify the constant lookup in later
refactorings.
@miq-bot add-label api, refactoring
@miq-bot assign @abellotti

LGTM!! waiting for 🍏


How to add more than one library

I have the custome card installed I would like to add all my libraries is this possible?

You can use another card/panel in home assistant for a different library.


[Bug] Manually created legend functionality

Version
5.4.1
Link to Minimal Reproduction
No response
Steps to Reproduce
.
Current Behavior
I have created the legends Manually and wanted the functionality on it.
Like when we click on any legend, the slice of pie chart should pop out.
Expected Behavior
On clicking on Manually created legend, the slice of pie chart should be pop out on when the slice value and legend value matches.
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

If you hope to customize the legend, you need to call the dispatchAction and manually dispatch the legend-related actions.
See also this demo.

Hii @plainheart , But dispatchAction can work only with the legends created by default.
I want to pop out the slice of pie when customized legend is clicked

Hii @plainheart thank you for comment. But it looks lime I may be missing something in my code, as not able to achieved the desired result. So, if you can look into it, it would be more help.
Thanks in advance.

"...look into it" ?!  And where is the code ?


URL rewrite doesn't work for non-regex

ASP.NET Core 2.1 (2.1.302)
I want to rewrite /favicon.ico to /images/favico.ico.
So I followed the docs and did this in Startup.cs at the end of Configure() (after app.UseMvc(), I hope that's correct?):
app.UseRewriter(new RewriteOptions()
  .AddRewrite("favicon.ico", "images/favicon.ico", skipRemainingRules:true));

But that gave me a 404.
So I thought maybe I need to use a dummy regex:
app.UseRewriter(new RewriteOptions()
  .AddRewrite("^(favicon.ico)$", "images/favicon.ico", skipRemainingRules:true));

And that also gave me a 404.
This was confirmed by another person on SO, so it's either a bug, or the documentation is wrong (in which case please correct me).

Thanks for contacting us, @lonix1.
Please provide us with a minimalistic repro project so we can investigate the issue.

cc @jkotalik

Seems like a bug, will look into it in the 2.2 timeframe.

@jkotalik, should this be moved to a different repo?

Home with the tag BasicMiddleware.

Oops: just BasicMiddleware.

This can be reproduced by taking the example at https://docs.microsoft.com/en-us/aspnet/core/fundamentals/url-rewriting?view=aspnetcore-2.1&tabs=aspnetcore2x and commenting out the app.Run command at the end of the Configure function. The url rewrite example will then 404 no matter the replacement url. This is using core 2.1 and Microsoft.AspNetCore.Rewrite 2.1.1.

Once this bug is resolved, please also give us some guidance (or better yet, update the docs) about the implications of putting this before/after/between app.UseStaticFiles() and app.UseMvc(), or whether it should be at the beginning/end of Configure() i.e. the beginning/end of the pipeline.

This issue was moved to aspnet/BasicMiddleware#355


Feature/<IP_ADDRESS>/auth-azure

What type of PR is this?

[ ] Refactor
[ ] Feature
[x] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description
This PR is a part of authentication with Azure. It adds the email scope to the OAuth Azure requests. In order to add the authentication, I followed the documentation here: https://supabase.com/docs/guides/auth/social-login/auth-azure .
There are a few future directions we should consider:

how can we automantically set up Azure and Supabase? It would be nice to use some sort of Cloud Formation tool so that all of the settings I configured manually on Supabase and Azure are described in the code.
It sounds like we will eventually remove the Google authentication and do everything through Azure. When that happens we'll need to figure out a way to allow DAS volunteers to access the application.

Related Tickets & Documents

Closes # <IP_ADDRESS>

QA Instructions, Screenshots, Recordings
The documentation gives an overview of the process I used to set up my end-to-end test for this change.
After adding the required information to Seattle Humane Supabase and to my personal Azure account, I was able to press Sign in with Microsoft

And then the authentication process returned the correct token from Supabase, showing the authentication was successful.

Added/updated tests?

[x] Yes
[ ] No, and this is why: please replace this line with details on why tests
have not been included
[x] I need help with writing tests

I added a unit test to show that the Azure auth function can be called, but all of the things happening behind the scenes with Supabase and Azure are not being tested automatically. I think this goes into what I had talked about before with automating the Supabase and Azure configurations. Once they are automated, we can have integration tests in a non-prod environment that run through the rest of the tests.

You mentioned that there were steps you had to make in Supabase and Azure.  How different are they from the documentation provided by Supabase?

You mentioned that there were steps you had to make in Supabase and Azure. How different are they from the documentation provided by Supabase?

It seems like following the documentation as written works. I may have made a mistake and set the redirect to be of the application type, rather than the web type. I never got full confirmation that this was the problem I was running into, but the app seems to be working now.

You mentioned that there were steps you had to make in Supabase and Azure. How different are they from the documentation provided by Supabase?

It seems like following the documentation as written works. I may have made a mistake and set the redirect to be of the application type, rather than the web type. I never got full confirmation that this was the problem I was running into, but the app seems to be working now.

Just to confirm, the redirect setting in the Azure application registration?

You mentioned that there were steps you had to make in Supabase and Azure. How different are they from the documentation provided by Supabase?

It seems like following the documentation as written works. I may have made a mistake and set the redirect to be of the application type, rather than the web type. I never got full confirmation that this was the problem I was running into, but the app seems to be working now.

Just to confirm, the redirect setting in the Azure application registration?

Yes in Azure

Thanks for applying the suggestions to reconsider the usage of class and arrow functions!


Further refactor digest and ID handling

This builds upon #402 and tries to improve the following:

Re-use Digests and remove duplication
Collect digests during storage and re-use when inserting document into the DB

@jcrossley3 So I continue here to improve things.

Right now the CI is expected to fail as refactoring the tests will be more effort. I'll do that if we can agree that this is the right approach.

Pushing another change which implements the result struct suggested in #402


Find out the gzipped sizes cause I'm lazy to do it

The sizes of the CSS files using gzip should be even smaller

Done. Used logerfo.gzip-status VS Code extension.


out-of-bounds w.r.t. dense side with broadcasted shape issue during promise12 demo training

When I run training with default settings of promise12 demo. The process fails with "out-of-bounds w.r.t. dense side with broadcasted shape" after couple of hundreds iterations.
This problem disappears if I switch off data augmentation :
#rotation_angle = (-10.0, 10.0)
#scaling_percentage = (-10.0, 10.0)
#random_flipping_axes= 1
Python libraries are as described in requirements and tensorflow in version 1.3. This problem is present in default branch of Niftynet as of Oct 26, 2017 .  It was also seen 1 month ago.
This is full log of the issue:
INFO:niftynet: iter 234, dice_loss=0.5082721710205078 (1.068s)
2017-10-26 10:57:30.556125: W tensorflow/core/framework/op_kernel.cc:1192] Invalid argument: Provided indices are out-of-bounds w.r.t. dense side with broadcasted shape
[[Node: worker_0/loss_function/mul = SparseDenseCwiseMul[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](worker_0/loss_function/stack, worker_0/loss_function/ones_like, worker_0/loss_function/ToInt64_2, worker_0/loss_function/Softmax)]]
2017-10-26 10:57:30.556195: W tensorflow/core/framework/op_kernel.cc:1192] Invalid argument: Provided indices are out-of-bounds w.r.t. dense side with broadcasted shape
[[Node: worker_0/loss_function/mul = SparseDenseCwiseMul[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](worker_0/loss_function/stack, worker_0/loss_function/ones_like, worker_0/loss_function/ToInt64_2, worker_0/loss_function/Softmax)]]
2017-10-26 10:57:30.556216: W tensorflow/core/framework/op_kernel.cc:1192] Invalid argument: Provided indices are out-of-bounds w.r.t. dense side with broadcasted shape
[[Node: worker_0/loss_function/mul = SparseDenseCwiseMul[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](worker_0/loss_function/stack, worker_0/loss_function/ones_like, worker_0/loss_function/ToInt64_2, worker_0/loss_function/Softmax)]]
INFO:niftynet: Cleaning up...
INFO:niftynet: iter 235 saved: /home/ladislav/temp/promise12_model/models/model.ckpt
INFO:niftynet: stopping sampling threads
INFO:niftynet: SegmentationApplication stopped (time in second 1073.88).
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1327, in _do_call
return fn(*args)
File "/usr/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1306, in _run_fn
status, run_metadata)
File "/usr/lib64/python3.5/contextlib.py", line 66, in exit
next(self.gen)
File "/usr/lib/python3.5/site-packages/tensorflow/python/framework/errors_impl.py", line 466, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.InvalidArgumentError: Provided indices are out-of-bounds w.r.t. dense side with broadcasted shape
[[Node: worker_0/loss_function/mul = SparseDenseCwiseMul[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](worker_0/loss_function/stack, worker_0/loss_function/ones_like, worker_0/loss_function/ToInt64_2, worker_0/loss_function/Softmax)]]
[[Node: worker_0/gradients/AddN/_1901 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/gpu:0", send_device="/job:localhost/replica:0/task:0/cpu:0", send_device_incarnation=1, tensor_name="edge_6703_worker_0/gradients/AddN", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/gpu:0"]]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ladislav/NiftyNet/net_segment.py", line 7, in
sys.exit(main())
File "/home/ladislav/NiftyNet/niftynet/init.py", line 83, in main
app_driver.run_application()
File "/home/ladislav/NiftyNet/niftynet/engine/application_driver.py", line 183, in run_application
self._training_loop(session, loop_status)
File "/home/ladislav/NiftyNet/niftynet/engine/application_driver.py", line 352, in _training_loop
graph_output = sess.run(vars_to_run)
File "/usr/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 895, in run
run_metadata_ptr)
File "/usr/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1124, in _run
feed_dict_tensor, options, run_metadata)
File "/usr/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1321, in _do_run
options, run_metadata)
File "/usr/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1340, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Provided indices are out-of-bounds w.r.t. dense side with broadcasted shape
[[Node: worker_0/loss_function/mul = SparseDenseCwiseMul[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](worker_0/loss_function/stack, worker_0/loss_function/ones_like, worker_0/loss_function/ToInt64_2, worker_0/loss_function/Softmax)]]
[[Node: worker_0/gradients/AddN/_1901 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/gpu:0", send_device="/job:localhost/replica:0/task:0/cpu:0", send_device_incarnation=1, tensor_name="edge_6703_worker_0/gradients/AddN", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/gpu:0"]]
Caused by op 'worker_0/loss_function/mul', defined at:
File "/home/ladislav/NiftyNet/net_segment.py", line 7, in
sys.exit(main())
File "/home/ladislav/NiftyNet/niftynet/init.py", line 83, in main
app_driver.run_application()
File "/home/ladislav/NiftyNet/niftynet/engine/application_driver.py", line 169, in run_application
self.graph = self._create_graph(self.graph)
File "/home/ladislav/NiftyNet/niftynet/engine/application_driver.py", line 236, in _create_graph
self.gradients_collector)
File "/home/ladislav/NiftyNet/niftynet/application/segmentation_application.py", line 237, in connect_data_and_network
weight_map=data_dict.get('weight', None))
File "/home/ladislav/NiftyNet/niftynet/layer/base_layer.py", line 32, in call
return self._op(*args, **kwargs)
File "/usr/lib/python3.5/site-packages/tensorflow/python/ops/template.py", line 268, in call
result = self._call_func(args, kwargs, check_for_new_variables=False)
File "/usr/lib/python3.5/site-packages/tensorflow/python/ops/template.py", line 217, in _call_func
result = self._func(*args, **kwargs)
File "/home/ladislav/NiftyNet/niftynet/layer/loss_segmentation.py", line 61, in layer_op
pred, ground_truth, weight_map))
File "/home/ladislav/NiftyNet/niftynet/layer/loss_segmentation.py", line 343, in dice
dice_numerator = 2.0 * tf.sparse_reduce_sum(one_hot * prediction,
File "/usr/lib/python3.5/site-packages/tensorflow/python/ops/math_ops.py", line 876, in binary_op_wrapper_sparse
name=name), sp_x.dense_shape)
File "/usr/lib/python3.5/site-packages/tensorflow/python/ops/gen_sparse_ops.py", line 601, in sparse_dense_cwise_mul
dense=dense, name=name)
File "/usr/lib/python3.5/site-packages/tensorflow/python/framework/op_def_library.py", line 767, in apply_op
op_def=op_def)
File "/usr/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 2630, in create_op
original_op=self._default_original_op, op_def=op_def)
File "/usr/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 1204, in init
self._traceback = self._graph._extract_stack()  # pylint: disable=protected-access
InvalidArgumentError (see above for traceback): Provided indices are out-of-bounds w.r.t. dense side with broadcasted shape
[[Node: worker_0/loss_function/mul = SparseDenseCwiseMul[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](worker_0/loss_function/stack, worker_0/loss_function/ones_like, worker_0/loss_function/ToInt64_2, worker_0/loss_function/Softmax)]]
[[Node: worker_0/gradients/AddN/_1901 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/gpu:0", send_device="/job:localhost/replica:0/task:0/cpu:0", send_device_incarnation=1, tensor_name="edge_6703_worker_0/gradients/AddN", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/gpu:0"]]

Hi @ladislav-urban many thanks for the feedback! This could happen when the largest voxel value in the discrete segmentation maps is greater than num_classes in the config file (since the voxel values are used as sparse binary map indices). Could you check if that's the case?

Hi Wenqi Li,
thanks for your quick answer! I do use default promise12 dataset. I have checked segmentation files in directories: TrainingData_Part1 to TrainingData_Part3. These are files starting from Case00_segmentation.mhd till Case49_segmentation.mhd . They include only values  0 or 1. There is a settings num_classes = 2 in the config files.
Can the higher voxel numbers be created by data augmentation process?
Thanks a lot for your answer
Ladislav

Yes I think you're right, the interp_order parameter should be 0 for [label] section, which means using the nearest neighbour interpolation in the data augmentations.

Hi Wenqi Li,
thanks a lot for the advice! The training is now working without errors.

I have been running into the same issue.
InvalidArgumentError (see above for traceback): Provided indices are out-of-bounds w.r.t. dense side with broadcasted shape
[[{{node worker_0/loss_function/map/while/mul}} = SparseDenseCwiseMul[T=DT_FLOAT<EMAIL_ADDRESS>_device="/job:localhost/replica:0/task:0/device:CPU:0"](worker_0/loss_function/map/while/SparseReshape, worker_0/loss_function/map/while/ones_like, worker_0/loss_function/map/while/SparseReshape:1, worker_0/loss_function/map/while/Softmax)]]
As stated, this could happen when the largest voxel value in the discrete segmentation maps is greater than num_classes in the config file.
what do you mean largest voxel value in the discrete segmentation maps?
my spatial window is 32 and the num_classes in the config is 160.
Thank you very much !


Make assignment fields have string primary keys

Often times I need to pull the "heroku url" from the assignment field submissions for an assignment in order to do grading. Right now, I have to do an ILIKE on the assignment field's label attribute. This is just horrid.
 Clearly I would have to do this for 2019.

Also, I should create an RPC for getting this kind of information, so that I'm not repeating myself when writing administrative code.


How to keep the cause of an error

I have a background of Java developer and I'm quite new to JavaScript/TypeScript.
Is there a standard way to manage and keep the cause of an Error in JavaScript/TypeScript?
My purpose is to get a complete stacktrace when I wrap an Error into another ; a little bit as with Java Exception stacktrace:
Message of exception 1
...
Caused by: Message of exception 2
...
Caused by: Message of the root exception

JavaScript and TypeScript have mechanisms to manage and preserve the cause of an error when wrapping one error into another, similar to Java's exception chaining. This can be achieved by leveraging the cause property introduced in ECMAScript 2022.

try {
    // Root operation that throws an error
    throw new Error("Root exception");
} catch (rootError) {
    try {
        // Another operation that throws an error, caused by rootError
        throw new Error("Exception 2", { cause: rootError });
    } catch (secondError) {
        // Final wrapping error, caused by secondError
        throw new Error("Exception 1", { cause: secondError });
    }
}

JavaScript and TypeScript have mechanisms to manage and preserve the cause of an error when wrapping one error into another, similar to Java's exception chaining. This can be achieved by leveraging the cause property introduced in ECMAScript 2022.

try {
    // Root operation that throws an error
    throw new Error("Root exception");
} catch (rootError) {
    try {
        // Another operation that throws an error, caused by rootError
        throw new Error("Exception 2", { cause: rootError });
    } catch (secondError) {
        // Final wrapping error, caused by secondError
        throw new Error("Exception 1", { cause: secondError });
    }
}

JavaScript and TypeScript have mechanisms to manage and preserve the cause of an error when wrapping one error into another, similar to Java's exception chaining. This can be achieved by leveraging the cause property introduced in ECMAScript 2022.

try {
    // Root operation that throws an error
    throw new Error("Root exception");
} catch (rootError) {
    try {
        // Another operation that throws an error, caused by rootError
        throw new Error("Exception 2", { cause: rootError });
    } catch (secondError) {
        // Final wrapping error, caused by secondError
        throw new Error("Exception 1", { cause: secondError });
    }
}

Thank you


fix: release v1.0.1

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


SamplingImplementation

How long does it take to get a sample?

It is doing the sampling of data within seconds i.e in less than a minute.

Please squash the commits.

Please squash the commits.

Squashed the commits


feat!: Exams & Request fixes

Implemented exams
Minor changes to the Request wrapper
(See PR commits for more details)

Good to go.


npm run prettier:format - file path pattern does not match

prettier --config .prettierrc 'src/**/*.ts' --write

[error] No files matching the pattern were found: "'src/**/*.ts'".
Reason : single quote around path
OS : Windows

This is OS depended problem so i am closing this .


getMultiCapabilities are not respected

When using getMultiCapabilities in Protractor 1.5.0 with Bluebird, the promise is ignored - I expected Firefox to be fired but only Chrome is.
Removing the getMultiCapabilities field and uncommenting the multiCapabilities field makes it all work.
My Protractor config:
'use strict';

/* global angular: false, browser: false */

var Promise = require('bluebird');

exports.config = {
    // Capabilities to be passed to the webdriver instance.
//    multiCapabilities: [
//        {browserName: 'firefox'},
//    ],

    getMultiCapabilities: function () {
        return new Promise(function (resolve) {
            resolve([
                {browserName: 'firefox'},
            ]);
        });
    },

    // Spec patterns are relative to the current working directly when
    // protractor is called.
    specs: ['test/e2e/spec/**/*.js'],

    allScriptsTimeout: 60000,
    // Options to be passed to Jasmine-node.
    jasmineNodeOpts: {
        defaultTimeoutInterval: 60000,
    },

    // A base URL for your application under test. Calls to protractor.get()
    // with relative paths will be prepended with this.
    baseUrl: 'http://localhost:8500',

    // Selector for the element housing the angular app - this defaults to
    // body, but is necessary if ng-app is on a descendant of <body>
    rootElement: 'html',

    onPrepare: function onPrepare() {
        var helpers = require('./test/e2e/lib/helpers');

        // TODO download results from API before tests, put them in some constant and use it in tests.

        // Disable animations so e2e tests run more quickly
        browser.addMockModule('disableNgAnimate', function disableNgAnimate() {
            angular.module('disableNgAnimate', []).run(['$animate', function ($animate) {
                $animate.enabled(false);
            }]);
        });

        browser.driver.manage().window().setSize(1024, 768);

        browser.get('/');
        helpers.user.registerAccount();
    },

    params: {
        settings: require('./app/settings'),
    },
};

The same happens when using the native Promise in Node 0.11.14.

Wrapping the resolve invocation in a large timeout doesn't result in any delay. Protractor just behaves as if this field didn't exist at all.

Ahh, this is just not released yet... Sorry for the fuss.

Has this ever been resolved? I am getting a very similar issue in Protractor 4.0.9 where Chrome is started immediately without waiting for a firefoxprofile promise to get resolved


Update values.preview.template.yaml

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] the enable_keep_helm label has been added, if the helm release should be persisted after a successful build

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Closing this dummy PR as testing is completed


NotImplementedError: fork() on Windows

Ruby/lib/ruby/gems/2.3.0/gems/tty-pager-0.7.1/lib/tty/pager/system.rb:62:in `fork'

Briefly, it's not friendly to see the error. :thinking:

Thanks for giving this library a try!
Would mind providing more information on the type of console you're using on Windows?
The TTY::Pager should automatically switch between SystemPager and BasicPager. However, this seems to fail in this situation as probably a given paging utility exists on your system that passes the check but you're probably running vanilla powershell without forking capability? For the time being, you should be able to use TTY::Pager::BasicPager directly to paginate.
Do you have time to look into why switching to BasicPager fails on your system?

It turns out that TTY::Pager::SystemPager.available? returns true.
TL;DR : the command more is executable on Windows, which causes the TTY::Pager switch to SystemPager.
However, it's not safe to check environment by this way, because I usually use these unix-like tools from mingw or git-for-windows.
C:\Users\hyrious>more /?
Displays output one screen at a time.

MORE [/E [/C] [/P] [/S] [/Tn] [+n]] < [drive:][path]filename
command-name | MORE [/E [/C] [/P] [/S] [/Tn] [+n]]
MORE /E [/C] [/P] [/S] [/Tn] [+n] [files]

May be check the RUBY_PLATFORM will be a better way.

I looked into source code, the SystemPager will check executables of
[ENV['GIT_PAGER'], ENV['PAGER'],
 `git config --get-all core.pager`,
 'less', 'more', 'cat', 'pager']

which in my circumstance is
[nil, nil, "", 'less', 'more', 'cat', 'pager']

after .compact.map(&:strip).reject(&:empty?).uniq.map { |cmd| TTY::Which.exist? cmd }, there are
[true, true, true, false] # the ENV includes git-for-windows, as in Cmder
[false, true, false, false] # `more` is executable on windows' cmd

Thanks for looking into this. As suspected the available? is broken and this confirms it. Checking for platform is less than optimal as people may well be using cygwin which actually supports forking behaviour on Windows. I will see if I can fix it later today. Will you have time to test the behaviour from master? If you have any ideas beforehand please submit PR and I will happily review.

@hyrious I have used your suggestion to detect fork presence on Windows. I've also added friendly error message that prevents initializing SystemPager if it cannot be used. Would you mind testing master branch?

Thank you! It works fine now.


navigationButtons not displayed

Navigation buttons disappeared between releases 6.0.0 and latest. Here is how to reproduce :
Create a package.json with 6.0.0 release :
{
  "name": "testvis",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "vis-network": "^6.0.0"
  }
}

type : yarn install
create this index.html file and open it in the browser :
<!DOCTYPE html>

    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width,initial-scale=1.0">
    <title>Test</title>
    <link rel="stylesheet" type="text/css" href="node_modules/vis-network/dist/vis-network.min.css">

The navigation buttons are displayed.
Update to the latest release :
yarn add vis-network@latest

(latest is: 6.3.1)
Refresh page in the browser : navigation buttons have gone.

Hi @Tazeg,
the default/dist build is deprecated now. Can't you switch to the standalone build instead?
The problem is that the CSS is supposed to have the images inlined which works in peer and standalone builds. However nobody has configured this for the legacy build.
PS: node_modules/vis-network/standalone/umd/vis-network.min.js and you no longer need the CSS nor the images, just this single file.

Thanks for your quick answer.
I use vis-network in Electron app. So as you said, it works fine with the following line and without including any CSS :
const vis = require('../../node_modules/vis-network/standalone/umd/vis-network.min')

But it is not supposed to be the right way. I should require like this :
const vis = require('vis-network')

Try
const vis = require("vis-network/standalone/umd/vis-network");

or if you bundle and want tree shaking
import vis from "vis-network/standalone/esm/vis-network";

or if you really want to use the legacy build (please don't, we'll remove it eventually anyway) you can wait for #219 which will fix the issue.

If I understand, legacy is deprecated code ? if yes i don't need it. I want to use the latest and futur releases.
I'm sorry but what are umd, esm and three shaking ?
Should i always use const vis = require("vis-network/standalone/umd/vis-network"); for latest and futur releases ?

The legacy bundle contains up to date code. It's just bundled in fundamentally flawed way. The recommended way of importing Vis Network is either https://visjs.github.io/vis-network/examples/network/basic_usage/standalone.html or https://visjs.github.io/vis-network/examples/network/basic_usage/peer.html.
UMD combines several legacy module systems in single file. These can be simply required in node or loaded by script tag in browsers. ESM is the modern standard compliant module system that can be imported in modern module script tags (not so well supported yet though it can be used already if you don't care about older browsers) or used in conjunction with Rollup, Webpack and other bundlers. With bundlers you gain the advantage of tree shaking which throws away unused code. This doesn't work so well yet but we're working on this. For example if you never import the Gephi parser in your code it can be tree shaken that is not included in the bundle saving you precious kB and loading/parsing time.


plot test not working in current master

test_upsample_max (pandas.tests.test_functions.TestReductions) ... ok
test_upsample_mean (pandas.tests.test_functions.TestReductions) ... ok
test_upsample_min (pandas.tests.test_functions.TestReductions) ... ok
test_boxplot (pandas.tests.test_graphics.TestDataFramePlots) ... ERROR
test_hist (pandas.tests.test_graphics.TestDataFramePlots) ... ERROR
test_plot (pandas.tests.test_graphics.TestDataFramePlots) ... ERROR
test_plot_bar (pandas.tests.test_graphics.TestDataFramePlots) ... ERROR
test_plot_int_columns (pandas.tests.test_graphics.TestDataFramePlots) ... ERROR
test_hist (pandas.tests.test_graphics.TestSeriesPlots) ... ERROR
test_plot (pandas.tests.test_graphics.TestSeriesPlots) ... ERROR
test_agg_apply_corner (pandas.tests.test_groupby.TestGroupBy) ... ok
test_agg_must_agg (pandas.tests.test_groupby.TestGroupBy) ... ok
test_agg_python_multiindex (pandas.tests.test_groupby.TestGroupBy) ... ok#
see the build recipe log for the daily Ubuntu package:
https://launchpadlibrarian.net/90884761/buildlog_ubuntu-precise-i386.pandas_0.7.0-ubuntu0~1714~precise1_FAILEDTOBUILD.txt.gz

Looking at the nose output you get:
ImportError: No module named _tkinter, please install the python-tk package

This is not pandas but matplotlib, matplotlib tries to use a backend which is not installed.
You can try to use another one, or install tkinter, as suggested in the error message.

It should be possible to implement all of the plotting functions in pandas without importing matplotlib.pyplot which is the culprit here. I don't really have time to look at it right now though

Tracking at Launchpad:
missing matplotlib agg backend for builder
https://bugs.launchpad.net/launchpad/+bug/921243
BTW, if this gets sorted, there is then a daily Ubuntu package builder for pandas.
Users will then be able to get daily updated packages in the package manager.
I am trying the same for statsmodels...

https://bugs.launchpad.net/launchpad/+bug/921243 mentions that 'The builders install what package dependencies tell them to install: the issue you are having is user data, not a code bug.'
pandas does not list matplotlib as a dependency, nor any matplotlib backend in setup.py.
The pandas plotting tests check if matplotlib is installed, if not tests are skipped. However when matplotlib is installed, but not the Agg backend, pandas plotting tests will fail.

So would you suggest to use python-tk as recommended here:
https://bugs.launchpad.net/launchpad/+bug/921243/comments/5

I added python-tk now:
The process stops again:
pandas.tests.test_tseries.test_get_reverse_indexer ... ok
pandas.tests.test_tseries.test_pad_backfill_object_segfault ... ok
pandas.tests.test_tseries.test_arrmap ... ok

======================================================================
ERROR: test_boxplot (pandas.tests.test_graphics.TestDataFramePlots)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/buildd/pandas-0.7.0/debian/python-pandas/usr/lib/python2.7/dist-packages/pandas/tests/test_graphics.py", line 100, in test_boxplot
    _check_plot_works(df.boxplot)
  File "/build/buildd/pandas-0.7.0/debian/python-pandas/usr/lib/python2.7/dist-packages/pandas/tests/test_graphics.py", line 127, in _check_plot_works
    fig = plt.gcf()
  File "/usr/lib/pymodules/python2.7/matplotlib/pyplot.py", line 369, in gcf
    return figure()
  File "/usr/lib/pymodules/python2.7/matplotlib/pyplot.py", line 343, in figure
    **kwargs)
  File "/usr/lib/pymodules/python2.7/matplotlib/backends/backend_tkagg.py", line 80, in new_figure_manager
    window = Tk.Tk()
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1688, in __init__
    self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use)
TclError: no display name and no $DISPLAY environment variable

https://launchpadlibrarian.net/91316914/buildlog_ubuntu-precise-amd64.pandas_0.7.0-ubuntu0~1765~precise1_FAILEDTOBUILD.txt.gz

You probably try to access the display before display service (X11?) has been started.
Normally linux sets up DISPLAY environment variable when X11 runs.
If not, set it yourself.
Could you try to get a running linux environment before installing pandas.

@timmie did you get it running?

what a concidence.
I just created a new build recipie on LP:
https://code.launchpad.net/~timmie/+recipe/pythonxy-daily-current
I think we hit what also hapeṕend to scikits.statsmodels:
The scientific packages in Ubuntu Version <= 11.10 are too old. Or otherwise put, devs of the scipy addon packages like to work with latest version of everthing and are not very backward-compatible aware.
In result, tests do not run and docs do not build on LP. My workaround is to use a recipie which does not run tests and does not build docs for the time being. This way, users can benefit from daily builds and we could take a bit more time to find out what's wrong.
I hope that situation's get better with Ubuntu 12.04. But I cannot test it, as my computer is still on 11.10.
So, I did not spend time to improve native code but rather invented a workaround to have daily builds of the package code.
I assume that tests are run by the developers and docs are also available online.

I'd be interested what process in the Debian build process triggers the package builder to run unittests of pandas?
is it in the Debian build process or the setup.py logic?
And, could this be disabled?
Because I am afraid that automatic daily builds won't work with testing enabled by default.
I will explain why in the next comment.

dpkg-buildpackage -us -uc

output:
warning: no previously-included files matching '.DS_Store' found anywhere in distribution
writing manifest file 'pandas.egg-info/SOURCES.txt'
Copying pandas.egg-info to debian/python-pandas/usr/lib/python2.7/dist-packages/pandas-0.7.2.dev_.egg-info
running install_scripts
: # Run unittests here against installed pandas
export PYTHONPATH=`/bin/ls -d $PWD/debian/python-pandas/usr/lib/python2.6/*/`; \
	export MPLCONFIGDIR=/tmp/pandas/build HOME=/tmp/pandas/build; \
	cd build/; python2.6 /usr/bin/nosetests -s -v pandas;
test_convert_sql_column_bools (pandas.io.tests.test_parsers.TestParseSQL) ... ok
test_convert_sql_column_decimals (pandas.io.tests.test_parsers.TestParseSQL) ... ok

then ...
pandas.tests.test_tseries.test_get_reverse_indexer ... ok
pandas.tests.test_tseries.test_pad_backfill_object_segfault ... ok
pandas.tests.test_tseries.test_arrmap ... ok
pandas.tests.test_tseries.test_series_grouper ... ok

======================================================================
FAIL: test_with_tzinfo_ambiguous_times (pandas.tests.test_daterange.TestDateRange)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/pandas/debian/python-pandas/usr/lib/python2.6/dist-packages/pandas/tests/test_daterange.py", line 282, in test_with_tzinfo_ambiguous_times
    self.assert_(not dr.tz_validate())
AssertionError

----------------------------------------------------------------------
Ran 1471 tests in 47.685s


wavebox: 10.127.10-2 -> 10.128.5-2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for wavebox is: Wavebox messaging application
meta.homepage for wavebox is: https://wavebox.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.126.22-2 in filename of file in /nix/store/7zdawpa88hjhlxm09b9kc44sgmk8bxz4-wavebox-10.126.22-2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7zdawpa88hjhlxm09b9kc44sgmk8bxz4-wavebox-10.126.22-2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wavebox https://github.com/r-ryantm/nixpkgs/archive/3534b781b0e0e3feab2d80e80cfcbaa12d379565.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3534b781b0e0e3feab2d80e80cfcbaa12d379565#wavebox

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7zdawpa88hjhlxm09b9kc44sgmk8bxz4-wavebox-10.126.22-2
ls -la /nix/store/7zdawpa88hjhlxm09b9kc44sgmk8bxz4-wavebox-10.126.22-2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

wavebox

Maintainer pings
cc @rawkode for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for wavebox is: Wavebox Productivity Browser
meta.homepage for wavebox is: https://wavebox.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.127.16-2 in filename of file in /nix/store/wvxp6x99k3avfq6gdgpc1cv7m80ag3xr-wavebox-10.127.16-2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

wavebox

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wvxp6x99k3avfq6gdgpc1cv7m80ag3xr-wavebox-10.127.16-2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wavebox https://github.com/r-ryantm/nixpkgs/archive/ae705cb66dd0ab4b0540abb52a6c5a81eb507f67.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ae705cb66dd0ab4b0540abb52a6c5a81eb507f67#wavebox

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wvxp6x99k3avfq6gdgpc1cv7m80ag3xr-wavebox-10.127.16-2
ls -la /nix/store/wvxp6x99k3avfq6gdgpc1cv7m80ag3xr-wavebox-10.127.16-2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

wavebox

Maintainer pings
cc @flexiondotorg for testing.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for wavebox is: Wavebox Productivity Browser
meta.homepage for wavebox is: https://wavebox.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.128.3-2 in filename of file in /nix/store/366hlxw433pl6jmhsz74vxycyjjlga6n-wavebox-10.128.3-2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

wavebox

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/366hlxw433pl6jmhsz74vxycyjjlga6n-wavebox-10.128.3-2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wavebox https://github.com/r-ryantm/nixpkgs/archive/1bf4070086ef25a583ed84eacb92260134f62014.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1bf4070086ef25a583ed84eacb92260134f62014#wavebox

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/366hlxw433pl6jmhsz74vxycyjjlga6n-wavebox-10.128.3-2
ls -la /nix/store/366hlxw433pl6jmhsz74vxycyjjlga6n-wavebox-10.128.3-2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

wavebox

Maintainer pings
cc @flexiondotorg for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for wavebox is: Wavebox Productivity Browser
meta.homepage for wavebox is: https://wavebox.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.128.4-2 in filename of file in /nix/store/cahkn4p8s13fgkgff82km37b1s40yrbz-wavebox-10.128.4-2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

wavebox

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/cahkn4p8s13fgkgff82km37b1s40yrbz-wavebox-10.128.4-2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wavebox https://github.com/r-ryantm/nixpkgs/archive/946e0fd3de6c37d7fcd874db95d66756af8e23b5.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/946e0fd3de6c37d7fcd874db95d66756af8e23b5#wavebox

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/cahkn4p8s13fgkgff82km37b1s40yrbz-wavebox-10.128.4-2
ls -la /nix/store/cahkn4p8s13fgkgff82km37b1s40yrbz-wavebox-10.128.4-2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

wavebox

Maintainer pings
cc @flexiondotorg for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for wavebox is: Wavebox Productivity Browser
meta.homepage for wavebox is: https://wavebox.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.128.5-2 in filename of file in /nix/store/filk9p0mhj1c57zchk8qyydygbkllii0-wavebox-10.128.5-2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

wavebox

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/filk9p0mhj1c57zchk8qyydygbkllii0-wavebox-10.128.5-2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wavebox https://github.com/r-ryantm/nixpkgs/archive/f993b8c0b506e6e1cc9d5cb35270722d94f3e23e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/f993b8c0b506e6e1cc9d5cb35270722d94f3e23e#wavebox

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/filk9p0mhj1c57zchk8qyydygbkllii0-wavebox-10.128.5-2
ls -la /nix/store/filk9p0mhj1c57zchk8qyydygbkllii0-wavebox-10.128.5-2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

wavebox

Maintainer pings
cc @flexiondotorg for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


Time between function calls

https://github.com/foundpatterns/torchbear/issues/27

what about when the logs are separated by potentially hours?

that's not at all what's going on in that screenshot

I know, it's a case the screenshot doesn't cover, I want to know what should we do if that happens? It can happen for sure, should we log hundreds of thousands of milliseconds or log the hour it happens?

timeago.js already answered that


Estimate Rewards

We currently calculate test group payments to users every two weeks to a month. We do this by collecting uptime, space, etc. over time for each user and then calculating a users relative performance to the network from the data to get a final payout.
There is an API exposed to do this for each user calculated daily: http://graph.driveshare.org/api/summary/15i4WvYn5KM5WupuCfQQvdTyHkXE34v2DE
Using the information from the API, and knowing the rewards to be distributed you can calculate and display the estimated rewards in real time to the user. You do this by doing points/total_points for a particular user to get their percentage of the total rewards.
Rewards increase linearly over time. So if 100k SJCX was supposed to be distributed in a month you would create a linear function current_user_rewards = rewards for the month * (current_time/month) * user_percentage. This should allow the user to see their estimated rewards go up every few seconds on the interface.

@gamedevsam Update?

@gordonwritescode Moving this to 0.7, but I'd like to have it done before then. Does it affect our core business? No. But it answers the question that is asked at least 3 times a day.

I removed the milestone due to lack of movement or communication on the issue. Milestones should track issues that have been triaged and discussed so that we can accurately plan releases.

Read: do we need to reassign this from @gamedevsam to myself or @mrfancymonocle?

Let discuss 0.6 and 0.7 milestones in their entirety tomorrow.

:+1:

I've made a calendar invite just to make sure we block out time
On Jan 5, 2016 4:46 PM, "Gordon Hall"<EMAIL_ADDRESS>wrote:

[image: :+1:]
—
Reply to this email directly or view it on GitHub
https://github.com/Storj/driveshare-gui/issues/72#issuecomment-169180346
.

hey @super3 i'm trying to visualize the rewards using the API that you sent, but I can't see nothing. In my DriveShare, my balance still zero...
how could I see the rewards?

@belisards This issue has the feature label. It is a issue for the devs. Please keep it clear. Please don't use it for FAQ. If you have any question you can ask on slack. If you think your question is importend you can open a new github issue. One closed issue more or less is not a problem for the devs as long as there own issues are clear.
Read the FAQ on the bottom of the page http://driveshare.org/rewards.html. There is the link to the last reward list. Look for your payout address. I hope to see you in slack for anything else :)

sorry, the slack was down yesterday. i will delete my first post and then this one, ok?

The closer we get to production the less meaningful this becomes. We won't be able to accurately estimate earnings as it will be based on the market. We can estimate payouts from bridge, but farmer-gui is not tied to bridge, so I'm not sure this should be an objective anymore.


no localtime on openbsd

as seen in https://github.com/tokio-rs/tracing/issues/2764 and https://github.com/Drakulix/simplelog.rs/issues/138 time does not properly return localtime on any version of openbsd. at best it returns nothing, at worst it crashes the app using the crate.

Given that one of the issues you linked is for tracing, is your program multi-threaded at the time of invocation? If so, that is why the call is failing. If it crashes the program, please post a stack trace.

not multithreaded. i posted over there but they said to bring the issue here.

Can you please provide some more information? At the moment, I have next to nothing to go off of.

let me know what you need and will try. there really isnt much i can see to go off of either.
using the example from https://time-rs.github.io/book/#getting-started here is what i get:
~/time-demo % cat Cargo.toml
[package]
name = "time-demo"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
time = { version = "0.3", features = ["macros", "local-offset"] }

~/time-demo % cat src/main.rs
use time::OffsetDateTime;

fn main() {
    println!("Hello, world!");

    let now_utc = OffsetDateTime::now_utc();
    dbg!(&now_utc);

    let now_local = OffsetDateTime::now_local();
    dbg!(&now_local);
}

~/time-demo % cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.01s
     Running `target/debug/time-demo`
Hello, world!
[src/main.rs:7] &now_utc = 2023-10-18 0:57:52.375686939 +00:00:00
[src/main.rs:10] &now_local = Err(
    IndeterminateOffset,
)

After looking at the possible scenarios where this could return the error variant, the reason is that no one has implemented a way to check the number of running threads (for the current process) for OpsnBSD. This information is required for soundness.

Closing in favor of jhpratt/num_threads#21, which is where the issue would actually be resolved.


realm_logo: Refactor build_realm_logo_widget function.

As a follow up of commit (bf1c9420dfcc846a8339a4388c9ad0cc65a2b3cc), this
commit removes the build_realm_day_mode_logo_widget and
build_realm_night_mode_logo_widget function , and changes
build_realm_logo_widget to take single argument is_night and depending
on this argument, corresponding day mode or night_mode widget is
handled.

As mentioned in https://github.com/zulip/zulip/pull/11698#issuecomment-470680089, I've refactored build_realm_logo_widget to take a single argument is_night, but about taking template refactors from Sahil's PR, I'm a little confused, do I need to rework his commit from his PR, and complete his work , or should I wait for his PR to get completed (which I guess he is doing, maybe) and then make further changes, if needed.
@timabbott FYI.

Merged, thanks @pragatiagrawal31!
I would just redo Sahil's PR in a clean way; I haven't had great luck getting him to adjust his PR to work the way it should, and I think getting it from what he's written to correct is more work than doing it from scratch.
There might also be some cleanups to exports.rerender  available as you proceed on this.


fix: update the current date when changing tabs

Fix #325
Previously the date was only update once the app start. So at some
point if the app survive a night, the date will be wrong. To prevent
that, we update now the date every time the tab is changed

I see why the CI tests failed, I will fix it

The CI here is green, however for the same code, the CI on my forked repository is red.
This test testItemCategories is inconsistent, and could failed, even when run on my Mac.
I don't understand why it's inconsistent yet.
Anyway, I will focus on that and do another PR, I don't think it's related with this one.

lgtm, @Dimillian, your turn


Set environment variable for preview mode

There are a couple hangups my team had with the current implementation of preview mode:

Having to explicitly pass preview or context into our data fetching tool in every route seems a little repetitive, and if missed could easily break the site, so it must be a hard-required parameter that throws an error if not present.
There's no way to tell if you're in preview mode or not in _app.js where we apply our layout. We'd love to be able to display a toolbar up top that calls out that you are in preview mode for extra clarity for viewers, but that becomes awkward when your layout can't tell if it's in preview mode or not.

Both of these are quickly and easily solved by having an environment variable reflect whether preview mode is active or not. I'm not sure if this is the most ideal spot to add it, but this feature immediately solves both problems and we would love to get it going if possible!
EDIT: Ok, I still have some work to do getting this to be present on the client side - right now it only works on server render.

Stats from current PR

Default Server Mode (Increase detected ⚠)

General Overall increase ⚠

zeit/next.js canary
jescalan/next.js preview-env-var
Change

buildDuration
12.6s
11.8s
-871ms

nodeModulesSize
58.7 MB
58.7 MB
⚠ +161 B

Page Load Tests Overall increase ✓

zeit/next.js canary
jescalan/next.js preview-env-var
Change

/ failed reqs
0
0
✓

/ total time (seconds)
2.011
1.97
-0.04

/ avg req/sec
1243.34
1269.17
⚠ +25.83

/error-in-render failed reqs
0
0
✓

/error-in-render total time (seconds)
1.148
1.143
0

/error-in-render avg req/sec
2178.18
2187.24
⚠ +9.06

Client Bundles (main, webpack, commons)

zeit/next.js canary
jescalan/next.js preview-env-var
Change

main-HASH.js gzip
6.67 kB
6.67 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

de003c3a9d30..e49d.js gzip
10.4 kB
10.4 kB
✓

framework.HASH.js gzip
39.1 kB
39.1 kB
✓

Overall change
57 kB
57 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
jescalan/next.js preview-env-var
Change

main-HASH.module.js gzip
5.71 kB
5.71 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..dule.js gzip
6.85 kB
6.85 kB
✓

framework.HA..dule.js gzip
39.1 kB
39.1 kB
✓

Overall change
52.4 kB
52.4 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
jescalan/next.js preview-env-var
Change

polyfills-HASH.js gzip
26.3 kB
26.3 kB
✓

Overall change
26.3 kB
26.3 kB
✓

Client Pages

zeit/next.js canary
jescalan/next.js preview-env-var
Change

_app.js gzip
1.26 kB
1.26 kB
✓

_error.js gzip
3.29 kB
3.29 kB
✓

hooks.js gzip
880 B
880 B
✓

index.js gzip
222 B
222 B
✓

link.js gzip
2.06 kB
2.06 kB
✓

routerDirect.js gzip
280 B
280 B
✓

withRouter.js gzip
278 B
278 B
✓

Overall change
8.26 kB
8.26 kB
✓

Client Pages Modern

zeit/next.js canary
jescalan/next.js preview-env-var
Change

_app.module.js gzip
599 B
599 B
✓

_error.module.js gzip
2.09 kB
2.09 kB
✓

hooks.module.js gzip
383 B
383 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js gzip
1.52 kB
1.52 kB
✓

routerDirect..dule.js gzip
279 B
279 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
5.37 kB
5.37 kB
✓

Client Build Manifests

zeit/next.js canary
jescalan/next.js preview-env-var
Change

_buildManifest.js gzip
61 B
61 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
122 B
122 B
✓

Rendered Page Sizes

zeit/next.js canary
jescalan/next.js preview-env-var
Change

index.html gzip
927 B
927 B
✓

link.html gzip
937 B
937 B
✓

withRouter.html gzip
925 B
925 B
✓

Overall change
2.79 kB
2.79 kB
✓

Serverless Mode (Increase detected ⚠)

General Overall increase ⚠

zeit/next.js canary
jescalan/next.js preview-env-var
Change

buildDuration
13s
13.1s
⚠ +65ms

nodeModulesSize
58.7 MB
58.7 MB
⚠ +161 B

Client Bundles (main, webpack, commons)

zeit/next.js canary
jescalan/next.js preview-env-var
Change

main-HASH.js gzip
6.67 kB
6.67 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

de003c3a9d30..e49d.js gzip
10.4 kB
10.4 kB
✓

framework.HASH.js gzip
39.1 kB
39.1 kB
✓

Overall change
57 kB
57 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
jescalan/next.js preview-env-var
Change

main-HASH.module.js gzip
5.71 kB
5.71 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..dule.js gzip
6.85 kB
6.85 kB
✓

framework.HA..dule.js gzip
39.1 kB
39.1 kB
✓

Overall change
52.4 kB
52.4 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
jescalan/next.js preview-env-var
Change

polyfills-HASH.js gzip
26.3 kB
26.3 kB
✓

Overall change
26.3 kB
26.3 kB
✓

Client Pages

zeit/next.js canary
jescalan/next.js preview-env-var
Change

_app.js gzip
1.26 kB
1.26 kB
✓

_error.js gzip
3.29 kB
3.29 kB
✓

hooks.js gzip
880 B
880 B
✓

index.js gzip
222 B
222 B
✓

link.js gzip
2.06 kB
2.06 kB
✓

routerDirect.js gzip
280 B
280 B
✓

withRouter.js gzip
278 B
278 B
✓

Overall change
8.26 kB
8.26 kB
✓

Client Pages Modern

zeit/next.js canary
jescalan/next.js preview-env-var
Change

_app.module.js gzip
599 B
599 B
✓

_error.module.js gzip
2.09 kB
2.09 kB
✓

hooks.module.js gzip
383 B
383 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js gzip
1.52 kB
1.52 kB
✓

routerDirect..dule.js gzip
279 B
279 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
5.37 kB
5.37 kB
✓

Client Build Manifests

zeit/next.js canary
jescalan/next.js preview-env-var
Change

_buildManifest.js gzip
61 B
61 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
122 B
122 B
✓

Serverless bundles Overall increase ⚠

zeit/next.js canary
jescalan/next.js preview-env-var
Change

_error.js
850 kB
850 kB
⚠ +161 B

404.html
4.18 kB
4.18 kB
✓

hooks.html
3.81 kB
3.81 kB
✓

index.js
850 kB
850 kB
⚠ +161 B

link.js
887 kB
887 kB
⚠ +161 B

routerDirect.js
880 kB
880 kB
⚠ +161 B

withRouter.js
880 kB
880 kB
⚠ +161 B

Overall change
4.35 MB
4.36 MB
⚠ +805 B

There's no way to tell if you're in preview mode or not in _app.js where we apply our layout. We'd love to be able to display a toolbar up top that calls out that you are in preview mode for extra clarity for viewers, but that becomes awkward when your layout can't tell if it's in preview mode or not.

A quick workaround for this would be to use pageProps in _app and return preview: true in getStaticProps of pages.

Closing as discussed offline. We'll work on a better solution for this.


Package/Module request: sops-nix

Project description
Atomic secret provisioning for NixOS based on sops

Metadata

homepage URL: https://github.com/Mic92/sops-nix
source URL: https://github.com/Mic92/sops-nix
license: mit
platforms: linux

Priorities
Add a :+1: reaction to issues you find important.

Adding it to nixpkgs would make setup easier, by not having to do things like this:
{
  imports = [
    "${
      builtins.fetchTarball {
        url = "https://github.com/Mic92/sops-nix/archive/59d6988329626132eaf107761643f55eb979eef1.tar.gz";
        sha256 = "0s33avmzay60bzx29fwpqpx5k30wgqqvll6h1mjc6kqvf3xqhsb4";
      }
    }/modules/sops"
  ];
}

Nixpkgs has releases, so it should be easier to manage for anyone not comfortable with just trying current HEAD.
Nixpkgs options are easily searchable.
The known limitations seem rather niche, and probably wouldn't be blockers for most users. It would still be useful to mention them.
But most importantly, AFAIK there's currently no simple way to manage secrets while using vanilla nixpkgs. sops-nix seems like an excellent first choice for this.


Animation compression has incorrect rotation

Tested versions

Reproducable in 4.3-stable

System information
Mac Mini, Apple Silicon
Issue description
With animation compression the animation glitches and jumps at certain points. With animation optimization done it does not.
https://github.com/user-attachments/assets/c0aaf8e3-3ab6-4b0e-843b-1dd4bfe02b27
Steps to reproduce

Open project
Disable animation optimization.
Switch import to animation compression enabled
Scrub the animation timeline and you will see near 6.1 s the animation flips.

Minimal reproduction project (MRP)
animation-compression-game-project.zip
From @Malcolmnixon

@TokageItLab @lyuma if you have any ideas

Just a guess, but the compression converts rotation to axis angle, so the ambiguity may be causing problems when the next angles are around 180 or 360 degrees.

Any idea how to solve? Can we directly get axis ambiguity?

I confirmed that changing the block size value from 8kb will change where the glitching occurs, so I think there is some problem with the data packet boundaries.

Do you think running a cubic / slerp interpolation between the end and the start will work?

There is definitely still work to be done, but IMO the stutter still looks better than the glitch, so I think it is acceptable to merge this PR and postpone the work to eliminate the stutter in the later.

From tokage


[SPARK-47491][CORE] Add slf4j-api jar to the class path first before the others of jars directory

What changes were proposed in this pull request?
This PR aims to add slf4j-api jar to the class path before the others of jars directory.
This will re-enable driver log links test in YarnClusterSuite, too.
Why are the changes needed?
BEFORE

The test fails due to the following in GitHub Action CI environment.

24/03/20 18:32:54.385 launcher-proc-24 INFO YarnClusterDriver: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
24/03/20 18:32:54.385 launcher-proc-24 INFO YarnClusterDriver: SLF4J: Defaulting to no-operation (NOP) logger implementation
24/03/20 18:32:54.385 launcher-proc-24 INFO YarnClusterDriver: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

[info] - running Spark in yarn-cluster mode displays driver log links *** FAILED *** (14 seconds, 21 milliseconds)
[info]   java.io.FileNotFoundException: /home/runner/work/spark/spark/target/tmp/spark-6660465a-18fd-41d7-be7c-a8f63b3c83ef/logs (No such file or directory)

AFTER

https://github.com/dongjoon-hyun/spark/actions/runs/8448089836/job/23139537396

[info] YarnClusterSuite:
[info] - run Spark in yarn-client mode (16 seconds, 37 milliseconds)
[info] - run Spark in yarn-cluster mode (15 seconds, 28 milliseconds)
[info] - run Spark in yarn-client mode with unmanaged am (12 seconds, 23 milliseconds)
[info] - run Spark in yarn-client mode with different configurations, ensuring redaction (14 seconds, 34 milliseconds)
[info] - run Spark in yarn-cluster mode with different configurations, ensuring redaction (15 seconds, 24 milliseconds)
[info] - yarn-cluster should respect conf overrides in SparkHadoopUtil (SPARK-16414, SPARK-23630) (13 seconds, 23 milliseconds)
[info] - SPARK-35672: run Spark in yarn-client mode with additional jar using URI scheme 'local' (15 seconds, 26 milliseconds)
[info] - SPARK-35672: run Spark in yarn-cluster mode with additional jar using URI scheme 'local' (15 seconds, 22 milliseconds)
[info] - SPARK-35672: run Spark in yarn-client mode with additional jar using URI scheme 'local' and gateway-replacement path (14 seconds, 22 milliseconds)
[info] - SPARK-35672: run Spark in yarn-cluster mode with additional jar using URI scheme 'local' and gateway-replacement path (15 seconds, 21 milliseconds)
[info] - SPARK-35672: run Spark in yarn-cluster mode with additional jar using URI scheme 'local' and gateway-replacement path containing an environment variable (15 seconds, 28 milliseconds)
[info] - SPARK-35672: run Spark in yarn-client mode with additional jar using URI scheme 'file' (14 seconds, 28 milliseconds)
[info] - SPARK-35672: run Spark in yarn-cluster mode with additional jar using URI scheme 'file' (15 seconds, 22 milliseconds)
[info] - run Spark in yarn-cluster mode unsuccessfully (12 seconds, 23 milliseconds)
[info] - run Spark in yarn-cluster mode failure after sc initialized (23 seconds, 25 milliseconds)
[info] - run Python application in yarn-client mode (16 seconds, 30 milliseconds)
[info] - run Python application in yarn-cluster mode (17 seconds, 27 milliseconds)
[info] - run Python application in yarn-cluster mode using spark.yarn.appMasterEnv to override local envvar (18 seconds, 26 milliseconds)
[info] - user class path first in client mode (15 seconds, 21 milliseconds)
[info] - user class path first in cluster mode (15 seconds, 22 milliseconds)
[info] - monitor app using launcher library (8 seconds, 501 milliseconds)
[info] - running Spark in yarn-cluster mode displays driver log links (16 seconds, 70 milliseconds)
[info] - timeout to get SparkContext in cluster mode triggers failure (16 seconds, 19 milliseconds)
[info] - executor env overwrite AM env in client mode (14 seconds, 23 milliseconds)
[info] - executor env overwrite AM env in cluster mode (14 seconds, 20 milliseconds)
[info] - SPARK-34472: ivySettings file with no scheme or file:// scheme should be localized on driver in cluster mode (29 seconds, 47 milliseconds)
[info] - SPARK-34472: ivySettings file with no scheme or file:// scheme should retain user provided path in client mode (28 seconds, 37 milliseconds)
[info] - SPARK-34472: ivySettings file with non-file:// schemes should throw an error (4 seconds, 37 milliseconds)

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs with re-enabled test case.
Was this patch authored or co-authored using generative AI tooling?
No.

YARN tests passed.

Could you review this PR, @HyukjinKwon ? This will recover the Maven Daily CI failure too.

Thank you for review and approval, @HyukjinKwon .
After recovering this YARN test and daily Maven CIs via this PR, we can revisit this area later while keeping CIs green.

Merged to master for Apache Spark 4.0.0.

For the record, Maven CI is recovered with this patch.

https://github.com/apache/spark/actions/runs/8452197772 (master Java 17 Maven)

late LGTM

@dongjoon-hyun
It's a bit magical, I found that in the latest test, Run / Build modules using Maven: repl,sql#hive-thriftserver also turned green, but before yesterday it was still red. May I ask if this is an additional benefit for this PR?

14 hours ago: https://github.com/apache/spark/actions/runs/8452197772/job/23152049324
2 days ago: https://github.com/apache/spark/actions/runs/8436403960/job/23138388265

Yes, @LuciferYang , as I mentioned in the above comment, I was also investigating them too because they failed at the log checking stage at that time due to SLF4J: Defaulting to no-operation (NOP) logger implementation.

https://github.com/apache/spark/pull/45618#issuecomment-2022177524

Before this PR, all Spark log output could disappear. In our CI, Spark Driver log and Spark Thrift Server log was missing. In the same way, all Spark JVMs like Spark Master and Spark Worker could be affected in the same way randomly before this PR.

May I ask if this is an additional benefit for this pr? Thanks ~

Thanks  for your explanation @dongjoon-hyun ~


'POST http://localhost:4200/users/sign_in 404 (Not Found)' with Rails 5 version of Devise

I was trying around Rails 5 and had to use a modified version of Devise to make it work because of the new routes structure of Rails. The issue is that now every time I try to login I get a 404 error.
POST http://localhost:4200/users/sign_in 404 (Not Found)

My setup is identical to this one. Just wanted to put this out here, I'll try and see if I can find a fix around this.

When the request is going to the wrong URL (on in this case the wrong port I guess), you need to configure the serverTokenEndpoint correctly.


Trait std::error::Error not implemented for dotenv::errors::Error

Much the same issue as here, but I'll put info here for simplicity.
Error is a trait that "[represents] the basic expectations for error values".
It should be easy to implement, the problem is that your implementation of failure::Fail conflicts because of the cause function. I was hoping there might be an updated version of failure that had fixed the issue and you could simply upgrade, but sadly the most recent version1 still has the collision.
1: Version 0.1.5 at time of writing this

Ok, upon further inspection I've found that you've fixed this problem: https://github.com/dotenv-rs/dotenv/commit/cfed2b85f4c8ed2816973200e8a228abfd45fdab
It's just not pushed as a version to crates.io
I'm going to leave this issue open to discuss a best way forward. For now I'm going to switch to Github in my Cargo.toml.

Does 0.15.0 contain this fix?

I don't have access to an IDE right now, but yes, it looks like 0.15.0 does indeed implement std::error::Error!
Thanks for the work that goes into this project!


fix FuzzyQuery in keyword field will use IndexOrDocValuesQuery when both of index and doc_value are true

Description
Fix FuzzyQuery in keyword field will use IndexOrDocValuesQuery when both of index and doc_value are true.
Related Issues
Resolves #14377

Check List

[x] Functionality includes testing.
[x] API changes companion pull request created, if applicable.
[x] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@harshavamsi  @msfroh, please help review the code when you are free, I am very grateful for this.

null

❌ Gradle check result for 751fc36: null
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

SearchRestCancellationIT.testAutomaticCancellationMultiSearchDuringQueryPhase #13674
RecoveryFromGatewayIT.testMultipleReplicaShardAssignmentWithDelayedAllocationAndDifferentNodeStartTimeInBatchMode #14346
RemoteSplitIndexIT.classMethod #13828

@dblock, please have s another look when you are free.

@andrross  please help merge, thank you.

❌ Gradle check result for 5e7ab2a: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

SearchWithRandomExceptionsIT.testRandomExceptions #14144


AMCL particles not appearing on rviz2

Hi,
My robot is working fine except 2 issues.
Thanks to Mr. Juan Miguel Jimeno.
issue 1: amcl particles are not appearing on the rviz2
issue 2: The robot BT navigator is making shortest path and robot is following the same. Can we have a slight margin (tolerance, wider radius) to make path in open place instead of shortest. I tried out with increased inflation but it not working out, Please.
Thanks , Regards, Hem

please post picture of rviz.
the nav config file is https://github.com/linorobot/linorobot2/blob/humble/linorobot2_navigation/config/navigation.yaml


Fix class pointer annotations

Fixes #4514
It looks like annotations attached to namenodes weren't correctly
processed with "InterpretCompilerDirectivesTransform"

Thanks


tolerate base_distro check & WSL detect

This will not work on Debian Linux. The changed script will search for all values with ID in the key. If there is the required value in the returned string, it passes the test.
WSL detection is not working on my debian WSL. I found the answer here: https://stackoverflow.com/a/38859331/13406850. It has been applied to the function.

Thanks for bringing this to my attention @ONLYA

I improved your solution a bit, do you mind checking if it is still working for you?

The base_distro is not assigned for fedora and Ubuntu. There should be an additional conditional assignment of base_distro from the distro_id_like.

Ah good point. For Ubuntu, it works, since it is going to be "debian". Now for Fedora it is going to fall in the "Unkown" section. And this part does not matter actually, since this script does not handle yum-based systems yet. No one has asked for this.
If someone complains about trying to install it on yum-based devices in the future, I will search better for an alternative to this function.
Maybe I just have to check if the apt or yum or whatever package manager the OS is present. And since the script just supports the known (by me) package managers, since functions have to be implemented, then it is currently a good enough approach, right?
Anyway, thanks for bringing this to my attention.


Multi-header assertion error

This is a variant on the SCC algorithm, mainly the yield statement are replaced: https://gist.github.com/sklam/dbe21c6df5b882bc41a27ff3e6cf79a0
Error:
Traceback (most recent call last):
  File "/path/to/numba-rvsdg/test_fig_scc.py", line 72, in <module>
    lflow = cflow._restructure_loop()
            ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/path/to/numba-rvsdg/byteflow2.py", line 637, in _restructure_loop
    restructure_loop(region.subregion)
  File "/path/to/numba-rvsdg/byteflow2.py", line 928, in restructure_loop
    extract_region(bbmap, loop, "loop")
  File "/path/to/numba-rvsdg/byteflow2.py", line 1002, in extract_region
    assert len(headers) == 1
AssertionError

After merging #20 this now passes the loop restructure phase but then a different exception is raised in the branch restructure phase:
Traceback (most recent call last):
  File "/Users/esc/git/numba-rvsdg/test_fig_scc.py", line 79, in <module>
    bflow = lflow._restructure_branch()
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/esc/git/numba-rvsdg/numba_rvsdg/core/datastructures/byte_flow.py", line 43, in _restructure_branch
    restructure_branch(region.subregion)
  File "/Users/esc/git/numba-rvsdg/numba_rvsdg/core/transformations.py", line 345, in restructure_branch
    head_region_blocks = find_head_blocks(bbmap, begin)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/esc/git/numba-rvsdg/numba_rvsdg/core/transformations.py", line 244, in find_head_blocks
    assert len(jt) == 1
AssertionError

With #40 I was able to fix this issue too, and was able to render the graph for this code for the first time.
Even with the monitor set to vertical orientation, the nodes are quite small:

With #61 the scc is now fully working and the test case has been added to the test-suite.
Here is s screenshot:

To note, that #61 eliminates the last bugs in the tail detection, as now all blocks are inside their tails. We still need to check if the translation is indeed correct manually.

@sklam can we close this now, are you satisfied?

Do we have a test for this for both loop and branch restructing?


Flow continuation fails when combining fdk handler to accept http input to function

With the provided flow example, add code from the fdk boiler plate to accept http input to the function as in the attached file. The stage continuation fails with the following output:
Enabled debugging
Awakened flow 26607dbd-66be-4eab-a2af-f09c43b43904
Handling continuation
panic: Failed to decode stage invocation request: EOF
goroutine 1 [running]:
func/vendor/github.com/fnproject/flow-lib-go.handleInvocation(0x8e79e0, 0xc42031cbe0)
/go/src/func/vendor/github.com/fnproject/flow-lib-go/invocations.go:86 +0x1ab
func/vendor/github.com/fnproject/flow-lib-go.WithFlow(0x8af880)
/go/src/func/vendor/github.com/fnproject/flow-lib-go/flows.go:108 +0x126
main.stringExample()
/go/src/func/func.go:58 +0x2d
main.myHandler(0x8e73a0, 0xc420070600, 0x8e3e60, 0xc42000e010, 0x8e3e80, 0xc42000e018)
/go/src/func/func.go:51 +0xcb
func/vendor/github.com/fnproject/fdk-go.HandlerFunc.Serve(0x8af878, 0x8e73a0, 0xc420070600, 0x8e3e60, 0xc42000e010, 0x8e3e80, 0xc42000e018)
/go/src/func/vendor/github.com/fnproject/fdk-go/fdk.go:19 +0x62
func/vendor/github.com/fnproject/fdk-go/utils.DoDefault(0x7f1e08c827c0, 0x8af878, 0x8e73a0, 0xc420070600, 0x8e3e60, 0xc42000e010, 0x8e3e80, 0xc42000e018)
/go/src/func/vendor/github.com/fnproject/fdk-go/utils/utils.go:63 +0xf9
func/vendor/github.com/fnproject/fdk-go/utils.Do(0x7f1e08c827c0, 0x8af878, 0xc4200240aa, 0x7, 0x8e3e60, 0xc42000e010, 0x8e3e80, 0xc42000e018)
/go/src/func/vendor/github.com/fnproject/fdk-go/utils/utils.go:49 +0x251
func/vendor/github.com/fnproject/fdk-go.Handle(0x8e4380, 0x8af878)
/go/src/func/vendor/github.com/fnproject/fdk-go/fdk.go:81 +0xce
main.main()
/go/src/func/func.go:31 +0x39
func.go.zip

There are a couple of reasons your example is failing:

The complete flow-based program needs to be enclosed within a flows.WithFlow block.  If you consume input or produce function output outside the block, things will break.
By calling printResult you are writing to the function's output. However, you later try to serialize a struct to json to stdout as well, so you have a mix of logging output and json. I doubt that is what you want.

Here is a snippet which does what I believe you want:
func myHandler(ctx context.Context, in io.Reader, out io.Writer) {
	flows.WithFlow(
		func() {
			p := &Person{Name: "World"}
			json.NewDecoder(in).Decode(p)
                          // use the name passed in as input to the function as initial flow stage
			cf := flows.CurrentFlow().CompletedValue(p.Name)
			valueCh, errorCh := cf.ThenApply(strings.ToUpper).ThenApply(strings.ToLower).Get()
			select {
			case value := <-valueCh:
                                   // output the result of the flow transformation as the result of this function
				p.Name = value.(string)
				json.NewEncoder(out).Encode(p)
			case err := <-errorCh:
				io.WriteString(out, fmt.Sprintf(`{"error":"Flow failed with error %v}`, err))
			case <-time.After(time.Minute * 1):
				io.WriteString(out, `{"error":"Flow timed out}`)
			}
		})
}


increase the resource limit for mco.

Signed-off-by: morvencao<EMAIL_ADDRESS>

@clyang82 not sure if we also need to increase the limit for CPU?

/lgtm


__CPP__REDIS_USE_CUSTOM_TCP_CLIENT build Error with no tacopie !

1.should add #ifndef __CPP__REDIS_USE_CUSTOM_TCP_CLIENT for every tacopie include
2.sentinel with no default construct error
3.sentinel.hpp and subscriber.hpp miss atomic include

Hi,
Thanks for reporting this issue, all the points listed here make sense and a fix will be pushed soon!
Best

fixed and pushed on master


Used Golang version is deprecated

The used Golang version is deprecated and since more than one and half year non-official supported.

Upgraded to 1.17


Change game ticking to start when it changes to RUNNING state

Motivation
This is required for sending state diffs, otherwise when players are joining they already are behind/don't know the original state the diff is referring to
Summary of changes

Change when we start calling update_game

How to test it?
Play games and nothing should have changed
Checklist

[x] Tested the changes locally.
[x] Reviewed the changes on GitHub, line by line.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

This breaks something in the clients (or how the flow is managed) and results in clients able to move as soon as it loads rather than after the countdown

Not going to happen for now


feat: 增加spring cloud nacos config配置提醒信息，方便快速配置nacos

Describe what this PR does / why we need it
增加配置提醒，方便用户快速配置nacos，这个pr还是很有用的
Does this pull request fix one issue?
None
Describe how you did it
没有任何
Describe how to verify it
Special notes for reviews

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


AMC-I Restructure into AWS Solutions repository format (folders, scripts, etc.)

Install skeleton solution layout into a branch, consider merging or other to re-organize.

Issue attached to incorrect repository. Closing and tracking issue here instead: https://github.com/orgs/aws-solutions/projects/9/views/2?filterQuery=AMC-I&pane=issue&itemId=21557142


add O_EXEC and O_SEARCH on apple

according to this fcntl.h,they exist: https://github.com/apple-oss-distributions/xnu/blob/main/bsd/sys/fcntl.h#L184C9-L184C47

O_SEARCH = (0x40000000 | 0x00100000) does the right thing on macos 13, but on macos 12 the read permission for the directory is still checked on opening, so i think it will be ignored there. (tried on github actions, as I don't own an apple device)
if we need a compile time version check to not provide the symbol for macos 12 (older versions are end of life), I currently don't know how to do it, help would be welcome.


Low numbers of genes in DGE

I am trying to perform DGE analysis of Kallisto results. However, the genes in differential gene expression are very low numbers.
Here is my script and results:
names(files) <- paste0("sample", 1:187)
txi.kallisto <- tximport(files, type = "kallisto", txOut = TRUE)
head(txi.kallisto$counts)
sampleMetaData <- data.frame(Group=c(rep(c("mutant"), 94), rep(c("control"), 93)), Gender=rep(c(rep(c("F"),
130), rep(c("M"), 57))))
rownames(sampleMetaData) <- colnames(txi.kallisto$counts)
dds <- DESeqDataSetFromTximport(txi.kallisto, sampleMetaData, design= ~ Group + Gender)
res <- results(dds)
dds <- DESeq(dds)
###Results###
out of 171018 with nonzero total read count
adjusted p-value < 0.1
LFC > 0 (up)       : 975, 0.57%
LFC < 0 (down)     : 12, 0.007%
outliers [1]       : 0, 0%
low counts [2]     : 73970, 43%
(mean count < 2)

It's hard for us to examine this without us having access to the starting data that you are using.


Implementation of BETA BCO Ranking systems

Implement the ideas from #328 into the BCO Scoring function:
https://github.com/biocompute-objects/bco_api/blob/456d00293e51f057b9d1755835e36e31881b9fe1/biocompute/services.py#L599-L621

BCO Scoring System New.zip

Spoke with Hadley and we had some ideas for the representation of the scores in the data model. I've been implementing scores in the biomarker project for scoring "trustworthy" biomarkers and a few things that we've done that have made things easier to track are:

Have some sort of internal versioning for the scores. The scoring is an iterative process that changes over time and as it changes having some sort of way to delineate which scores come from which version formula is very helpful.
When calculating the scores, create an object with the formula breakdown. This can be used both internally when investigating scores and on the frontend to show users how the score was calculated/where the weights are coming from. The biomarker project has that information in our data schema and returns it on API requests. It looks like this:

{
  "score": 3.4,
    "score_info": {
      "contributions": [
        {
          "c": "first_pmid",
          "w": 1,
          "f": 1
        },
        {
          "c": "other_pmid",
          "w": 0.2,
          "f": 7
        },
        {
          "c": "first_source",
          "w": 1,
          "f": 1
        },
        {
          "c": "other_source",
          "w": 0.1,
          "f": 0
        },
        {
          "c": "generic_condition_pen",
          "w": -4,
          "f": 0
        },
        {
          "c": "loinc",
          "w": 1,
          "f": 0
        }
      ],
      "formula": "sum(w*f)",
      "variables": {
        "w": "weight",
        "c": "condition",
        "f": "frequency"
      }
    }
}

This shows that the score was calculated by the sum of the weights times the frequencies. For example, having one PMID associated with the biomarker is a weight of 1. Additional PMIDs get a weight of 0.2, and so on. So the calculation for this score was 1(1) + 0.2(7) + 1(1).

Write a FAQ on how the ranking system works, criteria, etc?

FAQ created in #446


Ctrl+right goes too far

Issue Type: Bug
Pressing Ctrl+arrowright at the end of a line will jump to the end of the first word on the next line.
Expectation:
Pressing Ctrl+arrowright should go to the beginning of the next word, not the end.
Ctrl+arrowleft works as expected.
This issue is reproducible with all extensions disabled.
VS Code version: Code 1.33.0 (0dd516dd412d42323fc3464531b1c715d51c4c1a, 2019-04-04T15:14:28.026Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2904)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.74GB (17.54GB free)

Process Argv

Screen Reader
no

VM
67%

Extensions (21)

Extension
Author (truncated)
Version

better-comments
aar
2.0.3

overtype
ada
0.2.0

Bookmarks
ale
10.4.3

html-class-suggestions
And
1.0.7

color-info
bie
0.5.0

mustache
daw
1.1.1

vscode-eslint
dba
1.8.2

vscode-babel-coloring
dza
0.0.4

EditorConfig
Edi
0.13.0

file-icons
fil
1.0.16

auto-close-tag
for
0.5.6

duplicate
gee
1.0.1

beautify
Hoo
1.4.11

docthis
joe
0.7.1

vscode-duplicate
mrm
1.2.1

vscode-subword-navigation
ow
1.2.0

vscode-docker
Pet
0.6.1

vscode-versionlens
pfl
0.22.0

vscode-sort-json
ric
1.13.0

code-settings-sync
Sha
3.2.8

vscode-svg-previewer
vit
0.5.0

The expectation is the same with the behavior of Scintilla.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I'm not sure if this is a viable work around, but there's a lot of cursorWord* shortcuts available that are not defined by default. Perhaps using cursorWordStart(Left|Right) (and the associated *Select) would fit your desired behavior?

I do think there's, at a minimum, room for these shortcuts to make it into the settings somehow. Perhaps there could be a dropdown setting Cursor > Navigation > Cursor Navigation Profiles that has things like Word Start, Word End, Word Part, etc
I'm not sure if changing to Word Start actually fixes the issue as I'm not sure if Word End should treat whitespace as nothing, so perhaps an additional setting that's a checkbox to Cursor > Navigation > Treat Whitespace as a Word. Kind of ambiguous, but this would allow us to use the new Word End profile to still skip over . (and whatever things it skips over).

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

But it's not a feature request...

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


[0.9.0] line protocol: inserting multiple points without timestamp loses points

if i try to insert multiple points without a timestamp, only the last one is used.  i assume this is because they are all sharing the same timestamp.
should they each get a different timestamp or is this an invalid use case?  fyi: i don't have a need to be able to do this - it was done just as part of trying to make a script that might reproduce #2883
echo "creating database"
curl -G -ipv4 http://localhost:8086/query --data-urlencode "q=CREATE DATABASE foo"

echo "inserting data"
curl -d \
"score value=1
score value=2
score value=3" -ipv4 http://localhost:8086/write?db=foo

sleep 5

curl -G -ipv4 http://localhost:8086/query --data-urlencode "q=select value from score" --data-urlencode "pretty=true" --data-urlencode "db=foo"

EDIT: i'd lean towards it being invalid input - i can't seem to think of a situation where this would make sense.

It is an interesting question. In order to trigger this the user must provide multiple points with identical tag sets and no timestamps. I don't think we can know whether they intend the values to overwrite previous or add new points a few nanoseconds apart. I lean towards documenting the behavior for now and mark this RFC to see what the community prefers.
RFC question: When writing multiple points in a batch that have matching tag sets but no timestamps, should all the points be added with slightly different timestamps, or should one point win and all others be dropped? If the latter, which should win, the first point or last point parsed?

alternatively, should it be an error to try to send more than 1 point with matching tags but no timestamps?

Currently, any points without timestamps in a batch all receive the same timestamp.  That last one wins because it's the last point that is actually written when iterating over the points.  We could assign a new timestamp to each point as well but its always better to send points in with timestamps.
I don't think we should reject the write as it would cause extra overhead during parsing to detect this edge case which will slow things down for all writes.

this is a wontfix for now.