text:
Windows workaround for multiline runs while calling exectuables

Closes #6540

@edgarrmondragon / @WillDaSilva
I put this PR up to see if you all like this idea as a workaround? Wanted to prevent an issue like this from cropping up again on Windows. The fix for getting the correct Python version is seperate and much easier, but detecting an issue like this for the future seemed very important to me (maybe I think it's more important than it really is)


text:
Milvus Integration

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] Refactor (does not change functionality, e.g. code style improvements, linting)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Please delete options that are not relevant.

[ ] Unit Test

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #1617
[ ] Made sure Checks passed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Dev-Khant:x: JacksonxhxYou have signed the CLA already but the status is still pending? Let us recheck it.

我需要这个功能，你能尽快合并吗

need this feature, can someone please help to merge it

Hello @deshraj @Dev-Khant ,
I am working on this I have already created a branch i will raise pr in  1-2 days.

Hey @Jacksonxhx Are you working on this issue? Please let us know.

looking forword to @ketangangal  's contributing.  @Jacksonxhx seems have no time to deal with this, and if there are any problem, I can support it.

@zc277584121 watch out : https://github.com/mem0ai/mem0/pull/1821

Closing this PR has Milvus has been added in #1821.

source: gharchive/pull-request

authors: CLAassistant Dev-Khant Jacksonxhx geeker-smallwhite ketangangal zc277584121

license_type: permissive

license_source: github-api


text:
Fix_#1343: Correctly Store YouTube Video Publish Date with Timezone Support

Description
This PR resolves the issue where the publish date of YouTube videos was being stored as YYYY-MM-DD 00:00:00, without the time component. This caused issues when handling time zones. The fix ensures the publish date is stored with the correct time and in ISO 8601 format.
Fixes # (1343)
file: embedchain/loaders/youtube_video.py

Updated the code to properly handle the publishedAt field from the metadata.
Ensured that the publishedAt timestamp is converted to an ISO 8601 format (e.g., 2024-04-15T14:30:00Z) to correctly store both the date and time, considering UTC timestamps.
Introduced logic to replace the Z suffix with +00:00 for UTC timestamps, ensuring that the time zone is properly handled.
Added error logging to capture any parsing issues with the publishedAt field.
imported datetime

Type of change

[-] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Updated code to convert publishedAt timestamp to ISO 8601 format.
Validated that timestamps are now stored with time and timezone, e.g., 2024-04-15T15:00:00Z.
Manually tested the following cases:
*  Correct conversion for UTC (Z suffix) timestamps.
*  Conversion for time zone-aware timestamps (e.g., +02:00).
*  Ensured any invalid timestamps are logged with a warning.
Checklist:

[-] My code follows the style guidelines of this project
[-] I have performed a self-review of my own code
[-] I have checked my code and corrected any misspellings

Maintainer Checklist

[-] closes #1343
[ ] Made sure Checks passed

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

Hey @hensikavar Thanks for the PR, can you please share an example here where the publication date is properly captured?

authors: CLAassistant Dev-Khant hensikavar


text:
Error capturing video

Hi, I'm trying to record video but app crash.
This is the log:
12-27 17:32:01.052 6327-6327/io.github.memfis19.sample W/System: ClassLoader referenced unknown path: /data/app/io.github.memfis19.sample-1/lib/x86_64
12-27 17:32:01.070 6327-6327/io.github.memfis19.sample I/InstantRun: Instant Run Runtime started. Android package is io.github.memfis19.sample, real application class is null.

                                                                     [ 12-27 17:32:01.072  1541: 1562 D/         ]
                                                                     HostConnection::get() New Host Connection established 0x7bdee161e960, tid 1562
12-27 17:32:01.532 6327-6327/io.github.memfis19.sample W/System: ClassLoader referenced unknown path: /data/app/io.github.memfis19.sample-1/lib/x86_64
12-27 17:32:01.801 6327-6327/io.github.memfis19.sample W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter android.support.graphics.drawable.VectorDrawableCompat.updateTintFilter(android.graphics.PorterDuffColorFilter, android.content.res.ColorStateList, android.graphics.PorterDuff$Mode) would have incorrectly overridden the package-private method in android.graphics.drawable.Drawable
12-27 17:32:02.335 6327-6355/io.github.memfis19.sample I/OpenGLRenderer: Initialized EGL, version 1.4
12-27 17:32:02.335 6327-6355/io.github.memfis19.sample D/OpenGLRenderer: Swap behavior 1
12-27 17:32:02.477 6327-6355/io.github.memfis19.sample E/EGL_emulation: tid 6355: eglSurfaceAttrib(1174): error 0x3009 (EGL_BAD_MATCH)
12-27 17:32:02.477 6327-6355/io.github.memfis19.sample W/OpenGLRenderer: Failed to set EGL_SWAP_BEHAVIOR on surface 0x7bdee667f100, error=EGL_BAD_MATCH
12-27 17:32:04.360 6327-6327/io.github.memfis19.sample I/CameraManagerGlobal: Connecting to camera service
12-27 17:32:04.517 6327-6355/io.github.memfis19.sample E/EGL_emulation: tid 6355: eglSurfaceAttrib(1174): error 0x3009 (EGL_BAD_MATCH)
12-27 17:32:04.517 6327-6355/io.github.memfis19.sample W/OpenGLRenderer: Failed to set EGL_SWAP_BEHAVIOR on surface 0x7bdee667f280, error=EGL_BAD_MATCH
12-27 17:32:04.632 6327-6355/io.github.memfis19.sample E/EGL_emulation: tid 6355: eglSurfaceAttrib(1174): error 0x3009 (EGL_BAD_MATCH)
12-27 17:32:04.632 6327-6355/io.github.memfis19.sample W/OpenGLRenderer: Failed to set EGL_SWAP_BEHAVIOR on surface 0x7bdee667f280, error=EGL_BAD_MATCH
12-27 17:32:04.736 6327-6355/io.github.memfis19.sample D/OpenGLRenderer: endAllActiveAnimators on 0x7bdee66bf400 (RippleDrawable) with handle 0x7bdee5b2e0a0
12-27 17:32:08.550 6327-6453/io.github.memfis19.sample E/WVMExtractor: Failed to open libwvm.so: dlopen failed: library "libwvm.so" not found
12-27 17:32:08.555 6327-6454/io.github.memfis19.sample I/OMXClient: MuxOMX ctor
12-27 17:32:08.579 6327-6387/io.github.memfis19.sample I/MediaRecorderJNI: prepare: surface=0x7bdefd853e00
12-27 17:32:08.598 6327-6387/io.github.memfis19.sample E/MediaRecorder: start failed: -2147483648
12-27 17:32:08.599 6327-6387/io.github.memfis19.sample E/AndroidRuntime: FATAL EXCEPTION: BaseCameraManager
                                                                         Process: io.github.memfis19.sample, PID: 6327
                                                                         java.lang.RuntimeException: start failed.
                                                                             at android.media.MediaRecorder.start(Native Method)
                                                                             at io.github.memfis19.annca.internal.manager.impl.Camera1Manager$4.run(Camera1Manager.java:143)
                                                                             at android.os.Handler.handleCallback(Handler.java:751)
                                                                             at android.os.Handler.dispatchMessage(Handler.java:95)
                                                                             at android.os.Looper.loop(Looper.java:154)
                                                                             at android.os.HandlerThread.run(HandlerThread.java:61)
12-27 17:32:08.614 6327-6464/io.github.memfis19.sample I/OMXClient: MuxOMX ctor
12-27 17:32:08.650 6327-6355/io.github.memfis19.sample E/EGL_emulation: tid 6355: eglSurfaceAttrib(1174): error 0x3009 (EGL_BAD_MATCH)
12-27 17:32:08.650 6327-6355/io.github.memfis19.sample W/OpenGLRenderer: Failed to set EGL_SWAP_BEHAVIOR on surface 0x7bdee667f2c0, error=EGL_BAD_MATCH
12-27 17:32:08.716 6327-6327/io.github.memfis19.sample W/AudioTrack: AUDIO_OUTPUT_FLAG_FAST denied by server; frameCount 16808

Hi, I will take a look asap. Can you please send your device, android version details.

I'm using an emulator
`
Name: 5.4_FWVGA_API_25_Android_7.1.1
CPU/ABI: Google APIs Intel Atom (x86_64)
Path: C:\Users\Ares.android\avd\5.4_FWVGA_API_25_Android_7.1.1.avd
Target: google_apis [Google APIs] (API level 25)
Skin: 480x854
SD Card: C:\Users\Ares.android\avd\5.4_FWVGA_API_25_Android_7.1.1.avd\sdcard.img
hw.dPad: no
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: 5.4in FWVGA
vm.heapSize: 16
skin.dynamic: yes
hw.device.manufacturer: Generic
hw.gps: yes
hw.initialOrientation: Portrait
skin.path.backup: _no_skin
image.androidVersion.api: 25
hw.audioInput: yes
image.sysdir.1: system-images\android-25\google_apis\x86_64\
tag.id: google_apis
showDeviceFrame: no
hw.camera.back: emulated
hw.mainKeys: yes
AvdId: 5.4_FWVGA_API_25_Android_7.1.1
hw.camera.front: emulated
hw.lcd.density: 160
avd.ini.displayname: 5.4  FWVGA API 25 Android 7.1.1
hw.gpu.mode: auto
hw.device.hash2: MD5:fbd5143f5b48ba972391c87c302c0c69
hw.ramSize: 512
hw.trackBall: no
hw.battery: yes
hw.cpu.ncore: 2
hw.sdCard: yes
tag.display: Google APIs
runtime.network.latency: none
hw.keyboard: yes
hw.sensors.proximity: yes
disk.dataPartition.size: 800M
hw.sensors.orientation: yes
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes`

Hi, sorry for long response. But the answer is quite easy: "Note: Currently, MediaRecorder does not work on the emulator.": https://developer.android.com/reference/android/media/MediaRecorder.html

source: gharchive/issue

license: mit

license_source: bigquery


text:
更改 OPENAI_API_KEY 之後，仍然出現 failed with status code 429

我更改後, 重新佈署, 仍然顯示錯誤.
不知如何清除cache.

我也是，也重建了。。。

請問是使用第一次註冊的 API Key 嗎？

我改了三個 API Key  似乎沒差.
目前測試,是不斷地連線超時. 可能遇到高峰期了

如果是連線超時，有可能已經連上，但是系統超載，再試試。

license: MIT


text:
🛑 Kérwá is down

In 5c6d2ea, Kérwá (https://kerwa.ucr.ac.cr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kérwá is back up in d4b6888 after 8 minutes.

repo: memoemg/howyoudoing


text:
🛑 Portal de Revistas is down

In b31002c, Portal de Revistas (https://revistas.ucr.ac.cr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal de Revistas is back up in bc915f1.


text:
🛑 Kimuk is down

In 646477d, Kimuk (https://kimuk.conare.ac.cr/Search/Results?lookfor=&type=AllFields) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Kimuk is back up in 5d4582f after 754 days, 14 hours, 30 minutes.


text:
Setup data tests

Port the data tests in https://code.videolan.org/videolan/dav1d-test-data to Rust, ideally as cargo test tests. It's okay to add the test data files from that repo into this one, they're only about 50 MB of data total.

As of ea83e8f we can now use meson test to run data tests against the Rust dav1d executable. I've hacked the meson.build files to point any tests that were using the dav1d executable to use the Rust version instead. Looks like that's the tests in the testdata-8, testdata-10, and testdata-12 suites, with the tests in testdata-8 currently failing because of #3. Instructions for running tests are now in the README.
I've also imported the test data repo directly into this repo. This simplifies the test setup for users, since they don't need to manually clone the repo.


text:
Fixed TypeError when expiring

Only a very small change, but expiring the disk store doesn't properly work atm.
TypeError: unsupported operand type(s) for +: 'float' and 'datetime.timedelta'

Nevermind, it seems timeout isn't always a timedelta object. Need to further investigate. I'll move this to an issue.

repo: meraki-analytics/cassiopeia-datastores


text:
Initialising the APN client in an init method

Hello,
After looking at the pushNotificationWorker method, the apnClient gets initialized after we check whether its null or not, so why its not initilized just like the Android client inside an init method?

At the start, gaurun keeps TCP connections for GCM and APNs.
gaurun communicates to GCM with HTTPS and its HTTPS client belongs to net/http. net/http's client caches TCP connections transparently. So it is not requierd to handle TCP connections directly for communicating to GCM.
On the other hand, APNs is based TLS and original binary protocol. It is required to handle TCP connections directly for communicating to APNs. (e.g. A connection to APNs is sometimes closed.)
So pushNotificationWorker() requires the implementation for handling the connection to APNs directly.

I see, honestly I had  a feeling that the connection may expires because I saw expire property somewhere in their documentation, so I thought that might be the case, however you are basically keep continuing till you initilize a valid connection for the apn so what would happen if non of the goroutines have established a valid connection to the APN, and you have an android push notification you will never send the android notification because the code snippet which is responsible for that is unreachable.
as a solution you may do something like this:
switch notification.Platform {
	case PlatFormIos:
                    		if apnsClient == nil {
		apnsClient, err = apns.NewClient(
			ep,
			ConfGaurun.Ios.PemCertPath,
			ConfGaurun.Ios.PemKeyPath,
			time.Duration(ConfGaurun.Ios.Timeout)*time.Second,
		)
		if err != nil {
			msg := fmt.Sprintf("failed to connect to APNS: %s", err.Error())
			LogError.Error(msg)
			apnsClient = nil
			continue
		}
		apnsClient.TimeoutWaitError = time.Duration(ConfGaurun.Ios.TimeoutError) * time.Millisecond
	}

	if ConfGaurun.Ios.KeepAliveMax > 0 && loop > ConfGaurun.Ios.KeepAliveMax {
		apnsClient.Conn.Close()
		apnsClient.ConnTls.Close()
		apnsClient = nil
		loop = 0
		continue
	}
	loop++
		success = pushNotificationIos(notification, apnsClient)
		if !success {
			apnsClient = nil
		}
		retryMax = ConfGaurun.Ios.RetryMax

Instead of trying to connect in the beginning of the function.

@moadqassem Thank you for the suggestion. As you say there seems to be the point to be improved. I'll take it in the near future. Thank you again!

you are welcome, I already fix it my self locally and I would be glad to make a pull request for the enhancement if you are ok with it, if not its totally ok and thanks for the cool package anyway ;)

Patches welcome :)

fixed in https://github.com/mercari/gaurun/commit/6499a3a9b9c0ab793a3728092e577e7c468da6ed

authors: cubicdaiya moadqassem

repo: mercari/gaurun


text:
Feature 345 summary in reports

This PR will close #345

@Jeeppler
Some quick questions.

What does Secret Scan do? I haven't met this type of scan in SecHub before.
It seems to me it's neccessary to significantly change the structure of model in HTMLScanResultReportModelBuilder. Do you approve this?

@zigfridus

Secret Scan is looking through code or repositories and tries to find hard coded secrets and credentials. This is a common problem. For example, with AWS credentials https://github.com/ramimac/aws-customer-security-incidents.

It seems to me it's necessary to significantly change the structure of model in HTMLScanResultReportModelBuilder. Do you approve this? - Yes, go ahead and do the necessary changes.

@Jeeppler
I would like to ask, may I reorganize the summary table in the way like on this image.
image
This will greatly simplify for me the summary table creation?

@zigfridus please add the image of the table from the Google drive into this issue here. I would like to have the documentation of this issue in one place.

@Jeeppler
Proposition of transposition of the Summary table:

@Jeeppler
Please have a look at my last commit with a draft summary table.
Thanks

@Jeeppler
Could you please explain for me this your sentence:
"Please include a screenshot with your next pull-request review request (only as comment in the pull-request conversation)."
I don't clearly understand it.

@zigfridus It would be nice to have a screenshot of the report with the summary once you request a review. The simply reason is, that you are working on the HTML report and it is always a good idea to show case the visual changes.
Simply include the screenshot as part of this conversation.

Hello @Jeeppler
According to the test data in the example3_coverity.sarif.json the finding with the same CWE ID (for example CWE-352) could have HIGH and MEDIUM severity at the same time. Is it possible or is it a mistake in the test data?

@zigfridus yes, they could both have different severity levels even for the same CWE, depending on how the tool calculates the severity level (e, g. based on a Control Flow Graph). It is certainly an edge case.
In addition, some tools produce findings with a CWE-0. The problem, a CWE-0 does not exist.
In the real world there are a lot of oddities, quirks and bugs. Tests might help to check for those. However, I do expect that over time we will uncover some situations/combinations you/we did not account for. That is fine.

@Jeeppler Thank you for the explanation.

@zigfridus Thanks, I know it takes time. Overall, it look very nice. Good job. 🥇
The details block should exist in your report as well. I am surprised, that it does not exist in your code.
Regarding the tables. I think if they look this they would be easier to read:
CodeScan

High

CWE         | Name                                                                   | Count
-----------------------------------------------------------------------
CWE-543  | Bad choice of lock object                                      | 1
CWE-352  | Cross-site request forgery                                    | 1
CWE-79    | Cross-site scripting                                              | 131
CWE-22    | Filesystem path, filename, or URI manipulation    | 5
…

In addition, it would be nice to use the <details> - HTML tag for the table with CWE numbers.
Closed:
> SecretScan
> CodeScan
…

CodeScan open:
> SecretScan
v CodeScan

High

CWE         | Name                                                                   | Count
-----------------------------------------------------------------------
CWE-543  | Bad choice of lock object                                      | 1
CWE-352  | Cross-site request forgery                                    | 1
CWE-79    | Cross-site scripting                                              | 131
CWE-22    | Filesystem path, filename, or URI manipulation    | 5
…

@Jeeppler
Please have a look at my improvements:
examples.zip

Added the block of details in description.
Designed summary blocks as tables.
Add possibility to collapse summary blocks.

@zigfridus good job. Looks really nice.
One test case I am interested in is: what happens if you have for example results from a secret scan and a code scan in the same report?
Otherwise it looks good. If you push the code, I can review it again.

@Jeeppler

One test case I am interested in is: what happens if you have for example results from a secret scan and a code scan in the same report?
Unfortunately I don't know how to get a report from multiple scans. I use tests from ThymeLeafHTMLReportingTest and they generate single scan reports only. Could you please give an advice how to do it?

Otherwise it looks good. If you push the code, I can review it again.
I need some time to clean my code and create tests, then I'll push it.

@zigfridus Clean up the code and push it. Once, that is done. I will scan with codeScan and secretScan using your changes.

@Jeeppler
Please have a look and test my last commit.

@zigfridus nice work, I was able to confirm that SecretScan + CodeScan in one report works well.
What I did:

build SecHub server ./gradlew build
copied sechub-server-0.0.0.jar into the sechub-solution/docker/copy folder
set the build type to copy BUILD_TYPE=copy in the .env
started the sechub server using the ./01-start-single-docker-compose.sh
used the setup-pds scripts of gitleaks and gosec to setup both
started the gitleaks and gosec pds solutions using the 05-scripts… in both folders
created a new test project using the SecHub Developer UI (Java swing based)
assigned the test-gosec and test-gitleaks execution profiles to the test project
scanned with both pds-gosec and pds-gitleaks

Sounds complicated at first, but takes approx. 10-15 minutes to setup everything locally.

@Jeeppler
I ran the test as you asked before. It was completed with an error like the others.

@zigfridus : Could you please merge develop branch again - sorry for the inconvenience
I did some enhancements especially

#2593 and
#2577
#2561

Maybe this fixes your build problems here as well and we could finally merge your work.

@company-jcup
Thank you for enhancements. Unfortunately my branch failed again on merge : https://github.com/zigfridus/sechub/actions/runs/6669466960/job/18127302329
There are the same failed tests as before:
[com.mercedesbenz.sechub.systemtest.SystemTestFrameworkIntTest::even_integration_test_setup_can_be_tested_codescan_source_only_and_gen_example()] [com.mercedesbenz.sechub.systemtest.SystemTestFrameworkIntTest::even_integration_test_setup_can_be_tested__codescan_with_binary_and_sources()]
I have already fixed them, but there are more failed tests appeared. Right now I'm in the middle of modifying them to make them work with the new report from this branch. Unfortunately right now I have a lot of work to do and it could take some time.

@zigfridus you can do two things. Either a) push what you have and a team member will look over it and try to fix it or b) you fix it yourself.

@Jeeppler
At the weekend I merged last changes from the develop branch into the mine. After that system tests, that I've already fixed, failed again. Thus I have to fix them from the beginning. I would like to fix them by myself, but If I very slows merging this feature I certainly can push my fixes for a team member.

@zigfridus Go ahead and try to fix it yourself. In case you want some help just ask @company-jcup or me.
I will convert this to a draft again to indicate that this is still a pull-request which requires work.

@Jeeppler
Finally the code with my modifications were built without errors. Please have a look.

@zigfridus awesome. I will have a look.

@de-jcup please review as well.

@Jeeppler
I amended my code according to your recommendations. After that it was built successfully. Please have a look.

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

@zigfridus : I am happy to see that you have done some new commits/pushes. When your changes are complete, please re-request a review from me by GitHub UI. Thank you.

@zigfridus : Sorry (again) for the late response
With

#2759

we introduced a "community" branch.
Please do me a favor and change your PR target from develop to community.
After this, I will merge the PR to community branch, do some additions and after this
merge it finally to develop
We try to install this as the default mechanism - to speed up merges, reduce frustration at contributor side, see build failures before merging to develop (main) branch etc. (see #2759 for details).
So... this is like a test balloon, but I hope this works well in future for other contributions/contributors as well.
Thank you for your patience, your contribution and your perseverance regarding this long ongoing PR...

@de-jcup
I changed this branch to community.

@zigfridus awesome, thank you.

authors: CLA-Mercedes-Benz Jeeppler company-jcup de-jcup zigfridus

repo: mercedes-benz/sechub


text:
Could not create HG core class because of upstream ofi+verbs issues

Describe the bug
Hello, using the very last commit https://github.com/mercury-hpc/mercury/commit/d34cec49a18621c64b2be2bfce69d5b3e988ceab, I have the following reproducer registering a device:
#include <iostream>
#include <cstring>
#include <mercury.h>

int main(int argc, char** argv) {
    struct hg_init_info hii;
    memset(&hii, 0, sizeof(hii));
    hii.na_init_info.request_mem_device = true;

    HG_Init_opt("ofi+verbs://10.20.0.34", false, &hii);

    std::cout << "done" << std::endl;
    return 0;
}

Although this program executes successfully (no error in the console), it seems that the initialization is failling when inspecting the output with FI_LOG_LEVEL=warn HG_LOG_LEVEL=debug HG_LOG_SUBSYS=cls,ctx,~hg flags enabled:
# [3850.219780] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/mercury_core.c:5459
 # HG_Core_init_opt(): Initializing with ofi+verbs://10.20.0.34, listen=0
# [3850.219817] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na.c:293
 # NA_Initialize_opt(): Class: ofi, Protocol: verbs, Hostname: 10.20.0.34
# [3850.933494] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:5869
 # na_ofi_check_protocol(): Matched provider: verbs;ofi_rxm
# [3850.933518] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:5908
 # na_ofi_initialize(): Entering na_ofi_initialize() protocol_name "verbs", host_name "10.20.0.34"
# [3850.933528] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:5944
 # na_ofi_initialize(): Requesting use of memory devices
# [3850.933536] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:3027
 # na_ofi_parse_hostname_info(): Found hostname: 10.20.0.34, port 0, domain (null)
# [3850.933542] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:3048
 # na_ofi_parse_hostname_info(): Resolving name 10.20.0.34 with port 0
libfabric:48364:1674824988:ofi_rxm:core:core:fi_getinfo_():1141<warn> fi_getinfo: provider verbs returned -61 (No data available)
libfabric:48364:1674824988:ofi_rxm:core:core:fi_getinfo_():1141<warn> fi_getinfo: provider verbs returned -61 (No data available)
libfabric:48364:1674824988::core:core:fi_getinfo_():1141<warn> fi_getinfo: provider ofi_rxm returned -61 (No data available)
# [3850.933777] mercury->cls: [error] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:2882
 # na_ofi_getinfo(): fi_getinfo(verbs;ofi_rxm) failed, rc: -61 (No data available)
### ----------------------
### (na) debug log summary
### ----------------------
# Number of log entries: 6
# [3850.219816] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na.c:293
## NA_Initialize_opt()
# [3850.933493] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:5869
## na_ofi_check_protocol()
# [3850.933518] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:5908
## na_ofi_initialize()
# [3850.933528] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:5944
## na_ofi_initialize()
# [3850.933536] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:3027
## na_ofi_parse_hostname_info()
# [3850.933542] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:3048
## na_ofi_parse_hostname_info()
# [3850.933816] mercury->cls: [error] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:2961
# na_ofi_verify_info(): na_ofi_getinfo() failed
# [3850.933821] mercury->cls: [error] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na_ofi.c:5989
# na_ofi_initialize(): Could not verify info for verbs;ofi_rxm
# [3850.933828] mercury->cls: [error] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/na/na.c:335
 # NA_Initialize_opt(): Could not initialize plugin
 # [3850.933833] mercury->cls: [error] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/mercury_core.c:1190
 # hg_core_init(): Could not initialize NA class (info_string=ofi+verbs://10.20.0.34, listen=0)
### ----------------------
### (hg_core) debug log summary
### ----------------------
# Number of log entries: 1
# [3850.219778] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/mercury_core.c:5459
## HG_Core_init_opt()
# [3850.933854] mercury->cls: [error] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/mercury_core.c:5463
 # HG_Core_init_opt(): Cannot initialize core class
 # [3850.933859] mercury->cls: [error] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-2qquztbt3zdogokrnbwsp25nr4wrkxde/spack-src/src/mercury.c:1069
 # HG_Init_opt(): Could not create HG core class
done

In https://github.com/mercury-hpc/mercury/issues/640#issuecomment-1405711590, @soumagne suggests that I may have a configuration problem, or no support for GPU (cuda initialization may be failing).
Platform (please complete the following information):

System description: debian 11 broadwell
Compiler version: gcc 10.2.1
Plugin and protocol used: ofi+verbs
Dependency version: libfabric@1.16.1+cuda and rdma-core@41.0

Additional context
The ibstat and fi_info stuff looks fine:
fi_info -t FI_EP_RDM: fi_info -t FI_EP_RDM.txt
ibstat: ibstat.txt
I activated IPoIB myself on the ibp5s0 interface using ip address add 10.20.0.34/24 dev ibp5s0 and ip link set ibp5s0 up. Output of ip link show:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether d8:c4:97:b8:32:83 brd ff:ff:ff:ff:ff:ff
3: enp1s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether d8:c4:97:b8:32:84 brd ff:ff:ff:ff:ff:ff
4: ibp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2044 qdisc mq state UP mode DEFAULT group default qlen 256
    link/infiniband 00:00:11:07:fe:80:00:00:00:00:00:00:98:03:9b:03:00:92:66:da brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
5: ibp12s0: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
    link/infiniband 00:00:11:07:fe:80:00:00:00:00:00:00:98:03:9b:03:00:9a:3a:c6 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
6: ibp132s0: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
    link/infiniband 00:00:11:07:fe:80:00:00:00:00:00:00:98:03:9b:03:00:93:1f:6e brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
7: ibp139s0: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
    link/infiniband 00:00:11:07:fe:80:00:00:00:00:00:00:98:03:9b:03:00:9a:3a:f2 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff

Any help would be greatly appreciated :) Thanks!

Thanks for sending that log. I'm surprised that OFI is not producing more output... you might have to compile libfabric with the +debug variant and re-run with FI_LOG_LEVEL=debug instead of warn.
Also could you send the output for fi_info again but with: fi_info -v -t FI_EP_RDM -p verbs\;ofi_rxm -a FI_SOCKADDR_IN

Output with +debug:
debug.txt
This reminds me of https://github.com/mochi-hpc/mochi-margo/issues/235#issuecomment-1382038087. This looks suspicious:
libfabric:39826:1675069816:ofi_rxm:verbs:fabric:vrb_get_matching_info():1520<info> checking domain: #1 mlx5_0
libfabric:39826:1675069816:ofi_rxm:verbs:core:vrb_check_hints():240<info> Unsupported capabilities
libfabric:39826:1675069816:ofi_rxm:verbs:core:vrb_check_hints():241<info> Supported: FI_MSG, FI_RMA, FI_ATOMIC, FI_READ, FI_WRITE, FI_RECV, FI_SEND, FI_REMOTE_READ, FI_REMOTE_WRITE, FI_LOCAL_COMM, FI_REMOTE_COMM
libfabric:39826:1675069816:ofi_rxm:verbs:core:vrb_check_hints():241<info> Requested: FI_MSG, FI_RMA, FI_READ, FI_RECV, FI_SEND, FI_REMOTE_READ, FI_REMOTE_WRITE, FI_HMEM

Also, earlier in the file, I noticed some messages like:
libfabric:39826:1675069816::core:core:ofi_reg_dl_prov():611<debug> dlopen(libhook_hmem-fi.so): libhook_hmem-fi.so: cannot open shared object file: No such file or directory

Output of fi_info -v -t FI_EP_RDM -p verbs\;ofi_rxm -a FI_SOCKADDR_IN:
fi_info.txt
Could it be that my hardware does not support CUDA+verbs?

The log messages are confusing.  This segment indicates that CUDA HMEM support is initializing:
libfabric:39826:1675069816::core:core:fi_param_define_():229<debug> registered var hmem_cuda_use_gdrcopy
libfabric:39826:1675069816::core:core:fi_param_define_():229<debug> registered var hmem_cuda_enable_xfer
libfabric:39826:1675069816::core:core:fi_param_get_():278<info> variable hmem_cuda_use_gdrcopy=<not set>
libfabric:39826:1675069816::core:core:fi_param_get_():278<info> variable hmem_cuda_enable_xfer=<not set>
libfabric:39826:1675069816::core:core:ofi_hmem_init():247<info> Hmem iface FI_HMEM_ROCR not supported
libfabric:39826:1675069816::core:core:ofi_hmem_init():247<info> Hmem iface FI_HMEM_ZE not supported
libfabric:39826:1675069816::core:core:ofi_hmem_init():247<info> Hmem iface FI_HMEM_NEURON not supported
libfabric:39826:1675069816::core:core:ofi_hmem_init():247<info> Hmem iface FI_HMEM_SYNAPSEAI not supported

This is the loop where it is checking through each supported hmem type: https://github.com/ofiwg/libfabric/blob/main/src/hmem.c#L238 and this is the static array it is looping through: https://github.com/ofiwg/libfabric/blob/main/src/hmem.c#L45 .
It's definitely initializing the CUDA HMEM interface at that level or else we would see different messages (either the "not supported" like we see for  ROCR etc or else a "Failed to initialize" if it was supported but the corresponding init function failed at runtime.
I don't understand what the connection is between the FI_HMEM caps at the API level and the initialization of an hmem interface at this level though; the mismatch doesn't really make any sense.

Could it be that my hardware does not support CUDA+verbs?

That's a fair guess, maybe verbs initializes and cuda initializes but the two aren't compatible?  Can you remind us the Mellanox and NVidia models?

For now, I'm running all of this on a single server Nvidia DGX-1:

ib0, InfiniBand, configured rate: 100 Gbps, model: Mellanox Technologies MT27800 Family [ConnectX-5], driver: mlx5_core
8 x Nvidia Tesla V100-SXM2-32GB (32 GiB), Compute capability: 7.0

For now, I'm running all of this on a single server Nvidia DGX-1:
* ib0, InfiniBand, configured rate: 100 Gbps, model: Mellanox Technologies MT27800 Family [ConnectX-5], driver: mlx5_core

* 8 x Nvidia Tesla V100-SXM2-32GB (32 GiB), Compute capability: 7.0

FWIW, I'm not an expert, but I don't see any reason why that combination shouldn't work.

Following the advice given by @j-xiong in https://github.com/ofiwg/libfabric/issues/8444#issuecomment-1424521592, I installed MOFED and could initialize the HG core class successfully.
There is an assertion failing at the end, but I'll consider that issue as fixed. I still have to test the actual RDMA+CUDA call to check if that works too (I will create another issue if not). Thanks everyone :)
# [4927.185326] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/mercury_core.c:5459
 # HG_Core_init_opt(): Initializing with ofi+verbs://10.20.0.34, listen=0
# [4927.185395] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na.c:293
 # NA_Initialize_opt(): Class: ofi, Protocol: verbs, Hostname: 10.20.0.34
# [4927.774455] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:5869
 # na_ofi_check_protocol(): Matched provider: verbs;ofi_rxm
# [4927.774485] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:5908
 # na_ofi_initialize(): Entering na_ofi_initialize() protocol_name "verbs", host_name "10.20.0.34"
# [4927.774496] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:5944
 # na_ofi_initialize(): Requesting use of memory devices
# [4927.774505] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:3027
 # na_ofi_parse_hostname_info(): Found hostname: 10.20.0.34, port 0, domain (null)
# [4927.774528] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:3048
 # na_ofi_parse_hostname_info(): Resolving name 10.20.0.34 with port 0
# [4927.775160] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:2971
 # na_ofi_verify_info(): na_ofi_getinfo() returned 2 candidate(s)
# [4927.775170] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:2978
 # na_ofi_verify_info(): FI info for selected provider
fi_info:
    caps: [ FI_MSG, FI_RMA, FI_TAGGED, FI_READ, FI_WRITE, FI_RECV, FI_SEND, FI_REMOTE_READ, FI_REMOTE_WRITE, FI_MULTI_RECV, FI_SOURCE, FI_DIRECTED_RECV, FI_HMEM ]
    mode: [  ]
    addr_format: FI_SOCKADDR_IN
    src_addrlen: 16
    dest_addrlen: 0
    src_addr: fi_sockaddr_in://10.20.0.34:0
    dest_addr: (null)
    handle: (nil)
    fi_tx_attr:
        caps: [ FI_MSG, FI_RMA, FI_TAGGED, FI_READ, FI_WRITE, FI_SEND, FI_HMEM ]
        mode: [  ]
        op_flags: [ FI_INJECT_COMPLETE ]
        msg_order: [ FI_ORDER_RAR, FI_ORDER_RAW, FI_ORDER_RAS, FI_ORDER_WAW, FI_ORDER_WAS, FI_ORDER_SAW, FI_ORDER_SAS, FI_ORDER_RMA_RAR, FI_ORDER_RMA_RAW, FI_ORDER_RMA_WAW, FI_ORDER_ATOMIC_RAR, FI_ORDER_ATOMIC_RAW, FI_ORDER_ATOMIC_WAW ]
        comp_order: [ FI_ORDER_NONE ]
        inject_size: 192
        size: 2048
        iov_limit: 4
        rma_iov_limit: 1
        tclass: 0x0
    fi_rx_attr:
        caps: [ FI_MSG, FI_RMA, FI_TAGGED, FI_RECV, FI_REMOTE_READ, FI_REMOTE_WRITE, FI_MULTI_RECV, FI_SOURCE, FI_DIRECTED_RECV, FI_HMEM ]
        mode: [  ]
        op_flags: [  ]
        msg_order: [ FI_ORDER_RAR, FI_ORDER_RAW, FI_ORDER_RAS, FI_ORDER_WAW, FI_ORDER_WAS, FI_ORDER_SAW, FI_ORDER_SAS, FI_ORDER_RMA_RAR, FI_ORDER_RMA_RAW, FI_ORDER_RMA_WAW, FI_ORDER_ATOMIC_RAR, FI_ORDER_ATOMIC_RAW, FI_ORDER_ATOMIC_WAW ]
        comp_order: [ FI_ORDER_NONE ]
        total_buffered_recv: 0
        size: 2048
        iov_limit: 4
    fi_ep_attr:
        type: FI_EP_RDM
        protocol: FI_PROTO_RXM
        protocol_version: 1
        max_msg_size: 1073741824
        msg_prefix_size: 0
        max_order_raw_size: 1073741824
        max_order_war_size: 0
        max_order_waw_size: 1073741824
        mem_tag_format: 0xaaaaaaaaaaaaaaaa
        tx_ctx_cnt: 1
        rx_ctx_cnt: 1
        auth_key_size: 0
    fi_domain_attr:
        domain: 0x0
        name: mlx5_0
        threading: FI_THREAD_SAFE
        control_progress: FI_PROGRESS_MANUAL
        data_progress: FI_PROGRESS_MANUAL
        resource_mgmt: FI_RM_ENABLED
        av_type: FI_AV_MAP
        mr_mode: [ FI_MR_LOCAL, FI_MR_VIRT_ADDR, FI_MR_ALLOCATED, FI_MR_PROV_KEY, FI_MR_HMEM ]
        mr_key_size: 4
        cq_data_size: 4
        cq_cnt: 65536
        ep_cnt: 32768
        tx_ctx_cnt: 1
        rx_ctx_cnt: 1
        max_ep_tx_ctx: 1
        max_ep_rx_ctx: 1
        max_ep_stx_ctx: 0
        max_ep_srx_ctx: 0
        cntr_cnt: 0
        mr_iov_limit: 1
        caps: [  ]
        mode: [  ]
        auth_key_size: 0
        max_err_data: 0
        mr_cnt: 0
        tclass: 0x0
    fi_fabric_attr:
        name: IB-0xfe80000000000000
        prov_name: verbs;ofi_rxm
        prov_version: 116.10
        api_version: 1.9
    nic:
        fi_device_attr:
            name: mlx5_0
            device_id: 0x1017
            device_version: 0
            vendor_id: 0x02c9
            driver: (null)
            firmware: 16.26.4012
        fi_bus_attr:
            bus_type: FI_BUS_UNKNOWN
        fi_link_attr:
            address: (null)
            mtu: 4096
            speed: 100000000000
            state: FI_LINK_UP
            network_type: InfiniBand
---
# [4927.775435] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:3418
 # na_ofi_fabric_open(): fi_fabric opened
fi_fabric_attr:
    name: IB-0xfe80000000000000
    prov_name: verbs;ofi_rxm
    prov_version: 116.10
    api_version: 1.9
---
# [4927.776056] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:3637
 # na_ofi_domain_open(): MR max key is 4294967295
# [4927.776065] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:3644
 # na_ofi_domain_open(): Msg max tag is 4294967295
# [4927.776069] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/$a/na_ofi.c:3646
 # na_ofi_domain_open(): fi_domain opened
fi_domain_attr:
    domain: 0x0
    name: mlx5_0
    threading: FI_THREAD_SAFE
    control_progress: FI_PROGRESS_MANUAL
    data_progress: FI_PROGRESS_MANUAL
    resource_mgmt: FI_RM_ENABLED
    av_type: FI_AV_MAP
    mr_mode: [ FI_MR_LOCAL, FI_MR_VIRT_ADDR, FI_MR_ALLOCATED, FI_MR_PROV_KEY, FI_MR_HMEM ]
    mr_key_size: 4
    cq_data_size: 4
    cq_cnt: 65536
    ep_cnt: 32768
    tx_ctx_cnt: 1
    rx_ctx_cnt: 1
    max_ep_tx_ctx: 1
    max_ep_rx_ctx: 1
    max_ep_stx_ctx: 0
    max_ep_srx_ctx: 0
    cntr_cnt: 0
    mr_iov_limit: 1
    caps: [  ]
    mode: [  ]
    auth_key_size: 0
    max_err_data: 0
    mr_cnt: 0
    tclass: 0x0
---
# [4927.776155] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:3891
 # na_ofi_basic_ep_open(): Opening standard endpoint
# [4927.776700] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:3924
 # na_ofi_basic_ep_open(): Default FI_OPT_MIN_MULTI_RECV is 16384, setting it to 4096
# [4927.793106] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/na/na_ofi.c:3940
 # na_ofi_basic_ep_open(): fi_endpoint opened
 fi_ep_attr:
    type: FI_EP_RDM
    protocol: FI_PROTO_RXM
    protocol_version: 1
    max_msg_size: 1073741824
    msg_prefix_size: 0
    max_order_raw_size: 1073741824
    max_order_war_size: 0
    max_order_waw_size: 1073741824
    mem_tag_format: 0xaaaaaaaaaaaaaaaa
    tx_ctx_cnt: 1
    rx_ctx_cnt: 1
    auth_key_size: 0
---
# [4927.796183] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/mercury_core.c:1201
 # hg_core_init(): Multi-recv set to 1
# [4927.796193] mercury->cls: [debug] /tmp/spack-stage/root/spack-stage-mercury-d34cec49a18621c64b2be2bfce69d5b3e988ceab-nlfunmqzsoajgibhzsty2awa52bjc4cb/spack-src/src/mercury_core.c:5465
 # HG_Core_init_opt(): Initialized core class (0x563a8a52cbb0)
done
client: prov/util/src/util_mem_monitor.c:160: ofi_monitor_cleanup: Assertion `dlist_empty(&monitor->list)' failed.
Aborted

authors: carns soumagne thomas-bouvier

repo: mercury-hpc/mercury


text:
Wow orchestra

Hi,
Is there a way to select "wow orchestra" output ?
Thank you.

You mean as a sound output? Maybe it would be possible you would just need to find out the output id. From the readme:
Depending on the TV and connected devices to the TV there might also be other values. In that case just switch sound outputs on the TV and check the homebridge log.
You would need to try that.

You mean as a sound output? Maybe it would be possible you would just need to find out the output id. From the readme: Depending on the TV and connected devices to the TV there might also be other values. In that case just switch sound outputs on the TV and check the homebridge log. You would need to try that.

You’re right. Sorry to have bothered you before having read « read me ».

authors: CoStiC merdok

repo: merdok/homebridge-webos-tv


text:
⚠ SkyfallMC Minecraft Server has degraded performance

In 3d67305, SkyfallMC Minecraft Server (play.skyfallmc.ga) experienced degraded performance:

HTTP code: 200
Response time: 1096 ms

Resolved: SkyfallMC Minecraft Server performance has improved in d5a673c.


text:
Add an imported_at (or similar) column to most/all data tables

Often we want to know when a row was imported into a table to understand how up-to-date the data is, without looking at the sync log.

Do we have knowledge  of which tables   this change is not needed ?
also now that this  is  only a migration  , we could tackle this together with https://github.com/mergestat/fuse/issues/136
@patrickdevivo  @amenowanna  what do you guys  think ?

Sure - so this additional column is only needed in tables on the public schema right now, which are our "data" tables - what users will query and what the syncs populate. The idea here is to provide some context to the data in the database so the user can see how "fresh" it is (when were rows added). It may even make sense to prefix the column names here with something like mergestat_imported_at or just _imported_at.
@amenowanna what do you think?

also, for the #136, I'd rather handle in two separate PRs since the functionality is quite different

@patrick and I had a quick side bar on this and landed on _mergestat_synced_at since we are calling the things that do the work syncs. Adding the _mergestat prefix makes it very clear it is internal data. Moving forward we should use this prefix. I think we will eventually need to add more columns like _mergestat_synced_at and _mergestat_synced_at but we will add those when they are needed.

authors: amenowanna patrickdevivo ramiroJCB

repo: mergestat/fuse


text:
All items displayed on page load

Description
Link: Meshery catalog screen
When this page loads, I see all catalog items on the first page. When I press "Next," I see 9 catalog items.
Expected Behavior
There should be 9 catalog items on all pages.
Screenshots

Enviroment:

OS: Linux
Browser: Firefox
Version: Latest
Device: Desktop

Contributor Guides and Handbook
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Thank you @amitamrutiya, please go ahead.

@Muhammed-Moinuddin, any luck?

@Muhammed-Moinuddin, still working on it?

@Muhammed-Moinuddin, still working on it?

Yes completed. Will raise PR.

Hi @amitamrutiya  and @sudhanshutech ,
Is this issue still active? If so, could you please assign it to me? I’d love to contribute.

@bhushan354, Go ahead!

@Ashparshp I have fixed the issue

@Ashparshp can you review this ?

authors: Ashparshp Muhammed-Moinuddin amitamrutiya bhushan354


text:
Add-design-authors-on-Individual-Design-pages-on-the-catalog

Description
This PR fixes #1121

Adds the name of the publisher on the individual design page:

Fixes error in the yaml syntax in the file : collections/_catalog/deployment/2df29b2b-7e5e-4d8b-a5b3-3dea569f4d25.md

Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

Nice!

👏

authors: leecalcote vishalvivekm


text:
[Docs] Installation Guide : Add an Installation guide for Civo Cloud

Current Behavior
Does have an Installation guide for Civo Cloud
Desired Behavior
Should Have an Installation guide for Civo Cloud
Implementation

Acceptance Tests

Mockups

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I can add this guide but i need some limelight on this from the maintainers
about what they want or  I should exactly do how other installation like eks and aks does
.
.
thanks

repo: meshery/meshery


text:
added undefined check in columns

Description
This PR fixes https://github.com/service-mesh-performance/service-mesh-performance/issues/248
Notes for Reviewers
The error when logged was

identified Error
The error was due to the presence of undefined columns in the data
Correction
Applying filter for undefined values
let chartDataFiltered = chartData.filter(( element ) => element !== undefined);
Corrected Output

Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #4284 (4f99da4) into master (dac33b5) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 4f99da4 differs from pull request most recent head 3342b4a. Consider uploading reports for the commit 3342b4a to get more accurate results

@@           Coverage Diff           @@
##           master    #4284   +/-   ##
=======================================
  Coverage   20.15%   20.15%
=======================================
  Files          59       59
  Lines        5037     5037
=======================================
  Hits         1015     1015
  Misses       3727     3727
  Partials      295      295

Flag
Coverage Δ

unittests
20.15% <ø> (ø)

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

Continue to review full report at Codecov.

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

Whoo-hoo, @manav1403 🎈

authors: codecov-commenter leecalcote manav1403


text:
Newer Field Widgets UX .

Signed-off-by: harkiratsm multaniharry714@gmail.com
Description
This PR fixes #
Notes for Reviewers

[x] Separated out the TextWidget .
[x] Used the CustomBaseInput for most of the fields .
[x] UX - representation for error msg. Place the ! mark next to question mark.

#ref
Signed commits

[ ] Yes, I signed my commits.

Would you attach a screenshot.


text:
annual

Signed-off-by: Lee Calcote lee.calcote@layer5.io
Notes for Reviewers
This PR fixes #
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit 1984cb21fc17b07baa1f4e6170fea999f04b783e at: https://6508ca5d1e6913302a2dd94b--meshery-docs-preview.netlify.app

🚀 Preview for commit c0d4d227871a2d608750d29118f6d188fa338643 at: https://6508cd2790e9f35ee3c2008f--meshery-docs-preview.netlify.app

🚀 Preview for commit 6ef44114f429cad14c0b2c29aeebf55940b1e12c at: https://6508cf4a90e9f36030c2012f--meshery-docs-preview.netlify.app

🚀 Preview for commit 97d7af1cf6b3143654d8d8a15943e96607555970 at: https://6508d0f3df5e4665659673f5--meshery-docs-preview.netlify.app

🚀 Preview for commit 54b58783c2b19b9a59f65eb173f819956b45de81 at: https://6508e6051e6913429c2dd9ba--meshery-docs-preview.netlify.app


text:
Added error code utility workflow

Signed-off-by: metonymic-smokey ahuja.aditi@gmail.com
Description
This PR fixes #79
Signed commits

[x] Yes, I signed my commits.

@Blakelist7 could you please review this?
Thanks!

repo: meshery/meshsync


text:
Setting broker attributes

I've set rack attributes for the Mesos slave in /etc/mesos-slave/attributes, but they're not being added to the brokers according to kafka-mesos.sh broker list. Further, when attempting to follow the syntax in the broker help for using attribute filtering, i get a 400 - invalid broker-expr
I guess I'm just missing something elementary, here. Specifically, how do you add attributes to a broker? Some full command line examples of using attribute filtering would also be useful, since I can't seem to get it right based on the help/readme.

Did you find a way out for this?

repo: mesos/kafka


text:
Cassandra ignores set-up parameters

Hi guys,
Cassandra DCOS package ignores all configuration parameters and doesn't allow to change settings.
Any options regarding data directory, RAM, CPU and so on are ignored, there is no way to customize DCOS Cassandra package installation atm.

@AndriiOmelianenko
I submitted a PR to the universe to make resources configurable:  https://github.com/mesosphere/universe/pull/231
would love a PR for anything else you are looking for..

This repository is deprecated. Please use the latest supported framework here: https://github.com/mesosphere/dcos-cassandra-service, and provide feedback for us here: https://dcosjira.atlassian.net/browse/CASSANDRA.

authors: AndriiOmelianenko kensipe triclambert

repo: mesosphere/cassandra-mesos


text:
Create Marathon 1.4.0-RC6

[x] 69d4b26fd6c7c480c76e22f4e73027939bccbcdc (already picked) Fixes #4991 by specifically testing, if a property in the docker section is set, but is not supported.
[x] 3716181f59e11fba61bd16fc864c98a9181cbf7f (already picked) Use api-console in github pages
[x] 91cdc7e91afa774ca7eb5a04232cf8591b02f570 (already picked) add a docker container label with mesos task id (#4492)
[x] 205589b84c3038e9e07145626d9dee9f5abc50ff (already picked) Documentation: pods typo fix
[x] 96fd203e38aeeaa7743ef7541e13749a6c4c5731 (already picked) Documentation: first draft of task handling (#4642)
[x] 970ac26b4c8f4eac8336a648822ad1f51fed65d6 (already picked) Documentation: typo fix on task handling config page
[x] 370691989011e8b96210a73e866e34bd591889b2 (already picked) Documentation: markdown typo
[x] c4df9c662fb3300ba8bf8336e38935c051a53b60 (already picked) Documentation: markdown typo fixes
[x] 1d4d52ff0fadfeb5f101d1c70bd1c59ac7063758 (already picked) Documentation: Typo (#4939) directoy to directory
[x] bd1c69a23251c5361ae879a1a9544067a52f5664 (already picked) Make sure the HistoryActor only stores task failures once.
[x] fe00f46ac7978ba2489c8e6a234073694574a0b5 (already picked) Documentation: peg doc updates to release branch (#4937)
[x] 13add63d355ff4fe13798f31627c5c4c1890a293 (already picked) Documentation: apps + groups can be in a group (#4964)
[x] cf3d544806b3dfd40caca6605667cef3a9db4f9d (already picked) Remove authorization from /ping endpoint
[x] 589ad6a40f38d010a9117b2450b6bae1b34805c5 (already picked) Documentation: Fixed DC/OS link to dcos.io. (#4979)
[x] 6467d124aa636ce4b78dec4a6a831ae4eec59a00 (already picked) Log all Mesos capabilities on level Info instead of Debug.
[x] 5b712987663a6815e0d53e68a1d0068523864d95 (already picked) Documentation: Call out the artifact store as deprecated.
[x] ef13b44b0a3e5cc7a85e137f2efe585ecf5437ae (already picked) Make TaskResources async (#4807)
[x] 14177b0119c91c8687296893a9755ad71ee79b3a (already picked) Fixes #4932 | GET on empty apps list result 500 exception (#4940)
[x] c52b8dd077bda541543f92a0962c2aada442b5d6 (already picked) Use async instance tracker methods in TaskKiller (#4800)

-[ x ] 69d4b26fd6c7c480c76e22f4e73027939bccbcdc (already picked) Fixes #4991 by specifically testing, if a property in the docker section is set, but is not supported.

Please add D443 once it landed.

Cherry picked D443 with https://github.com/mesosphere/marathon/commit/79fe121505749fe709456211e9b80222d7b677c3

Cherry picked #4983 with https://github.com/mesosphere/marathon/commit/195295e8873e67ca59ce5ec3dea0af21f8de08df

Please add https://phabricator.mesosphere.com/D451

Please add https://phabricator.mesosphere.com/D447

Please add https://phabricator.mesosphere.com/D455

Release tirggered with https://github.com/mesosphere/marathon/commit/8ceec6c95faf667c4580c21ca65be0e257069f51

Release broke. Here is a quick fix https://phabricator.mesosphere.com/D456.

PR for Open DC/OS https://github.com/dcos/dcos/pull/1176
PR for DC/OS EE https://github.com/mesosphere/dcos-enterprise/pull/538

authors: aquamatthias jeschkies zen-dog

repo: mesosphere/marathon


text:
Add a config flag for selecting the Mesos state implementation

Valid option values are zookeeper, in-memory, leveldb, and soon replicated-log.

Moved to 0.9.0 as this is a bigger change.

We moved away from mesos state store.

authors: ConnorDoyle aquamatthias drexin


text:
TrueFi Mainnet QA

Review Info

Description
Info

Subgraph Reviewed
https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/name/corerouter/truefi&tab=protocol

Schema Version
2.0.1

Subgraph Version
1.1.4

Methodology Version
1.0.0

Evidence Spreadsheet
https://docs.google.com/spreadsheets/d/1Ylm7xUGUjYV69mm3OggwHgEXYZ8hMIlR/edit?usp=sharing&ouid=104027705798814439445&rtpof=true&sd=true

Metric to Review
Pool Overview TVL
TVL numbers have discrepancy of a few million compared to official website data, due mainly to the tracking of the pools. Please refer to worksheet "Pool_Overview" for details. In particular:

there's no TrueFi LP pool in the official website
the price of WOO pool price might be wrong
the TAM pool III is not tracked correctly in the subgraph

Revenue
Due to the nature of the transactions recorded (not only an daily evenly distributed way), it's hard to check the accuracy of daily data. We have manually calculated the monthly data  instead, of the three largest pools for verification.  We note:

The supply-side and total revenue might have decimal errors, as the interest revenue in less than a year's time should not be more than the loan initiated.
The protocol-side data might be accurate, as the protocol cumulative protocol-side revenue matches that of the official website.

Please refer to  worksheet "Supply-side" and "Pool_value" for more details.
Rewards
There are rewards token given in TrueFi now. This is not tracked by the subgraph.
Input Token
The input token supply and the exchange rate of the USDT pool do not look correct.

Comments: TVL discrepancy is within reasonable range. Likely variability due to when data was taken.
cumulative supply and protocol revenue add up to $34M. Front end says the same.
Woo pool is slightly off. likely cause of where and when price feed is coming from. It is not end of the world.
Otherwise TrueFi looks good should be frozen. @this-username-is-taken

repo: messari/subgraphs


text:
BulletBoxShape takes Width Length Height as input

I found in many places we are using length width height as input. This might cause wrong collision detection??!

When creating a box shape, the bullet API requires half of the length/width/height. This won't make any thing wrong. If you doubt this, turn on debug_physics_world and debug_static_world to see the results.

authors: QuanyiLi pengzhenghao

repo: metadriverse/metadrive


text:
Thank you for sharing your very interesting work

Sorry this is not an Issue, but thank you very much for sharing your really interesting work!
I also look forward to you sharing the policy dissection method and training code as well.

I did not realize that you had already shared them with us. Thank you very much!

repo: metadriverse/policydissect


text:
Use Waymo Protos Directly

What changes do you make in this PR?
In this PR, we remove the dependency on waymo-open-dataset-tf-2-11-0 by including the Protobuf definitions inside the scenarionet repository itself.

Please describe why you create this PR

This allows users to avoid having to install waymo-open-dataset-tf-2-11-0, which has many dependencies like numpy==1.5.1 which are outdated.
Checklist

[x] I have merged the latest main branch into current branch.
[x] I have run bash scripts/format.sh before merging.
Please use "squash and merge" mode.

@QuanyiLi Do we have license issue here?

The protobuf definitions are under Apache 2.0, so it should hopefully be fine. I'm not sure under which license scenarionet is under though.

Like MetaDrive, ScenarioNet can use Apache 2.0 as well. So there won't be conflicts.

authors: QuanyiLi pengzhenghao pimpale

repo: metadriverse/scenarionet


text:
Error running example dataset

Hi,
The program seems to fail with the example datasets provided in the repo. I did a conda installation with the yaml file running on MacOS
Please help troubleshoot it.
$mummer2circos -l -r genomes/NZ_CP008827.fna -q genomes/*.fna
nucmer -b 200 -c 65 -g 90 -l 20 -p CP006659 genomes/NZ_CP008827.fna genomes/CP006659.fna Traceback (most recent call last):   File "/Users/rajaldebnath/miniconda3/envs/mummer2circos/bin/mummer2circos", line 8, in <module>     sys.exit(main())   File "/Users/rajaldebnath/miniconda3/envs/mummer2circos/lib/python3.7/site-packages/mummer2circos/__init__.py", line 67, in main     blast_identity_cutoff=args.blast_identity_cutoff)   File "/Users/rajaldebnath/miniconda3/envs/mummer2circos/lib/python3.7/site-packages/mummer2circos/mummer2circos.py", line 71, in __init__     nucmer_utility.execute_promer(fasta1, fasta2, algo="nucmer")   File "/Users/rajaldebnath/miniconda3/envs/mummer2circos/lib/python3.7/site-packages/TPutils/nucmer_utility.py", line 41, in execute_promer     raise Exception("%s" % b) Exception: b'1: PREPARING DATA\n2,3: RUNNING mummer AND CREATING CLUSTERS\n# reading input file "CP006659.ntref" of length 5766619\n# construct suffix tree for sequence of length 5766619\n# (maximum reference length is 18446744073709551612)\n# (maximum query length is 18446744073709551615)\n# process 57666 characters per dot\n#....................................................................................................\n# CONSTRUCTIONTIME /Users/rajaldebnath/miniconda3/envs/mummer2circos/opt/mummer-3.23/mummer CP006659.ntref 2.46\n# reading input file "/Users/rajaldebnath/Software/mummer2circos/examples/genomes/CP006659.fna" of length 5781131\n# matching query-file "/Users/rajaldebnath/Software/mummer2circos/examples/genomes/CP006659.fna"\n# against subject-file "CP006659.ntref"\nERROR: mummer and/or mgaps returned non-zero\n'

Hi @rajaldebnath
It's an error from nucmer, but it's not very detailed, it's difficult to say what could be the cause of the problem. The easiest way to avoid this problem would be to use the docker container instead of installing the conda environment.
Do you also have an error if you use promer instead of nucmer?
mummer2circos -l -r genomes/NZ_CP008827.fna -q genomes/NZ_CP012745.fna -a promer
You can also try to use blast instead of mummer using the following command, but you will need to upgrade mummer2circos first
# update mummer2circos
conda activate mummer2circos
pip install --upgrade --force-reinstall git+https://github.com/metagenlab/mummer2circos
# run with megablast
mummer2circos -l -r genomes/NZ_CP008827.fna -qmummer2circos -l -r genomes/NZ_CP008827.fna -q genomes/NZ_CP012745.fna -a megablast

You can also try to update mummer to version 4
conda activate mummer2circos
# install mummer4
conda install -c bioconda mummer4

Thank you for your response. It works with nucmer and blast as an algorithm but does not generate the synteny plot with megablast.
Also, I just wanted to know if mummer2circos can be used for eukaryotic synteny analysis.
(mummer2circos) $ mummer2circos -r genomes/NZ_CP012745.fna -q genomes/*.fna -gb GCF_000281535_merged.gbk -b VF.faa -s GCF_000281535.depth -lf labels.txt -a megablast Traceback (most recent call last):   File "/home/ramesh/anaconda3/envs/mummer2circos/bin/mummer2circos", line 8, in <module>     sys.exit(main())   File "/home/ramesh/anaconda3/envs/mummer2circos/lib/python3.7/site-packages/mummer2circos/__init__.py", line 67, in main     blast_identity_cutoff=args.blast_identity_cutoff)   File "/home/ramesh/anaconda3/envs/mummer2circos/lib/python3.7/site-packages/mummer2circos/mummer2circos.py", line 80, in __init__     hit_list, query_list = self.get_link("%s.coords" % outname, algo=algo)   File "/home/ramesh/anaconda3/envs/mummer2circos/lib/python3.7/site-packages/mummer2circos/mummer2circos.py", line 1060, in get_link     10 + shift]) + '\t' + l[2] + '\t' + l[3] + '\tcolor=%s' % color_id + '\n') UnboundLocalError: local variable 'shift' referenced before assignment

authors: rajaldebnath tpillone


text:
Set aria-expanded attribute

Resolves #11

Can you ask someone to review this @jbalsas?

We are looking at adding this to our current sprint, so should be swinging around here shortly

Wonderful.
For posterity sake, the purpose of this PR is to add ARIA attributes to toggle components in order to communicate its expanded or collapsed state to accessibility tools.

aria-expanded indicates whether the element, or another grouping element it controls, is currently expanded or collapsed.
— https://www.w3.org/TR/wai-aria/states_and_properties#aria-expanded

For that reason I have added aria-expanded to both the toggle controller and the section it controls.

Later, I would like to expand on this PR to improve accessibility even further by adding aria-controls to the toggle controller in order to indicate the section it controls. This would also require adding an id to the section it controls. Using both aria-controls and aria-expanded is a recommended practice.

aria-controls identifies the element (or elements) whose contents or presence are controlled by the current element.
— https://www.w3.org/TR/wai-aria/states_and_properties#aria-controls

If the element with the aria-expanded attribute controls the expansion of another grouping container that is not 'owned by' the element, the author SHOULD reference the container by using the aria-controls attribute.

Here are two existing, popular projects on the web following this convention:

https://getbootstrap.com/docs/4.0/components/collapse/
https://adobe-accessibility.github.io/Accessible-Mega-Menu/

And here is illustrative markup to summarize all of the attributes being used and what their relationship would be like:
<x-control-element
  aria-controls="${ contentId }"
  aria-expanded="${ isExpanded }"
/>
<x-content-element
  id="${ contentId }"
  aria-expanded="${ isExpanded }"
  aria-hidden="${ !isExpanded }"
  aria-labelledby="${ controllerId }"
/>

Thanks for the detailed explanation @jonathantneal!

Resent with #15.

authors: Robert-Frampton jbalsas jonathantneal zenorocha

repo: metal/metal-toggler


text:
🌱 Bump Dockerfile golang image tag to v1.18.10

golang images less than v1.18.10 is vulnerable. Relates to https://github.com/kubernetes-sigs/cluster-api/issues/7974

/test-ubuntu-integration-release-1-2

/cc @lentzi90 @mboukhalfa


text:
🌱 Improve logging when releasing address

What this PR does / why we need it:

Add log when clearing IPClaim from IPPools allocations.
Disable logs for unit tests

/test unit

/test-ubuntu-integration-main

/cc @kashifest

Disable logs for unit tests

Does this mean there wont be any log while you run unit tests, wouldn't it be difficult to debug while writing tests ?

Disable logs for unit tests

Does this mean there wont be any log while you run unit tests, wouldn't it be difficult to debug while writing tests ?

It is the same we do in CAPM3 and other places (e.g. here. Logs are generally not useful in unit tests since we run hundreds of them and often in parallel. This makes it hard to keep track of which test the logs are coming from. Nothing is preventing enabling the logs again for specific tests while debugging.

parallel

Thanks for the clarification. I am still old school and like lots of logs!!!!!
/approve


text:
🌱 Bumping CAPI to 1.5.2

What this PR does / why we need it:

Bump Uplifts CAPI to v1.5.2
Bump Cert-manager to v1.13.0
Bump GO to 1.20.8

/test-centos-e2e-integration-main
/test-ubuntu-integration-main

/test-centos-e2e-integration-main
/test-ubuntu-integration-main

authors: adilGhaffarDev tuminoid


text:
is there any features with interaction with Panthom wallet ?

I need to mint using panthom wallet not keypair directly.
How can i handle this? please let me know.

https://solana-labs.github.io/wallet-adapter/

This is the base line requirements to use metaplex with the wallet adapter instead of the keypair. The if statement at the bottom is so that metaplex can establish a connection even if the wallet hasn't yet connected. Without that, it will thrown an error when there isn't a connected wallet. This is NOT and end - end solution. It's merely demonstrating the minimum required imports. You will likely need to import other things in addition what I have listed below.
import { Connection } from "@solana/web3.js";
import { Metaplex, walletAdapterIdentity, guestIdentity } from "@metaplex-foundation/js";
import { useWallet } from "solana-wallets-vue";

const wallet = useWallet();
const connection = new Connection("endpoint url here");
const metaplex = Metaplex.make(connection).use(
  wallet?.wallet?.value?.adapter ? walletAdapterIdentity(wallet.wallet.value.adapter) : guestIdentity()
);

authors: bytesmix devfather nurav97

repo: metaplex-foundation/js-examples


text:
Remove rest of moldb references

Fixes the sci test failing in master. Removes the rest of the references to the moldb service in docker-compose config files.

@LachlanStuart please review the new changes


text:
Join query issue

I get this error, when I try this join query
SELECT * FROM druid._pbngx left join druid._pbngx ON druid._pbngx.Category=druid._pbngx.Category;
Error:
An error occurred during query execution. Please contact your system administrator. (SQLException (00000) (-1) : Error -1 (00000) : Error while executing SQL "SELECT * FROM druid._pbngx left join druid._pbngx ON druid._pbngx.Category=druid._pbngx.Category": Remote driver error: RuntimeException: org.apache.calcite.tools.ValidationException: org.apache.calcite.runtime.CalciteContextException: From line 1, column 38 to line 1, column 49: Duplicate relation name '_pbngx' in FROM clause -> ValidationException: org.apache.calcite.runtime.CalciteContextException: From line 1, column 38 to line 1, column 49: Duplicate relation name '_pbngx' in FROM clause -> CalciteContextException: From line 1, column 38 to line 1, column 49: Duplicate relation name '_pbngx' in FROM clause -> SqlValidatorException: Duplicate relation name '_pbngx' in FROM clause)

You can modify and issue your query like this :
SELECT * FROM druid._pbngx t1 left join druid._pbngx t2 ON t1.Category=t2.Category;

Thank you @i1befree It works !

repo: metatron-app/metatron-discovery


text:
[Bug] 資料其實存在但是搜索刮不到資料

Verify steps

[X] Is this something you can debug and fix? Send a pull request! Bug fixes and documentation fixes are welcome.
[X] I have read the Wiki, especially the FAQ page.
[X] I have searched on the issue tracker for a related issue.

MetaTube Plugin Version
2023.503.910.0
MetaTube Server Version
數據庫
What OS are you seeing the problem on?
Linux
Description
使用完整番號刮去不到資料，比如搜索ipzz-020是空的，但是搜索ipzz-卻可以在裡面找到ipzz-020。這意味著ipzz-020是有資料的。但是現在直接搜索ipzz-020是沒法搜索到資料
MetaTube Server
No response
Jellyfin/Emby Logs
No response
MetaTube Server Logs
No response
How to Reproduce
No response

已解決


text:
IMPRO-1606: Ensure cycle time updated in cycle blending

In cycle blending the latest cube is currently used to set the cycle time (forecast reference time). If a file is missing for a particular validity time in the cycle in which the blending occurs, the cycle time for the output will be set as the most recent cycle for which data was available. This results in the forecast reference times for the blended output files from a given cycle potentially differing from one another.
There is an associated suite PR which adds the --cycletime argument for cycle blending.
We may wish to consider adding a CLI test for this behaviour, but I have not had time.
This work:

Ensures that if a cycletime argument is provided, even if we are processing a single cube in cycle blending, the cycletime of the output is updated.
I've added a unit test to cover this behaviour.

Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

@fionaRust as discussed, the multiple old cube case is covered by the suite change which now includes the cycletime argument. As such the blended output cycletime is updated in the WeightedBlendAcrossWholeDimension plugin. The change here covers the case of a single cube being passed in, which is returned before reaching this plugin.

repo: metoppv/improver


text:
Move hotmic to metrics.

This is a WIP to move hotmic to its new home as metrics.  We're also taking some time to flesh out more of the metrics-core support.
Open issue(s):

[ ] high tail latencies for sends, presumably due to histogram changes

@tobz we prob also want to move that benchmark to be a real one based on like criterion?

authors: LucioFranco tobz

repo: metrics-rs/metrics


text:
Issue in building MFEM on Vulcan

I am trying to build mfem on Vulcan and I am getting errors. I am following the steps below.
cd config
cp defaults.mk user.mk
Open user.mk in an editor
In place of CXX write CXX = bgxlC
In place of MPICXX write MPICXX = mpixlcxx
OPTIM_FLAGS = -O2
MFEM_USE_MPI         = YES
MFEM_MPIEXEC    = srun
MFEM_MPIEXEC_NP = -n
Save File
cd ..
make config USER_CONFIG=config/user.mk
make parallel -j10.
below is the error I am getting
===============ERRORS================================================
.
mpixlcxx  -O3 -I./../hypre-2.10.0b/src/hypre/include  -c fem/pgridfunc.cpp -o fem/pgridfunc.o
1500-036: (I) The NOSTRICT option (default at OPT(3)) has the potential to alter the semantics of a program.  Please refer to documentation on the STRICT/NOSTRICT option for more information.
mpixlcxx  -O3 -I./../hypre-2.10.0b/src/hypre/include  -c fem/plinearform.cpp -o fem/plinearform.o
1500-036: (I) The NOSTRICT option (default at OPT(3)) has the potential to alter the semantics of a program.  Please refer to documentation on the STRICT/NOSTRICT option for more information.
mpixlcxx  -O3 -I./../hypre-2.10.0b/src/hypre/include  -c fem/pnonlinearform.cpp -o fem/pnonlinearform.o
mpixlcxx  -O3 -I./../hypre-2.10.0b/src/hypre/include  -c fem/sidredatacollection.cpp -o fem/sidredatacollection.o
mpixlcxx  -O3 -I./../hypre-2.10.0b/src/hypre/include  -c fem/staticcond.cpp -o fem/staticcond.o
1500-036: (I) The NOSTRICT option (default at OPT(3)) has the potential to alter the semantics of a program.  Please refer to documentation on the STRICT/NOSTRICT option for more information.
"fem/pfespace.cpp", line 2390.6: 1540-0290 (S) The function template parameter "T" has been found to have two values: "double" and "T".
make[1]: *** [fem/pfespace.o] Error 1
make[1]: *** Waiting for unfinished jobs....
1500-036: (I) The NOSTRICT option (default at OPT(3)) has the potential to alter the semantics of a program.  Please refer to documentation on the STRICT/NOSTRICT option for more information.
1500-036: (I) The NOSTRICT option (default at OPT(3)) has the potential to alter the semantics of a program.  Please refer to documentation on the STRICT/NOSTRICT option for more information.
make[1]: Leaving directory `/g/g92/bhowmik1/proxyapps/bgqos_0/Laghos/mfem'
make: *** [parallel] Error 2

Hi Saptarshibh,
Can you try building MFEM with the CEED/benchmarks repository?
See in particular the following files:
https://github.com/CEED/benchmarks/blob/master/machine-configs/vulcan.sh
https://github.com/CEED/benchmarks/blob/master/package-builders/mfem.sh
Tzanio

Thank you Tzanio,
Sure, I am trying to build it with ceed/benchmark.
Regards,
Saptarshi Bhowmik
From: Tzanio Kolev notifications@github.com
Reply-To: mfem/mfem reply@reply.github.com
Date: Monday, July 2, 2018 at 7:21 AM
To: mfem/mfem mfem@noreply.github.com
Cc: "Bhowmik, Saptarshi" bhowmik1@llnl.gov, Author author@noreply.github.com
Subject: Re: [mfem/mfem] Issue in building MFEM on Vulcan (#523)
Hi Saptarshibh,
Can you try building MFEM with the CEED/benchmarkshttps://github.com/CEED/benchmarks repository?
See in particular the following files:
https://github.com/CEED/benchmarks/blob/master/machine-configs/vulcan.sh
https://github.com/CEED/benchmarks/blob/master/package-builders/mfem.sh
Tzanio
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mfem/mfem/issues/523#issuecomment-401821575, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Am0XW3VDEIltRWISzTifhiIMHjm7Hjdzks5uCixagaJpZM4U9ozk.

Hi Saptarshibh, were you able to complete the build?

Hi Tzanio,
Thank you for the help. I was able to build mfem on Vulcan.Thnk you so much.
Reagrds,
Sap Bhowmik
From: Tzanio Kolev notifications@github.com
Reply-To: mfem/mfem reply@reply.github.com
Date: Wednesday, July 11, 2018 at 11:58 PM
To: mfem/mfem mfem@noreply.github.com
Cc: "Bhowmik, Saptarshi" bhowmik1@llnl.gov, Author author@noreply.github.com
Subject: Re: [mfem/mfem] Issue in building MFEM on Vulcan (#523)
Hi Saptarshibh, were you able to complete the build?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mfem/mfem/issues/523#issuecomment-404409605, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Am0XW7obk_V-0Chf2EufF36l0dRfrNDPks5uFvNzgaJpZM4U9ozk.

authors: Saptarshibh tzanio

repo: mfem/mfem


text:
Recycle memory when recomputing geo-factors/ add user option for nodes.

This PR enables the GeometricFactors class to calculate geometric factors based on user provided nodes. I also did a minor clean up on the class.
Resolves #1500.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#1517
@artv3
@tzanio
@camierjs + @v-dobrev
06/07/20
⌛due 06/21/20
⌛due 06/28/20

I think this PR could be used for issue https://github.com/mfem/mfem/issues/1500. I noticed a performance improvement in my application by recycling memory when computing geometric factors.

@tomstitt , I added a few adjustments here to avoid CUDA mallocs when recomputing geometric factors.

@camierjs and @v-dobrev reminder that the reviews for this PR are due this week

@artv3, can you update us on the status of this PR?

@artv3, can you update us on the status of this PR?

I could use some help understanding why ->Recompute() did not update geometric factors as I expected. Is it that the nodes in the geometricfactors class become null or deleted as the application cycles? And we need to use new ones?

Looking at the code, GeometricFactors::AssembleWithNodes ensures that the internal mesh and nodes data members are synchronized, i.e. mesh->GetNodes() == nodes or equivalently mesh == nodes->FESpace()->GetMesh().
GeometricFactors::Recompute() just uses the nodes data member, so if the mesh nodes have been updated it will produce incorrect results.
We can maybe make the assumption that mesh and nodes are synced explicit by adding something like this in the beginning of Recompute():
if (nodes != mesh->GetNodes())
{
   nodes = mesh->GetNodes();
}

maybe even without the if.

Looking at the code, GeometricFactors::AssembleWithNodes ensures that the internal mesh and nodes data members are synchronized, i.e. mesh->GetNodes() == nodes or equivalently mesh == nodes->FESpace()->GetMesh().
GeometricFactors::Recompute() just uses the nodes data member, so if the mesh nodes have been updated it will produce incorrect results.
We can maybe make the assumption that mesh and nodes are synced explicit by adding something like this in the beginning of Recompute():
if (nodes != mesh->GetNodes())
{
   nodes = mesh->GetNodes();
}

maybe even without the if.

Thanks @tzanio , we are trying a few things with Umpire which may make the memory allocations and deletes okay. Will keep the team posted and update this PR as needed.

Merged in next for testing...

We're able to "hide" the mallocs in by telling the Vectors to use the temporary memory pool is this branch: https://github.com/mfem/mfem/blob/feature/tomstitt/temp-mem-type/mesh/mesh.cpp#L10536-L10556 so we might not want to merge this one because it will increase the permanent memory usage

We're able to "hide" the mallocs in GeometricFactors by telling the Vectors to use the temporary memory pool is this branch: https://github.com/mfem/mfem/blob/feature/tomstitt/temp-mem-type/mesh/mesh.cpp#L10536-L10556 so we might not want to merge this one because it will increase the permanent memory usage

Thanks, one additional feature this PR provided is being able to compute geometric factors with a user set of nodes. I'm going to close this PR and re-open a PR once it is ready.

@artv3, let me know when it is safe to delete the branch

We can delete now, I can do that.

authors: artv3 tomstitt tzanio


text:
Variable order NURBS elements [varnurbs-dev]

This patch should allow the use of variable order NURBS in MFEM. For each space each knot vector in the mesh can have a different order.
This modification forced the initiation procedure for the NURBSext and associated FESPACE  to be modified. The requested order is now given to the NURBSext in the constructor, and passed down to
the FE right before evaluation.  I believe the initiation of the NURBSext and FESPACE is a bit more natural, in the current form.
This order information residing in the NURBSext is written in the fespace header of the solution vector file to facilitate visualisation.
The order modification of the FE in runtime seems to violate some code  design assumptions, as some variables had to be declared mutable. But this did not pose any problems.
I believe the changes work in serial and parallel and visualise correctly in GLVIS and ViSit, after recompilation of course.
The reason for implementing variable order NURBS is the step towards H(div) and H(curl) conforming elements based on NURBS, effectively these are higher order continuity extensions of the Nedelec elements (of the 2nd kind?).
TODO:

[x] Cleanup examples before merging
[x] Remove debug printouts

Example 1 on the new pipe-nurbs-2d:

Approved modulus TODO items (in issue description).

@IdoAkkerman, @tzanio,
As you probably noticed, I added quite a few updates to the PR, so please take another look and let me know if anything looks suspicious or you do not like something I added.
The only remaining thing that I want to change is the NURBS-extended versions of the examples. I think it is better to keep the examples simple, so I propose to copy the changes related to variable-order NURBS to a new directory, e.g. miniapps/iga or miniapps/nurbs and remove the changes from the files in the examples directory. What do you think?

I differ to Ido on the code changes, but they all looked good to me.
Regarding the examples, I will also like to keep them simple so I agree that we probably don't want to merge the current changes.
In addition to Veselin's suggestion to moving the current modifications to a miniapps sub-directory, another option could be to postpone the illustration of variable-order NURBS to a better/specific example or miniapp to be added later (e.g. one using NURBS-based H(div)/H(curl) conforming elements)?

I have been struggling with rebasing my fork. At first I was mortified that "everything" changed and got broken. I but I think I am coming to grips with it...
I checked out:
git checkout remotes/upstream/varnurbs-dev
and I am not able to run:
ex1p -m   ../data/ball-nurbs.mesh
I am working on a fix.... or question?...

It seems to work now. I will have a closer look later this week.
Any particulars to look at?

The deep copy construct on lines 1181--1215 is that to facilitate compiler optimisations, or some stricter enforcement of coding style? Same is for the addition of the const keywords here and there?

Hi @IdoAkkerman,
The copy constructor and the const keywords were not about enforcing any rules.
I added the copy constructors, so that we can implement the Mesh and ParMesh copy constructors for NURBS meshes - having these was useful for some example codes. The const keywords were just something I noticed and decided to propagate - it could be useful for catching misuse and it also indicates intent, e.g. if an argument is const then it is purely an input parameter.

Just to be sure.
I did find a bug? But you fixed it a different way?

Hi @IdoAkkerman,
Yes and yes.
The call to the Mesh copy constructor (that you fixed by using shallow copy) was wrong - instead of calling it with Mesh & parameter it was called with Mesh * parameter, so what was happening there was an implicit construction of Mesh * to NCMesh and then a call the Mesh constructor that takes NCMesh &. So I just needed to de-reference the Mesh * to get it working. I also added a few explicit keywords to forbid some of these implicit conversions, e.g. the one from Mesh * to NCMesh.
What do you think about my suggestion regarding the examples? Are you OK to move them in a new directory, e.g. in miniapps/iga or miniapps/nurbs? The idea is to keep the examples simple and have more advanced usage (as variable-order nurbs spaces) illustrated in the miniapps.

@IdoAkkerman we will like to merge this soon, any chance you can review and give final approval?

authors: IdoAkkerman tzanio v-dobrev


text:
SSH host key verification: Can't deploy with a stack.yaml that points at github

I have an application that references an open-source haskell library on Github.
When I try to deploy my application to Heroku I get the following error in my output:
remote: stack will use a sandboxed GHC it installed
remote: For more information on paths, see 'stack path' and 'stack exec env'
remote: To use this GHC and packages outside of a project, consider using:
remote: stack ghc, stack ghci, stack runghc, or stack exec
remote: Cloning into '/app/.stack-work/downloaded/PCfuyCv8X378'...
remote: Host key verification failed.
remote: fatal: Could not read from remote repository.
remote:
remote: Please make sure you have the correct access rights
remote: and the repository exists.
remote: Process exited with ExitFailure 128: /usr/bin/git clone --recursive git@github.com:jdreaver/eventful.git /app/.stack-work/downloaded/PCfuyCv8X378
remote:  !     Push rejected, failed to compile Haskell app.
remote:
remote:  !     Push failed

The clone command works fine locally, and if I exec it using heroku run I do indeed get prompted to accept Github's SSH host key.
I'm not quite sure who's job it should be to add/accept the host key. The example in README.md kinda implied it should Just Work™. I'm not sure how I'd go about hooking into the build process of the Dyno to add the right host keys before the clone.

I temporarily worked around this and got the host key into the dyno, only to discover that, of course, the second permissions error is not the host key, but github denying the heroku dyno to clone over SSH.
Sorry to have bothered you!

repo: mfine/heroku-buildpack-stack


text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113519

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113739


text:
http get can't read  datasource for singleton like {name:'Ben',sex:'man'}

IMPORTANT: This repository's issues are reserved for feature requests and bug reports. Do not submit support requests here.
Steps to reproduce and a minimal demo of the problem
if data.json like {name:'Ben',sex:'man'},how to use the http for rxjs
What steps should we try in your demo to see the problem?
Current behavior
data.json just use data for array?
Expected/desired behavior
i can't get the datasource for singleton
Other information

For support requests you can use gitter or take a look at project's the wiki page in order to get more complete idea on how the it works.


text:
import destructuring space fails on one case

I got a report that something like import * as foo from './foo' makes it cry.
So a reminder to fix it.

It is fixed in master.

Ah, I am blind, sorry.

No problem. Would you try with the latest version?

authors: Foxandxss mgechev

repo: mgechev/codelyzer


text:
🛑 Strapi Home Page is down

In da149bd, Strapi Home Page (https://cms.wavemoney.io) was down:

HTTP code: 403
Response time: 65 ms

Resolved: Strapi Home Page is back up in ed379d3 after 2 hours, 43 minutes.

repo: mgmgpyaesonewin/strapi-upptime


text:
Cannot find module 'fs-plus'

Error: Cannot find module 'fs-plus'
at Module._resolveFilename (module.js:455:15)
at Module._resolveFilename (D:\Program Files\Atom x64\resources\electron.asar\common\reset-search-paths.js:35:12)
at Function.Module._resolveFilename (D:\Program Files\Atom x64\resources\app.asar\src\module-cache.js:383:52)
at Function.Module._load (module.js:403:25)
at Module.require (module.js:483:17)
at require (D:\Program Files\Atom x64\resources\app.asar\src\native-compile-cache.js:50:27)
at Object. (C:\Users\Administrator.atom\packages\remote-ftp\lib\remote-ftp.js:11:15)
at Module._compile (D:\Program Files\Atom x64\resources\app.asar\src\native-compile-cache.js:109:30)
at Object.value [as .js] (D:\Program Files\Atom x64\resources\app.asar\src\compile-cache.js:216:21)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (D:\Program Files\Atom x64\resources\app.asar\src\native-compile-cache.js:50:27)
at Package.module.exports.Package.requireMainModule (D:\Program Files\Atom x64\resources\app.asar\src\package.js:796:27)
at D:\Program Files\Atom x64\resources\app.asar\src\package.js:123:28
at Package.module.exports.Package.measure (D:\Program Files\Atom x64\resources\app.asar\src\package.js:96:15)
at Package.module.exports.Package.load (D:\Program Files\Atom x64\resources\app.asar\src\package.js:110:12)
at PackageManager.module.exports.PackageManager.loadPackage (D:\Program Files\Atom x64\resources\app.asar\src\package-manager.js:468:14)
at D:\Program Files\Atom x64\resources\app.asar\src\package-manager.js:412:19
at Config.module.exports.Config.transact (D:\Program Files\Atom x64\resources\app.asar\src\config.js:312:16)
at PackageManager.module.exports.PackageManager.loadPackages (D:\Program Files\Atom x64\resources\app.asar\src\package-manager.js:407:19)
at D:\Program Files\Atom x64\resources\app.asar\src\atom-environment.js:792:28

Cannot find module 'fs-plus‘’

Try reinstall remote-ftp!

npm(apm) install

Chinese garbled

authors: binxChen icetee yangshare

repo: mgrenier/remote-ftp


text:
Add floats?

Is this something you want? I thought maybe decimal but it would be a new dep.

This is welcome!
Decimal can accomplished with the raw schematic.

the property tests might fail, so you can ignore it for now. I have a PR #12 to fix them.

authors: jeregrine mhanberg

repo: mhanberg/schematic


text:
Unreachable code - sentry-example-api/route.js

Unreachable code.
All code should be reachable [javascript:S1763]
src/app/api/sentry-example-api/route.js
import { NextResponse } from "next/server";
export const dynamic = "force-dynamic";
// A faulty API route to test Sentry's error monitoring
export function GET() {
throw new Error("Sentry Example API Route Error");
return NextResponse.json({ data: "Testing Sentry Error..." });
Unreachable code.
}

This is Senty.io code example I removed

repo: mhenke/omaha-playground-collective


text:
New F5 metrics, cluster support and looping/service support

The changes here add the ability for the f5 collector to run as a service in a loop given a set time interval.  This drastically reduces system load and makes the metric collection timing more consistent.
This also adds the ability to only collect certain metrics from the active node in a cluster vs collecting all metrics all the time.
Also added code to dig into a pools members and send in metrics for those (e.g. current sessions/connections) etc.
Additionally, stat recursion logic has been moved into a function, names are now "cleaned" (forward slashes and double .'s removed).

Hi, @zonywhoop. I've pushed a long overdue update of the F5 collector to the repository. Some of the enhancements have overlap with your pull request. Specifically, pool member statistics are now included (along with several other new categories of statistics).
I do like the idea of being able to run in a continuous polling mode. I would like to potentially find a way to incorporate this into the current code base.
Similarly, the ability to dynamically skip certain metrics or metric categories based upon which node is active in an HA cluster is pretty neat. Does this play nice with traffic groups? I would personally like to have command line options that indicate what gets skipped on the inactive member.

Hey @mhite, I looked over the code change you just committed up and there are definitely a good bit of changes.  I can definitely refactor my code a bit with the new base but it will take some time.  One of the new things I added was function that loops over the handed dictionary with the STATISTICS_* indexes/values from the F5.  In conjunction you can also pass it a separate list that contains the values you want to capture or null to capture all.  The function then creates the graphite metric dictionary for that set of statistics and returns it.  This really simplified/reduced the code for processing each set of metrics, for me at least.  So if you are good with using that then I will wrap that back in to your changes as well.
On the HA cluster code, traffic groups are not currently taken into account.  If the cluster node is "FAILOVER_STATE_ACTIVE" then all metrics are collected as normal.  If the value is anything else then metrics involved VS, TMM, etc are skipped.  I do not currently have any F5's clustered that I can play with traffic groups in but could potentially spin some up on my machine.. Would be interesting to see how that would work.

I totally agree -- the redundant collection stuff belongs in its own function. I'll take a closer look at what you've done there.
Also, I want to get the new carbon class tested better, merge it, and then start to tackle some of other functionality we've been discussing. I'll start to open issues to address each one of these. There's a nasty bug in the remote timestamp right now that also needs to be fixed.
I plan on diving this week -- will update you soon.
Do you mind kicking the tires on the plaintext branch to test both plaintext and pickle delivery?

I merged the 'plaintext' branch into master. Also created new branch called 'timestamp' that should fix the remote timestamp issue.
Once I've got this all tested, can dig further into the items you've brought up!

Hey Matt,
Been working on another project but I’ll give the plaintext branch a whirl and see how it goes.  Hoping I’ll have some time in the next week or so to merge back in the function for stat collection too.  Let me know if I can help with anything else.
--
Ed McLain
ed@edmclain.com

On Aug 17, 2015, at 11:01 PM, Matt Hite notifications@github.com wrote:
I merged the 'plaintext' branch into master. Also created new branch called 'timestamp' that should fix the remote timestamp issue.
Once I've got this all tested, can dig further into the items you've brought up!
—
Reply to this email directly or view it on GitHub https://github.com/mhite/graphite-collectors/pull/3#issuecomment-132065455.

authors: mhite zonywhoop

repo: mhite/graphite-collectors