CSV stuck in Pending state, requirement not met on missing serviceAccount that is defined in said CSV

Bug Report

What did you do?
The serviceaccount defined in my CSV at spec.clusterPermissions[].rules[].serviceAccountName was deleted
What did you expect to see?
I would expect OLM to be able to reconcile this state by re-creating the serviceaccount, allowing the CSV to reconcile & progress.
What did you see instead? Under which circumstances?
CSV is stuck in Pending state because the requirements are not met. The specific missing requirement is the serviceaccount stated above
Group:
Kind:       ServiceAccount
Name:       myapp-operator
Status:     PresentNotSatisfied

Environment

operator-lifecycle-manager version: v0.10.0

Kubernetes version information: openshift 3.11

Possible Solution
Looking at the OLM code, I noticed the following code path which is reached when a CSV is in Pending state and requirements are not met. That code returns an appropriate error and sets the CSV state to Pending (even though it already is). It appears that the reconcile loop will always reach this code path and not progress any further
Shouldn't OLM re-create the serviceaccount if it's missing, especially since it's a permission requirement?
Additional context
This was observed on a staging cluster during a 3.11 cluster upgrade. We could not tell what deleted the serviceaccount (OLM or something else). The manual 'fix' was to delete the CSV, InstallPlan and Subscription and then re-create the subscription.
We plan on upgrading to OLM v0.13 on the production cluster before that cluster is upgraded. However from the changelogs and closed issues I see no indication that the behavior will be different on v0.13, hence why I'm opening this issue to get more insights and a potential fix.

We've identified that there was an error in the CRD which was only being reported in the InstallPlan conditions (not in the CSV conditions). After fixing the CRD, OLM was able to progress and replace the old CSV with the new one, including the creating of the missing serviceaccounts.


Update frpc.js

allow to use hostname and ip in server address

Hi, could you submit this patch to upstream?

Hi, could you submit this patch to upstream?

I will have a try

Thanks for PR, upstream commit: 665bbb014bbe05a40ca0422d028fe358a1f33694.


docs(docs-zh/docs)：update the community article docs

What this PR does / why we need it:
update the community article docs

There are some issues with the commit history, please organize it. We should not see any "merge" commits.

Mabye you can use "git rebase" to amend.


Update the image used to show how to make a project discoverable to match new settings control

PR: #1539

:+1:


V2 - Corporate Console link of V1 is displayed in email notification sent to CLA Manager

Observed that Corporate Console link of V1 is displayed in email notification sent to user when the user is added as CLA Manager to a project from V2 Corporate Console

Created PR https://github.com/communitybridge/easycla/pull/1479

Verified that the issue is fixed and when clicked on the link highlighted below, LFX portal login page is displayed in new tab


Update Formula to lacework-cli v0.2.15

@dmurray-lacework did you run the script to update the formula?

@dmurray-lacework did you run the script to update the formula?


check and code review error is fixed

Signed-off-by: gunjanmimo<EMAIL_ADDRESS>some errors are fixed

@gunjanmimo in order to sync your fork, will you run:
git fetch upstream
git checkout master
git merge upstream/master

so that the commits for the issue templates are not included in this PR?

Thanks, @gunjanmimo. I think we finally nailed this one in PR #42. Much appreciated.


chore(ci): increase linux build timeout

We are seeing a lot of tests time out while fetching from our nix caches, there might be temporary network congestion, but that shouldn't make our tests fail.

I doubt it will help after chatting with @dpc about it :(

Maybe I was wrong and whatever was stuck unstuck itself after an ungodly amount of time?!


GEOS not detected

I'm using GeoDjango buildpack for Heroku and keep having an issue that I can't solve and am going around in circles. I was hoping someone can help.
App seems to build ok:
Counting objects: 4, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 356 bytes | 0 bytes/s, done.
Total 4 (delta 3), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Fetching custom git buildpack... done
remote: -----> Python app detected
remote:        Using geos version: 3.4.2
remote:        Installed
remote:        GEOS installed and accessible with env variable 'GEOS_LIBRARY_PATH'
remote:        Using proj version: 4.8.0_1
remote:        Installed
remote:        Proj.4 installed and accessible with env variable 'PROJ4_LIBRARY_PATH'
remote:        Using gdal version: 1.11.1
remote:        Installed
remote:        GDAL installed and accessible with env variable 'GDAL_LIBRARY_PATH'
remote: -----> Installing dependencies with pip
remote:
remote: -----> Preparing static assets
remote:        Collectstatic configuration error. To debug, run:
remote:        $ heroku run python manage.py collectstatic --noinput
remote:
remote: -----> Discovering process types
remote:        Procfile declares types -> web
remote:
remote: -----> Compressing... done, 141.3MB
remote: -----> Launching... done, v33
But the issue arrises when I change the model file and then try to run:
heroku run python manage.py makemigrations
I'm getting an error:
django.core.exceptions.ImproperlyConfigured: GEOS is required and has not been detected. Are you sure it is installed?
My settings file contains:
GEOS_LIBRARY_PATH = environ.get('GEOS_LIBRARY_PATH')
GDAL_LIBRARY_PATH = environ.get('GDAL_LIBRARY_PATH')
I’m relatively new to Django and Heroku, is there something obvious I’m doing wrong? I suspect it might be a path issue, but I'm not sure how to resolve it.
Many thanks

I would advise to use the excellent https://github.com/cyberdelia/heroku-geo-buildpack.
Better architectured, it uses the multi-buildpack feature brillantly.
I am considering deprecating my buildpack over this one. You might give it a change, I personally have moved my project to this other buildpack.

I've taken the decision to deprecate it, but I keep the repo for those who reference it.
Cheers


Update _card.scss

Invites section doesn't expand past a certain height
https://media.discordapp.net/attachments/363087331475062785/493920826505035776/unknown.png?width=693&height=428
Displays correctly when position is set from relative to initial in the CSS.

@ykris45 We use the .card class in a lot of places. Have you tested that this doesnt affect other parts of the app? I will give it a test in a little bit.

@seanyesmunt i doesnt have a lot of referalls. and i will test it on locally.


Cannot read Downloaded chapters and invalidate download index not working

Steps to reproduce
1.download any manga
2.restart the device or open mihon after some hours
Expected behavior
After restarting the downloaded chapters should stay intact and we should be able to read them with no issue
Actual behavior
But i cant actually read them and the downloaded mark disappears and if i try to open the file with data turned off i get an error saying "failed to connect to ____(the extension you are using).
Crash logs
No response
Mihon version
0.16.5
Android version
Android 14
Device
Iqoo neo 9 pro
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.16.5.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Join discord for further support since it is definitely working


SyntaxError while running saturn_multiple_seeds.py

Hi,
I am trying to run multiple seeds on my SATURN intergated data using saturn_multiple_seeds.py.
Following is my command line code:
!python3 SATURN/saturn_multiple_seeds.py
--run=data/mouse_zebrafish_run_multi.csv
--embedding_model=ESM2
--gpus 1
--seeds=10 --pe_sim_penalty=0.2
However, I am getting the following syntax error:
['1']
0%|                                                    | 0/10 [00:00<?, ?it/s]RUNNING SEED: 0 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
RUNNING SEED: 1 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
RUNNING SEED: 2 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
RUNNING SEED: 3 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
RUNNING SEED: 4 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
RUNNING SEED: 5 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
RUNNING SEED: 6 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
RUNNING SEED: 7 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
80%|███████████████████████████████████▏        | 8/10 [00:00<00:00, 72.00it/s]RUNNING SEED: 8 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
RUNNING SEED: 9 ON GPU:1
File "train-saturn.py", line 108
key = f"{indices_mapped[0][j]},{indices_mapped[1][j]},{indices_mapped[2][j]}"
^
SyntaxError: invalid syntax
100%|███████████████████████████████████████████| 10/10 [00:00<00:00, 72.42it/s]
I cannot figure out what I am doing wrong. Could you please help me? Full analysis notebook can be found here
Thanking you in advance,
Vishnu

I had both python2 and python3 installed. So, I had to change the line 60 in saturn_multiple_seeds.py from
command_part_1 = f"python /DATAFILES/Cross_species/SATURN/train-saturn.py --in_data={args.run} --device_num="
to
command_part_1 = f"python3 /DATAFILES/Cross_species/SATURN/train-saturn.py --in_data={args.run} --device_num="
Everything works fine now.

Hi @vishnums007 , I could not find any output files in directory?
'/share/home/miniconda3/envs/saturns/bin/python3.10 /date/16.saturns/SATURN/saturn_multiple_seeds.py  --run=/date/16.saturns/SATURN/Vignettes/ah_atlas/data/ah_atlas_run.csv --embedding_model=ESM2 --gpus=0  --seeds=1'


Create Typescript compatible version of API

Beginner webdev here.
Do you have any workarounds to getting this module working in React?


[bug] Change target for tauri dev doesn't work as expected

Describe the bug
Running my main.rs file with cargo run --target x86_64-apple-darwin works but when using yarn tauri dev --target x86_64-apple-darwin I get a bug concerning libtorch:
dyld[64838]: Library not loaded: @rpath/libtorch_cpu.dylib
  Referenced from: <44B79842-D273-3676-9B7C-6C41F485BB99> /Users/santosh/Desktop/code/projects/ImageSearch/PixelDetective/src-tauri/target/x86_64-apple-darwin/debug/PixelDetective
  Reason: tried<EMAIL_ADDRESS>(no such file), '/usr/local/lib/libtorch_cpu.dylib' (no such file), '/usr/lib/libtorch_cpu.dylib' (no such file, not in dyld cache)

My question is not about libtorch but rather how I can fix this through Tauri since cargo run seems to work I am wondering why yarn Tauri dev with the appropriate target doesn't work too. Is there a way to fix that through Tauri?
Please tell me if I should mention any additional details!
Reproduction
Here is my main.rs
// Prevents additional console window on Windows in release, DO NOT REMOVE!!
#![cfg_attr(not(debug_assertions), windows_subsystem = "windows")]

use rust_bert::pipelines::sentence_embeddings::{
    SentenceEmbeddingsBuilder, SentenceEmbeddingsModelType,
};
extern crate redis;
use redis::Commands;

// Learn more about Tauri commands at https://tauri.app/v1/guides/features/command
#[tauri::command]
fn greet(name: &str) -> String {
    format!("Hello, {}! You've been greeted from Rust!", name)
}

#[tauri::command]
fn index() -> String {
    let client = redis::Client::open("redis://localhost/").expect("Failed to connect to Redis");
    let mut con = client.get_connection().expect("Failed to establish connection with Redis");
    let result: Option<String> = con.get("last_updated").expect("Failed to get value from Redis");
    format!("Indexing... {}", result.unwrap_or_else(|| String::from("No value found for 'my_key'")))
}

#[tauri::command]
fn search(name: &str) -> Vec<String> {

    // Set-up sentence embeddings model
    let model = SentenceEmbeddingsBuilder::remote(SentenceEmbeddingsModelType::AllMiniLmL12V2)
        .create_model()
        .expect("Failed to create embeddings model");

    let client = redis::Client::open("redis://localhost/").expect("Failed to connect to Redis");
    let mut con = client.get_connection().expect("Failed to establish connection with Redis");

    // Put query + all sentences in redis in the list to compute embeddings
    let keys: Vec<String> = con.keys("*").expect("Failed to get all keys from Redis");

    let mut sentences: Vec<&str> = vec![name];

    sentences.extend(keys.iter().map(|s| s.as_str()));

    // Generate embeddings
    let embeddings = model
        .encode(&sentences)
        .expect("Failed to generate embeddings");

    // Compute cosine distances
    let query_embedding = &embeddings[0]; // Assuming the first embedding is the query
    let mut distances: Vec<(f32, &str)> = Vec::new();

    for (embedding, sentence) in embeddings.iter().skip(1).zip(sentences.iter().skip(1)) {
        let distance = cosine_distance(query_embedding, embedding);
        distances.push((distance, sentence));
    }

    // Sort by cosine distances in ascending order
    distances.sort_by(|(distance1, _), (distance2, _)| distance2.partial_cmp(distance1).unwrap());

    // Take the top 10 sentences based on distance in ascending order
    let top_sentences: Vec<String> = distances.iter()
        .take(10)
        .map(|(_, sentence)| con.get::<&str, String>(&sentence).expect("Failed to get keys from Redis").to_string())
        .collect();

    top_sentences
}

fn dot_product(vec1: &[f32], vec2: &[f32]) -> f32 {
    let delta = vec1.len() - vec2.len();
    let shortest_vec = match delta {
        d if d < 0 => vec1,
        d if d > 0 => vec2,
        _ => vec1,
    };
    let mut dot_product = 0.0;
    for i in 0..shortest_vec.len() {
        dot_product += vec1[i] * vec2[i];
    }
    dot_product
}

fn root_sum_square(vec: &[f32]) -> f32 {
    let mut sum_square = 0.0;
    for i in 0..vec.len() {
        sum_square += vec[i] * vec[i];
    }
    sum_square.sqrt()
}

  fn cosine_distance(vec1: &[f32], vec2: &[f32]) -> f32 {
    let dot_product = dot_product(vec1, vec2);
    let root_sum_square1 = root_sum_square(vec1);
    let root_sum_square2 = root_sum_square(vec2);
    dot_product / (root_sum_square1 * root_sum_square2)
}

fn main() {
    tauri::Builder::default()
        .invoke_handler(tauri::generate_handler![greet, index, search])
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
}

This is the one causing problems. But it works fine when I run main.rs using cargo run --target x86_64-apple-darwin and replacing main() by:
fn main() {
    let phrase = "nice looking";
    let result = search(phrase);

    for item in result {
        println!("{}", item);
    }
}

Expected behavior
I expected my tauri app to compile smoothly when using yarn tauri dev --target x86_64-apple-darwin but I feel like I am missing something and I am not totally sure to understand if I am doing it correctly. I am unsure of what yarn tauri dev --target x86_64-apple-darwin is actually doing...
Platform and versions
[✔] Environment
    - OS: Mac OS 13.2.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.67.1 (d5a82bbd2 2023-02-07)
    ✔ Cargo: 1.67.1 (8ecd4f20a 2023-01-10)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.2.0
    - yarn: 1.22.19
    - npm: 9.6.6

[-] Packages
    - tauri [RUST]: 1.3.0
    - tauri-build [RUST]: 1.3.0
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.2
    - @tauri-apps/api [NPM]: 1.3.0
    - @tauri-apps/cli [NPM]: 1.3.1

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Svelte
    - bundler: Vite

Stack trace
No response
Additional context
MacOS M2

(thanks for the really extensive report!!)
I feel like this could be the same issue as https://github.com/tauri-apps/tauri/issues/6924 🤔

Hmm I see, he managed to solve it by adding to DLL to his resources if I understand correctly.
I digged a bit more into my problem and found out that the program cannot find the libtorch_cpu.dylib for the architecture I am asking for (it does have it for aarch64). Which is weird given that cargo run --target x86_64-apple-darwin works fine...

simconnect-sdk's build.rs normally links the DLL, and that works fine in typical cases like cargo run. However, something in Tauri breaks that. I'm still trying to figure out what and why, but it's on my TODO list to investigate at some point.

I think that is were the real problem lies

I ended up finding a way to solve the problem by putting those dylib files in the directory they asked for. It is up to you if you want to keep this issue open.

can you show detail way how to " putting those dylib files in the directory they asked for?" , I am building a ios target, i just block with the same error, when start it  shows below error.   thank you very much , if you can show me how you solve this~
Exception Type:  EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: DYLD 1 Library missing Library not loaded: /Users/*/libchatgptenhanced.dylib Referenced from: <CDCA8CD5-E8E6-3776-9A34-87D893A8D9B2> /Volumes/VOLUME/*/chatgptenhanced.app/chatgptenhanced Reason: tried: '/Users/*/libchatgptenhanced.dylib' (no such file), '/private/preboot/Cryptexes/OS/Users/*/libchatgptenhanced.dylib' (no such file), '/Users/*/libchatgptenhanced.dylib' (no such file), '/usr/local/lib/libchatgptenhanced.dylib' (no such file), '/usr/lib/libchatgptenhanced.dylib' (no such file, not in dyld cache) (terminated at launch; ignore backtrace) Triggered by Thread:  0 Kernel Triage: VM - (arg = 0x0) pmap_enter retried due to resource shortage VM - (arg = 0x0) pmap_enter retried due to resource shortage


Table View Edit Columns Dropdown

Adds support for editing columns displayed in a table view. (Vertical ellipses after last column header).

Components Implemented

Overlay Dropdown (can also be used for an account/login menu for example)
Edit Columns View
Updated Checkbox to support labels

TODO: Shift overlay dropdown on screen resize.

Also updated spacing for the Enum.js Java generation class.


Feature/hsu yati khin

Codecov Report

Merging #53 (3df15c3) into master (3a1ece9) will decrease coverage by 0.56%.
The diff coverage is 42.38%.

@@             Coverage Diff              @@
##             master      #53      +/-   ##
============================================
- Coverage     44.30%   43.74%   -0.57%
- Complexity       59       67       +8
============================================
  Files             9        9
  Lines           562      711     +149
  Branches         38       50      +12
============================================
+ Hits            249      311      +62
- Misses          312      399      +87
  Partials          1        1

Flag
Coverage Δ

IntegrationTests
43.74% <42.38%> (-0.57%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/main/java/com/napier/sem/App.java
0.00% <0.00%> (ø)

src/main/java/com/napier/sem/CountryReport.java
45.07% <44.11%> (-0.19%)
:arrow_down:

src/main/java/com/napier/sem/CityReport.java
44.50% <44.95%> (-0.25%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Class Specialtactics\L5Api\Http\Middleware\SnakeCaseInputParameterKeys does not exist

Cloned today, after running the commands in the page i still find this error.
taking a peak at \Specialtactics\L5Api\Http\Middleware\SnakeCase
/**
 * Class SnakeCaseInputParameterKeys
 *
 * This middleware makes sure all incoming request parameters are snake cased for the application
 */
class SnakeCase

so maybe this it's a typo on l5-api repo.
after renaming changing this:
--- a/app/Http/Kernel.php
+++ b/app/Http/Kernel.php
@@ -61,7 +61,7 @@ class Kernel extends HttpKernel
         'signed' => \Illuminate\Routing\Middleware\ValidateSignature::class,
         'throttle' => \Illuminate\Routing\Middleware\ThrottleRequests::class,
         'verified' => \Illuminate\Auth\Middleware\EnsureEmailIsVerified::class,
-        'snake_case' => \Specialtactics\L5Api\Http\Middleware\SnakeCaseInputParameterKeys::class,
+        'snake_case' => \Specialtactics\L5Api\Http\Middleware\SnakeCase::class,
         'check_role' => \Specialtactics\L5Api\Http\Middleware\CheckUserRole::class,
     ];

it worked

Hey there
This is really strange, but I think what happened here was that one of my symlinks to my l5-api local install got deleted and I forgot to update the package in that case. It should be fixed now, can you please update your l5-api package?

That was fast. 🎉

Glad to hear it's fixed :smile:


ikectl should safely handle existing certificates

The command ikectl ca ... certificate ... create should check if the certificate already exists, and handle them safely if so.
Currently, if a certificate already exists, then ikectl complains the certificate already exists, replaces it by an empty file, and then prints an error messages whenever you try to run ca-related commands:<PHONE_NUMBER>320:error:09FFF06C:PEM routines:CRYPTO_internal:no start line:/usr/src/lib/libcrypto/pem/pem_lib.c:694:Expecting: TRUSTED CERTIFICATE
It is difficult to recover from this inconsistent state. Indeed, deleting the certificate with ikectl does not fix the inconsistent state. For example, after running ikectl ca vpn certificate test create twice and then ikectl ca vpn certificate test delete, the inconsistent state persists:
<rak@hades:/home/rak:5021>$ doas ikectl show ca vpn certificate test
ikectl: could not open file test.crt: No such file or directory
<rak@hades:/home/rak:5022>$ doas ikectl ca vpn certificate test create
Generating RSA private key, 2048 bit long modulus
...................
......................................................
e is 65537 (0x010001)
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Common Name (eg, fully qualified host name) [test]:
Using configuration from /etc/ssl/vpn/test-ssl.cnf
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
commonName            :ASN.1 12:'test'
ERROR:There is already a certificate for /CN=test
The matching entry has the following details
Type      :Valid
Expires on    :240928132847Z
Serial Number :1F
File name     :unknown
Subject Name  :/CN=test
<rak@hades:/home/rak:5023>$ doas ikectl show ca vpn certificate test
unable to load certificate
6762873799744:error:09FFF06C:PEM routines:CRYPTO_internal:no start line:/usr/src/lib/libcrypto/pem/pem_lib.c:694:Expecting: TRUSTED CERTIFICATE

<rak@hades:/home/rak:5024>$ ls -lash /etc/ssl/vpn/test.crt
0 -rw-r--r--  1 root  wheel     0B Sep 29 09:38 /etc/ssl/vpn/test.crt

I get bit by this bug annually when renewing expired certificates. Perhaps we could document in ikectl(8) the steps to take for renewing an expired certificate?

Finally had some time to take a look and I think I figured it out.
The reason this fails is that the ca has unique_subject set to yes which causes the Error in your log. I can fix it upstream by modifying ikeca.cnf which will work for all future CAs.
Since you probably want to reuse your already existing CA you will need to fix that by hand. In /etc/ssl/$CANAME/index.txt.attr change unique_subject = yes to unique_subject = no. This fixed the issue for me.

For added context OpenSSL says that unique_subject = no should be the default. The man page also acknowledges the renewal problem you were seeing:

The default value is yes, to be compatible with older (pre 0.9.8) versions of OpenSSL. However, to make CA certificate roll-over easier, it's recommended to use the value no, especially if combined with the -selfsign command line option.

Closing because the fix has landed in OpenBSD and -portable.


set psl as optionnal dependcy

I just set psl as optionaldependencies. This may allow users to not install psl if he do not need to use tld flag.

LGTM. Thank you for your PR :)


Add support for min_length and min_new_tokens generation parameters

Closes #285

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Adjusted the min width for russian language for "Add Channel"

Adjusted the min-width for add option button as mentioned in
"Add channel" should widen as needed #30674
Before:

After:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Hey, I am beginner to using git this two commit is for another PR. I don't know how it was created here.

Hey, I am beginner to using git this two commit is for another PR. I don't know how it was created here.

@userAdityaa you should use separate branches for each PR. Make sure you're on the right branch before making any commits.
Take a look at zulip's git guide.
Here's the section on fixing commits.

Please close this PR as the issue has been fixed

Thanks for the work here, @userAdityaa !


Fixed a typo

Was skimming this interesting project, and found a few typos I wanted to help by fixing.

Thanks!


Setup FreeOTP as a translation project on Transifex

Reported by jfenal on 12 Dec 2013 07:56 UTC
Transifex is the localization platform of choice for Fedora projects and many others.
Transifex handles XLIFF files used by Android for localization, as well as Apple .strings files.
Setting up FreeOTP on Transifex will ensure that localization is available broadly to the Fedora community which has extensive localization experience, in both documentation and software, way beyond the only iOS or Android users.
One project for FreeOTP could handle multiple resources, where Transifex translation memory will also help to ease the work of translators: if the same string is in both apps, the first translated will make it available to the other app.
Proposed resources within the Transifex project:

freeotp-ios
freeotp-android
freeotp-documentation

You will then be able to keep track of languages coverage and completion, and benefit from an extensive and experienced translation community dedicated to open source.

Modified by npmccallum on 13 Dec 2013 14:51 UTC

If Fedora still uses this, I'm in for managing translations externally and setting up a periodic job to sync them. Hopefully it is better than PoEditor (used it at my last job, it was extremely painful and I would not recommend it)


Breakpoints disappeared after starting a debugging session

Environment data
dotnet --info output:
.NET Core SDK (reflecting any global.json):
 Version:   3.1.301
 Commit:    7feb845744

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.16299
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.1.301\

Host (useful for support):
  Version: 3.1.5
  Commit:  65cd789777

.NET Core SDKs installed:
  2.2.402 [C:\Program Files\dotnet\sdk]
  3.1.301 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.19 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.19 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.19 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

VS Code version: 1.47.2
C# Extension version: 1.22.1
Description
Here is a very weird debugger behaviour I encountered today. Recently I upgraded OmniSharp C# extension from 1.21.18 to 1.22.1. Today it was the 1st time I used this newly upgraded version to carry out a debugging session. I have a .NET Core 3.1 Web API project. The breakpoints disappear right after either launching it or attaching to a process! But during debugging, it stops at the statements where breakpoints were set up even they disappeared visually. No current statement indicator show up either like the below one.

When hovering the mouse on a local variable, only type info shows up but no run time value info, like the below one.

All the thing just looks like it isn't in a debugging session at all. But the call stack does show up properly, so I know the execution pauses. Further if double clicking any call in the call stack, it does take me to that call, and the current statement indicator shows up as normal like the below one.

If hovering the mouse on a local variable in that call, its run time value info does show up properly as normal! (like the below one).

I uninstalled and re-install the 1.22.1 version a few times and ended in no difference. So i downgraded this OmniSharp C# extension to 1.21.18, and found that 1.21.18 worked perfectly! Thus I created a simple .NET Core 3.1 Web API project, found that the latest 1.22.1 version worked fine with this simple project! Thus I compared the two projects' .csproj files. Found some difference I thought it might matter, so I commented out some line in my problematic project's .csproj file to make them the same:
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
    <!-- <LangVersion>8.0</LangVersion>
    <AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>
    <UserSecretsId>6ef70598-840f-490b-9d0e-09e9d09956fb</UserSecretsId> -->
  </PropertyGroup>

During debugging, the OmniSharp C# extension's behaviors are normal now. So I thought at least one of those 3 commented out lines caused the issue. To find out which one,  I uncommented each line one by one to see what happened. At the end all 3 lines were uncommented i.e., rolled back completely actually, and the debugger still worked fine. In other words, the ISSUE just disappeared without ANY real changes. The debugger works fine since! Very confused why the debugger has such a weird behaviour.

Do you still have a way of producing the problem? If so, can you grab a debugger log? (see instructions here)

@gregg-miskelly so far haven't yet 👀

This issue came back! I think it might because I restarted my laptop. The VScode version i'm using now is 1.47.3. The bug behaves slightly different & worse. This time, even jumping to one of the call in the call stack, it won't show the current statement indicator anymore. In the screenshot below, There is a breakpoint at Line 64 which is the current statement where the execution paused at. A debugger's log file has been attached at your instruction.

VSCodeDebuggerBreakpointsIssueLog.txt

To make sure, does this path match up with the file name opened in the editor (probably worth comparing the casing also, in case that has anything to do with this):
"C:\AAA.Core\src\AAA.TokenExchange.Api\TokenExchangeV2.API\src\AAA.TokenExchange.WebApi\Controllers\IdentityController.cs"
We probably need to move this issue to VS Code.

Yes, it does match up with the file's path opened in the editor including casing. Yesterday the issue came back. I'm debugging it right now, and the issue disappeared again 😕 without any changes to the project files, apart from some lines in the source logic. (maybe the rebuilding source after those changes made some difference to it, like last time after making some changes to the project file I also rebuilt the source certainly.) Next time when this issue appears again, i'll check out if any source change and rebuilding will make it work.

I'm having this issue right now. It happened to all the 3 different projects i'm debugging ATM. I think last time i was wrong after checking the casing carefully this time. In some places that path's casing does not match. All source files are located under the fold c:\Aaa.Core\src. Last time when i did the text substitution in the previous debugger log file, some casing had been messed up, so it is hard to tell. I've uploaded a new one for the debugger's logging with casing preserved.  There are 2 breakpoints one is at Line 18 in BobTokenMappingStrategy.cs which is working fine ATM, the other is at Line 61 in IdentityController.cs which isn't. You can see in the logging file, the one not working has C:\AAA.Core\src\AAA.TokenExchange.Api\TokenExchangeV2.API\src\AAA.TokenExchange.WebApi\Controllers\IdentityController.cs (Line 32 in the loggging file) which should be C:\Aaa.Core\src\AAA.TokenExchange.Api\TokenExchangeV2.API\src\AAA.TokenExchange.WebApi\Controllers\IdentityController.cs, meanwhile in Line 13 it's c:\Aaa.Core\src\AAA.TokenExchange.Api\....
Interestingly the one working in BobTokenMappingStrategy.cs has both upper and lower casing for the drive too, c:\Aaa.Core\src\AAA.TokenExchange.Api\... (Line 11 in the logging file), and C:\Aaa.Core\src\AAA.TokenExchange.Api\... (Line 285 in the loggging file). Maybe the drive's casing doesn't matter?
Anyway, i don't see where AAA.Core comes from, all all i can see is Aaa.Core provided. BTW as i've experienced, without essential changes, sometimes it just works. This issue just comes back & forth ...
VSCodeDebuggerBreakpointsIssueLog2.txt


PowerToys will not open when Settings is clicked

Microsoft PowerToys version
v0.49.1
Running as admin

[X] Yes

Area(s) with issue?
General, Settings
Steps to reproduce
After running PowerToys as an administrator, click settings in the right click menu in the Taskbar menu.
✔ Expected Behavior
The settings menu to open.
❌ Actual Behavior
Nothing happens. When looking at Event Viewer, this error occurs:
Message: A JSON parsing exception occurred in [C:\Program Files\PowerToys\Settings\PowerToys.Settings.runtimeconfig.json]: * Line 1, Column 2 Syntax error: Malformed token
Invalid runtimeconfig.json [C:\Program Files\PowerToys\Settings\PowerToys.Settings.runtimeconfig.json] [C:\Program Files\PowerToys\Settings\PowerToys.Settings.runtimeconfig.dev.json]

Attached is the .zip file created by the Bug Report feature on PowerToys.
I have tried uninstalling PowerToys using the apps menu, however it pops up with the error message "The feature you are trying to use is on a network resource that is unavailable."
PowerToysReport_2021-11-17-16-42-08.zip
Other Software
No response

@SteelStarling Can you post the content of C:\Program Files\PowerToys\Settings\PowerToys.Settings.runtimeconfig.json here?

I can't attach a .JSON file as an attachment to this, but whenever I try and open the .JSON in something else like notepad it looks like an empty text file. I don't know if I'm doing something wrong or not.

That is strange. That file must not be empty. Also The feature you are trying to use is on a network resource that is unavailable is new to me.
Can you try following things:

put this into PowerToys.Settings.runtimeconfig.json file manually

{
  "runtimeOptions": {
    "tfm": "netcoreapp3.1",
    "framework": {
      "name": "Microsoft.WindowsDesktop.App",
      "version": "3.1.0"
    }
  }
}

uninstalling again, if same message appears, just delete the PowerToys folder manually from program files, (be sure that PowerToys.Settings.runtimeconfig.json file is deleted), and then install PT again.

I tried entering it into PowerToys.Settings manually, and it didn't work. I also tried uninstalling it manually, however I cannot delete PowerRename or VideoConference from the modules folder, as it says they are being used by an open file (I would assume Windows Explorer for PowerRename), even though no PowerToys items are open if I check Task Manager.

I've tried comparing the installationFolderStructure.txt from inside the bug report to what should be the correct one and indeed the json files are reporting different hashes. Something in your system seems to be changing json files, which is surprising.
Are you still able to uninstall PowerToys from the "Add or Remove programs" screen in Windows?
Would you mind:
1 - Uninstall PowerToys.
2 - See if the PowerToys install directory (default: C:\Program Files\PowerToys) is still there. If it is, delete it manually.
3 - Install PowerToys.
Please let us know if this works for you.

I cannot uninstall PowerToys from the Add or Remove programs screen. It says "The feature you are trying to use is on a network resource that is unavailable," mentioning that it can't find the "PowerToysSetup-0.49.0x64.msi" file. As I have already mentioned, I cannot delete everything inside of C:\Program Files\PowerToys. PowerRename and VideoConference in the Modules Folder refuse to be delted, as they are "being used by an open file," despite me having closed every PowerToys item in Task Manager.

mentioning that it can't find the "PowerToysSetup-0.49.0x64.msi" file.

Please see the instructions in #14056 (comment) and #14056 (comment) and see if this helps :) You are able to get the msi file by these steps.

That seems to have fixed it! I managed to uninstall it, and install the newest update, and everything seems to be running smoothly. Thank you for the help, now I can go back to enjoying having PowerToys Run as my search system.


Add "Landlord Payment Status" to criteria to determine if a client is available for matching

This is how a case/client is 'closed'. Note: no such column currently in Evictions v2 sheet.

Any non-empty value would disqualify a client from being able to be matched.

This column does not exist in v1.l


OS X EI Capitan solves "Cannot find module './build/Debug/nodegit'"

Hi everyone,
I'd like show my case here for others reference:
Long long ago I use nodegit v0.1.4 to create a personal project and it worked well. Later node/npm/OSX had been upgraded greatly. Yesterday I accidentally removed all project node_modules and try npm install to rebuild, then the issue appears as title says. I use "n" and tried node versions v0.10.32/v0.10.40/v0.12.7/v4.2, but all unlucky.
Now I just upgrade to OS X El Capitan, the bug disappears for node v0.10.32. Maybe other node versions work too, I'll try soon.
I remember that previously the ./build/Release/nodegit will throw error saying can not load module etc, but now no error thrown and it works well.
Anybody can tell what's wrong and is there a better solution for Yosemite?
Thanks

Can you check your node on Yosemite and show me what is says when you enter:
node -p process.config

I got a similar issue. This is my node -p process.config output:
{ target_defaults:
   { cflags: [],
     default_configuration: 'Release',
     defines: [],
     include_dirs: [],
     libraries: [] },
  variables:
   { asan: 0,
     host_arch: 'x64',
     icu_data_file: 'icudt56l.dat',
     icu_data_in: '../../deps/icu/source/data/in/icudt56l.dat',
     icu_endianness: 'l',
     icu_gyp_path: 'tools/icu/icu-generic.gyp',
     icu_locales: 'en,root',
     icu_path: './deps/icu',
     icu_small: true,
     icu_ver_major: '56',
     llvm_version: 0,
     node_byteorder: 'little',
     node_install_npm: false,
     node_prefix: '/usr/local/Cellar/node/5.1.1',
     node_release_urlbase: '',
     node_shared_http_parser: false,
     node_shared_libuv: false,
     node_shared_openssl: false,
     node_shared_zlib: false,
     node_tag: '',
     node_use_dtrace: true,
     node_use_etw: false,
     node_use_lttng: false,
     node_use_openssl: true,
     node_use_perfctr: false,
     openssl_fips: '',
     openssl_no_asm: 0,
     python: '/usr/bin/python',
     target_arch: 'x64',
     uv_parent_path: '/deps/uv/',
     uv_use_dtrace: true,
     v8_enable_gdbjit: 0,
     v8_enable_i18n_support: 1,
     v8_no_strict_aliasing: 1,
     v8_optimized_debug: 0,
     v8_random_seed: 0,
     v8_use_snapshot: 1,
     want_separate_host_toolset: 0 } }

Note that it doesn't work with nvm use 5 either, but nvm use 4 works.

@Turbo87 could you try again please? Binaries are published now and this should work.

@johnhaley81 Actually I have a similar issue, but that's even worse since nodegit won't compile due to lissh2.
I've added log files in a gist
Here's brief version
npm ERR! Darwin 15.2.0
npm ERR! argv "/usr/local/Cellar/node/5.2.0/bin/node" "/usr/local/bin/npm" "run" "install-deps"
npm ERR! node v5.2.0
npm ERR! npm  v3.3.12
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install-deps: `npm-cache install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install-deps script 'npm-cache install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the project package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm-cache install
npm ERR! You can get their info via:
npm ERR!     npm owner ls project
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/brice/work/the/project/npm-debug.log

{ target_defaults:
   { cflags: [],
     default_configuration: 'Release',
     defines: [],
     include_dirs: [],
     libraries: [] },
  variables:
   { asan: 0,
     host_arch: 'x64',
     icu_data_file: 'icudt56l.dat',
     icu_data_in: '../../deps/icu/source/data/in/icudt56l.dat',
     icu_endianness: 'l',
     icu_gyp_path: 'tools/icu/icu-generic.gyp',
     icu_locales: 'en,root',
     icu_path: './deps/icu',
     icu_small: true,
     icu_ver_major: '56',
     llvm_version: 0,
     node_byteorder: 'little',
     node_enable_v8_vtunejit: false,
     node_install_npm: false,
     node_prefix: '/usr/local/Cellar/node/5.2.0',
     node_release_urlbase: '',
     node_shared_http_parser: false,
     node_shared_libuv: false,
     node_shared_openssl: false,
     node_shared_zlib: false,
     node_tag: '',
     node_use_dtrace: true,
     node_use_etw: false,
     node_use_lttng: false,
     node_use_openssl: true,
     node_use_perfctr: false,
     openssl_fips: '',
     openssl_no_asm: 0,
     python: '/usr/bin/python',
     target_arch: 'x64',
     uv_parent_path: '/deps/uv/',
     uv_use_dtrace: true,
     v8_enable_gdbjit: 0,
     v8_enable_i18n_support: 1,
     v8_no_strict_aliasing: 1,
     v8_optimized_debug: 0,
     v8_random_seed: 0,
     v8_use_snapshot: true,
     want_separate_host_toolset: 0 } }

@bric3 can you update to NodeGit 0.6.0 and try it again?

Also, if you need to actually build
brew install openssl
brew link openssl --force

@johnhaley81 Thanks that worked, without having to resort to force linking openssl
@maxkorp I'm a bit wary to force linking openssl, brew guys had a good reason to make this formula keg only, as it may break other things for osx / xcode.

For reference here's the successful install log : https://gist.github.com/bric3/6a6ad2d598a7b19d9fb2
Cheers guys :)

@bric3 yeah, thats specifically for compiling nodegit. with 0.6.0, we have published binaries out so you don't generally need to compile it.

That's good :)
Thanks again


feat(STD-NET): support netstandard2.0

Issue #, if available:
Description of changes:
Squash/merge commit message, if applicable:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@josecorella and I had a call about testing netstandard2.0.
While we disagreed on much,
we ended up agreeing that because Net Framework 4.8.1
is supported by net standard 2.0 but not 2.1,
if any of our dependencies moved from net standard 2.0 to net standard 2.1,
our CI would fail.
Thus, we do not need CI testing that explicitly tests for net standard 2.0 only targets.
There is a case I had not thought of:
What if a dependency drops net standard entirely?
i.e: Bouncy Castle goes from supporting net standard 2.0, to just net481.
Our CI would all pass, since we test against net6.0 and net481.
But would dotnet give some error or warning that our dependency
conflicted with our target frameworks?
(And would we notice such an error or warning,
if it was just emitted in CI?)

More From @josecorella :

if it removes netstandard2.0 and there is no supported framework equal to what we ship, yes it will fail
because the build command will error with something like “configured version does not match downstream dependency “x.x.x”
or a similar error

At this point, I know the tests pass on my local with net core app 2.0,
and that it is proving difficult to test net standard 2.0 only targets.
I am going to remove the net core app 2.0 test actions,
and then this PR should be good to go.

It turns out I clearly have not run all the projects against net core app 2.0 locally,
as some of the test projects were never modified...


Refactored FlutterBluePlus into a mockable service in order to use bluetooth during testing

The ScooterService now uses a mockable Service (with the same interface as the static service) so it is possible to write tests with programmatically added bluetooth devices.
An example is given in [device_scanning_test.test] which uses custom builder to create bluetooth device mocks

Wait, so does this mean it's no longer possible to access FlutterBluePlus statically? Every use of FlutterBluePlus needs to share an instance of FlutterBluePlusMockable?

Wait, so does this mean it's no longer possible to access FlutterBluePlus statically? Every use of FlutterBluePlus needs to share an instance of FlutterBluePlusMockable?

That's the idea. In order to make it accessible in testing, this is the way. As all calls to this class should be encapsulated in ScooterService, there should be no problem


Specify accepted manifest types

The distribution spec does not explicitly state the types of manifest supported and this PR helps clarify that so that when v1.1 of the spec is tagged, implementations should support all 3 manifest types if they are to claim conformance.
If there is a capability endpoint that calls out the version or manifest types then all three manifest types should be supported - refer - https://github.com/opencontainers/distribution-spec/issues/365
Signed-off-by: Sajay Antony<EMAIL_ADDRESS>

I'm fine with the location, but the phrasing implies that these are special manifests that must always be accepted, while registries may impose limits on other manifests. We went through that with the subject statement on the next line which is how the "otherwise valid" phrasing got added. We probably want some kind of wording that indicates the registry can still reject the manifest, but not because of the media type.

Do you have any recommended working and I'm happy to change as needed @sudo-bmitch
My goal was to ensure that when distribution 1.1 is released we clarify that the registry should support these media types that are tied with v1.1 of image spec without it being listed as an example.
Is there concern if we specify the types that MUST be supported?
Another related issue was https://github.com/opencontainers/image-spec/issues/907

Do you have any recommended working and I'm happy to change as needed @sudo-bmitch

The best I can come up with is adding "otherwise valid" but I'm not thrilled with it. It really feels like we need a common phrasing of things that registries can and cannot use when deciding to accept a manifest.

My goal was to ensure that when distribution 1.1 is released we clarify that the registry should support these media types that are tied with v1.1 of image spec without it being listed as an example.
Is there concern if we specify the types that MUST be supported?

I don't have any use cases myself, at least for index and image. I'm not sure if someone else wants to create a registry that supports the APIs but not the content from OCI.  If that were to happen, I think it's fair for us to say they aren't an OCI conformant registry.
The artifact manifest gets into a gray area since we consider registries (partially?) 1.0 conformant even if they don't support all the features. Each of the conformance tests are also gated behind flags, so we'd need to work out what that looks like for manifest types. In 1.0 tests, we only test for the image manifest support, not even the index manifest, so this will be an expansion in the type of confidence tests we run.

Give yesterday's discussion and opinions of keeping distribution and image spec separate I'm inclined to closing this PR.

nod.. let's close and reopen this requirement at some future point


When should normal routing be replaced with dynamic routing

I see you provide dynamic routing here.
My question is that what is an estimated rule of thumb on when to load routes dynamically vs loading all of them at once.
Do you go to dynamic routes if file size exceeds a size?
Or do you go that way if route numbers exceeds a number?
I didn't asked it on SO because I would get down-vote. sorry.

It's entirely up to you. There is no rule of thumb on these sorts of things.  It obviously can vary a lot.


bug: v3 with icons disabled doesn't show text for  and

Did you check docs and existing issues?

[X] I have read all the which-key.nvim docs
[X] I have searched the existing issues of which-key.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.0
Operating system/version
Ubuntu 24.04
Describe the bug
Before v3, <tab> and <space> would show for each group.
On v3, with icons disabled (see config below), all groups show the correct letter except from space and tab.

This is an old config showing <space> and <tab> in case it helps

Steps To Reproduce
Plugin config:
  {
    'folke/which-key.nvim',
    event = 'VeryLazy',
    opts = {
      icons = {
        rules = false,
      },
      spec = {
        {
          mode = { 'n', 'v' },
          { '<leader><tab>', group = 'tab' },
          { '<leader>b', group = '[b]uffer' },
          { '<leader>c', group = '[c]ode' },
          { '<leader>e', group = 'Tree [e]xplorer' },
          { '<leader>f', group = '[f]ile' },
          { '<leader>g', group = '[g]it' },
          { '<leader>gh', group = '[h]unk' },
          { '<leader>s', group = '[s]earch' },
          { '<leader>u', group = '[u]i' },
          { '<leader>w', group = '[w]indow' },
        },
      },
    },
  },

Expected Behavior
<space> and <tab> should show when icons are disabled.
Health
which-key: require("which-key.health").check()

- OK Most of these checks are for informational purposes only.
  WARNINGS should be treated as a warning, and don't necessarily indicate a problem with your config.
  Please |DON't| report these warnings as an issue.
- WARNING |mini.icons| is not installed
- OK |nvim-web-devicons| is installed

Checking for issues with your mappings ~
- OK No issues reported

checking for overlapping keymaps ~
- WARNING In mode `n`, <gc> overlaps with <gcc>:
  - <gc>: Toggle comment
  - <gcc>: Toggle comment line
- WARNING In mode `n`, <yS> overlaps with <ySS>, <ySs>:

- WARNING In mode `n`, <ys> overlaps with <yss>:

- OK Overlapping keymaps are only reported for informational purposes.
  This doesn't necessarily mean there is a problem with your config.

Checking for duplicate mappings ~
- OK No duplicate mappings found

Log
No response
Repro
No response

That's not the icons. Check the docs for replace


point visitors from old docs site to new docs site

http://dbt.readthedocs.io/en/docs-0.6.0/guide/usage/
these come up on google!

The SEO spirits were kind to us, and these pages are now (mostly) unindexed. Closing, since there's not much else for us to do here


The repo is not in the JugMK organization

I would expect the repo to be part of the JugMK organization in github https://github.com/jugmk

Yes, I have access to the JUGMK organization on github, and I can push the repo there, but I'm having doubts. Should all other JUGMK members who do presentations, become members of this organizations just to be able to push their personal code demos?
I think, this is not ideal. What do you think?
Maybe fork, or starred by JUGMK organization, or a list with links to all demos and presentations done at JUGMK meeetings, those are my ideas...


Error when evaluating expression

i follow the documentation but i have this error:

vue.common.js?e881:1019[Vue warn]: Error when evaluating expression "{
'width': progress.percent+'%',
'height': progress.options.height,
'background-color': progress.options.canSuccess? progress.options.color : progress.options.failedColor,
'opacity': progress.options.show ? 1 : 0
}": TypeError: Cannot read property 'percent' of undefined (found in component: )

@mahdisyazdani need live repo or you can see this example https://github.com/hilongjw/vue-progress-dev/tree/master/client/index

I was having the same problem as @mahdisyazdani in version 0.4.0. I'm using Vue-version v1.0.28. The link to your progress-dev works for me but uses other dependencies, like Vue 2. Now I get this error instead on version 0.4.1. Maybe vue-router related?

@sebastiansson I has tested in my Vue2 and VueRouter2 project, it's work fine.

@sebastiansson Run vm.$Progress.start() when vue app initializing will got this problem, I'll fix it soon.

@sebastiansson @mahdisyazdani  try update vue-progressbar to 0.5.0, I use eventbus instead of to rewrite instance data function

cannot read property '$Progress' of undefined?


How to use fork-awesome fonts with this theme?

I copied example-site content into root folder. And locally running with baseUrl="", (and theme disabled)
I downloaded fork-awesome font into /static folder of root dir.
.static/
|-- css
|   |-- brands.css
|   |-- dark.css
|   |-- fontello.css
|   |-- fork-awesome.css
|   |-- frameworks.min.css
|   |-- gitalk.css
|   |-- github-style.css
|   |-- github.min.css
|   |-- light.css
|   |-- syntax.css
|   `-- toc.css
|-- fonts
|   |-- forkawesome-webfont.eot
|   |-- forkawesome-webfont.svg
|   |-- forkawesome-webfont.ttf
|   |-- forkawesome-webfont.woff
|   |-- forkawesome-webfont.woff2

Fork-awesome.css
@font-face {
  font-family: 'ForkAwesome';
  src: url('../fonts/forkawesome-webfont.eot?v=1.1.7');
  src: url('../fonts/forkawesome-webfont.eot?#iefix&v=1.1.7') format('embedded-opentype'), url('../fonts/forkawesome-webfont.woff2?v=1.1.7') format('woff2'), url('../fonts/forkawesome-webfont.woff?v=1.1.7') format('woff'), url('../fonts/forkawesome-webfont.ttf?v=1.1.7') format('truetype'), url('../fonts/forkawesome-webfont.svg?v=1.1.7#forkawesomeregular') format('svg');
  font-weight: normal;
  font-style: normal;
}
.fa {
  display: inline-block;
  .....
}

Finally adding the stylesheet into layouts/partials/head.html
  <link rel="stylesheet" href='{{ "css/dark.css" | absURL }}' />
  <link rel="stylesheet" href='{{ "css/syntax.css" | absURL }}' />
  <link rel="stylesheet" href='{{ "css/fork-awesome.css" | absURL }}' />

However it doesn't work when using icon class in markdown content

<icon class="fa fa-envelope"></icon>
 Home

Any idea how to make it work ?

Hi @khurshid-alam , I downloaded Fork Awesome and tried your approach—it works on my end. My guess is that you're starting the server with the hugo server command. When you save changes, the server rebuilds the output files, which may overwrite your updates. So, it’s possible that it’s working on your end as well, but the server is overwriting your changes.
If that’s not the case, you could try installing the font via CDN instead:
<link rel="stylesheet"<EMAIL_ADDRESS>integrity="sha256-XoaMnoYC5TH6/+ihMEnospgm0J1PM/nioxbOUdnM8HY=" crossorigin="anonymous">

This also works for me.

@kurt-liao
Yes, it works if I directly add the icon fonts in overview.html. However in markdown post content it doesn't.

As you can see overview has icon fonts (although it is taking a new line ?).
And 2nd post doodle.edc0.com has images(12x12px). I want to replace those images with fork-awesome fonts.
Now I am building with hugo server --minify --disableFastRender.

The main issue is  doesn't work anywhere in post content. How do I enable it ?


Allow for project-specific design

Minimize eigenbranding
Icon, logo, or something comparable
Colors

I'd like to clean up the options at some point but the current implementation is usable and functional.


[Feature]: MLJ integration

Feature Request
I think it could be really cool to have an MLJ integration for SymbolicRegression. As an example of how it could be used, in https://discourse.julialang.org/t/ann-sirus-jl-v1-2-interpretable-machine-learning-via-rule-extraction/100932/2 I compared SymbolicRegression to SIRUS for performing interpretable regression on a basic ML example dataset (Boston housing).

Sure, sounds like a great idea! What methods do we need to write to interface it? And I guess it would go in ext/?

Potentially fixed by #226

Generally, only MLJModelInterface.jl is needed and it is very light. I think making it a hard dependency should be fine.


Added node-coap under Real-time

By submitting this pull request, I promise I have read the contribution guidelines twice and ensured my submission follows it. I realize not doing so wastes the maintainers' time that they could have spent making the world better. 🖖
⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆

Thanks for the suggestion. It looks good, but I'm unfortunately going to pass on this one as it's a bit too niche. If someone needs this, they can just search for it. The intent of the list is to gather best resources for something most developers will need.


Bundle asUInt ignores structural width

It appears bundle packing behavior ignores the structural (defined in the Bundle def) width, at least for bundle literals. When defining a bundle literal, the .asUInt returns a different value depending on if the literal components have an explicitly specified width or not. See example below.
Potentially related to FIRRTL (I think?) not having a concept of a bundle type?

Type of issue: bug report

Impact: unknown

Development Phase: request
Other information

Discovered during implementation of #1280
If the current behavior is a bug, please provide the steps to reproduce the problem:
This example reproduces the behavior: https://scastie.scala-lang.org/MYZTNgqTQdOrJuUDiuV1vw
import chisel3._
import chisel3.experimental.BundleLiterals._
import chiseltest._

class LongBundle extends Bundle {
  val a = UInt(32.W)
  val b = UInt(32.W)
}

class Foo extends MultiIOModule {
  val bun1 = (new LongBundle).Lit(_.a -> 0xBE.U, _.b -> 0xEF.U)
  val bun2 = (new LongBundle).Lit(_.a -> 0xBE.U(32.W), _.b -> 0xEF.U(32.W))
  chisel3.printf("bun1=%x, bun2=%x\n", bun1.asUInt(), bun2.asUInt())
}

RawTester.test(new Foo) { c =>
  c.clock.step(1)
}

What is the current behavior?
The value of bun1 is different from bun2, as shown by the print:
bun1=0beef, bun2=0000000be000000ef
bun1=0beef, bun2=0000000be000000ef

What is the expected behavior?
Both should be equal, namely bun1 should be be000000ef (optionally with leading zeros)
Please tell us about your environment:

Scastie, but reproduces on Windows.
What is the use case for changing the behavior?

I think the main problem comes from
https://github.com/freechipsproject/chisel3/blob/ac3ad980dd2e5abd43f3b36ecb1fb95b626aa398/core/src/main/scala/chisel3/Aggregate.scala#L539
In this case, problem is that we actually create a lit with unknown width and didn't check the width equality:
https://github.com/freechipsproject/chisel3/blob/ac3ad980dd2e5abd43f3b36ecb1fb95b626aa398/core/src/main/scala/chisel3/Aggregate.scala#L543
litArg fall back to unknown width, which will ask for a minimal width to create the LitArg
So a quick fix is to get width from field reflectively, if the !litArg.widthArg.known, but more question comes. if it's originally a unknown width and need to be infered by FIRRTL?

Here are 3 methods to do this job:

During elaborating, change behavior at
https://github.com/freechipsproject/chisel3/blob/9dda7f51dc7e515cec6e1d3445370df607652958/core/src/main/scala/chisel3/Data.scala#L325
"reflecting" width of Data, bind a new ElementLitBinding to Data.
like #1513 did, only fix bundle Lit method.
fix this at InferWidth FIRRTL transform.

Which method one should I adopt? I personally prefer 1 and 3.

There's definitely a bunch of quick fixes for this, but what would a proper fix look like?
Would #921 solve this cleanly, and is it worth reviving that effort?


a lot of "ArrayIndexOutOfBoundsException: 0" found by PR #252

All of them should be caused by calling IndexScanner.DUMMY_KEY_START.get(i)

@gfl94 Do you have bandwidth to check this issue? Since it happens in statistics part.


wip: docs

Proposed changes
Initial update of the docs
Types of changes

[x] 📚 Documentation Update (if none of the other choices apply)

Checklist

[x] 👀 I have read the CONTRIBUTING doc
[x] ✅ Lint and unit tests pass locally with my changes
[x] 🧪 I have added tests that prove my fix is effective or that my feature works
[x] 📚 I have added the necessary documentation (if appropriate)
[x] 🔀 Any dependent changes have been merged and published in downstream modules

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

Comparison is base (b094895) 100.00% compared to head (8caad30) 96.79%.
 Consider uploading reports for the commit 8360c28 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##              main     #891      +/-   ##
===========================================
- Coverage   100.00%   96.79%   -3.21%
===========================================
  Files          103       67      -36
  Lines          914      812     -102
  Branches       160      146      -14
===========================================
- Hits           914      786     -128
- Misses           0       16      +16
- Partials         0       10      +10

see 135 files with indirect coverage changes

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


Ubuntu docker gcc issue

Due to recent changes in aggregators needing gcc10+ version to compile, the following command:
https://github.com/binpash/pash/blob/3f5fcb7fefd05f92bebcfb5fd0848df7a05c4b3a/scripts/distro-deps.sh#L31
fails to execute (due to missing software-properties-common package which is about ~70Mb).
Can we do something about this without having to install this additional package?

I think this is not relevant anymore (aggregators are in a different repo and not used)


[Testerina] validate test:config annotation and attributes

Description:
Annotation attributes should be validated using the annotation extension when that is merged. The validation should include following.

Duplicate annotations.
Duplicate attribute.
Invalid values for attributes. etc.

Annotations:

@test:BeforeSuite, @test:AfterSuite, @test:BeforeEach,  @test:AfterEach
hese Should be allowed to duplicate and is already allowed.

@test annotation can not be duplicated for the same function

Annotation attributes:

enable: {true | false} This attribute needs validation

This is fixed in the current releases. Hence, closing.


[BUG]: Cannot read property 'ScaleAspectFill' of undefined

Version
6.4.3
What platforms are you having the problem on?
Android
System Version
Android 11
On what device are you experiencing the issue?
Real device
Architecture
Old architecture
What happened?
I just bumped React-Native-Video v5.2.1 to v6.4.3 to fix some issues regarding AGP 8 for React Native 0.73. While testing on debug the  component behaves with no issues but as soon as I build a production bundle I start to get a TypeError on all screens that renders it.
`TypeError: Cannot read property 'ScaleAspectFill' of undefined

Reproduction
No response
Reproduction
It was working fine on React-Native v0.72.6 and React-Native-Video v5.2.1 and I am rendering the component on the screen as:
<Video
  ref={videoRef}
  resizeMode="cover"
  repeat
  source={{ uri }}
  onBuffer={e => console.log('Buffer', e)}
  onError={e => console.log('Error', e)}
  style={styles.video}
/>

FIXED
For any future reference, apparently this issue is related to malformed node_modules and can get React-Native-Video to get corrupted.
I did a clean install on both Android and React-Native side and this issue stopped happening.


Chore(migration commands): added sequelize migration commands

What does this do?
This contains migration commands for migrating up and reverting a database model.
How to test?

Pull this branch
Run npm run migrate:up to migrate up
Run npm run migrate:down to migrate down

Task linked: CU-3xgy4jp Migration commands


Add asset page tabs to schema

Similar to https://github.com/carbon-design-system/carbon-platform/issues/555 for libraries, each asset in the schema needs keys that determine which content is available to fetch and render as page tabs. It could possibly be a docs or documentation object that belongs to each asset. For example,
assets:
  accordion:
    name: Accordion
    documentation:
      usagePath: https://github.com/carbon-design-system/carbon-website/blob/main/src/pages/components/accordion/usage.mdx
      stylePath: /docs/style.mdx
      codePath: /docs/code.mdx
      accessibilityPath: /docs/accessibility.mdx

Acceptance criteria

[ ] Asset schema is updated to support documentation
[ ] The intent of each asset documentation page is specified in the schema

Dependents
There will be follow-on issues to wire up indexed documentation paths to page tabs, and to provide markdown templates for all four documentation pages.

Hey team! Please add your planning poker estimate with ZenHub @jdharvey-ibm @alisonjoseph @francinelucca @andreancardona

@francinelucca this comment might be more for https://github.com/carbon-design-system/carbon-platform/issues/793, but can we ensure that absolute paths can work? For example, the usage docs for accordion will eventually need to live in here somewhere:
https://github.com/carbon-design-system/carbon/tree/main/packages/styles
But in the mean time, until that happens, the indexed accordion here:
https://github.com/carbon-design-system/carbon/blob/main/packages/styles/carbon.yml
Will want to point to the legacy documentation that currently lives in Carbon website…

https://github.com/carbon-design-system/carbon-website/blob/main/src/pages/components/accordion/usage.mdx
https://github.com/carbon-design-system/carbon-website/blob/main/src/pages/components/accordion/style.mdx
https://github.com/carbon-design-system/carbon-website/blob/main/src/pages/components/accordion/code.mdx
https://github.com/carbon-design-system/carbon-website/blob/main/src/pages/components/accordion/accessibility.mdx

Then, in the future, when Carbon website markdown is migrated to it's desired destination (in the styles package), then we can update the carbon.yml paths there to be relative.

@alisonjoseph @jdharvey-ibm 👆 FYI that above comment on absolute paths. Any concerns with this? We're pulling remote content from carbon-website for our static pages, so as a stop-gap until we move those files to the carbon repo, we might want to pull remote content for asset documentation too.

so if the absolute url is https://github.com/carbon-design-system/carbon-website/blob/main/src/pages/components/accordion/usage.mdx , we query the github api with GET /repos/{owner}/{repo}/contents/{path}, so -> GET /repos/carbon-design-system/carbon-website/contents/src/pages/components/accordion/usage.mdx , would we be calculating these values dynamically? (repo, owner, path) seems a bit iffy.
unless the absolute path is the raw content (https://raw.githubusercontent.com/carbon-design-system/carbon-website/main/src/pages/components/accordion/usage.mdx)? IDK if that'd work tho'

If not using the raw content, if using the absolute URL, could we parse it to strip out the protocol, add in the /repos, and transform it in the query we need for GitHub's API?

yeah, we'd have to assume it is a correct url with the https://{host}/{org}/{repo}/blob/{branch}/{path} format and we'd do something like:
const host = url.host
const pathnameChunks = url.pathname.split('/)
const org = pathnameChunks[1]
const repo = pathnameChunks('/')[2]
const path = pathnameChunks.slice(5, pathnameChunks.length).join('/')

and then use that to construct to query
are we ok with that?


Axe version is hardcoded as 3.2.2 instead of inferred from input/environment

getAxeToolProperties currently hardcodes axe version 3.2.2, but it would be more correct for it to infer the axe version from the input file (for v2 input) or from environment data (for raw input).

:tada: This issue has been resolved in version 2.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Create a Custom Message of ROS type and Not a Protobuffer

I want to create a custom message bla.msg type that can usually be made in a ROS catkin workspace, and compiled into an easy to include header file. How would I do this with Apollo?

I am also wondering this.  How to compile a custom msg in apollo that is not a proto msg.
How to add a my_custom_message.msg to the bazel BUILD file and so that I can include these custom classes in the Apollo .cc files

Update: Compiling msg files into c++ header files with catkin outside of docker container, then copying the header files into apollo and including them worked.

I has same issue. I need to use inside apollo module ackermann_msgs/AckermannDrive ROS message.
I copied from my own ROS kinetic installation folder ros/include/ackermann_msgs/.h files to bazel-out/local-dbg/bin/external/ros/_virtual_includes/ros_common/ros/include/ackermann_msgs/.h and I got this error from bazel-build:

ERROR: /apollo/modules/canbus/vehicle/new_vehicle/BUILD:35:1: undeclared inclusion(s) in rule '//modules/canbus/vehicle/new_vehicle:new_vehicle_controller':
this rule is missing dependency declarations for the following files included by 'modules/canbus/vehicle/new_vehicle/new_vehicle_controller.cc':
'bazel-out/local-dbg/bin/external/ros/_virtual_includes/ros_common/ros/include/ackermann_msgs/AckermannDrive.h'

What I missed?

Oh I got! My fault. I have copy to /home/tmp/ros/include directory inside docker. Have I cope content of ROS "share" folder to apollo docker  /home/tmp/ros/share directory?

Have I cope content of ROS "share" folder to apollo docker /home/tmp/ros/share directory?
No, just copy the header files to /home/tmp/ros/include will be ok.

@DevMohamedMI

It works. After adding header files to /home/tmp/ros/include I can include them with
#include "ackermann_msgs/AckermannDrive.h".
An issue can be closed I think.

I have to build with catkin_make package with my messages, copy them  in directory /home/tmp/ros/include and type in bash source ~/catkin_ws/devel/setup.bash.
It works until container was relaunched.

@gladijos were you able to resolve your issue?

How to make python script works with customized msg ? @natashadsouza

Closed for now, Please reopen if anyone has updates on this thread


JSON Schema Validation: Exception thrown when object contains multiple values with same name

Environment: VS2022, Windows 10, .Net 6.0,
Version: json.schema.dll <IP_ADDRESS>, 3.2.0 (found with 3.1.1, upgraded, confirmed exists with 3.2.0.)
If I try to validate a data file with the same value in an object twice, the validation throws an exception. The schema is written a little strangely so it's possible that's related.
Example:
{ "code": "123", "code": "456" }
I have an older tool with .Net 4.8 using version <IP_ADDRESS> and it doesn't work great (output is not highly intelligible) but it's not throwing an exception.
Note - I realize that this isn't legal JSON, I'd just like it to not throw an exception and instead have some vaguely intelligible output.
Attached files:

data.json.txt - JSON data file with "code" duplicated near the bottom.
schema.json.txt - JSON schema file. It does that weird thing with min/max because one of the validators we use doesn't deal with things named "type" properly.
Exception.txt - exception thrown
v1_10_6_0.txt - output from validation with json.schema.dll <IP_ADDRESS>.

Exception.txt
data.json.txt
schema.json.txt
v1_10_6_0.txt

The specification addresses this in section 4.2.1

Since an object cannot have two properties with the same key, behavior for a JSON document that tries to define two properties with the same key in a single object is undefined.

This isn't exactly a bug.  JSON itself doesn't regard duplicate keys as an error, but many parsers do, including System.Text.Json's JsonObject.
Unfortunately JsonObject doesn't throw an exception until you try to access the data.  It does this because of an internal delayed parse.  (Please see my open issue https://github.com/dotnet/runtime/issues/71784.)
All of that said, JSON Path and JSON Logic decree that evaluation-time errors MUST NOT occur, which means I had to create an extension method for accessing objects to account for the potential for duplicate keys, wrapping the access in a try/catch.  The problem is that running an operation through a try/catch is generally quite expensive, especially when that operation is object member access.
I'd prefer not to add that overhead to JSON Schema.

I have an older tool with .Net 4.8 using version <IP_ADDRESS> and it doesn't work great (output is not highly intelligible) but it's not throwing an exception.

That version is based on JsonElement rather than JsonNode.  This is probably the difference that you see.

I have to admit I'm only understanding maybe 25% of what you said a couple comments up. Far from my area of expertise (not that I'm sure I have an area of expertise.)
My problem is I'm not sure how to handle it up at the application level and get it to output something reasonable, and I assumed you were "close" enough to have a better idea of what happened.
Unless you have a better suggestion, I guess I'll just put in a catch for the annoyingly general exception type ("ArgumentException") and hope for the best. This is just a tool for our testing team anyway.
Something like:
catch(System.ArgumentException sae)
{
  if (sae.Source == "System.Text.Json")
  {
       Console.WriteLine($"{dataFileBaseName}\tFail - possibly a duplicate key named \"{sae.ParamName}\". Exception \"{sae.Message}\"");
  }
  else
  {
      Console.WriteLine($"{dataFileBaseName}\tException ArgumentException \"{sae.Message}\"");
  }
}

I agree that it's not the ideal solution, but I think a single overarching try/catch will perform better in the end.
If you have control of the data you're validating, I suggest trying to fix the duplicate keys issue at the source before you validate it.
If the data is coming from an external source, having a pre-process step of iterating over the data might be able to ensure that it's in a good state.  That shouldn't be very expensive.
In either case, I think failing earlier will give you a better idea of what's going on.

The tool I'm building is for our test team to validate data coming in from vendors in our test environment, so I just need to be able to say something vaguely sensible for them to bounce it back to the vendor development team. .
I'm running against my "test library" of around 50,000 files and only found one instance of it (and that was probably a manual edit error.) It just seemed like being a "good user" to mention it.


Issue#56: revised tests

Revised tests based on notes. The test on Line 18 returns a KeyError: 'version'.

Reviewing this on my phone so will have to run it later, but it looks like it's off to a good start.
KeyErrors are self explanatory. The issue you are running into is that you are passing 'version' into a dict that is just {str: list}.
The schema's keys should be strings, not a string type. There's a difference. Right now the key is just str: list but it should be e.g. 'version': list and so on. Remember what you're testing, which is that each key in the output json returns the type we want.

The schema's keys should be strings, not a string type. There's a difference. Right now the key is just str: list but it should be e.g. 'version': list and so on.

I think I get what you mean. Have been trying to tease out the structure for schema (a dictionary of dictionaries, with list value?) but unable to really get at that and wasn't able to find it while looking through the models info. (I see how it is first set up in model_api, but unclear how it becomes so much more complex). Need to understand the full details there to revise how it's set up in the test... have tried printing it out and using the console, will try again tomorrow.


add diagram for spa and aad auth/z flow

@yaweiw,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@aovechki

Codecov Report

Merging #106 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   44.35%   44.35%
=======================================
  Files          47       47
  Lines         868      868
  Branches       88       88
=======================================
  Hits          385      385
  Misses        446      446
  Partials       37       37

Continue to review full report at Codecov.

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


Unable to publish a message to Emqttd

I am publishing a message to a topic via paho python client, but when I send a message via Django server by hitting an api of message it get stuck in paho.publish method of python client in publishing a message but after sometime in metrics it does not increase the value of  qos1/sent and qos1/received
EMQTTD version is 1.1.3
when I do the same thing via emqttd benchmark, benchmark returns connack timeout for each client publishing a message however count of client is 200 in benchmark so setting 1 for client it able to send message but on other side all subscribers get exit via tcp_closed

please start the broker in console mode to check what's happened.
.bin/emqttd console

@huangdan  I got this earlier, the reason is too large number of connection in a single machine does not allow another clients to subscribe and publish a message in same machine.
What I did is connected another machine and make a cluster of machines to publish a message via another machine.


feature-aws-quotas

Code to automatically setup AWS EC2 spot and on demand quotas for g4dn instances.  Had to use lambda backed cloudformation resources as cloudformation doesn't natively support the quota resource
Quota Request works in the stack: -

It creates the quota requests: -

Which create the support tickets: -

CloudWatch logs from Lambda: -

Updating the stack works without creating another quota request: -

Delete of stack works, without creating another quota request: -

Lambda logs: -

resolves https://github.com/aws-deepracer-community/deepracer-on-the-spot/issues/80


Make Project Compatible With Rust Analyzer

The current project structure does not work with rust analyzer.  This makes it hard to develop using various open-source IDEs such as emacs and neovim.

Today's discussion, though no new progress on this:
Option 1: revert to the 1.3.2 version of the ee-966 contract that remains in the workspace:
https://github.com/casper-network/casper-node/blob/release-1.3.2/smart_contracts/contracts/test/ee-966-regression/src/main.rs
Option 2: Alternatively, we could remove the contracts from the workspace and instead build them, externally, perhaps with cargo-task.

https://github.com/casper-network/casper-node/pull/2193


controlled_frame vs tcp_frame?

Looking at the message definition(s) a bit closer, it appears CartesianTrajectory has a controlled_frame:
https://github.com/UniversalRobots/Universal_Robots_ROS_cartesian_control_msgs/blob/efd9900092aaa2ce030790138ee870a8b5d6a85a/msg/CartesianTrajectory.msg#L4
while the feedback section of FollowCartesianTrajectory defines a tcp_frame:
https://github.com/UniversalRobots/Universal_Robots_ROS_cartesian_control_msgs/blob/efd9900092aaa2ce030790138ee870a8b5d6a85a/action/FollowCartesianTrajectory.action#L22
IIRC these refer to the same entity, so I'm wondering whether tcp_frame is a remnant from before we renamed the field to controlled_frame or there is some other rationale.

FYI: @dave992

@fmauch: any idea?

Looking back at the design document it seams that we indeed missed to rename that.

With #7 (and #8) merged, I'll close this.
thanks @fmauch.


Remove duplicate declaration of gson

Some problems were encountered while building the effective model for io.netty:netty5-codec-http2:jar:5.0.0.Alpha6-SNAPSHOT
'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.google.code.gson:gson:jar -> duplicate declaration of version (?) @ line 122, column 17
It is highly recommended to fix these problems because they threaten the stability of your build.
For this reason, future Maven versions might no longer support building such malformed projects.

@qiyuey Please sign the CLA: https://netty.io/community.html

@qiyuey Please sign the CLA: https://netty.io/community.html

Done

@qiyuey thanks a lot!


Delete redundant branch

When https://github.com/nhsuk/profiles/pull/43 has been merged this branch https://github.com/nhsuk/ci-deployment/tree/feature/profiles-with-db can be deleted

Done


Add Load/Save feature to Pam's

Adds two new channel actions: Save and Load.  The application has 6 banks for saving channel settings. These banks are shared across all channels, making this a (relatively) easy way to copy settings from one channel to another, or to save presets for different pieces and load them during a performance.
Saving/loading channels was causing issues with memory usage, so the number of channels was kept intentionally small. I tried with 8 channels initially, but was consistently getting memory allocation errors after loading/saving a few times.  This is mitigated with manual gc.collect() calls, but we're really pushing against the limits here.
Save
Saves the channel's current settings to the selected bank.
Load
Loads the settings from the given bank and applies them to the current channel.
Misc Changes

reduced max BPM to 240; 300 BPM was consistently not able to keep up with realtime
very minor code refactoring/cleanup

I haven't tested it on a clean module; mine is very much in an in-development state as a result of all the various MRs.
I'd appreciate a second data point just to make sure I haven't missed anything. The changes should be low-risk, but a second person testing it would be appreciated.


add Docker Image Builder steps

Added icons and categories + renamed the directory. Will add the logos in roi next.


Transaction pool might panic if tags are pruned but no hashes provided on prune

Maybe it is unavoidable, but it is still might be an attack vector for some usage scenarios
Every time transaction is imported its hash is placed in `ready` map and tags in `provided_tags`;
Every time transaction is removed from the queue we remove the hash from `ready` map and from `provided_tags`;
Hence every hash retrieved from `provided_tags` is always present in `ready`;
qed

Can you elaborate on the case that you have in mind? This proof is internal to the "ready" part of the pool, the invariant is that we never put a hash to provided_tags (tags to hash mapping) without putting the same hash to ready (hash to transaction mapping). I don't see how it could ever break.
We really don't need to provided hashes of transactions when pruning, this is only done to temporarily ban the hashes and prevent them from being re-imported to the pool in some scenarios. We get the hashes from the aforementioned mapping given provided_tags.

Well I triggered this error during benchmarks using just public api, I'll post a failing test

See https://github.com/paritytech/substrate/compare/nv-txpool-panic-2?expand=1
cargo test -p substrate-transaction-graph
if hash is also passed in prune_tags, then no panic


Add websocket support for jenkins console. - [closed]

In GitLab by @wknet123 on Oct 9, 2017, 02:43
Merges dev-enable-websocket -> dev

In GitLab by @wknet123 on Nov 13, 2019, 10:05
closed


union_linestring cleanup realated to #49

I found that the core bug was a use of cbind that should have been a left_join. This also introduces some testing and brings back a deprecated function with identical behavior to the old one.
Note that I removed one sf::st_drop_geometry and switched one to an hyRefactor:::drop_geometry.
@mikejohnson51 can you make sure I'm not being dumb here?

Running this version of the package for region 06a I am getting what I expect now. So that's good.

Codecov Report

Merging #50 (0cdee61) into main (76bdbb6) will increase coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Current head 0cdee61 differs from pull request most recent head e38282e. Consider uploading reports for the commit e38282e to get more accurate results

@@            Coverage Diff             @@
##             main      #50      +/-   ##
==========================================
+ Coverage   89.28%   89.30%   +0.01%
==========================================
  Files          11       11
  Lines        1587     1589       +2
==========================================
+ Hits         1417     1419       +2
  Misses        170      170

Impacted Files
Coverage Δ

R/aggregate_network.R
98.20% <100.00%> (ø)

R/catchment_geometry.R
65.97% <100.00%> (+0.47%)
:arrow_up:

R/reconcile.R
88.70% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

This looks correct to me. I think there are some refactoring (hehe) of the code to separate some concerns but this works!


Zsh auto completion for pull request not populating

It looks from the hub completion file that once you get to hub pull-request you should get completion for other parameters like -m and -h but I don't seem to get anything. No errors, just no further completions.
$ zsh --version
zsh --version
zsh 5.0.7 (x86_64-apple-darwin14.0.0)

$ hub --version
hub --version
git version 2.3.0
hub version 2.2.0-g217f4b5

I get other auto completes, so the completion is mostly working but pull request would be awesome to get fully working :)

Sorry that our completion is a mess right now. We will be working on making it better.
In the meantime you could share whether you use any zsh configuration packages such as oh-my-zsh, and if so which plugins do you load from it. The completions and aliases from these projects can negatively affect hub's own completions.
I trust that you've installed hub via Homebrew?

I installed head from homebrew after removing my previous Hub. I'm acutally leveraging the vanilla install of yadr so it has a buttload of other completions.
However I did a check to see if there were any hub* completion files and there is only one, and I made sure to overwrite it from the provided hub completion file in the repo so ¯_(ツ)_/¯

There is currently just no support for this in the Zsh completion.
It provides the description, but no completions.
Any improvements to this should be based upon my simplification from https://github.com/github/hub/pull/788.

Sorry you had issues, @devshorts. Closing in favor of the referenced PR to improve zsh. It's a dup of our other zsh issues.


Change testImage based on GOARCH

Changes the test-image to be based off GOARCH, so that tests that use it will run on other platforms.
Signed-off-by: Christopher Jones<EMAIL_ADDRESS>

Codecov Report

Merging #1329 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1329   +/-   ##
=======================================
  Coverage   35.56%   35.56%
=======================================
  Files          23       23
  Lines        2874     2874
=======================================
  Hits         1022     1022
  Misses       1627     1627
  Partials      225      225

Continue to review full report at Codecov.

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

Looks like the CI had issues creating the btrfs snapshots for one of the tests
TestBtrfs/RemoveDirectoryInLowerLayer (0.68s)
    	issues.go:70: Check snapshots failed: "/tmp/snapshot-suite-Btrfs-054615590/root/active/5" not found

@tophj-ibm i bumped it.  I nothing this test failed the other day an another PR, we will have to take a look at it and see why its flaky

thanks @crosbymichael
I found out that 32-bit arm and i386 don't have alpine images, so they can't run these tests at all, not sure how big of a deal that is.
Also not sure if / where I should throw an error, right now it happens when getting the image.

@tophj-ibm i think its fine at pull time

I found out that 32-bit arm and i386 don't have alpine images, so they can't run these tests at all, not sure how big of a deal that is.

uhhh, can you elaborate? https://hub.docker.com/r/i386/alpine/ and https://hub.docker.com/r/arm32v6/alpine/ (they're not 100% official yet, so trollin/alpine doesn't include them, but they do exist)

@tianon nvm me, I can't search correctly. (/u instead of /r)
Do arm32v6 images work on a arm32v7 device?

Yes, they should indeed.

I did not know about these architecture namespaces on the hubs, good to know.
LGTM

@estesp SEE! no one knows these namespaces exist, its not just me

@crosbymichael definitely @dmcgowan is more culpable as former distribution team member; Sad.

@estesp agreed, not sure how I missed that.
appveyor is failing due to some connectivity issue. It had previously passed so I am going to merge this.


Add BBCT token

Official announcement:   https://www.bbct.cc/
Project team background:
The BBCT team is composed of elites in the financial industry, technical innovation experts and well-known corporate executives. It is an experienced and powerful team. In addition, a lot of work has been carried out in the early stage of the project, with outstanding achievements. Daniel Lackey, CEO, PhD of Leeds University, has rich experience in financial industry management, and has worked in international investment banks for many years, including senior management positions in institutions such as Royal Bank of Scotland. . Robin Tay, CTO, Master of Computer Science, Massachusetts Institute of Technology, core technical consultant of several listed groups, participated in the development of multiple software open source projects. In recent years, he has devoted himself to the research of block application technology.
Project basic information:
BBCT is a blockchain financial ecosystem with a composite business model and one-on-one application. BBCT is an ecological platform based on the financial industry. It is the world's first and the world's top technology research and development. It covers digital payment solutions, real-time seamless exchange and transaction payment in all fields related to the financial ecology. It is committed to building the world's first truly complex business. The model and landing are applied to the integrated blockchain financial ecological APP. On the basis of peer-to-peer network technology, build a new form of global finance based on blockchain and smart contract technology.As a decentralized blockchain platform, BBCT uses blockchain as a trusted foundation, combined with sandbox isolation mechanism and network isolation mechanism, so that digital assets can be confirmed, limited in number (scarce), tradable and consumable . Let everyone have digital assets and realize future wealth. So as to build the Internet into a smart economic ecosystem.
Recommended Gas Limit (For ERC-20 project teams) for transaction: 60,000

欢迎在社区中推荐用户使用 imToken 2.0 管理资产。