[C++][Parquet] Encoding: DeltaLengthByteArrayEncoder don't have right stats when Put with Array

Describe the enhancement requested
DeltaLengthByteArrayEncoder works well, however, when put with arrow-array, the statistics would be wrong. Because EstimatedDataEncodedSize() [1] uses encoded_size_, but it's only incremented in Put/PutSpaced [2], but not handled in Array put [3]. This makes statistics wrong, which makes a page grows larger than INT32_MAX [4]
Luckily, this doesn't affect the result of encoding, just makes the statistics smaller than expected.
[1] https://github.com/apache/arrow/blob/main/cpp/src/parquet/encoding.cc#L2749
[2] https://github.com/apache/arrow/blob/main/cpp/src/parquet/encoding.cc#L2814
[3] https://github.com/apache/arrow/blob/main/cpp/src/parquet/encoding.cc#L2763-L2775
[4] https://github.com/apache/arrow/blob/d10ebf055a393c94a693097db1dca08ff86745bd/cpp/src/parquet/column_writer.cc#L1561-L1563
Component(s)
C++, Parquet

Issue resolved by pull request 41546
https://github.com/apache/arrow/pull/41546

BTW thank you @mapleFU  for pushing the open parquet C++ implementation along ❤

Thanks! I'm a Parquet C++ user and benifit from it's code so I've duty to backport bugfix and optimizations, and thanks the help with community I can use it in a better way


Tuple enum variant generates unused_parens warning for Deserialize

After updating to 1.0.28 I started receiving an unused parens warning for an enum containing a tuple variant with at least two arguments (i.e. A(usize) won't trigger the warning). I don't get this warning on 1.0.27.
Example:
extern crate serde;
#[macro_use]
extern crate serde_derive;

#[derive(Serialize, Deserialize)]
enum A {
    A(usize, usize),
}

Output:
warning: unnecessary parentheses around function argument
 --> src/lib.rs:5:21
  |
5 | #[derive(Serialize, Deserialize)]
  |                     ^^^^^^^^^^^ help: remove these parentheses
  |
  = note: #[warn(unused_parens)] on by default

warning: unnecessary parentheses around function argument
 --> src/lib.rs:5:21
  |
5 | #[derive(Serialize, Deserialize)]
  |                     ^^^^^^^^^^^ help: remove these parentheses

    Finished dev [unoptimized + debuginfo] target(s) in 0.19 secs

Thanks! The parentheses used to be a workaround for a compiler issue that has since been fixed: https://github.com/rust-lang/rust/issues/47311. I removed the workaround in 30361ac6d022839be19fc608645756ed1be839ab and released 1.0.29 which should have no warnings.

Thanks for the quick turnaround! No more warnings now :smile_cat:


Add theme to childContext

Let's say I have some two components, ChildComponent
@themr('ChildComponent')
class ChildComponent extends Component {
  render() {
    const { theme } = this.props;
    return (

    )
  }
}

and ParentComponent
@themr('ParentComponent')
class ParentComponent extends Component {
  render() {
    const { theme } = this.props;
    return (

        <ChildComponent theme={theme} />

    )
  }
}

For the theme prop of ParentComponent to be applied to ChildComponent, it has to be explicitly passed down.  It would be a breaking change, but could Themed define getChildContext so that the theme of ParentComponent is automatically part of the theme of ChildComponent?

I guess there is something we could do to handle these cases explicitly. If a child component can be considered part of the parent component, they both can define (and must define) the same key. For example themr('Radio', style).
If you provide a theme via context it's going to work nicely because they use the same key but I guess that if you pass down a style to a parent of an specific type, it makes sense if this component writes in the context the updated theme. Therefore, the child would read from context the theme you passed to the parent via props.
This update is not breaking and has no downsides in my opinion apart from the cost of writing in the context when a theme is received

@wtgtybhertgeghgtwtg
You can easily set the same theme for different keys when constructing context:
import css from './shared.css';
const context = {
 ChildComponent: css,
 ParentComponent: css
};

On the other hand, if you accept exactly the same theme in different components why not to use the same keys (names) for them?

Yeah, you're right, that's what we are doing with react-toolbox. Just using the same key for both child and parent if the belong to the same complex component

@wtgtybhertgeghgtwtg What you are suggesting is a good old cascade when Parent component affects all possible Children on all levels deeper. Such behavior is unsafe and was meant to be eliminated by introduction of css-modules. However, ThemeProviders could still be nested to make such behavior explicit and #19 tracks it.
@javivelasco I believe this issue can be closed.

Cool, thanks @raveclassic !


[Autocomplete] Fix misleading warning

[x] I have followed (at least) the PR section of the contributing guide.

Should fix #19163.

@embeddedt It's a great first pull request on Material-UI 👌🏻. Thank you for working on it!


Using legion to implement matrix multiplication, its execution time is much longer than that of directly using c++ code

I followed legion's usage tutorial. Referring to 8.Partitioning, I wrote a code for matrix multiplication of 4096 sub-matrices 256*256 double precision floats. I found that matrix multiplication using legion is far less efficient than writing code directly in C++.
On my machine, it takes only 2.37s to perform 4096 sub-matrix multiplications, while legion takes 300+s, which is incredible.
I would like to ask, what did I do wrong so that the execution efficiency of legion is so slow, or the scene where I use legion is wrong.

The place to start with almost any performance issue in Legion is Legion Prof, the built-in profiler:
https://legion.stanford.edu/profiling/#legion-prof
Other things you should check while you're at it:

Are you in debug or release mode (DEBUG=1 or DEBUG=0 if using Make; note that the app template defaults to debug)
What version of Legion are you on (branch and specific commit)?
What command line flags did you pass (-ll:cpu ... etc.)?
Did you observe any warnings in the output when running the program?
More system details like OS, compiler, hardware, etc.

Without this information we really can't help you.

I'll also add to the list, did you write a completely custom mapper? If you're relying on the default mapper for performance measurements you're going to have a bad time. Legion has a mapper interface for a reason: if you want performance at the peak of your machine then you need to say exactly how it should be mapped to that machine.

If you want to see an optimized matrix multiple written in Legion I suggest you consult cuNumeric implementation of dot: https://github.com/nv-legate/cunumeric/

@lightsighter do you think not using a custom mapper could lead to 130x (300/2.37) slow down compared to the c++ implementation? I understand that the default mapper is not optimal, but 300s is about 0.4 gflops, which does not sound reasonable even if running with -ll:cpu 1

There are likely other problems with the way the code has been written, but writing a tuned mapper is always a requirement for measuring peak performance with Legion, which is why I added it to the list instead of suggesting that it was the sole problem.

There are also the DISTAL distributed MM implementations:
http://theory.stanford.edu/~aiken/publications/papers/pldi22a.pdf

From: Mike Bauer @.>
Sent: Sunday, March 26, 2023 12:09 AM
To: StanfordLegion/legion @.>
Cc: Subscribed @.***>
Subject: Re: [StanfordLegion/legion] Using legion to implement matrix multiplication, its execution time is much longer than that of directly using c++ code (Issue #1446)
If you want to see an optimized matrix multiple written in Legion I suggest you consult the cuNumeric implementation of dot: https://github.com/nv-legate/cunumeric/
—
Reply to this email directly, view it on GitHubhttps://github.com/StanfordLegion/legion/issues/1446#issuecomment-1484015078, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABBIV75VLZI6CEEUO6MKOY3W57TSJANCNFSM6AAAAAAWH6URNQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I followed legion's usage tutorial. Referring to 8.Partitioning, I wrote a code for matrix multiplication of 4096 sub-matrices 256*256 double precision floats. I found that matrix multiplication using legion is far less efficient than writing code directly in C++.

Something that would show up in the profiles is that your tasks are probably too small if I am understanding what you are saying. Are you 1) multiplying 4096 separate matrices of size 256 x 256? Decomposing a 4096x4096 matrix into blocks of size 256x256 and doing those multiplications in parallel?
If 1), the 256x256 multiplications are probably resulting in tasks that are too small, exposing the analysis overheads of Legion. If 2), you're partitioning the input matrix into too many pieces. Matrix multiplication is not a problem that benefits from over-decomposition, you want the tiles to be as large as possible. This particular application would do best if you partitioned the matrices into pieces equal to the number of processors you are trying to target.

I followed legion's usage tutorial. Referring to 8.Partitioning, I wrote a code for matrix multiplication of 4096 sub-matrices 256*256 double precision floats. I found that matrix multiplication using legion is far less efficient than writing code directly in C++. On my machine, it takes only 2.37s to perform 4096 sub-matrix multiplications, while legion takes 300+s, which is incredible. I would like to ask, what did I do wrong so that the execution efficiency of legion is so slow, or the scene where I use legion is wrong.

No way, how did you achieve that man? I wrote a matrix-multiplication code using C++. With AVX2, 4096 256x256 matrix multiplication took me 42.15s on 12700H (Single Thread).
#include <iostream>
#include <vector>
#include <random>
#include <chrono>
#include <immintrin.h>
typedef std::vector<double> float_vec;
typedef std::vector<std::vector<double>> matrix;

matrix matrix_mult(matrix &a, matrix &b) {
    int size_a[2] = {static_cast<int>(a.size()), static_cast<int>(a[0].size())};
    int size_b[2] = {static_cast<int>(b.size()), static_cast<int>(b[0].size())};
    if (size_a[0] == size_b[1] and size_a[1] == size_b[0]) {
        matrix c;
        c.reserve(size_b[0]);
        float_vec temp;
        temp.reserve(size_a[1]);
        for (int z = 0; z < size_b[0]; z++) {
            temp.clear();
            for (int y = 0; y < size_a[1]; y++) {
                float sum = 0.0;
                for (int x = 0; x < size_a[0] / 8; x++) {
                    __m256 vec_a = _mm256_set_ps(a[x][y], a[x + 1][y], a[x + 2][y], a[x + 3][y], a[x + 4][y], a[x + 5][y], a[x + 6][y], a[x + 7][y]);
                    __m256 vec_b = _mm256_set_ps(b[z][x], b[z][x+1], b[z][x+2], b[z][x+3], b[z][x+4], b[z][x+5], b[z][x+6], b[z][x+7]);
                    __m256 vec_c = _mm256_mul_ps(vec_a, vec_b);
                    sum += vec_c[0] + vec_c[1] + vec_c[2] + vec_c[3] + vec_c[4] + vec_c[5] + vec_c[6] + vec_c[7];
                }
                for (int x = size_a[0] - size_a[0] % 8; x < size_a[0] % 8; x++) {
                    sum += a[x][y] * b[z][x];
                }
                temp.push_back(sum);
            }
            c.push_back(temp);
        }
        return c;
    }
    std::cout << size_a[0] << " " << size_a[1];
    throw std::logic_error("Invalid Matrix");
}

matrix get_rand_matrix(int x, int y, double min, double max) {
    matrix a;
    a.reserve(x);
    std::random_device rd;
    std::mt19937 mt(rd());
    std::uniform_real_distribution<double> dist(min, max);
    for (int i = 0; i < x; i++) {
        float_vec temp;
        temp.reserve(y);
        for (int j = 0; j < y; j++) {
            temp.push_back(dist(mt));
        }
        a.push_back(temp);
    }
    return a;
}

template <typename T>
void print_matrix(T a) {
    for (int y = 0; y < static_cast<int>(a[0].size()); y++) {
        for (int x = 0; x < static_cast<int>(a.size()); x++) {
            std::cout << a[x][y] << " ";
        }
        std::cout << std::endl;
    }
    std::cout << std::endl;
}

int main() {
    auto out_1 = get_rand_matrix(256, 256, 0, 100);
    auto out_2 = get_rand_matrix(256, 256, 0, 100);
    auto start = std::chrono::high_resolution_clock::now();
    for (int x = 0; x < 4096; x++) {
        matrix_mult(out_1,out_2);
    }
    auto end = std::chrono::high_resolution_clock::now();
    auto duration = std::chrono::duration_cast<std::chrono::microseconds>(end - start);
    if (duration.count() < 1000) {
        std::cout << duration.count() << "us" << std::endl;
    } else if (duration.count() < 1000000){
        std::cout << static_cast<float>(duration.count()) / 1000 << "ms" << std::endl;
    } else {
        std::cout << static_cast<float>(duration.count()) / 1000000 << "s" << std::endl;
    }
}

No way, how did you achieve that man?

This is derailing the discussion, but your matrix multiply implementation is likely significantly slower than what you might find in MKL or OpenBLAS. 3.25G FLOPS sounds low.

@bobqianic "matrix multiplication of 4096 sub-matrices 256256" means the matrix size is 40964096 with tile size 256*256, which is different from your code.

Thanks to everyone who helped and replied, I read and tried your method，that helped me a lot.
As I said, the reference is the code of 8.Partitioning. I just enlarged the num_elements in the code of 8.Partitioning to<PHONE_NUMBER>. But the reason for the slow operation after enlarging the data is consistent with the slowness of my matrix multiplication.
After I set num_elements to 1024 * 1024 * 128, I used perf to count the running performance. Since the running time was too long, I terminated the program directly after running for 15s, and calculated the following flame graph.
As shown in the figure below, using FieldAccessor to directly access the field to write data one by one, most of the running time is spent on writing data.

This gave me an inspiration. For a large amount of data to be written into the field, the default FieldAccessor cannot be used. It is necessary to find an accessor that can quickly access the array.
Then I queried the documentation of legion and found the key sentence
“this code uses an AffineAccessor for the fields. Affine accessors support indexing into regions like arrays”
Then, I modified the default FieldAccessor in INIT_FIELD_TASK_ID to
FieldAccessor<READ_WRITE,double,1,coord_t ,Realm::AffineAccessor<double,1,coord_t>>, and the FieldAccessor in DAXPY_TASK_ID still uses the default one. At this point, as expected, INIT_FIELD_TASK should have a greater access speed increase, and DAXPY_TASK will have a larger bottleneck because it uses the default FieldAccessor. Due to the relatively long calculation time, I only ran it for about 15s this time.
The result is shown in the figure below, INIT_FIELD_TASK has been completed within 15s, and DAXPY_TASK is already being executed. At this point, you can see that the read data in DAXPY_TASK has become a performance bottleneck.

So, all this is due to my unfamiliarity with legion, but your replies have provided me with great help, thank you very much.

Great to hear! The physical instances that your tasks access can be backed by many different data structures, like arrays, or more complicated blocks of contiguous memory pieces. When you know that an instance will be allocated in a specific data structure (as chosen by the mapper), you can use this more specific kind of accessor (the AffineAccessor) to specialize the access method to the kind of data structure. AffineAccessor access usually compiles into a pointer dereference with all of the normal induction variable and strength reduction optimizations applied.

@rohany Yes, using AffineAccessor for access to special data structures can effectively improve read and write performance, which is not reflected in https://legion.stanford.edu/tutorial/, can we consider adding it in the tutorial How about an example or code snippet of AffineAccessor?

Accessors are discussed in more detail in Section 3.1 of the Legion manual including the performance penalties of using the GenericAccessor.


creation of endpoint of the provided example fails with sagemaker_containers._errors.ImportModuleError

Hello,
Following the tutorial for SM Studio  with the example from the SM studio folder I keep getting an error when I try to create to an endpoint. This is indicated by status "fail" for the endpoint.
I can see a error message from the SM dashboard:
"The primary container for production variant default-variant-name did not pass the ping health check. Please check CloudWatch logs for this endpoint."
And then in ClouldWatch I see a line with an error message:
sagemaker_containers._errors.ImportModuleError: 'NoneType' object has no attribute 'startswith'

I am having exactly the same issue trying to retrieve a previously trained model from s3 bucket and deploying it. Is there any news on this issue?


[Question] How does turbo-frame work with a livewire component :question:

:question:
Hello, how does turbo-frame work with a livewire component? Is it possible?

Closing, as there doesn't seem to be an issue between Livewire and Turbo. Feel free to reply or re-open if you think something is not working properly.


Allowing optional building in Full Network E2E Tests

Confirmation

[X] I have checked for similar issues.

Problem
As of now, our Full Network E2E tests build the following services' docker images every time they are run:

bfgd
bssd
popmd

this takes a long time, especially if the change you're testing doesn't affect these services
Suggested solution
allow optional building of each of these in the full network e2e tests; by default, we should build all of them but allow the user to optionally use the last build if it exists
Additional Information
No response

going to close this in favor of testing localnet #97


Perform Kernal 4.8.0-alpha release

Description
Need to perform Kernal 4.8.0-alpha release
Affected Component
APIM
Version
No response
Related Issues
No response
Suggested Labels
No response

Update :  Created PR for preparing for alpha release - https://github.com/wso2/carbon-kernel/pull/3449

Completed Kernel 4.8.0-alpha release. Hence closing.
Related PRs :

https://github.com/wso2/carbon-apimgt/pull/11708
https://github.com/wso2/product-apim/pull/13046


oom detection

Added support for OOM detection. Need to figure out how to test it.

[x] cgroup v2
[x] cgroup v1
[x] add oom exit paths

Codecov Report

Merging #365 (22ae0bb) into main (ff5aa21) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main    #365   +/-   ##
=====================================
  Coverage   6.89%   6.89%
=====================================
  Files          2       2
  Lines         29      29
  Branches      17      17
=====================================
  Hits           2       2
  Misses        27      27

going to fix the cgroup v1 flake.

Fixed... I had to import the tokio-eventfd library to work with cgroupv1 events.

Going to integrate a test and figure out cgroup v1... Something is still wrong.

I added all the requested fixes. We will need much more scaffolding to test OOMs within conmon-rs. I think we should rely on crio's test for now and add a TODO to natively test OOMs with this repo.

@saschagrunert can you try this on a cgroupv1 machine and see if it fails for you?

@saschagrunert can you try this on a cgroupv1 machine and see if it fails for you?

Hm, on Ubuntu 18.04 the setup seems to work:
root@ubuntu1804:~/conmon-rs# ginkgo run -v -r --focus="should write exit file$"
Running Suite: ConmonClient - /root/conmon-rs/pkg/client
========================================================
Random Seed:<PHONE_NUMBER>

Will run 1 of 25 specs
SSSSSSSS
------------------------------
ConmonClient CreateContainer
  should write exit file
  /root/conmon-rs/pkg/client/client_test.go:60
2022-05-03T08:37:52.689Z INFO [conmon::server] Using stdout logger
2022-05-03T08:37:52.689Z INFO [conmon::server] Set log level to: DEBUG
2022-05-03T08:37:52.694Z DEBUG [conmon::rpc] Got a version request
2022-05-03T08:37:52.697Z DEBUG [conmon::rpc] Got a create container request for id 145ac9c38327b45b8eb09b9823e2b71e8c43812226ef8abf2ba7d0b463cefb95
2022-05-03T08:37:52.697Z DEBUG [conmon::streams] Creating new IO streams
2022-05-03T08:37:52.698Z DEBUG [conmon::rpc] PID file is /tmp/conmon-client954065182/pidfile
2022-05-03T08:37:52.698Z DEBUG [conmon::server] Runtime args "--root=/tmp/conmon-client954065182/root create --bundle /tmp/conmon-client954065182 --pid-file /tmp/conmon-client954065182/pidfile 145ac9c38327b45b8eb09b9823e2b71e8c43812226ef8abf2ba7d0b463cefb95"
2022-05-03T08:37:52.698Z DEBUG [conmon::cri_logger] Initializing CRI logger in path /tmp/conmon-client954065182/log
2022-05-03T08:37:52.699Z DEBUG [conmon::streams] Start reading from IO streams
2022-05-03T08:37:52.845Z DEBUG [conmon::oom_watcher] 7611: enabled cgroup v1 oom handling
2022-05-03T08:37:52.845Z DEBUG [conmon::oom_watcher] 7611: using cgroup path : /proc/7611/cgroup
2022-05-03T08:37:52.850Z DEBUG [conmon::oom_watcher] 7611: memory_cgroup_file_oom_path /sys/fs/cgroup/memory/user.slice/145ac9c38327b45b8eb09b9823e2b71e8c43812226ef8abf2ba7d0b463cefb95/memory.oom_control
2022-05-03T08:37:52.852Z DEBUG [conmon::oom_watcher] 7611: successfully setup cgroup v1 oom detection
2022-05-03T08:37:52.881Z DEBUG [conmon::container_io] fd:14:read 21 bytes
2022-05-03T08:37:52.910Z DEBUG [conmon::container_io] fd:16:No more to read
2022-05-03T08:37:52.911Z DEBUG [conmon::container_io] fd:14:No more to read
VmRSS for server is 10592
•SSSSSSSSSSSSSSSS

Ran 1 of 25 Specs in 0.255 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 24 Skipped
PASS
2022-05-03T08:37:52.940Z INFO [conmon::server] Received SIGINT
2022-05-03T08:37:52.940Z DEBUG [conmon::child_reaper] 7611: killing pid
2022-05-03T08:37:52.940Z DEBUG [conmon::child_reaper] Failed killing pid 7611 with error ESRCH: No such process
2022-05-03T08:37:52.940Z DEBUG [conmon::server] Removing socket file /tmp/conmon-client954065182/conmon.sock
2022-05-03T08:37:52.940Z DEBUG [conmon::oom_watcher] 7611: done watching for ooms

one small nit, otherwise LGTM
what about 1.60 helped us?
great work on this, it's been a long haul!

@haircommander We hit this problem with the PR: rust-lang/cargo#10623. The only thing I could find to do is bump the version.

LGTM, summoning @saschagrunert for the merge


onError deos not work

onError deos not work, code below:
    console.error('error', err, logs);
  },

results in:
error undefined undefined

Going to close as I've updated the error reporting behavior. Re-open if you still have issues with some info about your configuration.


Fix/did web create key (#461)

merge in https://github.com/TBD54566975/ssi-sdk/pull/430

Codecov Report

Merging #462 (6bcd078) into main (7522c30) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #462   +/-   ##
=======================================
  Coverage   57.23%   57.23%
=======================================
  Files          67       67
  Lines        7494     7494
=======================================
  Hits         4289     4289
  Misses       2468     2468
  Partials      737      737

Files Changed
Coverage Δ

did/peer/peer0.go
58.54% <100.00%> (ø)

did/web/web.go
68.07% <100.00%> (ø)


proxy basic auth

Hello. Please tell me how you can use basic authorization (login , password) when
launch_arg => ['--proxy-server=proxy.com']

I've never used basic auth with a proxy, but maybe try
launch_arg =><EMAIL_ADDRESS>
... or try setting the HTTP_PROXY variable before launching Chrome:
$ENV{HTTP_PROXY} =<EMAIL_ADDRESS>$ENV{HTTPS_PROXY} =<EMAIL_ADDRESS>
my $mech = WWW::Mechanize::Chrome->new(
    ...
    # launch_arg => []
);

Thanks, but it didn’t work.
I managed to make authorization through:
launch_arg => ['--proxy-server=http://<IP_ADDRESS>:1234'],

...
$chrome->driver->send_packet('Fetch.enable' , 'handleAuthRequests' => JSON::true );

 my $asdf = $chrome->add_listener('Fetch.requestPaused', sub {
   my( $info ) = @_;
   my $requestId = $info->{'params'}{'requestId'};
   $chrome->driver->send_message('Fetch.continueRequest' , 'requestId' => $requestId);
 });

 my $asd = $chrome->add_listener('Fetch.authRequired', sub {
   my( $info ) = @_;
   my $requestId = $info->{'params'}{'requestId'};
   print "Fetch auth\n";
   my %auth = (
     'requestId' => $requestId ,
     "authChallengeResponse" => {"response" => "ProvideCredentials" , "username" => "my_user_name" , "password" => "my_password"});
     my $a = $chrome->driver->send_message('Fetch.continueWithAuth' , %auth);
   });

@arahnale
I'm trying your code, and it should work from what I can tell, but the Fetch.authRequired just doesn't seem to trigger.  It only triggers the Fetch.requestPaused.  "Fetch pause" is all that is outputted with a proxy error in chromium. Any suggestions?
my $asd = $mechtwo->add_listener('Fetch.authRequired', sub {    my( $info ) = @_;    print "Fetch auth\n";    my $requestId = $info->{'params'}{'requestId'};    my %auth = (      'requestId' => $requestId ,      "authChallengeResponse" => {"response" => "ProvideCredentials" , "username" => "" , "password" => ""});      my $a = $mechtwo->target->send_message('Fetch.continueWithAuth' , %auth);    });  my $asdf = $mechtwo->add_listener('Fetch.requestPaused', sub {    my( $info ) = @_;    print "Fetch pause\n";    my $requestId = $info->{'params'}{'requestId'};   $mechtwo->target->send_message('Fetch.continueRequest' , 'requestId' => $requestId);  });


add-repo: remove package signatures from the DB files

random observation, if we'd drop pacman v5 support (2.5 years ago, 1% of non-CI users) we could remove package signatures from the package databases, which would cut the DB size roughly in half.
Maybe we could give it a try for just some repos  like clang32.
All databases combined are ~11.5MB atm.

This is the upstream commit/discussion: https://lists.archlinux.org/pipermail/pacman-dev/2020-September/024530.html
The patch is in pacman master, but not released. https://gitlab.archlinux.org/pacman/pacman/-/commit/fbb29b5047ff98ecb4fa41ab1e4ae7e9ed470866
Probably best if we wait for Arch to start doing it, so we are not the only users of that configuration.

It's a reduction of 75% even.

Looking at the recent logs, 60% of all pacman v5 accesses are to the old /i686 and /x86_64 symlinks, 30% is to msys. So 10% is to newer repos. With clang32 and clangarm64 basically nothing.

backported and installed on the server now: https://github.com/msys2/msys2-main-server/commit/92f8c61291df0332530b6dca1662530b77b41837
disabled for now except for staging: https://github.com/msys2/msys2-devtools/commit/426b6313ef56931f92a3c3295450c8ba87afb8be
Handle missing signatures in msys2-web: https://github.com/msys2/msys2-web/commit/4f5dad3f86aefcab8d06571b56969fb95694813c

https://packages.msys2.org/base/mingw-w64-jj is the first package where the signatures are missing for clang32 and clangarm64

I've moved over everything else except msys now. While according to the logs there are still users mixing those 3 year old packages and new ones this seems like a good point to get their attention: https://www.msys2.org/news/#2023-11-05-package-installation-issues-for-very-oldoutdated-installations
The fix is a simple pacman -Suy, while who knows what can break in the future if they continue to not update any msys packages (like certificate issues, or the recent win11 cygwin fork fix).
The next steps is to look at the logs in some months and see if there are any pacman v5 users left and decide then if we should also do the same for the msys repo.

Before the update v5 usage was at 1.01%, now at 0.79%. Also no complains so far.
Removing those remaining 300kb is probably not worth leaving those 1% stranded, so I consider this done.
We can revisit in a year or so, and see if v5 usage dropped.

The remaining signatures have been removed, except for those packages needed to get a pacman v5 installation up-to-date.
So this is completely done now.


request.headers() does not give all headers that are used when making the request

const browser = await puppeteer.launch();
const page = await browser.newPage();

page.on('request', async (request) => {
  await request.headers();
});

await page.goto('http://gajus.com');

just gives:
'upgrade-insecure-requests': '1',
'user-agent': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/79.0.3945.0 Safari/537.36',
'sec-fetch-user': '?1'

whereas the actual headers include additional headers such as: accept, accept-language and accept encoding.
Related:

https://github.com/puppeteer/puppeteer/issues/3436 (closed without a solution)

@gajus did you found the solution?

whereas the actual headers include additional headers

What do you mean with "actual headers"?

@christian-bromann he meant request.
When intercepting an HTTP call, only the above mentioned headers are contained in the Request object of the interceptor. However there are several other headers that chrome sends.

Even if this is not practicable to fix, it is at the very least a documentation bug in that the documentation says the headers are listed, not a random sub-set of the headers.

you can you it like and it will work
const response = await page.goto( websiteUrl, { waitUntil: 'networkidle2', timeout: gotoTimeout });

			// wait for cart selector
			//await page.waitForSelector( 'footer', { timeout: gotoTimeout });

			const headers = response.headers();
			console.log(headers);

@ashish200025 These are the response headers. We are talking about the request headers. Also the context is the interceptor, not the result of goto.

I have managed to capture extra request headers using some of the underlying CDP events which provide extra information to requests and responses. See here for some example code: https://stackoverflow.com/questions/47078655/missing-request-headers-in-puppeteer/62232903#62232903

whereas the actual headers include additional headers

What do you mean with "actual headers"?

Visit with puppeteer headless: https://www.whatismybrowser.com/detect/what-http-headers-is-my-browser-sending
Headers missing when I check puppeteer API,
ACCEPT
ACCEPT-ENCODING
CACHE-CONTROL
PRAGMA
UPGRADE-INSECURE-REQUESTS
Those are actual headers being sent from what I can tell which we cannot retrieve from the puppeteer API.

Any updates on this?

Any updates on this?

Workaround: create a CDP session and listen for network events: https://stackoverflow.com/a/62232903

Not stale

Not stale

not stale, still


Add token lib

Imported from Cpython.

@rezaghanbari
The build was unsuccessful, but it's not my fault (there is no error in my file).

yeah... from the CI log on https://travis-ci.org/github/grumpyhome/grumpy/jobs/739947996#L887-L899 looks like isort is trying to install some the Python 3.5+ code.
And Grumpy unfortunately still runs on Python 2.7 :shrug:

@alanjds So what do you want to do?

Yeah... I do not think that merging your PR can make anything break. Yet do not know where it helps.
Will merge it and hope for someone to have time to push forward the Python 2.7 -> 3.X migration described on https://github.com/grumpyhome/grumpy/issues/135


🐛 Handle empty bodies when fetching MSCs

Fix suggested by @callahad, tested and confirmed it works.
Signed-off-by: Alexandre Franke<EMAIL_ADDRESS>

Do we need a changelog entry for this? (Does this repo use towncrier?)


Add Stock Visual Enhancements from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of Nhawks17, to add Stock Visual Enhancements to CKAN.
Please direct questions about this pull request to Nhawks17.

This mod requires EVE, which requires #2553 to be merged first. It also recommends Scatterer for atmospheric effects and Kopernicus for Jool's rings.
There are two downloads available on the thread and GitHub:

SVE Overhaul - Which requires the development version of EVE.
SVE Release - Which requires the released version of EVE.

Both downloads, on GitHub, have 4 seperate .zip files each for low, medium, high and ultra resolutions. The KerbalStuff page only includes the SVE Release with medium resolution textures.
@Nhawks1717, is this correct? More info is helpfull.

Yes this is correct. The SVE Overhaul version does not need to be added to CKAN, only the release version. If possible It'd be awesome to have all of the resolutions that are on GitHub to be added to CKAN. I didn't see a way to add multiple zips on Kerbal Stuff :) If you need anymore information just let me know.

Adding all the resolutions will be possible. The same method will be used as we use for installing RSS Textures.

Awesome! Sounds good to me then :D


Extensions never be activated after granting workspace trust

VS Code Version:
Version: 1.58.0-insider
Commit: 3caebff71e514ece73b125468881d102e767ee4d
Date: 2021-06-24T05:14:29.975Z
Electron: 12.0.12
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0
OS Version: macOS Catalina 10.15.7

Steps to Reproduce:

Open a new workspace and make it untrusted by default. Then use "Manage workspace trust" to trust the workspace.
Observe the extensions state in extensions view. Those extensions without declaring support for workspace trust are still grayed out. And those that are supposed to be activated in trusted workspace are not activated either.

https://user-images.githubusercontent.com/14052197/123240499-f155ed00-d512-11eb-9d10-808432036872.mov
This issue only exists in latest insider, but works in the stable VS Code.

@testforstephen, issue should be fixed in the next Insiders build.

fwiw I still have this issue (or at least the specific version of it reported in https://github.com/microsoft/vscode/issues/127012) today, running what I believe should be a build with the fix:
Version: 1.58.0-insider (user setup)
Commit: 9056b400b527c562871093916081c3e6df2691dd
Date: 2021-07-03T07:56:10.923Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000

[2021-07-04 11:24:36.867] [exthost] [error] ProxyResolver#resolveProxy Canceled: Canceled
	at Object.i [as canceled] (c:\Users\david\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:5:1157)
	at u._remoteCall (c:\Users\david\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:88:12817)
	at Proxy._.<computed>.D.charCodeAt._.<computed> (c:\Users\david\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:88:9349)
	at D.resolveProxy (c:\Users\david\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:88:36547)
	at Object.resolveProxy (c:\Users\david\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:93:57068)
	at useProxySettings (c:\Users\david\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\node_modules.asar\vscode-proxy-agent\out\index.js:159:16)
	at c:\Users\david\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\node_modules.asar\vscode-proxy-agent\out\index.js:107:13
	at c:\Users\david\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\node_modules.asar\vscode-proxy-agent\out\index.js:335:13
	at processTicksAndRejections (internal/process/task_queues.js:93:5)

@dboreham, I am unable to reproduce the problem in the latest Insiders release.
Could you please share the steps that you are using when running into the issue? Thanks!

Hi, some testing reveals that the problem is only present in WSL2 and Container targets (it works ok against local Windows).
Reproduction:

Create an empty directory in WSL2.
Open a new VSCode window.
Select "Open folder in WSL2".
Pick the empty directory.
Click to trust the folder.
Install the "Scala Metala" VSCode extension.
Observe that the extension is disabled for mysterious reasons.

This setup worked prior to a recent VSCode insiders update, so I am assuming we're looking at a symptom of the same problem, although it's also possible something specific to the Scala extensions is causing a different problem with similar symptoms. I don't see anything terribly useful in the logs, just the same error pasted above.
Not working case (remote, WSL2):

Working (local, Windows):

Thanks @dboreham for the steps. I was able to reproduce the problem on my side, but I do not believe that this is necessarily related to workspace trust. I am able to reproduce the issue even after I have disable the workspace trust feature using the security.workspace.trust.enabled setting.
If you hover over the warning icon for the Scala (Metals) extension, it looks like the extension is disabled because it depends on an extension (Scala Syntax (official)) that is currently being disabled. If you hover over the information icon for the Scala Syntax (official) extension, it looks like the extension is disabled in WSL because it is already enabled locally. @sandy081, is there anything obvious that I am missing?

If you hover over the warning icon for the Scala (Metals) extension, it looks like the extension is disabled because it depends on an extension (Scala Syntax (official)) that is currently being disabled. If you hover over the information icon for the Scala Syntax (official) extension, it looks like the extension is disabled in WSL because it is already enabled locally. @sandy081, is there anything obvious that I am missing?

I did some testing with non-insiders VSCode. What I see there is that initially the scala syntax extension is also in the "installed globally so disabled" state, however a popup appears saying something like "metals needs scala extension, would you like it downloaded?". Click yes, and after some gears turning it appears to be working.

I'll file a bug against the metals project...

@lszomoru metals folks are saying this is a VSCode bug (and actively closing every bug filed for this issue, I discovered):
https://github.com/scalameta/metals-vscode/issues/613 and https://github.com/scalameta/metals-vscode/issues/605
I'll see if I can find any open issue in this project for this, or else open one.

however a popup appears saying something like "metals needs scala extension, would you like it downloaded?"

Can you please copy/paste this pop up?

however a popup appears saying something like "metals needs scala extension, would you like it downloaded?"

Can you please copy/paste this pop up?

This took a bit of work because you have to completely uninstall both extensions to get it back into the right state:

I tried again to see if I could get the popup to show in VSCode insiders by uninstalling, restarting. No luck.
I also compared the logs between the Insiders and regular VSCode cases, and I didn't see any significant difference there.
Log looks like this:
[2021-07-08 11:24:46.646] [remoteagent] [info] Installing extension: scalameta.metals
[2021-07-08 11:24:47.444] [remoteagent] [info] Installing extension: scala-lang.scala
[2021-07-08 11:24:47.478] [remoteagent] [info] Downloaded extension: scala-lang.scala /home/david/.vscode-server-insiders/data/CachedExtensionVSIXs/scala-lang.scala-0.5.3
[2021-07-08 11:24:47.503] [remoteagent] [info] Removed the extension from uninstalled list: scala-lang.scala
[2021-07-08 11:24:47.508] [remoteagent] [info] Extensions installed successfully: scala-lang.scala
[2021-07-08 11:24:47.542] [remoteagent] [info] Downloaded extension: scalameta.metals /home/david/.vscode-server-insiders/data/CachedExtensionVSIXs/scalameta.metals-1.10.6
[2021-07-08 11:24:47.565] [remoteagent] [info] Removed the extension from uninstalled list: scalameta.metals
[2021-07-08 11:24:47.570] [remoteagent] [info] Extensions installed successfully: scalameta.metals

This popup says that Scala (Metals) extension got activated but it's dependency Scala Syntax (official) extension is not enabled. This is an error coming from VS Code and ideally VS Code should not be activating the extension when its dependencies are not there.
We enhanced VS Code recently to fix this error by not enabling the extension when its dependencies are not enabled - https://github.com/microsoft/vscode/issues/122448. Thats why you do not see the prompt in insiders.
To know the root cause may I know why Scala Syntax (official) extension is disabled? You can check it by hovering on the extension.

To know the root cause may I know why Scala Syntax (official) extension is disabled? You can check it by hovering on the extension.

Hover over only says that it is disabled, not why.
I have a theory as to why, testing it now...

I have a theory as to why, testing it now...

Nope, it wasn't that. (I noticed another extension complain that it needed JDK11, while I had switched to JDK8 on WSL2 recently, but after reverting to JDK11 in WSL2 the scalametals extension problem remains).

Digging into this some more: it appears that VSCode disabling the scala-lang plugin for remote is expected behavior. That extension is defined as of kind UI: https://github.com/scala/vscode-scala-syntax/blob/99868aa9177f33b9bd7dce2ea0d1b25e37e6899c/package.json#L11
So the question is probably not why is scala-lang disabled, but why does VSCode think that it needs to be enabled remote as a dependency of scalametals?
Also btw I noticed that the problem has crept into non-insiders VSCode now. It updated, so perhaps that's the reason, or perhaps there is a bad state causing the problem that wasn't initially present when I first downloaded VSCode this morning.
Version: 1.58.0 (user setup)
Commit: 2d23c42a936db1c7b3b06f918cde29561cc47cd6
Date: 2021-07-08T06:54:55.083Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000

Update: I found another computer that had working VSCode Insiders with working scalametals extension.
Using this system, by updating VSCode, I confirmed that something breaks scalametals between the following versions (first one works, second one does not):
Version: 1.57.0-insider (user setup)
Commit: b4c1bd0a9b03c749ea011b06c6d2676c8091a70c
Date: 2021-06-09T11:49:36.076Z
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000

Version: 1.58.0-insider (user setup)
Commit: 2d23c42a936db1c7b3b06f918cde29561cc47cd6
Date: 2021-07-07T12:09:55.219Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000

Isn't the reason for the issue the fact the scala-syntax is a UI extension so it is on the local machine and Metals works on the remote one? It seems they are on different "machines", so VS Code might not be detecting scala-syntax on a remote machine, which is why it's disabling Metals there.
So essentially, this a false negative caused by https://github.com/microsoft/vscode/issues/122448 ?

Isn't the reason for the issue the fact the scala-syntax is a UI extension so it is on the local machine and Metals works on the remote one? It seems they are on different "machines", so VS Code might not be detecting scala-syntax on a remote machine, which is why it's disabling Metals there.
So essentially, this a false negative caused by #122448 ?

I wondered about that, and to test the theory went looking for other extensions that might follow the same pattern. I couldn't find an example in my fairly large set of installed extensions where a remote plugin depends on a UI plugin, but I did find an example of a UI plugin "disabled" remote:

It displays with the same status as the scala-lang extension:

Conversely, I wondered about this pair of extensions which you'd think would be similarly afflicted:

But it appears the Haskell syntax extension is different vs Scala in that it is remote-only, and shows as disabled local:

Adding the remote extension behavior in my settings.json fixed the issue for me
    "remote.extensionKind": {         "scala-lang.scala": [ "workspace" ]     }

It seems that the Haskell syntax extension doesn't declare extensionKind, so I would say that the theory holds. Remote workspace extensions should be allowed to depend on local UI ones.
This should most likely be fixed in VS Code, we can alternatively remove extensionKind from Scala extension, but that would be a workaround.

The long, good fix is fine for me because I reverted to VSCode 1.57 for the time being.

Adding the remote extension behavior in my settings.json fixed the issue for me
 "remote.extensionKind": { "scala-lang.scala": [ "workspace" ] }

Thanks, I'd seen that in the doc and wondered if it would help, but hadn't tried it.

Opened a new issue here: https://github.com/microsoft/vscode/issues/128375

@dboreham and @tgodzik Thanks for the provided info. It seems there is a change in the behaviour and let's discuss in the newly opened issue.


isDefault glob doesn't work

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.78.2
OS Version: win11 / same on WSL

Steps to Reproduce:

.vscode/tasks.json
There is my tasks.json in the repo (I also have some unrelated tasks in user tasks)
{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "echo filename",
      "command": "echo ${file}",
      "type": "shell",
      "args": [],
      "problemMatcher": [],
      "presentation": {
        "reveal": "always"
      },
      "group": {
        "isDefault": "**.txt",
        "kind": "build"
      },
    },
    {
      "label": "Encrypt current file by SOPS",
      "command": "sops --encrypt --in-place ${file}",
      "type": "shell",
      "args": [],
      "problemMatcher": [],
      "presentation": {
        "reveal": "always"
      },
      "group": {
        "isDefault": "**.sops",
        "kind": "build"
      },
    },
    {
      "label": "Run ansible-playbook on current file",
      "command": "ansible-playbook -i inventory.yaml ${file} --diff",
      "type": "shell",
      "args": [],
      "problemMatcher": [],
      "presentation": {
        "reveal": "always"
      },
      "group": {
        "isDefault": "**.yaml",
        "kind": "build"
      },
      "options": {
        "env": {
          "ANSIBLE_DEBUG": "0",
          "ANSIBLE_HOST_KEY_CHECKING": "False",
          "ANSIBLE_CONFIG": "${workspaceFolder}/ansible.cfg"
        }
      }
    },
  ]
}

user tasks.json:
...
        {
            "label": "dotnet build",
            "detail": "runs dotnet build",
            "command": "dotnet",
            "type": "process",
            "args": [
                "build",
                "--no-restore",
                "-nologo",
                "-maxCpuCount",
                "-nodeReuse:false",
                "-p:UseRazorBuildServer=false",
                "-p:UseSharedCompilation=false",
                "-p:EnableAnalyzer=false",
                "-p:EnableNETAnalyzers=false",
                "-p:GenerateFullPaths=true",
                "/clp:ForceNoAlign"
            ],
            "runOptions": {
                "instanceLimit": 1,
                "reevaluateOnRerun": false
            },
            "group": {
                "kind": "build",
                "isDefault": "**.cs"
            },
            "presentation": {
                "reveal": "always",
                "echo": false,
                "focus": false,
                "revealProblems": "never",
                "showReuseMessage": false,
                "clear": true,
                "panel": "shared",
                "group": "shared"
            },
            "problemMatcher": [],
            "options": {
                "cwd": "${workspaceFolder}",
                "env": {
                    "MSBUILDDISABLENODEREUSE": "1"
                }
            }
        }

Go to any file and try to run default build task via keyboard or command -> looks like no default task is configured. Something broken with groups + isDefault globs

https://github.com/microsoft/vscode/pull/141230

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks for creating this issue! To help narrow it down, please take the time to follow below steps. Thanks a lot and happy coding 🙏
Is the issue caused by an Extension?
Stop VS Code and from the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If it still reproduces, jump to the next chapter.
If you see it is an issue with the extension, please run the command Start Extension Bisect and follow the instructions to find the extension that is causing this issue.

Please report the issue to the extension causing this.
Is the issue caused by VS Code Core?
If the issue is not caused by an extension, it is maybe caused by your configuration. Try to run code --disable-extensions --user-data-dir <directory> where <directory> is an empty folder. This will ensure Code is starting with a fresh data directory, e.g. no specific settings and without any extensions running.
If it still reproduces, it was maybe fixed already in our nightly release. Please download from https://code.visualstudio.com/insiders/ and see if you can reproduce the issue.
Finally, to help us narrow down what change caused the issue, please run the following command to find the build. It will start previous releases of VS Code insiders to see where the regression was introduced:

npx --yes vscode-bisect@latest
follow the instructions until you found the offending build
report back the commit range in this issue

Thanks!

yep, isDefault glob works fine with code --disable-extensions, I will update the message when I find the extension which cause this.


Some remarks about the whole project

I read the documentation again and again and I have problems to get an overview:
What is a "product" (well its a Gemstone product download), what is a "project". What is a "projectSet" ? What are "templates" ? How can I add an own template stone database to the registry ?
And please:

be NOT git centric - I went again back to simple http directories to load my software packages produced by Jade
perhaps one should force the users to use their own git server and not depend on github.
do not think that an access to the internet is always possible when installing Gemstone
an installation should be possible from a simple template database
reduce the number of touched external repository to an absolute minimum (best: only one repository like github or own git server)
if you do caching, then please make possible to turn off ...

Marten

be NOT git centric - I went again back to simple http directories to load my software packages produced by Jade

That is your choice, but the days are numbered for the http sites used to store monticello repositories, so be aware that github and git is the future ...
With that said, it should be possible to add Monticello repository support GsDevKit_stones ... I will not add this feature but if you have the cycles to add Monticello support to GsDevKit_stones, please do so ...

perhaps one should force the users to use their own git server and not depend on github.

GsDevKit_stones supports http and ssh git repositories and noone is forcing you to use github ... internally we have our own git server and I have project sets that interact with our ssh git repositories...
During the tODE image creation process there are still some network repositories that are hit (those happen to be Monticello repositories) .. and it should be possible to customize the image creation scripts to avoid hitting the network ...
I have a long term goal to make it possible to create images without hitting the network .. but I have lots of long term goals and not enough cycles to address them in a timely fashion ...


Data-to-file translation layer

Converts a Clojure Map of raw information into a requested file format, such as HDF5, HDF5, XML, JSON, etc.
Unit Tests

This is also in-progress.


Tab completion

I did not try with python 3 but tab completion does not work with 2.7 once PR https://github.com/vors/jupyter-powershell/pull/1 is applied. Is this a known issue? How hard would it be to fix or add this feature?

Currently this is an initial proof-of-concept/prototype that doesn't support tab completion.
The good way to get tab-completion and other intelligence would be to incorporate @daviwil's work from https://github.com/PowerShell/PowerShellEditorServices


Bug: "NA" values listed as "nan"

When ezEML correctly estimates a column type to be Categorical and this column contains "NA" values and no "nan" values, "NA" is not listed as a code but "nan" is. My best guess is the software underlying this operation interprets "NA" values as "nan".

Fixed in release 2021-03-17


fix dockerfile pg version error

fix action https://github.com/tensorchord/pgvecto.rs/actions/runs/11679434558/job/32520511574

You can debug the CI by manually triggering the workflow in a temporary branch.

I got it.


suppress alerts/confirms?

Hi, is there a way to suppress javascript alerts and confirms on a loaded page?
I tried this
<WebView
       injectedJavaScriptBeforeContentLoaded={'window.confirm = function(){}; true;'}
       source={{ uri: 'https://mobo2apps.s3.amazonaws.com/webview_example.html' }}
 />

but apparently the JS in the source page gets run before my JS gets injected.

hi, still needing this :)

Any news?


Fix broken members panel in visual script editor

Fix #42984 - I'm not sure I understand why this happens, but attempting to call _update_members as a deferred seems to resolve that bug.

Thanks!

Cherry-picked for 3.2.4.


fix catalog link in readme

the catalog link is currently pointing to agent

@Theaxiom can you merge pls?


🥢 ERC20:  _givePermit2InfiniteAllowance: true

Description
uh, true?
Checklist
Ensure you completed all of the steps below before submitting your pull request:

[x] Ran forge fmt?
[x] Ran forge test?

Pull requests with an incomplete checklist will be thrown out.

@atarpara help me update the tests

based thx @atarpara

Updated test, but I do not favor this because it will increase gas by default. The Solady ERC20 already has the permit functionality. So very less people use permit2.

Most tokens will be used on L2 such that the convenience might be indeed worth the tradeoff. If we are shooting for hyperoptimization, then I would suggest we shuck off permit() and make it into an inheritable.

Hmm… good point. @atarpara
This extra gas is very concerning.
Let’s marinate on this for at least a week.

We can have both. For max compat.

Ok, we shall only consider the gas overhead in the transferFrom function.
With Permit2 enabled, it costs about 20 more gas. An extra 21000 gas for the approve transaction is 1000 times more than this overhead. Hence, on overall, we save more gas. @atarpara

I'll merge this when the Spearbit audit has been finalized.


AttributeError: module 'kraken.node_actions' has no attribute 'common_node_functions'

Hey guys, I am running into an issue when running a chaos test, do you know if this is related to a bug or something like that?
thanks in advance!
Traceback (most recent call last):
  File "run_kraken.py", line 15, in <module>
    import kraken.node_actions.common_node_functions as nodeaction
  File "/root/kraken/kraken/node_actions/common_node_functions.py", line 10, in <module>
    from kraken.node_actions.aws_node_scenarios import aws_node_scenarios
  File "/root/kraken/kraken/node_actions/aws_node_scenarios.py", line 6, in <module>
    import kraken.node_actions.common_node_functions as nodeaction
AttributeError: module 'kraken.node_actions' has no attribute 'common_node_functions'

@napoleon-diaz Thanks for reporting the issue, @obrienrobert mentioned about this issue recently and looks like we are hitting this only when using the containerized version of kraken vs standalone version seems to be working fine. We are actively working on fixing it. We will have a fix out soon. Thanks.

wow, that was fast! thanks a lot @chaitanyaenr !

@napoleon-diaz @obrienrobert  #107 should fix the issue. Here is the temporary image with the patch which can be used for testing: quay.io/chaitanyaenr/kraken:latest until the patch is in. Thanks.

thank you @chaitanyaenr, I tested the image and now I am getting the following
[ndiaz@LAPTOP-NDIAZ cp4saas-chaos-tester (SECCON-12198a)]$ ./chaos.sh --kraken-config scenarios/common/litmus/rbac.yml
Wed Jun 16 23:44:01 UTC 2021 [chaos.sh]: Creating chaos docker network.
bd52cc6cd5d55c3987d401cea28555118e31a87928358096a9c4b2d0e94f8f45
Wed Jun 16 23:44:02 UTC 2021 [chaos.sh]: Building kraken image...
Wed Jun 16 23:44:15 UTC 2021 [chaos.sh]: Finished building kraken image.
Wed Jun 16 23:44:15 UTC 2021 [chaos.sh]: Starting chaos-kraken container...
Wed Jun 16 23:44:18 UTC 2021 [chaos.sh]: Started chaos-kraken container.
Wed Jun 16 23:44:18 UTC 2021 [chaos.sh]: Following execution of chaos-kraken...
2021-06-16 23:44:18,834 [INFO] Starting kraken
 _              _
| | ___ __ __ _| | _____ _ __
| |/ / '__/ _` | |/ / _ \ '_ \
|   <| | | (_| |   <  __/ | | |
|_|\_\_|  \__,_|_|\_\___|_| |_|

Traceback (most recent call last):
  File "run_kraken.py", line 144, in <module>
    main(options.cfg)
  File "run_kraken.py", line 27, in main
    config = yaml.full_load(f)
  File "/usr/local/lib64/python3.6/site-packages/yaml/__init__.py", line 142, in full_load
    return load(stream, FullLoader)
  File "/usr/local/lib64/python3.6/site-packages/yaml/__init__.py", line 114, in load
    return loader.get_single_data()
  File "/usr/local/lib64/python3.6/site-packages/yaml/constructor.py", line 49, in get_single_data
    node = self.get_single_node()
  File "/usr/local/lib64/python3.6/site-packages/yaml/composer.py", line 43, in get_single_node
    event.start_mark)
yaml.composer.ComposerError: expected a single document in the stream
  in "config/config.yaml", line 2, column 1
but found another document
  in "config/config.yaml", line 11, column 1
Wed Jun 16 23:44:19 UTC 2021 [chaos.sh]: chaos-kraken finished.
Wed Jun 16 23:44:19 UTC 2021 [chaos.sh]: Inspecting chaos-kraken execution results...
Wed Jun 16 23:44:19 UTC 2021 [chaos.sh]: chaos-kraken exited with non-zero exit code. Presuming failures.
Wed Jun 16 23:44:19 UTC 2021 [chaos.sh]: One of more errors found after chaos-kraken execution.
Wed Jun 16 23:44:19 UTC 2021 [chaos.sh]: Exiting with error.
Wed Jun 16 23:44:19 UTC 2021 [chaos.sh]: Cleaning up chaos-cerberus container.
Wed Jun 16 23:44:20 UTC 2021 [chaos.sh]: Cleaning up chaos-kraken container.
Wed Jun 16 23:44:21 UTC 2021 [chaos.sh]: Cleaning up chaos network.

I am using a wrapper called chaos.sh, and I am trying a different scenario I am getting this error
[ndiaz@LAPTOP-NDIAZ cp4saas-chaos-tester (SECCON-12198a)]$ ./chaos.sh --kraken-config config/kraken/suites/uds/trigger_synthetics_udiendpoints_redis.yml
Wed Jun 16 23:49:29 UTC 2021 [chaos.sh]: Creating chaos docker network.
2577a944746bdf5dea8b7928862d0f73dffec56bc6ef603094f89d708b9cc132
Wed Jun 16 23:49:30 UTC 2021 [chaos.sh]: Building kraken image...
Wed Jun 16 23:49:36 UTC 2021 [chaos.sh]: Finished building kraken image.
Wed Jun 16 23:49:36 UTC 2021 [chaos.sh]: Starting chaos-kraken container...
Wed Jun 16 23:49:40 UTC 2021 [chaos.sh]: Started chaos-kraken container.
Wed Jun 16 23:49:40 UTC 2021 [chaos.sh]: Following execution of chaos-kraken...
2021-06-16 23:49:40,556 [INFO] Starting kraken
 _              _
| | ___ __ __ _| | _____ _ __
| |/ / '__/ _` | |/ / _ \ '_ \
|   <| | | (_| |   <  __/ | | |
|_|\_\_|  \__,_|_|\_\___|_| |_|

2021-06-16 23:49:40,574 [INFO] Initializing client to talk to the Kubernetes cluster
Traceback (most recent call last):
  File "run_kraken.py", line 144, in <module>
    main(options.cfg)
  File "run_kraken.py", line 45, in main
    kubecli.initialize_clients(kubeconfig_path)
  File "/root/kraken/kraken/kubernetes/client.py", line 15, in initialize_clients
    config.load_kube_config(kubeconfig_path)
  File "/usr/local/lib/python3.6/site-packages/kubernetes/config/kube_config.py", line 753, in load_kube_config
    persist_config=persist_config)
  File "/usr/local/lib/python3.6/site-packages/kubernetes/config/kube_config.py", line 711, in _get_kube_config_loader
    'Invalid kube-config file. '
kubernetes.config.config_exception.ConfigException: Invalid kube-config file. No configuration found.
Wed Jun 16 23:49:41 UTC 2021 [chaos.sh]: chaos-kraken finished.

Hi @napoleon-diaz, looks like the config is not read, we need to define the scenarios in the kraken config: https://github.com/cloud-bulldozer/kraken/blob/master/config/config.yaml#L6 and pass the config file for the run: https://github.com/cloud-bulldozer/kraken/blob/master/docs/installation.md#run.
So basically trigger_synthetics_udiendpoints_redis.yml needs be part of the scenarios:https://github.com/cloud-bulldozer/kraken/tree/master/scenarios after which we can tell kraken to load it here: https://github.com/cloud-bulldozer/kraken/blob/master/config/config.yaml. This should do it for the standalone version, we will need to mount it into the container in case of using containerized version for it be part of the container as the scenario is not part of the code base:
$ podman run --name=kraken --net=host -v <path_to_kubeconfig>:/root/.kube/config:Z -v <path_to_kraken_config>:/root/kraken/config/config.yaml:Z -v :/root/kraken/scenarios:Z -d quay.io/openshift-scale/kraken:latest.
Please feel free to let us know in case of any questions. Thanks.

Thanks, @chaitanyaenr, will do that.
thanks a lot for the info.


Vendor zstr instead of fetching it from Git at build time

This way, the strobealign sources are more self-contained and it should not be necessary to have internet access at build time.

Approved


AIX build is fails with Cannot run program "git"

[2023-02-12T12:05:48.240Z] Caused by: java.io.IOException: Cannot run program "git" (in directory "/home/jenkins/workspace/build-scripts/jobs/jdk17u/jdk17u-aix-ppc64-temurin"): error=0, Failed to exec spawn helper: pid: 14483504, exit value: 127
[2023-02-12T12:05:48.240Z] 	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143)
[2023-02-12T12:05:48.240Z] 	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
[2023-02-12T12:05:48.240Z] 	at hudson.Proc$LocalProc.<init>(Proc.java:254)
[2023-02-12T12:05:48.240Z] 	at hudson.Proc$LocalProc.<init>(Proc.java:223)
[2023-02-12T12:05:48.240Z] 	at hudson.Launcher$LocalLauncher.launch(Launcher.java:997)
[2023-02-12T12:05:48.240Z] 	at hudson.Launcher$ProcStarter.start(Launcher.java:509)
[2023-02-12T12:05:48.240Z] 	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2668)
[2023-02-12T12:05:48.240Z] 	... 15 more
[2023-02-12T12:05:48.240Z] Caused by: java.io.IOException: error=0, Failed to exec spawn helper: pid: 14483504, exit value: 127
[2023-02-12T12:05:48.240Z] 	at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
[2023-02-12T12:05:48.240Z] 	at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:314)
[2023-02-12T12:05:48.240Z] 	at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:244)
[2023-02-12T12:05:48.240Z] 	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
[2023-02-12T12:05:48.240Z] 	... 21 more

To make it easy for the infrastructure team to repeat and diagnose, please
answer the following questions:

test suite/name (e.g, BUILD_LIST, TARGET, CUSTOM_TARGET)?

a link into recent Test_ job on https://ci.adoptopenjdk.net which showed the failure

https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-aix-ppc64-temurin/194/

Is there an existing issue elsewhere covering this?

Which machine(s) does it work on? build-osuosl-aix71-ppc64-2 - see https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-aix-ppc64-temurin/189/

Which machine(s) does it fail on? build-osuosl-aix71-ppc64-1

Any other details:

See also https://github.com/adoptium/infrastructure/issues/2922 which is an issue relating to the other build system being down, so we currently have no AIX7.1 build capability.

The issue with Git has been resolved, an unusual caching error in jenkins, resulted in the agent not being able to write to its workspace. A complete disconnect and reconnect of the agent, has allowed the build to success on this node.
https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-aix-ppc64-temurin/200/


Video: Installing basic tools (English)

Make a video showing how to install the basic tools on a tablet. Basically, video this: https://docs.odk-x.org/basics-install/
We have this in Spanish already as well so can do something very similar: https://youtu.be/jrGSySKK9p8
Can do without sound or with audio narration (if with audio narration please check & fix the automatic captioning).
Context: ODK-X has started a youtube channel to share videos of how to do key tasks in ODK-X. Although these tasks are often explained in the documentation, we frequently get requests for videos and some things are easier to learn watching a video than reading documentation. We are working on getting videos in English & Spanish but also welcome contributions in other languages!

Can you please assign this to me?

@Leena1666 just assigned you, thanks, let us know any questions or share your video when ready!

sure, Thanks

Here's my video, will be glad to get any feedback on what I can improve! https://drive.google.com/drive/folders/1M43qRk9Mm1ev7S_KOjT2QFctxkOF5rQ9?usp=sharing

@Leena1666 thanks for working on this, looks great and I will upload to our YouTube next!


Add repository description

GitHub allows to add a repository Description and optional Website.

At least the description should be set so users know what they are looking at and possibly improve search results.
I can only edit them for my fork, so @jakerr will need to do this.

Went with
Chip-8 virtual machine library and UI built with the Rust programing language

for now. Feel free to recommend something better :)


Documenting how to use EvenPodsSpread feature

This PR serves as a placeholder now. Will add content later.
cc/ @bsalamat @ahg-g @alculquicondor
/sig scheduling
/milestone v1.16

@Huang-Wei I am the 1.16 Docs Shadow. We need this PR ready for review before Sep 3.

@bsalamat @ahg-g @alculquicondor The PR is ready for review. We will focus on the technical part. And after that, I will request an editorial review.

@alculquicondor Appreciate a lot for your review! Comments have been addressed.

/lgtm

@sftim Thanks a lot for the review. The comments have been addressed. PTAL.
for the review's convenience, I intentionally made the change of file renaming to a separate commit.

@sftim I've addressed most of your comments. Some of them were kept as is. Can you take another review? We may need a /lgtm by the end of today.
Thanks.

@Huang-Wei you can help reviewers by putting a link to https://deploy-preview-15514--kubernetes-io-vnext-staging.netlify.com/docs/concepts/workloads/pods/pod-topology-spread-constraints/#prerequisites in the PR description.
Informally (this isn't a tech review), it /lgtm
I still think it's worth tracking an issue to replace the ASCII-art style diagrams with SVG ones (and I'm fine with the idea of merging this now without those diagrams done).

/lgtm

@Huang-Wei I sent a PR against your branch: https://github.com/Huang-Wei/website/pull/1
This adds an optional inbound link to the new concept page.

Thanks @sftim . I've merged your commit.

/lgtm

/approve


Geographic Maps

Does altair / vega-lite plan to support plotting on geographic maps? Faceting maps would be extremely powerful for my research and I imagine for others as well. Thanks for a great project!
Cheers,
Joe

Hi Joe – mapping is not currently in vega-lite, though it is on the roadmap. In the meantime, you might check out vincent, though unless I'm mistaken that project is no longer supported.

I can confirm that geo-support for Vega-Lite is being actively worked on,
but we do not have a fixed release date yet. Thanks for the request!
On Tue, Aug 9, 2016 at 8:22 AM, Jake Vanderplas<EMAIL_ADDRESS>wrote:

Hi Joe – mapping is not currently in vega-lite, though it is on the
roadmap
https://github.com/vega/vega-lite/issues?q=is%3Aopen+is%3Aissue+milestone%3A"1.x+Maps".
In the meantime, you might check out vincent
https://vincent.readthedocs.io/en/latest/, though unless I'm mistaken
that project is no longer supported.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ellisonbg/altair/issues/170#issuecomment-238588527,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMYLzmAKMhk6d9grmbNpCjfF9qIPSylks5qeJtFgaJpZM4JgIKE
.

Fantastic! thanks @jakevdp and @jheer


[Infra] Enable tests now that GHA supports Xcode 14.3

#no-changelog

Expecting at least one failure related to using a modular import in an AppCheck public header.

Resolved convos and turned on auto-submit.

Worth leaving a kudos for not just fixing my AppCheck C++ compile error but doing the usually unsung Proper Software Engineering Work of making sure the testing rig repro'd it and then the fix actually fixed the automated tests etc. I already appreciate the permanent quality improvement :-)

Thanks @mikehardy! 🙂


about testing

I have already downed the "activitynet_iter_135000.caffemodel", but when I prepare to generate the prediction log file on the validation set, and run "./experiments/activitynet/test/script_test.sh" , some questions occured,it said "Waiting for ./experiments/activitynet/snapshot/activitynet_iter_135000.caffemodel to exist...", and trapped in a dead circle.  I can't understand this question, could you please explain it?
Thanks for your kindness!

Did you set the right path?
On Nov 30, 2018, at 20:13, WangChangjiang <notifications<EMAIL_ADDRESS>wrote:
I have already downed the "activitynet_iter_135000.caffemodel", but when I prepare to generate the prediction log file on the validation set, and run "./experiments/activitynet/test/script_test.sh" , some questions occured,it said "Waiting for ./experiments/activitynet/snapshot/activitynet_iter_135000.caffemodel to exist...", and trapped in a dead circle. I can't understand this question, could you please explain it?
Thanks for your kindness!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/VisionLearningGroup/R-C3D/issues/45, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFOa_wBfLKwXvNxESFFzG9vFtMyMb1dUks5u0gIDgaJpZM4Y8tH5.

I also have sloved this question. thank you. I am building for Python 3 and running from Python 3 , I want to know can I run this project properly?


Move course materials to "Tutorials" page for visibility

Checklist
GitHub

[X] I've given this PR a concise, self-descriptive, and meaningful title
[X] I've linked relevant issues in the PR body
[X] I've applied the relevant labels to this PR
[X] I've assigned a reviewer

PR contents

[ ] I've consulted SCT's internal developer documentation to ensure my contribution is in line with any relevant design decisions
[ ] I've added relevant tests for my contribution
[X] I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

Courses/tutorials cover mostly the same material (in-depth usage of command line scripts), so I thought to combine them.
Linked issues

Fixes #3231.

Looks good to me, makes it a lot clearer :) I would even maybe put Tutorials and Courses as is its own header, outside of User Section, so you would have 4 main level headers:
Overview
User Section
Tutorials and Courses
Developer Section

Thanks for the kind words! :)

I would even maybe put Tutorials and Courses as is its own header, outside of User Section, so you would have 4 main level headers:
Overview
User Section
Tutorials and Courses
Developer Section

Just to clarify, what would the subpages be? Perhaps each of the subgroups would have its own page? e.g.
Overview
    Introduction
    Overview
    SCT Concepts
    References

User section
    Installation
    Getting Started
    Command-Line Tools
-   Tutorials
    Support

+ Tutorials and Courses
+   Courses
+   Tutorial pages
+   Video tutorials

Developer section
    Contributing to SCT
    Python API
    Changelog
    License

I wonder if there's enough material there to even have subpages, hrm. Maybe just the 1 page for now.

Thanks for the kind words! :)

I would even maybe put Tutorials and Courses as is its own header, outside of User Section, so you would have 4 main level headers:
Overview
User Section
Tutorials and Courses
Developer Section

Just to clarify, what would the subpages be? Perhaps each of the subgroups would have its own page? e.g.
Overview
    Introduction
    Overview
    SCT Concepts
    References

User section
    Installation
    Getting Started
    Command-Line Tools
-   Tutorials
    Support

+ Tutorials and Courses
+   Courses
+   Tutorial pages
+   Video tutorials

Developer section
    Contributing to SCT
    Python API
    Changelog
    License

I wonder if there's enough material there to even have subpages, hrm. Maybe just the 1 page for now.

Yah, exactly!


⚠ Bofrost.fr has degraded performance

In 5e0c462, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1267 ms

Resolved: Bofrost.fr performance has improved in 9e102fc.


Define in a single place constants used by the profiler code

For those constants that we currently don't allow customizing via the configuration, use something like internalConfig to define their values, as opposed to defining in various random places.
Filed from discussion in #20.

I don't feel this is actionable. Please re-open with more specific plan if it is.


Expected value of BLEU score and perplexity

Hi,
Can someone please tell what is the expected value of BLEU score and perplexity after running the nmt model for converting vi to en and vice versa.
Thanks in advance.

Could you also please tell on which dataset is the BLEU score of value greater than 20 obtained?
Thanks in advance.

note that English-Vietnamese parallel corpus of TED talks  contains only 133K sentence pairs.  For large scale you can use German-English parallel corpus (4.5M sentence pairs).

Okay thank you.
Apologies for a question again relating to my previous query,
Why the number of sentence pairs being less,  lower the value of BLEU score so much?
Could you please elaborate on this
Thanks in advance


Next PC not sampled when core wakes up from sleep in Verilator run

Scenario:

Core is halted which turns off clk
Core wakes up (i_cpu_run_req_d1 is asserted) and tlu_flush_path_r has next PC value
Clk is active 1 cycle after cpu_run_req_d1 is asserted
tlu_flush_path_r_d1 flop does not sample the next PC value on the first clk edge after core wakes up and remains at 0
The 0 value is propagated to mepc, core executes from instr 0 once again and the test goes in an infinite loop

Please use smoke_test_clk_gating to reproduce the issue in Verilator

@mgielda @kgugala - do either of you know if there is someone that owns/changes verilator code for issues like this?

@upadhyayulakiran can you point me to the code with the smoke_test_clk_gating test you are referring to?

@tmichalak, apologies for the late response. It looks like that test did not get merged yet. Same issue exists with this test:
src/integration/test_suites/smoke_test_cg_wdt
The test hangs and PC keeps going in a loop after core wakes up from halt.

When VEER is used in the Caliptra FPGA, we observe the same behavior. I cannot build the default TEC_RV_ICG defined in beh_lib.sv for FPGA and the USER_EC_RV_ICG I can get to work isn't identical logically. I am temporarily working around this by using free_l2clk as the clock signal for flush_lower_ff.


Minor issues with search

Hello,
First issue with issue happens on the demo page as well (https://fritz-c.github.io/react-sortable-tree/)
It's a bit difficult to explain, but if you search something that has more than 1 result, then move to the second or any other result that's not the first one, and then search again with only ONE key press with something that will yield only 1 result, the node is correctly found but the tree is not scrolled.
Example on the demo page:

Search for "Dep", and hit enter until you are on the "Depth: 5" node, the first search result "Limit nesting with ..." should be barely visible now.
Move to the beginning of the text input and type "x", you should have "xDep" now, you can see only 1 result is found now, and the node correctly highlighted but the tree isn't scrolled until you actually type something else.

Something very similar happens when you collapse all nodes, trying to search or move the search node to the next value won't automatically scroll the first time, you need to "move" twice in order for it to work. For example, search for "Dep", move until the 4th result and then collapse all, finally hit enter on the search text and the tree will expand again but it won't scroll to the matched node until you actually hit enter twice, this is an issue if you only have 1 result, since you have to delete and write again.

Hi, I'm having an issue with trying to set a initial search as well, not sure if it's related to this one.
In my case, I noticed that the componentWillReceiveProps is called after mounting for some reason, and
this.setState({ searchFocusTreeIndex: null })

resets the initial index that was found in search, which prevents the list from scrolling as desired. Are there any workaround for this? Is setting to null really necessary here?


How to get available printer list on iOS and how to do direct print on Android?

Hi.
I am using this plugin for iOS and android and I hope you help me with the following problems.

I can see that isAvailable() function returns an array for this on android but what about iOS?
I can't do direct print on Android. Is it impossible to do direct printing on Android?
I hope you would help me with these problems.
Thanks in advance.

This direct printing on Android is indeed a very important thing.
Any thoughts about this? Does anyone know an app, plugin or something that intercept the print dialog screen and jumps it over or just suppress it?


gtk: Add gnome_43 feature

Fixes #1156
This only adds the feature for GNOME 43, but I think going with the latest SDK version is fine.
Of course, new features should be added as soon as newer GNOME versions become available.

Looks good :+1:


4.x beta 6 override service body cofnig for twilio webhooks not working

Describe the bug
overide service body config setting not working.
What version are you running?
4.0 beta 6
Did this happen on prior versions to the one you are running?
no
To Reproduce
set your twilio webhook to use a service body config and alter those settings, the stalk config is still used
Expected behavior
respects the config settings

for the vineyard my hooks are set to ?override_service_body_id=8


test framework for helm chart

more and more changes on help comein, need a new mechanism to avoid things like like https://github.com/envoyproxy/gateway/pull/2371.

fixed by https://github.com/envoyproxy/gateway/pull/2935


Bounce Deletion Call Change

Added: {% info %} Please note, when you are completing the following requests they should not be combined. For example, if requesting to delete one address, it is not necessary to add the "delete_all=false" parameter in an effort to prevent deletion of further blocks, it is assumed. {% endinfo %}
(Previously added to the Blocks API deletion documentation as well)
Description of the change: ^^
Reason for the change: Users have tried using both together in "Try it now" and get an error. Only one or the other can be used.
Link to original source: https://sendgrid.com/docs/API_Reference/Web_API_v3/bounces.html#Delete-bounces-DELETE

Closes #

Hello @kelseyenglish,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

you made some awesome PRs today. Thanks for all of this!!


Outputting files as another user (www-data)

I'm using the vaapi enabled docker via node.js spawn shell, it's working perfectly with HW acceleration.
However the output encoded files are output as root:root, and so I cannot continue modifying the output with other applications that are running as www-data:www-data instead of root.
Upon using the user option the vaapi docker loses the privilege to access the vaapi device, here's the terminal log
docker run --device /dev/dri:/dev/dri -v /home/autoingest/:/autoingest --user 33:33 jrottenberg/ffmpeg:4.0-vaapi  -stats -vaapi_device /dev/dri/renderD128 -hwaccel vaapi -hwaccel_output_format vaapi -hide_banner -t 30 -i "/autoingest/films/source.mov"  -y -filter_complex 'format=nv12|vaapi.....
[AVHWDeviceContext @ 0x55b407756400] No VA display found for device: /dev/dri/renderD128.
Device creation failed: -22.
Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Invalid argument
Error parsing global options: Invalid argument

Is there any other way I can force ffmpeg to output as a specific user?

@jrottenberg I tried adding --cap-add=SYS_ADMIN like you suggested, I tried adding both --cap-add=SYS_ADMIN and --cap-add= SYS_PTRACE like the Intel docs asked me to, and I tried --privileged=true.
None of them worked, I still have the same error
[AVHWDeviceContext @ 0x559ca5f18480] No VA display found for device: .
Device creation failed: -22.
[h264 @ 0x559ca5f28440] No device available for decoder: device type vaapi needed for codec h264.
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (h264_vaapi))
  Stream #0:1 -> #0:1 (eac3 (native) -> aac (native))
Device setup failed for decoder on input stream #0:0 : Invalid argument

What now?

It's likely a permission issue on the device.
I should preface that I'm using my own Dockerfile with libmfx (no vaapi), but I had a similar problem, which I solved by adding - inside the container, so in the Dockerfile - the user to the group owning the device:
RUN groupadd -g ${PGID} ffmpeg \
 && groupadd -g ${render_gid} render \
 && useradd -u ${PUID} -g ffmpeg -G video,render ffmpeg

where render_gid is the group id owning the render device on the host (likely /dev/dri/renderD128):
render_gid=$(stat -c '%g' /dev/dri/renderD128)

Then you can just docker run --user ${PUID} --device ..., no need for --privileged or --cap-add.
Note that you shouldn't pass a group id to docker run, or it'll override the other group(s) defined in the Dockerfile and you'll get the same issue again.
Hope this helps.


support batch2 unet models, introduce the notion of a 'unet subdir'

1. Our HF repos are usually arranged as a 'base' folder (containing vae, text encoder models, etc.), and
 subfolders that store the unet model collateral. For example, 'FP16' and 'INT8'. This change-set adds the
 ability to set both the 'base' directory, and optionally the 'subdir' to find the unet model. If the subdir
 isn't set, then it will fall back to the old behavior and look for the unet model (and other related collateral)
 in the 'base' model folder.

2. Add a new 'batch2' specific unet loop class to support batch2 unet models.
3. Update all of the cmdline samples, and Windows documentation to reflect the new subdir feature.

Tested on both Windows & Linux.


Fails on numbers below 1k

Hi @FractalMachinist, what idea do you have in mind for numbers below 1,000?

I realize I was really unclear, my apologies. I'd imagined 999 -> "999",
and 1000 -> "1k". Right now (in my admittedly brief tests), numbers below
1k throw an error.
On Mon, Nov 14, 2022 at 6:13 AM JoshX @.***> wrote:

Hi @FractalMachinist https://github.com/FractalMachinist, what idea do
you have in mind for numbers below 1,000?
—
Reply to this email directly, view it on GitHub
https://github.com/JCalmCrasher/number-js-formatter/issues/1#issuecomment-1313516623,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANRXTS7CQNHUSD2PSKB3O7TWIINF5ANCNFSM6AAAAAAR53PB3A
.
You are receiving this because you were mentioned.Message ID:
@.***>

I realize I was really unclear, my apologies. I'd imagined 999 -> "999", and 1000 -> "1k". Right now (in my admittedly brief tests), numbers below 1k throw an error. EDIT: The specific error: friendlyFormat(999) Uncaught TypeError: Cannot read property '0' of undefined at friendlyFormat (/workspaces/cellarium/node_modules/number-js-formatter/dist/src/friendly-format.js:56:21)

Not an issue, thanks for that.
You mind making a PR for it?

Sure, it'll be a few days.
On Sat, Nov 26, 2022 at 4:27 PM JoshX @.***> wrote:

I realize I was really unclear, my apologies. I'd imagined 999 -> "999",
and 1000 -> "1k". Right now (in my admittedly brief tests), numbers below
1k throw an error. EDIT: The specific error: friendlyFormat(999) Uncaught
TypeError: Cannot read property '0' of undefined at friendlyFormat
(/workspaces/cellarium/node_modules/number-js-formatter/dist/src/friendly-format.js:56:21)
Not an issue, thanks for that.
You mind making a PR for it?
—
Reply to this email directly, view it on GitHub
https://github.com/JCalmCrasher/number-js-formatter/issues/1#issuecomment-1328117223,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANRXTS54N35SSL74YQJ7XTLWKJ6ENANCNFSM6AAAAAAR53PB3A
.
You are receiving this because you were mentioned.Message ID:
@.***>


Different objects with the same arguments

I have noticed a regularity: if you try to return in the function the object which is an argument of that function, than each time a new object returns (although the argument hasn't changed regarding the library's work).
const aFunction = (state) => Math.random();
const memoFunc = memoize(aFunction);
const result1 = memoFunc({a: 1, b: 2});
const result2 = memoFunc({a: 1, b: 2});
console.log(Object.is(result1, result2)) // true

const aFunction = (state) => state;
const memoFunc = memoize(aFunction);
const result1 = memoFunc({a: 1, b: 2});
const result2 = memoFunc({a: 1, b: 2});
console.log(Object.is(result1, result2)) // false?..

Even if the object is inside another object:
const aFunction = (state) =>({n: Math.random()});
const memoFunc = memoize(aFunction);
const result1 = memoFunc({a: 1, b: 2});
const result2 = memoFunc({a: 1, b: 2});
console.log(Object.is(result1, result2) && Object.is(result1.n, result2.n)) // true

const aFunction = (state) =>({n: Math.random(), data: state});
const memoFunc = memoize(aFunction);
const result1 = memoFunc({a: 1, b: 2});
const result2 = memoFunc({a: 1, b: 2});
console.log(Object.is(result1, result2) && Object.is(result1.n, result2.n)) // false?..

Is it bug or a feature?

That's a feature. You are returning a reference to an input value, declaring that you need that object, and thus it would be added to a dependencies list.
As long as dependency changes (a new value provided) - cache is dropped.
How to "fix"
const aFunction = (state) => ({...state});

return a copy of the object. Like "I dont need the object, I need only values inside it". Does not work for nested objects :)

But the main idea of memoization - storing the results of function call and return them with a same input values.
In the examples we see that the results are not storing. The function returns different values for the same inputs.
If the function has same value in input, it must return exactly the same value. It should not depend on a dependencies list and others. This is the meaning of memoization.
Reference comparison is very important in frameworks, it is used for optimise update (React.memo and onPush strategy in Angular).

Not exactly
const obj = {
 a: 1,
};
const result = useMemo(() => obj, []); // eslint: Hey, missing dependency
const result = useMemo(() => obj, [obj]); // eslint: ok
const result = useMemo(() => obj, [obj.a]); // eslint: ok

memoizestate creates dependenct list in runtime
useMemo(() => obj.a, [obj.a]) === memoizestate( state => state.a);
useMemo(() => obj, [obj]) === memoizestate( state => state);

While with useMemo you can use not quite real dependency list, memoizestate would always buld the true one.

Dependency is something you are using inside the function. Or something you are returning from the function.

Once again - let's check your example
const aFunction = (state) =>({n: 42, data: state});
const memoFunc = memoize(aFunction);
// why it is working that way
const result1 = memoFunc({a: 1, b: 2}); // {n: 42, data:state}
const result2 = memoFunc({a: 1, b: 2}); // {n: 42, data:state}

// but here it would be ok?
const result1 = memoFunc(5); // {n: 42, data:5}
const result2 = memoFunc(6); // {n: 42, data:6}

state is a new object every call, thus bypasses memoization.

state is a new object every call
No. According to the description of your library the object should be treated as the same.
And examples confirm this:

const aFunction = (state) => Math.random();
const memoFunc = memoize(aFunction);
const firstObject = {a: 1, b: 2};
const secondObject = {a: 1, b: 2};
const result1 = memoFunc(firstObject);
const result2 = memoFunc(secondObject);
console.log(Object.is(result1, result2))
// if the result is stored than the firstObject
// and the secondObject are the same object, right?

Your problem is that for one case the objects are considered the same, and for the second they are different.
And it should not depend on the implementation of the React hooks.

You don't get the point - the object should be treated as the same until they are become a part of a result. That's working ok if the original state is immutable - there would be no "unexpected" new objects.

👍 generate a derived data from incoming object.
👎 dont derive data, but return it as is.

I could make this behaviour configurable - that's a one line fix - if you need this behavior, but I would have to ask you - what do you actually need.
To be more concrete - on data return memoizestate is going thought returned information, and removing proxies if they exists, and detecting using the part of the original object as a side effect.
I could not track that usage, or I might not remove proxies, thus not stoping "observing" that you do actually looking for inside the data.

Can you give examples, how I can get "unexpected" new objects if I will be receive same object in a  state => state function (if the object should be treated as the same always, even if it is part of the result)?

Structural sharing which is base layer for immutable structures means that if object updated - it is updated, and if you are passing a new object - that's a new object.
However this library is solving exactly this problem - when change in underlaying state mutates all the parents, and that change might be ignored.
But not always:
const map = new Map();
const key1 = {a:1};
map.set(key1, 1);

const aFunction = (state) => state;
const memoFunc = memoize(aFunction);

const memoKey1 = memoFunc(key1);
expect(map.get(memoKey1)).toBe(1);

const key2 = {a:1}; // the same shape!
map.set(key2, 2);
const memoKey2 = memoFunc(key2);
expect(map.get(memoKey2)).toBe(2); // it is expected

more if it - if you are not assessing any properly it yet again will think that you need "all of it"
const aFunction = (state) => ({ x: state.a }); // would update ONLY when .a updated
const aFunction = (state) => ({ x: state.a, state }); // when .a, AND state updated
const aFunction = (state) => ({ x: 42, state }); // only state
const aFunction = (state) => (state); // only state

So, let's start everything from the beginning - what is the case you are trying to solve? I've written 4 memoization libraries, and might be you need "not this one".

And I am confused by the logic of working with objects in arguments.
I pass different objects (both by content and by reference), but memoizestate assumes that they are the same.
const aFunction = (state) => Math.random()
const memoFunc = memoize(aFunction);
const result1 = memoFunc({a: 1, b: 2});
const result2 = memoFunc({});
console.log(Object.is(result1, result2)) // true?..

I am not sure I have tests for zero-usage cases, so for me it would be not only an undefined behavior, but also a useless one.
Once again - the idea of the library is about automatical key usage tracking, or to be concrete - tracking of parts the calculation process depends on or the result was formed from.


background-color breaks Parallax

I'm trying to use Parallax on my landing page while having a sticky footer; however, I have light grey background and the sticky footer fills up the remaining space with white. In order to match this, I added light grey background-color to <main> but this breaks parallax.

Can you post a codepen?

Of course :)
https://jsfiddle.net/OminStyle/5hrpcp1j/

The issue I think is with your flexbox styles

The styles are from http://materializecss.com/footer.html.

This still is an issue. Anyone have a fix?

I can't seem to reproduce it. I close this issue for now. If anyone post a codepen that can reproduce the issue we can reopen.

I just ran into this issue. We had background-color set for html, body and main. Turns out, if you set a background colour on both html and body, it doesn't show properly: https://codepen.io/Xandaros/pen/MWYwRYy
Funnily enough, this seems to only affect the first parallax on the page. Took me absolute ages to debug.
Setting it on either html or body, but not both, also causes no issues.

I also had this issue, but for all .parallax-container divs instead of just the first. I tried applying the background color classes to various things per this thread without success. The fix for me was changing the z-index of the .parallax-container because the background image of the .parallax-container was being shifted behind the parent div somehow. I hope this helps someone in the future.


Parcel 2 support

Does this plugin work with Parcel 2? No report.html is generated for me after switching Parcel from v1 to v2. Thanks!

This is already implemented as a core plugin in Parcel 2 - invoking with the env variable PARCEL_BUNDLE_ANALYZER=1 set should create a folder "parcel-bundle-reports".
https://github.com/parcel-bundler/parcel/blob/v2/packages/reporters/bundle-analyzer/src/BundleAnalyzerReporter.js#L15


OmniSharp Failing on Windows

Hi,
I love the OmniSharp plugin so far. I just installed it of my OS X machine earlier today and it was working great! Unfortunately everything is a mess on my Windows machine. I am able to install the plugin, but I am not seeing the same options as I was on my OS X installation and OmniSharp will not run. Peeking into the Dev Tools console, I get the following messages:
getPackageDirPaths: d:\Users\John\.atom\packages
omni.ts:574 packagePath d:\Users\John\.atom\packages exists: true
index.js:52 Window load time: 3382ms
omnisharp-atom.ts:51 Activating omnisharp-atom solution tracking...
omnisharp-atom.ts:92 Getting features for "atom"...
/deep/ combinator is deprecated. See https://www.chromestatus.com/features/6750456638341120 for more details.
candidate-finder.ts:130 Omni Project Candidates: Searching d:\Users\John for global.json,*.sln
candidate-finder.ts:130 Omni Project Candidates: Searching d:\Users for global.json,*.sln
candidate-finder.ts:130 Omni Project Candidates: Searching d: for global.json,*.sln
D:\Users\John\AppData\Local\atom\app-1.6.0\resources\app.asar\src\text-editor-component.js:982 ::shadow pseudo-element is deprecated. See https://www.chromestatus.com/features/6750456638341120 for more details.
candidate-finder.ts:130 Omni Project Candidates: Searching d:\Users\John for project.json,*.csproj
candidate-finder.ts:130 Omni Project Candidates: Searching d:\Users for project.json,*.csproj
candidate-finder.ts:130 Omni Project Candidates: Searching d: for project.json,*.csproj
candidate-finder.ts:130 Omni Project Candidates: Searching d:\Users\John for *.csx
candidate-finder.ts:130 Omni Project Candidates: Searching d:\Users for *.csx
candidate-finder.ts:130 Omni Project Candidates: Searching d: for *.csx
candidate-finder.ts:91 Omni Project Candidates: Found d:\Users\John
solution-manager.ts:478 Uncaught (in promise) TypeError: _rxjs.Observable.fromArray is not a function(…)
omnisharp-atom.ts:99 Loading feature "atom/command-runner.js"...
omnisharp-atom.ts:99 Loading feature "atom/dock.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\omnisharp-atom.js:198 Loading feature "atom/feature-buttons.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\omnisharp-atom.js:198 Loading feature "atom/framework-selector.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\omnisharp-atom.js:198 Loading feature "atom/generator-aspnet.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\omnisharp-atom.js:198 Loading feature "atom/menu.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\omnisharp-atom.js:198 Loading feature "atom/server-information.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\omnisharp-atom.js:198 Loading feature "atom/settings-button.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\omnisharp-atom.js:198 Loading feature "atom/solution-information.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\omnisharp-atom.js:198 Loading feature "atom/status-bar.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\omnisharp-atom.js:198 Loading feature "atom/update-projects.js"...
d:\Users\John\.atom\packages\omnisharp-atom\lib\server\omni.js:548 Uncaught (in promise) TypeError: _rxjs.Observable.fromArray is not a function(…)

Also, my settings show this:

My installation on OS X shows many more settings

Crazy, seems like one the dependencies didn't install correctly for some reason.  I do know that the rxjs team released a new beta, so it's possible that's interfering with things.  If that's the case I'll be able to fix it fairly easily.
Two possible options for a quick fix at the moment.

from a command prompt run...

apm uninstall omnisharp-atom
apm install omnisharp-atom

If there is an error there, that would be good to know on the ticket as well!

Assuming you have node and npm installed, if you open a command window you can try...

cd %userprofile%\.atom\packages\omnisharp-atom
npm install

It appears I have everything working now. What I had to do was copy this repository into my packages directory and run npm install off of that. Thanks for your help 🙂


chore: Schedule the build at 1.30 AM

Motivation:
Streamling the build.

Is there a reason why this isn't 01:00?

@mdedetrich I just checked the publish in pekko, it took 1h5m.