DNS for service alias to external service sometimes unresolvable

We're using different stacks in our solution. As an example, we have a stack called platform that points on external services, the internal stacks that need external services use service aliases to ease the management when an external service is changed.
However, sometimes we get errors from our applications with the error "DNS unresolvable"

Useful
Info

Versions
Rancher v1.0.0 Cattle: v0.159.2 UI: v0.100.3

Access
Disabled

Route
authenticated.project.help

@eguswes could you share docker-compose.yml of your stack? And point which resolution path from this compose file not working. It would help us to reproduce the issue in house.

Here it is, I’ve cleaned it from a number of personal services. My theory is, it appears when a service breaks down, maybe the DNS service is disrupted by frequent renewals/restarts from a failing service.
httpd:
log_driver: ''
labels:
io.rancher.container.pull_image: always
tty: true
log_opt: {}
image: httpd:2.4
volumes:

jobs:/var/opt/jobs
stdin_open: true
kafka:
external_links:
platform/kafka:kafka
image: rancher/dns-service

kafka:
image: rancher/external-service
/Gustaf
From: Alena Prokharchyk<EMAIL_ADDRESS>Sent: den 22 april 2016 18:50
To: rancher/rancher
Cc: Gustaf Westin; Mention
Subject: Re: [rancher/rancher] DNS for service alias to external service sometimes unresolvable (#4517)
@egusweshttps://github.com/eguswes could you share docker-compose.yml of your stack? And point which resolution path from this compose file not working. It would help us to reproduce the issue in house.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/rancher/rancher/issues/4517#issuecomment-213506991

I used your docker-compose.yml using v1.2.0-pre2-rc3 and did not have any issues with dns resolution.
@eguswes Are you still having this issue with our later versions?

The problem occurred when one service was failing or something changed. Intermittent, maybe one in a hundred/thousand. That’s the big problem with intermittent problems, you just test them and can reproduce them straight away…

Closing this out as it sounds like you rooted the problem to a faulty container.


Add 'map' for container logs for CentOS 8

By default, if the systemdLogPath variable is unchanged from the
default of /var/log/journal in the rancher-logging chart, the Fluentd
container will create the /var/log/journal directory[1]. Once it is
created, systemd will treat the Storage method as "persistent" even if
the Storage setting is unchanged[2]. Since /var/log is mounted by the
Pod, then on an SELinux-enabled/enforcing system, the /var/log/journal
directory will get relabeled to container_log_t. On CentOS 8, the
rke_logreader_t domain needs the 'map' permission to read these files.
This does not seem to be a requirement for CentOS 7, so this change only
updates the policy for CentOS 8.
[1] https://github.com/rancher/fluentd/blob/0c484d7beeb67f7efbdfc87727989b5061b89140/package/run.sh
[2] https://www.freedesktop.org/software/systemd/man/journald.conf.html#Storage=

Closing in favor of fixing this in the logging chart


Would you be interested in a pull request ?

Hello,
First of all thanks for this project, it's saving me a lot of trouble while using schema less databases.
I have extended the project with some additions to make more useful to me and i was wondering if you'd be interested in having those added to the project :+1:

A generate function, that generate an empty array from a model. => Generating a skeleton before inserting data.
A casting function that casts the types of the fields according the a schema => preventing cast related errors  eg.  "1" <> 1

If you are indeed interested, let me know i'll send a pull request.

PRs are always welcome


Compiling Essentia with Gaia supports gives error

I'm trying to compile Essentia with Gaia, to use this plugin on Windows. I'm actually having an endless amount of issues even when compiling Gaia, but after a couple hours trying I managed to compile it. Essentia though spits out a ton of errors when compiling, and I'm sadly not competent enough to have found a solution. It would be awesome to have some precompiled binaries, but in case this won't be possible for Windows, here's the Dockerfile I used to compile it, so it can be replicable in the case someone might want to help me.
FROM ubuntu:20.04
ARG ESSENTIA_VERSION=2.1_beta5

ENV LANG C.UTF-8

RUN apt-get update \
    && apt-get -y upgrade \
    && DEBIAN_FRONTEND=noninteractive apt-get install -y \
       python3-matplotlib python3-numpy python3-six python3-yaml \
       libfftw3-3 libyaml-0-2 libtag1v5 libsamplerate0 \
       libavcodec58 libavformat58 libavutil56 libavresample4 \
    && rm -rf /var/lib/apt/lists/*

RUN apt-get update \
    && apt-get install -y build-essential python3-dev git \
    libfftw3-dev libavcodec-dev libavformat-dev libavresample-dev \
    libsamplerate0-dev libtag1-dev libyaml-dev libeigen3-dev \
    g++-mingw-w64 \
    libchromaprint-dev swig

# Gaia
RUN mkdir /essentia && cd /essentia && git clone https://github.com/MTG/gaia.git \
    && DEBIAN_FRONTEND=noninteractive apt-get install -y software-properties-common \
    && add-apt-repository ppa:rock-core/qt4 && apt-get -y update \
    && DEBIAN_FRONTEND=noninteractive apt-get install -y libqt4-dev libqtwebkit-dev
RUN apt install -y qt5-qmake qtbase5-dev qtbase5-dev-tools libqt5svg5-dev libqt5webenginewidgets5 libqt5webchannel5-dev qtwebengine5-dev

RUN cd /usr/local/include && ln -sf eigen3/Eigen Eigen && ln -sf eigen3/unsupported unsupported && cd /usr/include && ln -sf eigen3/Eigen Eigen && ln -sf eigen3/unsupported unsupported \
    && cd /essentia/gaia && python3 waf configure --with-python-bindings \
    && python3 waf && python3 waf install && ldconfig

# Essentia
RUN apt-get -y install build-essential libeigen3-dev libyaml-dev libfftw3-dev libavcodec-dev libavformat-dev libavutil-dev libswresample-dev libsamplerate0-dev libtag1-dev libchromaprint-dev wget curl \
    python3-dev python3-numpy-dev python3-numpy python3-yaml python3-six cmake gcc-multilib
RUN cd /essentia && git clone https://github.com/MTG/essentia.git \
    && cd /essentia/essentia && git checkout "v$ESSENTIA_VERSION" && ./packaging/build_3rdparty_static_win32.sh \
    && python3 waf configure --with-python --with-gaia --with-examples --with-static-examples --cross-compile-mingw32 --with-vamp \
    && python3 waf && python3 waf install && ldconfig \
    &&  apt-get remove -y build-essential libyaml-dev libfftw3-dev libavcodec-dev \
        libavformat-dev libavutil-dev libavresample-dev python-dev libsamplerate0-dev \
        libtag1-dev libeigen3-dev libchromaprint-dev swig \
    && apt-get autoremove -y \
    && apt-get clean -y

ENV PYTHONPATH /usr/local/lib/python3/dist-packages

WORKDIR /essentia

The original Dockerfile is from a gist I found somewhere, but I can't find it anymore lol
last error:
464.1 make[2]: Entering directory '/essentia/essentia/packaging/win32_3rdparty/tmp/chromaprint-v1.4.3'
464.2 [  5%] Building CXX object src/CMakeFiles/chromaprint_objs.dir/fft_lib_fftw3.cpp.obj
464.2 cd /essentia/essentia/packaging/win32_3rdparty/tmp/chromaprint-v1.4.3/src && /usr/bin/i686-w64-mingw32-g++  -DCHROMAPRINT_NODLL -DHAVE_CONFIG_H -D_SCL_SECURE_NO_WARNINGS -D_USE_MATH_DEFINES -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS @CMakeFiles/chromaprint_objs.dir/includes_CXX.rsp -std=c++11 -Wall -O3 -DNDEBUG   -o CMakeFiles/chromaprint_objs.dir/fft_lib_fftw3.cpp.obj -c /essentia/essentia/packaging/win32_3rdparty/tmp/chromaprint-v1.4.3/src/fft_lib_fftw3.cpp
464.5 In file included from /usr/share/mingw-w64/include/sec_api/stdlib_s.h:9,
464.5                  from /usr/share/mingw-w64/include/stdlib.h:768,
464.5                  from /usr/lib/gcc/i686-w64-mingw32/9.3-win32/include/c++/cstdlib:75,
464.5                  from /usr/lib/gcc/i686-w64-mingw32/9.3-win32/include/c++/bits/stl_algo.h:59,
464.5                  from /usr/lib/gcc/i686-w64-mingw32/9.3-win32/include/c++/algorithm:62,
464.5                  from /essentia/essentia/packaging/win32_3rdparty/tmp/chromaprint-v1.4.3/src/utils.h:15,
464.5                  from /essentia/essentia/packaging/win32_3rdparty/tmp/chromaprint-v1.4.3/src/fft_lib_fftw3.h:10,
464.5                  from /essentia/essentia/packaging/win32_3rdparty/tmp/chromaprint-v1.4.3/src/fft_lib_fftw3.cpp:4:
464.5 /usr/include/stdlib.h:62:5: error: conflicting declaration ‘typedef struct div_t div_t’
464.5    62 |   } div_t;
464.5       |     ^~~~~

Hi @Bestfast,
Essentia compilation issues should be reported on their repo.
I cannot help you on this. This is totally outside of my knowledge domain.

@Bestfast have you seen the hint in xtractor's resdme sbout precompiled packages for Linux?
https://github.com/doctorfree/mpplus-essentia


yarn start fails: cannot find module 'react-static/babel-preset.js'

Are you reporting a bug?
Yes
Environment

react-static -V: 6.0.18
node -v: v10.14.2
npm -v: 6.4.1
Operating system: macOS 10.14.2
Browser and version (if relevant):

Steps to Reproduce the problem

Create a new project:

$ react-static create

? What should we name this project? my-blog
? Select a template below... basic
=> Creating new react-static project...

Start the dev server:

$ cd my-blog
$ yarn start
yarn run v1.12.3
$ react-static start
  Error: Cannot find module 'react-static/babel-preset.js' from '/path/to/my-blog'
  [...]
  TypeError: Cannot read property 'DIST' of undefined

  - start.js:85 _callee2$
    [my-blog]/[react-static]/lib/commands/start.js:85:69

Template is installing the wrong version of react-static. If you bump the version in package.json, it fixes the issue.

Like like we need to fix the template.
On Sat, Dec 22, 2018 at 8:51 PM Matthew Sisley<EMAIL_ADDRESS>wrote:

Template is installing the wrong version of react-static. If you bump the
version in package.json, it fixes the issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/913#issuecomment-449612510,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCTpsjLbEfyzKvwi3drp-i2udOxUSks5u7v3NgaJpZM4ZfjLE
.

The package.json is actually fine as it says
"react-static": "^6.0.2"

It's more that the template also comes with a yarn.lock file
<EMAIL_ADDRESS>  version "6.0.2"

So deleting yarn.lock (and node_modules) then re-running yarn gets the latest version.
Maybe templates shouldn't have a yarn.lock file at all?

Yeah, tanner these lock files are great for corporations and company projects. But I’ve had tons of headaches with the my code not working because of lock files  still installing universal version 2.
It has definitely gotten better now that we don’t have all those examples, but something to consider

I'm fine not committing the lock files.
On Sun, Dec 23, 2018 at 2:32 PM Zack Jackson<EMAIL_ADDRESS>wrote:

Yeah, tanner these lock files are great for corporations and company
projects. But I’ve had tons of headaches with the my code not working
because of lock files still installing universal version 2.
It has definitely gotten better now that we don’t have all those examples,
but something to consider
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/913#issuecomment-449664472,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCcsvU_lddFf4yjBJ5zcqBE1z3MsZks5u7_aHgaJpZM4ZfjLE
.

Just need a PR to fix the package.json

Fixed in #917


maxquant: checks on exp. design template + documentation + bugfix for identifier parse rules

fixes #392 and #393. For discussion on it and a demonstration of my magic git skills see #394

Merci!

Cool. Thanks, installed it right away. Don't worry about git, your approach is very common: https://xkcd.com/1597/


Update typescript peer dependency (Angular 7, TS 3.1)

<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

I'm also running into this., Are there any known workarounds or timeline for update of this amazing angular integration?

We're also running into this issue. We've kept TS version but really would like to update all packages...

It's not live yet, but you could have a go with the current alpha - install ng2-semantic-ui@next. It contains a few fixes for various issues & an update to support a new S-UI. Let me know how you get on if you do install it!

any news?

It worked for me with 0.10.0-alpha.6 over 0.9.7

How extensive are the changes required to make this TS3/NG7 compatible? It'd be nice to have <IP_ADDRESS> for production use until 0.10.0 is considered live


Use patched version of xtra

This version includes a patch that logs long running message handlers.
That should be useful in detecting deadlocks in our software.

bors r+


Cannot build with Intel MKL include dirs.

Environment
toml++ version and/or commit hash:
Submodule : TOML++ v3.3.0 (c635f21)

Compiler:
$ c++ --version
c++ (GCC) 13.2.1 20230801

C++ standard mode:
set(CMAKE_CXX_STANDARD 17)

Target arch:
$ uname -a
Linux copak 6.4.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 x86_64 GNU/Linux

Library configuration overrides:
none
Relevant compilation flags:
After having installed intel-oneapi-mkl:
-I/opt/intel/oneapi/compiler/latest/linux/compiler/include

Describe the bug
The library compiles fine, until I add the above flag (because the project otherwise uses MKL), then I get:
In file included from ./extern/toml++/include/toml++/toml.h:36,
                 from ./main.cpp:1:
./extern/toml++/include/toml++/impl/forward_declarations.h:38:15: error: ‘FLT_RADIX’ was not declared in this scope
   38 | static_assert(FLT_RADIX == 2, TOML_ENV_MESSAGE);
      |               ^~~~~~~~~

Steps to reproduce (or a small repro code sample)
main.cpp
#include <toml++/toml.h>
int main(){};

CMakeLists.txt
cmake_minimum_required(VERSION 3.20..3.22)

project(TomlAndMkl LANGUAGES CXX)

set(CMAKE_CXX_STANDARD 17)

add_library(toml++ INTERFACE)
target_include_directories(toml++ INTERFACE "./extern/toml++/include")

add_executable(main main.cpp)

#-------------------------------------------------------------------------------
# Works if I remove this snippet.
find_package(PkgConfig REQUIRED)
pkg_search_module(MKL mkl-dynamic-lp64-iomp)
target_include_directories(main PRIVATE ${MKL_INCLUDE_DIRS})
#-------------------------------------------------------------------------------

target_link_libraries(main PRIVATE toml++)

I'm not exactly sure what the error deeply means here. FWIU the FLT_RADIX macro is (re-)defined within intel/oneapi/compiler/latest/linux/compiler/include/float.h:75 to:
#undef  FLT_RADIX
#define FLT_RADIX   2

but I'm not confident what it means or why this would result in "undeclared FLT_RADIX". I'm happy to learn more ^ ^"

Hmnmn, that is weird! If float.h is undefining and redefining FLT_RADIX immediately, nothing should be amiss from toml++'s perspective. I suppose the MKL package does something weird with FLT_RADIX and there's some include-order shenanigans going on with the CMake config. I have no idea what to do about it, though. This seems like a bug in the MKL headers.

Can you try replacing toml++'s use of FLT_RADIX with std::numeric_limits<double>::radix? i.e. change this line in toml++/impl/forward_declarations.hpp:
static_assert(FLT_RADIX == 2, TOML_ENV_MESSAGE);

to this:
static_assert(std::numeric_limits<double>::radix == 2, TOML_ENV_MESSAGE);

If that doesn't work, you can #define TOML_DISABLE_ENVIRONMENT_CHECKS somewhere and it should work OK. The float radix is only used to check that the local environment is compatible with the TOML spec, and isn't actually used anywhere else.

Replacing the macro invocation by std::*::radix does fix the problem. And indeed I should maybe report this to intel-mkl. It seems that they broke something ^ ^" Thank you for swift support, and feel free to close then. I'll just need to figure out where to find intel now ^ ^"

you can #define TOML_DISABLE_ENVIRONMENT_CHECKS

I think I'll go for some more targetted hack instead:
#ifndef FLT_RADIX
#define FLT_RADIX std::numeric_limits<float>::radix
#endif

.. but I just want to get rid of one confusion first: do you expect FLT_RADIX to be std::numeric_limits<float>::radix or std::numeric_limits<double>::radix ? (because it seems that DBL_RADIX also exists)

Wop, thank you for spotting the snag! ^ ^"

FWIW it seems that the error does not occur.. provided you opt into using Intel's proprietary compiler icpx :\

Ah, right, so I guess MKL assumes you're using that compiler and does #undef FLT_RADIX because it knows that the compiler has some special behaviour in that area.
That's... unfortunate 😅


Code coverage

The tricky part was that some lines of code are executed only when running tests for a specific locale.

Which is done by running xcodebuild multiple times. Luckily there is a tool to merge multiple profdata files into one.


Update README.rst

Just a drive-by typo fix but think you meant django-resto rather than django-sesame here ;)

Copy-paste FTL. Thanks!


Fix some styling issues

Hey @RomRider, thanks for contributing 🚀
Can you explain why this is necessary?

Sure.
That's without display: block:

That's with display block:

And the configuration (using decluttering-card, thus the [[xxxx]]):
    type: custom:vertical-stack-in-card
    cards:
      - type: horizontal-stack
        cards:
          - type: custom:button-card
            size: '[[size]]'
            entity: '[[entity]]'
            template: cover_up
          - type: custom:button-card
            size: '[[size]]'
            entity: '[[entity]]'
            template: cover_stop
          - type: custom:button-card
            size: '[[size]]'
            entity: '[[entity]]'
            template: cover_down
      - type: custom:card-modder
        extra_styles: >
          .card-content {
            padding: 0px 0px
          }
        card:
          type: entities
          entities:
            - type: custom:slider-entity-row
              entity: '[[entity]]'
              full_row: true
              hide_state: true
      - type: custom:button-card
        name: '[[name]]'
        template: cover_name

Thanks, merged

Thanks a lot!
Is there any way that you could release a version with this PR so that custom_updater and hacs could pick it up? :)


Read OS and device information in Dart code

In order to better support all the different platforms we need something like the Enricher from the dotnet guys:
https://github.com/getsentry/sentry-dotnet/blob/674627baf25e24eb2634443960adece3c25aab96/src/Sentry/Internal/Enricher.cs
It's also needed in order to not go through message channels after https://github.com/getsentry/sentry-dart/issues/344 is implemented and for platforms which have no native integration.
This way we can get all the environment, OS and device information.
There are a couple ways to get some of the information:

Dart's Platform class has some information (this would also work for non Flutter projects)
https://pub.dev/packages/device_info_plus

it's sort of a dup of https://github.com/getsentry/sentry-dart/issues/262

Oh yeah, I'll close this in favor of the other one.


Set default PhysicalResourceID for all request types

Codecov Report

Merging #76 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #76   +/-   ##
=======================================
  Coverage   69.65%   69.65%
=======================================
  Files          17       17
  Lines         659      659
=======================================
  Hits          459      459
  Misses        156      156
  Partials       44       44

Impacted Files
Coverage Δ

cfn/wrap.go
90% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks!


shader_debugprintf: support new VVL-DEBUG-PRINTF message and fix VVL version check for API selection

Description
Fixes two issues that arose with Vulkan SDK 1.3.296:

Supports new VVL-DEBUG-PRINTF callback message.  Previous SDKs used WARNING-DEBUG-PRINTF or UNKNOWN-DEBUG-PRINTF.  Without this fix the debug data is not available in the UI Overlay.
Fixes my incorrect assumption that the Vulkan instance version matched the SDK version for all platforms - true on macOS but not true for Windows and Linux.  This version is used to set the API level for the sample, which is important for performance and to avoid a previous defect in the Vulkan Validation layer.  I have replaced the instance version check with a Validation Layer version check which is portable across all platforms: Win, Linux, macOS.  Without this fix, performance is poor on Windows and Linux when using Vulkan SDK 1.3.296.

Fixes #1184.
Tested on Windows 10, Manjaro Linux, and macOS Ventura using Vulkan SDKs 1.3.290 and 1.3.296.
I hope this is the last time I have to fix this.  It seems that VVL changes can easily break this sample.
General Checklist:
Please ensure the following points are checked:

[x] My code follows the coding style
[x] I have reviewed file licenses
[x] I have commented any added functions (in line with Doxygen)
[x] I have commented any code that could be hard to understand
[x] My changes do not add any new compiler warnings
[x] My changes do not add any new validation layer errors or warnings
[x] I have used existing framework/helper functions where possible
[x] My changes do not add any regressions
[x] I have tested every sample to ensure everything runs correctly
[x] This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

[x] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[x] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

If this PR contains framework changes:

[ ] I did a full batch run using the batch command line argument to make sure all samples still work properly

Sample Checklist
If your PR contains a new or modified sample, these further checks must be carried out in addition to the General Checklist:

[x] I have tested the sample on at least one compliant Vulkan implementation
[ ] If the sample is vendor-specific, I have tagged it appropriately
[x] I have stated on what implementation the sample has been tested so that others can test on different implementations and platforms
[ ] Any dependent assets have been merged and published in downstream modules
[ ] For new samples, I have added a paragraph with a summary to the appropriate chapter in the readme of the folder that the sample belongs to e.g. api samples readme
[ ] For new samples, I have added a tutorial README.md file to guide users through what they need to know to implement code using this feature. For example, see conditional_rendering
[ ] For new samples, I have added a link to the Antora navigation so that the sample will be listed at the Vulkan documentation site

Thanks @SaschaWillems for the feedback.  I am away on vacation this week, but will make the requested changes when I am back.

No idea why, but with this PR and the latest SDK (1.3.296) and in windows, this sample is now again running with less than 1 fps. Forcing it to use VK 1.2 is somehow even slower (0 or inf fps).
If I force VK 1.0 performance is fine, but I don't get any debug output.
Not sure what is happening here and why this sample is so problematic. The debug printf sample from m own samples repo works just fine no matter the api version :/

No idea why, but with this PR and the latest SDK (1.3.296) and in windows, this sample is now again running with less than 1 fps. Forcing it to use VK 1.2 is somehow even slower (0 or inf fps).

Very strange.  Can I ask you to recheck before and after this PR, but being careful with your SDK version selection and project gen/build?  I did a lot of testing with old and new SDKs on Windows 10, Linux and macOS before submitting originally.  I will go back and test again to see if I can somehow duplicate what you are seeing.

If I force VK 1.0 performance is fine, but I don't get any debug output.

Debug PrintF requires Vulkan 1.1 or later.  So no surprise that you are not getting debug output with API 1.0.

The debug printf sample from my own samples repo works just fine no matter the api version

I suspect your repo's sample relies on the instrinsic Debug PrintF capability at the shader level on Windows.  However, this is not cross-platform portable.  Whereas the Vulkan-Samples one uses the VVL version of the feature all the time.  Perhaps that is why you are seeing a difference at least on Windows.  Again, I will so back and see if I can verify this.

It also happens with the old code (before this PR). I only have SDK 1.3.296 installed.
So probably a regression in the validation layers?

Ok, I have rechecked this PR on Windows 10, and even fast-forwarded my local branch to current main HEAD just to make sure.  I am using Vulkan SDK 1.3.296.0 with my Radeon RX6600XT GPU.  My Vulkan Configurator has been reset to default settings.
Before this PR I get:

After this PR I get:

Is it possible that your Vulkan Configurator has a custom setting that is interfering with the sample?  Or possibly a difference between AMD and nVidia GPUs?  Just grasping at straws since I cannot duplicate your issue.

That would explain why it's so slow for me. I never ran that sample with the VulkanConfigurator running. That's case 2.

Thanks @asuessenbach for pointing out the missing VK_EXT_validation_features extension.  I have made a few changes that might make a difference as follows:

Moved layer settings out of the constructor, and into ShaderDebugPrintf::create_instance().  Now it will run only if the VK_EXT_layer_settings extension is available.  This part is for encapsulation only and will not change behaviour.
Added and enabled the VK_EXT_validation_features extension when the VK_EXT_layer_settings extension is not available at runtime.  This might change behaviour, but I am concerned about @asuessenbach's comment that the extension is not available on his machine.  I'm not sure how that is possible.
Fixed an incorrect string comparison operation for VK_EXT_layer_settings in [HPP]Instance::[HPP]Instance().  This was my mistake from an earlier PR.  This could have prevented proper specification of the validation layer feature settings when VK_EXT_layer_settings is active.  Again, this could change behaviour.

These changes may not be the final solution as I have observed the following when testing:

Linux (Manjaro) using Vulkan 1.2.295 (from pkg mgr) and VVL 1.3.290 (from pkg mgr): this PR works properly (good frame rate, debug data available) when running with vkconfig and without. VK_EXT_layer_settings is only available when vkconfig is active. In this case the debug data is available both in the UI and in the stdout console.  No performance issues are visible in either case.
macOS (Ventura) using Vulkan 1.2.296 with VVL 1.3.296: this PR works properly (good frame rate, debug data available) when running with vkconfig and without. VK_EXT_layer_settings is available both when vkconfig is inactive and active - this is a difference vs Linux. In the latter case (vkconfig active) the debug data is available both in the UI and in the stdout console.  No performance issues are present.  Also tested with Vulkan SDK 1.3.290 and the results are the same - no performance problems.  The only issue is that vkconfig does not appear to recognize the repeated message limit for the new VVL-* messages (vs. the previous INFO-* or WARNING-* messages, etc).  A minor issue but likely a bug.
Windows 10 using Vulkan SDK 1.2.296 with my AMD 6600XT GPU: this PR works properly (good frame rate, debug data available) when running without vkconfig only. When vkconfig is active, the sample will not start and complains about an unsupported extension during vkCreateInstance().  However, VK_EXT_layer_settings is available during enumeration when vkconfig is active. Something very strange is going on here - either a bug on the Windows side or something I do not understand.  I am not sure how VK_EXT_layer_settings can be enumerated but not supported.  See my console output in this case:

In summary:

Linux: works properly using VVL 1.3.290 with and without vkconfig.  Can't test VVL 1.3.296 since it is not yet available as a package for my Manjaro distro.
macOS: works properly using VVL 1.3.290 and 1.3.296 with and without vkconfig.
Windows 10: works properly using VVL 1.3.296 without vkconfig only.

Lastly, I thought VK_EXT_layer_settings was meant to replace and deprecate VK_EXT_validation_features.  I don't understand why VK_EXT_layer_settings is available all the time on macOS, but for Windows and Linux seems to be enabled only when vkconfig is running.  This seems incorrect to me.  Can you explain this?

Ok, I think I have finally figured it out.  It appears that you don't need to actually enable the VK_EXT_layer_settings extension in order to use it.  I have updated the sample and [HPP]Instance::[HPP]Instance() to check for availability of the extension vs. enablement.  This approach works across all platforms and behaviours appear to be consistent now:

Sample is tolerant of Vulkan SDK versions:  tested against VVL 1.3.290 (Win, Linux, macOS) and 1.3.296 (Win, macOS)
Sample is tolerant of vkconfig running or not running.  The only thing to be careful of when running vkconfig is to make sure "Limit Duplicated Messages" is turned off - otherwise debug callback messages will be suppressed and the debug output UI will be blank.

AFAIK, those two extensions (VK_EXT_layer_settings and VK_EXT_validation_features) are not supported by any NVIDIA GPU, but are provided by a layer injected by for example the VulkanConfigurator. That might explain why it's that slow.
Besides that, just to make sure it has been noted: As VK_EXT_validation_features is deprecated in favour of VK_EXT_layer_settings, using VK_EXT_validation_features would just be a fallback solution. Don't know, if it's worth to have that. And you should bail out in a friendly way, if none of those extensions is available, maybe with a hint to the VulkanConfigurator.

Welp, still sub 1 fps for me with latest SDK and vkconfig NOT running.
Just let me know when it's in a state were I should test.
If we can't get this to work, we may simply go back to the initial version and maybe remove the debug output and tell people to attach a graphics debugger.

Oddly I can't get the sample to run at acceptable frame rates anymore. Even when removing the debug output. The sample from my repo (which this was initially based on) works fine. I'm officially confused right now -.-

Thanks @asuessenbach for the info re nVidia GPUs.  I have an AMD card and I guess this is the difference here.
@SaschaWillems would you please test using this PR with vkconfig running and let me know the result?  I presume you are using an nVidia GPU - please confirm.
If this works, and as @asuessenbach suggests, I will try to detect this condition and offer a message to nVidia users.

If this works, and as @asuessenbach suggests, I will try to detect this condition and offer a message to nVidia users.

If we get to a point where we have to show a message under certain conditions to users of a certain vendor we're not heading where I'd like our samples to head. I'd rather remove the output debug stuff then.

@SaschaWillems I understand.  However I’d still like to track this down if possible and you testing on Nvidia with vkconfig active would give more information.  I can’t do this test myself.  Thx.

Windows 11 23H2, nvidia RTX 4070, latest Vulkan developer driver, SDK 1.3.296.
And I get <1 fps even with vkconfig up and running:

I'm pretty sure that the sample ran fine when I initially wrote it, but not sure why it no longer does.

I just added a minor hygiene change to use vk::ExtensionProperties vs. VkExtensionProperties in HPPInstance().  Also updated some comments and decided to explicitly request required GPU features for debugPrintfEXT as per docs.
More importantly, I was able to find an nVidia GPU to test this.  I have narrowed down what causes the slowdown and am now convinced it is a VVL debugPrintfEXT defect on that GPU platform.  Simply by disabling the following debugPrintfEXT feature enablement lines I can restore FPS performance on nVidia machines for both vkconfig running and not running cases.  Unfortunately this drops the debug info, but hopefully this is a temporary thing until this issue can be addressed.
...
	//add_layer_setting(layerSetting);
...
	instance_create_info.pNext = nullptr; //&validation_features;
...

I will respond on the other thread to @spencer-lunarg to see if he can help.

@SRSaunders before we had the Slow Down on for Vulkan 1.1 and 1.2/1.3 were good... is that still the case or is it now for all versions?

When using an nVidia GPU with SDK 1.3.296, it slows down for all API versions.  When using SDK 1.3.290 with the same setup (nVidia GPU), the sample works properly when using API 1.2 - as expected per your previous fix.
For AMD GPUs (and Apple Silicon on macOS) with SDK 1.3.296 everything works properly when using API 1.1

ok, so the problem has be isolated down to an NVIDIA GPU (I was testing on Intel and found no issues)... Later tonight I will be back at my desk and can try again on my NVIDIA machine

@SRSaunders I saw

It appears that you don't need to actually enable the VK_EXT_layer_settings extension in order to use it

So DebugPrintf I came out in 2020 and Layer Settings came out in 2023, so it was designed to be use the "old" way, 2023 we made it possible to use with Layer Settings (which is what vkconfig uses as well)
in 2024 we have been slowly pouring more effort into GPU-AV and DebugPrintf was there so we merged it in, added features, fixed bugs, so lots have recently was touching it. I tried to update the VVL docs for it https://github.com/KhronosGroup/Vulkan-ValidationLayers/blob/main/docs/debug_printf.md
Not in the 1.3.296 SDK (didn't want to rush it) but the next future SDK will have to go set VK_LAYER_PRINTF_ONLY_PRESET=1 for people who "just want to turn it on now" and not fuss with settings

I tried to update the VVL docs for it https://github.com/KhronosGroup/Vulkan-ValidationLayers/blob/main/docs/debug_printf.md

@spencer-lunarg thanks for updating the docs.  This is the same doc I referred back to today when digging into the issue we are facing here.

... but the next future SDK will have to go set VK_LAYER_PRINTF_ONLY_PRESET=1 for people who "just want to turn it on now" and not fuss with settings

Good to know there will be an even simpler way to enable debugPrintfEXT going forward.
While we are on the topic of VK_EXT_layer_settings, I would like to ask about the different behaviours of this extension cross-platform.  For instance, on Windows and Linux, is seems this extension is not advertized during enumeration unless vkconfig is running.  And in addition, if you try to enable it on Windows (even with vkconfig running), it will bail out with an extension not found error during vkCreateInstance() - kind of unexpected.  This is in contrast to what happens on macOS where the extension is available at all times (not just when vkconfig is running), and can be enabled during instance creation without bailing out.  Perhaps I am off base or don't understand it properly, but I thought that VK_EXT_layer_settings was meant to allow setting of layer features under program control during instance creation, and should not depend on whether vkconfig is running or not.  Would you help clarify this for me?

@SRSaunders

but I thought that VK_EXT_layer_settings was meant to allow setting of layer features under program control during instance creation, and should not depend on whether vkconfig is running or not

That is correct... something is wrong here (and of course it involves 3 different things) ... do me a favor, for this thing, create a new VVL issue and I can work with Christope (who maintains both VkConfig and wrote the VK_EXT_layer_settings extension) to figure out what is going on.
The layer has to define its settings in way that can be used, for example you can set printf_to_stdout by setting VK_EXT_layer_settings::pSettingName to "printf_to_stdout". We (VVL) also use the layer setting code in VUL so that it will automatically allow people to set set VK_LAYER_PRINTF_TO_STDOUT=1 to do the same thing
What gets ugly is that we have legacy ways to do settings sadly...until the commit right after we branched for 1.3.296, DebugPrintf and GPU-AV both did Shader Instrumentation, but would step over each other, so we needed a way to prevent both used at the same time. This was done with this very ugly GPU_BASED_DEBUG_PRINTF enum thing and honestly I want no one to waste time thinking about it, the next SDK will have a simple printf_enable setting to turn off/on DebugPrintf

Also want to clarify that enables=VK_VALIDATION_FEATURE_ENABLE_DEBUG_PRINTF_EXT is correct what you have, it is the "original" way of setting things, seems the issue
So tested, I have a laptop with  AMD Radeon 780M integrated and NVIDIA 4060 (using env variables to turn on, not vkconfig, shouldn't really matter in theory)

Samples ToT | AMD - 1.3.290 SDK - slow (1 FPS)
Samples ToT | AMD - 1.3.296 SDK - normal
Samples ToT | AMD - ToT VVL - normal
Samples PR 1187 | AMD - 1.3.290 SDK - slow (1 FPS)
Samples PR 1187 | AMD - 1.3.296 SDK - normal
Samples PR 1187 | AMD - ToT VVL - normal

With NVIDIA

Samples ToT | NVIDIA - 1.3.290 SDK - slow (1 FPS)
Samples ToT | NVIDIA - 1.3.296 SDK -  slow
Samples ToT | NVIDIA - ToT VVL -  slow
Samples PR 1187 | NVIDIA - 1.3.290 SDK - slow (1 FPS)
Samples PR 1187 | NVIDIA - 1.3.296 SDK -  slow
Samples PR 1187 | NVIDIA - ToT VVL -  slow

so basically this PR is not fix/breaking things from my end... I agree this seems like something on the VVL side (we reopened the issue and I will look more into this weekend) but everything in this PR seems sane ... it should not take "hacks" to get DebugPrintf to work, if it does, we failed in VVL badly
... from a quick glance this seems to be a sync issue within how GPU-AV is working (we had to start using timeline semaphores under the hood to get things to be faster in GPU-AV, before we did a big vkQueueWaitIdle, ... but we share this code with Sync Validation, which has also been active and I feel we regressed here)

@spencer-lunarg I have raised issue https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/8760 as requested.

so basically this PR is not fix/breaking things from my end... I agree this seems like something on the VVL side (we reopened the issue and I will look more into this weekend) but everything in this PR seems sane

Thanks for reviewing and good to know this PR appears correct from your side.  I look forward to any discoveries you make regarding slowdowns we are seeing with nVidia GPUs.

Following interaction with the VVL team, I think this is now ready for review.  A couple of learnings:

The VK_EXT_layer_settings extension is trickier than I first realized.  On Windows and Linux it is primarily a layer instance extension and not a driver extension.  On macOS things are a bit different where VK_EXT_layer_settings is made visible by the MoltenVK driver as well.  However, to detect its availability in general you need to query the layer and not the driver during instance enumeration.  Thanks to @spencer-lunarg + team and armed with this new (to me) information, I have modified the sample to now do proper detection.  This results in all platforms using the layer settings path independent of whether vkconfig is running or not.  The legacy VkValidationFeatureEnableEXT path is still present in the code, but will be used only with older SDKs that don't have VK_EXT_layer_settings within the VVL layer.
The above findings also made me realize that the general framework for adding a layer setting (in [HPP]Instance()) was not using the correct criteria to chain in the VkLayerSettingsCreateInfoEXT struct during instance creation.  Testing for the presence of VK_EXT_layer_settings in the driver will not give the right answer.  And looking for which layer to check would only add a bunch of unnecessary complexity to the code.  So I simplified things and now leave it up to the sample to determine if layer settings is supported, and if so, to push a layer setting using add_layer_setting().  In [HPP]Instance() I now only check for the presence of layer setting entries in the required_layer_settings vector.  This puts the onus on the sample to make sure layer settings entries are supported.  However, this is not very risky since vkCreateInstance() will throw away any layer settings that don't match and should not complain.
Lastly, the observed performance slow-downs on various platforms and SDK versions has two mitigations:
a) The slow-downs that @spencer-lunarg observed with older SDKs in https://github.com/KhronosGroup/Vulkan-Samples/pull/1187#issuecomment-2439205768 has been solved.  While I was picking the correct API version 1.2 for older SDKs, I had added code that explicitly requested support for timeline semaphores.  It turns out that while the VVL requires this under the covers, explicitly requesting support in the sample breaks performance.  I am not sure why this is the case, but I will leave it to @spencer-lunarg to decide if this is an issue or not.  Nonetheless, I have removed this from the sample and older SDKs now work without performance degradation.
b) The slow-down that was visible for nVidia GPUs running SDK 1.3.296 is apparently solved by https://github.com/KhronosGroup/Vulkan-ValidationLayers/pull/8766#issuecomment-2443120271, which will be available with the next SDK.  I have not been able to test this yet, but will report back once I can.  The only workaround for now is to use SDK 1.3.290 for nVidia GPU users.

It turns out that while the VVL debugPrintfEXT feature requires this and implicitly enables it under the covers, explicitly requesting support in the sample breaks performance.

Is this still true? I tried to add it explicitly in this PR and didn't see it slow down (the issue was the old pre-1.3.290 SDK and should be patched now)

It turns out that while the VVL debugPrintfEXT feature requires this and implicitly enables it under the covers, explicitly requesting support in the sample breaks performance.

Is this still true? I tried to add it explicitly in this PR and didn't see it slow down (the issue was the old pre-1.3.290 SDK and should be patched now)

I observed this performance impact when using SDK 1.3.290 with API 1.2 and timeline semaphores explicitly enabled.  With SDK 1.3.296 using API 1.1 with timeline semaphores enabled, performance was fine.  So I removed the explicit enablement of timeline semaphores and now I get consistent performance using: a) API 1.2 with SDKs <= 1.3.290, and b) API 1.1 with SDKs >= 1.3.296 (aside from the nVidia issue mentioned above).

Given the long discussion and in case it wasn't clear, this PR is now ready to go.
Note for nVidia users (Windows) using SDK 1.3.296: A fix is also required from the VVL which will ship in the next SDK.  In the interim, nVidia users should run using this PR combined with SDK 1.3.290 for the shader_debugprintf sample.

Quick update: We discussed this in a recent call and will probably wait with the merge until the next SDK is available to make sure we can simply point people to update their SDK in case of any problems with this sample. Hope that's okay with you.

@SaschaWillems that’s fine re the debugprintf sample.  My only concern is the fix for the add_layer_setting() framework capability.  Not sure if you want that separated out and brought forward into a new PR for merging now.  Let me know.

Is that fix important (sorry, I got kinda lost with all the discussion in this issue)? If so, splitting it into a separate PR is fine, if not it's fine if we merge all of this once the new SDK is out.

I guess we can wait givin the add_layer_setting() feature is not used extensively at this point.  I will leave it up to @JoseEmilio-ARM to comment if an earlier fix would be preferable.


Central configuration UI shows motion detection ON even though it is OFF

Version of the custom_component
6.2.1
Configuration
{'use_window_feature': False, 'use_motion_feature': False, 'use_power_feature': False, 'use_presence_feature': False, 'use_central_boiler_feature': False, 'use_main_central_config': False, 'use_tpi_central_config': False, 'use_window_central_config': False, 'use_motion_central_config': False, 'use_power_central_config': False, 'use_presets_central_config': False, 'use_presence_central_config': False, 'use_advanced_central_config': False, 'thermostat_type': 'thermostat_central_config', 'name': 'Central configuration', 'external_temperature_sensor_entity_id': 'sensor.test_sensor_temperature', 'temp_min': 7.0, 'temp_max': 35.0, 'step_temperature': 0.1, 'window_sensor_entity_id': None, 'window_auto_close_threshold': None, 'window_auto_open_threshold': None, 'window_auto_max_duration': None, 'power_sensor_entity_id': None, 'max_power_sensor_entity_id': None, 'presence_sensor_entity_id': None, 'central_boiler_activation_service': None, 'central_boiler_deactivation_service': None, 'motion_delay': 301, 'motion_off_delay': 300, 'motion_preset': 'comfort', 'no_motion_preset': 'eco', 'motion_sensor_entity_id': None}

Describe the bug
On a fresh installation of HA, the "central configuration" config UI keeps showing the "motion detection" feature as enabled, even though it has never been selected.
The feature seems disabled though in the device config as shown above in the json log.
I'm trying to:
Disable "motion detection"
And I expect:
Motion detection to be shown as disabled in UI
But I observe this ....
UI show motion detection enabled

It looks like it may be the behavior of add_suggested_values_to_schema when editing the config, filling in "motion detection" to on by default, but that seems counter intuitive to me that the config does not reflect the real state of the device.

This looks like a bug.

Hello @brunoleon ,
I have reproduce the bug and finally this is normal but I admit this could be confusing. Motion sensor are not centralized, but only some configuration is. So this is not a real feature in the central configuration but more some default configuration. And default configuration is always present and can't be removed. That is why the checkbox keep checked.
The real motion detection feature is on each VTherm (not central).
Because there is no impact, I will keep that, else we could have side effect on Vtherm if central is not activated and Vtherm is.
I will close this issue, don't hesitate to reopen if you think I'm wrong.


Fontconfig warning: ignoring UTF-8: not a valid region tag : Ubuntu 14.04

Hi Team,
when convert html to pdf i am getting this error . kindly give me correct solution. i tried lot ways from google .
i belive this is phantomJS issue  on Ubuntu

i've got this error message too

Hmm. Sorry, I've never seen that error. Have you tried phantomjs2?

mine's:
root@mean:/home# locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

@lonedune, can you tell what exactly you did to solve this issue? I've been facing it too.

I have fixed by adding these lines to /etc/environment
LANG=en_US.utf-8
LC_ALL=en_US.utf-8

I fixed this issue set environment variable.
sudo nano /etc/environment
#append below line
LC_ALL=en_US.UTF-8
LANG=en_US.UTF-8
kindly restart env variable else log off and login onetime .

Facing the same issue on Ubuntu 14.04.
$ env | grep LC gives:

LC_ALL=en_US.UTF-8
LC_CTYPE=UTF-8

$ locale gives:

LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8

I have the same problem :(

It's warning only. you can skip this.
On Mon, Apr 3, 2017 at 4:02 PM, Dejan Korez<EMAIL_ADDRESS>wrote:

I have the same problem :(
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/marcbachmann/node-html-pdf/issues/52#issuecomment-291106147,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACPxqGIwWYDwzbfhfskfQewjx-xRVctQks5rsMqigaJpZM4Ffw-B
.

This should fix your issue:
sudo apt-get install language-pack-en-base
sudo dpkg-reconfigure locales (Select All and then select en_us for local)
sudo reboot

@uber1geek  Maybe you can help this question :  https://stackoverflow.com/questions/51947226/how-can-i-install-gitextensions-in-mac-os


Floating action button is rendered incorrectly in Chrome

The issue is present only on Images page. For some reason, the button stays in the initial position and scrolls with the content while having fixed position. You can also tweak the styles of the button and it will not respond to the change or respond with some delay

can not reproduce


Attempt to resolve deadlock

Description
Update all 'for update' locks to the more accurate 'for no key update'
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in 0d19d786b6fac312f1e01960dede06f23c25606d

Processing #6533.

Processing #6533.


Pre-Training Problem

When I try to run the code below I get this error at the pretrain function:
Error
  File "C:\Users\fabio\Desktop\wetransfer-08d028\Rope_ex_v1.5\RL_Training\behaviour_cloning.py", line 40, in <module>
    model.pretrain(dataset, n_epochs=1000)

  File "c:\users\fabio\desktop\virtual_env\env1\lib\site-packages\stable_baselines\common\base_class.py", line 346, in pretrain
    expert_obs, expert_actions = dataset.get_next_batch('train')

  File "c:\users\fabio\desktop\virtual_env\env1\lib\site-packages\stable_baselines\gail\dataset\dataset.py", line 152, in get_next_batch
    dataloader.start_process()

  File "c:\users\fabio\desktop\virtual_env\env1\lib\site-packages\stable_baselines\gail\dataset\dataset.py", line 231, in start_process
    self.process.start()

  File "C:\Python\Python37\lib\multiprocessing\process.py", line 112, in start
    self._popen = self._Popen(self)

  File "C:\Python\Python37\lib\multiprocessing\context.py", line 223, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)

  File "C:\Python\Python37\lib\multiprocessing\context.py", line 322, in _Popen
    return Popen(process_obj)

  File "C:\Python\Python37\lib\multiprocessing\popen_spawn_win32.py", line 89, in __init__
    reduction.dump(process_obj, to_child)

  File "C:\Python\Python37\lib\multiprocessing\reduction.py", line 60, in dump
    ForkingPickler(file, protocol).dump(obj)

PicklingError: Can't pickle <function rebuild_pipe_connection at 0x0000024B185C2168>: it's not the same object as multiprocessing.connection.rebuild_pipe_connection

Code
import gym
from stable_baselines.gail import generate_expert_traj
env = gym.make("CartPole-v1")
def dummy_expert(_obs):
    return env.action_space.sample()

generate_expert_traj(dummy_expert, 'expert_cartpole', env, n_episodes=10)

from stable_baselines import PPO2
from stable_baselines.gail import ExpertDataset

dataset = ExpertDataset(expert_path='expert_cartpole.npz',
                        traj_limitation=1, batch_size=128)

model = PPO2('MlpPolicy', 'CartPole-v1', verbose=1)
model.pretrain(dataset, n_epochs=1000)
model.learn(int(1e5))

env = model.get_env()
obs = env.reset()

reward_sum = 0.0
for _ in range(1000):
        action, _ = model.predict(obs)
        obs, reward, done, _ = env.step(action)
        reward_sum += reward
        env.render()
        if done:
                print(reward_sum)
                reward_sum = 0.0
                obs = env.reset()

env.close()

Please check the issue template and fill necessary parts, and also paste the full traceback of the exception and place the code into a code-block like ``` this ```

I am sorry. I hope the description of the issue is more clear now.

The full traceback of all processes tells the issue: It is trying to load file expert_cartpole.npz when creating ExpertDataset, but data is stored in dummy_expert_cartpole.npz. Fixing this fixes the issue.

Sorry, my fault again.  It was a typo, the name of the file is correct. Additionally, if I use the following code to generate the expert trajectories I obtain the same error:
Code
from stable_baselines import DQN
from stable_baselines.gail import generate_expert_traj

model = DQN('MlpPolicy', 'CartPole-v1', verbose=1)
      # Train a DQN agent for 1e5 timesteps and generate 10 trajectories
      # data will be saved in a numpy archive named `expert_cartpole.npz`
generate_expert_traj(model, 'expert_cartpole', n_timesteps=int(1e5), n_episodes=10)

For me the code runs as expected (Ubuntu 18.04, Python 3.6, stable-baselines 2.10) once I fixed the filenames. You need to study the full traceback printed by the code. The one you pasted is only a side-effect of multiple processes running.

I am using (windows10, Python 3.7.6, stable-baseline 2.10). Ok I will try to investigate more thoroughly.

I think I found a bug. If I run the pretrain function with the sequential parameter of Dataloader object set on False, so using multiprocessing to manage data extraction, the program get stuck in these lines of code inside dataset.py:
         try:
                val = self.queue.get_nowait()
                break
            except queue.Empty:
                time.sleep(0.001)
                continue

Instead if I do not use subprocesses to process data, sequential = True, everything works fine.
Additionally, if I am using the multiprocessing mode to process data and I interrupt the loop presented above with ctrl-c, when I try to run again the code I get the error reported in the original question. I found that a workaround for this issue is to open a new console.

Did you try putting your code in a if __name__ == "__main__": section (cf doc https://stable-baselines.readthedocs.io/en/master/guide/vec_envs.html)
This is required to use multiprocessing on windows.

I tried but I get the same error as in the main question.
import gym

from stable_baselines.gail import generate_expert_traj
from stable_baselines import PPO2
from stable_baselines.gail import ExpertDataset

if __name__ == "__main__":

    env = gym.make("CartPole-v1")
    # Here the expert is a random agent
    # but it can be any python function, e.g. a PID controller
    def dummy_expert(_obs):
        """
        Random agent. It samples actions randomly
        from the action space of the environment.

        :param _obs: (np.ndarray) Current observation
        :return: (np.ndarray) action taken by the expert
        """
        return env.action_space.sample()
    # Data will be saved in a numpy archive named `expert_cartpole.npz`
    # when using something different than an RL expert,
    # you must pass the environment object explicitly
    generate_expert_traj(dummy_expert, 'expert_cartpole', env, n_episodes=10)

    # Using only one expert trajectory
    # you can specify `traj_limitation=-1` for using the whole dataset
    dataset = ExpertDataset(expert_path='expert_cartpole.npz',
                            traj_limitation=1, batch_size=128)

    model = PPO2('MlpPolicy', 'CartPole-v1', verbose=1)
    # Pretrain the PPO2 model
    model.pretrain(dataset, n_epochs=1)

    # As an option, you can train the RL agent
    # model.learn(int(1e5))

    # Test the pre-trained model
    env = model.get_env()
    obs = env.reset()

    reward_sum = 0.0
    for _ in range(1000):
            action, _ = model.predict(obs)
            obs, reward, done, _ = env.step(action)
            reward_sum += reward
            env.render()
            if done:
                    print(reward_sum)
                    reward_sum = 0.0
                    obs = env.reset()

    env.close()


fix(react): don't set options before suspending

setting options right before suspending is a side effect, and it has repercussions if used in transitions where the component stays mounted
to fix #6392 in a different way, we can't rely on observer.getCurrentQuery() when reading for error boundaries / suspense, because it can lag behind; instead, we can just read from the queryCache directly to get the latest values
fixes #6486

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

Comparison is base (2ed4779) 39.12% compared to head (6299628) 56.16%.
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #6611       +/-   ##
===========================================
+ Coverage   39.12%   56.16%   +17.03%
===========================================
  Files         161       99       -62
  Lines        6597     4081     -2516
  Branches     1297     1001      -296
===========================================
- Hits         2581     2292      -289
+ Misses       3665     1570     -2095
+ Partials      351      219      -132

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

we can see here that this fixes the original issue:
https://codesandbox.io/p/devbox/tanstack-query-example-react-basic-typescript-forked-mqmdyw?file=%2Findex.html%3A15%2C10


add spring boot support and some tutorials for integrating springboot

This is not a new feature, but simply a better extension of SpringBoot support. Hopefully, the release of a Starter JAR for SpringBoot will make EasyRules easier for more developers. This is my original intention, because EasyRules is so easy to use after all. Thank you very much for the open source efforts of EasyRules.

Hi @Venus-WXP,
Thank you for your PR! We used to have spring support in Easy Rules and a spring boot starter as well (#65), but this has been discontinued since v3 (See #74 for more details about this decision).
I really appreciate the effort you've put into this, but I will close this PR for the aforementioned reason. Moreover, please note that the project is in maintenance mode now. Thank you for your comprehension.


Add social media share option to About page

Replace the current About page text with an option to share the info text on social media, preferably with an image. Use brown/other 100MoMiles colors to achieve an 'established' look. A very rough mock-up is included below:

Current styling (implemented). Still trying to make the textbox look more like a textbox, and need to implement logic for Share on FB/Twitter/Insta buttons.

Ran into some technical issues with the projected implementation:

textbox's editability was not clear (UX issue)
only links can be shared on Facebook
Instagram links cannot be shared
getting data from textbox was difficult
changing textbox based on hovering share buttons was difficult/unclear to user

Because some of these issues cannot be resolved, I opted for a simpler informative textbox and three share options not necessarily tied to the textbox on the left. I also changed the styling to match that of the Tagboard.


Update readme to add direct link to your home assistant

Add my.home-assistant.io/redirect URL

Merci!


GH-1494: Fix NPE in DeadLetterPublishingRecoverer

Resolves https://github.com/spring-projects/spring-kafka/issues/1494
I will back-port as needed after review/merge

Back ported to 2.4.x, 2.3.x, resolving conflicts.


idempotent: create redis implementation

From the X-Idempotency-Key issue (https://github.com/moov-io/paygate/issues/15#issuecomment-432066409) we want to implement a redis implementation of idempotent.Recorder.
There's https://github.com/rafaeljusto/redigomock which looks like it works with https://github.com/gomodule/redigo. It's GPL'd though.
@wadearnold That project is GPL v2, can we use that? Probably not?
https://github.com/rafaeljusto/redigomock/blob/master/LICENSE
See: https://github.com/moov-io/paygate/issues/21

Not sure the best solution so let's discuss.
Ideally, a different license library would exist but this is something I assume we will need to deal with.
I was trying to fix the GPL issue with the FOSSA project but it was digging down into dependencies of GoLang.
https://fossa.io/
We could also just add a page to moov.io/licenses
GPL USAGE
The software used by Moov products contain copyrighted software that is licensed under the GPL.
A copy of that license for Version 2.1 is referenced here and for version 3.0 here.
You may obtain the complete Corresponding Source code at no charge from us by reviewing the project dependencies or contacting the project authors.

We could use https://github.com/go-redis/redis also and run a redis with docker if needed.


Mixpanel returning a response object instead of undefined even when opted out in AVA Unit Test

I'm currently trying to implement an AVA Unit Test for mixpanel.track.
I'm doing the following
initialize mixpanel instance
mixpanel.opt_out_tracking()
const trackResponse = mixpanel.track('event_name', {})
return !!trackResponse

Expected behaviour (and the observed behaviour when I use it in my components):
trackResponse === undefined

Observed behaviour:
trackResponse === { event: 'asdf',
  properties:
   { '$browser': 'Safari',
     '$current_url': 'about:blank',
     '$browser_version': null,
     '$screen_height': 0,
     '$screen_width': 0,
     mp_lib: 'web',
     '$lib_version': '2.30.1',
     time:<PHONE_NUMBER>.142,
     distinct_id: '[some_id]',
     '$device_id': '[some_id]',
     '$initial_referrer': '$direct',
     '$initial_referring_domain': '$direct',
     token: '[token]' } }

where [some_id] and [token] are some distinct values I've deleted.
I don't understand why in the AVA test, I'm receiving a response when normally a failed track() results in an undefined response. Could someone shine some light on this?
Let me know if I need to provide any additional information. Thanks.

I figured it out in case anyone else runs into this issue.
I used a debugger to step into the mixpanel.track() calls and figured out that to see if the user had opted out, mixpanel checks for a property in the localStorage and compares it to see if it's === to '0'. If this fails, it assumes the user has not opted out and carries out the track call as normal.
I guess during the AVA test, it was unable to access this property and assumed the user had not opted out. To fix it, in my call to mixpanel.init(), I added   opt_out_tracking_persistence_type: 'cookie' as an option so that my opt_out call was being saved somewhere that the property could be accessed during the test.


Switch to 0o as the one true octal constant prefix (needs a 0.7.4 release)

This PR needs a new release of Crystal before merging (the compiler can be built with current HEAD, but not using 0.7.3).
This PR simply converts all constants in the standard library to use the 0o octal prefix and causes old 0700 style octal constants to cause an error. It updates the specs appropriately and adds a few new ones to double check the 0 case. Once merged, this should fix issue #740.
[Travis failure is expected, as Travis is not building using current crystal HEAD]

With 0.7.4, this should be mergeable. Is there a way to force Travis to re-run?

@asb one way to re-run travis, you can amend the commit and push-force it to your branch again, ie:
git commit --amend
git push --force origin your-topic-branch

Another way is to close and re-open pull request.

Thanks! 0_o


Font shading / fading makes visuals difficult to read

There is no error this is more of a visual issue

Version of Archi

5.1.0 Silicon
Also a problem with previous versions of Archi
Archi Plug-ins

No
Operating System

macOS 13.4.1 on an M2 Mac
Expected Behaviour

The font should render in dark black on the Work Package icon
Actual Behaviour

It is in a light grey color inconsistent with other icons in the view
It does not behave like this on my older MacBook 12" running macOS 13.5
Steps to Reproduce the Behaviour

Create a Motivation view
Create a Principle object
Create a Work Package object
Notice the difference in the font rendering

Hi Eric,
the reason you'll see an element "greyed out" like that is because you'll have set a Viewpoint for that View where the Work Package element is not part of the Viewpoint. For more info on Viewpoints check out the Archi User Guide on pages 53-56.
Cheers,
Phil

Thank you!!!!!--Eric A. Stephens @.*** | KD2YVA | +1<PHONE_NUMBER> | Signal: +1<PHONE_NUMBER>On Aug 24, 2023, at 14:45, Phil Beauvoir @.***> wrote:
Hi Eric,
the reason you'll see an element "greyed out" like that is because you'll have set a Viewpoint for that View where the Work Package element is not part of the Viewpoint. For more info on Viewpoints check out the Archi User Guide on pages 53-56.
Cheers,
Phil
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Thank you!!!!!

If it's OK with you, Eric, I'll close this one...

Shows you how long it’s been since using the tool 😀😀😀😀😀. Hope you are well. --Eric A. Stephens @.*** | KD2YVA | +1<PHONE_NUMBER> | Signal: +1<PHONE_NUMBER>On Aug 24, 2023, at 14:55, Phil Beauvoir @.***> wrote:
Closed #956 as completed.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Hope you are well.

All good here, thanks. Hope you and all yours are well, too!


[BUG] LinuxNodeVMSize is ignored in New-AksHciCluster

Describe the bug
When running New-AksHciCluster -clusterName demo -linuxNodeCount 1 -linuxNodeVmSize Standard_A2_v2, the VM that is created has 8GB RAM.
According this table it should have just 4.
$global:vmSizeDefinitions =
@(
    # Name, CPU, MemoryGB
    ([VmSize]::Default, "4", "4"),
    ([VmSize]::Standard_A2_v2, "2", "4"),
    ([VmSize]::Standard_A4_v2, "4", "8"),
    ([VmSize]::Standard_D2s_v3, "2", "8"),
    ([VmSize]::Standard_D4s_v3, "4", "16"),
    ([VmSize]::Standard_D8s_v3, "8", "32"),
    ([VmSize]::Standard_D16s_v3, "16", "64"),
    ([VmSize]::Standard_D32s_v3, "32", "128"),
    ([VmSize]::Standard_DS2_v2, "2", "7"),
    ([VmSize]::Standard_DS3_v2, "2", "14"),
    ([VmSize]::Standard_DS4_v2, "8", "28"),
    ([VmSize]::Standard_DS5_v2, "16", "56"),
    ([VmSize]::Standard_DS13_v2, "8", "56"),
    ([VmSize]::Standard_K8S_v1, "4", "2"),
    ([VmSize]::Standard_K8S2_v1, "2", "2"),
    ([VmSize]::Standard_K8S3_v1, "4", "6"),
    ([VmSize]::Standard_NK6, "6", "12"),
    ([VmSize]::Standard_NV6, "6", "64"),
    ([VmSize]::Standard_NV12, "12", "128")

)

To Reproduce
follow WSLab scenario
https://github.com/microsoft/WSLab/tree/dev/Scenarios/AzSHCI and Kubernetes
Screenshots

@jaromirk  you are looking at the Load Balancer size.
NAME
New-AksHciCluster
SYNOPSIS
SYNTAX
New-AksHciCluster [-clusterName]  [[-kubernetesVersion] ] [[-controlPlaneNodeCount] ] [[-linuxNodeCount] ] [[-windowsNodeCount] ] [[-controlplaneVmSize] ]
[[-loadBalancerVmSize] ] [[-linuxNodeVmSize] ] [[-windowsNodeVmSize] ] []
DESCRIPTION
Adds a worker cluster to the deployment.
Linux Node VM Size points to Linux Worker node
loadBalancerVmSize - LB VM size
windowsNodeVmSize - Windwos VM Size


VBA - Missing text "Step 5 of 5" under Test transactions

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Lunch the app
Log in with expensifail account
Enable the Staging Server under Setting
Tap on any workspace
Tap Connect with Bank Account
Log in with Wells Fargo using username: user_good / Password - pass_good
Fill out all necessary information for the VBA flow and hit Onfido Flow

Expected Result:
Text "Step 5 of 5" should present under Test transactions
Actual Result:
Missing text "Step 5 of 5" under Test transactions page
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: n/a ( unable to verify VBA flow in Prod)
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @bondydaa (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Triggered auto assignment to @Christinadobrzyn (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Hmm looks like we have a prop here that is saying if we should show the step counter or not https://github.com/PrashantMangukiya/ExpensifyApp/blob/b9ef450aa586285073af061a87418867d124c9d6/src/pages/ReimbursementAccount/ValidationStep.js#L171
I see these somewhat recent PRs but it doesn't look like they are the cause of this https://github.com/Expensify/App/pull/6477 https://github.com/Expensify/App/pull/5255/
Since it's also not showing the test amount inputs, I'm guessing this bank account is already in the validated state and that's most likely why the step counter isn't showing.
We could fix by always showing the step counter no matter what even if the bank account is validated. Or we could do nothing. I don't have a strong opinion.
I'm going to add the external label so @Christinadobrzyn please weigh in since you're more familiar with the app - if you think it's worth changing to always show the step counter then post it, if not then lets close it.

The validation step here, has two states.

Verifying (Ops is verifying the VBA)
Pending (User needs to add test transactions or validation amounts as its said in old-dot)

We used to just have it set to "Connect Bank Account", then it changed to "Test Transactions" indiscriminately of either VBA state for this issue and in this pr
cc @kevinksullivan
Going to update this so that if we the VBA is VERIFYING, it'll say "Connect Bank Account" (do we want to change this to "validate" or something?)

And if the VBA is in the PENDING state, it'll say as the issue requested, "Test Transactions"

Sorry just catching up on this @ctkochan22 . So  going forward there is still a generic Connect bank account rather than Test transactions when we're following up in chat (i.e. in Verifying state), and then Test transactions when in Pending? That sounds good to me! We could add the additional Validate bank account for the verifying state as well.

So going forward there is still a generic Connect bank account rather than Test transactions when we're following up in chat (i.e. in Verifying state), and then Test transactions when in Pending

Yes exactly

Yeah, happy to change it to Validate bank account. It sounds better to me


Where to host the web interface?

If possible, I'd suggest to host it on CERN WebServices -> type: AFS folder. According to the docs it should run Python code server side.

The python version installed there is: 2.6.6-52.el6  (so NOT the newest one...)

@mmuszkow pity they don't have Python 2.7 - but maybe 2.6 will be enough for the server side of the front-end interface? the back-end tool could work elsewhere, if it needs Python 2.7.

Python 2.6 is enough for Flask, but maybe it would be better to have both back-ends together otherwise we will need to develop an adapter to communicate each other. With the approach we have now it is really easy to include the backend-tool module inside the flask app and use them together. What do you think?
Is it mandatory to host it at CERN? Why not we use a standard service such as Heroku?

The virtual machine has Python 2.7.5-18.el7_1.1 installed.

Not mandatory to host at CERN. Anything that works, is for free, is easy to manage (like web site hosted on AFS ;-) is OK. For the time being, hosting it on tedxapp VM sounds good to me.


Can't Read Two Sensor

Hello,
this library didn't work if me using two sensor dht22 on my raspberry pi3 (raspbian, python2). My program only read one sensor. how to resolve it, thanks before.
code:
import Adafruit_DHT
while 1:
sensor = Adafruit_DHT.DHT22
pin = 13
pin2 = 26
humidity, temperature = Adafruit_DHT.read_retry(sensor, pin)
humidity2, temperature2 = Adafruit_DHT.read_retry(sensor, pin2)

if humidity != None and temperature != None :
	print('Temp={0:0.1f}*C  Humidity={1:0.1f}%'.format(temperature, humidity))
if  humidity2 != None and temperature2 != None :
		print('Temp2={0:0.1f}*C  Humidity2={1:0.1f}%'.format(temperature2, humidity2))
else:
		print('Failed to get reading. Try again!')

So, Harlilopez, did it work?
sensor = Adafruit_DHT.DHT22
pin = 13
pin2 = 26
humidity, temperature = Adafruit_DHT.read_retry(sensor, pin)
humidity2, temperature2 = Adafruit_DHT.read_retry(sensor, pin2)
if humidity != None and temperature != None :
print('Temp={0:0.1f}*C  Humidity={1:0.1f}%'.format(temperature, humidity))
if  humidity2 != None and temperature2 != None :
print('Temp2={0:0.1f}*C  Humidity2={1:0.1f}%'.format(temperature2, humidity2))
else:
print('Failed to get reading. Try again!')
Barry
<EMAIL_ADDRESS>

filyadive,
problem was solved, but my raspberry pi can't read data if sensor cable length out of 5 meter.... now i'm use arduino to read sensor dht and communicate it to raspberry pi via data serial...

Thank you for the response and update.
My testing will be with leads no longer than 1 meter.
Do you think the problem may be a voltage drop issue?
I’m thinkingm:
1 go to a larger diameter wire.
2 use shielded wire.
3 use the 5 VDC pins instead of the 3 VDC pins.
Ian totally new to the RPi and programming, I’m just considering some basic
electrical engineering.
YES, I am on a huge upward learning curve.
Thank you again,
Barry
On Wednesday, December 13, 2017, harlilopez<EMAIL_ADDRESS>wrote:

filyadive,
problem was solved, but my raspberry pi can't read data if sensor cable
length out of 5 meter.... now i'm use arduino to read sensor dht and
communicate it to raspberry pi via data serial...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/adafruit/Adafruit_Python_DHT/issues/73#issuecomment-351594639,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ag4RxQxgtWzrHDKQpe5r_4ZBZcQy7rSOks5tAI-wgaJpZM4QUZeg
.

I've used DHT22 with 50ft of CAT 5 cable on an Arduino Yun without any issues.   The Yun has 5V pins

Original issue seems to be resolved.

@harlilopez ,
I couldn’t find a better way to contact you so I’m writing here. This comment will be deleted in one week to keep the issue discussion clean.
My name is Marat, I am a PhD student at Carnegie Mellon University. As a part of my research, I’m trying to better understand the sources of issue reports in open source.
Can you please help me by answering few questions about this issue? It shouldn’t take more than a couple of minutes. Here’s the google form: link
I will share everything I learn from answers to this survey with the community afterwards.
Thank you very much!


Controller memory leak fix

While doing some profiling, I noticed that Controller instances store a reference to the options object passed during instantiation. Then on the next line, the object is looped over to store it's values as instance attributes.
I'm not sure why @options is stored like this, but it means that any construction parameters are retained in memory for the life of the instance. So even if a controller replaces one of these instance attributes, the original construction attribute can't be garbage collected because the @options object is still referencing it...
The fix is really simple, but does anybody know if this would be a breaking change?

at a glance I think it might force me to cleanup some apps where I referenced controller.options.whatever instead of just controller.whatever. Suppose that isn't a bad thing. In a sense it is a 'breaking' change, if that is what it is called when people utilized the bug as a feature kind of deal. :)

@adambiggs, saw you added some config related to travis CI. can we trigger rerun. tests passed locally for you I assume?

@aeischeid I tried to fix travis builds, but my change didn't work so builds are still failing... Then tried debugging travis builds locally in Docker, but couldn't get that working either.
Instead of wasting any more time on it, I was thinking of switching Spine from travis CI over to Lightmaker's CircleCI account. What do you think?

@aeischeid I sent you a Slack invite to discuss further.


Populate MetricsPanelCtrl with attributes

#2

Thanks @hagen1778 - I should really have fixed this earlier. Grafana is getting too popular and creating loads of work!


Per-residue, per-frame pKa

Calculator has been added on v0.3.0 based on PROpKa. The measurement can be added using the 'add_pKa' function of the Measurement class.


update to 0.5.0

anaconda-cloud-auth 0.5.0
Destination channel: main
Links

Ticket: https://anaconda.atlassian.net/browse/PKG-4435
Source: https://inspector.pypi.io/project/anaconda-cloud-auth/0.5.0/packages/ce/8f/137adeaf9e0f0080b42efe9d732b59b561588b94c8934655f28d77f09507/anaconda_cloud_auth-0.5.0.tar.gz/anaconda_cloud_auth-0.5.0/pyproject.toml
Relevant PRs: https://github.com/AnacondaRecipes/anaconda-cloud-auth-feedstock/pull/7

Explanation of changes:

Follow changes from PR7.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_df7iyb1934/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:47: invalid_url: https://anaconda.cloud : Not reachable: 524
===== Final Report: =====
1 Error and 0 Warnings were found


Autogenerate credential name

This will autogenerate the credential name in the format username@server.

closing in favor of #250


Whre can I find 1.0.2 documentation??

Whre can I find 1.0.2 documentation?? Actually I need to work with this version. Thanks

Found. Thanks and sorry xD


Fab button is clickable on order details page when disabled

Current behavior

When the fab button is disabled, the user still can click on it to perform the action
Expected behavior

When the button is disabled, no action should be performed on click.
Steps to reproduce the issue

In the mobile view of the app:

Go to open tab in bopis
Click on an order to move to the details page
Button is not disabled, so disable the button through code or by changing permission or perform some action and verify that the button is still clickable

Same issue happens on packed order details page
Can you handle fixing this bug by yourself?

[x] YES
[ ] NO

Environment details

Browser:
OS:
Code Version:

Additional information

Closing as handled in https://github.com/hotwax/bopis/pull/347


Failed to restore DHCP server configuration

Describe the bug
DHCP server has failed during the connection test module.
Error message is:
test_connection ERROR   Failed to restore DHCP server configuration: 'NoneType' object is not subscriptable
To Reproduce
Unknown
Environment (please provide the following information about your setup):

Version v1.1.1

Not able to reproduce at the moment. Closing.


[#148869083] Proxima returns nil instead of boolean for TrueClass attributes

We noticed that boolean values such as enable_two_factor_auth were returning nil in the proxima response instead of a boolean value.
This PR fixes the from_json serialization method so that we map a value to the field instead of sending nil back.

I've updated the Gem


Formatting numbers

Big numbers are difficult to read without separators. What is the best way to format them? I found https://hackage.haskell.org/package/format-numbers on hackage for this purpose, which is a tiny package. Should we put a dependency for this or just copy over the code, or are there better options in base or something we already depend on? Or write our own?

I think writing our own (which is not very hard) is the best option since I can imagine being in control of the displaying very precisely is key to a nice UX and that related to #1.


Low speeds on local server

Hello,
I having problem regarding the speed of responses to commands and other requests
earlier my bot was on api.telegram.org but later i planned to move bot to local server because sometimes i might need to send files over 50MB
but i noticed that even 5-10MB file takes 60-70 seconds sometimes 2-3 mins to deliver/uploaded and user gets it.
Before you guys ask for the log file please let me know where do i find the log file.
Thank you

Do you have a high-speed internet connection on the server where the Bot API server is hosted?
You can enable logs by adding parameters -v4 -l log.txt to the Bot API server and send the file log.txt to https://t.me/tdlib_bot to know the exact reason.

Why do use domain at all and don't host the Bot API server on the same server as the bot?

Bot and BOT API both are hosted on same server, i think because i am using HTTP://ip:port  and not HTTPS my download/upload speed is capped to certain kbps maybe
And i thought if i use HTTPS with domain name i will get good speeds
What to do ?

Bot and BOT API both are hosted on same server,

Then you should send request to http://<IP_ADDRESS>:. You should also consider to send local files using file:// URI scheme as specified in https://github.com/tdlib/telegram-bot-api?tab=readme-ov-file#usage.

Files are not on the disk i am sending media link directly to user using replywithVideo / replywithphoto with url,
My bot really works fast on api.telegram.org and i am using same sending methods and i do succeed its just that its super slow on BOT API
These are my logs,
botlogs.txt

Files are not on the disk i am sending media link directly to user using replywithVideo / replywithphoto with url,
My bot really works fast on api.telegram.org and i am using same sending methods and i do succeed its just that its super slow on BOT API
botlogs.txt
These are my logs,

In the log upload speed is less than 1 megabit per second. The speed depends on your server and there is no way to upload files with a higher speed.

This is my speed tests, also download and uploading speed on other apps are very impressive

thats the sample code
const { Telegraf } = require('telegraf');
const bot = new Telegraf('', {
telegram: {
apiRoot: 'http://IP:PORT'   },
});
bot.start((ctx) => ctx.reply('Welcome! Use /send to get a video.'));
bot.command('send', (ctx) => {
const videoUrl = '';
ctx.replyWithVideo(videoUrl);
});
bot.launch();

I also have the ### same problem, is there an answer now?

thats the sample code
const { Telegraf } = require('telegraf');
const bot = new Telegraf('', { telegram: { apiRoot: 'http://IP:PORT' }, });
bot.start((ctx) => ctx.reply('Welcome! Use /send to get a video.'));
bot.command('send', (ctx) => { const videoUrl = ''; ctx.replyWithVideo(videoUrl); });
bot.launch();

I also have the ### same problem, is there an answer now?


Add files via upload

Q
A

Bug fix?
no

New sample?
yes

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch.

Thanks for your contribution! Sharing is caring.

Hi Vesa,
As discussed, here is my contribution, please let me know if you need more details.  I am doing this first time so might have got this wrong.
Thanks,
Sohail

thx @sohailmerchant for the great contribution. I'll do small adjustments to the sample readme and folder name, but all good from the contribution perspective. Would also update your GitHub profile with your name and possible other connection details, so that we can provide you properly credits in our monthly summary communications. See for example Nov 2017 summary for details - https://dev.office.com/blogs/pnp-november-2017-update


Accessibility issues

Describe the bug
Umbrella bug capturing accessibility issues found by Google in July. Catalog of specific issues attached. Overall, these are P3 bugs that should have low overall user impact, but we may want to address if accessibility is a priority for UDP.
Summary of the findings
The majority of the bugs found were related to

Screen reader (label, focus, unable to reach controls), keyboard focus, improper headings (No H1's on page, heading hierarchy), error cases, color contrast,  Large text , high contrast, large text, page titles etc.

Missing/Improper labels prevent screen reader users from using the site as they would be unable to identify the purpose of the form fields.
section headings within pages allows screen reader users to jump sections within pages instead of moving onto every control on page
Color contrast issues would make it difficult for individuals with visual impairments from seeing certain items on the page hence, preventing them from using the site.

Platforms used for testing

Desktop - web :

OS | Browser | Screen Reader
macOS Big Sur:11.4| Safari Version 14.1.1 (166<IP_ADDRESS>.4)  | VoiceOver
ChromeBook | Chrome Version: 90.0.4430.218 (Official Build) (64-bit) | ChromeVox
Window | Chrome Version 91.0.4472.77 (Official Build) (64-bit) | JAWS/NVDA
Window | Firefox Version: 87.0 (64-bit) | JAWS

Mobile Web (Android) :

Pixel 3 XL, Android version: 11, Android build number: RQ2A.210505.002,Chrome browser: 91.0.4472.120
Pixel 4 XL , android version: 11 (build number: RQ2A.210505.002) browser: chrome

Mobile Web (iOS) :

Iphone mini 12 , version: 14.2.1 browser: safari
IPad (5th generation) Software Version: 14.4.1 browser: safari

The total number of issues identified:  68 on all 3 platforms combined. Issues reproduced on multiple platforms were merged as part of a single bug.
Date tested between:  June 16 - July 19
Additional context
issues.csv

Closing this bug as it is quite old. We've made a lot of a11y improvements since then, and have a more recent full audit for WCAG 2.1 standards. All bugs surfaced from the recent audit are here: https://github.com/civiform/civiform/issues?q=is%3Aopen+is%3Aissue+label%3Aa11y+"WCAG+2.1"+in%3Atitle


update default value for end_point_request_max_handle_duration

What is changed and how it works?

Issue Number: Close #15022
What's Changed:

Update default end_point_request_max_handle_duration for big region size

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test

Release note
default value for server.end_point-request-max-handle-duration is updated.
If the region size is smaller than 256MB,  the default value is still 60s.
Otherwise, it will be region size / 256 * 60s.  So for 10GB region size, the default will be 2400s

/merge


Onboarding Enter Private Key: Error Text

Is your feature request related to a problem? Please describe.
Some errors in the text during Onboarding when importing private key.
Text should say:
If you already have a Seeds account please enter your private key and your account will be imported automatically.

An easy fix, will implement 🤓

Added a comma after the conditional clause 🤓

If you already have a Seeds account, please enter your private key and your account will be imported automatically.


marketplace  always bad network in china ，provide special support to China?

you konw china network is strict ，always cannot visit vscode service in USA .Would be to provide mirror service in China.

Hi @Simon-wu  Can you please share more details ?

By VSCode service, do you mean accessing extensions search on the editor ?
Or Downloading an extension on VSCode ?

In china wuhan sometimes marketplace.visualstudio.com/vscode domain visit network timeout. Must be proxy or vpn.
It's can't ping with the domain


Make sure to check that the AssemblyDefinition for LeapMotion exists before trying to use it

When consuming MRTK through NuGet, the LeapMotionConfigurationChecker throw an IndexOutOfRangeException because the asmdef file does not exist. However, this is expected when using compiled NuGet binaries.
The fix here adds a length check, and does not continue configuration if the asmdef is not found in the assets directory.
Changes

Fixes: 8021

/azp run


Eventhub: Added APIs to 2018-01-01-preview API version

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[X] I commit to follow the Breaking Change Policy of “no breaking changes
[X] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[X] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run automation - sdk

While adding new version the recommendation is to copy the existing version into new directory structure for first commit and then push new changes for easy review. Please create new PR with this recommendation for faster review.

Why are we adding older preview API version?

Why are we adding older preview API version?

We are adding support for all API (as on 2017 stable version) on the 2018-preview version. we will discuss with team and update the PR.

Signing off from ARM side. This PR is bring all the APIs from 2017-04-01 api version to 2018 preview api version. There is no change in the APIs which were present in the 2017 stable api-version.

@allenjzhang , can you please take look, I think the CI is stuck.

/azp run


Issue with CoreCLR metric

I am pushing a set of Gauges that I recorded but when scraping the metrics in my push gateway I get the following error:
expected counter in metric process_cpu_seconds_total label:<name:"instance" value:"" > label:<name:"job" value:"test_job" > label:<name:"test_id" value:"978e7cdb-c017-4e69-a9ac-719f96deee91" > gauge:<value:0.9375 >
I am not capturing nor sending this (actively) so it seems like the set up of the metric in the coreclrexporter class is not done properly.

The issue appears to be in the CoreclrExporter line 121 where it pushes this metric process_cpu_seconds_total as a Gauge when that should be a Counter.


weight missing

Your work is very impressive. Thank you for open-sourcing this project. When I tried to run inference.py, it seems that some weight files are missing: ./checkpoints/ebm_trans.pt.

Thank you for your interest! I've added them back (weird that they disappeared...). Would you mind running the the download pre-trained weights script again, and let me know if the optimisation demo works?


Build Development APK

Question: is it possible to build a develoment APK? donejs build cordova command always builds a production APK - steal.production.js with minified and compressed asstes etc.
It would be very helpful for debugging purposes to able to build a NOT minified and compressed version.
This is very useful for debugging code related to cordova plugins like barcode-reader/geolocation/camera/etc. - which work only on the mobile device.
I tried to set NODE_ENV= and set NODE_ENV=development but none works.
Unfortunately the docs do not mention much about this...

Hi @indianscout! You can turn off minify in your build.js file like so:
stealTools.build({
  config: __dirname + "/package.json!npm"
}, {
  minify: false
});

Here is the full set of options for that second arguments to stealTools.build.
Does this answer your question?

Seems to be the right direction, but does not work:

Here my build.js:
var stealTools = require("steal-tools");

var buildPromise = stealTools.build({
  config: __dirname + "/package.json!npm"
}, {
  minify: false
});
// options added by `donejs add cordova` - START
var cordovaOptions = {
	buildDir: "./build/cordova",
	id: "my.app.org",
	name: "myApp",
	platforms: ["android"],
	plugins: [
		"cordova-plugin-transport-security",
		"cordova-plugin-barcodescanner",
		"cordova-plugin-geolocation"
	],
	index: __dirname + "/production.html",
	glob: [
		"node_modules/steal/steal.production.js"
	]
};

var stealCordova = require("steal-cordova")(cordovaOptions);
// Check if the cordova option is passed.
var buildCordova = process.argv.indexOf("cordova") > 0;

if(buildCordova) {
  buildPromise.then(stealCordova.build).then(stealCordova.android.emulate);
}
// options added by `donejs add cordova` - END

Any idea/hint why this does not work? THX

@indianscout maybe this can help you.
i used gulp for building the APK
https://github.com/pYr0x/testapp
https://github.com/pYr0x/testapp/blob/master/gulpfile.js

@pYr0x: THX for the hint. Looks like a good way too. But since steal is shiped with donejs I'll give it another try.
@matthewp: my builds work now :-) The problem was that cordova build used the www folder, but steal builds by default  into build\cordova\www. So actually I was building an APK from an old source and not the most recent one.


affected/package: go test exhibits degraded performance

What version of Go are you using (go version)?

$ go version
go version go1.18 darwin/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOVERSION="go1.18"

What did you do?
git clone git@github.com:seborama/fuego.git -b v11_type_parameters && cd fuego
Edit file comparable_test.go and add a comment anywhere in the file then save. This step is to ensure the build is executed without caching.
go test -timeout 10s -v ./... -count 1 -run TestComparableStream_Max
The execution of the test takes over 1 minute on my computer, rather than < 3s normally.
This problem may have started after I added mapto.go (generated via make generate).

What did you expect to see?
A fast test execution, at most 3 seconds, likely under 1s.
What did you see instead?
The outcome is correct, but the test build takes a drastically long time.
Right now, I only have one computer on which to test this issue.
This may conceivably be related to an unknown particular of my environment set-up, although I cannot think of any.

Can you build and run the test separately? Build with go test -c and then run the resulting binary.
That will let us know for sure whether it is compile time or run time.

Sure:
go test -c

For comparison, I've created a new branch v11_type_parameters_51957 that does away from the parameterised MapTo* methods in mapto.go.
Build performance is back to normal. Execution is also faster.
time go test -c
go test -c  0.92s user 0.56s system 222% cpu 0.665 total

time go test -timeout 10s ./... -count 1 -run "TestComparableStream_.*"
ok      github.com/seborama/fuego/v11   0.138s
?       github.com/seborama/fuego/v11/generate  [no test files]
go test -timeout 10s ./... -count 1 -run "TestComparableStream_.*"  0.77s user 0.61s system 188% cpu 0.732 total

There appears to be just a lot of code generated by this package. Like, 74302 functions.
For instance, there are 24299 functions that all came from orderlyConcurrentDoStream. Looks like there's some cross product of two different shapes, times a bunch of local functions in each.
I'm not entirely sure that all of these instantiations are necessary, but at first look there's nothing obviously duplicated.

I'd argue that my attempt to use methods with a generic receiver is probably inadequate in my use-case.
This article refers:
https://go.dev/blog/when-generics.