Build failure: xboxdrv

Steps To Reproduce
Steps to reproduce the behavior:

build xboxdrv on current nixpkgs-unstable (de1864217bfa9b5845f465e771e0ecb48b30e02d)

Build log

Build Log
nix log /nix/store/16aas80ng2a79g3fc9fnw7wfmdjd35js-xboxdrv-0.8.8.drv | sed 's/\x1B\[[0-9;]*[a-zA-Z]//g' | tail --lines=100 | xclip -selection clipboard:
include/boost/lexical_cast/try_lexical_convert.hpp:67:20: error: ‘caster_type’ has not been declared
include/boost/lexical_cast/try_lexical_convert.hpp: In function ‘bool boost::conversion::detail::try_lexical_convert(const CharacterT*, std::size_t, Target&)’:
include/boost/lexical_cast/try_lexical_convert.hpp:74:32: error: ‘is_character’ is not a member of ‘boost::detail’
include/boost/lexical_cast/try_lexical_convert.hpp:74:55: error: expected primary-expression before ‘>’ token
include/boost/type_traits/is_const.hpp:37:11: note: ‘boost::is_const’ declared here
include/boost/function/function_template.hpp:568:81: error: expected primary-expression before ‘>’ token
include/boost/lexical_cast/try_lexical_convert.hpp:74:58: error: ‘::value’ has not been declared
include/boost/lexical_cast/try_lexical_convert.hpp:73:13: error: there are no arguments to ‘static_assert’ that depend on a template parameter, so a declaration of ‘static_assert’ must be available []8;;https://gcc.gnu.org/onlinedocs/gcc-14.2.0/gcc/Warning-Options.html#index-fpermissive-fpermissive]8;;]
include/boost/lexical_cast.hpp: At global scope:
include/boost/lexical_cast.hpp:83:38: error: ‘char16_t’ does not name a type
include/boost/lexical_cast.hpp:90:38: error: ‘char32_t’ does not name a type
include/boost/lexical_cast.hpp:90:19: error: redefinition of ‘template<class Target> Target boost::lexical_cast(const int*, std::size_t)’
include/boost/lexical_cast.hpp:83:19: note: ‘template<class Target> Target boost::lexical_cast(const int*, std::size_t)’ previously declared here
include/boost/function/function_template.hpp:568:84: error: ‘::value’ has not been declared
include/boost/function/function_template.hpp:569:64: error: ‘is_volatile’ is not a member of ‘std’; did you mean ‘boost::is_volatile’?
include/boost/type_traits/is_volatile.hpp:37:11: note: ‘boost::is_volatile’ declared here
include/boost/function/function_template.hpp:569:87: error: expected primary-expression before ‘>’ token
include/boost/function/function_template.hpp:569:90: error: ‘::value’ has not been declared
include/boost/function/function_template.hpp: At global scope:
include/boost/function/function_template.hpp:704:18: error: ‘is_trivially_copyable’ has not been declared in ‘std’
include/boost/function/function_template.hpp:751:44: error: ‘enable_if’ in namespace ‘std’ does not name a template type
include/boost/function/function_template.hpp:751:44: note: ‘std::enable_if’ is only available from C++11 onwards
include/boost/function/function_template.hpp:751:53: error: expected ‘,’ or ‘...’ before ‘<’ token
include/boost/function/function_template.hpp:761:44: error: ‘enable_if’ in namespace ‘std’ does not name a template type
include/boost/function/function_template.hpp:761:44: note: ‘std::enable_if’ is only available from C++11 onwards
include/boost/function/function_template.hpp:761:53: error: expected ‘,’ or ‘...’ before ‘<’ token
include/boost/function/function_template.hpp:777:26: error: expected ‘,’ or ‘...’ before ‘&&’ token
include/boost/function/function_template.hpp:777:5: error: invalid constructor; you probably meant ‘boost::function_n<R, T> (const boost::function_n<R, T>&)’
include/boost/function/function_template.hpp:799:19: error: ‘enable_if’ in namespace ‘std’ does not name a template type
include/boost/function/function_template.hpp:799:19: note: ‘std::enable_if’ is only available from C++11 onwards
include/boost/function/function_template.hpp:799:28: error: expected unqualified-id before ‘<’ token
include/boost/function/function_template.hpp:851:37: error: expected ‘,’ or ‘...’ before ‘&&’ token
include/boost/function/function_template.hpp: In constructor ‘boost::function_n<R, T>::function_n(Functor, int)’:
include/boost/function/function_template.hpp:757:28: error: ‘move’ is not a member of ‘std’
include/boost/function/function_template.hpp:757:28: note: ‘std::move’ is only available from C++11 onwards
include/boost/function/function_template.hpp: In constructor ‘boost::function_n<R, T>::function_n(Functor, Allocator, int)’:
include/boost/function/function_template.hpp:767:30: error: ‘move’ is not a member of ‘std’
include/boost/function/function_template.hpp:767:30: note: ‘std::move’ is only available from C++11 onwards
include/boost/function/function_template.hpp: In member function ‘boost::function_n<R, T>::result_type boost::function_n<R, T>::operator()(T ...) const’:
include/boost/function/function_template.hpp:790:45: error: expected ‘>’ before ‘&&’ token
include/boost/function/function_template.hpp:790:45: error: expected ‘(’ before ‘&&’ token
include/boost/function/function_template.hpp:790:47: error: expected identifier before ‘>’ token
include/boost/function/function_template.hpp:790:51: error: expected ‘)’ before ‘...’ token
include/boost/function/function_template.hpp: In member function ‘boost::function_n<R, T>& boost::function_n<R, T>::operator=(boost::function_n<R, T>)’:
include/boost/function/function_template.hpp:853:12: error: ‘f’ was not declared in this scope
include/boost/function/function_template.hpp:858:27: error: ‘f’ was not declared in this scope
include/boost/function/function_template.hpp: In member function ‘void boost::function_n<R, T>::assign_to(Functor)’:
include/boost/function/function_template.hpp:940:40: error: ‘move’ is not a member of ‘std’
include/boost/function/function_template.hpp:940:40: note: ‘std::move’ is only available from C++11 onwards
include/boost/function/function_template.hpp:943:38: error: ‘is_trivially_copyable’ is not a member of ‘boost::detail::function’
include/boost/function/function_template.hpp:943:67: error: expected primary-expression before ‘>’ token
include/boost/function/function_template.hpp:943:70: error: ‘::value’ has not been declared
include/boost/function/function_template.hpp: In member function ‘void boost::function_n<R, T>::assign_to_a(Functor, Allocator)’:
include/boost/function/function_template.hpp:973:42: error: ‘move’ is not a member of ‘std’
include/boost/function/function_template.hpp:973:42: note: ‘std::move’ is only available from C++11 onwards
include/boost/function/function_template.hpp:976:38: error: ‘is_trivially_copyable’ is not a member of ‘boost::detail::function’
include/boost/function/function_template.hpp:976:67: error: expected primary-expression before ‘>’ token
include/boost/function/function_template.hpp:976:70: error: ‘::value’ has not been declared
include/boost/function/function_template.hpp: At global scope:
include/boost/function/function_template.hpp:1080:27: error: ‘enable_if’ in namespace ‘std’ does not name a template type
include/boost/function/function_template.hpp:1080:27: note: ‘std::enable_if’ is only available from C++11 onwards
include/boost/function/function_template.hpp:1080:36: error: expected ‘,’ or ‘...’ before ‘<’ token
include/boost/function/function_template.hpp:1089:27: error: ‘enable_if’ in namespace ‘std’ does not name a template type
include/boost/function/function_template.hpp:1089:27: note: ‘std::enable_if’ is only available from C++11 onwards
include/boost/function/function_template.hpp:1089:36: error: expected ‘,’ or ‘...’ before ‘<’ token
include/boost/function/function_template.hpp:1104:21: error: expected ‘,’ or ‘...’ before ‘&&’ token
include/boost/function/function_template.hpp:1104:3: error: invalid constructor; you probably meant ‘boost::function<R(T ...)> (const boost::function<R(T ...)>&)’
include/boost/function/function_template.hpp:1105:21: error: expected ‘,’ or ‘...’ before ‘&&’ token
include/boost/function/function_template.hpp:1113:33: error: expected ‘,’ or ‘...’ before ‘&&’ token
include/boost/function/function_template.hpp:1120:17: error: ‘enable_if’ in namespace ‘std’ does not name a template type
include/boost/function/function_template.hpp:1120:17: note: ‘std::enable_if’ is only available from C++11 onwards
include/boost/function/function_template.hpp:1120:26: error: expected unqualified-id before ‘<’ token
include/boost/function/function_template.hpp:1141:33: error: expected ‘,’ or ‘...’ before ‘&&’ token
include/boost/function/function_template.hpp: In constructor ‘boost::function<R(T ...)>::function(Functor, int)’:
include/boost/function/function_template.hpp:1084:20: error: ‘move’ is not a member of ‘std’
include/boost/function/function_template.hpp:1084:20: note: ‘std::move’ is only available from C++11 onwards
include/boost/function/function_template.hpp: In constructor ‘boost::function<R(T ...)>::function(Functor, Allocator, int)’:
include/boost/function/function_template.hpp:1093:20: error: ‘move’ is not a member of ‘std’
include/boost/function/function_template.hpp:1093:20: note: ‘std::move’ is only available from C++11 onwards
include/boost/function/function_template.hpp: In constructor ‘boost::function<R(T ...)>::function(base_type)’:
include/boost/function/function_template.hpp:1105:59: error: expected ‘>’ before ‘&&’ token
include/boost/function/function_template.hpp:1105:59: error: expected ‘(’ before ‘&&’ token
include/boost/function/function_template.hpp:1105:61: error: expected identifier before ‘>’ token
include/boost/function/function_template.hpp:1105:63: error: ‘f’ was not declared in this scope
include/boost/function/function_template.hpp:1107:3: error: expected ‘{’ at end of input
include/boost/function/function_template.hpp: In member function ‘boost::function<R(T ...)>::self_type& boost::function<R(T ...)>::operator=(self_type)’:
include/boost/function/function_template.hpp:1115:14: error: expected primary-expression before ‘(’ token
include/boost/function/function_template.hpp:1115:36: error: expected ‘>’ before ‘&&’ token
include/boost/function/function_template.hpp:1115:36: error: expected ‘(’ before ‘&&’ token
include/boost/function/function_template.hpp:1115:38: error: expected identifier before ‘>’ token
include/boost/function/function_template.hpp:1115:40: error: ‘f’ was not declared in this scope
include/boost/function/function_template.hpp: In member function ‘boost::function<R(T ...)>::self_type& boost::function<R(T ...)>::operator=(base_type)’:
include/boost/function/function_template.hpp:1143:14: error: expected primary-expression before ‘(’ token
include/boost/function/function_template.hpp:1143:36: error: expected ‘>’ before ‘&&’ token
include/boost/function/function_template.hpp:1143:36: error: expected ‘(’ before ‘&&’ token
include/boost/function/function_template.hpp:1143:38: error: expected identifier before ‘>’ token
include/boost/function/function_template.hpp:1143:40: error: ‘f’ was not declared in this scope
scons: *** [src/evdev_controller.o] Error 1
scons: *** [src/button_event.o] Error 1
scons: building terminated because of errors.

Additional context
@Madouura @Steinhagen This breaks Lutris.
Metadata

system: "x86_64-linux"
host os: Linux 6.12.5, NixOS, 25.05 (Warbler), 25.05.20241217.4989a24
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.24.11
channels(root): ""
nixpkgs: /nix/store/9bdl6wa2qck3q0f7l892plk5lwy3pvx1-source

Notify maintainers
@infinisil

Note for maintainers: Please tag this issue in your PR.

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

This is what I get, can't rebuild anymore:
error: builder for '/nix/store/16aas80ng2a79g3fc9fnw7wfmdjd35js-xboxdrv-0.8.8.drv' failed with exit code 2;
       last 25 log lines:
       >   837 |         process_name_value_string(opt.argument, boost::bind(&CommandLineParser::set_relative_axis, this, _1, _2));
       >       |                                                 ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       > src/helper.hpp:33:126: note: in passing argument 2 of ‘void process_name_value_string(const std::string&, const boost::function<void(const std::__cxx11::basic_string<char>&, const std::__cxx11::basic_string<char>&)>&)’
       >    33 | void process_name_value_string(const std::string& str, const boost::function<void (const std::string&, const std::string&)>& func);
       >       |                                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
       > src/command_line_options.cpp:841:60: error: invalid initialization of reference of type ‘const boost::function<void(const std::__cxx11::basic_string<char>&, const std::__cxx11::basic_string<char>&)>&’ from expression of type ‘boost::_bi::bind_t<boost::_bi::unspecified, void (CommandLineParser::*)(const std::__cxx11::basic_string<char>&, const std::__cxx11::basic_string<char>&), boost::_bi::list<boost::_bi::value<CommandLineParser*>, boost::arg<1>, boost::arg<2> > >’
       >   841 |         process_name_value_string(opt.argument, boost::bind(&CommandLineParser::set_axis_sensitivity, this, _1, _2));
       >       |                                                 ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       > src/helper.hpp:33:126: note: in passing argument 2 of ‘void process_name_value_string(const std::string&, const boost::function<void(const std::__cxx11::basic_string<char>&, const std::__cxx11::basic_string<char>&)>&)’
       >    33 | void process_name_value_string(const std::string& str, const boost::function<void (const std::string&, const std::string&)>& func);
       >       |                                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
       > include/boost/lexical_cast/try_lexical_convert.hpp: In instantiation of ‘bool boost::conversion::detail::try_lexical_convert(const Source&, Target&) [with Target = int; Source = std::__cxx11::basic_string<char>]’:
       > include/boost/lexical_cast.hpp:42:60:   required from ‘Target boost::lexical_cast(const Source&) [with Target = int; Source = std::__cxx11::basic_string<char>]’
       > src/command_line_options.cpp:574:48:   required from here
       >   574 |         opts.timeout = boost::lexical_cast<int>(opt.argument);
       >       |                        ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~
       > include/boost/lexical_cast/try_lexical_convert.hpp:52:26: error: ‘static_assert’ was not declared in this scope
       > include/boost/lexical_cast/try_lexical_convert.hpp: In instantiation of ‘bool boost::conversion::detail::try_lexical_convert(const Source&, Target&) [with Target = float; Source = std::__cxx11::basic_string<char>]’:
       > include/boost/lexical_cast.hpp:42:60:   required from ‘Target boost::lexical_cast(const Source&) [with Target = float; Source = std::__cxx11::basic_string<char>]’
       > src/command_line_options.cpp:1257:73:   required from here
       >  1257 |     = AxisFilterPtr(new SensitivityAxisFilter(boost::lexical_cast<float>(value)));
       >       |                                               ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
       > include/boost/lexical_cast/try_lexical_convert.hpp:52:26: error: ‘static_assert’ was not declared in this scope
       > scons: *** [src/command_line_options.o] Error 1
       > scons: building terminated because of errors.
       For full logs, run 'nix log /nix/store/16aas80ng2a79g3fc9fnw7wfmdjd35js-xboxdrv-0.8.8.drv'.

I mean, xboxdrv seems discontinued judging by source https://github.com/xboxdrv/xboxdrv

Notably, this prevents lutris from compiling.

it seems like Lutris may have removed their use of xboxdrv awhile back? https://github.com/lutris/lutris/commit/6f6b50cf66e676bbe05605e9813f0a034a35bb81


Self-hosted Ubuntu logs filling up the disk

Describe the problem
I've been running Netbird on my Ubuntu 22.04.4 for about two months.
Last week two peers failed to connect and I discovered that the Ubuntu VM was out of disk space.  I couldn't do much other than logging in so I had to restore the VM from backup to a week old image and I was then able to resize the volumes.
I have been trying to figure out the culprit (I'm a Linux beginner) and found the following issues:

There is a root_caddy_1 docker image that seems to be saving logs in "debug" mode, which caused the volume to fill up.  So far is about 17Gb in size and growing about 1Gb every 36 hrs.
I couldn't find a /etc/docker/daemon.json file to change the log level to "info" or to set logging rotation -- according to some research I did.
If there is not an automated way to clear the logs, what is the recommended way to do this?

Expected behavior
The logs should automatically truncate so the server doesn't run out of disk space.
Are you using NetBird Cloud?
Self hosted
NetBird version
netbird version
NetBird status -d output:
N/A
Screenshots

Additional context
This is an example of the logs:
{"level":"debug","ts":1719411987.5158257,"logger":"http.handlers.reverse_proxy","msg":"selected upstream","dial":"signal:10000","total_upstreams":1}
{"level":"debug","ts":1719411987.5170805,"logger":"http.handlers.reverse_proxy","msg":"upstream roundtrip","upstream":"signal:10000","duration":0.00113983,"request":{"remote_ip":"<IP_ADDRESS>","remote_port":"53576","client_ip":"<IP_ADDRESS>","proto":"HTTP/2.0","method":"POST","host":"my.domaingoeshere.com:443","uri":"/signalexchange.SignalExchange/Send","headers":{"Te":["trailers"],"Grpc-Timeout":["9999979u"],"X-Forwarded-For":["<IP_ADDRESS>"],"X-Forwarded-Proto":["https"],"X-Forwarded-Host":["my.domaingoeshere.com:443"],"Content-Type":["application/grpc"],"User-Agent":["grpc-go/1.64.0"]},"tls":{"resumed":false,"version":772,"cipher_suite":4867,"proto":"h2","server_name":"my.domaingoeshere.com"}},"headers":{"Content-Type":["application/grpc"]},"status":200}

@jluisoma you can update your docker-compose.yml file with the log configuration as the new template recently pushed:
https://github.com/netbirdio/netbird/blob/main/infrastructure_files/docker-compose.yml.tmpl#L47
After adding this to all services, you can run docker compose up -d to apply.

Great.  Made the changes and volume size went down to 13Gb.
Appreciate the help!


[Bug]: App crashes when using GSheets where condition operator using keyboard shortcuts

Is there an existing issue for this?

[X] I have searched the existing issues

Description
App crashes when using GSheets where condition operator using keyboard shortcuts
Steps To Reproduce

Go to any Goole Sheet query
Go to the where clause bit and type in a column name and then use TAB to move to the next feild and observe the app crash

Public Sample App
No response
Version
Cloud

not able to reproduce with the original steps anymore, but thanks to @prapullac here's another way to see this error:

Add a GSheets query
enter spreadhsheet, and sheet name
run the query once
go to where clause section
enter "column name"
hit TAB (app doesn't crash)
when the focus is on OPERATOR field, hit the "down" arrow to expand the dropdown
app crashes


Sample random values for structs in tests

This builds on #370
Basically I implemented Standard Distribution for all the types currently under NetworkMessage but this can be further extended.
the point is to be able to add random full round tests.
(might also be useful for fuzzing the serializer somehow? @TheBlueMatt. I'm no expert in fuzzing.)

Codecov Report

Merging #371 into master will increase coverage by 2.98%.
The diff coverage is 94.46%.

@@            Coverage Diff            @@
##           master    #371      +/-   ##
=========================================
+ Coverage   81.91%   84.9%   +2.98%
=========================================
  Files          39      40       +1
  Lines        7179    7400     +221
=========================================
+ Hits         5881    6283     +402
+ Misses       1298    1117     -181

Impacted Files
Coverage Δ

src/lib.rs
100% <ø> (ø)
:arrow_up:

src/test_rand_types.rs
93.26% <93.26%> (ø)

src/network/message.rs
95.68% <98.33%> (+34.08%)
:arrow_up:

src/consensus/encode.rs
85.6% <0%> (+3.65%)
:arrow_up:

src/network/address.rs
93.15% <0%> (+5.47%)
:arrow_up:

src/blockdata/block.rs
78.19% <0%> (+7.51%)
:arrow_up:

src/network/message_blockdata.rs
80.3% <0%> (+43.93%)
:arrow_up:

src/network/message_network.rs
75% <0%> (+50%)
:arrow_up:

... and 1 more

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 4c3ad9d...97dc4f0. Read the comment docs.

I really like the general idea of having a way to generate random instances of all our types.

Perhaps we can expose this even using a feature flag.

Sure. But that is RawNetworkMessage-specific behavior.
On Mon, Dec 23, 2019 at 1:27 PM Elichai Turkel<EMAIL_ADDRESS>wrote:

@elichai commented on this pull request.
In src/test_rand_types.rs
https://github.com/rust-bitcoin/rust-bitcoin/pull/371#discussion_r360871195
:

}
+}

+impl Distribution for Standard {

fn sample<R: Rng + ?Sized>(&self, rng: &mut R) -> CFCheckpt {

   CFCheckpt {

       filter_type: rng.gen(),

       stop_hash: gen_hash(rng),

       filter_headers: gen_vec_hash(rng),

   }

}
+}

+impl Distribution for Standard {

fn sample<R: Rng + ?Sized>(&self, rng: &mut R) -> CommandString {

   NetworkMessage::possibilites().choose(rng).unwrap().clone() // Can never fail. the array isn't empty.

It will fail decoding
https://github.com/rust-bitcoin/rust-bitcoin/blob/master/src/network/message.rs#L324
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-bitcoin/rust-bitcoin/pull/371?email_source=notifications&email_token=AAGQLXA257PCLGGQDMVQ25LQ2CVBNA5CNFSM4J6MBRD2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCQCIJEY#discussion_r360871195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGQLXHSLQNXZVL6NPKZGLLQ2CVBNANCNFSM4J6MBRDQ
.

Regarding "perhaps we can expose this using a feature flag", some relevant context here is that @elichai is basically recreating the rand crate, which has come under fire recently for being unstable.
My feeling is that if we want to expose this in a non-test context, we should probably make our own crate with traits that other projects can use.

@apoelstra I actually started to impl my own rand crate. I need to keep working on it


Import multiple (tiled) heightmaps simultaneously

Description
Some software / databases export heightmap data as multiple files, typically following some naming conventions to map position, e.g.: <X>_<Y>_<pixel size> (2672_1227.xyz or 2672_1227_0.5m.tif or x0_y0), or maybe with start/stop boundaries <X start>_<X end>_<Y start>_<Y end> (4.315_4.456_5.515_5.715), etc.
It would be nice if there was a way to point to a directory and import multiple files with a regex or something like that.

You could write a script to do it in a few minutes. Open up importer.gd which is a very simple script that uses the C++ API. You should be able to figure it out from there using the basic GDScript API to look at directories and get filenames.

Glorious success!

Thanks! It took me a while until I figured out I had to resize my 341x341 images to 1024x1024. I guess because of https://github.com/TokisanGames/Terrain3D/issues/77 the calculated offsets all fell in the same tile and each image overwrote the previous.
Do you think this is relevant for others?

Importer.gd does not resize to 1024. The import functions take in any size, smaller or larger than 1024 and automatically pads or slices to regions.


Look up daily data type definitions from the dynamic collection.

Overview
I ran into this issue while trying to use the DailyDataChart with a non-standard daily data provider.
I think the type definition lookup needs to use the dynamic collection of types, which gets updated by registrations, rather than the hard coded list of standard types.
Security
REMINDER: All file contents are public.

[x] I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc.

[x] Please verify that you double checked that .storybook/preview.js does not contain your participant access key details.
[x] There are no temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.

[x] These changes do not introduce any security risks, or any such risks have been properly mitigated.

Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.

No security risk.  This just corrects a bug to allow for custom daily data providers to be used, which was the original intent.

Checklist
Testing

[ ] MyDataHelps iOS app
[ ] MyDataHelps Android app
[ ] MyDataHelps website

Documentation
n/a

Summary by CodeRabbit

Refactor

Improved performance of daily data type definitions lookup by using direct access from a set instead of a map.

Chores

Incremented version from "2.21.1" to "2.21.2-FixDailyDataTypeDefinitionLookup.0".

Ah yep, makes sense.  Must have been some copy/paste flog


Printing to stdout does not work when calling eta code from leinigen

My minimal example is the following:
The eta code:
data {-# CLASS "MyClass" #-} MyClass = MyClass (Object# MyClass)
printStuff :: Java MyClass ()
printStuff =
    io $ do
        putStrLn "To stdout"
        hPutStrLn stdout "To stdout"
        hPutStrLn stderr "To stderr"

The clojure code:
(ns debug-ns (:import MyClass))

(.printStuff (MyClass.))

I use the leinigen command lein run -m debug-ns.
And the result:
To stderr

(plus a leinigen error that it doesn't find anything to run, but that doesn't actually matter.
FYI running the code
printStuff2 = do
    putStrLn "To stdout"
    hPutStrLn stdout "To stdout"
    hPutStrLn stderr "To stderr"

with epm run does work as intended, however the stderr stuff appears before the stdout stuff:
Running <executable>...
To stderr
To stdout
To stdout

Can you try running MyClass.printStuff() directly with java and share the result?

Same problem. Also only prints the stderr.

Here are the two files I'm using for testing.
Test.hs
{-# LANGUAGE MagicHash #-}

module Test where

import System.IO ( hPutStrLn
                 , hFlush
                 , stdout
                 , stderr
                 )
import Java

data {-# CLASS "java_interop.TestStdout" #-} TestStdout
  = TestStdout (Object# TestStdout)
  deriving Class

testStdout :: Java TestStdout ()
testStdout = io $ do
  hPutStrLn stderr "(stderr) 1. from Eta (hPutStrLn)"
  putStrLn "(stdout) 2. from Eta (putStrLn)"
  -- hFlush stdout
  hPutStrLn stdout "(stdout) 3. from Eta (hPutStrLn)"
  -- hFlush stdout
  hPutStrLn stderr "(stderr) 4. from Eta (hPutStrLn)"
  -- hFlush stdout

foreign export java testStdout :: Java TestStdout ()

Main.java
import java_interop.TestStdout;
import eta.runtime.Rts;

public class Main {

  public static void main(String[] argv) {
    TestStdout test = new TestStdout();
    System.out.println("(stdout) Before call into Eta code.");
    test.testStdout();
    System.out.println("(stdout) After call into Eta code.");
    System.out.println("(stdout) Calling Rts.hsExit().");
    Rts.hsExit();
  }
}

First thing is, you need to call Rts.hsExit() to flush stdout. I'm not yet sure why stderr behaves differently. By the way, even if you call Rts.hsExit() right after calling into the Eta function, the output isn't interleaved like it is in the function. All the stderr comes out during the call, and all the stdout comes out only when the call to Rts.hsExit() is made.
Here's the output I get from running these.
(stdout) Before call into Eta code.
(stderr) 1. from Eta (hPutStrLn)
(stderr) 4. from Eta (hPutStrLn)
(stdout) After call into Eta code.
(stdout) Calling Rts.hsExit().
(stdout) 2. from Eta (putStrLn)
(stdout) 3. from Eta (hPutStrLn)

What you can see here is that anything that goes into stdout gets buffered until Rts.hsExit() is called. But the weird thing is that you can write to stdout, and it gets output before everything that's flushed in Rts.hsExit().

I think this has to do with how IO is implemented. The default is to use BlockBuffering so there's a block buffer of size 8KB (see GHC.IO.Handle.Internals in base) that is allocated for the purposes of I/O on the Eta side that has no relation with the buffer in System.out that is flushed on call to println. That block buffer will only be flushed when:

The 8KB buffer is filled (will not happen for short programs like above)
hFlush is invoked on the handle
The runtime exits and flushStdHandles is called that flushes stdout and stderr.

While we're on the topic, I'm wondering whether making LineBuffering the default is better. BlockBuffering is a real pain and often unintuitive for users. In your program above, run hSetBuffering LineBuffering at the top to see what the behaviour is. Thoughts?

But this doesn't explain why the same thing isn't happening for stderr - stderr should also be BlockBuffering by default and hence shouldn't have printed when called from Java without hsExit().

The answer is in the definition of the stderr Handle:
-- | A handle managing output to the Haskell program's standard error channel.
stderr :: Handle
{-# NOINLINE stderr #-}
stderr = unsafePerformIO $ do
    -- ToDo: acquire lock
   setBinaryMode FD.stderr
   enc <- getLocaleEncoding
   mkHandle FD.stderr "<stderr>" WriteHandle False{-stderr is unbuffered-}
                (Just enc)
                nativeNewlineMode{-translate newlines-}
                (Just stdHandleFinalizer) Nothing

Note that {-stderr is unbuffered-}. Following the definition in mkHandle, it turns out the the Handle has NoBuffering set on it, so every write will flush the buffer.

Adding hSetBuffering stdout LineBuffering fixes the issue, and the output is what you would expect.
(stdout) Before call into Eta code.
(stderr) 1. from Eta (hPutStrLn)
(stdout) 2. from Eta (putStrLn)
(stdout) 3. from Eta (hPutStrLn)
(stderr) 4. from Eta (hPutStrLn)
(stdout) After call into Eta code.
(stdout) Calling Rts.hsExit().

Personally, I think line buffering for stdout is probably a less surprising default than an arbitrary sized block buffer.

Yeah even I feel the same. Would you be willing to submit a patch to set LineBuffering to default for stdout?

Or even NoBuffering, depending on what seems to be better.

Sure thing.

https://github.com/typelead/eta/pull/419

Closed by #419
(But it seems to be somewhat related with #710)


Remove duplicate README section

store.update was in there twice.

You caught me, I was trying to make it look fancier that it really is 😉


CPU 100% using netty 4.0.24

In our Product env,CPU 100% occur,Here is env  info:
NULL           ===============================
1TISIGINFO     Dump Event "user" (00004000) received
1TIDATETIME    Date:                 2016/08/02 at 10:00:52
1TIFILENAME    Javacore filename:    /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/javacore.20160802.100052.4568.0001.txt
1TIREQFLAGS    Request Flags: 0x81 (exclusive+preempt)
1TIPREPSTATE   Prep State: 0x4 (exclusive_vm_access)
NULL           ------------------------------------------------------------------------
0SECTION       GPINFO subcomponent dump routine
NULL           ================================
2XHOSLEVEL     OS Level         : Linux 2.6.32-279.el6.x86_64
2XHCPUS        Processors -
3XHCPUARCH       Architecture   : amd64
3XHNUMCPUS       How Many       : 8
3XHNUMASUP       NUMA is either not supported or has been disabled by user
NULL
1XHERROR2      Register dump section only produced for SIGSEGV, SIGILL or SIGFPE.
NULL
NULL           ------------------------------------------------------------------------
0SECTION       ENVINFO subcomponent dump routine
NULL           =================================
1CIJAVAVERSION JRE 1.6.0 IBM J9 2.4 Linux amd64-64 build jvmxa6460sr9-20111111_94827
1CIVMVERSION   VM build 20111111_094827
1CIJITVERSION  JIT enabled, AOT enabled - r9_20101028_17488ifx45
1CIGCVERSION   GC - 20101027_AA_CMPRSS
1CIRUNNINGAS   Running as a standalone JVM

and we use netty 4.0.24.
and below is TOP -H result:
26334 wasuser   20   0 6103m 1.1g  58m R 86.6 14.7 175:00.15 java
26342 wasuser   20   0 6103m 1.1g  58m R 86.6 14.7 173:12.17 java
26340 wasuser   20   0 6103m 1.1g  58m R 84.9 14.7 175:00.22 java
26346 wasuser   20   0 6103m 1.1g  58m R 76.4 14.7 175:16.43 java
26338 wasuser   20   0 6103m 1.1g  58m R 64.5 14.7 176:56.61 java
26336 wasuser   20   0 6103m 1.1g  58m R 61.1 14.7 175:26.48 java
26332 wasuser   20   0 6103m 1.1g  58m R 54.3 14.7 175:45.02 java
26344 wasuser   20   0 6103m 1.1g  58m R 54.3 14.7 175:41.66 java

we found top 5 thread's current stack is like:
3XMTHREADINFO      "client.worker-thread-3" J9VMThread:0x0000000064C89500, j9thread_t:0x00007F5CC435C350, java/lang/Thread:0x000000000705CF40, state:CW, prio=5
3XMTHREADINFO1            (native thread ID:0x66DE, native priority:0x5, native policy:UNKNOWN)
3XMTHREADINFO2            (native stack address range from:0x00007F5C4A005000, to:0x00007F5C4A046000, size:0x41000)
3XMTHREADINFO3           Java callstack:
4XESTACKTRACE                at java/nio/Bits.copyFromByteArray(Native Method)
4XESTACKTRACE                at java/nio/DirectByteBuffer.put(DirectByteBuffer.java:330(Compiled Code))
4XESTACKTRACE                at java/nio/DirectByteBuffer.put(DirectByteBuffer.java:292(Compiled Code))
4XESTACKTRACE                at io/netty/buffer/UnpooledDirectByteBuf.setBytes(UnpooledDirectByteBuf.java(Compiled Code))
4XESTACKTRACE                at io/netty/buffer/UnpooledDirectByteBuf.setBytes(UnpooledDirectByteBuf.java(Compiled Code))
4XESTACKTRACE                at io/netty/buffer/AbstractByteBuf.writeBytes(AbstractByteBuf.java:850(Compiled Code))
4XESTACKTRACE                at io/netty/channel/nio/AbstractNioChannel.newDirectBuffer(AbstractNioChannel.java:392(Compiled Code))
4XESTACKTRACE                at io/netty/channel/nio/AbstractNioByteChannel.filterOutboundMessage(AbstractNioByteChannel.java:269(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannel$AbstractUnsafe.write(AbstractChannel.java:651(Compiled Code))
4XESTACKTRACE                at io/netty/channel/DefaultChannelPipeline$HeadContext.write(DefaultChannelPipeline.java:1054(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:658(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:714(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:651(Compiled Code))
4XESTACKTRACE                at io/netty/handler/codec/MessageToByteEncoder.write(MessageToByteEncoder.java:107(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:658(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:714(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:643(Compiled Code))
4XESTACKTRACE                at io/netty/handler/timeout/IdleStateHandler.write(IdleStateHandler.java:259(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:658(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext.access$2000(AbstractChannelHandlerContext.java(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext$AbstractWriteTask.write(AbstractChannelHandlerContext.java(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext$WriteAndFlushTask.write(AbstractChannelHandlerContext.java(Compiled Code))
4XESTACKTRACE                at io/netty/channel/AbstractChannelHandlerContext$AbstractWriteTask.run(AbstractChannelHandlerContext.java:918(Compiled Code))
4XESTACKTRACE                at io/netty/util/concurrent/SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:380(Compiled Code))
4XESTACKTRACE                at io/netty/channel/nio/NioEventLoop.run(NioEventLoop.java:357(Compiled Code))
4XESTACKTRACE                at io/netty/util/concurrent/SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
4XESTACKTRACE                at java/lang/Thread.run(Thread.java:736)

Any advice?
L.J.W

The information you post is so limited. More detail? Especially on the situation and use scenery?

Our netty usage is normal.what infomation else needed?

Can you provide a few (e.g. 5) jstack outputs while in this 100% CPU usage state, and a few (e.g. 5) jstack outputs when in a "normal" state?
A write is being processed in the stack trace above ... just curious how are you handling back pressure? When you are in this 100% cpu usage state ... what is the state of the peer you are communicating with (is it reading data "fast enough")? Also what does your local state look like ... can you provide a heap dump?

you might want to track the GC CPU as well. It looks like you use unpooled DirectByteBuffer. This will cause a high GC rate to clean up the DBB

Following is client code:
    bootstrap.channel(NioSocketChannel.class);
            bootstrap.option(ChannelOption.TCP_NODELAY, true);
            bootstrap.option(ChannelOption.SO_KEEPALIVE, false);
            bootstrap.option(ChannelOption.CONNECT_TIMEOUT_MILLIS, getConnectTimeout());
            bootstrap.option(ChannelOption.ALLOCATOR, PooledByteBufAllocator.DEFAULT);
            bootstrap.option(ChannelOption.RCVBUF_ALLOCATOR, AdaptiveRecvByteBufAllocator.DEFAULT);

and attchment is javacore file.(I am using IBM J9 JDK,javacore same as jstack in oracle jdk)

Following is client code:
    bootstrap.channel(NioSocketChannel.class);
            bootstrap.option(ChannelOption.TCP_NODELAY, true);
            bootstrap.option(ChannelOption.SO_KEEPALIVE, false);
            bootstrap.option(ChannelOption.CONNECT_TIMEOUT_MILLIS, getConnectTimeout());
            bootstrap.option(ChannelOption.ALLOCATOR, PooledByteBufAllocator.DEFAULT);
            bootstrap.option(ChannelOption.RCVBUF_ALLOCATOR, AdaptiveRecvByteBufAllocator.DEFAULT);

follow is full thread  stack:
issue-stack.txt

Can you try to run it again with higher setting for MaxDirectMemorySize to see whether it helps? The option looks like this:
-XX:MaxDirectMemorySize=1024m

luengnat,thanks for reply,but  when the issue occur,there are few business(in night),so I think it is not caused by high load.

How often does it happen? You seem to use quite an old JVM.

This is the First happen.

@likebean Did you find anything?

Closing and make with need more info


New Homepage

(Mostly) closes #213
Done

Global style updates
New homepage content
Lots of CSS organization
Locally hosted web fonts
Multi-col utility class(es)
Fixed some of the repeated H1s

TODO

~Properly organize the content that was on the homepage (and is now on the COVID-19 page) so that translations work. Help: @nditada cc @mverzilli~

Follow-up issues

Tighten up the footer design
Fix the remaining pages with multiple H1 tags
Move ~"contribute"~ "Contact" out of the primary nav (into footer)
Add Ivan's jazzy new logo(?)
Convert language links to dropdown(?)
Rename /act_and_prepare permalink to match new page title (what-do-do)? ...and figure out how to redirect the old path. I created this branch which adds this redirect plugin that seems to work, but I ran out of time before I could figure out how to get it to play nice with the translation plugin.

Looks great overall! Just a couple of comments below, mostly around follow up issues:

Add Ivan's jazzy new logo

Let's park this for another time. Two reasons:

I'm a bit concerned about impacting readability.
Changing the logo is something most of the org has to be onboard with. I don't see a need to make that change at the same time as this homepage overhaul. Let's leave it out so we reduce the list of issues we need to resolve before releasing.

Move "contribute" out of the primary nav (into footer)

Can we leave it in both places for now? Or there was a broad discussion on removing Contribute from the navigation header and I missed it?

Rename /act_and_prepare permalink to match new page title (what-do-do)?

Ideally we should keep both, what-to-do for consistency and act_and_prepare links into it around the internet can still reach the page. Someone should check Jekyll to see how it can get done. Nice catch raising up this issue!

@mverzilli @matiasgarciaisaia I have a copy of this branch locally and am working at fixing that conflict, and getting the tree structure back into the canonical   _sections/<....>//, which is easy.  Should Icreate the subdirectories for all the other languages other than "en", or will they autogenerate with the whole translation process?

@emersonthis @mverzilli    I looked at all the languages on my little cellphone -- all menus function in all languages.   Looks good to go from that standpoint
One bad image link I found.   Simple edit in _sections/COVID-19/en/06-keep-the-main-thing-the-main-thing.md
This link needs a leeding "/" (like so)

Sorry for the confusion about “contribute”... I meant “contact” which I think was discussed with Nico last week.
About the list of future issues... I included those mostly to indicate things I knowingly did not include in this PR (and don’t plan to). So of course we can hold off on any of them, like the logo, etc

On Mar 27, 2020, at 7:21 AM, weltyj<EMAIL_ADDRESS>wrote:

@emersonthis @mverzilli I looked at all the languages on my little cellphone -- all menus function in all languages. Looks good to go from that standpoint
One bad image link I found. Simple edit in _sections/COVID-19/en/06-keep-the-main-thing-the-main-thing.md
This link needs a leeding "/" (like so)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Oops, I found two more image links needing a leading slash in
_sections/COVID-19/en/05-this-is-not-normal-flu.md

I confess I'm at the limit of my git understanding.   There maybe a better way to do this, but I pulled the issue-213 branch and made the small edits to correct the image links -- and create a "en" directory in _sections/04-about/ .   I made a new branch with my edits.  I DID NOT create a PR for this in order to avoid confusion.  @emersonthis @mverzilli here is the branch:
https://github.com/flattenthecurve/guide/tree/jw-edits-issue-213

Ideally we should keep both, what-to-do for consistency and act_and_prepare links into it around the internet can still reach the page. Someone should check Jekyll to see how it can get done. Nice catch raising up this issue!
^^^
I'll check into that.

I just merged @weltyj 's changes into this branch. That seems to have resolved the broken images and updated the other language versions touched by this. Anything left to solve before this can get merged?

@mverzilli @bcardiff @emersonthis I would add a review approval, but it doesn't seem to meet the intention of the approval process since my edits are now part of the branch.  If you think it's ok for me to approve I will.

@mverzilli @nditada does this still need the “do not merge” label? I think everything mentioned above has been addressed. Let me know if there’s anything left for me to do on this.

Given how critical this change is, I've asked the other team leaders to confirm they're ok with the change as seen in the preview. Once they 👍 and you fix this link I'll merge. Amazing work @emersonthis 🙇

https://github.com/flattenthecurve/guide/tree/issue-213-fix-dont-link
@emersonthis @mverzilli
Early riser here :-)   That fixes the broken link which was pointing to #dont, needed to be #do-not in _sections/home/01-site-header.md

@mverzilli The link is fixed

Awesome! The only remaining bit to solve is what to do with the "STAY INFORMED" section. I'm raising that issue and will get to you as soon as I have further direction from core team. Sorry I didn't realize about that gap before :/

@mverzilli can you say a bit more about “the problem” that needs to be solved? I wasn’t aware there is an issue. Maybe we can propose solutions?


Update 20-packages-overview.md

I reworded a bit more to clarify the bit about how (I think) the required files work. @smith1511, can you add specifically which files are required for each type?


btn btn-secondary

seems to be a default setting for a lot of these buttons any fix?

fixed in 2020design1


Importing Local Data

Hello,
On the sample app, there is the option to 'Use your own data'.

On my local version of sanddance-explorer, I don't see that option. How do I include this?

It's a local react app with the sample code from sanddance-explorer.

You can pass a datasetElement in your props to Explorer.
https://github.com/microsoft/SandDance/blob/master/packages/sanddance-explorer/src/explorer.tsx#L72
The online SandDanceApp's button source is here:
https://github.com/microsoft/SandDance/blob/master/packages/sanddance-app/src/dataSourcePicker.tsx

Thank you! That helped and I am able to load my own data now.
I'm interested in including the Dark/Light theme button in my version of Sanddance.

I've tinkered around and included
theme: 'dark-theme',
in my explorerProps but it's not coming out too readable:

Any guidance would be appreciated.

The dark theme needs to be passed to 3 component areas:

The SandDance Viewer (as ViewerOptions)
The SandDance Explorer props (you have this already!)
Office Fabric UI

Take a look at how its done for the SandDanceApp on the web and how its done for the VSCode extension

Closing this issue for now, please feel free to re-open if necessary.


JsonSerializationException after updating from 4.1 to 4.2

After updating from 4.1 to 4.2 we get Newtonsoft.Json.JsonSerializationException : Error converting value {null} to type 'System.Single'. Path 'failure_reason', line 1, position 440.
Code to reproduce
var sdk = new NeverBounceSdk(neverbounceConfig.ApiKey);
var jobStatusRequestModel = new JobStatusRequestModel
{
    job_id = jobId
};
JobStatusResponseModel jobStatusResponseModel = await _sdk.Jobs.Status(jobStatusRequestModel);

Response json:
{
  "status": "success",
  "id": 5432650,
  "job_status": "complete",
  "filename": "Advanced mailing 2020-09-25 09-14.csv",
  "created_at": "2020-09-25 03:14:42",
  "started_at": "2020-09-25 03:14:44",
  "finished_at": "2020-09-25 03:16:14",
  "total": {
	"records": 28,
	"billable": 28,
	"processed": 28,
	"valid": 25,
	"invalid": 3,
	"catchall": 0,
	"disposable": 0,
	"unknown": 0,
	"duplicates": 0,
	"bad_syntax": 0
  },
  "bounce_estimate": 10.714285714285714,
  "percent_complete": 100,
  "failure_reason": null,
  "execution_time": 13
}

I have a fix to this, but I can't push the change to the origin to create a pull request. 'Unauthenticated'

@paul-aspinall I've fixed this in a fork at https://github.com/EvolutionJobs/NeverBounce and also upgraded from Newtonsoft.Json to System.Text.Json and added better handling of parse exceptions.
There's a PR #20 to merge that fork back here, but it's not compatible with .NET 4.5


WASM

Hi, very cool project! Not an issue, just a question, sorry: do you have any plans for WASM support? How do you think talc would compare against the default dlmalloc? Thanks!

No problem. The plan was to make functionality like this possible through the OOM handler feature.
The WASM memory API looks simple enough that the existing Talc API will be sufficient. (attempt to grow the memory on OOM and resize the arena accordingly via the oom_handler). Although in order to avoid adding lots of dependencies to Talc, I'll distribute the support via a separate script or crate. How does that sound?
I've just gotten a basic WASM project setup; I'll try have something done soon!

Great,
I've been keen to see a new allocator for wasm space ever wee_alloc was declared unmaintained

https://github.com/rustwasm/wee_alloc/issues/107
https://github.com/rustsec/advisory-db/blob/main/crates/wee_alloc/RUSTSEC-2022-0054.md
https://nickb.dev/blog/avoiding-allocations-in-rust-to-shrink-wasm-modules/
https://www.reddit.com/r/rust/comments/x1cle0/dont_use_wee_alloc_in_production_code_targeting/

We mentioned that lol_alloc by @Craig-Macomber as a honorable mention but would be nice to see some more collaboration around in wasm space to have some alternatives - code sizes are the biggest concern for wasm as you want to shrink your .wasm typically.

code sizes are the biggest concern for wasm as you want to shrink your .wasm typically

Just to note, for me, the biggest concern would be performance, not code sizes. lol_alloc, rlsf etc. are already quite small, in my opinion.

I imagine talc-wasm is going to come in relatively heavy, at least at first. I'll see what I can do.
If anyone happens to know off the top of their head, is there a recommended way to measure talc's size contribution to a wasm binary?

v2.2 has just gone up with WASM support. Take a look here for some details https://github.com/SFBdragon/talc/blob/master/README_WASM.md
I think it's quite satisfactory as-is for use in other projects, but let me know if there are any problems; esp. with OOM handling on extremely memory constrained platforms, like mobile devices.
I'll close this issue, so if anyone has more specific concerns (bugs, binary size improvements, etc. etc.) please open a specific issue for it. Thanks.


Package pgfkeys Error

When I ran demo coverletter.tex, it went wrong and outputed
! Package pgfkeys Error: I do not know the key '/tikz/fill overzoom image' and  I am going to ignore it. Perhaps you misspelled it.
I guess there is something wrong with the line
\photo[circle,noedge,left]{./examples/profile}
How to fix it?

How to solve this problem ? I a facing the similiar problem

The Tex version is too old, update it to V2016. More details


feat: Adding fabric8 k8s library and helm client for use in Infra API

Description
This pull request changes the following:

Gradle changes to use fabric8 k8s library
Gradle changes for using helm client in infra API

Related Issues

Closes #385

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


❓ Should useCameraDevices always return the "default" device? Front camera in black and white

Question
I'm not sure if this is a bug. I'm using a Pixel 4 and the default front camera appears to be the infrared camera (it's grainy and in black and white). When using the back camera I seem to get the "default" camera. I say default because it's the same one other apps seem to use or other libraries return.
Should useCameraDevices return the "default" front and back cameras? It seems like that' would make the most sense otherwise you'd have to be filtering cameras for each device. I've looked through the other issues and I can't see anyone else hitting this. Is this something I'm doing wrong?
What I tried
const Foo = () => {
   const devices = useCameraDevices()
   const device = devices.front
   return (
       <Camera
          ref={(ref) => (cameraRef.current = ref)}
          device={device}
          isActive={true}
        />
    )
}

VisionCamera Version
2.12.2
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Lol that's definitely a bug. You could try filtering devices yourself, it's pretty straight forward:

useEffect(() => {
  const devices = await Camera.getAvailableDevices()
  // ...
}, []

Ha ok good to know.
We resolved by filtering for the "ultra-wide-angle-camera"
 const wideAngleCamera = frontDevices.filter((dev) =>
          dev.devices.includes("ultra-wide-angle-camera")
        );

Black and white photos for us on huawei P20 and huawei P20 Pro. Seems to be with back wide-angle camera

we met the exactly issue in Google Pixel 4, it seems the issue because the result of Camera.getAvailableCameraDevices() is not consistent. as following screenshot:

in react-native-vision-camera/src/hooks/useCameraDevices.ts
the Camera.getAvailableCameraDevices() sorts 'wide-angle-camera' first, so useCameraDevices() would use this one as front camera.
while in our app,
the Camera.getAvailableCameraDevices() sorts 'ultra-wide-angle-camera' first

sorts first

No one said that Camera.getAvailableDevices does do any sorting. You are responsible for sorting that list.

This should be now fixed with the all new Devices API in V3! 🥳


ExtendedPropery with a dateformat value will fail to load from saved modelfile.

Describe the bug
When creating extendedProperty on Table. If the value of the extendedProperty is a string containing a datetime, Tabular Editor fails to open this file after it has been saved.
It can however open the same model from server, with the datetime string, without any problems
The following error is returned:

Error: Cannot convert value 'dd.MM.yyyy HH:mm:dd' to required type 'String'. Check path 'model.tables[x].extendedProperties[x].value

This is a picture how the string containing a datetime is stored in the model file:

To Reproduce
Steps to reproduce the behavior:

Create extendedProperty on Table object
set name = "test"
set value = "2020-11-18T13:23:25:147Z"
save model as model.bim
open model from model.bim file ctrl+o
select modelfile you just created
see error

Expected behavior
A clear and concise description of what you expected to happen.
Tabular Explorer should be able to open model.bim file with a extendedProperty containing a formatted datetime as value.
Observed behavior
The following error is returned:

Error: Cannot convert value '<dd.MM.yyyy HH:mm:dd>' to required type 'String'. Check path 'model.tables[x].extendedProperties[x].value

Application specifics
Tabular Editor version 2.13.0
Azure Analysis Services
Model Compatibility level 1500
Additional context
Tabular Editor seems to parse the value as [System.DateTime] when it should just be seen as a [System.String]
Tabular Editor is able to open the same model-object from the server without encountering this error.

I was not able to reproduce this. Can you provide a minimal Model.bim file that produces the error when loaded?

I have included a model with one table.
on that table it has an extendedProperty with the value 1900-01-01T00:00:00.000Z
When i open this file "Example.bim", I get the following error

I had to zip the file to be allowed to upload it
Example.zip

Thanks for getting back to me.
I wrote the following C# application using only the AMO library to deserialize the JSON (this is the same technique Tabular Editor uses to load the JSON), which causes the same error:

So in other words, this is not a bug in Tabular Editor but in the underlying AMO library provided by Microsoft. I will report the bug to them. Maybe you can use a JsonExtendedProperty as a workaround in the mean while?


Remove devicelab mac android tasks from manifest.yaml

All these tests are already running in luci and were added to
prod_builders.json file.
Bug: https://github.com/flutter/flutter/issues/71960
Bug: https://github.com/flutter/flutter/issues/74059
Pre-launch Checklist

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

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

Can you update dev/devicelab/README.md on how to run these locally now?

Can you update dev/devicelab/README.md on how to run these locally now?

It's the same as before.  dart bin/run.dart -t <test>

It's the same as before.  dart bin/run.dart -t <test>

none of the tests from prod_builders.json seem to run when I dart bin/run.dart -a

none of the tests from prod_builders.json seem to run when I dart bin/run.dart -a

lders.json seem to run when I dart bin/run.dart -a

This change should not affect the way the runner is executing tests unless you try to use stages flag. Can you please share the full command you are using and the the current working directory?

lders.json seem to run when I dart bin/run.dart -a

This change should not affect the way the runner is executing tests unless you try to use stages flag. Can you please share the full command you are using and the the current working directory?

I'm just on master head on a mac.
cd dev/devicelab
(connect an android and ios phone)
dart bin/run.dart -a

I'm just on master head on a mac.
cd dev/devicelab
(connect an android and ios phone)
dart bin/run.dart -a

-a is trying to use stages, individual tests should still run. If we want to keep that functionality we need to update the runner to read prod_config.json instead of manifest.yaml

-a is trying to use stages, individual tests should still run. If we want to keep that functionality we need to update the runner to read prod_config.json instead of manifest.yaml

ah I see. Will try. Thanks!

ah I see. Will try. Thanks!

Works, thanks!

Works, thanks!

lders.json seem to run when I dart bin/run.dart -a

This change should not affect the way the runner is executing tests unless you try to use stages flag. Can you please share the full command you are using and the the current working directory?

Filed https://github.com/flutter/flutter/issues/74660 to get this working, or update the README.

lders.json seem to run when I dart bin/run.dart -a

This change should not affect the way the runner is executing tests unless you try to use stages flag. Can you please share the full command you are using and the the current working directory?

Filed https://github.com/flutter/flutter/issues/74660 to get this working, or update the README.


Create a Theme (Previously: Move all styles.js to global css)

Motivation:
When this project was first started each component and page has been using useStyles to inject styles as classes into each html element. We should be opting for a global css or sass style sheet.
File styles.js has 270 lines of code (exceeds 250 allowed). Consider refactoring.
https://codeclimate.com/github/civictechindex/CTI-website-frontend/src/components/Header/styles.js#issue_5fff8bee8ce7df0001000069

Kevin and I screen shared on Monday and discussed options for regularizing our styles. He and I are both more familiar with straight CSS (with or without using SASS to compile that css from separate files). But looking at our existing code, the problem we are having is more about not using shared styles than it is about using styles.js. We are both open to migrating everything from jss to plain css if that is what the team prefers to use. But before doing that, @kevinashworth is going to experiment with extracting shared styles from existing jss to create a theme that can be shared across all pages - leaving us with only the styles specific to a page or component inline in the page/component file.
One question he and I have is about the use of Material UI with JSS. I am not clear how that is supposed to work. I would appreciate it if If someone who is more familiar with Material UI could give us an overview of how this project intends to use it - and where the Material UI components and styles leave off and where our custom code begins.
ETA: Hoping to have more definition of the issue and possibly a decision on direction at this Tuesday's meeting (1/18/21). Then the real work can begin and will take a few weeks?

Kevin and I screen shared on Monday and discussed options for regularizing our styles. He and I are both more familiar with straight CSS (with or without using SASS to compile that css from separate files). But looking at our existing code, the problem we are having is more about not using shared styles than it is about using styles.js. We are both open to migrating everything from jss to plain css if that is what the team prefers to use. But before doing that, @kevinashworth is going to experiment with extracting shared styles from existing jss to create a theme that can be shared across all pages - leaving us with only the styles specific to a page or component inline in the page/component file.
One question he and I have is about the use of Material UI with JSS. I am not clear how that is supposed to work. I would appreciate it if If someone who is more familiar with Material UI could give us an overview of how this project intends to use it - and where the Material UI components and styles leave off and where our custom code begins.
ETA: Hoping to have more definition of the issue and possibly a decision on direction at this Tuesday's meeting (1/18/21). Then the real work can begin and will take a few weeks?

The team will update with decisions.  @nrrao has already started using the theme that @kevinashworth has proposed.

The team will update with decisions.  @nrrao has already started using the theme that @kevinashworth has proposed.

Closed by #243

Closed by #243


Move policy from kubernetes plugin to CNI plugin

calico_kubernetes/calico_kubernetes_cni.py, line 224 [r9] (raw file):
Paranoia: if _unassign_ip_address fails for an unforeseen reason, we'll dealloc the IP without deleting the endpoint. I'd prefer to delete the endpoint first, and have the consequence of an unforeseen failure be leaked IPs.
I think that concern might go away if we Pokemon catch in _unassign_ip_address function, but is there a reason to depend on that?

Comments from the review on Reviewable.io

calico_kubernetes/calico_kubernetes_cni.py, line 134 [r9] (raw file):
@caseydavenport,  have you thought about this one at all?

Comments from the review on Reviewable.io

calico_kubernetes/calico_kubernetes_cni.py, line 134 [r9] (raw file):
I actually wasn't aware we did this - I thought we removed this code a while back.  As it is, it shouldn't be a problem since we always have a profile per pod, we won't hit the race.
However, this will need to change when we look at sharing profiles for better perf.  I don't think we can get away with a compare-and-delete operation in etcd, since the profile object doesn't change I don't think when we add endpoints to it.  Might require locking or the new data model that some people have been tossing about.  Definitely needs more thinking.

Comments from the review on Reviewable.io

calico_kubernetes/calico_kubernetes_cni.py, line 588 [r9] (raw file):
This will lose information about the escaped characters, so we can't unescape them. That means that we will have collisions on policies (e.g. tag*1 == tag+1). The original design converted to hex character codes; did we change that deliberately?

Comments from the review on Reviewable.io

calico_kubernetes/calico_kubernetes_cni.py, line 588 [r9] (raw file):
Yes - this was deliberate.  AP was against properly escaping these since the resulting string was less human-readable, and real-world clashes seemed unlikely.

Comments from the review on Reviewable.io

Reviewed 1 of 3 files at r8, 3 of 3 files at r9.
Review status: all files reviewed at latest revision, 36 unresolved discussions, all commit checks successful.

calico_kubernetes/calico_kubernetes_cni.py, line 102 [r9] (raw file):
dump isn't a very descriptive variable name; how about json_result or json_output?

calico_kubernetes/calico_kubernetes_cni.py, line 111 [r9] (raw file):
Don't use % in log statements (pass variables as args to the log function instead).

calico_kubernetes/calico_kubernetes_cni.py, line 144 [r9] (raw file):
It's borderline. Functions are clearer to read if all of the operations are at the same level; the create() function is a composition of a few high-ish level functions. Also, functions should strive to be shorter than a screen's length; easier to test small functions that do one thing than god functions that do everything.
I'm inclined to keep the current split, because if create() was any bigger then inlining this function would make it too big.

calico_kubernetes/calico_kubernetes_cni.py, line 190 [r9] (raw file):
We should log e.output and e.returncode, in case the command gave us something useful.
Also, except Exception, e: is a deprecated syntax; it's ambiguous, so you should always use except Exception as e:.

calico_kubernetes/calico_kubernetes_cni.py, line 191 [r9] (raw file):
I'm not sure it makes sense to return the underlying error code here; the caller has no idea what those codes correspond to. Either we should return 1 on all failures, or we should synthesize our own error codes (i.e. 1=general failure, 2=ipam failure, etc). I'd go with the former for now.

calico_kubernetes/calico_kubernetes_cni.py, line 201 [r9] (raw file):
This should probably be a constant.

calico_kubernetes/calico_kubernetes_cni.py, line 246 [r9] (raw file):
We used to have a _configure_profile; I think that better describes what's going on.

calico_kubernetes/calico_kubernetes_cni.py, line 261 [r9] (raw file):
Can we make a better error message than "Cannot create profile"? Are we assuming that a better error was logged inside create_profile? This might be OK, but we should leave a comment explaining why, if that's the case. But ideally we can beef up the error here (e.g. catch an EtcdException and write a descriptive log; fall back to this error to catch unexpected errors).

calico_kubernetes/calico_kubernetes_cni.py, line 277 [r9] (raw file):
Yep, that's the right place. Should docstring the expected exceptions there: """ throws CalicoIPAMError if ...""" or something like that.

calico_kubernetes/calico_kubernetes_cni.py, line 283 [r9] (raw file):
I'd prefer you use a new variable json_result or something like that; reassigning an existing variable can be OK, but it can also mask programming errors. I generally would reuse the same variable if it's the same type (e.g. you're stripping whitespace on string input), but not when you're transforming to a different type as we are here.

calico_kubernetes/calico_kubernetes_cni.py, line 333 [r9] (raw file):
Popen is almost never the right answer. Why not check_output()?

calico_kubernetes/calico_kubernetes_cni.py, line 346 [r9] (raw file):
Indenting looks funny here. Too many spaces? Also suggests that we're not covering this line with UTs... can you fix that too if it's the case?

calico_kubernetes/calico_kubernetes_cni.py, line 384 [r9] (raw file):
I think this comment should be fleshed out a bit -- why are we assuming this? Critically, what bit of code/behaviour do I need to check to see if that's still the case?

calico_kubernetes/calico_kubernetes_cni.py, line 445 [r9] (raw file):
"Adding namespace tag...", to disambiguate from the "Adding tag" log below. (Rule of thumb -- never make the same log in two different places; it makes it harder to work backwards from a log to the code).
Also, s/ %/,/

calico_kubernetes/calico_kubernetes_cni.py, line 455 [r9] (raw file):
s/ +/,/ (don't do string interpolation unless needed).

calico_kubernetes/calico_kubernetes_cni.py, line 485 [r9] (raw file):
Is this what we want? If we're doing ns_isolation, but namespace==None, then we'll fall through to the allow all branch, which I don't think is correct.
I think we should nest:
if POLICY==ns_isolation:
  if ns==kube-system:
    allow all
  else:
    assert namespace
    allow namespace
else:
  allow all

Alternatively could de-dupe, like so:
if POLICY==ns_isolation && ns != kube-system:
  assert namespace
  allow namespace
else:
  allow all

This is less code, but the logic is slightly harder to grok; I don't mind duplicating two lines (approach 1) to make the flow clearer.

calico_kubernetes/calico_kubernetes_cni.py, line 506 [r9] (raw file):
Typo -- can you run through PyCharm's warning list to catch errors like this? Ideally you'd have no warnings in your IDE.
For things like PyCharm's "Too broad exception" error, OK to add pycharm-specific annotations like "        # noinspection PyBroadException" (Though always add your own comment describing why it's ok to disable the inspection).

calico_kubernetes/calico_kubernetes_cni.py, line 534 [r9] (raw file):
This code is brittle; if there is no "=", then we'll hit an error here (since that will turn into "key,value = ["label"]. If there are two "=" characters hilarity will also ensue.
This is a job for regexes; we should specify a strict match on label (\w+)\=(\w+)  (note trailing whitespace), and log an error if the regex doesn't match. Open question as to whether we should allow a pod to start if one of its rules failed to parse; the principle of least surprise suggests that we should fail fast here, rather than programming only some of the rules that were requested.

calico_kubernetes/calico_kubernetes_cni.py, line 597 [r9] (raw file):
Is this really a warning-level log? Probably most pods won't have the 'label' or 'annotations' metadata keys, so I suspect it's not exceptional. (I think we shouldn't log at all, and just log in the caller if it's unexpected for this to reply with no keys).

calico_kubernetes/calico_kubernetes_cni.py, line 598 [r9] (raw file):
Should be metadata = [] for consistency, since we return a list in the success case. Then callers can iterate over the returned list safely (rather than having to test for None, just do for k in metadata, which is a no-op for an empty list. If having no metadata is exceptional, the caller can say if not metadata: <log exception>.

calico_kubernetes/calico_kubernetes_cni.py, line 615 [r9] (raw file):
This indentation is not correct -- want the else to be branched from the for:, not the if:.
Also, the indentation in this function is not correct (5 chars not 4?), as discussed.

calico_kubernetes/calico_kubernetes_cni.py, line 780 [r9] (raw file):
What's this for? Looks like you're also checking that the ipam block has a type, but that should give a different error if that's what you're checking.
Also, shouldn't that cause an error in the ipam module itself? Do we really care what's in the ipam blob?
A comment would be useful to explain what's going on, if you do keep this check.

calico_kubernetes/tests/test_cni_plugin.py, line 183 [r9] (raw file):
We should be testing the failure cases for the IPAM plugin too, both at the UT level (i.e. calling function handles failure properly) and the FV level (call the top-level create(), stub out non-plugin calls, and check that we get the right output.)
Probably fair to leave FVs as a TODO: in the code for now, but we should get them on the agenda. Definitely need to UT failure cases before we can merge this PR though.

Comments from the review on Reviewable.io

calico_kubernetes/calico_kubernetes_cni.py, line 588 [r9] (raw file):
At very least we should make a comment explaining this. And the design doc should probably be mothballed (since it doesn't reflect reality any more). I don't think this is a production-ready design, but it's probably OK for our current demo implementation.

Comments from the review on Reviewable.io

The plugin should probably still be called 'calico_kubernetes.py', assuming we're not planning to keep the two side-by-side.

calico_kubernetes/calico_kubernetes_cni.py, line 588 [r9] (raw file):
Yep, the design doc can go away at this point.
FYI we are tracking this: https://github.com/projectcalico/calico-kubernetes/issues/8

Comments from the review on Reviewable.io

Closing for now since this is quite old.


ReferenceError: process is not defined

Hi,
I tried to use the ApiReference in a new Vue project, but I'm getting. ReferenceError: process is not defined.
Reproduction steps:

Create a new Vue project: npm create vue@latest.
Install dependencies: npm install.
Add @scalar/api-reference: npm install @scalar/api-reference
Replace the contents of App.vue with:

<script setup>
import { ApiReference } from '@scalar/api-reference'
</script>

<template>
  <ApiReference spec-url="https://petstore.swagger.io/v2/swagger.json" />
</template>

Start the project: npm run dev.
Open the page & check the console.

Initially, I tried to do it in my existing project and got this error, so I thought maybe I'll try with a brand new project but it was still not working. I followed the exact steps above.
I can provide a reproduction repo if needed.
I'm on Node v18.17.1.

Yup, that seems to be it.
Got it working with the polyfills. Thanks Hans!

We can remove the need for the polyfills

Wait, this if fixed already. :) We switched to our own parser, which doesn’t require polyfills anymore: #1131


Bug:  QA cert event / Tee import from historical data is not reflected in data table

Context
When a user imports from historical data in the QA cert event / Tee module, the system displays a success message but the imported data is not reflected in the UI.
Steps to Reproduce

Log in to ECMPS and navigate to the Cert events, extensions, and exemptions module
Check out a config
Import from historical
Import the data

The system displays a success message but the data is not reflected in the UI. As apart of the scope of this ticket need to ensure that data imported from historical is displayed in the applicable data tables
Testing
Tester: @JanellC

Bug remediated. Functionality works as expected


Update README.md

Sorry, this project is still in the development version, you can use the following code to create a demo project to try;
npm i bpframework-cli -g
bpframework init


[WFLY-15518] Test preparation errors shall cause failure (connector)

Fixes https://issues.redhat.com/browse/WFLY-15518

I have fixed JBJCA-1435. We would be able to remove @ignore after IJ 1.5.3 is released and merged.


Setup blog with VuePress

This issue could be used as a whiteboad where we can persist all things we would like to do for the blog infrastructure. Use comments for suggestions
Framework :

VuePress
Vue 3 (beta)

Code rules :

Use Composition API
TypeScript

Themes :

@recodable/vuepress-theme-tailwind-blog
https://vuepress-theme-tailwind-blog.netlify.app/#intro

Plugins :

vuepress-plugin-container
vuepress-plugin-git-log
vuepress-plugin-nprogress
vuepress-plugin-table-of-contents
vuepress-plugin-typescript + vuepress-types
vuepress-plugin-medium-zoom

Other (but not the least) :

Code Surfer

is Vue 3 relatively stable ? I don't want to refactor things for it to work in the next months

Yes, it would not evolve dramatically. No worry about that, we will don't use advanced features.

Awesome, I will setup a boilerplate soon

@KeziahMoselle some news ?


Add license file and GitHub license to the project

Please, it could be interesting to add a license file and configure the project license on github.
Thanks

Done

Thank you
On 19 December 2016 at 06:26, nyholku<EMAIL_ADDRESS>wrote:

Done
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nyholku/purejavacomm/issues/94#issuecomment-267884853,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACV0cmjFwDWiFFhkeukyZFIfSeqI07Euks5rJhWCgaJpZM4K_PXE
.

--
Alberto


No hooks directory error on fresh clone

Short description of the problem:
Getting
Error { [Error: ENOENT, no such file or directory '/Users/barbarian/TS/inceptd-app/hooks']

What behavior are you expecting?
No error
Steps to reproduce:

Clone fresh app
run ionic platform add ios --save
observe error

**Run ionic info :
Cordova CLI: 5.0.0
Gulp version:  CLI version 3.8.8
Gulp local:   Local version 3.9.1
Ionic CLI Version: 1.6.4
Ionic App Lib Version: 0.3.8
ios-deploy version: 1.7.0
ios-sim version: 4.1.1
OS: Mac OS X Yosemite
Node Version: v0.12.2
Xcode version: Xcode 7.3.1 Build version 7D1014

Could you try updating your CLI to version 2.x:
npm install -g ionic
Thanks!

works after upgarade


Fix: Move community oauth service bootstrapping to a factory class.

This allows the community oauth auth type to work. The reason it didn't work previously is because callables bound to core accept two parameters, $app and $args while the bound callable was expecting a string. This caused the callback url to always be an empty string which would break oauth.
I took this opportunity to move this logic into a factory class. Note that all of the dependencies of the factory class are provided by the IoC container.

:+1: good catch on the $this->app switch

@joe-meyer that was all me ;)

@joe-meyer mnkras is the one who noticed, not me :)

Reopening against develop


Add package s3scanner

Description of changes

This PR adds a new package, s3scanner.
S3scanner is a security tool written in Go to scan for misconfigured S3 buckets across S3-compatible APIs.
Project repository: https://github.com/sa7mon/S3Scanner
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Hey, there are some commit guidelines that you need to follow when making PRs to nixpkgs. Please read them here: https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#commit-conventions

Preferably, you should also add meta.platforms as applicable.


Updated README to list macOS as supported platform.

Context

Update README to list macOS as supported platform.

Choices

Changed README for English and Korean, still requires Chinese translation but I don't know any single Chines characters.

Checklist before requesting a review

[X] I have performed a self-review of my code
[X] I've added documentation about this change to the README.
[X] I've not introduced breaking changes.

Will merge as soon as i've created a new release, currently only the :dev image supports macOS


[Crypto] Add utility methods on HashValue for nibbles

Motivation
Add utility methods on HashValue for nibbles. Will be used in https://github.com/libra/libra/pull/978.
Have you read the Contributing Guidelines on pull requests?
Y.
Test Plan
CI.
Related PRs
None.

@bors-libra r+

:pushpin: Commit 4bbd4f7 has been approved by lightmark

:hourglass: Testing commit 4bbd4f7195d0f0d6a2df41d7cae3053f46ec0fbb with merge 7a6725422c809e70e97beacdd736305d6cd508b8...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: lightmark
Pushing 7a6725422c809e70e97beacdd736305d6cd508b8 to master...


Add binaries-location option

This PR adds a new parameter to specify a relative path to the release archive where one can find the binaries. For example, if the binaries are located in the 'bin' directory of the release archive, the parameter should be bin. As multiple files may exist in the release archive, the option rename-to has no effect combined with binaries-location.

Closes #25

@jonaprieto please readd the node_modules directory. GitHub actions requires that to function correctly.

Ok, I didn't know.

The README examples are used as the latest version, v0.10.0

Looks like there's still a big delta here between the original branch and your changes. Would be great to reduce that so i can adequately review it

Ok, let me know if I need to do something else. I guess after considering this PR, you need to generate again the node_modules folder with the new updates.

Thank you! can you add a smoke test to https://github.com/jaxxstorm/action-install-gh-release/blob/master/.github/workflows/test.yml?


Feedback-page

Title and Issue number

I have added the project. Can it be merged now?
Close #4123

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

@MohitGupta121 ,@TusharKesarwani Can it be merged now?

Sorry for the inconvinience, I have completed the necessary changes.
@MohitGupta121 ,@TusharKesarwani  Can it be merged now?


Google Sheets v3 API is being shutdown on March 3, 2020

Hi!
On the 3rd of October 2019 I received an email from Google saying that "Google Sheets v3 API is being shutdown on March 3, 2020". Sounds like the plugin has to be updated to use Google Sheets v4 API.
Here is the email from Google:

Hello Sheets Developer,
We're writing to let you know that Google Sheets v3 API will be shut down on March 3, 2020.
What do I need to know?
The Sheets v4 API, launched in 2016, opened new doors to custom development with programmatic access to critical features like conditional formatting, charts and pivot tables. Since then, we’ve continually improved version 4 by supporting new Sheets features and introducing developer metadata.
As part of the migration to the Sheets v4 API, we will shut down the Sheets v3 API on March 3, 2020.
What do I need to do?
To ensure projects originally built on the Sheets v3 API continue working long after it is gone, please migrate your projects to the Sheets v4 API before March 3, 2020.

You can review this migration guide which provides tips on how to transition your apps, including a mapping of operations in Sheets v3 API to operations in Sheets v4 API and some ideas for using the new functionality to your advantage.

Note that the Sheets v4 API does not provide the "List spreadsheets for the authenticated user" operation. However, this operation can be replicated via the Drive API Files.list method.

We have identified that the following projects have used the Sheets v3 API in the past 30 days:

(removed)

Need help?

Additional documentation is available to help you get started on a new project or leverage the content and appearance controls not available in previous versions.

Please bear in mind that after March 3, 2020, the Sheets v3 API will no longer be supported.
Thanks for being a valued Sheets Developer.
Sincerely,
The Sheets API team

I have upgraded the Google Sheet Plugin with latest API's here : https://github.com/jfmonteil/Pentaho-Google-Sheet-Plugin.
Any comments welcome.

Cool, thanks. Will look into it


add hadoop smoke test for openeuler

Description of PR
add hadoop smoke test for openeuler
change the cgroup of hdfs and yarn from hadoop to root in openeuler, otherwise, the namemode of hdfs has not the permission to create directories during smoke test.
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'BIGTOP-3638. Your PR title ...')?
[ ] Make sure that newly added files do not have any licensing issues. When in doubt refer to https://www.apache.org/licenses/

@guyuqi smoke test success for mapreduce/yarn/hdfs:
mapreduce component:

yarn component:

hdfs component:

@guyuqi smoke test success for mapreduce/yarn/hdfs: mapreduce component:  yarn component:  hdfs component:

The hadoop smoke test is ok , including hdfs/mapreduce/yarn.
@guyuqi please help review the code, thanks.

LGTM


How would we use monotone_constraints ?

I see that categorical features supports a string as param, but I am unsure how to pass monotone_constraints as it requires a list of -1,0,1 specified for each feature. How would we go about setting it ?
If we take the example of  https://github.com/frozenlib/lgbm-rs/blob/4b64ee9c721a4543c239f5152d53f0f0d147ce9e/lgbm/tests/booster.rs#L86
Which type should this be (in the case of monotone_constraints), i64 ?

For type = multi-int parameters such as monotone_constraints, you can use [i32],[i64], Vec<i32> Vec<i64> &'static str as follows.
p.push("monotone_constraints", vec![0, 1]);
p.push("monotone_constraints", [0, 1i64]);
p.push("monotone_constraints", "0,1");

Parameters are converted to a string and passed to lightgbm, so the result is the same in all cases.

Thank you ! Worked


Motor.run_to_position(blocking=False) does not check that no other calls are currently in progress

Motor.run_to_position(blocking=False) starts new thread for each call.
Multiple calls with with in short time interval will result in multiple simultaneous calls to Device.get(), which blocks on Device._instance.portcond[self.port].wait()
BuildHAT.loop will wake threads in random order.
It will be better, if each new call cancels all outstanding requests

Thanks a lot for pointing this out.  I'll work on this soon, I was thinking I can possibly
implement a queuing type mechanism so the threads are woken in the correct order.

I've just committed to 'main' changes that preserve the ordering of non-blocking motor commands.
Also if you do for example:
        m = Motor('A')
        m.run_for_seconds(5, blocking=False)
        m.run_for_degrees(360)

The 'run_for_degrees' call, will wait for all non-blocking calls to finish, prior to running.

@chrisruk, thank you for fixing this!
On a similar note, let's say I'm using a motor for steering and accepting and queueing remote commands. If I queue a command run_for_degrees and it's not yet started executing, but another command run_for_degrees in different direction comes in, I should be able to go to hat.motorqueue[target_port].pop or delete another command from queue, right?
That's unless that command is currently executing. If it's already in progress, any way to see what command is in progress on each port, and interrupt it if needed?

You'd have to find the correct run_for_degrees command in the queue which you'd want to remove, which could be tricky as
the synchronized queue class doesn't publicly expose the ability to remove specific elements as far as I'm aware, apart from grabbing and removing the first element, via .get().
If a command is currently in progress, currently you wouldn't be able to interrupt it.  That's an interesting question though.

Will close this issue now, as threads should now be woken in the correct order, due to the use of a queue system.


Add support for creating a pipeline

Currently it is only possible to update a pipeline and delete a pipeline, but not creating a new pipeline.
Goal of this request:

We would like to have a code quality run on every pull request branch, but it is currently not possible to have a regex for the code quality pipeline branch name (would like to make a feature request for this too, if you could tell me how?)
Seeing as previous is not possible, we will make a new code quality pipeline per branch so that we can execute the code quality on the specific branch

The CLI cannot expose capabilities which are not available through the underlying API. This is really a feature request for the API which should be done through Adobe Support.

@justinedelson  sure, how can this be done? what kind of support should i contact? I don't think I should / can open a daycare ticket for this?


feat: private schemas and contracts

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


Add words ending with "sy"

Add words ending with sy

[x] Autopsy
[x] Biopsy
[x] Busy
[x] Cutesy
[x] Clumsy
[x] Controversy
[x] Cosy
[x] Cheesy
[ ] Courtesy
[x] Creasy
[x] Drowsy
[ ] Epilepsy
[x] Embassy
[x] Fantasy
[ ] Gypsy
[x] Hypocrisy
[ ] Idiosyncrasy
[x] Jealousy
[x] Limpsy
[x] Prophesy
[ ] Queasy
[x] Quinsy
[x] Unsonsy
[x] Whimsy

Refer Contribution.md for more details on how to contribute.
Comment the word/words you're working on to avoid conflicts.
Add reference to this issue i.e Issue #547 in your pull request description.

Working on Jealousy, Fantasy and Embassy

Working on Autopsy, Busy and Gypsy

working on Cheesy, Clumsy, Cutesy

Working on Controversy, Prophesy, Hypocrisy.

working on whimsy, biopsy

working on Unsonsy, Quinsy and Limpsy

Working on Drowsy, Creasy

Working on Queasy and Epilepsy

I'll add rosy

I would add 'goosy' and 'nutsy'

adding easy, greasy and pu*sy #547


Importing Constructor

When upgrading from V5 to V6 and using Mef Attributes, Importing Constructor now throws an error stating that ImportingConstructor exists in both system component model and dryioc.

Try to remove the reference to System.ComponentModel.Composition.
Btw, what is your target framework?

@starprog ,
Did my suggestion helped?

Please update DryIocAttriibutes.dll to v6.0.1. Hope it helps.

My apologies, I for some reason did not get notified on your reply but kept on working. I will check it out and let you know thanks.


IAST source test

Description
Add IAST's Sources tests
Move current test (Sinks tests) to new sink package
Check list
Your PR is not ready to be reviewed? Please save it as a draft :pray:

[x] Follows the style guidelines of this project (See how to easily lint the code)
[x] CI is passing
[ ] There is at least one approval from code owners

Yes to all? Feel free to merge it whenever you want :heart:

Just a suggestion, it would be nice to have tests that request the secure URL and check that it does not return any source. For example, the controller could do a decode to avoid injections, in such a case we would not have to generate any event/message/source.

Thanks! I will keep it in mind for future implementations. These tests aims to check if we are "tainting" the current implemented sources more than check the vulnerability, we use this approach to to facilitate implementation in different languages as @smola suggested here


Move rotation of URL upstream in the init path

Has the benefit of preserving immutable data structures in more code, and isolates the rotation to the point at which a new connection is created for a given service. Seems like a lower impact change

comparison with master - https://github.com/mobilecoinofficial/MobileCoin-Swift/compare/master...the-real-adammork:task/ios-load-balancer-squashed-low-impact?expand=1


Use tags for reusable GitHub workflow calls

For example, change the following in .github/workflows/pr.yml from:
slateci/github-actions/.github/workflows/chart-repo-test.yml@master

to:
slateci/github-actions/.github/workflows/chart-repo-test.yml@v1

Apply this methodology to all references to reusable GitHub workflows.

This is related to https://github.com/slateci/slate-client-server/issues/248.


ENH/DOC: Overhaul callbacks doc, improve tiff export

This PR:

Overhauls organization of the callbacks documentation, leaving it much more readable.
Documents "subscription factories" and LiveRaster, both previously unmentioned in docs.
Provides new examples for automated data verification, automated TIFF export, and automated HDF5 export via suitcase. (cc @licode)
Nukes make_tiff_exporter in favor of LiveTiffExporter, which (1) can write TIFFs out live, potentially letting @sbillinge's software crank in real time and (2) incorporates some of the functionality in @pavoljuhas's #263. It's still comparatively light but can be more easily extended for more specific use cases.

Closes #13

With @tacaswell 's blessing


Adding international stock exchanges (ASX, HKEX, LSE, SGX, TSX)

Hi! This thing is great :)
As a request - could the other international stock exchanges be added? Their list of shares per exchange is available from the same site  as the american exchanges you have already.
You may have to split out the output into a separate folder per exchange, as I believe some tickers are not globally unique (The same ticker exists against a different company on the Singapore stock exchange as on the american exchanges).
Thanks!

Oops! Sorry for the late reply. Yeah, I can certainly add those. I wasn't sure if there were interests in international stocks. And thanks for the tip! I'll keep that in mind. I'll keep this open, until I actually add them.


loreAPI  for ja?

Please Is there a Japanese  loreAPI?
Not found API
https://xivapi.com/lore?string=legendary&language=ja

I'm sorry I solved it.


Refactor PostcodeConditionTests

Resolves #24 Refactor Postcode Tests.
Summary
Refactored PostcodeConditionTests.
Details

Create extendible PostcodeConditionTests for when we add new countries
Add tests for United States post codes
Add test for changing countries in PostcodeCondition
Update PostcodeCountries to include allValues convenience var
Make PostcodeCountries.regex public
Alphabetise enumeration values.

Current coverage is 42.74% (diff: 100%)

Merging #37 into master will increase coverage by 1.14%

@@             master        #37   diff @@
==========================================
  Files            35         35
  Lines           524        524
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            218        224     +6
+ Misses          306        300     -6
  Partials          0          0

Powered by Codecov. Last update c10005a...7070916

@madhikarma The updated tests is based (very loosely) to things I've seen in the way SwiftLint handles its tests.


Support multiple image tags for image removal

Fixes #89 #90 #94

@aharonha @rohansingh

Thanks

No, thank you. Sorry for the delay.
On Wed, Jul 29, 2015 at 5:01 PM, aharonha<EMAIL_ADDRESS>wrote:

Thanks
—
Reply to this email directly or view it on GitHub
https://github.com/spotify/docker-maven-plugin/pull/113#issuecomment-126094729
.

--
David Xia
Software Engineer
<EMAIL_ADDRESS>


new issue with perworldplugins - plugin messages not appear

Hello plugin creator or anyone reading this,
I tried the latest version you posted on Spigot and I'm happy to say that the bug in Essentials chat has been fixed!
But there is a new bug now on my server that you should check:
Every time when you do a command in the plugins, it just doesn't register anything, but if you execute the command, it working but not doesn't register anything in the chat, take an example: I updated someone on luckperms, I don't see a message about it in the chat
I create an NPC in citizens and it doesn't register anything either
I would appreciate it if you could update me about this problem!

This problem is not caused by my plugin.


Tracking issue for platform specific integer literals

This is the meta-issue for platform specific integer literals.  See https://github.com/dart-lang/sdk/issues/33160 for background discussion.
The decided upon course of action is here: https://github.com/dart-lang/sdk/issues/33160#issuecomment-392910496 (also summarized below).
TODO:
Step 1: (For Dart 2 release):

[ ] Update informal specification: https://github.com/dart-lang/sdk/issues/33283
[ ] Update formal specification: https://github.com/dart-lang/sdk/issues/33284
[ ] kernel: verify correct constant evaluation: https://github.com/dart-lang/sdk/issues/33285
[ ] dart2js: issue an error if an integer literal cannot be exactly represented as a double: https://github.com/dart-lang/sdk/issues/33286
[ ] ddc: issue an error if an integer literal cannot be exactly represented as a double: https://github.com/dart-lang/sdk/issues/33287

Step 2: (Post Dart 2):

[ ] kernel: allow all integer literals which can be exactly represented as a double when compiling for a JS platform
[ ] kernel: emit errors for literals which cannot be exactly represented using the platform integer
[ ] analyzer: allow all integer literals which can be exactly represented as a double when compiling for a JS platform
[ ] analyzer: emit errors for literals which cannot be exactly represented using the platform integer
[ ] analyzer: lint for cross platform integer literals

More details, copied over from https://github.com/dart-lang/sdk/issues/33160#issuecomment-392910496 .
Step 1 - In the Dart 2 timeframe:

It is an error if a literal is not exactly representable in 64 bits (current errors and warning)
Literals are interpreted as platform numbers (option 2 above)

So for example 0xffffffff00000000 will denote a different value on different platforms.

dart2js and DDC will report errors if a literal cannot be represented exactly in JS

Step 2 - In the post Dart 2 timeframe:

It is an error if a literal is not exactly representable in 64 bits when compiling to native
It is an error if a literal is not exactly representable as a double when compiling to JS
It may be desirable to have an opt-in int to warn if any literal is not in the intersection of the two

An implication of all of this is that we have (more) platform specific errors and warnings.  In the short term, these will only be surfaced by the compilers.  The analyzer/IDE may or may not choose to offer a way to select a platform for additional errors and warnings.
Implementation implications:
Step 1:

Requires no further work from kernel, except to guarantee that it does no incorrect-for-the-platform constant folding (which it already must guarantee)
Requires no further work from the analyzer (modulo existing bugs in platform correct constant evaluation)
Requires DDC and dart2js to warn if a literal is not exactly representable in JS

Step 2:

Requires kernel to support literals that cannot be represented as 64 bit integers (at least when compiling to JS)
Requires the analyzer/IDE to either stop warning on literals that exceed 64 bits, or else provide a platform selection mechanism to allow the correct set of errors and warnings to be surfaced.

cc @lrhn

There should be a step to announce this breaking change as well.