All packages installed but ImportError("packages h5py and pytables are missing!")

Hello, I'm new using Acoular and I'm having some issues with it.
One of them is that yesterday I ran the example "Airfoil in open jet – CMF" and everything went fine, but today I ran the exact same code again and it's giving this weird error, that I quote below.
And I do have all the packages that Acoular require installed, I don't know what is happening.
But the weirdest thing is that when I run the code in Spyder (using Anaconda) it magically works again.
I wish that someone can help me figure it out.
Thanks in advance for your attention.

Traceback (most recent call last):
File "D:\Softwares\Python\lib\site-packages\acoular\configuration.py", line 88, in assert_h5library
import tables
File "D:\Softwares\Python\lib\site-packages\tables_init.py", line 99, in
from .utilsextension import (
File "init.pxd", line 206, in init tables.utilsextension
File "D:\Softwares\Python\lib\site-packages\numpy_init_.py", line 152, in
from . import random
File "D:\Softwares\Python\lib\site-packages\numpy\random_init_.py", line 181, in
from . import _pickle
File "D:\Softwares\Python\lib\site-packages\numpy\random_pickle.py", line 1, in
from .mtrand import RandomState
File "_bit_generator.pxd", line 14, in init numpy.random.mtrand
File "_bit_generator.pyx", line 255, in init numpy.random._bit_generator
AttributeError: type object 'numpy.random._bit_generator.SeedSequence' has no attribute 'reduce_cython'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:\Softwares\Python\lib\site-packages\acoular\configuration.py", line 92, in assert_h5library
import h5py
File "D:\Softwares\Python\lib\site-packages\h5py_init.py", line 34, in
from . import version
File "D:\Softwares\Python\lib\site-packages\h5py\version.py", line 19, in
import numpy
File "D:\Softwares\Python\lib\site-packages\numpy_init_.py", line 152, in
from . import random
File "D:\Softwares\Python\lib\site-packages\numpy\random_init_.py", line 181, in
from . import _pickle
File "D:\Softwares\Python\lib\site-packages\numpy\random_pickle.py", line 1, in
from .mtrand import RandomState
File "_bit_generator.pxd", line 14, in init numpy.random.mtrand
File "_bit_generator.pyx", line 255, in init numpy.random._bit_generator
AttributeError: type object 'numpy.random._bit_generator.SeedSequence' has no attribute 'reduce_cython'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:\Workspace\Python\acoular testing\acoular_example_2.py", line 19, in
import acoular
File "D:\Softwares\Python\lib\site-packages\acoular_init_.py", line 59, in
from .configuration import config
File "D:\Softwares\Python\lib\site-packages\acoular\configuration.py", line 99, in
config = Config()
File "D:\Softwares\Python\lib\site-packages\acoular\configuration.py", line 37, in init
self._assert_h5library()
File "D:\Softwares\Python\lib\site-packages\acoular\configuration.py", line 95, in _assert_h5library
raise ImportError("packages h5py and pytables are missing!")
ImportError: packages h5py and pytables are missing!

This looks more like a problem in a different package, maybe due to deprecation. What version of numpy do you have installed?

I have installed the Numpy version 1.18.1.

Should be alright, actually. However, the error message still indicates that something with numpy's random number generator's initialization is not working correctly (numpy changed random number handling in 1.17.0). The ImportError thrown does indicate that tables AND h5py could not be imported correctly (because of them not being able to correctly import numpy), so something seems to be really broken in your general python setup.
I'd suggest to install a python distribution with conda, where you can make sure that all dependencies of installed packages are checked automatically.

So I tried to fix it by reinstalling python and all the packages and surprise, didn't work, so I did it again but this time I installed the same version of the packages that I have on my Conda, and also didn't work.
Really weird stuff. So I guess I need to start using Acoular through Conda, where it works.
Thanks anyway.


Automatically deploy main branche chart updates.

This Pull request aims to remove manual publishing of chart versions, stemming from issue #54
From the base as described on helm.sh and their example repo
This PR:

Adds instructions on how to add this helm repo and install this chart for an user
Moves the chart into the charts subdirectory, per Helm's defaults
Removes the two included dependencies artifacts in favour of inclusion in GitHub actions
Assumes the .helmignore defaults from the example repo
Adds testing configuration to the root
Adds a GitHub action that will package, upload, and deploy the chart to releases and the gh-pages branch, which does require the repository to follow these requirements; which it already does as far as I know

As far as I can see this should not introduce any breaking changes for users of this chart.

@jdenquin Would you have some time to look at this?

Hi @gilliangoud,
Thanks a lot for your PR! 🙏 It’s a great contribution, but for now, we’re avoiding breaking changes since some users still pull directly from the repo to deploy Lago. We’ve created a separate PR to address some of your ideas while maintaining compatibility.
We really appreciate your input and hope to collaborate more in the future!


Parallel tests do not complete

🐛 Bug
Parallel tests do do not complete
To Reproduce
Steps to reproduce the behavior:

poetry build
poetry run pytest -vv

Expected behavior

Environment
Not needed a virtual env is created by poetry

Solved in https://github.com/fteicht/scikit-decide/tree/master


glide: bump gopsutil to v2.16.10

This new version includes fixes for ppc64le which prevent rkt from
failing at build time on this platform.
Signed-off-by: Thomas Hipp<EMAIL_ADDRESS>

ok to test


vLLM error with omniquant Llama-3-8b

Hi developer,
I found another param_dict error when using vLLM for omniquant compressed  Llama-3-8b  (which saved with vLLM=True)

File ~/delta_p/lib/python3.10/site-packages/vllm/model_executor/models/utils.py:175, in AutoWeightsLoader._load_module(self, base_prefix, module, weights)
173     module_load_weights = getattr(module, "load_weights", None)
174     if callable(module_load_weights):
--> 175         module_load_weights(weights)
176         return
178 child_modules = dict(module.named_children())
File ~/delta_p/lib/python3.10/site-packages/vllm/model_executor/models/llama.py:407, in LlamaModel.load_weights(self, weights)
404 if is_pp_missing_parameter(name, self):
405     continue
--> 407 param = params_dict[name]
408 weight_loader = getattr(param, "weight_loader",
409                         default_weight_loader)
410 weight_loader(param, loaded_weight)
KeyError: 'layers.0.fc1_smooth_scale'
Thank you for your help!

Can you provide the configuration file?

Thank you for your reply, here is the configuration file, I also tried the qwen2 but also face the same error
base:
seed: &seed 2
model:
type: Llama
path: meta-llama/Meta-Llama-3-8B-Instruct
torch_dtype: auto
calib:
name: wikitext2
download: True
path: /save_files/data
n_samples: 128
bs: 10
seq_len: 2048
preproc: wikitext2_gptq
seed: *seed
eval:
eval_pos: []
name: wikitext2
download: True
path: /save_files/data
seq_len: 2048
# For 7B / 13B model eval, bs can be set to "1", and inference_per_block can be set to "False".
# For 70B model eval, bs can be set to "20", and inference_per_block can be set to "True".
bs: 10
inference_per_block: False
# Consistency of tokens between original and fake-quantized model output.
eval_token_consist: True
quant:
method: OmniQuant
weight:
bit: 8
symmetric: True
granularity: per_channel
calib_algo: learnable
ste: True
act:
bit: 8
symmetric: True
granularity: per_token
ste: True
special:
aug_loss: False
let: True
lwc: True
lwc_lr: 0.01
# Set "let_lr: 0.001" for w4a4 quantization.
let_lr: 0.005
# Set to "True" if the model has bias (e.g. Opt).
use_shift: False
# Use "0.75" for w4a4 quantization.
alpha: 0.5
deactive_amp: True
epochs: 1
wd: 0
robust_weight: 0
quant_out: True
save:
save_trans: False
save_vllm: True
save_path: vllm_omni_llama3_8b_w8a8

Okay, I'll try to reproduce the problem you encountered.

thank you very much !

You can try the latest code, which has already fixed the mentioned issue.

You can try the latest code, which has already fixed the mentioned issue.

Thank you for your help, however, it seems the added code influenced the block_forward function and caused the following error. May I know your configuration?
[rank0]: Traceback (most recent call last):
[rank0]:   File "/data/dwenlong/llmc/llmc/main.py", line 317, in
[rank0]:     main(config)
[rank0]:   File "/data/dwenlong/llmc/llmc/main.py", line 121, in main
[rank0]:     blockwise_opt.run_block_loop()
[rank0]:   File "/data/dwenlong/llmc/llmc/compression/blockwise_optimization.py", line 40, in run_block_loop
[rank0]:     self.block_opt(self.blocks[self.block_idx])
[rank0]:   File "/data/dwenlong/llmc/llmc/compression/quantization/base_blockwise_quantization.py", line 418, in block_opt
[rank0]:     self.run(block, input_feat, handles)
[rank0]:   File "/data/dwenlong/llmc/llmc/compression/quantization/base_blockwise_quantization.py", line 463, in run
[rank0]:     self.input['data'] = self.block_forward(block)
[rank0]:   File "/data/dwenlong/llmc/llmc/compression/quantization/omniq.py", line 132, in block_forward
[rank0]:     input_data[i] = input_data[i].to(device=next(block.parameters()).device)
[rank0]: StopIteration

The latest code should not affect the block forward function. You can clone it again, update the running environment (especially the transformers version), and try to run it again.


Use preview version of ruby

I've just install Ruby 2.5.0 preview with: ruby-install ruby 2.5.0-preview1 but chruby doesn't seem to see it (not listed in chruby and I can't seem to switch to it). It's located at ~/.rubies/ruby-2.5.0-preview1 and was successfully installed.
Is there a way to switch to it with chruby?

Never mind, just needed to reload bash 🙄


ShellTest.DiscardLayerTreeOnResize is flaky on presubmits.

An instance of the failure is here. The assertion failure is:
[ RUN      ] ShellTest.DiscardLayerTreeOnResize
../../flutter/shell/common/shell_unittests.cc:2373: Failure
Expected equality of these values:
  1
  external_view_embedder->GetSubmittedFrameCount()
    Which is: 2
[FATAL:flutter/fml/memory/weak_ptr.h(253)] Check failed: (checker_.checker).IsCreationThreadCurrent().
[ERROR:flutter/fml/backtrace.cc(116)] Caught signal SIGABRT during program execution.
Frame 0: 0x7fa680ecf42a abort

The test passed on re-run.

/cc @knopp @cyanglaz

I'm not able to reproduce this locally. If anyone has any luck reproduce this, please share the trick.
This test does not require external_view_embedder, but the current architecture requires external_view_embedder to be included in the test. It adds complicated thread merging logic into a simple test like this. I'm going to look into refactor this test so that it doesn't require thread merging, which can solve this issue as well.

please share the trick

This is a flake so there may not be a fully reliable way of reproducing this. But, the best shot IMO would be to rerun the same test with same seed used by the bots. From the logs, the seed was 96731. So --gtest_repeat=-1 --gtest_random_seed= 96731 ought to get you closest to the what the bot was doing.
If that fails, I would try running it with the thread sanitizers. But this would only be for data races and not race conditions.
Failing that, just good old fashioned reading the test to see if it non-racy or rewrite the test. Your intuituion that the test can be made less complicated is probably the right way to go.

I tried to rerun with repeats=-1 and was unsuccessful to repro. Haven't tried the random_seed, I'll try that.
Yeah if I still can't repro it i'll rewrite the test. There was a TODO I left for that test to rewrite it to remove the thread merging from that test anyway.

This is still failing https://cirrus-ci.com/task/5065923601104896

@cyanglaz Are you able to reason about this failure? Perhaps this is a different issue? Feel free to un-assign yourself if this is different from what you were originally trying to fix.

The thread merging part of the test has been removed and the failure is probably not related to the race condition in the thread merging set up in the test.
Maybe the test code I ended up with is wrong? Or the test failure actually indicates some issue with the current engine code?
CC @knopp @iskakaushik who might know more about this.
Could either of you review the current unittest and see if the test makes sense. https://github.com/flutter/engine/blob/main/shell/common/shell_unittests.cc#L2345

cc @iskakaushik Can you take a quick look at the test if you have some spare cycles?

@iskakaushik is OOO this week. I'll try to take a look at this this week but I am not sure I will be able to resolve it.

From critical issue triage, assigning you @chinmaygarde per your comment

I found another stack trace that looks similar, but in another test: ShellTest.ResubmitFrame.
https://cirrus-ci.com/task/5627663783034880?logs=test_host#L6132
[ RUN      ] ShellTest.ResubmitFrame
../../flutter/shell/common/shell_unittests.cc:1324: Failure
Expected equality of these values:
  1
  external_view_embedder->GetSubmittedFrameCount()
    Which is: 2
[FATAL:flutter/fml/memory/weak_ptr.h(253)] Check failed: (checker_.checker).IsCreationThreadCurrent().
[ERROR:flutter/fml/backtrace.cc(116)] Caught signal SIGABRT during program execution.
Frame 0: 0x7f47f47d842a abort
Frame 1: 0x273e7d9 Unknown
Frame 2: 0x273e7b8 fml::LogMessage::~LogMessage()
Frame 3: 0x268f73c fml::WeakPtrFactory<>::CheckThreadSafety()
Frame 4: 0x2683529 fml::WeakPtrFactory<>::~WeakPtrFactory()
Frame 5: 0x2628ca4 flutter::Shell::~Shell()
Frame 6: 0x234546b std::__1::default_delete<>::operator()()
Frame 7: 0x23453ec std::__1::unique_ptr<>::reset()
Frame 8: 0x2342c79 std::__1::unique_ptr<>::~unique_ptr()
Frame 9: 0x246e662 flutter::testing::ShellTest_ResubmitFrame_Test::TestBody()
Frame 10: 0x43953eb testing::internal::HandleSehExceptionsInMethodIfSupported<>()
Frame 11: 0x4385a27 testing::internal::HandleExceptionsInMethodIfSupported<>()
Frame 12: 0x43750d3 testing::Test::Run()
Frame 13: 0x4375794 testing::TestInfo::Run()
Frame 14: 0x4375d9d testing::TestSuite::Run()
Frame 15: 0x437f561 testing::internal::UnitTestImpl::RunAllTests()
Frame 16: 0x439882b testing::internal::HandleSehExceptionsInMethodIfSupported<>()
Frame 17: 0x4387467 testing::internal::HandleExceptionsInMethodIfSupported<>()
Frame 18: 0x437f15f testing::UnitTest::Run()
Frame 19: 0x41af591 RUN_ALL_TESTS()
Frame 20: 0x41af412 main
Frame 21: 0x7f47f47c42e1 __libc_start_main
Frame 22: 0x233176a _start

From triage: We should consider disabling these tests.

I filed a PR to disable these tests: https://github.com/flutter/engine/pull/32059

@iskakaushik is planning to give deflaking these one more try.


Exclude Teams from being installed

fixes #38

@activeshadow Thank you very much for the contribution. That's a clean and simple fix. Much appreciated. 👍


resolved conflicts of pr #340 and fixed tests

Thank you very much for your work. I didn't get the time to do this work.

Great, thanks @langco. It seems like there are some conflicts with the target branch to resolve. Also, the version should be 3.1.0 now.

Just manually tested it and it seems to work well 👍

You are welcome. I will have a look at the conflicts and update the pull request.

Resolved all conflicts.

Thanks a million again.


Does the dell e7240 profile or readme need some updating?

Having some suspend issues myself but I'm not about to go all the way back to 4.14 kernels when the 5.xx upstreams have fixed it somewhere.

Potentially out-dated, any thoughts? @ashgillman
I cannot comment on that further as I don't own the hardware.
In general you can try linuxPackages_latest to see if it fixes the issue.

I'm afraid I'm no longer using the hardware to comment with any certainty.
However, the linked bug report in the README reports the problem as fixed in 4.18.10, I can't comment on 5.xx but if it works for you without adding this line then I suggest the README be removed.
I imagine this file to still be fine.

Okay, thanks, maybe I'll manage this one.


feat: support scopes on compute credentials

The GCE metadata server is adding support for requesting tokens against user accounts with a predefined set of scopes.  This adds experimental support for passing the scopes as querystring parameters to the metadata service in compute credentials.

@bcoe @alexander-fenster this is ready for a look :)


dune-release fails with curl: command not found

dune-release fails with the following command:
[-] Creating release 4.3.0 on https://github.com/lemaetech/http-cookie.git via github's API
dune-release: [ERROR] curl execution failed: Non 0 exit code Exit code 127
  {status=Exit code 127; stderr="/bin/sh: line 1: curl: command not found
  ";
  stdout=""}

Curl is in the path
$ /bin/sh
sh-5.1$ curl --version
curl 7.86.0 (x86_64-pc-linux-gnu) libcurl/7.86.0 OpenSSL/3.0.7 zlib/1.2.13 brotli/1.0.9 zstd/1.5.2 libidn2/2.3.2 libssh2/1.10.0
 nghttp2/1.49.0
Release-Date: 2022-10-26
Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tft
p
Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB SPNEGO SSL thre
adsafe TLS-SRP UnixSockets zstd

Thanks for the report. Can you run which curl (or similar) from the shell where you're running dune-release? dune-release uses curly for making HTTP requests, so it needs a curl binary in the $PATH.

uses curly for making HTTP requests, so it needs a curl binary in the $PATH.

Do you mean curl? If so, here is the output:
$ /bin/sh
sh-5.1$ which curl
/run/current-system/sw/bin/curl

Is /run/current-system/sw/bin in your $PATH? We use the curly package which is an OCaml wrapper around curl, but as much as I look into its source, it doesn't use any hardcoded paths for curl (like /usr/bin/curl or so), it just uses the regular PATH lookup.

It seems curly doesn't set the PATH env when spawning curl. Here is the PR to fix it https://github.com/rgrinberg/curly/issues/11. After the fix is merged and released dune-release probably needs a version bump on dependencies list. Will keep this open till then. Thanks for your help.

Thanks for your investigation! I will bump the minimal required version once a new version of curly is out.

Looks like this can be bumped up to curly 0.3.0 now?


chore(docs): -a is not a vaild flag for kubectl get pods

kubectl get pods will take -A, which indicates --all-namespaces and is not needed in this case because the command declares the namespace

@fernandoataoldotcom thanks for the pr


Attempting to use Flexbox, not working

I am trying to use the Bootstrap 4 flexbox (https://v4-alpha.getbootstrap.com/utilities/flexbox/).
Something simple like this:

Flex item

Flex item

Flex item

The classes don't seem to be appearing correctly. I am using the Angular 2 version, with scss.
I do see the 'utilities' being pulled in style.scss
@import "bootstrap_src/utilities";
Any way to get the flex to work?

Found this: http://coreui.io/docs/utilities/flexbox#enable-flex-behaviors, and I think that works. It messes up other layouts that I have though.
I still see some other bootstrap utilities that do not seem to work though.


some svg support advice

I'm Chinese developer.This lib is wonderful.To solve my some problem.But I found your support svg format are: path,polygon,rect,ellipse,circle.Why don't you support polyline.Although I found other ways to solve it。I hope you could support "polyline".By the way.I like this lib.

The need hadn't come up.
We'd welcome a patch adding support.

polyline support is in!


set up SSO with github or google

Currently going with Google using flask-dance (https://flask-dance.readthedocs.io/en/v0.8.0/quickstarts/google.html#code)

Created a branch https://github.com/nsidc/usaon-vta-survey/tree/setup_sso

If someone got a new email or job would we be able to consolidate?

If someone got a new email or job would we be able to consolidate?

We chatted about this and decided this shouldn't be a concern until much farther down the line. For now, let them create a new account.


Support other subresources

Collect available subresources from the swagger definition
Try to handle subresources in a generic way (by having a common client code with subresource-specific modules created by the code generator)

Subresources in the schema:
pods/binding (#/definitions/io.k8s.api.core.v1.Binding) post
pods/eviction (#/definitions/io.k8s.api.policy.v1beta1.Eviction) post
pods/log (string) get
namespace/finalize (#/definitions/io.k8s.api.core.v1.Namespace) put
***/status (different type per resource) (patch, put, get)
***/scale (#/definitions/io.k8s.api.autoscaling.v1.Scale) (patch, put, get)
multiple resources have it, custom resources can have too
certificatesigningrequests/approval (#/definitions/io.k8s.api.certificates.v1.CertificateSigningRequest) (patch, put, get)
Based on that I am going to do the following implementation:

[ ] Keep the special status subresource handling as is, detecting automatically from the schema if a resource has it, and with what status type.
[ ] Collect subresource types from the schema identified by their name, data type and set of available actions. The classification phase should store for each resource the set of subresources, and also output the set of collected subresources from the whole schema.
[ ] For each such subresource, generate a client module similar to the ResourceStatus and it's wrappers. No type parameter needed, all the types are fixed from the schema. The set of operations filter the methods to generate. Must support: post, put and get. Patch support will be implemented separately (in #32)
[ ] For each resource when generating the client module, add the additional subresources to the layer like it is done with the status.
[ ] Support the Scale subresource for CRDs

Subresources in the schema:
pods/binding (#/definitions/io.k8s.api.core.v1.Binding) post
pods/eviction (#/definitions/io.k8s.api.policy.v1beta1.Eviction) post
pods/log (string) get
namespace/finalize (#/definitions/io.k8s.api.core.v1.Namespace) put
***/status (different type per resource) (patch, put, get)
***/scale (#/definitions/io.k8s.api.autoscaling.v1.Scale) (patch, put, get)
multiple resources have it, custom resources can have too
certificatesigningrequests/approval (#/definitions/io.k8s.api.certificates.v1.CertificateSigningRequest) (patch, put, get)
Based on that I am going to do the following implementation:

[ ] Keep the special status subresource handling as is, detecting automatically from the schema if a resource has it, and with what status type.
[ ] Collect subresource types from the schema identified by their name, data type and set of available actions. The classification phase should store for each resource the set of subresources, and also output the set of collected subresources from the whole schema.
[ ] For each such subresource, generate a client module similar to the ResourceStatus and it's wrappers. No type parameter needed, all the types are fixed from the schema. The set of operations filter the methods to generate. Must support: post, put and get. Patch support will be implemented separately (in #32)
[ ] For each resource when generating the client module, add the additional subresources to the layer like it is done with the status.
[ ] Support the Scale subresource for CRDs


Changing the transfer account of the split with the total amount set it to zero

If a transaction is edited and the transfer account of the split entry with the positive amount is changed, the amount of the transaction is set to zero.
Steps to reproduce:

Create a new transaction in Expenses:Education.
Enter a description and an amount.
Save the transaction.
Edit again the same transaction.
Open the split editor.
There will be two entries, one with negative amount and the other with a positive amount. For example -100 and 100.
Change the transfer account of the entry with the positive amount (100) to Expenses:Books.
Save the changes.
The split editor closes and the transaction account appears with 0 as its amount.

Some observations:

The transactions disappears from Expenses:Education and appears in Expenses:Book, just as expected.
The amount of the transaction and its splits are set to 0.
If after step 2, the split editor is opened instead, there's only the split with the positive amount and its transfer account can't be changed (the combo box is disabled).

Thanks for the comprehensive report :+1:


issue131 Describe security requirements of the JAX-RS endpoint genera…

…ted by the Proxy participant
resolves #131
Signed-off-by: xstefank<EMAIL_ADDRESS>

@rdebusscher PR updated, thanks for the review.

So this one looks complete now so I am merging


Internal Server error

Hey,
I just updated the project.
When I start the project (docker-compise up), all the containers launch correctly but I can't see the map, I have an error 500

Thanks for your help

Look at server logs first.

/data/expire_tiles/???????; No such file or directory

This is not an issue. You does not have expire_tiles until your update the OSM data and effectively got tiles to expire.
Check the logs of the 4 components: makina-maps_nginx_1, makina-maps_tileserver-gl_1, openmaptiles_postserve_1, openmaptiles_postgres_1

sudo docker logs makina-maps_nginx_1
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 19501 100 19501 0 0 1190k 0 --:--:-- --:--:-- --:--:-- 1190k EXPIRE SOURCE: bright v3 Setting up watches. Beware: since -r was given, this may take a while! Watches established. find: /data/expire_tiles/????????: No such file or directory
sudo docker logs makina-maps_tileserver-gl_1
INFO:tornado.access:200 GET / (<IP_ADDRESS>) 4.85ms INFO:tornado.access:200 GET / (<IP_ADDRESS>) 0.78ms
/usr/local/lib/python3.8/site-packages/asyncpg/connection.py:1329: InterfaceWarning: <asyncpg.connection.Connection object at 0x7fd4a7ac75f0> is being released to the pool but has 1 active log listener warnings.warn(w) ERROR:tornado.application:Uncaught exception GET /tiles/3/4/2.pbf (<IP_ADDRESS>) HTTPServerRequest(protocol='http', host='localhost:8080', method='GET', uri='/tiles/3/4/2.pbf', version='HTTP/1.0', remote_ip='<IP_ADDRESS>') Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/tornado/web.py", line 1699, in _execute result = await result File "/usr/src/app/openmaptiles/postserve.py", line 81, in get tile = await connection.fetchval(query, zoom, x, y) File "/usr/local/lib/python3.8/site-packages/asyncpg/connection.py", line 439, in fetchval data = await self._execute(query, args, 1, timeout) File "/usr/local/lib/python3.8/site-packages/asyncpg/connection.py", line 1413, in _execute result, _ = await self.__execute( File "/usr/local/lib/python3.8/site-packages/asyncpg/connection.py", line 1422, in __execute return await self._do_execute(query, executor, timeout) File "/usr/local/lib/python3.8/site-packages/asyncpg/connection.py", line 1434, in _do_execute stmt = await self._get_statement(query, None) File "/usr/local/lib/python3.8/site-packages/asyncpg/connection.py", line 329, in _get_statement statement = await self._protocol.prepare(stmt_name, query, timeout) File "asyncpg/protocol/protocol.pyx", line 163, in prepare asyncpg.exceptions.UndefinedFunctionError: function st_asmvt(unknown, integer, unknown, record) does not exist HINT: No function matches the given name and argument types. You might need to add explicit type casts.
sudo docker logs openmaptiles_postgres_1
ERROR: canceling autovacuum task CONTEXT: automatic analyze of table "openmaptiles.public.osm_ocean_polygon_gen3" ERROR: canceling autovacuum task CONTEXT: automatic analyze of table "openmaptiles.public.osm_ocean_polygon_gen4" ERROR: canceling autovacuum task CONTEXT: automatic analyze of table "openmaptiles.public.osm_ocean_polygon_gen1

Th error is
function st_asmvt(unknown, integer, unknown, record) does not exist

This function is provided by postgis.

it's a postgis version problem?

it works if i replace
image: "openmaptiles/postgis:build-5.0-dev" =>  image: "openmaptiles/postgis:${TOOLS_VERSION}"
in docker-compose from openmaptiles

Ok. So it is an other issue linked to the remote change of the docker images.

I commit this change to have a working setup on master. But note the OSM update is not working for now with this docker changes.


PyTorch implementation of MQ-CNN and MQ-RNN

References:

https://arxiv.org/pdf/1711.11053.pdf
MXNet implementation (in my opinion this is a little too dispersive)

Milestones for this one:

[ ] Implementing core modules (with option for different encoders, but more compact than the MXNet one)
[ ] Implementing LightningModule to handle training: this should take care of the "forking" logic described in the paper
[ ] Estimator wrapper

Any updates on this?


UseCdn and ResourceDebugMode settings

Allow to set the UseCdn and ResourceDebugMode property in the General settings.

For the resource debug mode. the default should be Use Configuration and would use the current environment value (production/development)


Warn when INotifyPropertyChanged isn't implemented

Model tracking requires INotifyPropertyChanged, just like WPF/Avalonia. Unfortunately, the typical user probably has no experience with either of these and may not read far enough or attentively enough into the (TBD) documentation to even realize that this is a requirement.
One way the framework can smooth over this is to log a warning when it detects an input binding being bound to a property on a non-INPC object, which I think is a relatively straightforward change to the AttributeBindingFactory and/or ContextPropertyValueSource.
I'd log a warning containing the declaring type and property name, and ideally a doc link to the property binding doc/wiki page explaining why it's necessary and how to do it easily (using source generator).

Addendum: We probably only want to warn about each type/property once per game session, to avoid spamming useless errors in the case that the user really never intends for that value to change.
Perhaps it might also be good to be able to disable these warnings at various levels: in the view itself (through some markup extension), at the document level (doc comments?), at the context level (via an Attribute on the context type, or an explicit API call for third-party types) or even for the entire mod - that is, the calling mod, not the StardewUI Framework mod.

Decided to go in a slightly different direction with suppressions, and came up with a solution that I believe is a lot more elegant: one-time bindings using a : prefix.
These work across the board; any binding can be modified as a one-time binding and it will in fact only update one time. But the real advantage, aside from some tiny performance gains, is as a way of declaring "I meant to do that" with any non-INPC types, since one-time bindings will inherently skip the INPC warning.


Fix decorators2 to support export @decorator class A {}

Q
A

Bug fix?
yes

Breaking change?
no

New feature?
no

Deprecations?
no

Spec compliancy?
yes

Tests added/pass?
yes

Fixed tickets

License
MIT

export @decorator class A {}

I hope this is correct and should be parsable, but I guess it should.
Also added tests for the old decorators plugin, just to ensure it works there (works with different syntax though)

I agree that this should be supported. The current spec text supports it as well. Make sure to test decorated anonymous default class exports, which are specifically also supported. cc @wycats @bterlson


Build dependencies of dependents on Monorepo CI

Important fix. Issue discovered by failing jobs on #987

Merging without CI running because the changes on this PR won't be run by any of the checks. We need to improve that, btw :)


Load Error sheets_v4

Expected Behavior
Read sheets
Actual Behavior
require': cannot load such file -- google/apis/sheet_v4 (LoadError)
Steps to Reproduce the Problem

Specifications

Ruby version (ruby -v)
OS (Mac/Linux/Windows)

Can you post what the solution was, in case other folks run into this issue?


Add a DSL for build tasks

Purpose
To make it easier to manage the build tasks and process.   Contributors, forkers, and the build (CI) server will all run the same build script, with consistent repeatability with regards to building the project and nuget package.  Building in VS is not enough nowadays because it leads to "it works on my computer" builds.  By using a build script in addition to VS, you as the developer can mimic the build process that runs on any developers' computer and also the build server.
For contributors and forkers, it makes the experience of building the project easier and less cumbersome... you just run the build script.
Using a build DSL also abstracts away the joy and complexities of MSBuild XML configurations.
Popular DSL's for .NET:

Fake (https://fake.build/) an F# build task DSL.
Cake (http://cakebuild.net/) a C# build task DSL.

I have extensive experience using Fake, but I have no objections to using Cake (it's newer than Fake) because it's a C# build DSL.
Seeing that this project itself is written in C# I think it may be easier for future contributors to work on the build script, if necessary, if we picked Cake as the DSL for building the project.
If we picked Fake, then contributors would either have to know or be willing to learn F# in order to make changes to the build script.  It's easy to learn, but then again it's another barrier to contributing.


Fetch raw message from URL

Problem:
When using QR Code flow, it is sometimes impossible to fit all information into a QRCode.
Solution:
It should be possible to scan a QR Code that contains a URL that is pointing to a message. Something like this:
https://example-service.io/presentation/1234567

probably a good idea to include /ipfs/<hash> as a possible pointer to a message

probably a good idea to include /ipfs/<message hash> as a possible pointer to a message

@mirceanis let's add it as a separate feature in the future


Delete https://developer.mozilla.org/en-US/docs/Web/CSS/@media/light-level

https://developer.mozilla.org/en-US/docs/Web/CSS/@media/light-level  should be completely deleted. light-level was never implemented in any browser engines, and it has now been removed from the Media Queries spec:

https://drafts.csswg.org/mediaqueries-5/#changes-since-2020-07-15

Remove the light-level media feature as it is redundant with prefers-contrast and prefers-color-scheme; add examples of how these media features may be automatically inferred by the user agent based on the same factors light-level was expected to respond to.

https://github.com/w3c/csswg-drafts/commit/f5b663c27d5a2715239633f4916880563969d770
https://github.com/w3c/csswg-drafts/issues/5359

Raised https://github.com/mdn/browser-compat-data/pull/6706 for the corresponding BCD change

Thanks @sideshowbarker. I've deleted that page and all its translations.


[Bug]: binary is not support

Describe the bug
sql:
select * from `ops_process_definition` where `plan_id` = binary '0000000031098452' limit 0,1000

The same goes for hex
select the_key, the_value, gmt_modified, status, gmt_expired, status from trade_nonappend023 where the_key = x'01323038383632313935353434313832352d3136313831313030363030323437393433'

select * from foo where column_name = _binary'1111'


feat(InterviewHeader): add interview header

PR includes

[ ] Refactor
[ ] Feature

Related issues
Resolve #


How to find the DFU functional descriptor?

Hi, I want to find the DFU functional descriptor of the USB devices, but it seems that this descriptor wasn't defined in usb.util
# descriptor type
DESC_TYPE_DEVICE = 0x01
DESC_TYPE_CONFIG = 0x02
DESC_TYPE_STRING = 0x03
DESC_TYPE_INTERFACE = 0x04
DESC_TYPE_ENDPOINT = 0x05

You can always use pyusb to retrieve the descriptor.
What you need to do is to read the DFU Specification from USBIF.
https://usb.org/sites/default/files/DFU_1.1.pdf
Is this a question or an enhancement request?

Thanks for response.
But I don't know how to use pyusb to get this descriptor.
Could you show me a demo code?

Hi,
I'm sorry, but guiding you step by step is outside the scope of an issue/not something I can take on right now.
Start by reading the DFU spec (and specific parts of the USB spec that may come up) and try to code something based on our general Tutorial.  Also take a look at the FAQ for a couple of common problems.
After that, you should be able to find most answers to questions by searching our issues or code that depends on PyUSB.  In fact, there are many DFU tools out there, and one of them could already use PyUSB.

@mcuee
Ops, I assumed you wouldn't be able to help him in Python either... it that's not the case, please feel free to reopen.

No problem. I agree to close this issue, as it is a question which requires the OP to study first.


Bump golang support to 1.18, use newer linter

Signed-off-by: Tim Rozet<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 5 (100.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 74.906%

Files with Coverage Reduction
New Missed Lines
%

ovsdb/schema.go
1
87.24%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
4982

Relevant Lines:
6651

💛  - Coveralls

/lgtm


Mouse interaction discussion

We need to find a reliable way of handling mouse interaction that allows for no collision between element interaction.

For masking mouse events, element mouse press methods will have a boolean return, and once the InputContext encounters a false, it wont invoke any more mouse press methods.

Closing for now. I will reopen this when considering further improvements for mouse interaction.

I will work on implementing depth-constants for the elements, so the masking order is more efficient.


Lean theorem (export format) export and parsing

Use Lean's export format for serialization.
Import from lean's library (and other lean sources) after exporting to the export format.
Write to a  .hlean file to use lean and its tools.
Write with an underscore to use the elaboration engine.

Very useful info at https://github.com/banacorn/agda-mode/wiki/Conversations-between-Agda-&-agda-mode

Very useful info at https://github.com/banacorn/agda-mode/wiki/Conversations-between-Agda-&-agda-mode

Have created an export to any entity having an expression language. To target lean we need some inductive types and corresponding constructors. In the library, we have:

file datatypes.hlean
pair type is sigma
inclusions are sigma.intro_left and sigma.intro_right
projections are sigma.pr1 and sigma.pr2

Have created an export to any entity having an expression language. To target lean we need some inductive types and corresponding constructors. In the library, we have:

File: datatypes.hlean
dependent pair type is sigma
projections are sigma.pr1 and sigma.pr2
also have a simpler product type: type is prod, with projections prod.pr1 and prod.pr2
the sum type is sum, with inclusions sum.inl and sum.inr
we also have the inductive nat (in the same file)

Need to change to the new, cleaner inductive definitions.

The differences between lean2 standard and hott libraries are mostly names and well documented. So one should be able to import both, using the names in HoTT.

The differences between lean2 standard and hott libraries are mostly names and well documented. So one should be able to import both, using the names in HoTT.

TODO:

Handle intro rules for inductive types.
Follow deBruijn indices for variables to get types.

Intro rules are coded (not checked). What is needed is to resolve deBruijn indices, passing a vector to getExpr and Expr.get

Written in 2533a

Use trepplein https://github.com/gebner/trepplein for API and parsing.

trepplein uses lean3, which so far has a limited library

A sample indexed inductive definition in lean
open nat
namespace hide

inductive vector (A : Type) : nat → Type :=
| nil  : vector A zero
| cons   : Π n, A → vector A n → vector A (succ n)

definition append (A: Type) (n m : nat) (s : vector A n) (t: vector A m) : vector A (nat.add m n) :=
(vector.rec t (λ k x l u, vector.cons(nat.add(m)(k))(x)(u))) s

check append

end hide

Almost everything is inferred  in vector.rec - the parameter A, the type family, whether this is really induction or recursion etc, based on the definition data.

To deduce the type family:

We define P: X -> Type recursively, but actually a cases definition (i.e., for each introduction rule but independent of the values of P on arguments).
We use the data phi for recursion for each introduction rule, recursively on the ConstructorSeq

if the rule is a constant, take the type of phi.
if it is a simple extension A -> ..., take a variable a : A, solve for phi(a) to get and return a :-> Q
for a non-trivial extension, say X -> ..., generate a variable x : X and another dummy one z by matching phi(x) with a function and taking a variable in the domain; solve for phi(x)(z) to get Q; return x :-> (A : Type) :-> Q

Check if this is a constant function (ideally while generating).
Invoke the getExst methods of (indexed) inductive types.

Do not infer from recursion data

this is impossible in general.
lean only allows definitions where we can infer types.
the type is specified in definitions.

this can be partially propagated to terms
we use this where available
one case where propagation fails is the type of f(a) does not determine that of f

Extending the previous vector example
open nat
namespace hide

inductive vector (A : Type) : nat → Type :=
| nil  : vector A zero
| cons   : Π n, A → vector A n → vector A (succ n)

definition append (A: Type) (n : nat) (s : vector A n) (m: nat) (t: vector A m) : vector A (nat.add m n) :=
(vector.rec t (λ k x l u, vector.cons(nat.add(m)(k))(x)(u))) s

check append

constant A: Type

constant m : nat

constant t : vector A m

check @vector.rec

definition core : Π n : nat, vector A n → vector A (nat.add m n) :=
λ n,
vector.rec t (λ k x l u, vector.cons(nat.add(m)(k))(x)(u))

check core /- core : Π n, vector A n → vector A (nat.add m n) -/

end hide

At least in the above case, hopefully in general,

given type of a recursive/inductive function type, deduce:

the inductive type
the codomain or (indexed) dependent type family.

the parameters are obtained from the inductive type, and can be used to obtain the ConstructorSeq.
the codomain or family can be used in recE or indexE.
finally fold with the arguments.

recursive definitions seems to be ignored, may be an issue with the way eval was used.
should have most definitions in a Name => Term map.

Several bugs fixed. The problem seems to be cases of _.rec with the definition type unknown due to weakness of inference.

The problem is likely to be in type inference.

the domain of recursion functions cannot be unified because it is very complicated.
the minimal example, based on the plift type is failing to parse as follows:

@ exp
res58: Expr = Lam(
  Binding(Str(, "\u03b1"), Sort(Param(Str(, "u"))), Default),
  Lam(
    Binding(Str(, "c"), App(Const(Str(, "plift"), Vector(Param(Str(, "u")))), Var(0)), Default),
    App(
      App(
        App(
          App(
            Const(Str(Str(, "plift"), "rec"), Vector(Param(Str(, "u")), Param(Str(, "u")))),
            Var(1)
          ),
          Lam(
            Binding(
              Str(, "c"),
              App(Const(Str(, "plift"), Vector(Param(Str(, "u")))), Var(1)),
              Default
            ),
            Var(2)
          )
        ),
        Lam(Binding(Str(, "down"), Var(1), Default), Var(0))
      ),
      Var(0)
    )
  )
)

@ typOpt
res59: Option[Typ[Term]] = Some(∏(α : 𝒰 ){ (plift(α) → α) })

@ pn.parse(exp, typOpt)
got argsPair Vector((#1,None)) while parsing @plift.rec.{u u} #1
 for inductive type plift($afyn), length 1, type: None
these parsed to Vector(Some(α : 𝒰 _0))
got argsPair Vector((#1,None)) while parsing @plift.rec.{u u} #1
 for inductive type plift($afyn), length 1, type: None
these parsed to Vector(Some(α : 𝒰 _0))
got argsPair Vector((#1,None)) while parsing @plift.rec.{u u} #1
 for inductive type plift($afyn), length 1, type: None
these parsed to Vector(Some(α : 𝒰 _0))
got argsPair Vector((#1,None)) while parsing @plift.rec.{u u} #1
 for inductive type plift($afyn), length 1, type: None
these parsed to Vector(Some(α : 𝒰 _0))
got argsPair Vector((#1,None)) while parsing @plift.rec.{u u} #1
 for inductive type plift($afyn), length 1, type: None
these parsed to Vector(Some(α : 𝒰 _0))
got argsPair Vector((#1,None)) while parsing @plift.rec.{u u} #1
 for inductive type plift($afyn), length 1, type: None
these parsed to Vector(Some(α : 𝒰 _0))
got argsPair Vector((#1,None)) while parsing @plift.rec.{u u} #1
 for inductive type plift($afyn), length 1, type: None
these parsed to Vector(Some(α : 𝒰 _0))
got argsPair Vector((#1,Some(((plift : ((𝒰 _0) → (𝒰 _0))) (α : 𝒰 _0) : 𝒰 _0) → (𝒰 _0)))) while parsing @plift.rec.{u u} #1
 for inductive type plift($afyn), length 1, type: Some((((plift : ((𝒰 _0) → (𝒰 _0))) (α : 𝒰 _0) : 𝒰 _0) → (𝒰 _0)) → (((α : 𝒰 _0) → (α : 𝒰 _0)) → (((plift : ((𝒰 _0) → (𝒰 _0))) (α : 𝒰 _0) : 𝒰 _0) → (α : 𝒰 _0))))
these parsed to Vector(Some(α : 𝒰 _0))
failed to unify plift($afyn) and (plift(α) → 𝒰 )
res61: Option[Term] = None

based on the inductive type
@ p3.toTermIndModOpt(pld).get
res62: TermIndMod = SimpleIndMod(Str(, "plift"), plift($cvbi), Vector(plift.up), 1)

while defining plift.down

Looks as if the export format has:

parameters applied
the type family specified

Recursion for not works, but plift is still troublesome:
When trying to fold, we have the following mismatch. There may be `simplifications' to apply
@ arg.typ
res34: Typ[U] = ∏(down : α){ C(plift.up(α)(down)) }

@ domain(fn)
res36: Typ[Term] = ∏($gufw : α){ C((plift.up : (α : 𝒰 _0 ~> (α : 𝒰 _0) → ((plift : ((𝒰 _0) → (𝒰 _0))) (α : 𝒰 _0) : 𝒰 _0))) ($gpef : 𝒰 _0)($gufw)) }

This is probably a problem with interpreting deBruijn indices

For replication, here is the code giving an error
import trepplein._
import interface._, LeanInterface._
val mods = getMods("data/group.export")
val pg0 = LeanToTerm.fromMods(mods.take(4))
val d = mods(4).asInstanceOf[DefMod].defn
pg0.parse(d.value, None)
val fails = LeanToTerm.appFailure.toSet
val min = fails.head
val parser = min._5
val fn = parser.parse(min._2, None).get
val arg = parser.parse(min._3, None).get

It is clearly the case that while parsing the expression for fn, Var(3) is misinterpreted.

Clearly the bug is in the induction function after replacement
New simple inductive type: plift(α)
type argument #2
 parsed as Some(C)
 with type Some((plift(α) → 𝒰 ))
induction function has type
(∏($ageo : α){
  C((plift.up : (α : 𝒰 _0 ~> (α : 𝒰 _0) → (
(plift : ((𝒰 _0) → (𝒰 _0))) (α : 𝒰 _0) : 𝒰 _0))
) ($afyn : 𝒰 _0)($ageo)) } → ∏($agce : plift(α)){ C($agce) })

the term $afyn is meaningless, and must be an escaped term

Several bugs, including  the ones represented above, fixed in 09bc07f2dd155.
Still crashes, but probably because of lean using _proof irrelevance' for equality.

equality is defined as having two parameters (type and starting point) and one index: the endpoint.
However, for fixed  A and a: A, the family for induction has type A -> Type
We expect type (b : A) -> eq(a)(b) -> Type, but if eq(a)(b) is  a proposition, then lean's form is fully  general
To fix this, we allow lifting  of iterated functions  with  respect to type families.

The propositions are represented by having type Sort(0) in lean export, and eq(A)(a) is indeed a proposition.

Should improve performance in the recursive case:

Single match, identifying type for an iterated Ap(_, _) starting with a RecName.
Call a method with these arguments in each (indexed) inductive type object.
Arguments are folded with apply.
First, step: refactor the method to handle an argument list.

Seems to work fine, but very slow: fills up memory, especially while parsing some terms.

Somewhat optimized, still slow. Should (re)open more specific issues if needed.


[battery] Moved battery to subdir

Description
In this pr, I have moved everything from battery to battery/battery.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Hey @ditman kindly take a look at this one :)


Implement TAP (https://testanything.org/)

Fixes #16.

Thanks for this!
I think there is an issue with stdout not being flushed before forking. When I pipe the output, the plan (1..n) repeats itself for each test, making the output invalid.
> ./tests/main --tap # Works as expected
1..5
ok 1 - ast/new
ok 2 - quad/new
ok 3 - quad/list
ok 4 - symbol/memory
ok 5 - symbol/same_name
> ./tests/main --tap | cat -
1..5
ok 1 - ast/new
1..5
ok 2 - quad/new
1..5
ok 3 - quad/list
1..5
ok 4 - symbol/memory
1..5
ok 5 - symbol/same_name
1..5

Not sure if it is a macOS specific issue, but here's a patch that solves it:
diff --git a/include/acutest.h b/include/acutest.h
index dba6370..5cf26b8 100644
--- a/include/acutest.h
+++ b/include/acutest.h
@@ -1162,8 +1162,10 @@ main(int argc, char** argv)
         /* TAP harness should provide some summary. */
         test_no_summary__ = 1;

-        if(!test_worker__)
+        if(!test_worker__) {
             printf("1..%d\n", (int) test_count__);
+            fflush(stdout);
+        }
     }

     /* Run the tests */

Added the fflush() just before fork(), it's imho more robust.
Thanks for the testing.


CI tracking issue

We should get some CI going. I think the TODO looks something like the below. Would love some input as I haven't done a ton of CI setup before.

[ ] Initial configuration: builds the Nix flake and outputs #33
[ ] After tests are added, run tests as well
[ ] self-host Github runner ? maybe with this

Sounds good. I was thinking of having a linter job would be lowest hanging fruit for the start. just pylint and/or flake8, the only real work is figuring out what errors we want to ignore and then fix the rest. I had started that process a few weeks ago and I will open a PR for that asap. I guess I can tag it on to the initial config PR.

i've been using ruff but I don't have any opinion on the best tool. Are you doing one big linting / formatting pass on the project? figure that's best as its own PR, yea.

I've never used ruff, we've been using pylint and flake8 in core so that's what I am used to.
I've opened #35 as a start, fixing some of the more interesting errors and marking a few others as ignored for now. We can fix these as we go along but most importantly this should be good to detect some stuff like unused variables and actual errors in code path we might have forgotten to test.


fix: add missing changelog entries for v1.0.0-dev.4

Merging this as it's only a changelog update!


Incorrect TxLevel from "getTxLevelByPercentage"

The function NurUtils.getTxLevelByPercentage(nurApi, 45) is returning an invalid TxLevel after  35%. Using this function gives values from 0-30, while the Tx_Levels goes from 0-19.
Here is an image to show the Tx_Level when the percentage is at 0%.

This is caused by the "txSteps" returning 30, while the txLevel goes till 19 (only having 20 steps).

If I just use the current function as is and set the TxLevel, I get this error; Indicating to an invalid txLevel.
Percentage used "0%"

Hi @Ashp116,
I’m having trouble replicating the issue you're experiencing. Could you please let me know which device you have tested this on? It seems that your device is recognizing 20 transmission steps only, although 'txSteps' says 30.
Debug with Nordic ID HH 85:

Thank you!

I have fixed the second error that occurred. The new JAR library can be found here: v1.1 release.
If you are using this repository, you can fetch and pull to get the latest library.

Hi @Buryyy,
Thank you for the fix! I updated NurUtils and it seems it not give me any errors.


N1 missing topics

Asking about "tea" and "animals" gives a generic non-response from Carol.  But they're bolded subjects within the scene.

Aha, it appears that {tea, animals, snortles, elephant} are example of things that are bolded, can be examined but have no ask/tell response.  Confusing to Frances -- she expects bolded things to be askable.

No, bolded should be askable...investigating

The problem in both cases was that grammar was expressed using the slash notation, but included spaces. fixed.


Ensure that Lines-Areas-Labels-Base-Template.stylx is updated to reflect "Scale Proportionally" Bug

Because our workflow in updating the Mil2525D stylx starts with editing a [Lines-Areas-Labels Base template] (https://github.com/Esri/military-features-data/blob/v.next/data/mil2525d/core_data/stylxfiles/mil2525d-lines-areas-labels-base-template.stylx) and then merging it with a Points-Only Stylx to create a new Mil2525D.stylx, my concern is that the .stylx files we currently have in our repository do not reflect the changes that @jeconley @mbriat made to the Mil2525D.stylx right before the Pro 1.2 install.
First, I'll replace the Mil2525D.stylx in our repo with the one included in the current install of Pro 1.2 (Builds 4846+)
Second, I'm wondering if the programmatic changes made to the Mil2525D.stylx need to be done for Lines-Areas-Labels-Base-Template. If we don't do that, I'm concerned that our future edits won't have the "Scale Proportionally" issue fixed when we hand it off to the Pro team.
@csmoore Feel free to clarify the concerns from our end, I'm just trying to document what happened to the Mil2525D stylx and how it might impact our workflow to make edits in the future.

We can run the ScaleProportionanlly update anytime if needed

Now is probably as good a time as any while we are thinking about, and before we forget. @mbriat can you run this against that stylx ( https://github.com/Esri/military-features-data/blob/v.next/data/mil2525d/core_data/stylxfiles/mil2525d-lines-areas-labels-base-template.stylx ) when you have a chance? Thanks

Updated version added to \marcb\Shared\mil2525d

Many thanks - we'll give this updated version a quick check-out & add it to GitHub

I added mil2525c + app6b to this issue since these styles will likely need updated also. @mbriat - sorry I didn't realize this yesterday - can we get you to run your "ScaleProportionanlly" utility against these also:
https://github.com/Esri/military-features-data/blob/v.next/data/mil2525c/stylxfiles/mil2525c.stylx
https://github.com/Esri/military-features-data/blob/v.next/data/app6b/stylxfiles/app6b.stylx

We installed an extension to the Pro SDK so that this can be done with an Add-in Deepinder wrote. I'd prefer to try this approach as you could also get the code in case you need to do more of that kind of work.

That would be great - we'd probably add right to this repo

This is assigned to me now to update mil2525c+app6b with this change (waiting to get access to the new location of the daily Pro SDK build so I can run the update plugin provided)

@Dbarnes1 - I believe this issue is addressed. It probably wasn't clear, but I believe I addressed this issue in #186 and #188 - you may want to double check the latest mil2525d-lines-areas-labels-base-template.stylx file just to make sure. I think I updated Asana but didn't update this issue.

@csmoore verified and Closing.


Disable crashkernel in grub config to prevent crashkernel being loade…

Disable crashkernel in grub config to prevent crashkernel being loaded after kernel panics.  If the crashkernel is loaded, it creates an outage, and we don't want that.

:+1:


Weights file can't be Path

See this line. Should be Union[str, Path].
https://github.com/RTIInternational/teehr/blob/33137f0676d059d5ef4a2f8d6590a3171661e512/src/teehr/loading/nwm/nwm_grids.py#L30

This was addressed in PR #153


space_touched class

concrete objects for space_touched
with transition to graphical display - we need to record space_touch as a line. we might want to pick a better name... like move_path?

We will not need this class when we move to graphical display


Fix symlink copying for deb init scripts

After 027f4fdca678ae955db6f115d6af15d532f6cf4b the paths to the symlinks under hack/make/.build-deb were broken.
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>

LGTM

LGTM

LGTM, all green, merging!


Integration Test - Release - 2019/06/20 23:05:06

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest2 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@PRMergerTest2 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Arbitrary flags to the send syscall

I noticed that it seems like the length argument in AsyncSocket::write will end up as arbitrary flags in the send syscall, unless I'm misunderstanding something:
AsyncSocket.h#L19 -> socket.c#L150 -> bsd.c#L190

Yeah length should probably be cut to 1 or 0.
msg_more * MSG_MORE only makes sense for 1 or 0


Add Portuguese translations for general strings

This issue is to add Portuguese translations for the existing strings found in https://github.com/devadvance/terminalcheatsheet/blob/staging/_data/translations.yml
Use pt (the locale code for Portuguese) as the key for the strings.

Hey! I can handle this one. Do you accept it?

@mailysantos sure! Assigned this to you.

Fixed by @mailysantos in #101!


GUACAMOLE-310: Fix clipboard handling of newlines.

As reported in GUACAMOLE-310, newlines are being stripped from clipboard data copied using the W3C Clipboard API. This makes clipboard use cumbersome for users where the browser provides direct integration of the clipboard, such as IE11 or Chrome with the Clipboard Permission Manager extension.
This is due to newlines being stripped from textContent of a <div> despite white-space: pre being set. As this did indeed work before, this seems to be a recent browser behavior change. By reverting back to using a <textarea> the clipboard event target, newlines work as expected.

Looks good to me.  I can merge it to master here, shortly.

Thanks, @necouchman!


OLS-1074: Azure identity as Konflux package

Description
Azure identity as Konflux package
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[ ] CI configuration change
[x] Konflux configuration change

Related Tickets & Documents

Related Issue #OLS-1074

/test unit

/test verify

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.59%. Comparing base (e77efdf) to head (324a466).
Report is 14 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1903       +/-   ##
===========================================
- Coverage   93.47%   73.59%   -19.88%
===========================================
  Files          64       63        -1
  Lines        2941     2795      -146
===========================================
- Hits         2749     2057      -692
- Misses        192      738      +546

see 34 files with indirect coverage changes

/test unit

/lgtm

/approve
/override "Red Hat Konflux / lightspeed-service-on-pull-request"


Automated cherry pick of #2406: - snapshot support custom snapshot policy

Cherry pick of #2406 on release/2.11.
#2406: - snapshot support custom snapshot policy

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@fb45719). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #2444   +/-   ##
==============================================
  Coverage                ?   7.06%
==============================================
  Files                   ?     454
  Lines                   ?   71696
  Branches                ?       0
==============================================
  Hits                    ?    5064
  Misses                  ?   66214
  Partials                ?     418

Flag
Coverage Δ

#aFlag
7.06% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/regiondrivers.go
20% <ø> (ø)

pkg/compute/models/disks.go
0.74% <0%> (ø)

pkg/compute/models/snapshotpolicydisks.go
1.58% <0%> (ø)

pkg/compute/models/snapshots.go
1.88% <0%> (ø)

pkg/compute/models/snapshotpolicy.go
3.43% <0%> (ø)

Continue to review full report at Codecov.

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

/lgtm

/approve


Writing to Firestore directly in the middle of a transaction updateFunction causes a deadlock/hang

I ran into this code mistake I made recently, and I think it would be nice if the API could help catch this issue.
Steps to reproduce:
Try writing to a document directly while in a transaction.
await db.runTransaction(async t => {
  const docRef = db.collection('cities').doc('Toronto');
  await docRef.set(...);
});

While of course, this is a code issue caused by the programmer, it is particularly frustrating to debug as it seems to cause a deadlock/unfulfilled promise. Possibly the API could help catch this issue by marking the stack and throwing an error (maybe only in dev?).

Hi @mmmulani ,
Could you please be more specific of which problem you are running into and what would you expected SDK behaviour be like? Because set() can be used in transaction.

oh sorry, I cleaned up my example but from what I tested, this will cause your Node server to just hang:
await db.runTransaction(async t => {
  const docRef = db.collection('cities').doc('Toronto');
  await docRef.set(...);
});

while the correct code to write is:
await db.runTransaction(async t => {
  const docRef = db.collection('cities').doc('Toronto');
  t.set(docRef, ...);
});

my ideal SDK behaviour would be that the Cloud Firestore API uses something like AsyncLocalStorage to mark when a promise/thread is inside a transaction, and warns you if you use an api like docRef.set() or docRef.get() manually while you are still in the scope of the transaction.

Hi @mmmulani ,
I run the code snippet below but the code returns successfully. Can you provide a minimal repo app?
await db.runTransaction(async t => {
  const docRef = db.collection('cities').doc('Toronto');
  await docRef.set(...);
});


Trigger select onChange

Hey there!
Thanks for your PR! Events support is definitely must have and planned, so thanks for help!
But there are few things which needs to be still done, before accepting your PR:

More events - I think there should be more events. Do you have some suggestions?
Prefix - the event's name should be prefixed to prevent conflicts (I would suggest prefix "sp-")
Documentation - the events have to be documented
Tests - tests are still not pushed to master branch, but I would like to finish basic tests and push them in to master this week

Would you like to incorporate these points? Otherwise I will work on it myself this or next week.

Hello,
I will not have enough time on these in such short period so looking forward for your changes.
Good luck!

I see, no problem!
Do you have some suggestion about what events should be supported? I am currently not completely sure for what kind of events I should aim for.
So far only one which is sure is the change event you proposed, then I was thinking about open/close events for the dropdown menu, but now I am not sure if it will be needed...

Hey!
I think you should concentrate on all select input default events at first.
Then move on with custom ones (on close, on open, on pick).
I would really be glad to help you, however, I will be busy for about a
month, however, later I can help you with my PR's.
Let's keep in touch!
P. S. Do you have full-time working position and on what programming
languages do you work? Maybe I can offer some freelance projects depending
on your experience and knowledge.
2016-04-27 10:43 GMT+03:00 Adam Uhlíř<EMAIL_ADDRESS>
I see, no problem!
Do you have some suggestion about what events should be supported? I am
currently not completely sure for what kind of events I should aim for.
So far only one which is sure is the change event you proposed, then I
was thinking about open/close events for the dropdown menu, but now I am
not sure if it will be needed...
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/AuHau/select-picker/pull/4#issuecomment-214996058

Hey there again!
that sounds reasonable! I will have look on it.
No problem, I am happy that I can at least consult things with somebody :-)
Currently I am studying, so no - no full-time work. I am working as front dev on one project as freelancer, but nothing too big. I have experiences both in backend and frontend, but more prefer to work on backend. More about me, languages I am working with and my references here: http://adam-uhlir.me/
But now during the summer I won't have much free time, but than later on during autumn I would be interested in some work if you would be interested in cooperation with me!
Take care!


Sidebar submenu

This pull request will solve the sidebar issues:

Fix the design of arrow in bottom of sidebar.
Now the submenu can be opened when the sidebar is minimized.
When sidebar is minimized, we record this status in localStorage.

That have some issues to solve, but will not be developed now:

Tooltip in options of menu
When the sidebar is minimized, when we hover the links, should be show a tooltip showing the name of item.

When we open the submenu in screens that have small height, the script need to move the submenu container.

I discovered some issues in this PR... Please, wait to accept.

Good to analyse.


fix: setTorrent typo

should be sending torrent-set as method

:tada: This PR is included in version 1.6.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Environment variable not found on latest alpha release

OS: MacOS
Prisma Version<EMAIL_ADDRESS>binary version: 3e74ccae138e0c7330c1d8f2a67fb7a234d220e8
When I'm running a prisma2 generate I get this error:
Error: Schema parsing
error: Environment variable not found: DATABASE_URL.
  -->  schema.prisma:3
   |
 2 |   provider = "postgresql"
 3 |   url      = env("DATABASE_URL")
   |

DATABASE_URL is present inside .env file.

Thanks for reporting @impowski!
This is a breaking change, we intentionally introduced in alpha.
https://github.com/prisma/prisma2/issues/1519
So please move the .env file into the ./prisma folder, then it should work again.


Add disk fields to cs submit

Changes proposed in this PR

Add disk request, limit, and type to cs submit

Why are we making these changes?

Allow users to request disk via cs submit

Will merge when green


Fix #1658: Fix constant-folding of classOf[T] === classOf[T].

Review by @nicolasstucki

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/1688/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2187/
Test PASSed.

Thats all.

LGTM


Make compatible with Tensorflow version 1.0 and beyond

I know this repository is approximately two years old but I needed to run this code for my own research. Had to make some minor changes for TensorFlow v1.0+ compatibility. Although an "official" PhasedLSTMCell now lives in tf.contrib, maybe some people are still interested in running this somewhat easier to read code. Therefore this pull request to make the code compatible with the latest version of TensorFlow again (tested on version 1.10, the current release).

Thanks @tomrunia going to have a look at this :)


FIX: daal4py sycl examples

Description
Please include a summary of the change. For large or complex changes please include enough information to introduce your change and explain motivation for it.
Changes proposed in this pull request:

@samir-nasibli  @Alexsandruss  - do we need this PR?

/intelci: run

/intelci: run


⚠ Bofrost.de has degraded performance

In 66ceb71, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1810 ms

Resolved: Bofrost.de performance has improved in 6975b8e after 51 minutes.


no self on EventDispatcher

I tried to use touch.grab(self) in method off an EventDispatcher, to get updates about this touches (interaction started by a widget, but managed by another EventDispatcher), i get a crash at dispatch time.
I think either i should get an error when i grab the touch, or the dispatching should happen correctly. Last time i had this issue a discussion ensued about various possible solutions:

moving __self__ to EventDispatcher
make class_instance try weakref.ref(class_instance) if it cannot find __self__
get class_instance.proxy_ref and only then create a new ref

Opinions/solutions welcome :)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@tshirtman I know it's an old thread, but could you perhaps paste some snippet if the issue still persists, please? If not for the fix, then to create a test/docs.

Not sure what exactly i wanted to do, but here is a simple (and quite artificial) example showing the issue:
from kivy.app import App
from kivy.lang import Builder

KV = '''
Widget:
    on_touch_down: app.manage_touch(args[1])
'''

class TouchGraber(App):
    def build(self):
        return Builder.load_string(KV)

    def manage_touch(self, touch):
        touch.grab(self)

    def on_touch_move(self, touch):
        if touch.grab_current is self:
            print("managed this touch")
        else:
            print("lolwhat?")

    def on_touch_up(self, touch):
        if touch.grab_current is self:
            print("ok, ungrabbing")
            touch.ungrab(self)
        else:
            print("seriously, wtf?")

if __name__ == '__main__':
    TouchGraber().run()

and here is the output
[INFO   ] [Logger      ] Record log in /home/gabriel/.kivy/logs/kivy_17-10-09_0.txt
[INFO   ] [Kivy        ] v1.10.1.dev0, git-4b77ede, 20170807
[INFO   ] [Python      ] v2.7.13 (default, Jan 19 2017, 14:48:08)
[GCC 6.3.0 20170118]
[INFO   ] [Factory     ] 194 symbols loaded
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_gif (img_pil, img_ffpyplayer ignored)
[INFO   ] [OSC         ] using <multiprocessing> for socket
[INFO   ] [Window      ] Provider: sdl2(['window_egl_rpi'] ignored)
[INFO   ] [GL          ] Using the "OpenGL" graphics system
[INFO   ] [GL          ] Backend used <gl>
[INFO   ] [GL          ] OpenGL version <3.0 Mesa 17.0.7>
[INFO   ] [GL          ] OpenGL vendor <Intel Open Source Technology Center>
[INFO   ] [GL          ] OpenGL renderer <Mesa DRI Intel(R) HD Graphics 620 (Kabylake GT2) >
[INFO   ] [GL          ] OpenGL parsed version: 3, 0
[INFO   ] [GL          ] Shading version <1.30>
[INFO   ] [GL          ] Texture max size <16384>
[INFO   ] [GL          ] Texture max units <32>
[INFO   ] [Window      ] auto add sdl2 input provider
[INFO   ] [Window      ] virtual keyboard not allowed, single mode, not docked
[INFO   ] [Base        ] Start application main loop
[INFO   ] [Base        ] Leaving application in progress...
 Traceback (most recent call last):
   File "test_grap.py", line 33, in <module>
     TouchGraber().run()
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/app.py", line 827, in run
     runTouchApp()
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/base.py", line 502, in runTouchApp
     EventLoop.window.mainloop()
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/core/window/window_sdl2.py", line 660, in mainloop
     self._mainloop()
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/core/window/window_sdl2.py", line 405, in _mainloop
     EventLoop.idle()
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/base.py", line 340, in idle
     self.dispatch_input()
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/base.py", line 325, in dispatch_input
     post_dispatch_input(*pop(0))
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/base.py", line 231, in post_dispatch_input
     listener.dispatch('on_motion', etype, me)
   File "kivy/_event.pyx", line 707, in kivy._event.EventDispatcher.dispatch (/tmp/pip-fYYBEy-build/kivy/_event.c:8191)
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/core/window/__init__.py", line 1189, in on_motion
     self.dispatch('on_touch_down', me)
   File "kivy/_event.pyx", line 707, in kivy._event.EventDispatcher.dispatch (/tmp/pip-fYYBEy-build/kivy/_event.c:8191)
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/core/window/__init__.py", line 1205, in on_touch_down
     if w.dispatch('on_touch_down', touch):
   File "kivy/_event.pyx", line 703, in kivy._event.EventDispatcher.dispatch (/tmp/pip-fYYBEy-build/kivy/_event.c:8146)
   File "kivy/_event.pyx", line 1214, in kivy._event.EventObservers.dispatch (/tmp/pip-fYYBEy-build/kivy/_event.c:14035)
   File "kivy/_event.pyx", line 1098, in kivy._event.EventObservers._dispatch (/tmp/pip-fYYBEy-build/kivy/_event.c:12816)
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/lang/builder.py", line 64, in custom_callback
     exec(__kvlang__.co_value, idmap)
   File "<string>", line 3, in <module>
   File "test_grap.py", line 16, in manage_touch
     touch.grab(self)
   File "/home/gabriel/.virtualenvs/kivy/local/lib/python2.7/site-packages/kivy/input/motionevent.py", line 330, in grab
     class_instance = weakref.ref(class_instance.__self__)
 AttributeError: 'TouchGraber' object has no attribute '__self__'

The easiest solution is probably to tighten the requirements on MotionEvent.grab parameter, considering this doesn't make much sense, but i think there may be legitimate use cases for this, if you want for example to delegate touches from a few widgets to a common controller, which would use properties to communicate it's updated state to widgets or other parts of the system.

Seems solved by https://github.com/kivy/kivy/pull/6448 by moving self to EventDispatcher.


Support for RHODS brew configuration

Adding RHODS brew configuration to install_addon flow

/verified

/verified cancel

/verified

@omrirh you need to cherrypick https://github.com/RedHatQE/openshift-python-utilities/pull/193 before this one can be marked as verified and merged

/verified cancel

/verified


Validate init kwargs to ScipyOdeSimulator

Previously, unrecognised kwargs would be silently ignored. Now a
ValueError is raised if they are not recognised.

Coverage increased (+0.8%) to 79.2% when pulling 2e4ecabf705049a37b1f47b8490ebb9eeddfe8df on alubbock:scipyode_kwargs into<PHONE_NUMBER>6b6df74872f1ebf94a1ef148775a63 on pysb:master.


DUPLO-9210 neglect tags created at backend new DUBPLO_CUSTOM_TAGS

DUPLO-9210, DUPLO-9337, DUPLO-9336 - time stream tags

Task linked: DUPLO-9210 Timestream: aws tag manager support tags for timestream tables

Task linked: DUPLO-7734 Provided Tags are not attached to Timestream DB and Table

Task linked: DUPLO-9336 Timestream UI: Added tags should be shown in db/table json details

Task linked: DUPLO-9337 Timestream TF: Updating tags gives table already exists error

same comment: it looks like we wrote a new method to deal with this logic instead of leveraging existing logic

as talked in today's call,  split method into smaller  ones.


Enhancement: Data Accelerator Release Candidate: PostgreSQL

Goal-State/What/Result

Why/Purpose

By When

Issue/Spec written and reviewed: Target Date
Done-Done: Target Date
Done-Done

[x] Principles Driven
[x] The Algorithm
[x] PM/Design Review
[x] DX/UX Review
[x] Threat Model / Security Review
[ ] Tests
[ ] Performance / Benchmarks
[ ] Documentation
[ ] Samples/Quickstarts/Tutorials
[ ] Release Notes prepared

The Algorithm

[x] Every requirement questioned?
[x] Delete (Scope) any part you can.
[x] Simplify.
[x] Break down into smaller iterations/milestones.
[x] Opportunities for automation.

Specification

RC Release Criteria
The RC release criteria expand on and require that all Beta release criteria continue to pass for the accelerator.

[x] All Beta release criteria pass for this accelerator.

Test Coverage
RC quality accelerators should be able to run test packages derived from the following:

TPC-H
TPC-DS
ClickBench

Indexes are not required for test coverage, but can be introduced if required for tests to pass (e.g. due to performance characteristics, etc).
TPC-H

[x] The accelerator can load TPC-H SF10 in all Access Modes, and can run all queries with no Major or Minor Bugs.
[x] The accelerator can load TPC-H SF100 in either file or database mode, and can run all queries with no Major or Minor Bugs.

TPC-DS

[ ] The accelerator can load TPC-DS SF10 in all Access Modes, and can run all queries with no Major or Minor Bugs.
[ ] The accelerator can load TPC-DS SF100 in either file or database mode, and can run all queries with no Major or Minor Bugs.

ClickBench

[ ] A test script exists that can load ClickBench data into this accelerator in all Access Modes.
[ ] The accelerator can load ClickBench in all Access Modes, and all queries run with no Major Bugs.

Data correctness

[ ] TPC-H SF10 loaded into memory, returned results are identical across source and accelerated queries for all TPC-H queries and TPC-H simple queries.
[ ] ClickBench loaded all Access Modes, returned results are identical across source and accelerated queries for all ClickBench queries.

Documentation

[ ] Documentation includes all known issues/limitations for the accelerator.
[ ] Documentation includes any exceptions made to allow this accelerator to reach RC quality (e.g. if a particular data type cannot be supported by the accelerator).
[ ] The accelerator status is updated in the table of accelerators in spiceai/docs.

Release Notes

q47 is a false positive - issue with shm_size being too low in the docker test environment: db error: ERROR: could not resize shared memory segment "/PostgreSQL.3204424506" to 8388608 bytes: No space left on device
All other queries fail with:
Query execution failed.
db error: ERROR: subquery in FROM must have an alias
HINT: For example, FROM (SELECT ...) [AS] foo.
For details, refer to the PostgreSQL manual: https://www.postgresql.org/docs/17/index.html

ClickBench Failed queries:
../../crates/runtime/benches/queries/clickbench/q19.sql
../../crates/runtime/benches/queries/clickbench/q24.sql
../../crates/runtime/benches/queries/clickbench/q25.sql
../../crates/runtime/benches/queries/clickbench/q27.sql
../../crates/runtime/benches/queries/clickbench/q37.sql
../../crates/runtime/benches/queries/clickbench/q38.sql
../../crates/runtime/benches/queries/clickbench/q39.sql
../../crates/runtime/benches/queries/clickbench/q40.sql
../../crates/runtime/benches/queries/clickbench/q41.sql
../../crates/runtime/benches/queries/clickbench/q42.sql
../../crates/runtime/benches/queries/clickbench/q43.sql
../../crates/runtime/benches/queries/clickbench/q7.sql


Decide whether to wait for tokio reform

The first piece of the tokio reform was just released: https://tokio.rs/blog/2018-02-tokio-reform-shipped/
At this point, however, neither futures, nor mio or hyper have had the chance to release updates that align them with the new tokio crate.
The blog post hints at more changes to happen within the next 6-8 weeks.
We should observe how the situation develops, and decide whether we want to ship 0.32.0 for the "old" or the new tokio ecosystem.

I am still not up to speed on tokio, let alone the tokio reforms done and changes coming, but waiting six weeks for another release is a bit long for my tastes.
Would a README note as suggested above be enough notice about Rusoto's use of tokio and friends?

I suppose so, yeah.
As long as we can try to push out a release soon after the changes to future and hyper are released, that should be okay (I'm keen to drop the "custom" default reactor in rusoto for the new one in tokio).
Is this what we can record as the outcome here?

we will not wait for futures 0.2 (and associated hyper 0.12) before releasing Rusoto 0.32.0
we will call out clearly in the README that Rusoto 0.32.0 is not compatible with the new tokio crate

When can we cut a new release?

Here's the list of issues that are part of the 0.32 milestone: https://github.com/rusoto/rusoto/milestone/3

@srijs Those two items look right to me. 👍


Fix icon button

Here I tried to provide TextButton child to IconButton to overcome material and splash position issues.  Also, code inside ButtonStyleButton doesn't have properties to control button splash independent of its size.
The major problem with this approach is since TextButton has a Material widget, it constraints child splash radius. So TextButton size has to match splash radius size to get the same appearance

No way to control splash radius (I have tried custom splash factory but it cannot be bigger than parent material widget)
Cannot make splash bigger than minimum button size.

Current IconButton doesn't have its own material so Splash doesn't get any constraints while as far as I can see all Material button's splash don't exist the min size.
This leads to lots of tests failures as existing tests expects IconButton to be independent of splash

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@HansMuller
Would love to know your thoughts on this approach


Incident-22111 Remove token from logs

Context
Incident: https://app.datadoghq.com/incidents/22111
We don't want to log the tokens even when debugging. These debug logs
end up showing up in GitLab and k8s, and they contain real usable
tokens. We don't want to leak these tokens accidentally.
We remove the logging of the tokens, since that appears to be where the
leak is.

Current dependencies on/for this PR:

main:

PR #8 👈

This comment was autogenerated by Freephite.

Thanks for the review!


Sender and OTC Gating

We need to have the ability to hold off or prevent senders and sender types (OTC) from going to receivers. This epic will allow us to track all of the work around building the logic that lets us filter by sender and/or sender type, and eventually to hold off or queue up data into timed batches.

Closing since the only ticket in this epic is complete


Testnet error

Hi,
I would like to use the daemon on the testnet but I have this error :
connect() to <IP_ADDRESS>:26178 failed after select(): Connection refused
I have no issue on the main net. Any idea why I can't use the testnet ?
Thanks.

Any help ? What am I doing wrong ?

testnet is only local - set up 2 wallets on -regtest network, connect together and start solo mining...


should remove console.log of keycode on keydown

Hey, I really like this library, but I noticed that you might be accidentally logging the event keycode on keydown.
https://github.com/djorg83/react-bootstrap-sweetalert/blob/master/lib/dist/SweetAlert.js#L171
Thanks.

fixed in 4.0.1.


v3.2.0 default parameters

The 3.2.0 update seems to have messed up default parameters in some way. Specifically, the following example worked before the update, and fails after the update:
function foo(options?: {
        option1?: string,
        option2?: boolean
    } = { })
{
    // ...
}

The error message is:
Invalid default value for argument "options", expected { option1?: string;
  option2?: bool;
}.
  29 |         option1?: string,
  30 |         option2?: boolean
> 31 |     } = { })
     |       ^
  32 | {
  33 |
  34 | }

I have not tested more basic default parameter examples.

This seems to have partially fixed the issue. It does fix properties that can be undefined or a value (thus name?: ...), but it still fails to properly deal with nullable types (name: ?string). It gives the same error message as before.
I think adding && !maybeNullableAnnotation(aprops.value) at https://github.com/codemix/babel-plugin-typecheck/blob/master/src/index.js#L725 will fix it, but I don't understand enough about the library to be sure.
I will add a pull request after Thanksgiving if you haven't already gotten around to fixing it.


Use volatile qualifier to prevent optimizations

Use volatile to prevent clang optimizations, fix int2float

@bashbaug  Can this be merged? Thanks.

Created https://github.com/KhronosGroup/OpenCL-CTS/issues/1405 for follow-up work


[3.5.rc6] Broken touch input on iOS

Godot version
3.5 RC6
System information
iOS
Issue description
Touch input on iOS became unresponsive in RC6 vs. RC5. I know about the change in the default for accumulated input.
But:

It works on Android
It doesn't work any longer on iOS (both with iOS touch delay = 0.01 in our project and the default of 0.15)
It still doesn't work on iOS by calling Input.set_use_accumualted_input(true)

I'll have to extract the touch controller code (again) to provide an MRP. Let me know if whoever tries RC6 with iOS cannot reproduce the problem. Thanks.
Steps to reproduce
Try an existing project known to be working with touch input on iOS + Godot 3.5 RC6 :-)
Minimal reproduction project
iOS_Touch.zip

It still doesn't work on iOS by calling Input.set_use_accumualted_input(true)

You shoudl call Input.set_use_accumulated_input(false) to turn it off, not on. It made turned on by default in RC 6.

 It was turned on by default in RC 6.

You are right, my bad.

Could you confirm if turning it off solves the issue?

Unfortunately I can't. I need to do more investigation. Actually the situation is quite puzzling:

Calling Input.set_use_accumulated_input(false) doesn't change anything. true and false behave the same. Touch is dead. This is with a release build export.
Calling Input.set_use_accumulated_input(false) crashes the game if I export a debug build. Now, we have stout/stderr disabled on export and I know some debug printing has been changed there so I am really not sure what's going on.

Is it touch input on specific node types? Or touch input in general doesn't register any event ever?

See https://github.com/godotengine/godot/commit/f64d5f40950505296f63a77d0d00bfe37f239695. This warning should only be enabled if you have the HDR property enabled on the Viewport

Thanks. In the project settings I have Rendering Quality HDR unchecked, and nowhere else can I see a HDR setting to disable, but that's off topic here.
I'll come back on the touch issue with more info and hopefully an MRP

Adding the MRP - it's a nice simplistic gesture controller. In RC6 no events seem to be reaching the _input(event) handler of the TouchScreenButton node. There is no output. In RC5 all is fine.
iOS_Touch.zip
.

While I don't get why Input.set_use_accumulated_input(false) doesn't do the trick in RC6, I believe iOS was missing a call to flush the accumulated input events when it was enabled. I've created #62842 to sort that out.

Thanks, this is good news. I have actually reproduced with the MRP what @akien-mga asked for:

RC6 with Input.set_use_accumulated_input(false) added in the MRP as 1st thing in _ready() works
RC5 with Input.set_use_accumulated_input(true) doesn't work, the same way as RC6 without 1.

Now, our big project from which the MRP is extracted from probably crashes because the added Input.set_use_accumulated_input() statement is done late in the initialization or for some other reason that I'd need to investigate.

Thanks for the report. Things really look like the PR will fix the issue.

Thanks - does this mean that it will work on iOS out of the box like it does on Android without the additional input config statement?

Yes.

@oeleo1 Could you test this iOS template made with @RandomShaper's fix?
https://downloads.tuxfamily.org/godotengine/testing/Godot_v3.5-rc6%2Bfixiostouch_export_templates.tpz
It should be compatible with the 3.5-rc6 macOS editor build, you can install the .tpz on top of existing templates to replace the iphone.zip template.

Yes, it works out of the box, without additional configuration. Good job!


SvgAnimatedLinearGradient rotating children

Hi there
I was testing your component to implement a skeleton in my React Native app. I wanted a simple 3x3 grid loading, something like this:

Here is the relevant part of my code:
      <SvgAnimatedLinearGradient
        height={500}
        width={500}
        primaryColor="#f6f8f9"
        secondaryColor="#dddee1"
      >
        <Rect x="0" y="0" rx="5" ry="5" width="75" height="75" />
        <Rect x="95" y="0" rx="5" ry="5" width="75" height="75" />
        <Rect x="190" y="0" rx="5" ry="5" width="75" height="75" />
        <Rect x="0" y="95" rx="5" ry="5" width="75" height="75" />
        <Rect x="95" y="95" rx="5" ry="5" width="75" height="75" />
        <Rect x="190" y="95" rx="5" ry="5" width="75" height="75" />
        <Rect x="0" y="190" rx="5" ry="5" width="75" height="75" />
        <Rect x="95" y="190" rx="5" ry="5" width="75" height="75" />
        <Rect x="190" y="190" rx="5" ry="5" width="75" height="75" />
      </SvgAnimatedLinearGradient >

The result I got was odd, my svg came out rotated:

After some digging, I found out this piece of code, in react-native-svg-animated-linear-gradient/src/index.js , line 122:
<ClipPath id="clip">
  <G rotation="50"
  origin="100, 50">
    {this.props.children}
  </G>
</ClipPath>

I tested removing this rotation prop, and my SVG came out on the right direction, only with a horizontal offset. Look at the result with this <G/> component without any prop:

Is this supposed to be like this? Why would the children be rotated/moved horizontally? With the code as is, none of the examples provided at the Readme.md work, they all come out with positioning issues. Could you expose this rotation/origin prop so we can edit it in the main component? Or remove it, I'm not sure if it should be there in the first place.
Thanks

Thanks for your report.
The issue was resolved by @musamaahmad with this commit:
https://github.com/virusvn/react-native-svg-animated-linear-gradient/commit/3a2ebc56b6f63cff0089f8055c8f1c57d8e85775#diff-1fdf421c05c1140f6d71444ea2b27638
I released new version 0.3, please let me know if still have any errors in your project.

@phpc91 Sorry so much!
I published 0.3.2, please check it.

@virusvn it's all right now. Thanks!


std/typecons: make Nullable payload void initialized

Signed-off-by: Luís Ferreira<EMAIL_ADDRESS>

Why?

Why?

Because this payload only gets valid when assigned and the assignment only occurs when it is not null. Therefore, it doesn't necessarily need to be initialized.
It still needs to be initialized in order to be @safe in edge cases where a reference to the payload is returned and assigned afterwards as get might return a reference.
This can be beneficial and have a real-world impact on beefy structs or static arrays.

Why?

Because this payload only gets valid when assigned and the assignment only occurs when it is not null. Therefore, it doesn't necessarily need to be initialized.
It still needs to be initialized in order to be @safe in edge cases where a reference to the payload is returned and assigned afterwards as get might return a reference.
This can be beneficial and have a real-world impact on beefy structs or static arrays.

This can be fully void initialized if the assignment of void initialized memory doesn't override it.

I can come up with an idea to fully void initialize this safely and discuss

This will not achieve the desired effect. Because there is at least one non-void member, the entire struct will get an initializer value, and the entire struct will be initialized to set the value of the non-void member _isNull. I believe the void initialized member will be set to all 0.
Not only that, but the _isNull condition assumes that the payload is T.init, so if the =void initializer actually did what you wanted, it could be consequentially bad, as I think its destructor would be called on assignment.

This will not achieve the desired effect. Because there is at least one non-void member, the entire struct will get an initializer value, and the entire struct will be initialized to set the value of the non-void member _isNull. I believe the void initialized member will be set to all 0.

Can you prove me with a specification point? I think that behaviour is implementation-defined, although didn't find anything in there. If there is no point talking about that, I assume the default behaviour of the void initialization.

Not only that, but the _isNull condition assumes that the payload is T.init, so if the =void initializer actually did what you wanted, it could be consequentially bad, as I think its destructor would be called on assignment.

What do you mean here? The destructor is never called as it is wrapped in a union to specifically have that behaviour.
// the lifetime of the value in copy shall be managed by
// this Nullable, so we must avoid calling its destructor.
auto copy = DontCallDestructorT(value);

If this is not what you mean, can you elaborate on that with an example, please?

The spec does not say how types with partial void initializers are initialized. True, one could implement a compiler that only initializes the non void parts. But that's not what happens now. But at least Andrei agrees that the current implementation is substandard (while also acknowledging the "spec" of TypeInfo requires the current implementation): https://issues.dlang.org/show_bug.cgi?id=21277

What do you mean here?

I actually misread this note:
        if (_isNull)
        {
            // trusted since payload is known to be T.init here.
            () @trusted { moveEmplace(copy.payload, _value.payload); }();
        }

I didn't realize moveEmplace would not call the destructor. So you are right on that point. Perhaps change the note.
The code inside the assign operator is confusing for sure (why make a copy to avoid destructing the value, when the value's destructor will already run?). I have the feeling that this can be done in a simpler way. But this PR is not about that.

The spec does not say how types with partial void initializers are initialized. True, one could implement a compiler that only initializes the non void parts. But that's not what happens now. But at least Andrei agrees that the current implementation is substandard (while also acknowledging the "spec" of TypeInfo requires the current implementation): issues.dlang.org/show_bug.cgi?id=21277

Arguing that this shouldn't be a thing because currently it is implemented in a way it is not described in the specification is not correct.

I actually misread this note:
        if (_isNull)
        {
            // trusted since payload is known to be T.init here.
            () @trusted { moveEmplace(copy.payload, _value.payload); }();
        }

I didn't realize moveEmplace would not call the destructor. So you are right on that point. Perhaps change the note.

I changed.

The code inside the assign operator is confusing for sure (why make a copy to avoid destructing the value, when the value's destructor will already run?). I have the feeling that this can be done in a simpler way. But this PR is not about that.

This is to efficiently move memory to _value.payload reference as it is known to be uninitialized, and therefore no need to call the destructor although I'm not aware of how this can be done in a better way.

The code inside the assign operator is confusing for sure (why make a copy to avoid destructing the value, when the value's destructor will already run?). I have the feeling that this can be done in a simpler way. But this PR is not about that.

This is a workaround introduced in PR #6619 to deal with types whose destructor cannot be called on T.init, because T.init violates the type's invariant contract. See issue 19065 for further discussion.

Commit message changed to comply with the contributions guidelines.

The code inside the assign operator is confusing for sure (why make a copy to avoid destructing the value, when the value's destructor will already run?). I have the feeling that this can be done in a simpler way. But this PR is not about that.

This is a workaround introduced in PR #6619 to deal with types whose destructor cannot be called on T.init, because T.init violates the type's invariant contract. See issue 19065 for further discussion.

Thanks for clarifying this! Anyway, this enters a bit out of the scope of this PR.


Telemetry: Fix for issue #234

Grafana repository from packge-cloud repository has been moved, hence grafana installation is failing from ansible installer .
taking stable release from original repo and made grafana repository as configurable item.
which issue
#234

@leonwanghui @xing-yang @skdwriting @joseph-v
This resubmision of https://github.com/opensds/opensds-installer/pull/235 to master with 1 commit.
Please review and merge.

Hi @NajmudheenCT Please cherry-pick this commit to stable/capri as soon as possible.  Thanks.