Basic example of using within node?

We are building a set of angular components in TypeScript, and I am attempting to integrate TypeDoc into our build system to automatically pull out the options for each component and generate some HTML so that it is more automated (we're currently copy/pasting).
I noticed that I can create a new instance of the typedoc.Application within node, but I am a bit lost as to where to go from here. I'm just printing out the app object, and it all happens so fast that I can't imagine it's actually doing anything.
Can you give me some pointers on how to get up-and-running and the types of things I might want to access/use?
I'd be happy to create a wiki page or update the README with my findings and some examples if you can point me down the right path :-)
Thanks!
/*
 * My current (VERY basic) code
 */
var gulp = require('gulp');
var typedoc = require('typedoc');

gulp.task('microsite:build', function(cb) {
  var app = new typedoc.Application({
    includes: ["components/**/*.ts"]
  });

  console.log(app);

  // TODO: Iterate over the components and extract some options

  // TODO: Generate a JSON file/object which we can use within Angular to generate HTML

  cb();
});

Hi Topher, your setup seems to be okay. After requiring the TypeDoc module you can create an instance of the application class like above. You can pass an object to the constructor containing the desired options, a full list of available options is available here.
The application exposes the convert method which expects an array of source files and returns a ProjectReflection instance. This root reflection contains all reflections of the given source files and offers utility methods to work with them, see the docs for details. If you want to get the data TypeDoc stores using the --json option you may call the toObject of the project reflection.
Using the generateDocs method of the application you can directly generate a html documentation, the generateJson method writes a json file. Both methods require a list of source files or a ProjectReflection as their first argument and the desired output location as their second argument. You can find the full documentation of the application class here.
TypeDoc has no support for glob patterns, you must expand the pattern in your code. However, you may use the expandInputFiles method of the application to replace directories in your source array with the contained files.
TypeDoc has built in grunt support, the script is a good example of how to run TypeDoc programmatically. Check it out for a basic example.

Thanks Sebastian! I'll take a look at it and post back here if I can get it working :-)

After I upgraded to 0.3.4 (I was still on 0.2.3) I got it working and was able to extract the necessary information that I needed!
Thanks so much for your help!
Here's an excerpt of the semi-final solution for future reference (I still need it to iterate over every single TypeScript file and actually output the final JSON, but this is close):
var path = require('path');
var typedoc = require('typedoc');

gulp.task('docs:extract', function(cb) {
    // Setup our paths
    var outPath = path.join('build', 'test-file.json');
    var filePaths = [
        path.join('components', 'my-component.ts')
    ];

    // Setup our TypeDoc app
    var app = new typedoc.Application({
        name: 'My Awesome App'
    });

    // Actually generate the JSON file
    app.generateJson(filePaths, outPath);

    // Parse it
    var json = JSON.parse(fs.readFileSync(outPath, 'utf8'));

    // Clean up our JSON with a special function that removes unnecessary stuff
    var cleaned = cleanupJson(json);

    cb();
});

Hope this helps someone in the future!


multithread

I use OpenSSL
OpenSSL 1.0.1e-fips 11 Feb 2013
OpenSSL 1.0.0-fips 29 Mar 2010
in a multithread enviroment. I have two context: one for https request and one for wss connections. It's possible ? Wich functions cannot execute conncurrently ?
Thank you

You cannot use SSL_CTX in multiple threads unless you lock it (with your own lock wrapper).  OpenSSL data structures are not built for concurrent multi-threads use.


LLama 2 and Code LLama support?

I have been trying to get llama 2 models to function correctly. They start off ok but then all of them goes into a loop with repetitions or gibberish.
I haven't tried setting model_type:llama to something else, could it be that we need to add llama2 here instead?
model_type: llama
Possible to get any of the code llms to support this ?

I tried with llama-2 and llama2 and read the ctransformers documentation and realized its just llama.
The answer gets into a loop when using llama2 models:
The telecom industry is not not not not not not not not not not not not not not not
Like that, I read somewhere that it could be related to something RoPE but don't know how to set that!

Fixed it by implementing prompt template!


Channel info page

Implement the channel info page, behind the (i) button on the channel screen. It should show:

the topic,
channel modes,
button to quit the channel,
channel members

Fixed by https://github.com/hhirtz/Discussions/commit/10a684755b829f82285ac3aecd005c2b05f8a611
not showing channel modes for now, see #18


Issue in installation

Hi,
When I install the bundle with composer, it is installed under vendor directory but the directory web/bundles/starrating/ doesn't exist, when I add it manually and I try to execute I get the error
ClassNotFoundExceptionAttempted to load class "StarRatingBundle" from namespace "blackknight467\StarRatingBundle".Did you forget a "use" statement for "blackknight467\StarRatingBundle\StarRatingBundle"?
in AppKernel.php
and it is caused by this  declaration:  new blackknight467\StarRatingBundle\StarRatingBundle()
can You tell me how to fix this ?
Also I would like to uninstall the bundle and reinstall it, as I tried many manipulations, should I remove it from the vendor directory?
Thanks

Mee too...


[Bug]: Fix Wasm executors to exit after run completion

Bug Description
In youki we expect that executor.exec will not return if the exec is successful. This behavior is consistent for tradition containers, where we do an exec syscall and replace process image, thus never returning from exec call. However for wasm workloads our exec implementation does return, and causes crash as it reaches the unreachable! statement. We can either allow the executor to return, or just do a process.exit with exit code from wasm code in our wasm executors to conform it to traditional containers.
Steps to Reproduce
Follow https://containers.github.io/youki/user/webassembly.html to create a wasm container and run it. It will run, but in the end it will error saying -
Printing args
1
2
3
Printing envs
("PATH", "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin")
("TERM", "xterm")
("container", "podman")
("HOSTNAME", "b569c0459007")
thread 'main' panicked at crates/libcontainer/src/process/container_init_process.rs:644:5:
internal error: entered unreachable code: the executor should not return if it is successful.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Expectation
Youki should not crash in this way. The exit should be graceful, i.e. with a proper exit code (non-zero in case of wasm module returning non-zero exit)
System and Setup Info
N/A , should be reproducible on all systems
Additional Context
FYI, if a new contributor is interested in taking this , ping me (@YJDoc2 ) for help before starting!

@YJDoc2 I'm interested in this issue, but I won't be able to work on it until the weekends in October. If that’s okay, I would love to take it on.

Hey, sure I will assign this to you.
Context for this is - for normal binaries we use exec syscall so that process image is replcaed by that binary. For wasm, we use wasm runtimes which execute the wasm file. Unlike binary here we do not replcae the process image so after the runtime is done executing, it returns and causes the error. So in the main wasm executor implementation we want to take the exit code returned by those runtime and basically do a process.exit with that exit code.

@YJDoc2 Thanks for sharing contexts! My new PC has arrived, I just started using a Linux desktop machine from today. So I can finally tackle this issue. I need an additional bit of time, but I will do this for sure.

My new PC has arrived, I just started using a Linux desktop machine from today. So I can finally tackle this issue.

Great! Also congrats on the PC and starting with Linux!

I need an additional bit of time, but I will do this for sure.

Yep, no worries.

Hey @kiokuless , ping!
Let me know if you are facing any issues in this.

@kiokuless Hey please let me know if you are still working on this. It is ok if you are busy with other things and cannot work on this anymore, just let me know so I can mark this unassigned for someone else to take up.


Need to write api docs with sanic-openapi

https://github.com/sanic-org/sanic-openapi

close in #22


Scala implementation is not validated on every PR.

The Travis CI job should run the Scala implementation against all test files.

@MichaelCurrie - Travis kind of sucks at multi-language projects in its nice set-things-up-for-you scripts only work for a single language, so you have to do the installations yourself for all languages past the first.
One idea would be, since Scala looks to be the hardest to install, to the language to Scala, then install Python and possibly Julia by hand.  But then the feature matrix is going to be a little wonky.
An alternate idea is to decide that only Python's getting CI treatment.  But then the Python ought to validate the WCON_format.md examples.  (Then one is responsible for running sbt test before checking in a Scala PR, and similarly for Julia etc..)
Or we could try using different CI services for different languages.  Kind of weird, but ironically it might be the simplest and best solution.
Thoughts?

From Tomas Zezula's blog and this conversation on Travis-CI's GitHub site, it seems like one approach would be to use Python as the "master" language but then within the test .travis.yml script, install scala, and run its tests as well:
before_install:
- sudo apt-get update
- sudo apt-get install scala
script: "./whatever/you/run/tests/with"

I've got the Python test suite checking all the JSON snippets in the .MD files as per issue #34.  If you want to add testing for Scala, etc, and I agree it would be great to give it the full "CI treatment" as you say, I think the above would be the simplest approach.

Python is easier to install than Scala, because everything in Scala is built with SBT, but Linux distributions generally don't package SBT.  Also, Scala + dependencies is a bigger download than Python, so it's less efficient.  So if we go with multiple languages, it should almost certainly be Scala by default with others added.
I'm just not convinced that this is the way to go as opposed to multiple different CI services.

In that case I'm happy to go along with the approach you decide here; even if it means subordinating Python within the Travis CI file that's no problem, or perhaps going with multiple CI services.  Let me know if you need anything from me.

I'm going to try a second CI service.  I like how well the Python feature matrix works, so I'd rather just leave the current CI alone.  If we don't have CI for Scala, I don't think it's a disaster; the protocol can just be "run sbt test before you check in".  It will occasionally get forgotten, but it's not that big a burden.  (It only takes a few seconds.)

Resolved by testing Scala with Semaphore CI.  Build status tag delivered via https://github.com/openworm/tracker-commons/pull/56


are you interested in freelancing?

@acbull

Sorry, what do you mean by "freelancing"?

i have a task that i want to solve using graph neural networks.
dealing predicting the reading-order
are you interested?

If you want to use my previous work to solve it, I'm glad to discuss the details, but I cannot directly work on them.


How can I backup and restore tags info when reinstall files

What feature or improvement do you think would benefit Files?
I tried to export settings, then I totally clean reinstall files and import the setting zip, but all of my tags missed, is this expected?
So how can I backup my tags info?
Requirements

This proposal will backup tags info and which file has which tags info, so that when clean install files I can restore all tags system

Files Version
<IP_ADDRESS>
Windows Version
Edition	Windows 11 Pro Version	23H2 Installed on	3/19/2024 OS build	22631.3880 Experience	Windows Feature Experience Pack 1000.22700.1020.0
Comments
No response

Just checked, it is also not in settings > Tags, totally disappeared

I mean those new tags created by myself disappeared, the default one still there

Can you send the filetags.json file from your export zip. You may have to rename to .txt to upload


dictionary_pickle not available

I was trying to work with the pre-trained embeddings but was unable to do that since the dictionary_pickle file is not provided in the repository. I don't see a way to generate the dictionary without having to train the embeddings as well.

I found the issue.
https://github.com/socal-ucr/ncc/blob/871239faa5f882db41caa3ed59f95e0795c3f324/task_utils.py#L38
This line defines the vocabulary directory as published_results/vocabulary when it should be data/vocabulary.

Since the link to the dictionary file appears in the published_results README (it is too large to store in the repository), that's where it is loaded from by default.
It seems that the server where the file is hosted is down at the moment, we are looking into this. Thanks for reporting!

Just checked and the file is available online. Closing this issue for now. Please let us know if we should reopen.


Response interceptor not triggering when using OpenAI tools

Hey Ovidijus,
I've been trying to implement the response interceptor ( as described on https://deepchat.dev/docs/interceptors#responseInterceptor ).
Everything works well without tools, but when I add a tool, the interceptor doesn't trigger for the OpenAI response anymore.
For example, in my case, the interceptor is triggered for the tool call:
{
   "id":"chatcmpl-454564641878945465",
   "object":"chat.completion",
   "created":1706708920,
   "model":"gpt-4-0125-preview",
   "choices":[
      {
         "index":0,
         "message":{
            "role":"assistant",
            "content":null,
            "tool_calls":[
               {
                  "id":"call_123456789",
                  "type":"function",
                  "function":{
                     "name":"get_current_weather",
                     "arguments":"{\"location\":\"New York\",\"unit\":\"metric\"}"
                  }
               }
            ]
         },
         "logprobs":null,
         "finish_reason":"tool_calls"
      }
   ],
   "usage":{
      "prompt_tokens":81,
      "completion_tokens":19,
      "total_tokens":100
   },
   "system_fingerprint":""
}

Then, I return a result formatted like this:
[
   {
      "response":"{\"location\":\"New York\",\"temperature\":\"12.5\"}"
   }
]

However, I'm not able to retrieve the follow-up reply because the interceptor is not triggered.
{
  "id": "chatcmpl-456456456421689489",
  "object": "chat.completion",
  "created":<PHONE_NUMBER>,
  "model": "gpt-4-0125-preview",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "The current temperature in New York is 12.5°C."
      },
      "logprobs": null,
      "finish_reason": "stop"
    }
  ],
  "usage": {
    "prompt_tokens": 64,
    "completion_tokens": 12,
    "total_tokens": 76
  },
  "system_fingerprint": ""
}

Am I missing something, or is this behavior expected?
Thank you for your assistance.
Best

Hi @devpulse01.
I have updated the interceptor code for OpenAI Assistants and published it to version 9.0.119 of deep-chat-dev and deep-chat-react-dev packages. Can you let me know if that works for you.
Thanks!

Oh, my bad, I'll see what I can change there.

I've made the change in version 9.0.121. Let me know if this works for you.

That makes sense, I made this change in 9.0.122.

Everything is working perfectly. Thank you so much!

Glad to hear it works! I'll include this code in the next release. Thanks!

This has now been deployed in Deep Chat version 1.4.11. See the release notes for more.


AntiDupl Recycle Bin for Replaced Images`

Is it possible to to set AntiDupli to send the replaced image to the Recycle Bin?

Hi! If you send replaced image to Recycle Bin you can't then restore it because there will another image with the same name. So this functionality can't work properly.

Couldn't the name be sent to the recycle bin with a different name (like image-r.jpg?)


Storage specification doesn't seem to support values coming from variables

Description
When setting the storage value from a variable, terraform complains about the value not being a string, even though the variable type is a string:
variable "postgresql_storage"{
  type    = string
  default = "2G"
}
...
storage_directives = {
      pgdata = var.postgresql_storage
}
# complains about the type of pgdata

if i set the value of pgdata directly, without using a variable, it works correctly.
storage_directives = {
      pgdata = "2G"
}

Urgency
Blocker for our release
Terraform Juju Provider version
0.13.0
Terraform version
v1.7.2
Juju version
3.4.4
Terraform Configuration(s)
#variables.tf
variable "postgresql_storage"{
  type    = string
  default = "1G"
}

# main.tf
terraform {
  required_version = "~> 1.7.2"
  required_providers {
    juju = {
      version = "0.13.0"
      source  = "juju/juju"
    }
  }
}

resource "juju_application" "postgresql-k8s" {
  name  = "postgresql-k8s"
  model = "test"
  trust = true

  charm {
    name     = "postgresql-k8s"
    channel  = "14/stable"
    revision = 198
  }

  storage_directives = {
      pgdata = var.postgresql_storage
  }

  units       = 1
}

Reproduce / Test
# on a k8s controller
juju add-model test
terraform init && terraform apply

Debug/Panic Output
Error: Value Conversion Error
│
│   with juju_application.postgresql-k8s,
│   on main.tf line 11, in resource "juju_application" "postgresql-k8s":
│   11: resource "juju_application" "postgresql-k8s" {
│
│ An unexpected error was encountered trying to build a value. This is always an error in the provider. Please report the following to the provider developer:
│
│ Received unknown value, however the target type cannot handle unknown values. Use the corresponding `types` package type or a custom type that handles unknown values.
│
│ Path: ["pgdata"]
│ Target Type: string
│ Suggested Type: basetypes.StringValue

Notes & References
No response

Is this a regression from something that used to work? If so I don't think we can treat it as a blocker vs desired functionality.

@gtato, are we sure that we are using terraform vars here correctly. Because I think we should use the var with the same type as a attribute in schema to pass Conversion.
There is the usage of terraform vars that passed for me:
terraform {
  required_providers {
    juju = {
      source  = "juju/juju"
      version = "0.14.0"
    }
  }
}
provider "juju" {}

resource "juju_model" "tf-test" {
  name = "tf-test"
}

variable "pgstorages" {
  type = map
  default = {
    "files"  = "2G"
  }
}

resource "juju_application" "test-app-storage" {
  model = juju_model.tf-test.name
  name = "test-app-storage"
  charm {
    name = "ubuntu"
    channel = "latest/stable"
    revision = 24
  }

  storage_directives = var.pgstorages

  units = 1
}

Is it make sense for your case?

I am okay with using variables like that, but I don't think that should be the only way to pass variables.
For config for example we can do both, we can pass each config as an individual variable, or pass the whole config as a single object variable:
# option 1
config = {
   x = var.x
   y = var.y
}
...
# option 2
config = var.config


Add style tag for style.css

Vite generates a style.css chunk when build.cssCodeSplit is disabled
https://github.com/vitejs/vite/blob/main/packages/vite/src/node/plugins/html.ts#L682-L698

Good to know, and nice fix! I'll merge and push up a new release :)


[Event Request] codeunit 108 "Net Cust/Vend Balances Mgt." - OnNetBalancesBeforeSetVendorRemainingAmount

Describe the request
Hello, can you please add a new Event OnNetBalancesBeforeSetVendorRemainingAmount codeunit 108 "Net Cust/Vend Balances Mgt."?
    local procedure NetBalances(var VendLedgEntry: Record "Vendor Ledger Entry"; var CustLedgEntry: Record "Cust. Ledger Entry"; var VendorRemainingAmount: Decimal; var CustomerRemainingAmount: Decimal; var TempNetAmount: Decimal);
    var
        MinNetAmount: Decimal;
    begin
        NetAmount := NetAmount - TempNetAmount;
        if VendorRemainingAmount = 0 then
            VendLedgEntry.FindFirst();
        if CustomerRemainingAmount = 0 then
            CustLedgEntry.FindFirst();
        repeat
            if VendorRemainingAmount <= 0 then begin
                SetOnHold(VendLedgEntry);
                VendLedgEntry.CalcFields("Remaining Amount");
                OnNetBalancesBeforeSetVendorRemainingAmount(VendLedgEntry);
                VendorRemainingAmount := -VendLedgEntry."Remaining Amount";
                InsertGenJnlLine(VendorGenJnlLine, VendLedgEntry, CustLedgEntry, true);
            end;

    [IntegrationEvent(false, false)]
    local procedure OnNetBalancesBeforeSetVendorRemainingAmount(var VendorLedgerEntry: Record "Vendor Ledger Entry")
    begin
    end;

Additional context
We have additional values to calculate the Remaining Amount of the Vendor Ledger Entry and need to recalculate it before being allocated.
Internal work item: AB#547390

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 24468.

Availability update: We will publish a fix for this issue in the next update for release 25.
Build ID to track: 24487.


Support for custom html meta

Fix for #1204
Custom HTML meta tags can be defined in app.ini
[ui.meta]
AUTHOR = Gitea - Git with a cup of tea
DESCRIPTION = Gitea: Git with a cup of tea
KEYWORDS = go,git,self-hosted,gitea

LGTM

LGTM

Missing in the docs: https://docs.gitea.io/en-us/config-cheat-sheet/
Somebody can update the docs please :+1:  ??!

@danger89 PRs are welcome


Apply section name check to sections only

Why is this the best possible solution? Were any other approaches considered?
#511 is a helpful solution to #510, providing less-confusing error text when a group name matches the root node name, but it also ensnared (unintentionally?) regular question names. Other approaches considered and rejected were:

Reverting #511, losing a valuable addition to pyxform and ignoring the problem described in #510;
Doing nothing, and thus requiring unnecessary changes to forms that worked with pyxform prior to v1.3.4.

What are the regression risks?
Some unknown tool could depend on the recently-added check that prevents question names from equaling the form name.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No; however, if this PR is undesirable, then the documentation should be updated to reflect the new restriction on question names.
Before submitting this PR, please make sure you have:

[x] included test cases for core behavior and edge cases in tests_v1
[x] run nosetests and verified all tests pass
[x] run black pyxform to format code
[x] verified that any code or assets from external sources are properly credited in comments

Indeed, thank you! I had missed @pbowen-oc's https://github.com/XLSForm/pyxform/issues/510#issuecomment-763063318 to that effect.
Could you please add a test very similar to https://github.com/XLSForm/pyxform/pull/511/files#diff-2f87b2f8ddd9e41e8ebf5bf45472a415f5d2744e146a487aa0516762c79c47cf that verifies that a field name that matches the root node name is accepted?

Sure :) I added one just now. Should I also check the generated XML, or is it enough as-is? I started writing that but threw it away, thinking that it'd add brittleness and duplicate other tests

Codecov Report

Merging #529 (d606704) into master (43ea039) will not change coverage.
The diff coverage is 50.00%.

:exclamation: Current head d606704 differs from pull request most recent head 3e37c32. Consider uploading reports for the commit 3e37c32 to get more accurate results

@@           Coverage Diff           @@
##           master     #529   +/-   ##
=======================================
  Coverage   83.94%   83.94%
=======================================
  Files          25       25
  Lines        3719     3719
  Branches      867      867
=======================================
  Hits         3122     3122
  Misses        452      452
  Partials      145      145

Impacted Files
Coverage Δ

pyxform/survey.py
92.54% <50.00%> (ø)

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 43ea039...3e37c32. Read the comment docs.

I might add errored=False

Aye, aye :+1: I don't want to get run out of town or anything :laughing:

Fine with me. Thanks! 👍

@lognaturel - We would like this update, but there is no urgency on it.


Make support() synchronous

Based on feedback from @ddorwin and @leandromoreira, we should make support() synchronous.
According to https://github.com/w3c/encrypted-media/issues/178#issuecomment-216299258 and https://github.com/w3c/encrypted-media/issues/178#issuecomment-220381909, we should not be probing EME.  Probing EME may result in lots of prompts on some browsers, leading to a bad UX.  Since app devs don't really need this info anyway, it's fine to skip probing EME in support().
According to https://github.com/clappr/dash-shaka-playback/issues/4#issuecomment-207183093, having an asynchronous support() call is inconvenient.  Since the only asynchronous part of it is the EME probe, we can make things simpler for developers by removing that.
Since EME probes are still useful for platform diagnostics, we should move any EME probes to a separate method.  That method should be named in such a way that it is clearly not to be used in production.  In contrast, checking basic library support should definitely be done in production.

I disagree about EME probing.  I think this is a very real use-case to be able to determine key-system support early.  In the demo app, we disable assets that the browser does not support.  If we stopped EME probes, we would be unable to do this.
An app would need to wait until it tries to play a manifest before it could determine if the browser supported the key-system.  Plus, it would need to listen to Player error events and have special code to check for the error code and do something different.  As opposed to currently, where it can detect it before it even creates a Player.
I agree we should split up support() into a synchronous version and an async version.  But, I think we should keep EME probes (for production).  Maybe we should modify the way we do it.  Instead of probing all key systems with empty configs, what about accepting an array of DrmInfo and using that to construct the EME query.  This will mirror the query we will do later and allow apps to detect the exact support they want.  Plus, the support method will only probe the key-systems that the app needs.

It is very useful for our demo app to screen which assets are playable based on key system.  However, I'm not sure this is a common scenario for most app developers.
A real application's content catalog is generally under their complete control, and is not likely to be segmented into pieces by key system.  Our demo content is mostly third-party, and the content we encoded ourselves is not currently multi-DRM.  So I don't think our demo app is representative of the needs of a typical video-streaming service.
I believe most real applications will be serving all content with the same key systems.  For example, a catalog of DASH content may be all Widevine-encrypted, or all Playready-encrypted, or all multi-DRM using a specific set of DRM providers across all content.

worked like a charm. Did you think about create a gem for Shaka?

What's a gem?

Rails Gem.

Sorry, rails is not on our roadmap.

no problem, just curiousity. thanks again sir.


fix(cli): handle empty files

Gracefully handle empty files uploads.
Closes https://github.com/chainloop-dev/chainloop/issues/380

Waiting for the fix we agreed on

@buccarel ptal, it seems that the fix is now up.


Enforce white background for logo - fixes #627

This is to ensure that there is always an appropriate level of contrast.
The lack of contrast is an issue both on Windows and Linux with dark themes.
Here's an example:

Thanks for your contribution. I think we should create a new asset instead specifically for the Windows icon. The images in the assets are used in multiple ways so the risk for unintended side effects are too high.
I will use your image and make the necessary changes for you.


docs(/contact-us): add Discord server invite link

Closes #2023
Adds a Discord server invite link to the /contact-us page. Worth noting is that it's above our Slack links which led off the section previously. Made sense to me to have our first point of contact reachable as an open source project, but happy to adjust if I need to.

At a loss on this one here. Cleared cache, scrapped yarn lock, triple checked my Node version and reinstalled 🤷

@dakahn want to just try a new PR? Not sure what the ~20,000 yarn.lock changes are


Support multiline pipeline input (issue #19)

Support piping stuff into the Write-*Log CmdLets.
e.g.
ping localhost -n 5 | Write-InfoLog

See issue #19

CI appears to fail due to an unrelated issue?


Not able to use acorn pull to pull images from registry when it matches  --internal-registry-prefix setting

Acorn version - acorn version v0.5.1-49-gdc65d88+dc65d881
Not able to use acorn pull to pull images from registry when it matches  --internal-registry-prefix setting
sangeethahariharan@Sangeethas-MBP example1 % acorn pull docker.io/sangeetha/nnn:xxx
 [56881771/56881771] █████████████████████████████████████████████████ 100% | 2s
sangeethahariharan@Sangeethas-MBP example1 %  acorn install --internal-registry-prefix=docker.io/sangeetha/
  ✔  Running Pre-install Checks
  ✔  Installing ClusterRoles
  ✔  Installing APIServer and Controller (image ghcr.io/acorn-io/acorn:v0.5.1-49-gdc65d88)
  ✔  Waiting for controller deployment to be available
  ✔  Waiting for API server deployment to be available
  ✔  Running Post-install Checks
  ✔  Installation done

sangeethahariharan@Sangeethas-MBP example1 % acorn pull docker.io/sangeetha/nnn:xxx
  ✗  ERROR:  websocket: close 1011 (internal server error): invalid image reference prefix docker.io/sangeetha/nnn:xxx

from @ibuildthecloud:

I think this behavior is by design.  Maybe there's some nuisance that needs to be fixed but in general if the prefix is set we don't users directly pulling/pushing/using the prefix.

there's explicit code that says "if it start's with prefix fail"

So, perhaps just an improved error message to explain what's going on


Add Spring Security support

See related #289 issue.

windows  platform , graalvm-ce-java11-20.2.0 and spring-graalvm-native-0.8.2 . I'm working on building a working project to exe for quite a few days and encounter many problems. current is , when I compiled to native exe and run , it prints:
java.lang.IllegalStateException: java.security.NoSuchAlgorithmException: RSA KeyFactory not available
at org.springframework.security.converter.RsaKeyConverters.rsaFactory(RsaKeyConverters.java:135) ~[na:na]
at org.springframework.security.converter.RsaKeyConverters.pkcs8(RsaKeyConverters.java:71) ~[na:na]
at org.springframework.security.config.crypto.RsaKeyConversionServicePostProcessor.pkcs8(RsaKeyConversionServicePostProcessor.java:88) ~[na:na]
at org.springframework.security.config.crypto.RsaKeyConversionServicePostProcessor.postProcessBeanFactory(RsaKeyConversionServicePostProcessor.java:65) ~[na:na]
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:299) ~[na:na]
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:185) ~[na:na]
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:751) ~[na:na]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:569) ~[na:na]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:144) ~[na:na]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:770) ~[na:na]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:762) ~[na:na]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:421) ~[na:na]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:329) ~[na:na]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1302) ~[na:na]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1291) ~[na:na]
at com.kingbase.AppRun.main(AppRun.java:55) ~[com.kingbase.apprun.exe:na]
Caused by: java.security.NoSuchAlgorithmException: RSA KeyFactory not available
at java.security.KeyFactory.(KeyFactory.java:138) ~[na:na]
at java.security.KeyFactory.getInstance(KeyFactory.java:183) ~[na:na]
at org.springframework.security.converter.RsaKeyConverters.rsaFactory(RsaKeyConverters.java:132) ~[na:na]
... 15 common frames omitted

Thanks for reaching out @doujs.
We're still actively working on adding Spring Security support.
Can you share some more information on the type of application you are building?
Is it a servlet app or reactive? What kind of security are you using? Form login, OAuth2?

I've found you need to add --enable-https to solve this issue.
<plugin>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-maven-plugin</artifactId>
    <configuration>
        <image>
            <env>
                <BP_BOOT_NATIVE_IMAGE>1</BP_BOOT_NATIVE_IMAGE>
                <BP_BOOT_NATIVE_IMAGE_BUILD_ARGUMENTS>
                    -Dspring.native.remove-yaml-support=true
                    -Dspring.spel.ignore=true
                    --enable-https
                </BP_BOOT_NATIVE_IMAGE_BUILD_ARGUMENTS>
            </env>
        </image>
    </configuration>
</plugin>

https://github.com/okta/okta-spring-boot/issues/192#issuecomment-696485752

@mraible Thanks for your feedback. We kind of document that but we could probably make that more discoverable.
@eleftherias We could maybe also work on setting that automatically when needed via #225.

@mraible thank you very much , it works now , but i'm encounting another error ,  checking....
@eleftherias It's a servlet app[spring mvc] and Form login.

@doujs Have you looked at the security sample in this repo? It is also a servlet app with form login. https://github.com/spring-projects-experimental/spring-graalvm-native/tree/master/spring-graalvm-native-samples/security
@sdeleuze Yes, I like the idea of setting the flag automatically.

@eleftherias yes , I have read the samples and the docs . I didn't start from the sample but from our working project , so I didn't notice thant . Besides , I think maybe it's better to put the arguments together and tell when to use them , maybe it's better to give an example

We could indeed probably improve our documentation for now, I have created the related #352 issue.

according to the example project for spring security you need to add the --enable-all-security-services (found it in the compile.sh).
had the same error as described and setting the flag at native-image helped. (i'm running a servlet app with basic auth)

@eleftherias As discussed previously, I have added required flags for dependency using a starter by starter granularity to the support documentation. Since master branch is now targeting 0.9.0-SNAPSHOT, feels free to add Spring Security  starter with the limitation of the support and the potentially required flags.
For HTTPS, I think --enable-https should be favored against -H:EnableURLProtocols=http,https (I think this is equivalent but to be checked). It would be helpful to identify when --enable-all-security-services is required (always?).
We can relax the documented limitations as this support progress.

Closing this issue, since initial Spring Security support is available.
This issue encompasses:

Form login
HTTP basic authentication
OAuth 2.0
RSocket Security
Kotlin Security DSL for WebMvc applications

For any additional features new issues should be created.

Closing this issue, since initial Spring Security support is available.
This issue encompasses:

Form login
HTTP basic authentication
OAuth 2.0
RSocket Security
Kotlin Security DSL for WebMvc applications

For any additional features new issues should be created.


Secor stops processing new messages

We are running secor 0.27 in production for past 6-7 months. The message in rate of the topic secor is subscribed to is 1.2K/s avg and min-max of 0.3K - 2K.
Everything was running fine till yesterday. Yesterday all of a sudden secor stops processing messages. There is nothing in the logs. However, when I restart the java process, it does start processing for very few second and then again stops.

The small towers are the time when I restarted the java process.
Here I am attaching INFO log of whole one cycle where it starts consuming for few seconds and then goes idle. I have also attached the config file used for secor.
The Kafka version we are using is 1.0.0 and ZK version is 3.4.10
I strange thing I noticed is with latency of one ZK node. We have 5 ZK nodes, and out of that one is showing very high max latency as below.
ZK1 follower Latency min/avg/max: 0/0/49
ZK2 follower Latency min/avg/max: 0/0/787
ZK3 follower Latency min/avg/max: 0/0/7
ZK4 follower Latency min/avg/max: 0/0/125
**ZK5 leader Latency min/avg/max: 0/0/4929**

Could this be the issue ?
Log logs-insights-results.txt
Config
secor.common.properties.txt
Does anyone see something fishy here ?

We restarted the high latency ZK5 node and now latency of all node is between 2-24.

Was the issue resolved by bouncing ZK nodes?


Disable being able to set the automatic adjustment of indistinguishable text

Summary of the Pull Request
Disables the automatic adjustment of indistinguishable text (added in #11095) because of the concerns brought up in #11917. Also, the setting is hidden in the SUI for as long as this feature remains disabled.
PR Checklist

[ ] Closes #xxx
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx
[ ] Schema updated.
[x] I work here

Sorry, I think my PR #12127 has messed things up a bit for you here. The color adjustment code has now been moved into a new RenderSettings class. Hopefully it shouldn't be too much effort to reincorporate these changes there.

Was going to merge, but want to see @PankajBhojwani address @carlos-zamora's questions.

oop!

My bad, this slipped my mind while trying to get #12144 ready for the bug bash. Will file a separate PR to make this a preview-only feature that's disabled by default as per @carlos-zamora's suggestion


Gradle 8 Support

The library does not support Gradle 8 and above, I ran into a few problems.
Task :app:localization FAILED
Caching disabled for task ':app:localization' because:
  Caching has not been enabled for the task
Task ':app:localization' is not up-to-date because:
  Task has not declared any outputs despite executing actions.

Execution failed for task ':app:localization'.
> Could not get unknown property 'outputDirectory' for task ':app:localization' of type pl.droidsonroids.gradle.localization.LocalizationTask.

Could you attach a reproducer project?

thanks, i have example project, https://github.com/MotiElitzur/Example-App

I could not reproduce that issue with that project.


Wrong ESM exports

Describe the bug
I'm using open-telemetry instrumentation with esm that is using import-in-the-middle library. The library parses output from each module and proxies every export to give ability to patch.
How to reproduce

Use esm in node
Register import-in-the-middle
Try to use @ts-rest/fastify or @ts-rest/core

Expected behavior
I guess it's happening because of wrong "exports" fields. If i delete "exports" field everything works fine. The issue is that "import" property is not an actual esm its just reexport of cjs module.

Code reproduction
https://github.com/DataDog/import-in-the-middle/issues/107
ts-rest version
3.45.2

It is a very common strategy to create an ESM wrapper for a CJS module (called faux ESM) and is actually recommended (see this). So this is what the ".cjs.mjs" files are. The pure/true ESM files defined in "exports.module" are only used by bundlers and are there to help with tree shaking in order to reduce the size of frontend packages.
Our libraries work in all environments and configurations, so there is nothing to fix or change really and it's a problem with import-in-the-middle for sure.


Add window.postMessage support v2

This is our contribution to the existing https://github.com/Chainlit/chainlit/pull/1162.
Our updates

Added a window_message e2e test validating 2-way messaging
Post the server message to the window parent even if it's the same as the iframe window, which is the case in our e2e tests.
Initialize the session context so we can use the user_session in on_window_message
Added missing stub in BaseChainlitEmitter

Original pull request:
Description
This update enhances the functionality of the Chainlit application when it is embedded within another web application via an iframe. By enabling message exchange between the parent and child windows, the application can now support extended features. Some examples of the use cases would be; allowing users to select datasets from their dashboard, supply saved prompts, and more.
Changes

Added an event listener listening for window message events in AppWrapper.tsx.
Added a callback to emit the window_message event in useChatInteract.ts
Added a new decorator on_window_message to init.py
Added the callback for the decorator in config.py
Added a socket io event window_message in socket.py
Add support for 2-way messaging (cl.send_window_message)

@jfperusse-bhvr Super! In addition to the E2E tests, we'll need to do manual tests.
Would you be able to give test instructions and/or code, so I can see this wonderful feature demonstrated on my local machine?
A good way to go about this would be to make a PR to the documentation where the general idea is explained and a minimal example is given. We can then use it to evaluate and test the feature.
Really nice to see this coming, I'm sure many users will benefit. And appreciate your help in QA!

Thanks @dokterbob! I will look into adding a simple example to the cookbook.

Added a sample to the cookbook, see https://github.com/Chainlit/cookbook/pull/154.

@mauanga Any chance you would like to help us testing by giving @jfperusse-bhvr's cooking entry a try?

@mauanga Any chance you would like to help us testing by giving @jfperusse-bhvr's cooking entry a try?
You can install chainlit straight from this repo branch (as per README instructions).

@dokterbob Let me know if I can help you test this so we can move forward with the PR.

Tested the cookbook entry. Great work, thanks!
@jfperusse-bhvr Would it be possible for you to also fire a PR against the docs? Thanks again!

@dokterbob Is this PR what you are looking for: https://github.com/Chainlit/cookbook/pull/154 ?

@dokterbob I documented the feature under webapp, PR at https://github.com/Chainlit/docs/pull/194.


python311Packages.aiolifx-themes: 0.4.9 -> 0.4.10

Diff: https://github.com/Djelibeybi/aiolifx-themes/compare/refs/tags/v0.4.9...v0.4.10
Changelog: https://github.com/Djelibeybi/aiolifx-themes/releases/tag/v0.4.10
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 270178 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.lifx
python310Packages.aiolifx-themes
python310Packages.aiolifx-themes.dist
python311Packages.aiolifx-themes
python311Packages.aiolifx-themes.dist


Markdown Highlighting

Would be good if we could get Highlighting for Markdown front matter sections (for Jekyll, etc.) within files set to the HTML (Liquid) syntax.

Maybe this is something that has to bee added to the Markdown syntax xml—using Content Match Detectors?
https://docs.nova.app/syntax-reference/syntaxes/#content-match-detectors

Sorry for the belated response! I'm not around my Mac right now, but I'll look it this next Saturday and try some things, for sure! I think I can do something similar with #3.

Just released v1.2 with a new Markdown (Liquid) syntax, which highlights Liquid syntax in your Markdown files. There are still two issues:

For some reason, I can't find a way for Nova to detect Liquid tags and variables to choose the proper syntax automatically like it happens with HTML (Liquid), so you need to choose Markdown (Liquid) manually in your Editor Syntax selector.
I also can't figure it out how to prevent Nova from interpreting 4 spaces tabbing as a Markdown code, which prevents Liquid highlighting.

I'll look into these issues to release a fix whenever I can, but if you manage to find out how to, I would love some help!

Awesome. Will take a look at the other issues.

Yeah, I've added in detectors for filetypes and opening tags and still doesn't seem to work. What's more—I can't seem to get some other extensions to extend to liquid-markdown as a syntax. (specifically the  tailwind, and emmet extensions). Not sure what the problem is.

err...actually I take that back, sorry! Was able to get them to extend to both liquid-html and liquid-markdown.

Yay! You can create an PR with this fix if you want, I'd love to check what went wrong with my approach.


Enable multiple partner servers and failover of read-only endpoint for SQL DB Failover Group in version 2023-02-01-preview.

ARM API Information (Control Plane)
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month (August).
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Note that this doesn't apply if you are trying to merge a PR that was previously in the private repository.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

we are asking exception for these resource name restriction rules; because SQL RP has not enabled this restriction feature

❌ ResourceNameRestriction
The resource name parameter 'serverName' should be defined with a 'pattern' restriction.Location: Microsoft.Sql/preview/2023-02-01-preview/FailoverGroups.json#L403
RPC-Uri-V1-05

❌ ResourceNameRestriction
The resource name parameter 'failoverGroupName' should be defined with a 'pattern' restriction.Location: Microsoft.Sql/preview/2023-02-01-preview/FailoverGroups.json#L403
RPC-Uri-V1-05

@lobash Please contact Breaking Change Board owner to review the breaking change in this PR, you can follow this comments.
And, contact the ARM team to review the lintdiff error. If it's ok, let them to add label Approved-LintDiff.

@JeffreyRichter Please help review the breaking change in this PR.

@lobash Please contact the ARM team to review the lintdiff error. If it's ok, let them to add label Approved-LintDiff.

@v-xuto can you please paste the alias of ARM team or some point of contact from the ARM team to get the lint diff approved?

@mentat9 Could you help review the LintDiff error? If you feel okay, please add label Approved-LintDiff. Thanks a lot.

we are asking exception for these resource name restriction rules; because SQL RP has not enabled this restriction feature
❌ ResourceNameRestriction	The resource name parameter 'serverName' should be defined with a 'pattern' restriction.Location: Microsoft.Sql/preview/2023-02-01-preview/FailoverGroups.json#L403	RPC-Uri-V1-05
❌ ResourceNameRestriction	The resource name parameter 'failoverGroupName' should be defined with a 'pattern' restriction.Location: Microsoft.Sql/preview/2023-02-01-preview/FailoverGroups.json#L403	RPC-Uri-V1-05

@mentat9 FYI for the LintDiff error.

@mentat9 Could you help review the LintDiff error? If you feel okay, please add label Approved-LintDiff. Thanks a lot.

@ms-zhenhua is oncall this week.

@mentat9 Could you help review the LintDiff error? If you feel okay, please add label Approved-LintDiff. Thanks a lot.

@ms-zhenhua is oncall this week.

@v-xuto, @lobash - I just noticed nobody applied the WaitForARMFeedback label, so this PR won't be on ARM review's radar. I added the label for you.

        "pattern": "^[a-z][a-z0-9]*$",

The "pattern" property is required for a resource name:
https://github.com/Azure/azure-openapi-validator/blob/main/docs/resource-name-restriction.md

Refers to: specification/sql/resource-manager/Microsoft.Sql/preview/2023-02-01-preview/FailoverGroups.json:423 in aa09213. [](commit_id = aa09213a404735f49a49750d213c6209a347a118, deletion_comment = True)

        "pattern": "^[a-z][a-z0-9]*$",

Why delete these properties? The "pattern" property is required for a resource name: https://github.com/Azure/azure-openapi-validator/blob/main/docs/resource-name-restriction.md
Refers to: specification/sql/resource-manager/Microsoft.Sql/preview/2023-02-01-preview/FailoverGroups.json:423 in aa09213. [](commit_id = aa09213, deletion_comment = True)

@ms-zhenhua  added you to an email thread.

        }

The location header is required for 202:
https://github.com/Azure/azure-openapi-validator/blob/main/docs/lro-location-header.md

Refers to: specification/sql/resource-manager/Microsoft.Sql/preview/2023-02-01-preview/FailoverGroups.json:450 in aa09213. [](commit_id = aa09213a404735f49a49750d213c6209a347a118, deletion_comment = True)

        }

The location header is required for 202: https://github.com/Azure/azure-openapi-validator/blob/main/docs/lro-location-header.md
Refers to: specification/sql/resource-manager/Microsoft.Sql/preview/2023-02-01-preview/FailoverGroups.json:450 in aa09213. [](commit_id = aa09213, deletion_comment = True)

Can we ask for an exception for these newly added ARM rules (to pipeline)? All SQL RP's manifests are auto-generated via C# reflection. We are adding this location property in the next API version: 2023-05-01-preview. Thanks!

@mentat9 Could you help review the LintDiff error? If you feel okay, please add label Approved-LintDiff. Thanks a lot.

@v-xuto can we please get an approval for the PR now? The Approved-LintDiff label has been applied by the ARM team. Thanks.

@lobashh please check why eaf29c4c7f8a0f0cc8487f8f558998b70aaa66ee introduced new broken pipeline

@lobashh please check why eaf29c4 introduced new broken pipeline.
and normally, we do not manually edit any auto-generated swagger file. We just ask for exception from reviwers.

I think my manual edit introduced a whitespace character on the first line. I have pushed an update to fix the same in commit 5.

/azp run

Same azure-sdk-for-net-track2 error as PR #23802. We can ignore the failure of .NET track 2 automation for sql all the time.
For more details, check comments #23802 (comment).

@qiaozha  Please help review JS breaking change.
@raych1  Please help review Go breaking change.
@msyyc  Please help review Python breaking change.


Update ConvertTo-ARMTemplate.ps1 for parallelism

Change
Feel free to remove this sample text

Thank you for your contribution !

Uncommented parallelism in the ConvertTo-ARMTemplate before SPARK Lab
Type of Change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update (Wiki)

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] My corresponding pipelines / checks run clean and green without any errors or warnings
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas ( I dont believe there is a pipeline for this?)
[x] I have made corresponding changes to the documentation (readme)
[x] I did format my code

Is this PR became stale, I'll close it for now


Default TabBar indicatorColor should contrast with its background

Running the example provided here  https://flutter.io/cookbook/design/tabs/ fails if the TabBar's indicatorColor isn't explicitly set to white.
This is a regression.

This appears to have be an inadvertant side-effect of https://github.com/flutter/flutter/pull/15265

This affects v0.2.4 (and probably v0.2.5 depending on when the fix lands).  Does this make for a Bad Build?

Yes, this was a serious regression.


empty string as translation language

The empty string is listed as a translation language and cannot be removed. This has the unfortunate effect of taking up the first result on every translation :(
Thanks for the great work on this. It's much appreciated!

As a workaround, I directly edited the file ~/Library/Application Support/Alfred 3/Workflow Data/com.spr.translate.api/config.ini


#106 fix: The ability to start appium server programmatically

Change list is below:

The namespace OpenQA.Selenium.Appium.Service with designed classes was added;

The class OpenQA.Selenium.Appium.Service.AppiumLocalService was designed. It implements OpenQA.Selenium.Remote.ICommandServer;

AppiumDriver and subclasses were refactored. New constructors were added.

almost all tests were redesigned. iOS tests are supporting iOS 8.2. Some new test were added.

Requirements

Installed Node.js.

At least an appium server instance installed via npm.

Which capabilities these features provide
Proposed features provide abilities and options of the starting of a local Appium node server. End users still able to open apps as usual
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.SetCapability(MobileCapabilityType.PlatformVersion, "6.0");
capabilities.SetCapability(MobileCapabilityType.DeviceName, "Android Emulator");
capabilities.SetCapability(MobileCapabilityType.App, app);
driver = new AndroidDriver<AppiumWebElement>(new Uri("desired remote or local URL"), capabilities, timeSpanForTheResponse);

when the server works locally\remotely. Now they are free to launch a local Appium node server and open their app for the further testing the following way:
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.SetCapability(MobileCapabilityType.PlatformVersion, "6.0");
capabilities.SetCapability(MobileCapabilityType.DeviceName, "Android Emulator");
capabilities.SetCapability(MobileCapabilityType.App, app);
driver = new AndroidDriver<AppiumWebElement>(capabilities, timeSpanForTheResponse);

How to prepare the local service before the starting
If there is no specific parameters then
using OpenQA.Selenium.Appium.Service;
...

AppiumLocalService service = AppiumLocalService.BuildDefaultService();
service.Start();
 ...
service.Dispose();

Requirements(!!!):

make sure that the path to node.js is defined at the PATH environmental variable and there is an Appium server instance installed via NPM

OR

please set up the NODE_BINARY_PATH environmental variable. Here should a full path to the node.js executable file.  This usecase is very useful for platforms which differ from Windows. There are possible unpredictable issues related to user's environmental settings. Also it is useful then the instance of non-default (it is not defined at the PATH, it is the another node.js modification such as NSolod and so on) node.js is requred. Also it is possible to define the path to not default appium.js via APPIUM_BINARY_PATH environmental variable.

This usecase is possible to perform programmatically like:
using OpenQA.Selenium.Appium.Service;
using System;
...

Environment.SetEnvironmentVariable(AppiumServiceConstants.NodeBinaryPath, "the full path to node.js executable file");
Environment.SetEnvironmentVariable(AppiumServiceConstants.AppiumBinaryPath, "the full path to appium.js");
AppiumLocalService service = AppiumLocalService.BuildDefaultService();
service.Start();
 ...
service.Dispose();

If there should be non default parameters specified then
If non localhost IP address is requred then
using OpenQA.Selenium.Appium.Service;
...

AppiumLocalService service = new AppiumServiceBuilder().WithIPAddress("listenableIP").
                Build();
service.Start();
 ...
service.Dispose();

If the the log file is required for server output
using OpenQA.Selenium.Appium.Service;
using System.IO;
...

AppiumLocalService service = new AppiumServiceBuilder().
WithLogFile(new FileInfo("path\to\log\file")).Build();
service.Start();
 ...
service.Dispose();

If it needs for the port which differs from 4723 then
using OpenQA.Selenium.Appium.Service;
...

AppiumLocalService service = new AppiumServiceBuilder().UsingPort(4000).Build();
service.Start();
 ...
service.Dispose();

or
using OpenQA.Selenium.Appium.Service;
...

AppiumLocalService service = new AppiumServiceBuilder().UsingAnyFreePort().Build();
service.Start();
 ...
service.Dispose();

If it needs to define other server parameters then
using OpenQA.Selenium.Appium.Service;
using OpenQA.Selenium.Appium.Service.Options;
...

OptionCollector args = new OptionCollector().AddArguments(GeneralOptionList.LogNoColors());
AppiumLocalService service = new AppiumServiceBuilder().WithArguments(args).Build();
service.Start();
 ...
service.Dispose();

Actual server flags are listed here. In order to use them easyly they are listed by:

OpenQA.Selenium.Appium.Service.Options.GeneralOptionList - here are common server options
OpenQA.Selenium.Appium.Service.Options.AndroidOptionList - here are Android-specific server options
OpenQA.Selenium.Appium.Service.Options.IOSOptionList - here are iOS-specific server options

Boolean arguments have no parameters. Other server flags require not empty string values.
If it needs to override the default file path to node.js executable and/or the path to appium.js file then
using OpenQA.Selenium.Appium.Service;
...

AppiumLocalService service = new AppiumServiceBuilder().
WithAppiumJS(new FileInfo("the path to the desired appium.js")).
UsingDriverExecutable("the path to the desired node.js executable file").Build();
service.Start();
 ...
service.Dispose();

How to create an AppiumDriver instance
The common constructors are still available
public AppiumDriver(Uri remoteAddress, ICapabilities desiredCapabilities, TimeSpan commandTimeout)

public AppiumDriver(Uri remoteAddress, ICapabilities desiredCapabilities)

There are new constructors:
public AppiumDriver(AppiumLocalService service, ICapabilities desiredCapabilities, TimeSpan commandTimeout)

public AppiumDriver(AppiumLocalService service, ICapabilities desiredCapabilities)

public AppiumDriver(AppiumServiceBuilder builder, ICapabilities desiredCapabilities, TimeSpan commandTimeout)

public AppiumDriver(AppiumServiceBuilder builder, ICapabilities desiredCapabilities)

public AppiumDriver(ICapabilities desiredCapabilities, TimeSpan commandTimeout)

public AppiumDriver(ICapabilities desiredCapabilities)

An instance of AppiumLocalService which has passed through constructors will be stopped when
  driver.Quit();

If there is need to keep the service alive during a long time then something like that is available
  service.Start();

  ....

  new IOSDriver<AppiumWebElement>(service.ServiceUrl, capabilities, commandTimeout)

The known issue
This case can cause problems
TimeSpan timeOutOfTheWaitingForASimulator //(!!!);
...
AppiumServiceBuilder builder = new AppiumServiceBuilder();
OptionCollector collector = new OptionCollector().AddArguments(IOSOptionList.LaunchTimeout(Convert.
ToString(timeOutOfTheWaitingForASimulator.TotalMilliseconds)));
AppiumLocalService localService = builder.WithArguments(collector).Build();

  ....
TimeSpan  commandTimeout; //imagine that this timeout is much lesser than
//timeOutOfTheWaitingForASimulator

new IOSDriver<AppiumWebElement>(localService.ServiceUrl, capabilities, commandTimeout)
//or
//new IOSDriver<AppiumWebElement>(localService, capabilities, commandTimeout)
//here the starting of IOSDriver may be failed

So a command timeout and an iOS Simulator launching timeout should be synchronized for now.
This issue may be fixed further.

@Astro03 Can you please review this PR? :)
@Jonahss @bootstraponline you can take a look at this if it is interesting to you.

@TikhomirovSergey I honestly don't have time to look through all 62 files but just looking from the first 15 or so, looks good. The only comment I have is that I would like DOC tags on all public methods which would be useful to developers.


simplify

Simplify: 1 select + 1 input + that’s it:

(Select a keyword:)
(Enter/auto-fill an input box that has this placeholder:)

Click on:
[e.g. button]

Select:
[e.g. label]

Enter:
[text]

It should show:
[text]

For advanced users:
Copy-and-paste sentences into a text-only input field.
The steps above get generated from that text.

To simplify things for the user, try to communicate between popup and page.
To do that, try following this example:
https://github.com/CodingTrain/website/tree/master/CodingChallenges/CC_084_Word_Definition_Extension/JavaScript

Update: this is already fixed as of 5c2795140fd4abda89210ebc5dd05b03313cbf6d
Don't bother with the text-based input.


⚠ Bofrost.lu has degraded performance

In 98b2605, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1073 ms

Resolved: Bofrost.lu performance has improved in 3da06bb after 6 minutes.


Services: Captive Portal: Administration - remove Transparent proxy settings

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
A long time ago we added "Transparent proxy" options in the captive portal to be able to use captive portal combined with the squid proxy. Last time we did some internal tests, the feature introduced in https://github.com/opnsense/core/commit/0fb1cb1d68f9582b1108ac273f9d786fbadd0253 seemed to be broken and likely has been for a very long time.
My assumption is nobody has been using this for a very long time, in which case we better remove the toggles for clarity.
Describe the solution you like
Remove the toggles before 24.7 is released.
Describe alternatives you considered
none
Additional context

https://github.com/opnsense/core/issues/1189
https://forum.opnsense.org/index.php?topic=3670.msg12576#msg12576

Hello !
Can this change be reconsidered, and tests be re-run ?
Since this removal and updating to 244.7, our captive-portal-with-transparent-proxy is broken
and adding ipfw rules manually "fixes it".
Did I miss something ?
Thanks


[NEW] RocketChatLinkButton Component

Created a new RocketChatLinkButton Component which by default redirects to https://open.rocket.chat
https://user-images.githubusercontent.com/73601258/150687434-46c98142-5c44-4586-96eb-11d6c9870cf0.mp4

Please revise this PR.   Do not keep closing and openning new PRs.  Thanks.

@Sing-Li I've added the rocketchatlinkbutton component and kept it independent, please let me know if we need to make some other changes.
Thank you

@sidmohanty11    Please resolve the trivial conflict and  it will be good-to-merge.  Thx

Done! @Sing-Li


Holopad Megaissue

Megaissue for any holopad bugs/issues that need to be fixed. This is related to #33954. Maybe the issues should be merged, but I wanted to separate issues & bugs from future features.

[ ] Holopad networking needs to be reworked

[ ] Holopads are client-authoritative. Modified clients can make their holopads appear however they want.
[ ] Holopads likely don't play nicely with replays, the appearance data should be part of a component state, not a networked event.
The easiest fix for this is likely to use PVS overrides to directly send the viewed entity and their children, and then having the client copy the data. If we eventually get sprite nesting (using an entity as a layer in another entity's sprite), it should use that.

Holopads absolutely spam the chat of observers/aghosts when they are broadcasting, because you hear the speecs of every last one of them

I actually originally used PVS overrides for this, and it worked just fine, but I got worried about how every client was getting holopad users data and that cheaters might exploit this. But if you don't think it will be problematic, I'll make the switch back

I actually originally used PVS overrides for this, and it worked just fine, but I got worried about how every client was getting holopad users data and that cheaters might exploit this. But if you don't think it will be problematic, I'll make the switch back

Yeah, It's also not a great solution, and also kind of sucks for performance, but having it be client authoritative feels pretty icky as well. The same problem more or less also exists for the round end lobby (#29160). But I also don't really know of a good way to fix either one aside from just sending the entities.

Holopads don't work with displacement maps, which cause vox to be warped into human proportions.

I actually originally used PVS overrides for this, and it worked just fine, but I got worried about how every client was getting holopad users data and that cheaters might exploit this. But if you don't think it will be problematic, I'll make the switch back

Yeah, It's also not a great solution, and also kind of sucks for performance, but having it be client authoritative feels pretty icky as well. The same problem more or less also exists for the round end lobby (#29160). But I also don't really know of a good way to fix either one aside from just sending the entities.

At least we'd only be adding a much smaller number of players to the PVS at a time, up to two per call in progress. Even if multiple people speak into a the same holopad, the holopad on the other end only displays one person at a time, so one one will be added to the PVS override. It'll also fix issues like the displacement maps cos I don't have worry about applying all the sprites by hand

If an A.I. is using a holopad and its unanchored, it breaks the A.I. eye, which can only be fixed by the A.I. returning to core.

Newly spawned holopads do not show the coundown for the broadcast option when it is running. The button does not work until the cooldown is over, so this is visual only.

Another thing that might be intended but feels wrong is that mute players are absolutely fucked if they have a PAI or anything else that talks near them. This feels like it could be intentional, but at the same time holopads feel like the ultimate accessability option for communication. A simple fix for this would be to have a "Gain Focus" button in the holopads UI when on a call, so if my PAI makes a glib remark it won't prevent me from being able to gesture over the call.
Another thing to build on this idea would be to have a "Lock Focus" option that requires extra ID access. That way if I'm mute and plan on using holopads I can go to HOP round start and give them my Holopad Focus Lock request form, and no longer have to worry about a mouse screaming near me. Also department heads should probably have this access too as being CE and having a Technical Assistant budge into a holocall can be undesired.

The focusing issue with PAIs can be partly solved by having it so that when a speaking player is in the inventory of another the holopad focuses on the parent player
The second part is to have emoting bring the focus back to the player in adddtion to speaking. Then there would be no need to have focus buttons


bump minor version number for release 0.6.0

Commit b78dd92cc92b0cfe4eedad823cfd411c13afeb66 was tagged as v0.6.0, but the version number has not been increased in code.

Thanks @striezel , also for the other recent PRs!


Update user manual to clarify how plot parameters x, y, z, colorMap are specified.

This change clarifies how data series are specified to the plotting system in the user manual.
Closes #262

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

I still have to test to make sure this builds on my machine; otherwise it looks good to go in.

Thank you for looking at it.


Update code, fix clippy, update dependencies

Hi Geomatsi,
This project is super cool. I updated the code to the best of my knowledge with help of the compiler and clippy. I also updated to GPIO v2 from embedded-hal. Posting the changes here for your consideration :)
Right now, I cannot run the tests because they require attaching an FTDI device and I think there might be something wrong with my configuration (FTDI cannot be detected).
Is the NRF24L01 also required for the tests?

Hello Rafael,
Thanks for your MR! Looks good, I will merge after CI completion.
Concerning your questions:

No, nrf24 is not required at all. In fact, I plan to replace this example by something more useful, probably some SPI display.
If you can not attach to you FTDI device, then probably ftdi_sio kernel module has been loaded to handle FTDI serial converter. Check using lsmod and then remove that module to enable direct access to FTDI device.

Regards,
Sergey


Add PluginTemplateExtension to show installs on device/VM pages

I use another plugin, netbox-documents, which adds a module to the page for objects which have a relationship to that model. Here's an example:

I'm not proficient in Python, at a cursory glance at the plugin docs this appears to be done via: https://netboxlabs.com/docs/netbox/en/stable/plugins/development/views/#extra-template-content
netbox-documents implements it here for example: https://github.com/jasonyates/netbox-documents/blob/main/netbox_documents/template_content.py
It would be very convenient to be able to see software installations on the page for a device and VM.

Hi @natecohen
That sounds like a great enhancement for the plugin! Thanks for providing an example where this has already been implemented.
I will add it to our backlog. There are a few other things we want to pick up first, though.
But we also accept PRs should anyone have time before we do ;)


add binary installation documentation and add lossless compress keywords to summary to help searching

Let me know if you need anything else.


Incorrect end of comment detected

In case, in an item we have something like: =item 1. Add*/Mod*/Del*/ - high-level then the */ are after translation to cpp seen as end of comment. So they have to be escaped.
(this might happen on other places as well, as soon as found they can be fixed in a similar way).
Note: end of comments in code section will be handled by doxygen in https://github.com/doxygen/doxygen/pull/7026

Something is still wrong, put on hold.

Withdrawn in favor of https://github.com/jordan2175/doxygen-filter-perl/pull/12


Do not show send_button_html() if there are no enabled documents in a bundle

Made a small refactor to logic in enabled_documents() and added an is_enabled() method that tracks the logic that was in enabled_documents(). This allows us to use a generator expression, so that we can return True as soon as we figure out at least one document is enabled.
Fix #503

do you mean download_list_html? That method iterates directly over the list of documents, so it will already produce an empty string

It looks like it still generates an empty HTML table. I don't know if it's announced by screen readers or not (the screen reader I usually test with is acting up at the moment so I can't test it).


tabs are not lining up

I'm new to using spyder, and only been coding for a few months. I just set up 2 monitors in addition to my laptop. Was wondering if this had to do with the multiple monitors or is it a bug?

Thanks for reporting this bug. Unfortunately, it seems you dismissed the information asked by our issues template, i.e. the information we asked our users when they try to open an issue here on Github.
This information includes Spyder version, operating system, dependencies information and several other things. Without it we are not able to understand and solve Spyder bugs as efficiently as we would like to.
Because of that, I'm going to close your report, and ask you to open a new one with that information filled.


Suggest appearance improvements for the site

The problem
The web site is OK, but it could use some improvements from the UI design/UX point of view. We have no such kind of experts onboard, any kind of help would be welcome.
Suggestions
Propose changes, mock them up and show them here before actually including them in the site.

It'd be good to do this while at the same time also swapping to a dynamic app to resolve a bunch of other issues (like better controls for lang-versioned stuff and search).
I think @coke had some sort of design work done in a [private] branch.

@zoffixznet you mean #1246. That kind of thing is actually orthogonal to this issue, which was intended solely to encourage people to consider new CSS appearance.

This ticket is superseded by the new site at raku/doc-website; any suggestions for style changes should now be solicited there.


Recipie App. ROR Capstone

Project Link: https://github.com/users/V-Blaze/projects/3/views/1
There are two Person's in this team.
Valentine: @V-Blaze
Trust: @Trust-007

Hi @TEAM 🥇
Your project is complete!  There is nothing else to say other than... it's time to merge it
Congratulations!
Highlights
✅ Good work on setup the kanban board 🥇
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!:aplauso::aplauso::aplauso:
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.._)


Bugfix for getData/setData on 64 bit operating systems.

Chunk data is not working on 64 bit operating systems, possibly due to the boxed slice handling. This method works but I am not 100% confident about it so I would prefer if we all test it. On the other hand, it does appear to work properly across all platforms which is better than what we have.
I've made a small project to test this, and I will clean it up (remove logging, etc) as an example project and add it to the examples as a separate PR once we're done here. You can find it here:
https://github.com/robsaunders/dd-plugs/tree/master/dd-chunks
Keep in mind you'll have to change the Cargo.toml to point to this branch as it fails on the master branch.

Tests worked for multiple hosts on MacOS as well as Windows so I'm going to merge this.


updating the service page description

Hello Bob, I am updating the description on the service page.

Hi - can you update your master? the merge is shown as out of date.


Update to ESMF 8.5.0b22

Per @theurich, ESMF 8.5.0b22 has two of the MAPL desired updates:

hconfig
geom

Time to update what's in Baselibs!

@tclune ESMF 8.5.0b22 also includes https://github.com/esmf-org/esmf/pull/128. You might already know.


Tellus requires additional packages

Hello,
after the addition of tellus (node-tellus package), i've been getting a lot of errors.
Apparently to solve the missing .h file, it's now required to follow these steps ( https://github.com/Hexagon/node-telldus/issues/60 )
After that, i still can't run npm install :
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Linux 3.13.0-62-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
gyp ERR! cwd /opt/homebridge/node_modules/telldus
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok

npm ERR! Linux 3.13.0-62-generic
npm ERR! argv "node" "/usr/bin/npm" "rebuild"
npm ERR! node v0.12.7
npm ERR! npm  v3.3.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: `node-gyp configure build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp configure build'.
npm ERR! This is most likely a problem with the telldus package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp configure build
npm ERR! You can get their info via:
npm ERR!     npm owner ls telldus
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /opt/homebridge/npm-debug.log

Could we make it that the tellus package is at least optional for now? It looks like it's bringing a lot of headaches (at least for me)

Same here, I had to remove the telldus lines from package.json to get the latest master to build tonight. The answer here is probably the new module system, which @nfarina is working on, but it's a project.


Can we add a Parameter to adjust "Number of Violations"

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Description
We noticed that we cannot adjust options which appear as "Advanced" in the portal, using the AMBA json.
While we are extremely appreciative of the effort the AMBA team invested in picking the best practice alerts, we found some cases where we would like to still use the AMBA repo and deploy from it, but we dont have the flexibility in the template parameters file to make the adjustments we need.
This is an example.  There are probably more, but this one is the one we need to adjust now.  We get too many false positives with the value as provided.
VMHeartbeat
So in the portal we see that there is an adjustment allowed to set the # of violations from 1 - 6, with the default being 2 and AMBA hardcodes this as 2 (since there is no parameter to change it).

Here is the json template parameter file,  Notice there is no option (parameter) to adjust that.
"VMHeartBeatRGAlertSeverity": {
"value": "0"
},
"VMHeartBeatRGWindowSize": {
"value": "PT15M"
},
"VMHeartBeatRGEvaluationFrequency": {
"value": "PT5M"
},
"VMHeartBeatRGAutoMitigate": {
"value": "true"
},
"VMHeartBeatRGAutoResolve": {
"value": "true"
},
"VMHeartBeatRGAutoResolveTime": {
"value": "00:10:00"
},
"VMHeartBeatRGPolicyEffect": {
"value": "deployIfNotExists"
},
"VMHeartBeatRGAlertState": {
"value": "true"
},
"VMHeartBeatRGThreshold": {
"value": "10"
},
"VMHeartBeatRGOperator": {
"value": "GreaterThan"
},
"VMHeartBeatRGTimeAggregation": {
"value": "Average"
},
Might it be possible to expose that as a parameter and include it in the next build?

Hello @stevedistef ,
thanks for your feedback. The idea sounds interesting. We will investigate on this request and let you know.
Thanks,
Bruno.

Hello @stevedistef ,
we added your request to our backlog. Given that, I will close this issue as resolved
Thanks,
Bruno.

I don't think this should be resolved until it is.  Most customers using GitHub issues do not have access to internal mS backlog resources.
Can we mark it a different way so it's still visible so others can see it is being worked on?

@stevedistef , we could make it "Close as not planned" which is not the case or leave it opened and sitting for the time being. I would prefer to close it since it is now under our control.

Lets leave it open @Brunoga-MS i have added a tag to capture the request


Code Review for Github Bot

The task was to find a way to enhance the Open-source license compatibility by having an automated way to check for incompatible licenses in a user's repo and the it's dependencies.
The approach on the task was to listen to a Github action "push", through  a Github App "LegalzardBot" that would then receive an payload with the repo's information and pass it on to a webhook url.
The code in the branch "legalzard-bot-Dennis" is for the webhook listener. When called it extracts the repo license information and all the repos dependencies (repo Insights must be enabled for this to return valid data).
Since all the license information returned is a license IDs, the app gets detailed names from the spdx api and uses this information to run compatibility checks for each license. For all incompatible licenses, the app creates a list and creates an issue on the repo.

Need a demo on this @George-Kibe