Update how it works documentation

Update the How it Works Documentation with latest Proposal Metadata.
Acceptance Criteria :

[ ] Add Teams, Authors Definition in Document.
[ ] Total Required Amount in Document.
[ ] Committed Amount in Document.

@srossross In the how it works documentation,

committed metadata should be the amount proposal received.
total metadata should be the total amount proposal required.

We have to change values in proposal metadata need to update it.


ci(cloud): dependabot cannot access the aws credentials

next time these are rotated: add these variables as secrets to both actions and dependabot

https://github.com/zimeg/.DOTFILES/actions/runs/7538385055/job/20518823991


Handle oil directory listings

oil uses a custom scheme of oil:// for its directory-listing buffers.  This throws off vim-rooter because the none of these paths actually exists.
To get to the "real" path we drop the custom scheme from the filepath.
Closes #136.

@airblade works for me! Thanks as always for your support 😄

Thanks for letting me know!


[FEATURE] Perform Data Analytics on Output Generated JSON

Is your feature request related to a problem? Please describe.
Implement Analysis data based on the output JSON file to calculate i.e., Free space, Compression Ratio, comparing any two or more JSON file data to show difference
Describe the solution you'd like
Any kind of Dashboard view is sufficient enough which gives easy idea to perform firmware binary analysis.

Queries -

Free space of the firmware volume/FFS/Flash space is expected here ?

Yes (for Firmware Volume and FFS), So to be precise Free-space can be categorized as:

Free Space within uncompressed section
Free Space within compressed section  [Compressed section have GUID defined in PI Specification] --- this section needs to be differed because free space before compression v/s after compression would not be the same.

According to Specification, the free space can be under FV, FFS or Section. However, FFS would be part of FV only so that is kind of contributes to overall Free Space to FV

Compression ratio for each FV inside the FFS is expected here ?

Yes, it would be of data where amount of size data which is compressed and the GUID of compression algorithm

comparing 2 or more JSON files to show the difference between FVs, Free space, compression ratio, etc. ? What more is expected here ?

Comparison could be on parameters described below (4).

Firmware binary analysis should be on what parameters ?

That is up to implementation effort to bring possibilities for assessment, there can be any possibility for comparing number of sections, drivers, classifying available driver types, analyzing space consumption of space by type, etc...


PamBackend authentication fails with PAM_AUTH_ERR or PAM_SYSTEM_ERR

Internal Jira: CDPD-56693
What changes were proposed in this pull request?
Added to print the failure message and also disabled resetting the credentials.
How was this patch tested?
The patch was tested in a internal cluster which has Pam + kerberos enabled at that OS level
Pam file
cat /etc/pam.d/hue
#%PAM-1.0
auth required pam_krb5.so realm=ROOT.HWX.SITE keytab=FILE:/etc/pam.keytab
password required pam_deny.so
account required pam_permit.so  -------->   this is needed as an additional check for the user's account status was implemented by calling the function pam_acct_mgmt is by default in python-pam module. If the response indicates that the user is not allowed access to the system, authentication might fail with one of the following errors:
PAM_AUTH_ERR
PAM_SYSTEM_ERR
The call to pam_acct_mgmt fails when the authentication configuration on the system is denying the user access to the system.

@quadoss Where the the error message will go? The rungunicornserver.log?

Yes, the message will go to the gunicorn log file.

What does the failure message look like? Does it go to stderr?
What does the resetcreds mean?

This is a pam auth mech where the pam module itself does a resetting of credentials to get a token which is not needed for Hue when doing the pam auth.

I have the same problem.


Due to login captcha on bitcointalk, autobump does not work anymore

until we find a way to bypass it, this repo won't achieve its goal :(

bitcointalk have option to disable captcha now.
can we run this?


File size by day and month

Hi
would it be possible to built an app with this library, that would calculate storage usage per Month and possibly per day for all the photos stored in the account?
something like 'du -sh *' in bash

Unfortunately the Google Photos API doesn't return file size, it only returns;

photo dimensions
video resolution, frames per second

So you would need to either;

download all the media items locally (or just to memory) and then store that information locally.
extrapolate/estimate the file size based on the meta data (very inaccurate)

Then finally iterate over them to calculate out the total bytes used and use Linq to group by month/day/hour/etc...

oh man, that's what I was afraid of (from looking over it)
I guess there is no way to do any stats on photos itself? Android and web client are quite lame :(


How does :LspInstall work ?

Invalid server name: bashls
Invalid server name: bash-language-server

This is not really and issue I'm just confused as to how should I install lsps with this plugin after installing it.

I fixed this. Try latest master branch.


Adding main method for LaunchDataIngestionJobCommand for spark-submit command

Description
Adding main method for LaunchDataIngestionJobCommand for spark-submit command
Got this exception when try to use class: org.apache.pinot.tools.admin.PinotAdministrator
22/02/08 13:51:20 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Exception in thread "main" java.lang.ExceptionInInitializerError
	at org.apache.pinot.tools.admin.command.StartKafkaCommand.<init>(StartKafkaCommand.java:51)
	at org.apache.pinot.tools.admin.PinotAdministrator.<clinit>(PinotAdministrator.java:98)
	at java.base/java.lang.Class.forName0(Native Method)
	at java.base/java.lang.Class.forName(Class.java:398)
	at org.apache.spark.util.Utils$.classForName(Utils.scala:238)
	at org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:806)
	at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:161)
	at org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:184)
	at org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:86)
	at org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scala:920)
	at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:929)
	at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
Caused by: java.util.NoSuchElementException
	at java.base/java.util.ServiceLoader$2.next(ServiceLoader.java:1308)
	at java.base/java.util.ServiceLoader$2.next(ServiceLoader.java:1296)
	at java.base/java.util.ServiceLoader$3.next(ServiceLoader.java:1394)
	at org.apache.pinot.tools.utils.KafkaStarterUtils.getKafkaConnectorPackageName(KafkaStarterUtils.java:54)
	at org.apache.pinot.tools.utils.KafkaStarterUtils.<clinit>(KafkaStarterUtils.java:46)
	... 12 more

Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)

[ ] Yes (Please label as backward-incompat, and complete the section below on Release Notes)

Does this PR fix a zero-downtime upgrade introduced earlier?

[ ] Yes (Please label this as backward-incompat, and complete the section below on Release Notes)

Does this PR otherwise need attention when creating release notes? Things to consider:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

[ ] Yes (Please label this PR as release-notes and complete the section on Release Notes)

Release Notes

Documentation

Codecov Report

Merging #8168 (1974bd0) into master (8bbf93a) will decrease coverage by 57.17%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master    #8168       +/-   ##
=============================================
- Coverage     71.39%   14.22%   -57.18%
+ Complexity     4303       81     -4222
=============================================
  Files          1624     1579       -45
  Lines         84198    82411     -1787
  Branches      12602    12431      -171
=============================================
- Hits          60116    11722    -48394
- Misses        19970    69809    +49839
+ Partials       4112      880     -3232

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
14.22% <ø> (+0.03%)
:arrow_up:

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

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


[ResourceIsolation] cpu isolation for normal workgroup

Introduction
Use the two-level global queue instead of the one-level driver queue, containing the work group queue as the first level, and the driver queue int a work group as the second level.
The mainly workflow of the workgroup and driver schedule is as follows:

The running driver yields, when it costs 100ms or pulls and pushes chunk 100 times.
Accumulate the virtual runtime to the workgroup of this yielded driver.
Select the driver in the workgroup, whose virtual runtime is the smallest.

Detail
Use DriverQueueWithWorkGroup instead of QuerySharedDriverQueue to schedule drivers running on the dispatcher threads.
DriverQueueWithWorkGroup contains two levels of queues. The first level is the work group queue, and the second level is the driver queue in a work group.

DriverQueueWithWorkGroup::take()

Firstly, select the work group with the minimum vruntime.
Secondly, select the proper driver from the driver queue of this work group.

DriverQueueWithWorkGroup::put_back()
When the driver's workgroup is not in the workgroup queue and the driver isn't from a dispatcher thread (that is, from the poller or new driver), the workgroup's vruntime is adjusted to workgroup_queue.min_vruntime-ideal_runtime/2, to avoid sloping too much time to this workgroup .

TODO
In this PR, a driver maybe runs at most 100ms regardless of its cpu limit weight, so the schedule latency is about 100ms.
In the future, We can provide a workgroup queue per dispatcher thread instead of a global workgroup queue to schedule more accurately.

run starrocks_fe_unittest

starrocks_be_unittest

run starrocks_be_unittest


Add support for TreatLife motion sensor

Proposed change
This adds support for the TreatLife motion sensor, which is basically rebranded Tuya TS0601.
The change just adds a new signature to the tuya.ts0601_motion.NeoMotion quirk and a test to verify signature matching.
The change has been tested on a local Home Assistant instance and verified to work with the sensor.
Additional information
Checklist

[x] The changes are tested and work correctly
[x] pre-commit checks pass / the code has been formatted using Black
[x] Tests have been added to verify that the new code works

Looks good! But any reason why I'm listed as the author of your commit? 😄
Can you change that or should I change it?

Sorry, I messed up the rebase. Should be fixed now.


Use Nuke for UriImageSource only (remove FileImageSource)

Proposal:
Xamarin.Forms.Nuke is an amazing library, and works awesome with UriImageSource, but has some problems with FileImageSource like seen on issues #11 and #9. If the resources are on the Resources folder and manage resolution using three images for each one (for example add_photo.png<EMAIL_ADDRESS>and add_photo@3x.png), on high density devices Images are blurred and Buttons with image shows the smallest image. On attached image you will see both issues: on left side loaded with Xamarin.Forms.Nuke and on right side with the library modified to use UriImageSource only.

Fixing this issues is not simple, based on ffimageloading code, and if finally most of the resources will be load using UIImage.FromBundle (as seen on #5), why don't be simple and use Nuke only for UriImageSource? It will work great on caching and managing url images, and resources will be managed as usual.
Also, Glidex works for UriImageSource only 👍

Yup.
But since it caches and handles way better file image than the default one (50% memory), I still want to support this case.
I won't support adding different density images in the Resources folder since it is a deprecated way to deal with images.
Starting with iOS 9, you should use Asset Catalogs Image Sets:
https://docs.microsoft.com/en-us/xamarin/ios/app-fundamentals/images-icons/displaying-an-image?tabs=macos
However I will add a configuration option to disable the handling of such source in the next version :)

Wow! A configuration option will be awesome! Thank you!
Meanwhile, I will investigate how to migrate into Asset Catalogs 😅

Ok I think I talked some nonsense here.
I am currently investigating this, and it seems that if you are using xcasset, you can't get around the native caching of images.
It means you can't get the URI of the image matching your density.
So in fact Nuke will never work with Asset catalog (I dunno why I assumed it would, silly me :).
But it might work with the deprecated way of doing it since I can add @2x, @3x automatically depending on the scale returned.
But anyway, I will add the option to disable it just in case.

Yup, Nuke will be able to cache images ONLY when using the good old fashion way x)
So your issue will be fixed: you don't have to move anything around.
Anyway, with the next fix, it should also work if your put images in the Asset Catalog, it will just use the native cache in this case.

Great! If you want I can test the fix on a huge App with lots of images on Resources folder :)
Thanks!

that's the plan, will post a pre release here to be tested :)

Here we go.
Please @spidei @acuntex @libin85 test this pre release package see if it fixes your FileImageSource issues.
Xamarin.Forms.Nuke.8.4.1-pre1.nupkg.zip

Wow! 8.4.1 works great with Resources folder! Great work!
Suggestion: It will be great if HandleFileSourceAsync not only look for the current density image, also try to find for closest density. For example, if @3 file don't exists, try to use the @2 density, or @1. In most all cases, it will find the correct file at the first attempt, and if the resource exists, will always find a resource, even if is on a smaller resolution.
Something like:
if (!Path.HasExtension(fileName))
{
	FormsHandler.Debug(() => $"Image without extension: loading \"{fileName}\" from Bundle");
	return Task.FromResult(UIImage.FromBundle(fileName));
}
else
{
	string name = Path.GetFileNameWithoutExtension(fileName);
	NSUrl fileUrl = null;

	for (float currentScale = scale; currentScale >= 1; currentScale--)
	{
		string nameWithSuffix = $"{name}{ScaleToDensitySuffix[currentScale]}";
		string filenameWithDensity = fileName.Replace(name, nameWithSuffix);
		if (File.Exists(filenameWithDensity))
		{
			FormsHandler.Debug(() => $"Loading \"{filenameWithDensity}\" as a file URI");
			fileUrl = NSUrl.FromFilename(filenameWithDensity);
			break;
		}
	}

	if (fileUrl != null)
		return LoadImageAsync(fileUrl);
	else
	{
		FormsHandler.Debug(() => $"Couldn't retrieve the image URI: loading \"{fileName}\" from Bundle");
		return Task.FromResult(UIImage.FromBundle(fileName));
	}
}

yeah I get the idea but I won't do that :)
I don't want user that name correctly their local resources to get a performance hit to take care of lazy dev x)

Ok, fair enough :D
Thanks for the new version fix! Works like a charm :)

@roubachof Thank you very much!
I was finally able to replace FFImageLoading, which was responsible for a lot of problems in my App!
When are you going to upload the new version to nuget.org (even as prerelease)? I just don't want to put too many unnecessary binary assets in my git repository.

Glad it solved your issue ! It will be released Monday

fixed by https://github.com/roubachof/Xamarin.Forms.Nuke/releases/tag/v8.4.1


feat: add time-based build and generation hash for every nuxt build

TODO

[ ] Dev mode
[x] Verify it works with nuxt generate --no-build

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This PR adds two new hash variables (process.BUILD_HASH and process.EXPORT_HASH).
The build hash differs per nuxt build (and therefore also per nuxt generate with rebuild) and indicates changes to the code.
The export hash will change only when re-generating the Nuxt project via nuxt generate and also works with nuxt generate --no-build. However, it is only available from the generation process on and might not be available (?) in the final app itself.
The idea originated a few months ago when @hootlex suggested a build token feature. :relaxed:
These hashes could be used for various reasons, but especially for export-based caching of resources that aren't touched by webpack and have a common name otherwise. This will also be the case for the upcoming full static mode ( https://github.com/nuxt/rfcs/issues/22 ), where payloads can't be processed by webpack but caching of them would be a great benefit.
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

That'd mean that e.g. the API content has changed (for example when re-generating a page with `--no-build'). Seems like a valid use case to me :relaxed:

Codecov Report

Merging #6150 into dev will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev    #6150      +/-   ##
==========================================
+ Coverage   95.75%   95.75%   +<.01%
==========================================
  Files          80       80
  Lines        2659     2660       +1
  Branches      682      682
==========================================
+ Hits         2546     2547       +1
  Misses         97       97
  Partials       16       16

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.9% <100%> (+0.01%)
:arrow_up:

#unit
92.44% <100%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

packages/webpack/src/config/base.js
94.79% <100%> (+0.05%)
:arrow_up:

Continue to review full report at Codecov.

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

It depends on what is this hash used for.
In current or change, every build will be a different build since they have different hash

@clarkdo 	I see. Would it make sense to split it up in BUILD_HASH and GENERATION_HASH or so?

For now we can leave it as your current change and see what the future feedback will be like, then apply more changes.
Thanks for the great idea!

@clarkdo I had to split it up anyway, as the build hash doesn't change on nuxt generate --no-build and overriding the build hash could lead to logic errors where on would assume another hash (as WP define plugin fully replaces occurrences as you know)

I think it should not be done through Webpack finally but from the generating part of the HTML, and then inserting a script with the data (like window.NUXT) that Nuxt will use in static mode to know the last hash when generated for the payloads.

Stale


Test/build config

This makes a few changes:

ensures checkstyle runs before any tests
ensures checkstyle violations fail build
ensures jmh tests run after RoaringBitmap tests (they were taking alphabetical precedence)
parallelises RoaringBitmap and jmh tests (build runs in under 4:30 mins on my laptop)

Coverage remained the same at 91.607% when pulling 455e54083d38e5192fa4ed7c5362ec0837a1f445 on richardstartin:test-config into bda3d060d4de04d423f4c01fe07d2dc74639400d on RoaringBitmap:master.

LGTM


MODELIX-794: adapt the detekt configuration according to the discussions from the coding conventions workshop

Updates detekt to:

lint for missing docs on public members
lint for usage of !! to prefer checkNotNull or requireNotNull

I've also fixed a bug in CI where multiplatform code was not linted due to the detekt target not including multiplatform targets.

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


Hugo v0.115.3 Disobeys 'disableLiveReload = true' Config Rendering Setting

Latest update broke the LiveReload settings where it disobeys the already existing configuration not to be rendered. This is not seen in hugo 0.111.3. Check screenshot:

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.115.3-5c2e014a5150553a9fa4f9c1eb7dc4db89c0f1ab linux/amd64 BuildDate=2023-07-13T16:11:34Z VendorInfo=gohugoio

Does this issue reproduce with the latest release?
Yes

Means when it is set to be disabled, it should not appear. Hence, the disobdience.

Means when it is set to be disabled, it should not appear. Hence, the disobdience.

When what is disabled?

disableLiveReload = true. Left side of the setting.

OK,
Try
hugo server --disableLiveReload

I understand that this may have been possible to set in site config in earlier Hugo versions -- and that got lost in the big flag/commands/config consolidation/rewrite.
I will consider adding this to the main config set, but you will get a faster response by just using the flag.

I will consider adding this to the main config set, but you will get a faster response by just using the flag.

Understood. Thank you.


Unable to Create Multiple Agents on Specified GPU

Hi!
I'm trying to create multiple agents on different GPUs. When I don’t specify a particular GPU, I can create many agents as shown below:
clearml-agent daemon --detached --queue hello_queue --docker hello_image
{worker created with worker ID "agent:0"}
clearml-agent daemon --detached --queue hello_queue --docker hello_image
{worker created with worker ID "agent:1"}

This creates two worker agents with different worker IDs:
However, the issue is that they both use the first of my two available GPUs.
But when I try to create multiple agents on a specific GPU like this:
clearml-agent daemon --detached --queue hello_queue --docker hello_image --gpus 1 # creating the first worker
{worker created with worker ID "agent:gpu1"}
clearml-agent daemon --detached --queue hello_queue --docker hello_image --gpus 1 # creating the second worker

I encounter an error while creating the second worker; the system reports that the worker ID "agent:gpu1" is already in use. Is there a way to automatically assign indices to such workers, perhaps like "agent:0-gpu1"?
Or is there another way to create multiple agents using a specific GPU?

@konstantinator can you elaborate on the use case that leads you to running multiple agents running concurrently on the same GPU?

@konstantinator can you elaborate on the use case that leads you to running multiple agents running concurrently on the same GPU?

Hi, @ainoam !  I have 2 GPUs, and my current data training configuration uses just under half of the video memory of one GPU. I've calculated that I can run 4 workers for training to tune optimal training parameters (like tuning the learning rate).


Proposal: move all Docker related files into a new docker directory

Proposal
Description
This PR is a proposal to move the docker-compose.yml file, and all other docker related files into a new docker directory at the top level of the repo.
What's the problem?
Currently our docker-compose.yml and all related files are nested inside the .github/scripts directory. There's no functional problem with this, but I'd argue that it's a confusing location. If you're new to the repository and you're trying to find the docker files, it's probably one of the last places you'd look for them — you only know to look there if you already know that's where they are.
What's the proposed solution?
We create a new docker directory at the top level of the repo, which will contain the docker-compose.yml file(s), the Dockerfile, and any supporting configuration files needed by the services, nested within their own directories.
Pros:

More conventional location makes the docker files much easier to find
The path to any file is shorter, easier to remember and type
Room for growth — if we add more services that need supporting configuration files or assets, we can add those to this directory (appropriately nested, like we have for docker/prometheus and docker/grafana)

Cons:

Currently the only non-hidden top-level directories are apps and ghost, which both contain actual source code. This would break that unwritten convention
docker falls between apps and ghost alphabetically, so it would be between these two directories in most IDEs

Alternative solutions:

Keep these files in .github/scripts
Keep the main files (Dockerfile and any compose.yml files in the root), and keep supporting files in a hidden dir (i.e. .config, .infra, .services, etc)
Instead of docker, name the new directory .docker which would hoist it to the top (although this would also hide the files by default in most operating systems so they wouldn't appear in ls or Finder)
Instead of docker, name the new directory _docker which would hoist it to the top, but not hide them.

Based on the feedback, planning to change this up a bit:

Keep the docker-compose.yml file at the top level of the repo
Move all the other docker files into .docker


CHW/ANC - Create a FHIR Questionnaire to record pregnancy outcome and create new Patient(s)

This questionnaire will  be used to :

[ ] Record a pregnancy outcome details
[ ] Create new patient(s) record for newborn(s)

Form dictionary available here
NB. Multiple resource extreaction will be required here

Based on the below mock

If multiple births do we need to create a nested form that will be used to record the new children born ?
Do we create a new patient record and mark deceased if child dies or stillbirth?

CC @isabelcshaw @rowo @HenryRae

Pregnancy outcome form: https://docs.google.com/spreadsheets/d/1vMCTQTfh4NN0IgtUWPGeU1uxreUgXPCGbiy59exNV7E/edit#gid=1097941285
Figma mockups: https://www.figma.com/file/QZ4cdpgBNy86XTOUnrnLap/COVID19-FHIR-Future-Design-System?node-id=3426%3A34064

Multiple children at birth has repeat groups. @HenryRae think about this a bit if there's a better UX we can do here.

For new patient record for stillbirth — what goes into making this decision? Is it about reporting or whether the stillbirth appears as a family member?

Quick thoughts : This approach for adding births via an incremental count may not be supported by FHIR questionnaire, may need a custom approach
@rowo @HenryRae


Pod cannot access external network

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
After installing Cilium, I found that pods (except for the Cilium node and controller pods) cannot communicate to any external addresses. I have however, tested and confirmed that pod <-> pod communication works both on the same node, and between nodes. I am also able to curl pods from the node they reside on.
Deployed a single 'ping' pod, to test pinging another device on my local network (<IP_ADDRESS>). A tcpdump on the node shows the packet does not appear to reach the cilium_* interfaces, nor the eventual enp0s1 ethernet interface:
wojoinc@big-poppa:~$ sudo tcpdump -i any icmp
tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
05:23:33.563609 lxc4f83255e50eb In  IP <IP_ADDRESS> > xxxx.xyz: ICMP echo request, id 1, seq 229, length 64
05:23:34.563702 lxc4f83255e50eb In  IP <IP_ADDRESS> > xxxx.xyz: ICMP echo request, id 1, seq 230, length 64
05:23:35.563782 lxc4f83255e50eb In  IP <IP_ADDRESS> > xxxx.xyz: ICMP echo request, id 1, seq 231, length 64

Deployed through helm with the following values:
hubble:
  enabled: true
  relay:
    enabled: true
  ui:
    enabled: true
    ingress:
      ...
ipam:
  operator:
    clusterPoolIPv4PodCIDR: ""
    clusterPoolIPv4PodCIDRList:
      - <IP_ADDRESS>/16
    clusterPoolIPv4MaskSize: 24
bpf:
  hostRouting: false
  masquerade: true
containerRuntime:
  integration: containerd
nodePort:
  enabled: true
kubeProxyReplacement: strict
k8sServiceHost: k8s-ctl
k8sServicePort: 6443
externalIPs:
  enabled: true
hostPort:
  enabled: true
rollOutCiliumPods: true
debug:
  enabled: false
installIptablesRules: true
localRedirectPolicy: false
policyEnforcementMode: "never"
policyAuditMode: true
nodeinit:
  enabled: true
ipMasqAgent:
  enabled: true

I have also attempted to uninstall/reinstall via both the cilium-cli and helm.
Cilium Version
Client: 1.11.5 b0d3140 2022-05-10T02:47:42+02:00 go version go1.17.9 linux/amd64
Daemon: 1.11.5 b0d3140 2022-05-10T02:47:42+02:00 go version go1.17.9 linux/amd64
Kernel Version
Linux big-poppa 5.15.0-33-generic #34-Ubuntu SMP Wed May 18 13:34:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.1", GitCommit:"86ec240af8cbd1b60bcc4c03c20da9b98005b92e", GitTreeState:"clean", BuildDate:"2021-12-16T11:41:01Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.1", GitCommit:"86ec240af8cbd1b60bcc4c03c20da9b98005b92e", GitTreeState:"clean", BuildDate:"2021-12-16T11:34:54Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
cilium-sysdump-20220605-002242.zip
Relevant log output
Cilium Status:
root@big-poppa:/home/cilium# cilium status --verbose
KVStore:                Ok   Disabled
Kubernetes:             Ok   1.23 (v1.23.1) [linux/amd64]
Kubernetes APIs:        ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumEndpoint", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "core/v1::Namespace", "core/v1::Node", "core/v1::Pods", "core/v1::Service", "discovery/v1::EndpointSlice", "networking.k8s.io/v1::NetworkPolicy"]
KubeProxyReplacement:   Strict   [enp1s0 <IP_ADDRESS> (Direct Routing)]
Host firewall:          Disabled
Cilium:                 Ok   1.11.5 (v1.11.5-b0d3140)
NodeMonitor:            Listening for events on 128 CPUs with 64x4096 of shared memory
Cilium health daemon:   Ok
IPAM:                   IPv4: 6/254 allocated from <IP_ADDRESS>/24,
Allocated addresses:
  <IP_ADDRESS> (default/ping)
  <IP_ADDRESS> (media/unpackerr-c79b95fc-wjkft[restored])
  <IP_ADDRESS> (health)
  <IP_ADDRESS> (media/gaps-786765bbcd-p9x6m[restored])
  <IP_ADDRESS> (router)
  <IP_ADDRESS> (kube-system/coredns-64897985d-kglbt[restored])
BandwidthManager:       Disabled
Host Routing:           BPF
Masquerading:           BPF (ip-masq-agent)   [enp1s0]   <IP_ADDRESS>/24 [IPv4: Enabled, IPv6: Disabled]
Clock Source for BPF:   jiffies               [250 Hz]
Controller Status:      39/40 healthy
  Name                                          Last success   Last error   Count   Message
  bpf-map-sync-cilium_lxc                       9s ago         never        0       no error
  cilium-health-ep                              25m43s ago     53s ago      31      Get "http://<IP_ADDRESS>:4240/hello": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  dns-garbage-collector-job                     56s ago        never        0       no error
  endpoint-1725-regeneration-recovery           never          never        0       no error
  endpoint-2110-regeneration-recovery           never          never        0       no error
  endpoint-311-regeneration-recovery            never          never        0       no error
  endpoint-343-regeneration-recovery            never          never        0       no error
  endpoint-381-regeneration-recovery            never          never        0       no error
  endpoint-4091-regeneration-recovery           never          never        0       no error
  endpoint-gc                                   57s ago        never        0       no error
  ipcache-inject-labels                         25m55s ago     25m55s ago   0       no error
  k8s-heartbeat                                 27s ago        never        0       no error
  metricsmap-bpf-prom-sync                      6s ago         never        0       no error
  neighbor-table-refresh                        14s ago        never        0       no error
  resolve-identity-2110                         53s ago        never        0       no error
  resolve-identity-343                          2m47s ago      never        0       no error
  restoring-ep-identity (1725)                  25m44s ago     never        0       no error
  restoring-ep-identity (311)                   25m44s ago     never        0       no error
  restoring-ep-identity (381)                   25m44s ago     never        0       no error
  restoring-ep-identity (4091)                  25m44s ago     never        0       no error
  sync-endpoints-and-host-ips                   44s ago        never        0       no error
  sync-lb-maps-with-k8s-services                25m44s ago     never        0       no error
  sync-node-with-ciliumnode (big-poppa)         25m54s ago     25m55s ago   0       no error
  sync-policymap-1725                           36s ago        never        0       no error
  sync-policymap-2110                           52s ago        never        0       no error
  sync-policymap-311                            39s ago        never        0       no error
  sync-policymap-343                            47s ago        never        0       no error
  sync-policymap-381                            39s ago        never        0       no error
  sync-policymap-4091                           39s ago        never        0       no error
  sync-to-k8s-ciliumendpoint (1725)             4s ago         never        0       no error
  sync-to-k8s-ciliumendpoint (2110)             13s ago        never        0       no error
  sync-to-k8s-ciliumendpoint (311)              4s ago         never        0       no error
  sync-to-k8s-ciliumendpoint (343)              7s ago         never        0       no error
  sync-to-k8s-ciliumendpoint (381)              4s ago         never        0       no error
  sync-to-k8s-ciliumendpoint (4091)             4s ago         never        0       no error
  template-dir-watcher                          never          never        0       no error
  update-k8s-node-annotations                   25m55s ago     never        0       no error
  waiting-initial-global-identities-ep (311)    25m44s ago     never        0       no error
  waiting-initial-global-identities-ep (381)    25m44s ago     never        0       no error
  waiting-initial-global-identities-ep (4091)   25m44s ago     never        0       no error
Proxy Status:   OK, ip <IP_ADDRESS>, 0 redirects active on ports 10000-20000
Hubble:         Ok   Current/Max Flows: 3698/4095 (90.31%), Flows/s: 2.27   Metrics: Disabled
KubeProxyReplacement Details:
  Status:                 Strict
  Socket LB Protocols:    TCP, UDP
  Devices:                enp1s0 <IP_ADDRESS> (Direct Routing)
  Mode:                   SNAT
  Backend Selection:      Random
  Session Affinity:       Enabled
  Graceful Termination:   Enabled
  XDP Acceleration:       Disabled
  Services:
  - ClusterIP:      Enabled
  - NodePort:       Enabled (Range: 30000-32767)
  - LoadBalancer:   Enabled
  - externalIPs:    Enabled
  - HostPort:       Enabled
BPF Maps:   dynamic sizing: on (ratio: 0.002500)
  Name                          Size
  Non-TCP connection tracking   295029
  TCP connection tracking       590058
  Endpoint policy               65535
  Events                        128
  IP cache                      512000
  IP masquerading agent         16384
  IPv4 fragmentation            8192
  IPv4 service                  65536
  IPv6 service                  65536
  IPv4 service backend          65536
  IPv6 service backend          65536
  IPv4 service reverse NAT      65536
  IPv6 service reverse NAT      65536
  Metrics                       1024
  NAT                           590058
  Neighbor table                590058
  Global policy                 16384
  Per endpoint policy           65536
  Session affinity              65536
  Signal                        128
  Sockmap                       65535
  Sock reverse NAT              295029
  Tunnel                        65536
Encryption:               Disabled
Cluster health:           2/2 reachable   (2022-06-05T05:31:53Z)
  Name                    IP              Node        Endpoints
  big-poppa (localhost)   <IP_ADDRESS>        reachable   reachable
  a2                      <IP_ADDRESS>        reachable   reachable

Anything else?
Possibly related to #19983, however unsure as to what the resolution was here?
I am also transitioning this cluster from Calico -> Cilium, so curious if there's just something obvious I've missed in the process.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Just an update, I found that providing the following when deploying via Helm resolves the issue
endpointRoutes:
  # -- Enable use of per endpoint routes instead of routing via
  # the cilium_host interface.
  enabled: true

However, from the logs, it looks like this causes Cilium to fallback to legacy host routing, so I feel like this probably isn't the right way, but it is a decent workaround for now.

I'm on Cilium v1.11.6 and experience the same issue, but only affected pods on 1 of 3 nodes.
Enabling endpointRoutes helped the failing node.

We are observing the same behaviour where pods are intermittently unable to connect any external network. This is  the case even while running in:
policyEnforcementMode: "never"

I got the same issue with AWS EKS 1.22, and Cilium 1.13.1

Same issue with K8S 1.25.8 and Cilium 1.13.2

Same issue with K8S 1.25.8 and Cilium 1.13.3

Why is this issue closed? What was the solution? We are facing the same problem on EKS version 1.26

I am still facing this issue also, a clear path to resolution is definitely needed.

If only cilium pods that can access external network, so it is likely because of Cilium configuration.
Easy way to get both KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT_HTTPS values is to from a pod
k8sServiceHost => KUBERNETES_SERVICE_PORT_HTTPS
k8sServicePort => KUBERNETES_SERVICE_HOST
You can try to upgrade your cilium installation with the correct values.
helm upgrade cilium cilium/cilium --version 1.12.4 --set k8sServiceHost=... --set k8sServicePort=... --set kubeProxyReplacement=strict

We might want to reopen this, doesn't seem like it's fixed.


Custom DNS client for connecting to centrifuge server

We need to connect to centrifuge server using custom DNS. Currently have to use custom build of this library to achieve this.
This PR adds ability to pass custom DNS client through Options.

Thanks!


Dockerized

Checklist

[x] Read CONTRIBUTING.md, and accept the CLA by including the provided snippet. We will not accept PR without this.

I, @codearranger, confirm that I have read and understood the terms of the CLA of Kyutai-labs, as outlined in the repository's CONTRIBUTING.md, and I agree to be bound by these terms.

[x] Run pre-commit hook.

$ pre-commit run --all-files
flake8 on moshi package..................................................Passed
pyright on moshi package.................................................Passed
flake8 on moshi_mlx package..............................................Passed
pyright on moshi_mlx package.............................................Passed

[ ] If you changed Rust code, run cargo check, cargo clippy, cargo test.

PR Description
Added Dockerfiles and docker compose to run the service on a Linux with the NVIDIA Container Toolkit
Docker Server setup
Install the NVIDIA Container Toolkit
https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html
Start the docker container
docker compose up

Could you add a section in the readme explaining how to use the docker image? Then I can accept the PR.
Thanks a lot!

@adefossez done

Thanks a lot, merged!


Timeline does not zoom when ctrl+scroll wheel are used when Rerun does not have focus

Describe the bug
When the cursor is over the timeline, Ctrl is pressed, and scroll wheel is used Rerun zooms the timeline.
When Rerun does not have focus, however, Ctrl is ignored and the scroll wheel will scroll down regardless.

To Reproduce
Steps to reproduce the behavior:

Open Rerun and put something on the timeline
Use Ctrl+scroll wheel on the timeline to observe zoom
Click into another app so that Rerun does not have focus
Without clicking back into Rerun, observe that the timeline will scroll when the user hovers over it and scrolls.
Without clicking back into Rerun, not that Ctrl is ignored when using scroll wheel

Expected behavior
Rerun respects Ctrl when zooming on the timeline, even without focus.  Note that other applications, like Firefox do respect Ctrl in this case.
Desktop (please complete the following information):
Operating System: Ubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 6.8.0-40-generic (64-bit)
Graphics Platform: X11
Processors: 32 × Intel® Core™ i9-14900KF
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Rerun version
rerun-cli 0.18.2 [rustc 1.76.0 (07dca489a 2024-02-04), LLVM 17.0.6] x86_64-unknown-linux-gnu 7312/merge 59ff15b, built 2024-08-29T13:49:48Z

cc @nikolausWest, @gavrelina

I cannot reproduce on macOS. Ctrl-scroll wheel works regardless of whether the rerun window is focused or not.
I suspect that this might be a platform-specific limitation (or bug) in winit. This comment seems vaguely related, though I'm not able to dive into the details or test on linux right now.
In any case, I'm afraid we won't be able to fix this by 0.21, so I'm removing it from the milestone.


<EMAIL_ADDRESS>Fix URL

Files for Google Sites are now hosted on Google Drive. So, "https://drive.google.com/uc?id=1reCUlV4He6ZDqX8GgJtuFsegc557PgDi&export=download" instead of "https://sites.google.com/site/regexreplace/home/rxrepl.zip?attredirects=0". Everything else seems the same.

Closes #XXXX

Relates to #XXXX

[ ] I have read the Contributing Guide.

/verify


404

Does someone know why it does not appear in the chrome extension store? It looks like it is missing

It's back online! We have a problem with the Chrome Store policy requirements.


mWeb - Cursor is missing after adding an emoji.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found we executing PR https://github.com/Expensify/App/pull/11033
Action Performed:

Go to any chat
Verify that you can type text in the composer.
Open emoji picker
Verify that you can add emojis, and that cursor position is after emoji.

Expected Result:
Verify that cursor position is after emoji.
Actual Result:
Cursor is missing after adding an emoji.
Workaround:
Unknown
Platform:

Where is this issue occurring?

Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/191844565-18f57edd-fcae-4c13-b150-29d43b8106e6.mp4
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub

This is probably being introduced here https://github.com/Expensify/App/pull/11033

Actually, I can reproduce this on prod. So nvm my comment above.

I can't reproduce on mWeb, neither on staging nor production on an iOS simulator. And I also can't reproduce on my Android device.
https://user-images.githubusercontent.com/2229301/192608910-e243a8ca-d9a0-4b98-89a5-eca2058e33ae.mov
It looks like various discussions point to https://github.com/Expensify/App/issues/11239 / https://github.com/Expensify/App/pull/11036 being reverted, so I imagine this was possibly a side effect of that PR that was also fixed by reverting. Going to wait for the next deploy to see if it's popping up again, otherwise will close this.


Question: sorry but how do you open a prompt

how do you properly open a prompt, like a prompt with yes/no questions, i tried opening a prompt with the ui files but buttons didnt display as sprites or something

i managed to open a prompt with the text and everything nvm


not require specific directory structure or keys in package.json

In LESS, if you require something from MODULE_NAME/dir/file.less it resolves to the npm path. I'd like the same thing in sass, so I can grab files directly from node_modules, without setting anything up or making the upstream project change their structure or package.json, like this:
@import "material-colors/dist/colors.scss";

It would resolve this issue so I could have inter-dependant modules that include each other's scss.

Actually nevermind, this totally works. I will make a PR for the README :)

for anyone interested, here is a gist that illustrates the working path-resolution.


jsonpickle: guard against invalid b85 and b64 data

I'll add a changelog entry tonight once I'm back home.

I found a few more out-of-band values that could trigger other errors so I amended this commit with  more tests and exception cases to cover these values for b64 and b85. We have a number of unreleased fuzz fixes at this point so I'm going to deploy a patch release today.


Update singlediode.bishop88 parameter types in docs

[x] Closes #1820
[x] I am familiar with the contributing guidelines
[ ] Tests added
[ ] Updates entries in docs/sphinx/source/reference for API changes.
[ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[x] Pull request is nearly complete and ready for detailed review.
[ ] Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

Update docs of singlediode.bishop88* functions to say that the parameters related to the bishop88 model and PVSyst are float types, not numeric.

+1 for the reverse bias parameters breakdown_factor, breakdown_voltage and breakdown_exp being floats. The common reason reason to compute the negative voltage portion of IV curves is to get to an IV curve for a series-connected devices, and it's hard to imagine having different diode behavior among the series-connected components.
I'm not sure about making the recombination current term parameters NsVbi and d2mutau to floats. The code lets one use an array. My impression is that these parameters are seldom used, but when they are used, they are probably set to PVsyst's constant defaults. So I don't think it does any harm to expect float.

Since the code already works when NsVbi and d2mutau are arrays, they should probably be left as numeric.


make failed on linux mint 19: failed to run custom build command for cairo-sys-rs v0.3.3

$ git clone https://github.com/mmstick/systemd-manager && cd systemd-manager && make
Cloning into 'systemd-manager'...
remote: Enumerating objects: 851, done.
remote: Total 851 (delta 0), reused 0 (delta 0), pack-reused 851
Receiving objects: 100% (851/851), 2.89 MiB | 276.00 KiB/s, done.
Resolving deltas: 100% (469/469), done.
cargo build --release
    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading gdk v0.5.2
 Downloading quickersort v2.2.0
 Downloading dbus v0.5.2
 Downloading gtk v0.1.2
 Downloading gio v0.1.2
 Downloading gdk-sys v0.3.3
 Downloading gdk-pixbuf v0.1.2
 Downloading glib-sys v0.3.3
 Downloading bitflags v0.5.0
 Downloading libc v0.2.21
 Downloading cairo-rs v0.1.2
 Downloading glib v0.1.2
 Downloading pango v0.1.2
 Downloading gio-sys v0.3.3
 Downloading gobject-sys v0.3.3
 Downloading bitflags v0.4.0
 Downloading pkg-config v0.3.9
 Downloading pango-sys v0.3.3
 Downloading gdk-pixbuf-sys v0.3.3
 Downloading cairo-sys-rs v0.3.3
 Downloading c_vec v1.2.0
 Downloading nodrop v0.1.9
 Downloading num-traits v0.1.37
 Downloading unreachable v0.1.1
 Downloading odds v0.2.25
 Downloading void v1.0.2
 Downloading metadeps v1.1.1
 Downloading error-chain v0.7.2
 Downloading toml v0.2.1
 Downloading gtk-sys v0.3.3
 Downloading atk-sys v0.3.3
   Compiling pkg-config v0.3.9
   Compiling bitflags v0.4.0
   Compiling libc v0.2.21
   Compiling error-chain v0.7.2
   Compiling bitflags v0.5.0
   Compiling toml v0.2.1
   Compiling gdk-pixbuf v0.1.2
   Compiling cairo-rs v0.1.2
   Compiling gio v0.1.2
   Compiling c_vec v1.2.0
   Compiling gdk v0.5.2
   Compiling gtk v0.1.2
   Compiling odds v0.2.25
   Compiling void v1.0.2
   Compiling num-traits v0.1.37
   Compiling unreachable v0.1.1
   Compiling glib-sys v0.3.3
   Compiling gobject-sys v0.3.3
   Compiling gio-sys v0.3.3
   Compiling gdk-pixbuf-sys v0.3.3
   Compiling pango-sys v0.3.3
   Compiling cairo-sys-rs v0.3.3
   Compiling atk-sys v0.3.3
   Compiling gdk-sys v0.3.3
   Compiling gtk-sys v0.3.3
   Compiling nodrop v0.1.9
error: failed to run custom build command for `cairo-sys-rs v0.3.3`
process didn't exit successfully: `/home/agricolamz/systemd-manager/target/release/build/cairo-sys-rs-0aaf000d5db048c5/build-script-build` (exit code: 1)
--- stderr
`"pkg-config" "--libs" "--cflags" "cairo >= 1.10"` did not exit successfully: exit code: 1
--- stderr
Package cairo was not found in the pkg-config search path.
Perhaps you should add the directory containing `cairo.pc'
to the PKG_CONFIG_PATH environment variable
No package 'cairo' found

warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `glib-sys v0.3.3`
process didn't exit successfully: `/home/agricolamz/systemd-manager/target/release/build/glib-sys-51f6194bcd1549e8/build-script-build` (exit code: 1)
--- stderr
`"pkg-config" "--libs" "--cflags" "glib-2.0 >= 2.32"` did not exit successfully: exit code: 1
--- stderr
Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found

warning: build failed, waiting for other jobs to finish...
error: build failed
Makefile:6: recipe for target 'all' failed
make: *** [all] Error 101

I am having the same problem. I managed to get past these two errors by installing these missing packages first:
sudo apt install glib-2.0
sudo apt-get install libcairo2-dev

I am currently stuck at this error though:
cargo build --release
   Compiling glib-sys v0.3.3
   Compiling gobject-sys v0.3.3
   Compiling cairo-rs v0.1.2
   Compiling cairo-sys-rs v0.3.3
   Compiling dbus v0.5.2
   Compiling gio-sys v0.3.3
error: failed to run custom build command for `dbus v0.5.2`
process didn't exit successfully: `/home/greg/Desktop/systemd-manager/target/release/build/dbus-45f9123a8b2403d0/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error(PkgConfig(Failure { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"dbus-1 >= 1.6\"", output: Output { status: ExitStatus(ExitStatus(256)), stdout: "", stderr: "Package dbus-1 was not found in the pkg-config search path.\nPerhaps you should add the directory containing `dbus-1.pc\'\nto the PKG_CONFIG_PATH environment variable\nNo package \'dbus-1\' found\n" } }), State { next_error: None })', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.

warning: build failed, waiting for other jobs to finish...
error: build failed
Makefile:6: recipe for target 'all' failed
make: *** [all] Error 101

Got it working. Here is a list of the dependencies I had to install:
sudo apt install glib-2.0
sudo apt-get install libcairo2-dev
sudo apt install libdbus-1-dev
sudo apt install libpango1.0-dev
sudo apt install libatk1.0-dev
sudo apt install libgtk-3-dev

Got it working on Ubuntu 18.04. Here is a list of the dependencies I had to install:
sudo apt install glib-2.0
sudo apt install libcairo2-dev
sudo apt install libdbus-1-dev
sudo apt install libpango1.0-dev
sudo apt install libatk1.0-dev
sudo apt install libgtk-3-dev

Hi @in3rsha, working perfectly on:
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco


Problems with Web GUI project build errors

Created a project from Web GUI using the archetype=io.fabric8.archetypes:karaf-cxf-rest-archetype:2.2.81
When the pipeline runs for the canary build it runs and looks ok until:

INFO] DOCKER> ... Status: Downloaded newer image for fabric8/karaf-2.4:latest
[INFO] Copying files to /home/jenkins/workspace/workspace/rest1/target/docker/fabric8/rest1/1.0.1/build/maven
[INFO] Building tar: /home/jenkins/workspace/workspace/rest1/target/docker/fabric8/rest1/1.0.1/tmp/docker-build.tar
[ERROR] DOCKER> Error building image: The command '/bin/sh -c chown -R jboss:jboss /tmp/6c1a2ff7-dfe9-4442-9cb1-cd5042bc9749 && cp -rp /tmp/6c1a2ff7-dfe9-4442-9cb1-cd5042bc9749/* / && rm -rf /tmp/6c1a2ff7-dfe9-4442-9cb1-cd5042bc9749' returned a non-zero code: 1
[ERROR] DOCKER> The command '/bin/sh -c chown -R jboss:jboss /tmp/6c1a2ff7-dfe9-4442-9cb1-cd5042bc9749 && cp -rp /tmp/6c1a2ff7-dfe9-4442-9cb1-cd5042bc9749/* / && rm -rf /tmp/6c1a2ff7-dfe9-4442-9cb1-cd5042bc9749' returned a non-zero code: 1
[ERROR] DOCKER> The command '/bin/sh -c chown -R jboss:jboss /tmp/6c1a2ff7-dfe9-4442-9cb1-cd5042bc9749 && cp -rp /tmp/6c1a2ff7-dfe9-4442-9cb1-cd5042bc9749/* / && rm -rf /tmp/6c1a2ff7-dfe9-4442-9cb1-cd5042bc9749' returned a non-zero code: 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 03:38 min
[INFO] Finished at: 2015-12-24T15:21:28+00:00
[INFO] Final Memory: 60M/388M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jolokia:docker-maven-plugin:0.13.7:build (default-cli) on project rest1: Unable to build image [fabric8/rest1:1.0.1] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Sorry logged in the wrong place


Show: Support Directory and can monitor dir's files increase.

@mengxy  plz have a check

@dongmx

thanks @dongmx

@YongHaoWu You are very welcome :)

@dongmx  I am curious. Do u really review my code? haha

@YongHaoWu Reviewed, but no tests.


Update CURLRequest.php

empty content-lenght header fix

@lonnieezell , @jim-parry : could you merge this pls to fix "Content-length:" header?


Select Componet Issue PreSelect value

There are something wrong in select component i have array of JSON of object So i used  URL as Data Source Type until now every thing it's ok .
I want now preselect on of these options, based on documention should  be there are field called "value property" but it's not there .
there are any advice to solve this ?

Hello,
The ‘Value Property’ field has not been added to  our beta site yet but is definitely on our backlog.  This is available on our production portal at https://portal.form.io/ .
Let us know if you need anything else

If you are using the Value Property option, you should be able to use the default value option to set the property value. For example, for your select field, if the Value Property is set to "value", you can set the default value to "BH" and it will select that one from the list by default.

@randalkuntson thanks for your response,
The Value property available in beta website , currently I use angular-formio version 3.8.0 , how can get this feild property in my project

@AnasHijazi the Beta website just uses the core builder which is already available within the form manager module within this library. The documentation shows how this can be used within your own application.

@travist  i can't understand you , i have get component select manual ? if yes can share me location please ?

Here is that documentation for select: https://help.form.io/userguide/form-components/#select

@wag110894 , I know this documention based on this there are field value property it's available on beta web site how can get this property ?
I can't understand comment @travist
I using angular-formio version 3.9.0


a typo in your the build section of Readme

Hi,
It is a great tool, thank you. However, I found the following typo will cause the build to fail
./gradlew quarkusBuild -Dquarkus.package.type=uber-jar
it shall be
./gradlew quarkusBuild -D quarkus.package.type=uber-jar

Fixed in https://github.com/sharplab/epub-translator/commit/bff504f8d8c7af8b33eeb96178e48a8c74e438dd


Veil.Secure fails when a conn does not hold an user-agent header

If there's  no user agent header in a conn (e.g. in tests) then Veil.Secure fails because it's trying to concatinate the nil user agent with the <> operator.

Thanks very much for your pull requests, all have been merged. Any feature requests?


Use default property values when adding a new column in a migration

This one bit me as well. Is there any timeframe on this or would it maybe be an idea to note it in the migration documentation?

I just added this to our docs: https://realm.io/docs/objc/latest/#migrations

Note that default property values aren't applied to new objects during migrations. We consider this to be a bug and are tracking it as #1793.

I hope this will be fixed soon as it's difficult for the developers to test if the migrated DB works for each of the previous versions of the realm. (after 90 updates in our case)
We recently received errors because of unexpected null string properties (with normally a default value of @""), when we released a major update of our app.

The challenge here is to only ever set default values if they haven't explicitly been set by a user, which in turn requires tracking which setters were invoked.

This does seem challenging. I would imagine that a user explicitly set a properties value back to the default, it should not be automatically migrated if the default changes. It almost seems that there ought to be some sort of resetProperty: method.

@jpsim Couldn't we also strictly set the default values before the user sets the property?

Yes, I think eagerly setting default values before user set the property would be acceptable. It shouldn't have a significant performance impact, but I'd prefer if we checked nonetheless.

So what is solution for assigning default value for new Column after migration ? any magical method ?

No magic. Set manually :(

Any solution or fix to this issue?

Still happens here, any progress on this?


Change tmux pane title for fzf splits

Hello!
I'm having the following problem while using fzf with custom tmux keybindings required to work with vim-tmux-navigator:
I use C-h/j/k/l shortcut to navigate between vim and tmux splits, but the same shortcuts are used to iterate over lists in fzf split. vim-tmux-navigator basically solves the problem of shortcuts clash between tmux and vim using if-shell statement inside tmux config that detects the current command of the pane and sends appropriate commands to current pane.
The same solution would apply to fzf if only there were a way to detect that current split is running fzf. Currently it's impossible because there is no identity of fzf in the tmux pane - the active command is bash.
This commit changes the tmux pane title to "fzf" which allows to differentiate it in tmux if-shell command.

Since you use C-h/j/k/l to navigate between splits, don't you want to use different set of keys for moving cursor up and down in fzf? CTRL-N and CTRL-P are idential to CTRL-J and CTRL-K by default, so you can use them instead, and you can further customize keys using --bind option.
Having said that, if you still think it makes sense to change the title of the pane, please update the commit to use ; between the commands instead of && just for consistency.

In this particular case I would like to avoid learning new shortcuts just because
a) Jumping out of the fzf split is not the reasonable workflow for me
b) I don't use CTRL-N and CTRL-P anywhere
c) This is an easy fix that doesn't introduce any other inconsistencies for others

Okay, fair enough. Not using CTRL-N/P part was a bit surprising to me though as they're universal; shell, vim, emacs, any apps using readline.

Merged, thanks!

@junegunn Thanks for merging this. @akashin Now that FZF opens a new split with the "fzf" pane title, do I have to update my .tmux.conf to have a flag called $is_fzf (or similar) to conditionally send the change window command? Further, what would that look like? Sorry for my inexperience with Tmux (I am trying to learn!)

@kieran-bamforth Unfortunately this was reverted due to #586.

@kieran-bamforth yes, you're right. You can find my tmux.conf here: https://github.com/akashin/dotfiles/blob/master/tmux/tmux.conf.symlink#L72
I'm still going to investigate the problem that appeared for some other shells, hopefully on this weekend.

@akashin #T is showing just localhost for me if I open fzf from vim and run :run-shell 'echo "#T"'. Did you ever figure this out?

This seems to be working for me:
not_tmux='`echo "#{pane_current_command}" | grep -iqE "(^|\/)g?(view|n?vim?x?)(diff)?$"` || `echo "#{pane_start_command}" | grep -iqE "fzf"` || `echo "#{pane_current_command}" | grep -iqE "fzf"`'

I didn't know that there is "pane_start_command" available. Unfortunately for me without the PR it shows "env TERM=screen-256color" when I invoke fzf.
With the PR I get "printf '\033]2;fzf\033';' env..." in pane_start_command.
With this PR #T shows fzf as expected when I invoke fzf-tmux.
I print #T in tmux status pane with
set -g status-left '#T'

Actually I was seeing only part of #{pane_start_command}.
After adding
set -g status-left-length 120

I indeed got
env TERM=screen-256color  bash /tmp/fzf-args-26570

which contains fzf as a substring. So this is a possible workaround without my PR.

pane_start_command and pane_current_command no longer contain anything relating to fzf. Is there another workaround?

In case this helps for others looking for the same functionality, I noticed that christoomey/vim-tmux-navigator had been updated in June 2016 to suggest a new detection strategy using ps scoped to the current pane's TTY (https://github.com/christoomey/vim-tmux-navigator/pull/117). I thought that was a better solution (as it doesn't rely on pane titles), and I was able to adapt it to support fzf as well. I tested this using both fzf-tmux and regular fzf, and it seems to work perfectly.
# Smart pane switching with awareness of Vim splits and fzf.
# See: https://github.com/christoomey/vim-tmux-navigator
not_tmux="ps -o state= -o comm= -t '#{pane_tty}' | grep -iqE '^[^TXZ ]+ +(\\S+\\/)?(g?(view|n?vim?x?)(diff)?|fzf)$'"
bind-key -n C-h if-shell "$not_tmux" "send-keys C-h"  "select-pane -L"
bind-key -n C-j if-shell "$not_tmux" "send-keys C-j"  "select-pane -D"
bind-key -n C-k if-shell "$not_tmux" "send-keys C-k"  "select-pane -U"
bind-key -n C-l if-shell "$not_tmux" "send-keys C-l"  "select-pane -R"
bind-key -n C-\ if-shell "$not_tmux" "send-keys C-\\" "select-pane -l"

I ran into this no longer working with C-h,j,k,l. C-n and C-p work. Did the configuration change recently on this?

I also ran with the same problem as @exosyphon

me 3


Ignoring files, using .stylelintignore doesn't seem to work, alternative ?

Hi,
I have passed in a glob to my files config on stylelint webpack plugin like so
    new StyleLintPlugin({emitErrors: false, files: ['**/*.+(css|scss)']})
I also have a number of CSS files from 3rd parties that I have placed under my assets/css/external directory, and I added a .stylelintignore file in the /external direcory with the following contents
    **/*.css

but also tried
   **/*.*

But it doesn't seem to respect it, the webpack process shows all the warning still in the console for the files I wish to ignore.
Any ideas? Am I doing something wrong?
Thanks

@appsolutegeek sorry for the delayed reply, you could add a negated glob for the assets/css/external folder so that it's not included.
.stylelintignore is a responsibility of stylelint as far as I'm aware, so have you been able to reproduce it with just the stylelint CLI?

I'm going to close this issue for now due to inactivity. I hope your problem was resolved @appsolutegeek :) but feel free to let me know if not and we can reopen this.


More than one connection per broker in C++ client

Motivation
Allow more than one connections per broker in C++ client - prevents clients with 100s of topics from waiting to acquire the lock on connection.
Modifications

Created a container for holding the connections, pooling starts once the container is full.
Added new APIs in Client.h to set number of connections per broker
Added new test cases and modified existing ones

Result
Performance improvement in C++ client
Don't Merge - Want to wait for current client to roll out in production

@merlimat @msb-at-yahoo @saandrews @rdhabalia - when you get time can you pls have a look and give a +1

@msb-at-yahoo - Addressed all your comments


Remove wildcard imports 🍷 🥇

Currently we have some wildcard imports in the project. Would be nice to remove these 🛩 😄
I think this was my bad, when initialising the project and moving the code, the IDE added them automatically since I had not removed that option.

Hey @oas004, I can give this a go!

Hey @oas004 I couldn't find any wildcard imports. There were some unused imports in Chips.kt but other than that everything looks good!

Hey @oas004 I couldn't find any wildcard imports. There are some unused imports in Chips.kt but other than that everything looks good!

Oh okay, sorry about that. I think we can probably close this issue then :) Thank you for looking into it :) You can remove the unused import in Chips.kt if you want the hacktober contribution :)

Thanks very kind of you, thanks! I can contribute to #27 as well!

No worries! Feel free to take a look at that if you want to! :)


MBBConnect Problem

Hello,
With guide of document, i want to use MBBConnect. My Steps are like:
Open MBBConnect, this is CPP project,
Debug mode, set the platform ARM.
After Rebuild, copy MBBConnect.exe to Iot Core Device "C:\Data\Users\administrator\Documents"
after over Power shell run the MBBConnect but gettin this error.
The term 'MBBConnect.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
+ CategoryInfo          : ObjectNotFound: (MBBConnect.exe:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
What is my wrog ?
Could someone help me .
Thanks

@saraclay Could you chekck this ?
Thanks

@saraclay huhu sara are you there ?

@rtarta did you find a solution to this?

@Eugene0469  Hi, I could not find any solution, i asked many question but nobody  answered. I leaveout the Windows Core IoT, with raspbery pi 3 it is so slow.
I turn back to Arduino with sim800L it will be better for me. With Esp32.

@Eugene0469  Not yet

@rtarta Ok. Thanks for the reply. We were thinking that it might be an issue with the processor. We saw that the mbbconnect.exe was built for an Intel x64 processor and we were trying to run it on an arm based processor. That is our take for the moment though.

@Eugene0469  do not play around the Windows Core IoT, being a .net developer, it needs to be work on it. I do not know what is your project but, i turn it to ESP32, it has released Feb.  mbbconnect just create profile xml for you.  if you can find vodafone modem which is listed on supported devices.
Best thing for me using SIM800L or higher, for camera use ESP32 these are cost 20$ max. If you need more help do not hesiate to get in touch.


Add Recovery Emails

When an alert instance goes from (Unknown Warning or Critical) to Normal a recovery email should be sent.
Considerations:

Should recovery templates be their own template? I think they should, and repeated logic can be done via include templates
Who to notify? The same notifications that were notified of the previous state.
notifications will need a no_recovery option. This is needed if we want to hook up alerts to pagerduty (don't want our phones being dialed to let us know that an issue is recovered, at that point we can rely on email)

My main reservation about this feature is that users are more likely not to investigate an alert that is recovered, this is dangerous because the alert could be a latent issue. However, it is better to provide a better frictionless workflow than a road block. Bosun aims to provide all the tools needed for very informative notifications so good judgements can be made at times without needing to go to a console. Furthermore, we should also add acknowledgement notifications. This will be a way to inform all recipients of an alert that someone has made a decision about this alert and hopefully committed to an action (fixing the actual problem, or tuning the alert).
Ack emails will be described in another issue.
This feature needs discussion and review prior to implementation.

Is this still under consideration? It'd be nice to have bosun auto-resolve with pagerduty :)

+1

+10

I still have the same concern that an alert going back to "normal" does mean that the issue has been resolved. We have implemented ack emails. Ideas for the future:

"normal" notifications could go to the person who ack'd or anyone that "subscribes" to the incident (This isn't current a thing)
We could have a recovery expression. The main problem is that !down doesn't equate to recovered. If we do want the expression language to evaluate recovery, then we need to be able to extend the recovery condition to not just be the inverse of down. This could be complex by evaluating other conditions - or a probably more common case would be that the recovery and down are just asymmetrical in that timespan of the query.

I'm more okay if we have support for these sort of recovery conditions - but that would involve a new factor in an already complicated state machine. So I don't think this is currently in Stack's roadmap.

+1 for this!

:+1:

+1 Had to wake up several times for alerts that were recovered

+1 for PagerDuty integration; we too would like to like to tell it that we crossed back over the threshold for a particular incident ID to normal.
We're investigating Bosun to mediate multi-site monitors (New Relic synthetics checking externally-facing pages from multiple sources); initial goal is to require multiple source checks to fail for a period of time before alerting.
Regarding philosophy of this RFE:
I agree the ideal solution is to tune the alert rule and thresholds correctly so it only alerts when it matters, and use the groups/notification timeouts/nexts to set a notification chain.
An Bosun admin can do that; but we're trying to cure an alert deafness problem across a larger team. Enabling recipients to individually tune their alerts based on return to normal is needed (think management escalation paths).
The concern about "not investigating" is a choice that the recipient should be allowed to make on their own -  simply provide the information when there's a state change from warn/crit to normal.
Re: the closure issue; leave the incident in open/normal state on the Bosun dashboard - if one chooses to investigate; all the information is there - and future alerts trigger on the same incident and keep the history available.
As near as I can tell; it is not required for someone addressing the underlying condition causing an alert to actually touch Bosun in any way - they can just fix the problem. This would be a boon in our situation. A small Ops squad in a large DevOps team should not create a large Bosun user base that needs regular custom Bosun configs; and most outside our squad wouldn't know how or care to fuss with Bosun.
I might suggest an alert implementation similar to this:
alert is_normal {
	template = norm_pagerduty_tmp
	norm = <any_warn_or_crit_legal_condition>
	normNotification = pagerduty
}

The {{.Alert.Prior.<whatever>}} variables would be available in the template to allow one to indicate in the notification any information from its last alert state.
It might be worth adding the state change from crit->warn as a notification; though this isn't a feature we're presently concerned with.
I hope you'll reconsider the value of this feature.

@djohnsen Can you expand on how your team uses pagerduty. It might help me to understand the integration story there, and in particular why the lack state change notifications hurts there.
Perhaps a notification flag will just send all events (state changes) to that endpoint for any alerts that are associated with alerts going to that notification.
Bosun's state machine is already pretty complex. We have log which sort of bypasses that, but doesn't do anything in regards to normal notifications. We have ignoreUnknown, Dependencies (unevaluated states), squelching, silences. All this is kind of meant to behave in a certain way:
Bosun creates issues, and issues are resolved by humans. A new issue is created when normal goes to a warn, crit, or unknown state (a.k.a Abnormal States). If notification chains exist, notifications will be sent until a human acknowledges the incident.
Currently notifications are triggered when the abnormal state increases (warn->crit, crit->unknown, warn->unknown) within the lifetime of an incident (until a person closes it). A property of this model flap suppression. If we start sending all state changes, the next thing I think people will want is flapping detection.
So add more options to possible incident / alert states isn't trivial since it increases the number of combined states an alert key can be in (and then result in bugs).
But I wonder if maybe people just want to bypass our state machine completely, pipe events to pagerduty, and let it take it from there.

Use case:
New Relic synthetic monitoring of www.example.com.  Every 1 minute 5 New Relic locations (amazon data centers) are doing a "url ping" of www.example.com.
3 New Relic url ping check locations fail, New Relic alert is sent to bosun.
Bosun alert rule "if >50% of locations testing www.example.com fail, then send alert to pager duty".
Bosun sends alert to pager duty since > 50% condition was met.  Pager duty policy is set to delay waking someone up for 5 minutes.
1 minute later, 5 New Relic locations (amazon data centers) are doing a "url ping" of www.example.com.
All locations pass.  "All Clear notice" is sent to bosun for this incident.  Bosun sends "all clear" to pager duty for this incident.  Pager duty issue resolves.  Nobody is woken up.
This "fail, then 1 minute later recovered" incident is displayed in bosun's "history of events" for a human to review and see patterns later.
Bypassing bosun to send alerts directly to pager duty is not the answer.  We would like bosun to make rule decisions based on it's data.  Pager duty can't do that.
Flap detection built into bosun would be nice, but that is an extra feature request unrelated to this RFE.

@cncook001 In this case I don't understand why an alert is sent to pager duty if people might not be woken up.

You could change the alert not trigger unless 50% of locations have been down for longer than X.
You can also have a warn that is more sensitive, but won't notify pagerduty, and a crit that does
Another option is to use escalation chains, and only send to pagerduty when a human hasn't acked the alert within a certain amount of time.

Also, relevant to this a blog post on some of my thinking: http://kbrandt.com/post/alert_status/

I agree with your blog post.  Don't send an alert unless you really have a problem.  Also, only send an alert to someone who can do something about it.

In this case I don't understand why an alert is sent to pager duty if people might not be woken up.
New Relic alerting is "very poor".  It is a known issue for them, we don't know when New Relic alerting will get any sort of "intelligence".  I don't want to wake people up due to their poor alerting.  We should throw New Relic out but this is one of the monitoring systems we need to work with.

If bosun can handle recovery messages nicely we will initially implement it to utilize it's alerting engine.

You could change the alert not trigger unless 50% of locations have been down for longer than X.
Agreed.  But... what happens when the rule fires because X minutes is true.  1 minute later the condition is resolved?  I may have received an alert, saw it on my phone, before I got out of bed the "all clear" alert came though.

As a general rule (for some components) I prefer not to send an alert until it has failed for two test cycles.  e.g. SNMP or ping.  SNMP may not respond since it is low on the device priority list.  The device may be working fine though.

You can also have a warn that is more sensitive, but won't notify pagerduty, and a crit that does
With my first example, this would not matter.  New Relic does not have reliable location monitoring.  We don't control the Amazon data centers nor do we control the quality of New Relic synthetics.

Another option is to use escalation chains, and only send to pagerduty when a human hasn't acked the alert within a certain amount of time.
We only want a human involved when it really is a problem.  Something that goes bad then quickly good again is not an offense we want to wake someone up for.

Want to make sure I understand some things:

Somehow you use new relic as a data source for bosun. That data source has some built-in availability issues. This leads to some of the alerts to trigger falsely based on observation data missing (and not the site being down).
When this triggers, bosun notifies pagerduty
Pagerduty calls someone

Between 2 and 3, there is some lag, where the pagerduty escalation could have been stopped, but it wasn't.
Is this a correct characterization of the scenario?

3 New Relic url ping check locations fail, New Relic alert is sent to bosun.
Bosun alert rule "if >50% of locations testing www.example.com fail, then send alert to pager duty

That confuses me. How does new relic send an alert to bosun? I'm not clear if the fail logic is in bosun or new relic

Correct.  We have an app that calls the New Relic API.  "give me the results from all locations that tested www.example.com, send those results directly to bosun"
If bosun alert rule == true (for this instance), immediately notify pagerduty.
Pagerduty is also "not smart" with escalation delays.  We have a dummy user that receives the first alert.  After X minutes if Pagerduty has not received an "all clear" for this incident it escalates to a human who gets woken up.

New Relic absolutely has failed logic.  I should be able to say in New Relic "only send an alert out if >50% locations failed", but I can't.  I am trying to use Bosun to implement that logic.  Bosun certainly can send the alert out, but it can't send the "great, we are working again" message.

Another question...
An bosun event triggers.  An alert is sent.  Is a human expected to manually close it?
e.g. Human goes to Bosun alert console.  Sees alert for url check www.example.com failed.  Go to web page for www.example.com, confirm it is up.  Go to Bosun and close the alert.
What is the value of the Human's time spent?

We don't use Bosun for very many short term, self healing or availability style alerts. We use Pingdom or  RainTank for that, which already has recovery alerts and integrates with PagerDuty.
Most of our Bosun alerts are things like disk space, high cpu, puppet errors, etc, which require a human to investigate and verify that the root cause was fixed.
Bosun can create log=true alerts, which are designed to skip the entire alert workflow for things like spikes in exceptions. In that case we dont want a human involved, and it is more of a raw realtime notification (this event happened at this time) and the alert defines how often it triggers (once when > 1000 exceptions in last 5m, runEvery = 1 for 60s trigger time, maxLogFrequency = 10m so it only fires a max of once ever 10m)
That way we still don't need a "recovery" alert, since we watch the graphs and chat notifications and know we are in the clear if it hasn't triggered in the last 10m.

+1
Also add the it would be usefull to notify an external system via HTTP that the system is recovering.

We are also using bosun as a way to relay alerts to various systems operated by different NOC teams; the external systems are used for incident management instead of Bosun, so in this instance we end up ignoring Bosun's state machine.
We are using a fork that uses an "autoClose" flag per each alert.; if an incident is open, and an event with the status of normal is received the incident is closed. This doesn't support custom recovery templates/messages though. Would this be useful/accepted upstream?


Fix client singleton router ii

What kind of change does this PR introduce?
Replaces: https://github.com/toomuchdesign/next-page-tester/pull/161
Fixes: https://github.com/toomuchdesign/next-page-tester/issues/160
What is the current behaviour?
You can also link to an open issue here.
What is the new behaviour?
...
Does this PR introduce a breaking change?
What changes might users need to make in their application due to this PR?
Other information:
Please check if the PR fulfills these requirements:

[x] Tests for the changes have been added
[x] Docs have been added / updated

Coverage remained the same at 100.0% when pulling 187c984537ad68b359ee1f4cad8c5021f0c4e6b9 on fix-client-singleton-router-II into dad5cbb7ca4175290ad32820290575f3318fc263 on master.


esp32_c3_s3/wifi_ble: Use nxsem_trywait to take semphr from ISR

Summary

esp32_c3_s3/wifi_ble: Use nxsem_trywait to take semphr from ISR

Use the non-blocking nxsem_trywait to try to take the semaphore
during the interrupt handler.
Impact
Fix usage of the registered callback for the _semphr_take_from_isr from the Wi-Fi and BLE adapter.
Testing
Internal CI testing with Hardware testing + NuttX CI

The proposal of #10234 was reviewed for each chip/arch ;)


Quick steps to resolve connection refused error

Resolving my own issue on #348 (NB: Please fix my grammar, I'm not an english native speaker)

@imamassi thanks for sharing the solution.


feat(cw logs identifier): add log id

:tada: This PR is included in version 1.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Config system and tests

Coverage increased (+11.2%) to 76.214% when pulling 76f7befa4a507cf4335efd144156f3b1ca5bd703 on dongryphon:config2 into 06b841a3c4c09826ba2dbdace4616f177830f547 on EpiphanySoft:master.

Coverage increased (+21.2%) to 86.173% when pulling fc24b8b806b3dbf23ead62bf81e3b3ad39c7c567 on dongryphon:config2 into 06b841a3c4c09826ba2dbdace4616f177830f547 on EpiphanySoft:master.

Coverage increased (+25.03%) to 90.02% when pulling 2a94e4830ba7dfbc41e83da05c5806c77f91b591 on dongryphon:config2 into 06b841a3c4c09826ba2dbdace4616f177830f547 on EpiphanySoft:master.


[Bug]: Yaw and Pitch reset after player respawn

/mv version -p output
[14:30:32 INFO]: [Multiverse-Core] Multiverse Plugins Loaded: 0 [14:30:32 INFO]: [Multiverse-Core] Economy being used: EssentialsX Economy [14:30:32 INFO]: [Multiverse-Core] Permissions Plugin: Bukkit Permissions (SuperPerms) [14:30:32 INFO]: [Multiverse-Core] Dumping Config Values: (version 2.9) [14:30:32 INFO]: [Multiverse-Core]   enforceaccess: false [14:30:32 INFO]: [Multiverse-Core]   prefixchat: false [14:30:32 INFO]: [Multiverse-Core]   prefixchatformat: [%world%]%chat% [14:30:32 INFO]: [Multiverse-Core]   useasyncchat: true [14:30:32 INFO]: [Multiverse-Core]   teleportintercept: true [14:30:32 INFO]: [Multiverse-Core]   firstspawnoverride: false [14:30:32 INFO]: [Multiverse-Core]   displaypermerrors: true [14:30:32 INFO]: [Multiverse-Core]   enablebuscript: true [14:30:32 INFO]: [Multiverse-Core]   globaldebug: 0 [14:30:32 INFO]: [Multiverse-Core]   silentstart: false [14:30:32 INFO]: [Multiverse-Core]   messagecooldown: 5000 [14:30:32 INFO]: [Multiverse-Core]   version: 2.9 [14:30:32 INFO]: [Multiverse-Core]   firstspawnworld: spawn [14:30:32 INFO]: [Multiverse-Core]   teleportcooldown: 1000 [14:30:32 INFO]: [Multiverse-Core]   defaultportalsearch: true [14:30:32 INFO]: [Multiverse-Core]   portalsearchradius: 128 [14:30:32 INFO]: [Multiverse-Core]   autopurge: true [14:30:32 INFO]: [Multiverse-Core] Special Code: FRN002
Server logs
no errors
Server Version
1.20.6

Bug Description
Player direction resets to 0/0 but its defined to       pitch: -7.200036
yaw: 147.75058 in the world.yml file.
Steps to reproduce
/kill a player and he will respawn.
Agreements

[X] I have searched for and ensured there isn't already an open or resolved issue(s) regarding this.
[X] I was able to reproduce my issue on a freshly setup and up-to-date server with the latest version of Multiverse plugins with no other plugins and with no kinds of other server or client mods.

full server logs and properly /mv version -p output please


Publish lastest changes

Hi there!
I noticed that some dependencies were upgraded, particularly node-uuid to uuid. I'm received this nasty error:
[SECURITY] node-uuid: crypto not usable, falling back to insecure Math.random() Error

I believe it should be solved by publishing the next minor/patch release.

0.12.7 is out there.


Updated localization

added strings for vertical tab view
translated some strings to German

@yaichenbaum I don't know want you want me to do since I applied your suggestions during review.

@yaichenbaum I don't know want you want me to do since I applied your suggestions during review.

Can you solve the merge conflicts?

@yaichenbaum I can't solve the merge conflicts because Visual Studio doesn't show me the merge conflicts in the "Solve conflicts" view

@yaichenbaum I can't solve the merge conflicts because Visual Studio doesn't show me the merge conflicts in the "Solve conflicts" view

I recommend trying to solve them in Visual Studio Code.

I recommend trying to solve them in Visual Studio Code.

They don't show up in VS Code either

:shipit:


Reset to default system titlebar is broken

Describe the bug
Simply set ExtendsContentIntoTitleBar=true  then set it back to false, now you have a broken system titlebar. The inactive color is the same as active, and caption button foreground color is also bugged.
This issue only occurs on Windows 11.
Steps to reproduce the bug

Create a new WinUI3 packaged project C# project
Use this code

        public MainWindow()
        {
            InitializeComponent();
            ExtendsContentIntoTitleBar = true;
        }

        private void myButton_Click(object sender, RoutedEventArgs e)
        {
            ExtendsContentIntoTitleBar = false;
        }

Click the button

Expected behavior
No response
Screenshots

NuGet package version
WinUI 3 - Windows App SDK 1.5.4: 1.5.240607001
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

@codendone : Could you pls. disable this STUPID AI answers in this repository!.
It makes quick scanning all the issues and finding out what's going on a really cumbersome process! Any reasonable developer contributing an issues IMHO is basically able to use google and co. to get this information beforehand to contributing valuable time and effort. Just my 2ct., thx.

@RobertK66 Thanks for the feedback. See #9769.


Right usage of helpers or is it a bug

Im having problems understanding how i need to use helpers, since the info outputs in console are misleading.
My use case: Im getting a cursor from a collection, and i extend it (similar to project) with a special attribute, that is needed to use jsTree:
this.helpers({
            tree: function () {
                return Trees.find().map(function(elem){
                  return _.extend(elem,{text:elem.description}); //add additional field
                });
            }
        });

Later in view i pass the 'tree' to the jstree (as e.g. vm.tree). If i preview this on chrome 47, the jsTree can build up the components, but in the console i get following Information:
defining 'tree' value helper, note that this feature will be deprecated in 1.4 in favor of using 'getReactively'
If i run it on Safari or Firefox, the tree is not build up, i get the same Information and additional one:
[Warning] overriding 'tree helper' (angular-meteor-data.js, line 1853)
What im doing wrong or is it a bug?

Seems to be simmilar to https://github.com/Urigo/angular-meteor/issues/1110

Hi @sauliuni
The return value of the helper function should be Cursor in order to create the function helper you wish to create.
In this case, the return value of Trees.find() is a Mongo.Cursor which is great, but running map will return another return value (Array) so in this case, you will create a value helper.
If you wish to do some of your own logic to the return values, use transform method for the Mongo.Collection object, as described in http://docs.meteor.com/#/full/mongo_collection .
Please re-open if you have another questions... good luck!


Use OGC-WCS together with GeoTIFF files

OGC-WCS -- Web Coverage Service -- allows one to request a specific area and get a GeoTIFF response.  Since GeoTIFF is the data format used for training/inference, using a WCS would free users from having to store GeoTIFF files on their hardware.  This is turn has the benefit of easier integration to a Big Data environment that would expose its raster data sets as WCS.  We ought to make the code use GeoTIFF files generated on the fly through WCS web requests just as easy as using local GeoTIFF files.

Considerations:
User-specified informations

Service URL
Layer name
Bands information in WCS request (number, type, sensor, etc.)

All those informations should be stored within the hdfs files and with the model, once the training is done. This will improve re-usability of the datasets and models. Moreover, we should store (or at least make sure to include an easy access to) the service's GetCapability result.
Handling the bbox for the request
Options:

Specified by the user from a csv-like file.
(+) Same approach for data preparation (images_to_samples.py) or inference (inference.py).
(-) Substantial effort required by the user.

AOIs are stored as polygons in the gpkg, differentiating trn/val/tst AOIs.
(+) Easy for the user to generate those polygons.
(+) Same approach for data preparation (images_to_samples.py) or inference (inference.py).
(++) AOIs can be stored and re-used once the model is trained. Giving context on the training process will greatly improve the model's re-usability.

AOIs are deducted from the reference (ground truth) data. Convex hull around polygons, differentiating trn/val/tst data.
(+) Not much preprocessing required by the user, for data preparation.
(++) AOIs can be stored and re-used once the model is trained. Giving context on the training process will greatly improve the model's re-usability.
(-) Another approach must be designed for inference, since there are usually no reference data, at that stage.

Support for WCS in inference was implemented in my fork but we decided not to continue on this track for multiple reasons. Of which:
First, WCS might not be the best solution for what we intend to do. WCS services are very vendor specific, I believe we're more looking for a "raster data connector", in order to directly access the stored raw data, not reprocess/interpolated data. To that end, we might end up with OPeNDAP or THREDDS services. As other options, we note [OGC API coverage] (https://github.com/opengeospatial/ogc_api_coverages) which might get more attention from the public in a near future and STAC, which is getting a lot of attention these days.
Second, OWSLib does not meet our requirements yet;

We got issues regarding http handling
We have to handle the version negotiation
Maxsize and other server limitations are not handled by the lib

Apparently, the OGC Spatio-Temporal Coverage / Datacube Standards -- amongst which WCS -- do not include url parameters relating to pixel size in GetCoverage operations.  MapServer's support for those parameters is nice, but since we cannot rely on an arbitrary WCS resource to support pixel resampling, WCS as a standard to fetch raster datasets for learning or inference looses much of its value.


Proxy letting through too many requests before additional replicas ready

Report

0-4 HTTPScaledObject with targetPendingRequests = 40
send 10 requests, scales up to 1, everything works
send 150 requests, all 150 requests go to the single replica while the others are scaling up

Expected Behavior
The keda proxy should know how many replicas of a given deployment are up, and only allow (N*X) requests through, where N=num of replicas of the deployment running, and X = the targetPendingRequest value
Actual Behavior
our server cannot physically handle all 150 requests with 1 replica, which causes the requests to fail. KEDA sends all the pending requests to the single replica.
Steps to Reproduce the Problem

0-4 HTTPScaledObject with targetPendingRequests = 40
send 10 requests, scales up to 1, everything works
send 150 requests, all 150 requests go to the single replica while the others are scaling up

Logs from KEDA HTTP operator
example

HTTP Add-on Version
0.7.0
Kubernetes Version
< 1.27
Platform
Other
Anything else?
No response

Hello @noyoshi
This is an interesting scenario tbh. I guess that something like a rate limiter can be useful at this point, but I'm not totally sure about how to implement this. Do you have any suggestion? Are you willing to contribute this this feature?
FYI @zroubalik  @wozniakjan

what would be the desired response from the interceptor in this case? Should it start responding with 429 when there are too many requests?
Overall stability might be slightly harder to achieve because interceptor would probably need to get involved with some form of loadbalancing too. There might be a situation, where

150 requests saturated the single replica
new replica is spinning up but is not ready yet
interceptor is rejecting new requests with 429
new replica becomes ready
the initial single replica managed to process 0 requests in that window
interceptor sees new replicas and stops responding 429
interceptor sends requests to Service which will round-robin load balance among replicas
first replica is still saturated and failing to process
second replica gets only 50% of the new load resulting in 50% fail rate

I guess we could introduce some form of request window per replica and instead of using Service for routing requests, route these to Endpoints directly based on the size of internal request windows?

@wozniakjan hey! Sorry for the late reply.
The interceptor shouldn't be responding with 429 - it should hold onto the requests like normal. I think it should just "release" the requests, allowing N*M requests to go to the service, where N = the autoscaling request count, and M = the number of running pods in the deployment

This is all under the assumption that the scaleup threshold was properly configured and it is the max concurrent requests a replica can handle at once. Otherwise, this would technically leave some throughput on the table in some cases where the single replica could handle more than N requests.
So probably something that should be up to the user to configure IMO.


does not send message

When I send the communicator with the authors within a team in teams, they do not receive the card, and the communication is sent but it is correct: 0 and error: 0. I don't know what it could be.

Hi @maye-vargas Thanks for highlighting, We will discuss with our team and get back to you with proper response soon.

Hi @maye-vargas ,

Could you please confirm that message is delivered to the respective user. Supporting screenshot would be more helpful.
Is it happening to all the sending options or only to one of the sending options?
And check whether function apps were deployed successful or not?
If they are successful and issue persists then please share the app service logs.

Hi @gsv022,

Currently I do not have a screenshot since the implementation was carried out in production with a client, the process is carried out in sessions and currently I do not have screenshots. But the implementation issue in the app service, its status is correct (active).
When I send the communication, it is happening with all the communications that I send, they are sent but they never arrive and they are correct: 0, error: 0
The last time I reviewed them, your process was correct in the functions, but I would have to review them again.

I don't know what other service could check that this is the error?

@maye-vargas ,
yes, please keep us posted on function apps working state and just to re-iterate "Is it happening to all the sending options or only to one of the sending options?"

@gsv022 To all shipping options.}
Apart from the functions, what other topic could I review?

@maye-vargas  There might be multiple reason of the above error. Below few configuration you can cross verify

Check the status of Azure functions.
Go to Graph App registration and verify if the Expose an API, Authentication and Manifest are updated as per the deployment guide.
If above steps looks good, please go the application insights and share the the details error logs. It will give us the exact area it is throwing error.

Hi @maye-vargas ,
Could you please share the status.

Hi @maye-vargas,
Please share the export details of the above message that you tried to sent.

Thanks you, I managed to correct the error.


update market participant client version

Description
update market participant client version
References

#0000

Codecov Report

Merging #553 (7d8a2e3) into main (2bad1d4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #553   +/-   ##
=======================================
  Coverage   66.32%   66.32%
=======================================
  Files          11       11
  Lines         196      196
  Branches       19       19
=======================================
  Hits          130      130
  Misses         61       61
  Partials        5        5

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more