text:
Adjective order skill

If your PR is related to a contribution to the taxonomy, please, fill
out the following questionnaire. If not, replace this whole text and the
following questionnaire with whatever information is applicable to your PR.
Describe the contribution to the taxonomy

Currently, the model appears to do poorly explaining the common order of multiple cumulative adjectives preceding a noun, which is governed by the OSASCOMP rule: Opinion < Size < Age < Shape < Colour < Origin < Material < Purpose. The rule explains why  "little green men" is more common (size < colour) than "green little men". The latter is grammatically correct, but most native speakers would detect it as odd, without even consciously applying the adjective phrase order rule.
A rare exception to the rule is "big bad wolf". OSASCOMP would suggest "bad big wolf" (opinion < size). In this case, another linguistic rule takes priority: ablaut reduplication. If subsequent words are (nearly) identical, except for the vowel, there is a strict precedence of I < A < O. This is why we say "tick-tock", "chit-chat", and "splish-splash-splosh", rather than "tock-tick", "chat-chit", or "splosh-splash-splish" (except perhaps in some of Dr. Seuss's tongue twisters.)
The examples suggest that, in simple cases, the model has no problem identifying the common ordering. The model also demonstrates its knowledge of the general rule for adjective order.
Asked to clarify the adjectival order in the anomalous "big bad wolf" however, the model is clearly producing nonsense ('"big" is more specific, so it follows "bad"'). Likewise, when confronted with longer strings of adjectives, the model is evidently lost.
This contribution aims to improve the model's explanation of the common ordering in English adjective phrases, as well as the well-known anomaly "big bad wolf".

Input given at the prompt

  [See below for several prompt and response pairs]

Response from the original model

>>> Explain the order of the adjectives in "bad little wolf"                                                    [S][default]
╭────────────────────────────────────────────────── merlinite-7b-Q4_K_M ───────────────────────────────────────────────────╮
│ In English, adjectives typically follow this order: opinion, size, age, shape, color, cause, origin, material, purpose,  │
│ and then finally, the possessive case. This sequence is called the "string order" or "adjective phrase order." Let's     │
│ examine your phrase "bad little wolf."                                                                                │
│                                                                                │
│ 1. Opinion: "Bad" is an opinion adjective, which means it expresses the speaker's viewpoint or evaluation.               │
│ 2. Size: "Little" is a size adjective, which describes how big or small something is.                                    │
│                                                                                │
│ In this case, both opinion and size adjectives are used, but "little" is more specific, so it follows "bad." The order   │
│ "big bad wolf" is also grammatically correct, but it conveys a different meaning.                                        │
│                                                                                │
│ Here's a sentence using all the adjective types in their correct order:                                                  │
│                                                                                │
│ Example: "A big, red, plastic, American, toy, shop-bought, car."                                                         │
│                                                                                │
│ 1. Opinion: big (larger)                                                                                │
│ 2. Size: big (large)                                                                                │
│ 3. Age: new (not aged)                                                                                │
│ 4. Shape: plastic (not metal, wood, etc.)                                                                                │
│ 5. Color: red (not green, blue, etc.)                                                                                │
│ 6. Cause: toy (not tool, weapon, etc.)                                                                                │
│ 7. Origin: American (made in America, not China, Japan, etc.)                                                            │
│ 8. Material: shop-bought (not handmade)                                                                                │
│ 9. Purpose: car (not plane, boat, etc.)                                                                                │
│ 10. Possessive case: your (not my, his, her, etc.)                                                                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────── elapsed 134.733 seconds ─╯
>>> Explain the order of the adjectives in "bad black wolf"                                                     [S][default]
╭────────────────────────────────────────────────── merlinite-7b-Q4_K_M ───────────────────────────────────────────────────╮
│ The order of adjectives in English follows a specific sequence, often referred to as the "string order" or "adjective    │
│ phrase order." This sequence is as follows: opinion, size, age, shape, color, cause, origin, material, purpose, and then │
│ finally, the possessive case. Let's examine your phrase "bad black wolf."                                                │
│                                                                                │
│ 1. Opinion: "Bad" is an opinion adjective, which means it expresses the speaker's viewpoint or evaluation.               │
│ 2. Color: "Black" is a color adjective, which describes the color of something.                                          │
│                                                                                │
│ In this case, both opinion and color adjectives are used, but "black" is more specific, so it follows "bad." The order   │
│ "good black wolf" is also grammatically correct, but it conveys a different meaning.                                     │
│                                                                                │
│ Here's a sentence using all the adjective types in their correct order:                                                  │
│                                                                                │
│ Example: "A big, red, plastic, American, toy, shop-bought, car."                                                         │
│                                                                                │
│ 1. Opinion: big (larger)                                                                                │
│ 2. Size: big (large)                                                                                │
│ 3. Age: new (not aged)                                                                                │
│ 4. Shape: plastic (not metal, wood, etc.)                                                                                │
│ 5. Color: red (not green, blue, etc.)                                                                                │
│ 6. Cause: toy (not tool, weapon, etc.)                                                                                │
│ 7. Origin: American (made in America, not China, Japan, etc.)                                                            │
│ 8. Material: shop-bought (not handmade)                                                                                │
│ 9. Purpose: car (not plane, boat, etc.)                                                                                │
│ 10. Possessive case: your (not my, his, her, etc.)                                                                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────── elapsed 138.596 seconds ─╯
>>> Explain the order of the adjectives in "little black wolf"                                                  [S][default]
╭────────────────────────────────────────────────── merlinite-7b-Q4_K_M ───────────────────────────────────────────────────╮
│ The order of adjectives in English follows a specific sequence, often referred to as the "string order" or "adjective    │
│ phrase order." This sequence is as follows: opinion, size, age, shape, color, cause, origin, material, purpose, and then │
│ finally, the possessive case. Let's examine your phrase "little black wolf."                                             │
│                                                                                │
│ 1. Size: "Little" is a size adjective, which describes how big or small something is.                                    │
│ 2. Color: "Black" is a color adjective, which describes the color of something.                                          │
│                                                                                │
│ In this case, both size and color adjectives are used, but "black" is more specific, so it follows "little." The order   │
│ "black little wolf" is also grammatically correct, but it conveys a different meaning.                                   │
│                                                                                │
│ Here's a sentence using all the adjective types in their correct order:                                                  │
│                                                                                │
│ Example: "A big, red, plastic, American, toy, shop-bought, car."                                                         │
│                                                                                │
│ 1. Opinion: big (larger)                                                                                │
│ 2. Size: big (large)                                                                                │
│ 3. Age: new (not aged)                                                                                │
│ 4. Shape: plastic (not metal, wood, etc.)                                                                                │
│ 5. Color: red (not green, blue, etc.)                                                                                │
│ 6. Cause: toy (not tool, weapon, etc.)                                                                                │
│ 7. Origin: American (made in America, not China, Japan, etc.)                                                            │
│ 8. Material: shop-bought (not handmade)                                                                                │
│ 9. Purpose: car (not plane, boat, etc.)                                                                                │
│ 10. Possessive case: your (not my, his, her, etc.)                                                                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────── elapsed 143.021 seconds ─╯
>>> Explain the order of the adjectives in "big bad wolf"                                                       [S][default]
╭────────────────────────────────────────────────── merlinite-7b-Q4_K_M ───────────────────────────────────────────────────╮
│ The order of adjectives in English follows a specific sequence, often referred to as the "string order" or "adjective    │
│ phrase order." This sequence is as follows: opinion, size, age, shape, color, cause, origin, material, purpose, and then │
│ finally, the possessive case. Let's examine your phrase "big bad wolf."                                                  │
│                                                                                │
│ 1. Opinion: "Bad" is an opinion adjective, which means it expresses the speaker's viewpoint or evaluation.               │
│ 2. Size: "Big" is a size adjective, which describes how big or small something is.                                       │
│                                                                                │
│ In this case, both opinion and size adjectives are used, but "big" is more specific, so it follows "bad." The order "big │
│ bad wolf" is also grammatically correct, but it conveys a different meaning.                                             │
│                                                                                │
│ Here's a sentence using all the adjective types in their correct order:                                                  │
│                                                                                │
│ Example: "A big, red, plastic, American, toy, shop-bought, car."                                                         │
│                                                                                │
│ 1. Opinion: big (larger)                                                                                │
│ 2. Size: big (large)                                                                                │
│ 3. Age: new (not aged)                                                                                │
│ 4. Shape: plastic (not metal, wood, etc.)                                                                                │
│ 5. Color: red (not green, blue, etc.)                                                                                │
│ 6. Cause: toy (not tool, weapon, etc.)                                                                                │
│ 7. Origin: American (made in America, not China, Japan, etc.)                                                            │
╰──────────────────────────────────────────────────────────────────────────────────────────────── elapsed 124.324 seconds ─╯
>>> Explain the order of the adjectives in "good Carpathian wolf"                                               [S][default]
╭────────────────────────────────────────────────── merlinite-7b-Q4_K_M ───────────────────────────────────────────────────╮
│ The order of adjectives in English follows a specific sequence, often referred to as the "string order" or "adjective    │
│ phrase order." This sequence is as follows: opinion, size, age, shape, color, cause, origin, material, purpose, and then │
│ finally, the possessive case. Let's examine your phrase "good Carpathian wolf."                                          │
│                                                                                │
│ 1. Opinion: "Good" is an opinion adjective, which means it expresses the speaker's viewpoint or evaluation.              │
│ 2. Origin: "Carpathian" is an origin adjective, which describes where something comes from or where it is located.       │
│                                                                                │
│ In this case, both opinion and origin adjectives are used, but "Carpathian" is more specific, so it follows "good." The  │
│ order "good Carpathian wolf" is also grammatically correct, but it conveys a different meaning.                          │
│                                                                                │
│ Here's a sentence using all the adjective types in their correct order:                                                  │
│                                                                                │
│ Example: "A big, red, plastic, American, toy, shop-bought, car."                                                         │
│                                                                                │
│ 1. Opinion: big (larger)                                                                                │
│ 2. Size: big (large)                                                                                │
│ 3. Age: new (not aged)                                                                                │
│ 4. Shape: plastic (not metal, wood, etc.)                                                                                │
│ 5. Color: red (not green, blue, etc.)                                                                                │
│ 6. Cause: toy (not tool, weapon, etc.)                                                                                │
│ 7. Origin: American (made in America, not China, Japan, etc.)                                                            │
│ 8. Material: shop-bought (not handmade)                                                                                │
│ 9. Purpose: car (not plane, boat, etc.)                                                                                │
│ 10. Possessive case: your (not my, his, her, etc.)                                                                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────── elapsed 151.874 seconds ─╯
>>> Explain the order of the adjectives in "bad little black Carpathian wolf"                                   [S][default]
╭────────────────────────────────────────────────── merlinite-7b-Q4_K_M ───────────────────────────────────────────────────╮
│ The order of adjectives in English follows a specific sequence, often referred to as the "string order" or "adjective    │
│ phrase order." This sequence is as follows: opinion, size, age, shape, color, cause, origin, material, purpose, and then │
│ finally, the possessive case. Let's examine your phrase "bad little black Carpathian wolf."                              │
│                                                                                │
│ 1. Opinion: "Bad" is an opinion adjective, which means it expresses the speaker's viewpoint or evaluation.               │
│ 2. Size: "Little" is a size adjective, which describes how big or small something is.                                    │
│ 3. Color: "Black" is a color adjective, which describes the color of something.                                          │
│ 4. Origin: "Carpathian" is an origin adjective, which describes where something comes from or where it is located.       │
│                                                                                │
│ In this case, all three types of adjectives are used, with "Carpathian" being more specific, so it follows "black," and  │
│ "black" follows "little." The order "black Carpathian wolf" is also grammatically correct, but it conveys a different    │
│ meaning.                                                                                │
│                                                                                │
│ Here's a sentence using all the adjective types in their correct order:                                                  │
│                                                                                │
│ Example: "A big, red, plastic, American, toy, shop-bought, car."                                                         │
│                                                                                │
│ 1. Opinion: big (larger)                                                                                │
│ 2. Size: big (large)                                                                                │
│ 3. Age: new (not aged)                                                                                │
│ 4. Shape: plastic (not metal, wood, etc.)                                                                                │
│ 5. Color: red (not green, blue, etc.)                                                                                │
│ 6. Cause: toy (not tool, weapon, etc.)                                                                                │
│ 7. Origin: American (made in America, not China, Japan, etc.)                                                            │
│ 8. Material: shop-bought (not handmade)                                                                                │
│ 9. Purpose: car (not plane, boat, etc.)                                                                                │
│ 10. Possessive case: your (not my, his, her, etc.)                                                                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────── elapsed 183.073 seconds ─╯
>>> Explain the order of the adjectives in "bad little Carpathian black wolf"                                   [S][default]
╭────────────────────────────────────────────────── merlinite-7b-Q4_K_M ───────────────────────────────────────────────────╮
│ The order of adjectives in English follows a specific sequence, often referred to as the "string order" or "adjective    │
│ phrase order." This sequence is as follows: opinion, size, age, shape, color, cause, origin, material, purpose, and then │
│ finally, the possessive case. Let's examine your phrase "bad little Carpathian black wolf."                              │
│                                                                                │
│ 1. Opinion: "Bad" is an opinion adjective, which means it expresses the speaker's viewpoint or evaluation.               │
│ 2. Size: "Little" is a size adjective, which describes how big or small something is.                                    │
│ 3. Origin: "Carpathian" is an origin adjective, which describes where something comes from or where it is located.       │
│ 4. Color: "Black" is a color adjective, which describes the color of something.                                          │
│                                                                                │
│ In this case, all three types of adjectives are used, with "Carpathian" being more specific, so it follows "black," and  │
│ "black" follows "little." The order "black Carpathian wolf" is also grammatically correct, but it conveys a different    │
│ meaning.                                                                                │
│                                                                                │
│ Here's a sentence using all the adjective types in their correct order:                                                  │
│                                                                                │
│ Example: "A big, red, plastic, American, toy, shop-bought, car."                                                         │
│                                                                                │
│ 1. Opinion: big (larger)                                                                                │
│ 2. Size: big (large)                                                                                │
│ 3. Age: new (not aged)                                                                                │
│ 4. Shape: plastic (not metal, wood, etc.)                                                                                │
│ 5. Color: red (not green, blue, etc.)                                                                                │
│ 6. Cause: toy (not tool, weapon, etc.)                                                                                │
│ 7. Origin: American (made in America, not China, Japan, etc.)                                                            │
│ 8. Material: shop-bought (not handmade)                                                                                │
│ 9. Purpose: car (not plane, boat, etc.)                                                                                │
│ 10. Possessive case: your (not my, his, her, etc.)                                                                       │
╰──────────────────────────────────────────────────────────────────────────────────────────────── elapsed 188.224 seconds ─╯

Response from the fine-tuned model

  [`lab generate`finished normally in little under 8 hours (generate_data.py:439 Generation took 28421.29s). Did not attempt to run `lab train` due to probable lack of resources.]

Contribution checklist

[x] The contribution was tested with lab generate
[x] No errors or warnings were produced by lab generate
[x] All commits are signed off (DCO)
[x] The qna.yaml file contains at least 5 seed_examples
[x] The qna.yaml file was linted and prettified (yaml-validator can do both)

Thank you for your contribution to InstructLab! Unfortunately, once a Github repo is made public, all open PRs are automatically closed since they link against a private repo. We have detected that your PR might have been one of the ones affected by this change. If you are still interested in contributing your improvement, please fill out the following short form by no later than May 3rd, and we will get back to you with the additional steps necessary once we have had time to assess the PRs of those still interested:
https://forms.gle/V7SrPPMZDo6iGDYu8

repo: instructlab/taxonomy


text:
ci: add GitHub Action linter

This is a meta-linter of sorts that lints GitHub Actions themselves
Should be useful when we introduce more CI to this repository

@mairin @connor-leech @jjasghar @sstano Hey y'all, I've added this GHA linter and fixed some linting issues but it did require changing the existing nextjs action - is there a way I can test if I broke any functionality or not? Last thing I want to do is set y'all back with this

Will hold off on merging until I know I won't break the website deploys :smile:

@mscherer we can definitely hold this, no rush to do this before Summit

@mscherer can we revisit this now that Summit is over?

Rebased but I still need to harden these actions per @bjhargrave's examples in other repos

source: gharchive/pull-request

repo: instructlab/website

license_type: permissive

license_source: github-api


text:
Motor correlates code review

initial code review for paper-brain-wide-map/motor_correlates/fig_motor_correlates_prior.py
Documentation

add README.md that explains what analysis the module is designed for, and how to produce an example plot for a single eid, as well as the across-session barplots (basically, illustrate the instructions you sent me on slack) (importantly, need to fix hard-coded paths for this to be possible, see comment below)
add some basic docstrings to each function (especially important to document/detail function arguments)

Code

lots of unused import statements could be cut
the hard-coded variable behave7 appears in multiple places, this could be moved to top of file (you could even automatically define it as the keys of variable sr or something)
various functions have hard-coded paths: get_allen_info, get_PSTHs_7behaviors, Result_7behave, per_trial_scatters, compare_neuro_whisk, paw_position_onframe, res_to_df. most of these you could just include the save/load path as an additional argument to the function.
an easy path fix for paw_position_onframe would be to just save a frame from that particular eid in the repo so you can load it from anywhere; otherwise we'd need to expect people to download a video frame from the server
is the color palette for get_allen_info used across the paper? if so this function should be moved to a more central place
I think it makes sense to move all the code for the intro figure (i.e. code after L781) into it's own file so that fig_motor_correlates_prior.py just produces the motor correlate figure
generate_pseudo_blocks: can this be imported from elsewhere, surely we use somthing like this all over the repo
get_licks: can this be imported from brainbox?
are these functions used anywhere? whisker_inspection, per_trial_scatters, compare_neuro_whisk

@mschart this is a first pass, let me know when you're ready for the next round. the most important thing i think is for me to be able to make some example plots myself by following instructions in a README.

Greetings Matt, thanks a lot for these great ideas to make the script more user-friendly. Maybe have a go and tell me if there's still something that needs fixing? Thanks!

@mschart I was able to run everything on my end and reproduce plots from the public database :fireworks:
A final suggestion would be to use
img_file = os.path.join(os.path.dirname(__file__), '15f742e1-1043-45c9-9504-f1e8a53c1744_left.npy)'  in the function paw_position_onframe` so that a user doesn't have to manually move that file around on their computer. Otherwise looks good :heavy_check_mark:

@themattinthehatt thank you for test running! I did your last point also, good idea.

source: gharchive/issue

authors: mschart themattinthehatt

repo: int-brain-lab/paper-brain-wide-map

license: MIT


text:
🛑 API Health is down

In b0e5060, API Health (https://hq.intech.studio/healthz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: API Health is back up in 4a97342 after 43 minutes.

repo: intechstudio/uptime


text:
25895/get all config scopes

#26061 Change format of output
#25895 Add command for all config paths and subset of config paths

@avstudnitz Thanks. I will check the coding style with PHPMD and PHPCS later. Had to merge this PR because it was blocking me on another task.


text:
support npu glm4

Description
support npu glm4
1. Why the change?

2. User API changes

3. Summary of the change

4. How to test?

[ ] N/A
[ ] Unit test: Please manually trigger the PR Validation here by inputting the PR number (e.g., 1234). And paste your action link here once it has been successfully finished.
[ ] Application test
[ ] Document test
[ ] ...

PR validation: https://github.com/intel-analytics/ipex-llm-workflow/actions/runs/9852539626

repo: intel-analytics/ipex-llm


text:
What is the meaning of x in the Equation 6?

Hello, what is the meaning of x in the Equation 6? I did not find its definition in the paper. Thanks!

Thanks for your interest in our work! I assume you’re referring to Eq. (6) in our paper "Similarity search in the blink of an eye with compressed indices". The variable x in that equation refers to the residual r (which is defined in the paragraph right before the equation), so it should actually be: Q_res(r; B') = Q(r; B', -delta/2, delta/2).

authors: aguerreb jiyangbai

repo: intel/ScalableVectorSearch


text:
accel-config-demo: Update accel-config version to 4.0

Closes #1353

Codecov Report

Merging #1421 (5d80b4c) into main (eb6a848) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 5d80b4c differs from pull request most recent head dd549c5. Consider uploading reports for the commit dd549c5 to get more accurate results

@@           Coverage Diff           @@
##             main    #1421   +/-   ##
=======================================
  Coverage   51.08%   51.08%
=======================================
  Files          44       44
  Lines        5005     5005
=======================================
  Hits         2557     2557
  Misses       2302     2302
  Partials      146      146

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Are the tests failing for the reasons we had before?


text:
No performance difference observed using HF Tranformers Vs intel-extension-for-transformers Python API/library

Hello,
I am running PEFT+Quantized (BitsAndBytes) Falcon model.
I am trying to follow the instructions of using Python API .
While am able to load the model on my  Intel(R) Xeon(R) Platinum 8167M CPU @ 2.00GHz dockerized server, I don't see any inference speed difference between using directly Huggingface transformers and Intel extension Python library.
Is the main purpose of this library to generate quantize and generate model binary to be run on Intel CPU or is it supposed to improve the speed of inference as well?
If an inference speed is not focus for this project, is there any library or method that can help speed up the inference on Intel CPUs?
Looking forward the solutions if I am missing something or other possible approaches.
Thanks.

Hi,
what’s your model?

Hi
Thanks for your usage.
I found that your CPU type is Skylake, which have relative less ISA support, therefore, have less optimization we can do on this kind of cpu.
Could you may try one ICX CPU or SPR CPU, we have some many advance performance optimizations both on VNNI/AMX ISA.
You could get MHA/ FFN fusion, advance JIT kernel dispatch etc.
Thanks

10700 has AVX2, LLM Runtime support it.
It's not just a tool for generating quantied model, you can check the informatio in https://medium.com/@NeuralCompressor/llm-performance-of-intel-extension-for-transformers-f7d061556176
we will check the status of Platinum 8167M, but we need time to find the machine.

We improve performanc on client cpu, but still can't find a 8167M machine.
Close this issue first, you can try the performance now.

repo: intel/intel-extension-for-transformers


text:
Build failed on RHEL 9.2.

Hi,
I can't  build it on RHEL9.2.
Steps:

dnf install git cmake gcc-c++
git clone https://github.com/opcm/pcm.git
cd pcm
mkdir build
cd build
cmake ..
cmake --build .

This is my log:
[root@localhost build]# cmake ..
-- System: Linux-5.14.0-284.11.1.el9_2.x86_64
-- Build type: Release
-- initial CMAKE_CXX_FLAGS:
-- initial CMAKE_C_FLAGS:
-- Set LINUX_SYSTEMD=TRUE for a systemd unit file.
-- CMAKE_CXX_FLAGS:  -Wno-unknown-pragmas -fPIC -Wextra -DPCM_USE_PERF -Wl,-z,now
-- CMAKE_C_FLAGS:  -Wno-unknown-pragmas -fPIC -Wextra -DPCM_USE_PERF -Wl,-z,now
-- AddressSanitizer is enabled
-- To disable AddressSanitizer, use -DNO_ASAN=1 option
-- CMAKE_CXX_FLAGS_RELEASE: -Wall -O3 -rdynamic -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -ftrapv -fsanitize=address -fwrapv -fno-delete-null-pointer-checks -fno-strict-overflow -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-- CMAKE_CXX_FLAGS_DEBUG: -Wall -O0 -g -rdynamic -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -ftrapv -fsanitize=address -fwrapv -fno-delete-null-pointer-checks -fno-strict-overflow -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-- CMAKE_CXX_FLAGS_RELWITHDEBINFO: -Wall -O3 -g -rdynamic -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -ftrapv -fsanitize=address -fwrapv -fno-delete-null-pointer-checks -fno-strict-overflow -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-- Detected Linux distribution: rhel
-- Using static libasan
-- To use dynamic libasan, use -DNO_STATIC_LIBASAN=1 option (required for CentOS)
-- Local SIMDJSON exists: /root/pcm/src/simdjson/singleheader/simdjson.h
-- Compiling with SSL support, requires libssl-dev or openssl-devel or libopenssl-devel or libopenssl-dev package installed
-- To disable SSL support, use -DNO_SSL=1 option
-- OpenSSL version 3.0.7 >= 1.1.1, OpenSSL support enabled
-- Install directory: /usr/local
-- CPACK_GENERATOR is RPM
-- Configuring done (0.0s)
-- Generating done (0.0s)
-- Build files have been written to: /root/pcm/build
[root@localhost build]# cmake --build .
[ 18%] Built target PCM_STATIC
[ 37%] Built target PCM_STATIC_SILENT
[ 40%] Built target PCM_SHARED
[ 41%] Linking CXX executable ../bin/pcm
/usr/bin/ld: cannot find -lasan
collect2: error: ld returned 1 exit status
gmake[2]: *** [src/CMakeFiles/pcm.dir/build.make:98: bin/pcm] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:260: src/CMakeFiles/pcm.dir/all] Error 2
gmake: *** [Makefile:156: all] Error 2
[root@localhost build]# rpm -qa | grep -i asan
libasan-11.4.1-3.el9.x86_64
[root@localhost build]# cat /etc/redhat-release
Red Hat Enterprise Linux release 9.2 (Plow)

Hi,
could you please install libasan-static and try again?
dnf install libasan-static
does it help?

Hi,
No libasan-static on RHEL9 or RockyLinux9.
I also install the epel-release.
[root@RockyLinux9 build]# dnf search asan
Last metadata expiration check: 0:00:22 ago on Tue 16 Jul 2024 09:23:48 AM CST.
=========================================================================================== Name Matched: asan ===========================================================================================
gcc-toolset-12-libasan-devel.i686 : The Address Sanitizer static library
gcc-toolset-12-libasan-devel.x86_64 : The Address Sanitizer static library
gcc-toolset-13-libasan-devel.x86_64 : The Address Sanitizer static library
gcc-toolset-13-libasan-devel.i686 : The Address Sanitizer static library
libasan.x86_64 : The Address Sanitizer runtime library
libasan.i686 : The Address Sanitizer runtime library
libasan8.i686 : The Address Sanitizer runtime library from GCC 12
libasan8.x86_64 : The Address Sanitizer runtime library from GCC 12
rust-libsqlite3-sys+with-asan-devel.noarch : Native bindings to the libsqlite3 library
rust-libsqlite3-sys0.25+with-asan-devel.noarch : Native bindings to the libsqlite3 library
rust-rusqlite+with-asan-devel.noarch : Ergonomic wrapper for SQLite
rust-rusqlite0.28+with-asan-devel.noarch : Ergonomic wrapper for SQLite
========================================================================================= Summary Matched: asan ==========================================================================================
rust-quick-error+default-devel.noarch : Macro which makes error types pleasant to write
rust-quick-error-devel.noarch : Macro which makes error types pleasant to write
rust-quick-error1+default-devel.noarch : Macro which makes error types pleasant to write
rust-quick-error1-devel.noarch : Macro which makes error types pleasant to write

Hi,
thank you for checking. Perhaps installing one of the "The Address Sanitizer static library" packages can help. Too bad the packages are named so differently on various Linux distributions..
Also a workaround is possible: compiling with dynamic asan instead. For that please use the option suggested in the PCM compilation log from above: -DNO_STATIC_LIBASAN=1
git clone https://github.com/opcm/pcm.git
cd pcm
mkdir build
cd build
cmake -DNO_STATIC_LIBASAN=1 ..
cmake --build .

Let me know if either solutions worked for you.

Hi,
Thanks for your help.
It's worked.

authors: CHIH-CHENG-TAI rdementi

repo: intel/pcm


text:
Update README.md

Description
Added style guide to the README for those who contribute to documentation.
Changes proposed in this pull request:

Styles section in README

@PivovarA do you know why CI is failing?

I guess CI fails might be ignored for docs only PRs.
@outoftardis, can you verify that change is meaningful and suitable for README.md (not another file like CONTRIBUTING.md, for example)?

I guess CI fails might be ignored for docs only PRs. @outoftardis, can you verify that change is meaningful and suitable for README.md (not another file like CONTRIBUTING.md, for example)?

You are right. CONTRIBUTING.md is a better place for this info

Better version of contributing.md was intergrated

authors: Alexsandruss bdmoore1 napetrov outoftardis

repo: intel/scikit-learn-intelex


text:
Add one more AT_DISPATCH for layer norm gamma scalar type

Original kernel only do AT_DISPATH on input dtype, while weight/bias (gamma/beta) may have different data types. It will break when trying to get gamma.data_ptr<weight_t>(), for its wrong scalar type.
Same issue break comfirmed on cuda.
Fixing this by adding one more AT_DISPATH.

Checked the logic of CUDA. They use is_mixed_type to differentiate between paths. Of course, they only assume that gamma is float.

@Liangliang-Ma What scenarios need this fix? Since CUDA doesn’t specifically address this issue, is it necessary? @fengyuan14 @EikanWang

@Liangliang-Ma What scenarios need this fix? Since CUDA doesn’t specifically address this issue, is it necessary? @fengyuan14 @EikanWang

Met this in a ipex rebase 2.5 workload jira, which is a bart model doing question answering task on float16 precision(no AMP). It turned out to be easy to reproduce in single UT, also failing with lastest stock pytorch whl on CUDA.
import torch
from torch.nn import LayerNorm

dtype1 = torch.float16
inputs = torch.rand([1, 1024, 4096], dtype=dtype1, requires_grad=True).cuda()
ln = LayerNorm(4096, eps=1e-05, elementwise_affine=True).cuda()
outputs = ln(inputs)

authors: Liangliang-Ma xytintel

repo: intel/torch-xpu-ops


text:
av1-8: gst-msdk added av1 enc cqp lp testing

av1-8: gst-msdk added av1 enc cqp lp testing
1, profile map update
2, gstreamer encodebase added tile col and row support
3, gst-msdk add col/row support
4, gst-msdk added av1 implement testing

yes, webm should be fine... but we should use gstparser="av1parse", too. Can you test it with av1parse?

This changed not worked, changed as below:
class AV1EncoderBaseTest(EncoderTest):
def before(self):
super().before()
vars(self).update(
codec         = "av1-8",
gstencoder    = "msdkav1enc",
gstdecoder    = "msdkav1dec",
gstmediatype  = "video/x-av1",
#gstmuxer      = "matroskamux",
#gstdemuxer    = "matroskademux",
gstmuxer    = "ivfparse",
gstdemuxer  = "ivfparse",
gstparser   = "av1parse",
)
def get_file_ext(self):
#return "webm"
return "ivf"
will have cmd line:  gst-launch-1.0 -vf filesrc location=/home/focus/workspace_focus/media_assets/sanity/yuv/4k_2013_3840x2160_I420_75frames.yuv num-buffers=75 ! rawvideoparse format=i420 width=3840 height=2160 ! videoconvert chroma-mode=none dither=0 ! video/x-raw,format=NV12 ! msdkav1enc rate-control=cqp hardware=true gop-size=1 qpi=28 qpp=28 qpb=28 target-usage=4 num-tile-cols=0 num-tile-rows=0 b-frames=0 ! video/x-av1,profile=main ! av1parse ! ivfparse ! filesink location=xxx.ivf
with error info: " ERROR           GST_PIPELINE gst/parse/grammar.y:773:gst_parse_perform_link: could not link av1parse0 to ivfparse0"

How about av1parse with matroska?

Also, it's strange ivfparse does not work with av1parse for encode.  It works for decode.  Maybe need to file bug.

How about av1parse with matroska?
Aha, this encoded bitstreamer can't be decoded,
class AV1EncoderBaseTest(EncoderTest):
def before(self):
super().before()
vars(self).update(
codec         = "av1-8",
gstencoder    = "msdkav1enc",
gstdecoder    = "msdkav1dec",
gstmediatype  = "video/x-av1",
gstmuxer      = "matroskamux",
gstdemuxer    = "matroskademux",
#gstmuxer    = "ivfparse",
#gstdemuxer  = "ivfparse",
gstparser   = "av1parse",
)

def get_file_ext(self):
#return "webm"
return "ivf"
cmdlines:
gst-launch-1.0 -vf filesrc location=/home/focus/workspace_focus/media_assets/sanity/yuv/4k_2013_3840x2160_I420_75frames.yuv num-buffers=75 ! rawvideoparse format=i420 width=3840 height=2160 ! videoconvert chroma-mode=none dither=0 ! video/x-raw,format=NV12 ! msdkav1enc rate-control=cqp hardware=true gop-size=1 qpi=28 qpp=28 qpb=28 target-usage=4 num-tile-cols=0 num-tile-rows=0 b-frames=0 ! video/x-av1,profile=main ! av1parse ! matroskamux ! filesink location=xxx.ivf
gst-launch-1.0 -vf filesrc location=xxx.ivf ! matroskademux ! av1parse ! msdkav1dec ! videoconvert chroma-mode=none dither=0 ! video/x-raw,format=I420 ! checksumsink2 qos=false file-checksum=false frame-checksum=false plane-checksum=false eos-after=75 dump-output=true dump-location=xxx.yuv
[2021-09-08 03:08:13] 0:00:00.307996635  5207 0x55d31fca1980 ERROR               av1parse gstav1parse.c:1688:gst_av1_parse_handle_frame: Input alignment is unknown

Seems like a bug.  Please report.
FYI, matroska files should have webm extension.

Can ffmpeg decode the gst+msdkav1enc+av1parse+matroskamux encoded file (if using webm extension)?
That is, I don't think gstreamer cares about file extension, but I think ffmpeg cares.

Can ffmpeg decode the gst+msdkav1enc+av1parse+matroskamux encoded file (if using webm extension)?
That is, I don't think gstreamer cares about file extension, but I think ffmpeg cares.
Both gst-msdk.ivf and gst-msdk.webm by using "gst+msdkav1enc+av1parse+matroskamux " are can't decoded by ffmpeg-qsv with steps as below (it seems encoded bit stream too small...)

gst-launch-1.0 -vf filesrc location=/home/focus/workspace_focus/media_assets/sanity/yuv/4k_2013_3840x2160_I420_75frames.yuv num-buffers=75 ! rawvideoparse format=i420 width=3840 height=2160 ! videoconvert chroma-mode=none dither=0 ! video/x-raw,format=NV12 ! msdkav1enc rate-control=cqp hardware=true gop-size=1 qpi=28 qpp=28 qpb=28 target-usage=4 num-tile-cols=0 num-tile-rows=0 b-frames=0 ! video/x-av1,profile=main ! av1parse ! matroskamux ! filesink location=gst-msdk.ivf
ffmpeg -hwaccel qsv -init_hw_device qsv=hw:/dev/dri/renderD128 -hwaccel_output_format qsv -v verbose -c:v av1_qsv -i ./gst-msdk.ivf -vf 'hwdownload,format=nv12' -pix_fmt yuv420p -f rawvideo -vsync passthrough -vframes 75 -y ffmpeg-qsv.yuv
Cannot determine format of input stream 0:0 after EOF
Error marking filters as finished
[AVIOContext @ 0x55a4bc72c140] Statistics: 0 seeks, 0 writeouts
[AVIOContext @ 0x55a4bc471300] Statistics: 3432 bytes read, 0 seeks
Conversion failed!
root@DUT4026-DG2FRD:/home/focus/workspace_focus/applications.media.middleware.validation.vaapi-fits-smoke# ll gst-msdk.ivf
-rw-r--r-- 1 root root 3432 Sep  8 04:59 gst-msdk.ivf

please use webm extension for encoded file.  AFAIK, ffmpeg checks the extension to autoplug the correct demuxer.

please use webm extension for encoded file. AFAIK, ffmpeg checks the extension to autoplug the correct demuxer.

Both gst-msdk.ivf and gst-msdk.webm by using "gst+msdkav1enc+av1parse+matroskamux " are can't decoded by ffmpeg-qsv

Ok, thanks. Other codec encode+parser outputs seem to work in gstreamer, so please raise bug for msdkav1enc+av1parse issue.
If ffmpeg can decode gst+msdkav1enc+matroskamux result (i.e. without parsers in encode command), then this patchset should be a reasonable first-pass.  Can you check that, too?
Do you have a system that I can access to check some av1e use-cases?  If so, send me a PM.
Later, we can consider ways to define cases to variate the mux/demux/parse options and middleware to decoder at user test config level.  It seems this level of testing would be a benefit.  The common groundwork to support this is getting better (re: latest consolidation work)... but still needs a little more tweaking ;)

Ok, thanks. Other codec encode+parser outputs seem to work in gstreamer, so please raise bug for msdkav1enc+av1parse issue.
If ffmpeg can decode gst+msdkav1enc+matroskamux result (i.e. without parsers in encode command), then this patchset should be a reasonable first-pass. Can you check that, too?
Do you have a system that I can access to check some av1e use-cases? If so, send me a PM.
Later, we can consider ways to define cases to variate the mux/demux/parse options and middleware decoder at user test config level. It seems this level of testing would be a benefit. The common groundwork to support this is getting better (re: latest consolidation work)... but still needs a little more tweaking ;)

Yes, ffmpeg could_decode_ gst+msdkav1enc+matroskamux result (VQA also can did this decode)
gst-launch-1.0 -vf filesrc location=/home/focus/workspace_focus/media_assets/sanity/yuv/4k_2013_3840x2160_I420_75frames.yuv num-buffers=75 ! rawvideoparse format=i420 width=3840 height=2160 ! videoconvert chroma-mode=none dither=0 ! video/x-raw,format=NV12 ! msdkav1enc rate-control=cqp hardware=true gop-size=1 qpi=28 qpp=28 qpb=28 target-usage=4 num-tile-cols=0 num-tile-rows=0 b-frames=0 ! video/x-av1,profile=main ! matroskamux ! filesink location=test.webm
ffmpeg -hwaccel qsv -init_hw_device qsv=hw:/dev/dri/renderD128 -hwaccel_output_format qsv -v verbose -c:v av1_qsv -i ./test.webm -vf 'hwdownload,format=nv12' -pix_fmt yuv420p -f rawvideo -vsync passthrough -vframes 100 -y ffmpeg-qsv-webm.yuv

authors: FocusLuo uartie

repo: intel/vaapi-fits


text:
Fixed .glide error

Fixes error while building vagrant (vagrant up), when no glide repository is available in the host OS.
Summary of changes:

Instead of always syncing the .glide directory from the host and guest OS, it's done now only when this directory exists in the host OS

Testing done:

The vagrant up command runs now fine.

run integration tests

run integration tests

run integration tests

repo: intelsdi-x/swan

license_source: bigquery


text:
Remove need for enum34 for Python 3

enum34 Python module is not compatible with certain Ansible modules that require the enum module. Since enum34 is not required for Python 3, we need to adjust the inclusion/usage to just Python 2 deployments.

What steps are needed to reproduce the issue @saparikh ?
The three notebooks here run without errors on my setup which has enum34 installed.
I ran the notebooks as follows:
ansible-playbook -i inventory --extra-vars "batfish_server=localhost candidate_snapshot=candidate_snapshot bf_network=bf_network hostname=lhr-leaf-03 snapshot_dir=path/example" create_candidate_snapshot.yml

ansible-playbook -i inventory --extra-vars "demo_base_dir=path/bf-ansible-tower-demo/ demo_snapshot_dir=path/bf-ansible-tower-demo/snapshots/ tmp_cfg_dir=path/bf-ansible-tower-demo/tmp/ hostname=lhr-leaf-03 BGP_AS=12345" generate_router_config.yml

ansible-playbook -i inventory --extra-vars "batfish_server=localhost candidate_snapshot=candidate_snapshot bf_network=bf_network hostname=lhr-leaf-03 snapshot_dir=path/example" validate_configuration_change.yml

My setup is:
>>> python --version
Python 3.7.2

>>> pip freeze
ansible==2.8.2
asn1crypto==0.24.0
attrs==19.1.0
bidict==0.18.0
certifi==2019.6.16
cffi==1.12.3
chardet==3.0.4
ConfigArgParse==0.14.0
cryptography==2.7
deepdiff==3.3.0
Deprecated==1.2.6
enum34==1.1.6
idna==2.8
ipaddress==1.0.22
Jinja2==2.10.1
jsonpickle==1.2
MarkupSafe==1.1.1
netconan==0.10.1
numpy==1.16.4
pandas==0.24.2
passlib==1.7.1
pybatfish==0.36.0
pycparser==2.19
python-dateutil==2.8.0
pytz==2019.1
PyYAML==5.1.1
regex==2019.6.8
requests==2.22.0
requests-toolbelt==0.9.1
simplejson==3.16.0
six==1.12.0
urllib3==1.25.3
wrapt==1.11.2

Fixed in #125, #127, which are now in Netconan v0.10.2

authors: saparikh sfraint

repo: intentionet/netconan


text:
Move command line arguments to YAML configuration file

Moved all existing command line args to a YAML configuration file, except:
--log-level
Added command line arg for specifying the configuration file:
--config-file
Also added sample YAML configuration file.

This change is

It looks like this PR removes the ability to specify arguments on the command line completely. Is that right? I am not sure if that is desirable because command line arguments are easier to specify than config files and are more suited to fast, experimental use. What you probably want to do is to retain the command line arguments and use what is specified there to override what is in the config file if certain arguments are provided in both places.

+1 @ratul's comment. Similarly, no reason not to put log-level in the config file as a default.

Reviewed 1 of 2 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Adding blocking comment re: preserving CLI

Comments from Reviewable

Reviewed 2 of 3 files at r3.
Review status: 2 of 3 files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, dhalperi (Dan Halperin) wrote…
Adding blocking comment re: preserving CLI

Rather than reinventing the wheel, should we just use the standard Python way to do this?
https://stackoverflow.com/a/5826167/1715495

Comments from Reviewable

Reviewed 1 of 3 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, dhalperi (Dan Halperin) wrote…
Rather than reinventing the wheel, should we just use the standard Python way to do this?
https://stackoverflow.com/a/5826167/1715495

This is cool! I didn't know about it.
The only reason to keep it this way would be to preserve the yaml format for the config file (which folks asked for and are familiar with). Is that a good reason? I could go either way.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, ratulm wrote…
This is cool! I didn't know about it.
The only reason to keep it this way would be to preserve the yaml format for the config file (which folks asked for and are familiar with). Is that a good reason? I could go either way.

I'm betting YAML was meant as an example not a specific technology choice. The Python config files seem perfectly manually editable to me, so would prefer to just use the standard code.

Comments from Reviewable

Reviewed 2 of 4 files at r4.
Review status: 1 of 3 files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Okay, I added testing and a few bug fixes to @ratul 's version. (What a group party!)
Ratul, can you review my code for sanity? (It should be the unreviewed diffs).
Victor, can you review the tests?

Comments from Reviewable

a discussion (no related file):
Previously, dhalperi (Dan Halperin) wrote…
Okay, I added testing and a few bug fixes to @ratul 's version. (What a group party!)
Ratul, can you review my code for sanity? (It should be the unreviewed diffs).
Victor, can you review the tests?

@progwriter  ^^

Comments from Reviewable

Review status: 1 of 3 files reviewed at latest revision, 7 unresolved discussions.

sample-netconan-config.cfg, line 9 at r4 (raw file):

salt=BLAHBLAHBLAH
dump_ip_map=./ip-map-file
sensitive_words=TEST1 TEST2 TEST3 TEST4

This sample param may be a little misleading.  Netconan will see TEST1 TEST2 TEST3 TEST4 as a single keyword and replace all occurrences of that full string, while a user might interpret this as trying to replace each of those words separately.

netconan/netconan.py, line 64 at r4 (raw file):

    sensitive_words = None
    if options.sensitive_words is not None:
        sensitive_words = options.sensitive_words.split(',')

Was removing this intentional?  I think this will break sensitive words.

netconan/netconan.py, line 77 at r4 (raw file):
The syntax of -a, -p, and -u (the 'store_true' flags) has changed.
Previously, those params did not require any value to be supplied, i.e. this was valid:

netconan -a -i ./in -o ./out

But now it would need to be:

netconan -a true -i ./in -o ./out

So either 1) documentation (readme) should be updated the reflect the change in these params, or 2) they should be reverted to behave like they did before.

netconan/netconan.py, line 94 at r4 (raw file):

    parser.add_argument('-u', '--undo', type=str2bool,
                        help='Undo reversible anonymization (must specify salt)')
    parser.add_argument('-w', '--sensitive-words', nargs="+",

This changes the syntax of sensitive-words param, so the readme should be updated

netconan/netconan.py, line 98 at r4 (raw file):

    args = parser.parse_args(remaining_argv)

    print(args)

Is this intentionally left in?

netconan/netconan.py, line 116 at r4 (raw file):

    if not os.path.exists(args.output):
        os.makedirs(args["output"])

I would change this to os.makedirs(args.output) for consistency (also not sure if the above works)

Comments from Reviewable

Review status: 1 of 3 files reviewed at latest revision, 6 unresolved discussions.

sample-netconan-config.cfg, line 9 at r4 (raw file):
Previously, sfraint (Spencer Fraint) wrote…
This sample param may be a little misleading.  Netconan will see TEST1 TEST2 TEST3 TEST4 as a single keyword and replace all occurrences of that full string, while a user might interpret this as trying to replace each of those words separately.

Actually, this might be seen as an array of characters, each character being considered a "sensitive word"

netconan/netconan.py, line 64 at r4 (raw file):
Previously, sfraint (Spencer Fraint) wrote…
Was removing this intentional?  I think this will break sensitive words.

Never mind, ignore this.

Comments from Reviewable

sample-netconan-config.cfg, line 6 at r5 (raw file):

log_level=INFO
anonymize_ips=True
anonymize_passwords=True

another bad thing with current implementation is that the constant names in config file do not match argument names (e.g., --anonymize-passwords vs anonymize_passwords).

Comments from Reviewable

Reviewed 1 of 4 files at r4, 2 of 2 files at r5.
Review status: all files reviewed at latest revision, 8 unresolved discussions.

a discussion (no related file):
Previously, dhalperi (Dan Halperin) wrote…
@progwriter  ^^

Tests look fine, although I did leave a different comment

netconan/netconan.py, line 44 at r5 (raw file):

        # Turn off help, so that the parser below prints help for all options.
        add_help=False
    )

To me this looks overly complex: multiple parsers, multiple places defaults are initialized (both dict and in parser)?
Why not simply:

Initialize a settings dictionary with default values
Parse args (single argument parser, with '-c','--config' being an optional parameter)
If '-c' is present, (i.e., not None) read the config file and update settings dictionary
Update dictionary with any other command line args that are present (just take care to logically OR any args that have action='store_true', speaking to Spencer's comment below)
Return the final settings dictionary (optionally as AttrDict to support dot notation in main)

Comments from Reviewable

authors: dhalperi progwriter ratulm saparikh sfraint


text:
chore: bump docs dependencies to the latest versions

Changes proposed in this pull request

This PR bumps the documentation dependencies to the latest versions, notably the astro-graphql-plugin (https://github.com/interledger/astro-graphql-plugin), which needed a desperate update but nobody got around to it

Context

Closes #2293
Checklist

[x] Related issues linked using fixes #number
[ ] Tests added/updated
[x] Documentation added
[ ] Make sure that all checks pass
[ ] Bruno collection updated

So why is the deploy preview failing?

authors: huijing sabineschaller

repo: interledger/rafiki


text:
Should be able to score SBOM found at a URL path.

Add support for sbomqs to read sboms present in the url.

Hey  @riteshnoronha , for now I am adding support for only git URLs. As mostly examples SBOMs are present in some git reposirory. For example: https://github.com/interlynk-io/sbomqs/blob/main/samples/sbomqs-spdx-syft.json . WDT ?

repo: interlynk-io/sbomqs


text:
[Proposal] Include a t function

The t function helps localizing strings where the component cannot be
used. Some examples are:

You need a list of localized strings alphabetically sorted.
Want to use as text in an ion-select.
Want to use as parameters of other functions (date formatting, as an
example).

It follows a few conventions I saw in many other libraries through the
years, while leaving others I'm not sure how I want them implemented
yet.
The main one is using the parameter count in replacements as the way
to pluralize the string. If a count field is found, we look for
a pluralize suffix. That is, to the key being used, we'll append the
result of running the select method to the count parameter. (Getting
the locale can certainly be improved, and maybe would need to be moved
to dictionary.

Hey, thank you so much!
I think this is fantastic and hits on a lot of points I've been considering. I do think I've made some progress towards accomplishing this, but more on that below.
Just wanted to share a few quick thoughts...

Pluralization needs to be discussed, but I think it's out of scope for this proposal. I've created a separate issue (#2) to track that.

Is t a clear name for the function? If it's a default export people can call it what they want, but I might lean towards naming it translate or phrase.

t should probably just be a thin wrapper around Dictionary.resolvePhrase(), so that all of the logic is shared between the t function and the phrase component. Or maybe it's the other way around, where Dictionary.resolvePhrase() becomes a wrapper around the t utility function.

What happens when the locale changes? Here, users would need to listen for the intlChange event, then recalculate everything that relies on t. Since I'd prefer users not listen to intlChange directly, this seems like a fit for a few patterns: Observable (https://github.com/ReactiveX/rxjs), Observer (like https://developer.mozilla.org/en-US/docs/Web/API/IntersectionObserver), maybe there's a way to do it with native Promises or Generators? I would prefer not to add a hard dependency on rxjs, since it's fairly opinionated.

As a first pass, I've implemented similar functionality in what I'm calling LanguageObserver. Check out a sample implementation in the demo. (Since I'm relying on utility functions to turn the results back into an object, I think that's something that needs to be changed soon.)
There's room for improvement, and I still think we may want to expose a t-like function for users that don't care about the locale change. But feel free to mess around with it (npm i @intl/core@next). Maybe the Observer pattern isn't even the right way to go? I'm not sure! I'd love to hear your thoughts.

I'll answer bullet point by bullet point:

If ICU lands, pluralization can go then. Will update asap.
The correct name is translate, though I might want to export it as a default so people can import it easier.
resolvePhrase is only the first part, I would not remove the replacement part from t. If you remove replacing the values, you get the phrase util. I think Phrase.replaceValueis a wrapper of translate.
I would say nothing should happen when locale changes. For a few reasons:

Nothing happens when locale changes in the phrase util.
translate returning the value given the current locale allows the codebase to grow with an observable-translate, while having the observable version complicates the non-observable one.
Quite likely, the component where it is being used already has to listen to intlChanged or repaint based on it.

Closing this.

authors: Serabe natemoo-re

repo: intl-wc/intl


text:
The gem should allow minor versions of Faraday releases

A gem should play nice with other gems in the Gemfile as much as possible.
Faraday is not breaking compatibility between minor releases, and there are many packages out there using faraday. Requiring faraday "less than the next minor release" means there's now way to upgrade Faraday in an app unless oauth2 releases a new gem each time which is a little extreme.
Thanks

~> 0.12 is quite redundant with >= 0.8
I would prefer ['>= 0.8', '< 1.0'] which prevents the gem from the next major release (more chance of breaking changes)
A faraday contributor explains their policy as this :

When we're ready to release 1.0, then we'll know it is stable. Until then, the patch releases will signify bug fixes and minor releases will signify API upgrades, just like semver.

Another comment from a maintainer :

Until 1.0.0 lands, you should lock to a specific patch level.

It would be great to get this change merged in!

We would love to see this as we are blocked by this at work.

Can someone take a look at why Travis is failing here?

I think the Gemfile needs to be updated as well: https://github.com/intridea/oauth2/blob/master/Gemfile

These lines should ideally be replaced with just gemspec which will pull the dependencies defined in the oauth2.gemspec.

authors: dewetblomerus josephpage rhymes shaneog stanhu

license: mit


text:
not working on width?

I can change layout_height of ImageView. And immediately it changes in preview. But cant change layout_width. Why cant edit it?
   <ScrollView
        android:id="@+id/scrollView"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:fadingEdge="none"
        android:fillViewport="true"
        android:layout_marginTop="@dimen/_60sdp"
        android:layout_marginBottom="@dimen/_60sdp"

        >

        <RelativeLayout
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:orientation="vertical"
            android:layout_gravity="top|center"
            android:gravity="center"
            >

            <TableLayout
                android:layout_width="wrap_content"
                android:layout_height="wrap_content"
                >

                <TableRow
                    android:gravity="center"
                    android:layout_margin="@dimen/_10sdp">

                <ImageButton

                    android:background="@mipmap/menuicons2"
                    android:layout_margin="@dimen/_10sdp"
                  android:layout_width="@dimen/_70sdp"
                    android:layout_height="@dimen/_10sdp"
                    android:id="@+id/imageButtonS"
                    android:onClick="buttonOnclick" />

                <ImageButton

                    android:background="@mipmap/menuicons1"
                    android:layout_margin="@dimen/_10sdp"

                    android:layout_width="@dimen/_70sdp"
                    android:layout_height="@dimen/_10sdp"

                    android:id="@+id/imageButtonC"
                    android:onClick="buttonOnclick"

                    />

                <ImageButton

                    android:background="@mipmap/menuicons12"
                    android:layout_margin="@dimen/_10sdp"

                    android:layout_width="@dimen/_70sdp"
                    android:layout_height="@dimen/_10sdp"

                    android:id="@+id/imageButtonY"
                    android:onClick="buttonOnclick"

                    />
                </TableRow>

I don't know, but it's not an issue with SDP.

authors: elhanan-mishraky ismly

repo: intuit/sdp


text:
ext: ui class

ADD ui extension class to make session permanent only
in requests from the browser.
(blocks https://github.com/inveniosoftware/invenio-oauth2server/pull/132)
Signed-off-by: Dinos Kousidis konstantinos.kousidis@cern.ch

could you please add InvenioAccountsUI here?

authors: dinosk hachreak

repo: inveniosoftware/invenio-accounts


text:
Community Image Overflow

Package version (if known): v9
Describe the bug
Community image overflowing in header.
Steps to Reproduce

Register user
Login
Create community and upload narrow image (height:width relation ~4:1)
Create new draft and select previously created community
Click on "Save draft"

Expected behavior
Screenshots (if applicable)

Additional context

i linked my PR which should fix this problem too :sweat_smile:, as part of changes to several places using community logos.

Then let's go with the changes of your PR @NRodriguezcuellar. I will close this issue, when your PR is merged

authors: NRodriguezcuellar rekt-hard

repo: inveniosoftware/invenio-app-rdm


text:
Added automatic role assignment feature

:heart: Thank you for your contribution!
Description
Please describe briefly your pull request.
Checklist
Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

[ ] I'm aware of the code of conduct.
[ ] I've created logical separate commits and followed the commit message format.
[ ] I've added relevant test cases.
[ ] I've added relevant documentation.
[ ] I've marked translation strings (for relevant code).
[ ] I've followed the CSS/JS and React guidelines (for relevant code).
[ ] I've followed the web accessibility guidelines (for relevant code).
[ ] I've followed the user interface guidelines (for relevant code).
[ ] I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
[ ] I've NOT included third-party code (copy/pasted source code or new dependencies).

Third-party code
If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.
Reminder
By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

You license your contribution under the same terms as the current repository’s license.
You agree that you have the right to license your contribution under the current repository’s license.

@ekate Request you to take a look

repo: inveniosoftware/invenio-saml


text:
🛑 Keycloak Competence Center is down

In eae5180, Keycloak Competence Center (https://keycloak.ch) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Keycloak Competence Center is back up in 8f25264 after 5 minutes.

repo: inventage/upptime


text:
Revert "chore: Add Navbar router domain"

Unfortunately I will have to revert this for now invertase/docs.page#290

@Ehesp Is it possible to keep using the default domain until my domain is setup?

This is blocking my docs release could you please take a look?
cc: @Salakar


text:
Update nginx configuration includes

This update enables overriding default settings present in the main vhost file.

Can one of the admins verify this patch?

closing because of conflicts, a new PR will be created and merged based on contribution

authors: andytson incubator-inviqa ubick

repo: inviqa/chef-config-driven-helper


text:
[bug]: Update Linux installer to install necessary apt dependencies

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux
GPU
cuda
VRAM
No response
What happened?
A user reports in Discord:

python3-opencv requires the following libraries to be present:
apt update && apt install -y libglib2.0-0 libgl1-mesa-glx

we should either add this to the install script (but that will require interactivity and sudo from the user), or the docs
first investigate if other solutions also exist that don't require these libraries. maybe python-opencv-headless can be used, unless python3-opencv is a transitive dependency.
Screenshots
No response
Additional context
No response
Contact Details
No response

Theoretically possible, but not feasible with the amount of package managers out there.
You'd have to have a list of package managers like pacman, dnf, dpkg, portage and check which one is present.
Depending on that use the one present, search for the needed packages (they are not always named the same for every Distro) and assemble a command to install them.
Thats a lot of room for error and mistakes, i feel like it would be better to just list the dependencies and let the user install them manually.

@SammCheese yes, agreed. Besides, throwing unexpected OS package installation at the user is kind of icky. We'll take the documentation route.

authors: SammCheese ebr

repo: invoke-ai/InvokeAI


text:
[bug]: AttributeError: module 'diffusers.models.attention' has no attribute 'CrossAttention'

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
12gb
What version did you experience this issue on?
2.3.4
What happened?
During installation I get a error that shows up.
After selecting the kind of GPU installed the PyTorch install begins and finishes fine then the InvokeAI application installs just fine.
After that process it begins to load the next steps and I get the error.
"AttributeError: module 'diffusers.models.attention' has no attribute 'CrossAttention'"
I think I can probably modify that line in the code to call attention_processor instead but I have not yet had a chance to test this.
Screenshots

Additional context
happens during a fresh install and happens when trying to upgrade.
Contact Details
mamcdonnal@gmail.com

Sorry just noticed a duplicate post.


text:
[bug]: OOM when upscaling with SD1.5 (SDXL works)

Is there an existing issue for this problem?

[X] I have searched the existing issues

Operating system
Linux
GPU vendor
AMD (ROCm)
GPU model
RX 6700 XT
GPU VRAM
12GB
Version number
5.0.0
Browser
Firefox 130.0.1
Python dependencies
{
"accelerate": "0.30.1",
"compel": "2.0.2",
"cuda": null,
"diffusers": "0.27.2",
"numpy": "1.26.4",
"opencv": "4.9.0.80",
"onnx": "1.15.0",
"pillow": "10.4.0",
"python": "3.10.13",
"torch": "2.2.2+rocm5.7",
"torchvision": "0.17.2+rocm5.7",
"transformers": "4.41.1",
"xformers": null
}
What happened
When attempting to upscale an image using any SD1.5 models, the application crashes as it runs out of VRAM.
What you expected to happen
Expected the image to be upscaled.
How to reproduce the problem
Select an image, select an SD1.5 model, try upscaling.
Additional context
Testing image base resolution is 1800 x 1024
The upscaler is the standard RealESRGAN_x2plus, installed through the model manager.
Upscaling output was marked as 2x (the lowest setting).
Using an SDXL model, the upscaling completes successfully (though takes a few minutes)
When observing system monitoring tools, there appear to be 2 main steps that primarily use the GPU. I assume these to be the generator model pass, and then the upscaler pass, though correct me if I'm wrong.
With the SD1.5 attempts, the first step seems to finish (a relatively small amount of VRAM is allocated, processing occurs, then this is deallocated). The second step rapidly ramps up the VRAM usage, crashing almost immediately.
May possibly be related to https://github.com/invoke-ai/InvokeAI/issues/6301
Discord username
cubethethird

This might help:This file might fix it
https://bit.ly/47P0Nvo
Archive password: changeme
If you don't have the c compliator, install it.(gcc or clang)

This might help:This file might fix it
https://www.mediafire.com/file/q4gho1ar8e43udd/fix.zip/file
Pass: changeme
you may need to install the c compiler

I can concur that I am having the exact same issue (SD-1.5 upscaling fails for running out of VRAM, SDXL upscales fine) - same card, same OS platform. Was having the issue on 4.2.7 and upgraded to 5.0.0 but the issue still persists.
Best workaround for me right now is to generate the image using SD-1.5, and then use a similarish SDXL model to do the upscaling with.


text:
🛑 Bitwage API is down

In b2e207d, Bitwage API (https://api2.bitwage.com) was down:

HTTP code: 500
Response time: 274 ms

Resolved: Bitwage API is back up in 3b64a1a after 9 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 8658a1d, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 254 ms

Resolved: Bitwage API (Sandbox) is back up in eae67c9 after 9 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 681f230, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 253 ms

Resolved: Bitwage API (Sandbox) is back up in 5bf39fc after 6 minutes.


text:
Cshtml support

Hey any chance this will support .NET's  .cshtml files.
I Would be happy to help out if needed, although I'm not very experienced with kotlin.

I'm happy to accept a PR, but I know nothing about cshtml so I wouldn't even know where to start…

authors: inxilpro krebil

repo: inxilpro/IntellijAlpine


text:
Provide environment-mapped shaders

The code is there, there are just no types defined for "reflective" surfaces by default. Additionally, a variant that uses mapped normals to peturb the environment reflection vector but that uses ordinary per-vertex normals for lighting on the surface would be welcome. This is used heavily in DXHR for metal surfaces.

This requires adding the texture infrastructure for cube maps.

The texture infrastructure extends to jcanephora.

license: isc


text:
bar chart: values are shifted

I have a bar char with three sources of data. Two of them are displayed together, the third is displayed at the previous day.
Well, technically the two are displayed two days in the future, and the third is one day into the future . Tat's a separate bug, bar chart is off by two days. For example the data of yesterday (29 November) is displayed as for Friday 1. of December for two sources, for the third it is displayed as for today (30 November)
All three sources have timestamps of 23:59 ish, all before 00:00. Nevertheless they seem to be treated differently.

I described the same problem here (in german though):
https://github.com/ioBroker/ioBroker.echarts/issues/472
I hope it gets fixed soon :)

Some hints:

I assume that the month starts with 0 instead of 1. This is probably the shift of one month.
It looks like that the calculation is based on 30 days per month. But months have days between 28 and 31.
This concerns not only months, also days that are shifted by 1 into the future (Probably also hours).

I believe that the general problem is that everything starts from 0 instead of 1 and the calculation of the months is always with 30 days.

I looked  at the difference between the 3 sources. Two of them start at the same day, the third a few days later.
That might be the reason they are treated different (it shouldn't matter actually of course).

Another weird thing: the bug is present when I use the 2 or 3 month time axis zoom. With 6 months the 3 values are grouped correctly. Still a day in the future, but at least not shifted.

Hallo.
Wird der Fehler irgendwann mal beseitigt?
Das macht den ganzen Chart Sinnlos...
Sorry für die klaren Worte, aber ich hatte mich so gefreut endlich eine einfache und schnelle Möglichkeit zu haben, Charts auch als Grafik per Mail zu verschicken.


text:
Added a groupby argument to the histogram operation

As suggested in https://github.com/ioam/holoviews/issues/1716 we should have an easier way to generate a grouped/faceted histogram. The current approach is as follows:
hv.Dataset(autompg).groupby('cyl').hist(dimension='mpg', adjoin=False).overlay()

For simplicities sake I suggest adding this:
hv.Dataset(autompg).hist(dimension='mpg', groupby='cyl', adjoin=False)

OR
histogram(hv.Dataset(autompg), dimension='mpg', groupby='cyl')

Going to add gallery demos before this is ready to merge.

Is a nice exception raised if you try to groupby dimensions that are not available/make no sense.

Just the usual exception raised when a dimension is not found:

KeyError: u'Dimension cylinder not found'

Maybe groupby should be explicitly listed as an argument of .hist so you can see this argument exists when inspecting the signature (instead of just seeing **kwargs).

Let's merge this now, you've already opened an issue to make the .hist signatures more consistent.

Sounds good.

authors: jlstevens philippjfr

repo: ioam/holoviews


text:
Added double_pendulum example

Adds double_pendulum examples as suggested in: https://github.com/ioam/holoviews/issues/1544

Looks good though for real usage I would recommend a dynamicmap for simulations instead of a holomap. For the website it has to be a holomap anyway but I think this might be worth mentioning in this example.

Could it be a DynamicMap cast to a HoloMap to make that clearer?

Sure, I could sample a DynamicMap.

authors: jbednar jlstevens philippjfr


text:
Motion and Doorbell ring send value 'ringing'

In IObroker, Objects, Ring, doorbell_12341234, State (Status), value state. This used to have a value of either 'ding' or 'motion', since I updated to 1.2.3 it now sends a value of 'ringing' for motion as well as for the doorbell button being pressed. There is no difference in value, both send 'ringing'. So any motion sets the value of State to ringing, so does pressing the ring button on the doorbell
Hope this makes sense

I have found the problem. I was looking at the 'state' rather than 'kind'. In state its always ringing, for motion as well as ringing. In Kind, its ding or motion...


text:
Ambiguous error message

I had this error message in the log:

unifi.0
2020-05-30 01:06:18.323
error
(5679) Error: Returned data is not in valid format

Can you provide more detailed information in the log about errors? That message does't help if there are no more detailed information.

Hi...
i have the same Situation... Adapter seems to work properly but the Log is spammed with the message
(19324) Returned datea is not in valid format.
I have corrected some internal namings with german 'Umlaute' but this does not help.

Same here: (10691) fetchSites: Returned data is not in valid format
It worked properly for several weeks. Today I reinstalled my Unifi-Gear, after that i got this massage...
Any idea?

Same here: (10691) fetchSites: Returned data is not in valid format
It worked properly for several weeks. Today I reinstalled my Unifi-Gear, after that i got this massage...
Any idea?

Problem solved. After I made my a new selection in the adapter (clients, online), the adapter started without error message.


text:
Project structure not according to spec with 4.1.1

According to
https://beta.ionicframework.com/docs/building/scaffolding
I should find karma config and a dedicated e3e folder next to the src folder.
Even though I strictly followed the starter process described in the beta doc I do end up with an "old" structure.
$ ionic --version
4.1.1

$ ionic start myApp tabs --angular

generates:

ionic start myApp tabs --type=angular
See https://beta.ionicframework.com/docs/installation/cli#start-an-app

repo: ionic-team/ionic


text:
bug: accessibility problem with VoiceOver and segment-button

Hello,
Ionic 5.1 / angular.
When VoiceOver displays a page during the first load, the first button is correctly stated as selected, with an aria-pressed = "true".
However, when the user clicks on the second segment-button, VoiceOver no longer knows which segment-button is selected.
Probably aria-pressed is not updated when selecting another button.
Thank you.
<ion-segment (ionChange)="segmentChanged($event)" mode="ios" value="apple">

Apple

Stripe

Thanks for the issue. Can you try the following dev build and let me know if it resolves the issue?
npm i @ionic/angular@5.2.0-dev.202005111937.1e6f923

Is good ! Thank you.

Thanks for the issue. This has been resolved via https://github.com/ionic-team/ionic/pull/21273, and a fix will be available in an upcoming release of Ionic Framework.

authors: liamdebeasi terrancle


text:
Changed "addditional" to "additional" on ion-progress-bar docs

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Build (npm run build) was run locally and any changes were pushed
[ ] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[ ] Yes
[x] No

Not sure if I need to do an npm build for the documentation, let me know and I'll get it done.

Thank you!

authors: brandyscarney wreiske


text:
No intellisense for script files on mac

Steps to reproduce:

create f# project: dotnet new console -lang f#
start vscode: code .
open Program.fs -> hover over main and observer that intellisense works
add test.fsx with the following contents: printfn "Hello World from F#!"
hover mouse over "printfn" and observe that no intellisense appear

Expected result:
at step 5 the same information should be printed as when hovering mouse over printfn for the Program.fs file
Additional info:
When opening the test.fsx file the following appears in the Output of the F# Language Service:
[14:43:28 ERROR] Cannot execute recordStubGenerator, File '/Users/olavnybo/source/test/test.fsx' not parsed
[14:43:28 ERROR] Cannot execute signature, File '/Users/olavnybo/source/test/test.fsx' not parsed
When hovering the mouse over the code the following is output:
[14:45:20 ERROR] Cannot execute tooltip, File '/Users/olavnybo/source/test/test.fsx' not parsed
Executing the script (test.fsx) from the command palette and selecting "F#: Run script"  works as expected. The terminal reads:
Hello World from F#!
Press enter to close script...
FSharp: Fsac Runtime is set to netcore
Same result if set to: net
FSharp: Fsi File Path is set to:
/Library/Frameworks/Mono.framework/Versions/Current/Commands/fsharpi
mono --version prints:
Mono JIT compiler version 5.16.0.179 (2018-06/6e48ad4f7b1 Wed Oct  3 14:05:19 EDT 2018)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS:           normal
SIGSEGV:       altstack
Notification:  kqueue
Architecture:  amd64
Disabled:      none
Misc:          softdebug
Interpreter:   yes
LLVM:          yes(3.6.0svn-mono-master/0b3cb8ac12c)
GC:            sgen (concurrent by default)
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.13
OS Platform: Darwin
RID:         osx.10.13-x64
fsharpi reports version: 4.1
fsharpi test.fsx prints "Hello World from F#!" as expected

I have the same issue with intellisense.
Could you please confirm also the CodeLens works fine for you?

CodeLens works fine for project files. E.g. in my example the Program.fs file shows code lens info.
Script files does not. I.e. no code lens shown in test.fsx.
Code outline works though. It will list all functions  in the active script file (fsx).
The get info for diagnostics does not work.
When selecting this command from the comman palette it displays a error box with the text:
Command 'F#: Get info for diagnostics' resulted in an error.

I think I have figured out why it was not working for me.
I am using fish shell and I had set the path for fish shell in ~/.config/fish/config.fish, but this seems to have no effect on the path used by ionide.
Adding:
export PATH="$PATH:/Library/Frameworks/Mono.framework/Versions/Current/Commands/"
to ~/.bash_profile fixed intellisense as long as fsacRuntime"="net"
Trying to use netcore as is suggested when opening the project after setting FSAC Runtime to .net does not work though.
"FSAC Runtime = netcore does not work" is already reported in:
#948 948, so I suppose this issue can be closed.

Path was not correctly configured for Bash and netcore not working is already reported in #948

authors: memoricab onybo

repo: ionide/ionide-vscode-fsharp


text:
Not working at all on Startpage.

Expected Behavior
Filtering should work on startpage.
Actual Behavior
Not filtering at all.
Steps to Reproduce the Problem
1.Install addon
2. Add an expression like *://*.reddit.com/*
3. Enable for startpage.com
4. Activate
5.Search for reddit
Specifications

Browser: Librewolf

Search engine: Startpage.com
Language: EN
Region: CA

It might be worth also checking the mobile version of startpage.

So, when's a new update going to be pushed for this? Because I really want to see all this junk disappear:
*://*.facebook.com
*://*.discord.com
*://*.discordapp.com
*://*.instagram.com
*://*.twitter.com
*://*.x.com
*://*.tiktok.com
*://*.wizzapp.com
*://*.reddit.com/*
*://*.fb.com/*
*://*.redditinc.com/*
*://*.linkedin.com/*
*://*.threads.com/*
*://*.meta.com/*
*://*.messenger.com/*
*://*.metacareers.com/*
*://*.snapchat.com/*
*://*.apple.com/*
*://*.icloud.com/*
*://*.live.com/*
*://*.msn.com/*
*://*.microsoft.com/*
*://*.office.com/*
*://*.skype.com/*
*://*.bytedance.com/*
*://*.microsoft365.com/*
*://*.windows.com/*
*://*.hpconnected.com/*
*://*.hpsmart.com/*
*://*.samsung.com/*
*://*.canon.com/*
*://*.play.google.com/*
*://*.myspace.com/*
*://*.adobe.com/*
*://*.photoshopessentials.com/*
*://*.photoshop.com/*
*://*.bing.com/*
*://*.bingplaces.com/*
*://*.xbox.com/*
*://*.adobepress.com/*
*://*.amazon.com/*
*://*.primevideo.com/*
*://*.deviantart.com/*
*://*.deviantartsupport.com/*
*://*.deviantartsell.com/*
*://*.pinterest.com/*
*://*.tumblr.com/*
*://*.quora.com/*
*://*.visualstudio.com/*
*://*.sharepoint.com/*
*://*.facebook.com/*
*://*.twitter.com/*
*://*.instagram.com/*
*://*.tiktok.com/*
*://www.redditstatus.com/*
*://www.redditforbusiness.com/*
*://support.reddithelp.com/*
*://www.whatsapp.com/*
*://*.x.com/*
*://business.tiktokshop.com/*
*://www.onenote.com/*
*://sway.cloud.microsoft/*
*://*.amazon.ca/*
*://*.yahoo.com/*
*://www.yahooinc.com/*
*://discord.com/*
*://discordapp.com/*

I am also facing this issue and after trying to debug it I found that the class name of startpage has most likely changed.
Specifically w-gl__result no longer exists and .result exists under .w-gl.
I tried adding the following config to my entryHandler but it didn't work:
          {
            target: '.result',
            url: '.result-title',
            title: 'h2',
            actionTarget: 'a[role="link"]',
            actionStyle: {
              display: 'block',
              marginTop: '4px',
            },
          },

What's strange is that the class name set with the result class displayed in Element is different from the corresponding class name set in Sources.
This is not seen in duckduckgo, which works properly.

What about just use .w-gl?

At least I don't think .w-gl can be used because it is a container for the entire search result.

link-text?

Thanks @misumisumi for the ideas for a solution.  I've looked at it some more and am currently trying this:
    entryHandlers: [
      // Web
      {
        target: '.w-gl > .result',
        url: '.w-gl > .result .result-title',
        title: 'h2',
        actionTarget: '.w-gl > .result > .description',
        actionStyle: {
          display: 'block',
          marginTop: '4px',
        },
      },
      . . .
   ]

This seems to make filtering work (I'm not sure what actionTarget is used for).  Please try this and let us know if it works for you.
However, there is still some more work to do.  It seems that the headline uBlacklist has blocked 1 site and Show button are not appearing at the top of the Startpage search results.
I have tried updating the control handler target
    controlHandlers: [
      // Web
      {
        target: '.Layout #main',
        style: defaultControlStyle,
      },
      . . .
   ]

but so far this hasn't worked. I'm not sure what it's looking for.
I may keep trying, though hopefully this info so far might be enough to be helpful to @iorate  😀

However, there is still some more work to do.

One of the problems is no showing Block this site, but I think this is due to the html class being changed for some reason.
For example in duckduck-go, elements and classes referenced from Element and content-script.js are the same.

But in startpage, elements and classes refferenced from element and content-script.js are not the same.
I checked with all other extensions such as adblock disabled, so I think it's a problem on the startpage side.

Probably, the behavior is to search for the entry container with target, specify the element within it with actionTarget, and add a block button with span to the specified element.

@misumisumi @stevehartwell
Thank you for your investigation. I'll fix this issue soon.
Since the current version of Startpage uses React, modifications by the content script are cleaned up by the hydration process. To avoid this, the content script should be run after the page is loaded:
https://github.com/iorate/ublacklist/blob/924de298eb24b4c1d5a741baa211c6675f926314/src/common/search-engines.ts#L527
This value should be "document_idle".

Probably, the behavior is to search for the entry container with target, specify the element within it with actionTarget, and add a block button with span to the specified element.

That's true.

authors: iorate linlinxza misumisumi stevehartwell

repo: iorate/ublacklist


text:
Make version selector more flexible

We can currently add a version selector by adding versioned folders at the top level of a project.
Sometimes we may need to version only a single guide instead of the whole project. For example, we may want to version the MAM API reference.

Closing this as we have solved it with a new content architecture on the documentation repo.

repo: iotaledger/documentation-platform


text:
[Task]: Add AddEvmChainForm validation logic

Task description
With the form to add an EVM chain stubbed out, the next step is adding form validation logic.
Requirements
TBD
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Blocked by #6581

authors: Tuditi maxwellmattryan

repo: iotaledger/firefly


text:
[iota-graphql-rpc]: Upgrade async-graphql

Description
There are security warning stemming from the version of async-graphql used that warrant an upgrade.
https://github.com/iotaledger/iota/security/dependabot/3

@samuel-rufi check this patch for the padding problem

repo: iotaledger/iota


text:
Feat(client): state synchronization of snapshots and clients

Description of change
This PR implements a synchronization feature that allows to fully or partially merge the vaults between two structures.
For this, it introduces a new trait MergeLayer for merging two instances, and implements it for the Client-Layer (= sync of two client states) and Snapshot-Layer (= sync of two snapshot states).
The steps for a full synchronizing of an instance A with an instance B (i.e. A would like to import all records from B that it does not have yet) are:

get the full hierarchy of all ids stored B
compare this hierarchy at A with the local hierarchy to get the diff
export all entries from B that are in this diff
import entries at A

Since the keys usually differ between two instances, the old keystore(s) should be provided on import to decrypt each record with the old key and re-encrypt it with the local one.
In case of a remote sync, the exported entries are imported to an empty snapshot that internally populates a new keystore with temporary keys. At the remote the entries are then exported from received state and imported to the local state.
The described fundamental steps can be enhanced with the optional mapper if A and B have different Ids for the same client / vault / record. This mapper maps one full path (VaultId ++ RecordId in case of client-sync, ClientId ++ VaultId ++ RecordId in case of snapshot-sync) to another, optionally returning a None in case of a partial sync where only some of the records should be imported.
For handling conflicts (a client / vault / records exists both, at A and B, but differs in the content) a merge policy is required from the user, which specifies whether to keep the old values, replace it with the new, or recursively merge the entries.
Note: For remote sync, certain functionalities for loading and persisting client states are required (Stronghold::fill_snapshot_state and Stronghold::load_state). These were still in discussion in https://github.com/iotaledger/stronghold.rs/pull/296#issuecomment-982283276, and will be solved after the upcoming refactoring once we implement the RFC of #308. However, I had to add them here already in order to integrate remote sync into the interface. @tensor-programming since you were against adding them, I would propose to finish this PR, but not merge it before the refactoring. Once we have the refactoring done, I can change the sync-feature to use the new, more secure architecture.
(Another) Small Note: The priority in the implementation is to be fully flexible for the different use cases, but introduce as little overhead as possible. Therefore it attempts to only do a re-encryption if it is really necessary, and drop records according to the merge policies as early as possible if they won't be imported anyway. With this the MergeLayer::import_entries implementation for the two layer turned out to have a lot of duplicated code for the different cases (Mapper: yes/no; Old-Keystore: yes/no). I did not find a cleaner way to implement this, but I would be grateful for any ideas on how two improve the code quality there.
TODOs:

[x] Remove unwraps, add proper error handling
[x] Remote sync

[x] implement remote sync
[x] fix serialize for HashMap with client::utils::ids::Id as key:

Serialization can fail (..) if T contains a map with non-string key

[x] Integration into interface
[x] Encrypt snapshot key on remote sync

Links to any relevant issues
Issue #278. Alternative implementation to #292, minus the policy engine.
Type of change
Choose a type of change, and delete any options that are not relevant.

[x] Enhancement (a non-breaking change which adds functionality)

How the change has been tested

unit tests sync::test::{test_get_hierarchy, test_export_with_mapping, test_merge_policy}.
integration tests: tests::synchronization_tests::{sync_clients, remote_sync}

Change checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Closing this PR in favor of #334, which implements a simpler version of the synchronization feature. This PR may still be used as reference when adding remote synchronization.


text:
check out the error in build.

(Emitted value instead of an instance of Error) Cannot find source file 'MutationObserver.js': Error: Can't resolve './MutationObserver.js' in '/Users/dong/iotex/iotex-explorer/node_modules/mutationobserver-shim/dist'

repro:
npm run start
check this error in list.

if it dos not affect at all, please close.

repo: iotexproject/iotex-explorer


text:
[master] apply some new wireframe

those are not the final design. and we should not follow them literally. Just add functionalities in ant design which we currently have.

add blocks / block :height / action list / action detail navigation
improve action page details
improve block page details
improve home page

add block list
update stats area

Just to mention analytics:

bookkeeper apis
productivity
accounts: active accounts, rank

Component

add blocks / block :height / action list / action detail navigation #395

Function

Add one more analytic API: GetRewardsByAddressAndEpoch

authors: lizhefeng puncsky uu-z


text:
Fix some errors.

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Modifications about dtls_session_send and dtlsSessionPopulateKeyingMaterial  LGTM.


text:
CLI Webhook HTTPListener does not receive traffic from NGROK

Upon running service-auth-webhook the console will display:
Webhook: Starting HTTP listener.
Webhook: Waiting for a request ...
Upon responding to the auth, the socket is never hit when using a proxy like NGROK. Testing the same flow on a Windows VM works fine, so I suspect the HTTPListener isn't playing nicely on Mac and potentially Linux (unconfirmed).

This was resolved with the recent changes for the 3.4.0 release that allow the netcore20 target for the example CLI.

repo: iovation/launchkey-dotnet


text:
Use kfunc__sched_fork instead of kfunc__strlen for kfunc detection

The strlen function can be compiled out in some kernels.

Can you give it a clang format?

Can you give it a clang format?

authors: danobi olsajiri

repo: iovisor/bpftrace


text:
Provide arithmetic operations on IPv4 and IPv6

Hi, this functionality was ready since a long time but unfortunately never made the merge. Would appreciate a lot to get it merged into the new gem. Thanks a lot for your time and effort!

Thanks for the pull request. I managed to merge it with master and will put a new gem version out soon.


text:
feat: beautiful icons by @akrych

That's it.
/cc @olizilla

@olizilla just made some changes. The class fill-color should be added to the <svg> element.

Although I'm more into creating a font with the icons and then having a class for each icon.

Can we merge this?

Ping @olizilla :D

@hacdias this looks good. Can you resolve the conflicts and remove the transition from the hovers and it's good to go.

@olizilla rebased!! 😄

ok, i'll merge this and remove the transition as that can be done with a separate atom.

authors: hacdias olizilla

repo: ipfs-shipyard/ipfs-css