Brainstorming: integrate Prometheus /metrics handler in Falco

Motivation
Since falco-exporter is a great tool to expose prometheus metrics through gRPC, I think there are some caveats to use it. Our (w/ @developer-guy @f9n) some motivations to create this issue is that the following ones:

To reduce unnecessary gRPC communication: we have to enable gRPC output feature in the configuration. ^1
To do not manage mTLS certs: to connect gRPC over unix socket, we have to manage additionally CA Certs as described under connection options
To manage one single helm chart: there are two different helm charts that we have to manage and maintain in our infrastructure, which are falco and falco-exporter
To reduce complexity: simplicity is always better, to easily see the metrics in the Grafana, requires additional work to implement in current design
To make monitoring easier on local: we can instantly check the metrics using /metrics endpoint in some troubleshooting scenarios

$ kubectl port-forward svc/falco 8756
$ curl localhost:8756/metrics

I think that implementing a Prometheus metrics in C++ would not be as easy as it looks like. Here is an example metric server that currently using in fluentbit.
Feature
This feature already clearly proposed in #421 and #530 and implemented in the projects.
Alternatives

https://github.com/falcosecurity/falco-exporter
https://github.com/falcosecurity/falcosidekick#prometheus

Additional context
By throwing this issue actually does NOT mean that we should achieve the falco-exporter and provide this metrics in only falco by built-in. What I want to say mostly are the following ones to clarify and understand the design:

How we can make this process simpler by removing unnecessary dependencies?
What is the correct way to do?
Why did not falco provide /metrics endpoint in the first place?
What is the motivation of behind this design: separating metrics module into another project?

Waiting your feedback!

Kind ping here 🎗

We can take a look Fluent Bit's cmt_gauge.h for C++ implementation.

See: https://github.com/falcosecurity/falcosidekick#prometheus

FYI Falcosidekick exposes prom metrics exactly like you want, it can be managed with the same chart and it does not require mtls.
See: falcosecurity/falcosidekick#prometheus

Thanks, just noticed that! AFAICS, it exposes 3 metrics: falco, inputs, outputs
It could be very useful to use this on cloud or small clusters. But someone who actively use a log aggregator solution on cluster, Fluent Bit for example, might not want to install and maintain an external app in cluster. I mean, you'd have to do an additional HTTP request for each event x cluster count. I am not sure how this fits in a pull-based system.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale
/milestone 0.36.0

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

cross-linking https://github.com/falcosecurity/libs/issues/1463
cc @incertum
/assign


No breaks added between paragraphs when they don't end with a punctuation

When using Edge TTS to read an epub formatted book, the following sorts of paragraph won't be read correctly:

Chapter One
The Chapter Title
This is the first sentence of the chapter.

because it will be read as: "Chapter one the chapter title this is the first sentence of the chapter", as though it's all once sentence with no breaks. This can be especially confusing if there's a heading in a paragraph in the middle of a chapter, something like:

... This is the final sentence of a paragraph.
The Next Section
Here is another sentence.

since it'll be read as "The next section here is another sentence", making it easy to miss that the first half of that sentence was supposed to be a header.
I looked in the source code and the trouble seems to come from epub_book_parser.py, where the second text cleaning step replaces all groups of white space (including newlines) with a single space. So this might affect Azure and OpenAI TTS as well, but I haven't tested it.
At least in the case of Edge TTS, though, it's not sufficient to simply keep a newline in there, because it appears that the edge_tts module automatically replaces newlines with spaces as well. So I think the solution for it needs to include inserting periods where needed.
An even better solution for Edge TTS would be to insert longer pauses between such paragraphs, though since Microsoft prevents using SSML, it would require using something like this.

+1
I came here to report this same issue. I am using OpenAI TTS.


Surface PulumiTV on the docs landing page

We've got a lot of useful content on PulumiTV and more going in all the time. We should surface it where users are more likely to see it. A few places to consider are:

Docs home page
At the end of the getting-started flow
In a dedicated blog post

Resolved in #12875


FileNotFoundError: /opt/homebrew/lib/python3.11/site-packages/gd/submodules/schema/gd/schema/artist.capnp

when i run even a simple code it gives this error

FileNotFoundError: /opt/homebrew/lib/python3.11/site-packages/gd/submodules/schema/gd/schema/artist.capnp

Code :
import gd

client = gd.Client()

entire error
Traceback (most recent call last):
  File "/Users/-----/main.py", line 1, in <module>
    import gd
  File "/opt/homebrew/lib/python3.11/site-packages/gd/__init__.py", line 11, in <module>
    from gd import (
  File "/opt/homebrew/lib/python3.11/site-packages/gd/api/__init__.py", line 1, in <module>
    from gd.api.artist import ArtistAPI
  File "/opt/homebrew/lib/python3.11/site-packages/gd/api/artist.py", line 11, in <module>
    from gd.schema import ArtistAPISchema
  File "/opt/homebrew/lib/python3.11/site-packages/gd/schema.py", line 39, in <module>
    artist = load_module("artist")
             ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/lib/python3.11/site-packages/gd/schema.py", line 32, in load_module
    raise FileNotFoundError(path_string)
FileNotFoundError: /opt/homebrew/lib/python3.11/site-packages/gd/submodules/schema/gd/schema/artist.capn

I'm having a very similar problem, but on Windows 11.
Here's my error:
Traceback (most recent call last):
  File "C:\Users\*\Documents\Scripts\Python\Apps\gdinfobot\main.py", line 1, in <module>
    import gd
  File "C:\Users\*\Documents\Scripts\Python\Apps\gdinfobot\venv\Lib\site-packages\gd\__init__.py", line 11, in <module>
    from gd import (
  File "C:\Users\*\Documents\Scripts\Python\Apps\gdinfobot\venv\Lib\site-packages\gd\api\__init__.py", line 1, in <module>
    from gd.api.artist import ArtistAPI
  File "C:\Users\*\Documents\Scripts\Python\Apps\gdinfobot\venv\Lib\site-packages\gd\api\artist.py", line 11, in <module>
    from gd.schema import ArtistAPISchema
  File "C:\Users\*\Documents\Scripts\Python\Apps\gdinfobot\venv\Lib\site-packages\gd\schema.py", line 39, in <module>
    artist = load_module("artist")
             ^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\*\Documents\Scripts\Python\Apps\gdinfobot\venv\Lib\site-packages\gd\schema.py", line 32, in load_module
    raise FileNotFoundError(path_string)
FileNotFoundError: C:/Users/*/Documents/Scripts/Python/Apps/gdinfobot/venv/Lib/site-packages/gd/submodules/schema/gd/schema/artist.capnp

Process finished with exit code 1


Sensors used during inference

Hi, it seems that you are using the function sampling_4d which requires lidar2img transformations during evaluation as well.
It is my understanding that you proposed a method that uses only camera images during inference.
Please let me know if there's been a misunderstanding.

Issue is resolved. I confused the lidar point cloud with the actual lidar device.

We do not require lidar, but the projection matrix is still necessary


Support for CM13

not yet: FLAG_TURN_SCREEN_ON needs to be implemented

I just installed on SM-G900F running CM13 (20160114 Build) and can confirm it works for me

can you post a debug output (incl. cover actions)?

I closed and opened the cover 5 times in this log.
Log_2016-01-16_21-28-18.txt
I am having  a random issue with the screen coming on when the cover is closed and not turning back off.  I will attach the log when I can get one.

thx for logs. it seems not to be my fork of the project. can you post a link of used apk file?
accept/reject/hangup calls works?

Here's the link
https://github.com/durka/HallMonitor/blob/0.4.1/bin/HallMonitor-debug.apk?raw=true
Haven't tried calls yet,  sorry, will let you know when I dodo.
Will give your fork a go tomorrow.

habeIchVergessen here is the log from your fork and a screenshot.

Log_2016-01-17_12-58-43.txt
Haven't had a chance to test the calls yet but none of the shortcuts work in either build but the other one does not have the display issues, also the battery percentage doesn't change in your build

I can take a log on sm-n910c cm13 if you want.
It doesn't work too reliable, if you close the lid very gently the s view doesn't kick in. Your fork maybe slightly less reliable than durka's apk and I may have a crash in your fork overnight but I didn't take a log.
As for the shortcuts, I need to do more testing but the issue is that high sensitivity for the screen (glove mode, not sure how it is actually called) is not activated. You can do it manually and then the shortcuts seem to sort of work (though sometimes Google now or something starts and that uses full screen). Not really a solution though as the glove mode gets deactivated when opening the lid again.
As for the camera, it gives me a tiny preview venster but the actual picture taking does not work (only tried on durka's apk).
I could silence an alarm with glove mode activated, haven't tested calls yet.
Guess biggest issue for now is the glove mode not getting activated (maybe I can do it with tasker?) and the actual picture taking not working.
Guess I need to mod it myself a bit for the larger s view venster on the note 4.

debug my fork:

press seven times About ("debug enabled" messages appears)
do some cover actionsi
check the sd-card option
press seven times About ("debug disabled" message)
new file should be written to Download

changing touch sensivity requires root privileges. do you checked the option?

Yes root enabled but seems it doesn't kick in tot handel the screen sensitiviteit. It just worked for a minuten or so after I reinstalled tour fork but stoppen now.
I attached a regular logcat, debugging output is saved to a nog existing location I don't have /storage/sdcard0
Anyway, dit soms fast closes of the lid at which hallmonitor kicks in and a few slow ones where it doesn't. After that I manually enabled glove mode and pushed some of the buttons. Picture preview for camera shows up, taking a picture causes a crash according to the logcat. Also in camera preview mode the screen times out. On touchwiz camera preview keeps the screen awake so you have more time to take a picture. Maybe it is an idea to increase the screen time out when the camera is activated.
Let me know if I need to do more tests.
Cheers,
logcat.txt

try to enable the glove mode manually
S4

on: echo clear_cover_mode,1 > /sys/class/sec/tsp/cmd && cat /sys/class/sec/tsp/cmd_result
off: echo clear_cover_mode,0 > /sys/class/sec/tsp/cmd && cat /sys/class/sec/tsp/cmd_result

S4 mini

on:
echo module_on_master > /sys/class/sec/tsp/cmd && cat /sys/class/sec/tsp/cmd_result ; echo clear_cover_mode,3 > /sys/class/sec/tsp/cmd && cat /sys/class/sec/tsp/cmd_result
off:
echo module_on_master > /sys/class/sec/tsp/cmd && cat /sys/class/sec/tsp/cmd_result ; echo clear_cover_mode,0 > /sys/class/sec/tsp/cmd && cat /sys/class/sec/tsp/cmd_result

The s4 commands seem to work on the note4 as well, although not 100% reliable. Somehow the camera als started to take pictures, albeit sideways. Guess I'll need to take another logcat to find out why at is going on and why it sometimes works and sometimes causes a crash.

Seems that finally google provided a fix for this issue, please take a look here: https://github.com/AOSP-JF-MM/platform_frameworks_base/commit/39d533c5d8c4e16baed4f1d8b3a309622a5fb918
This is a better solution than force FLAG_TURN_SCREEN_ON when the device tries to go to sleep
Can be simply enabled with an overlay in the device tree (see here: https://github.com/AOSP-JF-MM/platform_device_samsung_jflte/commit/7b27428c887c554b1fc649db9a9ee0b19cade256 )
Tested with my old Hallmonitor fork and it's working fine without any issue! Well, timeout does not work, and a lot of things must be updated but... It's working now! ;)
Ps: can be easily merged on cm-13.0 too, but the rom must be compiled with the different overlay


Can't package .node file & use child_process.fork

node_loader use absolute path, package can't find in other pc. example: npm serialport modules.
webpack build all js to build.js, child_process.fork can't find path.
how to improve?
Thank you very much.

Using node-loader really isn't the easiest thing to accomplish.
__dirname within webpack doesn't work as you would expect when in a regular node.js application. In order to get a better file reference you could add const __root = __dirname within your index.ejs file that way your JS has a global variable to reference to when using absolute paths that could be combined with the use of path.
This probably doesn't solve your issue completely but should give a general idea on what is happening. Since this isn't a direct issue with electron-vue, I will be closing this. Also the use of native node modules should be easier in the near future as there are major plans for supporting these types of situations.


Disable animations for native-fullscreen toggle

Is there a way to speed up or disable the animation when toggling a window into our out of native fullscreen? (yabai -m window --toggle native-fullscreen)

Probably technically possible, but I don't expect that this is something I will be spending time on any time soon.

This feature is greatly needed, as the switching animation has a delay and also affects the visual experience. It is indeed a very necessary function.

I basically never use macOS native-fullscreen. Feel free to submit a PR that solves this.

Actually stopped using yabai but still looking for a solution for this. Offering $100 bounty for a solution to this (ideally one that's not reliant on yabai)

Omg you figured it out??

No, I am not interested on spending time on this, as mentioned in my previous comment.
Since the original poster also no longer uses yabai I didn't feel the need to keep this open.


Add more Settings links

This pull request adds support for more tg://settings links:

tg://settings/theme - from the iOS client
tg://settings/language - from Telegram Desktop
tg://settings/privacy - from the native macOS client

These could be defined "non-standard" links, but some of the already implemented ones (such as tg://settings/change_number) are non-standard as well.

Other two links also weren't supported intentionally, but I don't hesistate their addition.
If you change the following, the commit will be merged.

internalLinkTypePrivacySettings needs to be renamed to internalLinkTypePrivacyAndSecuritySettings.
New types and functions needs to be moved to the correct place in lexicographical order in td_api.tl, LinkManager.cpp, LinkManager.h and test/link.cpp.

If you change the following, the commit will be merged.

Done, I applied those fixes. Would it be possible to also add the tg://scanqr and tg://calllog links (from Android), before merging?


Make buttons scrollable on mobile

Even though Gamelab isn't designed to support mobile, this PR makes the buttons list scrollable, allowing mobile users to run games.
Previously, if you were on a small device, the run button would be just out of reach.
Old buttons:

New buttons:

You can scroll the new buttons to access all of them.

Nice!


Count on secondary index causes missed key schema element

I have a time series table UserActivity
case class UserActivity(
  id: Long,
  activity: String,
  occurred: Long = System.currentTimeMillis()
)
object UserActivity {
  val tableName = "UserActivityV2"
  object Attributes {
    val id = "Id"
    val activity = "Activity"
    val occurred = "Occurred"
  }
  val tableRequest =
    new CreateTableRequest()
      .withTableName(UserActivity.tableName)
      .withProvisionedThroughput(
        Schema.provisionedThroughput(10L, 5L))
      .withAttributeDefinitions(
        Schema.numberAttribute(Attributes.id),
        Schema.numberAttribute(Attributes.occurred),
        Schema.stringAttribute(Attributes.activity)
      )
      .withKeySchema(
        Schema.hashKey(Attributes.id),
        Schema.rangeKey(Attributes.occurred))
      .withGlobalSecondaryIndexes(
        new GlobalSecondaryIndex()
          .withIndexName("ActivitiesOccurred")
          .withKeySchema(
            Schema.hashKey(Attributes.activity),
            Schema.rangeKey(Attributes.occurred))
          .withProjection(new Projection().withProjectionType(ProjectionType.KEYS_ONLY))
          .withProvisionedThroughput(
            Schema.provisionedThroughput(10L, 5L)),

Using the AWS UI, I can query the index.  Although I didn't find an example for running a query, I came up with:
mapper.countQuery[UserActivity](
      mapper.CountQueryMagnet.countQuerySecondaryIndex(
        "ActivitiesOccurred",
        "sometext",
        "Occurred",
        QueryCondition.greaterThan(1421023065979l)
      ))

However this blows up with:
com.amazonaws.AmazonServiceException: Query condition missed key schema element Activity (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ValidationException; Request ID: KD4364FBV747MPFBQALD9ONS17VV4KQNSO5AEMVJF66Q9ASUAAJG)
	at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1077)
	at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:725)
	at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:460)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:295)
	at com.amazonaws.services.dynamodbv2.AmazonDynamoDBClient.invoke(AmazonDynamoDBClient.java:3106)
	at com.amazonaws.services.dynamodbv2.AmazonDynamoDBClient.query(AmazonDynamoDBClient.java:1118)
	at com.amazonaws.services.dynamodbv2.AmazonDynamoDBAsyncClient$18.call(AmazonDynamoDBAsyncClient.java:1557)
	at com.amazonaws.services.dynamodbv2.AmazonDynamoDBAsyncClient$18.call(AmazonDynamoDBAsyncClient.java:1553)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Is this due to a feature that needs to be implemented upstream? See: https://github.com/aws/aws-sdk-ios/issues/75
My build.sbt has:
  "com.amazonaws" % "aws-java-sdk" % "1.9.14"

that's latest, at least as of last week.
UPDATE: Here is the serializer

  implicit object userActivitySerializer
    extends DynamoDBSerializer[UserActivity] {

    override val tableName = UserActivity.tableName
    override val hashAttributeName = Attributes.id
    override val rangeAttributeName = Some[String](Attributes.occurred)

    override def primaryKeyOf(userActivity: UserActivity) =
      Map(Attributes.id -> userActivity.id,
        Attributes.occurred -> userActivity.occurred
      )

    override def toAttributeMap(userActivity: UserActivity) =
      Map(
        Attributes.id     -> userActivity.id,
        Attributes.email -> userActivity.email,
        Attributes.activity  -> userActivity.activity,
        Attributes.occurred -> userActivity.occurred
      )

    override def fromAttributeMap(
      item: collection.mutable.Map[String, AttributeValue]) =
      UserActivity(
        id     = item(Attributes.id),
        email = item(Attributes.email),
        activity  = item(Attributes.activity),
        occurred = item(Attributes.occurred)
      )
  }

Hmm, looks like there may be a way to identify keys there.  That could be my problem.

I think I just made some progress!
https://github.com/pellucidanalytics/aws-wrap/blob/master/src/main/scala/dynamodb/mapper.scala#L1203
Clearly that's looking at the serializer's hash/range pair.  I currently have only a single serializer, which is for the primary key.  Is the intent here that with (potentially multiple) GSIs, should I be making a serializer for each, perhaps extending from a base?  Or is implementation currently LSI-only?

Hi @peoplemerge, I’m sorry I missed this.
Did you find a resolution? Let me know if there is anything I can still do to help.

@peoplemerge
I have forked this repo and published it under version 0.9.0
https://github.com/mingchuno/aws-wrap
Can you please check if you still have any problems? If yes, please submit an issue there


Add option to pass in secret key

Allow to pass in a precreated key pair and store the secret key with the source feed. This allows to first create the key pair and then the hyperdb - useful e.g. if you want to manage many hyperdb and store them in dirs named after the pubkeys (otherwise you'd have to move the db after creation because you'd only know the pubkey after creation).

Great job with adding tests as well


Add arbitrary shape of style

Sometimes, ol.style.RegularShape, ol.style.Circle and ol.style.Image can not handle my cases,  I need some arbitrary shape with different size and color. such as

I have added a new style ol.style.ArbitraryShape . It can be used as follows:
         feature.setStyle(new ol.style.Style({
			image: new ol.style.ArbitraryShape({
				fill: new ol.style.Fill({
					color: 'red'
				}),
				stroke: new ol.style.Stroke({
					color: '#0000ff',
					width: 2
				}),
				size: [100, 100],
				points: [[1, 1], [1, 99], [99, 99], [99, 1]],
				rotation: 30 * Math.PI / 180
			})
		}));

size: {ol.Size} size of image.
points: {Array.<ol.Coordinate>} points of the arbitrary shape.
The new style can make shapes showed before.  So I think it maybe useful to others, I want to pull the code to the master if you like it. Do you like it?  Also, any suggestion? Thank you.

Have you seen the http://openlayers.org/en/v3.13.1/examples/earthquake-custom-symbol.html example?

Thank you! It is nice.  Canvas + ol.style.Icon seems to more flexible.


[QA-584]: Update target volume for Auth scenarios

QA-584
What?
Update target volume of Auth scripts
Changes:

Update target volume of auth scripts to 10% of the NFR volume

Why?
To conduct a combined test for Auth scenarios at 10% of the NFR volume.

Suggest adding a new profile instead of replacing

Added the profile for 20% of NFR volume


add license

Please add a license file.

Looking into this right now. Which one to use? So many options.

I would like to preface this entire message by saying I'm not a lawyer, and this is all based on my own personal understanding.
This site has a nice succinct comparison of popular open-source licenses (assuming this is meant to be open source):  https://choosealicense.com/licenses/
Personally, I always prefer projects which use Apache or MIT, as they allow usage in commercial products as well. Since this is Java you can also use GPLv2 + Classpath exception (http://openjdk.java.net/legal/gplv2+ce.html), which basically (to my personal understanding!) means simply including the JAR in the classpath does not force a project using your JAR to also be GPL. This is somewhat similar to LGPL.
If you want to completely disallow integrating this into commercial projects, your best bet is probably AGPL. This is used by e.g. iText, so programmers can freely use it as long as their project is open source as well, but may purchase a commercial license if they need it (as the owner of the code you may re-issue it under whatever license you like).

I have added the Apache 2.0 license.


Configure different webroot

@bartmcleod commented on Thu Aug 30 2018
Usually index.php doesn't live in the document root of a git project, but in a directory like html, public or web. I would appreciate a quick hint on how to configure the webapp to use this directory. I am sure this information lives somewhere, but I would really appreciate a quick hint on this page also.

Documentdetails
⚠ Dit gedeelte niet bewerken. Het is vereist om problemen te koppelen tussen docs.microsoft.com en GitHub.

ID: ef971d21-e72b-7771-d34a-b6da42d602bb
Version Independent ID: f60dc748-8cf9-a8eb-9b96-e30cd13acc56
Content: Een PHP-web-app maken en implementeren in App Service on Linux
Content Source: articles/app-service/containers/quickstart-php.md
Service: app-service-web
GitHub Login: @SyntaxC4
Microsoft Alias: cfowler

Hi team,
Please check the request made by the user.
Thanks!

@bartmcleod Thanks for the feedback! We are currently investigating and will update you shortly.

@bartmcleod I apologize for the delay in getting back to you.
With Windows App Services, this setting can be changed in the portal under app services. For Linux web apps, this setting will have to be changed directory in your image and then deploy the image itself to Azure. You should be able to define the location in the httpd.conf file.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@BryanTrach-MSFT The point is, with a simple out of the box Linux for web apps, it is not your own image that you deploy. I understand that I can create my own image, but I did not manage to get SSH working on that, since it doesn't have systemd on Centos 7. That is, I got SSH working locally, but on Azure that worked only 1 out of 100 tries approximately, possibly because sshd wasn't running as a service, but just called directly and demonized with -D. So I finally gave up on Web apps.

@bartmcleod you are correct and we apologize for the frustration that you have encountered. The default App Service on Linux does not allow you to edit the image and thus this is a parameter that cannot be changed when using this product.
In order to define this parameter, you would need to use Web Apps for Containers, which allows you to bring your own image and thus edit the httpd.conf file.

@BryanFranzMSFT I understand and I do not mind a little frustration from to time to time. However, I would appreciate some insights on how to address or circumvent the issue with SSH. I have tried Web Apps for Containers, with a Centos 7 image that does not have systemd. So I installed openssh and ran  /usr/sbin/sshd -D -E /var/log/ssh.log from an init shell script. This only gave me an SSH shell twice in many attempts and it broke almost instantly. Please by aware that systemd is generally considered not done for containers and that the documentation should address this. As it is now, the documentation suggests anyone can easily call service ssh start from an init script, but that is definitely not true in a lot of cases. It would be awesome to able to use Web apps for containers, but without shell access, it is hard to run commands in them (I needed to run command in them). Also, there is a security issue with Web apps for containers. The password to the repository is exposed as an application environment variable, while it is properly hidden in the settings screen, the variable is displayed. This means that my peers will see my personal docker hub password if they login to our Azure account... So all in all, I did not feel that Web apps for containers was very mature...


Unable to create custom error messages for dynamically created input elements!

Versions

vee-validate: 2.0.#
vue: 2.#.#

Describe the bug
Unable to generate custom messages for dynamically generated input elements.
To Reproduce
Whenever generating dynamic inputs with dynamic input elements name, we are unable to generate the custom error messages.
Expected behavior
Demo Link
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context

Can you please provide a working demo for the issue?

I am able to generate the input fields dynamically with dynamic names, but in dictionary i cant add dynamic values.
https://jsfiddle.net/bspatil007/m67d8f4x/1819/
let me know if i am missing something!

You were not referencing the field name correctly in the errors.first call. And you should always try to deal with the validation result when the promise resolves (then callback) since the validation result/state isn't updated until then.
here is an example:
https://jsfiddle.net/m67d8f4x/1820/

That is the issue i am facing, i want make "The testfield0 field is required." error message into something user readable. I cant use "data-vv-as". Instead of "The testfield0 field is required." i want to show "This field is mandatory". What i need to do??

@bspatil0001 i am also having same issue. Did you find solution ?

@bspatil0001 I found it.
const dictionary = {
en: {
messages:{
required: (field) => field +' should not be empty'
}
},
ar: {
messages: {
alpha: 'حاجة عربي'
}
}
};
// Override and merge the dictionaries
Validator.localize(dictionary);

If the DOM element is dynamically created, name will also be dynamic. I this case you don't know the value of 'field'!

If the DOM element is dynamically created, name will also be dynamic. I this case you don't know the value of 'field'!

No need know. You can add this code in the app.js where you initialize the vee validate.
The field value is dynamic and vee validate itself identifies the name. No need to worry about Field value. The argument field is passed by vee-validate.

@pravnovumcapital  i tried your solution but still not working please see
https://jsfiddle.net/ws3m5kLr/

Add the below code
messages:{
required: (field) => field +' should not be empty',
}


Apply same focal weight to both loss_pos and loss_neg in your implementation.

I saw that in your implementation, you multiplied the negative sum of los_pos and los_neg with the same focal weight, how does that align with your paper?

Sorry I didn't notice the multiply with the targets!


Link cleanup

r? @metajack @mbrubeck
Few fixes here:

Turns out the additional missing symbols I'd added support for were only missing due to linker-related shenanigans (they would be discarded in particular link lib argument passing configurations). Reverted.
Added the cargo output flags & removed the #[link.
On Android, skia statically links against freetype and so needs the extern crate or the rlib for the sys project will not be included.

cc @alexcrichton

@bors-servo r+

Reviewed 4 of 4 files at r1.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from the review on Reviewable.io

:pushpin: Commit 196292c has been approved by metajack

:hourglass: Testing commit 196292c with merge 8d334a8...

:broken_heart: Test failed - travis

This was my fault - I failed to push up the removal of linkhack.rs!
r? @metajack

@bors-servo r+

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful.

Comments from the review on Reviewable.io

:pushpin: Commit acff820 has been approved by metajack

:hourglass: Testing commit acff820 with merge 7ddbc48...

:broken_heart: Test failed - travis

Adding the per-target additional dependencies appears to fix the cargo test issue (which is similar to what I was running into with mozjs, where we went from dynamic to static linking and thus had to be able to satisfy all the dependencies).

r? @metajack
Confirmed it passes cargo test on OSX and the binaries compile & run on OSX and Android.

Reviewed 3 of 3 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions, all commit checks successful.

build.rs, line 27 [r3] (raw file):
remove this blank line

src/lib.rs, line 22 [r1] (raw file):
xx

Comments from the review on Reviewable.io

@metajack I think it's good to go now, though I don't know what the "xx" means?

:pushpin: Commit 2fc09c0 has been approved by metajack

@bors-servo r+
xx was me in a text field trying to use reviewable key commands :)

Reviewed 1 of 1 files at r4.
Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful.

Comments from the review on Reviewable.io

:hourglass: Testing commit 2fc09c0 with merge eb5200b...

:broken_heart: Test failed - travis

aster is here to ruin your day

@bors-servo retry
(Aster should be fixed with https://github.com/serde-rs/aster/pull/33)

:hourglass: Testing commit 2fc09c0 with merge 70ed23d...

:broken_heart: Test failed - travis

As @Manishearth points out, this is a crates.io dependency, so I'm stuck waiting for a version update.

@bors-servo retry
And, updated version pushed to crates.io!

:hourglass: Testing commit 2fc09c0 with merge e282ecc...

:broken_heart: Test failed - travis

Disabled cargo test, per @alexcrichton
r? @metajack

@bors-servo r+

Reviewed 1 of 1 files at r5.
Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful.

Comments from the review on Reviewable.io

:pushpin: Commit c47a10f has been approved by metajack

:hourglass: Testing commit c47a10f with merge 0a08cc9...

:sunny: Test successful - travis


How to add additional cookies to monitors

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
Other
🔖 Feature description
At the moment I have a monitor checking our production servers, but they are behind a loadbalancer.
I can force the loadbalancer choosing with a cookie, but I can't find any documentation on this topic, if it's even possible?
✔ Solution
Being able to add a cookie to a monitor
❓ Alternatives
No response
📝 Additional Context
No response

If you only need to add a static cookie, you should be able to use the "Headers" option and add "Cookie": "your-value". Dynamic cookies is currently not supported.


Revamp Jelly completion suggestions

This PR sets out to revamp the completion suggestions for .jelly files. It aims to fix several existing issues, as well as add new features.
Existing issues

Don't prepend namespace if it already exists in Jelly (https://github.com/jenkinsci/idea-stapler-plugin/issues/190)
You can get duplicates results (one from IntelliJ, one from this plugin)
Inconsistent behaviour between the duplicates (IntelliJs will add required fields by default, our implementation does not)

What's new

Offer suggestions for namespaces that aren't imported yet, based on other files in your project.
Automatically imports namespaces if they are not already present.

I'm often creating new .jelly files from scratch and having to manually add namespaces was a pain, now once you select a completion suggestion the namespace will get automatically imported.

Generates templates for components with required attributes, offering them to the user as completion suggestions.

https://github.com/user-attachments/assets/2c20bd57-4a57-45fd-a9a9-855e04012bb7
Testing done

Tested with core and plugins (Design Library plugin)
Added some basic tests

Submitter checklist

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[x] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

I've tested this out and it worked really nicely

This is too much, IMO. The built-in XSD-based completion just works. JetBrains maintains it. And as you said, it works better than what we've got. It already knows about required attributes (and more) and adds them automatically. If there duplicates some time, I'd say figure out why and stop showing the duplicates. Don't reinvent the wheel.

You can get duplicates results (one from IntelliJ, one from this plugin)

They are all from this plugin.
IntelliJ only knows about Jelly tag library namespaces because this plugin registers XSDs. src/main/resources/META-INF/plugin.xml#L76-L115
For custom tag libraries that are just resources in a package marked with taglib file, there is src/main/java/org/kohsuke/stapler/idea/descriptor and this java/org/kohsuke/stapler/idea/JellyCompletionContributor.java.
If descriptors and JellyCompletionContributor clash and cause duplicate suggestions. I think it is better to reduce the amount of code and just remove JellyCompletionContributor.


[imporvement](table property) support for alter table property: skip wirte index , single compaction

Proposed changes
CREATE TABLE IF NOT EXISTS example_db.example_tbl
(
    `user_id` LARGEINT NOT NULL,
    `date` DATE NOT NULL,
    `city` VARCHAR(20),
    `age` SMALLINT,
)
DUPLICATE KEY(`user_id`)
DISTRIBUTED BY HASH(`user_id`) BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1"
);

alter table  example_db.example_tbl set ("enable_single_replica_compaction"="true");
alter table  example_db.example_tbl set ("skip_write_index_on_load"="true");

Issue Number: close #xxx

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

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.46 seconds
stream load tsv:          536 seconds loaded<PHONE_NUMBER>9 Bytes, about 133 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>0 Bytes

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.86 seconds
stream load tsv:          560 seconds loaded<PHONE_NUMBER>9 Bytes, about 127 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size:<PHONE_NUMBER>9 Bytes

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.34 seconds
stream load tsv:          556 seconds loaded<PHONE_NUMBER>9 Bytes, about 128 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          29.5 seconds inserted 10000000 Rows, about 338K ops/s
storage size:<PHONE_NUMBER>7 Bytes

run external


Allow use of SlackThread() as no-op in generic coding

Currently when you use SlackThread() you get warnings when you attempt to thread a message. Instead a useful feature could be to have this be treated as a no-op. This would allow generic functions to use calls like slack_log_exception and pass in an instance of SlackThread when they want to disable the Slack messaging functionality.

I should call out that using SlackThread() to return a dummy instance conflicts with defaulting to using ENV values. One way around this is to allow callers to opt into the dummy instance when the ENV values aren't set:
SlackThread(channel, token) = ...

function SlackThread(; fallback_noop::Bool=false)
    if haskey(ENV, "SLACK_CHANNEL") && haskey(ENV, "SLACK_TOKEN")
        SlackThread(ENV["SLACK_CHANNEL"], ENV["SLACK_TOKEN"])
    elseif fallback_noop
        SlackThread(nothing, nothing)
    else
        error(...)
    end
end

We alternatively may want to consider not using ENVs as part of the SlackThread constructor as a caller may want to specify different ENV variables and instead. The caller then could do:
thread = if haskey(ENV, "SLACK_BOT_CHANNEL") && haskey(ENV, "SLACK_BOT_TOKEN")
    SlackThread(ENV["SLACK_BOT_CHANNEL"], ENV["SLACK_BOT_TOKEN"])
else
    SlackThread()
end


Integration tests

We should have something that tests the integration of our code against some existing flows. Following flows can be tested

creating a twin
creating a farm
adding / removing public ips
changing farm name
creating a node
adding / removing public config on a node
creating a contract (node, rent, name)
updating contracts
reserving public ips
billing
....

The script should compile and start a node locally, insert some offchain worker keys and the integration tests should run after.
Tasks:

[ ] extend client https://github.com/DylanVerstraete/tfchain-client (based on https://github.com/paritytech/subxt/)
[ ] hook up with github actions and run integrations tests on commit
[ ] run unit tests on commit

Proposition 1
Write a python tool that runs the node(s) in different threads (running the commands as described by substrate). We use an extra thread for running the client. The client can then run specific scenarios (specific calls in sequence). For that python tool we can use modules such as argparse, logging, etc to make life easier. That tool can also keep the logs and "store" them for later use. We can always extend the tool to validate the tests (check the balance at the end of the calls, etc.). We can use that tool in the github actions (yaml file) when we need to. This will be after the build and after the unit tests (maybe before a merge).
Benefits

No dependencies to other frameworks
We can make it do what we want it to do
Easy for other people to run specific scenario's

Proposition 2
Use a framework for running integration tests. We can write code for starting the node(s) and write test suites for the integration tests. The Robot Framework is a great open source framework used by many companies. It contains a lot of functionality and allows you to call custom made python modules. In the Robot Framework one can create test suites and add suite setup and tear down code. The setup could for example start the nodes while the individual tests can call the client and eventually check the logs for validation (or call specific client functions). Such a framework can easily be ran from the github actions later (or manually by developers).
Benefits

Easy to add new integration tests
Frameworks like Robot Framework already have many useful functionality
Proper visualization of the integration test status (Robot Framework is similar to rust tests)
Easy to run only parts of the tests (in specific use cases)
Most quick way to add proper integration tests that are maintainable and extensible

Both share the following benefits

Easy to run the tests in github actions
Easy to run specific scenario's (don't have to run the nodes, etc)

Merged branch with development


Cookie Consent

Summary
Hey, I recently updated our SDK to that one. I am implementing a cookie consent banner and I wanted to ask some questions:

Are cookies mandatory for amplitude analytics / experiments to work well?
For such a feature (cookie consent banner). I would have init amplitude with disableCookies: true then re-init amplitude when the user would have accept the cookies. Is this the way to go with amplitude, is there any method to re-enable them on the fly?

Thanks!

Hi @Liroo

Cookies are not mandatory for amplitude analytics. If cookies are disabled, SDK will use local storage instead.
For Amplitude browser SDK, we provide defer initialization. You can call tack before initialization. And call the init method after the customer grants cookie consent. The track events will be sent to the server after you call the init method.


Update README.md to add deprecation notice

As part of the new website roll-out we need to archive : json-schema-org.github.io, blog and UJS.
This PR contains the deprecation notice.

@Relequestual Can you please merge the PR? For any reason I don't have the permissions to do it myself.


Add license information to health_check.go

Description
This Pull Request makes the following changes to the health_check.go file in the fluid repository:
Corrected the Copyright year from [incorrect year] to [correct year].
These changes ensure that the proper licensing information is included and that the Copyright year is accurate.
Please review these changes and let me know if any further adjustments are needed.

/lgtm


License split for theme vs content

One license applies to the content of the repo (CC-BY 4.0), while another applies to the theme template that was used (Apache 2.0). See issue #32. This adds the content license to the LICENSE file.

Thanks, @Blahah!


[FEATURE] Migrate Docs from Documenter to DocumenterVitepress

Issue Description
Difficulty: Beginner
Time: 6 - 8 hours
Description: The aim of this issue is to support the major refactor beginning across all of JuliaHealth to improve discoverability and unity of the JuliaHealth ecosystem as it pertains to documentation. This issue's purpose is to provide guidance on how one will migrate the IPUMS.jl documentation website built on Documenter.jl to DocumenterVitepress.jl to support a more winsome entry point to new Julians curious about health research within the Julia community.
Requirements

[ ] Add DocumenterVitepress.jl dependency into the docs directory of this repository
[ ] Migrate the Documenter.jl make.jl file to a compatible DocumenterVitepress.jl make.jl file
[ ] Make sure each page renders correctly
[ ] Open and submit a PR

Expected Outcomes
After this transition is completed, the website should go from looking like this:

To something more like this:

Additional Notes
For how to approach this issue, I would suggest the following steps:
First, if you have never worked with Documenter.jl before, I would highly recommend these videos and resources:

Video: Documenter.jl Deep Dive
Documentation: Documenter.jl Official Documentation

Next, I would recommend creating a practice folder (repository) on your computer to download Documenter to. From there, I would follow the above tutorials and guides to create a documentation website on your own computer from scratch. Once you know how to create a documentation website, how to add pages, and how to write documentation for the website, you are ready for the next step!
Second, I would then create a fork of the  JuliaHealth website. Within this fork, I would add Documenter.jl to this fork. You can do this from within the Julia REPL.
Third, you will now need to begin migrating the make.jl file to DocumenterVitepress -- this guide by @Jay-sanjay is a great place to start. This will take some time and the way to preview the documentation locally can be a bit challenging. In case there are any problems, please see the resources section for help.
Third, once you are done with this, go ahead and open a Pull Request with all your changes saved to your fork. At this point, myself or @00krishna will review this PR to suggest changes or help.
Then, you should be done with this PR!
Other Resources
Julia Slack:

documentation channel - you should post here first
helpdesk channel - this would be to get more attention to your issue but maybe not as precise as you need.
health-and-medicine channel - this is where most of JuliaHealth is located these days.

Julia Discourse - I would advise posting here if you have an issue that you feel is long or requires a lot of time to explain as you might lose it within Julia Slack. Consider cross-posting your forum post to the Julia Slack in helpdesk and/or documentation.

Status so far. So there is an issue with DocumenterVitepress that @TheCedarPrince is tracking for resolution. The issue has to do with building the docs or the liveserver aspects.
@MichelaRocchetti and @00krishna were working on getting the basic Documenter.jl piece working. We were encountering some errors with generating the basic Documenter docs. Here is a paraphrase of the problem.
Basically in each of the generated openapi documentation files, there is a reference to a README.md that contains some specific sections. Here is an example.
[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)

So the README is supposed to have sections #api-endpoints and #models, but our current README does not have these files in it. These are not the only sections, as some of the generated docs look for other sections in their corresponding README.md files. Do you know if there was a README.md generated during the openapi build process that was possibly discarded or something?
Like even in the openapi docs, it was really hard to figure this out. There is no mention of the README files, but in the openapi docs itself, the corresponding README files is not in the docs section of their repo, but it is in their test section. So really strange, haha. It is like they did not want anyone to know, but it is necessary to test with the README.
So the next steps are to check with the OpenAPI folks about where this README.md file should be, and what sections it should contain.


RayClicks integration

Similar to "ClickMessage"s supported in the previous Nerfstudio viewer, where a doubleclick sends a ray to the client.
The ray is specified in world coordinates, where:

the origin is the camera origin, and
the direction is based on the vector drawn from the origin to the clicked pixel on the viewport camera's image plane.

I named it "RayClicking" here, to disambiguate it with the "Clicks" on the SceneNodeHandles.

Notes from chat:

Start with single click instead of double click.
Pass a single event object to callbacks. This could be like:

@dataclasses.dataclass
class ScenePointerEvent:
    client_id: int
    type: Literal["click"]  # Later we can add `double_click`, `move`, `down`, `up`, etc
    ray_origin: Tuple[float, float, float]
    ray_direction: Tuple[float, float, float]

We can also rename the existing viser.ClickEvent to viser.SceneNodePointerEvent?

Set up another message to turn on pointer events? So we don't send them unless a callback is actually attached.
Check if stopPropagation() in scene node click callbacks prevents scene clicks. (I'd prefer to send both events if a node is clicked but also if only the node one is clicked I think that's OK)
We can see if we can borrow naming etc from Javascript? Here's a test page for pointer events: https://devtools.terrymorse.com/pointerevents/index.html
Have a function for removing callbacks. I think a nice pattern would be:

add_sphere_button = server.add_gui_button("Add sphere")

@add_sphere_button.on_click
def _(_) -> None:
    @viser_server.on_scene_click # Or whatever this is called
    def add_sphere(event: viser.ScenePointerEvent) -> None:
        add_the_sphere(event)
        viser_server.remove_scene_click_cb(add_sphere)

Separate PRs:

Consider passing in intersected objects.
Add ray_origin / ray_direction to the scene node clicks.
Enable/disable camera controls.
Plots!

Moved everything to a separate file ScenePointerControls.tsx because it was originally inside CameraControls.tsx. Hopefully this is not only the right thing to do (ScenePointer is not camera controls!), but also will facilitate adding further ScenePointer actions in this file.
Also, with regards to the prior notes:

Start with single click instead of double click.
Pass a single event object to callbacks.
Both should be there now.

Check if stopPropagation() in scene node click callbacks prevents scene clicks. (I'd prefer to send both events if a node is clicked but also if only the node one is clicked I think that's OK)
I experimented a bit with the example test file, and it seems that both the scene node clicks and the scene pointer events are registered. :)

Set up another message to turn on pointer events? So we don't send them unless a callback is actually attached.
This should be implemented now with EnableScenePointerMessage. This state is stored inside the ViewerContext, and now can be set from the python side. I recall that you mentioned a strong preference to avoid hardcoding stuff though.

Have a function for removing callbacks.
... still thinking about it, I think it's worth trying the approach in the code snippit in the previous convo. Will try soon!


Death/damage/health/food system

Continuation of #5
This implements the food system (done by Meronat) and a basic damage/healing system. Event's will be thrown in the process, players now actually die and respawn afterwards. Void and hunger damage is implemented, food health regerenation is also working. Absorption is working (currently only receivable through a command). Probably more...

Large steps forward here with gameplay. Exciting stuff.


[Enhancement] Improve the randomness of the random function

Why I'm doing:
The original random function of SR was implemented through the rand_r function. The randomness was very poor and usually did not meet expectations.
before:

after:

What I'm doing:
Fixes #34026
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[x] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[x] 3.0
[x] 2.5

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

@zenoyang
After run is slower than current, I think you pasted the wrong picture.

@zenoyang After run is slower than current, I think you pasted the wrong picture.

No, that is the result of the intermediate state of development. The performance was not very good at the beginning.

@zenoyang After run is slower than current, I think you pasted the wrong picture.

No, that is the result of the intermediate state of development. The performance was not very good at the beginning.

CI clang-format failed in
--- /home/runner/_work/starrocks/starrocks/be/src/exprs/math_functions.cpp
+++ /home/runner/_work/starrocks/starrocks/be/src/exprs/math_functions.cpp (after clang format)
/home/runner/_work/starrocks/starrocks/be/src/exprs/math_functions.cpp had clang-format style issues
@@ -34,7 +34,7 @@
 static const double MAX_EXP_PARAMETER = std::log(std::numeric_limits<double>::max());

 static std::uniform_real_distribution<double> distribution(0.0, 1.0);
-static thread_local std::mt1[9](https://github.com/StarRocks/starrocks/actions/runs/6928566833/job/18844627873?pr=35199#step:6:10)937_64 generator { std::random_device{}() };
+static thread_local std::mt[19](https://github.com/StarRocks/starrocks/actions/runs/6928566833/job/18844627873?pr=35199#step:6:20)937_64 generator{std::random_device{}()};

 // ==== basic check rules =========
 DEFINE_UNARY_FN_WITH_IMPL(NegativeCheck, value) {

cla also need check

sign off also need check. try to execute
git commit -s -m "[Enhancement] Improv...."

sign off also need check. try to execute签核也需要检查。尝试执行
git commit -s -m "[Enhancement] Improv...."

done

@Mergifyio backport branch-3.2

@Mergifyio backport branch-3.1

@Mergifyio backport branch-2.5


fix cell background

https://github.com/composeuisuite/ohteepee/issues/35
Fixed cell background - looks like it only happens for projects that use material3
However this change should not impact on project with material2
Also i bumped libs, agp, gradle distribution, and get rid of some warnings

Looks fantastic, Thanks @mkowol-n @luongvo 🙏


Rounded buttons - Prototype Utilities

How to reproduce this bug:

Included last version *.min.css of framework in *.html file
Set class on buttons - .rounded
Nothing was changed...
Tried to find this class on official docs, but didn't find this one there...

What should happen:
Wanted to set buttons with rounded corners
What happened instead:
Couldn't set rounded corners on buttons with helper class: .rounded
Browser(s) and Device(s) tested on:
Chrome  61.0.3163.100  (64 bit) (Windows 7)
Foundation Version(s) you are using:
6.4.2

Just to be clear he faced issue while making this => https://codepen.io/IamManchanda/pen/GMJxXN

cc @kball prototype utilities are not well mentioned in the docs!

Ok, thanks

This is the part of the docs you are looking for: https://foundation.zurb.com/sites/docs/prototyping-utilities.html#component-styling
But note that you also need to enable prototype mode if you want to use this (and any prototype utilities): https://foundation.zurb.com/sites/docs/prototyping-utilities.html#enabling-prototype-mode
I also recommend you to read the introduction part of the Prototyping Utilities section. It's pretty important to understand why these utilities exist but also why you shouldn't use them in production.
Happy coding!

This is the part of the docs you are looking for: https://foundation.zurb.com/sites/docs/prototyping-utilities.html#component-styling
But note that you also need to enable prototype mode if you want to use this (and any prototype utilities): https://foundation.zurb.com/sites/docs/prototyping-utilities.html#enabling-prototype-mode
I also recommend you to read the introduction part of the Prototyping Utilities section. It's pretty important to understand why these utilities exist but also why you shouldn't use them in production.
Happy coding!

@Deckluhm But man the thing is that he was facing issue as didn't know how to replace
foundation-prototype.min.css file with foundation.css
We have to agree that we are not making things clear!
Secondly I would argue that,
Component Styling Section should be also in respective component section
( with an alert that this is part of prototype utility and disabled by default )

Plus the prototype introduction page is so long ( and I am sorry to say this @rafibomb ) that the demo get's hidden. I have to scroll to 5 pages to get to the first demo
{ I would suggest that introduction part should be moved to an article by zurb or at medium }
@kball Would love your thoughts on this!

it would be well, Iam!

Awaiting reply @rafibomb ... I think we need a video tutorial here!

I am open to moving the intro section somewhere else, for launch of a new major feature it helps to have it on the docs page for a few releases.
@IamManchanda Since you know the most about the feature, can you help with a small outline of what this page needs in terms of a tutorial video?

Also - I don't see any foundation-prototype.min.css, where does this come from?
As far as I know, the custom download allows you to include in the prototype classes into the main foundation.min.css

@rafibomb This is coming from here
https://github.com/zurb/foundation-sites/tree/develop/dist/css

@IamManchanda Since you know the most about the feature, can you help with a small outline of what this page needs in terms of a tutorial video?

For Classes,

Button ( Radius/Rounded, Bordered, Shadow )
Switches ( Rounded ) - Coming in v6.4
Cards  ( Radius, Bordered, Shadow )
Tables ( Radius, Bordered, Shadow )
Images ( Radius )
Arrow Utility ( Top, Right, Bottom, Left )
Separator ( Left, Center, Right )
Font Styling - here
List Styling - here
Text Helpers - here
Margin & Padding Helpers
Sizing
Border None ( Callout )
Display, Positioning & Overflow

For Mixins,

Box Mixin - here
Rotate Mixin - here
Relational Mixins - here

Also when you do @rafibomb ... Please would be greatfull if you add the codepen's too as this page is missing that too :D
( Component Styling should surely have the codepen's )

I am open to moving the intro section somewhere else

Would it be ohk if I move Introduction, and Enabling Prototype Mode section to medium articles and start with just 1 scroll for the demo?


Add some more coverage to utils functions

I'm going to revert last commit. Maybe it's the one which is causing the issues


How can i get this available on Mac?

Project had compiler error and not opening when i copy plugin folders to my plugins folder.

HI, Ah so your on Mac too, same version huh, unreal engine developing with Mac, I know the pain, feels sometimes folks forgetting about us Mac users when it comes to unreal engine. I bet we run into very similar issues ie Mac users get little love from UE, but thats for another day.
So regarding your issue,
Ok so can you do me a favor and first try to remove the advanced steam sessions, and see if the advanced sessions plugin loads up successfully.
If that still is an issue, please delete the following folder from your project (BEFORE YOU DO THIS PLEASE BACK UP YOUR PROJECT)
Delete the folders boxed in purple in the screenshot below

The reason I said remove advanced steam sessions for now is I think I ran into that same problem with that specific plugin and then ended up never fixing it. but let me also confirm shortly. I just want to make sure at least the first plugin works for you, so we can say we both have the same issue going on. ie with the second plugin.

Its telling you to compile the plugin in XCode, launching the project won't compile the plugin and I don't have the hardware to ship pre-compiled MacOS binaries.

https://docs.unrealengine.com/5.0/en-US/setting-up-an-unreal-engine-project-for-ios/

the general concept, i am not aware of tutorials for this really as I have never had to do it.


Added Registration Page and Modify Moderators Page

I have completed the assigned work. This PR closes the issue #8 .

Other than the basic design, the following are the extras I would emphasise on.
Moderator Modify Page -

Floating button which triggers a Dialog Box to add moderators
Email field validation using RegEx
Showing the number of requests passed by moderators to the admin
Remove option for moderators

Registration Page -

Dropdown for hostels
Scroll Problem Fixed
Validation for each TextField
CircularProgressIndicator in an AlertDialog for loading time while interacting with backend

I have added how the background of the App was prepared with Widgets. Have a look at those too.


Add Paketo SC and CFF TOC nomination statements for candidates to date

Nomination statements are taken from the nomination issues filed on this repo:

#877: Beyhan Veli
#879: Ruben Koster
#880: Jan von Löwenstein

FYI @christopherclark @cloudfoundry/toc, as I don't have sufficient access to request a review myself.

LGTM. We miss you Eric!