[BUG] Assign list of  roles a list of users

Is there an existing issue for this?

[X] I have searched the existing issues

What version of the Terraform provider are you using?
1.7.0
What version of the Terraform CLI are you using?
1.8.0
What type of issue are you facing
bug report
Describe the bug
We want to assign more than one role a list of users, we are use this main.tf:
resource "btp_subaccount_role_collection_assignment" "subaccount-seguridad" {
subaccount_id        = "19545252-3943-46d9-a893-72841d94f332"
role_collection_name = "Subaccount Viewer"
for_each             = toset(var.seguridad)
user_name            = each.value
}
But we want to change role_collection_name to a list of roles. Can you help us?
Expected Behavior
No response
Steps To Reproduce
No response
User's Role Collections
No response
Add screenshots to help explain your problem
No response
Additional context
No response

@jizquga As mentioned in issue #926 please do not abuse issues for question. I kindly advice you to use the discussions area. Happy to answer these questions there


opensshremotes.openEmptyWindow not found

When selecting the command Remote-SSH: Connect to Host..., it displays this error: opensshremotes.openEmptyWindow not found
I am using VSCodium 1.73.1 on Windows 7

I cannot reproduce :thinking:
@solmersa did you enable the extension in argv.json? did you try reinstalling the extension?

@jeanp413, I reainstalled, I also tried with the new VSCodium insider release 1.74.0 which supports Windows 7 out of the box and there is a similar error message.
I see there is code to register the command in out/extension.js, but looks like it is not running.  How can I enable the extension in argv.json?, VSCodium reports the extension is globally enabled.
In insider 1.74.0 the error message is a bit different:

You can follow the requirements sections in readme

Run Preferences: Configure Runtime Arguments command
argv.json file will open and update it

{
    ...
    "enable-proposed-api": [
        ...,
        "jeanp413.open-remote-ssh",
    ]
    ...
}

Restart vscodium

Thanks it is working, to modify argv.json was the thing needed, I was blindsided because of the Globally enabled status.
I also detected an issue if your try to connect to<EMAIL_ADDRESS>it tries to setup SSH on mydomain.com, and that is not valid in this case.

Hello! i've the same issue, .json edited, no errors but it does not activate...

@dan195794 be sure the json file doesn't have any errors like missing trailing comas, etc. and be sure to restart vscodium meaning quit completely closing all windows

helpful for Code-OSS(1.83.1), Open Remote - SSH(0.0.45)


Unable to use auto assigned USB Ethernet Adapter named enx with MACVLAN in Links

Running containerlab 0.53.0 on a Debian 12 system using the default naming schema for USB network devices.
When attempting to setup links the MACVLAN with the default interface name of enxa0cecc8dfd0f the Link will fail to be built and the only error received is:
ERRO[0004] failed to deploy links for node "router1": device or resource busy
link example of failed link:
endpoints: ["router1:eth3", "macvlan:enxa0cecc8dfd0f"]
Workaround:
Use udev to rename the network interface to something like ethusb0

Nevermind. I believe this was due to the fact there was a bridge running on the interface Docker was attempting to macvlan.


Building wheel for diff-gaussian-rasterization (setup.py) ... error

Hello dear friends,
When I try to install requirements.txt using pip install -r requirements.txt command, I get an error like;
Building wheels for collected packages: diff-gaussian-rasterization
  Building wheel for diff-gaussian-rasterization (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [60 lines of output]
      running bdist_wheel
      /home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py:411: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend.
        warnings.warn(msg.format('we could not find ninja.'))
      running build
      running build_py
      creating build
      creating build/lib.linux-x86_64-cpython-310
      creating build/lib.linux-x86_64-cpython-310/diff_gaussian_rasterization
      copying diff_gaussian_rasterization/__init__.py -> build/lib.linux-x86_64-cpython-310/diff_gaussian_rasterization
      running build_ext
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-req-build-zunyy40x/setup.py", line 17, in <module>
          setup(
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/__init__.py", line 103, in setup
          return distutils.core.setup(**attrs)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/dist.py", line 989, in run_command
          super().run_command(command)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/wheel/bdist_wheel.py", line 364, in run
          self.run_command("build")
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/dist.py", line 989, in run_command
          super().run_command(command)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/command/build.py", line 131, in run
          self.run_command(cmd_name)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/dist.py", line 989, in run_command
          super().run_command(command)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 88, in run
          _build_ext.run(self)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 345, in run
          self.build_extensions()
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 420, in build_extensions
          compiler_name, compiler_version = self._check_abi()
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 791, in _check_abi
          _, version = get_compiler_abi_compatibility_and_version(compiler)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 324, in get_compiler_abi_compatibility_and_version
          if not check_compiler_ok_for_platform(compiler):
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 280, in check_compiler_ok_for_platform
          which = subprocess.check_output(['which', compiler], stderr=subprocess.STDOUT)
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/subprocess.py", line 420, in check_output
          return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
        File "/home/cz/anaconda3/envs/splatam/lib/python3.10/subprocess.py", line 524, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['which', 'g++']' returned non-zero exit status 1.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for diff-gaussian-rasterization
  Running setup.py clean for diff-gaussian-rasterization
Failed to build diff-gaussian-rasterization
ERROR: Could not build wheels for diff-gaussian-rasterization, which is required to install pyproject.toml-based projects

And also I cannot execute anything because of gaussian-rasterization. (My system is Ubuntu 20.04 and my conda version is 24.1.2)

I solved the problem by using pip install instead of conda install for the torch packages.

Same error..

Okey, I tried to clone diff-gaussian-rasterization-w-depth.git file manually and put it inside the SplaTAM folder manually, and also I tried to install "setup.py" file using python setup.py install and get an error as;
File "/home/cz/anaconda3/envs/splatam/lib/python3.10/subprocess.py", line 421, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/home/cz/anaconda3/envs/splatam/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['which', 'g++']' returned non-zero exit status 1.

I do not now is there any other way to solve the problem?

Finally, I have solved my problem using the issue #24 .  As mentioned in the issue, the problem is the version of gcc&g++ version is incompatable with CUDA. I fixed the problem using conda install gxx_linux-64=10 command.


Faster documentation generation

get rid of generator dependencies on core and cli

This reduces complexity of the argument parsing and the cli module.

do not use shadow plugin for generator

The shadow plugin runs additional bundling tasks creating distributation jars in 8 seconds which we never use making it quite extension. As it is an internal tool I feel confident to bundle the dependencies ourselves.

fixes generator dependency on formatting rules

Now the documentation gets regenerated when a formatting rule changes.

fixes some task dependencies so that dokka can run earlier reducing build times

Fails
danger-kotlin failed.
Log
Executing kotlinc -script-templates systems.danger.kts.DangerFileScript -cp /usr/local/lib/danger/danger-kotlin.jar -script /Dangerfile.df.kts /tmp/danger-dsl.json danger_out.json - pid 377
Uncaught Kotlin exception: kotlin.Exception: Command kotlinc -script-templates systems.danger.kts.DangerFileScript -cp /usr/local/lib/danger/danger-kotlin.jar -script /Dangerfile.df.kts /tmp/danger-dsl.json danger_out.json exited with code 768
        at kfun:systems.danger.cmd.Cmd.exec() (0x21c739)
        at kfun:systems.danger.cmd.dangerfile.DangerFile.execute(kotlin.String;kotlin.String) (0x21d227)
        at kfun:systems.danger.DangerKotlin.run() (0x21c0e6)
        at Init_and_run_start (0x21f472)
        at __libc_start_main (0x7fe1223bbb97)
        at  (0x20f029)
        at  ((nil))

Generated by  dangerJS against 6e79da8

@Mkohm Hey, maybe you can take a look at this one. Now 'only' 15 files were changed.

Codecov Report

Merging #2722 into master will decrease coverage by 0.30%.
The diff coverage is 8.10%.

@@             Coverage Diff              @@
##             master    #2722      +/-   ##
============================================
- Coverage     80.55%   80.24%   -0.31%
  Complexity     2323     2323
============================================
  Files           380      380
  Lines          6941     6967      +26
  Branches       1256     1261       +5
============================================
  Hits           5591     5591
- Misses          723      749      +26
  Partials        627      627

Impacted Files	Coverage Δ	Complexity Δ
...tlin/io/gitlab/arturbosch/detekt/cli/JCommander.kt 20.00% <0.00%> (-63.34%) 0.00 <0.00> (ø)
...io/gitlab/arturbosch/detekt/generator/Generator.kt 0.00% <0.00%> (ø) 0.00 <0.00> (?)
...itlab/arturbosch/detekt/generator/GeneratorArgs.kt 0.00% <0.00%> (ø) 0.00 <0.00> (ø)
...tlin/io/gitlab/arturbosch/detekt/generator/Main.kt 0.00% <0.00%> (ø) 0.00 <0.00> (ø)
.../kotlin/io/gitlab/arturbosch/detekt/cli/CliArgs.kt 100.00% <100.00%> (ø) 8.00 <1.00> (ø)
...ain/kotlin/io/gitlab/arturbosch/detekt/cli/Main.kt 50.00% <100.00%> (ø) 11.00 <11.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 fdebbc4...01ff112. Read the comment docs.

The coverage report was not updated and is wrong. I've added two more tests to test some paths in parseArguments which were tested implicitly by generator module.

Do we need :generator to have a cli interface? As you pointed out in this PR this is an internal tool and I think that all of us use through gradle. So it could be just a library and call it directly from the gradle task.

Good point, thanks! I've changed this! Should improve the build time again by 2-5 seconds :).

Probably out of scope of this PR. But, could we remove jcommander from generator? Does it help now?

help

JCommander leads to easier arg parsing. Why should we remove it :)?
We could think to replace JCommander in cli with embedded picocli for 2.0 to reduce a dependency :)

I mean, does it help in :generator? In the cli it helps A LOT.

I mean, does it help in :generator? In the cli it helps A LOT.

It makes everything easier to extend, so I would leave it for now (4 parameters as of now).


TBInput.GetFinger(TBInput.Finger.Thumb) ignores Oculus Thumb Rest

Describe the bug
It appears that the API TBInput.GetFinger(TBInput.Finger.Thumb) does not track the Thumb Rest capacitive area on the CV1 Oculus Touch controllers. These controls are Touch.PrimaryThumbRest/Touch.SecondaryThumbRest in the Unity manual.
To Reproduce
Open the InputTest demo scene, start the demo, and touch the Thumb Rest capacitive area. No change will be registered in the input levels of the FingerInputPanel.
Expected behavior
When the user touches the Thumb Rest, the thumb should close down in the same way as when the user touches the thumbstick or face buttons.
Additional information:

Unity Version: 2018.3.13f1
Affected Integrations: Oculus
TButt Version: 1.0.2

Additional context
The Touch Rest buttons are seldomly used in most projects, and most probably will never miss them, so this is probably a low priority fix. In addition, the Thumb Rest has been removed from the remodeled Touch controllers included with the Rift S and Quest.

This functionality is now available on the beta branch.


Runtime generation fails on "Batching Static" meshes

To reproduce:

Place multiple mesh objects in the scene.
Toggle on "batching static" for the objects.
Import the sample runtime decal generator, placing it to overlap with the meshes.
Add the static objects to the target list of the decal generator.
Enter play mode and trigger the decal generator.

What happens:
The generator fails to project any decals, giving a warning that target meshes aren't set to be readable. This warning is misleading; it appears even if the meshes created by the user are readable.
The problem appears to be that Unity's static batching replaces the original meshes with a combined mesh, which is not flagged to be readable.
What should happen:
Ideally decal generation would succeed even in this case. If that's not feasible a more useful warning should be generated.

Is there a fix for this yet? I'm experiencing the same issue.

it is not work rutime spawn decal error occur


Android dependency 'androidx.core:core' has different version for the compile (1.0.0) and runtime (1.0.1) classpath

🐛 Bug Report

Hi everybody,
Can't install this plugin, tried different versions this plugin (3.0.1, 3.0.0, 2.1.1, 2.1.0), but not one did not work. Has anyone encountered this problem already?
pubsec.yaml
name: flutter_app
description: A new Flutter application.
version: 1.1.0+1
environment:
sdk: ">=2.1.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
cupertino_icons: ^0.1.2
geolocator: ^3.0.1
permission_handler: ^3.0.0
meta: ^1.1.6
google_api_availability: ^2.0.0
dev_dependencies:
flutter_test:
sdk: flutter
flutter_launcher_icons: ^0.6.1
flutter_icons:
image_path: "assets/img/location.png"
android: true
flutter:
uses-material-design: true
assets:
- assets/img/location.png
- assets/img/gps.png
- assets/img/no_gps.png
- assets/img/where.jpg
LocationPage.dart
import 'package:flutter/material.dart';
import 'package:geolocator/geolocator.dart';
class LocationPage extends StatefulWidget {
@override
LocationPageState createState() => LocationPageState();
}
class LocationPageState extends State{
initLocation()async{
Position position = await Geolocator().getCurrentPosition(desiredAccuracy: LocationAccuracy.high);
print(position);
}
initState()  {
super.initState();
initLocation();
}
@override
Widget build(BuildContext context) {
return Scaffold(...);
}
}
CONSOLE OUTPUT:
Running "flutter packages get" in flutter_app...                    0.6s
Launching lib/main.dart on MI 6 in debug mode...
Initializing gradle...
Resolving dependencies...
Running Gradle task 'assembleDebug'...
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:preDebugBuild'.

Android dependency 'androidx.core:core' has different version for the compile (1.0.0) and runtime (1.0.1) classpath. You should manually set the same version via DependencyResolution

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 4s

The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.

Finished with error: Gradle task assembleDebug failed with exit code 1
Reproduction steps
flutter run -d
Configuration
Version: 3.0.1
Platform:

[ ] :iphone: iOS
[*] :robot: Android

[✓] Flutter (Channel stable, v1.2.1, on Mac OS X 10.13.6 17G65, locale en-UA)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
[✓] Android Studio (version 3.3)
[✓] VS Code (version 1.31.1)
[✓] Connected device (1 available)
• No issues found!

for me , i added the android migration to the gradle properties file and then changed classpath 'com.android.tools.build:gradle:3.2.1' to classpath 'com.android.tools.build:gradle:3.3.1'. im using geolocator 3.0.1. follow this link https://www.youtube.com/watch?v=ZRl4t2KdEHQ and then do what i have said above

I

for me , i added the android migration to the gradle properties file and then changed classpath 'com.android.tools.build:gradle:3.2.1' to classpath 'com.android.tools.build:gradle:3.3.1'. im using geolocator 3.0.1. follow this link https://www.youtube.com/watch?v=ZRl4t2KdEHQ and then do what i have said above

when i added the (android.useAndroidX=true
android.enableJetifier=true)
to the gradle properties it worked thanks

Thanks @aidooyaw1992 , changing the classpath to 3.3.1 worked for me too :)

I

for me , i added the android migration to the gradle properties file and then changed classpath 'com.android.tools.build:gradle:3.2.1' to classpath 'com.android.tools.build:gradle:3.3.1'. im using geolocator 3.0.1. follow this link https://www.youtube.com/watch?v=ZRl4t2KdEHQ and then do what i have said above

when i added the (android.useAndroidX=true
android.enableJetifier=true)
to the gradle properties it worked thanks

I had these set and the same issue was happening.
What solved for me was the tip from @aidooyaw1992, changing the classpath to gradle:3.3.1.
Thanks, @aidooyaw1992!

My pleasure
On Mon, 18 Mar 2019, 17:17 Matheus Henrique de Oliveira, <
<EMAIL_ADDRESS>wrote:

I
for me , i added the android migration to the gradle properties file and
then changed classpath 'com.android.tools.build:gradle:3.2.1' to classpath
'com.android.tools.build:gradle:3.3.1'. im using geolocator 3.0.1. follow
this link https://www.youtube.com/watch?v=ZRl4t2KdEHQ and then do what i
have said above
when i added the (android.useAndroidX=true
android.enableJetifier=true)
to the gradle properties it worked thanks
I had these set and the same issue was happening.
What solved for me was the tip from @aidooyaw1992
https://github.com/aidooyaw1992, changing the classpath to gradle:3.3.1.
Thanks, @aidooyaw1992 https://github.com/aidooyaw1992!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/BaseflowIT/flutter-geolocator/issues/228#issuecomment-474014943,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIG4X9VG3JH5L3NctGCqQ0NzTDuWl3XGks5vX8obgaJpZM4brXKj
.

ref: https://github.com/Lyokone/flutterlocation/issues/117
Looks similar.

I there mates... Facing the same issue did solved it by changing the classpath from 3.2.1 to gradle:3.3.0 (not 3.3.1); and also did add the (android.useAndroidX=true
android.enableJetifier=true) to gradle.properties ....
Not sure wich one made it happend...
Thaks a lot, futter team...

Guys, that would be very nice if you could tell us in which files you made the changes. I did a search for com.android.tools.build:gradle:, found 1 match, but now I get another error :
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:

@Robouste, the problem is that we have upgraded the Geolocator plugin to support AndroidX (as well as still be compatible with older Android versions). This means you will also have to upgrade you App which can be done following these instructions:
https://github.com/BaseflowIT/flutter-geolocator/issues/196#issuecomment-465460801

try to add script in app level
subprojects {
project.evaluationDependsOn(':app')
project.configurations.all {
resolutionStrategy.eachDependency { details ->
if (details.requested.group == 'com.android.support'
&& !details.requested.name.contains('multidex') ) {
details.useVersion "28.0.0"
}
}
}
}

if (details.requested.group == 'androidx.core'
&& !details.requested.name.contains('androidx') ) {
details.useVersion "1.0.1"
}

Its working fine by adding android.enableJetifier=true and android.useAndroidX=true in build project and change the classpath to 3.3.1

Following solved my issue
(1)Adding Two lines to gradle properties
android.enableJetifier=true
android.useAndroidX=true
(2)Add following to root gradle
subprojects {
project.evaluationDependsOn(':app')
project.configurations.all {
resolutionStrategy.eachDependency { details ->
if (details.requested.group == 'com.android.support'
&& !details.requested.name.contains('multidex') ) {
details.useVersion "29.0.0"
}
}
}
}

对我来说，我将Android迁移添加到gradle属性文件中，然后将类路径'com.android.tools.build:gradle:3.2.1'更改为类路径'com.android.tools.build:gradle:3.3.1'。即时通讯使用geolocator 3.0.1。按照此链接https://www.youtube.com/watch?v=ZRl4t2KdEHQ，然后按照我上面所说的做
解决了我的问题，谢谢大佬

Thanks aidooyaw1992 that worked for me.
Another problem I had was that intl 0.16 is incompatible with flutter_localizations but you ca declare
dependencies:
...
flutter_localizations:
sdk: flutter
intl: 0.15.8
...
and then override
dependency_overrides:
intl: ^0.16.0
and it works for dependencies on intl ^0.16.0


2.0.2 Export Knowledge Base Snapshot

Execute export process to generate and store a snapshot of the knowledge base in Qdrant. This includes validating the data export to ensure completeness and accuracy, as well as performing any necessary post-export checks. Successfully exporting the knowledge base snapshot is vital for preserving a reliable and up-to-date repository of information that can be utilized by AI agents and other applications.
This process should be automated in the pipeline.
Resources:

How to generate a vector snapshot ((link)[https://docs.gaianet.ai/creator-guide/knowledge/text#create-a-vector-snapshot])

Solved in #14


Added forwarded port for sdm

Closes issue #2063 .

Can one of the admins verify this patch?

@ewpatton Please review.


flake: Update inputs

Pull in new Nickel that includes newer version of Topiary so that it can be pulled from the cache instead of rebuilt on each CI call.


Hotfix: Fix for Dropdown Re-rendering Infinite Loop

Jira
TBD
Summary
Hotfix patching infinite re-rendering loop reported by @EvanLovely in #1383 when the Dropdown component is rendering and Shadow DOM is disabled.
How to test
Test to confirm the re-rendering issue reported (aka the page crashes very quickly) no longer occurs when Shadow DOM is disabled -- either by setting the no-shadow prop on the component itself OR by wrapping the Dropdown in a <form> tag.

^ @adamszalapski the main issue @EvanLovely mentioned was patched on the develop branch during one of the early 2.8.0 beta releases which would explain why you weren’t seeing the infinite rendering loop issue.
Not 100% sure if these other issues are being caused by that fix or if these are separate issues...

For what it’s worth, I feel like ya originally using Handrogel for this particular component was a mistake.
Accordion and Navbar / Nav Priority already handle the complex interactive behaviors — Dropdown just really just needs to focus on toggling a container of content + handle click / keyboard events to auto-close. 🤦♂

@colbytcook closing and deleting. This change was merged in another PR, I think #1207.


Add Aurora RDS TF example to docs

PR 2/2 for https://github.com/weaveworks/weave-gitops-enterprise/issues/724
https://github.com/weaveworks/weave-gitops/pull/2339 should be merged first

What changed?
Add a more advanced use case to the TF template Guide in the docs.

Why was this change made?
This Guide adds instructions on how to use the TF-Controller in WGE to create an Aurora DB.

How was this change implemented?
N/A

How did you validate the change?
Tested these steps locally. Ideally, a reviewer would also go through the instructions to make sure it works for someone else as well and that no steps were missed.

Release notes
N/A

Documentation Changes

@nikimanoledaki Love this one.
Could you make it a bit self-contained by telling users how to install TF-controller at the beginning of the docs, please?

Thank you @chanwit 😄
The installation steps will be added in a different PR since these are still being decided, see Gini's comment and this ADR PR.
I would love to get your thoughts on some questions I outlined here :)


Create Profile for Charles Lotara

Name
Charles Lotara
Profile Image

Country
South Sudan
Region
Central Equatoria
Organisation
Eve Organization for Women Development
Languages
English (Excellent), Juba Arabic (Good)
Skill 1
Media & Art
Qualifications for Skill 1

Worked as a digital editor for The City Review newspaper for more than two years.
https://cityreviewss.com/caf-president-handed-five-year-ban-fined-219000/

Worked as a copy editor for Juba Monitor for one year.

Skill 2
None
Qualifications for Skill 2
No response
Skill 3
None
Qualifications for Skill 3
No response
Skill 4
None
Qualifications for Skill 4
No response
describe yourself
Charles is a professional South Sudanese journalist with over five years of experience in the mainstream media industry. He served as a copy editor for Juba Monitor before moving to The City Review newspaper, where he worked as an Acting Managing Editor and later as a Digital Editor.
E-Mail
<EMAIL_ADDRESS>Phone
+211928587380
WhatsApp
+211928587380
Website
No response
Telegram
+211928587380
GitHub
No response
LinkedIn
charleslotara
Twitter
charles_lotara
Facebook
charleslotara
Instagram
No response
Mastodon
No response
WikiFab
No response
Other
No response

hey @timmwille this is a duplicate profile the complete profile is at #332 so am closing this issue


.taw files

Hi, is there a way to write .taw (Terrain / Obstacle) files?

No - but if you post your services.xml file, I can take a look at supporting them. Run jdmtool login and jdmtool refresh, then (assuming you have Linux) it should be in ~/.local/share/jdmtool/. Just censor your username, email, customer ID, tail number, etc.


remove unused codegen test

Description of changes:
There was a CMake parameter called ENABLE_FUNCTIONAL_TESTING that at test time would use the code generator to create a "fake" aws client and run unit tests on it. From what i can tell this was from the early days of the SDKs where we didnt have many clients and it was useful to test the code generator. In its current state it is more or less noise and doesnt add any valuable testing to our current release process. We have decided to remove it to reduce the noise of our CMake paramters.
Check all that applies:

[x] Did a review by yourself.
[x] Added proper tests to cover this PR. (If tests are not applicable, explain.)
[x] Checked if this PR is a breaking (APIs have been changed) change.
[x] Checked if this PR will not introduce cross-platform inconsistent behavior.
[x] Checked if this PR would require a ReadMe/Wiki update.

Check which platforms you have built SDK on to verify the correctness of this PR.

[x] Linux
[x] Windows
[ ] Android
[x] MacOS
[ ] IOS
[ ] Other Platforms

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Do we want to remove all references to this cmake parameter: https://github.com/search?q=repo%3Aaws%2Faws-sdk-cpp ENABLE_FUNCTIONAL_TESTING&type=code


How do I work with multiple epics?

I'm missing an example of how to work with multiple epics. I know there's a combineEpics function in redux-observable. But epics look different in ng2-redux. Normally epics are functions. Here they are classes. That's why examples for redux-observable don't help a lot. The linked example app by Rangle also doesn't really answer that question.
How do I register more than one epic as store middleware? And can a class contain more than one epic or should there be one class per epic?

Okay, after fiddling a little I found the solution:
Yes, you can have multiple epics per class.
To combine multiple epics do this:
import { createEpicMiddleware, combineEpics } from "redux-observable";

@NgModule({
  declarations: [ /* ... */ ],
  imports: [ /* ... */ ],
  providers: [
    MyEpics,
    MoreEpics,
    /* ... */
  ],
  bootstrap: [ /* ... */ ]
})
export class AppModule {
  constructor(
    ngRedux: NgRedux<IAppState>,
    myEpics: MyEpics,
    moreEpics: MoreEpics,
  )
  {
    const epics = combineEpics(
      myEpics.login,
      myEpics.logout,
      moreEpics.loadData,
      moreEpics.loadMoreData,
    );

    const middleware = [ createEpicMiddleware(epics) ];

    ngRedux.configureStore(rootReducer, initialAppState, middleware);
  }
}

Hi @alinnert - epics with ng2-redux are exactly the same as for redux-observable - they are functions in both places.
In our example, our epic is a member of a class, but that's just for the sake of convenience: classes make it easier to access stuff from Angular2's dependency injector.
So your code above makes sense.

Hi @SethDavenport I'm trying to find a way to export all epics as single epic/variable/module. I'm used to combining stuff within a folder in index.ts and export a single variable.
Since in angular-redux epics are services I cannot just do export default combineEpics(MyEpics, MoreEpics) like I do with reducers. As shown by @alinnert I have to import all epics in AppModule and combine them there, but it's not a ideal because it's easy to forget to add a new epic whereas adding in effects/index.ts feels more natural.
Do you have any solution?

@jiayihu the animals example demonstrates a method for constructing the "root" epic using an epic factory  - https://github.com/angular-redux/example-app/blob/master/src/app/store/root.epics.ts
A more generalized example of the same approach can be found at https://github.com/arielpartners/capdash2/blob/master/webapp/src/app/store/root.epics.ts

I'm starting to like the approach taken in the animals example:
@Injectable()
export class RootEpics {
  constructor(private animalEpics: AnimalEpics) {}

  public createEpics() {
    return [
      this.animalEpics.createEpic(ANIMAL_TYPES.ELEPHANT),
      this.animalEpics.createEpic(ANIMAL_TYPES.LION),
    ];
  }
}

Since there is nothing very "animal" specific about the epics (standard ajax) a more general approach might be something like:
@Injectable()
export class RootEpics {
  constructor(private itemEpics: ItemEpics) {
  }

  public createEpics() {
    return [
      this.itemEpics.createEpic(ITEM_TYPES.INFO),
      this.itemEpics.createEpic(ITEM_TYPES.TOKEN),
      this.itemEpics.createEpic(ITEM_TYPES.USER),
      this.itemEpics.createSimpleEpic({
        action: {
          type: '@angular-redux/router::UPDATE_LOCATION',
          payload: '/'
        },
        filter: 'jwt',
        trigger: ItemActions.LOAD_SUCCEEDED
      }),
    ];
  }
}

https://github.com/arielpartners/capdash2/blob/master/webapp/src/app/store/root.epics.ts

Yeah at a fundamental level an epic is just a function that takes an observable of actions and maps it to a different observable of actions.
Our examples attach those functions as arrow functions to services so that we can inject stuff for them to use (e.g. Http).  But as long as you have a reference to that arrow function that's all that redux cares about.  So you can combine them however you want.
Or you can make a 'higher order' function that creates several epics based on some parameters as you have done with createAjaxEpic.
Then you just need to decide how to attach those epics to redux: either by calling createEpicMiddleware a bunch of times on member functions from several services and adding all the middlewares to the store; or by calling combineEpics first and creating one middleware.


[BEAM-6356] Use TFRecord to store cache results using PCollection's PCoder

To enable Python Interactive CacheManager to work with arbitrary types such as Google protobufs,
it should start using pcoder attached to PCollection instead of hard-coded one. It changes the file format for cache results to TFRecord to take advantage of direct writing and reading binary data.
R: @aaltay

LGTM. Thank you.
@qinyeli could you also take a look at it?

Thanks, Hennadiy!
Verified that it works with Jupyter notebook. LGTM


windows hidpi 200% , window position moves with the mouse

Very weird, but the mouse can still click the button, but the mouse is moving the button is also moving

This is known and actually something that is wrong with the UI library itself (See here). I will attempt to implement a fix by doing some calculation based the on the Windows scaling percentage, but I cannot guarantee perfection.

Fixed in this release, lemme know how it works for you!


Move API documentation from README to gitbook

Fixes #454.
This is a follow-up to PR #612; I took all the information from the README that wasn't already in the book and put it there, and then I replaced the API information in the README with a link to the book.  Let me know if there's any extra information you think is still missing from the book, and I'll add it!
Changes proposed:

Remove duplicate information in README.md in favor of gitbook reference.
Move remaining additional API details from README.md into gitbook.

Upgrade Path (for changed or removed APIs): N/A
Acceptance Checklist:

[X] All commits have been squashed to one.
[X] The commit message follows the guidelines in CONTRIBUTING.md.
[X] Documentation (README.md) and examples have been updated as needed.
[X] If this is a code change, a spec testing the functionality has been added.
[X] If the commit message has [changed] or [removed], there is an upgrade path above.

Coverage remained the same at 89.588% when pulling 70a0aef84fb8c1808c21c74c5a85d364bbfe79fe on ianprime0509:master into 4c1e59014061fb963740bcb0e5624b9a6c0e9972 on reactjs:master.

Fantastic! Thank you again, @ianprime0509!

I'll release the new version of the docs after merging this one.

No problem, happy to help!

Can you add [chore] to the commit message, please? I'm reviewing #588 right now, so we can release the docs and this new feature for v3.3.1.

Yes; I amended the commit accordingly.

Thanks!!

There is one place missing update (Table of Contents).

Oh, my bad!  I'll fix it and send in another (small) PR for it.


Integration: encrypt secrets on disk using Azure Key Vault

Actually, keeping the master key in Azure keyvault automatically enables that.
We don’t need a more sophisticatd mechanism (unless there is a community demand for it)


support require-adobe-auth on sequences

Describe the bug
Currently setting the annotation on a sequence doesn't add the /adobeio/shared-validators-v1/app-registry action to the sequence and hence doesn't protect the sequence. Individual web actions "components" of the sequence should also be protected with the require-whisk-annotation
Workaround
A workaround is to configure the protection manually:
runtimeManifest:
  packages:
    dx-excshell-1:
      license: Apache-2.0
      actions:
        action1:
          function: actions/action1/index.js
          web: 'yes'
          runtime: nodejs:18
          annotations:
            require-whisk-auth: true
        action2:
          function: actions/action2/index.js
          web: 'yes'
          runtime: nodejs:18
          annotations:
            require-whisk-auth: true
      sequences:
        mysequence:
          web: 'yes'
          actions: /adobeio/shared-validators-v1/app-registry, action1, action2

why does an action need require-whisk-auth here? Especially since they might want it to be public, as well as in a sequence?
If they wanted the action to require-whisk-auth, they can make it a non-web-action (web: false)

@shazron the idea is to protect the actions in the sequence. It's one way of doing it, the other way would be to delete the web annotation just like we do when parsing require-adobe-auth (https://github.com/adobe/aio-lib-runtime/blob/ea597e5a40c82f8a021dbaf10830774fb9eaeabe/src/utils.js#L1144)
Here is an updated workaround
runtimeManifest:
  packages:
    dx-excshell-1:
      license: Apache-2.0
      actions:
        action1:
          function: actions/action1/index.js
          runtime: nodejs:18
        action2:
          function: actions/action2/index.js
          runtime: nodejs:18
      sequences:
        mysequence:
          web: 'yes'
          actions: /adobeio/shared-validators-v1/app-registry, action1, action2


game keeps loading

After opening the game, it keeps loading the screen and does not enter the main game page.

I've been using the cheat without any problems for the past few hours, game runs just fine.
Have you tried running the game without booting up the cheat?

Which version of Proton do you use.
When I try to enter the game first, then turn on cheating and enter the matching wait, it will cause the game to remain waiting.
Everything is normal when I use grinder

How do I start it in debug mode


remote ssh failure

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.63.2
OS Version:fedora 34

Steps to Reproduce:
1.connect host
2.could not establish connection

output generated, but i can not copy


Build multi-arch images

Fixes #586, Replace #588.
While trying the ARM container image from #588, I noticed that the executable inside was in the wrong architecture and creating an "exec format error".
Changes:

Use TARGETARCH variable to pick the right base image in Dockerfile
Added build-container-amd64 and build-container-arm64 target to Makefile
Replace push-container target to use buildx build that push the multi-platform image to the registry

/assign @dchen1107

/assign @andyxning
Would you please review this PR, thank you!

sorry to butt in, but maybe @Random-Liu can make good on his offer to review? :wink:

/assign @Random-Liu

Ah, didn't check the PRs first. I wrote another version of this in #644

/remove-lifecycle stale

I have been working on getting our Kubernetes platform to work with arm64 and it would be amazing if this can be shipped soon 🙏

I have successfully built Node-problem-detector arm64 image locally using above made changes.
It will be very helpful if this PR is merged, and node-problem-detector image is released.

/close


Add commit message guidelines to CONTRIBUTING.md

I've added the guidelines to a separate branch. I do however need permissions to publish the branch to this repository.

You have to fork the project and create a pull request from your forked branch. You will find further information here. Thanks for your contribution.

You have to fork the project and create a pull request from your forked branch. You will find further information here. Thanks for your contribution.

Thank you. I've created the fork and pull request.

Closed with #89.


[Suggestion] Set default value of cronSchedule to * */6 * * *

The previous is * 0/6 * * *, but after a period of use I found it only executed at 0:00 every day, not every 6 hours. Set the value to * */6 * * * will the make the CronSchedule works as expected.

You're right. I was misled by https://crontab.guru/#0_0/6___* it seems.
I didn't originally go with * */6 * * * because it's impossible to escape in JSDoc for some reason. I'll switch the default to 0 0,6,12,18 * * * instead.


Tracking issue: Typst support

TODO:

[ ] richer Typst support, WIP at https://github.com/alexpovel/srgn/tree/typst

[ ] make it useful with type checking (aspell), for which the text node type seems most useful

[ ] which requires piping into aspell, for which srgn currently doesn't have good support. Probably needs refactoring the crappy apply function:
https://github.com/alexpovel/srgn/blob/9238fc161ceaf88dd754d71b4fb65393dcee964b/src/main.rs#L568
so its output is something like (command run on commit https://github.com/alexpovel/srgn/commit/47be5f0ed8aab2afb2e9e473ea3eac9ed4607cf3)
[filename if not stdin];linenum;startcol;endcol: text

e.g. (numbers made up)
$ cat tests/langs/typst/base.typ | c run -- -j --typ text --typ strings
[...snip...]
62;12;13: In case you missed it, there's a recording on
62;58;62: "http://purview.edu/lts/2023-lee"

i.e., it doesn't print non-text nodes such as #link(, as it currently does:

cc @ju6ge

Kinda blocked, as I'd prefer not vendoring and only using grammars part of the tree-sitter org. Otherwise, it can get pretty painful with updates and keeping things in sync (see HCL support in srgn).

For spell checking I was wondering if it might be sufficient to strip out the markup, similar to what the TeX tool detex does, only making this print the selected nodes in some mode. The resulting file could then be piped into a user's favourite spellchecker and should, for that task, probably be good enough?

Thanks for your thoughts!
I had considered skipping the whole part about "if srgn is piped into something that is not a terminal, use machine-friendly/parseable output" and instead just offer JSON output. That's much more flexible, and (probably) easier to implement at the same time. It avoids work on my side (coming up with a parse-friendly format), but also allows full flexibility on the reading side of the pipe. It could look like srgn --whatever | jq '.whatever' | spellcheck. You would "only" need to massage the jq query, which is infinitely more powerful than what srgn could ever offer (and an LLM could probably write it very well for you). Let me know if you have any thoughts on that.
(work on srgn is currently slow, sorry!)

I am not opposed to json. Might very well be more flexible when transformed with jq. The blocker on my side ist that I have not found a spell checking tool gives me simple enough output that can be further processed easily. So no need to apologise for slow development.


Sharing Data between Docker Containers

Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
This fixes #2151
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines

@WanjaMIKE I've made the changes. Thanks

@hectorkambow hello, my reviewer seems to have been off for a while. Is there a way to know the progress on the PR? Thanks.

@OkothPius - Check the message below. If you have already done so, you can ignore. Otherwise try to make a final push after updating your folder structure
In order to publish your article as soon as possible, please do the following:
- Download the most recent files off this PR (Make sure to pick the latest one with my revisions and edits).
- Delete your article directory from the articles folders.
- Do a git pull (take a look at the new structure of the repo after a git pull).```

@WanjaMIKE already did. Thanks

Thank you v much for your patience as we worked through our Repo re-structuring process.
The purpose behind this restructure - was to better allow us to handle more volume and allow students to publish more articles and get more involved with the community (with open-source contribution and suggestions).
With most of the changes coming to completion - we will be sure to get your article published asap.
Thank you again - and we are looking forward to more amazing articles.

Plagiarism check done 💯

Kindly, add a hero page to this artice

@WanjaMIKE done!

@OkothPius great work gents
cc @WanjaMIKE 🚀 (very minor formatting edits - please go through my final edits). 👍


Adding virtualisation for the table

Is your feature request related to a problem? Please describe.
I've been using this library for my project and found that there is no virtualisation available. We used a basic <div> like structure to render a list of items with react-window for performance purposes. Using mantine-datable is a delight, but then I could not find a way in which I can virtualise the list for handling large amounts of rows and columns. Our table has continuous pagination (infinite scrolling type) so virtualisation makes for a very strong use case.
Describe the solution you'd like
I explored other libraries like TanStack Table and it seems to have virtualisation enabled. If there could be a way to virtualise the rows it would do the job of handling extensive data without making the DOM heavy.
Describe alternatives you've considered
N/A
Additional context
N/A

+1

+1

Guys, this has already been discussed a number of times :-)
I'm fully aware of the benefits of virtualization, and I'm more than open to review/accept a PR implementing virtualization in a way that plays nicely with all the other features...

@icflorescu
I can work on it.
My question is, there are many ways to solve this:

Windowing ( React recommendation for Virtualize Long Lists )
Intersection Observer
Dynamic Loading
Memoization

I suggest windowing, because intersection Observer is new and maybe will be needed pollyfill.
We can use react-window or react-virtualized
what you think ?
PS: What you think to having Discord channel for this project?

@icflorescu  ?

Hey @AlexcastroDev, sorry for being unable to reply sooner, but I'm currently pretty caught-up in a deadline.
I don't have experience with any of them, but at the first glance  react-window seems the obvious logical choice.
So, yes, if you're up to it and have the time, feel free to have a go at it, I'd be happy to support in any way I can (though, as stated above, I'm currently under a bit of pressure) and your PRs are more than welcomed.
I have built a few other open-source projects besides mantine-datatable over the last years and learned that - while lots of users would come up with feature requests or how-to questions - very few are willing and/or able to contribute their own effort :-)
About setting up a discord channel for the project, yes, I did thought about it a while ago, but again, couldn't find the time to do it...


Device Support: T8970

Hi, external siren t8970 has been relasead by Eufy. The device is recognized by Addon but there's no way to trigger siren.
The error is:
Failed to call service button/press. {'type': 'result', 'success': False, 'messageId': 'device.reset_alarm.07f255530a63477abe52ec25be4c9005', 'errorCode': 'device_not_supported'}
Thank you.

Is it supported by eufy-security-client library, did you check?

https://bropat.github.io/eufy-security-client/#/supported_devices
I do not think it is supported, check with eufy-security-client first


Remove non-existing CPU metrics

I couldn't find any Elasticsearch versions where these CPU metrics
were exposed, so they are always set to 0.

I can't confirm all versions, but I can say that these are always 0 for my 7.x setup


Api calls better handling

After the approval of the state management intro.

Improve the structure
[ ] Add better api call structure. Depending on the Zustand make sure that the architecture of api calling is the correct one.
[ ] Loaders while the api call, in order to display to the user
[ ] Empty state if the response returned zero results
[ ] Error information, in case of an error

Added to the app


Add unwrap_type assist

I found this assist pretty useful

changelog feature add "unwrap type" assist

@lnicola I'm not sure to understand what you means sorry :/

@bnjjj no worries, I have had until 5 minutes ago some code that scrapes the GitHub PR pages to extract these comments and put things in their right place in the changelog.

I think that this use-case is better served by the more general expand selection infrastructure:

I wonder though, how do we teach users that this is possible? It took me some time to realize that this "select, copy, select more, paste" workflow is possible.

Is it also available in other editors than vscode ?

It should be, that's a standard protocol feature now: https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_selectionRange

Oh ok. I don't know then :/ to be honest when I'm looking for something to help me I just flood my quick fix shortcut haha

Closing based on https://github.com/rust-analyzer/rust-analyzer/pull/8070#issuecomment-804041892


Scanner position moves by itself

I run two scanners on two different accounts and set them coordinates. But every time the scanner which is below, moves two areas up And just did not scan areas I want. Marker is always on place where I set localization, but scanner gives a f*ck about that and scan in other place -.- Any possible solutions?

Are you sure you didn't give access to other people who manually change the location?
Also if they use the same db you'll see both results on the same web page

Nope, I didn't give access to anybody. I reinstalled app, didn't worked.  But it is some kind of javascript bug. I figured out how to deal with it. When second scanner was running, I manually move markers for both scanners(just a bit, maybe milimeters of first positions) and then it started to scan on proper places. I wonder if I use more scanners, must I do it after every scanner lanuch.


We should define a couple (say 3) of default topologies for different sizes

e.g.:

small (10-100 households)
medium (100-1000 households)
large (1000+ households)

:+1:

Perhaps we could then make ETMoses choose those defaults automagically based on the number of households in the scaled scenario.

I love automagic!


[UI] Create spool from the filament page

From the filaments page it would be nice to quickly create a spool by using either the click-menu or the actions column.

2 second mock-up of the idea...

Good idea :)


Implement Num.isZero as a low-level

This will be needed ahead of the Eq ability.
Closes #4223

Because other functions in Num.roc check for == 0, so otherwise we must generate them too

I still don't understand: what makes the generated version different from one generated by roc code?

Oh. The generated one is calling the low-level directly. The Roc code is calling Bool.eq, which after Eq ability, will be calling Eq.eq. But calling Eq.eq inherits an Eq constraint on the number variable, which we can't fulfill for Float. So to get around that, we want to call the eq low-level directly instead.


Circular dependency issue in the module

Bug report
Summary
There is a circular dependency warning when using the library that seems internal to the library. It's obviously not necessarily a bug but would be good to avoid the warning.
Environment info
react-native info output:
System:
    OS: macOS 10.15.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 651.83 MB / 32.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.17.0 - ~/.nvm/versions/node/v12.17.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v12.17.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.0
      System Images: android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_231 - /usr/bin/javac
    Python: 3.7.7 - /Users/memetral/miniconda3/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 0.27.1
Steps to reproduce

Oh - perhaps important detail - I'm using a monorepo.

I'm seeing the same circular dependency issue. react-native v0.63.2, react-native-maps v0.27.1

this was not fixed

this was not fixed

any new about of this issue ? still happends


can't run any fxlauncher commands (gradle)

Both on my project and on the demo project I get this error if I run generateNativeInstaller gradle command.
`> Could not resolve all dependencies for configuration ':internal_fxlauncher'.

Could not resolve no.tornado:fxlauncher:1.0.16.
Required by:
no.tornado:fxldemo-gradle:1.0
Could not resolve no.tornado:fxlauncher:1.0.16.
Could not get resource 'https://repo1.maven.org/maven2/no/tornado/fxlauncher/1.0.16/fxlauncher-1.0.16.pom'.
Could not GET 'https://repo1.maven.org/maven2/no/tornado/fxlauncher/1.0.16/fxlauncher-1.0.16.pom'.
Connection to https://repo1.maven.org refused
Could not resolve no.tornado:fxlauncher:1.0.16.
Could not get resource 'https://jcenter.bintray.com/no/tornado/fxlauncher/1.0.16/fxlauncher-1.0.16.pom'.
Could not GET 'https://jcenter.bintray.com/no/tornado/fxlauncher/1.0.16/fxlauncher-1.0.16.pom'.
Connection to https://jcenter.bintray.com refused`

I am also behind a corporate proxy if that matter though other packages work just fine.

It seems your corporate proxy is prohibiting you from accessing the maven central repo mirrors, so you need to work around this somehow :) Maybe you can add proxy parameters to the jvm as described here:
https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html
Hope this helps :)

Well you were right. I didn't even expected the proxy to be an issue since I set it in intelij's settings and other packages seemed to work just fine.
If anyone fell for the same issue, to fix this I created a gradle.properties with the following content
`systemProp.http.proxyHost=<YOUR_HTTP_PROXY_HERE>
systemProp.http.proxyPort=<YOURS_HTTP_PROXY_PORT_HERE>
systemProp.https.proxyHost=<YOUR_HTTPS_PROXY_HERE>
systemProp.https.proxyPort=<YOURS_HTTPS_PROXY_PORT_HERE>

Great! Thanks for updating the ticket, I'm sure that will be useful to others.


Range processing bug.

Description
A sentence or two describing the issue.
Add info or delete as appropriate:
https://tex.stackexchange.com/questions/597185/range-option-not-working-properly-in-setmathfont
https://tex.stackexchange.com/questions/348481/when-specifying-a-character-in-unicode-maths-range-option-why-are-alternativ
Minimal example demonstrating the issue
\documentclass{article}
\usepackage{unicode-math}
\setmathfont{Latin Modern Math}
\setmathfont{XITS Math}[range={`0-`9}]
%\setmathfont[range={}]{Latin Modern Math}

\begin{document}
<PHONE_NUMBER>
	$ x^{2}+y^{2}=z^{2}, \xi\alpha\beta,<PHONE_NUMBER> $
\end{document}

The font for numbers is not set.

If add something to the range
\documentclass{article}
\usepackage{unicode-math}
\setmathfont{Latin Modern Math}
\setmathfont{XITS Math}[range={`0-`9,"0391}]

\begin{document}
1234567890
$ x^{2}+y^{2}=z^{2}, \xi\alpha\beta,<PHONE_NUMBER> $
\end{document}

The font is changed is there's at least one code point in the final range which is located in "0391-"03A1,"03A3-"03AF,"03B1-"03BF,"03F4,"2202,"2207,"1D434-"1D454,"1D456-"1D467,"1D6E2-"1D6FA,"1D6FC-"1D714
Further details

Range
Meaning

U+0391- U+03A9
Greek Capital Ketters (U+03A2 is Undefined Character)

U+03AA, U+03AB
ΪΫ Greek Capital Letter with Dialytika

U+03AC - U+03AF
Greek Small Letters with Tonos

U+03B0 (not working)
ΰ Greek Small Letter Upsilon with Dialytika and Tonos

U+03B1 - U+03BF
Greek Small Letters from alpha to omicron

U+03C0 - U+03C9 (not working)
Greek Small Letters from pi to omega

U+03CA - U+03E1 (not working)
Some Viariants of Greak Letters

U+03F4
ϴ Another Capital Theta

U+2202，U+2207
partial and nabla

U+1D434 - U+1D467
Math letters of A-Z and a-zU+1D455 is not defined, mathmatical h is at U+210E (not working)

U+1D6E2 - U+1D6FA
Math Greek Capital Letters

U+1D6E2 - U+1D6FA
Math Greek Small Letters

I have a related but opposite issue when unicode-math 0.8q (2020/01/31) is used with XeTeX 3.141592653-2.6-0.999995 or LuaHBTeX 1.17.0 shipped with TeX Live 2023. If I specify range={up, X}, where X is from the following table, up is ignored:

codepoints
characters

U+00391–U+003A1, U+003A3–U+003A9
Α–Ω

U+003B1–U+003C9
α–ω (incl. ο, ς)

U+003F4
ϴ

U+02202
∂

U+02207
∇

U+1D434–U+1D44D
𝐴–𝑍

U+1D44E–U+1D454, U+1D456–U+1D467
𝑎–𝑔, 𝑖–𝑧

U+1D6E2–U+1D6FA
𝛢–𝛺 (incl. 𝛩, 𝛳)

U+1D6FC–U+1D714
𝛼–𝜔 (incl. 𝜍, 𝜎)

Here is the script that prints out each offending codepoint. Be warned that it may take days to loop through all the codepoints:
import os
import subprocess

latex = 'xelatex' # or 'lualatex'

doc1 = r'''
\documentclass{article}
\usepackage{unicode-math}
\setmathfont{XITS Math}
\setmathfont{TeX Gyre Termes Math}[range={up, "
'''.strip('\n')

doc2 = r'''
}]
\begin{document}
$\symup{ABC}$
\end{document}
'''.strip('\n')

for code in range(0x20000):
  char = chr(code)
  hex  = f'{code:05X}'
  uni  = f'U+{hex}'

  try:
    subprocess.run(
      [latex, f'--jobname={uni}'],
      check=True, input=doc1+hex+doc2, stdout=subprocess.DEVNULL,
      encoding='utf8')
    result = subprocess.run(
      ['pdffonts', f'{uni}.pdf'],
      check=True, capture_output=True, encoding='utf8')
    if 'TeXGyreTermesMath' not in result.stdout:
      print(uni, char, flush=True)
  except:
    print(uni, char, 'error', flush=True)
  finally:
    os.remove(f'{uni}.log')
    os.remove(f'{uni}.aux')
    os.remove(f'{uni}.pdf')


Pano Logic G1 devices?

 Did you happen to have any of them or just the G2? They have a smaller device in them that is supported by webpack which is why I never picked up any of the G2 devices (as ISE doesn't support them without a license).
I'm going to make an effort at continuing reverse engineering the G1 devices, maybe turn them into a tiny Sparcstation LX or Mac (Plustoo port) device I think that would be pretty neat as they have just enough ram to pull something like that off, or I could swap the ram chip for a larger version of course.
Anyway I figure your openocd scripts will be useful so thanks for that!
Also since you seemed to have some interest in the protocol... the sunray protocol may be interesting to you as well (and it has been reverse engineered to a large extent as I understand). http://www.jopenray.com/

I started working on the G1 a month or two ago.
I'm made decent progress. Next step is getting audio up and running:
https://tomverbeure.github.io/pano/logic/2018/06/04/pano-logic-project-update.html
Tom


Changes to reduce the variability of timings in smoke/launch_latency.

Added a Python program to search the results.csv file produced by "rocprof --stats" and return the average kernel times for the various number of teams.

The test used to report a first kernel time, but that doesn't appear in the new output
1st kernel Time 0.01254017

Also, instead of reporting this:
avg kernel Time  21882.86 TEAMS=  1
please add a unit (I'm guessing ns):
avg kernel Time  21882.86 ns TEAMS=  1
as the extract-tests script will report it as seconds (saw "Time") if no units are given.


Relax tslib requirement specifier

Brief Information
This pull request is in the type of:

[ ] bug fixing
[ ] new feature
[x] others

What does this PR do?
Relax dependency specifier of tslib
Fixed issues

Details
Before: What was the problem?
I was testing my library with vite v6.beta, and found that<EMAIL_ADDRESS>did not work; later version of tslib did work.
After: How does it behave after the fixing?
echarts now allows users to pick their own version of tslib - so a. it now works with vite v6 and b. users aren't unecessarily shipping two copies of tslib
Document Info
One of the following should be checked.

[x] This PR doesn't relate to document changes
[ ] The document should be updated later
[ ] The document changes have been made in apache/echarts-doc#xxx

Misc
ZRender Changes

[x] This PR depends on ZRender changes (ecomfe/zrender#1097).

Related test cases or examples to use the new APIs
N.A.
Others
Merging options

[ ] Please squash the commits into a single one when merging.

Other information

Curious about why tslib 2.3.0 doesn't work.
I can not reproduce it with<EMAIL_ADDRESS>Could I have more info to reproduce it? @mrginglymus
What I've done is:
npm i -D<EMAIL_ADDRESS>npm i echarts
touch index.html

            <!DOCTYPE html>

                    <meta charset="utf-8">
                    <meta name="viewport" content="width=device-width, initial-scale=1" />

good

npx vite

And the chart displayed normally.

@Ovilia @plainheart
Does this modification lead to breaking change?
Or should we do full test against different version of tslib? or check every breaking changes of tslib since 2.3.0 to latest?
Or should we make this change in a patch version if it might introduce breaking or error?

Honestly I didn't spend too much time on working out the why, only the what.
The error as spotted was this:

I will see if I can dig into what was wrong with vite here, as it may be worth an issue on their end as a regression.
Aside from compatibility in whatever obscure set of conditions I've discovered, the more significant benefit of this change is allowing users to ship only one copy of tslib; I currently use<EMAIL_ADDRESS>to support decorators and whilst the size of tslib is insignificant compared to the echarts stack, it still bugs me to be shipping two copies.

Some monos:

Found that at present echarts only uses __extends function of tslib. (by searching from "tslib in echarts/lib.).
About bundle size: After tree shaking (tested in<EMAIL_ADDRESS>tsc -b && vite build), only used functions of tslib will be included in bundle. That is only __extends (and extendStatics, which is called by __extends internally) is included. So the bundle size is probably not a concern till now.
Compatibility if changing to "tslib": "^x.x.x": Checked the commit log of __extends on git, there's no breaking. Thus this change does not break echarts.
Use different versions of tslib in one JS context: (tested in<EMAIL_ADDRESS>tsc -b && vite build) , the build bundle is like this :// At the top scope of the bundle file dist/assets/index-JsGP8STl.js
// Two tslib are included but the name are modified to avoid conflict.
var extendStatics$1 = function(d, b) { /* ... */ };
function __extends$1(d, b) { /* ... */ }
/* ... */
var extendStatics = function(d, b) { /* ... */ };
function __extends(d, b) { /* ... */ }


[Event Request] Codeunit 415 - "Release Purchase Document" - OnCodeOnAfterPurchLineSetFilters

Dear ALAppExtensions team,
through this issue we would like to request adding a parameter to event publisher OnCodeOnAfterPurchLineSetFilters in Codeunit 415 "Release Purchase Document" with the following signature:
[IntegrationEvent(false, false)]
local procedure OnCodeOnAfterPurchLineSetFilters(PurchaseHeader: Record "Purchase Header"; var PurchaseLine: Record "Purchase Line"; var IsHandled: Boolean)
begin
end;

which would be used to control the execution of functionality related to PurchLine.Find('-') in procedure CheckPurchLines (comparable to the corresponding Event in Codeunit Release Sales Document) as follows:
local procedure CheckPurchLines(var PurchLine: Record "Purchase Line")
    var
        IsHandled: Boolean;
    begin
        IsHandled := false;
        OnBeforeCheckPurchLines(PurchaseHeader, PurchLine, IsHandled);
        if IsHandled then
            exit;

        PurchLine.SetRange("Document Type", PurchaseHeader."Document Type");
        PurchLine.SetRange("Document No.", PurchaseHeader."No.");
        PurchLine.SetFilter(Type, '>0');
        PurchLine.SetFilter(Quantity, '<>0');
        // >>>OLD>>>
        // OnCodeOnAfterPurchLineSetFilters(PurchaseHeader, PurchLine)
        // <<<OLD<<<
        // >>>NEW>>>
        IsHandled := false;
        OnCodeOnAfterPurchLineSetFilters(PurchaseHeader, PurchLine, IsHandled);
        if not IsHandled then
        // <<<NEW<<<
            if not PurchLine.Find('-') then
                Error(Text001, PurchaseHeader."Document Type", PurchaseHeader."No.");

        CheckMandatoryFields(PurchLine);
    end;

Thanks in advance!

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: 11076.


HTML reports

It would be nice to have the possibility to generate local HTML coverage reports like lcov does without having to rely on external tools like travis or coverall. Mostly, having a percentage indicators and a function breakdown while being able to browse the code would be a very valuable addition. imo.

So that is the main approach I was thinking of for the road-map item of "annotated coverage reports". I realise that's really open ended and non-specific but I was leaving my options open. I haven't really worked on it yet because no one's expressed an interest in the feature. Until now!
I'll start investigating and try to get something in for my 0.6.x release. I'm not gonna make any promises yet just cause it's early days. But if I have any updates I'll let you know here.

Great, thanks a lot.
As always time is scarce, but I'm happy to lend a hand when possible

Thanks for the offer. Firstly, I'll need to choose a crate to let me generate the html. I'm having a look at some options but if you have any specific recommendations I'd be open to suggestions :+1:

There's a ton of template crates (there's a ton of everything Rust right now...). Have a look at https://github.com/rust-unofficial/awesome-rust#template-engine. I think something simple with as few dependencies as possible would be nice here, I think horrorshow-rs looks interesting.
Otherwise I would probably use serde and implement a custom deserializer into HTML.
Just my two cents of course!

What about generating markdown and letting that get rendered using a markdown crate?

So there's currently significant process on this that hasn't yet been pushed to github yet. There are more interactive elements like a project browser to let people browse their results. No one get too excited yet but wait and see what's in store :wink:

OK, sounds good :) .

Hey @xd009642 Im totally interested in this project, could I help in this one?

Hmm I'm not sure how easy this one is to jump into, it's being done as part of a near complete rewriting of the report module. Also the HTML reports are actually designed, it's now just a case of doing the rewrite and filling in the template.
If you're open to other issues, #54 #113 and #63 might be good ones to work on. (Though #113 depends how comfortable you are reading the cargo source code).
I was also going to look into what windows support would take - though that is a big addition

@xd009642 Yeah! I didn't think that will be easy. Correct me if I am wrong, tarpaulin didn't create any kind of coverage files.
In my vision, we need to improve the CLI output and format a .lcov file! Has many HTML reporters that accept lcov + code string and create the reporter automatically <3
About another issues: I'm taking a look at the list into #63, and unsure if I understand #113! But I will try open PR's in the next days!

Just using kcov somedir/ target/debug/test-6e8607e47b97cdb7 gives nice HTML reports.
Can tarpaulin just automatically call kcov if it is available and put the HTML into some target/coverage/?

I kinda don't see the need for tarpaulin to call into another code coverage tool as part of it's run. Supporting standard outfor formats like the lcov file and cobertura is much more productive I feel. For example you can get html reports currently by processing an outputted cobertura.xml with pycobertura (which is detailed in the readme).
Tarpaulin will be rolling it's own HTML reports with additional information that isn't relevant to other HTML reports which also enables future reports like condition coverage, MCDC etc which I haven't seen in other open source tools.
When the reporting module is in a state others can work on it, I think generating a .lcov file would definitely be a good addition 👍


Lutris Support

Hi All,
is there any way this supports GW1 as run though Lutris as this is my main driver, I'd love to use the tool there as well. Have dug around a bit but could not get it to run. Does anyone have experience with it and can point me to a tutorial or guide?
Also if such a resource exists, can we put it in the documentation of the Repo?
Regards,
jan

It should technically be possible, but we cannot offer support for Linux with emulation layers, as this is a windows game.

Comment from discord:

if I want to answer this guy who is asking about Lutris support I need a github acc? I ran GW+Toolbox through lutris before. I'm assuming he already has GW running fine. IIRC I installed the DirectX Redistributables which are in the FAQ of tb website in the Wine instance(wrong wording, but dunno right one) used for GW. then I installed tb on the same wine instance and at last I started tb through lutris while GW was already running.


x-client-X-MS-CLIENT-PRINCIPAL-NAME header is only available on the first call to oninitialized

Description
if you deploy your code in app service and have app service check authentication, the x-client-X-MS-CLIENT-PRINCIPAL-NAME header is only available on the first call to oninitialized()... so disabling is probably necessary and needs to be documented.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/lifecycle?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/lifecycle.md
Document ID
4871f4f7-9cf6-ac7a-0f21-c65d34bd1119
Article author
@guardrex
Related Issues

I assume this is an internal feedback item, so I can't discuss this with the dev.
That task wouldn't be handled that way in a Blazor app. The auth state provider can establish a claim from the header. And ...

disabling is probably necessary and needs to be documented

... makes no sense without additional context.


Move Component Embedded Simulator next to its example

Right now the embedded simulator is always at the top right corner.
This can be confusing as to what code is associated with the simulation.
So, move the simulator next to its actual code.
This has the added benefit of allowing us to use the React Native
Web Player for the simpler examples in the components.
Test Plan:
http://localhost:8079/react-native/docs/switch.html

By analyzing the blame information on this pull request, we identified @caabernathy and @janicduplessis to be potential reviewers.

Yay, thanks - this was bothering me too.

LGTM

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


Bump version to 2.0.0 for plotAsOutline in mm

Coverage remained the same at 100.0% when pulling 0acf031688dc44b038b895f254c1c057e9567d5e on bump-to-2.0.0 into 90c59d21334b0b15d058d921f5a361a88e9b9a2b on master.

Coverage remained the same at 100.0% when pulling 0acf031688dc44b038b895f254c1c057e9567d5e on bump-to-2.0.0 into 90c59d21334b0b15d058d921f5a361a88e9b9a2b on master.

Coverage remained the same at 100.0% when pulling 0acf031688dc44b038b895f254c1c057e9567d5e on bump-to-2.0.0 into 90c59d21334b0b15d058d921f5a361a88e9b9a2b on master.


Wrong prefix when configuring via pkg-config

It appears the prefix in ujit.pc is always /usr (or whatever the system default is) even when a non-standard prefix is set via CMake:
$ cmake -DCMAKE_INSTALL_PREFIX=~/local .
...
$ make install
...
$ PKG_CONFIG_PATH=~/local/lib/pkgconfig pkg-config ujit --cflags
-I/usr/include/ujit

ujit.pc.in:
prefix=@CMAKE_INSTALL_PREFIX@

instead of
prefix=/usr

would solve the issue.


Earthdawn (by FASA) v3.01 - Big Fixes

V3.01 Bug Fixes

Submission Checklist
Required

[X ] The pull request title clearly contains the name of the sheet I am editing.
[ X] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[X ] The pull request makes changes to files in only one sub-folder.
[ X] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

Character Sheet Info Roll20 Internal Use only.


module initialisation functions

yotta should provide a way for each module to have an initialisation function called.
preferred method:

__yotta_module_init or __yotta_module_<modulename>_init which you add  __attribute__((constructor)) to, (toolchains possibly provide a nice abstraction for this attribute). when creating your library yotta adds the right -Wl,-u etc. options to pull in this symbol if it's undefined, and to suppress errors if the symbol isn't defined.

I've been experimenting, but haven't figured out if this is uniformly possibly yet.
If the preferred method isn't possible, other implementations might include:

add method name(s) to module.json that you must have defined
instead of using the constructor attribute and c library startup code to run the init function, a yotta-init module could collect them all with custom CMake, and provide a idempotent initialisation API that any module can call to ensure initialisers have been called.
system libraries (like mbed) that define startup code may hide the use of this initialisation library from the user by calling it at startup.

Preferably whatever mechanism is used to call the init function should support calling de-init functions (at least in theory), so that the possibility of dynamically loading and unloading yotta modules is not precluded.
cc @bremoran @hugovincent

I've been experimenting, but haven't figured out if this is uniformly possibly yet.

Do you mean across toolchains? Looks like at least gcc, Clang and ARM tools support this gcc extension too, which is good.
Is __yotta_module_init  (or __yotta_module_<modulename>_init) a name Yotta is explicitly aware of?  Or is it something used by convention (with the only explicit awareness on Yotta being the -u __yotta_module_init etc)? For user-friendliness and search-ability (and to hide any toolchain variations), maybe Yotta should define YOTTA_MODULE_INIT() or something at the compiler command line that expands to e.g. void __yotta_module_<modulename>_init() __attribute__((constructor)). Then in the module source, you would write:
YOTTA_MODULE_INIT()
{
   ...
}

(I wonder if we should also document the existence and use of __attribute__((destructor)) (even if it won't ever be called at present, at least in mbed) and/or provide the appropriate macro as above to better support dynamic loading/unloading in the future?)
From reading this, it is good to know that priorities (to control ordering) are available if we need them, but choosing the priorities would be pretty difficult for a module author. Could Yotta do anything to help? For example if a macro was defined as above, maybe priorities could be synthesised from the Yotta depgraph. Or at least give us the option to do that in the future.
Note that either relying on C runtime, or an idempotent API as you describe may prevent or complicate some more advanced future use cases for this in early boot in mbed, where more explicit ordering control may be needed (example, with reference to our conversation on Slack: an embedded platform with DRAM on a SODIMM, using an I2C/SMBus memory to read the EEPROM config data before configuring the memory and allocator). To solve this, the simplest way would probably be to introduce groups, and provide the guarantee that all initialisers in one group are called before the next group are called -- that could probably be done with priorities, a macro, and a contract across the system for how groups are used. But having explicit named groups collected into named sections would permit more control and be more readable and understandable.

My preference, even if it's a little less generic and the implementation more complex, is to permit yotta to collect specified sets of initialisation symbols matching a specified pattern. Example semantics:

permit arbitrarily many "exports" specified in module.json using e.g. an "exports" key, that by default do nothing.
an ability to capture them into groups using (JSON-schema flavoured) regexes that operate over all exports the exports in a given module's dependencies.
have Yotta generate header file(s) for them. Example top-level module.json:

{
  "name": "helloyotta",
  ...
  "captureExportsGroup": {
    "pattern": "^(ExampleGroup_.*)$",
    "transform": "&$1", // this would use Javascript "".replace(/regex/, "$1") semantics for example.
    "join": ",\n",
    "header": "fptr_t myInitFunctionPointers = {\n",
    "footer": "}\n",
    "generatedFile": "relative/path/to/MyInitFunctions.h"
  }
}

Resulting generated C header file:
fptr_t myInitFunctionPointers = {
    &ExampleGroup_example1,
    &ExampleGroup_example2
}

Big disadvantage of this include the fragility of non-trivial JavaScript regexes and transforms when implemented in Python, and that it's making Yotta be a bit of a programming language which might be undesirable.

Do you mean across toolchains? Looks like at least gcc, Clang and ARM tools support this gcc extension too, which is good.

Yes, but this isn't the hard part: the problem is being able to ask the linker to pull in a symbol whether or not you've actually defined it.

Is __yotta_module_init (or _yotta_module_init) a name Yotta is explicitly aware of? Or is it something used by convention (with the only explicit awareness on Yotta being the -u __yotta_module_init etc)?

Yes, it's explicitly aware of it because it has to do -u or whatever.

YOTTA_MODULE_INIT

Sure, why not.

(I wonder if we should also document the existence and use of attribute((destructor)) (even if it won't ever be called at present, at least in mbed) and/or provide the appropriate macro as above to better support dynamic loading/unloading in the future?)

Yup, that's what I was thinking of as the corresponding unload mechanism.

From reading this, it is good to know that priorities (to control ordering) are available if we need them, but choosing the priorities would be pretty difficult for a module author. Could Yotta do anything to help? For example if a macro was defined as above, maybe priorities could be synthesised from the Yotta depgraph. Or at least give us the option to do that in the future.

No, as we discussed, without complete coordination between all module authors, or the app author defining everything, init functions will have to be written in a very defensive manner to be safe. I don't believe there's any way to avoid that.

Note that either relying on C runtime, or an idempotent API as you describe may prevent or complicate some more advanced future use cases for this in early boot in mbed, where more explicit ordering control may be needed (example, with reference to our conversation on Slack: an embedded platform with DRAM on a SODIMM, using an I2C/SMBus memory to read the EEPROM config data before configuring the memory, before enabling the memory allocator. Thus some early boot stuff might have to be runnable without the ability to malloc).

Defensively programming init functions wouldn't necessarily require mallocing. You'd just need to use an EEPROM driver that didn't need to malloc.

My preference, even if it's a little less generic and the implementation more complex.

Umm, OK – why would you prefer something less generic and more complex over something simpler and more generic?
The most important goal of this is to do it in a way that is as simple as possible – for people to use, if not for us to implement!

so:
associating the correct undefined flags with a static library so that they get propagated by cmake to any executable that links that library has proven impossible to do in a straightforward way.
I'm now thinking that having an "modloader" module that provides an API for the system startup code to call all the registered initialisation functions is the way to go.
This module will probably work by generating source from CMake based on a yotta-defined list of exported symbols: in any case there will be nothing special about it, so replacing/extending it with functionality to provide ordering/groups of init functions should be possible. Multiple such modules should even be able to co-exist in an application.

If the undefined flags thing didn't work, why not have a module.json key to tell the build system that you're using YOTTA_MODULE_INIT? If you define it as true and the symbol is missing, that is correctly an error.

I still prefer my proposed approach above with module-controlled export and collection preferable to the "modloader" approach.

To be clear. It's possible to make undefining symbols work, but what I can't make work in a sane way is for you to be able to link against a module in custom CMake, and have its initialisation function called correctly – without significant additional yotta magic in all custom CMakeLists.
It isn't so much the "telling the build system that you're using an init function" that's the problem, but propagating the flags to pull in that init function through CMake to everywhere they need to be.
It isn't possible to just add an extra  target_link_libraries(your module "-Wl,-u,__yotta_module_load" "-Wl,-u,__yotta_module_unload") because those flags will appear after your library on the linker command line of any executable that uses your library – they need to appear before it. As far as I can find there is no built-in mechanism for doing that (and simply listing the library in its own dependencies so that it appears twice doesn't work either, as CMake deduplicates it).

(I didn't appreciate this difficulty when I wrote my first comment, which is probably the cause of confusion)

Thanks for the clarification.

After more discussion, I think we agree that Yotta shouldn't itself do the string munging as in my proposal above. How about instead, the Yotta module.json has a key for exporting symbols that are made available to the build system, so that the munging can be done by a script called by CMake?

I'm wondering if the right answer here is to generate a C/C++ file that calls the functions defined in module init.

As demonstrated in https://github.com/ARMmbed/mbed-example-network/issues/31, the lack of module initialization functions forces network objects to be created on the heap.  It is not possible to statically allocate a network object, since it must be initialized after the stack registration (e.g. lwipv4_init()).

@bremoran got it, thanks.

It feels a bit weird and dangerous to me to rely on yotta to define initialization order for C/C++ functions and/or objects. If we do it, at least we need to let the users know how their initialization works.

Ok, fair enough. But we also need to be prepaired for situations when a module needs to initialize something before another module on which it depends, because this might happen sooner or later. Also, it A depends directly on B, C and D, what should be order for calling B, C and D's respective initialization functions? (I'm guessing the same order in which they are listed in module.json?)

The order should be irrelevant, otherwise the modules should express a dependency.


Better error messages for mismatched data and datatype?

If I do something wrong like this:
import holoviews as hv
shape = (100, 100)
img = hv.Image( (range(shape[1]), range(shape[0])), datatype=['grid'])

I get an error message like this:
Traceback (most recent call last):
  File "note2.py", line 4, in <module>
    img = hv.Image( (range(shape[1]), range(shape[0])), datatype=['grid'])
  File "C:\holoviews\holoviews\element\raster.py", line 256, in __init__
    Dataset.__init__(self, data, kdims=kdims, vdims=vdims, extents=extents, **params)
  File "C:\holoviews\holoviews\core\data\__init__.py", line 231, in __init__
    datatype=kwargs.get('datatype'))
  File "C:\holoviews\holoviews\core\data\interface.py", line 194, in initialize
    if interface in head:
holoviews.core.data.interface.DataError: None of the available storage backends were able to support the supplied data format.

I had to stare at that for a while to realize I hadn't supplied the third dimension, rather than that e.g. I'd forgotten to install some appropriate backend.

I made one round of improvements to the data interface validation which made things a little bit better but is still far from perfect and downright terrible in many cases so there definitely needs to be more work in this regard. There are probably other cases mentioned in https://github.com/ioam/holoviews/issues/2101

Actually, when I look at GridInterface, I see the kind of error I'd expect: raise ValueError("Values for dimension %s not found" % dim) (https://github.com/ioam/holoviews/blob/master/holoviews/core/data/grid.py#L92)
I could investigate why that's not happening.

Sorry, didn't see that issue!

Yes, this is an important problem that has bitten me several times.  It sounds like the current logic is to assume that any error in a data interface just means that it's not supported, with only a specific type of error actually reported to the user.  Can we switch that logic around so that all errors are reported by default, and only a specific type of error causes it to move on to the next interface silently?  That seems like it would be a safer and more informative approach; basically, whenever we find bogus errors raised that indicate that the data interface simply doesn't support this data, then we catch those in the data interface and re-raise them as the one type of exception that causes HoloViews to move on to the next interface.  Anything else goes to the user as a real error.  Would that work?

Can we switch that logic around so that all errors are reported by default, and only a specific type of error causes it to move on to the next interface silently?

No I really don't think so, endless things would break and it would take a long time and a lot of code to ensure things continue working as expected. As I described above errors that can be safely raised and indicate a definite error already use the DataError exception type which will be re-raised immediately.
I think we should simply write some dedicated code to pre-validate the python literal formats including tuples, dictionaries and lists.

Prevalidating python literals sounds straightforward and like it will catch a lot of simple problems, so I'm all in favor of that.
But let's say you've done that; won't there still be the same problem, i.e., endless other things that are actual issues with the data or how it's supported or not by the various data libraries, that the user needs to know about in order to correct them or work around them?  I.e. aren't there an untold number of exceptions that pandas, xarray, or other underlying libraries can raise that we can't really anticipate or know about, and that users can't address if they aren't given that information?

Maybe the existing error message could suggest a special mode users could enter, a special flag to pass, or something like that, which would show all the exceptions raised by all the data backends considered, so that users could figure out what the real problem was?

This is a pretty tricky problem. I think I would be in favor of exposing some validation tools explicitly to the user to debug things when they have a problem. The do idea of a special debug mode might be one easy solution but I suspect figuring out what is going on when there is an error would be really tricky, even for advanced users. Alternatively, some good links to some docs detailing what the data should look like?

Maybe the existing error message could suggest a special mode users could enter, a special flag to pass, or something like that, which would show all the exceptions raised by all the data backends considered, so that users could figure out what the real problem was?

I've considered that and it's probably a good idea, basically you'd have a debug flag or similar which simply prints the errors from all interfaces that were tried.

Or given that the default error message is basically useless maybe it should simply do that by default.

aren't there an untold number of exceptions that pandas, xarray, or other underlying libraries can raise that we can't really anticipate or know about

This is true but there is specialized logic to handle specific types, e.g. if you pass in an xarray object it will recognize that only the xarray interface understands that data and therefore the actual error will be reraised. It's only in ambiguous cases, i.e. mostly the python literals, where it doesn't know which error is the most appropriate and therefore does not reraise any specific error.

Ah, that makes sense.  Thanks.
Sounds like adding the explicit validation for Python literals will help a lot then, and then if the above generic error message is still reached, showing all the errors from every backend considered would do it.


Trying to find Corp-Laptop VM

Virtual machines folder shows no corp-laptop VM files

Hi,
You’re right, I’ll upload the Corp-Laptop VM.
Thank you for your feedback.
Regards.
Roberto M.
Get Outlook for iOShttps://aka.ms/o0ukef

From: ahatamleh @.>
Sent: Friday, July 1, 2022 4:28:40 AM
To: PacktPublishing/Incident-Response-with-Threat-Intelligence @.>
Cc: Subscribed @.***>
Subject: [PacktPublishing/Incident-Response-with-Threat-Intelligence] Trying to find Corp-Laptop VM (Issue #1)
Virtual machines folder shows no corp-laptop VM files
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPacktPublishing%2FIncident-Response-with-Threat-Intelligence%2Fissues%2F1&data=05|01||c0f4152f4ee24afe803808da5b441616|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637922645226334923|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=VIODcVaIIZbf0GOqHFNetWXk%2BXoziheqGpt0se0Qhng%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABZNMYQB2ZVGTB6ZYNOTHNDVR224RANCNFSM52MC7GKQ&data=05|01||c0f4152f4ee24afe803808da5b441616|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637922645226334923|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=PbH8Bi3mksT%2B503d6b0cPuoFQ9zQ0QksUJfPmNO4a%2Fc%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I cannot install the VM snapshot. saying I need the vmx configuration file. please help.


chore: update dispatch event type

First-time contributors' checklist

[ ] I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added, or deleted? (Required)
Customize dispatch workflow event type.

Which DM version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v3.0 changes)
[x] v2.0 (TiDB DM 2.0 versions)
[x] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

Do your changes match any of the following descriptions?

[ ] Delete files
[ ] Change aliases
[ ] Need modification after applied to another branch
[ ] Might cause conflicts after applied to another branch

/run-cherry-picker

/run-cherry-picker

/run-cherry-picker

/run-cherry-picker


Implement a UI with Automated BDD Testing

As a eCommerce manager
I need to manage the backend service via a web user interface.
So that I can efficiently handle administrative tasks like adding, updating, and monitoring resources without requiring direct access to the backend system.
Details and Assumptions

The UI should support core functionalities: Create, Read, Update, Delete, List, Query, and Action.
BDD tests will be implemented using Selenium to interact with the UI.
The BDD tests will follow the Gherkin syntax to ensure clarity and understanding for non-technical stakeholders.

Acceptance Criteria
Given I am on the Recommendations List page
When I select a specific Recommendation
Then I should see detailed information about the Recommendation

Given I am on the Recommendations List page
When I select a Recommendation and click the Delete button
Then I should see a prompt to confirm the deletion
And when I confirm, the Recommendation should be removed from the list

Should be written into smaller stories


[Concurrency] Split out the default cooperative executor into a separate opt-in library

Currently, the Embedded Swift's libswift_Concurrency.a includes an implementation of a default cooperative executor (via CooperativeGlobalExecutor.cpp) inside, and the mechanism to use a user-provided executor instead relies on the linker preferring code from a .o file and/or order of libraries listed on the linker time. This feels unintuitive and possibly error prone, so this PR changes the setup: Instead, libswift_Concurrency.a stops including any global executor, and the user is expected to either explicitly link a new library, libswift_ConcurrencyDefaultExecutor.a, or link in their own executor. If they don't do either, they'll receive a (pretty self-explanatory) linker error about missing symbols like swift_task_enqueueGlobalImpl, etc.

@swift-ci Please Build Toolchain macOS Platform

@swift-ci please test

@swift-ci Please Build Toolchain macOS Platform

@swift-ci please test