error 400 parameter is missing but it doesn't says what

I'm trying to export table from BigQuery to Storage using Airflow:

CONNECTION_ID = Variable.get("gcp_connection_id")
gcs_export_uri_template = 'gs://bucket/folder/file.csv'
table_to_csv_op = BigQueryToCloudStorageOperator(
                    task_id='table_to_csv_task',
                    source_project_dataset_table=table_name_template,
                    destination_cloud_storage_uris=gcs_export_uri_template,
                    export_format='CSV',
                    field_delimiter=',',
                    print_header=False,
                    bigquery_conn_id=CONNECTION_ID,
                    dag=dag)

The lib raises exception:
INFO - Subtask: Traceback (most recent call last):
INFO - Subtask:   File "/usr/local/bin/airflow", line 27, in <module>
INFO - Subtask:     args.func(args)
INFO - Subtask:   File "/usr/local/lib/python2.7/dist-packages/airflow/bin/cli.py", line 392, in run
INFO - Subtask:     pool=args.pool,
INFO - Subtask:   File "/usr/local/lib/python2.7/dist-packages/airflow/utils/db.py", line 50, in wrapper
INFO - Subtask:     result = func(*args, **kwargs)
INFO - Subtask:   File "/usr/local/lib/python2.7/dist-packages/airflow/models.py", line 1488, in _run_raw_task
INFO - Subtask:     result = task_copy.execute(context=context)
INFO - Subtask:   File "/usr/local/lib/python2.7/dist-packages/airflow/contrib/operators/bigquery_to_gcs.py", line 95, in execute
INFO - Subtask:     self.print_header)
INFO - Subtask:   File "/usr/local/lib/python2.7/dist-packages/airflow/contrib/hooks/bigquery_hook.py", line 316, in run_extract
INFO - Subtask:     return self.run_with_configuration(configuration)
INFO - Subtask:   File "/usr/local/lib/python2.7/dist-packages/airflow/contrib/hooks/bigquery_hook.py", line 560, in run_with_configuration
INFO - Subtask:     .insert(projectId=self.project_id, body=job_data) \
INFO - Subtask:   File "/usr/local/lib/python2.7/dist-packages/oauth2client/util.py", line 137, in positional_wrapper
INFO - Subtask:     return wrapped(*args, **kwargs)
INFO - Subtask:   File "/usr/local/lib/python2.7/dist-packages/googleapiclient/http.py", line 842, in execute
INFO - Subtask:     raise HttpError(resp, content, uri=self.uri)
INFO - Subtask: googleapiclient.errors.HttpError: <HttpError 400 when requesting https://www.googleapis.com/bigquery/v2/projects/comp-data/jobs?alt=json returned "Required parameter is missing">

It doesn't say what is missing. What is the parameter that causes the problem?
I should note I have no problem with loading from Storage to BigQuery.

Found the problem it should be:
destination_cloud_storage_uris=[gcs_export_uri_template]
In any case I still think the library should raise a better error message explaining in which parameter there is a problem.

cc @leahecole Some feedback on the Airflow operator for BigQuery.

The error message should have more details with #739.

I spent a lot of time this morning trying to replicate this error and couldn't because there was lots of detail, so I believe this can be resolved @tswast


WIP: Reorganizes leftnav files.

Changes to be committed:
modified:   tensorflow/g3doc/tutorials/leftnav_files

Can one of the admins verify this patch?


reba!

[X] cutout ong
[X] cutout svg
[ ] isolate vocal audio
[ ] calculate diva score
[ ] write into story as needed


Pluck id from record before passing to destroy

Fixes #186
Full record was being passed to destroy function, not the ID of the record

Thanks James! I've modified this to use getKey() instead of hard-coding id to account for other primary key columns.
This has been merged into develop. I encourage you to test it out, we are pending a large refactor and want to encounter as many issues as possible before we release it.


Add playground build job to the CI

What this PR does / why we need it:
Which issue(s) this PR fixes:
Ref #1617
Does this PR introduce a user-facing change?:

NONE

Great! Thank you.
/approve


feat(relayer): add retain public key check before deserialization retain checks

closes #182

Also, please add more info in the PR description about why this is necessary.


Compiler Problem

I am trying to build and run the FlexConv as explained on GitHub, I am pretty stuck already for a few days.
I have Cuda 10.1 and now I have installed python 3.6 and TensorFlow 1.14 which is built with Cuda 10.
I have set my .bashrc like this:
#CUDA
export OPT_PATH="/graphics/opt/opt_Ubuntu18.04"
export CUDA_INSTALL_PATH=${OPT_PATH}/cuda/toolkit_10.1/cuda
export CUDA_PATH=$CUDA_INSTALL_PATH
export MW_NVCC_PATH=${CUDA_INSTALL_PATH}/bin/
export CUDA_LIB_PATH=${CUDA_INSTALL_PATH}/lib64
export CUDA_INC_PATH=${CUDA_INSTALL_PATH}/include
export LD_LIBRARY_PATH=${CUDA_LIB_PATH}:$LD_LIBRARY_PATH
export PATH=${CUDA_INSTALL_PATH}/bin:$PATH
export PATH=${CUDA_INSTALL_PATH}/nvvm/bin/:$PATH
#CUB
export CUB_INC=${OPT_PATH}/cub/cub-1.8.0
#CUPTI
export CUPTI_LIB_PATH=${OPT_PATH}/cuda/toolkit_10.1/cuda/extras/CUPTI/lib64
export LD_LIBRARY_PATH=${CUPTI_LIB_PATH}:$LD_LIBRARY_PATH
#CUDNN
export CUDNN_INC_PATH=${OPT_PATH}/cuda/cudnn/7.6.5_for_10.1/cuda/include
export CUDNN_LIB_PATH=${OPT_PATH}/cuda/cudnn/7.6.5_for_10.1/cuda/lib64
export LD_LIBRARY_PATH=${CUDNN_LIB_PATH}:$LD_LIBRARY_PATH
#CUPTI
export CUPTI_LIB_PATH=${OPT_PATH}/cuda/toolkit_10.1/cuda/extras/CUPTI/lib64
export LD_LIBRARY_PATH=${CUPIT_LIB_PATH}:$LD_LIBRARY_PATH
export OPT_PATH=/graphics/opt/opt_Ubuntu18.04
export CUDA_INSTALL_PATH=${OPT_PATH}/cuda/toolkit_10.1/cuda
export CUDA_PATH=$CUDA_INSTALL_PATH
export MW_NVCC_PATH=${CUDA_INSTALL_PATH}/bin/
I also have change Findtensorflow.cmake and allow for version 1.14.
After calling cmake I am getting errors like:
-- Reuse cached information from TensorFlow 1.14.0
-- [WARNING] The TensorFlow version  has a bug (see #22766). We disable asserts using -DNDEBUG=True
-- No TensorFlow-CC-LIBRARY detected
-- No TensorFlow source repository detected
-- CUDA_INCLUDE_DIRS: /graphics/opt/opt_Ubuntu18.04/cuda/toolkit_10.1/cuda/include
-- CUDA_SAMPLE_INC: /graphics/opt/opt_Ubuntu18.04/cuda/toolkit_10.0/cuda/samples/common/inc
-- Use Cuda-CUB from /graphics/opt/opt_Ubuntu18.04/cub/cub-1.8.0
-- will build custom TensorFlow operation "flex_conv" (CPU+GPU)
-- will build custom TensorFlow operation "flex_deconv" (CPU+GPU)
-- will build custom TensorFlow operation "flex_pool" (CPU+GPU)
-- will build custom TensorFlow operation "knn_bruteforce" (CPU+GPU)
-- Configuring done
-- Generating done
-- Build files have been written to: /home/zakeri/Documents/Codes/MyCodes/FlexConvPytorch_20052020/Flex-Convolution-master/user_ops
[ 16%] Building NVCC (Device) object CMakeFiles/flex_conv_op_cu.dir/kernels/flex_conv_op_cu_generated_flex_conv_kernel_gpu.cu.cc.o
[ 16%] Building NVCC (Device) object CMakeFiles/flex_pool_op_cu.dir/kernels/flex_pool_op_cu_generated_flex_pool_kernel_gpu.cu.cc.o
[ 16%] Building NVCC (Device) object CMakeFiles/flex_deconv_op_cu.dir/kernels/flex_deconv_op_cu_generated_flex_deconv_kernel_gpu.cu.cc.o
[ 16%] Building NVCC (Device) object CMakeFiles/knn_bruteforce_op_cu.dir/kernels/knn_bruteforce_op_cu_generated_knn_bruteforce_kernel_gpu.cu.cc.o
/home/zakeri/Documents/Codes/MyCodes/FlexConvPytorch_20052020/Flex-Convolution-master/user_ops/kernels/flex_deconv_kernel_gpu.cu.cc:24:10: fatal error: tensorflow/core/util/cuda_kernel_helper.h: No such file or directory
#include "tensorflow/core/util/cuda_kernel_helper.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/zakeri/Documents/Codes/MyCodes/FlexConvPytorch_20052020/Flex-Convolution-master/user_ops/kernels/flex_pool_kernel_gpu.cu.cc:25:10: fatal error: tensorflow/core/util/cuda_kernel_helper.h: No such file or directory
#include "tensorflow/core/util/cuda_kernel_helper.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
compilation terminated.
/home/zakeri/Documents/Codes/MyCodes/FlexConvPytorch_20052020/Flex-Convolution-master/user_ops/kernels/knn_bruteforce_kernel_gpu.cu.cc:34:10: fatal error: tensorflow/core/util/cuda_kernel_helper.h: No such file or directory
#include "tensorflow/core/util/cuda_kernel_helper.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
/home/zakeri/Documents/Codes/MyCodes/FlexConvPytorch_20052020/Flex-Convolution-master/user_ops/kernels/flex_conv_kernel_gpu.cu.cc:25:10: fatal error: tensorflow/core/util/cuda_kernel_helper.h: No such file or directory
#include "tensorflow/core/util/cuda_kernel_helper.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
CMake Error at flex_deconv_op_cu_generated_flex_deconv_kernel_gpu.cu.cc.o.cmake:219 (message):
Error generating
/home/zakeri/Documents/Codes/MyCodes/FlexConvPytorch_20052020/Flex-Convolution-master/user_ops/CMakeFiles/flex_deconv_op_cu.dir/kernels/./flex_deconv_op_cu_generated_flex_deconv_kernel_gpu.cu.cc.o
CMake Error at flex_conv_op_cu_generated_flex_conv_kernel_gpu.cu.cc.o.cmake:219 (message):
Error generating
/home/zakeri/Documents/Codes/MyCodes/FlexConvPytorch_20052020/Flex-Convolution-master/user_ops/CMakeFiles/flex_conv_op_cu.dir/kernels/./flex_conv_op_cu_generated_flex_conv_kernel_gpu.cu.cc.o
CMake Error at knn_bruteforce_op_cu_generated_knn_bruteforce_kernel_gpu.cu.cc.o.cmake:219 (message):
Error generating
/home/zakeri/Documents/Codes/MyCodes/FlexConvPytorch_20052020/Flex-Convolution-master/user_ops/CMakeFiles/knn_bruteforce_op_cu.dir/kernels/./knn_bruteforce_op_cu_generated_knn_bruteforce_kernel_gpu.cu.cc.o
CMake Error at flex_pool_op_cu_generated_flex_pool_kernel_gpu.cu.cc.o.cmake:219 (message):
Error generating
/home/zakeri/Documents/Codes/MyCodes/FlexConvPytorch_20052020/Flex-Convolution-master/user_ops/CMakeFiles/flex_pool_op_cu.dir/kernels/./flex_pool_op_cu_generated_flex_pool_kernel_gpu.cu.cc.o
CMakeFiles/flex_conv_op_cu.dir/build.make:63: recipe for target 'CMakeFiles/flex_conv_op_cu.dir/kernels/flex_conv_op_cu_generated_flex_conv_kernel_gpu.cu.cc.o' failed
make[2]: *** [CMakeFiles/flex_conv_op_cu.dir/kernels/flex_conv_op_cu_generated_flex_conv_kernel_gpu.cu.cc.o] Error 1
CMakeFiles/flex_deconv_op_cu.dir/build.make:63: recipe for target 'CMakeFiles/flex_deconv_op_cu.dir/kernels/flex_deconv_op_cu_generated_flex_deconv_kernel_gpu.cu.cc.o' failed
make[2]: *** [CMakeFiles/flex_deconv_op_cu.dir/kernels/flex_deconv_op_cu_generated_flex_deconv_kernel_gpu.cu.cc.o] Error 1
CMakeFiles/knn_bruteforce_op_cu.dir/build.make:63: recipe for target 'CMakeFiles/knn_bruteforce_op_cu.dir/kernels/knn_bruteforce_op_cu_generated_knn_bruteforce_kernel_gpu.cu.cc.o' failed
make[2]: *** [CMakeFiles/knn_bruteforce_op_cu.dir/kernels/knn_bruteforce_op_cu_generated_knn_bruteforce_kernel_gpu.cu.cc.o] Error 1
CMakeFiles/flex_pool_op_cu.dir/build.make:63: recipe for target 'CMakeFiles/flex_pool_op_cu.dir/kernels/flex_pool_op_cu_generated_flex_pool_kernel_gpu.cu.cc.o' failed
make[2]: *** [CMakeFiles/flex_pool_op_cu.dir/kernels/flex_pool_op_cu_generated_flex_pool_kernel_gpu.cu.cc.o] Error 1
CMakeFiles/Makefile2:141: recipe for target 'CMakeFiles/flex_conv_op_cu.dir/all' failed
make[1]: *** [CMakeFiles/flex_conv_op_cu.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/knn_bruteforce_op_cu.dir/all' failed
make[1]: *** [CMakeFiles/knn_bruteforce_op_cu.dir/all] Error 2
CMakeFiles/Makefile2:178: recipe for target 'CMakeFiles/flex_deconv_op_cu.dir/all' failed
make[1]: *** [CMakeFiles/flex_deconv_op_cu.dir/all] Error 2
CMakeFiles/Makefile2:326: recipe for target 'CMakeFiles/flex_pool_op_cu.dir/all' failed
make[1]: *** [CMakeFiles/flex_pool_op_cu.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
So I added two lines to FindTensorFlow.cmake:
set(TensorFlow_INCLUDE_DIR) &
set(TensorFlow_LIBRARY)
And calling CMake again, I am getting this:
-- Reuse cached information from TensorFlow 1.14.0
-- [WARNING] The TensorFlow version has a bug (see #22766). We disable asserts using -DNDEBUG=True
-- No TensorFlow-CC-LIBRARY detected
-- No TensorFlow source repository detected
-- CUDA_INCLUDE_DIRS: /graphics/opt/opt_Ubuntu18.04/cuda/toolkit_10.1/cuda/include
-- CUDA_SAMPLE_INC: /samples/common/inc
CMake Error at CMakeLists.txt:26 (message):
requires 'export CUB_INC=/path/to/cub
I went through all the closed issues on GitHub and the instructions, I do not know what can I do further to make this built and run. Would you please help in this regard?

This is probably way too late, but if anyone has similar a similar issue: I think the file cuda_kernel_helper.h has been renamed to gpu_kernel_helper.h at some point, so this has to be changed in all of the import statements for newer tensorflow versions


AJ-873: Remove creation of Leo App in Terra UI

Relates to https://broadworkbench.atlassian.net/browse/AJ-873
and changes in https://github.com/broadinstitute/rawls/pull/2283

closing as obsolete.


Fix unit tests

We had a listener which was never getting removed. It should really just
be automatically getting removed once it gets dealloced. So this probably
indicates a memory cycle in the tests somewhere. I took a pass at the
actual app and that leak doesn't seem to be there, so I don't think it's
a serious problem - though we should fix it.
But in the mean time this fixes the tests.

I think this fixes the test issue that I believe was introduced by https://github.com/edx/edx-app-ios/commit/259f6b6b945848d27855fd4137c5bb0cd9da2906 cc @saeedbashir

@BenjiLee please review

:+1:


Support Update Channels in FTBA Server Type

Enhancement Type
Improve an existing feature
Describe the enhancement
Support Update Channels like "Beta" in the FTBA Server type. The FTB-App automatically updates modpacks to the latest beta release however currently the server only targets the "Release" channel.
An Environment variable like FTBA_UPDATE_CHANNEL could be added that if set to "Beta" tracks the latest versions from the  Beta channel, or if the latest Release build is newer it takes that.

Great idea. Feel free to submit a PR if you want try implementing that also.


Particle System Improvement

Godot's particle system is very simple and does its job very well, but some things can be added to it:
Random lifetime
Collision
Take out the delay it takes to emit particles when emitting is marked or make a emit() function
Array of colors to choose randomly
Fix randomness "bug" where if the param is 0 it doesn't do anything. Suggestion: make it more controllable, like if I put direction 10 and random direction 5 then it do 10 + randi_range(-5, 5)
Graph of size during lifetime
Off topic: add randi_range(min, max). No more cyber-bulling to integers!

Seen #6235 then, regarding the random numbers?

@Sslaxx No I didn't. But that's something that I don't see why it's not implemented yet. I mean, they made the hard part, the float version, but skipped the easy one.

IMO each particle parameter should be input as a Vector2: Max and Min. That would be easy and let you choose any range you like.

See also #3994, #4003, and #4294

I will add to this particle improvement general subject.
It would be great if Godot particle system was able to do things similar to Hayate Particle Turbulence that was available in Unity's Assetstore for previous version of Unity.
Especially two features:

particles "turbulence" generated from Sine, Cosine, Perlin, Animation Curves, Textures and Audio.
particles leaving trail.

Watch it in action on https://youtu.be/vG-0RO7e48U
There was a similar request before, so also add #4250

currently working on new particle system, this kind of stuff will be
possible
On Fri, Jan 6, 2017 at 8:34 PM, Freeman<EMAIL_ADDRESS>wrote:

I will add to this particle improvement general subject.
It would be great if Godot particle system was able to do things similar
to Hayate Particle Turbulence http://maxproude.com?p=160 that was
available in Unity's Assetstore for previous version of Unity.
Especially two features:

particles "turbulence" generated from Sine, Cosine, Perlin,
Animation Curves, Textures and Audio.
particles leaving trail.

Watch it in action on https://youtu.be/vG-0RO7e48U
There was a similar request before, so also add #4250
https://github.com/godotengine/godot/issues/4250
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/6377#issuecomment-271039013,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z25QMvHBliyfCBrWpMPYP4FCbMDdYks5rPs98gaJpZM4J0DEg
.

Hi @reduz
Is current existed particle system in master branch a new particle system? Or is it old and will be replaced in the future?

#7199 - related to this issue - is still open.

If some of the features proposed here are still relevant in the current master branch, I would suggest to add them to this tracker: #20473.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v3.10 to before v4.9.291",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=be055b2f89b5842f41363b5655a33dffb51a8294",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ff169909eac9e00bf1aa0af739ba6ddfb1b1d135"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "be055b2f89b5842f41363b5655a33dffb51a8294",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "ff169909eac9e00bf1aa0af739ba6ddfb1b1d135",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "NFC: reorder the logic in nfc_{un,}register_device\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.9.291 by commit ff169909eac9e00bf1aa0af739ba6ddfb1b1d135, it was introduced in version v3.10 by commit be055b2f89b5842f41363b5655a33dffb51a8294. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002227


Cannot save figure as svg

Hello stevengj and all the gang:
This may be an issue on an update on matplotlib and not here, but I do not know for sure. I have recently created some "image" (colormaps) plots on PyPlot and saved them as svg, no problem. In the same Jupyter notebook, then, I created a more complex figure, that overlays line plots over the colormap and puts various custom labels. I can save the picture as png and eps, but not as svg. I get a very unreadable error message:
LoadError: PyError (:PyObject_Call) <class 'TypeError'>
TypeError("'H�E�I�\x07H��H[A\\A]A^A_]�H���H�\x05/��\x01H�@\x08H�E�H�\x05(��\x01H�E�1�L���\x02' object is not callable",)
  File "/usr/lib64/python3.4/site-packages/matplotlib/pyplot.py", line 688, in savefig
    res = fig.savefig(*args, **kwargs)

and continues for various lines on the same vein...
Okey, new detail: I cannot save any longer the simpler figures as svg also. I swear I did not "upgraded" anything in the middle...

I just tried
using PyPlot
plot(rand(10))
savefig("foo.svg")

in IJulia with Julia 0.4.3 on MacOS X, using the Matplotlib from Conda, and it works fine.

Hi stevengj,
I am pretty sure the error may be on the matplotlib side. I just ran the code at my home computer and it works there, with Julia 0.4.3 and matplotlib 1.4.3. I think at the laboratory computer there is matplotlib 1.5.0.
I shall  put the issue over there.
Thanks!

@kzapfe, to be sure, the best thing to do would be to try it from Python (ideally with the same backend).  If you still have the problem there, then it definitely can't be PyPlot.


[many ports] Fix shared library build on Linux

Add patch for boost-chrono to produce libraries in stage directory
Use stage target in b2 to produce correct symlinks for libraries
Use .so extension in boost-modular-build-helper for dynamic build
Add conditionals for Windows-only actions in fmt portfile
Add conditional in grpc portfile - dynamic build works on Linux
Add pthread link in liblzma to prevent FindLibLZMA errors
in boost-iostreams - it failed to link when it checked for
library symbols
Fix libpq port not to produce undefined symbols
Add install step for libraries in openssl-unix
Add conditional in tbb portfile - dynamic build is recommended
when available
Add conditional for Windows-only actions in zstd portfile

Closes https://github.com/microsoft/vcpkg/issues/5247

It did not work out as intended, I will break this up into smaller pull requests.


Apex does not work with gpu-small preset

apex does not work with gpu-small preset and throws no compatible CUDA device error. Have not noticed this problem with gpu-large preset.
It works after package rebuilding.

apex was removed


In upload data option: SDK upload, in step 2,3 there is a need to add apikeycedentials else it gives an error

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 70fbb1c8-1435-e762-8824-78cf96faed84
Version Independent ID: 062879b5-72cf-2353-63f2-d862fe1b40ba
Content: Microsoft Docs contributor guide overview - Contributor Guide
Content Source: Contribute/index.md
Product: non-product-specific
GitHub Login: @Jim-Parker
Microsoft Alias: jimpark

@soumalyatheking22012001 thank you for the suggestion. Can you tell me which specific article you're referring to?

@soumalyatheking22012001 thank you for the suggestion. Can you tell me which specific article you're referring to?

I'm talking about this article.
The codes in here doesn't work it keeps giving errors. I was using python by the way.

I'm talking about this article.
The codes in here doesn't work it keeps giving errors. I was using python by the way.

@soumalyatheking22012001 I have forwarded this issue via the issue reporting functionality in that content. Waiting for a response.
thanks for letting us know about this.

As you have reported it to the authority I'm closing this issue here. Considering I have done my part in it.


Build document

Is your feature request related to a problem? Please describe.
when running go test
# github.com/Hyperledger-TWGC/Gm-Go/gmssl
../gmssl/build.go:17:10: fatal error: openssl/bio.h: No such file or directory
 #include <openssl/bio.h>
          ^~~~~~~~~~~~~~~
compilation terminated.
FAIL    github.com/Hyperledger-TWGC/Gm-Go/test [build failed]

It obviously show I miss something related to CGO.
Describe the solution you'd like
Add document about how to link up CGO and dance with original gmssl
It should be part of build from source document
Describe alternatives you've considered
N/A
Additional context
N/A

we could have TravisCI config file a primitive document

Add as a section in usage.md


not correctly joining lines for HTML

This is really hurting me. Here is an example HTML file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>

    <title>Test Line Join</title>

The key words <q>must</q>, <q>must not</q>, <q>required</q>, <q>shall</q>, <q>shall not</q>, <q>should</q>, <q>should not</q>, <q>recommended</q>, <q>may</q>, and <q>optional</q> in this document are to be interpreted as described in RFC 2119.

js-beautify should be getting rid of all that whitespace inside the  tag. I want js-beautify to give me this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>

    <title>Test Line Join</title>

The key words <q>must</q>, <q>must not</q>, <q>required</q>, <q>shall</q>, <q>shall not</q>, <q>should</q>, <q>should not</q>, <q>recommended</q>, <q>may</q>, and <q>optional</q> in this document are to be interpreted as described in RFC 2119.

But it doesn't. This is a huge problem and is really dragging down the workflow. (The reason the lines are like that to begin with is a bug in BlueGriffon. So bugs in js-beautify are preventing it from fixing the bugs in BlueGriffon. Such is life.)
See #841.
Perhaps you could point me to a place in the code I might go to try to put in some workaround?

q tags are not formatted by default. If you add an "unformated" option to your .jsbeautifyrc file, with the defaults minus the q you'll get each of the q groups on their own line at least, with the spans correctly un-whitespaced.
eg:
"unformatted": ["a", "abbr", "area", "audio", "b", "bdi", "bdo", "br", "button", "canvas", "cite", "code", "data",
		"datalist", "del", "dfn", "em", "embed", "i", "iframe", "img", "input", "ins", "kbd", "keygen", "label", "map",
		"mark", "math", "meter", "noscript", "object", "output", "progress", "ruby", "s", "samp", "select", "small", "span",
		"strong", "sub", "sup", "svg", "template", "textarea", "time", "u", "var", "video", "wbr", "text", "acronym",
		"address", "big", "dt", "ins", "strike", "tt"],

Yes, but you see @HookyQR , I want the '' tags formatted --- I just want them inline, not block. js-beautify conflates the two concepts. See #841, as I mentioned above.
@bitwiseman I want to help and not just complain. As I mentioned above, could you point me to where I might look in the code to track this down? Or do we have to just rewrite it all from scratch?

@garretwilson - just rewrite it all from scratch.  👍  Sooner or later, the HTML and CSS beautifiers will need to be rewritten to at least have a parse stage like I did with the JS beautifier.  It's just a major undertaking.

Yes, but I'm extremely, extremely overloaded with work --- and every time I add a tool to help me with my work, it seems to have a huge bug that adds more to my workload. (As an example, the reason I need this capability in the first place is that BlueGriffon has a stupid bug that the owner ignores by making line breaks even when we request in the configuration never to break lines, and so I have to use js-beautify to fix that, and it has bugs that doesn't join lines... and now Atom introduced a workaround where it is automatically soft-wrapping lines (because it crashes on what it considers long lines) --- one after another, more bugs in the tools to fix bugs.
So @bitwiseman , would you or anyone else be interested in fixing this bug or at least creating a workaround in the code, for payment? In general js-beautify for XHTML is hanging together, and if we could fix a couple of these big issues it would really help. How much would you charge to do something about this? Please contact me (you or anyone else) offline. Thanks.

I'm trying to fix the same problem for the last 3 days.
My question still is why beautify does not rely on the indent-character which is defined in my eslint.json?
Shouldn't the project-based configuration overwrite every other setting?

@garretwilson
Thanks for the offer of compensation.  I appreciate the thought.  For me, much like @Glavin001,  my main limitation is not money, but time.
What I need is people who can write code and tests that I don't have to spend cycles debugging or fixing to join this project and contribute fixes.  Until that happens, issues will continue to be addressed as I find time (that is to say, very slowly).

OK, so I'm trying out this Bountysource thing. While I want to eventually address js-beautify and atom-beautify problems, I'm going directly to the ultimate source of some of pain, and then work my way up if there is any success.
https://www.bountysource.com/issues/29803090-line-wrapping-setting-ignored

Basically the whole thing starts because the BlueGriffon editor has the blatant bug https://github.com/therealglazou/bluegriffon/issues/7 that arbitrarily adds line breaks in the middle of elements even though line wrapping are turned off. (To top it off, it adds them as LF even on the Windows platform, where it uses CRLF on the lines I really want: https://github.com/therealglazou/bluegriffon/issues/5. And you'll remember that js-beautify at one time would choose the wrong line ending: https://github.com/beautify-web/js-beautify/issues/829. So there were bugs upon bugs upon bugs. Thank goodness https://github.com/beautify-web/js-beautify/issues/829 is fixed. Thank you very much)

Because of https://github.com/beautify-web/js-beautify/issues/841 , atom-beautify refuses to re-join the lines that should have never been broken in the first place.

So when one tool's bugs prevent working around another tool's bugs, it leaves me frustrated and a bit grouchy. Cross your fingers that this Bountysource thing works, and if so I can go up the chain start knocking off some of the nasty js-beautify ones as well, such as this one.

@bitwiseman , I've thought about this a lot, and I think I have a way forward with this issue. I would like to put up a bounty on Bountysource for this bug, but before I put up the money I want to get your approval for the solution so I can know it would be integrated.
The following solution is based on the understanding that the current logic must add newlines in two separate cases:

Whenever it thinks that a line should be wrapped (if wrapping is turned on). I'll refer to this as a "wrap-newline".
Whenever it is ready to start a new element that is not in unformatted. I'll refer to this as a "block-newline".

Here is what I propose:

Create a new setting inline with the exact same value as unformatted. (These are the HTML5 inline elements you and I discussed and which you fixed in #840.)
Find the line(s) in which the current formatting logic adds a block-newline. (All the code for wrap-newline will go untouched.) For every block-newline occurrence, add the following logic: "if the new element (to appear after the block-newline) is in inline, do not add the block-newline."

I have not looked at the code, but seriously, that seems pretty simple and straightforward to me, regardless of the complexity of the code. There has to be some line(s) at which you perform a block-newline break, and I don't see why one can't just do a check to see if the new element is in the newline list or not. (I could be completely wrong about the feasibility of this solution, but that would have to be some really jumbled code not to allow this approach.)
With the above approach, if no changes are made to a user's configuration, the formatting will function 100% exactly as it did before. However for those of us who realize there is a distinction between "inline vs block" and "formatted vs unformatted", we'll merely set our unformatted setting to "" (that is, we don't want any elements to be "unformatted"). Suddenly all of our , , <q>, etc. elements will be formatted correctly, yet without them being placed on separately lines as if they were block elements!
@bitwiseman I'd like to get your approval that you would integrate such a solution if I were to write it or pay someone else to do it.
Thank you! I think we all want to get this fixed, and I'm trying the best I can to find a way to help get it done.

@garretwilson -
Either way, I'd rather see the behavior change and be consistent for all users.  I've never argued against the correctness of what you described in #841, only that I didn't have bandwidth to do it.
I'd like to make sure you understand, the bounty poster does not get any say in how a fix is designed or implemented.  The bounty is paid when the issue is fixed.  Period.  I appreciate you proposing a design and asking for a review, whoever submits a fix is not required to pay any attention to that proposal.
Are you planning to bounty this issue or #841?

Either way, I'd rather see the behavior change and be consistent for all users.

Sure, I'd like that even better! I just wasn't sure you wanted to make such a change that would affect some behavior without increasing the major version number.
We could therefore set unformatted to "", and move all the current unformatted elements to inline. That would make all the inline element format correctly, but still be inline; and by default no elements would be "unformatted".
If people considered this issue a bug, then everyone would be happy. The only problem would occur for people who both 1) thought "unformatted" really meant "unformatted", and 2) did not change the value of "unformatted". They would then be surprised when js-beautify started formatting their elements (while still leaving them inline). But I would imagine that if people are using unformatted, they have explicitly specified which elements they want by overriding unformatted, so they would never see any difference.
The only reason I suggested leaving unformatted the way it was is that I was afraid you wouldn't want existing behavior changed, and I was trying to make it more palatable for you.

The bounty is paid when the issue is fixed. Period.

If they want to rewrite the thing, that's fine with me. I was just suggesting an ultra-easy approach to getting it done and making some money. I just wanted to make sure you were fine with it.

Are you planning to bounty this issue or #841?

It makes no difference to me --- it may be that they are really the same thing: #841 explains the design problem, while this issue #1033 illustrates a negative behavior resulting from the design problem. Do you have a preference on which issue I put the bounty on? And more importantly, are you OK with what I proposed? (Because I imagine the bounty person will choose the easiest path, and I don't think there could be an approach much easier than what I laid out above.)
(If this discussion goes on much longer, I may just do it myself...)

Do you have a preference on which issue I put the bounty on? And more importantly, are you OK with what I proposed?

Did you have an opinion here? I'll be putting up actual dough, so it would be nice to know ahead of time if you're OK with this direction...

Never mind; it's easier just to start the thing.
https://www.bountysource.com/orders/68866

I just realized that I had posted the incorrect bounty link a year ago. I updated it. I see someone says they are working on it. Please let me know any questions you have or clarifications you need. Thanks.

Thanks. I'm replacing unformatted tags with inline tags, the intent of unformatted seeming to be contained in content_unformatted.
It's not a question, but may I thank you for the large number of tests. It makes me confident that I'm not breaking anything with my changes.

@madman-bob , you don't know what a huge help this will be do me. Anything you need on my end, just ask.

And just in case you missed it, @madman-bob , #841 has a more in-depth discussion of the semantics of this bug. I recommend reading that ticket as well, if you haven't already. Thanks!!

Ready for review: https://github.com/beautify-web/js-beautify/pull/1407

@garretwilson
This is the branch for that PR: https://github.com/madman-bob/js-beautify/tree/format-inline-tags
It includes the built files under https://github.com/madman-bob/js-beautify/tree/format-inline-tags/js/lib

@garretwilson
It is important to me that you have a chance to test this before I merge this.
I don't have an npm package for you, so you'll need to pull the files linked above and copy them into the folder where you have the beautifier installed.  Sorry for the hacky process, but it is what I have right now.

I apologize for not getting to this yet. I'm being overloaded with a couple of very stressful things right now. I'll try my best to get to this by this weekend.
So if I pull the new files, do you think I can simply replace the ones in the atom-beautify plugin? If so, that would make this really simple to test.

Oh, this is something cool I found in one file. BlueGriffon would produce something like this (with preformatted content removed for brevity:
    The Super POM already contains the following definitions, which is why the standard resource directories are copied by default:

…

Before now, js-beautify would live this untouched except for tabifying the non-
 indentions, as per my settings. (The  is correctly not indented, because it's inside a
.) But now with the new changes, we get this:
	The Super POM already contains the following definitions, which is why the standard resource directories are copied by default:

…

Note that the trailing  is now indented! I hadn't noticed this before, as the biggest problem earlier was the newlines inside phrasing/inline elements. But as  should be block formatted, it should indeed come on another line and be indented. So it appears there have been some possibly unrelated positive side effects from these changes as well. 👍

I'm super-excited about this issue being fixed! I just came in for the night. Remind me how to mark the bounty as done so that @madman-bob can be awarded as soon as possible. I just read the FAQ and I think maybe I'll receive some email for me to confirm.

This if available in 1.8.0-rc2.

@madman-bob, @bitwiseman, and others, I cannot begin to express my appreciation for finally getting this bug fixed and released. After a little prodding on the atom-beautify side, we finally got this into the Atom plugin as well.
It's hard to describe just how refreshing it is, when I reformat the ugly, buggy HTML that BlueGriffon puts out, to not have to manually search for those weird, wrapped lines that BlueGriffon should not have put in. Now js-beautify just fixes them, automatically (like it always should have). It's so amazing that at times I think I'm dreaming. I cannot count up all the time this is saving me, reducing my workflow, and also reducing my irritation level (or at least not adding to it 😉 ).
Thank you, thank you, thank you.
 This means that after installing VSCodeBeautify, I can open up my HTML and format it exactly like I did with atom-beautify (except using a different shortcut key), with the results being exactly the same—and it even uses the exact same .jsbeautifyrc file! This is the smoothest transition I could never have even dreamed possible. For once—for once—everything worked just like it should have.
I am very grateful. Thanks for making this happen.


Add support for SERVER_TIMEOUT SDO

There is a new SDO endpoint SERVER_TIMEOUT_SDO (0x2d06) that, when set to 1 enables a watchdog mode in the node firmware.
When enabled the node will reset its node_id after not being pinged for some time, so that it can be re-discovered via LSS.
I would go about implementing this feature like this:

Break out the discovery of supported SDOs from LxaNode::get_info() into a separate method (maybe also cache the results)
Check the supported SDOs early in the node discovery
Enable SERVER_TIMEOUT for nodes that support it as early in the node discovery as possible

During firmware development we have decided that the watchdog should default to always on.  So we do not need to change any behavior in the server component.
I will add the watchdog-diable to the commandline-use documentation for the products. I'll leave this issue open to track that change.

It looks to me like the documentation changes are now online.
I will close this issue now.


blank page when starting livebook from the command line using WSL (Windows 11)

Environment

Elixir & Erlang/OTP versions:
Erlang/OTP 26 [erts-14.0.2] [source] [64-bit]
Elixir 1.15.5 (compiled with Erlang/OTP 26)

Operating system:
Microsoft Windows 11 Home 10.0.22621 with WSL installed (v<IP_ADDRESS>) using Ubuntu 22.04.3

How have you started Livebook?
from the shell in Ubuntu (using WSL):

$ livebook server

Livebook version:
0.12.1

Browsers that reproduce this bug:

Firefox Nightly (123.0a1)
Chrome (Version 120.0.6099.131)
Brave (Version 1.61.114 Chromium: 120.0.6099.199)

Include what is logged in the browser console:
No errors in the browser console

Include what is logged to the server console:

[Livebook] Application running at http://localhost:8080/?token=skkfdma4ghobvsljhsddy22kvmej5hty

Current behavior
After starting the installed Ubuntu Linux distribution via running wsl from the Command Prompt, I am on the Linux shell and I run livebook server
➜  steff livebook server
[Livebook] Application running at http://localhost:8080/?token=53bbz6vv24hs6lha6wowr5anvmxpeyeq

Following the link, my browser opens a blank page with a "EDB Postgres" logo on it and a text "Server is up and running."

Expected behavior
Expected to see the start page (as with the Desktop version from the Windows installer):

The start page I see when I open livebook via clicking Livebook.exe in Windows file explorer.
Additional information
When starting a new livebook notebook from the shell via livebook server @new, I see this 404 page:

The browser console shows two errors:
GET http://localhost:8080/new?token=yckexycfr32fyfzdsi3qtg4upqhlizqh [HTTP/1.1 404 Not Found 1ms]
GET http://localhost:8080/favicon.ico [HTTP/1.1 404 Not Found 0ms]

Using Docker
The blank pages also show up when starting livebook from a Docker container via docker run -p 8080:8080 -p 8081:8081 --pull always ghcr.io/livebook-dev/livebook

I think there is something else hijacking port 8080 on your machine. Perhaps EnterpriseDB? Try passing the --port option to livebook server or setting the LIVEBOOK_PORT env var.

@josevalim You were exactly right. Running livebook server --port 8002 solved my problem and showed the start page as expected, thanks!
p.s. Curious about what's running on 8080 I ran netstat -aon | findstr 8080 to find a process with id 4484 running on it. Inspecting the process via tasklist | findstr 4484, it turned out to be httpd.exe which seems to be Apache webserver. I don't remember installing it, but it might have come with the installation of WSL2 or my Ubuntu distribution.

I would also expect it to report the port is being used but neither Livebook nor Docker does it, so it seems to be a OS issue. :)


[Question] Any plans for snapshot diff?

Hey,
I want to ask, if you have any plans for showing diff of screenshots if diff is there. It would be nice to create for example new folder /diff and store diffs there.
I am not sure if this is possible by your approach.

Hi @vojtech-cerveny,
In case of a failing test, diff images are automatically created, pulled to the host machine and cleared from the test device. They are stored on the host machine in the configured resultsDir, which is <path_to_your_project>/<module_name>/build/outputs/test-results/ by default.
If you want to leave the diff images on your test device, you can exclude the ClearScreenshotsTask like so:
./gradlew :<module_name>:connectedDebugAndroidTest --exclude-task :<module_name>:clearDebugAndroidTestScreenshots

(or equivalent for your build variant.)
You'll be able to find the diff images on your test device in /sdcard/Download/screenshots/.
Let me know if this answers your question.

Hey there,
In additional to store diffs. Is it possible to store a captured screenshots and get it from device? Also if tests is success


implement golangci-lint feature and fix linter Errors

Description
Why we need this ?
This pull request introduces a comprehensive golangci-lint CI/CD pipeline setup to enforce coding standards and improve code quality across the project. Let's understand why we need this:

whether it's a maintainer or a contributor everyone does mistake on revieving code or writing code respectively from coding perspective because no one is perfect. These are not big mistakes but a tiny mistakes but important such as:

not following CamelCase for writing variable names.
not handling error after error is being thrown and hide it with "_" variable
providing more permission on writing files than it requires
not formatting the code according to the standard of the project
mis-spelled of some variables or function
not making use of arguments passed in the function
declared variables, imports, or functions  but not used
leaving a blank line or whitespace
and many such things.

To handle such errors golang provides wide range of linters i.e. 50+ linters such as gofmt, govet, and many more mentioned here. But  no one want to  import each one of them in your package manually. Therefore, to solve this we have golangci-lint. It is the preferred Go linters aggregator that covers most the linters you’ll ever need. It runs these linters in parallel and reuses the build cache for improved performance during development.
What changes are being made ?

Added golangci-lint.yaml with configured linters and settings in a github worflow, which will be triggered on each PR made to the main branch.
Added the configuration file of golangci-lint  in golangci.yml to include linting steps and all linters to process.
Ran locally these errors and resolved all the  identified linting errors to adhere to the new standards and configurations.

Resources:

https://golangci-lint.run/
https://golangci-lint.run/welcome/install/#github-actions

@viveksahu26 need to resolve conflicts

Hey @riteshnoronha , any update on this ?

@viveksahu26 lets resolve the conflicts then we can merge this in

Hey @riteshnoronha , merged conflict is resolved now !!


Hotfix/adjust doc make

update adjust doc make

Codecov Report

Merging #303 into 2.0 will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            2.0   #303   +/-   ##
===================================
  Coverage   100%   100%
===================================
  Files        25     25
  Lines       638    638
===================================
  Hits        638    638

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 e433b73...d6bcb96. Read the comment docs.


[absent] Add new port

Describe the pull request
This PR adds a new port for the library: absent. absent is a small library meant to simplify the composition of nullable types in a generic, type-safe, and declarative style
for some C++ type-constructors

What does your PR fix? Fixes #
N/A

Which triplets are supported/not supported? Have you updated the CI baseline?
I believe it should work fine for all triplets as long as the compiler supports C++17 or greater.

Does your PR follow the maintainer guide?
I hope it does. Please let me know if otherwise.

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

Perfect, thanks much @rvarago :D


[BUG] Pod outside reservation triggers unexpected preemption

What happened:

Make  resource requests of all Pods on a node are empty.
Create Reservation in the node to reserve all CPUs.
Create a Pod named PodA that matched the Reservation and request 4000m cpu.
Create a high priority Pod but does not match the Reservation.
PodA is deleted by high priority Pod.

What you expected to happen:
High Priority Pod cannot preempt the PodA.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

App version:
Kubernetes version (use kubectl version):
Install details (e.g. helm install args):
Node environment (for koordlet/runtime-proxy issue):

Containerd/Docker version:
OS version:
Kernal version:
Cgroup driver: cgroupfs/systemd

Others:

/assign