Support for multiple clusters

Thanks for continuing the development of prometheus-slurm-exporter
We have a set of independent clusters, which can be controlled from a single machine using the --clusters option (in e.g., squeue or sinfo). This allows us to centralize the management whilst maintaining completely independent installations.
We would like to use prometheus-slurm-exporter from this single machine to get information from all the clusters.
Our current homemade solution has been to add an extra option (-slurm.cluster <clustername>) to specify which cluster to export, and then run multiple instances of prometheus-slurm-exporter. As you can guess, this is hardly scalable after a few clusters and requires a lot of manual configuration (setting up ports,...).
Thus, the ideal solution for us would be to have prometheus-slurm-exporter to export the cluster information.
We have done some explorations of this and it seems trivial for --json as the cluster field is already there.
Only expanding the metrics fields to include a "cluster" field would suffice.
For the fallback CLI, this may not be that easy as there is no cluster output when formatting with -o.
I wouldn't mind dedicating some time to this, but as I'm not very familiar with Go and this code, I think that someone with a deeper understanding of Go could implement this easily.
Thanks

Just an update, we have chosen at the end to simply deploy separate exporter in each cluster and then gather the data in a single prometheus. It still requires deploying a few instances, but for now, it is manageable.
It would be okay if this issue is closed or marked low-priority.

Oh snap, sorry I missed this. For some reason, I didn't get a notification. We can add static labels for multi-cluster support. If you'd like to give it go be my guest. Currently, we believe launching an exporter per cluster is ideal as you can then configure each exporter independently. For example, if you need different poll limits or custom CLI opts for each cluster it'd be better to keep them independent. How do you guys deploy the exporter currently? With -json or the cli-fallback?

No problem :)
Yes, I think that in the end it is more customizable to have an exporter per cluster. The installation of the exporter is now part of our procedures when deploying new clusters, so it is not very time-consuming to set up (and so far quite stable).
We have been using the cli-fallback so far as we do not compile slurm with json.

Sounds good! I think the preferable approach here would be to use the slurmrestd and poll a list of urls. Do you have slurmrestd setup? I have no idea how to switch targeted clusters on the cli. If that's super easy, then if you could give the cmd line on how to do that/ref that'd be great. if its a cli opt, I think it'd be as simple as modifying the configs struct for each cluster and then registering each config. I could give it a go late next week if you think that approach makes sense

Closing for now...


Move drush site aliases to ../drush

Drush site aliases are now recognized automatically in a drush folder one level above the web root (see https://github.com/drush-ops/drush/blob/master/examples/example.aliases.drushrc.php). We should follow this convention, this also means we would have one less file in the Drupal-specific conf folder.

Project build.sh should be updated to reflect this change. It assumes aliases file to be found under drupal/conf when linking it.


HADOOP-17077. S3A delegation token binding to support secondary binding list

2083

 Quality gate: Failed
19 Issues

 4 Vulnerabilities
 14 Code issues
 1 Anti-patterns

Details

 Quality gate: Failed
14 Issues

 4 Vulnerabilities
 10 Code issues

Details


Upgrade to npm-groovy-lint 12.0.0

Minimum java version is now 17

@stevenh oops with 12.0.0 :(
Help ?  ❤

Hi @nvuillam I would like to give it a shot 🔥
Could you please run test workflow on current 2.0.0 version?
It seems tests were already failing back then but runs history have been purged and I would like to be sure I get same error when I test locally

I do have a big rewrite of the tests pending, as I found that currently they are very dependent on internal state, so when running locally, including independently they are very flaky.
Haven't had much time recently as been busy at work. Hopefully in the next few weeks, todays job is getting CodeNarc fix in kindly done by @chrismair 👍

@stevenh that's great, many thanks !
If you think @djukxe can help you, please invite him to work on your fork / branch :)

Need to get some more issues fixed in npm-groovy-lint first.


cmake: make install include dir configurable

Workaround for #172, one can set -DCMAKE_INSTALL_INCLUDEDIR=include/legion to chance the install location (and the library interface) to workaround header collisions.

@chuckatkins : please review!

I see the issue this is referencing but I'm still not sure I get the problem it's trying to solve.  IS the issue at hand conflicts because of sharing an installation directory with other projects?

Yes, if you share the include directory with libscrotch, scotch won't compile.
Long term headers like common.h should not be installed in the root include, but for now we can put them in a sub directory using CMAKE_INSTALL_INCLUDEDIR and can still have the lib directory with other projects.

I don't particularly like the idea of the include dir being configurable since it opens the door for a lot of inconsistencies on how legion will be deployed by various people.  I'd rather see the issue addressed in how the headers are organized within the project itself and then still install into a consistent directory.

Perhaps to re-org to have:
runtime/lowlevel
runtime/highlevel
runtime/mappers
runtime/realm
And then always install headers from runtime/ into include/legion/.  The only directory to be added to -I then would be /path/to/install/include/legion for the install interface or /path/to/source/runtime for the build interface.  It would also remove the need to have multiple legion include dirs specified in the interface.   It would be a more invasive change but you'd end up with, at least in my opinion, a more maintainable and better code layout.

See my comments on #177, this will be a destructive change.

And hence I like a band-aid for now, beside the fact that it is confusing to have CMAKE_INSTALL_INCLUDEDIR exposed as a configure option, but being functional.

I did see that.  from what I could tell though it's still being reviewed and discussed but wasn't rejected.  Can we not use that as the the path forward with this issue being resolved as a side effect?

I'm still not liking #177 much, but haven't had a chance to propose an alternative.  Ideally a 'make install' would only copy over "public" header files, and that's also at odds with a "line things up so we can just copy the whole directory tree" approach.
Doesn't the cmake version of 'make install' also create a config file that cmake uses to find things like include files?  Why does the end user have to worry about different choices of CMAKE_INSTALL_INCLUDEDIR by the installer?
@junghans Would the issue that this is trying to address go away if you weren't installing Legion into /usr or /usr/local?

I'm still not liking #177 much, but haven't had a chance to propose an alternative. Ideally a 'make install' would only copy over "public" header files, and that's also at odds with a "line things up so we can just copy the whole directory tree" approach.

I certainly agree on this.  Is there a defined set of "public" headers that I can use to take a shot at this with?

Doesn't the cmake version of 'make install' also create a config file that cmake uses to find things like include files?

Yes it does but that also assumes that a user can only consume the resulting build with CMake.  It's not a particularly unreasonable assumption to make but if things already need to go into a subdirectory then why not just always put it in the same spot.

@junghans Would the issue that this is trying to address go away if you weren't installing Legion into /usr or /usr/local?

Not really no.  The issue at hand is sharing an install directory with anything else.  Even if you're not installing to /usr or /usr/local you'll have the same problem if legion is one of may packages that make up a larger project.  This happens to always be the case when using /usr or /usr/local but it certainly come up in other situations.

@chuckatkins is correct, the problem will show up again in one way or another if you don't use subfolders.
@streichler: If you tell us, which headers should be installed I can do that, too. However, common.h, which originally triggered #172, gets included in multiples place include realm, so it still needs to get installed somewhere.
And to clarify again, this pull request is just a band-aid not a fix for #172. and hence meant as a workaround until you find a version of #177, you like.

Seeing as #172 has been resolved, can we close this?

With no votes against, the motion passes.  Closing...


YoloV7 and RealSense RuntimeError: No device connected error

Required Info

Camera Model
{ Arducam IMX219 }

Operating System & Version
Linux (Ubuntu 14/16/17)

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
NVIDIA Jetson

Language
{python}

Segment
{Artificial Vision}

Issue Description
I have installed YoloV7 and RealSense using this video as tutorial: https://www.youtube.com/watch?v=o42BFhtVqyo&t=0s
When I try to run the detect_RS.py file it shows me this message:
Traceback (most recent call last):
File "detect_RS.py", line 179, in
detect()
File "detect_RS.py", line 64, in detect
profile = pipeline.start(config)
RuntimeError: No device connected
I already installed NanoCamera and CSI-Camera, tried both and work fine, but this program can't seem to detect the camera.

Hi @NeroRGB  The JetsonHacks installation procedure and subsequent pyrealsense2 installation procedure in the video look okay.
Is the camera able to be detected if you try the simple pyrealsense2 test script at the link beow, please?
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/python#streaming-using-rspipeline

Hi @NeroRGB The JetsonHacks installation procedure and subsequent pyrealsense2 installation procedure in the video look okay.
Is the camera able to be detected if you try the simple pyrealsense2 test script at the link beow, please?
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/python#streaming-using-rspipeline

Hi! I already tried that code and the camera is still undetected, same error

The RealSense SDK and its pyrealsense2 Python wrapper is designed for Intel RealSense camera devices.  Your camera model is listed at the top of this case as Arducam IMX219.  A RealSense SDK script designed specifically for RealSense camera hardware would not be able to access a non-RealSense camera even if it was only the RGB image that was being accessed.
The YouTube video does not list the camera model but seems to assume that a RealSense camera is being used.
It is possible to import data into the SDK from non-RealSense cameras via the SDK's software device interface, but this would not be helpful for your YoloV7 project and software device works best on C++ as it has problems on Python.
https://github.com/IntelRealSense/librealsense/tree/master/examples/software-device

Hi @NeroRGB  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


<EMAIL_ADDRESS>

Release:
https://github.com/MobileNativeFoundation/rules_xcodeproj/releases/tag/2.5.0

Hello @BalestraPatrick, modules you maintain (rules_xcodeproj) have been updated in this PR. Please review the changes.


fix: ukcp c++ redists url

Was still pointing at the old ones, hence why people are having setup issues!

:tada: This PR is included in version 6.29.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


BeanieBaseUserDocument unique email index not being applied, multiple users with the same email in the database

Describe the bug
BeanieBaseUserDocument defines 2 indexes on the  email field , one being a unique index and the other being a collation. However only the collation index is applied to the email field in the database. This means that multiple users with the same emaill can end up in the database.
To Reproduce
To make reproducing this simpler i have lifted the BeanieBaseUserDocument model directly from this repo and put it into a minimal example.
Model from
https://github.com/fastapi-users/fastapi-users-db-beanie/blob/eedd1039cd8d3aece0f49fa1a90d9649ca80d1ee/fastapi_users_db_beanie/__init__.py#L16
import asyncio
from typing import Optional

from motor.motor_asyncio import AsyncIOMotorClient
from pydantic import BaseModel

from beanie import Document, Indexed, init_beanie
from pymongo import IndexModel
from pymongo.collation import Collation

class BeanieBaseUser(BaseModel):
    email: str
    hashed_password: str
    is_active: bool = True
    is_superuser: bool = False
    is_verified: bool = False

    class Settings:
        email_collation = Collation("en", strength=2)
        indexes = [
            IndexModel("email", unique=True),
            IndexModel(
                "email", name="case_insensitive_email_index", collation=email_collation
            ),
        ]

class BeanieBaseUserDocument(BeanieBaseUser, Document):  # type: ignore
    pass

async def example():
    client = AsyncIOMotorClient("mongodb://localhost:27017")
    await init_beanie(database=client.db_name, document_models=[BeanieBaseUserDocument])

    await BeanieBaseUserDocument(email="email@email.email",hashed_password="hashed_password").save()
    await BeanieBaseUserDocument(email="email@email.email",hashed_password="hashed_password1").save()

if __name__ == "__main__":
    asyncio.run(example())

The behavior is not as expected:

Instead of mongo complaining about the same email it allows multiple emails to be the same:

There is no unique index on the email field in the mongodb index list:

Expected behavior
The database should prevent duplicate emails from being added via the indexes.
Additional context

If you reverse the index definition order then the unique index works but the collation does not. Implying the second index takes precedence.
This can be fixed by putting the index definitions into a single definition  like below:

class BeanieBaseUser(BaseModel):
    email: str
    hashed_password: str
    is_active: bool = True
    is_superuser: bool = False
    is_verified: bool = False

    class Settings:
        email_collation = Collation("en", strength=2)
        indexes = [
            IndexModel(
                "email", name="case_insensitive_email_index_unique", collation=email_collation, unique=True
            ),
        ]

Software versions

beanie 1.24.0

Thank you @mthanded for the very detailed error report. I'm surprised both indices are not created properly 🤔
Anyway, it makes more sense to directly have the collation index unique, since it's the behavior we adopt on Python's side.
PR welcome to solve this :)


[Github Actions]Remove dependence on personal project

Is your feature request related to a problem? Please describe.
The current Github action test run depends on a personal maven project https://github.com/aahmed-se/setup-maven. We need to remove it https://github.com/apache/pulsar/blob/master/.github/workflows/ci-unit.yaml#L45.

@aahmed-se will you fix this issue? or @tuteng could work on it.

I don't have time right now

Closed as stale. You can report a flaky test with the corresponding issue form if it's still relevant.


Fix reserve minimal compute units for builtins

Problem
Implementing https://github.com/solana-foundation/solana-improvement-documents/pull/170 by defining MAX_BUILTIN_ALLOCATION_COMPUTE_UNIT_LIMIT to 3K CUs, then use it to allocate builtin instructions' CU Meters for VM and cost tracking for leaders.
Summary of Changes

Resolve if builtin program has been migrated to core bpf by check feature status
When calculates default tx cu limits, use MAX_BUILTIN_ALLOCATION_COMPUTE_UNIT_LIMIT per builtin instruction, including compute-budget program instructions.
Cost model reads cu limits from RuntimeTransaction's static_meta, replacing a localized implementation that isn't consistent with compute-budget.
Changes are behind Feature gate
updated existing tests to allow additional feature_set parameters (touch many files)
add final tests to verify new behavior

Feature Gate Issue: https://github.com/anza-xyz/agave/issues/2562

I'm now thinking it was a mistake to have this SIMD-0170 implementation PR also handle the builtin program migration case. How about we push that off for now since those migration feature gates aren't scheduled yet? Then this PR can just focus on making the cost tracker and compute limit agree on 3k cu's per builtin. The extra allocation for builtin migration tracking can be figured out later since we don't need to backport that part.

chat, please merge the SIMDs before the implementations


Cordova-Android Version Issue

I am having trouble with this plugin since the recent release. I was able to use the plugin until the android requirement changed. Now I cannot add the push plugin on a basic cordova app. I am getting a message stating the Android Manifest file cannot be found. This file location has changed in cordova-android 7.1. Suggestions?
Expected Behaviour
phonegap-plugin-push installs to a cordova project
Actual Behaviour
phonegap-plugin-push fails to install to a cordova Android project, but installs to cordova iOS project
Reproduce Scenario (including but not limited to)
Add cordova version 7 or higher
Add android version 7.1 as required by phonegap-plugin-push version 2.2.2
Install fails
Steps to Reproduce
Add cordova version 7 or higher
Add android version 7.1 as required by phonegap-plugin-push version 2.2.2
Attempt to install new phonegap version
Install fails
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Cordova 7/8
Cordova-Android 7.1
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
N/A
Cordova CLI version and cordova platform version
Cordova 7/8
Cordova-Android 7.1
Plugin version
latest, 2.2.2
Sample Push Data Payload
N/A
Sample Code that illustrates the problem
N/A
Logs taken while reproducing problem
Failed to install 'phonegap-plugin-push': Error: ENOENT: no such file or directory, open 'C:\Development\platforms\android\AndroidManifest.xml'
Thank you

@paperKeys what is the exact version of cordova that you are using? Are you adding the plugin to a new app or an existing app?

This is part fault of cordova-android and part fault of another plugin you are using.
Is usually caused by plugins using source-file tag for images, when this happens a res folder is created in platforms/android/, and when the res folder is there, cordova-android thinks it's an eclipse project, so it search for AndroidManifest.xml in the old location, but the file is not there because it's an Android Studio project and the location changed.

@jcesarmobile but maybe if we figure out the other plugin causing the problem we can send a PR to change the source-file tags to resource-file tags?

I think we should fix cordova-android to avoid this false positives as there is no way of being an Eclipse project, there is only Android Studio projects now. And make sure source-file tag keeps working the same way it worked in previous versions

thank you for the quick replies. this is an existing app and I had push working before this frustratingly enough.
cordova -v is 7.1.
i have the following plugins:
cordova-plugin-camera
cordova-plugin-device
cordova-plugin-file
cordova-plugin-image-picker

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

jcesarmobile - I think you may be on to something there. I have had reference errors where the project is searching for image files in that location you described. should I just remove the res folder?
what would be a recommended order of operations here?

@paperKeys it's the cordova-plugin-image-picker which isn't up to date with the latest version of cordova-android.
https://github.com/wymsee/cordova-imagePicker/blob/master/plugin.xml#L86

that was absolutely the issue. i removed the image picker plugin and was able to add the push plugin without issue.
thank you and your team for designing and maintaining this plugin, and following up on support requests the way you do. I really like this plugin and chose it because of the maintenance and support you offer. your team really helped me out on this one.


added reviews section on the home page, added basic html and css

added reviews section on the home page, added basic html and css.
would be open to suggestions to change anything.

Looks good on desktop, but the mobile view is all over the place - could you have a look at that before we merge please?

I'm still getting an issue with the reviews overspilling the mobile screen I'm afraid.  Not sure if Nico is too?  I think it needs a media query to shrink the images and font size for that bit!  The actual review bit and the button are looking much better though!


k8s-mc script help

ubuntu at omega in ~/Documents/k3s-minecraft-server on main
$ k8s-mclist
NAME   MODE   VERSION   SERVER   RUNNING
error: array index out of bounds: index 22, length 7

get the above error when i try to list my running mc servers. have no idea how to exec into them and run commands without doing this first as i dunno what the names are.

It looks like something is up with your k8s installation since k8s-mclist just calls a basic kubectl command.
To find out what pods you have running:
kubectl get pods -n minecraft

Or you could try
kubectl get pods --all-namespaces

If you don't see anything in the first command.

So k8s-mclist only does this
kubectl -n minecraft get deploy -o $format

where format is set using
format=custom-columns=\
NAME:metadata.labels.release\
,MODE:spec.template.spec.containers[0].env[22].value\
,VERSION:spec.template.spec.containers[0].env[2].value\
,SERVER:'spec.template.spec.nodeSelector.kubernetes\.io/hostname'\
,RUNNING:status.availableReplicas

I can only assume that one of the columns in format is missing from your setup for some reason - its not a great errror!


Staging_build_linux framework_tests_misc failing at tip of tree

Marked flakey but failing
https://github.com/flutter/flutter/blob/master/.ci.yaml#L2469
Has not had a passing test in over a year.
https://ci.chromium.org/p/flutter/builders/staging/Staging_build_linux framework_tests_misc?cursor=id>8814429255333607313&limit=200
Has never had a passing run
https://ci.chromium.org/ui/p/flutter/builders/staging/Staging_build_linux framework_tests_misc/2/overview
We should delete this code.

@reidbaker
good first contribution for this kinda issue is unusual so I'm guessing it was added by mistake.

@yusuf-goog Shall we remove these targets?

It was intentional since the only task is to delete the code. I figured it would be pretty easy.

@MahmoudZayad we do not need this build anymore, and it is a good candidate for fully removing the entire  "Staging_build_linux framework_tests_misc" target.

Pr approved waiting on green tree and google testing passing.


chore(pubspec): 🚚 use correct repository URL

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1158

Relevant Lines:
1158

💛  - Coveralls


Support for nativeSystemdSupport flag in config CR

Add a new flag to config CRD nativeSystemdSupport. This should be set to true on systems that has a native support for systemd (Openshift). If this flag is specified, we will skip setting up additional volume mounts to support systemd inside the container
Add watch for config CR and store the config info in the handler structure
structural changes and refactor to pass handler object.

Should cr-config-oc.yaml be cr-config-os.yaml ? ("os" for OpenShift)

OpenShift Container (for oc)
May be i should change to okd instead


peer to peer setting takes time. need to provide user feedback

Environment info

Version: 1.0.0-92796da
Deployment: AZURE
Customer: online sandbox

maybe have animated button like diagnostics download.
Actual behavior

http://noobaaonline.eastus.cloudapp.azure.com:8080/fe/systems/noobaaonline/management/advanced-options/p2p

Try to change. It takes about 20-30 seconds. no feedback for the user.
Expected behavior

feedback. It takes time until we show the green message that it's ok.

Steps to reproduce

URL: http://noobaaonline.eastus.cloudapp.azure.com:8080
Username<EMAIL_ADDRESS>Password: XlkJvFXz
Screenshots or Logs or other output that would be helpful
(If large, please upload as attachment)

No longer relevant due to OVA deployment support removal


Realm database is empty

Hello.
Thank you for your plugin. I am trying to use it. I see my database but the base is empty although I have a data (4 realm object classes and data in them)?

Faced the same issue.
Don't setup a custom name for the realm or custom folder solved this.

Thank you sir, removing line ".name("myrealm2.realm") solved my problem, but It's quite sad that we can't use custom realm database names. I.e. I need more than one db than it can become an issue.
new RealmConfiguration.Builder()
                .name("myrealm2.realm")
                .schemaVersion(2)
                .migration(DbUtils.migration)
                .build();

Yes, I deleted the name of the database, but it is not a good solution. Thank you!

Any plans on releasing this fix??

stetho-realm 2.0.1 is released.
edit build.gradle:
repositories {
    maven { url 'https://github.com/linchaolong/stetho-realm/raw/master/maven-repo' } // realm-stetho
}

dependencies {
    compile 'com.facebook.stetho:stetho:1.4.2'
    compile 'com.uphyca:stetho_realm:2.0.1'
}

I've released 2.1.0 that contains the fix.
I'll close this issue.


@val and @Delegate combined cause an error compiling with javac

Migrated from Google Code (issue 601)

Confirming this is still an issue.

Experiencing this issue in IntelliJ IDEA Ultimate 2018.2


Warning cleanup "The private field is assigned but its value is never used"

Identify and cleanup "The private field is assigned but its value is never used" warnings

There are some in the SpectatorView feature that was introduced in the may18_dev branch.

Found one more when building Standalone:


Static URLs should be wrapped in static() so they resolve correctly in production environments

For my production environment, I store my static files on S3 using the following in settings:
STATICFILES_STORAGE = 'storages.backends.s3boto.S3BotoStorage'
DEFAULT_FILE_STORAGE = 'storages.backends.s3boto.S3BotoStorage'
AWS_ACCESS_KEY_ID = 'XXXXXXXXXXXXXXXXXXX'
AWS_SECRET_ACCESS_KEY = 'YYYYYYYYYYYYYYYY'
AWS_QUERYSTRING_AUTH = False
AWS_STORAGE_BUCKET_NAME = 'myproject-static'
For this to work correctly, I had to add the following import:
from django.contrib.admin.templatetags.admin_static import static
And I needed to wrap each of the media files in a static() call like the following:
def _media(self):
    js_files = [static('django_extensions/js/jquery.bgiframe.js'),
                static('django_extensions/js/jquery.ajaxQueue.js'),
                static('django_extensions/js/jquery.autocomplete.js')]

    return forms.Media(css={'all': (static('django_extensions/css/jquery.autocomplete.css'),)},
                           js=js_files)

The code in question is here:
https://github.com/django-extensions/django-extensions/blob/b6951d39736fc1d13e667c3a11f52f5c1764767d/django_extensions/admin/widgets.py#L27

Thanks for the issue !
Could you please make a PR for this ?


[FEA] Add cuSpatial repo/package to all Docker images

This repo and corresponding conda package needs to be added to the appropriate Docker images:
https://github.com/rapidsai/cuspatial
https://anaconda.org/rapidsai-nightly/cuspatial
devel images will have the new repo added alongside the other repos in /rapids and will have it built and installed from sources (using standard build.sh)

NOTE: the current cuspatial build process requires that it be built after cudf, since it dependes on cudf headers and libs.

base will need cuspatial added to the conda install line (and therefore runtime will automatically have it included)

I have patch ready but not fully tested. Base images both build and ubuntu-devel also builds. Verifying centos7-devel image now. Patch is here:
https://github.com/rapidsai/build/pull/36/files

https://github.com/rapidsai/build/pull/36 has been merged.


Support for multiple configuration fragment loads for an application

This request was taken from #29  by @ahusic-clgx
I would very much like a support for multiple configuration fragment loads for an application. What I was thinking about was extending "Pivotal.Extensions.Configuration.ConfigServer.ConfigServerClientSettings" with new property called "Fragments":
public class ConfigServerClientSettings
{
public Collection Fragments{ get; } = new Collection();
}
and then use this collection of strings in "ConfigServerConfigurationProvider" class to load each fragment along side application configuration. It would be app's responsibility to provide fragments it needs (besides its own) to successfully work.
This way, I can load not only app configuration, but any other "shared fragment" application needs.
Thank you very much.

Feel free to provide a PR to address this.   If we understand your need, we believe the config server already provides this kind of functionality.


Update the two-time notebook to use matplotlib AxesGrid

Great!, Thanks @ericdill I will merge it, Just want to make the fig size little bit bigger once ready I will let you know


Please update winget msix package Desktop App Installer dependency version

Brief description of your issue
Please update winget msix package Desktop App Installer dependency version
At present, the Microsoft.UI.Xaml version used by the desktop installer of the msix package that winget depends on is 2.7, and the latest version of Microsoft.UI.Xaml is 2.8, and I hope to upgrade the Microsoft.UI.Xaml version to the latest version as soon as possible

Steps to reproduce
None
Expected behavior
hope to upgrade the Microsoft.UI.Xaml version to the latest version as soon as possible
Actual behavior
None
Environment
See screenshot.

Duplicate of #3380


Resiliency - Service Invocation allow to ignore resiliency policy based on response http status code

Describe the solution you'd like
Add doc for service Invocation allow to ignore resiliency policy based on response http status code.
Where should the new material be placed?

The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos

related dapr issue https://github.com/dapr/dapr/issues/6683
related dapr pr https://github.com/dapr/dapr/pull/7132
Additional context

/assign

code PR: dapr/dapr#8252


Blank screen, app not hooking into html

Following the Quick start instructions  at 1:49 pm PDT:
1.Clone this repo using $ git clone --depth=1 https://github.com/mxstbr/react-boilerplate.git
2. Run $ npm run setup to install dependencies and clean the git repo.
3. At this point you can run $ npm start to see the example app at http://localhost:3000.
Server starts as expected
localhost:3000 opens with a blank page
No errors in terminal or browser console
web page html shows empty app div

common.js.js and main.js both have substantial content, hundreds and thousands of lines respectively.
Have cleared browser cache, tried Chrome (51.0.2704.79) and firefox (43.0.4) and another machine on the private LAN. Same results on all.
All 65 tests pass.
OS X 10.11.5
Node 5.8.0
npm 3.8.2
Thanks for your attention.

I'm seeing this same issue.

+1 same issue

Same issue here. Tested on Chrome and Firefox on latest Ubuntu

Working on reproducing and fixing this asap, sorry for the troubles! Thanks for the detailed bug report @gihrig!

The problem is<EMAIL_ADDRESS>which is installed recently.
$ npm install --save-dev<EMAIL_ADDRESS>gets things working again.

Nice on @gihrig, fix is pushed up to master, I pinned the dependency! Thanks for the help! :tada:

Hey… I know i'm showing a little late, but i have the same issue here. Webpack is compiling but i have a "grey" screen… Yes my CSS styles are applied but no HTML is injected into my

.
Any idea ? I have no error in browser's console… Here is my webpack config :
const path = require('path');
const webpack = require('webpack');
let env = process.env.NODE_ENV ? process.env.NODE_ENV : 'dev';

module.exports = {
    context: path.join(__dirname, 'public', 'index.html'),
    entry: path.join(__dirname, 'src', 'App.jsx'),
    output: {
        publicPath: "/public/",
        path: __dirname + "/public/",
        filename: "bundle.js"
    },
    module: {
        loaders: [
            {
                test: /\.(js|jsx|es6)$/,
                loader: "babel-loader",
                exclude: "/node_modules",
                query: {
                    presets: ["es2015", "react", "stage-2"]
                }
            },
            {
                test: /\.scss$/,
                loaders: ["style-loader", "css-loader", "sass-loader"],
                exclude: "/node_modules"
            },
            {
                test: /\.css$/,
                loaders: ["style-loader", "css-loader"],
            },
            {
                test: /\.html$/,
                loader: 'file-loader?name=[name].[ext]'
            },
            {test: /\.woff(\?v=\d+\.\d+\.\d+)?$/, loader: "url-loader?limit=10000&mimetype=application/font-woff"},
            {test: /\.woff2(\?v=\d+\.\d+\.\d+)?$/, loader: "url-loader?limit=10000&mimetype=application/font-woff2"},
            {test: /\.ttf(\?v=\d+\.\d+\.\d+)?$/, loader: "url-loader?limit=10000&mimetype=application/octet-stream"},
            {test: /\.eot(\?v=\d+\.\d+\.\d+)?$/, loader: "file-loader"},
            {test: /\.svg(\?v=\d+\.\d+\.\d+)?$/, loader: "url-loader?limit=10000&mimetype=image/svg+xml"},
        ]
    },
    resolve: {
        extensions: ['.js', '.jsx'],
    },
};

@gop-aroy You likely have a JS error that is crashing the render of one of your components.
The best I can recommend is to retrace your steps since it was working. Hopefully you have made frequent git commits, so you can step back to a working configuration and compare to see what is breaking your app.

I didn't even think about this possibility considering i didn't change anything in my components (as far as i remember) and when i'm run react-scripts start i have no error :(

I know i look like a noob, and i surely am, but do you have anything you can think of for me to investigate on ?

Ok, it was because of my webpack configuration, but i won't be able to tell you where and why (maybe my vendors ?)… I used this awesome configuration sample : https://github.com/ModusCreateOrg/budgeting-sample-app-webpack2
and by updating some data (folders etc.) i have a result \o/
Thank you for your time.

Congrats on finding the bug 🎉

Same issue here. I tried to update webpack and other dependencies to the latest version

Did you try the sample I linked ?

@gop-aroy actually I solved. something to do with the redux data apparently

what to do with redux ?

I have the same problem when I upgrade Webpack from 1.x to 3.10.0.
No error messages, it's really hard to find out the problem, It's not a helloworld project...

Same here. The annoying thing is, I had it working fine, but now, nada, just the empty  plus css and script links.
Seriously, I spend more time chasing bugs and updating packages and modules than actually producing work some days!

I have the issue; my reactjs application is displaying empty container

That how it is.
please help.


Harbor using multiple /16 overlay networks

We have found that docker images in Harbor using multiple /16 overlay networks, which are having conflicts from Corporate networks.
Could you please share some insight on default algorithm, in meaning how it is assigning the bridge networks etc, what is the possibility of externalizing the RFC 1918 range as text field like PAS. So user can specify /decide which subnet range to use it instead of defaults.
Current LAB Status:
Our network we have what we call “Black-Hole or Non-Routed” address space that we have allocated for lab usage but with the stipulation that it will never I mean never be routed on the Corporate Network. As I have stated this was used when a lab needs a large chunk of address space for any kind of back end testing with the understanding that it would never be routed outside of that lab environment. We need to come up with best steps …
Ex: We have assigned infra as <IP_ADDRESS>/16
but if you look at the docker images, you see below.
"<IP_ADDRESS>/16"
"<IP_ADDRESS>/16"
"<IP_ADDRESS>/16"
"<IP_ADDRESS>/16"
"<IP_ADDRESS>/16"
"<IP_ADDRESS>/16"
Here is how to replicate from your end:

login to harbor
sudo -i
harbor-app/20f8e780-4563-44ca-b26d-2c7747f3357c:~# /var/vcap/packages/docker/bin/docker -H unix:///var/vcap/sys/run/docker/dockerd.sock network list
NETWORK ID NAME DRIVER SCOPE
059e69117bca bridge bridge local
6022a7999a6c harborapp_harbor bridge local
66038237192f harborapp_harbor-clair bridge local
5c5e6c6fdea0 harborapp_harbor-notary bridge local
6f7dd25eba5f harborapp_notary-mdb bridge local
7b0dc7433746 harborapp_notary-sig bridge local
a062b600f9a0 host host local
71b8952b60f6 none null local
/var/vcap/packages/docker/bin/docker -H unix:///var/vcap/sys/run/docker/dockerd.sock network inspect 7b0dc7433746

@deshab
To resolve the confliction, you can modify the docker-compose template files to assign subnets for networks that dockerd creates, for details please see:
https://docs.docker.com/compose/compose-file/#ipam

Closing due to inactivity.

We need to have solution, could you please provide why it using /16 subnets for each docker container?
Ex:

If I assigned HARBOR_INFRA to /16, and all docker containers hosted on this VM will be using /16 subnet.

If I assigned HARBOR_INFRA to /24, and all docker containers hosted on this VM will be using /24 subnet.

Do you know why it is required? Could you please provide design consideration around this?
-Bala

From: Daniel Jiang<EMAIL_ADDRESS>Sent: Monday, July 9, 2018 11:46 AM
To: vmware/harbor
Cc: Deshamouni, Balakrishna; Mention
Subject: Re: [vmware/harbor] Harbor using multiple /16 overlay networks (#5149)
Closing due to inactivity.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vmware/harbor/issues/5149#issuecomment-403525047, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJR2sgBg8cJ8jBhzu6duN-fl6TPLlIhGks5uE3qggaJpZM4Un472.

@deshab It's the behavior of docker-compose and dockerd that creates /16 network by default.
And you can modify that by updating the docker-compose template to assign different subnets for the networks created by dockerd while deploying Harbor.

We are using harbor tile, we would like to specify RFC 1918 same as PAS, in PAS we are able to specify selective subnet from RFC 1918 without conflicting IP’s as our environment configured behind NATing.
Question, it is creating approximately 8 docker container within Harbor VM, need a clarification on why each container need separate /16 or /24 as each container using only one IP.
We cannot modify manually as Harbor upgrades will not work.
From: Daniel Jiang<EMAIL_ADDRESS>Sent: Tuesday, July 10, 2018 2:47 AM
To: vmware/harbor
Cc: Deshamouni, Balakrishna; Mention
Subject: Re: [vmware/harbor] Harbor using multiple /16 overlay networks (#5149)
@deshabhttps://github.com/deshab It's the behavior of docker-compose and dockerd that creates /16 network by default.
And you can modify that by updating the docker-compose template to assign different subnets for the networks created by dockerd while deploying Harbor.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/vmware/harbor/issues/5149#issuecomment-403718489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJR2sswRpnHsRuLW2b89uxASsije8-IMks5uFE3xgaJpZM4Un472.

@deshab
As for the question regarding Harbor tile, could you contact the support of VMware?


percentile csv files are added by default

Percentile csv files are added by default even though --save-csv is not true. The check was not added previously.

Thanks @sohamm17 !


Azure OpenAI not working with Agents - Unknown parameter: 'tools[0].function.strict

Not sure if this is an Azure OpenAI issue or a simple configuration fix for agency-swarm. Here's my code:
client = AzureOpenAI(
api_key=settings.OPENAI_KEY,
api_version=settings.OPENAI_VERSION,
azure_endpoint=settings.OPENAI_ENDPOINT,
timeout=5,
max_retries=5,
)
set_openai_client(client)
ceo = Agent(
name="CEO",
description="Responsible for client communication, task planning and management.",
instructions="You must converse with other agents to ensure complete task execution.",  # can be a file like ./instructions.md
files_folder="./files",  # files to be uploaded to OpenAI
schemas_folder="./schemas",  # OpenAPI schemas to be converted into tools
temperature=0.5,  # temperature for the agent
max_prompt_tokens=25000,  # max tokens in conversation history
model=settings.OPENAI_MODEL_GPT_4o
)
dev = Dev(id=model=settings.OPENAI_MODEL_GPT_4o)
agency = Agency(
[ceo,
[ceo, dev]
]
)
agency.run_demo()
Error code: 400 - {'error': {'message': "Unknown parameter: 'tools[0].function.strict'.", 'type': 'invalid_request_error', 'param': 'tools[0].function.strict', 'code': 'unknown_parameter'}}

Yah even I’m facing same issue can anyone help to resolve it

@simoninnyc @vishnureddysai
Please provide more details:

Library versions: agency-swarm, openai
Model that you use.

Currently, Structured Outputs is only supported on the gpt-4o model, specifically version 2024-08-064. This is a crucial requirement, as older models or different versions do not have this capability.

Agency swarm version : 0.3.0
Open ai - 1.41.0 & even tried with latest version
Model version : gpt-4o - 2024-05-13 version

When I use 2024-08-06 version I’m getting this below error
this deployment is not compatible with assistant functionality

gpt-4o - 2024-05-13 version
Either update the model, or do not use strict: true in your tool schemas.
In your case @vishnureddysai, you might need to check your API version. And contact OpenAI support it case of issues.

I have tried both the ways still facing same issue but it’s the issue related to using tools

In order to install from the main branch:
pip install git+https://github.com/VRSEN/agency-swarm.git

I tried and tested that still getting same error

API Version:
Which API Version on Azure do you use in your settings?
AZURE_API_VERSION = "2024-05-01-preview"   # this is the actual version
https://learn.microsoft.com/en-us/azure/ai-services/openai/how-to/assistant
Model Deployment
Check, if the model gpt-4o is deployed in your Azure resource and region?
https://oai.azure.com/resource/deployments

I have used both 2024-05-01-preview & latest model version in the both cases I was facing the same issue
and also everything works if I don’t use any tools
Issue occurres while using the tools

I just saw that there is a newer API version, where strucutred outputs are supported:
2024-08-01-preview
https://learn.microsoft.com/en-us/azure/ai-services/openai/how-to/structured-outputs?tabs=python-secure

Hey guys, a push for this is already in main, I will make a release shortly. Install from main and test again please if you can

Thanks! This fixed the issue for me. Discovered a bug related to the Browsing Agent with Azure OpenAI but I'll create another ticket.


CamelCase class naming updated in usage.md

Liking readimc so far Jonas! Just noticed this when going through the quickstart docs. Good to keep them literal for someone like me ;)

Thanks Merrick! Updated a few more typos


Update multisig.xml to match upstream

https://github.com/ton-blockchain/multisig-contract-v2/blob/master/contracts/multisig.tlb#L47

sorry but i can't merge it now. in this case i need to clean or migrate all decoded messages in our database


Auto corrected by following Lint Ruby Style/SoleNestedConditional

Auto corrected by following Lint Ruby Style/SoleNestedConditional
Click here to configure it on awesomecode.io

Coverage increased (+0.05%) to 78.298% when pulling 56f91c3b59318dbfcc3f9e0c2dc766810c5d02c4 on awesomecode-lint-ruby-style-solenestedconditional-48370 into c23c99a44549228266d4ec8c77d1530e8967047c on master.


CLA•LaAzteca

Create
New
Links

Changes Unknown when pulling 88bfb294a72b3267f07755185059cdaa110d698f on AdminDevelopment:master into ** on dondyabla:master**.


Option to disable custom tabs browsing mode

I'd like to be able to disable embedded browsing mode from Kiwi Browser options.
i.e. force links from other apps to open in the full browser, e.g. from Instagram

Hello, any news on this ? Thanks

Any update on this issue?


[NFC] Fix clang 10 warnings

Resolves the following clang-10 compiler warnings:
$ ninja
[65/177] Building CXX object examples/CMakeFiles/oit.dir/oit/oit.cpp.o
../examples/oit/oit.cpp:501:7: warning: 'buildCommandBuffers' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
        void buildCommandBuffers()
             ^
../base/vulkanexamplebase.h:351:15: note: overridden virtual function is here
        virtual void buildCommandBuffers();
                     ^
1 warning generated.
[78/177] Building CXX object examples/CMakeFiles/inlineuniformblocks.dir/inlineuniformblocks/inlineuniformblocks.cpp.o
../examples/inlineuniformblocks/inlineuniformblocks.cpp:19:27: warning: implicit conversion from 'int' to 'float' changes value from<PHONE_NUMBER> to<PHONE_NUMBER> [-Wimplicit-int-float-conversion]
        return ((float)rand() / (RAND_MAX));
                              ~  ^~~~~~~~
/usr/include/stdlib.h:86:18: note: expanded from macro 'RAND_MAX'
                        ^~~~~~~~~~
1 warning generated.

[84/177] Building CXX object examples/CMakeFiles/pushconstants.dir/pushconstants/pushconstants.cpp.o
../examples/pushconstants/pushconstants.cpp:24:28: warning: implicit conversion from 'int' to 'float' changes value from<PHONE_NUMBER> to<PHONE_NUMBER> [-Wimplicit-int-float-conversion]
        return ((float) rand() / (RAND_MAX));
                               ~  ^~~~~~~~
/usr/include/stdlib.h:86:18: note: expanded from macro 'RAND_MAX'
                        ^~~~~~~~~~

There's one more warning, but I don't know if the switch the switch is fine or not:
[82/177] Building CXX object examples/CMakeFiles/textoverlay.dir/textoverlay/textoverlay.cpp.o
../examples/textoverlay/textoverlay.cpp:509:11: warning: enumeration value 'alignLeft' not handled in switch [-Wswitch]
                switch (align)
                        ^
1 warning generated.


New ReadMe with associated Images

@jinghaomiao changes made. Images stored in docs/demo_guide/images.


Display modifiers on score screen and Hundun win implies SC%

Fixes #126.

Fixed the SC% goofiness, which stemmed from the same underlying issue.

Awesome, thanks for fixing these!


improvement do not captute stack trace for txn error codes

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


WL2K-go as RMS Realy

Hi,
I have question that wl2k-go is possible use as rms relay ???

You could certainly build something like RMS Relay using the wl2k-go framework, but the wl2k client does not support these features.
A simple implementation could be done without much hassle I believe, using these three packages:

github.com/la5nta/wl2k-go/transport (to support winmor, ardop, telnet and ax25)
github.com/la5nta/wl2k-go/mailbox (for store-and-forward)
github.com/la5nta/wl2k-go/fbb (for the B2F-protocol)

It would be nice if anyone would take this challenge and build an open source RMS Relay clone :+1:

Thank you for information. I am asking about this because I have use BPQMail as RMS Relay but I have found one problem that during getting message from BPQMial via RMS Express BPQMial cut of subject to max 60 chars when we use RMS Express to send Radiogram IARU which have defined
SUBJECT which contain more than 60 chars information.

FYI, an email header should not exceed 78 characters according to RFC 2822, section 2.1.1. That leaves 69 characters for the actual subject, unless they support multi-line headers. Maybe this is the reason BPQMail trims the subject, I don't know.
I'm sorry that I can't be more helpful. I think you're proposal sounds like a very fun and useful sub-project, but until we get more contributors I believe my main priority must be to work on the client application and improving the framework.
I hope developers will see this project as a good framework for developing more open source Winlink tools. Hopefully we'll see server-side applications providing the features you're looking for :)


Support pickling of cdef classes.

Nice one.
I guess I would have used getattr() instead of hasattr(), but your version is probably shorter.
It feels like there should be a class decorator to disable this, though. There's always a reason why people would want back the old behaviour.
I also agree that we could try to support it for the "only no-args __cinit__()" case, but I'm not entirely sure if this plays nicely with subtyping. If a base class can be pickled, how would a subtype with a non-trivial __cinit__() know that it can't be?

We would produce an error-raising __reduce__ in the subclass if it had a non-trivial __cinit__.


Best Practice: Code organization

Hi @valyala,
thank you for the great project. What is your best practice organizing the files? Do you usually commit the templates and compiled templates in your projects or just the templates and compile e.g. during CI just before test/build?
Thanks for your advice.
Sven

The initial plan was to put template files in a dedicated folders and then just import them as go packages. For instance, let the following folder structure exists:
src/
   cmd/
       app1/   <- here is the main package for app1
       app2/   <- here is the main package for app2
    package1/ <- here is package1, which may be used by any app from cmd
    ....
    packageN/ <- here is packageN, which may be used by any app from cmd
    templates/ <- here is a package with templates (qtpl files)

Then all the templates must be placed inside templates folder. But this solution didn't work properly in practice, since sometimes templates are used only inside the given package and require internal struct and functions from this package. So now we resorted to mixing .qtpl files with the ordinary .go files in package folders. And this works great for our use cases :)

Do you usually commit the templates and compiled templates in your projects or just the templates and compile e.g. during CI just before test/build?

We usually commit compiled templates in our projects. This gives us two benefits:

Reproducible builds, since the build doesn't depend on qtc version.
There is no need to install qtc on build machines - plain go build is enough.


Excluding certain test cases

I have an API with marshmallow validation. The problem is that it break if string is .
Case
self = Case(endpoint=Endpoint(path='/reviews/{reviewId}/comments', method='POST', definition=EndpointDefinition(raw={'tags': ...), path_parameters={'reviewId': 1}, headers=None, cookies=None, query=None, body={'': None, '.': None}, form_data=None)
response = <Response [500]>

Error
# https://marshmallow.readthedocs.io/en/stable/_modules/marshmallow/utils.html see set_value
ValueError: Cannot set . in  due to existing value: None

How to disable generating . ?
Global hook snippet is not correct here https://github.com/kiwicom/schemathesis/pull/356/files
EDIT: based on a closed issue the solution is:
import os

import schemathesis

from conftest import get_root_url

schema = schemathesis.from_path(
    os.path.join(os.path.dirname(__file__), "api_spec.yaml"), get_root_url()
)

@schema.hooks.register("before_generate_body")
def schema_hook(context, strategy):
    return strategy.filter(lambda x: "." not in str(x))

@schema.parametrize()
def test_no_server_errors(case, flask_test_app, cookies):
    # `requests` will make an appropriate call under the hood
    response = case.call(cookies=cookies)
    # You could use built-in checks
    case.validate_response(response)
    # Or assert the response manually
    assert response.status_code < 500

It's a bit restrictive since filters all values with . not just they keys.

Hi @lukasz-madon,
Thank you for asking :) The general direction for such adjustments is to use hooks indeed!

Global hook snippet is not correct here https://github.com/kiwicom/schemathesis/pull/356/files

This PR you are referring to is outdated and the current README doesn't contain it - the hooks system was working that way at the time when that PR was merged (except for the typo in the function name). The most up-to-date documentation on hooks is here - https://schemathesis.readthedocs.io/en/stable/customization.html
Regarding your exact case, I think that it would be better to explicitly check all keys in that dictionary (or other structure, depending on your schema - e.g. an array). Something like this:
import schemathesis

@schemathesis.hooks.register
def before_generate_body(context, strategy):
    return strategy.filter(lambda x: "." not in x)

This should be sufficient for disabling . generation as a key of that dictionary.
Depending on your schema you could implement different kinds of filters there - that x could be of some other types so, keep it in mind. That example from the linked PR (that one with str(x)) is somehow misleading and I missed to provide some more verbose explanation on how filtering could be done. I'll update that section of our docs
Let me know if I can provide more info on this topic

Hopefully, it answers your question :) If not, then feel free to reopen this issue or create a new one. Or reach me on Gitter


contrib: CERN typo fix

Fixes a small typo in the fetch_groups method, which incorrectly retrieves
the CERN_HIDDEN_GROUPS instead of CERN_HIDDEN_GROUPS_RE.

Signed-off-by: Orestis Melkonian<EMAIL_ADDRESS>

@omelkonian do we have any simple test case?

@omelkonian can you bump minimal required version of invenio-db to 1.0.0b1?

@jirikuncar test_fetch_grous had the same typo, that's why it passed previously


Typealiases for RuleId and RuleSetId

Currently we pass a lot of Strings around which don't really convey what they actually include.
By introducing these typealiases for RuleId and RuleSetId it becomes a bit clearer what these types actually contain and mean imo.
I just went through some of the files where I found usages of the Id Strings and replaced them with the typealias, I probably missed some cases.

Also with Kotlin 1.3 coming up and inline classes being introduced, this change is made even better!


.gitallowed is scanned for secrets making ignoring specific secrets tedious...

if a file has a secret you can ignore the specific instance of it using a regular expression in the .gitallowed file
However as you want the exception to be as specific as possible - generally you do not want a generic regexp but a very specific one that will match the exact secret (to prevent any other secrets).
For example a README which contains an example of how to convert an rsa private key would have the line
        String s = "-----BEGIN RSA PRIVATE KEY-----\n"
And so as you do not want to genericall allow any RSA key to be added you would add a lie like the following to .gitallowed
        String s = "-----BEGIN RSA PRIVATE KEY-----\\n"
This is great and allows the secret to be ignored in the file, however there is an epic fail as now you can not commit as the .gitallowed file itslef is flagged as containing a match.
c:\workarea\myrepo >git commit -a -m "Add instructions for converting a key"
README.md:72:        String s = "-----BEGIN RSA PRIVATE KEY-----\n"

[ERROR] Matched one or more prohibited patterns

Possible mitigations:
- Mark false positives as allowed using: git config --add secrets.allowed ...
- Mark false positives as allowed by adding regular expressions to .gitallowed at repository's root directory
- List your configured patterns: git config --get-all secrets.patterns
- List your configured allowed patterns: git config --get-all secrets.allowed
- List your configured allowed patterns in .gitallowed at repository's root directory
- Use --no-verify if this is a one-time false positive

c:\workarea\myrepo >echo         String s = "-----BEGIN RSA PRIVATE KEY-----\\n"> .gitallowed

c:\workarea\myrepo >git add .gitallowed

c:\workarea\myrepo >git commit -a -m "Add instructions for converting a key"
.gitallowed:1:        String s = "-----BEGIN RSA PRIVATE KEY-----\\n"

[ERROR] Matched one or more prohibited patterns

Possible mitigations:
- Mark false positives as allowed using: git config --add secrets.allowed ...
- Mark false positives as allowed by adding regular expressions to .gitallowed at repository's root directory
- List your configured patterns: git config --get-all secrets.patterns
- List your configured allowed patterns: git config --get-all secrets.allowed
- List your configured allowed patterns in .gitallowed at repository's root directory
- Use --no-verify if this is a one-time false positive

as the .gitallowed file is expect to have things that would trigger secret warnings (otherwise it would not need to contain them to supress them) this file should be excluded from scanning.

Just ran into this as well.


How to not show a file or make a file hidden?

I want to hide a file so no one can see it on the Directory Lister's home directory? What should I do?

Take a look at the Hiding Files documentation.


Tests for each method on Init.prototype

I think we need some testing for each method, as I've already found and fixed some bugs in methods, that seem to have received less attention from Ben.
We've already got testing using Jest implemented thanks to @Stephn-R, but we'll need a test file for each method. Probably in a format like: __tests__/addClass.js etc.

@philplckthun , check out the PR #8 for the templates

Okay, nice. I guess it'll take some time to fill all these template files ^^

I will do my best to help out

We should consider integrating some kind of CI Hook like Travis to run the test suite with new PR's

Ok, the Travis hook is all set up. How do we split the work for the 70 (!) files effectively? The answer just can't be 70 issues and 70 PRs. lol

How would you like to go about it? It may be easier if I was given
contributor access
On Tue, Jun 9, 2015 at 11:46 AM Phil Plückthun<EMAIL_ADDRESS>wrote:

Ok, the Travis hook is all set up. How do we split the work for the 70 (!)
files effectively? The answer just can't be 70 issues and 70 PRs. lol
—
Reply to this email directly or view it on GitHub
https://github.com/philplckthun/sprint/issues/6#issuecomment-110408576.

my thought exactly. We should probably make a to do list, split it in half and go at it in two separate branches

added you as a contributor. I'm currently not home, but I can write up the to do lists and start later this night

@Stephn-R Okay, I thought about it, and maybe we should just comment here on what tests we're working on. This way we can just put in time, when we've got it, and it's easier to track.

Ok, have you begun yet? It may be also worthwhile to organize a Slack chat

Not yet, but I guess I'll try to start today

Personally I always wanted to test gitter https://gitter.im/


DynamoDB doesn't support ReturnValues for put, delete, and update item

This is an extension of issue https://github.com/spulec/moto/issues/1404
put_item and update_item ignores the ReturnValues argument and will always return the updated new item (behaves like ALL_NEW).
delete_item supports ALL_OLD but for any other value it return an item with no attributes where it should not be returning an item at all.
These actions should also be raising a ValidationException for invalid arguments passed to ReturnValues.
Here a notebook with an example of the current behaviour: https://nbviewer.jupyter.org/gist/Ben-Wu/7945add78b69c1e45b47d2450ae27d1d
(moto==1.3.6)

Addressed by PR #1938.

Closed with https://github.com/spulec/moto/pull/1938


version bump for SQL management nuget

Bump version of Nuget package containing classes for LTR.

Hi @hchungmsft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

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

TTYL, AZPRBOT;

@azuresdkci retest this please

@hchungmsft This is just a version change, were the actual changes pushed earlier?


Stuck in "Connecting" but already connected

Doing a firmware update of our peripheral from Android works fine. However on iOS the DFU process is stuck at a very early phase.
We are using Secure Buttonless DFU with our own control characteristic.
We first connect our device, then we hit a "Start DFU" button. On Android the lib now writes to the control characteristic which will reboot the device into the bootloader. On iOS basically nothing happens. We get one single log entry. The device stays connected and that's it.
dfuStateDidChange(): Connecting

I think the lib should not try to connect, because the peripheral is already connected. Using the debugger I can see, that things go wrong in DFUPeripheral.start().
        // Set the initial peripheral. It may be changed later (flashing App fw
        // after first flashing SD/BL).
        guard let peripheral = centralManager
            .retrievePeripherals(withIdentifiers: [targetIdentifier]).first else {
            delegate?.error(.bluetoothDisabled, didOccurWithMessage:
                "Could not obtain peripheral instance")
            return
        }
        self.peripheral = peripheral

        if peripheral.state != .connected {
            connect()   // <<<<<<<<<<<<<<<<< We end up here, but shouldn't
        } else {
            let name = peripheral.name ?? "Unknown device"
            //....
        }

For some reason peripheral.state == .connected while still in our code. But if we enter library code the peripheral which is received by centralManager.retrievePeripherals is not connected but still has the correct name, so it seems to be the correct peripheral.
Does anyone here has some insights on that behavior?
DFU Bootloader version

SDK version: SDK 15.3
Bonding used: no
Library version: 4.9.0

Device information

Device: iPad 7th gen
OS: iOS 14.3

We've now switched from SwiftPackageManager to CocoaPods so that we could add some logging.
As it turns out we're ending up here: https://github.com/NordicSemiconductor/IOS-Pods-DFU-Library/blob/d4a1da27fbf195b325cea3036235a4939a8f4efa/iOSDFULibrary/Classes/Implementation/GenericDFU/DFUPeripheral.swift#L370
The strange thing is, that all those logger calls do not log anything for us which is odd, because we do implement the LoggerDelegate protocol.
Anyways there are different issue and I'll open different tickets if needed.


Support prefer_literal option for intrinsic decorator

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

Hi,
I noticed that prefer_literal option that was added recently for overload decorators is not supported for intrinsic.
It seems that make_intrinsic_template does not have prefer_literal argument (unlike for example make_overload_template) and moreover objects of _Intrinsic class do not store any options at all. At the same time intrinsic templates are created from base FunctionTemplate, which has prefer_literal hardcoded to False:
https://github.com/numba/numba/blob/4f985a5d90c4202c5f77bbd05fcff894200752de/numba/core/typing/templates.py#L261
This results in multiple calls to get_call_type with non-literal arguments during type-inference and may cause subtle issues if intrinsic code does not have correct input type checks. For instance the output of the following script
import numba
from numba import types
from numba.extending import overload, intrinsic
from numba.core.typing.templates import signature
import numpy as np

@intrinsic
# @intrinsic(prefer_literal=True)
def tuple_take(typingctx, data, idxs):

    print("DEBUG: tuple_take: data", data)
    print("DEBUG: tuple_take: idxs", idxs)
    if not isinstance(data, types.Tuple):
        return None
    if not (isinstance(idxs, types.Tuple)
            and all(isinstance(x, types.IntegerLiteral) for x in idxs)):
        return None

    old_ncols = len(data)
    unlit_keep_idxs = [a.literal_value for a in idxs]
    keep_col_idxs, new_typs = zip(*((i, t) for i, t in enumerate(data) if i in unlit_keep_idxs))
    def codegen(context, builder, signature, args):
        old_data = args[0]
        new_data = [
            builder.extract_value(
                old_data,
                types.intp(i)
            ) for i in range(old_ncols) if i in keep_col_idxs
        ]

        res = context.make_tuple(builder, ret_typ, new_data)
        return res

    ret_typ = types.Tuple(new_typs)
    sig = signature(ret_typ, data, idxs)
    return sig, codegen

def foo(data, idxs):
    pass

@overload(foo, prefer_literal=True)
def foo_ovld(data, idxs):
    print(f"DEBUG: foo: data={data}")
    print(f"DEBUG: foo: idxs={idxs}")

    def foo_impl(data, idxs):
        return tuple_take(data, idxs)
    return foo_impl

@numba.njit
def test_func():
    data = ('a', [2, 3], np.nan, 600)
    keep_idxs = (1, 3)
    return foo(data, keep_idxs)

res = test_func()
print(f"DEBUG: res={res}")

shows that we entered tuple_take code twice with non-literal arguments

DEBUG: foo: data=Tuple(Literalstr, list(int64)<iv=[2, 3]>, float64, Literalint)
DEBUG: foo: idxs=Tuple(Literalint, Literalint)
DEBUG: tuple_take: data Tuple(unicode_type, list(int64)<iv=None>, float64, int64)
DEBUG: tuple_take: idxs UniTuple(int64 x 2)
DEBUG: tuple_take: data Tuple(Literalstr, list(int64)<iv=[2, 3]>, float64, Literalint)
DEBUG: tuple_take: idxs Tuple(Literalint, Literalint)
DEBUG: tuple_take: data Tuple(unicode_type, list(int64)<iv=None>, float64, int64)
DEBUG: tuple_take: idxs UniTuple(int64 x 2)
DEBUG: res=([2, 3], 600)

and in the ideal case it can be this way:

DEBUG: foo: data=Tuple(Literalstr, list(int64)<iv=[2, 3]>, float64, Literalint)
DEBUG: foo: idxs=Tuple(Literalint, Literalint)
DEBUG: tuple_take: data Tuple(Literalstr, list(int64)<iv=[2, 3]>, float64, Literalint)
DEBUG: tuple_take: idxs Tuple(Literalint, Literalint)
DEBUG: res=([2, 3], 600)

Can this be changed in the future and prefer_literal added to intrinsic too?
BR,
Alexey.

The requested changes makes sense and it should be very easy to accomplish.

Tips for implementation:

Plumbing needed to set prefer_literal at https://github.com/numba/numba/blob/4f985a5d90c4202c5f77bbd05fcff894200752de/numba/core/typing/templates.py#L878-L879 from @intrinsic(prefer_literal=True)
other changes needed at https://github.com/numba/numba/blob/4f985a5d90c4202c5f77bbd05fcff894200752de/numba/core/extending.py#L280-L282, and https://github.com/numba/numba/blob/4f985a5d90c4202c5f77bbd05fcff894200752de/numba/core/extending.py#L308
a test can be created from the reproducer code in this issue.

I would love to contribute back to numba, can I work on this one? @sklam

I would love to contribute back to numba, can I work on this one? @sklam

@ashutoshvarma thank you for asking about this. I see you have already started, that's the spirit! Good luck with the implementation!

@ashutoshvarma thank you for asking about this. I see you have already started, that's the spirit! Good luck with the implementation!

Thanks for your reply! @esc
@kozlov-alexey Its not related to this issue but I kept getting MemoryError while running your code snippet on latest numba.
❯ python _test.py
DEBUG: foo: data=Tuple(Literal[str](a), list(int64)<iv=[2, 3]>, float64, Literal[int](600))
DEBUG: foo: idxs=Tuple(Literal[int](1), Literal[int](3))
DEBUG: tuple_take: data Tuple(unicode_type, list(int64)<iv=None>, float64, int64)
DEBUG: tuple_take: idxs UniTuple(int64 x 2)
DEBUG: tuple_take: data Tuple(Literal[str](a), list(int64)<iv=[2, 3]>, float64, Literal[int](600))
DEBUG: tuple_take: idxs Tuple(Literal[int](1), Literal[int](3))
DEBUG: tuple_take: data Tuple(unicode_type, list(int64)<iv=None>, float64, int64)
DEBUG: tuple_take: idxs UniTuple(int64 x 2)
MemoryError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "_test.py", line 56, in <module>
    res = test_func()
SystemError: CPUDispatcher(<function test_func at 0x7f1760a6d8b0>) returned a result with an error set

Replacing list [2,3] in data variable with tuple (2,3) seems to fix this.

Thanks for your reply! @esc
@kozlov-alexey Its not related to this issue but I kept getting MemoryError while running your code snippet on latest numba.
❯ python _test.py
DEBUG: foo: data=Tuple(Literal[str](a), list(int64)<iv=[2, 3]>, float64, Literal[int](600))
DEBUG: foo: idxs=Tuple(Literal[int](1), Literal[int](3))
DEBUG: tuple_take: data Tuple(unicode_type, list(int64)<iv=None>, float64, int64)
DEBUG: tuple_take: idxs UniTuple(int64 x 2)
DEBUG: tuple_take: data Tuple(Literal[str](a), list(int64)<iv=[2, 3]>, float64, Literal[int](600))
DEBUG: tuple_take: idxs Tuple(Literal[int](1), Literal[int](3))
DEBUG: tuple_take: data Tuple(unicode_type, list(int64)<iv=None>, float64, int64)
DEBUG: tuple_take: idxs UniTuple(int64 x 2)
MemoryError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "_test.py", line 56, in <module>
    res = test_func()
SystemError: CPUDispatcher(<function test_func at 0x7f1760a6d8b0>) returned a result with an error set

Replacing list [2,3] in data variable with tuple (2,3) seems to fix this.

Thanks for your reply! @esc
@kozlov-alexey Its not related to this issue but I kept getting MemoryError while running your code snippet on latest numba.

Example is segfaulting, probably need to incref the list:
    def codegen(context, builder, signature, args):
        old_data = args[0]
        new_data = [
            builder.extract_value(
                old_data,
                types.intp(i)
            ) for i in range(old_ncols) if i in keep_col_idxs
        ]
        context.nrt.incref(builder, new_typs[0], new_data[0])

        res = context.make_tuple(builder, ret_typ, new_data)
        return res

Thanks for your reply! @esc
@kozlov-alexey Its not related to this issue but I kept getting MemoryError while running your code snippet on latest numba.

Example is segfaulting, probably need to incref the list:
    def codegen(context, builder, signature, args):
        old_data = args[0]
        new_data = [
            builder.extract_value(
                old_data,
                types.intp(i)
            ) for i in range(old_ncols) if i in keep_col_idxs
        ]
        context.nrt.incref(builder, new_typs[0], new_data[0])

        res = context.make_tuple(builder, ret_typ, new_data)
        return res


Research mouse-locking options on Linux

Follow-up to #360 which upgraded DS to use LWJGL3 on the backend. As noted by @BenjaminAmos in that PR "Mouse locking has been disabled on Linux, as it does not appear to work anymore (the mouse co-ordinates returned are incorrect when the cursor is locked, so the mouse cursor is never visible when locked)."
See SolInputManager.java for the related code. Probably this is a subject that can be researched decently online for an available alternative. Alternatively if we don't need it / can find a whole other approach then suggestions are welcomed!
May also want to look through older closed issues or PRs that may have touched the area in the past.

First interesting idea on SO I found uses java.awt for this:

you can query the actual mouse position with https://docs.oracle.com/javase/8/docs/api/java/awt/PointerInfo.html#getLocation--
you can reset the mouse to the center with https://docs.oracle.com/javase/7/docs/api/java/awt/Robot.html#mouseMove(int, int)
I'll try it out when I have some time


Automated cherry pick of #8817: fix: add error cause

Cherry pick of #8817 on release/3.4.
#8817: fix: add error cause

/lgtm

/approve


[ASUSWRT] sensor - wrong interface name

Home Assistant release with the issue:
0.83.3
Last working Home Assistant release (if known):
Null
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
https://www.home-assistant.io/components/sensor.asuswrt/
Description of problem:
Aioasuswrt uses the following commands to determine upload/download speed:
ifconfig eth0 |grep bytes
cat /sys/class/net/eth0/statistics/rx_bytes
cat /sys/class/net/eth0/statistics/tx_bytes
There is also the following for loop which looks for the interface name 'eth0':
        for line in data:
            if 'eth0' in line:
                rx = data[i+3].split(' ')[4]
                tx = data[i+5].split(' ')[4]
                break
            i += 1
        return int(rx), int(tx)

The problem is that this code only works if the main interface on the router is named 'eth0'.  The code fails if, for example, a bridged connection is in use, which is often named 'br0'.
The code could be amended so that it checks for either 'br0' or 'eth0'.  Alternatively, Home Assistant could specify the interface name via the configuration.yaml file.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
asuswrt:
  host: <IP_ADDRESS>
  username: !secret router_username
  password: !secret router_password

Traceback (if applicable):
Null
Additional information:
Null

This is the issue tracker and according to your description it's a feature request for support different interface names. Please use the forum for feature requests as stated in the PR template. Thanks


Support travis pro

This changes allows travis-pro users to use this tool to upload data to coveralls.
Travis-pro users have to specify the 'service-name' keyword for coveralls to link to the correct commits.

Thanks!


Change git diff-files to git diff in check mod tidy

What does this PR do?
Change git diff-files to git-diff. Since git diff-files has a strange behaviour sometimes.
For example here it showed that there are changes in a binary file even if there are no changes in the content or the mode:
go mod tidy && git diff-files --compact-summary  go.mod go.sum
pkg/serializer/go.sum | Bin 82719 -> 82719 bytes
1 file changed, 0 insertions(+), 0 deletions(-)

go mod tidy && git diff-files --exit-code go.mod go.sum
:100644 100644 2aa64ac827c79df812ae5adcf0bf72b932728e52<PHONE_NUMBER>000000000000000000000000000000 M	pkg/serializer/go.sum

Here we see that diff-files output zero out go.sum<PHONE_NUMBER>000000000000000000000000000000 ❓

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


SAK-40474 Add Unit Tests and Utility Code for LTI 1.3

This is the first of many code bits - this is new LTI 1.3 code and tests for that code.  It is low-risk.

I feel like the codacy issues, while minor and mostly in the tests, are still issues. Otherwise looks good and thanks for the tests!


Unable to send data to cloud

After updating Home Assistant to 2022.12.1 data is no longer sent to the cloud.
The logs say:

Error resending request to cloud: <InvalidURL /gateway/put>

Hi, I am still unable to send sensor updates to the cloud under Home Assistant Core version 2022.12.x as the python dependency is throwing an error about the invalid URL.
Is there a way to fix this?

I have this same error now that I updated to 2023.3.1. Data arrives to HA just fine but will no longer appear in the cloud.
Could it potentially be an issue on the API side? Meaning that www.data199.com/api/ would be blocking access after receiving some erreous data?
https://mobile-alerts.eu/info/public_server_api_documentation.pdf

API Rate Limits
Rate limiting is considered on a per sensor basis. Allowed are up to 3 calls for a sensor within one minute. If more than 3 calls are made within one minute further calls are blocked for 7 minutes. If rate limiting is applied the server returns the HTTP response code “429 Too Many Requests”.

Invalid call blocking
To prevent misuse, if more than 5 calls with invalid parameters are made from the same ip address within 15 minutes, further calls from the same ip address within the 15 minute time window will be blocked. If invalid call blocking is applied the server returns the HTTP response code “403 Forbidden”.

I've just created a new release, check it out, please.

Perfect timing :) Just updated, and looking at the logs after reboot there is no error. Let's hope this is now resolved. Thank you!


User Error Definition is not defining what a User Error is

User Error - The number of requests not processed because of user errors over a specified period.
Ok - the first rule of a definition is to NOT use the same word in the definition.
R

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f9dc38fd-a706-d840-f933-18df696ad18d
Version Independent ID: d294b1b3-c62e-02ce-8d40-5f0e72c12ccd
Content: Monitoring Azure Service Bus data reference - Azure Service Bus
Content Source: articles/service-bus-messaging/monitor-service-bus-reference.md
Service: service-bus-messaging
GitHub Login: @spelluru
Microsoft Alias: spelluru

@RichardReukemaOptimus The document talks about the metrics so how does the metric is calculating its description calls out. In case if you want to know more on what the user error means that we already have the document for Azure service bus exception and it specifically talks about what type of exception comes under the user exception.
Further I will review this with the team and will update the document as necessary.

I'm not sure how to respond to your statement, but the link the exceptions is appreciated.  All I can tell you is this, I needed to know the definition of what a User Error is, and the article does not provide that, nor does it have this link.  To me, that indicates that the documentation is not complete or answering a question a user like me is trying to answer.  That said, the definition of User Error is totally in adequate from my 40+ years of creating documentation.
Regards,
Richard
From: MayankBargali-MSFT @.>
Sent: Tuesday, May 9, 2023 2:15 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Richard Reukema @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] User Error Definition is not defining what a User Error is (Issue #109151)
@RichardReukemaOptimushttps://github.com/RichardReukemaOptimus The document talks about the metrics so how does the metric is calculating its description calls out. In case if you want to know more on what the user error means that we already have the document for Azure service bus exceptionhttps://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-exceptions and it specifically talks about what type of exception comes under the user exception.
Further I will review this with the team and will update the document as necessary.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/109151#issuecomment-1539438940, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMATTOVYWM7P73WZACZKGS3XFIDJXANCNFSM6AAAAAAXXIHC7U.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@RichardReukemaOptimus Thanks for the feedback. Post internal discussion we will be pointing to the document for user and server errors for more clarification what does those errors mean. We appreciate the feedback.


Update trigger parameters

Adds 2 new parameters to the trigger:
queueManager: <queue-manager> # REQUIRED - Queue Manager

tlsDisabled: <TLS> # REQUIRED - Set 'true' to disable TLS.

 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.


Respect ExcludeFromCodeCoverage attribute

As with other testing frameworks, exclude any class or structure marked with ExcludeFromCodeCoverage from analysis.

Seems like a good idea, I will try to add that in the next couple of days.

We now support this attribute (with release 1.1.0).  So we will not mutate code in classes, methods or properties that have this attribute.


localhost entries incorrectly rewritten to <IP_ADDRESS>

It looks like the filter that converts all IPs to the chosen target (e.g. the default <IP_ADDRESS>) is a bit too greedy.  The valid localhost entries along with the broadcashost from the someonewhocares.org hosts file are incorrectly converted to <IP_ADDRESS>.
Original file snippet:
#<localhost>
<IP_ADDRESS>       localhost
<IP_ADDRESS>       localhost.localdomain
<IP_ADDRESS> broadcasthost
::1             localhost
<IP_ADDRESS>       local
#fe80::1%lo0    localhost
#</localhost>

Resulting hosts file:
#<localhost>
<IP_ADDRESS> localhost.localdomain
<IP_ADDRESS> broadcasthost
<IP_ADDRESS> local
#fe80::1%lo0    localhost
#</localhost>

@lucianf do you know of any issue that actually.arises from this?

Of course it's an issue.

localhost.localdomain is required if you have programs expecting to connect to a FQDN.  localhost.localdomain is a FQDN and can help avoid timeouts in certain applications (the very reason why this concept was introduced in the first place).  Certainly localhost.localdomain must resolve to <IP_ADDRESS> and not <IP_ADDRESS>.  Also see this.
broadcasthost is useful for addressing all machines on the network.  See this.

That being said, I think it would be a safe approach to not change anything the OS comes default with.  For example I couldn't find references on what "local" is used for (it may be something Windows-related) but the mere fact that this is part of the default hosts file should mean there was a valid reason to keep it there in the first place.

OK, you've convinced me.


Handle Unauthorized Access on /blogs Page

Description:
When receiving an unauthorized response on the /blogs page, the application should display an error notification indicating "Unauthorized" and redirect the user to the sign-in page.
Suggested Implementation:
Show an error notification when the response is unauthorized.
Automatically redirect users to the sign-in page after the notification is displayed.
Hey @AkshitLakhera  Please assign this issue to me under hactoberfest2024 and gssoc-ext tags

Description of Changes:
Error Notification: Implemented an error notification that displays "Unauthorized" when an unauthorized response is received on the /blogs page.
Automatic Redirection: Configured the application to automatically redirect users to the sign-in page after the notification is displayed, enhancing user experience and security.
Code Modifications:
Updated the useBlogs hook to handle unauthorized responses.
Integrated a custom notification component for better user feedback.
How the Issue Was Resolved:
Detected Unauthorized Responses: Added error handling in the API call to catch 401 errors.
Displayed Notification: Created a custom notification to inform users about the unauthorized access.
Redirect Logic: Implemented a redirection to the sign-in page after showing the notification
Thank you for the opportunity to contribute to this project.

Hey @AkshitLakhera ,
I've come across an issue on the /blogs page where unauthorized responses are not properly handled. I propose the following implementation to resolve this:
Description: When receiving an unauthorized response on the /blogs page, the application should display an error notification indicating "Unauthorized" and redirect the user to the sign-in page.
Suggested Implementation:
Show an error notification when the response is unauthorized.
Automatically redirect users to the sign-in page after the notification is displayed.
I believe this will enhance the user experience by providing clear feedback and ensuring they are directed to the appropriate sign-in page.
Please assign this task to me so I can begin working on it.


Failed to start with Missing X server or $DISPLAY error

What I am trying to do is to display the test GUI on my host machine, following the post here
Here are docker files.
version: "3.8"
networks:
  default:
services:
  client:
    depends_on:
      - backend
    build:
      context: ./client
    container_name: client
    volumes:
      - ./client:/app
      - ./client/node_modules:/app/node_modules
    ports:
      - "3000:3000"
    restart: always
    env_file:
      - ./client/.env
    networks:
      - default
  backend:
    build:
      context: ./backend
      target: development
    container_name:backend
    volumes:
      - ./backend:/app
      - ./backend/node_modules:/app/node_modules
    ports:
      - "3001:3001"
    restart: always
    env_file:
      - ./backend/.env
    networks:
      - default
  e2e:
    image: cypress
    build: ./e2e
    container_name: cypress
    depends_on:
      - client
      - backend
    environment:
      - CYPRESS_BASE_URL=http://client:3000
      - DISPLAY
    volumes:
      - /tmp/.X11-unix:/tmp/.X11-unix
      - ./e2e/cypress:/app/cypress
      - ./e2e/cypress.config.js:/app/cypress.config.js
    networks:
      - default

FROM cypress/included:10.8.0
WORKDIR /app
# dependencies will be installed only if the package files change
COPY package*.json ./
RUN npm ci
ENTRYPOINT [ "npx", "cypress", "open", "--project", "." ]

Folder structure:
.
├── README.md
├── docker-compose.yaml
├── e2e
├── backend
├── client

When I try to run with an environment variable $DISPLAY, it shows the error below.
IP = 'xxxx'
DISPLAY=$IP:0 docker compose up

If I run without injecting the DISPLAY variable, it does run but not in watch mode, seems it was running as cypress run instead of cypress open.

How can I solve this issue?

@convers39
This is quite an old post, however it may still be relevant. Could you please let us know if the problem is still open for you or if you resolved it in the meantime? Please also state what your Docker host system is running.
The image cypress/included:10.8.0
docker run -it --rm --entrypoint bash cypress/included:10.8.0 -c "node -v"

shows Node.js v16.14.2 which is no longer supported, so this would need to be retested under a current cypress/included version.

Closing.
We can re-open if there is new information available.


SAK-29145 Don’t allow some tools to be re-named.

The config poh.uneditables is a comma separated list of tools IDs that should be editable. By default it’s empty.

Does this PR need to be rebeased before merge?


Should not need Helm to install Helm Operator

I do not think it is a good prerequisite to make the user install helm, just to install the helm-operator. I understand the irony of that statement, but setup should be as simple as possible. Put simply, helm is completely unnecessary (not saying difficult to install or anything, just unnecessary).

Check out the docs https://docs.fluxcd.io/projects/helm-operator/en/stable/get-started/using-yamls/


B1

confirmed:B1
node:29297a14e524c48b

confirmed:B3

confirmed:B3

Form Submitted
Time: 21:05
Timezone: GMT+3


Update docs/samples/pipelines/

What this PR does / why we need it:
Because KFserving was updated to KServe, the model-app-ui does not display model with using current sample code.

@markwinter I think you contributed the the kserve pipeline component, can you help review this?

/ok-to-test

/retest

/retest

/ok-to-test

/ok-to-test

@yuzisun
I think because of force-push you might need to re-approve the tests?

Thanks @georgetree and @markwinter !
/lgtm
/approve


Add client statistics

Use this issue to track our initial effort to add Lustre client statistics to the exporter.

Todo:

[ ] Add singlestat metrics from clients
[ ] Expand *stats files to include missing metrics

I added a 'phase 3' here, FYI (rpcstats). No rush on it, just a reminder that we had a different potential user ask about it.


Updated Es

Can i get access to CrowdIn instead?

Apologies, missed the notification for this one.  The CrowdIn is publically accessible.


Add additional PlanBuilder::tableWrite API to simplify usage

Refactor PlanBuilder::tableWrite so that PlanBuilder provides a simple
API to use.
Move the customized table write node creation code out of PlanBuilder
to TableWriteTest.

I haven't refactor the tableWrite with aggregationNode and tableHandle
Because it's used by TableWriteTest utility function, which means I have to create a PlanBuilder::tableWrite with 12 parameters to meet the requirement of usage.
So I briefly walk through the tests in TableWriteTest, they're heavily tangled. The only way I can think of right now is to optimize each test in TableWriteTest.

For next step, I can either create a function with 12 parameters or start optimizing TableWriteTest in background to unblock.

I briefly walk through the tests in TableWriteTest, they're heavily tangled and needs to be decoupled.

This seems a problem on its own. We should not have tests that are "heavily tangled". Consider cleaning these up first.

@kewang1024 LGTM. Thanks for the simplification. So table writer test uses its own API to customize the table write node?

@xiaoxmeng My understanding is that this is a temporary state and a follow-up will refactor the test to use PlanBuilder's API. Ke, please, confirm.


fix futures example to work with current nightly (2019-08-18)

Update the futures example to work with current nightlies (tested with 2019-08-18). I also added the futures example to the examples workspace.

Thanks!


response flag URX on requests with postpone_requests

Describe the bug / error
I've created a wasm plugin based on postpone_requests.
I can get the wasm filter to intermittently and also consistently fail with response_flags URX.
If I delete the wasm plugin requests will return to 200 responses as expected.
The simplest way to reproduce is to scale the service to 0 and back up.
maybe related to #368
curl -sSL -w '%{time_total} %{http_code}\n' -o /dev/null 'localhost/productpage?[1-10]'
0.030480 503
0.024163 503
0.042674 503
0.046643 503
0.061877 503
0.034901 503
0.054737 503
0.073135 503
0.072683 503
0.058561 503

 curl -Lv http://localhost/productpage
*   Trying <IP_ADDRESS>:80...
* Connected to localhost (<IP_ADDRESS>) port 80 (#0)
> GET /productpage HTTP/1.1
> Host: localhost
> User-Agent: curl/7.85.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 503 Service Unavailable
< date: Mon, 27 Mar 2023 21:41:09 GMT
< server: istio-envoy
< content-length: 0
< x-envoy-upstream-service-time: 58
<
* Connection #0 to host localhost left intact

example bad response with wasm trace.
https://gist.githubusercontent.com/ajohnstone/5671b422f0d66a72c9f94fe37d86e70b/raw/e73c8a567fc8e903677ee0f0c39687bb5a8662a8/bad.log
What is your Envoy/Istio version?
1.16.1
What is the SDK version?
v0.21.0
What is your TinyGo version?
tinygo version 0.26.0 darwin/amd64 (using go version go1.19.5 and LLVM version 14.0.0)
URL or snippet of your code including Envoy configuration
Additional context (Optional)

I mean all subsequent requests once the underlying pods are back in a ready state, will continue to produce URX responses despite the pod being in a healthy state.
Only by removing the wasm plugin does the responses get restored to a 200 response code.
I’m unsure why URX would persist once restored?


phpExtensions.grpc: init at 1.45.0

Description of changes
Needed at work, the GRPC extension for talking with the Go service
Things done

Built on platform(s)

[X] x86_64-linux
[X] aarch64-linux
[X] x86_64-darwin
[X] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

@ofborg build php81.extensions.grpc php80.extensions.grpc php74.extensions.grpc


AlignConsecutiveMacros does not work

Hi,
I try to align consecutive C/C++ preprocessor macros but fail.
The error message is as follows, so aligning preprocessor macro is not available now?

YAML:17:25: error: unknown key 'AlignConsecutiveMacros'
AlignConsecutiveMacros: true
^~~~
Error reading d:\Code.clang-format: invalid argument

I experience the same problem using a bare clang-format, so it seems to be clang-format issue, not vscode-clang-format-provider
bash-3.2$ clang-format --version
clang-format version 9.0.0 (tags/google/stable/2019-05-14)
bash-3.2$ clang-format src/poisson.cu
YAML:13:25: error: unknown key 'AlignConsecutiveMacros'
AlignConsecutiveMacros: true
                        ^~~~
Error reading /.clang-format: Invalid argument

Updating your clang-formatter to latest version 9.0.0 should fix your problems. Here's a link to their download page.
@sin1231 @aborzunov

I wish it to be as easy as you say, @ab22
I have two versions of clang-format:

a standalone brew version. Installed with brew install clang-format
version supplied with llvm. Installed as a part of llvm with brew install llvm

> brew --prefix clang-format
/usr/local/opt/clang-format
> $(brew --prefix clang-format)/bin/clang-format --version
clang-format version 9.0.0 (tags/google/stable/2019-05-14)

> brew --prefix llvm
/usr/local/opt/llvm
> $(brew --prefix llvm)/bin/clang-format --version
clang-format version 9.0.0 (tags/RELEASE_900/final)

My .clang-format file is
BasedOnStyle: Mozilla
AlignConsecutiveMacros: true

I have expected result with llvm version of clang-format
> /usr/local/opt/llvm/bin/clang-format src/main.cpp
#include <iostream>

int
main(int argc, char* argv[])
{
  std::cout << "Hello World!" << std::endl;
  return 0;
}

But with standalone version i have an error:
> /usr/local/opt/clang-format/bin/clang-format src/main.cpp
YAML:7:25: error: unknown key 'AlignConsecutiveMacros'
AlignConsecutiveMacros: true
                        ^~~~
Error reading /Users/andreyborzunov/mountpoint/projects/factorizedpoisson/.clang-format: Invalid argument

Well.. I'm just guessing here so what I think is your standalone clang-format version 9.0.0 (tags/google/stable/2019-05-14) was built before the new AlignConsecutiveMacros option was added.
Checking the LLVM repo, the version 9.0.0 (tags/RELEASE_900/final) was created on Sept 19 and your standalone version says it's based on a May 14 tag, so that's probably it.
Hope this helps, @aborzunov.

This might be so.
Actually, i fixed my problem just by substitution of clang-format. Maybe waiting for update of clang-format could help @sin1231 too :)


feat: easier way to have custom endpoints

easier way to have custom endpoints that also use ent data types (e.g. /settings/<id> -> /settings if there is only one)

Singular() annotation?

Mostly resolved through existing exported functions + e1a33306617b7606121e5af513453335d6a182e9


Update ocean diagnostic requests

For the released configurations, we want to include new default diagnostic requests for the ocean which prevent unused variables being output. We also want to switch to saving one variable per output file to make model evaluation simpler. This will involve:

[ ] Decide on which variables to keep, hopefully with community input (see forum post).
[ ] Use the make_diag_table.py script used by OM2 to produce a diag table for the updated outputs, with one variable being saved per file.

Closing this as updates and discussion were moved to #53 and #54.


Add posibility to create events with categories.

How to add categories:
attrs = {
:subject => @temp_travel_name,
:start => Time.now,
:categories => 'Blue Category'
}
@travel = calendar.create_item(attrs)

thanks


Remove Shelley specific transaction CLI tests from Jormungandr

Issue Number
#2020
Overview

5291da59337ec266e7e54262a15b41528c15fad7
Remove Shelley specific transaction CLI tests from Jormungandr

Comments
Currently TRANSMETA_CREATE_01 - Transaction with metadata via CLI fails now on Jormungandr. Jormungandr has it's own (smaller) subset of CLI tx tests (also API tx tests) so, I think, it makes sense to remove core-integration tx CLI tests (which become more and more Shelley specific) from Jormungandr suite.

bors merge

bors r+

bors r+

bors r+

bors r+

bors merge


Use implementation instead of compile

Support for gradle 3.+.
Use implementation instead of compile in build.gradle.

Thank you @ma96o
I have merged your changes 👍