Unable to compile ot_br if option CONFIG_OPENTHREAD_ESP_LIB_FROM_INTERNAL_SRC=y (IDFGH-7703)

Before submitting a new issue, please follow the checklist and try to find the answer.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

Environment

Development Kit:  ESP32-DOIT DevKit v1
Kit version (for WroverKit/PicoKit/DevKitC): V1
Module or chip used:  ESP32-WROOM-32
IDF version (run git describe --tags to find it): v5.0-dev-3654-gc2ccc383da
Build System:  idf.py
Compiler version (run xtensa-esp32-elf-gcc --version to find it): xtensa-esp32-elf-gcc (crosstool-NG esp-2022r1-RC1) 11.2.0
Operating System:    Linux (Arch Linux fully updated)
Using an IDE?: No
Power Supply:       USB
CMAKE version: cmake version 3.23.2

Problem Description
Trying/testing the new releases from the openthread repository. For that I need to regenerate the libopenthread_*.a files.
For doing so, on the ot-br project ran: idf.py menuconfig and enabled "Build esp_openthread libraries from source" option by going to Components->Openthread and selecting the above option. This adds CONFIG_OPENTHREAD_ESP_LIB_FROM_INTERNAL_SRC=y to the sdkconfig file.
Expected Behavior
Example is compiled and the Openthread libs under components/openthread/lib/esp32 are regenerated.
Actual Behavior
Compilation fails when executing the idf.py build command:
`
.....
-- Adding linker script /opt/ESP32/esp-idf/components/esp_rom/esp32/ld/esp32.rom.newlib-funcs.ld
-- Adding linker script /opt/ESP32/esp-idf/components/soc/esp32/ld/esp32.peripherals.ld
CMake Error at /opt/ESP32/esp-idf/tools/cmake/component.cmake:380 (__component_get_property):
__component_get_property Function invoked with incorrect arguments for
function named: __component_get_property
Call Stack (most recent call first):
/opt/ESP32/esp-idf/components/openthread/CMakeLists.txt:169 (idf_component_get_property)
CMake Error at /opt/ESP32/esp-idf/tools/cmake/component.cmake:380 (__component_get_property):
__component_get_property Function invoked with incorrect arguments for
function named: __component_get_property
Call Stack (most recent call first):
/opt/ESP32/esp-idf/components/openthread/CMakeLists.txt:183 (idf_component_get_property)
-- Components: app_trace app_update asio
...
....
....
-- Configuring incomplete, errors occurred!
See also "/opt/ESP32/esp-idf/examples/openthread/ot_br/build/CMakeFiles/CMakeOutput.log".
FAILED: build.ninja
/usr/bin/cmake --regenerate-during-build -S/opt/ESP32/esp-idf/examples/openthread/ot_br -B/opt/ESP32/esp-idf/examples/openthread/ot_br/build
ninja: error: rebuilding 'build.ninja': subcommand failed
ninja failed with exit code 1
`
Steps to reproduce

Run idf.py menuconfig on the ot_br example from esp-idf.
Goto Component config->OpenThread and enable Build esp_openthread libraries from source

Save and exist the menuconfig.
Try to compile with idf.py build
Fails to compile.
To recover, edit the sdkconfig file and change the CONFIG_OPENTHREAD_ESP_LIB_FROM_INTERNAL_SRC=y to =n.

#
# Openthread
#
CONFIG_OPENTHREAD_ENABLED=y
# CONFIG_OPENTHREAD_RADIO_NATIVE is not set
CONFIG_OPENTHREAD_RADIO_SPINEL_UART=y
CONFIG_OPENTHREAD_FTD=y
# CONFIG_OPENTHREAD_MTD is not set
# CONFIG_OPENTHREAD_RADIO is not set
CONFIG_OPENTHREAD_DIAG=y
# CONFIG_OPENTHREAD_COMMISSIONER is not set
# CONFIG_OPENTHREAD_JOINER is not set
# CONFIG_OPENTHREAD_SRP_CLIENT is not set
CONFIG_OPENTHREAD_BORDER_ROUTER=y
CONFIG_OPENTHREAD_ESP_LIB_FROM_INTERNAL_SRC=y
CONFIG_OPENTHREAD_NUM_MESSAGE_BUFFERS=65
# end of OpenThread

Other items if possible

[X] sdkconfig file (attach the sdkconfig file from your project folder)
sdkconfig.txt

@fcgdam The CONFIG_OPENTHREAD_ESP_LIB_FROM_INTERNAL_SRC is not public available, only for internal use, so please don't enable this option from your side.
Currently only the ESP Openthread port and Border Router implementation are released in library, the Openthread core stack is still built from source.

Ok, fair enough. So is not possible to recompile libopenthread*.a files under the lib/esp32 folder? I'm asking this because any change on the Openthread source is not mirrored on the used openthread stack in applications. What I mean is that if I add some debug log output to openthread sources, those changes aren't used since the ot_br code links to the library, not to the compiled code.

Actually any changes to openthread sources, will be built into the final binary.
Attach a stack layer diagram for your reference, only the ESP OpenThread Port and Border Router are in library, the Openthread itself is built from source code, so you can make any changes you want, as long as no changes to the interface(APIs).

Ok, thanks. The issue that I have right now is that I only see the ot_br sending IPV6 router solicitation messages (check by using Wireshark) and no Router Advertising messages. Hence the OMR (Off-Mesh Prefix) is not know by client computers. Nevertheless this seemed to work on previous versions of esp-idf (April/May I'll have to check) where OMR was added to host computers routing table automatically. So I was trying to add debug messages to the Openthread code to see if the Router ADV code is called.
The fact is if I add garbage code or lines to the Openthread code under components/openthread/openthread/, ot_br compiles fine... hence it does not compile the Openthread from sources, at least from disk and on my setup...


Add support for Operator Mono Italic

Please add support for Operator Mono Italic font. (react component props, import...from, classes, ...)

Can post a list of what you should like to see italic?

all of these will be italic:
keyword.control",
        "constant.other.color",
        "punctuation",
        "meta.tag",
        "punctuation.definition.tag",
        "punctuation.separator.inheritance.php",
        "punctuation.definition.tag.html",
        "punctuation.definition.tag.begin.html",
        "punctuation.definition.tag.end.html",
        "punctuation.section.embedded",
        "keyword.other.template",
        "keyword.other.substitution"

From the official website it looks like that:

Basically comments, attributs and "this" (maybe "function" and "class" too, depend on the tastes).
Thanks in advance !


fix staticheck and add to linter

@Sharpz7 brought up this linter issue so I added to our linter and fixed it.
This way we can discover issues like this consistently among different developers.

There is now an issue for this;
Closes https://github.com/armadaproject/armada-operator/issues/12


merge from template-sync/template-coveralls

package.json

chore(deps): add ^15.3.36 remove ^15.3.35 (devDependencies.npm-pkgbuild)

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

npm package (@latest dist-tag)
v6.11.30
GitHub release

Your semantic-release bot :package::rocket:


Build test tools in parallel

Summary of the new feature/enhancement
Currently we compile our test tools in every test job.
We could do this in parallel with job building pwsh.
It will save about 2 minutes and consumed resources.
/cc @RDIL @TravisEz13

What do you mean by test tools?

If we run Start-PSPester we compile some test helper tools from test/tools folder before run tests.

@iSazonov Do you mean during CI or locally?

@TravisEz13 During CI.

Even doing this in the main build would technically be a compute time savings, but not a clock time savings.  I agree this would be worth doing.  We have done something like this for release build testing.  cc @adityapatwardhan

Or we could just use caching...

It's possible.  The artifact system in AzureDevOps is pretty slow.  My intuition is that using the cache will be slower that building, unless that made the caching an order of magnitude faster than other artifacts operations.
I'd like to know either way.
One way to make this work would be to:

Restore the cache(s)
make the -SkipTestToolBuild build if the files are not there and use this in CI
save the cache(s)

Caching was introduced . https://devblogs.microsoft.com/devops/caching-and-faster-artifacts-in-azure-pipelines/


Syncing to S3 lasts forever

Hi,
Thank you for such a great tool!
Anyway, I have set backup to sync to S3 and I'm using Ruby 1.8.7, and while it copies some of the files (the total is 357MB) it just hangs forever. I have a 10Mbps internet connection, 5Mbps outbound, and I left it a whole night and in the morning it was still hanging at:
[timestamp][message] Performing backup for fullofcaffeine_backup!
[timestamp][message] Backup::Syncer::S3 started syncing '~/workspace'.
Any ideas?

Marcelo.

I'm having a similar problem with Ruby 1.9.2. I'm able to use aproxacs-s3sync from the command line, but it just hangs when I try to use it with Backup of directories over a certain size.

This also happened to me while syncing a directory 66MB in size with Ruby 1.8.7 on Ubuntu 10.04.

I have the same issue with 1.8.7 and I see that there is 15 min timeout, maybe  on the s3sync level. Trying to understand how can I manage this timeout.

reopening, since it seems to remain unsolved.
so, what are our options? working around s3sync? switching to fog?

What about using https://github.com/fredwu/ssync? Envato uses ssync in production and it's supposedly more efficient than s3sync.

Currently I used s3fs http://code.google.com/p/s3fs/wiki/FuseOverAmazon quite tricky but it's work for me.

subscribe...

Same issue on backup 3.0.21 : ruby 1.9.2p290.

eventually I used rsync with s3fs, work flawlessly, but take a lot of effort to setup.

Check out this for now guys and gals: http://freelancing-gods.com/posts/backing_up_with_backup
This is something we want to incorporate in to Backup itself once we have time. Essentially his fork provides syncing to Amazon S3 and Rackspace Cloud Files. It uses the Fog gem (which we use) as it's only dependency, unlike the current Backup release, we use external CLI dependencies which kind of sucks.
Pat Allan has done a nice job with his current work, but there are a few things still missing:

Use threads to boost up performance dramatically.

His single-threaded solution works, but you can easily spawn 50+ threads to dramatically reduce the process time

Doesn't mirror yet
It isn't up to date (last I checked) with the current Backup release. The code-base he forked is I think 2 releases off, which is a lot considering we completely overhauled the internals and how things work.

We want to get this done, but lacking the time to do so right now. It will definitely make it in at some point though.

Same problem. According to strace it hungs when writing something (to s3?):
munmap(0x7fb52fa0a000, 4096)            = 0
stat("/srv/gitosis/repositories/repo.git/objects/d5/4d2bbb00c80c3cdf099f79b0770d1775f25a3c", {st_mode=S_IFREG|0444, st_size=2077, ...}) = 0
write(1, "positories/repo.git/objects/d3"..., 4096


Postgres table in which data exists can't be upsert unless "key" is specified in the config when creating

Postgres table in which data exists can't be upsert unless "key" is specified in the config when creating  Postgres Destination connector (request: /v1/connectors). Even if the "key" field is present in the metadata
Steps to reproduce

There is a table with data with the  primary "key" in Postgres
Create a new pipeline
Create Postgres destination connector with configs
"settings": {
"url": "postgresql://postgres:postgres@localhost:5432/postgres",
table: "",
"key": ""
}
Create Source connector that transfers the "key" in metadata (For example, Postgres or Snowflake Source)
Run the pipeline -> the system is trying to transfer data by "key" which already exists
Actual result: data isn't transferred to the Postgres table
Expected result: The data should be updated by "key" from the metadata.

2022-05-12T13:56:39+00:00 ERR node stopped error="node 9873f4b8-61d7-483e-8b24-a52f12395ad0-acker stopped with error: error receiving ack: ERROR: duplicate key value violates unique constraint "table2_pkey" (SQLSTATE 23505)" component=pipeline.Service node_id=9873f4b8-61d7-483e-8b24-a52f12395ad0-acker stack=[{"file":"/Users/serhii/conduit/pkg/pipeline/lifecycle.go","func":"github.com/conduitio/conduit/pkg/pipeline.(*Service.runPipeline.func1","line":387},{"file":"/Users/serhii/conduit/pkg/connector/destination.go","func":"github.com/conduitio/conduit/pkg/connector.(*destination.Ack","line":194},{"file":"/Users/serhii/conduit/pkg/plugin/builtin/v1/destination.go","func":"github.com/conduitio/conduit/pkg/plugin/builtin/v1.(*destinationPluginAdapter.Ack","line":137}]

related to issues #58


Release Event Hubs Track 2 Library Preview 5 for Java

The work items linked to this issue herein represent the tasks needed to produce the 5th preview for the "track two" Event Hubs client library.
API Design Review with the Board

[ ] Follow up review for Event Processor

Features

[ ] Event Processor
[x] Stop exposing implementation classes in azure-core-amqp

Diagnosability

[ ] Review existing logging story

Links to previous preview items

Event Hubs Track 2 Preview 1
Event Hubs Track 2 Preview 2
Event Hubs Track 2 Preview 3
Event Hubs Track 2 Preview 4

Closing this issue as Preview 5 has been released.


deploy model

Thank you for your excellent work.
Is it possible for you to provide  code on how to deploy your model?
My email address is<EMAIL_ADDRESS>

Thanks for your interest. The unrefined deployment code has been sent to your email. :)


Add(tools): Tailiscope.nvim

Name
Link

Tailiscope.nvim
https://github.com/danielvolchek/tailiscope.nvim

Tailiscope nvim is a tool I built that converts the popular tailwind css cheatsheet format into a form that can be accessed directly within neovim as an extension to the very popular telescope.nvim plugin

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

Done!

Your project should be below "Impulse.dev" to group them by emoji :) I would do it but it's inconvenient on GitHub UI.

Sorry about that! I thought I put it their initially when I forked since it was near the other cheat sheets but I thought I moved it before I PRed. My bad 😅


Parallel functionals in rowDists() and rowStats() are leaky

Need to protect them with local() like the other parallel functionals.

Fixed by https://github.com/kuwisdelu/matter/commit/9fea34e6338e93a7f9fe19aa7ab7772b89dd5c4a


fix: send heal node status when healing single node

Fixes #1375

Pull Request Test Coverage Report for Build 970515523

0 of 6 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-11.0%) to 19.584%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ZwaveClient.ts
0
6
0.0%

Totals

Change from base Build 968336902:
-11.0%

Covered Lines:
3611

Relevant Lines:
19559

💛  - Coveralls


FYI - Refactored version available: AnnotationClustering

I didn't know how to inform you guys other than creating a new issue: i've started to refactor the code of this repo to use it in a project of mine. Along the way i decided to put the refactored version in a new repo instead of creating a fork and a pull request.
So in case anyone is interested, here's my version:
AnnotationClustering
Note: i use only Carthage for package management, so i dropped CocoaPod support.

Thank you for doing this @gunterhager!

@gunterhager will it be available via pod?

At the moment i have no plans to support CocoaPod, since i only use Carthage in all my projects. Carthage is much easier to use than pods since you don't need any special support in the repo to be able to get it via Carthage.
If you feel the strong need to use it as pod, you could submit pod support as a pull request.


Txt token Header

I assume the token is sent in the header. Do we have any recommendations for the header name?

In what situations would we have multiple tokens such that leveraging the Authorization header is not sufficient? My preference would be to leverage the Authorization header. Receiving entities can distinguish token types based on the JWT Header.

@gffletch It is mainly in the transition phase. In our case, we want to pass both Access Token and Transaction Token until all the downstream are ready.

This topic has come up again so re-opening the issue as it's something I think we need to address in the specification.

Duplicate of #49

I believe, this issue can be closed as well?


Jobs not acting as cores locally?

Snakemake version
6.5.0
Describe the bug
When deploying v0.3.0 of https://github.com/nikostr/dna-seq-deepvariant-glnexus-variant-calling deployed with snakedeploy and running with snakemake -j50 --use-conda --conda-frontend mamba -p --use-singularity  on my local machine, multiple 50 thread jobs are launched in parallel. In the documentation I'm interpreting --jobs and --cores to be aliases locally, but I'm assuming that this is not the expected behavior.

Thanks for reporting! Fixed in commit ffa5cf87.


ArmDocker

How can we help you?

That does not make sense what you are writing here.
Openshift on a arm phone via an x86_64 emulated docker?
Try stating your problem in a sentence.


what is apache server-info module?

a2enmod server-info
ERROR: Module server-info does not exist!

ok it's "info" not "server-info"

no in fact it's not because the file is very different than your example and then the script doesn't work :(

The script can be adapted. Nevertheless I am not sure about the difference between the info and the server-info module.


Make Health Analysers UI continuously update

About the PR
Health Analysers (and medical PDA's) will continuously update after scanning the patent, provided you do not drop or place the analyser in a bag/pocket.
Why / Balance
Solves the complaints of constant beeping in medbay as we spam scan patients.
Technical details
Hook into DamageChangedEvent to send UI updates, rather than on DoAfter.
Added some subs for the item being dropped or inserted into a container
Swapped UseRate for DrawRate on Health Analyser, calculated for 5 minutes per small cell.
Continuous updates are range limited, currently set to 5 tiles (prevent knowing someones vitals from across the station).
Media
https://github.com/space-wizards/space-station-14/assets/11758391/947d5f9c-a257-495c-ba67-31df5aa5a21b

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

tweak: Health Analysers now continuously update their UI after scanning a patient

there needs to be a maximum distance to keep the UI up or somebody will just scan the captain and be their personal paramedic

Continuous updates are range limited, currently set to 5 tiles (prevent knowing someones vitals from across the station).

nevermind :trollface:

Does it also work with cryopods?

No, cryopods use the same ui - but dont share the same code.
Cryopod is outside the scope of this PR

Unfortunately the TemperatureComponent and BloodstreamComponent are only available serverside.
That means i have 3 options:

Exclude blood level and temperature from the health analyzer UI.
I dont think this is a good idea, those fields are important to diagnosis.

Do the majority of the fields client side, and just send the blood and temperature information from the server
Feels like a messy solution, with the data coming from local and remote sources

Move all of the temperature and bloodsteam stuff to shared
I dont think this is feasable, it would be a major amount of work for a simple change.

As for the damage listener checks, i can move those to an update method - a slight delay in disabling the monitor when someone moves too far away isnt a problem


make gradient shimming work as good as possible...

should be able to achieve mean = 0 at the very least, with marginal improvement on STD.

if that still does not work, will need to characterize gradients better to see if they are actually linear #16 which is dependent on #2 so that you could more adhoc test random things...

with longer delta TE and phase unwrapping to enable that, the results look more promising but are still not there. the standard deviation drops almost exactly as much as expected, without much fail. the only thing is that the mean is still quite off from 0... maybe i am missing something in my assumptions...

think this is getting solved currently with #20, #31, and #28


Sub menus auto expand on down arrow

Describe the bug
When pressing arrow key down in a menu, any sub menus automatically expand and draw focus from the main menu.  The only way for the user to continue down the main list is to press then LEFT arrow to get back into the main tree.
This is not the way keyboard navigation works in most GUIs e.g. Visual Studio:

Comparing keyboard navigation of menus that have submenus in Visual Studio vs Terminal.Gui
To Reproduce
Steps to reproduce the behavior:

Create menu with multiple submenus
Press down arrow multiple times

Expected behavior
It should be possible to keep scrolling down a menu using only up/down.  Submenus should only expand on pressing RIGHT arrow (when using keyboard only navigation).

Through the mouse the sub menus are auto expanding. So, I understand that they must have different behaviors.
You have to be aware that currently if you press the right arrow key the next menu from the menu bar will be selected.
Therefore the solution is, if the current opened menu has no sub menu, pressing the right arrow key the next menu from the menu bar will be selected. Otherwise the sub menu of the current opened menu will be opened.

Therefore the solution is, if the current opened menu has no sub menu, pressing the right arrow key the next menu from the menu bar will be selected. Otherwise the sub menu of the current opened menu will be opened. The same logic have to be used for the current sub menu opened.

That sounds perfect 💯


Time Series Forecasting with SAP HANA APL (Automated Predictive Library)

A broken link to the "apl_timeseries_data.txt", makes tutorial impossible to complete.

Link is fixed. Thanks for alerting us.

Works fine! Thank you for quick fix.


Turns out, the cats might have breed information too. If I took more time to read the documentation, I might have discovered that. TODO: add breed info to cat card if available.

https://developers.thecatapi.com/


[PIO-30] Set up a cross build for Scala 2.10 (Spark 1.6.2) and Scala …

This PR introduces a simple profile-based build of PredictionIO, which comes along with some upgrades including a new version of Spark.
The key changes include:

build.sbt - here I created two profiles with different sets of artifacts to be included. Their names are scala-2.11  and scala-2.10, where the former is chosen by default. In order to set a desired profile for sbt command -Dbuild.profile=<profile_name> property has to be provided.
You can print the description of some profile by e.g.
sbt -Dbuild.profile=scala-2.10 printProfile
The scala-2.11 settings include Spark version 2.0.0, while scala-2.11 sets it to 1.6.2. This can be configured, by adding a dedicated property:
sbt -Dbuild.profile=scala-2.11 -Dspark.version=1.6.0 -D Dhadoop.version=2.6.4 <sbt task>
This command will set a build profile to scala-2.11, but will use a different versions of Spark and Hadoop. It makes the configuration more flexible, especially if someone wants to build the project according to their own needs.
Very important thing to note is that versions of spark before 1.6.x are no longer supported and scala 2.10.x is deprecated.

data/src/main/spark-1/org/apache/predictionio/data/SparkVersionDependent.scala and data/src/main/spark-2/org/apache/predictionio/data/SparkVersionDependent.scala - are the only examples of version dependent code. They are solely for providing a proper type of an object for Spark sql related actions. Sbt is configured to include version specific source paths like these.

make_distribution.sh - in order to create an archive for Scala 2.10 one has to provide it with an argument in the same way as sbt (./make_distribution.sh -Dbuild.profile=scala-2.10). By default it will build for scala-2.11.

integration tests - The docker image is updated, I pushed it with a tag spark_2.0.0 not to interfere with the current build. It contains both versions of Spark and on startup sets up environment according to dependencies that predictionIO was built with. It uses a simple Java program tests/docker-files/BuildInfoPrinter.java linked with the assembly of PredictionIO to acquire necessary information. Travis CI makes use of the setup and runs 8 parallel builds, the number doubled because of introducing two different build profiles.

I also noticed that there are many places hardcoding different version numbers and links to packages to be downloaded. Maintaining the project and keeping everything consistent gets only more difficult, therefore I came up with a few small scripts getting proper versions of dependencies from the build config and setting some variables accordingly. An example is conf/vendors.sh, which provided that some variables are set (e.g. by dev/set-build-profile.sh) initializes some other useful variables, i.e. SPARK_DOWNLOAD, SPARK_ARCHIVE, SPARK_DIRNAME. They are used in travis configuration as well as in the Dockerfile, which now should be built with a dedicated script tests/docker-build.sh. Such approach makes it easier to keep everything coherent while bumping version numbers.
Some problems encountered during upgrade
Updating Spark caused some troubles

The classpath has to be extended to run the unit tests successfully for some sub-packages. (see build.sbt)
Column names have to be handled differently for Postgres in JDBCPevents, as Spark surrounds them with "..." what breaks the current schema in this case
tests/pio_tests/utils.py - has a special Spark pass through argument to set spark.sql.warehouse.dir, because the defaults cause runtime exceptions. See -> here

I should also mention that I install.sh is not updated in this PR. I could use some advice on how to integrate it with the current build settings, which versions to choose not to make the whole process to convoluted for the users.


Two VS Code windows have the same terminal

I'm not 100% certain how I got into this state, but the terminal in question has several reconnect messages in it when I scroll up.
These might be the steps that caused this:

Open one VS Code window and open a folder. This will be window/folder A.
Open a second VS Code window and open a different This will be window/folder B.
Do something that causes all VS Code windows to close in such a way that they'll be restored later.
Open VS Code and see that your open folders are restored.
Window A has the expected terminal (cwd is folder A). 🐛 Window B's terminal has cwd of folder A. Run a command in that terminal, and see that the terminal output is the same between Windows A and B, so it seems they now share a terminal.

I suspect there's a race condition when windows launch and fetch the orphaned windows such that they get adopted by multiple windows.

/duplicate #133542


Is there a limit to the number of chat threads? What is the maximum number of chat threads that can be created?

Is there a limit to the number of chat threads?
What is the maximum number of chat threads that can be created?
Will the chat thread automatically destroy the code if it is not used for a long time?

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

ID: 9083c4c3-dd89-b628-84e3-77faf5765bac
Version Independent ID: b4e04b2d-7b24-1f50-5fad-17d11606e15b
Content: Service limits for Azure Communication Services - An Azure Communication Services how-to document
Content Source: articles/communication-services/concepts/service-limits.md
Service: azure-communication-services
Sub-service: data
GitHub Login: @GrantMeStrength
Microsoft Alias: jken

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

hi, Is there any progress?

Hi, Is there any progress? Thanks!

haohighview, Apologies for the delay! (@SnehaAgrawal-MSFT) We are checking with our product team and will get back with an update soon.

@haohighview Thanks for reaching here!

Is there a limit to the number of chat threads?
What is the maximum number of chat threads that can be created?

There no limit to the number of chat threads. However, there's a limit on the chat thread creation rate as documented.

Will the chat thread automatically destroy the code if it is not used for a long time?

No. They will be stored until they are deleted explicitly.
We will now proceed to close this thread. If there are further questions regarding this matter, please let us know.


It can't catch killed app

Describe the bug
If the app wake up, it can work. But I killed the app it can't work.
    final appLinks = AppLinks();
    // Subscribe to all events when app is started.
    // (Use allStringLinkStream to get it as [String])
    appLinks.allUriLinkStream.listen((uri) {
      // Do something (navigation, ...)
      onUrlSchemeUpdate(context, url: uri);
    });

  void onUrlSchemeUpdate(BuildContext context, {required Uri url}) {
    // bla bla ...
  }

Does it related to
[ ] App Links (Android)
[o ] Deep Links (Android)
[o ] Universal Links (iOS)
[ ] or Custom URL schemes? (iOS)
Does the example project work?
[o ] Yes
[ ] No
[ ] Irrelevant here
Did you fully read the instructions for the targeted platform before submitting this issue?
Uploaded your files to webserver, HTTPS, direct connection, scheme pattern setup, ...
[ ] Yes
[o ] No
[ ] Irrelevant here

are you find the solution?

@BhargavJani
Did you meet same bug?
I guess I should get url from the code of Decomposed usage in README.
final uri = await _appLinks.getLatestAppLink();

Same issue here on Android

First, thank you for this lib. I appreciate your work. However, we face the same issue as mentioned above: when a user opens the app with a deeplink and the app is created from scratch, getInitialAppLink() returns 'null' and the deep linking fails. It works well when app is in background.
The behaviour is the same on Android and iOS.
Here's the code:
main.dart
Future<void> main([List<String>? param]) async {
  WidgetsFlutterBinding.ensureInitialized();
  await firebaseInitializer.initFirebase();
  ...
  runApp(MyApp());
}

main_screen.dart (1st widget)
class MainScreen extends ConsumerStatefulWidget {

  @override
    Widget build(BuildContext context, WidgetRef ref) {
    initDeepLinkListeners(context, ref);
    ...
  }

  Future<void> initDeepLinkListeners(BuildContext context, WidgetRef ref) async {
    final _appLinks = AppLinks();
    Uri? initialDeepLink = await _appLinks.getInitialAppLink(); // this is 'null' when app is created fresh; otherwise it works!
    ...
  }
}

Is this setup correct?

I guess not.

You seem to try to catch the link very lately. The native plaform may have already sent its event.
AppLinks has nothing to do in a build method because there's nothing related to BuildContext (even if your use case is to do something with it).

For resolving purpose, move AppLinks() intanciation to main function to see if the very first link is now catched.
You can leave you as it is in your example.

Thanks for the hint. I tried initializing AppLink as soon as possible:
main.dart
Future<void> main([List<String>? param]) async {
  WidgetsFlutterBinding.ensureInitialized();

  final _appLinks = AppLinks();
  Uri? initialDeepLink = await _appLinks.getInitialAppLink();
  print("INIT with DEEP LINK while CREATED: $initialDeepLink");

However, getAppLink() still returns null.

Can you just read the comment above yours?
I need to instanciate the plugin early to register it to the engine.
After this, in your flutter app, use it normally.


GitHub.Dev editor not opening file, opens a blank untitled page instead of URL

After GitHub extension updated last night the Github.Dev editor is not loading files in the URL anymore, and goes to the page that shows when no project is opened.

I tried reopening from GitHub.com and pressing '.' but it does the same thing, and tried different sources, and always get the same results

Version: 1.85.0
Commit: af28b32d7e553898b2a91af498b1fb666fdebe0c
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
Embedder: github.dev

I can repro that we do not open the file but only if I visit https://github.dev/secana/penet/blob/master/src/PeNet/PeNet.csproj all lowercased (which makes sense since casing matters)
I can't repro there not being a workspace at all though, are there any logs from the output channel when you see this?

Please let me know if this repros still for you, thanks!


Statement parameter name suggestion

Hi,
First, thanks to your great library. I will use it in my mobile project and my tool EzoRed (ezored.com) to build cross-platform mobile apps.
I want suggest only a thing: If the user dont put the ":" in parameter name, it can be added on bind function, no?
Query:
select * from customer where name = :name

Instead of:
.bind(":name", "Paulo")

.bind("name", "Paulo")

You library:
void bind(...)
{
    if param_name[0] != ':'
    {
        param_name = param_name + ':';
    }
}

Something like this.
What you think?

Thank you for suggesting this. I am very busy ATM, working on entirely other technologies, so I can't develop this kind of new features, sorry.


Improvements authorization

Some improvements for the Authorization screen/activity

@anuj1708 Can you make sure I did not break anything?

Work in progress ;)

It is working fine :+1:

Build fixed!

Thanks @danielpassos


GROOVY-6514: groovysh: Add :grab command

Take two— notes mostly copied from the first Pull request.
This commit adds a first revision :grab command to the Groovy Shell.
@tkruse Sorry— I know @PascalSchumacher was asking me to fork from your fork, but I couldn't quite square that circle.  So I created a new branch, and added you as a collaborator (you should be able to force push here, so you can rebase the commits if you like, as well).
In any case, we should be able to see some diffs here and at least critique the approach.  I've tested it, and it does appear to work well.
do not like: The only reliable way I could find to send a message to the existing ImportCommand was to invoke property changes (to which it's registered as a listener).  We could make ImportCommand open by registering another type of event listener, but this seems like overkill to me.
I did add the bit that verifies that the import completion property has been set before sending the disable/enable events (to force the reload).
Two changes: I removed an unneeded package specification, and replaced the completer (which gives the user a nice ' ' following the command, but doesn't suggest files as completions for :grab.
Let me know what you think.
Cheers,
Jake

Thanks for creating this pull request. :)

but doesn't suggest files as completions for :grab.

If I understand this correctly it is an advantage because you do not want files as completions for grab.
I think you should also allow the two argument grab like https://github.com/apache/groovy/pull/104/files and add a four argument version with the fourth argument being the classifier: http://docs.groovy-lang.org/latest/html/documentation/grape.html#Grape-Detail

So I rebased my 8 long-standing PRs by the way.
Regarding this PR, compared to mine at #104, it seems that the allowed values behind :grab seems implemented differently, I think my approach in GrabCommand.groovy:buildSpec might be more versatile but maybe they are equivalent.
My Test class GrabCommandTest.groovy defines more test cases for that purpose. Adding those tests to this PR might help comparing the syntax capabilites.
Regarding the import completer, I believe my rescan command invokes a new reset() function in PackageHelper. I think you can copy those changes from #104, even if you leave out the rescan command.

The classloading seems to work btw, I can reproduce the behavior, so hopefully that means we can have the :grab command soon.
Still no solution for this one<EMAIL_ADDRESS>

btw, I notice the imports suggestions are not sorted, not sure since when. Looks messy.

@tkruse You're absolutely right, sir— the buildSpec check is more versatile: the only reason I didn't pick it up was that it allowed the version component to be empty, and I wasn't sure how the modified GrabUtil and Grab calls would deal with it.  I only left it out because of my own ignorance, there.  I'll definitely add the input tests from your branch here.
I saw the reset() method over in PackageHandler!  It'd be a heck of a lot nicer than having to toggle the event— but I couldn't get it to work out for re-loading completions.  What I though* have been happening was that the wrong instance of the class was getting the message— but I think* that's wrong now.  I really think reset() is a better way to go.
I don't know how we're feeling, but Pull #104 might wind up being the way we want to go, anyhow; but I'll chug along and put some of the changes above in here.

Oh... @tkruse ... should we take a look at the package import sorting while we're in here?

Yup— @tkruse 's reset() solution is far nicer here.

...and the tests fail if we don't implement reset() in the test...
The more I look, the more I'm liking Pull #104 .

Wow... that was frustrating.
I can't seem to find a way to get the general Grab() resolver to resolve remotes with only the module set in the dependency Map.  I don't... think it's possible?
So, it's looking more like we need to construct something that the Grape helper can get to— executing in a sub-shell call loses the classloader.
I'm going to try constructing the canonical short name again and reconstructing it with GrapeUtil again before the call.

I'm not a grape expert. In my opinion supporting the three and four argument version is sufficient. What do you think @paulk-assert ?

@Dispader Sorry, there is no one argument grab version: https://github.com/apache/groovy/commit/fd567f7e5cd9af35bd53a19af034a5520665b121

It would be nice if the same syntax as supported by GrapeMain#install was supported:
<group> <module> [<version> [<classifier>]]

It would also be nice to be able to specify a GrabResolver but that could be done as a separate PR.

Thank you all!
The problem here is that I've been wrong-headed about this— I've been trying to reproduce the behavior of Gradle, using the notation that gets passed in dependency sections.  (A mistake that Pull #104 isn't making.)
The way that this code was getting that job done was by putting the single-argument version of :grab through the GrabUtil.getIvyParts method.  I recall using the notation @Grab('group:module:version').
But a Groovy Shell user can just type @Grab('...') right now— that's what you were going for with the :reload command, wasn't it, @tkruse ?

One can't register as a listener for ClassLoader changes, can one?

Yes, the :rescan command was meant as a trigger to reload the definitions for import completion, after any action the user does to add files to the classloader (such as manually invoking grapes).
The way I knew about using grab manually in groovysh was this:
http://tech.puredanger.com/2010/03/01/groovy-grape-groovysh/
but apparently this may work too:
http://www.groovy-lang.org/mailing-lists.html#nabble-td4632257
However both are too clumsy for my taste to advertize them to novice users (in particular when having to additionally call :rescan next for import completion), hence my wish for a :grab command.
Is the only remaining problem the invocation of GrapeUtil.getIvyParts() and passing only a module name?
I don't see too much value in reusing this function anyway. It seems that function is not particularly useful for the interaction case anyway, it returns an empty map in error cases. (Also the function is undocumented and I guess untested, as too much of the core groovy code).
I would recommend recreating the expression parsing logic even if that means having duplicate code.
In #104 I was not even aware of GrapeUtil.getIvyParts, else I would probably have copy&pasted it, and made the modifications needed for Groovysh.

Yeah, the place that got me started on this track was Grab command was the Grape documentation.  That led me to the same conclusion sounds like you came to: it's confusing for new users, and still quite a bit of keyboarding even when you know what you want.  It's just a bit ham-handed for my tastes, as well.
The approach I took was that I was looking for something that was playing the role of supplying things that would be understood by the Grab Annotation.  That seemed like something that might be familiar, and didn't ask too-too much from the user.
Thus, my original tests for acceptance were 1) passing in things that the annotation could accept and 2) getting added packages to the import command's completion.  That's where the GetIvyParts() bit came in— the Grab Annotation class was looking for either the map... or the short form, but neither is really open to being called from the outside world, but GrapeUtil.getIvyParts()  seemed to be.
The GrapeUtil.getIvyParts() call seems to chop either the abbreviated forms (e.g.: 'com.google.guava:guava:19.0', things that come back from these kinds of searches), and value-type part calls (e.g.: :grab com.google.guava guava assumes the only two-part dependency that Grape would take, group and module; and :grab com.google.guava guava 19.0 would take the only three-part.)
I don't know if that's the right way to go, but it's what I was going for.
(I see the :rescan command gives a lot of power to the user in it's own right (it'll at least... make the runtime environment look consistent?)  And I'd love to see the rescan() method called on all changes to the parent classloaders of the shell, but I'm not finding a way to passively listen for changes to a classloader tree.)
(FWIW, I figured out how to pull and build the branch from Pull #104 — and spent a few hours trying to modify the buildSpec to take the Annotation short-form, but I ran into a problem: the buildSpec there presumes we can issue the arguments to Grape.grab() from a shell runtime environment.  So, we can modify it, but we can't then pass the shell's parent classloader, so rescan() wouldn't pick it up (without, of course, modifying Grape).  And I get the feeling that's what's been holding up #104 from being merged.)
So— sorry for the long post— and sorry it's been a few days since I could get back to this, but what do folks think of trying for this as a target contract?

:grab with one string argument

attempts the Annotation short-form (Gradle form)

:grab with two string arguments

that don't represent Groovy Maps

attempts the two-argument version of the Grab install in fd567f7

that do represent Groovy Maps (e.g.:

:grab [group: 'com.google.guava'] [module: 'guava'] or
:grab [[group: 'com.google.guava'] [module: 'guava']]

attempts the two-argument map version of the Grab install in fd567f7

same as above, but for the three-argument constructor with version
same as above, but for the four-argument constructor with classifier

If I hear a yea or two, I'll start work on the above.

Yes, +#104 could not be merged because it had to modify Grape to work with a rescan.

:grab with one string argument
attempts the Annotation short-form (Gradle form)

Consider the unit tests from #104, they test these arguments:
// one argument
assert 'group:\'\', module:\'foo\', version:\'\'' == grabCommand.buildSpec(['foo'])
assert 'group:\'\', module:\'foo\', version:\'\'' == grabCommand.buildSpec([':foo'])
assert 'group:\'\', module:\'foo\', version:\'\'' == grabCommand.buildSpec([':foo:'])
assert 'group:\'foo\', module:\'bar\', version:\'\'' == grabCommand.buildSpec(['foo:bar'])
assert 'group:\'foo\', module:\'bar\', version:\'baz\'' == grabCommand.buildSpec(['foo:bar:baz'])
// two arguments
assert 'group:\'foo\', module:\'bar\', version:\'\'' == grabCommand.buildSpec(['foo', 'bar'])
// three arguments
assert 'group:\'foo\', module:\'bar\', version:\'baz\'' == grabCommand.buildSpec(['foo', 'bar', 'baz'])

Not sure if that's what you were going for. But a subset would also work, this can later be extended as users play with it and come up with ideas for how to speed up their workflows.
#104 does not consider the 4-argument case merely because I did not know about that possibility.

In my opinion :grab 'foo:bar:1.0' should work as the absolute minimum. Then I would add support  for :grab 'foo:bar:1.0:jdk7' and for :grab 'foo:bar'. Anything else e.g. maps is optional.

All right, then, I've sketched out test specification on a test truss class.  It tests the private dependencyMap(String) method just now, which I'll fix and change to a test on the caller.  For now, it should demonstrate a test of producing a Grab-consumable Map from a single-argument input.  Hopefully that'll be a bit more clear.
I'll propose:
import spock.lang.Specification

class GrabCommandSpec extends Specification {

    // this test acts on a private method -- if this test ever fails, DELETE IT
    def 'creates valid depenency maps when passed valid inputs'() {
        expect:
            GrabCommand.dependencyMap(input).group == group
            GrabCommand.dependencyMap(input).module == module
            GrabCommand.dependencyMap(input).version == version
            GrabCommand.dependencyMap(input).classifier == classifier
        where:
            input                                  | group             | module     | version | classifier
            'net.sf.json-lib:json-lib:2.2.3:jdk15' | 'net.sf.json-lib' | 'json-lib' | '2.2.3' | 'jdk15'
            'net.sf.json-lib:json-lib:2.2.3'       | 'net.sf.json-lib' | 'json-lib' | '2.2.3' | null
            'net.sf.json-lib:json-lib'             | 'net.sf.json-lib' | 'json-lib' | '*'     | null
    }

    // this test acts on a private method -- if this test ever fails, DELETE IT
    def 'throws IllegalArgumentException when passed invalid inputs'() {
        when:
            GrabCommand.dependencyMap(input)
        then:
            thrown IllegalArgumentException
        where:
            input << 'net.sf.json-lib:json-lib:2.2.3:jdk15'
    }

}

One note: the test differs from the buildSpec test in #104 because direct calls to Grape.grab() require the Map inputs.
Iffn we think this describes a decent behavior, I'll shine it up and move it into the test tree.  (I'll also convert it to a GroovyTestCase and subclass CommandTestSupport, to keep it consistent with the rest of the test tree.)

Spock spec looks nice, but groovy core code should not depend on Spock, btw, so you cannot actually use it in the PR.
In contrast to Pascal I really would love to see support for providing just the module name. The main purpose of groovysh is to enable users to very quickly hack something instead of firing up an IDE. In particular since we cannot offer tab completion. It feewls wrong to have to type out :grab org.springframework.boot/spring-boot-starter-web when just :grab spring-boot-starter-web is realistically sufficient.

@tkruse As I said, I've no intention of including a Spock test here— and I'd translate it to a CommandTestSupport.  The only thing I was going for with the above was to get us to hone in on what we'd like to send to Grape.grab().  Also why I just added as a comment here.
I think we agree on the spirit of the thing: the less a user has to type when they're extemporizing with the shell, the better the experience is going to be for everyone.  (And I couldn't agree more: I'm half into trying to create a completer that can pull in some kind of group and module for tab completion.)
But— I don't really understand "to have to type out :grab org.springframework.boot/spring-boot-starter-web when just :grab spring-boot-starter-web is realistically sufficient".
I... really don't know any way to iden a module without the group at this time.
This may be my fault, and I'll try to be clearer.  The Grape.grab() method I'm trying to use won't resolve module without group
groovy:000> import groovy.grape.Grape
===> groovy.grape.Grape
groovy:000> dependencyMap = [module: 'spring-boot-starter-web']
===> [module:spring-boot-starter-web]
groovy:000> classloader = ClassLoader.getSystemClassLoader()
===> sun.misc.Launcher$AppClassLoader@33909752
groovy:000> grapeArgs = [classLoader: classloader]
===> [classLoader:sun.misc.Launcher$AppClassLoader@33909752]
groovy:000> Grape.grab(grapeArgs, dependencyMap)
ERROR java.lang.RuntimeException:
Error grabbing Grapes -- [unresolved dependency: #spring-boot-starter-web;latest.default: not found]
groovy:000> dependencyMap = [group: 'org.springframework.boot', module: 'spring-boot-starter-web']
===> [group:org.springframework.boot, module:spring-boot-starter-web]
groovy:000> Grape.grab(grapeArgs, dependencyMap)
===> null
groovy:000>

I got there by tracing the Grab annotation.  But even the grab command line utility doesn't seem to be able to resolve just the module
] grape install spring-boot-starter-web
install requires two to four arguments: <group> <module> [<version>] [<classifier>]

Haha, #104 tricks Grape! Try this:
groovy:000> import groovy.grape.Grape
groovy:000> Grape.grab(group:'', module:'joda-time', version:'')

It seems passing an empty string bypasses some validation maybe.
I don't know if I had done this intentionally in the past, or I never tried to pass a map without the empty string values.

Weeeeird!
I can't get it to work, but I see the confusion now!  And if the empty-map-element works like above, the buildSpec in #104 would totally* work.  (And we can easily build the empty elements into all the forms.)  Very* nice catch.
Okay— so— I can't* get the above to work yet
groovy:000> import groovy.grape.Grape
===> groovy.grape.Grape
groovy:000> Grape.grab(group:'', module:'joda-time', version:'')
ERROR java.lang.RuntimeException:
Error grabbing Grapes -- [unresolved dependency: #joda-time;latest.default: not found]
groovy:000> Grape.grab(group:'joda-time', module:'joda-time', version:'')
===> null
groovy:000> Grape.grab(group:'', module:'joda-time', version:'')
ERROR java.lang.RuntimeException:
Error grabbing Grapes -- [unresolved dependency: #joda-time;latest.default: not found]
groovy:000>

but something*'s going on here.  (The call-with-group in the middle was I thought we might need to have the package in the local Grab cache to pull it by module.)  But Grab over there is working, and I think it'd be great* to have a one-arg option (even if it does need to be loaded with a cache, it'd make using groovysh fast.)
So— can you help try to figure what's special... like, how you're able to trick Grab in the shell over there?  If we can figure it out, I can try to reproduce it here.  I can't help but think that, since it does* work somewhere, we can make it reproducible in the code.
Here's what my env in telling me I'm running, iffn it helps
~){azazel}07:00P] groovy --version
Groovy Version: 2.4.6 JVM: 1.8.0_60 Vendor: Oracle Corporation OS: Mac OS X
(~){azazel}07:00P] groovysh --version
@|green Groovy Shell|@ 2.4.6

Hm, actually it does not work me for anymore, either.  I thought it was the empty strings that made it work back then, but apparently that wasn't it.
Maybe it depends on the remote server returning a result. Maybe that was the case for me back then, and they switched it off at maven central.
So I suggest going with Pascals suggestion to require group and module, and maybe when I find more time, I can figure out what went on back when I implemented #104

All right— sorry about my long absence from this Pull:  I had some problems isolating tests from the collaborators, then managed to let myself fall off the face of the Earth, there.
All that said, I believe we've been able to isolate the tests from collaborators, and get tests that look trustworthy on the public command.
This Pull is rebased from origin/master as of today, and implements @PascalSchumacher 's https://github.com/apache/groovy/pull/286#issuecomment-196498228 (great suggestion for the minimal interface).  It lives up to the https://github.com/apache/groovy/pull/286#issuecomment-197187196 (external truss contract here), but uses a https://github.com/Dispader/groovy/blob/add_grab_command/subprojects/groovy-groovysh/src/test/groovy/org/codehaus/groovy/tools/shell/commands/GrabCommandTest.groovy ( GroovyTestCase with collaborator isolation).  It exposes a variant of @tkruse 's reset() for PackageHelper  It leaves off exposing a package reloading command, and GrabResolver specification for another Pull.
What d'y'all think?

It looks fine as far as I can tell.

+1

Thanks! :+1:


Change default value of metadata enrichment

Description
Same as in #3715
How can this be tested?
Same as in #3715

?
https://github.com/Dynatrace/dynatrace-operator/blob/main/pkg/api/v1beta3/dynakube/metada_enrichment.go#L11
https://github.com/Dynatrace/dynatrace-operator/blob/main/pkg/api/v1beta2/dynakube/metada_enrichment.go#L11

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 64.88%. Comparing base (ccd5328) to head (784f6ba).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3716   +/-   ##
=======================================
  Coverage   64.88%   64.88%
=======================================
  Files         386      386
  Lines       21117    21117
=======================================
  Hits        13702    13702
  Misses       6098     6098
  Partials     1317     1317

Flag
Coverage Δ

unittests
64.88% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

? https://github.com/Dynatrace/dynatrace-operator/blob/main/pkg/api/v1beta3/dynakube/metada_enrichment.go#L11 https://github.com/Dynatrace/dynatrace-operator/blob/main/pkg/api/v1beta2/dynakube/metada_enrichment.go#L11

cherry-pick went wrong - sorry


Feature: visualize novel alternative splice variants

I am interested in studying how predictions of splice variants. For example, splice variants leads to cryptic splice site and alternative splice variants. Can you suggest how to visualize those splice variants?

Hi @husamia, thanks for your interest in our work.
If you have an annotation that includes the start and end sites for cryptic exons in your splice variants, you should be able to achieve this.
We provide several examples that might be adaptable to your needs:
Custom Color Maps
Separate CDS Interactivity
With an annotation that identifies the cryptic exons, you can create a column to distinguish cryptic from non-cryptic exons. This way, you can display them in different colors on the plot, as shown in the examples above.
If you are having trouble doing this, but have some example data and can provide a sketch of the plot you are envisioning I can try to help you further.
Hope this helps!

Hi @husamia, I am closing this issue. Feel free to re-open it if you need help or have questions.


 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.4 out of 5 committers have signed the CLA.:white_check_mark: jmarecek:white_check_mark: phschiele:white_check_mark: befelix:white_check_mark: PTNobel:x: dependabot[bot]You have signed the CLA already but the status is still pending? Let us recheck it.

CI is passing (mod sonar for duplicated code in the tests).
@SteveDiamond @PTNobel I'd appreciate a quick look at this before I go ahead with the 1.4.3 patch release.


Can't differentiate between multiplication operator and pointer

Describe the bug
On the line of code, we can see "* TEXWIDTH" the norminette expects a pointer while it is a case where the students want to multiply a value.
The problem could be solved by removing the space between the * and the Variable.
But this makes the code less readable
Thank you!
Erroneous code
XXXX 2 + data->s_par->s_sc_x))) * TEXWIDTH / data->s_par->s_Z / 256)

Additional infos

OS:
python --version:
norminette -v:  3.51

Additional context
Add any other context about the problem here.

duplicate #296


Possible composition serialization bug

Background
I've tried many times to add a template and a composition that suits it, but every time I try to add composition, I get an error:
{
"error": "java.lang.IllegalArgumentException",
"status": "Bad Request"
}
Expected output
Where can I find a working template and composition set that I can send to ehrbase?
Success criteria

[ ] add template to ehrbase
[ ] add composition to ehrbase

Hey! Can you give a more detailed description of want you are doing (what REST endpoint with what headers etc., what template and composition)? So we can reproduce the error and fix it.
Meanwhile here's a simple set I've been working with:
template+composition.zip

@talex1
you can use https://github.com/ehrbase/documentation/tree/master/examples
Import the files into https://www.postman.com/ and chose the ehrbase Environment and collection

Thanks, template+composition.zip is ok, and  postman collection is usefull too :). Now I know that my ehrbase is working and problem is in composition and/or template.
After using composition from
error_example.zip
I got an error:
{
"error": "java.lang.IllegalArgumentException",
"status": "Bad Request"
}

Was able to follow the problem up to here, but then stopped due to missing time: https://github.com/ehrbase/openEHR_SDK/blob/develop/serialisation/src/main/java/org/ehrbase/serialisation/dbencoding/CompositionSerializer.java#L191
Obviously our serialization works with many examples, so it is really interesting to see and find out what the problem is with the given example set.
Someone needs to take a look at this, so I marked this issue as bug to resolve.

@talex1
This works with the latest version of EHRbase when changing the composition accordingly:
 </name>
            <archetype_details>
            <archetype_id>
                <value>openEHR-EHR-OBSERVATION.laboratory_test_result-coded.v0</value>
            </archetype_id>
            <rm_version>1.0.2</rm_version>
        </archetype_details>
    <language>
      <terminology_id>
        <value>ISO_639-1</value>
      </terminology_id>
      <code_string>en</code_string>
    </language>
        <encoding>
            <terminology_id>
                <value>IANA_character-sets</value>
            </terminology_id>
            <code_string>UTF-8</code_string>
        </encoding>

as the archetype_details were missing and the encoding was not correct.


implement subscription

subscribe to recurring updates of cmds.
I don't like, that now every callback has to get the PROTOCOL_STAT pointer.. Do you have a better idea?

I like it.  especially the simplicity of just turning a subscription into a pseudo read request :).
Set some minimum & default on the subscription period...  else we could kill it easily.
Kind of a side discussion:
1/ Actually, when looking through (and from a previous thought):
if (params[i].preread) params[i].preread(s);
could even be
if (params[i].preread) params[i].preread(s, i);
or even
if (params[i].preread) params[i].preread(s, &params[i]);
or even
if (params[i].fn) params[i].fn( s, &params[i], FN_TYPE_PREREAD );
This would then mean that some of the functions could be more generic with knowledge of the data they were acting on, rather than having to have separate identical (or similar) functions.  The last one would simplify the structure and gather functions together, at a small performance loss.
2/ A concept of time may become important.
e.g. if subscribing to hall position, the tick at the read time should be in the data to give us a feeling for accuracy (or ability to predict position now?
This may then need a subscription to 'time' (heartbeat?).  This may need an alternative approach of either:
Only send the time message if the raw tx buffer is empty.
or
Set a flag in the time message if the tx buffer was empty.
But both of these indicate that the time message is 'special' - because the raw send function must recognise it to make the distinction between delayed and undelayed.
3/ the actual data read/write definition does not belong here?
I am conscious that the data we read and write, and operations we perform are application specific, and don't fit so well within the protocol repo :(.  As a longer term consideration, maybe we should define HOW data is read/written here (i.e. the PARAMSTAT structure, and operational methods), but provide for 'codes' to be added to the structure from the main repo.  - e.g. the protocol repo may add it's own codes for protocol stats read/reset, the flash may (in flashinit) add it's own codes for flash read/write, sensor code could add it's own codes, etc.
If you agree, then we'll add a project task to be addressed at our leisure later... ?

Set some minimum & default on the subscription period... else we could kill it easily.
Was thinking about that too. But what is a good minimum? 1 ? 10 ?
(time unit is 1ms here, I'm writing it like this, because I define HAL_TICK manually on non stm32 controllers.)

Kind of a side discussion:
1/ Actually, when looking through (and from a previous thought):
if (params[i].preread) params[i].preread(s);
could even be
if (params[i].preread) params[i].preread(s, i);
or even
if (params[i].preread) params[i].preread(s, &params[i]);
or even
if (params[i].fn) params[i].fn( s, &params[i], FN_TYPE_PREREAD );
This would then mean that some of the functions could be more generic with knowledge of the data they were acting on, rather than having to have separate identical (or similar) functions. The last one would simplify the structure and gather functions together, at a small performance loss.

I like the last one, I was almost adding another prereceivedreadfunction, but didn't want to blow up PARAMSTAT anymore. Let's do it.

2/ A concept of time may become important.
e.g. if subscribing to hall position, the tick at the read time should be in the data to give us a feeling for accuracy (or ability to predict position now?

Hmmm. right now "time" is local.

This may then need a subscription to 'time' (heartbeat?). This may need an alternative approach of either:
Only send the time message if the raw tx buffer is empty.
or
Set a flag in the time message if the tx buffer was empty.
But both of these indicate that the time message is 'special' - because the raw send function must recognise it to make the distinction between delayed and undelayed.

Let's put this into a new Issue/Feature proposal.

3/ the actual data read/write definition does not belong here?
I am conscious that the data we read and write, and operations we perform are application specific, and don't fit so well within the protocol repo :(. As a longer term consideration, maybe we should define HOW data is read/written here (i.e. the PARAMSTAT structure, and operational methods), but provide for 'codes' to be added to the structure from the main repo. - e.g. the protocol repo may add it's own codes for protocol stats read/reset, the flash may (in flashinit) add it's own codes for flash read/write, sensor code could add it's own codes, etc.

Yes, I already started to modify the callbacks in my control code during runtime. We could move the callbacks and variable definitions out of this repo into a application specific file. Just a blind #include?

If you agree, then we'll add a project task to be addressed at our leisure later... ?

Ok.

tested, works for me!

FYI, started rewriting to if (params[i].fn) params[i].fn( s, &params[i], FN_TYPE_PREREAD );
(btw, this looks wrong:
void PreRead_getspeeds(PROTOCOL_STAT *s){
    speedsx.speedl = SpeedData.wanted_speed_mm_per_sec[0];
    speedsx.speedr = SpeedData.wanted_speed_mm_per_sec[1];
}

)

yes, not even sure speedsx is used.  At first I was thinking to give a reduced size in the return, but in the end did not.

done. First step without using a separate file for application specific functions.
Btw. We could skip allocationg memory for the locally used variables now ;)


bump marpat to 3.0.5

to hopefully address vulnerabilities in underscore

Coverage remained the same at 99.44% when pulling 101ee98501ab8c26b51ba8f9704c5f1ca4a76224 on update-marpat into f5edc39d18cd914122f99ccb82df6d5d41eca8ac on master.


Improved stability for render settings node

Updated description:
The main problem solved here is stopping the render pass blitting when the render buffer has just been deallocated.
Along with this, we are also removing the mutex locks for all primitive adding and deleting in the render param. These are no longer needed.
Testing has been done and stability has increased.

With this patch it also removes all those scene mutex locks, I'm assuming you were experiencing crashes and put them all in place to prevent it, but then later discovered the crashes were due to Houdini clearing the render buffer? Sorry I'm just trying to understand this patch better as the description isn't very informative to what the patch is doing per se.

yep, the mutex locks were added early on. It no makes more sense to lock the mutex outside of these. I.e. when adding a mesh and its object, we lock around the higher level calls.
From my tests, removing these causes no issues in an interactive viewport.

On top of this, I also think they were causing render failures on the farm, but I have less evidence of this until we test on farm

In general, for the future, instead of using lock()/unlock() mechanism, that eventually leads to errors, it's better to use some sort of scoped lock that does it automatically for you.

Agreed, @bareya unfortunately cycles doesnt offer too much in that department. they offer try_lock, but in my original tests, this did not work well with Hydra.

@Vochsel in util_thread.h you can find aliases:
typedef std::mutex thread_mutex;
typedef std::unique_lock<std::mutex> thread_scoped_lock;

Seems like you can use thread_scoped_lock, or std::lock_guard next time.


is premium still required for tokens?

this pages says the premium sku is required to support tokens, but they do not seem to be restricted in portal for basic sku and https://learn.microsoft.com/en-us/azure/container-registry/container-registry-skus indicates 100 tokens is supported in basic.  are these docs out of date?

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

ID: d9769320-10f9-bc69-5b34-ab15e18fead2
Version Independent ID: d58f4440-c1a2-6035-fe96-b02ce7dab4ea
Content: Permissions to repositories in Azure Container Registry - Azure Container Registry
Content Source: articles/container-registry/container-registry-repository-scoped-permissions.md
Service: container-registry
GitHub Login: @tejaswikolli-web
Microsoft Alias: tejaswikolli

@drdamour
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@tejaswikolli-web
Can you please check and add your comments on this doc update request as applicable.

Hello @drdamour, we have been updating Portal and the documentation in the last couple of weeks, making sure both changes drop at the same time is tricky.
The Tokens and Scope Maps feature has gone GA and is available from all SKUs, I think this document change removes the discrepancy you saw.

#please-close


Readme: Add info about external templates

For me, it looks like we can add an "intro" sentence to emphasize that ng-template is not a part of our API.
For example:
While dxTemplate doesn't support external templates out of the box, it's possible to use it with ng-template. ....
However, I'm not sure if it's a good style for guides :)


Fix missing '**kwargs' parameters passing to imshow_bboxes()

'**kwargs' parameters haven't passed to mmcv.imshow_bboxes() in show_result() of mmdetection/mmdet/models/detectors/rpn.py
close #6033

 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.

Hi! @MartaYang  First of all, we want to express our gratitude for your significant PR in this project. Your contribution is highly appreciated, and we are grateful for your efforts in helping improve this open-source project during your personal time. We believe that many developers will benefit from your PR.
We would also like to invite you to join our Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/raweFPmdzG
If you are Chinese or have WeChat，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


test-branch/execute-job/quoted-authorization/47886be7-a860-448c-ac06-eb3df574f6f7

PR for testing 7f6ccb1a81702347a7b7a1268cd41b2a19752528

/canonical/self-hosted-runners/run-workflows 7f6ccb1a81702347a7b7a1268cd41b2a19752528


Artifacts in Godot 3.2

Can't wait to try it out but it looks a bit off on my XUbuntu machine:

If you need more information I'd be glad to provide it to you!
Can't wait for the project to advance.

Thanks for the report! That does look rather off. I'm on Xubuntu with Godot 3.2 as well, so I'd guess it's hardware-related... What graphics card are you using? I noticed that on integrated graphics, there can be graphical artifacts (though I haven't noticed anything this bad). I think that's either related to the 3D texture or just the complexity of the shader. I can try to do some testing for that.
In the Material of the CloudRenderer node, you should be able to change shader parameters of the clouds. Can you check if changing the 'Random Vector Offset Amount' or the 'Num Steps' does anything?
Do you get the same visuals when running the demo game?

Thanks for taking the time to check this out!
I'm running on a Intel HD Graphics 615 (see screenshot).
I tested your suggestions and the result aren't too different.

If I can be of further assistance, I'd gladly help!

Ok! I managed to test it on two laptops, both with Intel HD 620 graphics; it worked fine on both aside from some quirks (like having to move the camera once). Seems like parts of the shader are either too complex or undefined on the 615... I'll try to write a minimal version of it for you to test, to see where exactly the issue might be. Thank you for your help!

Sure thing, let me know what I should do whenever you have it ready!
I can't wait to test this in my flight simulator.

Is this still a problem? ... there are some commits done since 22 Mar 2020

Sorry, I sold the hardware with the problems.
Looks fine on my current hardware:
AMD Ryzen 3 4300u with radeon graphics AMD Renoir.
Running Ubuntu 21.04

Thanks for testing again, good to see it works!
And sorry for never sending that minimal version! I started working on it but got stuck and then forgot :sweat_smile:


Update: bundle files as a Universal Module Definition

This appears to add very little to file size and supports

@montehurd, please review this when you can. I've found this new configuration really simplifies testing.

I'm self-merging per previous discussion.


Swagger page loads HTTP in 'try it out' instead of HTTPS

Our swagger scheme supports only requests via HTTPS (or at least, this is what the swagger.json is telling me).
Despite this, https//mydomain.com/swagger/index.html only shows that HTTP is supported. The try it out feature hence also only uses http, which firefox blocks as being "mixed content".

You can manually change the protocol scheme in PostProcess
https://github.com/RSuter/NSwag/wiki/AspNetCore-Middleware#post-process-the-served-swagger-specification


sst start: warn if local Node version does not match runtime version

Tim mentioned:

we debugged an issue today where the same lambda code was behaving differently when using sst start or sst deploy, which turned out to be because the local environment was running node 16 and the deployed lambda was using node 14. would it be possible to have sst warn/error when sst start is running with the wrong runtime version?

Requests:

Tim https://serverless-stack.slack.com/archives/C01HQQVC8TH/p1654811494750139

Hi there, I'd like to take this one.
The solution I see is to loop through stack functions. In case we have at least one function with Node.js runtime then we check it's version against process.version or process.versions.node.
This version check can be added somewhere in  packages/cli/scripts/start.mjs and can look look like this:
const checkNodejsVersion = () => {
  const funcs = State.Function.read(paths.appPath);

  const NODE_MAJOR_VERSION = process.versions.node.split(".")[0];

  for (const func of funcs) {
    if (
      func.runtime &&
      func.runtime.includes("nodejs") &&
      func.runtime.match(/^nodejs(\d+)/)[1] !== NODE_MAJOR_VERSION
    ) {
      logger.warn(
        [
          "⚠  Node js versions do not match!",
          `Your function '${func.handler}' has runtime ${func.runtime}`,
          `while this Node.js process has version ${process.versions.node}`,
        ].join(" ")
      );
    }
  }
};

Would love some feedback on this

@preshetin In https://github.com/sst/sst/blob/master/packages/sst/src/runtime/handlers/node.ts#L55 the lambda's process.env is injected. It contains AWS_EXECUTION_ENV which is defined as specified here. You can compare it to process.version in the local runtime (packages/sst/support/nodejs-runtime/index.ts) to see if they match and throw/warn if they don't.

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


{AKS} Vendor 2022-09-02-preview for aks-preview

This checklist is used to make sure that common guidelines for a pull request are followed.
{AKS} Vendor 2022-09-02-preview for aks-preview.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

Rerun live tests to update recordings in pipeline.

AKS


gyp: fix android generator

When generating Android .mk files, ready to be used within Android build
system, we don't need LOCAL_SDK_VERSION specified, since the Android
build system already uses the latest one.
By specifying LOCAL_SDK_VERSION in Android makefiles, the build using
Android build system will fail, because the build system won't set the
path to stlport from prebuilts.
Signed-off-by: Robert Chiras<EMAIL_ADDRESS>#Note: This patch is very useful to help integrate node into an Android build system, mostly used by vendors when generating their products. I know the android generator is not maintained anymore, but fixing this generator is crucial for building node as target in an Android build system.

Thanks Robert, landed in a981ef8 and released as v3.3.1.

Also, /cc @othiym23.

Thanks for the heads up, @bnoordhuis<EMAIL_ADDRESS>will get landed in the next testing versions of npm@3 and npm@2 when they're cut next Thursday.


commit for FINERACT-65 (Implement ability to schedule & e-mail reports)

@nazeer1100126
Will create a new pull request.


No unit tests for pkg/storage/storage.go

We don't even have a unit test oriented file for storage
Functions in pkg/storage/storage.go

[x] Create
[ ] Unmount
[ ] Delete
[x] List
[x] ListMounted
[ ] ListUnmounted
[ ] Exists
[ ] generatePVCNameFromStorageName
[x] getStorageFromPVC
[ ] GetComponentNameFromStorageName
[ ] IsMounted
[ ] GetMountPath
[ ] Mount
[ ] GetStorageNameFromMountPath
[x] Push

@kadel Done

@mik-dass  can you please check out list that we have covered from your list?

@kadel You mean ticking the covered functions? Already done. Only one function is covered :D

@kadel You mean ticking the covered functions? Already done. Only one function is covered :D

yes, thank you :-)

/close


Update Chinese translation and fix English spell errors

Chinese translation.
Improve lexicon localization keys.
Fix English lexicon texts' spell errors.
Add Hammer Mobility enchantment's description for the compataion of EnchantmentDescription mod.

You need to change the lexicon text in LexiconProvider.java.

You need to change the lexicon text in LexiconProvider.java.

I don't know how to change this file, sorry.


No CSS Showing

In reference to PG14, my version of the site does not appear to have any CSS so it does not look like the image in the book. If it helps, I am running Windows 11 Home using an installation of DDEV on Ubuntu through WSL.

@mkefiles This issue has been addressed here https://github.com/PacktPublishing/Modernizing-Drupal-10-Theme-Development/issues/11


the luash model can't work , please help me solve this problem

th> local sh = require('sh')
                                                                      [0.0001s]
th> sh
function: 0x410888b0
                                                                      [0.0001s]
th> local dockerbusybox = sh.command('docker', 'run', 'busybox')
[string "local dockerbusybox = sh.command('docker', 'r..."]:1: attempt to index global 'sh' (a function value)
stack traceback:
	[string "local dockerbusybox = sh.command('docker', 'r..."]:1: in main chunk
	[C]: in function 'xpcall'
	/home/tao/Datas/torch/install/share/lua/5.1/trepl/init.lua:679: in function 'repl'
	...atas/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:204: in main chunk
	[C]: at 0x004065c0
                                                                      [0.0002s]
th> dockerbusybox('echo', 'hello')
sh: 1: dockerbusybox: not found

                                                                      [0.0027s]

When I installed the sh as the command
   "luarocks install --server=http://luarocks.org/dev luash "

It's successful , but when I run the example as above ， the problem occured .
I don't know how to solve it,  please help me sovle this problem. Thanks in advance ~   : )

It's because of how lua variables are looked up in the lua shell vs during full script interpretation; so these two things will produce different results.
test.lua:
#!/usr/bin/lua
local sh = require("sh")
print(type(sh))

$ lua test.lua
table

$ lua
Lua 5.2.4  Copyright (C) 1994-2015 Lua.org, PUC-Rio
> local sh = require("sh")
> print(type(sh))
function

And the reason this happens is because luash changes _G's metatable, adding a __index that translates all attempts at accessing unset _G.xyz members as invoking a shell command of the same name (xyz).
So in your shell, type(sh) == "function" is not a defined function from the library, it's a function that in turn would have invoked this shell command for you:
$ sh
Here is a snippet of the relevant code from https://github.com/zserge/luash/blob/master/sh.lua
local mt = getmetatable(_G)
if mt == nil then
  mt = {}
  setmetatable(_G, mt)
end

-- set hook for undefined variables
mt.__index = function(t, cmd)
	return command(cmd)
end


Examples in the online documentation

The Numerical Examples section of the documentation introduces a range of mathematical models, and shows various output plots generated by LINFA.

To help the reader understand how each model is implemented in LINFA, it might be helpful to either (a) link to the Python source file for each example; or (b) use the literalinclude directive to include relevant chunks of code in the documentation itself.

Does the log-loss for the Three-element Windkessel Model get worse as the number of iterations increases? If so, should this page include some comments that point this out and discuss the implications for the obtained fit?

The README.md links to two very helpful notebook tutorials (2D and 3D ballistic models). These notebooks demonstrate how to perform inference tasks and highlight some of LINFA's key features. I found them very helpful in trying to understand how to run LINFA with my own model (as opposed to running one of the models in the test suite) — I felt that these notebooks were the missing link I was looking for.
It would be great to have some of this information included in the online documentation; possibly as a separate page under "Numerical examples", or anywhere else that the authors feel is suitable. I did a search and found that Sphinx can render .ipynb files as HTML pages with the nbsphinx extension.

Thank you for these comments.

I have included the code in the examples using the literalinclude directive as suggested.
That RCR example uses annealing, so it is normal for the loss to increase going from t=0 to t=1, instead of being reduced monotonically like for the other examples. I have added a comment so this is more clear.
I tried the nbsphinx extension to render notebooks, but I get a large number of errors and warning, like these below:

WARNING: Block quote ends without a blank line; unexpected unindent.
ERROR: Unexpected indentation.

I'm trying to fix these problem. Have you seen them before?

Hi @daneschi

That RCR example uses annealing, so it is normal for the loss to increase going from t=0 to t=1, instead of being reduced monotonically like for the other examples. I have added a comment so this is more clear.

Thanks very much for the clarification, I was thoroughly confused!

I tried the nbsphinx extension to render notebooks, but I get a large number of errors and warning [...] Have you seen them before?

I haven't used the nbsphinx extension myself, but I've just given it a try and found a few things:

I needed to install nbsphinx (it's not listed in docs/requirements.txt).

I also installed ipython (also not listed) to avoid some warnings about syntax highlighting.
I also removed the numpy version in docs/requirements.txt so that it could install a newer version — otherwise it would try to build numpy from source when using Python 3.10.

The nbsphinx docs say to add the file names of your notebooks (without the .ipynb extension) to the toctree directive, rather than creating a .rst file and using the include directive.

I suspect this was the cause of the "unexpected indentation" error message.

When I added the notebook files to the toctree in docs/content/num_examples.rst, sphinx complained that it couldn't find the referenced images (which are in ./tutorial).

I resolved this by moving the tutorial directory to docs/content/tutorial.
The notebook links in README.md would need to be updated.

The toctree in docs/contents/num_examples.rst now looks like this:
.. toctree::
   :maxdepth: 2

   tutorial/tutorial_linfa_2d
   tutorial/tutorial_linfa_3d
   trivial
   ...

After these steps, I was able to build the documentation and view the notebooks!
There is still one warning:
MissingIDFieldWarning: Cell is missing an id field, this will become a hard error in future nbformat versions. You may want to use `normalize()` on your notebooks before validations (available since nbformat 5.1.4). Previous versions of nbformat are fixing this issue transparently, and will stop doing so in the future.
  validate(nb)

The good news is that this can be resolved relatively easily.

Thank you @robmoss! I have included the tutorials in the documentation and updated it on readthedocs.

The tutorials look great!


Update to 1.17.8-2-fips, 1.18.0-2-fips

This is the result of running dockerupdate on each build's build asset JSON file, no other modifications. (Enabling automerge to merge with one approval.)

Fixes this issue that shows up in our images if the user sets CGO_ENABLED=0:
https://github.com/microsoft/go/issues/492

Once this PR goes through, I'll queue the builds to get this onto MCR.


[SPARK-23510][SQL] Support Hive 2.2 and Hive 2.3 metastore

What changes were proposed in this pull request?
This is based on https://github.com/apache/spark/pull/20668 for supporting Hive 2.2 and Hive 2.3 metastore.
When we merge the PR, we should give the major credit to @wangyum
How was this patch tested?
Added the test cases

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1040/
Test PASSed.

Test build #87653 has started for PR 20671 at commit 0fdf29b.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1041/
Test PASSed.

Test build #87654 has started for PR 20671 at commit 2e12c10.

Test build #87653 has finished for PR 20671 at commit 0fdf29b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87653/
Test PASSed.

Test build #87654 has finished for PR 20671 at commit 2e12c10.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87654/
Test PASSed.

Merged build finished. Test PASSed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1160/
Test PASSed.

Test build #87795 has started for PR 20671 at commit 2e12c10.

Test build #87795 has finished for PR 20671 at commit 2e12c10.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87795/
Test PASSed.

cc @cloud-fan

LGTM. In the future we should refactor this part so that adding a new version doesn't need to touch so many files.

thanks, merging to master!


Fixes accessibility of empty repository commit status

Avoid empty labelled anchor in repo without commits.
Contributed by @forgejo.

The JS function initCommitStatuses in web_src/js/features/repo-commit.js relies on  the commit-statuses-trigger to show the status.
This class is now missing when there are multiple statuses, preventing from seeing any status.
Investigation is ongoing on how to best address this issue (without hurting accessibility).


Support Sakhal DLC

Update database/destinations.js to support Sakhal DLC

closed in https://github.com/SowinskiBraeden/dayz-reforger/pull/44


Protect safeStringify from TypeError

Protect safeStringify from TypeError, when state vars have types that can not be stringified (like bigint).  This in turn protects getCurrentState(), which failed when dealing with such state.
Also, updated the tests with a bigint to show the failure/test the fix.

@abhinaba-ghosh , any chance we'll see this fix ?

Fantastic find!
Should be available in v2.3.17


Using RBAC Authorization

I am a kubernetes novice so i was going throught the documentation and
From the documentation at rbac it says that:
ClusterRoles have several uses. You can use a ClusterRole to:

define permissions on namespaced resources and be granted access within individual namespace(s)
define permissions on namespaced resources and be granted access across all namespaces
define permissions on cluster-scoped resources

I am a bit confused on point 1 and 2 be cause the definations say
A Role always sets permissions within a particular namespace; when you create a Role, you have to specify the namespace it belongs in.
ClusterRole, by contrast, is a non-namespaced resource. The resources have different names (Role and ClusterRole) because a Kubernetes object always has to be either namespaced or not namespaced; it can't be both.
May someone please clarify point 1 and 2

Page related to the issue: https://kubernetes.io/docs/reference/access-authn-authz/rbac/

/sig docs

/language en

ClusterRoles provides a flexible mechanism for defining and granting permissions across namespaces, but on the other hand ClusterRoleBinding act as a bridge between ClusterRoles and specific namespaces.

/kind support

You can also post your question on the Kubernetes Slack or the Discuss Kubernetes forum.
These places are better to resolve support queries fast.


Add files via upload

Please consider submitting using https://beaconcha.in/tools/broadcast

Please consider submitting your messages using https://beaconcha.in/tools/broadcast

I literally checked yesterday and the tool wasn't live yet.
Thanks mate! Keep up the great work.
Regards,
Benjamin
On Mon, Mar 27, 2023 at 4:46 PM Benjamin Evans Chodroff <
@.***> wrote:

Please consider submitting using https://beaconcha.in/tools/broadcast
—
Reply to this email directly, view it on GitHub
https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/pull/182#issuecomment-1485251573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APUVFHCIY2FOQTW7BY5773DW6GR3ZANCNFSM6AAAAAAWF2WJAI
.
You are receiving this because you authored the thread.Message ID:
<benjaminchodroff/ConsensusLayerWithdrawalProtection/pull/182/c1485251573@
github.com>