When the number of producers is greater than or equal to the number of cpu cores, the performance will be greatly reduced

Hello，thank for your work。When the number of producers is bigger than or equal to the number of cpu cores, the performance will be greatly reduced。
My test machine cpu has 4 cores.
If I set buffSize = 64, msgNum = 10_000_000, producerNum = 2, it consumes 972 ms.
But if I set producerNum = 4, it consumes over 20000ms, much worse than crossbeam.
Could you please tell me what cause this? Thansk very much!!!
My code is as below:
use std::sync::{Arc, Mutex};
use std::sync::atomic::{AtomicI64, Ordering};
use std::{env, thread};
use std::time::Instant;
use disruptor::*;

// The event on the ring buffer.
struct Event {
    price: i64,
}

impl Event {
    fn set(&mut self, price: i64) {
        self.price = price;
    }
    fn get(&mut self) -> i64 {
        self.price
    }
}

fn main() {
    let mut size = 64;
    let mut count = 10_000_000;
    let mut num_threads = 8;

    let args: Vec<String> = env::args().collect();
    if args.len()>1 {
        size = args[1].parse::<i64>().unwrap();
        num_threads = args[2].parse::<i64>().unwrap();
        if args.len() > 3 {
            count = args[3].parse::<i64>().unwrap();
        }
    }
    println!("size: {}, count: {}, num_threads: {}", size, count, num_threads);
    let factory = || { Event { price: 0 }};

    // let sink = Arc::new(AtomicI64::new(0)); //bcos we read and print value from main thread
    // Consumer
    let processor = {
        // let sink = Arc::clone(&sink);
        move |event: &Event, _sequence: i64, _end_of_batch: bool| {
            // sink.fetch_add(event.price, Ordering::Release);
            // println!("thread id: {:?}", thread::current().id());

        }
    };

    let mut producer1 =
        disruptor::build_multi_producer(size as usize, factory, BusySpin)
            .handle_events_with(processor.clone())
            .build();

    // Create another producer.

    let mut producers: Vec<_> = (0..num_threads-1).map(|_| producer1.clone()).collect();

    let start_time = Instant::now();
    // Publish into the Disruptor.
    thread::scope(|s| {
        s.spawn(move || {
            for i in 0..count {
                producer1.publish(|e| {
                    // println!("thread id: {:?}", thread::current().id());
                    e.set(1);
                });
            }
        });
        for producer in producers.iter_mut() {
            s.spawn(move || {
                for i in 0..count {
                    producer.publish(|e| {
                        // println!("thread id: {:?}", thread::current().id());
                        e.set(1);
                    });
                }
            });
        }
    });

    // Wait for the producers to finish.

    // Get the final sum.
    // let final_sum = sum.lock().unwrap();
    let d = Instant::now().duration_since(start_time);
    let delta = d.as_millis();
    // let res = sink.load(Ordering::Acquire);
    println!("Sum: {}, processed time: {}", 0, delta);
}

The problem is that your machine has too few CPU cores compared to how may threads you spawn.
In your example, you spawn 5 producer threads and one consumer thread (the ladder is done by the Disruptor).
When you have more threads than cores, the threads have to be context-switched during execution to allow all threads to make progress. That generates a lot of overhead. That's why you're seeing much slower execution in your example.
You haven't posted your Crossbeam code so I'm not sure if you also spawn 6 threads in that code? How are you comparing the two libraries?

I should add that the difference is also that the consumer thread in the Disruptor is busy-spinning while it waits for events. I.e. it fully occupies a core which a receiver in Crossbeam does not. So Crossbeam performs better in the case where you have more threads than cores - but then it's not a low latency scenario which is what the Disruptor is designed for.
Does it make sense?
Kind regards
Nicholas

The problem is that your machine has too few CPU cores compared to how may threads you spawn. In your example, you spawn 5 producer threads and one consumer thread (the ladder is done by the Disruptor).
When you have more threads than cores, the threads have to be context-switched during execution to allow all threads to make progress. That generates a lot of overhead. That's why you're seeing much slower execution in your example.
You haven't posted your Crossbeam code so I'm not sure if you also spawn 6 threads in that code? How are you comparing the two libraries?

First of all, thank you for your answer.
According to what you said, when using rust-disruptor, the number of threads needs to be controlled to be less than the number of cpu cores. When I use rust-crossbeam and java-disruptor(with BusySpin), there is no such limitation. They will not cause exponential performance decay because the number of threads exceeds the number of cpu cores.
Here are my comparison results:
Setting 1 (buff_size=256, producer_num=2, msg_num_per_producer=10_000_000):
java-disruptor: 3875ms
rust-crossbeam: 1820ms
rust-disruptor: It took more than 2 minutes so I stopped the program.
Setting 2 (buff_size=256, producer_num=4, msg_num_per_producer=10_000_000):
java-disruptor: 1620ms
rust-crossbeam: 788ms
rust-disruptor: 761ms
I wonder if your code design requires the number of threads to be less than the number of cpu cores to achieve ideal performance.
Here are my other two codes:
import com.lmax.disruptor.BusySpinWaitStrategy;
import com.lmax.disruptor.EventHandler;
import com.lmax.disruptor.RingBuffer;
import com.lmax.disruptor.dsl.Disruptor;
import com.lmax.disruptor.dsl.ProducerType;
import com.lmax.disruptor.util.DaemonThreadFactory;

import java.util.ArrayList;
import java.util.List;
import java.util.concurrent.atomic.AtomicLong;

class Event {
    private int value;
    public int get() {
        return value;
    }
    public void set(int value) {
        this.value = value;
    }
}

class Task implements EventHandler<Event> {
    AtomicLong consume_num = new AtomicLong(0);
    private Disruptor<Event> disruptor;
    private RingBuffer<Event> buffer;

    public Task(int bufSize) {
        this.disruptor = new Disruptor<>(Event::new, bufSize, DaemonThreadFactory.INSTANCE,
                ProducerType.MULTI, new BusySpinWaitStrategy());
        this.buffer = disruptor.getRingBuffer();
        this.disruptor.handleEventsWith(this);
        this.disruptor.start();
    }

    public boolean emit() {
        final long sequence = buffer.next();
        final Event event = buffer.get(sequence);
        event.set(1);
        buffer.publish(sequence);
        return true;
    }

    @Override
    public void onEvent(Event event, long l, boolean b) throws Exception {
//        this.consume_num.getAndAdd(event.get());
    }
}

class ProducerThread extends Thread {
    long msg_num = 0;
    Task task;
    public ProducerThread(Task task, long msg_num) {
        this.task = task;
        this.msg_num = msg_num;
    }
    @Override
    public void run() {
        for (long i = 0; i < msg_num; i++){
            task.emit();
        }
    }
}

public class Disruptor3P1CDemo {
    public static void main(String[] args) throws Exception
    {
        int bufSize = 512;
        int num_threads = 2;
        long num_msg = 10_000_000;

        if (args.length > 0) {
            bufSize = Integer.parseInt(args[0]);
            num_threads = Integer.parseInt(args[1]);
        }

        Task task = new Task(bufSize);
        List<ProducerThread> producerThreads = new ArrayList<>();
        for (int i = 0; i < num_threads; i++) {
            ProducerThread producerThread = new ProducerThread(task, num_msg);
            producerThread.start();
            producerThreads.add(producerThread);
        }
        for( ProducerThread producerThread : producerThreads){
            producerThread.join();
        }
        producerThreads.clear();
        long st = System.currentTimeMillis();
//        List<ProducerThread> producerThreads = new ArrayList<>();
        for (int i = 0; i < num_threads; i++) {
            ProducerThread producerThread = new ProducerThread(task, num_msg);
            producerThread.start();
            producerThreads.add(producerThread);
        }
        for( ProducerThread producerThread : producerThreads){
            producerThread.join();
        }
        long et = System.currentTimeMillis();
        System.out.println(String.format("Sum: %s, Process time: %s", task.consume_num, (et - st)));
    }
}

use crossbeam::channel::*;
use std::{env, thread};
use std::time::Instant;

fn main() {
    let mut buf_size = 8192;
    let mut num_threads = 8;
    let mut producer_msg_no = 10_000_000;

    let args: Vec<String> = env::args().collect();
    if args.len() > 1 {
        buf_size = args[1].parse::<i64>().unwrap();
        num_threads = args[2].parse::<i64>().unwrap();
        if args.len() > 3 {
            producer_msg_no = args[3].parse::<i64>().unwrap();
        }
    }

    let (s, r) = bounded(buf_size as usize);

    let mut threads = Vec::new();
    let mut producers: Vec<_> = (0..num_threads - 1).map(|_| s.clone()).collect();

    let start_time = Instant::now();

    let t1 = thread::spawn(move || {
        for _ in 0..producer_msg_no {
            s.send(1).unwrap();
        }
    });

    for s_clone in producers {
        threads.push(thread::spawn(move || {
            for _ in 0..producer_msg_no {
                s_clone.send(1).unwrap();
            }
        }));
    }

    // 消费者线程，负责接收和处理生产者发送的消息
    let mut sum = 0;
    for msg in r {
        let tmp = msg;
        // sum += tmp;
    }

    let _ = t1.join();
    for thread in threads {
        let _ = thread.join();
    }

    let d = Instant::now().duration_since(start_time);
    let delta = d.as_millis();
    println!("Sum: {}, processed time: {}", sum, delta);
}

I can see that in both the Disruptor (Rust version) and Crossbeam examples, you have commented out code inside the receiving/consuming end. That can cause the compiler to perform dead-code removal so I'm not sure you're measuring what you intended.
I would recommend you try out the benchmark in benches/mpsc.rs with a the number of producers you're trying here.
That should measure everything in a comparative way so you can compare the two.
Also, to answer your question on the number of threads and cores for optimal performance of the Disruptor: Yes, there need to be enough available cores. If you need to use more producer threads than cores, you should use Crossbeam as you are trying to maximize throughput and not minimize latency.
Kind regards,
Nicholas

I can see that in both the Disruptor (Rust version) and Crossbeam examples, you have commented out code inside the receiving/consuming end. That can cause the compiler to perform dead-code removal so I'm not sure you're measuring what you intended. I would recommend you try out the benchmark in benches/mpsc.rs with a the number of producers you're trying here. That should measure everything in a comparative way so you can compare the two.
Also, to answer your question on the number of threads and cores for optimal performance of the Disruptor: Yes, there need to be enough available cores. If you need to use more producer threads than cores, you should use Crossbeam as you are trying to maximize throughput and not minimize latency.
Kind regards, Nicholas

Thanks for your reply!!!
After our testing, your tool outperforms others in most cases. We will do more testing to decide whether to use rust-disruptor or crossbeam.
Best wishes!!!


Trailhead Events no longer has events

The iCal URL was https://trailheadboise.org/events/?ical=1&tribe_display=list but it appears Trailhead started using a Google Calendar instead, which doesn't appear to be shared aside from a rendering through WP (Simple Calendar?) on the site here: https://trailheadboise.org/events/

Also:

This is still an issue as of Oct 13 2020, although at this point the only events listed are Trailhead office hours, which require you be a paying member, and cross-list events like Boise Startup Week, so perhaps not much is being missed.
As Josh points out, Trailhead also has Facebook https://www.facebook.com/trailheadboise/events but there's not much gemstate.io can do with that due to no API.
I do not see an EventBrite organizer ID they're using.
This will stay open to monitor.


early intra-hart --> early inter-hart

perhaps this was a typo?

Original looks correct to me.  The sentence is talking about store-load forwarding within a hart.

That's true -- i amended the pull request to remove the word 'other' also -- it seems to me that the first part of the sentence is saying that early intra-hart forwarding IS permitted, and the second part (should be) saying that early inter-hart forwarding IS NOT permitted. This makes sense to me because the property of multi-copy atomicity is about inter-hart behavior, i think. But i could be wrong -- sorry if i am incorrect.

Thanks @bshanks, you're right, it was meant to say "inter".  I think your latest proposed change (also removing "other") does a good job clarifying the text.


APKAM - client side changes for authenticate using apkam keypair

Is your feature request related to a problem? Please describe.
https://github.com/atsign-foundation/at_protocol/blob/trunk/decisions/2023-01-pkam-per-app-and-device.md
Describe the solution you'd like

changes while creating atchops instance to set apkam keypair
changes to places where auth is done to remote secondary using apkam keypair
any other client side changes based on the apkam spec

Describe alternatives you've considered
No response
Additional context
No response

Did not start in PR65, Will complete onboarding_cli changes and take this up.

onboarding_cli changes still in progress.carrying over

onboarding_cli changes still in progress.carrying over

No progress in PR67

Carrying over to PR68. Have to start with changes in at_client_mobile

at_client_mobile changes in progress.
https://github.com/atsign-foundation/at_client_sdk/tree/apkam_onboarding_changes

changes done in PR70

onboarding implementation in at_client_mobile done.
changes to at_onboarding_flutter to use new impl in at_client_mobile
onboarding test. atKeys file is not getting generated. Have to fix this bug
pending impl - authenticate and enroll methods in at_client_mobile

pending

replace the duplicate code with at_auth package once the package is ready

Closing this task and creating specific tasks for pending client side changes.

https://github.com/atsign-foundation/at_client_sdk/issues/1140
https://github.com/atsign-foundation/at_widgets/issues/750
https://github.com/atsign-foundation/at_client_sdk/issues/1141


Spring boot compatibility table?

Describe the bug
I am running:

spring-boot-starter-parent:2.3.11
spring-cloud-starter-contract-stub-runner:3.0.2

After writing a test with @AutoConfigureWireMock(port = 0), I am getting exception:
java.lang.NoClassDefFoundError: org/springframework/test/context/TestContextAnnotationUtils
	at org.springframework.cloud.contract.wiremock.WireMockTestExecutionListener.annotationMissing(WireMockTestExecutionListener.java:96) ~[spring-cloud-contract-wiremock-3.0.2.jar:3.0.2]

This is because spring boot 2.3.x is using only spring-test:jar:5.2.15.RELEASE whereas TestContextAnnotationUtils was introduced only from spring-test:jar:5.3.0
Do we have compatibility mentioned anywhere in the docs?
Happy to contribute in any way, please point me in the right direction

It's on the front page of the Spring Cloud homepage - https://spring.io/projects/spring-cloud . You have to use Boot 2.4 or 2.5

Silly me, I was looking at the reference docs! Thanks!


less than character in filename breaks git on windows

1. Why is this change necessary?
Because git on windows does not allow to check out the repsitory.
error: unable to create file changelog/_unreleased/2020-10-06-fix-systemconfigservice-on-mariabdb-<10.3.22.md: Invalid argument

2. What does this change do, exactly?
Just rename the file. I did not find any reference in the code to it, it's just the changelog, so I think it can be renamed without any problems - avoiding problems with git on windows.
3. Describe each step to reproduce the issue or behaviour.
Just try to checkout the repo in git on windows.
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[X] I have squashed any insignificant commits
[ ] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

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

hey @ThomasChr
thanks for your contribution!
anyway this issue was already fixed by a colleague in https://github.com/shopware/platform/commit/d89592f2190d1ce0d66decb31b5f16135c40dbba


32-core 16 GB Linux VM for linting

New bots running clang-tidy will benefit from a VM with more cores: https://github.com/flutter/engine/pull/31477
The macOS clang-tidy runs are coming in under budget, but the Linux runs are going over, so only Linux needs the beefier VMs.
/cc @godofredoc

@yusuf-goog can you please help us setting this up in the chrome configs?

@yusuf-goog is this something you have bandwidth for? If not, please assign to me

Proposed CL in https://chrome-internal-review.googlesource.com/c/infradata/config/+/4591714

@zanderso there's some comments in the CLs. To confirm, do we want a 32 core, 16 gb ram vm? This hasn't been used before in infra (usually builders are constrained by their memory). (See https://chrome-internal-review.googlesource.com/c/infradata/config/+/4592272)

Here's some of the options. Can you take a look and let me know what would best fit the workload? If needed, we can provision a custom machine as well
# Machine type - vCPUs, RAM GB
"c2-standard-60": (60, 240),
"c2d-standard-112": (112, 448),
"e2-highmem-8": (8, 64),
"e2-highmem-16": (16, 128),
"e2-standard-4": (4, 16),
"e2-standard-8": (8, 32),
"e2-standard-16": (16, 64),
"e2-standard-32": (32, 128),
"n1-standard-4": (4, 15),
"n1-standard-8": (8, 30),
"n1-standard-16": (16, 60),
"n1-standard-32": (32, 120),
"n1-standard-64": (64, 240),
"n1-highmem-8": (8, 52),
"n1-highmem-16": (16, 104),
"n1-highmem-32": (32, 208),
"n2-standard-8": (8, 32),
"n2-standard-16": (16, 64),
"n2-standard-32": (32, 128),
"n2-standard-64": (64, 256),
"n2-highmem-8": (8, 64),
"n2-highmem-16": (16, 128),
"n2-highmem-32": (32, 256),
"n2-highmem-64": (64, 512),
"n2d-standard-32": (32, 128),
"t2d-standard-60": (60, 240),

Decided on e2-standard-32 as that's the preferred choice internally
Updated CL in https://chrome-internal-review.googlesource.com/c/infradata/config/+/4597748

The bots are available. Next step is to add to the .ci.yaml a new platform to target these machines:
platform_properties:
  Linux_highmem:
    properties:
      cores: "32"
     # This should be a copy of Linux

Linux_highmem clang_tidy:
  # Same as before

Unassigning myself for the next oncall to pick up

Linux Clang Tidy builders have now a 20 execution time compared to the previous 45.


[fea] moe support

PR types

PR changes

Description

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.kebo01 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

有些代码看看能不能是不是参考我这个PR的修改：https://github.com/PaddlePaddle/PaddleNLP/pull/8511


fix(deps): upgrade undici from 5.28.2 to 5.28.3 due to CVE

Partial fix for #12031, "Vulnerabilities"
Motivation

After the Snyk failure for #12753, I also checked OpenSSF Scorecard's current vuln report and found this vuln too: https://github.com/nodejs/undici/security/advisories/GHSA-3787-6prv-h9w3
Modifications

update yarn.lock to bump undici

undici is a transitive dep, used by swagger-ui-react

swagger-ui-react -> swagger-client -> undici

Verification

Ran yarn after, no additional changes
Ran npx yarn-audit-fix && yarn deduplicate to check for more vulns and auto-update them (same as #12036), no others popped up

Same for plain yarn audit: 0 vulnerabilities found - Packages audited: 1488

Ran yarn again, no additional changes

Dependabot is still not updating these deps timely. I thought it might be the "weekly" schedule in the dependabot.yml, but apparently the schedule is entirely ignored for security updates anyway.
Something else is going on... I'm wondering if we have security updates disabled or something at the repo or org level? Or is dependabot just very slow / not have the most up-to-date info? A lot of these vulns were reported with GHSAs, so GitHub should have these available in their CVE DB for dependabot...

I'm wondering if we have security updates disabled or something at the repo or org level?

I think this is the case -- "Dependabot alerts" are not enabled, and those seem to be required for security updates

Cherry-picked into release-3.5 as 6d41e8cfa90940d570fe428e3e3fc039d77cd012


No release version

cant install extension : VS Code reports "No Release Version"
screenshot

Thanks for raising the issue. I've published v0.1.1 just now (no changes compared to 0.2.0)
Install from https://marketplace.visualstudio.com/items?itemName=lionello.terminal-open-with

thank you!
WordpressCenter.net https://www.wordpresscenter.net/
@ajaxStardust
-------- Original Message --------
Subject: Re: [lionello/terminal-open-with] No release version (Issue #1)
Date: Sun Apr 09 2023 19:03:52 GMT-0400 (Eastern Daylight Time)
From: "Lio李歐" @.>
To: "lionello/terminal-open-with" @.>
CC: "ajaxStardust" @.>, "Author" @.>
Thanks for raising the issue. I've published v0.1.1 just now (no changes compared to 0.2.0)
Install from https://marketplace.visualstudio.com/items?itemName=lionello.terminal-open-with https://marketplace.visualstudio.com/items?itemName=lionello.terminal-open-with
—
Reply to this email directly, view it on GitHub https://github.com/lionello/terminal-open-with/issues/1#issuecomment-1501232573 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AWO26CHUAS4GI7P7BYR6KDDXAM55PANCNFSM6AAAAAAWYJ6CFA .
You are receiving this because you authored the thread.Message ID: @.***>


Grammatical error in docs for reusable workflows

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
Reusing Workflows
What part(s) of the article would you like to see updated?
Under Access to reusable workflows, the line A reusable workflow can be used by another workflow if either of the following is true: references a list of three items. The logic in the source file attempts to use "either" when only two items are in the list, but "any" when there are more. This check doesn't account for private-actions being set.
Additional information
No response

@tvalenta Thank you for opening an issue and linking it to your PR! ✨


Per request timeout

Considering adding a timeout per add-on request (instead of just add-on loading).
The timeout should be larger then eval's (currently 60 seconds) for obvious reasons. (considering 120 seconds)
If the timeout is reached, PMS should either drop the request or kill the add-on entirely.
Killing the add-on is obviously safer, as it can safeguard against an infinite loop scenario, but problematic, as some add-ons may be bugged and simply not reply in some very specific scenarios, leading to them being killed without a good reason.
An alternative would be adding logic based on number of attempts, in which the request is stopped if the add-on reaches the timeout for the first 2 times it happens, and is killed if it happens a 3rd time.

This was done, currently killing add-ons if they fail to respond to a request within 120 seconds.
If this fails in any way, i will revisit the subject, otherwise i consider it a more then fair amount of time for a response.


Can't resolve a JS function node

This is the relevant snippet of my yml:
group: {
  cooldowns: [{
    aggressive: true,
    duration: 5e3,
    limit: 2
  }, {
    aggressive: true,
    duration: 2e4,
    limit: 20,
    sorter: !!js/function "msg => msg.channel.guild?.id ?? msg.channel.id"
  }]
}

I automatically load the yml using yml.load(await fs.readFile(filePath, "utf8")), and in other yml files I use !!js/regexp, which works as expected. I thought it might be some issue with a character in the function, but wrapping it in "s doesn't change anything. I'm using Node.js v14.4.0 and the library is v3.14.0. I'll put the error below:
YAMLException: cannot resolve a node with !<tag:yaml.org,2002:js/function> explicit tag at line 59, column 82:
     ... nel.guild?.id ?? msg.channel.id"
                                         ^
    at generateError (/../node_modules/js-yaml/lib/js-yaml/loader.js:167:10)
    at throwError (/../node_modules/js-yaml/lib/js-yaml/loader.js:173:9)
    at composeNode (/../node_modules/js-yaml/lib/js-yaml/loader.js:1426:9)
    at readFlowCollection (/../node_modules/js-yaml/lib/js-yaml/loader.js:746:7)
    at composeNode (/../node_modules/js-yaml/lib/js-yaml/loader.js:1360:11)
    at readFlowCollection (/../node_modules/js-yaml/lib/js-yaml/loader.js:735:5)
    at composeNode (/../node_modules/js-yaml/lib/js-yaml/loader.js:1360:11)
    at readFlowCollection (/../node_modules/js-yaml/lib/js-yaml/loader.js:746:7)
    at composeNode (/../node_modules/js-yaml/lib/js-yaml/loader.js:1360:11)
    at readBlockMapping (/../node_modules/js-yaml/lib/js-yaml/loader.js:1089:11)
    at composeNode (/../node_modules/js-yaml/lib/js-yaml/loader.js:1359:12)
    at readDocument (/../node_modules/js-yaml/lib/js-yaml/loader.js:1525:3)
    at loadDocuments (/../node_modules/js-yaml/lib/js-yaml/loader.js:1588:5)
    at Object.load (/../node_modules/js-yaml/lib/js-yaml/loader.js:1614:19)
    at loadData (file:///../services/data.js:131:23)
    at async file:///../src/index.js:47:3

Your sample can be reduced:
const text = '!!js/function "msg => msg.channel.guild?.id ?? msg.channel.id"';

console.log(require('js-yaml').load(text));

js-yaml uses esprima to validate fn body. I does not understands edge features syntax. es6 synax works as expected:
const text = '!!js/function "msg => (msg.channel.guild || {}).id || msg.channel.id"';

console.log(require('js-yaml').load(text));

I don't think this needs fix.

I does not understands edge features syntax.

Both nullish coalescing and optional chaining are stage 4 in ECMAScript, are supported in every major browser, and are supposed in Node.js 14. They aren't remotely "edge features", and missing support for them definitely needs a fix.

While it's bad idea in general to use functions in yaml, js-yaml is not for node 14 only.

I don't see how support of Node 10 and 12 is relevant here, there should be no problems with backwards compatibility here. Are you saying you also wouldn't add any syntax supported in Node 12 if it isn't supported in Node 10? Also, this error message seems very misleading if the problem is syntax and not the tag.

This may cause different work in different versions. That's not nice.
This package is stable, and i don't like idea to play with edge features in mainstream. If you wish to play with latest syntax - you can do your own schema, with prefered tag implementation.

Supporting node 14 syntax shouldn't cause problems for node 10 and 12 users. With that said, it seems like Esprima is outdated and provides no attempt at supporting multiple versions of ECMAScript. A different parser like Espree might be better to use, as it is up-to-date, stable, and supports multiple ECMAScript versions at once.

Supporting node 14 syntax shouldn't cause problems for node 10 and 12 users

It will, because will not load files, created for node 14 only. Yaml is about portability first, not about js support. As i said - you can create custom schema, or keep functions as strings, if you wish to use yaml as "programming language". But promoting such features to mainsream is not nice idea.

Are you saying there's no way to support Node 14 syntax in only Node 14, without affecting other versions? If so, then I would recommend checking out that parser I linked previously, it makes doing this easy. Also, I found another example of missing syntax, async interation.
yml.load("!!js/function 'async msgs => { for await (const msg of msgs.get()) {} }'");
``` This is valid syntax in Node 10, 12, and 14. Yet it appears to fail for the same reason as the Node 14 syntax.

Reasons are different. You may prepare PR like this if it's really needed.
But, as i said, here are no plans to support all js features in embedded JS tag. Replace it with your own, if you wish.

Possibly a bad example then, what about numeric seperators? They're supported in Node 12 and 14. Also, I see no reason not to support all stable JS features when there's no cost to portability. Could you explain where this cost is a bit more?
yml.load("!!js/function ' msg => msg || 5_000'");

https://github.com/nodeca/js-yaml/issues/560#issuecomment-650688965

Yaml should return the same result everywhere.
It's not good idea to use it as programming language (yaml is for data, not for code).

You may have different opinion, and if your modifications are local - nobody cares what you do. But in mainstream nobody wish to risk with stable package & promote unwanted feature [using yaml as programming language].

I don't understand how your concerns are relevant here. The problem is that the ECMAScript parser in use is outdated and lacks support for more than one version of ECMAScript. The obvious solution seems to be switching to a better parser, like espree, which allows for both of those things. This solution is:

Part of the same standard as esprima, which makes the switch easier and maintains stability.
Able to support multiple ECMAScript versions, allowing you to support new ECMAScript syntax without losing portability.
Limited to supporting stage 4 ECMAScript proposals, which avoids the concerns about edge features.
Maintained by a major package, which ensures stability will be kept.

This shouldn't have any effect in YAML returning the same result, and if this feature itself is a bad idea then why keep it? The feature not being recommended for use seems like an unusual reason to not properly support the feature. I don't see how this would be a risk to stability or promote unwanted features.

The obvious solution seems to

That's only your point of view. From my point of view the obvious solution is to do nothing. You were suggested at least 2 alternatives to solve issue without touching mainstream. When more people require this feature we can discuss it again.


[QUESTION] Not support OpenBLAS for ABI

when i run build.sh script ,have a error message "not support OpenBALS for ABI: armeabi-v7a with NEON, Failed to build OpenBLAS"

Please refer to the updated README.

thanks


If you want to keep IE11 compatibility just close the PR.
Checklist

[X] Checkstyle and unit tests are passed locally with my changes by running gradlew check chrome_headless firefox_headless command
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

@cocorossello I would like to merge this PR, but it has merge conflicts. Could you resolve them? Probably just rebase the branch from master.

I have opened #2080. I'm closing this one. Sorry for the inconveniences

overseded by https://github.com/selenide/selenide/pull/2080


Enhance Documentation with Detailed Setup Guide for New Users by Usman Ghias

Follow me on GitHub Visit My Web App
Description:
Exadel CompreFace is an excellent tool, but new users may find the initial setup process challenging. I propose adding a more detailed, step-by-step setup guide to the documentation, including:

Installation prerequisites
Docker and Docker Compose installation instructions
Detailed setup commands for different operating systems
Troubleshooting common issues

Follow me Usman Ghias Visit My Web App COD Crafters
Proposed Solution:

Add a Prerequisites Section: Clearly list required tools and software.
Step-by-Step Installation Guide: Provide detailed instructions for Docker and Docker Compose installation.
Platform-Specific Instructions: Separate setup guides for Linux, MacOS, and Windows.
Troubleshooting Section: Common issues and solutions during installation.

Benefits:

Improves User Experience: Makes it easier for new users to get started.
Reduces Support Requests: Clear instructions can minimize the need for user support.


Where should cli resolve platform packages from?

I am on tag v2.1.1/v2.1.301 of source-build. I noticed that changes I made to corefx to add more target platforms (via patch files thrown in patches/corefx) aren't making it through to the final SDK build. For example, one patch file contains changes like this:
pkg/Microsoft.NETCore.Platforms/runtimeGroups.props:
     <RuntimeGroup Include="rhel">
       <Parent>linux</Parent>
       <Architectures>x64</Architectures>
-      <Versions>7;7.0;7.1;7.2;7.3;7.4</Versions>
+      <Versions>7;7.0;7.1;7.2;7.3;7.4;7.5;7.6</Versions>
+    </RuntimeGroup>

pkg/Microsoft.NETCore.Platforms/runtime.json:
+    "rhel.7.5-x64": {
+      "#import": [
+        "rhel.7.5",
+        "rhel.7.4-x64"
+      ]
+    },

pkg/Microsoft.NETCore.Platforms/runtime.compatibility.json:
+  "rhel.7.5-x64": [
+    "rhel.7.5-x64",
+    "rhel.7.5",
+    "rhel.7.4-x64",
+    "rhel.7.4",
+    "rhel.7.3-x64",
+    "rhel.7.3",
+    "rhel.7.2-x64",
+    "rhel.7.2",
+    "rhel.7.1-x64",
+    "rhel.7.1",
+    "rhel.7.0-x64",
+    "rhel.7.0",
+    "rhel.7-x64",
+    "rhel.7",
+    "rhel-x64",
+    "rhel",
+    "linux-x64",
+    "linux",
+    "unix-x64",
+    "unix",
+    "any",
+    "base"
+  ],

When I run the sdk (located at ./bin/x64/Release/dotnet-sdk-2.1.301-linux-x64.tar.gz) using
COREHOST_TRACE=1 ./dotnet --version 2>&1 | grep rhel.7.5

I get nothing. It seems like my changes to corefx are not flowing across? Looking at src/cli/msbuild.log, I see:
$ grep Microsoft.NETCore.Platforms src/cli/msbuild.log
                         Microsoft.NETCore.Platforms/2.1.0
                                 Name=Microsoft.NETCore.Platforms
                         Microsoft.NETCore.Platforms/2.1.0/.signature.p7s
                                 PackageName=Microsoft.NETCore.Platforms
                         Microsoft.NETCore.Platforms/2.1.0/LICENSE.TXT
                                 PackageName=Microsoft.NETCore.Platforms
                         Microsoft.NETCore.Platforms/2.1.0/THIRD-PARTY-NOTICES.TXT
                                 PackageName=Microsoft.NETCore.Platforms
                         Microsoft.NETCore.Platforms/2.1.0/microsoft.netcore.platforms.2.1.0.nupkg.sha512
                                 PackageName=Microsoft.NETCore.Platforms
                         Microsoft.NETCore.Platforms/2.1.0/microsoft.netcore.platforms.nuspec
                                 PackageName=Microsoft.NETCore.Platforms
                         Microsoft.NETCore.Platforms/2.1.0/runtime.json
                                 PackageName=Microsoft.NETCore.Platforms
                         Microsoft.NETCore.Platforms/2.1.0/useSharedDesignerContext.txt
                                 PackageName=Microsoft.NETCore.Platforms
                         Microsoft.NETCore.Platforms/2.1.0/version.txt
                                 PackageName=Microsoft.NETCore.Platforms
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                         Microsoft.NETCore.Platforms/2.1.0
                               Name=Microsoft.NETCore.Platforms

It looks like it's only using Microsoft.NETCore.Platforms version 2.1.0? And never the version built by source-build (2.1.1 The source-built version is also 2.1.0). The build log also shows things like:
                         Microsoft.NETCore.Platforms/2.1.0
                                 Name=Microsoft.NETCore.Platforms
                                 Path=microsoft.netcore.platforms/2.1.0
                                 ResolvedPath=/home/omajid/source-build/packages/microsoft.netcore.platforms/2.1.0
                                 Type=package
                                 Version=2.1.0

Which also shows that the ResolvedPath is source-build/packages, not source-build/bin/obj/x64/Release/blob-feed/.

cc @weshaggard

@weshaggard Thanks. I am still quite confused. When I build source-build, isn't it building some version of Microsoft.NETCore.Platform package from the sources at src/corefx/pkg/Microsoft.NETCore.Platforms/? Where does that package end up? Is there no way to make a change (say, for local testing) in that package without bumping the version?

By default it only builds the packages we list in https://github.com/dotnet/corefx/blob/v2.1.1/src/packages.builds which we don't list any packages we don't plan to ship. So I did miss the fact that you would also need to add it to that list to be able to build it, or pass BuildAllPackages=true.
If you do that without bumping the version it will produce a 2.1.0 which may conflict with the one we already shipped. If you are building offline and only using the packages you build it may still work but if there are any online feeds you still risk picking up packages from nuget.org.

By default it only builds the packages we list in https://github.com/dotnet/corefx/blob/v2.1.1/src/packages.builds which we don't list any packages we don't plan to ship.

Aaaaah. Thanks! That makes a lot more sense now.
A general question about the design here: isn't the goal to build everything from source in source-build? Why would we want the final cli build in source-build to consume a Microsoft.NETCore.Platforms which is not from the source-build version of corefx?

That is a very good question and I agree that the general goal. We may want to consider always passing BuildAllPackages=true when doing a source-build.

I will fix this when I get some time, unless you would be interested in submitting a PR?

Sure. Let me try it out: if I can fix it, I will open a PR.

I opened a PR for this: #653

Assigning to @crummel to see if this is fixed with buildAllPackages


[Bug] compilation errors after defining ACHORDION_STREAK

Describe the bug
ACHORDION_STREAK leads to the following compilation errors:
Compiling: users/proostas/features/achordion.c                                                     users/proostas/features/achordion.c: In function 'settle_as_tap':
users/proostas/features/achordion.c:122:23: error: 'keycode' undeclared (first use in this function)
  122 |   update_streak_timer(keycode, record);
      |                       ^~~~~~~
users/proostas/features/achordion.c:122:23: note: each undeclared identifier is reported only once for each function it appears in
users/proostas/features/achordion.c:122:32: error: 'record' undeclared (first use in this function)
  122 |   update_streak_timer(keycode, record);
      |                                ^~~~~~
users/proostas/features/achordion.c:123:7: error: 'is_streak' undeclared (first use in this function)
  123 |   if (is_streak && is_key_event && is_tap_hold && record->tap.count == 0) {
      |       ^~~~~~~~~
users/proostas/features/achordion.c:123:20: error: 'is_key_event' undeclared (first use in this function)
  123 |   if (is_streak && is_key_event && is_tap_hold && record->tap.count == 0) {
      |                    ^~~~~~~~~~~~
users/proostas/features/achordion.c:123:36: error: 'is_tap_hold' undeclared (first use in this function); did you mean 'is_tap_record'?
  123 |   if (is_streak && is_key_event && is_tap_hold && record->tap.count == 0) {
      |                                    ^~~~~~~~~~~
      |                                    is_tap_record
users/proostas/features/achordion.c:133:12: error: 'return' with a value, in function returning void [-Werror=return-type]
  133 |     return false;
      |            ^~~~~
users/proostas/features/achordion.c:97:13: note: declared here
   97 | static void settle_as_tap(void) {
      |             ^~~~~~~~~~~~~

I was setting Achordion according to this great article and everything went smoothly until I defined ACHORDION_STREAK and this function:
uint16_t achordion_streak_chord_timeout(uint16_t tap_hold_keycode, uint16_t next_keycode) {
    // disable for layer-tap keys
    if (IS_QK_LAYER_TAP(tap_hold_keycode)) {
        return 0;
    }

    uint8_t mod = mod_config(QK_MOD_TAP_GET_MODS(tap_hold_keycode));
    // disable for shifts
    if (mod & (MOD_LSFT|MOD_RSFT)) {
        return 0;
    }

    return 150;
}

Is it a bug or I did something wrong?
Addition: The issue is with the current main's HEAD. With v1.5.0 tag, everything compiles without errors.
Information
Do the keys involved use any of the following features?

[x] Achordion (from this repo)
[ ] Auto Shift
[ ] Combos
[ ] Key Overrides
[ ] Mod-tap or Layer-tap keys
[ ] Other custom userspace code:

I think the logic got a bit re-arranged in the last commit, and the streak logic got separated from some variables it needs. Needs a bit of a fix to get the streak logic working again.

@proostas thanks for the report! Sorry about the churn.

I think the logic got a bit re-arranged in the last commit, and the streak logic got separated from some variables it needs. Needs a bit of a fix to get the streak logic working again.

Yes, that's exactly it. I'm working on a fix now.


ng test exception via commented out .browserslistrc file

Bug Report
Affected Package
I'm not exactly sure where this bug is originating. My guess is @angular-devkit/build-angular or @angular/cli.
Is this a regression?
Yes
Description
An Angular project I am working on had a .browserslistrc file but all the fields were commented out like so:
# This file is used by the build system to adjust CSS and JS output to support the specified browsers below.
# For additional information regarding the format and rule options, please see:
# https://github.com/browserslist/browserslist#queries

# For the full list of supported browsers by the Angular framework, please see:
# https://angular.io/guide/browser-support

# You can see what browsers were selected by your queries by running:
#   npx browserslist

# last 1 Chrome version
# last 1 Firefox version
# last 2 Edge major versions
# last 2 Safari major versions
# last 2 iOS major versions
# Firefox ESR
# not IE 11 # Angular supports IE 11 only as an opt-in. To opt-in, remove the 'not' prefix on this line.

After upgrading from Angular 11 to Angular 12, running ng test threw a very cryptic exception somehow related to the commented out lines in .browserslistrc.
ng build and ng serve ran correctly with no exceptions.
Minimal Reproduction
First create a new test app:
ng new test-app

Comment out all lines in .browserslistrc. Then do:
ng test

You should see the exception below.
Exception or Error

Chrome 91.0.4472.101 (Mac OS 10.15.7) ERROR
  An error was thrown in afterAll
  Uncaught SyntaxError: Unexpected token ':'
  SyntaxError: Unexpected token ':'
  Uncaught TypeError: __webpack_modules__[moduleId] is not a function
  TypeError: __webpack_modules__[moduleId] is not a function
      at __webpack_require__ (http://localhost:9876/_karma_webpack_/webpack:/webpack/bootstrap:19:1)
      at Object.4289 (http://localhost:9876/_karma_webpack_/main.js:113:73)
      at __webpack_require__ (http://localhost:9876/_karma_webpack_/webpack:/webpack/bootstrap:19:1)
      at http://localhost:9876/_karma_webpack_/webpack:/webpack/startup:4:1
      at Function.__webpack_require__.O (http://localhost:9876/_karma_webpack_/webpack:/webpack/runtime/chunk loaded:23:1)
      at http://localhost:9876/_karma_webpack_/webpack:/webpack/startup:5:1
Chrome 91.0.4472.101 (Mac OS 10.15.7): Executed 0 of 0 ERROR (0.007 secs / 0 secs)

Your Environment
Angular Version:

Angular CLI: 12.0.4
Node: 14.17.0
Package Manager: npm 6.14.13
OS: darwin x64

Angular: 12.0.4
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1200.4
@angular-devkit/build-angular   12.0.4
@angular-devkit/core            12.0.4
@angular-devkit/schematics      12.0.4
@schematics/angular             12.0.4
rxjs                            6.6.7
typescript                      4.2.4

What is happening here is by commenting the contents of .browserslistrc`, Browserslist will return that there are matching browsers.
In our test webpack configuration we don't explicitly state the we want to target browsers environments. This causes webpack to output invalid output.
While, I'll be working on a fix to address the issue from our side, I recommand that you that do correctly configure which browser you want to support in .browserslistrc as a number of tools and steps in the pipeline do depending on the settings configured in .browserslistrc.


SAK-42831 - Event duration error when importing Google Calendar

It looks like getting the house and minutes here effectively doubled up on the import times. I just removed the hour as pushing a minute value looks like it's working as expected. I wanted to add a unit test but CalendarImporterService was mocked out in BaseExternalCalendarSubscriptionTest and I didn't have the time to try to get that to work. I would add more unit tests if more of this was the actual impls, and I think we would have caught this. Maybe for another jira.

 Here is an overview of what got changed by this pull request:

Complexity decreasing per file
==============================
+ calendar/calendar-impl/impl/src/java/org/sakaiproject/calendar/impl/readers/IcalendarReader.java  -1

See the complete overview on Codacy


Reduced contrast on bolded words on Kindle

Since the recent Kindle updates, the Fast Serif and Fast Sans font has low contrast on the bold portion of the word in comparison to the regular part.  Is there a work around for this? Unfortunately, I am not savvy enough to rewrite the fix.  The contrast is even less in the fast serif ttf.
Thank you for your time, this font is really helping my students process their reading faster and with more cognitive retention.

Thank you for reporting the issue!
I was not aware that they have changed something on the Kindle.
Since I do not own a Kindle, I am not able to reproduce the issue.
Can you tell me if the lower contrast applies on all bold words, also with other fonts?
Or is it only affecting the Fast-Fonts?


deprecate berlin token

WIth this PR, we are deprecating the BERLIN token, as in the future we will release a new EVMOS based token with a technology that will allow us to have a native IBC token.

This will be updated automatically once the chain registry's update gets merged.


karate-netty proxy sends previous request payload when dealing with next request

It happens that the karate.proceed() is sending the body of a previous scenario when the incoming request is lacking one.
Forwarding a GET request doesn't make it happens, maybe karate strips the payload automatically in the GET request, but in
the last request, the DELETE one, it happens that the proxy is sending to the mock server the payload of the first POST request.
After the first and second scenarios are executed (karate-proxy-post and karate-proxy-get), once reached the karate-proxy-delete scenario, the karate.proceed() call in the proxy feature, sends a DELETE request to the mock with the payload of the first POST.
My setup is this:
karate.feature
#################################
@karate
@karate-proxy-post
Scenario:

Given url "http://localhost:8090"
And path 'resources', 1, 'M'
And request read('request.json')
And header TestSuite-Test-ID = 'karate-proxy-post'
When method post
Then status 200
And match response == read('response.json')

@karate
@karate-proxy-get
Scenario:

Given url "http://localhost:8090"
And path 'resources', 'object', 1
And header TestSuite-Test-ID = 'karate-proxy-get'
When method get
Then status 200
And match response == read('request.json')

@karate
@karate-proxy-delete
Scenario:

Given url "http://localhost:8090"
And path 'resources', 'object', 1
And header TestSuite-Test-ID = 'karate-proxy-delete'
When method delete
Then status 204

#################################
proxy.feature (on port 8090)
#################################

Scenario: isTest('karate-proxy-post')
    * karate.proceed("http://localhost:8091")

Scenario: isTest('karate-proxy-get')
    * karate.proceed("http://localhost:8091")

Scenario: isTest('karate-proxy-delete')
    * request '' # THIS HAS NO EFFECT, THE BODY RECEIVED IN 'karate-proxy-post' IS STILL SENT
    * karate.proceed("http://localhost:8091")

#################################
mock.feature (on port 8091)
#################################
Scenario: isTest('karate-proxy-post')

    * def responseStatus = 200
    * def response = read('response.json')

Scenario: isTest('karate-proxy-get')

    * def responseStatus = 200
    * def response = read('request.json')

Scenario: isTest('karate-proxy-delete')

    * def responseStatus = 204
    * def response = {}

we normally insist on a way to replicate: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue
given that hacktoberfest is on - I'll leave this open for a while

@ptrthomas - if its ok I will be interested in working on this.
@scarlink - as mentioned by @ptrthomas earlier, can you pls drop a sample project showing the logs / bug you are experiencing? This will help in resolving [ if issue exists ] in a much timely manner, Thank you for your understanding.

I'll try to send you one tomorrow

@scarlink can you try setting request to non-empty value?
* request 'some value'
@ptrthomas - seems if request body is set empty, its not properly reset inside ScriptValueMap - I recreated the scenario by running :
Given url "http://localhost:8090"
#And path 'resources', 1, 'M'
And request { name: 'Billie' }
And header TestSuite-Test-ID = 'karate-proxy-post'
When method post
Then status 200
And match response.data == { name: 'Billie' }

Given url "http://localhost:8090"
#And path 'resources', 1, 'M'
And request { name: 'Jamie' }
And header TestSuite-Test-ID = 'karate-proxy-post'
When method delete
Then status 200
And match response.data == ''

both above calls are intercepted by proxy as -
Scenario:
* print '>>', request
* karate.proceed('https://postman-echo.com/post')
* print '<<', response

If I try reset request to empty before DELETE, then previous request body is used - if it's not empty, then correct value is passed - i believe its something minor somewhere, will keep debugging trying to find the bug. Thank you.

@ptrthomas - i think i got the issue - will submit PR soon. Thank you.

1.0 released

Hello, I think there is a regression somewhere because I'm working with the master branch and I confirm this is an issue again.

@fscarlato follow this process and open a new issue please: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue


Allow User to Adjust Life Time of Notification

Timer for how long the notification stays on the screen

To clarify, are you asking for the ability to set how long a notification stays on the screen?

Yep

This should technically be possible by using a Timer to call removeDeliveredNotification x seconds after delivering the notification.
I'm not sure if it will be implemented and if so what priority it would take, I'll let @sebj weigh in with any thoughts he has.

@citruspi Would be pretty easy to add, I don't mind (although I feel as though it's a slightly odd/unnecessary cluttering of the preferences window, especially if it gets more crowded with the other feature request issues).
If you 'sign off' on this, I could add something like this though:

Hi @sebj, would be great if you could share how you did the timer addition, so those of us that want could potentially manually edit the source code of the app to include?
I'm not at all a programmer, but think I could work out how to edit the code via 'show package contents'. (Right?)
Ta!

@Macbookair9 Nothing's been implemented yet.
You can't edit the code of any application via 'Show Package Contents' – the actual code (spanning numerous files) is compiled into a binary executable (e.g. actual code is Contents/MacOS/Spotify Notifications which looks like nonsense in any text editor).
If you want to make changes, download Xcode from the Mac App Store, download this repository, use Terminal to update any dependencies, make code changes, and then Build (to compile) & Run.


Test linked comments

AB#76915

✅ Successfully linked to Azure Boards work item(s):

User Story 76915


Hey!

Yo,
I really love your script! Seriously! At last. I won't be using OpenVPN's Access Client that has 2 concurrent connections limit. Really, thanks.
Have an awesome day! Also, I hope your script is compatible with CentOS :)

Thanks.
At the moment, the script is compatible with Debian and Ubuntu.
CentOS support will be added in the future.

Your script does not allow me to access the internet.

I'm willing to give you access to a special VPS server. Please enter your email address here: http://goo.gl/forms/P9SHSTEqgM

Sorry, I don't provide free personal support. The script does work on clean Debian and Ubuntu setups.

Because it does not allow me to access the Internet. I even disabled IPtables. Same thing. I can connect to the vpn thingy but it does not allow me to access any website.

I even disabled IPtables

So you are not using a clean setup. Again, I can only guarantee it to work on a clean Debian/Ubuntu system, no further support is provided except for NATed networks and some other common configurations.

What if I’m under NAT, what will I do?
From:  Nyr<EMAIL_ADDRESS>Reply-To:  Nyr/openvpn-install
<reply+007b41a19c962b93289ade8da76d7c06f597b59b263654a692cf0000000110e3480b
<EMAIL_ADDRESS>Date:  Friday, January 30, 2015 at 9:24 PM
To:  Nyr/openvpn-install<EMAIL_ADDRESS>Cc:  Juan Karlo de Guzman<EMAIL_ADDRESS>Subject:  Re: [openvpn-install] Hey! (#33)
I even disabled IPtables
So you are not using a clean setup. Again, I can only guarantee it to work
on a clean Debian/Ubuntu system, no further support is provided except for
NATed networks and some other common configurations.
—
Reply to this email directly or view it on GitHub.

I will repeat one last time: support for custom setups will never be provided and you will need to work your way around issues.
Locking this issue now.


When finetune the model, how do I use different learning rate for different layers?

I was using resnet-50 to do saliency detection. When I used learning rate 1e-3, the validation loss started to increase just after one epoch; when I reduce the learning rate to 1e-4 or 3e-4,or 5e-4, the validation rate decreased but the final result was worse than  1e-3. I think the learning rate was too high for the resnet layers, but the learning rate is too slow for other layers.
So, can I use different learning rates for different layers? Could you give some tips?

Hi!
It's impossible with the current way the framework is made.
But if you're willing to modify the keras code, you can look up the file optimizer.py.
Let's say you want to add a factor when the weights are updated with plain SGD. In line 168, there is a loop over all the weights of the network and this is where the gradients are multiplied by the learning rate.
If you're willing to do it, this would be the place to start. But i'm not sure what the most beautiful implementation of this would look like.
Hope this helps.


got exception when replay star mgr journal

Steps to reproduce the behavior (Required)

Use the main branch to build FE
start to run SR In shared-data mode
do some SQL operation
restart FE and check the fe.warn.log.

Expected behavior (Required)
there is no logs in fe.warn.log
Real behavior (Required)
2024-04-26 00:17:21.299+08:00 ERROR (star mgr LeaderCheckpointer|112) [Checkpoint.replayAndGenerateStarMgrImage():236] Exception when generate new star mgr image file, null.

StarRocks version (Required)

main
branch-3.3

done


When i do selection in brush chart it removes xaxis annotation but it works on selection in main chart

When i do selection in brush chart it removes xaxis annotation but it works on selection in main chart
Steps to Reproduce

Create main chart with annotation on React.

export const combinedChartDataOptions = (chartData: ChartData) => {
  const chartOptions: ApexOptions = {
    series: [
      {
        name: 'Bait filling',
        type: 'area',
        data: chartData.bait_filling || [],
        color: '#6A37D4',
      },
      {
        name: 'Eaten bait',
        type: 'bar',
        data: chartData.eaten_bait || [],
        color: '#fae600',
      },
    ],
    chart: {
      id: 'main-chart',
      height: 350,
      type: 'line',
      stacked: false,
      zoom: {
        enabled: true,
        type: 'x',
      },
      toolbar: {
        show: true,
      },
    },
    markers: {
      size: 0,
      shape: undefined,
    },
    stroke: {
      show: true,
      width: [2, 2],
      curve: 'smooth',
    },
    fill: {
      opacity: [0.2, 0.6],
    },
    plotOptions: {
      bar: {
        columnWidth: '20%',
        borderRadius: 3,
        hideZeroBarsWhenGrouped: true,
        borderRadiusApplication: 'around',
      },
    },
    xaxis: {
      categories: chartData.date_time || [],
      offsetY: 1,
      labels: {
        trim: false,
        style: {
          colors: '#9aa0ac',
        },
      },
      type: 'category',
      tickPlacement: 'on',
    },
    dataLabels: {
      enabled: true,
      background: {
        enabled: true,
      },
    },
    annotations: {
      xaxis: chartData.annotations,
    },
  };

  return chartOptions;
};

Creact brush chart for it

// Brush chart options
export const brushChartOptions = (chartData: ChartData) => {
  const brushOptions: ApexOptions = {
    series: [
      {
        name: 'Bait filling',
        type: 'line',
        data: chartData.bait_filling || [],
        color: '#6A37D4',
      },
    ],
    chart: {
      id: 'brush-chart',
      height: 100,
      type: 'line',
      stacked: false,
      zoom: {
        enabled: true,
        type: 'x',
      },
      brush: {
        enabled: true,
        target: 'main-chart',
      },
      // selection: {
      //   enabled: true,
      //   type: 'x',
      //   xaxis: {
      //     min: chartData.date_time.length - 10,
      //     max: chartData.date_time.length - 1,
      //   },
      // },
    },
    xaxis: {
      categories: chartData.date_time || [],
      offsetY: 1,
      labels: {
        trim: false,
        style: {
          colors: '#9aa0ac',
        },
      },
      type: 'category',
      tickPlacement: 'on',
    },
    plotOptions: {
      bar: {
        columnWidth: '50%',
        borderRadius: 3,
      },
    },
    legend: {
      show: false,
    },
    dataLabels: {
      enabled: false,
    },
    annotations: {
      xaxis: chartData.annotations,
    },
  };

  return brushOptions;
};

Select are in brush chart and annotation will disapear

Annotation must be shown
Desapear when use selection on brush chart but works correct on main chart selection
Screenshots

Reproduction Link <= Video of problem

Please provide a link to a code pen that reproduces the issue. Something we can run ourselves.

I can reopen when provided.

Can it be without codepen? All data from API and so mush custom hooks to provide here... All problem and chartOptions are privided.

Preferably you would use fake/mock data and not rely on a functioning API call. We need to be able to duplicate the issue and step through it to observe the code as the issue occurs.
If you can create a sample app that is very easy for us to run and debug, then that will be fine. Only include what is absolutely necessary for the issue to be replicated.  I did +- same but cant connect my brush chart with main. Can i sand it? Maby code producer cen easylly fix it and my error will b eprovided/

https://codesandbox.io/p/sandbox/react-basic-example-forked-dqzsc2?file=%2Fsrc%2FApp.js%3A4%2C1

Your sample does not reproduce the issue. Please update your sample to reproduce the issue.


Network box

Is it possible  to hide the network box or to collapse it if the network is already set up? or at least place it at the bottom.

Yes, good idea. I'll look into it.

Thanks ! your Italian clock face was just added to the repository with PR #27
Regarding updates not working, there was a timer bug that was just fixed yesterday that could have caused this, but if you are still able to reproduce it would be helpful to see if there's any info on the serial console.
As for AMPM it's the same with French actually (unused too), I need to think of a simple way to toggle that.

Can I reach out to you somehow? I have issues with the new code. If you can, text me at @ilgiurgi on telegram.

Sorry I'm not in telegram. Feel free to file as many issues as necessary here! It might help others.

For some reason I messed up something maybe with the cables or something but the ESP keeps rebooting with the code, I tried uploading a code to see if each component works well and they do, so I can't figure out what's the reason of the reboots.. That's the error, I always used same usb cables ecc so it could be the board maybe?
12:51:36.869 ->
12:51:36.869 -> Brownout detector was triggered
12:51:36.869 ->
12:51:36.869 -> ets Jul 29 2019 12:21:46
12:51:36.869 ->
12:51:36.869 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
12:51:36.869 -> configsip: 0, SPIWP:0xee
12:51:36.869 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
12:51:36.869 -> mode:DIO, clock div:1
12:51:36.869 -> load:0x3fff0030,len:1344
12:51:36.869 -> load:0x40078000,len:13964
12:51:36.869 -> load:0x40080400,len:3600
12:51:36.869 -> entry 0x400805f0

Uh oh Brownout detector was triggered ?
Is the power supply too weak?

Ok thanks for the heads up I will also do some testing

As of 1d2bcd9 there is now a language selector (including italian) and we hide the am/pm if unused. We also move the network section to the bottom after initial setup.
I've tested the firmware on my clock and it works without issue, so I'll close this ticket (which was about the network section of the web UI) but feel free to open another if your issues persist!


Add features section to info response

Towards https://github.com/giantswarm/giantswarm/issues/5465
This PR adds an attribute to the GET /v4/info/ response that will allow clients to detect from which release version on support for node pools will be available.

I have moved the features key up one level.

FYI @giantswarm/sig-ux We are adding this section to the info endpoint to enable clients to understand from which release on the feature "node pools" will be available.


Remove backend

Summary
Now that the backend is available at dev.api.antalmanac.com, we can use that instead of running it locally! This drastically simplifies the onboarding experience for new developers. Devs no longer need to recursively clone the project or have the .env file for the backend.
In this PR, we do the following:

remove the backend submodule
move the contents of /client into the root directory
update package.json in the root directory to be for the website
update the readme accordingly

Test Plan

Delete package-lock.json, delete /node_modules, and re-run npm i
Run npm start and verify that that site loads on localhost:3000.
Verify that I can load and save schedules to the dev.api.antalmanac.com backend.
Run npm run deploy and verify that deployment succeeds

Issues
#138
Future Followup

Maybe make it easier to hook up the backend with the frontend for local development? Right now it requires a code change but it would be nice if it was just a flag or env variable.

This is a big PR. In addition to testing the branch locally, the most important files to review are:

package.json
README.md

It might be easier to look at the commits inside of all of the changed files at once.


NEW Pass in-memory-cache input for extra_jobs

Passes along the new input for extra_jobs. See https://github.com/silverstripe/gha-ci/pull/135
Issue

https://github.com/silverstripe/silverstripe-framework/issues/11145

Needs a unit test

I had considered that but there's no tests for any of the extra_jobs stuff right now. If we want test coverage for extra_jobs we should do that as a separate card, and add coverage for it as a whole rather than just for this small part of it.


Resolve syncing conflicts from from-prod-live to live

Pull request opened by Docs to resolve syncing conflicts from from-prod-live to live.

Docs Build status updates of commit 32996c9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-powershell, working directory: W:\dgb4-s, target branch: live, target branch commit: 04457e2bc9b0b566c932d3087da9b0ae23228615, source commit: 32996c98754b562211a020bdd62b4bc8051e2026.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 56ed085:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-powershell, working directory: W:\2bnu-s, target branch: live, target branch commit: 04457e2bc9b0b566c932d3087da9b0ae23228615, source commit: 56ed085a868afa8263f8eb0f755b5822f5c29532.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d677aa5:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-powershell, working directory: W:\lf2m-s, target branch: live, target branch commit: 04457e2bc9b0b566c932d3087da9b0ae23228615, source commit: d677aa58b251a8fb35732478a6b67d882fdbe3cc.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 66caf7f:
:clock10: Full build: the average full build time is 59 min(s) 33 sec(s), this is based on the last 1 build(s) for this repository.

Docs Build status updates of commit 66caf7f:
:clock10: Full build: the average full build time is 59 min(s) 33 sec(s), this is based on the last 1 build(s) for this repository.

Docs Build status updates of commit 66caf7f:
:clock10: Full build: the average full build time is 59 min(s) 33 sec(s), this is based on the last 1 build(s) for this repository.

Docs Build status updates of commit 66caf7f:
:clock10: Full build: the average full build time is 59 min(s) 33 sec(s), this is based on the last 1 build(s) for this repository.

Docs Build status updates of commit 66caf7f:
:clock10: Full build: the average full build time is 59 min(s) 33 sec(s), this is based on the last 1 build(s) for this repository.

Docs Build status updates of commit 66caf7f:
:clock10: Full build: the average full build time is 59 min(s) 33 sec(s), this is based on the last 1 build(s) for this repository.

Docs Build status updates of commit 66caf7f:
:clock10: Full build: the average full build time is 59 min(s) 33 sec(s), this is based on the last 1 build(s) for this repository.

Docs Build status updates of commit 66caf7f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

azuresmps-4.0.0/Azure.Service/Add-AzureAccount.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureApplicationGatewaySslCertificate.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureCertificate.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureDataDisk.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureDisk.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureDns.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureEndpoint.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureEnvironment.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureHDInsightConfigValues.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureHDInsightMetastore.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureHDInsightScriptAction.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureHDInsightStorage.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureInternalLoadBalancer.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureNetworkInterfaceConfig.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureNodeWebRole.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureNodeWorkerRole.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzurePHPWebRole.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzurePHPWorkerRole.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureProvisioningConfig.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureRemoteAppUser.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureTrafficManagerEndpoint.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureVMImage.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureVhd.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureVirtualIP.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureWebRole.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Add-AzureWorkerRole.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Azure.Service.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Clear-AzureProfile.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Clear-AzureRemoteAppVmStaleAdObject.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Confirm-AzureStorSimpleLegacyVolumeContainerStatus.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Copy-AzureRemoteAppUserDisk.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Disable-AzureDataCollection.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Disable-AzureServiceProjectRemoteDesktop.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Disable-AzureTrafficManagerProfile.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Disable-AzureWebsiteApplicationDiagnostic.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Disable-AzureWebsiteDebug.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Disconnect-AzureRemoteAppSession.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Enable-AzureDataCollection.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Enable-AzureServiceProjectRemoteDesktop.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Enable-AzureTrafficManagerProfile.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Enable-AzureWebsiteApplicationDiagnostic.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Enable-AzureWebsiteDebug.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Export-AzureRemoteAppTemplateImage.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Export-AzureRemoteAppUserDisk.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Export-AzureVM.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Get-AzureAccount.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Get-AzureAclConfig.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Get-AzureAffinityGroup.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

azuresmps-4.0.0/Azure.Service/Get-AzureApplicationGateway.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Problem: (BEP-21) no way to propose validator election

Solution: Integrate the new election spec specified in BEP-21
Implements one of the tasks in issue #2372

Codecov Report

Merging #2392 into master will increase coverage by 0.28%.
The diff coverage is 96.89%.

@@            Coverage Diff             @@
##           master    #2392      +/-   ##
==========================================
+ Coverage    86.9%   87.18%   +0.28%
==========================================
  Files          38       40       +2
  Lines        2169     2248      +79
==========================================
+ Hits         1885     1960      +75
- Misses        284      288       +4

Removing @vrde from review as he is on holiday.


Consignment Tracking

As a customer, I want to see my package tracking information in the Order Detail Page, so that I can know the route of my package
If the order is in "Shipped" status, show a "Track Package" button for each consignment in Order Detail Page
If there is no tracking information for now, show a message to indicate this situation
Pop-up a page when click "Track Package" button to show the package tracking information:
Estimated Delivery data
Delivery Service(a.k.a Delivery Carrier Name)
Tracking Number(no link for now)
Package routing(in reverse chronological order). Don't need "Shipped" item in the list; OOTB, show the mock package tracking events
Show a loading indicator in the pop-up before receiving data from backend server
Don't consider localization for now
Please refer to the mock-up; should support responsive as the mock-up shows

PR: https://github.com/SAP/cloud-commerce-spartacus-storefront/pull/3365


Signs fail to parse if using an external diffing tool

Description
I use this external viewer for diffs https://github.com/Wilfred/difftastic and have it setup in my gitconfig as a global external differ tool with
[diff]
     external = difft
     tool = difftastic

I assume the different format of the diff isn't parsable so it fails to show the signs. I think it would be safe to just git diff --no-ext-diff  always , but if not it'd be nice to be able to override the diff command
Neovim version
0.8.2
Operating system and version
macOS 13.1
Expected behavior
Signs show up on a diff
Actual behavior
No signs show up. It took a few for me to figure out what was going on
Minimal config
vim.o.packpath = '/tmp/nvim/site'

local plugins = {
  gitsigns = 'https://github.com/lewis6991/gitsigns.nvim',
  -- ADD OTHER PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE
}

for name, url in pairs(plugins) do
  local install_path = '/tmp/nvim/site/pack/test/start/'..name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
end

require('gitsigns').setup{
  debug_mode = true, -- You must add this to enable debug messages
  -- ADD GITSIGNS CONFIG THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
}

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE

Steps to reproduce

Setup any external diff viewer (i use https://github.com/Wilfred/difftastic)
Setup your gitconfig as above
Try and get signs to show
Comment out gitconfig diff section
Signs now show

Gitsigns debug messages
No response

Difftastic does not support patch formats:

Patching. Difftastic output is intended for human consumption, and it does not generate patches that you can apply later. Use diff if you need a patch.

So by design, it is unable to work with other tools, including GitSigns.

I think it would be safe to just git diff --no-ext-diff always , but if not it'd be nice to be able to override the diff command

Sorry, missed this.

Yes, i'm not asking to have it work. i'm asking to disable this tool

Do you not have internal set in set dittopt?

I'm using lunarvims setup with the defaults https://github.com/LunarVim/LunarVim/blob/master/lua/lvim/core/gitsigns.lua

What does set diffopt? show?

setting internal fixes it, tnx!

internal is apart of the default value of diffopt. I suggest in your config to have either:
set diffopt+=vertical

or
vim.opt.diffopt:append('veritcal')

My personal setting is:
  vim.opt.diffopt:append{
    'linematch:50',  -- needs neovim nightly
    'vertical',
    'foldcolumn:0',
    'indent-heuristic',
  }

cool thanks for the info, really appreciate the plugin!


Unknown error: local variable 'encoded_body' referenced before assignment

Not solving mini game. Got an error:
Unknown error: local variable 'encoded_body' referenced before assignment

Same problem

the solution was recently released
https://github.com/shamhi/HamsterKombatBot/commit/f3505ac917587008666f0c2aaf8131da1cc53380


style.css not getting recreated when generating after highlight colorschemes change

Hello, not sure if this belongs here or to hexo's repository.
style.css is not getting recreated when running hexo generate after changing the highlight colorscheme, you have to delete the file from /public/css and then hexo generate.

I just tested it and it works fine for me (using Hexo 3.2.2).
Did you try running hexo clean? Usually that command fixes these kind of problems. If the problem persists, I advise you to create an issue in Hexo's repository.

It works if I run hexo clean every time before hexo generate, probably because it deletes /public.
Thanks for the help, I'll create a new issue in Hexo's repository.


Reseting the emulator session

I am trying to test the firstRun middleware, but the session persists even after restarting both, the bot server and the emulator.
bot.use(builder.Middleware.firstRun({ version: 1.0, dialogId: '*:/firstRun' }));

So, ironically, I can get to the first run dialog only once.
Is there any way to clear the session?

Hi @almirbi, A feature for this will be added to the emulator next week. In the meantime, restarting the emulator will clear the state. Sorry for the inconvenience and thanks for your patience.


Update AutoReconnector.cs

@ScrPits You should probably add those changes to Silv3rs master, since it is the original - not my forked project xD
But if you do, you shold probably explain your changes. So developers can discuss over the integration of you pull request ;)
Couldn't find any message functionallities, so I hope this comment reaches you ,)


Fatal error Installing using composer

I got a fatal error in the browser after installing CodeIgniter using composer with the following command:
composer create-project codeigniter4/devstarter my_project_name -s dev
The error was:
Fatal error:  require(): Failed opening required 'I:\\my_project_name\\app\\Config/../../vendor/codeigniter4/framework/system/bootstrap.php'
I checked the vendor folder and the "framework" folder /vendor/codeigniter4/ is missing. I only saw  /vendor/codeigniter4/codeigniter4/.
I renamed the /vendor/codeigniter4/codeigniter4 to /vendor/codeigniter4/framework and there were no more errors.

I think that is related with #1871 . Try running 'composer update'  and check if fix it

Running 'composer update' did not fix it.
I created another test project.
composer create-project codeigniter4/devstarter testproj -s dev
After installing cd testproj
and run 'composer update' and there is still the error.

This is because of https://github.com/codeigniter4/devstarter/issues/1, and it makes the devstarter unusable.
The quick fix is to open app/Config/Paths.php and change this line:
public $systemDirectory = __DIR__ . '/../../vendor/codeigniter4/framework/system';

to this:
public $systemDirectory = __DIR__ . '/../../vendor/codeigniter4/codeigniter4/system';

("framework" to "codeigniter4")
@jim-parry and I wrote about it a bit, but there's going to need to be a change to the release scripts in admin/ in order to fix this.

devstarter is not created by the release scripts. I have updated its app/Config/Paths.php, which should fix the problem for new installs this way. Existing ones might need to manually update the path, as described aboce.

Not hearing anything contrary in 6 days, I presume the fix works.

Thanks Guyz

I use linux, so this worked for me:
composer update --ignore-platform-reqs

I have getting the fatal error. after updating composer also getting same error.
PHP Warning:  require(/opt/lampp/htdocs/ci4/app/Config/../../vendor/codeigniter4/codeigniter4/system/bootstrap.php): Failed to open stream: No such file or directory in /opt/lampp/htdocs/ci4/spark on line 46
PHP Fatal error:  Uncaught Error: Failed opening required '/opt/lampp/htdocs/ci4/app/Config/../../vendor/codeigniter4/codeigniter4/system/bootstrap.php' (include_path='.:/usr/share/php') in /opt/lampp/htdocs/ci4/spark:46
Stack trace:
#0 {main}
thrown in /opt/lampp/htdocs/ci4/spark on line 46


chore(ci): Test more features and MSRV

Adding explicit check and clippy steps for the default features,
because --all-features enables the "testing" feature which in turn
disables a bunch of production code.  Preferably we figure out how to
not make --all-features skip prod code like this, but this is a stop
gap in the mean time.
Adding an explicit MSRV check and removing the rust-toolchain file.
This means local dev will default to using the latest rust compiler
and we'll not be surprised by failing CI that worked locally.  The
explicit MSRV check makes it so that we at least notice when we break
this.

@Arqu  the msrv job needs a fair bit of copying of protoc etc.  I wonder if we instead should run it as one of the steps in build_and_test job instead?

@Arqu any idea how to fix windows here?  everything else seems to work

@Arqu the msrv job needs a fair bit of copying of protoc etc. I wonder if we instead should run it as one of the steps in build_and_test job instead?

Yes, lets absorb it into the build and test, we do better with sequential builds in a single job instead of lots of smaller independent ones in parallel.

@Arqu any idea how to fix windows here? everything else seems to work
AFAIK windows doesn't do too well with env vars. Maybe try absorbing the MSRV into the build matrix as a single element and use ${{ matrix.msrv }} to pipe it in. Should probably work out + leaves us the option to simply extend the matrix later.

I will need to update GH Actions required checks with the new flag

AFAIK windows doesn't do too well with env vars. Maybe try absorbing the MSRV into the build matrix as a single element and use ${{ matrix.msrv }} to pipe it in. Should probably work out + leaves us the option to simply extend the matrix later.

Ah, that's a neat trick and works!
This PR is now ready.
The only related question I still have is how caching is handled in current CI?

AFAIK windows doesn't do too well with env vars. Maybe try absorbing the MSRV into the build matrix as a single element and use ${{ matrix.msrv }} to pipe it in. Should probably work out + leaves us the option to simply extend the matrix later.

Ah, that's a neat trick and works!
This PR is now ready.
The only related question I still have is how caching is handled in current CI?

No caching, currently timewise more is spent pulling and pushing the cache than it's saving.

If you have better ideas than shoving into the matrix I'd welcome it, otherwise we can merge for now and I'll bump the settings.

actually can you try with $env:MSRV as the env var if: matrix.os == "windows-latest"

I will need to update GH Actions required checks with the new flag. Ideally this would have been an env var or similar so we can simply update without changing the GHA config every time but will do for now

Not sure I follow, the current approach of extending build_and_test does not change the required checks does it?

actually can you try with $env:MSRV as the env var if: matrix.os == "windows-latest"

sure, i can give this a go

It does, because the matrix is part of the check signature. So "new ones" appear and the old ones don't exist any longer

ah, i see.  the environment var with different syntax for windows does duplicate a lot of stuff though :(

ah, i see. the environment var with different syntax for windows does duplicate a lot of stuff though :(

but it works

ah, i see. the environment var with different syntax for windows does duplicate a lot of stuff though :(

but it works

Lets do that then.


ja-docs: Update kops Installation Steps

Document downloading the latest or a specific kops version.

Add links to Install Homebrew On MacOS, Linux.

@kihahu Thank you for PR! Could you switch base branch to dev-1.16-ja.1?

@oke-py I have done the switch.

/lgtm

/assign @cstoku

/approve


Request - IHtmlContent.ToString() to return markup string

We have an extension method:
public static string GetString(this IHtmlContent content)
{
    var writer = new System.IO.StringWriter();
    content.WriteTo(writer, HtmlEncoder.Default);
    return writer.ToString();
}

to get markup from, for example, IHtmlHelper.ActionLink(..). In MVC5 ActionLink.ToString returns markup code. Would be nice to have IHtmlContent's .ToString() overload to return the same, so to simplify the consumers' code.

Related to this, could you please suggest if there is a better / optimized way in ASP.NET Core of writing this kind of extension (for example, without having to use StringBuilder and StringBuilder.ToString()):
// HtmlHelperExtensions.cs
public static string GetList(this IHtmlHelper helper)
{
    // actual code is doing many more such 'ActionLink()' appends
    return new StringBuilder("

")
        .Append(helper.ActionLink("foo", "bar", "example").GetString())
        .Append("

").ToString();
}

// usage in Razor
@Html.Raw(Html.GetList())

Thanks! :)

Hi @am11 , the reason that there's no built-in ToString() method is that it would be very inefficient because it would allocate a whole lot of strings. We did a lot of work in ASP.NET Core Razor to help make sure that HTML rendering can be done very efficiently.
Here's a very efficient way to write your HTML helper method that minimizes memory allocations:
    public static IHtmlContent GetList(this IHtmlHelper helper)
    {
        var listHtml = new HtmlContentBuilder();
        listHtml.AppendHtml("

");
        listHtml.AppendHtml(helper.ActionLink("foo", "bar", "example"));
        listHtml.AppendHtml("

");
        return listHtml;
    }

Note that all the built-in HTML helpers return an IHtmlContent, and then you can use the HtmlContentBuilder to compose a lot of smaller HTML content elements into a larger element. And this is all without using ToString!
Now, to render this, it's even simpler:
@Html.GetList()

Notice that it isn't using @Html.Raw(...) because this content is already marked as HTML, so Razor can do the right thing.

Thnaks @Eilon! That worked perfectly fine. 👌


Make floaterm position and dimensions configurable

Hi,
It would be great if one could configure the position and dimensions of the floaterm used for tests.
Position like "center", "top", "right", "bottom", "left".
Dimensions in percentage of width and height of the screen.
I often run tests that log lots of long lines of output, and the default split right makes it a bit cumbersome to read all output.
If I could configure the term to open covering almost all of the screen, that would be awesome!
BR,
Odd

Hi,
I've noticed that lately, the float term closes after a short timeout after the test is complete. Disabling this auto-close would also need to be configurable for the above to be useful.
BR,
Odd

Both should been fixed

Hi folks,

Hi, 你好，
I've noticed that lately, the float term closes after a short timeout after the test is complete. Disabling this auto-close would also need to be configurable for the above to be useful.我注意到最近，测试完成后，浮动窗口会在短暂的超时后关闭。禁用这个自动关闭功能也需要可配置，以便上述功能能够发挥作用。
BR, 您好，以下是您要求的翻译内容： BR, Odd 奇怪的

this is not fixed, still have this isuee