Fix for usage in Engines and nested addons, remove the need for htmlb…

…ars plugin

Hmm. This will collide with any variable named title. Is there any way to allow the AST transforms work with this?

Well, I'd say that's kind of expected when you use a helper named title, but I can see the problem. It doesn't work if you include htmlbars into the nested addon's dependencies instead of devDependencies, but I'm afraid I don't know enough about Ember internals to fix it. Maybe you could try it with Engines demo apps? https://github.com/dgeb/ember-engines-demo and https://github.com/dgeb/ember-blog-engine

I added ember-cli-htmlbars as a direct dependency of ember-page-title: https://github.com/tim-evans/ember-page-title/commit/da9af61447aa152415268bdc3b22b78422dcc3ba

If this doesn't resolve the issue, please open a new issue :)


add jobFailed() to docs

I had to dig for this one, hopefully this change saves others some time.

Thanks!


shuffle function test case

Generated this one very simple test in Python side. Before the standardized testing format, can dear other clients sides help to check in your codebase as well? :)
import pytest

from beacon_chain.state.helpers import (
    shuffle,
)
from beacon_chain.utils.blake import blake

@pytest.mark.parametrize(
    (
        'values,seed,expect'
    ),
    [
        (
            [i for i in range(100)],
            b"\x8d\x8dd\xb9\x84\x05*Bw\xf5\x87\xdd\x04nj\xee\x82\xfc9\xb9\x19\x82'x!#p];\xa5\x8e\xc9",
            [87, 32, 76, 41, 61, 9, 44, 78, 70, 42, 8, 6, 79, 37, 4, 67, 3, 66, 55, 0, 69, 98, 38, 47, 20, 31, 48, 97, 34, 33, 96, 63, 91, 15, 1, 77, 39, 64, 58, 53, 82, 49, 26, 29, 5, 65, 19, 86, 74, 23, 46, 14, 10, 51, 85, 89, 57, 73, 71, 52, 88, 30, 16, 81, 24, 22, 36, 45, 12, 2, 62, 93, 18, 72, 83, 95, 13, 21, 27, 28, 80, 43, 68, 59, 94, 60, 99, 56, 92, 54, 25, 75, 7, 90, 50, 35, 11, 84, 17, 40],
        ),
        (
            [i for i in range(12)],
            b"&P\x18'\x91\xf6\x8f\xc8;<\xb8\x8f\x1d\x92?\xad4\xb5\xb8\x0b\xca\x8a'\x8e\xae'\xcf7\xa3(\xb2\x8d",
            [7, 3, 2, 5, 11, 9, 1, 0, 4, 6, 10, 8],

        )
    ],
)
def test_shuffle_consistent(values, seed, expect):
    assert shuffle(values, seed) == expect

Updated: added Lighthouse's testcase.

cc @@paulhauner I just tested lighthouse's testcase, works for Python side too! 👍

Ahh sorry! Just updated the testcase again. Thank you @mkalinin! :)


Prompt Engineer the Scheduling Request!

The file api_notebook.ipynb contains a first draft of a prompt and instructions. It works, but it can certainly get better!
We need to optimize a prompt that hallucinates as least as possible. You can either try in your local machine and post the suggestion here, or try it in the notebook and submit a pull request.

Hey I have worked with LLMs(OpenAI, Llama etc) and prompt engineering for the past year, including SoTA techniques like Chain-of-Thought, Zero/Few shotting etc. I can help you with this. Are there any benchmarks that I can use to compare the results?

Sure, I would love to take some ideas from you. You can reach me on Discord at aalejandrx!

Cool, I have sent you a friend request in Discord. My id is smantony. If we could come to a conclusion, I would love for this to be my first pull request which could be merged 😊


Use Configuration class to pre-process configuration objects (e.g. Path(local_temp_path).expanduser())?

The Pydantic Configuration model (in nowcasting_dataset/config/model.py) could perhaps be responsible for converting YAML configuration to the object that downstream-code uses... e.g. converting paths to Path or Pathy objects, and expanduser() where necessary?

Hi Jack,
If I understand correctly, this could be done by adding a validator in Process for local_temp_path ? The same way as the filepath validator in OutputData.

I think that's right!  @peterdudfield is the real expert on Pydantic though... what do you think of this plan, Peter?

Hi Jack,
If I understand correctly, this could be done by adding a validator in Process for local_temp_path ? The same way as the filepath validator in OutputData.
Thanks !

I think thats a great idea, and a good way to do it

Great, thank you both! I should handle that this week


Enable Auto rotation of labels (#250)

Fixes #250

One more thought. Should we make 'auto' the default? (Would match the PR description better :))

One more thought. Should we make 'auto' the default? (Would match the PR description better :))

Yes, we could (not should !! ;)). The only point of attention to do it is ,changing the default, the label will follow always the line and currently the default is to have the label horizontally (rotation 0).
Some users could not appreciate that.


Can't move the screen left and right on the touchpad

Issue Type: Bug

Can't move the screen left and right on the touchpad

2.setting sync can't download sync, but on my other machine， it's  work
VS Code version: Code 1.35.1 (c7d83e57cd18f18026a8162d042843bda1bcf21f, 2019-06-12T14:27:31.086Z)
OS version: Linux x64 4.15.0-20-generic

System Info

Item
Value

CPUs
Intel(R) Celeron(R) CPU N3450 @ 1.10GHz (4 x 1596)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwaresurface_synchronization: enabled_onvideo_decode: unavailable_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 1

Memory (System)
5.67GB (0.96GB free)

Process Argv
--unity-launch

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

code-runner
for
0.9.11

vscode-language-pack-zh-hans
MS-
1.35.1

code-settings-sync
Sha
3.2.9

Can't move the screen left and right on the touchpad

Can you clarify what you mean by this?

setting sync can't download sync, but on my other machine， it's work

You will need to create an issue on the extension's repo https://github.com/shanalikhan/code-settings-sync

I mean: In the VSCode, use the touchpad to slide, move to the left and right, the interface will not change, you can only move by the cursor
(I am sure the line length exceeds the screen width)

I mean: In the software, use the touchpad to slide, move to the left and right, the interface will not change, you can only move by the cursor
(I am sure the line length exceeds the screen width)


passwd: Add -rounds option to specify rounds independent of salt

As explained in #16530 , passwd only allows number of rounds used with SHA256/SHA512 algorithms to be specified as part of a salt. This change adds a -rounds option to passwd to explicitly specify the number of rounds, while letting the salt itself to be generated randomly.

Checklist

[x] documentation is added or updated
[x] tests are added or updated

Could you please sign a CLA? We cannot accept the PR without it.
https://openssl-library.org/policies/cla/index.html

@t8m I've sent in the CLA. Do I need to close this pull request and open a new one?

Could you please drop the merge commit? git reset --hard HEAD~ ; git push --force should help.

Oops, that merge commit definitely shouldn't have been there. Fixed.

The CI is relevant.

Ooops. I think I did this rebase very wrongly.


Pool member creation fails with network_type opflex

Issues:
Fixes #443
Problem:
The fix for F5Networks/f5-openstack-lbaasv2-driver#353 enabled the
F5 driver/agent to detect and bind a virtual server to a dynamic VLAN
segment, created by Cisco ACI. Now pool member creation fails because
the agent cannot find the VLAN segment for the pool network.
Need to allow member creation with missing seg ID or network segment.
Community code already knows how to do the right thing to create a VLAN
network segment under the opflex parent. Follow that for member creation.
The current agent code expects the VLAN to be present prior to member
creation. For type opflex, need to move this earlier in the workflow.
Analysis:

If the port for the service does not exist, we create one with the
f5lbaas device owner.
Add logic to delete ports on member delete
if the owner is f5lbaas.
Add logic to detect opflex network_type in disconnected service.
Add segment data to pool member network definition.

Tests:
Manual:
Create loadbalancer service with all objects: listener, pool, members
Create member with and without existing port.
Create member on opflex network, add vlan child segment manually and
verify that the member is connected.
Create listener on opflex network, add vlan child segment manually
and verify that the virtual is created.
Create listener on opflex network, don't add segment and check that
the loadbalancer is put in 'ERROR' state after timeout.
TODO:
Automate above tests.
Run neutron-lbaas scenario tests.

In the Tests section for the PR comments, I believe you also re-wrote the existing automated disconnected tests.  Add that comment and any deviations (like the gross timeout test that won't run since our standalone tests are icontroldriver based instead of agent-manager).


How

Hi guys, I'd like to encrypt the advertise packet since some secure fields in the payload, and also the scanner can decrypt the packet automatically. So anybody knows how to implement this feature with zephyr?


Add atlantis

Add once https://github.com/runatlantis/atlantis/issues/3741 is merged.

https://www.runatlantis.io/blog/2024/integrating-atlantis-with-opentofu

https://github.com/runatlantis/atlantis/releases/tag/v0.30.0


Add talk image notebook

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 51.776%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
476

Relevant Lines:
813

💛  - Coveralls


DNS: Merge two definitions of RDATA

The new union approach is superior, but some lingering declarations
were left behind.

I also did a few minor changes: using visibility qualifiers, adding / moving documentation, and renaming cname to just name as it's used by other records (e.g. NS).

This apparently broke docker build
source/agora/common/DNS.d(670,13): Error: field `RDATA.a` cannot access pointers in `@safe` code that overlap other fields
source/agora/common/DNS.d(675,13): Error: field `RDATA.name` cannot access pointers in `@safe` code that overlap other fields
source/agora/common/DNS.d(680,13): Error: field `RDATA.soa` cannot access pointers in `@safe` code that overlap other fields
Type 'FlashControlAPI' implements more than one interface: make sure the one describing the REST server is the first one

It needs to upgrade the ldc2 to the latest version.

It needs to upgrade the ldc2 to the latest version.

Weirdly, it is already on v.1.28.0

I had the same problem on the local machine yesterday. I solved the problem with brew update & brew upgrade, so I thought the version was old. But it could be aroused from another cause, I guess.

Actual PR that added mentioned code is #2711 BTW, it didn't throw any errors on my machine

As discussed on Slack, it was an outdated agora-builder locally.


libcamera-detect: add multiple file name output generation options

Added file name generation similar to libcamera-still including timestamp and datetime. Also added a the --timeformat argument to allow passing in custom strftime() date/time format strings when the --datetime option is true. The default value for timeformat is: "%m%d%H%M%S". The file extension is set by options->encoding for the datetime and timestamp options.
The default --output option retain its previous functionality.
Examples:
-o /home/user/capture/car- --datetime
output file: car-1223033452.jpg
-o /home/user/capture/car- --timestamp --timeformat "%F %r"
output file: car-2022-12-23 03:34:52 PM.jpg
-o /home/user/capture/ --timestamp
output file:<PHONE_NUMBER>.jpg
-o /home/user/capture/car%03d.jpg (Default/Existing)
output file: car001.jpg

@ThingEngineer, thanks for the patch!
Functionally, it looks fine and I am happy to merge it.  Before I do, could you squash both commits down into one as they are related, and could you re-format the commit message please.  We need a small title with an appropriate prefix (probably "libcamera_detect:" in this case), and a small description of the change.  Have a look at the git log to see examples of other commit message formats.


Support players that do not need random states

Add a configuration key random in the player configuration file to declare whether random numbers are required, for example:
https://github.com/DataCanvasIO/TSBenchmark/blob/54bf8d33b1eaf8fcc9fb259b7f1924ce55fb2ab3/tsbenchmark/tests/players/non_random_player_univariate/player.yaml#L8


Not running 'apt update' causing: "E: Unable to locate package unzip"

Flag --client has been deprecated, use the new flag client-addr
[INFO] Uploading generated Consul configuration ...
[INFO] Installing Consul ...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package unzip
error received during installation: Process exited with status 100

Logging in on the server and running apt update first solves the issue. :)  (ah and also, the docs said to use --client, but I see it is now --client-addr.)

Hi @odinho
Apologies for the late reply ;-)
I considered adding this to the script, but most of the time this shouldn't be necessary and executing apt update every time can slow down the installation.
But if hashi-up can access the target host via ssh, the user can easily execute apt update remotely as well:
ssh root@$TARGET_IP "apt update"
# or
ssh ubuntu@$TARGET_IP "sudo apt update"

Could maybe come with that suggestion/hint if you already are reading error messages. : )


Re-organize code to have pkg/ebpf only be common eBPF code

What does this PR do?
Re-organizes code such that pkg/ebpf is common eBPF related functionality, while pkg/network, pkg/security, and pkg/collector/corechecks contain the eBPF code for their respective functionality.
It also makes clear how an eBPF program is compiled, by putting those programs in specific folders:

with BCC (bcc)
prebuilt with clang (prebuilt)
runtime compiled (runtime)

Motivation
All feature functionality should live next to where it is used.
Additional Notes

tracer-ebpf renamed to tracer since the ebpf part is implied.

Describe your test plan
No functionality change.

Should we have the same package structure in pkg/security/ebpf/c ?

Yes. Just pushed that change.


squoosh cli windows conversion stuck

Installed on Windows 10 with following cmd: npm i -g @squoosh/cli
Ran squoosh-cli --webp auto pic.png, which created pic.webp (but it was larger than original png
Then tried squoosh-cli --webp '{"quality":75}' pic.png
It starts but is stuck on 1 thread, even after 30 min:
0/1 | ▐▨▨▨▨▨╌╌╌╌╌▌ Encoding (8 threads)
pic.png: 15.66KB(node:13288) UnhandledPromiseRejectionWarning: Cannot use 'in' operator to search for 'lossless' in {quality:75}
(Use node --trace-warnings ... to show where the warning was created)
(node:13288) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:13288) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejection0/1 / ▐▨▨▨▨▨╌╌╌╌╌▌ Encoding (8 threads)

What is your Node version? Can you make sure you are using the latest Squoosh CLI by using npm i -g @squoosh/cli@latest? Does the problem still occur?

Hi @surma
My node version is v14.15.4. I ran pm i -g @squoosh/cli@latest, but still get the same error.

Thanks, @PetrusVermaak.
I can’t reproduce this on MacOS or Linux. So I guess this is an issue with Windows. I don’t have a machine at hand, so if anyone wants to help here, that’d be awesome.
$ docker run --rm -ti -v /Users/surma/Downloads:/Downloads node:14.15.4 /bin/bash

# root@acab10b6660b:/# npm i -g @squoosh/cli
/usr/local/bin/squoosh-cli -><EMAIL_ADDRESS>/usr/local/bin/cli -><EMAIL_ADDRESS>+<EMAIL_ADDRESS>added 37 packages from 39 contributors in 2.815s

# root@acab10b6660b:/# squoosh-cli --webp '{"quality":75}' /Downloads/squoosh.png
1/1 ✔ Squoosh results:
 /Downloads/squoosh.png: 72.68KB
  └ squoosh.webp → 13.79KB (19.0%)

Windows here!
Funny, I tried first to reproduce on Powershell and there was no issue.
> ~\Downloads\node-v14.15.4-win-x64\node<EMAIL_ADDRESS>--webp '{"quality":75}' .\heaps.png
⠋ (node:15588) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 unpipe listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
(node:15588) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 error listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(node:15588) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 close listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(node:15588) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 finish listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
1/1 ✔ Squoosh results:
 .\heaps.png: 111.55KB
  └ heaps.webp → 9.86KB (8.83%)

Then, I opened a regular Command Prompt and found that I could reproduce it.
The problem TypeError: Cannot use 'in' operator to search for 'lossless' in {quality:75}:

does not occur in powershell (weird!)
also occurs in node version 16.4.0
has the full stack trace:

TypeError: Cannot use 'in' operator to search for 'lossless' in {quality:75}
    at Object.toWireType (C:\Users\jcao2\dev\squoosh\libsquoosh\build\index.js:1:96950)
    at Object.encode (eval at new_ (C:\Users\jcao2\dev\squoosh\libsquoosh\build\index.js:1:104602), <anonymous>:10:26)
    at encodeImage (C:\Users\jcao2\dev\squoosh\libsquoosh\build\index.js:37:73)
    at async MessagePort.<anonymous> (C:\Users\jcao2\dev\squoosh\libsquoosh\build\index.js:26:742)

Hmm, so further investigation showed me that using this command:
npx @squoosh/cli --webp "{\"quality\":75}" heaps.png (notice the double quotes and escaping)
makes it work on Windows Command Prompt. The root issue has something to do with CLI arg parsing?

It appears that in the Windows Command Prompt, single quotes are simply parsed as an ordinary character. So the command is the equivalent of doing in Powershell or even a POSIX Shell something like:  npx @squoosh/cli --webp "'{quality:75}'" heaps.png which reproduces the original error, Cannot use 'in' operator to search for 'lossless' in {quality:75}
We should do better CLI arg validation in order to prevent this.

@jcao219 PowerShell!! That worked!! Still cannot get your npx @squoosh/cli --webp "{\"quality\":75}" heaps.png to work on Windows cmd, but happy that I can get it to work on PowerShell.
Sorry for asking, but how would I convert all jpg and png and output them in the same folder? I tried: squoosh-cli --webp '{"quality":75}' ./*.* but no go. Am new to running scripts and all that...

And just a big thank you to @surma and @jcao219 for the awesome support and helping a total noob. Much appreciated!!!! :D

@PetrusVermaak Wildcards are not quite working yet on Windows, see #973.

For those who want to batch on Windows 10:
Finally managed to get macOS going on vmware, installed node.js from https://nodejs.org/en/download/ and batch cmd squoosh-cli --webp '{"quality":75}' ./*.* is working!! Yea it's ugly but it works...
@surma & @jcao219 When wildcards are fixed on Windows 10, please let us know! :D

I can work  on cmd of Windows 10 as @jcao219 said, using the command like:
npx @squoosh/cli --mozjpeg "{\"quality\":80,\"baseline\":false,\"arithmetic\":false,\"progressive\":true,\"optimize_coding\":true,\"smoothing\":0,\"color_space\":3,\"quant_table\":3,\"trellis_multipass\":false,\"trellis_opt_zero\":false,\"trellis_opt_table\":false,\"trellis_loops\":1,\"auto_subsample\":true,\"chroma_subsample\":2,\"separate_chroma_quality\":false,\"chroma_quality\":75}" "C:\Users\dell\Desktop\IMG_20210729_195643.jpg"

On Windows:
cd the folder containing images to optimize and run the command without single quotes around config parameters (keep curling braces):
cd C:\Path\To\Folder\
npx @squoosh/cli --mozjpeg {qality:30} filename.png
@surma I tried various commands without luck for batch optimization, including wildcard *.png ;  * ;  etc. no luck. Any hint ?

@ivanshilo cmd works like a charm, thanks for sharing.
Only thing is I'm getting a warning message and squoosh cli gets stucked:
- (node:9092) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 unpipe listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
(node:9092) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 error listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(node:9092) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 close listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(node:9092) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 finish listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
30/32 / ▐▨▨▨▨╌╌╌╌╌╌▌ Decoding...
0/32 - ▐▨▨▨▨▨╌╌╌╌╌▌ Encoding (12 threads)
 src\images\ajh.png: 747.46KB
 src\images\Copy of IMG-20201127-WA0006.jpg: 144.98KB

@shirokoweb Quick search shows something similar to your problem: https://stackoverflow.com/questions/50709059/maxlistenersexceededwarning-possible-eventemitter-memory-leak-detected-11-mess
By default there are maximum 10 event listeners in node.js 'event' module allowed. It sounds for me like a software issue in squoosh (either bug with unsubscribing from event or wrong initial code configuration - should be more than 10 allowed)
What happens if you process only 9 images in your folder?

can you please share how?

or those who want to batch on Windows 10:
Finally managed to get macOS going on vmware, installed node.js from https://nodejs.org/en/download/ and batch cmd squoosh-cli --webp '{"quality":75}' ./*.* is working!! Yea it's ugly but it works...

can you please share how?

is still wildcards an issue using windows ? I am facing the same<EMAIL_ADDRESS>and node js 14.13.2 windows 11

Unfortunately, due to a few people leaving the team, and staffing issues resulting from the current economic climate (ugh), the CLI and libsquoosh packages are no longer actively maintained. I know that sucks, but there simply isn't the time & people to work on this. If anyone from the community wants to fork it, you have my blessing. The squoosh.app web app will continue to be supported and improved.


Maximum Number of Levels of Gaussian and Laplacian pyramid now as expected.

Until now, the amount of levels depended on the mount of twos in the prime factors of the width/height of the input image.

I think it is helpful to have a general image Pyramid.
I'm however not sure if it is a good idea to replace the more restrictive implementation. Maybe some algorithm would produce wrong results in some cases. Further is it well defined (is there only one way) how to align the lower pixels grid to the upper? And how to calculate the lower levels?

The thing with the 1:2 pixel grids is: We never really use this information anyway. In the current implementation, upscaling uses the resample method. This method is not using this information explicitly and always solves the general resampling problem using the specified interpolation kernel and interpreting pixels values as cell-center sample points. It cannot profit from an exact 1:2 relation. Also, frameworks, such as OpenCV, allow to create pyramids from odd-sized dimensions. The smaller image's size is then just rounded. Reconstruction in the Laplace pyramid should not be an issue because the difference of the original and the actual upscaling is stored. So, a perfect reconstruction is still possible.
The issue is keeping the upscaled size somewhere - as multiplying by 2 is not always correct. However, in the Laplacian pyramid (the only case where this is required), you can easily have this as the size of the next larger level.
Currently, I do not see a problem with rounding of size. However, OpenCV does mathematical rounding - "55 -> 28". In this proposed implementation, we loose a pixel due to integer division (floor).

I have updated the pull request and adressed your comments.
The expand function is now independent of the scaling of the reduce function used in the GaussPyramid:

It is now possible to have a LaplacePyramid with scalings other than 2 for example 3.
The LaplacePyramid and the GaussPyramid are now consistent in their scaling behaviour.
Example reduce function: GaussPyramid.reduceScaled

These changes are reflected in the tests too.
I think that these changes make the pyramids more useful and the code less complicated because the maximum number of reductions is inferred from the reduce function.

With the provided changes I see the raised concerns of the reviewers addressed and resolved and the PR ready to be merged.


Fix seek

Goal
To fix seek in iOS 10.3.
How to test

Test the startAt
Try to do a seek when the player receives a ready event.
Test manually a seek in a video.

Hey guys,
Don't forget to remove the readyToPlay from our events if we won't use it anymore to fix the seek issue.


Implement key generation, signing, and verification for secp256r1

Use secp256k1 from TypeScript SDK as a reference:
https://github.com/TBD54566975/web5-js/blob/main/packages/crypto/src/crypto-primitives/secp256k1.ts

@frankhinek if memory serves, secp256r1 was added because it's FIPS compliant. secp256k1 is as well right?


Add what's new page for September 2020

Major rewrite and include .NET 5

[Handle errors in ASP.NET Core](xref:fundamentals/error-handling)


What is the  commond for devlake  installation

What is the  commond for devlake  installation

You can follow the Installation from the Readme.md
Follow up link : https://devlake.apache.org/docs/QuickStart/LocalSetup/

Yes, it's run in docker. Or you can add our WeChat group to get enthusiastic help.

suggest docker deploy @matthewxuda


Update real-time-marketing-developer-push.md

Additions to code

@alfergus Please have a look to approve - thanks.


Filter dialog doesn't show all options for Postgres composite type subfields, even with "Read from server" checked

System information:

Operating system (distribution) and version: Windows 10 Pro 21H1
DBeaver version: 21.3.1
Additional extensions: Office support, git support, SSHJ, Debug and SVG

Connection specification:

Database name and version: Postgresql 14.1
Driver name: PostgreSQL JDBC Driver
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
When I click on the funnel icon at the header of a subfield of Postgres composite column, the filter window that appears for me to select the values only shows those that are already loaded in the data editor. Keeping "Read from server" checked doesn't seem to make a difference.
Steps to reproduce, if exist:

Create testing set:

CREATE TYPE inventory_item AS (
	name text,
	supplier_id integer,
	price numeric(5,2)
);

CREATE TABLE test (
	id integer PRIMARY KEY GENERATED ALWAYS AS IDENTITY,
	item inventory_item
);

INSERT INTO test (item)
	SELECT ROW('Item ' || n, n / 10 + 1, random() * 100)::inventory_item
	FROM generate_series(1, 1000) as n;

Open table test in the data editor with the result-set fetch size set to 200. Make sure it didn't load more than the first 200 rows.

Click on the filter icon of column item.supplier_id. Make sure "Read from server" is checked. You should see only values 1 to 21, like this:

If you scroll to the bottom of the currently loaded rows in order to load the next 200, repeating step 3 will show values 1 to 41. And so on.

Include any warning/errors/backtraces from the logs

!ENTRY org.jkiss.dbeaver.model 4 0 2021-12-22 14:05:24.613
!MESSAGE SQL Error [42809]: ERROR: "inventory_item" is a composite type
  Position: 35
!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2021-12-22 14:05:24.613
!MESSAGE ERROR: "inventory_item" is a composite type
  Position: 35
!STACK 0
org.postgresql.util.PSQLException: ERROR: "inventory_item" is a composite type
  Position: 35
	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2440)
	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2183)
	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:308)
	at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441)
	at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365)
	at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:143)
	at org.postgresql.jdbc.PgPreparedStatement.execute(PgPreparedStatement.java:132)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCPreparedStatementImpl.execute(JDBCPreparedStatementImpl.java:261)
	at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCPreparedStatementImpl.executeStatement(JDBCPreparedStatementImpl.java:205)
	at org.jkiss.dbeaver.model.impl.jdbc.struct.JDBCTableColumn.getValueEnumeration(JDBCTableColumn.java:240)
	at org.jkiss.dbeaver.ui.controls.resultset.valuefilter.GenericFilterValueEdit$5.lambda$0(GenericFilterValueEdit.java:344)
	at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:171)
	at org.jkiss.dbeaver.ui.controls.resultset.valuefilter.GenericFilterValueEdit$5.readEnumeration(GenericFilterValueEdit.java:342)
	at org.jkiss.dbeaver.ui.controls.resultset.valuefilter.GenericFilterValueEdit$KeyLoadJob.run(GenericFilterValueEdit.java:633)
	at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

thanks for the report


Updated Swift Autocompletion Syntax

Performed updates to the Swift Snippets JSON so that they match the latest language syntax
Updated :

print()
repeat {} while

Added :

Guard statement
Optional Binding Statement

Hi @alexaubry, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@alexaubry, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Thanks @alexaubry !


PNaCl kernel refactoring

Note: this concerns code that will be committed to naclports, not this repo.
The current version of kernel.py is based on overriding certain classes defined by IPython.  However, this is done in a very messy way that requires duplicating a lot of IPython code.
A much cleaner approach would be to subclass the IPython.kernel.zmq.Session and create alternative implementations of zmq.eventloop.zmqstream.ZMQStream and zmq.Socket.
@MatthewTurk You probably know more about zmq, while I'm more familiar with the IPython internals.  What do the ZMQStream and zmq.Socket classes look like?  Are they trivial to override or does their public interface include ZMQ specific things?

This version of colaboratory is no longer supported, please switch to https://colab.research.google.com.


MarkdownString.appendText doesn't handle visually significant whitespace

VSCode Version: Code 1.30.2 (61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8, 2019-01-07T22:54:13.295Z)
OS Version: Windows_NT x64 10.0.17763

Steps to Reproduce:

Respond to an LSP hover with a MarkupContent of kind plaintext with visually significant whitespace.
See hover formatted improperly in the editor.

Does this issue occur when all extensions are disabled?: N/A
The Python extension uses vscode-languageclient to communicate with a language server over LSP. The LSP has support for plaintext as a markup kind in many calls, for example, hover. vscode-languageclient converts MarkupContent of kind plaintext to VS Code's MarkdownString by using appendText to append the text as is:
https://github.com/Microsoft/vscode-languageserver-node/blob/5a198a0982e3d8f538a2f30fa87eb4ca27f1728d/client/src/protocolConverter.ts#L294-L297
Which is implemented as:
https://github.com/Microsoft/vscode/blob/527b6628e6bdcb046a31bbcb0cd17c3702c4ee8a/src/vs/base/common/htmlContent.ts#L24-L28
However, escaping these special characters isn't enough to convert plaintext to something that's rendered properly in markdown. For example, the following Python code:
def func(param1=True, param2='default val'):
    '''Description of func with docstring groups style.

    Params:
        param1 - descr of param1 that has True for default value.
        param2 - descr of param2

    Returns:
        some value

    Raises:
        keyError: raises key exception
        TypeError: raises type exception

    '''
    pass

Could produce, on hover of func, the following LSP response:
Result: {
    "contents": {
        "kind": "plaintext",
        "value": "func(param1=True, param2='default val')\n\nDescription of func with docstring groups style.\n\n    Params:\n        param1 - descr of param1 that has True for default value.\n        param2 - descr of param2\n\n    Returns:\n        some value\n\n    Raises:\n        keyError: raises key exception\n        TypeError: raises type exception\n\n    "
    },
    "range": {
        "start": {
            "line": 0,
            "character": 4
        },
        "end": {
            "line": 0,
            "character": 8
        }
    }
}

The signature is on the first line, followed by the docstring unmodified. However, the hover actually appears as:

Because in markdown a four space indent means a code block, producing a dual effect of text being rendered as code and exposing the markdown escaping done previously.
A more extreme example:

For our purposes, it may be "enough" for the leading whitespace to be replaced with  , but that may not fully handle every case.

Easy to reproduce using VS Code API only:
	vscode.languages.registerHoverProvider('bat', {
		provideHover: (doc, pos, token) => {
			let content = new vscode.MarkdownString();
			content.appendText("func(param1=True, param2='default val')\n\nDescription of func with docstring groups style.\n\n    Params:\n        param1 - descr of param1 that has True for default value.\n        param2 - descr of param2\n\n    Returns:\n        some value\n\n    Raises:\n        keyError: raises key exception\n        TypeError: raises type exception\n\n");
			return new vscode.Hover(content)
		}
	});

@jrieken  , can I take a look at this ?
A few starter and code points would be helpful.
Thanks :)

@skprabhanjan Did you read the issue? It points precisely to the line of code that's troublesome ;-)

@jrieken , Sorry about that , I read the issue but forgot to update the comment.
With what should I go ahead here ? Just replacing leading whitespaces with &nbsp ?
This will not fully handle every case as suggested and discussed by @jakebailey as well :)
Thanks :)

/verified

Hacking pylance to do plaintext in insiders:

And on the stable build:

We still do markdown, but thanks for fixing this; I'm sure someone'll be happy. 🙂


Homography

In the paper it was mentioned that homography is performed to align the two video sources. Is that part of the code in this repo? If yes, could you point me to it? Thank you!

@ag14774
The published code can be run on the test scenes provided that have already been pre-processed - homography transformation and color matching using NRDC.
To align the video frames, we take one pair of corresponding low and high resolution frame. Compute the transform and apply it to all the other frames. It is straightforward and I can add it to the repository at a later date if needed.

@avinashpaliwal
Thanks! If you are not too busy, it would be great if you could add it

@ag14774 The published code can be run on the test scenes provided that have already been pre-processed - homography transformation and color matching using NRDC.
To align the video frames, we take one pair of corresponding low and high resolution frame. Compute the transform and apply it to all the other frames. It is straightforward and I can add it to the repository at a later date if needed.
I failed when clicking on the above website, and it said "You don't have permission to access this resource."  Could you please provide the website (estimating the homography transformation) again? Thank you!

@ag14774 Do you find the link of NRDC code?  I failed when clicking on the above website, and it said "You don't have permission to access this resource."

Hey back when I asked the question the resource was there but it seems it's not available now

Hey back when I asked the question the resource was there but it seems it's not available now

Hey back when I asked the question the resource was there but it seems it's not available now

Could you please provide the resources  you downloaded?  This would make a great help to my work.  Thank you!

Hey back when I asked the question the resource was there but it seems it's not available now

@ag14774 Could you please provide the resources you downloaded? This would make a great help to my work. Thank you!

It was not very useful for me so I did not save it anywhere. Sorry

Hey @women1995. It looks like all the pages from the author was removed from the domain. I can share the file with you.

Hey @women1995. It looks like all the pages from the author were removed from the domain. I can share the file with you.
@avinashpaliwal Thank you very much for  sharing the source files with me. My email address is<EMAIL_ADDRESS>


Set minimumCacheTTL to 1 year in next image config

Description
Set minimumCacheTTL to 1 year in next image config
Checklist

[x] Base branch of the PR is dev

Not a massive issue but this could create an issue with dNFTs and reveal as the url of the image will not change but its content will


Impossible to brew Alumentum?

I think a found a Problem, because if i am trying to make Alumentum, my coal, which i must use as a catalyst, just adds more essentia.

This is currently being fixed


Subscritions store cleanup

Hi Andreas
thankyou for your PR, but before creating a PR usually is better to discuss the issue the PR is solving in GoogleGroups or creating a question issue. Said that, could you better describe you PR please?
For example you said that LinkedQueue is worst than ArrayList, have you got done any measurement on this improvement inside Moquette, because that queue was originally an ArrayList and was decided to move to Queue because is FIFO and not random access list.

I will splitt this PR and add some measurement data. The LinkedBlockingQueue is not the best option for a singel Thread enviroment.


How to pin app to taskbar?

#114 says there is pinnable icons on taskbar but I can't find how to show/add to them.

Add programs to the Quick Launch

Click "Programs" from the Menu Bar.
Right-Click the desired program
Click "Add to Quick Launch"

Please confirm if the steps work for you.

My bad, I expected for it to work like explorer in that you right click the actual window icon and 'pin it'.
Also it does not recycle the icon?

Sounds like you may want to consider this Issue closed and then open a new issue using the Feature Request template

yeah


add Marmara University marun.edu.tr domain

Marmara University domain included in marmara.txt, however marmara.edu.tr used only for academics and administrative personnels. There's another domain as marun.edu.tr which is used by students.
Here FAQ you can see related information.

@onurcangolge I am sorry, the domain marun.edu.tr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).

@philipto Sorry to hear about an abuse. Will go with GitHub Student Developer Program, thanks.


Not able to scrape endpoints in kubernetes using prometheus and blackbox

What did you do?
Deployed prometheus in kubernetes and it scraping nodes and showing status on dashboard.
What did you expect to see?
Scraping services and endpoints of k8s
What did you see instead? Under which circumstances?
kubernetes-service-endpoints and kubernetes-services are down. I dont understand if its the problem of k8s configuration in my cluster or blackbox configuration
Environment
Prometheus container v1.3.0

System information:
Linux 3.13.0-92-generic x86_64

Prometheus version:
prometheus, version 1.1.3
build user:       root@3e392b8b8b44
build date:       20160916-11:36:30
go version:       go1.6.3

Prometheus configuration file:

global:
  scrape_interval: 30s
  scrape_timeout: 30s
scrape_configs:
- job_name: 'prometheus'
  static_configs:
    - targets: ['localhost:9090']
- job_name: 'kubernetes-cluster'
  scheme: https
  tls_config:
    ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  kubernetes_sd_configs:
  - api_servers:
    - 'https://kubernetes.default.svc'
    in_cluster: true
    role: apiserver
- job_name: 'kubernetes-nodes'
  scheme: https
  tls_config:
    ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
    insecure_skip_verify: true
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  kubernetes_sd_configs:
  - api_servers:
    - 'https://kubernetes.default.svc'
    in_cluster: true
    role: node
  relabel_configs:
  - action: labelmap
    regex: __meta_kubernetes_node_label_(.+)
- job_name: 'kubernetes-service-endpoints'
  scheme: http
  tls_config:
    ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  kubernetes_sd_configs:
  - api_servers:
    - 'https://kubernetes.default.svc'
    in_cluster: true
    role: endpoint
  relabel_configs:
  - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scrape]
    action: keep
    regex: true
  - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scheme]
    action: replace
    target_label: __scheme__
    regex: (https?)
  - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_path]
    action: replace
    target_label: __metrics_path__
    regex: (.+)
  - source_labels: [__address__, __meta_kubernetes_service_annotation_prometheus_io_port]
    action: replace
    target_label: __address__
    regex: (.+)(?::\d+);(\d+)
    replacement: $1:$2
  - action: labelmap
    regex: __meta_kubernetes_service_label_(.+)
  - source_labels: [__meta_kubernetes_service_namespace]
    action: replace
    target_label: kubernetes_namespace
  - source_labels: [__meta_kubernetes_service_name]
    action: replace
    target_label: kubernetes_name
- job_name: 'kubernetes-services'
  metrics_path: /probe
  params:
    module: [http_2xx]
  tls_config:
    #ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
    insecure_skip_verify: true
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  kubernetes_sd_configs:
  - api_servers:
    - 'https://kubernetes.default.svc'
    in_cluster: true
    role: service
  relabel_configs:
  - source_labels: [__meta_kubernetes_role, __meta_kubernetes_service_annotation_prometheus_io_probe]
    action: keep
    regex: service;true
  - source_labels: [__address__]
    target_label: __param_target
  - target_label: __address__
    replacement: blackbox
  - source_labels: [__param_target]
    target_label: instance
  - action: labelmap
    regex: __meta_kubernetes_service_label_(.+)
  - source_labels: [__meta_kubernetes_role]
    target_label: kubernetes_role
  - source_labels: [__meta_kubernetes_service_namespace]
    target_label: kubernetes_namespace
  - source_labels: [__meta_kubernetes_service_name]
    target_label: kubernetes_name
- job_name: 'kubernetes-pods'
  scheme: https
  kubernetes_sd_configs:
  - api_servers:
    - 'https://kubernetes.default.svc'
    in_cluster: true
    role: pod
  relabel_configs:
  - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
    action: keep
    regex: true
  - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]
    action: replace
    target_label: __metrics_path__
    regex: (.+)
  - source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]
    action: replace
    regex: (.+):(?:\d+);(\d+)
    replacement: ${1}:${2}
    target_label: __address__
  - action: labelmap
    regex: __meta_kubernetes_pod_label_(.+)
  - source_labels: [__meta_kubernetes_pod_namespace]
    action: replace
    target_label: kubernetes_namespace
  - source_labels: [__meta_kubernetes_pod_name]
    action: replace
    target_label: kubernetes_pod_name

Note that the kubernetes SD config had a breaking change in the v1.3.0 release. It seems like your config is the old format. Have a look at the sample config for guidance.

when i try sample config , it throws
time="2016-11-09T06:13:19Z" level=info msg="Starting prometheus (version=1.1.3, branch=master, revision=ac374aa6748e1382dbeb72a00abf47d982ee8fff)" source="main.go:73"
time="2016-11-09T06:13:19Z" level=info msg="Build context (go=go1.6.3, user=root@3e392b8b8b44, date=20160916-11:36:30)" source="main.go:74"
time="2016-11-09T06:13:19Z" level=info msg="Loading configuration file /etc/prometheus/prometheus.yml" source="main.go:221"
time="2016-11-09T06:13:19Z" level=error msg="Error loading config: couldn't load configuration (-config.file=/etc/prometheus/prometheus.yml): Kubernetes SD configuration requires at least one Kubernetes API server" source="main.go:126"
then i add api_servers configs and target is created for nodes but not for apiserver
prometheus conf file:
scrape_configs:
- job_name: 'kubernetes-apiservers'
  scheme: https
  tls_config:
    ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
    insecure_skip_verify: true
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  kubernetes_sd_configs:
  - api_servers:
    - 'https://kubernetes.default.svc'
    in_cluster: true
    role: apiserver
  relabel_configs:
  - source_labels: [__meta_kubernetes_namespace, __meta_kubernetes_service_name, __meta_kubernetes_endpoint_port_name]
    action: keep
    regex: default;kubernetes;https

- job_name: 'kubernetes-nodes'
  scheme: https
  tls_config:
    ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
    insecure_skip_verify: true
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  kubernetes_sd_configs:
  - api_servers:
    - 'https://kubernetes.default.svc'
    in_cluster: true
    role: node
  relabel_configs:
  - action: labelmap
    regex: __meta_kubernetes_node_label_(.+)

Are you sure you are using the v1.3.0 container? The log output says differently
version=1.1.3, branch=master, revision=ac374aa6748e1382dbeb72a00abf47d982ee8fff

My mistake, changed it to 1.3.0 in deployment file.
But still endpoint are not getting scrape
this is the error - "server returned HTTP status 404 Not Found" for endpoint -http://<IP_ADDRESS>:80/metrics
When testing this url in k8s
curl -v http://<IP_ADDRESS>:80//xyz/metric is working from k8s(response status - 200)
but not http://<IP_ADDRESS>:80/metrics(response status - 404)

If http://<IP_ADDRESS>:80//xyz/metric works and http://<IP_ADDRESS>:80/metric doesn't, then that sounds like you want your metrics path to be different. You'll probably want to look into relabelling those targets' metric endpoints. If your metrics path is consistently different you can just set the value you need into the __metrics__ meta label using relabelling. If your metrics path is variable you'll want to relabel based on two annotations of your Endpoints object from kubernetes. All annotations of the Endpoints object are converted into Prometheus meta labels. A common practice is to use one annotation to declare that this target should be kept and one that defines the metrics path. Note that you may need to duplicate that section of the config if you want to mix a default and custom metrics paths.

I want flexibility of creating different metrics for services.
So I add  prometheus.io/path: "/xyz/metrics" in service file and
relable config in prometheus.yml file
   - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_path]
    action: keep
    target_label: __metrics_path__

But the endpoint does not change(http://<IP_ADDRESS>:80/metrics)
Do u have any example to refer to?
I tried something like this also
https://movio.co/blog/prometheus-service-discovery-kubernetes/

hey that worked by replacing action to "replace"

Yes, the "keep" action only makes Prometheus keep that particular target, whereas "replace" by default takes the content of the source_labels and puts it in target_label.
Does that solve your questions?

kubernetes-apiservers and kubernetes-pods jobs are not getting displayed on prometheus dashboard
I kept all the configuration as is from sample yaml file and added prometheus.io/scrape,etc. annotations in service as well as in deployment file.
Is it intended to add annotation in deployment file also?

Make sure that the annotations are set in the PodTemplate in the Deployment as those are the annotations that will show up in the Pod created by the ReplicaSet which in turn is created by the Deployment. Could you besides checking that provide your config in a gist or equivalent? (if you can show me the deployment manifest that would be even better)

it doesn't look like you have the label map action on the api-server nor the pod job.
btw; I probably wouldn't have the pods show on the targets page. (I did it a few versions back; and it was a never ending page)

@brancz
This is my deployment file
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: apm-monitoring
  annotations:
    prometheus.io/scrape: "true"
    prometheus.io/probe: "true"
    prometheus.io/port: "80"
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: xyz
    spec:
      containers:
      - name: xyz
        securityContext:
          privileged: true
        image: xyz:latest
        imagePullPolicy: Always
        ports:
        - containerPort: 80
          name: http
        - containerPort: 443
          name: https

Looks like you're setting the prometheus.io/port to port 80; however, you have the pod scraping job set to probe HTTPS.
Try commenting out this line on the pod scraping job.
scheme: https

@Krylon360
api server was there in my older version but when i updated to 1.3.0 ,its not showing
and role: apiserver is not working with new version.
There is no scheme: https in scraping job
Im using sample ex. from https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml

I'm seeing the same thing as @Priyanka098 - I've simply loaded the sample config into a ConfigMap and have a Deployment set to pull the latest Prometheus image.

I'll need to load a local instance of 1.3 and do some testing tomorrow. I know I've been getting the "Kubernetes SD configuration requires at least one Kubernetes API server"  error occurring at random times on 1.2.2 as well.
What does your current Prometheus configmap look like after the changes you've made?
Also, what version of k8s? I ask due to breaking changes made when they cut over to kube-dns.
inCluster now uses "name.namespace.type.cluster.local."
Service Example: kubernetes.default.svc.cluster.local.
Pod Example:
xyz.apm-monitoring.pod.cluster.local.
It's a pain.
I'd also check the logs for the kube-dns pods. We found a bug with SkyDNS that was truncating in_cluster dns queries causing internal lookups to drop.
We patched it on our cluster; but found today we need to revert it now that we're on k8s v1.4.4 and it's causing issues. Ugh

Sorry there's been a few different issues in here that have been worked through & I've lost track of what issue you're hitting at the moment. Could you clarify please?
Last I see is the apiserver role not working? That was removed in 1.3.0 in favour of static sd or preferably kubernetes endpoints role. Just checked example config & looks like that endpoint role is missing from apiservers job. See https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml#L10 ff

@jimmidyson I'm currently getting the "Kubernetes SD configuration requires at least one Kubernetes API server" error. My cluster is running k8s v1.4.5, prometheus:latest, and the sample config verbatim.

@jimmidyson
I dont see any error in my deployment but apiserver job is not getting created.

looks like that endpoint role is missing from apiservers job

does this mean something like below in apiserver job?
  kubernetes_sd_configs:
  - role: endpoints

@Priyanka098 Yes try that.
@boj That looks like you're using an old version - that error message doesn't appear in 1.3.1 AFAIK & can't see it in config validation. Please use the tagged version :v1.3.1 to ensure you get a stable version. Looks like your infra hasn't pulled down :latest tag correctly (possibly you have a IfNotPresent pull policy?).

I tried that and then api-server job appeared on dashboard with error
Get http://<IP_ADDRESS>:443/metrics: malformed HTTP response "\x15\x03\x01\x00\x02\x02"
for endpoint - http://<IP_ADDRESS>:443/metrics

hey i resolved that....I was using http instead of https

So it's working for you? I'll send in a PR with the updated example config.

Awesome.
One thing I can see coming out of this, it to build in support to use
Kube.conf w/ kubectl which would have all the necessary information for the
cluster. Just a thought.
Bryce Walter
On Nov 10, 2016 2:37 AM, "Priyanka098"<EMAIL_ADDRESS>wrote:
hey i resolved that....I was using http instead of https
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/issues/2175#issuecomment-259644032,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATiztRf4_TuU7TBWZM5vZZdymypZhcPks5q8uXtgaJpZM4Ksa3k
.

@jimmidyson Ah, thanks for the hint. Turns out I was using quay.io/coreos/prometheus and not quay.io/prometheus/prometheus

I now get the following error:

2016-11-10T09:56:14.805294529Z time="2016-11-10T09:56:14Z" level=error msg="Error loading config: couldn't load configuration (-config.file=/etc/prometheus/prometheus.yml): relabel configuration for replace action requires 'target_label' value" source="main.go:149"

@jimmidyson

So it's working for you?
yes

I have added scheme: http in my job kubernetes-service-endpoints
some of my services are exposing port 80 and others with 443.
If I add prometheus.io/port: "443" in service.yml file in k8s, then the services are showing status down.
How to deal with this?

@Priyanka098 Add another annotation to the service: prometheus.io/scheme: https

All jobs are up except kubernetes-pods
Here is my deployment file
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: xyz
  annotations:
    prometheus.io/scrape: "true"
    prometheus.io/probe: "true"
    prometheus.io/port: "80"
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: xyz
    spec:
      containers:
      - name: xyz
        securityContext:
          privileged: true
        image: xyz:latest
        imagePullPolicy: Always
        ports:
        - containerPort: 80
          name: http
        - containerPort: 443
          name: https

@boj
check your indentation in config file (last line of your file),
I had similar error when i paste sample config in .yml file

@Priyanka098 Those annotations should be in spec.template.metadata.annotations to be applied to the pod, not the deployment itself.

@jimmidyson
thanks, i solved my problem by changing place of annotations.
All jobs are working now :-)

@Priyanka098 You're welcome. Can you close this now please?

hiii,
i had setup prometheus outside kubernetes cluster but having error
<unable to use specified CA cert /etc/kubernetes/pki/ca.crt: open /etc/kubernetes/pki/ca.crt: no such file or directory>


Common sanitization logic for all env var and arguments

Description
Goal of this PR is to introduce a common logic for all env var and argument handling for containers. Basically duplication shall be avoided and arguments/env vars passed by the user always shall take precedence.
How can this be tested?
Deploy a Dynakube with Active Gate and One Agent, provide custom env var and argument settings and check the daemonset/statefulset.
Checklist

[x] Unit tests have been updated/added
[x] PR is labeled accordingly with a single label
[x] I have read and understood the contribution guidelines

Codecov Report

Merging #2230 (cea992c) into main (cc2f549) will increase coverage by 0.04%.
Report is 1 commits behind head on main.
The diff coverage is 88.15%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main    #2230      +/-   ##
==========================================
+ Coverage   64.61%   64.66%   +0.04%
==========================================
  Files         242      245       +3
  Lines       15315    15398      +83
==========================================
+ Hits         9896     9957      +61
- Misses       4697     4719      +22
  Partials      722      722

Files
Coverage Δ

...e/internal/statefulset/builder/modifiers/config.go
100.00% <100.00%> (ø)

...internal/statefulset/builder/modifiers/rawimage.go
100.00% <100.00%> (ø)

...ernal/statefulset/builder/modifiers/serviceport.go
100.00% <100.00%> (ø)

...ube/activegate/internal/statefulset/statefulset.go
94.91% <100.00%> (+0.02%)
:arrow_up:

...ntrollers/dynakube/oneagent/daemonset/arguments.go
100.00% <100.00%> (ø)

...ntrollers/dynakube/oneagent/daemonset/daemonset.go
96.40% <100.00%> (ø)

...ontrollers/dynakube/oneagent/daemonset/env_vars.go
100.00% <100.00%> (ø)

...g/controllers/edgeconnect/deployment/deployment.go
100.00% <100.00%> (ø)

pkg/util/prioritymap/cmdline_parser.go
100.00% <100.00%> (ø)

...nternal/statefulset/builder/modifiers/synthetic.go
63.97% <16.66%> (-0.59%)
:arrow_down:

... and 2 more


fix word-boundary matching in TextProbe

DAN: doesn't match in DAN: OK I'm Dan if match type is word. It should.

look for detectors where this has been switched to str-matching, undo & test

fixed in 14d8bb59e31d2bcf75f7ce4d23d324148a19da5e


Update README to remove prepare task and add Cordova steps

The gulp prepare task for cordova was removed in touchstone-tasks v3.0.0, so it should be removed from the README to avoid confusion.
Instead, you could guide developers to use the cordova cli commands to add a platform and build/run after the gulp dev task is run.
Cordova steps

gulp dev
cordova platform add ios
cordova run ios // automatically runs cordova prepare  and build first

Note: if this plugin version issue is not resolved, they will need to update their config.xml manually for the cordova commands above to install the plugin dependencies, otherwise they could see issues when running the starter project without them.

@hollyschinsky you could probably submit this as a pull request!

@hollyschinsky Thank you for that heads-up!

I rewrote the readme pretty comprehensively, let me know if you think it could use any more tweaks :)


update riscv intrinsics for latest spec

update intrinsics to match latest spec at https://github.com/riscv-non-isa/rvv-intrinsic-doc (in particular, _riscv prefixes for rvv intrinsics)
fix multiple numerical stability and corner case issues
add a script to generate arbitrary gemm kernel shapes
add a generic zvl256b target to demonstrate large gemm kernel unrolls

Can you take dot.c fix into separate PR - that file is duplicated around tree and will need deduplication of sorts. Not obligation to split, but merely better to have reminder to "look at" others.
CI error is with flang dependencies, not related to your code as you duly noticed.

dropped dot.c from this PR as requested :)

Well, copying the dot.c fix into the other incarnations of dot.c would make sense, but I guess it is not critical as the subsequent while loop never executes in the n=0 case anyway. Only kernel/generic/dot.c does some spurious initializations when universal intrinsics are available.

Note kernel/riscv/dot_vector.c has the equivalent fix, and it saves some actual work there.
In general, my thinking is that people begin work on new ports by copy/pasting existing code, so having existing code just always bail early for n=0 will save a bunch of time working out whether that corner case is sane in any new code even when it has no direct benefit to existing code. If people don't reckon it's worth it, though, I'll not bother :)

Would you like to prepare a PR for the dot.c fix as will ? I assume that was what brada4 intended when he suggested to remove it from this PR. (No problem if you do not have the time, but I wanted to ask as the fix was yours)

Wasn't clear if the consensus was to do this or not bother! PR sent, https://github.com/xianyi/OpenBLAS/pull/3928

Thank you @sergei-lewis !!!

OK. It looks like to merge this PR

Hello @sergei-lewis, I noticed that the zvl256b kernels you added say they are autogenerated, wondering if there is an available tool for generating these kernels?
Thanks!

@OMaghiarIMG yes, it's committed alongside everything else: https://github.com/xianyi/OpenBLAS/blob/risc-v/kernel/riscv64/generate_kernel.py

@OMaghiarIMG yes, it's committed alongside everything else: https://github.com/xianyi/OpenBLAS/blob/risc-v/kernel/riscv64/generate_kernel.py

Hi, @sergei-lewis, I got around to looking through the script and it's quite great!
One thing I did notice is the way LMUL is used, it seems to increase the number of accumulation registers, not the number of vector elements. Basically this way the maximum vl used is only going to be the VLMAX for LMUL=1, no matter what LMUL is actually used.
Also there is a line that says 'conjugate gemm not yet supported' - are you still planning to work on this?

It occurs to me that this PR renamed some of the instances of the target name "x280" to "riscv64_zvl256b" where it claimed to add the latter - is everybody OK with that (including @HellerZheng who contributed the initial x280 support) ? (And also there appears to be no attempt at autodetecting the cpu name/model - but from what I've seen so far, lack of CPUID may be a feature of current RISCV ?)

Good spot! That certainly wasn't the intent. Looks like a mismerge. I'll
put together a patch to fix this; apologies for letting it slip through.
On Wed, Dec 13, 2023 at 10:15 AM Martin Kroeker @.***>
wrote:

It occurs to me that this PR renamed some of the instances of the
target name "x280" to "riscv64_zvl256b" where it claimed to add the latter

is everybody OK with that (including @HellerZheng
https://github.com/HellerZheng who contributed the initial x280
support) ? (And also there appears to be no attempt at autodetecting the
cpu name/model - but from what I've seen so far, lack of CPUID may be a
feature of current RISCV ?)

—
Reply to this email directly, view it on GitHub
https://github.com/OpenMathLib/OpenBLAS/pull/3919#issuecomment-1853632321,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3VVR5IVKRIRHPPZAYQSA63YJF54DAVCNFSM6AAAAAAVGYHESGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJTGYZTEMZSGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you - I think your ZVL256B target would need adding to getarch.c (the FORCE_cpuname block) and TargetList.txt unless I overlooked it there.

Hi @sergei-lewis!
I noticed that this PR changes kernel files with _vector postfix, which are used to build C910V target.
C910V is RVV 0.7.1 target and, AFAIK, should be build with Xuantie toolchain (as it done in CI for develop branch). But latest Xuantie toolchain version 2.8.0 doenst support 0.11.0 or 0.12.0 RISC-V Vector intrinsics spec.
Did you build C910V target with these changes? For me now it looks impossible, since GEMM kernels for C910V are written in inline ASM, which obliges compiler to support RVV 0.7.1 version. But I don't know compiler that supports RVV 0.7.1 and 0.11.0 or 0.12.0 RISC-V Vector intrinsics spec.
Thanks!

Hi Andrey,
This PR was tested for the C910V target with version 2.6.1 of the Xuantie
toolchain, as well as for rvv 1.0 targets supported by ToT
gcc/clang/qemu/spike, at the time of submission.
Please ensure that CORE is set to C910V when compiling for C910V. This
selects version 0.7 of the vector spec by
passing -march=rv64imafdcv0p7_zfh_xtheadc to the compiler (the v0p7 part is
what controls this; cf. Makefile.riscv64 in project root).
On Fri, Dec 22, 2023 at 11:35 AM Sokolov Andrey @.***>
wrote:

Hi @sergei-lewis https://github.com/sergei-lewis!
I noticed that this PR changes kernel files with _vector postfix, which
are used to build C910V target.
C910V is RVV 0.7.1 target and, AFAIK, should be build with Xuantie
toolchain (as it done in CI for develop branch). But latest Xuantie
toolchain version 2.8.0
https://www.xrvm.cn/community/download?id=4237187318466809856 doenst
support 0.11.0 or 0.12.0 RISC-V Vector intrinsics spec.
Did you build C910V target with these changes? For me now it looks
impossible, since GEMM kernels for C910V are written in inline ASM, which
obliges compiler to support RVV 0.7.1 version. But I don't know compiler
that supports RVV 0.7.1 and 0.11.0 or 0.12.0 RISC-V Vector intrinsics spec.
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/OpenMathLib/OpenBLAS/pull/3919#issuecomment-1867581967,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3VVR5OZUJR2KXV5I4TKUOLYKVWARAVCNFSM6AAAAAAVGYHESGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRXGU4DCOJWG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Note that gcc trunk also still supports version 0.7 of the vector spec if
selected via the arch string. If we do still need support for the older C
intrinsic names, it's straightforward to add back since the intrinsics are
referenced using the #defines at the top of each file rather than directly.
I'll take a look at doing that.
On Fri, Dec 22, 2023 at 12:42 PM Sergei Lewis @.***> wrote:

Hi Andrey,
This PR was tested for the C910V target with version 2.6.1 of the Xuantie
toolchain, as well as for rvv 1.0 targets supported by ToT
gcc/clang/qemu/spike, at the time of submission.
Please ensure that CORE is set to C910V when compiling for C910V. This
selects version 0.7 of the vector spec by
passing -march=rv64imafdcv0p7_zfh_xtheadc to the compiler (the v0p7 part is
what controls this; cf. Makefile.riscv64 in project root).
On Fri, Dec 22, 2023 at 11:35 AM Sokolov Andrey @.***>
wrote:

Hi @sergei-lewis https://github.com/sergei-lewis!
I noticed that this PR changes kernel files with _vector postfix, which
are used to build C910V target.
C910V is RVV 0.7.1 target and, AFAIK, should be build with Xuantie
toolchain (as it done in CI for develop branch). But latest Xuantie
toolchain version 2.8.0
https://www.xrvm.cn/community/download?id=4237187318466809856 doenst
support 0.11.0 or 0.12.0 RISC-V Vector intrinsics spec.
Did you build C910V target with these changes? For me now it looks
impossible, since GEMM kernels for C910V are written in inline ASM, which
obliges compiler to support RVV 0.7.1 version. But I don't know compiler
that supports RVV 0.7.1 and 0.11.0 or 0.12.0 RISC-V Vector intrinsics spec.
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/OpenMathLib/OpenBLAS/pull/3919#issuecomment-1867581967,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3VVR5OZUJR2KXV5I4TKUOLYKVWARAVCNFSM6AAAAAAVGYHESGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRXGU4DCOJWG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi Andrey, This PR was tested for the C910V target with version 2.6.1 of the Xuantie toolchain, as well as for rvv 1.0 targets supported by ToT gcc/clang/qemu/spike, at the time of submission. Please ensure that CORE is set to C910V when compiling for C910V. This selects version 0.7 of the vector spec by passing -march=rv64imafdcv0p7_zfh_xtheadc to the compiler (the v0p7 part is what controls this; cf. Makefile.riscv64 in project root).

Thanks to quick reply!
Yes, I tried to build with 2.6.1 of Xuantie toolchain. The problem is that it doesn't seem to support intrinsics with the __risсv prefix.
Build command:
make all ARCH=riscv64 TARGET=C910V CC=/home/andrey/Xuantie-900-gcc-linux-5.10.4-glibc-x86_64-V2.6.1/bin/riscv64-unknown-linux-gnu-gcc FC=/home/andrey/Xuantie-900-gcc-linux-5.10.4-glibc-x86_64-V2.6.1/bin/riscv64-unknown-linux-gnu-gfortran HOSTCC=gcc

For risc-v branch with __risсv prefix (one of many errors):
/home/andrey/Xuantie-900-gcc-linux-5.10.4-glibc-x86_64-V2.6.1/bin/riscv64-unknown-linux-gnu-gcc -c -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_WARMUP -DMAX_CPU_NUMBER=8 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.21.dev\" -march=rv64imafdcv0p7_zfh_xtheadc -mabi=lp64d -mtune=c920 -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME=ismin_k -DASMFNAME=ismin_k_ -DNAME=ismin_k_ -DCNAME=ismin_k -DCHAR_NAME=\"ismin_k_\" -DCHAR_CNAME=\"ismin_k\" -DNO_AFFINITY -I.. -UDOUBLE  -UCOMPLEX -UCOMPLEX -UDOUBLE -UUSE_ABS  -DUSE_MIN ../kernel/riscv64/imin_vector.c -o ismin_k.o

...

../kernel/riscv64/imin_vector.c:77:15: warning: implicit declaration of function '__riscv_vmv_x_s_u32m8_u32'; did you mean 'vmv_x_s_u32m8_u32'? [-Wimplicit-function-declaration]
   77 | #define VMV_X __riscv_vmv_x_s_u32m8_u32
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~
../kernel/riscv64/imin_vector.c:116:29: note: in expansion of macro 'VMV_X'
  116 |                 min_index = VMV_X(compressed);
      |                             ^~~~~
../kernel/riscv64/imin_vector.c:60:20: error: incompatible types when assigning to type 'vfloat32m8_t' from type 'int'
   60 | #define VLEV_FLOAT __riscv_vle32_v_f32m8
      |                    ^~~~~~~~~~~~~~~~~~~~~
../kernel/riscv64/imin_vector.c:120:33: note: in expansion of macro 'VLEV_FLOAT'
  120 |                         v_min = VLEV_FLOAT(&x[j], gvl);
      |                                 ^~~~~~~~~~
../kernel/riscv64/imin_vector.c:62:26: error: incompatible types when assigning to type 'vfloat32m1_t' from type 'int'
   62 | #define VFREDMINVS_FLOAT __riscv_vfredmin_vs_f32m8_f32m1
      |                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../kernel/riscv64/imin_vector.c:122:33: note: in expansion of macro 'VFREDMINVS_FLOAT'
  122 |                         v_res = VFREDMINVS_FLOAT(v_min, v_res, gvl);
      |                                 ^~~~~~~~~~~~~~~~

For develop branch without __risсv prefix its ok, build successful.
I haven't looked with intrinsics version trunk gcc\clang supports for RVV 0.7, but I think С910 target is expected to be builded using Xuantie toolchain.
So you can clarify how you tested this PR (with __riscv) with Xuantie toolchain v2.6.1? Am I missing something?

Hi Andrey,
thank you for reporting the issue. I have now reproduced the problem. It
looks like my testing environment had incorrectly been using a mainline gcc
when performing the C910 target tests. I will put together a PR that
selects the old intrinsic names when built with a toolchain that does not
support the current ones.
On Fri, Dec 22, 2023 at 3:03 PM Sokolov Andrey @.***>
wrote:

Hi Andrey, This PR was tested for the C910V target with version 2.6.1 of
the Xuantie toolchain, as well as for rvv 1.0 targets supported by ToT
gcc/clang/qemu/spike, at the time of submission. Please ensure that CORE is
set to C910V when compiling for C910V. This selects version 0.7 of the
vector spec by passing -march=rv64imafdcv0p7_zfh_xtheadc to the compiler
(the v0p7 part is what controls this; cf. Makefile.riscv64 in project root).
Thanks to quick reply!
Yes, I tried to build with 2.6.1 of Xuantie toolchain. The problem is that
it doesn't seem to support intrinsics with the __risсv prefix.
Build command:
make all ARCH=riscv64 TARGET=C910V CC=/home/andrey/Xuantie-900-gcc-linux-5.10.4-glibc-x86_64-V2.6.1/bin/riscv64-unknown-linux-gnu-gcc FC=/home/andrey/Xuantie-900-gcc-linux-5.10.4-glibc-x86_64-V2.6.1/bin/riscv64-unknown-linux-gnu-gfortran HOSTCC=gcc
For risc-v branch with __risсv prefix (one of many errors):
/home/andrey/Xuantie-900-gcc-linux-5.10.4-glibc-x86_64-V2.6.1/bin/riscv64-unknown-linux-gnu-gcc -c -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DNO_WARMUP -DMAX_CPU_NUMBER=8 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION="0.3.21.dev" -march=rv64imafdcv0p7_zfh_xtheadc -mabi=lp64d -mtune=c920 -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME=ismin_k -DASMFNAME=ismin_k_ -DNAME=ismin_k_ -DCNAME=ismin_k -DCHAR_NAME="ismin_k_" -DCHAR_CNAME="ismin_k" -DNO_AFFINITY -I.. -UDOUBLE  -UCOMPLEX -UCOMPLEX -UDOUBLE -UUSE_ABS  -DUSE_MIN ../kernel/riscv64/imin_vector.c -o ismin_k.o
...
../kernel/riscv64/imin_vector.c:77:15: warning: implicit declaration of function '__riscv_vmv_x_s_u32m8_u32'; did you mean 'vmv_x_s_u32m8_u32'? [-Wimplicit-function-declaration]
77 | #define VMV_X __riscv_vmv_x_s_u32m8_u32
|               ^~~~~~~~~~~~~~~~~~~~~~~~~
../kernel/riscv64/imin_vector.c:116:29: note: in expansion of macro 'VMV_X'
116 |                 min_index = VMV_X(compressed);
|                             ^~~~~
../kernel/riscv64/imin_vector.c:60:20: error: incompatible types when assigning to type 'vfloat32m8_t' from type 'int'
60 | #define VLEV_FLOAT __riscv_vle32_v_f32m8
|                    ^~~~~~~~~~~~~~~~~~~~~
../kernel/riscv64/imin_vector.c:120:33: note: in expansion of macro 'VLEV_FLOAT'
120 |                         v_min = VLEV_FLOAT(&x[j], gvl);
|                                 ^~~~~~~~~~
../kernel/riscv64/imin_vector.c:62:26: error: incompatible types when assigning to type 'vfloat32m1_t' from type 'int'
62 | #define VFREDMINVS_FLOAT __riscv_vfredmin_vs_f32m8_f32m1
|                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../kernel/riscv64/imin_vector.c:122:33: note: in expansion of macro 'VFREDMINVS_FLOAT'
122 |                         v_res = VFREDMINVS_FLOAT(v_min, v_res, gvl);
|                                 ^~~~~~~~~~~~~~~~
For develop branch without __risсv prefix its ok, build successful.
I haven't looked with intrinsics version trunk gcc\clang supports for RVV
0.7, but I think С910 target is expected to be builded using Xuantie
toolchain.
So you can clarify how you tested this PR (with __riscv) with Xuantie
toolchain v2.6.1? Am I missing something?
—
Reply to this email directly, view it on GitHub
https://github.com/OpenMathLib/OpenBLAS/pull/3919#issuecomment-1867788640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3VVR5OUZEVZGWB6QEZNJDLYKWOKHAVCNFSM6AAAAAAVGYHESGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRXG44DQNRUGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi all,
I've submitted PR 4439 which fixes both the above issues (building with toolchains that don't support the release candidate vector intrinsics spec; x280 target getting dropped from cpuid_riscv64.c)


Wrong link of GraphQL Nexus in example readme

Fixed via https://github.com/prisma/photonjs/pull/84


high FPKM called with few reads mapping to transcript

Thanks for making Stringtie-- I have been running it on some test data and it calls FPKM in places where there are almost no reads at all.
I ran it like this:
stringtie -b stringtie/tx/tmpsZIpEI/Test1 -p 1 -G /v-data/bcbio-nextgen/tests/data/genomes/mm9/rnaseq/ref-transcripts.gtf -e /v-data/bcbio-nextgen/tests/test_automated_output/align/Test1/1_110907_ERP000591_tophat/Test1.bam

which generates this:
18	chrM	+	6942	7011	ENSMUST00000082404	1	70	ENSMUSG00000064353	mt-Td	8911.531250	2380952.250000
19	chrM	+	7013	7696	ENSMUST00000082405	1	684	ENSMUSG00000064354	mt-Co2	911.998718<PHONE_NUMBER>25
20	chrM	+	7700	7764	ENSMUST00000082406	1	65	ENSMUSG00000064355	mt-Tk	9597.033203	2564102.500000
21	chrM	+	7766	7969	ENSMUST00000082407	1	204	ENSMUSG00000064356	mt-Atp8	3057.877197<PHONE_NUMBER>00
22	chrM	+	7927	8607	ENSMUST00000082408	1	681	ENSMUSG00000064357	mt-Atp6	916.016357<PHONE_NUMBER>75
23	chrM	+	8607	9390	ENSMUST00000082409	1	784	ENSMUSG00000064358	mt-Co3	795.672424<PHONE_NUMBER>75

ENSMUST00000082404 has a very high FPKM but no reads map there.
IGV screenshot:

It doesn't look like it on IGV, but there are a couple of reads that overhang ENSMUST00000082404 by a couple of bases:
vagrant@vagrant-ubuntu-trusty-64:/v-data/bcbio-nextgen/tests$ samtools view test_automated_output/upload/Test1/Test1-ready.bam chrM:6942-7011
ERR032227.10543296	99	chrM	7008	50	76M	=	7233	301	CTTATATGGCCTACCCATTCCAACTTGGTCTACAAGACGCCACATCCCCTATTATAGAAGAGCTAATAAATTTCCA	HHHHHHHHHHHHHHHGHHHHFHHFHFHH?HFGGGEDFHEHEBGCBCFEF@EBECCB>>@;;A>??>B?>??=>?B=	MD:Z:76	RG:Z:1	XG:i:0	NH:i:1	NM:i:0	XM:i:0	XN:i:0	XO:i:0	AS:i:0	YT:Z:UU
ERR032227.10212620	99	chrM	7010	50	76M	=	7263	329	CCTATGGCCTACCCATTCCAACTTGGTCTACAAGACGCCACATCCCCTATTATAGAAGAGCTAATAAATTTCCATG	HHHHDHHHHHHHHHGHHGHDHECHEH;GFEHGCCFCCGCCGA?@CEE?<?B@?A>:>=;>??=>?;>><:?;@;;;	MD:Z:0T0A74	RG:Z:1	XG:i:0	NH:i:1	NM:i:2	XM:i:2	XN:i:0	XO:i:0	AS:i:-10	YT:Z:UU
ERR032227.10782111	161	chrM	7010	50	76M	=	7280	346	GTTATGGCCTACCCATTCCAACTTGGTCTACAAGACGCCACATCCCCTATTATAGAAGAGCTAATAAATTTCCATG	EEEEEEEEEEEEEEEEEEE?EAEEEE>BDEEEBE>=DB=?A>>??=BB<BA@B>A==>8>9A=:A=><;;=<=;<<	MD:Z:0T0A74	RG:Z:1	XG:i:0	NH:i:1	NM:i:2	XM:i:2	XN:i:0	XO:i:0	AS:i:-10	YT:Z:UU
ERR032227.10060210	99	chrM	7011	50	76M	=	7257	322	CTATGGCCTACCCATTCCAACTTGGTCTACAAGACGCCACATCCCCTATTATAGAAGAGCTAATAAATTTCCATGA	HGHHGFHHHHHHHHHHHHHHFGHHH=HHHHGDBGHFHGGFE@AECF=B@AAAC::D@>?C>???@AC><>=??<=<	MD:Z:0A75	RG:Z:1	XG:i:0	NH:i:1	NM:i:1	XM:i:1	XN:i:0	XO:i:0	AS:i:-5	YT:Z:UU
ERR032227.11020015	163	chrM	7011	50	76M	=	7191	256	CGATGGCCTACCCATTCCAACTTGGTCTACAAGACGCCACATCCCCTATTATAGAAGAGCTAATAAATTTCCATGA	EEEEEEEEEEEEEEEEEEEEBEEEE>EE8EEEE@EBEB@EB?ABAA?>>EA@??>=>:@<>?:;?<<@<===<<88	MD:Z:0A0T74	RG:Z:1	XG:i:0	NH:i:1	NM:i:2	XM:i:2	XN:i:0	XO:i:0	AS:i:-10	YT:Z:UU
ERR032227.11305478	99	chrM	7011	50	76M	=	7258	323	CGATGGCCTACCCATTCCAACTTGGTCTACAAGACGCCACATCCCCTATTATAGAAGAGCTAATAAATTTCCATGA	HHHHHHHHHHHHHHHHHHHHHHHHHCHHHHHHHGGGHFEGBCFBEAA?=C@?C@=>@>AE?=BAA<@;@B:?=@?5	MD:Z:0A0T74	RG:Z:1	XG:i:0	NH:i:1	NM:i:2	XM:i:2	XN:i:0	XO:i:0	AS:i:-10	YT:Z:UU

The FPKM is so high because this is a really tiny test dataset of about 50k reads.
Cufflinks and featureCounts both call this as having an expression level of zero, which seems correct to me. Is there something I could tweak to get similar results? I tried setting -g 1 and omitting -e but that didn't make any difference. I tried the brew installed 1.0.3 and also building from master, but had the same behavior.
Here are the Cufflinks FPKM calls for reference:
ENSMUST00000082404	0.0
ENSMUST00000082405	224658.0
ENSMUST00000082406	0.0
ENSMUST00000082407	24456.4
ENSMUST00000082408	234162.0
ENSMUST00000082409	0.0

I can provide all of the test data if that would be helpful. Thanks!

Great bug report - thank you for the clear and detailed explanations. Indeed it seems that those few overlapping reads which are connecting the separate transcripts in the same bundle could also make StringTie report an inaccurate FPKM for that overhanging transcript..
Could you please upload that test data set on our ftp (ftp.ccb.jhu.edu) in the incoming/gpertea subdirectory? Thanks a lot!

Hi @gpertea,
Thanks for the reply, hope you are enjoying your weekend. The data is so tiny I just stuck it up on Dropbox. I included the FASTQ files, the Tophat alignments and the genome and GTF annotation I used, along with the Stringtie t_data.ctab output. The reference is just chrM so it is tiny. If I can include anything else that would help as well that isn't in there, just let me know.
Here is the link: https://dl.dropboxusercontent.com/u/2822886/Test1.tar

Got it - and thanks to your excellent report we identified the problem and it will be fixed in the next release.
Thank you!

Hi @gpertea,
Sweet, you guys rock. I'm down for testing a prerelease version on a more comprehensive dataset if you push your fixes back to github.

@gpertea: Hi, I'm assuming you guys use a private clone of this repository for buxfixes and only push to github for new releases. Could you us give an indication of when this bugfix will appear in an release that we can use? Thanks a bunch!

Somewhat true - I am using the public github branches for working some bugfixes but we also have an internal SVN repo and I am only merging everything in the master branch here when it's ready for release..
Sorry guys for not responding to @roryk's request earlier, the CSHL conference delayed things a bit and I meant to signal a testing branch for this issue when I could confirm it was working properly on his example - but right now there are still a few details to work out for this FPKM miscall issue. I'll let you know when a testing branch is available here - though we may skip directly to a release version, since there were also a couple little bugfixes that I am eager to push out there.

Sweet, thanks for the followup @gpertea. Hope you had fun at CSHL.

The devel branch here on github (which we are now testing for the imminent v1.0.4 release) should be ready for testing - and should have been fixed these (and other) issues.

We just released v1.0.4  - @roryk or others who were waiting for it, please let us know if you encounter any problems with this new version..

Thanks @gpertea, good timing!


switch ureq to reqwest for system proxy support

Lapce's plugin list is hosted on github pages. Some users need proxy to be able to access github sites. ureq doesn't read system proxy settings, which will cause an empty plugin list for some users. Switch it back to reqwest to fix that.

It didn't work on my machine, maybe we can add a manual proxy config?

It might need HTTP_RPOXY or HTTPS_PROXY environment variables.

oh, yes!

Thanks for testing!


Error While attempting to use Cocoapods, not sure what to do.

Error
SyntaxError - /Users/<mycomp>/Desktop/iPhone Dev/<projectFolder>/Podfile:6: syntax error, unexpected tCONSTANT, expecting end-of-input
pod 'SwiftHTTP', :git => "https://github.co...
              ^
/Library/Ruby/Gems/2.0.0/gems/cocoapods-core-0.36.0/lib/cocoapods-core/podfile.rb:254:in `eval'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-core-0.36.0/lib/cocoapods-core/podfile.rb:254:in `block in from_ruby'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-core-0.36.0/lib/cocoapods-core/podfile.rb:51:in `instance_eval'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-core-0.36.0/lib/cocoapods-core/podfile.rb:51:in `initialize'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-core-0.36.0/lib/cocoapods-core/podfile.rb:251:in `new'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-core-0.36.0/lib/cocoapods-core/podfile.rb:251:in `from_ruby'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-core-0.36.0/lib/cocoapods-core/podfile.rb:227:in `from_file'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/config.rb:176:in `podfile'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/command.rb:109:in `verify_podfile_exists!'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/command/project.rb:100:in `run'
/Library/Ruby/Gems/2.0.0/gems/claide-0.8.1/lib/claide/command.rb:312:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/command.rb:46:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/bin/pod:44:in `<top (required)>'
/usr/bin/pod:23:in `load'
/usr/bin/pod:23:in `<main>'

[!] Oh no, an error occurred.
It appears to have originated from your Podfile at line 6.

I just updated the README for the latest Cocoapods update. Make sure you have the use_frameworks! in your podfile.
https://github.com/daltoniam/SwiftHTTP#cocoapods

Got email confirmation this worked.


Add example of using paths relative to cwd

Resolves #256

The readme is generated. Needs to be updated in the corresponding /docs files.

Thanks for pointing that out @sindresorhus. I have made the change in the corresponding /docs file, rebuilt, and rebased.


[Feature Request] Syntax extension for filtering conditions

For instance, when filtering through a source with numbered entries, it would be nice to do something like the following:
Considering a source with only numbers
1
2
3
4
5

Only the sources with numbers greater than four (regex-based approach)
The regex-based approach tests the condition against the first captured group on each item
[0-9]+ >= 4
I don't like this approach because

It would need to bring in regex-parsing to FZF, making it more difficult to maintain and adding more lines to the code base.
Regex isn't as flexible as eval-based approach, which can leverage every process in the shell.

Only the sources with numbers greater than four (line eval-based approach)
The script between the brackets gets evaluated by the shell for each item, and it should echo something if the item is to be kept.
{[ $LINE -gt 4 ] && echo "keep this item" ]}
It would also allow for pretty much anything else, e.g. comparing two dates by converting them to timestamps and filtering dates greater than $TODAY or $TOMORROW.
Note: brackets are only for demonstration purposes and it could instead follow the Bash syntax more closely with `command`.

My main motivation is that I wish to be able to filter, for instance, only Markdown headings which are below three levels.
# Shelf                          - H1
├── ## Banana                    - H2
├── ## Cherry                    - H2
├── ## Oranges                   - H2
├────── ### Fresh Oranges        - H3

'Banana {[ $(regex_to_extract_number $LINE) -gt 2 ] && echo "keep" ]}
Or only tasks before a certain date
04/04/2018 Do laundry
05/04/2018 Run in the park
06/04/2018 Watch movie

{[ $(convert_line_to_number $LINE) -lt $TODAY ] && echo "keep" ]}

Thanks for the suggestion, but this is going to be a niche feature, and in my opinion, it's beyond the scope of the project. fzf was designed to be a simple interactive grep, rather than a building block for sophisticated terminal applications and I want to keep it simple.

@resolritter commented on Apr 4, 2019, 4:58 PM GMT+4:30:

For instance, when filtering through a source with numbered entries, it would be nice to do something like the following:
Considering a source with only numbers
1
2
3
4
5

Only the sources with numbers greater than four (regex-based approach)
The regex-based approach tests the condition against the first captured group on each item
[0-9]+ >= 4
I don't like this approach because

It would need to bring in regex-parsing to FZF, making it more difficult to maintain and adding more lines to the code base.
Regex isn't as flexible as eval-based approach, which can leverage every process in the shell.

Only the sources with numbers greater than four (line eval-based approach)
The script between the brackets gets evaluated by the shell for each item, and it should echo something if the item is to be kept.
{[ $LINE -gt 4 ] && echo "keep this item" ]}
It would also allow for pretty much anything else, e.g. comparing two dates by converting them to timestamps and filtering dates greater than $TODAY or $TOMORROW.
Note: brackets are only for demonstration purposes and it could instead follow the Bash syntax more closely with `command`.

Did you find any alternatives to fzf that were more suited to UI building?

@NightMachinary

Did you find any alternatives to fzf that were more suited to UI building?

I didn't try to find anything else. The use-case I had in mind was something like a poor man's wiki based on Markdown headers; instead of having links and all sorts of structured formatting like those wiki plugins usually have, I'd instead grep a whole "notes" directory through FZF and narrow to what I wanted with the expression syntax which was proposed here.
I ended up doing some custom CLI scripts instead which do those things separately and not using FZF after all.
Not sure which kind of UI you're going for, but there're a couple of libraries for CLI UIs you could try (e.g. tig uses ncurses).

@resolritter commented on Jul 31, 2020, 2:35 AM GMT+4:30:

@NightMachinary

Did you find any alternatives to fzf that were more suited to UI building?

I didn't try to find anything else. The use-case I had in mind was something like a poor man's wiki based on Markdown headers; instead of having links and all sorts of structured formatting like those wiki plugins usually have, I'd instead grep a whole "notes" directory through FZF and narrow to what I wanted with the expression syntax which was proposed here.
I ended up doing some custom CLI scripts instead which do those things separately and not using FZF after all.
Not sure which kind of UI you're going for, but there're a couple of libraries for CLI UIs you could try (e.g. tig uses ncurses).

BTW, take a look at org-mode if you haven't seen it already. It seems the closest thing to a good free-software solution to having a knowledge graph on the desktop. Unfortunately, it's mobile support isn't very good.


proposal: cmd/go: add package search functionality

Hi Go Community,
This is proposal for adding functionality of package search in go toolchain.
How it would work?
$ go search logrus

Package | Get                             | Downloads | Version | Release Date | Bugs
logrus  | hosted.site.com/sirupsen/logrus | 32002     | 3.2.4   | 01 July 2019 | 11

This would be handy and also a step towards better package management support in Go 2.
We already have web search interface for this sort of thing
https://go-search.org/
https://godoc.org/
Why not at the command line ?

I don't think this needs to be a Go2 proposal: it's a language change, and it could be a go mod subcommand (probably not a top level command as you propose). Changing the title accordingly.

@ALTree I disagree.
Search top level command could have multiple subcommands instead.
$ go search -local logrus

To check if it's installed and the path it's located at.
By default if you don't mention -local flag, it would search remotely.
$ go search -history logrus

To check version history and changelog of the package
$ go search -dependencies logrus

To list all imports along with their version used in that package
$ go search -bugs logrus

To list all open issues on the package's repository
And many more possibilities that the community would bring

It's a little unclear to me what the use-case for this is. Is this meant to be a tool for discovery of packages? Or just a quick way to see version numbers and metadata?
Go packages can be hosted anywhere (not just GitHub), so it wouldn't always be possible to query metrics like "bugs" or "downloads". In fact, even for GitHub repositories, I'm not sure getting those metrics is really feasible. Open issues on GitHub are not always bugs, and I don't think the public can see metrics for a repo's clone counts. I also think in general Go should steer away from GitHub-specific integrations.

We already have web search interface for this sort of thing
Why not at the command line ?

"Why not" isn't really the question we should be asking when considering new features. If there's not a compelling reason for a feature, it shouldn't be added.
I'm personally not necessarily against a CLI search tool; this proposal as-is just doesn't seem very compelling to me.

@ccbrown Agreed.
Go should indeed steer away from GitHub-specific integrations and Github hosted packages, as if in a case where the account of a package maintainer gets compromised, and malicious code gets injected into the package, it would affect projects all over the world.
This is just a proposal for starting a debate on integrating search functionality and making some central package management which we can rely on as a community. I know metrics like "bugs" and "downloads" and "changelog" are not possible to track (or with precision) with Github or any other package hosting service like Gitlab. This is a proposal to bring this to problem to light and that we need a better way for package discovery in Go with CLI.

https://index.golang.org/ is something to that effect.

CC @julieqiu @ianthehat @jayconrod

@julieqiu is working on a new site for searching and discovering modules and packages. I'm not sure if they're planning on exposing an API that a command line tool could access. We've talked about having goimports use such an API for ranking, so it seems possible to me.
That said, I'm not convinced this belongs in the go tool, which should remain focused on building and testing. The go tool also has a very rigid release cycle and dependency restrictions. A standalone tool would be more flexible.

Good point, the go tool should remain focused on building and testing. goimports serving the search functionality seems reasonable.
Updating in the proposal

The output shown in the top comment is not in scope for either the go command or goimports; neither would have any idea about "bug count" for example.
The discovery site (or for now godoc.org) is the mechanism for collecting and displaying that kind of information. We should probably focus on that and not command-line tools.

The output shown in the top comment is not in scope for either the go command or goimports;

Then why not new tool, something like goensure (go-ensure), or gop (go-package), or something else.

neither would have any idea about "bug count" for example

Okay, excluding "bug count"

The discovery site (or for now godoc.org) is the mechanism for collecting and displaying that kind of information

Exactly. And it is tedious.

We should probably focus on that and not command-line tools

Why not command-line tool for search?
You probably use or have used all of the following
apt search,
docker search,
vagrant cloud search,
pip search,
gem search,
cpan search
or other similar examples on other systems and for other languages.
@rsc Why not in Golang ?

I'm sure you've used all of the following
apt search,
docker search,
vagrant cloud search,
pip search,
gem search,
cpan search
or other similar examples on other systems and for other languages.

Every single one of those has a central package database, though. Go does not. That being said, I don't think it would be too weird to have an optional feature for whatever module proxy server your system is using to enable search, and have it implemented for the default server.
I also think it makes more sense to integrate this into go list, rather than making it its own thing. Something like go list -search, go list -remote, or go list -proxy.

@DeedleFake
Talking about non-centralized package management, found some tools you online for decentralized package management in Go
The pioneer’s guide to GX — decentralized dependency management on IPFS
https://github.com/whyrusleeping/gx
https://github.com/enzoh/go-revolver

The discovery site / godoc.org is still the place where this information should live. Maybe some day there might be a command-line interface to query it, but we are still standing up the new site. In any event, the search functionality would not be in cmd/go itself.
Go list itself is also already too overloaded. I suggest we decline this. Any objections?

I'll go ahead and close this. Having this in a separate tool, possibly integrated with the discovery site or godoc.org is a good plan.

For updates on the status of the discovery site, see #33654.

https://search.gocenter.io can be used to discover go modules.


Add testing

Preferably image-diff since Sass and Stylus will always fail at matching percentage values since they have different specificity on floats.

There's just no real way to test for this. Even image-diff wouldn't return true or false since SCSS and Stylus produces ever so slightly different widths and such.


Support CPU hotplug for VMs with Virtual Topologies

Description
VMs with a virtual CPU topology (not pinned) should be able to be live-resized (VCPU_MAX) parameter. This requires to properly compute the topology based on the current CPU value as well as adding the hotplugable attribute in the libvirt definition.
It may also require some support from context (udev rules).
Use case
Resize VMs with virtual topolgies (not pinned)
Interface Changes
NONE
Additional Context
Lots of details about the implementation can be found in #5293

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Hello!
I maybe found problem. CPU hotplug work up and down if VM running and up vcpu to vcpu_max and down vcpu to start value vcpu.
Example: VCPU_MAX=5 and start VCPU=2 increase to VCPU=4 and poweroff VM. Poweron VM and VCPU_MAX=5 and start VCPU=4 and hotplug(onlne) decrease VCPU before VCPU=3 not work.
Sorry for bad english.


Extend Panic Sell?

Running the docker image, whenever a buy occurs, it basically has 10 seconds to fill the sell order, if it doesn't, it panic sells.
I get WHY it does that but it would be great to be able to configure it to wait longer or wait-until-sold.

The gekko trading bot uses a methodology where each time it checks and the order isn't filled, it cancels and re-places the order at the top of the order book.  I think this (more aggressive strategy) would be more successful in getting orders placed in highly volatile markets, especially with other (faster and more aggressive) bots outbidding ours.  Lately, only about 50% of the buy attempts have been successul.  Thoughts?


[codegen] Support explicit #[count] arg for VarLenArray

Previously this only worked at the end of a table, with the #[count(..)] attribute.

unblocks #1120

cc @simoncozens This is slightly different than what I'd described; specifically it doesn't require an explicit count, and #[count(..)] will still work. I think this is better since computing the length from an explicit count requires an additional redundant iteration, so it seems silly to require that unnecessarily. Please check that this works your avar2 needs?

I've rebased the avar2 branch on top of this, and t he tests pass. Thank you very much!


multiple schema fix

Checked performance on the user repo - everything is fine
Fix for #199

@comigor the PR is ready


Cache should only notify on change

A potential optimization. It is not guaranteed to be useful :thinking:
The cache currently notifies its subscribers on every cache update (e.g. file modification).
It could make sense to only notify the subscribers when the cache has actually changed.

It appears this is currently not a performance issue and I wouldn’t want to do a premature optimization that isn’t even guaranteed to provide any benefits.