*: replaced ignition and cloud config with container linux configs

Here's an incomplete pass at changing all the OS docs over to using container linux configs instead of ignition or cloud configs.
Everything alphabetically before iscsi.md should be good to go, with the exception of cluster-architecture.md, which needs a complete rewrite.

This should now be complete, and ready for review

Found and replaced the ignition and cloud config references outside of the os dir, which I had forgotten about initially. Need to rewrite large parts of etcd/tls-etcd-clients.md. Going to do the standard CLC thing you mentioned, still getting to it.

Just did what I probably should've done in the beginning: pulled in ct's docs test and tweaked it for here. All markdown files in this repo are now parsed for CLC blocks, and the found blocks are run through the parser and converter. Any warnings or errors cause the test to fail.
There's no CI for it on this repo, but at the very least it's something that docs authors can run when they modify/add CLC blocks.

Just pushed some stuff:

fixed errors in the ec2 CLC
updated the digitalocean screenshot to be of an ignition config instead of a cloud config
finished the etcd/tls-etcd-clients.md file
switched all ignition-supported cloud providers to using the same, heavily commented CLC that starts etcd. This relies on https://github.com/coreos/container-linux-config-transpiler/pull/54, which is not yet in a release. I just tested booting a machine in ec2 with this CLC, and it behaved as expected.


chore: re-pin awkward to 2.2.0

Your force-push (or something unknown) made the logs of the failed run disappear :|


Please help me solve the problem. thanks

(songdh) [root@localhost server_llm]# python -m vllm.entrypoints.api_server     --model $model_path     --tokenizer $model_path     --tensor-parallel-size $GPUS     --dtype auto     --port $port     --host <IP_ADDRESS>     --gpu-memory-utilization 0.9     --quantization awq --dtype float16    --load-format auto &
[1] 86402
(songdh) [root@localhost server_llm]# WARNING 11-25 10:47:23 config.py:398] Casting torch.bfloat16 to torch.float16.
WARNING 11-25 10:47:23 config.py:140] awq quantization is not fully optimized yet. The speed can be slower than non-quantized models.
INFO 11-25 10:47:23 llm_engine.py:72] Initializing an LLM engine with config: model='/data5/llama/models_hf/13B', tokenizer='/data5/llama/models_hf/13B', tokenizer_mode=auto, revision=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.float16, max_seq_len=2048, download_dir=None, load_format=auto, tensor_parallel_size=1, quantization=awq, seed=0)
INFO 11-25 10:47:23 tokenizer.py:31] For some LLaMA V1 models, initializing the fast tokenizer may take a long time. To reduce the initialization time, consider using 'hf-internal-testing/llama-tokenizer' instead of the original tokenizer.
Traceback (most recent call last):
File "/root/anaconda3/envs/songdh/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/root/anaconda3/envs/songdh/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/entrypoints/api_server.py", line 80, in
engine = AsyncLLMEngine.from_engine_args(engine_args)
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/engine/async_llm_engine.py", line 486, in from_engine_args
engine = cls(parallel_config.worker_use_ray,
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/engine/async_llm_engine.py", line 269, in init
self.engine = self._init_engine(*args, **kwargs)
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/engine/async_llm_engine.py", line 305, in _init_engine
return engine_class(*args, **kwargs)
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/engine/llm_engine.py", line 110, in init
self._init_workers(distributed_init_method)
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/engine/llm_engine.py", line 142, in _init_workers
self._run_workers(
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/engine/llm_engine.py", line 700, in _run_workers
output = executor(*args, **kwargs)
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/worker/worker.py", line 70, in init_model
self.model = get_model(self.model_config)
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/model_executor/model_loader.py", line 67, in get_model
quant_config = get_quant_config(model_config.quantization,
File "/root/anaconda3/envs/songdh/lib/python3.10/site-packages/vllm/model_executor/weight_utils.py", line 114, in get_quant_config
raise ValueError(f"Cannot find the config file for {quantization}")
ValueError: Cannot find the config file for awq

try --tokenizer-mode=slow?

same

--max-model-len 2048

vLLM does not quantize models for you. If the model you are trying to load isn't quantised then it won't work. This appears to be what is happening.


Raspberry Pi 4B: Have to run rpiboot twice to get it to boot my kernel

Describe the bug
I have a dev directory containing these files:
$ ls dev
bcm2711-rpi-4-b.dtb  blink.img  bootcode.bin  config.txt  fixup4.dat  start4.elf

I pass this directory to rpiboot and my blink kernel works, but it takes two tries. I think this is related to https://github.com/raspberrypi/usbboot/issues/8.
$ ./rpidev -d dev
RPIBOOT: build-date Jul 13 2023 version 20221215~105525 c4b12f85
Loading: dev/bootcode.bin
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode4.bin
Second stage boot server
Loading: dev/config.txt
File read: config.txt
Cannot open file vl805.sig
Cannot open file pieeprom.sig
Cannot open file recover4.elf
Cannot open file fixup4rc.dat
Cannot open file recovery.elf
Cannot open file fixup_rc.dat
Loading: dev/start4.elf
File read: start4.elf
Loading: dev/fixup4.dat
File read: fixup4.dat
Second stage boot server done

$ ./rpidev -d dev
RPIBOOT: build-date Jul 13 2023 version 20221215~105525 c4b12f85
Loading: dev/bootcode.bin
Waiting for BCM2835/6/7/2711...
Loading: dev/bootcode.bin
Second stage boot server
Cannot open file recovery.elf
Loading: dev/config.txt
File read: config.txt
Cannot open file dt-blob.bin
Cannot open file recovery.elf
Loading: dev/config.txt
File read: config.txt
Cannot open file bootcfg.txt
Loading: dev/blink.img
Loading: dev/bcm2711-rpi-4-b.dtb
File read: bcm2711-rpi-4-b.dtb
Cannot open file overlays/overlay_map.dtb
Loading: dev/config.txt
File read: config.txt
Cannot open file cmdline.txt
Cannot open file armstub8-gic.bin
Loading: dev/blink.img
File read: blink.img
Second stage boot server done

I also notice that some files are being transferred again. This entire sequence takes 13s with -l set. Would it be possible to reduce this time somehow?
Steps to reproduce the behaviour

Set BOOT_ORDER=0xf31 in the EEPROM bootloader config.
Remove SD card and power on the board.
Run ./rpidev -d dev
Run it again to load the kernel

Device(s)
Other
Compute Module IO board.
No response
RPIBOOT logs
No response
Kernel logs
No response
Device UART logs
No response

My use case is kernel development for the RPi 4B and I'm planning to use USB boot to load the kernel from my laptop. Since I'm fairly new to the RPi ecosystem, any suggestions would be highly appreciated.
On a side note, one doubt I'm having is with the need for bootcode.bin. Isn't it already in the EEPROM for RPi 4B? Why does the CLI tool still enforce that it is needed?

Run "rpiboot -l" to keep it running.
N.B. Individual file loading is deprecated in favour of the boot.img ramdisk approach. The file-loading is prone to timeouts and is no longer maintained.

Thanks for the update. I knew about the -l flag as mentioned in the issue description. #8 also had this issue and got a fix. Do I take it that this issue is only for single file loading and will go away if I use boot.img?

On a side note, one doubt I'm having is with the need for bootcode.bin. Isn't it already in the EEPROM for RPi 4B? Why does the CLI tool still enforce that it is needed?

Could you also please let me know about this? USB boot takes about 13s and I was just curious if removing bootcode would make it faster.

Loading a boot.img means that bootloader loads a single large blob which avoids problems when there are delays between loading individual files.
rpiboot causes the bootrom to load the second-stage (bootcode.bin) from USB rather than the SPI EEPROM so it's not possible to get rid of bootcode.bin.
13s seems about right, unfortunately the only way to make this after is to make the kernel smaller

Thanks a lot for the clarification and for this really handy tool. Regarding the kernel (blink example), it is only 332B, so I don't think it could be reduced. I guess this is just how USB boot performs and that is totally fine.


[e2e]: delegator-generic workflow_dispatch main checkout slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5815728385
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Aug 10 01:11:34 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5816617774
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Aug 10 03:33:48 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5816746835
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Aug 10 03:58:13 UTC 2023
Tests are passing now. Closing this issue.


Model and API changes

Added replace_original and delete_original  params to actions
Added type App to handle apps_changed  and apps_uninstalled  events
Added tz_offset  to User
Updated file_share message subtype to handle SlackFile
Fixed typo in comment timestamp

Looks good to me, thanks for the contribution!


beast::http::string_view_body and boost::string_view

Using beast::http::string_view_body and boost::string_view
void blub()
{
    beast::http::request<beast::http::string_view_body> request;
    request.body = boost::string_view("Hello, world!");
}

gives this error:
gcc.compile.c++ bin/gcc-7/release/example/foo.o

    "g++"  -ftemplate-depth-128 -march=native -ftemplate-depth=256 -std=c++17 -O3 -finline-functions -Wno-inline -Wall -fPIC  -DBOOST_ALL_DYN_LINK -DNDEBUG  -I"/home/mike/workspace/Beast/include" -I"include" -c -o "bin/gcc-7/release/example/foo.o" "example/foo.cpp"

example/foo.cpp: In function ‘void blub()’:
example/foo.cpp:168:51: error: no match for ‘operator=’ (operand types are ‘beast::http::string_view_body::value_type {aka boost::basic_string_ref<char, std::char_traits<char> >}’ and ‘boost::basic_string_view<char, std::char_traits<char> >’)
  request.body = boost::string_view("Hello, world!");
                                                   ^
In file included from /home/mike/workspace/Beast/include/beast/core/string.hpp:11:0,
                 from /home/mike/workspace/Beast/include/beast/core/static_string.hpp:12,
                 from /home/mike/workspace/Beast/include/beast/core.hpp:29,
                 from /home/mike/workspace/Beast/include/beast.hpp:13,
                 from example/foo.cpp:8:
/usr/include/boost/utility/string_ref.hpp:77:27: note: candidate: constexpr boost::basic_string_ref<charT, traits>& boost::basic_string_ref<charT, traits>::operator=(const boost::basic_string_ref<charT, traits>&) [with charT = char; traits = std::char_traits<char>]
         basic_string_ref& operator=(const basic_string_ref &rhs) BOOST_NOEXCEPT
                           ^~~~~~~~
/usr/include/boost/utility/string_ref.hpp:77:27: note:   no known conversion for argument 1 from ‘boost::basic_string_view<char, std::char_traits<char> >’ to ‘const boost::basic_string_ref<char, std::char_traits<char> >&’
...failed gcc.compile.c++ bin/gcc-7/release/example/foo.o...

boost::string_view and boost::string_ref are two different classes. Beast declares beast::string_view as an alias for boost:string_ref. You need to write:
void blub()
{
    beast::http::request<beast::http::string_view_body> request;
    request.body = beast::string_view(Hello, world!");
}

I know. May be the name beast::http::string_ref_body is better.

So everybody knows to use boost:string_ref.
No need for beast::string_view as an alias for boost:string_ref
In future a beast::http::string_view_body could work with boost::string_view

Or even better a generic and configurable design for beast::http::string_body:
template <typename StringRep>
class string_body;

So StringRep could be at least

std::string
boost::string
std::string_view
boost::string_view
boost::string_ref

I would use std::string_view if it was part of C++11 or if Beast required C++17. But since its not available, and because using non-owning strings in Beast interfaces provides tremendous benefits, I had to pick an implementation of string_view. I chose boost::basic_string_ref because that's the one I found first. I guess I could have gone with boost::basic_string_view although I'm not sure what the differences is, and why does Boost have two of them? This is something that should be brought up during the formal review.
There's no way that Beast can provide every possible body type nor would I want to do so, it just needs to provide the common types. The rest can be left to users - you can write your own Body for any class that you desire, its pretty easy:
http://vinniefalco.github.io/beast/beast/using_http/custom_body_types.html
http://vinniefalco.github.io/beast/beast/concept/Body.html

Using the generic string_body
template <typename StringRep>
struct string_body
{
    /// The type of the body member when used in a message.
    using value_type = StringRep;

    ...
};

compiles this without problems out-of-the-box
template <typename StringRep>
void test()
{
    boost::asio::io_service service;
    boost::asio::ip::tcp::socket socket {service};
    beast::http::request<beast::http::string_body<StringRep>> request;
    request.body = StringRep();
    beast::http::write(socket, request);
}

void test()
{
    test<std::string>();
    test<boost::container::string>();
    test<std::string_view>();
    test<boost::string_view>();
    test<boost::string_ref>();
    test<std::vector<char>>();
    test<boost::container::vector<char>>();
    test<std::array<char, 100>>();
    test<boost::array<char, 100>>();
}

That's the generic way. No need to restrict the user at all.

template
struct string_body

In designing Beast interfaces, I try to keep the types as simple as possible. For example string_body is limited to std::string, and not std:basic_string<CharT, Traits, Allocator>. I don't think I want to make string_body a template now since that complicates a very common use case to satisfy the needs of only a small number of users. How many people plan on mixing all the different types of containers you listed in your example, in the same program? And as you correctly pointed out, implementing a Body type is trivial.
You left out the part about writing - you can't parse into a string_view. Still, you would need a correctly written trait metafunction or else users would get odd compile errors when using StringRep that don't meet the requirements (for example std::list<char> won't work).
Its not clear to me that Beast benefits from enlarging its scope to include a body for all conceivable containers that have data() and size() for reading, and reserve() and append() for writing. However, if you feel strongly about it, then I encourage you to participate in the Boost formal review! Perhaps your idea will gain some traction. Perhaps others will make proposals to improve the idea and change my mind? You never know!
All you have to do is sign up for the mailing list before July 1 and listen for the announcements:
http://www.boost.org/community/groups.html#main

How many people plan on mixing all the different types of containers you listed in your example, in the same program?

Nobody - i think. But

People work with existing source code - which specifies the types you must use.
People use frameworks - which specifies the types you must use.
Be able to use your string_body with any type specified by existing code or framework is a huge gain.

void bad1()
{
    boost::asio::io_service service;
    boost::asio::ip::tcp::socket socket {service};
    beast::http::request<beast::http::string_view_body> response;
    beast::flat_buffer buffer;
    beast::http::read(socket, buffer, response);
}

is a broken as
void bad2()
{
    boost::asio::io_service service;
    boost::asio::ip::tcp::socket socket {service};
    beast::http::request<beast::http::string_body<std::string_view>> response;
    beast::flat_buffer buffer;
    beast::http::read(socket, buffer, response);
}

But a nice way could be

mutable_sting_body for write and read
immutable_sting_body for write only

mutable_sting_body needs mutable strings:

std::string
boost::container::string
std::vector<char>

immutable_sting_body can handle immutable strings too

see all examples above - including refs and views

That's clear design, isn't?

I like the names

is as broken as

Yes, read on non-writable bodies will produce this error
1> static assertion failed: BodyWriter requirements not met

But I am referring to the error generated when the user chooses an incorrect type. For example if they try to use string_body<std::list<char>> they will see something like this:
1>C:\Users\vinnie\src\Beast\test\http\read.cpp(80): error C2440: 'initializing': cannot convert from 'initializer list' to 'beast::http::string_bod<beast::multi_buffer>::reader::const_buffers_type'
1>C:\Users\vinnie\src\Beast\test\http\read.cpp(80): note: No constructor could take the source type, or constructor overload resolution was ambiguous
1>C:\Users\vinnie\src\Beast\test\http\read.cpp(77): note: while compiling class template member function 'boost::optional<std::pair<beast::http::string_body::reader::const_buffers_type,bool>> beast::http::string_bod<beast::multi_buffer>::reader::get(beast::error_code &)'
1>C:\Users\vinnie\src\Beast\include\beast/http/impl/serializer.ipp(77): note: see reference to function template instantiation 'boost::optional<std::pair<beast::http::string_body::reader::const_buffers_type,bool>> beast::http::string_bod<beast::multi_buffer>::reader::get(beast::error_code &)' being compiled
1>C:\Users\vinnie\src\Beast\include\beast/http/impl/write.ipp(738): note: see reference to class template instantiation 'beast::http::string_bod<beast::multi_buffer>::reader' being compiled
1>C:\Users\vinnie\src\Beast\test\http\read.cpp(205): note: see reference to function template instantiation 'void beast::http::write<beast::test::pipe::stream,false,beast::http::string_bod<beast::multi_buffer>,beast::http::fields>(SyncWriteStream &,const beast::http::message<false,beast::http::string_bod<beast::multi_buffer>,beast::http::fields> &)' being compiled
1>        with
1>        [
1>            SyncWriteStream=beast::test::pipe::stream
1>        ]
1>C:\Users\vinnie\src\Beast\test\http\read.cpp(80): error C2440: 'return': cannot convert from 'initializer list' to 'boost::optional<std::pair<beast::http::string_body::reader::const_buffers_type,bool>>'
1>C:\Users\vinnie\src\Beast\test\http\read.cpp(80): note: No constructor could take the source type, or constructor overload resolution was ambiguous

string_body needs a traits metafunction to perform type checking on its template parameter to make sure it meets the requirements, otherwise the user will see an error novel.

Agreed! The mutable_sting_body should check the StringRep for method

append
and/or reserve

in a meta is_mutable<StringRep>::value

I'm warming up to the idea

If xxx_string_body get a template argument StringRep
there should be a check like
static_assert(sizeof(typename StringRep::value_type) == 1, "Unsupported character size.");
too. Otherwise you could compile this:
    test<std::wstring>();
    test<std::u32string>();
    test<std::u16string>();

And this does not work. Adding utf16, utf32, etc. support is far behind this scope...

Ouch, that's a problem... But why not support those as well? The calculation for content length would be value.size() * sizeof(typename value_type::value_type). The container would require a nested type called value_type. Which they all have.

Although, this brings up a new problem. How do you prevent this
class Thing {
  unsigned char v_;
public:
  ...
};

Now use const_body<std::vector<Thing>> This doesn't really make any sense because there is no guarantee that Thing is something which makes sense to perform a bitwise serialization on.
And what if we have
struct Thing2 {
  std::string s_;
};

Now use const_body<std::vector<Thing2>> this is undefined behavior. I am starting not to like this idea.

std::is_integral for StringRep::value_type will sort Thing and Thing2 out.

I think you should write it and submit a pull request. I'd like const_body and mutable_body for the names, since they are short and general sounding.

okay

I can do it now in the fork. If you want i can give you a pull request after the formal review.

I don't want to waste your time, I am trying to get feedback from some other people who have worked on Boost to know if this is a good idea or not. Remember that every additional feature means additional testing. maintenance, and documentation. So it has to really be worth it.

Roger that

Okay I have discussed it with my colleagues and come to a conclusion. I have reservations about making const_body and mutable_body class templates part of the library's public interface. However, having them as example code (which is compiled and tested as part of the continuous integration process) included in the documentation would be very nice. Users can simply copy the source file into their project to use it.
This doesn't stop us from promoting it to become part of the library in the future. This way, it creates less work in terms of maintenance, documentation, and testing, and also serves a purpose, to show users how to create body types.
It would go in example/common which is where I am putting other similar things like file_body.hpp
What do you think?

This should all be handled by https://github.com/vinniefalco/Beast/issues/580


Reduced vs basic model

Thanks for the great project! The LPRNet paper talks about the "basic" and "reduced" model:

To improve runtime performance we also modified LPRNet basic by using 2 × 2 strides for all pooling layers. This
modification (the LPRNet reduced model) reduces the size
of intermediate feature maps and total inference computational cost significantly

Is your model using the basic or reduced architecture? From what I can see, it is the basic architecture, I'm interested to know if you tried the reduced architecture? If I try modifying your maxpool3d layers to maxpool2d, and use 2x2 strides instead of 1x1, 1x2 and 1x2, I can't get the shapes to match up at the end. Just curious to know if this is something that you tried?

@barrypitman how did you solve it then?

@barrypitman can you share the "reduced"  Net.py?

My changes are here: https://github.com/barrypitman/tensorflow_LPRnet.


Dockerfile interactive blocked

this is my dockerfile:
FROM python:2.7
MAINTAINER rockywu
ADD . /app
WORKDIR /app
RUN apt-get update
RUN apt-get install postfix mailutils -y
RUN pip install -r requirements.txt
ENTRYPOINT ["/etc/init.d/postfix","restart"]
EXPOSE 5000
EXPOSE 25

when  going to install postfix , it need me to select the domain name,after i selected ,it blocked.this is the code:
Please select the mail server configuration type that best meets your needs.

 No configuration:
  Should be chosen to leave the current configuration unchanged.
 Internet site:
  Mail is sent and received directly using SMTP.
 Internet with smarthost:
  Mail is received directly using SMTP or by running a utility such
  as fetchmail. Outgoing mail is sent using a smarthost.
 Satellite system:
  All mail is sent to another machine, called a 'smarthost', for delivery.
 Local only:
  The only delivered mail is the mail for local users. There is no network.

  1. No configuration  3. Internet with smarthost  5. Local only
  2. Internet Site     4. Satellite system

General type of mail configuration: 3

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
 It's related to how Debian based distributions set up packages during installation. There's a way to provide the required options before installing the packages so that you don't get the prompt any more.
This isn't a general support forum. This is an issue tracker for Docker bugs, features and pull requests. Please take this into account when opening an issue.
This isn't a Docker bug, this is a question which is more appropriate for

the forums: https://forums.docker.com/

the docker-user mailing list https://groups.google.com/forum/#!forum/docker-user

the #docker channel on Freenode.

and 2) should be better for longer conversations.

Since this isn't a bug, I'm going to close this now. Please feel free to comment.


Typo in Readme.md

look at this line
requestButton.setCallback(callback));
there is an extra closing bracket.

Fixed in v0.5.4


Update getEvents retention window

Preview is available here:http://developers-pr975.previews.kube001.services.stellar-ops.com

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Preview is available here:http://developers-pr975.previews.kube001.services.stellar-ops.com


added getName() to server module

Fix for #742

This change is

Coverage decreased (-0.06%) to 54.607% when pulling 6593fd4c5aebcc9672c92e3ac93ae7ee235678c8 on module-name into 063c769eaa6f52b6485d18f63ae7dc81e3b2d316 on master.

Reviewed 9 of 9 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


Properties menu does not like capital letters.

I have recreated this property a few times and the field above the icon search always comes up blank. I believe it is due to the capital letter in the property because if I create a new property without the capital letter, it works. I was trying to set the icon of homeAddress. Remove the capital letter and it works.

Oh wow, that's a subtle bug. I found the code that's causing it too. You can work around this for now by setting homeAddress from the Properties sidebar, because the bug doesn't exist over there.
 {};

Replace:
    const propBases = Object.values(this.app.metadataTypeManager?.properties) ?? [];
    const propBase = propBases.find(propBase => propBase.name === propId) ?? {};

Thanks! Will do!

@gfxholo I just realized when you publish this, it creates a main.js file that is compiled so I can't update that. I will await your next plugin update. 🥰

@DudeThatsErin No!  This will definitely be fixed in 1.1, but I might push out an earlier patch since this could be aggravating quite a few people.
Thanks a bunch for the quality bug report 💜


feat: Support VLESS XTLS Vision

This is now ready for tests. I've already tested (with Firefox and NatTypeTester) and it looks good for me:

[x] XUDP and FullCone support
[x] Speedtest passed
[ ] Connect SSH (untested)

The code of TLS filtering is similar to Xray but is not the same. So there is no guarantee that the effect will be exactly the same. Anyhow, this PR has implemented all Vision protocol semantics, except splice support on Linux.

After testing, ssh is available.


Integrate e2e with playwright

Goal
Add e2e using playwright for local and CI
Added some e2e tests to sanity check some important parts of the home page, and test navigation using the header items
The CI workflow has changed as follows.

Unit tests & Lint >> Build and Deploy to Vercel >> Test E2E on vercel deployment

Notes:

Will run automatically for PR's on develop branch only.
Only using chromium to test for speed and stability until we have a reason to test using a different browser
The More header dropdown items are causing problems as clicking them using playwright will take you to  /about instead of opening the dropdown so this is not yet implemented.

How to test
See README Testing section here or follow instructions below

Confirm vitest only runs unit tests

pnpm test

Install playwright for e2e testing

pnpm test:e2e:install

Test using next production server

Playwright will automatically start the production server so just make sure to create a next build
cd apps/bestofjs-nextjs/
pnpm build && pnpm test:e2e

Screenshots
Testing with vitest

Testing with playwright

Updated CI workflow

Thank you so much for introducing the setup and providing the tests!
Tests pass for me too!

The report we get with pnpm exec playwright show-report is nice:

It would be great to have this report available on GitHub actions.
Let's try to simplify the setup and we should be good to go (I added another comment).

Thank you for your hard work on the topic.
I like the idea of running E2E against the preview application built by Vercel, to avoid having built it on CI, because my main worry is to keep the feedback loop fast when iterating during the development of a PR.
You mentioned it during the development but I noticed the following errors thrown by the local server, when running tests locally:
TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed
    at new NodeError (node:internal/errors:399:5)
    at ReadableByteStreamController.enqueue (node:internal/webstreams/readablestream:1150:13)
    at eM (/Users/michaelrambeau/dev/bestofjs/bestofjs-monorepo/node_modules/.pnpm/next@13.5.3_@babel+core@7.22.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:125:15562)
    at eI (/Users/michaelrambeau/dev/bestofjs/bestofjs-monorepo/node_modules/.pnpm/next@13.5.3_@babel+core@7.22.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:125:15037)
    at Timeout._onTimeout (/Users/michaelrambeau/dev/bestofjs/bestofjs-monorepo/node_modules/.pnpm/next@13.5.3_@babel+core@7.22.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:125:12095)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7) {
  code: 'ERR_INVALID_STATE'

Is it because of the streaming feature provided by Next.js 13, should we just ignore them?
About streaming in Next.js 13: https://nextjs.org/docs/app/building-your-application/routing/loading-ui-and-streaming#streaming-with-suspense

Thank you for your hard work on the topic.
I like the idea of running E2E against the preview application built by Vercel, to avoid having built it on CI, because my main worry is to keep the feedback loop fast when iterating during the development of a PR.
You mentioned it during the development but I noticed the following errors thrown by the local server, when running tests locally:
TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed
    at new NodeError (node:internal/errors:399:5)
    at ReadableByteStreamController.enqueue (node:internal/webstreams/readablestream:1150:13)
    at eM (/Users/michaelrambeau/dev/bestofjs/bestofjs-monorepo/node_modules/.pnpm/next@13.5.3_@babel+core@7.22.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:125:15562)
    at eI (/Users/michaelrambeau/dev/bestofjs/bestofjs-monorepo/node_modules/.pnpm/next@13.5.3_@babel+core@7.22.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:125:15037)
    at Timeout._onTimeout (/Users/michaelrambeau/dev/bestofjs/bestofjs-monorepo/node_modules/.pnpm/next@13.5.3_@babel+core@7.22.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:125:12095)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7) {
  code: 'ERR_INVALID_STATE'

Is it because of the streaming feature provided by Next.js 13, should we just ignore them?
About streaming in Next.js 13: https://nextjs.org/docs/app/building-your-application/routing/loading-ui-and-streaming#streaming-with-suspense

These errors are gone when using the vercel deployment
They very well might still be throwing on the vercel hosting side, but it doesn't affect the functionality
So in the end its a non issue


Update ChangeLog for beta.9 release

Update ChangeLog for beta.9 release

@SteveL-MSFT I have addressed your comments. Please take another look, thanks!

@mirichmo You comments have been addressed. Please take another look.


[AutoPR logic/resource-manager] RosettaNet Process configuration apis

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6702

(message created by the CI based on PR content)


Fix implicit assumption about inplace installation etc.

Some general problems identified during https://github.com/snowleopard/hadrian/pull/312
Most changes are about generalizing different facilities, like runGhcWrapper so it works with both inplace installation and installation to dest path.

CI failed in seemly random ways like below, @snowleopard do you have a good guess about why that happened?
AppVeyor:
Error when running Shake build system:
* inplace/bin/ghc-stage2.exe
* _build/stage1/compiler/libHSghc-8.3-0.a
* _build/stage1/compiler/TcRnTypes.o
* _build/stage1/compiler/TcRnTypes.o _build/stage1/compiler/TcRnTypes.hi
user error (Development.Shake.cmd, system command failed
Command: inplace/bin/ghc-stage1.exe -Wall -hisuf hi -osuf o -hcsuf hc -static -hide-all-packages -no-user-package-db "-this-unit-id ghc-8.3" "-package-id base-<IP_ADDRESS>" "-package-id deepseq-<IP_ADDRESS>" "-package-id directory-<IP_ADDRESS>" "-package-id process-<IP_ADDRESS>" "-package-id bytestring-<IP_ADDRESS>" "-package-id binary-<IP_ADDRESS>" "-package-id time-<IP_ADDRESS>" "-package-id containers-<IP_ADDRESS>" "-package-id array-<IP_ADDRESS>" "-package-id filepath-<IP_ADDRESS>" "-package-id template-haskell-<IP_ADDRESS>" "-package-id hpc-<IP_ADDRESS>" "-package-id transformers-<IP_ADDRESS>" "-package-id ghc-boot-8.3" "-package-id ghc-boot-th-8.3" "-package-id ghci-8.3" "-package-id hoopl-<IP_ADDRESS>" "-package-id Win32-<IP_ADDRESS>" -i -i_build/stage1/compiler -i_build/stage1/compiler/build/autogen -icompiler/backpack -icompiler/basicTypes -icompiler/cmm -icompiler/codeGen -icompiler/coreSyn -icompiler/deSugar -icompiler/ghci -icompiler/hsSyn -icompiler/iface -icompiler/llvmGen -icompiler/main -icompiler/nativeGen -icompiler/parser -icompiler/prelude -icompiler/profiling -icompiler/rename -icompiler/simplCore -icompiler/simplStg -icompiler/specialise -icompiler/stgSyn -icompiler/stranal -icompiler/typecheck -icompiler/types -icompiler/utils -icompiler/vectorise -Iincludes -I_build/generated -I_build/stage1/compiler -Icompiler/. -Icompiler/parser -Icompiler/utils -Icompiler/../rts/dist/build -IC:/ghc/libraries/process/include -IC:/ghc/libraries/directory -IC:/ghc/libraries/time/lib/include -IC:/ghc/libraries/containers/include -IC:/ghc/libraries/Win32/include -IC:/ghc/libraries/bytestring/include -IC:/ghc/libraries/base/include -IC:/ghc/libraries/integer-gmp/include -IC:/ghc/_build/stage1/rts -IC:/ghc/includes -IC:/ghc/_build/generated -I_build/generated -optc-I_build/generated -optP-include -optP_build/stage1/compiler/build/autogen/cabal_macros.h -optc-fno-stack-protector -optP-DGHCI -odir _build/stage1/compiler -hidir _build/stage1/compiler -stubdir _build/stage1/compiler -c compiler/typecheck/TcRnTypes.hs -o _build/stage1/compiler/TcRnTypes.o -O0 -H32m -Wall -fno-warn-name-shadowing -this-unit-id ghc -XHaskell2010 -DSTAGE=2 -DGHCI_TABLES_NEXT_TO_CODE -Wno-deprecated-flags
fd:5: hGetContents: illegal operation (delayed read on closed handle))

Linux:
error when running Shake build system:
* inplace/bin/runhaskell
* /home/travis/build/snowleopard/hadrian/ghc/inplace/lib/bin/runhaskell
Error, file does not exist and no rule available:
  /home/travis/build/snowleopard/hadrian/ghc/inplace/lib/bin/runhaskell

macOS:
Error when running Shake build system:
* inplace/bin/ghc-pkg
* /Users/travis/build/snowleopard/hadrian/ghc/inplace/lib/bin/ghc-pkg
Error, file does not exist and no rule available:
  /Users/travis/build/snowleopard/hadrian/ghc/inplace/lib/bin/ghc-pkg
CallStack (from HasCallStack):
  error, called at src/Development/Shake/Rules/File.hs:103:58 in shake-0.15.11-CVjJniLH3Qx6A17WAr0L7I:Development.Shake.Rules.File

CI failed in seemingly random ways like below, @snowleopard do you have a good guess about why that happened?
AppVeyor:
Error when running Shake build system:
* inplace/bin/ghc-stage2.exe
* _build/stage1/compiler/libHSghc-8.3-0.a
* _build/stage1/compiler/TcRnTypes.o
* _build/stage1/compiler/TcRnTypes.o _build/stage1/compiler/TcRnTypes.hi
user error (Development.Shake.cmd, system command failed
Command: inplace/bin/ghc-stage1.exe -Wall -hisuf hi -osuf o -hcsuf hc -static -hide-all-packages -no-user-package-db "-this-unit-id ghc-8.3" "-package-id base-<IP_ADDRESS>" "-package-id deepseq-<IP_ADDRESS>" "-package-id directory-<IP_ADDRESS>" "-package-id process-<IP_ADDRESS>" "-package-id bytestring-<IP_ADDRESS>" "-package-id binary-<IP_ADDRESS>" "-package-id time-<IP_ADDRESS>" "-package-id containers-<IP_ADDRESS>" "-package-id array-<IP_ADDRESS>" "-package-id filepath-<IP_ADDRESS>" "-package-id template-haskell-<IP_ADDRESS>" "-package-id hpc-<IP_ADDRESS>" "-package-id transformers-<IP_ADDRESS>" "-package-id ghc-boot-8.3" "-package-id ghc-boot-th-8.3" "-package-id ghci-8.3" "-package-id hoopl-<IP_ADDRESS>" "-package-id Win32-<IP_ADDRESS>" -i -i_build/stage1/compiler -i_build/stage1/compiler/build/autogen -icompiler/backpack -icompiler/basicTypes -icompiler/cmm -icompiler/codeGen -icompiler/coreSyn -icompiler/deSugar -icompiler/ghci -icompiler/hsSyn -icompiler/iface -icompiler/llvmGen -icompiler/main -icompiler/nativeGen -icompiler/parser -icompiler/prelude -icompiler/profiling -icompiler/rename -icompiler/simplCore -icompiler/simplStg -icompiler/specialise -icompiler/stgSyn -icompiler/stranal -icompiler/typecheck -icompiler/types -icompiler/utils -icompiler/vectorise -Iincludes -I_build/generated -I_build/stage1/compiler -Icompiler/. -Icompiler/parser -Icompiler/utils -Icompiler/../rts/dist/build -IC:/ghc/libraries/process/include -IC:/ghc/libraries/directory -IC:/ghc/libraries/time/lib/include -IC:/ghc/libraries/containers/include -IC:/ghc/libraries/Win32/include -IC:/ghc/libraries/bytestring/include -IC:/ghc/libraries/base/include -IC:/ghc/libraries/integer-gmp/include -IC:/ghc/_build/stage1/rts -IC:/ghc/includes -IC:/ghc/_build/generated -I_build/generated -optc-I_build/generated -optP-include -optP_build/stage1/compiler/build/autogen/cabal_macros.h -optc-fno-stack-protector -optP-DGHCI -odir _build/stage1/compiler -hidir _build/stage1/compiler -stubdir _build/stage1/compiler -c compiler/typecheck/TcRnTypes.hs -o _build/stage1/compiler/TcRnTypes.o -O0 -H32m -Wall -fno-warn-name-shadowing -this-unit-id ghc -XHaskell2010 -DSTAGE=2 -DGHCI_TABLES_NEXT_TO_CODE -Wno-deprecated-flags
fd:5: hGetContents: illegal operation (delayed read on closed handle))

Linux:
error when running Shake build system:
* inplace/bin/runhaskell
* /home/travis/build/snowleopard/hadrian/ghc/inplace/lib/bin/runhaskell
Error, file does not exist and no rule available:
  /home/travis/build/snowleopard/hadrian/ghc/inplace/lib/bin/runhaskell

macOS:
Error when running Shake build system:
* inplace/bin/ghc-pkg
* /Users/travis/build/snowleopard/hadrian/ghc/inplace/lib/bin/ghc-pkg
Error, file does not exist and no rule available:
  /Users/travis/build/snowleopard/hadrian/ghc/inplace/lib/bin/ghc-pkg
CallStack (from HasCallStack):
  error, called at src/Development/Shake/Rules/File.hs:103:58 in shake-0.15.11-CVjJniLH3Qx6A17WAr0L7I:Development.Shake.Rules.File

It looks the problem is: if the target is inplace/lib/bin/ghc-pkg, then the rules exist, but if it is the full path, e.g. /Users/zz/Repos/ghc2/inplace/lib/bin/ghc-pkg, then the rule doesn't exist. It is really weird...

@izgzhen AppVeyor is happy now. Was it simply a glitch?

All CI bots are happy now. Was it simply a glitch?

No, I made some changes to the code. It is still the target problem: inplace/bin/ghc-pkg has its rule, but <top>/inplace/bin/ghc-pkg doesn't. So I reverted back to the relative one.

@izgzhen I see. These may be a relevant discussions:
https://github.com/ndmitchell/shake/issues/517
https://github.com/ndmitchell/shake/issues/376

As a general rule I find all Shake rules should be relative to the current directory. Otherwise you get confusing issues sound two paths referring to the same place. If you find yourself needing an absolute path rule, fix the caller instead.

Just pushed some cosmetic changes to follow my rules :)
BTW, this is basically all the content I want to cover in this PR.

@izgzhen I have doubts about modules Rules.Wrappers and Settings.Install -- they seem to be too small to justify a separate module.
Perhaps, Rules.Wrappers could take care of defining all program wrappers, e.g. Rules.Wrappers.Ghc etc?
Regarding Settings.Install: will it accumulate more settings in upcoming PRs?

Perhaps, Rules.Wrappers could take care of defining all program wrappers, e.g. Rules.Wrappers.Ghc etc?

I think this is a better idea.

Regarding Settings.Install: will it accumulate more settings in upcoming PRs

It will, probably like https://github.com/snowleopard/hadrian/pull/312/files#diff-5032c3797e40155b06c847c4a5f26535R277, https://github.com/snowleopard/hadrian/pull/312/files#diff-5032c3797e40155b06c847c4a5f26535R73, https://github.com/snowleopard/hadrian/pull/312/files#diff-5032c3797e40155b06c847c4a5f26535R40
But I am not very enthusiastic about putting all of them in a separate module.

OK, I see. Shall I merge this now?

Wait a bit ... should I put the wrappers into Wrappers? I favor this since I guess we won't have a lot of wrappers anyway.

@izgzhen Sure, go ahead and ping me when ready.

ready now

Thanks, merged!


Fix issue #3 -  style

May I suggest to squash the commits into one?

Is there any way to do this without creating a new pull request, @vkeusebio?

Hi @joaobarbosa on your select-caret branch: do
git rebase -i HEAD~5
this will merge the last 5 commits you made.

@fabienwang great, I'll do this right now :)

humm @joaobarbosa you'll have to change "pick" by "squash" in the rebase operation to merge them.
Read it: http://eli.thegreenplace.net/2014/02/19/squashing-github-pull-requests-into-a-single-commit
Regards.

@fabienwang I guess its almost done! hahah after rebase it asked for a merge, should I try it again or leave it like this?

Yeah, it should ask for a merge after squashing commits. Looks fine to me @joaobarbosa :ok_hand:

Thanks @vkeusebio!

Thank you so much for the PR.
But i will — unfortunately — not merge it because there are some changes directly in CSS files, and not in the source code.
In a way it's my fault. I need to urgently make available a contributing.md file with these informations: "How to contribute for the project".

I did changes in the .sass files, and Grunt did the rest of the job. :/
Box-sizing change I was my mistake, I haven't noticed that html was already set to border-box. :+1:
About the select element, I think it could be set to menulist until another way is defined for it, so, at least, the browser render gets it done for a while. I will try to think about a solution for it. :)


Code Coverage shown is incorrect

After adding support for nodejs, the code coverage provided is reduced to 77%. This is not correct coverage report. Due to the addition of polyfill code the coverage is reduced.

Replaced jasmine with jest and fixed the coverage issue


Question about r + δr, s + δs

There two methods to realize r + δr, s + δs

base value addition

self._scaling + delt

as: https://github.com/graphdeco-inria/gaussian-splatting/blob/main/scene/gaussian_model.py#L50C19-L50C19

activated value addition

self.opacity_activation(self._opacity) + delt

as: https://github.com/graphdeco-inria/gaussian-splatting/blob/main/scene/gaussian_model.py#L115
which one you take?

Tnanks for your answer

Hey @ingra14m
I find that your code seems to implement the latter. Is this a mistake or is it intentional?
(https://github.com/ingra14m/Deformable-3D-Gaussians/blob/152ff1fff21abff0400bfa6df9cc9ee50c9b9694/gaussian_renderer/__init__.py#L87C16-L87C16)
        scales = pc.get_scaling + d_scaling
        rotations = pc.get_rotation + d_rotation

where get_scaling and get_rotation are both activated value: (https://github.com/ingra14m/Deformable-3D-Gaussians/blob/152ff1fff21abff0400bfa6df9cc9ee50c9b9694/scene/gaussian_model.py#L58C6-L58C6)
    @property
    def get_scaling(self):
        return self.scaling_activation(self._scaling)

    @property
    def get_rotation(self):
        return self.rotation_activation(self._rotation)

Should this part of the code be modified like this:
        scales = pc.scaling_activation(pc._scaling + d_scaling)
        rotations = pc.rotation_activation(pc._rotation + d_rotation)

Hi, sorry for late reply. Because I cannot receive messages in time for issues that are closed.
Your modification is certainly physically correct, and this change is very appropriate. However, in early attempts, this would reduce the rendering quality. Therefore, I adopted the format in the code, which is kind of a trick for quality.


disable BackAndroid HardwarePress on bottom scene

Version
Tell us which versions you are using:

react-native-router-flux v3.37.0
react-native v0.41.2

I'm trying to disable the BackAndroid hardware button when I'm sitting on a certain scene. I've tried using:
BackAndroid.addEventListener('hardwareBackPress', () => {...})

to control it myself but I can't seem to find a way to get the current scene's "key" If I could test for my "base" key then I would return true and disable BackAndroid.
Is there another way to do this?

Current scene or current router stack i suppose.

You should be able get the scene key/name from props
try to print the following into the console log, to understand what I'm talking about, in your render method:
console.log(this.props.navigationState.key)

This should return your key, same for name just access the name value inside navigationState.
Hope this helps.


Fix scale test errors caused by upstream server count

Proposed changes
Problem: When scale test runs with NGINX Plus with 648 upstream servers, it reports both NGF and NGINX Plus errors, because at some point the upstream zone size is no longer enough to hold all upstream servers. As a result, NGF fails to update NGINX Plus.
Solution: Adjust the upstream server count on the scale test when it runs with NGINX Plus.
Testing: Test works and no longer reports errors.
Closes #2023
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[ ] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that all unit tests pass after adding my changes
[ ] I have updated necessary documentation
[ ] I have rebased my branch onto main
[ ] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

None

I've added the change to scale_test.go such that when running with NGINX Plus, it only uses 556 upstream servers.
However, I encountered some issues where this fix had flaky results. Sometimes the test would pass and sometimes it would error.
I've recorded the results from multiple runs of the test. the files with the name big-node are test runs on the n2d-standard-16 which is the correct node size. I made a mistake where I used a default node of e2-medium for the other results.
Regardless of the node size, I found that with upstream server count of 557 (one above the recommended limit), it always failed and reported errors in the logs and in the writeup. However, with upstream server count of 556 it sometimes passed and sometimes failed. However, when it did fail, there would be no reported errors in the test writeup, however the error was present in the logs.
Does anyone have any thoughts on how to proceed with this?

@bjee19

However, with upstream server count of 556 it sometimes passed and sometimes failed. However, when it did fail, there would be no reported errors in the test writeup, however the error was present in the logs.

What's the error in the logs? Is it the upstream server full error?

Yep from the nginx logs its:
2024/08/21 20:52:25 [crit] 121#121: ngx_slab_alloc() failed: no memory in upstream zone "scale_backend_80"
2024/08/21 20:52:25 [notice] 28#28: signal 1 (SIGHUP) received from 7, reconfiguring
2024/08/21 20:52:25 [notice] 28#28: reconfiguring
2024/08/21 20:52:25 [crit] 28#28: ngx_slab_alloc() failed: no memory in upstream zone "scale_backend_80"

And the NGF logs its:
{"level":"error","ts":"2024-08-21T20:52:25Z","logger":"eventLoop.eventHandler","msg":"couldn't update upstream via the API, reloading configuration instead","batchID":287,"upstreamName":"scale_backend_80","error":"failed to update servers of scale_backend_80 upstream: failed to add <IP_ADDRESS>:8080 server to scale_backend_80 upstream: expected 201 response, got 500. error.status=500; error.text=upstream memory exhausted; error.code=UpstreamOutOfMemory; request_id=6b9527946bd39bb7c95829698260544d; href=https://nginx.org/en/docs/http/ngx_http_api_module.html","stacktrace":"github.com/nginxinc/nginx-gateway-fabric/internal/mode/static.(*eventHandlerImpl).updateUpstreamServers\n\tgithub.com/nginxinc/nginx-gateway-fabric/internal/mode/static/handler.go:374\ngithub.com/nginxinc/nginx-gateway-fabric/internal/mode/static.(*eventHandlerImpl).HandleEventBatch\n\tgithub.com/nginxinc/nginx-gateway-fabric/internal/mode/static/handler.go:200\ngithub.com/nginxinc/nginx-gateway-fabric/internal/framework/events.(*EventLoop).Start.func1.1\n\tgithub.com/nginxinc/nginx-gateway-fabric/internal/framework/events/loop.go:74"}

Update to the above: there was user testing error on my behalf which gave false negative results for these changes. After fixing my testing procedure, setting the upstream server count to what we suspected would work (original number from the manual test) 556, lets the scale test correctly pass.


npm install failed

I am following the basic instruction "Running Project" on ubuntu 16.04 but it throws error at npm install as follows
Package cairo was not found in the pkg-config search path.
Perhaps you should add the directory containing cairo.pc' to the PKG_CONFIG_PATH environment variable No package 'cairo' found gyp: Call to './util/has_lib.sh freetype' returned exit status 0 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error  gyp ERR! stack Error: gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:336:16)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.13.0-39-generic
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/abhijit/sdk/node_modules/canvas
gyp ERR! node -v v8.11.1
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/abhijit/.npm/_logs/2018-05-11T06_20_25_381Z-debug.log

Try the steps in the developing notes https://github.com/boundlessgeo/sdk/blob/master/DEVELOPING.md


keylog_start  not working

[ Session Opened ] <IP_ADDRESS> - Windows 10
paradoxia >> (<IP_ADDRESS>:58371) : sessions 0
paradoxia >> (<IP_ADDRESS>:58371) : keylog_start
paradoxia >> (<IP_ADDRESS>:58371) : keylog_start
[+] Injected Reflective DLL into PID 10368 ...
paradoxia >> (<IP_ADDRESS>:58371) : ls
[i] 20 seconds have passed and we have received no response from Paradoxia. There may be a problem.
paradoxia >> (<IP_ADDRESS>:58371) : ls

Can you kill the session and try again? And let me know if it works then?


Make elf loading independent of section order

Previously, elf parsing failed if the sh_link or sh_info field of a
section referenced a section that was not yet parsed (i.e. greater than
the current section index).

Can one of the admins verify this patch?

ok to test

test this please

Test summary for commit b34a720ce2e30a45fb4051177c9562c9f06e80c9
Driver commits used in build
LLPC: dev 3ad209dfb4bdf88dd26879d2b3ea152bcd3db5b3
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 9795e006e9adb7b49b8abd32cd47c49b290fa3fc
LLVM: amd-vulkan-dev 97cc33415120ae3ed472b6dd5cb234b74a80bd80

Build Failed

retest this please

Test summary for commit b34a720ce2e30a45fb4051177c9562c9f06e80c9
Driver commits used in build
LLPC: dev 3ad209dfb4bdf88dd26879d2b3ea152bcd3db5b3
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 9795e006e9adb7b49b8abd32cd47c49b290fa3fc
LLVM: amd-vulkan-dev 1ca248e6fc6d4d15491756f92f4da139222ef3ca

Build Failed

retest this please

Test summary for commit b34a720ce2e30a45fb4051177c9562c9f06e80c9
Driver commits used in build
LLPC: dev 3ad209dfb4bdf88dd26879d2b3ea152bcd3db5b3
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 9795e006e9adb7b49b8abd32cd47c49b290fa3fc
LLVM: amd-vulkan-dev 1ca248e6fc6d4d15491756f92f4da139222ef3ca

Build Failed

retest this please

Test summary for commit b34a720ce2e30a45fb4051177c9562c9f06e80c9
Driver commits used in build
LLPC: dev 3ad209dfb4bdf88dd26879d2b3ea152bcd3db5b3
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 9795e006e9adb7b49b8abd32cd47c49b290fa3fc
LLVM: amd-vulkan-dev 1ca248e6fc6d4d15491756f92f4da139222ef3ca

Build Failed

retest this please

Test summary for commit b34a720ce2e30a45fb4051177c9562c9f06e80c9
Driver commits used in build
LLPC: dev e310ad7ad84d3aa8c6e717c605f35c5e6906089c
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 54194f5ebb7d1d6b44b9eb87217041f44e08f789
LLVM: amd-vulkan-dev 1ca248e6fc6d4d15491756f92f4da139222ef3ca

Build Failed

retest this please

Test summary for commit b34a720ce2e30a45fb4051177c9562c9f06e80c9
Driver commits used in build
LLPC: dev e310ad7ad84d3aa8c6e717c605f35c5e6906089c
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 54194f5ebb7d1d6b44b9eb87217041f44e08f789
LLVM: amd-vulkan-dev 1ca248e6fc6d4d15491756f92f4da139222ef3ca

Build Failed

retest this please

Test summary for commit b34a720ce2e30a45fb4051177c9562c9f06e80c9
Driver commits used in build
LLPC: dev e310ad7ad84d3aa8c6e717c605f35c5e6906089c
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 54194f5ebb7d1d6b44b9eb87217041f44e08f789
LLVM: amd-vulkan-dev 1ca248e6fc6d4d15491756f92f4da139222ef3ca

Build Failed

retest this please

Test summary for commit b34a720ce2e30a45fb4051177c9562c9f06e80c9
Driver commits used in build
LLPC: dev e310ad7ad84d3aa8c6e717c605f35c5e6906089c
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 54194f5ebb7d1d6b44b9eb87217041f44e08f789
LLVM: amd-vulkan-dev 1ca248e6fc6d4d15491756f92f4da139222ef3ca

CTS tests (built with branch Vulkan-CTS-<IP_ADDRESS>-cherry-picks)
Rhel 7.6, Vega10
Passed: 3906/3907 (100.0%)
Failed: 1/3907 (0.0%)
Failures:
FAILURE: dEQP-VK.api.object_management.alloc_callback_fail.instance
Stack trace: Timeout or crahsed

Hi @Flakebi , looks like dEQP-VK.api.object_management.alloc_callback_fail.instance is failed, could you please help to take a look?

Uh right, seems like I overlooked the effect of the break in the for-loop on errors.
The test should pass now.

retest this please

Test summary for commit 554d53c819c25230be06018a11d8dc20da1a9ce7
Driver commits used in build
LLPC: dev e310ad7ad84d3aa8c6e717c605f35c5e6906089c
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 54194f5ebb7d1d6b44b9eb87217041f44e08f789
LLVM: amd-vulkan-dev 1ca248e6fc6d4d15491756f92f4da139222ef3ca

CTS tests (built with branch Vulkan-CTS-<IP_ADDRESS>-cherry-picks)
Rhel 7.6, Vega10
Passed: 312622/312622 (100.0%)
Failed: 0/312622 (0.0%)

Ubuntu 18.04, Vega20
Passed: 312622/312622 (100.0%)
Failed: 0/312622 (0.0%)

Test summary for commit 554d53c819c25230be06018a11d8dc20da1a9ce7
Driver commits used in build
LLPC: dev e310ad7ad84d3aa8c6e717c605f35c5e6906089c
SPVGEN: dev 5378c7618a2a3bf60ba01a86db980930e8581146
XGL: dev 54194f5ebb7d1d6b44b9eb87217041f44e08f789
LLVM: amd-vulkan-dev 1ca248e6fc6d4d15491756f92f4da139222ef3ca

CTS tests (built with branch Vulkan-CTS-<IP_ADDRESS>-cherry-picks)
Rhel 7.6, Vega10
Passed: 312622/312622 (100.0%)
Failed: 0/312622 (0.0%)

Ubuntu 18.04, Vega20
Passed: 312622/312622 (100.0%)
Failed: 0/312622 (0.0%)

Thanks!


Default timelamps conversion commands and other methods

Used to use avcon and t0000 folder created for terminal if it failed. Folder is no longer created.

A folder is still created named txxxx where xxxx is the time lapse number. It gets filled with the images renamed so that they can be recognised by the converter.
The folder and files are removed after the conversion routine finishes. This is done by the command line formed in preview.php round about line 205
$cmd = "(" . str_replace("i_%05d", "$tmp/i_%05d", $cmd) . BASE_DIR . '/' . MEDIA_PATH . "/$vFile ; rm -rf $tmp;) >/dev/null 2>&1 &";
You can take out the rm -rf $tmp; part if you wish to check the folder out.
The command was changed to use gstream from avconvert as this uses the GPU to do the processing and is much faster. However, this won't work for all combinations of image resolution due to GPU restrictions. In particular, it won't convert very high image resolutions. I find that it works OK up to 1920 x 1080. Start by using 1296 x 972.


DOCSP-33297: fix link to Helpers.scala and mention its use in code comments

https://jira.mongodb.org/browse/DOCSP-33297

@rozza could you do a tech review on this when you get the chance? While the only code change is the one you suggested, just wanted to confirm that everything looks correct to you. Thanks!


Defaulting webhook for enforced Velero Backup/Restore spec in NAB/NAR spec

With https://github.com/migtools/oadp-non-admin/issues/37, admin users will be able to enforce Velero Backup/Restore spec in NonAdminBackup/Restore spec fields. For better non admin users experience, would be good to apply the enforced NonAdminBackup/Restore spec fields as defaults. To do this, we need to create a defaulting webhook.
To do that, we need to run
kubebuilder create webhook \
    --plugins go.kubebuilder.io/v4 \
    --group nac \
    --version v1alpha1 \
    --kind NonAdminBackup \
    --defaulting
make manifests

and update docs/architecture.md. Reference https://book.kubebuilder.io/cronjob-tutorial/webhook-implementation

Note: would be better to update kubebuilder version prior to this work.

We also need to update NAC Deployment in OADP and deploy a NAC Service and NAC MutatingWebhookConfiguration

@mateusoliveira43 will this webhook be part of non-admin backup or installed via oadp?


feat: display owner of selected pixel

[x] issue #10
[x] follows contribution guide
[ ] code change includes tests
[ ] breaking change

Replaced hardcoded placed_by value in the Owner field with address data

Nice work!


Fix comments flagged by comment style checker

Overview
After #7635 was merged, it looks like a few comments hadn't been updated to the newly enforced style. This PR should fix the last of them.
https://dev.azure.com/aipmr/MixedRealityToolkit-Unity-CI/_build/results?buildId=10576&view=logs&j=ae5f814d-d003-5afd-2125-fa0189ea8658&t=12d627c1-3bb6-55bf-f915-b77e58828cea
Changes

Fixes: CI failure found by #7635

/azp run

Thanks! Sorry for missing those


[editor] Module parse failed error

There seems to be a syntax error/typo that leeds to a failing import of rdf-editor.
I tried to import '@rdfjs-elements/rdf-editor' as it is desribed in the README but got an error (see attached screenshot below) that pointed to the following line of code:
https://github.com/zazuko/rdfjs-elements/blob/d72708215c97ff263edb19a3c690961c8ddbfeec/packages/rdf-editor/src/RdfEditor.js#L135
Removing the ? solved the issue.
Screenshot of error message in console:

Hi @zollillo. Thank you for raising this.
The ?. syntax for optional chaining which is not yet fully supported on all platforms.
I can push a new version with this part removed but please tell me about your setup. Are you using a bundler?

Hi @tpluscode, thank you for clarifying - I didn't know about optional chaining.
Yes, we are using Webpack as a module bundler.

Please try v0.3.4

Hey @tpluscode, v0.3.4 is working - no errors when importing @rdfjs-elements/rdf-editor! Thank you for pushing a new version!
FWIW, we are using webpack v4.42.1 and also typescript v3.5.3.
We tested using optional chaining from within our codebase and there were no problems.
Again, thank you! ✨

You're welcome.
TypeScript would compile down to remove this syntax. node_modules, however, are usually excluded from processing unless explicitly configured.
It is ironic that webpack would fail to parse this, while the syntax is otherwise widely supported by latest browsers :)


docs(using-packages): global configurations

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


Replace all usages of <Reference> with <Dependency> to workaround issues in Visual Studio

Still haven't figured out what leads to https://developercommunity.visualstudio.com/content/problem/377676/argumentexception-thrown-by-referenceshostbridge-a.html (cref https://github.com/dotnet/project-system/issues/4237), but it seems the root cause is that we are attempting to use the <Reference> item group name.
This PR replaces all usages of <Reference> with <Dependency> to workaround this.

Command line builds work fine with either item group name. I attempted to figure out what was wrong in VS. Design time builds in VS are running our custom <Reference> resolution correctly, but CPS was still blowing up with an ArgumentException in ReferencesHostBridge. I don't have the VS debugging skills to figure out what is wrong, so I'm giving up on using <Reference>. Just a hunch - my guess is there is something else in VS that still reads the project statically to find <Reference> items, and this leads to duplicate keys in some internal VS dictionary because we convert <Reference> to <ProjectRefenence> or <PackageReference> based on which is the correct thing to do given versions/servicing/patching etc.
cc @Pilchie @davkean

Closing in favor of a less-intrusive workaround: https://github.com/aspnet/Extensions/pull/616.


Manually change EOL to LF for many files at once

type: feature request
Right now there is no integrated tool to convert all line endings for existing files in a project to LF from CRLF. You either have to change them manually for every file or resort to command line scripts as in #25209.
Requested feature: One-click solution to convert the EOL of many existing files in a folder/workspace.

VSCode Version: 1.31.1
OS Version: Windows 10 Home 64

I second that motion... It's a huge pain


Consider consolidating some effort with nalgebra?

Hi there, I unfortunately missed the chance to comment on your Reddit announcement post in a timely manner, but I've had your efforts here in the back of my mind since then.
I'm a co-maintainer of nalgebra. I'm using nalgebra for my research on finite element methods applied to computational mechanics (elasticity, contact problems etc.). We have a number of plans for making nalgebra more suitable use for scientific computing, but we're stretched awfully thin - although we have many contributors who help out with small fixes and PRs, we have too few people with the skill set required to drive the bigger changes and to review non-trivial pull requests. My own ability to allocate time to the library is very limited these days. Given the small number of people with the necessary skill set to drive development in scientific computing, I think it would be great if we could consolidate our efforts more when our goals are shared.
I'm not asking you to contribute to nalgebra (although I'd love for that to happen) - I understand very well the allure of starting fresh and building something unhindered by backward compatibility concerns and a large code base that needs to be adapted. I also very much understand the desire for something akin to expression templates - heck, I've written no less than five prototypes for an expression system in Rust myself, but I've never been able to commit the time to going beyond a prototype. I do have many thoughts on this topic, however - it would be great to discuss that further although that is beyond the scope of this issue.
However, I would like to ask you if you would consider contributing some of your effort in a form that nalgebra can take advantage of it as well, similar to how matrixmultiply is used across the ecosystem. For example, for native factorizations it would great to have a relatively lower-level library that would provide factorizations that could be used in different higher-level linear algebra libraries across the ecosystem. This way we could consolidate efforts for the lower-level high-performance parts while having different high-level interfaces for different purposes in the form of nalgebra, householder etc.
Tangentially, your name (@tbetcke) came up during a brief discussion with @jedbrown lately. I think it would be great to have a common communication channel dedicated scientific computing in Rust, in part for the purpose of consolidating efforts like these. Something like a low-maintenance Zulip/Discord or something else maybe? nalgebra has a fairly vibrant community through the @Dimforge Discord server, but a relatively large proportion of users are (hobby) game developers, whereas I've been wanting for a dedicated community focused specifically on scientific computing. If this is of any interest to you, then please feel free to get in touch!

Thanks for the very swift response, and for elaborating on your goals with householder. It's really great to see external funding dedicated to building out the scientific computing ecosystem in Rust. I'm also relieved that you're open to the idea of consolidating some efforts in lower-level packages.
What you're describing is also a bit of a sweet spot that I've also been wanting for. Typically I don't necessarily need maximum performance, but something close without the hassle and inherent issues of BLAS/LAPACK depedencies. I'm excited to see what comes out of householder!
I'd be 100% behind those online meetups, and I can think of a few colleagues/friends who'd likely want to join as well. Coupling occasional synchronous meetups with a more permanent asynchronous channel (Discord/Zulip/whatever) sounds like a good match. I'd be happy to set aside a little bit of time for setting up such a channel if this could be helpful - though we'd have to decide on the technology stack first. Perhaps @jedbrown also has some thoughts on the matter here.

I guess I'm less stressed about the BLAS dependency since BLIS (https://github.com/blas-lapack-rs/blis-src/) has been pretty pain-free if you have a C compiler. But I live in a world where some C code is unavoidable right now and making true research/production use possible feels more urgent than enabling a pure Rust stack (nice for teaching and first steps).
I use Zulip a lot more than Discord so would lean that way. There is a Rust-ML Zulip (some related to linfa, some discussion of AD tools like Enzyme; :wave: @ZuseZ4, who has been doing great work with Enzyme and may be interested in broader Rust scientific computing community). We could join Rust-ML or make a new RustSciComp or RustHPC. And I think we should coordinate a virtual event in the spring.

Hi and thanks @jedbrown for the ping.
I have been thinking about the Blas issue too and while I first didn't cared that much, I have been talking to a few Julia lang developers and generally started to re-consider my opinion. The question they brought up often wasn't whether more experienced Julia / Rust devs, often with a C/C++ background are able to set things up, but rather if those who are coming to python can handle it. I would love some Rust based BLAS which then could even be used by both ndarray and nalgebra (keeping both around is something important for me). We are however a smaller group compared to julia labs + julia computing, so I guess it is worth discussing where we want to invest our time.
I am currently working on moving the Rust+Enzyme autodiff prototype into the nightly compiler, s.t. all Rust functions become differentiable. That and the contributions to Enzyme proper will probably keep me busy for now, but I would also be interested in discussing any related Rust + HPC / ML subjects. As a side note, I'll graduate tomorrow and apply for PhD positions in the Scientific Computing area. There I'll likely have some time to work on Rust related projects there too, so I will would be happy to have meetups with anyone in the broader area. In https://rust-ml.zulipchat.com/ we had bi-weekly meetups and discussions in the past, maybe there is enough overlap to use it? I also wouldn't mind using another zulip  / discourse / ...
ping @Bytesnake, who also works on the rust-enzyme frontend and linfa. They also discussed Blas issues quite a bit at linfa.

@jedbrown:

I guess I'm less stressed about the BLAS dependency since BLIS (https://github.com/blas-lapack-rs/blis-src/) has been pretty pain-free if you have a C compiler. But I live in a world where some C code is unavoidable right now and making true research/production use possible feels more urgent than enabling a pure Rust stack (nice for teaching and first steps).

Last time I looked at BLIS it looked problematic to compile on Windows. I don't use Windows myself but some of my colleagues do, so it's important for me to have something that works smoothly on Windows. Has the Windows support improved? I can't see any "warnings" in the README anymore... That'd be great!

I use Zulip a lot more than Discord so would lean that way. There is a Rust-ML Zulip (some related to linfa, some discussion of AD tools like Enzyme; wave @ZuseZ4, who has been doing great work with Enzyme and may be interested in broader Rust scientific computing community). We could join Rust-ML or make a new RustSciComp or RustHPC. And I think we should coordinate a virtual event in the spring.

I'd personally prefer a separate channel or server for scientific computing. ML and sci comp often get conflated (for example on the Rust community Discord), and in my experience this means that scientific computing stuff often gets lost among all the ML content, given the huge number of ML researchers/practitioners compared to scientific computing people. Doubly so for those of us who are not working on ML!

Hi,
I agree with @Andlon that we should have a dedicated group for Rust Scientific Computing Discussions.
With regards to BLIS, etc. The matrixmultiply project is a wonderful start. I had a discussion with Barry Smith from the PETSc project yesterday about Rust for Scientific Computing. His suggestion with regards to Rust native BLAS was to simply start with some current Fortran Lapack functions and translate them into native Rust as a lot of the heavy lifting with regards to BLAS3 is already done by matrixmultiply.
But such discussions about strategy would be perfect for a dedicated Scientific Computing Channel. There are lots of other things to work through. One important topic is the role of async/await in Scientific Computing, great tool to build complex task graphs but little experience about use in CPU intensive tasks. Nevertheless, Barry mentioned a number of algorithmic problems that would benefit from proper async support.
A dedicated group would also allow us to coordinate Resources better. We have some decent resources now on our side with a new computational researcher @mscroggs and some Research Software Engineers who are keen to get into Rust Scientific Computing and will support this work. But we need to find good coordination across the various efforts.
I am happy with Zulip and Discord and have no preference.

A quick note on Zulip / Discord: one thing that irks me about Discord is that it doesn't support LaTeX rendering. I have precious little experience with Zulip, but it looks like it supports TeX, which may be useful for a community focused on science...

Yeah, we've been using Zulip heavily for a few years, in part due to the math support and code snippet integration (it can automatically link code snippets to the appropriate playground). Any preference on names? rust-scicomp? scicomp-rs? rust-cse?
BLIS is tested in Appveyor on Windows, though it needs mingw. I guess it could be added to Chocolatey (which we use out of convenience in rsmpi testing). I get your point that it isn't automatic. While translating Fortran Lapack is possible, it just seems like a lot of developer effort. Note that one needs a lot more than GEMM for things like eigensolvers so there would be additional work at the BLAS level (probably emulating BLIS).
I think async/await could be really useful for GPU offload and overlapping communication with computation.

@jedbrown: I'd say rust-scicomp is the most descriptive, at least. It also uses a naming scheme consistent with the aforementioned rust-ml, which is probably also a minor bonus. I can't think of any particular arguments for the other alternatives.

Cool, please sign up here.
https://rust-scicomp.zulipchat.com/join/uznofpa3bvfjkw4nzpj3qfyn/

Hi all, it's great to see the numerics community in Rust gain traction!
Like @ZuseZ4 said, we had our issues with the BLAS/LAPACK dependencies. They are easy to use for experienced users but we got frequent requests from newbies who weren't able to set up their system libraries correctly. Also cross-compiling to embedded devices is no fun with LAPACK. @yuhanlii started to port important routines to pure Rust for ndarray, you can find it at rust-ml/linfa-linalg and we use them now as a slower default. What I would wish for is a crate with minimal dependencies and generics, similar to matrixmultiply but for linear algebra routines. Though we have a decade of development to catch on, I think that the network effects of cargo and superb tooling can give an edge to established languages. I think that the Rust language itself does not bring much new to the menu for numerical computation.
But I'm super thrilled to see better einops for ndarray/nalgebra, AD with enzyme, simple configuration of complex experiments with serde etc. play together and see the effects of this on other communities.

The matrixmultiply project is a wonderful start.

has anyone experience using polly in LLVM, there is a port of the polybench with mixed results here and I was wondering how that would compete against matrixmultiply

[..] and in my experience this means that scientific computing stuff often gets lost among all the ML content, given the huge number of ML researchers/practitioners compared to scientific computing people.

people using Rust for machine learning are normally a bit insane and not your day-to-day ML practitioners :wink: my hope for the future is that we find a niche with people deeply caring about solving problems and ML libraries with strong background in statistics.

I have precious little experience with Zulip, but it looks like it supports TeX, which may be useful for a community focused on science...

like you said TeX support is necessary to be even practical but what actually makes a real difference are how Zulip organizes everything into topics, the model feels much more like mailing lists (you can actually use it like this) and supports the use with sane shortcuts and fast interface
Also make sure to check out the https://rust-edu.org/ website and Zulip channel, they had recently their first workshop on how to teach Rust paradigms in academia!

Thanks for your input, @bytesnake! I'm particularly curious to hear about people sharing their expectations/ambitions/visions for the Rust scientific computing ecosystem. I hope the new Zulip server that @jedbrown set up can be a great place to do just that :-)


feat: Add CPU-based images

feat: Add CPU-based images
What's changed:

Added CPU-based images;
Refactored GPU-based images, changed their names and moved out apt-packages;

Better and better! 💪🏻


Cannot locate tfevents files

Hi everyone,
Thank you for developing this framework. It is incredibly useful.
Right now, I have successfully implemented an environment for my research. Anyway, I cannot find a way to visualize the learning curves using tensorboard.
Inside my project folder, I have another one called "exp_results", which contains "algo_enc_map" folders. Inside these, for each experiment, I have a pair of JSON files named "experiment_state-date" and "basic-variant-state-date" plus a trainer folder, again containing files such as "progress.csv", "result.json", "params.json", "params.pkl". Furthermore, there's a folder for each checkpoint done during training.
The problem is: no matter which logging directory I use for tensorboard, it will not find any dashboard since no tfevent files are present.
Could you please tell me what I am doing wrong? Thank you in advance.

hello, in any script/.py file, there is a tune.run() function call.
In this calling the last parameter named "local_dir" is the tf_logs dir. You can print it out or customize it if you want to know the specified path.
Thanks.

@fortyMiles thank you very much. It seems I had installed the wrong tensorboard version; it successfully creates tfevents files with an older version (2.2). You could add this as a requirement.


Emit changelog perf degradation

Describe the situation

More perf degradation in emit changelog and memory usage is continuously growing, eps is continuously dropping.
 WITH t AS (
                SELECT
              ip_prefix, count() AS count
            FROM
              (
                SELECT
                  ipv4_cidr_to_range(ip, 28).1 AS ip_prefix, bit_shift_right(ip, 24) AS shuffle_key
                FROM
                  ip_rand
              )
            SHUFFLE BY
              shuffle_key
            GROUP BY
              ip_prefix
            EMIT CHANGELOG
            )
            SELECT count(), ip_prefix FROM t group by ip_prefix

→ Progress: 23.68 million rows, 94.71 MB (6.44 million rows/s., 25.74 MB/s.)                                                                                (3.2 CPU, 4.34 GB RAM)
...

↗ Progress: 79.08 million rows, 316.32 MB (2.08 million rows/s., 8.33 MB/s.)
...
↑ Progress: 82.22 million rows, 328.88 MB (1.08 million rows/s., 4.31 MB/s.
...
↖ Progress: 83.20 million rows, 332.80 MB (923.71 thousand rows/s., 3.69 MB/s.)   (1.7 CPU, 39.40 GB RAM)

How to reproduce

Which Proton server version to use
Which interface to use, if matters
Non-default settings, if any
CREATE TABLE statements for all tables involved
Queries to run that lead to slow performance

Expected performance

Additional context

For count emit changelog, there are additional operations:

save retracted data (i.e. previous count result for changed groups)
loop the changed groups, emit -1 retracted data and +1 aggregated data

Now, I am re-implementing changes tracking in #446
BTW, I think emit changelog is not suitable for scenarios with large amounts of changes.
For large amounts of data, only a small amount of data changes can be supported better.

The more serious problem is it appears having memory leak


Update README.md

Added the OSF link to Project Instruction & Possible Projects

Same comment as in #258


fixing distribution on windows - the wrong location was causing a NPE on create

don't merge this yet please

ok.. can be merged now


Add getAccount operation of sellers API

Could you please add support for the new sellers endpoint call called: 'getAccount'?
Thank you very much.
https://developer-docs.amazon.com/sp-api/docs/sellers-api-v1-reference#getaccount

@jesusvalle Added it. But please note that it is only available for sandbox and in EU region: https://developer-docs.amazon.com/sp-api/docs/sellers-api-v2024-07-14-use-case-guide


[Issue #272] Remove unnecessary parameters in DataReaderPredicate

This PR removes 2 unnecessary parameters passed in DataReaderPredicate, which are queryString and attributeList.
These two parameters exist because of the legacy design of DataReader. After the refactor of DataReader and some operators in issue #182 during summer, these two parameters are no longer needed by DataReader. This is one of the steps to replace a list of attributes with a list of attribute names, as mentioned in issue #272 .
This PR also modifies all the uses cases of DataReaderPredicate.
This PR is built based on PR #273 .

This PR includes changes from other PRs.  I will review it after you merge other PRs.

@chenlica The previous PR has been merged, now it's good to be reviewed.

LGTM now.


Vague description of TargetResourceGroup property

[Enter feedback here]
Please include mention of how the target resource group is to be identified.  Is this the resource group name or ID?

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

ID: 0ad60041-54f5-d46e-82be-33f451b6593c
Version Independent ID: 2bc1e194-41a3-53b0-cd92-5f5983e3bccd
Content: ResourcesMoveContent.TargetResourceGroup Property (Azure.ResourceManager.Resources.Models) - Azure for .NET Developers
Content Source: xml/Azure.ResourceManager.Resources.Models/ResourcesMoveContent.xml
Service: azure
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

From the description of this operation (for instance here: https://github.com/Azure/azure-rest-api-specs/blob/06042d4ffed6a1ea8319c39cd07ea21efe5d49f7/specification/resources/resource-manager/Microsoft.Resources/stable/2022-09-01/resources.json#L2835) the target resource group must be in another subscription, therefore despite there is no description on this property nor anything on this operation mentioned this, it should be an arm resource id of the resource group. We will follow up on this to get confirmation, and if we confirm this is an arm resource id, we will introduce a new property with the type of ResourceIdentifier to replace this old property to emphasize.

I have confirmed that this should be an arm resource id. I will update the SDK accordingly soon


Refresh Token Expiration Policy

From what I see these two values are not currently supported in Terraform, is there an option to somehow manage it or I'd have to set it manually ?

By the way, from what I see, currently it is not even possible to set Usage Policy using the API, am I correct ?

This has been released as part of https://github.com/FusionAuth/terraform-provider-fusionauth/releases/tag/v0.1.106.


Topics and frame ids for compatibility with Nav2

As I mentioned about the rule of Nav2 (PR) before, topics are separated by namespace and each topic should have the same frame id.
I thought this rule is only for tf (PR), but every topics including sensors should follow this.
I want to add compatibility with Nav2 to mvsim, but I worry about I will break the policy and projects using mvsim.
If there is any rule to follow, I will consider to add additional parameter.
I think there are three options.
a) Make every frame id of each topic the same. (radical)
b) Add parameter to control frame ids. (safe)
c) This changes are not considered in mvsim. (abort)
I will follow the decision.
before (now)

r1

topic name
frame id

cam1
cam1

r1, r2

topic name
frame id

r1/cam1
r1/cam1

r2/cam1
r2/cam1

after (compatible with Nav2)

r1

topic name
frame id

cam1
cam1

r1, r2

topic name
frame id

r1/cam1
cam1

r2/cam1
cam1

So, what I see is that topics are ok: in Nav2 they use as prefix the robot name and mvsim does too, and I think it all makes sense.
On /tf: what I understand in Steve's answer in https://github.com/ros-navigation/navigation2/pull/4594 is that each robot listen to the tf topic tf so it becomes /tf or /r1/tf, etc. depending on the case, right?
What I don't understand is how to avoid collisions between frame_ids (not the /tf topics themselves).
Maybe the point is that multi-robot systems are expected not to share /tf, right?? cc: @SteveMacenski  :pray:
If the answer is yes, ok, let's follow the same convention here, and we'll fix tutorials, and examples,etc. in mvsim.

Maybe the point is that multi-robot systems are expected not to share /tf, right?? cc: @SteveMacenski 🙏

For that setup, yea. You don't need to avoid collisions when there are no collisions

Alright, @SteveMacenski , thanks, it makes sense.
@finani Then, go on and feel free of PR for making things compatible with multi-robot Nav2. :+1:

Thank you all.
Yes, Exactly I worried about frame id collisions.
Because I was already using the entire tf tree for monitoring, and tf tree works only using frame ids.
But, after splitting by namespace, even rviz, It has no problem. (Thanks Steve)
Thank you again.
I will go update this feature.

https://github.com/MRPT/mvsim/pull/51 is merged
Close this issue.


Check if ID_ARRAY IS TABLE OF PLS_INTEGER would be faster

I found different ressources ranging from "generally faster" to "neglectable" in comparison to NUMBER. We might try it out. Would this have side effects to other tools e.g. when ID_ARRAY is transferred to Java?

Ok, so creating a type which is a nested table of PLS_INTEGER is not possible. It only works inside PL/SQL code blocks as an index-by table. As all we do is BULK COLLECT INTO id_array and SELECT a.COLUMN_VALUE FROM t(id_array) AS a and no array lookups I don't see room for huge performance gains. According to this PLS_INTEGER "almost ALWAYS gets turned into a number anyway". Closing the issue for now.


How to rename output from terraform block

In terragrunt.hcl
terraform {
source = "git::https://github.com/terraform-aws-modules/terraform-aws-s3-bucket.git?ref=v2.1.0"
}
I know that the aws s3 module will come out some outputs like "s3_bucket_arn", But I want to re-name it with some prefix like "order_service_s3_bucket_arn". In terraform I can do that with
output "order_service_s3_bucket_arn" {
value       = module.aws_s3_bucker.s3_bucket_arn
}
How to do that in terragurnt?  Thanks.

There really isn't a way to do this in terragrunt, as terragrunt doesn't manipulate the outputs fed out from terraform. You need to do this at the terraform module level. The only way I can think of to do this is via monkey patching of the terraform module.
Terragrunt supports injecting terraform code into an existing module by generate blocks, so you can probably get the output you want by injecting the "right" output block using generate.


[Snyk] Upgrade react-hook-form from 7.43.7 to 7.50.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade react-hook-form from 7.43.7 to 7.50.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 36 versions ahead of your current version.
The recommended version was released 22 days ago, on 2024-02-06.

Release notes

Package name: react-hook-form

7.50.1 - 2024-02-06🥲 Regression: Revert "⌨ fix #10734 watch and useWatch without parameters return type (#11359)"

7.50.0 - 2024-02-01🔧 fix data param in handleSubmit when TTransformedValues is a union type (#11420)
👷 build(Engines): remove pnpm dependency (#11425)
🐞 fixes #11386 get new dirtyFields when reset keeping defaults and dirty values (#11401)
🏷 improve CustomElement type (#11309)
💫 feat(useForm): leave formState flags in a consistent state when throwing in handleSubmit onValid (#11214)
⌨ fix: change DeepPartial to account for object union types & unknown (#11385)
✨ feat(values): priorities values over defaultvalues (#11399)
🐞 close #11246 skip root validation on action when mode and revalidate mode is onSubmit (#11395)
💩 fix #11322 trigger extra re-render with useWatch plus shouldUnregister (#11394)
⌨ fix #10734 watch and useWatch without parameters return type (#11359)
🧑✈ fix #11281 issue with upgrade node version (#11392)
🐞 fix #11368 keep form state mounted when keeping values (#11384)
🐞 fix #11374: Nested deep partial with unknown (#11373)
thanks to @ Moshyfawn, @ jonahallibone, @ eladattias1996, @ RulerOfCakes, @ anonkey, @ Ar4ys, @ IanVS and @ r-kataoka11

7.49.3 - 2024-01-08🐛 fix(formState, disabled): infer controlled disabled form state (#11361)
🐛 fix(reset): remove global reset option flag (#11355)
🐛 fix(useController): check if disabled state was set by user (#11353)
🖨 fix: Change DeepPartial type definition to be compatible with unknown (#11333)
🐞 fix #11328 resetField with object as defaultValue (#11329)
thanks to @ Moshyfawn, @ geeee and @ RulerOfCakes

7.49.2 - 2023-12-13🐞 fix #11292 issue with controller validation prop (#11294)

7.49.1 - 2023-12-12🐞 fix #11276 issue with disabled omit on Controller (#11277)
🐞 fix #11287 disabled prop cause const dirtyFields update (#11291)

7.49.0 - 2023-12-09 Read more

7.48.2 - 2023-11-05🐞 #11106 fix disabled prop not update dirty formState (#11143)
🐞 fix controller update with disabled prop from useForm (#11142)

7.48.1 - 2023-11-04🐞 fix controller update with disabled prop from useForm

7.48.0 - 2023-11-04 Read more

7.47.0 - 2023-10-02🫡 allow keepIsSubmitSuccessful flag (#9640)
const { reset } = useForm()
<Form
onSubmit={() => {
reset(formValues, {
keepIsSubmitSuccessful: true,
});
}}
/>
🦉 fix typo in form.ts (#10978)
🤡 close #10907 potential fix on unmounted component (#10980)
🪖 simplify logic for subscription by name (#10947)
thanks to @ stefanpl, @ kai-dorschner-twinsity & @ nitschSB

7.46.2 - 2023-09-21

7.46.1 - 2023-09-04

7.46.0 - 2023-09-03

7.46.0-next.0 - 2023-08-13

7.45.4 - 2023-08-05

7.45.3 - 2023-08-04

7.45.2 - 2023-07-17

7.45.1 - 2023-06-28

7.45.0 - 2023-06-19

7.45.0-next.1 - 2023-06-18

7.45.0-next.0 - 2023-06-11

7.44.3 - 2023-06-01

7.44.3-beta.1 - 2023-05-31

7.44.3-beta.0 - 2023-05-31

7.44.2 - 2023-05-28

7.44.1 - 2023-05-27

7.44.0 - 2023-05-27

7.44.0-rc.5 - 2023-05-20

7.44.0-rc.4 - 2023-05-20

7.44.0-rc.3 - 2023-05-07

7.44.0-rc.1 - 2023-04-15

7.44.0-rc.0 - 2023-03-10

7.44.0-next.1 - 2023-02-16

7.44.0-next.0 - 2023-02-09

7.43.9 - 2023-03-30

7.43.8 - 2023-03-24

7.43.7 - 2023-03-18

    from react-hook-form GitHub release notes

Commit messages

Package name: react-hook-form

6a57117 7.50.1
7cffc95 Revert "⌨ fix #10734 watch and useWatch without parameters return type (#11359)"
5c3b4c0 ✅ chore: add noop Utils Function (#11455)
2dacf05 7.50.0
6fee03c 🔧 fix data param in handleSubmit when TTransformedValues is a union type (#11420)
919c578 👷 build(Engines): remove pnpm dependency (#11425)
4c21b28 🐞 fixes #11386 get new dirtyFields when reset keeping defaults and dirty values (#11401)
f8bbb30 🏷 improve `CustomElement` type (#11309)
f18c147 💫 feat(useForm): leave formState flags in a consistent state when throwing in handleSubmit onValid (#11214)
cec3267 ⌨ fix: change `DeepPartial` to account for object union types & `unknown` (#11385)
a0583ff ✨ feat(values): priorities values over defaultvalues (#11399)
4e6fccb 🐞 close #11246 skip root validation on action when mode and revalidate mode is onSubmit (#11395)
ede7f1e 💩 fix #11322 trigger extra re-render with useWatch plus shouldUnregister (#11394)
fdbadbb ⌨ fix #10734 watch and useWatch without parameters return type (#11359)
f4c126f 🧑✈ fix #11281 issue with upgrade node version (#11392)
7459afe 🐞 fix #11368 keep form state mounted when keeping values (#11384)
75cab7f 🐞 fix #11374: Nested deep partial with unknown (#11373)
e4c1fb1 7.49.3
e6a5b1a 🐛 fix(formState, disabled): infer controlled disabled form state (#11361)
dab35e1 🐛 fix(reset): remove global reset option flag (#11355)
4f4eae5 🐛 fix(useController): check if disabled state was set by user (#11353)
012bb19 🖨 fix: Change `DeepPartial` type definition to be compatible with `unknown` (#11333)
94114e4 🐞 fix #11328 resetField with object as defaultValue (#11329)
7e5af8d 7.49.2

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

/retest


Migrated Spring Boot demo to 1.11.

Thanks @joerg84 but I'm going to close this as it's now somewhat out of date.  If you fancy refreshing it for DC/OS 2.0 feel free to issue a new PR.


"Unexpected error" running bonnet_model_compiler.par on "mobilenet_v1_160res_0.5_imagenet.pb" (Macbook Pro issue?)

As a fist step, I've been trying to run the latest bonnet_model_compiler.par using "mobilenet_v1_160res_0.5_imagenet.pb" (both located in the same folder on my machine and downloaded using the links on aiyprojects.withgoogle.com/vision/).
I run the compiler using:
./bonnet_model_compiler.par  --frozen_graph_path=./mobilenet_v1_160res_0.5_imagenet.pb --output_graph_path=./mobilenet_v1_160res_0.5_imagenet.binaryproto --input_tensor_name="input" --output_tensor_names="MobilenetV1/Predictions/Softmax"  --input_tensor_size=160
but it always returns an "unexpected error".  I tried using the --debug flag, but I can't find the crash log.  Setting the flag does create a folder called "bonnet_model_compiler.runfiles-mircea" in the /tmp directory, but it I don't see any log files in there.
I've tried the above running 64-bit versions of Ubuntu 14.04.5 LTS, Ubuntu 16.04 and Lubuntu 14.04 installed on a 2007 Macbook Pro, but with no luck.  In each case, Ubuntu/Lubuntu was the only the OS installed (not a virtual box) and I made sure that Python 2.7 was the default version being used.
Can the Macbook Pro hardware be the problem or is there something else I'm missing in the setup?  I checked issue #314, but did not see an answer that would help troubleshoot my problem any further.
Thanks,
Mircea

I've never run into such issue before. Could you try with python3?

Just tried it with Python 3.4.3 and still no luck.  Also tried another fresh install of Lubuntu 14.04 followed by installing Python3, pip3 and Virtualenv and same result.  Any particular packages that need to be installed?

@mircea800  Are you still having this problem?

I just downloaded another copy of bonnet_model_compiler.par and the latest mobilenet_v1_160res_0.5_imagenet.pb, but same problem with an "unexpected error".  And still no log file in the "bonnet_model_compiler.runfiles-mircea" subfolder in the /tmp directory.

@mircea800
I tried again on Ubuntu 16.04, installed on a VirtualBox. It works fine. It's hard to imagine this is caused by running Ubuntu on MBP directly. But would you mind to try again with Ubuntu installed in VirtualBox?


Governance. Add delegation. Can't copy the address

Description
Can't copy the address of delegate.
Also, there is no block explorer links
https://github.com/user-attachments/assets/fc6d622a-9f67-4849-8018-9b44a9cde50c
Steps to Reproduce

Go to Governance
Open Add delegation
Try to open Delegate info

Expected Behavior
Can open info about delegator, showing his address and possibility to open his address on block explorers
Actual Behavior
Can't copy address - will open detailed page
Has no block explorers link
Environment
https://github.com/novasamatech/nova-spektr/commit/b3a381d4e43fe8ca1218e07e785f903d5eda47a4

Status verification: ✅