#1978 hide sections

@david-yz-liu Is it possible to undo only the last commit? It introduces an issue for the marks_graders page since its not using react. If not it's something that will be fixed when I finish the other bug Im working on (1673)


Contains rework to handle maps, arrays and slices

Signed-off-by: Maxime Soulé<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build 108

95 of 95 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 99.041%

Totals

Change from base Build 105:
0.02%

Covered Lines:
3613

Relevant Lines:
3648

💛  - Coveralls


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 2220 ms

Resolved: Bofrost.de performance has improved in 00625e4 after 18 minutes.


Protocol extension

Thank you for your contribution!! 🎉
Sorry, I found 2 points I cannot accept your pull request.

Sample project is not working.

Project got error that struct ApplicationState dose not conform to protocol Writable.

CustomStringConvertible is too general protocol.

(I want to use String(describing: self) instead of "\(self)" :clap: ).


I would like to get reminded frequently to make a backup of my state

User Story
As Chris I would like to get reminded frequently to make a backup of my state so that I don't lose tokens.
Acceptance criteria

It is shown as a notification
Show it once a day

Tasks

@sashseurat Design?

@taleldayekh Thanks for implementing this.
The notification get's easily missed.
As a quick-fix:

Could we make the notification sticking or at least staying there for a much longer time? I wasn't even able to take a screenshot)

And two additional changes to the notification card:

Backup state to not risk loosing funds -> Backup your state to not risk loosing tokens
Backup state menu -> Click here to go to the backup state menu


Offset manager: make initial offset configurable

This allows you to set the initial offset Offset() will return if no offset was committed yet for the partition.
Right now, we depend on the implicit behaviour of the Kafka broker, which is returning -1. This patch makes the behaviour explicit, and allows you to change that to either OffsetOldest or OffsetNewest`.
I prefer using a config setting instead of an extra argument to ManagePartition, because this value will always be the same for every partition in a consumer.
@Shopify/kafka

Given that this allows you to send the return value directly to Consumer.ConsumePartition, we should probably make sure it always returns the next offset to consume, instead of the last offset that was committed.

I am not convinced this makes sense when the offset manager is just a subcomponent of the higher-level consumer.

because this value will always be the same for every partition in a consumer.

Is that true? What about the migration case where you want to pass a distinct constant (manual) offset for each partition?

For the migration case, I was thinking either of the following models:

Use a separate tool to simply commit the current offsets for Kafka, and restart the consumer afterwards.
Get the Offset(), and if it is negative, get it from to old storage engine, and set it with SetOffset.

Renamed Offset to NextOffset, and moved the logic to that function. Also renamed SetOffset to MarkOffset: I think it's a little bit more descriptive, but I am open to other suggestions.
Also, the godoc comments probably deserve some :eyes: as well to make sure it's clear how this functions should be used.

I added a functional test for the offset manager. I discovered a bug with it: once you have managed a partition, and closed the partition offset manager, you cannot open a new partition offset manager for that partition.
As a consumer this has to work: it's possible to start consuming a partition, then have another instance manage that partition, but later get the partition assigned back to you if the other consumer instances shuts down.
My attempt at fixing: https://github.com/Shopify/sarama/commit/3d1316a183c15224ea66a126e722287ddb326146

:+1:


Add support for OTel Java runtime metrics

What does this PR do?

Moves runtime metric mappings into separate file
Adds mappings for Java runtime metrics
Removes metricType field from runtimeMetricMapping, changes code to use incoming metric type instead
Refactors runtime metric attributes to support metrics that map from multiple attributes
Changes mapping code to remove attributes that were used in the mapping process (i.e. when jvm.heap_memory is mapped, it doesn't copy the "type=heap" attribute from the OTel metric)
Support mapping histogram runtime metrics

The aliasing of process.runtime.jvm.gc.duration to jvm.gc.parnew.time breaks setups that have both legacy Java apps using JMX and new Java applications using OTel due to a incompatibility in metric type (distribution vs. gauge).
In these scenarios, the jvm.gc.parnew.time metric metadata on the Datadog backend gets changed from a gauge to a distribution which causes the JMX-fetched gauge variant of jvm.gc.parnew.time to be completely unqueryable (disappears from all dashboards and monitors).

@sirianni can you file a support ticket for this? Please share the case number here and I can loop in the relevant people :)

Please share the case number here and I can loop in the relevant people :)

https://help.datadoghq.com/hc/en-us/requests/1434627


Multi-platform build support

Perhaps I'm approaching this incorrectly, but I'm having problems previewing SwiftUI for iOS while this package is added to the project.
I have disabled LaunchAtLogin and MenuBarExtraAccess for iOS like this:

This makes it possible to build the project for iOS, but I still get a crash when previewing.

Any ideas on how to make previews work would be amazing. Otherwise, and it probably makes little sense for you to do it since this is explicitly a macOS package, adding #if os(macOS) around the code in this package and MenuBarExtraAccess, would make the package build on iOS.
Thank you

Thank you! Together with KeyboardShortcuts 1.16.1, I can confirm that all build errors are now gone.
Too bad that SwiftUI previews don't take platform exclusion into consideration.


missing 4.7.0 and 4.8.0 releases on npmjs

It seems 4.7.0 and 4.8.0 are missing on npmjs. Is there a reason or were they just forgot to be published on npmjs?
https://www.npmjs.com/package/node-sass?activeTab=versions

They were removed because they were broken.
On Fri., 12 Oct. 2018, 1:40 am Daniel Ruf<EMAIL_ADDRESS>wrote:

It seems 4.7.0 and 4.8.0 are missing on npmjs. Is there a reason or were
they just forgot to be published on npmjs?
https://www.npmjs.com/package/node-sass?activeTab=versions
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2511, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWBiRfdnXW_a8Ud4c3cm2ibzhl0n0ks5uj1h5gaJpZM4XXqqo
.


Having trouble for compiling fftconv

Thanks for your great work. I have encountered difficulties in compiling fftconv, can you provide torch and cuda versions, as well as other environment variables. One more question, do you have plans to release the following version of the fftconv code:
u_f = torch.fft.fft(u)
k_f = torch.fft.fft(k)
y_f = u_f * k_f
y = torch.fft.ifft(y_f)

Thanks for the question! Can you paste in what output you get from trying to compile it?
cd csrc/fftconv
pip install -e .

Here is an example of the reference FFTConv: https://github.com/HazyResearch/H3/blob/main/src/ops/fftconv.py#L15
The CUDA kernel also fuses in the residual connection, GELU, and dropout, so we benchmark against those as well.

I paste the log as follow:
Looking in indexes: https://pypi.douban.com/simple/
Obtaining file:///data/user/code/H3/csrc/fftconv
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Installing collected packages: fftconv
  Attempting uninstall: fftconv
    Found existing installation: fftconv 0.1
    Can't uninstall 'fftconv'. No files were found to uninstall.
  Running setup.py develop for fftconv
    error: subprocess-exited-with-error

    × python setup.py develop did not run successfully.
    │ exit code: 1
    ╰─> [144 lines of output]

        torch.__version__  = 1.10.0+cu111

        running develop
        running egg_info
        writing fftconv.egg-info/PKG-INFO
        writing dependency_links to fftconv.egg-info/dependency_links.txt
        writing top-level names to fftconv.egg-info/top_level.txt
        reading manifest file 'fftconv.egg-info/SOURCES.txt'
        writing manifest file 'fftconv.egg-info/SOURCES.txt'
        running build_ext
        building 'fftconv' extension
        Emitting ninja build file /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/build.ninja...
        Compiling objects...
        Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
        /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/easy_install.py:156: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
          warnings.warn(
        /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
          warnings.warn(
        /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py:782: UserWarning: The detected CUDA version (11.2) has a minor version mismatch with the version that was used to compile PyTorch (11.1). Most likely this shouldn't be a problem.
          warnings.warn(CUDA_MISMATCH_WARN.format(cuda_str_version, torch.version.cuda))
        [1/2] /usr/bin/g++-7 -MMD -MF /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o.d -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/data/user/code/H3/csrc/fftconv/mathdx/22.02/include -I/data/user/code/H3/csrc/fftconv/cub-1.17.2 -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/TH -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/company/user/anaconda3/envs/lra/include/python3.8 -c -c /data/user/code/H3/csrc/fftconv/fftconv.cpp -o /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o -g -march=native -funroll-loops -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=fftconv -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
        FAILED: /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o
        /usr/bin/g++-7 -MMD -MF /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o.d -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/data/user/code/H3/csrc/fftconv/mathdx/22.02/include -I/data/user/code/H3/csrc/fftconv/cub-1.17.2 -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/TH -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/company/user/anaconda3/envs/lra/include/python3.8 -c -c /data/user/code/H3/csrc/fftconv/fftconv.cpp -o /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o -g -march=native -funroll-loops -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=fftconv -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
        cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
        /data/user/code/H3/csrc/fftconv/fftconv.cpp:6:10: fatal error: cuda/std/complex: 没有那个文件或目录
         #include <cuda/std/complex>
                  ^~~~~~~~~~~~~~~~~~
        compilation terminated.
        [2/2] /usr/local/cuda-11.2/bin/nvcc  -I/data/user/code/H3/csrc/fftconv/mathdx/22.02/include -I/data/user/code/H3/csrc/fftconv/cub-1.17.2 -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/TH -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/company/user/anaconda3/envs/lra/include/python3.8 -c -c /data/user/code/H3/csrc/fftconv/fftconv_cuda.cu -o /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv_cuda.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -O3 --threads 4 -lineinfo --use_fast_math -std=c++17 -arch=compute_70 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=fftconv -D_GLIBCXX_USE_CXX11_ABI=0 -ccbin /usr/bin/gcc-7
        FAILED: /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv_cuda.o
        /usr/local/cuda-11.2/bin/nvcc  -I/data/user/code/H3/csrc/fftconv/mathdx/22.02/include -I/data/user/code/H3/csrc/fftconv/cub-1.17.2 -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/TH -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/company/user/anaconda3/envs/lra/include/python3.8 -c -c /data/user/code/H3/csrc/fftconv/fftconv_cuda.cu -o /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv_cuda.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -O3 --threads 4 -lineinfo --use_fast_math -std=c++17 -arch=compute_70 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=fftconv -D_GLIBCXX_USE_CXX11_ABI=0 -ccbin /usr/bin/gcc-7
        In file included from /usr/local/cuda-11.2/include/thrust/system/cuda/detail/execution_policy.h:33:0,
                         from /usr/local/cuda-11.2/include/thrust/iterator/detail/device_system_tag.h:23,
                         from /usr/local/cuda-11.2/include/thrust/iterator/iterator_traits.h:111,
                         from /usr/local/cuda-11.2/include/thrust/detail/type_traits/pointer_traits.h:23,
                         from /usr/local/cuda-11.2/include/thrust/type_traits/is_contiguous_iterator.h:27,
                         from /usr/local/cuda-11.2/include/thrust/type_traits/is_trivially_relocatable.h:19,
                         from /usr/local/cuda-11.2/include/thrust/detail/complex/complex.inl:20,
                         from /usr/local/cuda-11.2/include/thrust/complex.h:1031,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/util/complex.h:8,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/util/Half.h:14,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/core/ScalarType.h:5,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/core/Scalar.h:11,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Operators.h:13,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Tensor.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Context.h:4,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/ATen.h:9,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:8,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/torch.h:3,
                         from /data/user/code/H3/csrc/fftconv/fftconv_cuda.cu:3:
        /usr/local/cuda-11.2/include/thrust/system/cuda/config.h:78:2: error: #error The version of CUB in your include path is not compatible with this release of Thrust. CUB is now included in the CUDA Toolkit, so you no longer need to use your own checkout of CUB. Define THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
         #error The version of CUB in your include path is not compatible with this release of Thrust. CUB is now included in the CUDA Toolkit, so you no longer need to use your own checkout of CUB. Define THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
          ^~~~~
        In file included from /usr/local/cuda-11.2/include/thrust/system/cuda/detail/execution_policy.h:33:0,
                         from /usr/local/cuda-11.2/include/thrust/iterator/detail/device_system_tag.h:23,
                         from /usr/local/cuda-11.2/include/thrust/iterator/iterator_traits.h:111,
                         from /usr/local/cuda-11.2/include/thrust/detail/type_traits/pointer_traits.h:23,
                         from /usr/local/cuda-11.2/include/thrust/type_traits/is_contiguous_iterator.h:27,
                         from /usr/local/cuda-11.2/include/thrust/type_traits/is_trivially_relocatable.h:19,
                         from /usr/local/cuda-11.2/include/thrust/detail/complex/complex.inl:20,
                         from /usr/local/cuda-11.2/include/thrust/complex.h:1031,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/util/complex.h:8,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/util/Half.h:14,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/core/ScalarType.h:5,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/core/Scalar.h:11,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Operators.h:13,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Tensor.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Context.h:4,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/ATen.h:9,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:8,
                         from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/torch.h:3,
                         from /data/user/code/H3/csrc/fftconv/fftconv_cuda.cu:3:
        /usr/local/cuda-11.2/include/thrust/system/cuda/config.h:78:2: error: #error The version of CUB in your include path is not compatible with this release of Thrust. CUB is now included in the CUDA Toolkit, so you no longer need to use your own checkout of CUB. Define THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
         #error The version of CUB in your include path is not compatible with this release of Thrust. CUB is now included in the CUDA Toolkit, so you no longer need to use your own checkout of CUB. Define THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
          ^~~~~
        ninja: build stopped: subcommand failed.
        Traceback (most recent call last):
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1717, in _run_ninja_build
            subprocess.run(
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/subprocess.py", line 516, in run
            raise CalledProcessError(retcode, process.args,
        subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

        The above exception was the direct cause of the following exception:

        Traceback (most recent call last):
          File "<string>", line 2, in <module>
          File "<pip-setuptools-caller>", line 34, in <module>
          File "/data/user/code/H3/csrc/fftconv/setup.py", line 116, in <module>
            setup(
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/__init__.py", line 153, in setup
            return distutils.core.setup(**attrs)
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/core.py", line 148, in setup
            dist.run_commands()
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/dist.py", line 966, in run_commands
            self.run_command(cmd)
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/dist.py", line 985, in run_command
            cmd_obj.run()
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/develop.py", line 34, in run
            self.install_for_development()
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/develop.py", line 114, in install_for_development
            self.run_command('build_ext')
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/cmd.py", line 313, in run_command
            self.distribution.run_command(command)
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/dist.py", line 985, in run_command
            cmd_obj.run()
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 79, in run
            _build_ext.run(self)
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/command/build_ext.py", line 340, in run
            self.build_extensions()
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 735, in build_extensions
            build_ext.build_extensions(self)
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/command/build_ext.py", line 449, in build_extensions
            self._build_extensions_serial()
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/command/build_ext.py", line 474, in _build_extensions_serial
            self.build_extension(ext)
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 202, in build_extension
            _build_ext.build_extension(self, ext)
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/command/build_ext.py", line 528, in build_extension
            objects = self.compiler.compile(sources,
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 556, in unix_wrap_ninja_compile
            _write_ninja_file_and_compile_objects(
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1399, in _write_ninja_file_and_compile_objects
            _run_ninja_build(
          File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1733, in _run_ninja_build
            raise RuntimeError(message) from e
        RuntimeError: Error compiling objects for extension
        [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Can't roll back fftconv; was not uninstalled
error: subprocess-exited-with-error

× python setup.py develop did not run successfully.
│ exit code: 1
╰─> [144 lines of output]

    torch.__version__  = 1.10.0+cu111

    running develop
    running egg_info
    writing fftconv.egg-info/PKG-INFO
    writing dependency_links to fftconv.egg-info/dependency_links.txt
    writing top-level names to fftconv.egg-info/top_level.txt
    reading manifest file 'fftconv.egg-info/SOURCES.txt'
    writing manifest file 'fftconv.egg-info/SOURCES.txt'
    running build_ext
    building 'fftconv' extension
    Emitting ninja build file /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/build.ninja...
    Compiling objects...
    Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
    /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/easy_install.py:156: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
      warnings.warn(
    /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
      warnings.warn(
    /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py:782: UserWarning: The detected CUDA version (11.2) has a minor version mismatch with the version that was used to compile PyTorch (11.1). Most likely this shouldn't be a problem.
      warnings.warn(CUDA_MISMATCH_WARN.format(cuda_str_version, torch.version.cuda))
    [1/2] /usr/bin/g++-7 -MMD -MF /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o.d -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/data/user/code/H3/csrc/fftconv/mathdx/22.02/include -I/data/user/code/H3/csrc/fftconv/cub-1.17.2 -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/TH -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/company/user/anaconda3/envs/lra/include/python3.8 -c -c /data/user/code/H3/csrc/fftconv/fftconv.cpp -o /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o -g -march=native -funroll-loops -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=fftconv -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
    FAILED: /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o
    /usr/bin/g++-7 -MMD -MF /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o.d -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/data/user/code/H3/csrc/fftconv/mathdx/22.02/include -I/data/user/code/H3/csrc/fftconv/cub-1.17.2 -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/TH -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/company/user/anaconda3/envs/lra/include/python3.8 -c -c /data/user/code/H3/csrc/fftconv/fftconv.cpp -o /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv.o -g -march=native -funroll-loops -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=fftconv -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
    cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
    /data/user/code/H3/csrc/fftconv/fftconv.cpp:6:10: fatal error: cuda/std/complex: 没有那个文件或目录
     #include <cuda/std/complex>
              ^~~~~~~~~~~~~~~~~~
    compilation terminated.
    [2/2] /usr/local/cuda-11.2/bin/nvcc  -I/data/user/code/H3/csrc/fftconv/mathdx/22.02/include -I/data/user/code/H3/csrc/fftconv/cub-1.17.2 -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/TH -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/company/user/anaconda3/envs/lra/include/python3.8 -c -c /data/user/code/H3/csrc/fftconv/fftconv_cuda.cu -o /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv_cuda.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -O3 --threads 4 -lineinfo --use_fast_math -std=c++17 -arch=compute_70 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=fftconv -D_GLIBCXX_USE_CXX11_ABI=0 -ccbin /usr/bin/gcc-7
    FAILED: /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv_cuda.o
    /usr/local/cuda-11.2/bin/nvcc  -I/data/user/code/H3/csrc/fftconv/mathdx/22.02/include -I/data/user/code/H3/csrc/fftconv/cub-1.17.2 -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/TH -I/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/company/user/anaconda3/envs/lra/include/python3.8 -c -c /data/user/code/H3/csrc/fftconv/fftconv_cuda.cu -o /data/user/code/H3/csrc/fftconv/build/temp.linux-x86_64-3.8/fftconv_cuda.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -O3 --threads 4 -lineinfo --use_fast_math -std=c++17 -arch=compute_70 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=fftconv -D_GLIBCXX_USE_CXX11_ABI=0 -ccbin /usr/bin/gcc-7
    In file included from /usr/local/cuda-11.2/include/thrust/system/cuda/detail/execution_policy.h:33:0,
                     from /usr/local/cuda-11.2/include/thrust/iterator/detail/device_system_tag.h:23,
                     from /usr/local/cuda-11.2/include/thrust/iterator/iterator_traits.h:111,
                     from /usr/local/cuda-11.2/include/thrust/detail/type_traits/pointer_traits.h:23,
                     from /usr/local/cuda-11.2/include/thrust/type_traits/is_contiguous_iterator.h:27,
                     from /usr/local/cuda-11.2/include/thrust/type_traits/is_trivially_relocatable.h:19,
                     from /usr/local/cuda-11.2/include/thrust/detail/complex/complex.inl:20,
                     from /usr/local/cuda-11.2/include/thrust/complex.h:1031,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/util/complex.h:8,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/util/Half.h:14,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/core/ScalarType.h:5,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/core/Scalar.h:11,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Operators.h:13,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Tensor.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Context.h:4,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/ATen.h:9,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:8,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/torch.h:3,
                     from /data/user/code/H3/csrc/fftconv/fftconv_cuda.cu:3:
    /usr/local/cuda-11.2/include/thrust/system/cuda/config.h:78:2: error: #error The version of CUB in your include path is not compatible with this release of Thrust. CUB is now included in the CUDA Toolkit, so you no longer need to use your own checkout of CUB. Define THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
     #error The version of CUB in your include path is not compatible with this release of Thrust. CUB is now included in the CUDA Toolkit, so you no longer need to use your own checkout of CUB. Define THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
      ^~~~~
    In file included from /usr/local/cuda-11.2/include/thrust/system/cuda/detail/execution_policy.h:33:0,
                     from /usr/local/cuda-11.2/include/thrust/iterator/detail/device_system_tag.h:23,
                     from /usr/local/cuda-11.2/include/thrust/iterator/iterator_traits.h:111,
                     from /usr/local/cuda-11.2/include/thrust/detail/type_traits/pointer_traits.h:23,
                     from /usr/local/cuda-11.2/include/thrust/type_traits/is_contiguous_iterator.h:27,
                     from /usr/local/cuda-11.2/include/thrust/type_traits/is_trivially_relocatable.h:19,
                     from /usr/local/cuda-11.2/include/thrust/detail/complex/complex.inl:20,
                     from /usr/local/cuda-11.2/include/thrust/complex.h:1031,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/util/complex.h:8,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/util/Half.h:14,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/core/ScalarType.h:5,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/c10/core/Scalar.h:11,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Operators.h:13,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Tensor.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/Context.h:4,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/ATen/ATen.h:9,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:8,
                     from /home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/torch.h:3,
                     from /data/user/code/H3/csrc/fftconv/fftconv_cuda.cu:3:
    /usr/local/cuda-11.2/include/thrust/system/cuda/config.h:78:2: error: #error The version of CUB in your include path is not compatible with this release of Thrust. CUB is now included in the CUDA Toolkit, so you no longer need to use your own checkout of CUB. Define THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
     #error The version of CUB in your include path is not compatible with this release of Thrust. CUB is now included in the CUDA Toolkit, so you no longer need to use your own checkout of CUB. Define THRUST_IGNORE_CUB_VERSION_CHECK to ignore this.
      ^~~~~
    ninja: build stopped: subcommand failed.
    Traceback (most recent call last):
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1717, in _run_ninja_build
        subprocess.run(
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/subprocess.py", line 516, in run
        raise CalledProcessError(retcode, process.args,
    subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last):
      File "<string>", line 2, in <module>
      File "<pip-setuptools-caller>", line 34, in <module>
      File "/data/user/code/H3/csrc/fftconv/setup.py", line 116, in <module>
        setup(
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/__init__.py", line 153, in setup
        return distutils.core.setup(**attrs)
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/dist.py", line 966, in run_commands
        self.run_command(cmd)
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/develop.py", line 34, in run
        self.install_for_development()
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/develop.py", line 114, in install_for_development
        self.run_command('build_ext')
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 79, in run
        _build_ext.run(self)
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/command/build_ext.py", line 340, in run
        self.build_extensions()
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 735, in build_extensions
        build_ext.build_extensions(self)
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/command/build_ext.py", line 449, in build_extensions
        self._build_extensions_serial()
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/command/build_ext.py", line 474, in _build_extensions_serial
        self.build_extension(ext)
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 202, in build_extension
        _build_ext.build_extension(self, ext)
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/distutils/command/build_ext.py", line 528, in build_extension
        objects = self.compiler.compile(sources,
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 556, in unix_wrap_ninja_compile
        _write_ninja_file_and_compile_objects(
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1399, in _write_ninja_file_and_compile_objects
        _run_ninja_build(
      File "/home/company/user/anaconda3/envs/lra/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1733, in _run_ninja_build
        raise RuntimeError(message) from e
    RuntimeError: Error compiling objects for extension
    [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.

There are some problems when using cub head file with 1.10.0+cu111, to solve this, I download cub-1.17.2 in the fftconv dir, my working dir is as follows:
build       fftconv.cpp      fftconv.egg-info   lut_code_gen.py  map.h   setup.py         tmp.log
cub-1.17.2  fftconv_cuda.cu  launch_fftconv.py  lut.h            mathdx  static_switch.h  twiddle.cuh

I think most problems are caused by the version of torch and cuda. Could you please give their version, rr export the conda environment of h3 in the form of yaml? This will be very helpful.

PyTorch version: 1.13.1
CUDA version: 11.7
We use Docker for everything, the FlashAttention Dockerfile should compile things well: https://github.com/HazyResearch/flash-attention/blob/main/training/Dockerfile
(that one may install a different version of `lash-attention than the one this code depends on).

Hi, thanks for your suggestion. I have changed the environment to torch-1.13.1 and cuda-11.7, then I meet new problems as follow:
[1/3] /opt/rh/devtoolset-9/root/usr/bin/g++ -MMD -MF fftconv.o.d -DTORCH_EXTENSION_NAME=tno_causal_v12 -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -I/nvme/user/code/fast-tno/src/fftconv/mathdx/22.02/include -I/nvme/share/cuda-11.8/include -isystem /nvme/user/miniconda3/envs/tno/lib/python3.8/site-packages/torch/include -isystem /nvme/user/miniconda3/envs/tno/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -isystem /nvme/user/miniconda3/envs/tno/lib/python3.8/site-packages/torch/include/TH -isystem /nvme/user/miniconda3/envs/tno/lib/python3.8/site-packages/torch/include/THC -isystem /nvme/share/cuda-11.8/include -isystem /nvme/user/miniconda3/envs/tno/include/python3.8 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++14 -g -march=native -funroll-loops -c /nvme/user/code/fast-tno/src/fftconv/fftconv.cpp -o fftconv.o
FAILED: fftconv.o
/opt/rh/devtoolset-9/root/usr/bin/g++ -MMD -MF fftconv.o.d -DTORCH_EXTENSION_NAME=tno_causal_v12 -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -I/nvme/user/code/fast-tno/src/fftconv/mathdx/22.02/include -I/nvme/share/cuda-11.8/include -isystem /nvme/user/miniconda3/envs/tno/lib/python3.8/site-packages/torch/include -isystem /nvme/user/miniconda3/envs/tno/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -isystem /nvme/user/miniconda3/envs/tno/lib/python3.8/site-packages/torch/include/TH -isystem /nvme/user/miniconda3/envs/tno/lib/python3.8/site-packages/torch/include/THC -isystem /nvme/share/cuda-11.8/include -isystem /nvme/user/miniconda3/envs/tno/include/python3.8 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++14 -g -march=native -funroll-loops -c /nvme/user/code/fast-tno/src/fftconv/fftconv.cpp -o fftconv.o
/nvme/user/code/fast-tno/src/fftconv/fftconv.cpp:8:10: fatal error: cuda_fp16.h: No such file or directory
    8 | #include <cuda_fp16.h>
      |          ^~~~~~~~~~~~~

My environment variable is as follows:
export CUDA_HOME=/nvme/share/cuda-11.8
export PATH=$CUDA_HOME/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=$CUDA_HOME/lib64

We provide a Dockerfile here, are you able to try this? https://github.com/HazyResearch/H3/blob/main/Dockerfile
Usually in my experience these compile errors mean that there is something misconfigured with the CUDA or NVIDIA drivers. I believe NVIDIA has more information about the versions in the Docker image here: https://docs.nvidia.com/deeplearning/frameworks/support-matrix/index.html (we use nvcr.io/nvidia/pytorch:22.11-py3).
Please let us know if this helps!

Thanks for your suggestions, all problems are solved now.

My solution is slightly different, and I list it here for the convenience of others.

Update setup.py from:

ext_modules.append(
    CUDAExtension(
        'fftconv', [
            'fftconv.cpp',
            'fftconv_cuda.cu',
        ],
        extra_compile_args={'cxx': ['-g', '-march=native', '-funroll-loops'],
                            'nvcc': ['-O3', '--threads', '4', '-lineinfo', '--use_fast_math', '-std=c++17', '-arch=compute_70']
        # extra_compile_args={'cxx': ['-O3'],
        #                     'nvcc': append_nvcc_threads(['-O3', '-lineinfo', '--use_fast_math', '-std=c++17'] + cc_flag)
                            },
        include_dirs=[os.path.join(this_dir, 'mathdx/22.02/include'),
                      ]
    )
)

to
cuda_dir = os.environ["CUDA_HOME"]

ext_modules.append(
    CUDAExtension(
        'fftconv', [
            'fftconv.cpp',
            'fftconv_cuda.cu',
        ],
        extra_compile_args={'cxx': ['-g', '-march=native', '-funroll-loops'],
                            'nvcc': ['-O3', '--threads', '4', '-lineinfo', '--use_fast_math', '-std=c++17', '-arch=compute_70']
        # extra_compile_args={'cxx': ['-O3'],
        #                     'nvcc': append_nvcc_threads(['-O3', '-lineinfo', '--use_fast_math', '-std=c++17'] + cc_flag)
                            },
        include_dirs=[os.path.join(this_dir, 'mathdx/22.02/include'),
                      os.path.join(cuda_dir, "targets/x86_64-linux/include")
                      ]
    )
)

Most problems are caused by cuda/torch version and env variable, I list them as follows:
torch version:

torch: 1.13.1+cu117

env variable:
export CUDA_HOME=/nvme/share/cuda-11.8
export PATH=$CUDA_HOME/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=$CUDA_HOME/lib64:${CUDA_HOME}/targets/x86_64-linux/include:$CUDA_HOME/include


add polsky.ac.id

Institution Official Website: polsky.ac.id

@YudistiraPolsky First stage of verification passed, official domain is polsky.ac.id as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

Hi @YudistiraPolsky
Please provide us with a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

You can provide us with any of the following:

A copy of instruction (a hard-copy or electronic one) given to you by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that students use this email domain
A reference to a recognized journal where an article was published by someone from the school, with explicit affiliation to the school, and e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be verified independently.

@YudistiraPolsky Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Fix build warnings in TachyonFS.java and package-info.java .

Patch fixes these recently introduced warnings:
[WARNING] /home/abutala/work/tachyon/source/abhirajbutala/tachyon/core/src/main/java/tachyon/client/TachyonFS.java:631: warning - @param argument "the" is not a parameter name.
[WARNING] /home/abutala/work/tachyon/source/abhirajbutala/tachyon/core/src/main/java/tachyon/client/TachyonFS.java:631: warning - @param argument "the" is not a parameter name.
[WARNING] /home/abutala/work/tachyon/source/abhirajbutala/tachyon/core/src/main/java/tachyon/worker/package-info.java:58: warning - Tag @link: can't find createBlockResponseMessage(boolean, long, long,
[WARNING] long) in tachyon.worker.nio.DataServerMessage

Can one of the admins verify this patch?

Thanks!


BUG: Fix DICOM display fields merging

@jcfr I noticed a problem with merging the fields, and although it does not cause an actual bug in this version, it will when more plugins start popping up. It's good I caught it now. Also fixed a typo that would have caused issues with the same thing.

It would be good, I agree. I'll do it when I have some time.


Container Security Operator v1.0.2

Signed-off-by: alecmerdler<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

@J0zi Could you please review? Please note that this Operator has behavior that will cause it to fail one of the tests, [but we have merged it before](@J0zi Could you please review? Please note that this Operator has behavior that will cause it to fail one of the tests, but ). We are working on a fix to make it pass this test.


v4.4 on Raspberry Pi 4 ... "gcc is not able to compile a simple test program." (IDFGH-6180)

Hi.
If I do this everything works exactly as expected:
# Install IDF
export IDF_TOOLS_PATH=/home/esp/tools/
mkdir /home/esp/idf
cd /home/esp/idf
git clone -b v4.3.1 --recursive https://github.com/espressif/esp-idf.git .
./install.sh

# Pull fix for broken CA file
cd /home/esp/idf/components/mbedtls/esp_crt_bundle
mv  cacrt_all.pem  cacrt_all.pem.orig
wget https://raw.githubusercontent.com/electrocucaracha/esp-idf/4e45f13e2df72a4cb4dc875942e95775198db85c/components/mbedtls/esp_crt_bundle/cacrt_all.pem

# Compile 'blink'
cp -pr  /home/esp/idf/examples/get-started/blink  /home/esp/blink/
cd /home/esp/blink
. /home/esp/idf/export.sh
idf.py  set-target  esp32s2
idf.py build

However, the author of TinyUSB (@hathach) has told me that TinyUSB does not (and will not in the forseeable future) do what I need, so I need to use v4.4 of the IDF.
If I erase everything (and clear the environment) ...and repeat all the above steps using -b release/v4.4, the set-target command fails with:
~/blink $ idf.py  set-target  esp32s2
Adding "set-target"'s dependency "fullclean" to list of commands with default set of options.
Executing action: fullclean
Build directory '/home/esp/blink/build' not found. Nothing to clean.
Executing action: set-target
Set Target to: esp32s2, new sdkconfig created. Existing sdkconfig renamed to sdkconfig.old.
Running cmake in directory /home/esp/blink/build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -DIDF_TARGET=esp32s2 -DCCACHE_ENABLE=0 /home/esp/blink"...
-- Found Git: /usr/bin/git (found version "2.20.1")
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc
-- Check for working C compiler: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc
-- Check for working C compiler: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc -- broken
CMake Error at /usr/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message):
  The C compiler

    "/home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc"
  is not able to compile a simple test program.
  It fails with the following output:
    Change Dir: /home/esp/blink/build/CMakeFiles/CMakeTmp

    Run Build Command(s):/usr/bin/ninja cmTC_a0212 && [1/2] Building C object CMakeFiles/cmTC_a0212.dir/testCCompiler.c.obj
    [2/2] Linking C executable cmTC_a0212
    FAILED: cmTC_a0212
    : && /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc -mlongcalls   CMakeFiles/cmTC_a0212.dir/testCCompiler.c.obj  -o cmTC_a0212   && :
    /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../lib/gcc/xtensa-esp32s2-elf/8.4.0/../../../../xtensa-esp32s2-elf/bin/ld: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so: error loading plugin: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
    collect2: error: ld returned 1 exit status
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  /home/esp/idf/tools/cmake/project.cmake:290 (__project)
  CMakeLists.txt:8 (project)

-- Configuring incomplete, errors occurred!
See also "/home/esp/blink/build/CMakeFiles/CMakeOutput.log".
See also "/home/esp/blink/build/CMakeFiles/CMakeError.log".
cmake failed with exit code 1

The directory /home/esp/blink/build/CMakeFiles/CMakeTmp DOES exist:
~/blink $ ls -ald /home/esp/blink/build/CMakeFiles/CMakeTmp
drwxr-xr-x 2 esp esp 4096 Nov  8 21:27 /home/esp/blink/build/CMakeFiles/CMakeTmp

And so does /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so:
~/blink $ ls -al /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so*
lrwxrwxrwx 1 esp esp    22 Nov  8 21:25 /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so -> liblto_plugin.so.0.0.0
lrwxrwxrwx 1 esp esp    22 Nov  8 21:25 /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so.0 -> liblto_plugin.so.0.0.0
-rwxr-xr-x 1 esp esp 71508 Oct 15 07:35 /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so.0.0.0

The log files don't give me any further clues:
~/blink $ cat build/CMakeFiles/CMakeError.log
Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc
Build flags: -mlongcalls
Id flags:

The output was:
1
/home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../lib/gcc/xtensa-esp32s2-elf/8.4.0/../../../../xtensa-esp32s2-elf/bin/ld: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so: error loading plugin: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
collect2: error: ld returned 1 exit status

Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
Compiler: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-g++
Build flags: -mlongcalls
Id flags:

The output was:
1
/home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../lib/gcc/xtensa-esp32s2-elf/8.4.0/../../../../xtensa-esp32s2-elf/bin/ld: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so: error loading plugin: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
collect2: error: ld returned 1 exit status

Determining if the C compiler works failed with the following output:
Change Dir: /home/esp/blink/build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/ninja cmTC_a0212 && [1/2] Building C object CMakeFiles/cmTC_a0212.dir/testCCompiler.c.obj
[2/2] Linking C executable cmTC_a0212
FAILED: cmTC_a0212
: && /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc -mlongcalls   CMakeFiles/cmTC_a0212.dir/testCCompiler.c.obj  -o cmTC_a0212   && :
/home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../lib/gcc/xtensa-esp32s2-elf/8.4.0/../../../../xtensa-esp32s2-elf/bin/ld: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so: error loading plugin: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/../libexec/gcc/xtensa-esp32s2-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

~/blink $ cat build/CMakeFiles/CMakeOutput.log
The target system is: Generic -  -
The host system is: Linux - 5.10.63-v7l+ - armv7l
Compiling the C compiler identification source file "CMakeCCompilerId.c" succeeded.
Compiler: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc
Build flags: -mlongcalls
Id flags: -c

The output was:
0

Compilation of the C compiler identification source "CMakeCCompilerId.c" produced "CMakeCCompilerId.o"

The C compiler identification is GNU, found in "/home/esp/blink/build/CMakeFiles/3.16.3/CompilerIdC/CMakeCCompilerId.o"

Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" succeeded.
Compiler: /home/esp/tools/tools/xtensa-esp32s2-elf/esp-2021r2-8.4.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-g++
Build flags: -mlongcalls
Id flags: -c

The output was:
0

Compilation of the CXX compiler identification source "CMakeCXXCompilerId.cpp" produced "CMakeCXXCompilerId.o"

The CXX compiler identification is GNU, found in "/home/esp/blink/build/CMakeFiles/3.16.3/CompilerIdCXX/CMakeCXXCompilerId.o"

Checking whether the ASM compiler is GNU using "--version" matched "(GNU assembler)|(GCC)|(Free Software Foundation)":
xtensa-esp32s2-elf-gcc (crosstool-NG esp-2021r2) 8.4.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

The same error happens if I use master or 4.4-dev branches, or if I use git to switch branches from 4.3.1 (as per the official docs) ...IE. 4.3.1 is the only version I can get to work - and I need v4.4 for the native USB support!
I'm out of ideas! Can anybody help please?
Thanks,
BC

Hello @csBlueChip
I don't get the error you are reporting with either master or release/v4.4. Here are the steps I use on Ubuntu 20.04 after deleting .espressif and esp directories (e.g. fresh install):
mkdir esp
cd esp
git clone -b release/v4.4 --recursive https://github.com/espressif/esp-idf.git
cd esp-idf
./install.sh
. ./export.sh
cd ..
cp -r esp-idf/examples/get-started/blink .
cd blink
idf.py set-target esp32s2
idf.py build

Hopefully this can shed some light on the issue you are seeing.
Thanks
Felix
P.S. Have you verified there is enough free space on your drive?

@felmue
Felix. Thank You. Your success has led me to the source of my problem!
I pasted your exact commands to a "clean" user, and got the same problem (again) ...Then I repeated the exercise on an x86 Debian VM! ...Success!
It seems the source of the problem is that I have been using a Raspberry Pi 4 as my μC dev box ...release/v4.4 DOES work on x86/Debian; and does NOT work Pi4/Raspbian.
$ uname -a
Linux devserver 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux

$ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

I'm not sure if you are the right person to ask this question, but: Is IDF v4.4 expected to work on a Pi4? ...Should I change the title of this Issue? Or start another? Or <other please specify>?  ...Either way I offer my help to test any potential fixes.
On the bright side, Thank You for prompting me to realise the issue and find a functional workaround.
BC

Hello @csBlueChip
Thank you for your feedback. Unfortunately I don't know it IDF v4.4 is supposed to work on a Pi4 at this point in time and I don't posses a Pi4 so I cannot test myself. So yes, I'd suggest you change the title to indicate the issue is in conjunction with the Pi4. Hopefully somebody with better knowledge than me can help you figuring out what's causing the issue on the Pi4.
Thanks
Felix

@csBlueChip Our tools team is looking into this issue currently.

Hey @0xjakob,
Do you have any update on this issue?
Cheers,
BC

same problems on my raspberry pi 4 after update the esp-idf to latest code on master branch

it seems that the toolchain has some problems.
the command line:
~/oss/esp-idf/examples/get-started/blink/build/CMakeFiles $ /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc 3.16.3/CompilerIdC/CMakeCCompilerId.c
/home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: error loading plugin: /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
if use host gcc, compile is ok.
pi@raspberrypi:~/oss/esp-idf/examples/get-started/blink/build/CMakeFiles $ gcc 3.16.3/CompilerIdC/CMakeCCompilerId.c
pi@raspberrypi:~/oss/esp-idf/examples/get-started/blink/build/CMakeFiles $ ls
3.16.3  a.out  cmake.check_cache  CMakeError.log  CMakeOutput.log  CMakeTmp  git-data

ok.... after add these params, compile is ok now..
-fno-lto -fno-use-linker-plugin
pi@raspberrypi:~/oss/esp-idf/examples/get-started/blink/build/CMakeFiles $ /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc -fno-lto -fno-use-linker-plugin 3.16.3/CompilerIdC/CMakeCCompilerId.c
pi@raspberrypi:~/oss/esp-idf/examples/get-started/blink/build/CMakeFiles $ ls
3.16.3  a.out  cmake.check_cache  CMakeError.log  CMakeOutput.log  CMakeTmp  git-data

@zikalino
zikalino

@csBlueChip add these two lines in CMakeLists.txt can avoid this problem temporarily
set(CMAKE_C_FLAGS "-fno-lto -fno-use-linker-plugin")
set(CMAKE_CXX_FLAGS "-fno-lto -fno-use-linker-plugin")

Hi,
I'm experiencing the same issue. I thought I'd mention that if instead of using . export.sh I directly execute ~/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc -c foo.c -o foo then the compiler has no problem producing a binary executable. However, every attempt at compiling anything via idf.py fails with the same error reported by @csBlueChip above.
If there's something I can do to narrow this issue down and help you debug it, please let me know.

Thanks for reporting and sorry for the late response! Could you please run ldd ~/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so and paste the output here?

pi@raspberrypi:~/esp/hello_world $ ldd ~/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so
	not a dynamic executable

always the same type of error
/home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: error loading plugin: /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
and
pi@raspberrypi:~/esp/hello_world $ ls -l /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld
-rwxr-xr-x 4 pi pi 1285276 Oct 15 08:33 /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld
pi@raspberrypi:~/esp/hello_world $ ls -l /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so
lrwxrwxrwx 1 pi pi 22 Jan  5 17:36 /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so -> liblto_plugin.so.0.0.0

Thank you for following up, @igrr.
I get the same "not a dynamic executable" message from ldd that @rrobinet reports.
-- Found Git: /usr/bin/git (found version "2.20.1")
-- Component directory /home/pi/esp/esp-idf/components/esp_phy does not contain a CMakeLists.txt file. No component will be added
-- Component directory /home/pi/esp/esp-idf/components/ieee802154 does not contain a CMakeLists.txt file. No component will be added
-- Component directory /home/pi/esp/esp-idf/components/openthread does not contain a CMakeLists.txt file. No component will be added
-- ccache will be used for faster recompilation
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
-- Check for working C compiler: /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
-- Check for working C compiler: /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc -- broken
CMake Error at /usr/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60 (message):
  The C compiler

    "/home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /home/pi/8-channel/build/CMakeFiles/CMakeTmp

    Run Build Command(s):/usr/bin/ninja cmTC_08ba7 && [1/2] Building C object CMakeFiles/cmTC_08ba7.dir/testCCompiler.c.obj
    [2/2] Linking C executable cmTC_08ba7
    FAILED: cmTC_08ba7
    : && /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc -mlongcalls -Wno-frame-address   CMakeFiles/cmTC_08ba7.dir/testCCompiler.c.obj  -o cmTC_08ba7   && :
    /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: error loading plugin: /home/pi/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory
    collect2: error: ld returned 1 exit status
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  /home/pi/esp/esp-idf/tools/cmake/project.cmake:311 (__project)
  CMakeLists.txt:11 (project)

-- Configuring incomplete, errors occurred!
See also "/home/pi/8-channel/build/CMakeFiles/CMakeOutput.log".
See also "/home/pi/8-channel/build/CMakeFiles/CMakeError.log".
cmake failed with exit code 1

I can confirm that v4.3.1 works on Debian 11 (bullseye). v4.3.2 (stable) doesn't work and yields the same issue as above.

I also confirm that v4.3.1 (esp-2021r1-8.4.0) works on Raspberry Pi 4 (2 GB model) with Raspberry Pi OS 32 bit (based on Debian 11). However, IDF v4.4 and v4.3.1 do NOT work, for the same issue as described as OP. I also investigated whether said file was present and it was.
NOTE: For my project's purposes, I am currently using IDF v4.2 for better compatibility with a couple of Arduino modules.

My heart goes out to all those waiting for this issue to be fixed. I have shed many a tear and wept daily since discovering this unfortunate problem. This issue is the source of persistent pain and great suffering and it will be a day of great joy and celebration when the issue is resolved.

All the weeping due to this unfortunate issue resulted me having in chronic dehydration condition. However, what I have discovered is that ESP-IDF v4.4 and gcc do appear to work as expected for the ESP32 on a Raspberry Pi 4 if the 64-bit version of Raspberry Pi OS is used. Up until now I had been using the 32-bit version of Raspberry Pi OS as the 64-bit version was still in beta. This is no longer the case and the first non-beta 64-bit version of Raspberry Pi OS was released recently so I gave it a try.
 Smallest app partition is 0x100000 bytes. 0xd68d0 bytes (84%) free.
[2/4] Performing build step for 'bootloader'
[1/1] cd /home/pi/src/hello_world/build/bootloader/esp-idf/esptool_py && /home/pi/.espressif/python_env/idf4.4_py3.9_env/bin/python /home/pi/esp/esp-idf/components/partition_table/check_sizes.py --offset 0x8000 bootloader 0x1000 /home/pi/src/hello_world/build/bootloader/bootloader.bin
Bootloader binary size 0x62b0 bytes. 0xd50 bytes (12%) free.

Project build complete. To flash, run this command:
/home/pi/.espressif/python_env/idf4.4_py3.9_env/bin/python ../../esp/esp-idf/components/esptool_py/esptool/esptool.py -p (PORT) -b 460800 --before default_reset --after hard_reset --chip esp32  write_flash --flash_mode dio --flash_size detect --flash_freq 40m 0x1000 build/bootloader/bootloader.bin 0x8000 build/partition_table/partition-table.bin 0x10000 build/hello_world.bin
or run 'idf.py -p (PORT) flash'
pi@raspberrypi:~/src/hello_world $

idf.py -p /dev/ttyUSB0 flash functions as expected:
pi@raspberrypi:~/src/hello_world $ idf.py -p /dev/ttyUSB0 flash
Executing action: flash
Running ninja in directory /home/pi/src/hello_world/build
Executing "ninja flash"...
[1/5] cd /home/pi/src/hello_world/buil.../src/hello_world/build/hello_world.bin
hello_world.bin binary size 0x29730 bytes. Smallest app partition is 0x100000 bytes. 0xd68d0 bytes (84%) free.
[2/5] Performing build step for 'bootloader'
[1/1] cd /home/pi/src/hello_world/build/bootloader/esp-idf/esptool_py && /home/pi/.espressif/python_env/idf4.4_py3.9_env/bin/python /home/pi/esp/esp-idf/components/partition_table/check_sizes.py --offset 0x8000 bootloader 0x1000 /home/pi/src/hello_world/build/bootloader/bootloader.bin
Bootloader binary size 0x62b0 bytes. 0xd50 bytes (12%) free.
[2/3] cd /home/pi/esp/esp-idf/componen...nents/esptool_py/run_serial_tool.cmake
esptool.py esp32 -p /dev/ttyUSB0 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 40m --flash_size 4MB 0x1000 bootloader/bootloader.bin 0x10000 hello_world.bin 0x8000 partition_table/partition-table.bin
esptool.py v3.2-dev
Serial port /dev/ttyUSB0
Connecting....
Chip is ESP32-PICO-D4 (revision 1)
Features: WiFi, BT, Dual Core, Embedded Flash, Coding Scheme None
Crystal is 40MHz
MAC: d8:a0:1d:40:78:d8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00007fff...
Flash will be erased from 0x00010000 to 0x00039fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Compressed 25264 bytes to 15785...
Writing at 0x00001000... (100 %)
Wrote 25264 bytes (15785 compressed) at 0x00001000 in 0.7 seconds (effective 277.0 kbit/s)...
Hash of data verified.
Compressed 169776 bytes to 89622...
Writing at 0x00010000... (16 %)
Writing at 0x0001afdf... (33 %)
Writing at 0x00020758... (50 %)
Writing at 0x00025fa1... (66 %)
Writing at 0x0002e5b5... (83 %)
Writing at 0x00036945... (100 %)
Wrote 169776 bytes (89622 compressed) at 0x00010000 in 2.5 seconds (effective 538.7 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 103...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (103 compressed) at 0x00008000 in 0.0 seconds (effective 524.3 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
Done
pi@raspberrypi:~/src/hello_world $

idf.py -p /dev/ttyUSB0 monitor functions as expected:
pi@raspberrypi:~/src/hello_world $ idf.py -p /dev/ttyUSB0 monitor
Executing action: monitor
Running idf_monitor in directory /home/pi/src/hello_world
Executing "/home/pi/.espressif/python_env/idf4.4_py3.9_env/bin/python /home/pi/esp/esp-idf/tools/idf_monitor.py -p /dev/ttyUSB0 -b 115200 --toolchain-prefix xtensa-esp32-elf- --target esp32 --revision 0 /home/pi/src/hello_world/build/hello_world.elf -m '/home/pi/.espressif/python_env/idf4.4_py3.9_env/bin/python' '/home/pi/esp/esp-idf/tools/idf.py' '-p' '/dev/ttyUSB0'"...
--- idf_monitor on /dev/ttyUSB0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6604
ho 0 tail 12 room 4
load:0x40078000,len:14780
load:0x40080400,len:3792
0x40080400: _init at ??:?

entry 0x40080694
I (29) boot: ESP-IDF v4.4 2nd stage bootloader
I (29) boot: compile time 23:33:05
I (29) boot: chip revision: 1
I (32) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (39) boot.esp32: SPI Speed      : 40MHz
I (44) boot.esp32: SPI Mode       : DIO
I (48) boot.esp32: SPI Flash Size : 4MB
I (53) boot: Enabling RNG early entropy source...
I (58) boot: Partition Table:
I (62) boot: ## Label            Usage          Type ST Offset   Length
I (69) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (77) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (84) boot:  2 factory          factory app      00 00 00010000 00100000
I (92) boot: End of partition table
I (96) boot_comm: chip revision: 1, min. application chip revision: 0
I (103) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=07784h ( 30596) map
I (122) esp_image: segment 1: paddr=000177ac vaddr=3ffb0000 size=02340h (  9024) load
I (126) esp_image: segment 2: paddr=00019af4 vaddr=40080000 size=06524h ( 25892) load
I (141) esp_image: segment 3: paddr=00020020 vaddr=400d0020 size=14a40h ( 84544) map
I (172) esp_image: segment 4: paddr=00034a68 vaddr=40086524 size=04c84h ( 19588) load
I (180) esp_image: segment 5: paddr=000396f4 vaddr=50000000 size=00010h (    16) load
I (186) boot: Loaded app from partition at offset 0x10000
I (186) boot: Disabling RNG early entropy source...
I (201) cpu_start: Pro cpu up.
I (201) cpu_start: Starting app cpu, entry point is 0x40080fe8
0x40080fe8: call_start_cpu1 at /home/pi/esp/esp-idf/components/esp_system/port/cpu_start.c:156

I (0) cpu_start: App cpu up.
I (215) cpu_start: Pro cpu start user code
I (215) cpu_start: cpu freq: 160000000
I (215) cpu_start: Application information:
I (219) cpu_start: Project name:     hello_world
I (225) cpu_start: App version:      1
I (229) cpu_start: Compile time:     Feb 10 2022 23:32:46
I (235) cpu_start: ELF file SHA256:  5e34838f30b80de0...
I (241) cpu_start: ESP-IDF:          v4.4
I (246) heap_init: Initializing. RAM available for dynamic allocation:
I (253) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (259) heap_init: At 3FFB2C28 len 0002D3D8 (180 KiB): DRAM
I (266) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (272) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (278) heap_init: At 4008B1A8 len 00014E58 (83 KiB): IRAM
I (286) spi_flash: detected chip: gd
I (289) spi_flash: flash io: dio
I (294) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
Hello world!
This is esp32 chip with 2 CPU core(s), WiFi/BT/BLE, silicon revision 1, 4MB embedded flash
Minimum free heap size: 293268 bytes
Restarting in 10 seconds...
Restarting in 9 seconds...
Restarting in 8 seconds...
Restarting in 7 seconds...
Restarting in 6 seconds...
Restarting in 5 seconds...
Restarting in 4 seconds...
Restarting in 3 seconds...
Restarting in 2 seconds...
Restarting in 1 seconds...
Restarting in 0 seconds...
Restarting now.
ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6604
ho 0 tail 12 room 4
load:0x40078000,len:14780
load:0x40080400,len:3792
0x40080400: _init at ??:?

entry 0x40080694
I (29) boot: ESP-IDF v4.4 2nd stage bootloader
...

So I am now happy 😄
I guess it's only the 32-bit Xtensa compilers that are broken the 64-bit compilers appear to work.

all, the fix for this issue should be available in master soon, i will keep an eye on updates, and post more information soon

Is there any more information available yet?

@csBlueChip We are on our way to get a new release of the toolchain. It is a big release with updating GCC and newlib versions. There is a chance to get a fix for the issue too

Thank you. After 3 years of waiting, it is good to know that Espressif are "on their way" to releasing a devkit which will unlock the USB features of the chip, and there is "a chance" that it will work :)

Any new updates on this? I installed 64 bit RPi OS recently, but I have yet to migrate my whole toolchain (which is based on a modified MicroPython codebase). I would like to update to IDF 4.4 (for ESP32 S3 support), but I am unable. I have a working executable generated from IDF 4.2.0, but I would prefer to use IDF 4.4.

Hi @RSC-Games ! The new toolchain with ARM*@linux fixes will come to master branch already on these days. Also the fixes will be ported to v4.4, but I'm not sure about ETA

Hi, I have got also this problem on v4.4 with Raspberry Pi 4.
As I read, the v4.4. should be supported on Raspberry Pi 4, but it is still not.
Can you please keep this issue open until the fix will be available?

@MMucka  right, for v4.4 we can open this

What I have done:
cd ~/esp/esp-idf
git fetch
git checkout remotes/origin/release/v4.4
git submodule update --init --recursive
~/esp/esp-idf/install.sh esp32c3
. ~/esp/esp-idf/export.sh

but in tools, there is still old gcc
ls ~/.espressif/tools/riscv32-esp-elf
esp-2021r2-patch3-8.4.0

So I tried to apply changes from https://github.com/espressif/esp-idf/commit/bf43076c044a58429ebd90ac508e32dd82321af1 for tools/tools.json and tools/toolchain_version.mk, but I have still problem to build simple test program.

I have not verified that the latest commit works, because I migrated my toolchain to rpi 4 64 bit on Monday. I'll have to dig out my 32 bit sd card.

Thanks for reporting, fix is available at https://github.com/espressif/esp-idf/commit/00077545bf23134379133cfd979aaad35d5f3552, feel free to reopen.

Is this fix not available in the latest 5.1.2?
I still get:
&& /config/.esphome/platformio/packages/toolchain-xtensa-esp32/bin/xtensa-esp32-elf-gcc -mlongcalls -Wno-frame-address   CMakeFiles/cmTC_d0ead.dir/testCCompiler.c.obj  -o cmTC_d0ead   && :
/config/.esphome/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /config/.esphome/platformio/packages/toolchain-xtensa-esp32/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: error loading plugin: /config/.esphome/platformio/packages/toolchain-xtensa-esp32/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/liblto_plugin.so: cannot open shared object file: No such file or directory


Update to Oracle Docs for 7.4 to 7.6 support

Stole the columns from the RH docs
Updated the notes to match those on the oracle page

@lizap

UEK5 supports SRIOV (Accelerated Networking) and has been released with Oracle Linux 7.6 and up. We should add a column for that.

@lizap can we merge this?


Viewer works on dataset landing page but not on full viewer page: UnexpectedApiError

The viewer works on the dataset landing page; see for example: https://huggingface.co/datasets/hyperdemocracy/us-congress-bills

However it raises UnexpectedApiError  on the full viewer page; see: https://huggingface.co/datasets/hyperdemocracy/us-congress-bills/viewer/default/train

Fix Hub issue: https://huggingface.co/datasets/hyperdemocracy/us-congress-bills/discussions/1
CC: @galtay @lhoestq

This is because the row group size of the parquet export of the dataset is too big for the API.
So we need to either modify maxRowGroupByteSizeForCopy (currently 500_000_000) and/or maxArrowDataInMemory (currently 300_000_000) to make them compatible.
I think it's fine to lower maxRowGroupByteSizeForCopy to 300_000_000 and re-run the config-parquet-and-info job for this dataset.
I can take care of this next week when I'm back, or feel free to do it @albertvillanova

Also reported in: https://huggingface.co/datasets/RiddleHe/commonsense-baseline/discussions/1

I can take care of the small modification you proposed, @lhoestq.


Buffer storage temperature

It would be really helpful for energy management automations to get the top and bottom buffer storage temperature, for example to use it for overheating commands during high solar production.
The data is available local in the SensoComfort unit menu

This would be great!

Are these values shown in the app somewhere? Or can you see these values when you run the generate test data service?

allSTORE with VR921 provides me sensors:

sensor.myvaillant_top_dhw_cylinder_temperature
sensor.myvaillant_bottom_dhw_cylinder_temperature
sensor.myvaillant_top_central_heating_cylinder_temperature
sensor.myvaillant_bottom_central_heating_cylinder_temperature

I could not find these values anywhere in the myVaillant application.


FAQ

1. How do you set the application icon in for golang binary program?

https://stackoverflow.com/questions/25602600/how-do-you-set-the-application-icon-in-golang

2. How to make golang compiled binary file more small ?

https://stackoverflow.com/questions/28576173/reason-for-huge-size-of-compiled-executable-of-go

# add -ldflags -s -w
go build -ldflags "-s -w"
# using upx
upx -9 target.bin.exe


Set 7.54.0 as current_milestone

Set current_milestone to 7.54.0 so the automatic milestone action works properly on the main branch.

/merge


Getting wrong value from parsing time and date

Description of the Issue and Steps to Reproduce:
var obj = {
  "startDate": "17/12/1",
  "startTime": "12:40"
}
obj.startDateTime = moment(obj.startDate+"-"+obj.startTime, "YY-MM-DD-HH-mm").toISOString();
console.log(obj.startDateTime);// "2018-01-08T23:00:00.000Z"

The output is totally wrong!
I managed to get it to work by changing "-" to " " and in the format string "-" to " ":
obj.startDateTime = moment(obj.startDate+" "+obj.startTime, "YY-MM-DD HH-mm").toISOString();

Environment:
Chrome 59.0.3071.115 (Official Build) (64-bit) on Ubuntu 16.0.4
If you are reporting an issue, please run the following code in the environment you are using and include the output:
console.log( (new Date()).toString()) // "2018-01-08T23:00:00.000Z"
console.log((new Date()).toLocaleString()) // 8/10/2017, 2:49:34 PM
console.log( (new Date()).getTimezoneOffset()) // -120
console.log( navigator.userAgent) // Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
console.log(moment.version) // 2.9.0

Ensure your issue is isolated to moment. Issues involving third party tools will be closed unless submitted by the tool's author/maintainer.

Your string is "17/12/1-12:40" but your format is "YY-MM-DD-HH-mm", which looks nothing like that. Without having debugged it, my guess on what's happening is that when when you put in a space, you somehow managed to convince Moment's very forgiving parsing to do what you were hoping. But in general, you shouldn't depend on Moment being able to figure out what format you really meant.
My advice is to use strict parsing (i.e. add a true third argument) and provide a format string that matches the format of your input.

What do you mean with "nothing like that", the documentation says i should be able to use any(like - and /) character instead of "-".


queue blocks token loader AGPUSH-1512

Use address-full-policy=FAIL instead of PAGE,
means transactions will fail and they will be retried after configured delay,
instead of paging to disk and eventually failing on running out of disk space.
And upgrade to WildFly 10.
https://issues.jboss.org/browse/AGPUSH-1521

I've tested with WildFly 10.0.0.CR5 and it Android push notification was delivered to real device

There are test failures, I will look into them shortly, but in the meantime, this can be tested manually

:eyes:
btw. why WF-10-CR5? Final was released two month ago :)

@matzew yea, just my commits are 2 months around :-)

@lfryc tests are failing, locally and on Travis

@matzew ok, all comments were incorporated :recycle:

@lfryc :tada: thanks !
I did remove the unsed bits myself, can you follow up on: https://github.com/aerogear/aerogear-unifiedpush-server/pull/694#discussion_r56679147
in a different/new PR?


How can i use llvm-slicing to split the project which includes multiple source files

Hi,  I wanna ask how can i use your framework to split a project which has multiple source files.
For example, under the directory of source, there are several programs. Just take barcode for example, there are 6 directories and 221 files. Although not all of them can be sliced with llvm-slicing, there are also mutliple c implementation should be splitted.
I want to know is it possilbe to use llvm-slicing directly for this barcode program. Or should I write a small script which utilizes llvm-slicing $name repeatedly?

Sorry, llvm-slicing now is not used directly for a barcode project with multiple source files, since it is just an IR slicer. Therefore, for a multi-programs project, you can first compile these programs into corresponding IRs, then combine them into a single IR with the LLVM tool llvm-link, and finally use llvm-slicing to slice this project.


Fix build with recent sphinx

app.info() was deprecated on Jan 4, 2017 (sphinx-doc/sphinx#3267), and removed as of Sphinx 2.0.0.
libuv 1.28.0 currently fails to build with Sphinx 2.0.1: https://github.com/Homebrew/homebrew-core/pull/38978

Other than building, does itstill  generate proper man pages?

It appears to work fine, yes.

Landed in https://github.com/libuv/libuv/commit/68173cc8026a3eb1a90dcce19e16011ba613d599. Thanks!


JSON Parse Error on GET

Hi,
I am getting a JSON Error for any type of request that I'm making. I have tested the same on C9 as well as my local dev machine. I also tried more than one woocommerce installation yet the issue still persists?
/Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/json-2.0.2/lib/json/common.rb:156:in `parse': 743: unexpected token at '{"code":"woocommerce_rest_authentication_error","message":"Invalid timestamp.","data":{"status":401}}' (JSON::ParserError)
	from /Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/json-2.0.2/lib/json/common.rb:156:in `parse'
	from /Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/httparty-0.14.0/lib/httparty/parser.rb:118:in `json'
	from /Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/httparty-0.14.0/lib/httparty/parser.rb:138:in `parse_supported_format'
	from /Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/httparty-0.14.0/lib/httparty/parser.rb:105:in `parse'
	from /Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/httparty-0.14.0/lib/httparty/parser.rb:67:in `call'
	from /Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/httparty-0.14.0/lib/httparty/request.rb:345:in `parse_response'
	from /Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/httparty-0.14.0/lib/httparty/request.rb:297:in `block in handle_response'
	from /Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/httparty-0.14.0/lib/httparty/response.rb:25:in `parsed_response'
	from /Users/nikhilgoyal/.rvm/gems/ruby-2.3.3@nik/gems/httparty-0.14.0/lib/httparty/response.rb:74:in `respond_to?'
	from test.rb:20:in `puts'
	from test.rb:20:in `puts'
	from test.rb:20:in `<main>'

UPDATE:
After testing continuously I found that this issue is being caused by the SMART COUPONS (https://woocommerce.com/products/smart-coupons/) plugin.
Also I would like to add that Woocommerce API is working fine in a REST client like POSTMAN.
Also I would like to add that Woocommerce API when working with Ruby REST Client like https://github.com/rest-client/rest-client
The main problem appears to be how HTTParty is using JSON to parse. I think thats the issue. I am working on a way around this to make this work. In the meantime I would request the plugin author to shed some light, as I am not a very well versed programmer.

#35

JSON Parse Error on GET

This error is generally caused by some PHP warning that you site should not be displayed since it is a security flaw.
Just fix all PHP warning and notices that will start work again.


swift: cast to the appropriate type

This fixes an error from the swift compiler:
error: cannot convert value of type 'UInt32' to expected argument type 'UInt'

@swift-ci please test

Please test with the following PRs:
apple/swift-corelibs-libdispatch#400
@swift-ci please test