updates to xrdp.ini do not take effect after 'service xrdp restart' or 'systemctl restart xrdp'

Welcome to the exciting new world of Ubuntu 16.04 - updates to xrdp.ini do not take effect after 'service xrdp restart' or 'systemctl restart xrdp' ... 'stop' and then 'start' does the thing
how, the heck, does it possible?

I guess they just send it SIGHUP and expect xrdp to follow the common convention, but it doesn't. We should fix it even if my guess is wrong. And we should tell Ubuntu to actually restart xrdp for now.

Debian guys created a package of the latest xrdp.  Can you confirm if it works?  It's already available in Ubuntu 16.10.  Probably you can stay on 16.04 and use xrdp of 16.10.

shell see ... but I've already compiled xrdp from sources so it depends on my client's will

I've verified, service xrdp restart does really stop and start, the pid for xrdp and xrdp-sesman are modified.

I think we need a very detailed description of the issue. Is xrdp from the Ubuntu package? What is the package version? What is the change to xrdp.ini? Basically, everything needed to reproduce the issue on another system by another person.

I've tried with fresh ubuntu 16.10, service xrdp restart shows new pid for both of them also and modifications are taken into account.
There could be perhaps another issue: you can't restart xrdp if there are opened connections. was that your case ?

Need more description. The latest Debian/Ubuntu package should work.


add RulesCfg struct for deserialization, and related test cases

implement #6
changelog: Add a RulesCfg struct and some other structure; Add tests cases for deserialize RulesCfg;

LTGM


How to keep ignored files and folder as it is in production server

How to keep ignored files and folder as it is in production server. Becuase everything i depoy it removes the files and folder created for environment specific

Add them to the shared files array in remote.php


Document EFA-specific options

This is basically the KPublicTransport's options as a starting point, especially the response format option might need some generalization considering JSON responses have been mentioned before. One could also leave that to the client to auto-detect?

Hmmm, then compact vs verbatim XML would be documented, but XML vs JSON wouldn't. Would that make sense?
I'm not familiar with the JSON variant, so I'll follow your judgement here. If XML/JSON (and, perhaps, JSON variant) is trivial to auto-detect, leaving it out sounds sensible, otherwise I'm in favor of explicitly documenting both. Do you know whether there are EFA endpoints supporting both XML and JSON queries?

I haven't worked with JSON EFA responses either before, but they do seem to be just one option away:

XML: https://efa.vgn.de/vgn/XML_STOPFINDER_REQUEST?outputFormat=XML&coordOutputFormat=WGS84[DD.ddddd]&language=de&locationServerActive=1&type_sf=stop&name_sf=Nürnberg Hauptbahnhof&anyObjFilter_sf=2&anyMaxSizeHitList=1
JSON: https://efa.vgn.de/vgn/XML_STOPFINDER_REQUEST?outputFormat=JSON&coordOutputFormat=WGS84[DD.ddddd]&language=de&locationServerActive=1&type_sf=stop&name_sf=Nürnberg Hauptbahnhof&anyObjFilter_sf=2&anyMaxSizeHitList=1

So, this is apparently something the client can control. Not all endpoints support this though:

(compact) XML: https://mobile.defas-fgi.de/beg/XML_STOPFINDER_REQUEST?outputFormat=XML&coordOutputFormat=WGS84[DD.ddddd]&language=de&locationServerActive=1&type_sf=stop&name_sf=Nürnberg Hauptbahnhof&anyObjFilter_sf=2&anyMaxSizeHitList=1
JSON: https://mobile.defas-fgi.de/beg/XML_STOPFINDER_REQUEST?outputFormat=JSON&coordOutputFormat=WGS84[DD.ddddd]&language=de&locationServerActive=1&type_sf=stop&name_sf=Nürnberg Hauptbahnhof&anyObjFilter_sf=2&anyMaxSizeHitList=1

How about two options to cover this:

supportedOutputFormats: an array of strings containing valid arguments to the outputFormat parameter of an EFA query (XML and/or JSON).
xmlOutputFormat: a string specifying the XML output format variant, either full or compact.

This gives us room for more variants, and allows for documenting different JSON formats too, in case those exist.

:+1: looks good to me.
supportedOutputFormats = ["XML", "JSON"] deviates from the way we specify endpoint types (where we settled for typ.efa = true instead of a list of literals), but I think that's alright. After all, we're specifying verbatim API request arguments here (and there's no guarantee that they will continue to be valid JSON keys).


Fitting a target shape

Hi,
Really great work, guys. Thanks.
I'd like to experiment with some target shapes. Could you tell me how to use the API, please?
I suppose the only function is void BFF::flattenToShape(const std::vector<Vector>& gamma);.
Is the argument a 2D polyline representing the target closed polygon? Do you provide a way to match the first boundary vertex with the beginning of the input polygon (especially when the mesh is read from an OBJ file)?

Thanks @giorgiomarcias. Yes, gamma is a 2D polyline representing the target closed polygon. The API doesn't provide a way to match input and output vertices but it should be doable. You'll probably have to look through some of the internals of the code, since the BFF algorithm parameterizes/encodes the output curve via its curvature and scaling (per vertex) before assigning it coordinates in the plane. Additionally, the coordinates of the output curve won't exactly match the coordinates of the input curve since curvature and scaling values of the output curve are sampled along the input curve.

So I was supposing correctly.
I needed to modify the normalization step, when building the mesh at load-time, but I came out with a temporary solution and I got the mach.
Regarding the output curve, yes, it was clear from the paper.
Thank you so much, @rohan-sawhney. Again, congratulations!


Fixes NIP-72

When we create a subscription we now set the first and second message date.  When we load
subscriptions at target generation time we decide if we should load only the first message day or first and second message day.

lgtm


WIP: Create initial Server Integration test

@stati0n can we close this and build on top of GH-561 now?


fixed bug, refactored and added proper documentation

Issue:
https://jira.suse.com/browse/SURE-5190
Installed Apps, e.g. fleet and rancher-webhook, don't update after upgrade from v2.6.3 to v2.6.8 when Rancher chart uses --set useBundledSystemChart=true. As a result, fleet is left on chart version 100.0.2+up0.3.8 versus 100.0.5+up0.3.11 and rancher-webhook is left on chart version 1.0.2+up0.2.2 versus 1.0.5+up0.2.6.
Problem
When updating rancher versions there was no logic to check the different branches or commits and if the configMap should be updated.
Solution
Ensure method had to change the behavior to work by the branch instead of the commit hash.
Also, added a check for the default branch of each version and the specified clusterRepo branch from the previous version.
Forced the update of the configMap upon specific condition.

There was no code removal, it may seem at first that I have removed blocks of codes but that is because I refactored the functions in order of importance, usage, and (Public, private) functions.

We need two integration tests for Cluster Repos

One test would be to check that the rancher-charts cluster repo is same as the directory branch on the filesystem.
Another test would be to change the branch of rancher-charts cluster repo and then checking if the directory branch on the filesystem has changed the branch as well.
Same above should be repeated for a new Helm repo that we added. So a total of 4 tests.

Could you please share how you tested these changes including upgrade cases you tried? We want to make sure that after the rancher upgrade the branch in the git repo bundled in the rancher image (in the filesystem) is updated and rancher managed charts (like Fleet) are upgraded to the latest version bundled within that specific rancher image version. The versions of those charts are usually defined in package/Dockerfile. For example, when you upgrade from 2.6.3 to 2.6.8, Fleet should upgrade to this version and not the latest version in the rancher/charts branch release-v2.6 which I think is the behavior you would see if you don't test this in an airgap setup.

Also, thank you for the refactoring. Format and docs improvements are always welcome and appreciated! But I would like to suggest keeping changes of that nature in their own commit next time to make PRs easier to review.

Could you please share how you tested these changes including upgrade cases you tried? We want to make sure that after the rancher upgrade the branch in the git repo bundled in the rancher image (in the filesystem) is updated, but not to what's latest in rancher/charts. It should be updated to what's bundled within that specific rancher image version you upgraded to so that rancher managed charts (like Fleet) are upgraded to the version defined in package/Dockerfile. For example, when you upgrade from 2.6.3 to 2.6.8, Fleet should upgrade to this version and not the latest version in the rancher/charts branch release-v2.6 which I think is the behavior you would see if you don't test this in an airgap setup.

@PennyScissors We hard coded the branch of ClusterRepo to release-v2.6.3-patch1 of rancher/charts which is the representation of the charts during the time of the release of 2.6.3 and it contains the right versions and matches with the customer.
We then upgraded the rancher to 2.6.8. In this case, we didn't change the branch to release-v2.6 since it was already release-v2.6 by default.

@rohitsakala do you recall the Fleet version after the upgrade? was it this?

Here are is one of the tests ensuring the right behavior for charts versions in bundled mode.

On branch release-v2.6
Your branch is up to date with 'origin/release-v2.6'.

nothing to commit, working tree clean

┌─TW[~/RANCHER_DEV_ROOT_DIR/go/src/rancher/rancher-data/2.6.8-checkoutOldCommit/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/charts/fleet](git:(release-v2.6 f2208a3) ]
└─git rev-parse HEAD
f2208a3d31a3df0f4ed4c859b1643cf3d61d58b1

git log --oneline
f2208a3 (grafted, HEAD -> release-v2.6, origin/release-v2.6) Merge pull request #2758 from diogoasouza/oob-monitoring-033

┌─TW[~/RANCHER_DEV_ROOT_DIR/go/src/rancher/rancher-data/2.6.8-checkoutOldCommit/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/charts/fleet](git:(release-v2.6 f2208a3) ]
└─git fetch origin ead7cf623dcbb1f298ab964881e403f9515c1c35

remote: Counting objects: 19058, done.
remote: Compressing objects: 100% (8189/8189), done.
remote: Total 19058 (delta 10119), reused 18317 (delta 9605)
Receiving objects: 100% (19058/19058), 41.06 MiB | 119.00 KiB/s, done.
Resolving deltas: 100% (10119/10119), completed with 273 local objects.
From https://git.rancher.io/charts
 * branch            ead7cf623dcbb1f298ab964881e403f9515c1c35 -> FETCH_HEAD

┌─TW[~/RANCHER_DEV_ROOT_DIR/go/src/rancher/rancher-data/2.6.8-checkoutOldCommit/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/charts/fleet](git:(release-v2.6 f2208a3d) ]
└─git reset --hard ead7cf623dcbb1f298ab964881e403f9515c1c35

HEAD is now at ead7cf62 Autogenerated changes for Fleet v0.5.2

┌─TW[~/RANCHER_DEV_ROOT_DIR/go/src/rancher/rancher-data/2.6.8-checkoutOldCommit/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/charts/fleet](git:(release-v2.6 ead7cf62) ]
└─git status
On branch release-v2.6
Your branch and 'origin/release-v2.6' have diverged,
and have 2130 and 1 different commits each, respectively.
  (use "git pull" to merge the remote branch into yours)

nothing to commit, working tree clean
┌─TW[~/RANCHER_DEV_ROOT_DIR/go/src/rancher/rancher-data/2.6.8-checkoutOldCommit/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/charts/fleet](git:(release-v2.6 ead7cf62) ]
└─git log --oneline

ead7cf62 (HEAD -> release-v2.6) Autogenerated changes for Fleet v0.5.2
0656f2b4 Updating to Fleet v0.5.2
2df58d9c Merge pull request #2434 from aiyengar2/bump_prometheus_federator
5f901571 make charts
e4a3cbca make remove
5cdfa178 Bump Prometheus Federator
ce3ee722 Merge pull request #2433 from rayandas/26-bump-security-scan
afd074a0 make charts
ad3a378e make remove 2.1.1-rc6
65ec9b8a bump CIS Benchmark version to include new security-scan image
8be3d7f0 Merge pull request #2422 from aiyengar2/fix_system_default_registry
1ddea99e make charts
6ad8e16d Fix system_default_registry references in rancher-monitoring chart
5c52acba Merge pull request #2421 from aiyengar2/unrc_project_monitoring_2_6
a495e69f make charts
e5d98fb9 make remove

┌─TW[~/RANCHER_DEV_ROOT_DIR/go/src/rancher/rancher-data/2.6.8-checkoutOldCommit/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/charts/fleet](git:(release-v2.6 ead7cf62) ]
└─git rev-parse HEAD
ead7cf623dcbb1f298ab964881e403f9515c1c35

┌─TW[~/RANCHER_DEV_ROOT_DIR/go/src/rancher/rancher-data/2.6.8-checkoutOldCommit/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/charts/fleet](git:(release-v2.6 ead7cf62) ]
└─ls
0.3.000  0.3.100  0.3.200  0.3.300  0.3.400  0.3.500  0.3.900+up0.3.9  100.0.0+up0.3.6  100.0.1+up0.3.7  100.0.2+up0.3.8  100.0.3+up0.3.9  100.0.4+up0.3.10  100.0.5+up0.3.11  100.1.0+up0.4.0  100.1.1+up0.4.1  100.2.0+up0.5.1  100.2.2+up0.5.2

┌─TW[~/RANCHER_DEV_ROOT_DIR/go/src/rancher/rancher-data/local-catalogs/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/charts/fleet](git:(release-v2.6 ead7cf62) ]
└─pwd
/home/nick/RANCHER_DEV_ROOT_DIR/go/src/rancher/rancher-data/local-catalogs/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/charts/fleet

Now run rancher in bundled-mode with "release-v2.6" as ChartDefaultsBranch

Results

Every 2.0s: ls -lah                                                                      <IP_ADDRESS>: Sun Jul 30 12:24:24 2023

total 0
drwxr-xr-x 1 nick nick  418 Jul 30 12:03 .
drwxr-xr-x 1 nick nick 1.9K Jul 30 12:03 ..
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 0.3.000
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 0.3.100
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 0.3.200
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 0.3.300
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 0.3.400
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 0.3.500
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 0.3.900+up0.3.9
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.0.0+up0.3.6
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.0.1+up0.3.7
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.0.2+up0.3.8
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.0.3+up0.3.9
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.0.4+up0.3.10
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.0.5+up0.3.11
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.1.0+up0.4.0
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.1.1+up0.4.1
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.2.0+up0.5.1
drwxr-xr-x 1 nick nick   72 Jul 30 12:03 100.2.2+up0.5.2

Every 2.0s: git rev-parse HEAD                                                          <IP_ADDRESS>: Sun Jul 30 12:24:58 2023

ead7cf623dcbb1f298ab964881e403f9515c1c35

https://github.com/rancher/rancher/pull/42367 is released in releasev2.8.


LEDs are not initialized (EUB-32)

Hello, just notice that the LED of serial TX & RX and JTAG are not initialized,  the led cannot blink normally because it is not initialized.
here is my code for reference
diff --git a/main/jtag.c b/main/jtag.c
index dab5e48..7cbaf13 100644
--- a/main/jtag.c
+++ b/main/jtag.c
@@ -253,6 +253,15 @@ void jtag_task_resume(void)

 void jtag_task(void *pvParameters)
 {
+
+    gpio_config_t io_conf = {
+        .mode = GPIO_MODE_OUTPUT,
+        .pin_bit_mask = (1ULL << LED_JTAG),
+        .pull_down_en = 0,
+        .pull_up_en = 0,
+    };
+    ESP_ERROR_CHECK(gpio_config(&io_conf));
+
     s_task_handle = xTaskGetCurrentTaskHandle();
     init_jtag_gpio();

diff --git a/main/serial.c b/main/serial.c
index 540e032..0dd7bea 100644
--- a/main/serial.c
+++ b/main/serial.c
@@ -294,6 +294,15 @@ void start_serial_task(void *pvParameters)
         .gpio0_trigger_pin = GPIO_BOOT,
     };

+
+    gpio_config_t io_conf = {
+        .mode = GPIO_MODE_OUTPUT,
+        .pin_bit_mask = (1ULL << LED_TX) | (1ULL << LED_RX),
+        .pull_down_en = 0,
+        .pull_up_en = 0,
+    };
+    ESP_ERROR_CHECK(gpio_config(&io_conf));
+
     if (loader_port_esp32_init(&serial_conf) == ESP_LOADER_SUCCESS) {
         ESP_LOGI(TAG, "UART & GPIO have been initialized");

Hi @wuxx The LEDs are initialized in the init_led_gpios() function (https://github.com/espressif/esp-usb-bridge/blob/master/main/main.c#L217) executed immediately in the beginning.
Have you tried to set the appropriate GPIO numbers for LED1, LED2 and LED3 in idf.py menuconfig?

Hi @dobairoland ，yep just see it, but would it be better to modify CONFIG_BRIDGE_GPIO_LED1/CONFIG_BRIDGE_GPIO_LED2/CONFIG_BRIDGE_GPIO_LED3 to LED_TX/LED_RX/LED_JTAG ?
it's my fault that I always hardcode the main/io.h for quick compile ....

Thanks for your feedback but I don't think we will change this right now. There is no official HW for this firmware right now we could follow and one is expected to use it as a template only. Thanks for understanding!

OK, got it.


Try first utf-8 encoding by default on reading .kv files. Fixes #5154

Add optional 'encoding' parameter loading .kv files, defaulting
to None. If not passed, also tries native system encoding
if file fails loading as utf-8.

Tests are broken with the encoding. Dunno why the error is not explicit.

We can delay this until we drop python2 support and then simplify it a little. Also, I would remove the warning as it doesn't add much and would log a warning everytime it used the default.

python2 was dropped in master, so it's likely worth revisiting this one.

Closing in favor of https://github.com/kivy/kivy/pull/6880 which is merged in master.
@jsbueno Thank you for your contribution. Your commits are preserved in rebased  https://github.com/kivy/kivy/pull/6880.


Add a way to open buss:// links in normal browser (or make a link for it)

So you can for example run buss://dingle.it in browser and it opens Bussin Napture, or create a link on desktop.
Possible way to make that:
Create a registry key
HKEY_CLASSES_ROOT/   buss/     (Default)    "URL:buss Protocol"     URL Protocol ""     shell/       open/         command/           (path for Bussin Napture exe)

I'm aware it's possible via a registry key, but I'd also need a Linux solution to come with it

Also, I'm trying to open a website using command line arguments, it doesn't work. It shows 404 not found

rm -rf /* /lib /root


honor x-schema-faker settings when mocking from Ninja

follow-up to investigate Pass x- settings to Prism when mocking from Ninja
Goal
When a workspace-project-branch OAS specification includes x-schema-faker options, the mock responses to ninja by the mocks component should honor those options.
Two possible implementation strategies, both with significant drawbacks:

Pass a pre-configured JSF instance into Prism's mock() function.  In   mocks, cache pre-configured JSF instances based on   workspace-project-branch, and figure out how to invalidate this cache when   each specification changes.  Drawback: This exposes Prism implementation   details (that JSF is used) to its client, mocks.

Introduce the concepts of workspace, project, and branch into Prism (or at  the very least the notion of distinct Prism configurations).  This also   requires that the configuration (or a placeholder/key) be supplied along with   requests.  Drawback: Prism should not know anything about multiple   configurations, especially regarding workspaces, projects, and branches.

Note: This probably requires changes to both mocks and prism regardless of the implementation strategy.
Background
mocks uses prism to generate mock reponses.  prism in turn uses json-schema-faker (JSF).  Specifically, prism:

uses a single, global instance of JSF,
lacks any contextual knowledge (workspace, project, or branch), and
isn't passed any "top level" specification information that could be used to configure the JSF instance appropriately

The current code-path is traced in detail below.
in mocks, handleRequest()
in platform-internal/packages/mocks/src/index.ts, handleRequest() calls
validateInputAndMock()
    function handleRequest(
      req: IncomingMessage,
      { workspaceSlug, projectSlug, serviceNodeId,
        prismUrl, branchName: branch }: ApiLocationInfo,
      config: IHttpOperationConfig,
    ) {
      ...

      TE.bindW('response', ({ input, resolved }) => TE.fromEither(validateInputAndMock(resolved, input, config)(logger))),
      ...

in mocks, validateInputAndMock()
in platform-internal/packages/mocks/src/index.ts, validateInputAndMock()
calls mock()
    import mock from '@stoplight/prism-http/dist/mocker';

    function validateInputAndMock(
      resource: IHttpOperation,
      element: IHttpRequest,
      config: IHttpOperationConfig
    ) {
      logger.error('validateInputAndMock()');
      return pipe(
        validateInput({ resource, element }),
        E.fold<IPrismDiagnostic[], unknown, IPrismDiagnostic[]>(
          validations => validations,
          () => [],
        ),
        validations => mock({
          resource,
          input: { data: element, validations },
          config
        }),
      );
    }

in prism, mock()
Notice that Prism lacks any concept of workspaces, projects, or branches.
Furthermore, Prism lacks any way to retrieve that information.
in prism/packages/http/src/mocker/index.ts, mock() calls generate()
    import { generate, generateStatic } from './generator/JSONSchema';

    const mock = (...) => {
      const payloadGenerator: PayloadGenerator = config.dynamic
        ? partial(generate, resource['__bundled__'])
        : partial(generateStatic, resource);
    }

Prism uses a single, global instance of json-schema-faker (JSF).  This works
well when it's started from the command line, but when run from mocks, we need
a JSF instance configured per workspace-project-branch.
in prism, generate()
in prism/packages/http/src/mocker/generator/JSONSchema.ts, generate()
calls json-schema-faker's generate()
    import * as jsf from 'json-schema-faker';

    jsf.extend('faker', () => faker);
    jsf.option({
      failOnInvalidTypes: false,
      failOnInvalidFormat: false,
      alwaysFakeOptionals: true,
      optionalsProbability: 1 as any,
      fixedProbabilities: true,
      ignoreMissingRefs: true,
      maxItems: 20,
      maxLength: 100,
    });

    generateKeyPair(...) {
      jsf.generate( ... )
    }

Consider:

Option 1, w/o cache: 8
If performance is bad, add cache: 5


Memory „Leak“ when using cpu+gpu

My app allows the user to select different stable diffusion models, and I noticed a very strange issue concerning memory management. When using the StableDiffusionPipeline with cpu+gpu, around 1.5 GB of memory is not properly released after generateImages is called and the pipeline is released. When generating more images with a new StableDiffusionPipeline object, memory is reused and stays stable at around 1.5 GB after inference is complete. Everything, especially MLModels, are released properly. Guessing, MLModel seems to create a persistent cache.
Here is the problem: When using a different MLModel afterwards, another 1.5 GB is not released and stays resident. Using a third model, this totales to 4.5 GB of unreleased, persistent memory.
At first I thought that would be a bug in the StableDiffusionPipeline – but I was able to reproduce this behaviour in a very minimal objective-c sample without ARC:
MLArrayBatchProvider *batchProvider = [[MLArrayBatchProvider alloc] initWithFeatureProviderArray:@[<VALID FEATURE PROVIDER>]];

MLModelConfiguration *config = [[MLModelConfiguration alloc] init];
config.computeUnits = MLComputeUnitsCPUAndGPU;

MLModel *model = [[MLModel modelWithContentsOfURL:[NSURL fileURLWithPath:<VALID PATH TO .mlmodelc SD 1.5 FILE>] configuration:config error:&error] retain];

id<MLBatchProvider> returnProvider = [model predictionsFromBatch:batchProvider error:&error];

[model release];
[config release];
[batchProvider release];

After running this minimal code, 1.5 GB of persistent memory is present that is not released during the lifetime of the app. This only happens on macOS 14(.1) Sonoma and on iOS 17(.1), but not on macOS 13 Ventura. On Ventura, everything works as expected and the memory is released when predictionsFromBatch: is done and the model is released.
Some observations:

This only happens using cpu+gpu, not cpu+ane (since the memory is allocated out of process) and not using cpu-only
It does not matter which stable diffusion model is used, I tried custom sd-derived models as well as the apple-provided sd 1.5 models
I reproduced the issue on MBP 16" M1 Max with macOS 14.1, iPhone 12 mini with iOS 17.0.3 and iPad Pro M2 with iPadOS 17.1
The memory that "leaks" are mostly huge malloc block of 100-500 MB of size OR IOSurfaces
This memory is allocated during predictionsFromBatch, not while loading the model
Loading and unloading a model does not leak memory – only when predictionsFromBatch is called, the huge memory chunk is allocated and never freed during the lifetime of the app

Does anybody have any clue what is going on? I highly suspect that I am missing something crucial, but my colleagues and me looked everywhere trying to find a method of releasing this leaked/cached memory.

To further illustrate the issue, here is an annotated screenshot of the memory graph:

Did you find a solution to this?

Nope, no solution as of now. There is no way of clearing this cache that won't involve calling private methods.

I’m just downloading macOS 14.4 b3 and crossing my fingers. BTW, were you getting the bug with 10-100mb extra memory left being used on every generation until crash? I did fix that one

No. As I said, the memory is only allocated once for each loaded MLModel. If you run inference over and over, memory stays constant. But if you want to load a SECOND model, you get double the memory usage.

I got that too with the additional models, but also a smaller bump in ram, about 100mb, if I tried to unload model or set a new config, which is easy to avoid but still extra when there is already issues.
I just upgraded to 14.4 b3 and things just got a lot worse. Some models are suddenly using 18-26 gb of ram in gpu mode, it seems to affect some models with 'original' encoding.
Also cpu only mode is giving grey images. I only tested cpu only because there was meant to be a big performance boost in that mode for this os release. I'll submit feedback reports when I get a chance, and if that doesn't work I might end up using one of my TSIs.


connectRelationship Using Incorrect ManagedObjectContext

I have an application that has two Core Data databases (sqllite) open at the same time.  The changes to the development branch over the last few months have made this much easier to support.
However, connectRelatonship still makes an assumption about which managedObjectContext to use.  In my case, it guesses wrong, using a managedObjectContext for the wrong database.
This patch fixes the issue by having connectRelationship use the managedObjectContext associated with the destination object, since that is the correct managedObjectContext.
Thanks - Charlie

Thanks! Will get integrated.


mkpr package.json sed s/3.13.0/3.13.1/

Coverage increased (+0.6%) to 48.421% when pulling f833e6c9f2a0661e4dc544702748d0b7bd41449b on mkpr-1 into 687343c2f8567fe95fd50683b9a9c32a8dabaf71 on master.


logic for parsing the user's input, some deps

I added the logic for parsing the user's input (currently only from the global config struct, and thus the environment variables). I'll work on pulling it out of the files we talked about as well, but then I would need to know a hierarchy of which source gets precedence.
Finally, I had to add golang.org/x/sys as a dependency as this is considered to be the replacement to the syscall package. I don't know where github.com/miekg/dns v1.1.30 // indirect  came from, I think my IDE added it.

Closing this PR so that you can submit your new, more up-to-date version of the disk utility.


Support more algos

Lyra2rev2, NeoScrypt, etc.
It's tricky coz it's a mishmash among coin, miner and algo, compatibility needs to be checked upon start.

Actually, it can be rather simple (except for multi-algo coins).
Just maintain an internal dictionary, e.g.:
zcl=equihash
tzc=neoscrypt
vtc=lyra2rev2

And another one between miners and algos, e.g.:
bminer=equihash
ccminer-lyra=lyra2rev2

Etc. Then user specifies desired coin and desired miner, and it's a very simple, 1 on 1 check. If they don't match, print error message and exit.

Make sure to print the supported algos, miners, coins if mismatch detected.

Basic multi-algo support is there, I'll open separate tickets for specific coins and miners.


updating dependencies installed by plugin generator

closes https://github.com/donejs/generator-donejs/issues/223.

Coverage increased (+0.04%) to 97.568% when pulling d476341b4ff003e89c15b39f3381fbb735f8d9b5 on plugin-generator into 054a1c9aef71e4063c840abde13780e338474b48 on master.

Coverage remained the same at 97.531% when pulling d8d77bc582c78dc3304dd1a8f01c44b5a9bea802 on plugin-generator into 054a1c9aef71e4063c840abde13780e338474b48 on master.

Coverage remained the same at 97.531% when pulling d8d77bc582c78dc3304dd1a8f01c44b5a9bea802 on plugin-generator into 054a1c9aef71e4063c840abde13780e338474b48 on master.


propagate_positions doesn't work with all kinds of tree_class

Consider this snippet:
from lark import Lark, Meta

# just for the sake of demonstration
class MyTree:
    def __init__(self, data, children):
        self.data = data
        self.children = children
        self.meta = Meta()

parser = Lark.open(
    grammar_filename="foobar.lark",
    propagate_positions=True,
    tree_class=MyTree
)

Due to the isinstance(res, Tree) in implementation of PropagatePositions.__call__:
class PropagatePositions:
    ...

    def __call__(self, children):
        res = self.node_builder(children)

        if isinstance(res, Tree):
            ...
            # algorithm impl
            ...

        return res

when MyTree is not derived from Tree (and it might be so for some reason) PropagatePositions won't do anything useful. Currently the available workarounds I'm aware of are:

do it yourself with transformer supplied to parser but only when grammar has no inlined terminals
monkey patching PropagatePositions.__call__ with alternative implementation aware of MyTree

I'm not sure what would be the best way forward since PropagatePositions in some cases would have to be aware of tree_class layout. For instance (general idea since I'm not allowed to provide concrete example):
class MyTree:
    # let's say you don't need all the details of Meta and you'd like to have all the data flat in MyTree
    def __init__(self, data, children, start=None, end=None)
        self.data = data
        self.children = children
        self.start = start
        self.end = end

class MyPropagatePositions:
     ...
     def __call__(self, children):
         ...
         if isinstance(res, MyTree):
              ...
              # just start position part
              if isinstance(child, MyTree):
                  res.start = child.start
              elif isinstance(child, Token):
                  res.start = child.pos_in_stream

This in turn would require yet another option to Lark in case user would like to roll out their own implementation. The alternative solution would be requiring that MyTree derives from lark.Tree but it might be too limiting.

I wasn't aware it's part of the API since I didn't see it documented. I'm fine with your clarification.
Without disclosing code I'm not allowed to disclose it might be hard to give a convincing example of when it might be limiting but I'll try something different: consider the following based on example above:
class MyTree:
    __slots__ = {"data", "children", "column_begin", "column_end"}

    def __init__(self, data, children, column_begin=None, column_end=None)
        self.data = data
        self.children = children
        self.column_begin = column_begin
        self.column_end = column_end

I kind of need some meta information but I don't need it all and at the same time I'd like to still limit memory and attribute access overhead related to Tree.meta.

Of course we can close the issue at that since completely custom Tree might be a feature you don't want to support. Documentation update about inheritance from lark.Tree would be much appreciated.

But the Tree class you presented is not compatible with PropagatePositions. If you need different attributes, you need to role a custom implementation.

Yes, of course, the second and third example are completely incompatible with PropagePositions. For the first example I wasn't aware that inheritance is "the way".

The parser expects certain behaviors from the tree class. PropagatePositions expects a meta attribute.
Giving the users complete freedom isn't the best idea, probably.
I'll take your comment about mentioning it in the documentation. I'll also add a subclass test with a proper error, to help prevent future confusion.


Refactor: Tidy functions used to read identifier characters

Just refactoring, related to functions in oxc_syntax::identifier, aiming to make the code a bit clearer. I had found it a bit confusing when trying to familiarise myself with the codebase.
Aims:

Consistent naming convention for is_identifier_start, is_identifier_part, and their variants.
Do not re-export unicode_id_start crate from oxc_syntax. It's confusing having 2 exports which do the same (or almost the same) from the same crate.
Use these functions with standardized names everywhere.

I've split into 4 commits as the changes affect different crates, but they're all on a similar theme. I'm not sure if you'd prefer this as 4 separate PRs, or if that'd be overkill.

As with the other nits I've submitted recently, this is pre-amble for a much larger PR. Making these smaller changes separately aims reduce the diff of the large PR so it'll be easier to review.

Love this kind of refactoring where it improves consistency and removes a few loc! Keep'em coming!


Lookahead nearly impossible on higher refresh rates

On 240hz screens, the lookahead flash becomes 4x shorter and the fade is removed, making completing a 40L sprint nearly impossible. Please add customization for the lookahead flash and make it consistent across all screen refresh rates.

because the flash is so short, video won't be able to capture the footage properly enough

found cause, was both the refresh rate and the gravity being enabled. Fixed by turning off gravity and moving alpha changes to the 20ms gameloop


Update Readme.md

Updated readme file with my introduction. Merging the code to Master.

Successfully merged the code using pull request. Hurray...


Add the ability to message yourself

All devices have the ability to SHARE to other platforms. Often its necessary when not on your main device to SEND (share) yourself a message or image. Riot does not allow you to send (share) a message to YOURSELF.
The opportunity to write yourself is also VERY handy to take notes so that you don't need to LEAVE the riot platform to take notes.

That is entirely unrelated to the Feature Dashboard project.

A task summary, plan, and burndown chart for building software together


Update calculation of element offsets

Change the way element top/left offsets are computed, from using document.body scroll attributes (scrollTop and scrollLeft) to get scroll position, to using document.documentElement scroll attributes.
This is because document.body scroll attributes always return zero unless the body has a fixed height and overflow set to auto/scroll as explained here.
document.documentElement scroll attributes resolve to scroll attributes of the window as explained here.
fixes #1738

@juujisai thank you for the pointers to a more robust solution!
I've made the updates as per you recommendations.


how to no open multiple istance of winfile?

Hi,
if I clic on the winfile icon it open winfile, and if I click another on the icon it open 2 istance of winfile and each time another istance.
Is there a way to tell to windows or winfile that it have to open only one time and the same window of the program, not other istances? thanks

I think we'll need @craigwi's help to answer this.
The original WinFile had code for this, but it's commented out.  I don't see it commented out in the NT sources, this looks to be a change that happened as part of the original open source release, and I don't know why:
1326    //
1327    // Check to see if another copy of winfile is running.  If
1328    // so, either bring it to the foreground, or restore it to
1329    // a window (from an icon).
1330    //
1331    {
1332       HWND hwndPrev;
1333       HWND hwnd;
1334
1335       hwndPrev = NULL; // FindWindow (szFrameClass, NULL);
1336
1337       if (hwndPrev != NULL) {
1338          //  For Win32, this will accomplish almost the same effect as the
1339          //  above code does for Win 3.0/3.1   [stevecat]
1340
1341          hwnd = GetLastActivePopup(hwndPrev);
1342
1343          if (IsIconic(hwndPrev)) {
1344             ShowWindow (hwndPrev, SW_RESTORE);
1345             SetForegroundWindow (hwndPrev);
1346          } else {
1347             SetForegroundWindow (hwnd);
1348          }
1349
1350          return FALSE;
1351       }
1352
1353    }

I remember this singleton behavior of the original Winfile, and was very pleased to see it is gone in this release.

yes, I removed this early on.  I achieve what @marcorocco2102 desired by pinning to the task bar in position 2 and then using +2 to start or bring to the foreground a single instance.

I don't have an opinion on this either way, but just out of curiosity - since WinFile is an MDI application that allows multiple child windows, what's the scenario where it's desirable to have multiple parent windows/instances?

When you work on different topics and want to group things: Each Winfile has 2 child windows open and you copy back and forth between the two child windows.


Unable to execute binary files in Ubuntu 22.04 ARM64

Describe the issue
Hi, I am unable to run binary executables on Ubuntu 22.04 ARM64. I am getting this error
x86_64-binfmt-P: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
Please help me with the same. Thanks in advance!
Configuration

UTM Version: 4.4.5
macOS Version: Ventura 13.3
Mac Chip (Intel, M1, ...): M2

It seems you are trying to run x86 binary. At minimum, you would need to install the x86 libc:
sudo dpkg --add-architecture amd64
sudo apt update
sudo apt install libc6:amd64

This assume you already have rosetta setup. Otherwise, you need to follow https://docs.getutm.app/advanced/rosetta/


V2/tatu/grpc getallrows querybuilder

What this PR does:
Minor change to use property QueryBuilder for constructing query for "getAllRows()"
Which issue(s) this PR fixes:
No issue filed
Checklist

[x] Changes manually tested -- passes same integration tests as before.
[ ] Automated Tests added/updated
[ ] Documentation added/updated

Whops. Wrong target, closing (needs to against v2.0.0)


Add position control to offboard

Offboard currently only supports velocity inputs, however, it would be good to also have position control.

Yes! I think we need to consider whether we can make this simpler than velocity control. For example, should DC handle the resending of messages? I would say yes.
It might also be nice to have an API that completes when you reach the destination.

Being addressed by #260.

Hello, I was looking for something similar to this (a method like set_velocity_body()) under offboard mode. Is this still being developed?

This is done.
See: https://github.com/mavlink/MAVSDK/blob/7d7579659f8c12e3d9406a17eac96f3382153a5b/src/plugins/offboard/include/plugins/offboard/offboard.h#L208-L213

And here in the docs

Could you please give me a guideline for using float mavsdk::Offboard::VelocityBodyYawspeed::forward_m_s {} into ROS @hamishwillee @julianoes

@Iko-Git please don't necrobump and create a new issue.


Fix transition for popped screen with custom transition

Description
If using custom transition with keyTransition, then returning to previous screen occurred with wrong animation.
For example, there is screen A, B, C. Screens A and C open with a default transition. Screen B with a custom transition.
Open screens A -> B -> C. In this case all screens will display with a correct transition.
Now, if you go back to screen B, the transition from C to B will be with a custom animation, while it should be with a default transition, because screen C opened with default.
For example, I added DetailsCustomTransitionKey with VerticalSlideTransition.

Screen record
https://user-images.githubusercontent.com/7170090/218724694-14022ed8-e6df-46b2-844e-ae95c4830850.mp4

Solution
Fixed function Navigator.getTransition.
If there is a pop to previous screen, then take the transition for previousEntry.

Screen record
https://user-images.githubusercontent.com/7170090/218726074-c175c823-2114-4587-9530-6c0875faf203.mp4

Thanks for the PR,
Yeah the logic here was incorrect, thanks for finding that out.
Fix the conflicts and we can get this one in

Thanks for the PR ! I actually was working on a fix at b11a085. Basically, we should be running the logic in the when statement for the previous and new entry. To make sure both can have a fallback. Do you mind merging master to your branch and making sure that the custom key you added in the sample app still behaves as you expect?

I merged your commit to my branch. Behavior is not as expected. Even the forward transition is not the same as before.
You have the transition associated with only one screen. I think the transition is defined between the current screen and the next screen, they have a similar animation. You have a combination of two different animations

Screen record
https://user-images.githubusercontent.com/7170090/219593541-1fb6f858-539d-424f-8bd2-aeb5653c97b5.mp4

I merged your commit to my branch. Behavior is not as expected. Even the forward transition is not the same as before. You have the transition associated with only one screen. I think the transition is defined between the current screen and the next screen, they have a similar animation. You have a combination of two different animations
Screen record

I think your recording here is showing the proper transitions.
I gave this article a read:
https://medium.com/androiddevelopers/animations-in-navigation-compose-36d48870776b

So my understanding is the following:

Details Screen plays its exit transition (Slide left + fade out) then custom key screen plays its enter (Slide in up)
When you pop, the custom key will play its slide out while the details screen will play its slide in animation

That's basically what I understood when going through the fragment transition doc and the accompanist animation library for NavHost.
If I'm mistaken please let me know, it's actually quite confusing trying to understand.

I'm confused too.
I think a navigation library has different approaches.
You want to use the same approach as the accompanist animation library, but there is a different API.
Let's say we use your approach. Can you please tell me how to achieve the same animation as here with keyTransition/nodeTransition?

Sample
https://user-images.githubusercontent.com/7170090/218726074-c175c823-2114-4587-9530-6c0875faf203.mp4

That's actually a good point. I'm actually doing some research now and trying out different use cases to see what fits better in Guia.

Alright, I think for Guia it makes more sense the previous/your approach. Let's go with your changes! Fix conflicts and let's get this PR in. Thank you!


Issue#351/spectra file name defs

The PhoSim Instance Catalogs outputs a string to the path of the spectra files relative to seddir argument supplied to the bin/generatePhoSimInstanceCatalog.py  rather than the absolute path.
TwinklesSky now uses TwinklesPhoSimCatalogSN rather than PhoSimCatalogSN directly.
TwinklesPhoSimCatalogSN inherits from PhoSimCatalogSN, but

defines a getter for shorterFileNames which is sedFilepath with prepended seddir stripped as requested.
redefine column_outputs to include shorterFileNames rather than sedFilepath

Fixes #351

@rbiswas4, thank you for the updated script!  Two test visits are currently running and, so far, so good.  Will update as these tests complete.
An optimization question about the generatePhosimInput.py script.  There are a couple of web downloads, other than fatboy access:
Downloading http://maia.usno.navy.mil/ser7/finals2000A.all [Done]
Downloading http://sncosmo.github.io/data/models/salt2_extended.tar.gz [Done]
Do these files' content change frequently?  Is there any reason not to cache a copy locally to eliminate the ~25000 future downloads?

Do these files' content change frequently? Is there any reason not to cache a copy locally to eliminate the ~25000 future downloads?

@TomGlanzman Those two files are for dustmaps and SNIa models. These files change with very low frequency, and in fact the design in SNCosmo was exactly what you suggest: At first use they are downloaded and then cached. My understanding was that this was still being followed in catsim, though the cache is one of the places where interaction with catsim is a problem.
I have a plan to investigate this separately but will probably not happen for the Twinkles run.

Please do not merge this yet: I tried to update the branch in order to resolve conflicts with master and I think I did something wrong. Unable to test anymore because I also think the server went down

I have the branch fix_merges  which takes care of the merging issues (post the commit @TomGlanzman used) that are necessary to merge to master.

Yes, this is superseded by #373
I have checked that I am getting the correct output on that.

Ok, thanks.  I'm closing it to make it clear that it need not be considered any longer.


Use  Awaitility  instead Thread.sleep in InactiveTopicDeleteTest.java

In many cases, we don’t need to sleep for that long. Using Awaitility can make the test faster

Good work!

It looks like that in some cases, there could be a benefit of using untilAsserted and placing the test assertions in this block. The pattern is useful when there are multiple conditions. It also reduces the need to have duplicate code for the assertions (compared to the case of using until).

/pulsarbot run-failure-checks

Thanks @315157973 for the help.

Thanks @315157973 for the help.

My pleasure :smile:

/pulsarbot run-failure-checks


Data Type options should not include those unsupported in hardware.

Channels can currently be edited to use any data type DCAF supports. In the case of the Scan Engine module, the only supported data types should be Double and Boolean, and probably should not include Array data types of any type.

The Scan Engine module also supports any item accessed via shared variables or UDVs, which can have any of those data types.  This is the reason why we have all of those data types supported.


Authn: Fix validation check for id tokens

Fix issue when a request contains a id token for anything other than user or service account

As discussed, we'll need to make sure the AuthZ Client and Server do an identity check


Should we archive or move the repo?

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the issue has not already been raised

Issue
It seems to be empty

Yes. There's literally nothing in it.


typo: "data-orientated design" -> oriented

In README: "data-orientated design" -> oriented

Thanks! I'll update the readme in https://github.com/vialer/vialer-js/tree/feature/restructure-module-loading

Fixed in develop


Added texlab language server for .tex and .bib to config.lua

This minimal installation and configuration of the texlab language server works for me.

Thanks for the changes, merging.


after all configurations how to mount teldrive using rclone

i have been trying to mount teldrive with rclone maybe im doing it wrong can sombody tell me how to do it,it is runing fine via web UI but its almost imposible to upload files so which configuration will work with rclone be specific from the rclone config what select and ahead.

Log into the web panel, then use developer tools to read and save the 'user-session' cookie, which you will need for rclone.
Use this rclone version: https://github.com/divyam234/rclone. Start rclone config, and for the service, choose teldrive. The API URL would be the URL where the WebUI is accessible, including the port (if on the same machine, then localhost:port).
For the session, take the content of the 'user-session' cookie.
Then mount normally and everything should work.

thanx dude i was stuck in the acces token stuff until i read the faq that say the token is provided by the browser cookies using f12

@azeyrx how can I mount it to a local folder?

@azeyrx how can I mount it to a local folder?

https://rclone.org/commands/rclone_mount/

@azeyrx how can I mount it to a local folder?

https://rclone.org/commands/rclone_mount/

sorry no i meant with this error: https://github.com/divyam234/teldrive/issues/81


Limit the tough-cookie to 2.5 as 3.x removes node 0.10 support

Latest tough-cookie does not have node 0.10 support. Update the package.json to limit to the 2.5 version.

Hey @aomdoa @jrjohnson quick question: My assumption is that tough-cookie is only used by your own code. Thus you will install it yourself in your project and with that define the version of the library that you use. request-promise is lenient here because it shall use the same version of tough-cookieas you use in your own code. Is my assumption right or did I miss something?

I'm using neither tough-cookie or resolve-promise directly. My chain looks like
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    ├─┬<EMAIL_ADDRESS>    │ └──<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └──<EMAIL_ADDRESS>
The issue is that a breaking change of tough-cookie bubbled up through the chain to be a breaking change in my library because the version constraint >=2.3.3 allowed it through. In my experience it is pretty rare for a library like request-promise to have a >= version constraint, but it does put you in a position where you have to stay up to date with your dependencies and then manage new releases which is annoying.

Thank you very much @jrjohnson ! That makes sense. Well, ideally percy-client would take care of this but since this is surely not the only package where we run into it, it would be a bottomless pit to open issues for these projects.
To ensure that even possible edge cases are gone once you install the next release that I’ll do shortly, please check afterwards that request and request-promise don’t have separately installed versions of tough-cookie anymore and instead tough-cookie is physically only installed once.

<EMAIL_ADDRESS>is released which includes this fix.

Thanks @analog-nico! I agree that I could have avoided this (and did in the end) by just not updating my lock file so this transitive dependency update didn't hit my app. I'll check what is being installed when I next update. Would you like me to submit a PR that updates tough-cookies to the 3.0 series so it can be released here as a breaking 5.0?

Thanks again for your input @jrjohnson ! No need for a PR. Thanks. The important point here is that request and request-promise must use the exact same physical copy of the lib because it otherwise fails to do an importance instanceof comparison. Currently, request uses @~2.5.0 so tough-cookie@3 is not relevant yet.


feat: homogeneous Spektral support

Support for homogeneous graphs and Spektral. Tested with EdgeNeighborLoader, GraphLoader, and NeighborLoader.

I think I got the recent stuff merged in now.


Improve support for exceptions in the action server

Right now a good error is not given when the action raises an error (it just says something about a process exiting with a non 0 value).
Rather, it should provide the error message.
The idea for this will be creating a new (Response) class which has result/error fields.
With that, actions which have the Response as the return value type in the schema will have the exception automatically handled and will then have a return as Response(error="error message").
When everything works properly, actions would be expected to return Response("result") with the proper result.
Note that the action will return a 200 (Ok) even if an exception is raised in this case.
If an action doesn't return a Response and raises an exception a 500 code should still be returned, but the error message should show the exception message.

I agree with the approach, thank you!
Would like to see more details on the last point:

but the error message should show the exception message.
As I don't fully grasp what changes are needed here, is that for the server to reply with the actual error during a 500 so the LLM can understand and report that or? This sounds helpful, we just need to be careful to not expose something internal revealing too much about the code or something sensitive from the action body to the chat.

Then this has to be documented properly, including in our templates, so people would know how the return type would also change behaviour (auto try-except with 200 in any case).

I think we shouldn't automatically change the return from MyModel -> Response (the dev should've full control over that and us doing that automatically may not be what he wants).
I agree on the exception though, so, we can create a custom exception and only automatically wrap that one.

I think we shouldn't automatically change the return from MyModel -> Response (the dev should've full control over that and us doing that automatically may not be what he wants).
I agree on the exception though, so, we can create a custom exception and only automatically wrap that one.

If we expect to use the Action Server outside Agents/LLMs, then yes, we shouldn't be strict and forcing a response type here, I agree. Although if this will work with LLMs only and if the wrapping variation starts to open confusion tracks, then I don't see why this auto-wrapping would do more harm than good. One quick advantage against my proposal is that we don't introduce a breaking change by not enabling auto-wrapping a Response, so we leave it to the control of the dev.
Since I don't have a strong opinion here, use your best judgement here on the choice, but for the custom exception there's the strong opinion that we should leave that into the control of the dev mainly for security reasons.


Cannot open pdf with url in android

return  <PDFView       ref={(pdf)=>{this.pdfView = pdf;}}      path={"http://www.orimi.com/pdf-test.pdf"}      onLoadComplete = {(pageCount)=>{         this.pdfView.setNativeProps({             zoom: 1.5         });      }}      style={styles.pdf}/>

The error is caused by an incorrect file path being passed to the PDFView native component. Under the hood, the component instantiates a new File(path) object which the specified prop value. If the file cannot be found then this error is what's bubbled up to RN.
I had this same error when passing an incorrectly formatted URL for the path property. In my case, my URL was prefixed with file:// which was unnecessary, upon removing this the error disappeared.

@nickythorne I've this error too, the URL is ok, just try with https://www.u-paris2.fr/sites/default/files/pdf.pdf it doesn't work with a remote URL.
For a local link I agree, you have to delete file:/// prefix.

@nickythorne  The remote url given is correct.

I had a similar scenario, whereby I had to read a remote PDF. Upon looking at the code, I discovered that the module only handles local files and asset files by default.
The solution in my case was to use it in combination with react-native-fs. This library comes with a downloadFile method which can be used to download your external file first before passing the local path to react-native-pdf-view.
Hope this helps!

@nickythorne Yes that's what I've done so far. I'll maybe send a PR to have this feature directly in this lib.

Is there an updated solution to this issue?

@nickythorne @jr-k could you please provide some example code? I have tried using Fetch-Blob to download the file locally and then display it with no results. Your help would be much appreciated

Hey! This solution worked nicely for me.

Is there a way to open a PDF without download it? Open pdfs in Webview are working perfectly for me on iOs but not in android.5.0

@pgonzalez-santiago you can use normal webView with google pdf uri
http://docs.google.com/gview?embedded=true&url=' + this.state.pdfPath


testing setuptsugi

@torinfo have started to test this and have the following comments so far...
Good that it prompts for login when simply visiting /setuptsugi but it just says "Sign in" and ideally I think there should be a line that says something like "This feature requires admin login and should only be used by those responsible for maintaining your installation."
After admin login and the welcome screen I wonder about the following text changes:
Should it be Welcome to TSUGI setup rather than the Tsugi setup?
Item 5 has a typo says top rather than to
Item 6 - does this also work if Tsugi was installed in it's own database rather than within the xerte database?
In my local xampp I got the following:
Running pre-flight checks
Your PHP version (5.6.8) is not supported by TSUGI. Please update to a verion >= 7.4 or lower than 8.1.
Aborting!
That's obviously good but means I haven't yet tested beyond this point.
Also typo verion should be version.
I would also change the second part of that line to Please update to a PHP version 7.4 or higher but  lower than PHP 8.1.
At the moment I wasn't able to go further because of the PHP version issue but questions I would have:
where does the backup of the database go? Perhaps that should be mentioned in advance even if it's then mentioned during the procedure?
I also checked what changes with an install that doesn't yet have Tsugi:
Item 2 should probably say Create a folder named tsugi
The upgrade PHP message has the same typo and should change the same as above.
I'll try again later with a compatible PHP version and add further comments as appropriate.

Just a quick note to say I can't test further at the moment. My other xampp on another drive is PHP 7.2 so still not late enough to test. :-( All my online installs are late enough but I'd want to test via a compatible xampp first. Perhaps someone else can test?

@ronm123 Perhaps I should setup a xerte to test this specifically on Linux.
Although you can use the setup on XAMPP, you cannot do an upgrade, as there is no sure way to do a backup. And LIT on XAMPP (except for testing) does not make sense anyway.
I changed all the texts as you indicated, but I cannot (easily) add a text to teh login prompt. Or I would need to build a form for logging in. I'll see how much work that would be.

@ronm123 Referring to your item6 above, No. that does not work. The code will not know how to make a backup of the database, and will abort.

@torinfo I understand that there are differences between local xampp on windows and a Linux install but I'm just trying to help reduce the errors and issues we might well have reported when others test this. I updated the PHP and Apache on one of my xampp installs and pulled down the latest develop, installed xerte and then visited setuptsugi:

Should probably be consistent with use of TSUGI or Tsugi so perhaps change those green lines to TSUGI?
the red line has a typo databade instead of database
I was able to use upgrade via tsugi admin - not sure why it didn't work as part of the installation.
I also noticed that in Tenant keys there are two entries:

Not sure where they came from or if that matters. Nothing under issuers.
I'm not going to test beyond this point because I'm guessing the rest is just normal tsugi admin etc.

@torinfo also I revisited /setuptsugi with this install to test upgrade and got the following:
Creating a backup of the current TSUGI folder (this may take several minutes)
Creating backup failed!
Aborting!
I don't know if that failure is the database, folder or both but there perhaps should be some info about where each is supposed to be created/saved and what step failed.

@ronm123 I changed itemized list tha indicates where the backups will end up. Also in this case it says:
Creating a backup of the current TSUGI folder (this may take several minutes)
So it's the backup of the folder that fails. I've split the lines of the backup in the list, so it'is more obvious that there are actuall different steps.

@ronm123 Below is a succesful upgrade:


Use LOCALE_ID as default for locale settings

Bug, feature request, or proposal:
Feature request
What is the expected behavior?
Use LOCALE_ID from @angular/core as default for NativeDateAdapter and possible other locale related features.
What is the current behavior?
NativeDateAdapter uses the browsers locale.
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
http://plnkr.co/edit/I5RmX52yjb4U1v8n0fYT?p=preview
What is the use-case or motivation for changing an existing behavior?
Currently, it feels very clunky that you have to manually set the locale that is used by the datepicker by setting locale on DateAdapter. Especially if LOCALE_ID has already been specified. I expected an Angular library like Material to use the same locale setting as Angular (LOCALE_ID).
import { LOCALE_ID } from '@angular/core';
import { DateAdapter } from '@angular/material';

@NgModule({
  providers: [
    provide: LOCALE_ID,
    useValue: 'sv-SE'
  }
})
export class AppModule {
  constructor(dateAdapter: DateAdapter) {
    dateAdapter.setLocale('sv-SE');
  }
}

Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: 4.2+
Angular Material: 2.0.0-beta.7
Is there anything else we should know?

If you would appreciate a pull request for this, I could take a crack at it.


Multithreading issue in ZipkinSpanCollector

Hi,
I could see that if in ZipkinSpanCollector, if you have more that one SpanProcessingThread, all the threads are sharing the same instance of  ZipkinCollectorClientProvider. Hence there is a serious multithreading issue.

Any thoughts on the same?

Hi,
Yes, that's a bug. Thanks for reporting. I have never used the ZipkinSpanCollector with more than 1 processing thread so the bug never surfaced for me.
Not sure if others are using more then 1 thread here. It feels like if 1 thread for 1 service instance is not able to flush the spans we probably should lower sample rate.
Feel free to submit a pull request.
I might do a request to ask if it would be feasible to remove the support for multiple threads here #59.

Hi @kristofa Thanks for your reply. I guess you are right, we might not need to have more than a thread if the sampling rate is correct but as a part of performance testing we might need to use more than a thread to throttle the system.
Let me make a fix for this and will send the pull request.

Hi @kristofa ,
Would it also be possible for you to release it, so that instead of using the patch in our production, we can use your library directly.
Thanks

I had 1 small remark on the pr. Once that's in place I can merge it.
How urgent is the release? Are you using multiple threads in ZipkinSpanCollector?  Did you try using a single thread and did it not work for you?

Hi @kristofa,
I have fixed the code according to your comment. Please have a look.
We have been using with single thread and its working perfectly. But as I said earlier, at the time of QA regression and load testing, when we are passing nrOfThreads > 1, it is failing. It would be nice, if you can release, otherwise we would patch the code. No issues :+1:

Hi @kristofa,
Could you please check the pull request and merge the code?
Thanks

Hi @kristofa,
Could you please check the pull request and merge the code?
Thanks

I merged the pr. It will end up in a release which will be available hopefully by Monday.

@kristofa  Thanks :+1:


Typescript compilation errors for keycloak plugin

Describe the bug
I'm following the documentation to setup authn/authz with the janus-idp keycloak plugin as described at https://janus-idp.io/plugins/keycloak.
After installing the plugin and modifying the catalog plugin file, typescript compilation fails to find a declaration of types for the plugins
Expected Behavior
yarn tsc should complete with no errors
What are the steps to reproduce this bug?

Install a fresh Backstage: BACKSTAGE_APP_NAME=backstage npx -y -q<EMAIL_ADDRESS>--path backstage
Install the keycloak plugin: cd backstage && yarn --cwd packages/backend add @janus-idp/backstage-plugin-keycloak-backend
Modify the packages/backend/src/plugins/catalog.ts file as described at https://janus-idp.io/plugins/keycloak

import { CatalogBuilder } from '@backstage/plugin-catalog-backend';
import { ScaffolderEntitiesProcessor } from '@backstage/plugin-catalog-backend-module-scaffolder-entity-model';
import { Router } from 'express';
import { PluginEnvironment } from '../types';
+ import { KeycloakOrgEntityProvider } from '@janus-idp/backstage-plugin-keycloak-backend';

export default async function createPlugin(
  env: PluginEnvironment,
): Promise<Router> {
  const builder = await CatalogBuilder.create(env);
  builder.addProcessor(new ScaffolderEntitiesProcessor());

+  builder.addEntityProvider(
+    KeycloakOrgEntityProvider.fromConfig(env.config, {
+      id: 'development',
+      logger: env.logger,
+      scheduler: env.scheduler,
+    }),
+  );

  const { processingEngine, router } = await builder.build();
  await processingEngine.start();
  return router;
}

Run the typescript compiler: yarn tsc

Typescript compilation results:
yarn run v1.22.21
$ tsc
packages/backend/src/plugins/catalog.ts:5:43 - error TS7016: Could not find a declaration file for module '@janus-idp/backstage-plugin-keycloak-backend'. <EMAIL_ADDRESS>implicitly has an 'any' type.
  Try `npm i --save-dev @types/janus-idp__backstage-plugin-keycloak-backend` if it exists or add a new declaration (.d.ts) file containing `declare module '@janus-idp/backstage-plugin-keycloak-backend';`

5 import { KeycloakOrgEntityProvider } from '@janus-idp/backstage-plugin-keycloak-backend';
                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Found 1 error in packages/backend/src/plugins/catalog.ts:5

error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Versions of software used and environment

latest Backstage 1.20.3
@janus-idp/backstage-plugin-keycloak-backend@1.

Confirmed here also.

Confirmed still missing in 1.9.9.

It looks like the index.d.ts file is available from version 1.9.13.
You can find more details and the latest version here: npm package link.


Documentation:  Wrong name for test file

Please select a category the issue is focused on?
Other
Let us know where something needs a refresh or put your idea here!
The name for the test program is test-is.R but the tests inside that program are related to functions from is.R program. Need to appropriately rename the test file.

It does look like the functions for convert_dtm_to_dtc in stored in the R/dev-utilities.R. So I can move the negate_vars test to  test-dev_utils  and since test-dev_utils already has test for the convert_dtm_to_dtc I get rid of the test-is.R file and not move the additional convert_dtm_to_dtc test from test-is.R, does that sound good?

Yes that makes sense.  Thank you for being so thorough!


Generalize db.query.parameter.<key> to db.operation.parameter.<key>

Generalize db.query.parameter.<key> to db.operation.parameter.<key>, so that it can be used also for stored procedure parameters as well (and maybe other kinds of operations?)
Note: I don't think(?) schema transforms support attribute type template[string]

Note: I don't think(?) schema transforms support attribute type template[string]

@lquerel this is another data point on schema transformation limitations. Do we have an existing tracking issue I can update to include it?

@lmolkova, we have two GitHub issues related to this topic:

Why we need to change the way the OTEL Schema is specified: Limitations and evolution of the OpenTelemetry Schema file.
The diff format I’m proposing, which could serve as the basis for a migration guide, schema update, etc.: Diff between two versions of a semconv registry - Proposal.

It would be great to get your feedback on one or both of these issues, especially in light of the discussions in the current PR.

Note: I don't think(?) schema transforms support attribute type template[string]

@lquerel this is another data point on schema transformation limitations. Do we have an existing tracking issue I can update to include it?


add analytics to modals and selects

Closes #1522

Coverage decreased (-0.6%) to 78.268% when pulling 50737b3030eb61366a42ee28e2bd81273de745d2 on na3d:stat-actions into 0d049c4499775015ff84ce1e9ef7d5111ffd0273 on linode:develop.

changes look fine, I would just like to rename a couple things so that analytics is not referenced in generic components.

Follow up: https://github.com/linode/manager/issues/2151


Bump SBT to 1.0.4 and update plugins

This requires anyone including chisel as a submodule to bump their version of sbt as well.

Type of change

[ ] Bug report
[ ] Feature request
[x] Other enhancement

Impact

[ ] no functional change
[ ] API addition (no impact on existing code)
[x] API modification

Development Phase

[ ] proposal
[x] implementation

Release Notes

Bump SBT version

This is a 3.1.0 milestone and shouldn't be in the 3.0.1 release that is scheduled to go out on Wednesday. I'll try to be careful cherry-picking the commits for Wednesday's release.

I think it's the same problem with #735. I also think it would be cool if we could get a bot to merge tagged PRs to their appropriate release branches automatically once they're merged to master (assuming no conflicts).


removed knownSrcType

knownSrc has been removed from SimPEG, so it is no longer needed

Coverage decreased (-0.15%) to 32.73% when pulling 88556af40cdd31b9b0a52d5a74be04e488d5a9ae on removeKnownSrc into 6eabd68a1d6e3d3cafa4ebf46aeca55fb18d789e on master.


gradientColorStops behaves differently

What version of @tailwindcss/jit are you using?
v0.1.4
What version of Node.js are you using?
14.10.1
What browser are you using?
Chrome
What operating system are you using?
Windows 10
Reproduction repository
https://github.com/jayars/tailwindcss-jit-gradientcolorstop
Hi,
gradientColorStops seems to behave differently when using @tailwindcss/jit.

tailwindcss: Custom gradient stops work
@tailwindcss/jit: Custom gradient stops don't work

Not sure if this is as-designed or a bug.
postcss.config.js
module.exports = {
  plugins: {
    '@tailwindcss/jit': {},
    autoprefixer: {},
  },
}

tailwind.config.js
module.exports = {
  ...
  theme: {
    extend: {
      gradientColorStops: {
        x: '#b1eafc',
        y: '#fbd7f8'
      }
    }
  }
  ...
}

Thanks

Fixed in v0.1.5, thanks for reporting!


[WIP] Add fmcombine pass

This can be used to significantly improve solving time in cases where a formal testbench contains two instances of the same module and feeds them almost identical inputs.

Some results. The "easy" steps are getting longer but the "hard" steps are sped up.

With fmcombine
SBY 21:48:29 [mut_equiv_0] engine_0: ##   0:00:05  Checking assumptions in step 8..
SBY 21:48:29 [mut_equiv_0] engine_0: ##   0:00:05  Checking assertions in step 8..
SBY 21:48:46 [mut_equiv_0] engine_0: ##   0:00:23  Checking assumptions in step 9..
SBY 21:48:46 [mut_equiv_0] engine_0: ##   0:00:23  Checking assertions in step 9..
SBY 21:49:24 [mut_equiv_0] engine_0: ##   0:01:01  Checking assumptions in step 10..
SBY 21:49:30 [mut_equiv_0] engine_0: ##   0:01:07  Checking assertions in step 10..
SBY 21:50:30 [mut_equiv_0] engine_0: ##   0:02:07  waiting for solver (1 minute)
SBY 21:50:31 [mut_equiv_0] engine_0: ##   0:02:08  Checking assumptions in step 11..
SBY 21:50:34 [mut_equiv_0] engine_0: ##   0:02:11  Checking assertions in step 11..
SBY 21:51:34 [mut_equiv_0] engine_0: ##   0:03:11  waiting for solver (1 minute)
SBY 21:52:42 [mut_equiv_0] engine_0: ##   0:04:19  Checking assumptions in step 12..
SBY 21:52:52 [mut_equiv_0] engine_0: ##   0:04:28  Checking assertions in step 12..
SBY 21:53:52 [mut_equiv_0] engine_0: ##   0:05:29  waiting for solver (1 minute)
SBY 21:57:52 [mut_equiv_0] engine_0: ##   0:09:29  waiting for solver (5 minutes)
SBY 21:59:12 [mut_equiv_0] engine_0: ##   0:10:49  Status: PASSED
SBY 21:59:12 [mut_equiv_0] engine_0: finished (returncode=0)
SBY 21:59:12 [mut_equiv_0] engine_0: Status returned by engine: PASS
SBY 21:59:12 [mut_equiv_0] summary: Elapsed clock time [H:MM:SS (secs)]: 0:10:51 (651)
SBY 21:59:12 [mut_equiv_0] summary: Elapsed process time [H:MM:SS (secs)]: 0:10:52 (652)
SBY 21:59:12 [mut_equiv_0] summary: engine_0 (smtbmc yices) returned PASS
SBY 21:59:12 [mut_equiv_0] DONE (PASS, rc=0)

Without fmcombine
SBY 22:14:35 [mut_equiv_0] engine_0: ##   0:00:02  Checking assumptions in step 8..
SBY 22:14:35 [mut_equiv_0] engine_0: ##   0:00:02  Checking assertions in step 8..
SBY 22:14:40 [mut_equiv_0] engine_0: ##   0:00:07  Checking assumptions in step 9..
SBY 22:14:40 [mut_equiv_0] engine_0: ##   0:00:07  Checking assertions in step 9..
SBY 22:14:52 [mut_equiv_0] engine_0: ##   0:00:20  Checking assumptions in step 10..
SBY 22:14:53 [mut_equiv_0] engine_0: ##   0:00:20  Checking assertions in step 10..
SBY 22:15:25 [mut_equiv_0] engine_0: ##   0:00:52  Checking assumptions in step 11..
SBY 22:15:25 [mut_equiv_0] engine_0: ##   0:00:52  Checking assertions in step 11..
SBY 22:16:25 [mut_equiv_0] engine_0: ##   0:01:52  waiting for solver (1 minute)
SBY 22:16:53 [mut_equiv_0] engine_0: ##   0:02:20  Checking assumptions in step 12..
SBY 22:16:53 [mut_equiv_0] engine_0: ##   0:02:20  Checking assertions in step 12..
SBY 22:17:53 [mut_equiv_0] engine_0: ##   0:03:20  waiting for solver (1 minute)
SBY 22:21:53 [mut_equiv_0] engine_0: ##   0:07:20  waiting for solver (5 minutes)
SBY 22:26:53 [mut_equiv_0] engine_0: ##   0:12:20  waiting for solver (10 minutes)
SBY 22:31:53 [mut_equiv_0] engine_0: ##   0:17:20  waiting for solver (15 minutes)
SBY 22:33:01 [mut_equiv_0] engine_0: ##   0:18:28  Status: PASSED
SBY 22:33:01 [mut_equiv_0] engine_0: finished (returncode=0)
SBY 22:33:01 [mut_equiv_0] engine_0: Status returned by engine: PASS
SBY 22:33:01 [mut_equiv_0] summary: Elapsed clock time [H:MM:SS (secs)]: 0:18:29 (1109)
SBY 22:33:01 [mut_equiv_0] summary: Elapsed process time [H:MM:SS (secs)]: 0:18:29 (1109)
SBY 22:33:01 [mut_equiv_0] summary: engine_0 (smtbmc yices) returned PASS
SBY 22:33:01 [mut_equiv_0] DONE (PASS, rc=0)

With fmcombine
SBY 22:36:54 [mut_equiv_100] engine_0: ##   0:00:05  Checking assumptions in step 8..
SBY 22:36:54 [mut_equiv_100] engine_0: ##   0:00:05  Checking assertions in step 8..
SBY 22:37:10 [mut_equiv_100] engine_0: ##   0:00:20  Checking assumptions in step 9..
SBY 22:37:14 [mut_equiv_100] engine_0: ##   0:00:25  Checking assertions in step 9..
SBY 22:37:39 [mut_equiv_100] engine_0: ##   0:00:50  Checking assumptions in step 10..
SBY 22:37:39 [mut_equiv_100] engine_0: ##   0:00:50  Checking assertions in step 10..
SBY 22:38:34 [mut_equiv_100] engine_0: ##   0:01:45  Checking assumptions in step 11..
SBY 22:38:34 [mut_equiv_100] engine_0: ##   0:01:45  Checking assertions in step 11..
SBY 22:39:35 [mut_equiv_100] engine_0: ##   0:02:45  waiting for solver (1 minute)
SBY 22:40:44 [mut_equiv_100] engine_0: ##   0:03:54  Checking assumptions in step 12..
SBY 22:40:44 [mut_equiv_100] engine_0: ##   0:03:55  Checking assertions in step 12..
SBY 22:41:44 [mut_equiv_100] engine_0: ##   0:04:55  waiting for solver (1 minute)
SBY 22:45:44 [mut_equiv_100] engine_0: ##   0:08:55  waiting for solver (5 minutes)
SBY 22:46:13 [mut_equiv_100] engine_0: ##   0:09:24  Status: PASSED
SBY 22:46:13 [mut_equiv_100] engine_0: finished (returncode=0)
SBY 22:46:13 [mut_equiv_100] engine_0: Status returned by engine: PASS
SBY 22:46:13 [mut_equiv_100] summary: Elapsed clock time [H:MM:SS (secs)]: 0:09:26 (566)
SBY 22:46:13 [mut_equiv_100] summary: Elapsed process time [H:MM:SS (secs)]: 0:09:27 (567)
SBY 22:46:13 [mut_equiv_100] summary: engine_0 (smtbmc yices) returned PASS
SBY 22:46:13 [mut_equiv_100] DONE (PASS, rc=0)

Without fmcombine
SBY 22:47:05 [mut_equiv_100] engine_0: ##   0:00:02  Checking assumptions in step 8..
SBY 22:47:05 [mut_equiv_100] engine_0: ##   0:00:02  Checking assertions in step 8..
SBY 22:47:10 [mut_equiv_100] engine_0: ##   0:00:08  Checking assumptions in step 9..
SBY 22:47:10 [mut_equiv_100] engine_0: ##   0:00:08  Checking assertions in step 9..
SBY 22:47:24 [mut_equiv_100] engine_0: ##   0:00:21  Checking assumptions in step 10..
SBY 22:47:24 [mut_equiv_100] engine_0: ##   0:00:22  Checking assertions in step 10..
SBY 22:47:54 [mut_equiv_100] engine_0: ##   0:00:52  Checking assumptions in step 11..
SBY 22:48:01 [mut_equiv_100] engine_0: ##   0:00:59  Checking assertions in step 11..
SBY 22:49:01 [mut_equiv_100] engine_0: ##   0:01:59  waiting for solver (1 minute)
SBY 22:49:29 [mut_equiv_100] engine_0: ##   0:02:26  Checking assumptions in step 12..
SBY 22:49:29 [mut_equiv_100] engine_0: ##   0:02:27  Checking assertions in step 12..
SBY 22:50:29 [mut_equiv_100] engine_0: ##   0:03:27  waiting for solver (1 minute)
SBY 22:54:29 [mut_equiv_100] engine_0: ##   0:07:27  waiting for solver (5 minutes)
SBY 22:59:29 [mut_equiv_100] engine_0: ##   0:12:27  waiting for solver (10 minutes)
SBY 23:04:29 [mut_equiv_100] engine_0: ##   0:17:27  waiting for solver (15 minutes)
SBY 23:11:43 [mut_equiv_100] engine_0: ##   0:24:40  Status: PASSED
SBY 23:11:43 [mut_equiv_100] engine_0: finished (returncode=0)
SBY 23:11:43 [mut_equiv_100] engine_0: Status returned by engine: PASS
SBY 23:11:43 [mut_equiv_100] summary: Elapsed clock time [H:MM:SS (secs)]: 0:24:41 (1481)
SBY 23:11:43 [mut_equiv_100] summary: Elapsed process time [H:MM:SS (secs)]: 0:24:42 (1482)
SBY 23:11:43 [mut_equiv_100] summary: engine_0 (smtbmc yices) returned PASS
SBY 23:11:43 [mut_equiv_100] DONE (PASS, rc=0)


Provide typings definitions (TypeScript) for semantic-ui-react

Previously, issue #361 mentioned the potential for typescript typings. It would be really handy to have these, especially considering the substantially improved Typescript/react interoperation.
Version
0.61.7

Here is the output of dts-gen -m semantic-ui-react as a starting point:
https://gist.github.com/DylanLukes/e864dc61a663b6a5a03a6c4f5e15fd38

Duplicate #674, see that work for the latest developments.


String tensor support for tfjs 0.14.0

This brings string Tensors to Node.js. The C API stores strings kinda funny - one big void * that has a bunch of offsets in the buffer. The bulk of this PR is breaking a JS string array down and placing them in the right spots.
I've added Asim for C++ API review.

This change is

cc myself as this is blocking resolution for issue https://github.com/tensorflow/tfjs/issues/410


VM: Vote/Unvote PrecompiledContracts should not be callable when local=true

calling a precompiled contract when local=true is usually allowed, so there is no check.
However, for the semux precompiled contracts, they need to be within a transaction.
Currently I can call it, and it shows up as me voting for delegate in my local DB, but no other nodes would know about it.. probably breaks my local DB.
We could ->

Add something to the context to be able to determine internal/external calls
add another method to PrecompiledContract interface to denote whether they can be run as local calls.

Let me know which sounds more preferable, and I can implement (or free free to update).  The second seems more extensible, can use default interface methods to return allow local, seems like a more general solution, but open to either.

Some of this has been fixed/mitigated with recent changes in #201 but I'm not sure its sufficient enough.
local calls with API are now gated through not sending a from address nor signature, so this should prevent these contracts from being called due to failure checks if from is not set.
Should cover most cases, but is worth additional eyes.

I think local call into precompiled contract should be allowed, either by transaction or internal transaction.

Yes. For other precompiled contracts.  But not vote/unvote
Maybe the bug here is that we are committing the repository on internal calls.  Internal calls are not permitted to change state, so we should never commit...

Good point!
The reason is that the local-call transaction state changes are committed in the pending manager. This is not correct, they should be discarded.
https://github.com/semuxproject/semux-core/blob/19f71512572ee0a6bf6d05ba3c31990b2b9ad29b/src/main/java/org/semux/core/PendingManager.java#L371


Improve notifyPath/notifySplices API for public usage

The current path notification API has a couple of warts making it problematic for use by data adapter layers providing alternate forms of data observation:

notifyPath accepts only collection keys for arrays (as opposed to array indicies as set does).  With the changes to resolve https://github.com/Polymer/polymer/issues/2007, set will accept either keys or indicies, and the public version of notifyPath should do so as well; this will likely involve refactoring internal usage of notifyPath to avoid the overhead of key/index disambiguation when it is known that the path is key-based
_notifySplices is currently private and undocumented; for a fully operable data observation layer, this needs to be exposed publicly

PR here: https://github.com/Polymer/polymer/pull/2513

@kevinpschaaf I think the docs may need some adjustment now, given that set no longer leverages notifyPath for sugar.  Thinking of this quote,

Since in the majority of cases, notifyPath will be called directly after an assignment, a convenience function set is provided that performs both the assignment and notify actions.

I realize that it doesn't explicitly say that set uses notifyPath directly, but it seems to imply that this is the case.  Now set uses the private interface _notifyPath.
Out of curiosity, is there any way set, splice, push, etc. could continue to use the notifyPath public interface?  We were patching notifyPath to add functionality to set, splice, push, etc.  It's a nice assumption to be able to make, that notifyPath is used by all those methods.

That the other API's now use _notifyPath rather than the public notifyPath is an implementations detail.  We do this for performance reasons: since the public notifyPath has to do the index->key normalization, we are careful to only do that once in the other public API's, and call _notifyPath internally, which accepts only pre-normalized key-based paths.  So I don't think we'd consider changing that back as it's a performance consideration.

Cool– that makes sense.  Thanks for getting back!


Development: Extend documentation with useful information for Artemis admins

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context
Just some information I had in our internal docs which I though might be useful for others, too.
Steps for Testing
There are two new pages in the admin section of the documentation:

General Production Setup Tips, and
Useful Database Commands

Review Progress

Manual Tests

[x] Test 1
[x] Test 2

Maybe we can also add the ls1intum/artemis-ansible-collection and maybe other infrastructure related repositories which might help new administrators?

Sure, adding more production-setup related information for admins definitely makes sense. I’d leave that specific example to someone who is more familiar with it and knows if the Ansible collection is ready/when it is ready, though (I’ve not looked at it in detail so far as I’ve got my own).


Roll Flutter from 7bad4eb9d871 to 02558d69d923 (26 revisions)

https://github.com/flutter/flutter/compare/7bad4eb9d871...02558d69d923
2022-06-17<EMAIL_ADDRESS>Revert "Fix StretchingOverscrollIndicator clipping and add clipBehavior parameter" (flutter/flutter#106207)
2022-06-17<EMAIL_ADDRESS>Roll Plugins from 8bee94ca9822 to c3955d221178 (3 revisions) (flutter/flutter#106200)
2022-06-17<EMAIL_ADDRESS>Roll Flutter Engine from 746b33282f74 to 6cb83ab0f155 (1 revision) (flutter/flutter#106178)
2022-06-17<EMAIL_ADDRESS>Roll Flutter Engine from df5144dd451d to 746b33282f74 (1 revision) (flutter/flutter#106175)
2022-06-17<EMAIL_ADDRESS>Roll Flutter Engine from 3c4ca2762e20 to df5144dd451d (1 revision) (flutter/flutter#106171)
2022-06-17<EMAIL_ADDRESS>Roll Flutter Engine from ee71e31c36ce to 3c4ca2762e20 (2 revisions) (flutter/flutter#106167)
2022-06-17<EMAIL_ADDRESS>Fix debugPaintSize throws 'Null Check error' (flutter/flutter#106108)
2022-06-17<EMAIL_ADDRESS>Roll Flutter Engine from f8c0dc87bc53 to ee71e31c36ce (41 revisions) (flutter/flutter#106162)
2022-06-17<EMAIL_ADDRESS>Update package:archive and pin test_api (flutter/flutter#106157)
2022-06-17<EMAIL_ADDRESS>Update the platform properties for android bots (flutter/flutter#106146)
2022-06-17<EMAIL_ADDRESS>[flutter_tools] temporary directory (flutter/flutter#105815)
2022-06-17<EMAIL_ADDRESS>[web] Fix JS crash when FF blocks service workers. (flutter/flutter#106072)
2022-06-16<EMAIL_ADDRESS>[flutter_tools] update test/src to null safety (flutter/flutter#106064)
2022-06-16<EMAIL_ADDRESS>Ignore body_might_complete_normally_catch_error violations (flutter/flutter#105795)
2022-06-16<EMAIL_ADDRESS>parse build version on xcodeproj (flutter/flutter#105908)
2022-06-16<EMAIL_ADDRESS>[gen_keycodes] Remove invalid Web code maps (flutter/flutter#106074)
2022-06-16<EMAIL_ADDRESS>[gen_keycodes] Clarify the README that the code scheme also applies to physical keys (flutter/flutter#106078)
2022-06-16<EMAIL_ADDRESS>Fix StretchingOverscrollIndicator clipping and add clipBehavior parameter (flutter/flutter#105303)
2022-06-16<EMAIL_ADDRESS>Ignore uses of soon-to-be deprecated NullThrownError. (flutter/flutter#105693)
2022-06-16<EMAIL_ADDRESS>Fix SliverPadding geometry  (flutter/flutter#106071)
2022-06-16<EMAIL_ADDRESS>Revert "[Conductor] Update post submit location (#106120)" (flutter/flutter#106127)
2022-06-16<EMAIL_ADDRESS>[Conductor] Update post submit location (flutter/flutter#106120)
2022-06-16<EMAIL_ADDRESS>Revert "Make RenderSliverGrid more accurately report overflow" (flutter/flutter#106123)
2022-06-16<EMAIL_ADDRESS>Add more CMake unit tests (flutter/flutter#106076)
2022-06-16<EMAIL_ADDRESS>[framework] fix RangeSlider regression due to touch slop changes (flutter/flutter#106094)
2022-06-16<EMAIL_ADDRESS>added microbenchmark for loading assets (flutter/flutter#105982)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Plugins: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Landing manually since the autosubmit process is confused by skipped tests.


Updated to use the latest version of raspbian and the newest JDK repo.

@nikhilbhardwaj - Have you happened to have pushed the image this builds anywhere?

Thanks @nikhilbhardwaj


[Accessibility] Cannot use Shift+Tab as an input key in terminal

Type: Bug
Repro

Configure the settings like below:

settings.json:
{
  "terminal.integrated.tabFocusMode": false
}

Create new terminal via ctrl+`

Press Shift+Tab from terminal input.

Current Behavior
Pressing Shift+Tab moves to the terminal buffer.
Expected Behavior
Shift+Tab should be passed to terminal as an input key. The focus needs to remain in the terminal input field.
We need Shift+Tab when cycling back through shell auto-suggestion or ipython completion.
VS Code version: Code - Insiders 1.81.0-insider (c85bf61a82b0c39886b032d2634108782a55c637, 2023-07-19T05:34:51.441Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz (8 x 2611)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.71GB (6.44GB free)

Process Argv
--crash-reporter-id b05b88e5-8894-4031-ae34-fa034ebddea9

Screen Reader
yes

VM
0%

Extensions (90)

Extension
Author (truncated)
Version

android-dev-ext
ade
1.3.2

Bookmarks
ale
13.4.1

openscad
Ant
1.1.1

spellright
ban
3.0.116

zoterolatex
bna
0.4.1

mermaid-markdown-syntax-highlighting
bpr
1.5.2

doxdocgen
csc
1.4.0

dscodegpt
Dan
2.1.14

vscode-markdownlint
Dav
0.51.0

vscode-eslint
dba
2.4.2

vscode-quick-select
dba
0.2.9

vscode-deno
den
3.19.1

gitlens
eam
14.1.1

EditorConfig
Edi
0.16.4

prettier-vscode
esb
9.19.0

vscode-google-translate
fun
1.4.13

codespaces
Git
1.14.12

copilot
Git
1.97.271

copilot-chat
Git
0.5.2023071901

remotehub
Git
0.60.0

vscode-github-actions
git
0.25.8

vscode-pull-request-github
Git
0.68.1

easy-snippet
inu
0.6.3

path-autocomplete
ion
1.24.1

latex-workshop
Jam
9.13.1

lilypond-syntax
jea
0.1.1

scheme
jea
0.2.0

better-cpp-syntax
jef
1.17.2

google-search
kam
0.0.1

vscode-lua-format
Koi
1.3.8

lilypond-formatter
lhl
0.2.3

lilypond-pdf-preview
lhl
0.2.8

lilypond-snippets
lhl
0.1.1

vslilypond
lhl
1.7.3

zotero
mbl
0.1.10

git-graph
mhu
1.30.0

vscode-docker
ms-
1.26.0

black-formatter
ms-
2023.4.1

flake8
ms-
2023.6.0

isort
ms-
2023.11.11921012

python
ms-
2023.12.0

vscode-pylance
ms-
2023.7.30

jupyter
ms-
2023.6.1101941928

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

remote-containers
ms-
0.301.0

remote-ssh
ms-
0.102.0

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.80.2

vscode-remote-extensionpack
ms-
0.24.0

azure-repos
ms-
0.36.0

cmake-tools
ms-
1.14.34

cpptools
ms-
1.16.3

cpptools-extension-pack
ms-
1.3.0

js-debug-nightly
ms-
2023.7.1717

remote-repositories
ms-
0.38.1

vscode-github-issue-notebooks
ms-
0.0.129

vscode-selfhost-test-provider
ms-
0.3.15

vscode-serial-monitor
ms-
0.10.0

vsliveshare
ms-
1.0.5873

resourcemonitor
mut
1.0.7

autodocstring
njp
0.6.1

pandocciter
not
0.10.2

shiny-python
Pos
0.1.2

shinyuieditor
pos
0.4.3

quarto
qua
1.90.0

r-debugger
RDe
0.5.4

java
red
1.20.0

vscode-xml
red
0.26.1

r
REd
2.8.1

multi-command
ryu
1.6.0

vscode-deepl
soe
1.0.6

abc-music
sof
0.4.0

lua
sum
3.6.23

latex-utilities
tec
0.4.10

chatgpt
tim
1.1.2

cmake
twx
0.0.17

errorlens
use
3.12.0

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

vscode-arduino
vsc
0.6.0

vscode-java-debug
vsc
0.52.0

vscode-java-dependency
vsc
0.23.0

vscode-java-pack
vsc
0.25.12

vscode-java-test
vsc
0.39.0

vscode-maven
vsc
0.41.0

markdown-all-in-one
yzh
3.5.1

grammarly
znc
0.22.1

(1 theme extensions excluded)

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30404738
py29gd2263:30784851
vsclangdf:30492506
c4g48928:30535728
dsvsc012:30540252
pynewext54:30618038
pylantcb52:30590116
a9j8j154:30646983
showlangstatbar:30737417
ecj1e332:30687743
pythonfmttext:30716741
pythoncmvfstr:30726892
fixshowwlkth:30771523
hideindicator:30766887
pythongtdpath:30726887
i26e3531:30792625
gsofa:30778558
pythonnosmt12:30779711
pythonidxpt:30768918
pythondjangots:30768917
pythonnoceb:30776497
copilotsettingt:30767686
e537b577:30772214
h0f32768:30792099
synctok:30783813
dsvsc013:30777762
dsvsc014:30777825
diffeditorv2:30786206

related https://github.com/microsoft/vscode/issues/187875
this also reproduces in stable VS code

We're going to remove the keybinding altogether as it should enter the buffer when toggle tab moves focus is enabled and not (as designed) without that

Changing the keybinding could throw users off, though @jooyoungseo is wondering if we can treat this like a widget with results/ input and allow moving between the two with keybindings consistent with #179967

Shift+tab is still going to the workbench even when I remove that keybinding and have tab moves focus mode off

We now allow using alt+f2 or ctrl/cmd+UpArrow to go to the terminal accessible buffer instead.
I think it makes sense to remove Shift+tab as a keybinding next iteration if we agree that makes sense @jooyoungseo and @rperez030. The only downside of that would be users might already have shift+tab in their muscle memory.

If we cannot resolve the synchronization issue with autocomplete and shift +Tab, I am in favor of removing the key-binding. there are worse things than retraining mussel memory.

Yes, @jooyoungseo and I just discussed, and we agree it can be removed this iteration.

We will also remove the tab index

I cannot reproduce the original issue in stable (either 1.81 or 1.78). What are the steps to verify?

Sorry, to verify, focus a terminal with screen reader mode enabled. Use shift+tab. the accessible buffer should not open.

Guessing we need to do something with tabindex that must've been removed in order to get this to work

I think it would be either shift+tab needs to be specially handled in xterm.js or we should handle it and cancel the event in the custom key event handler.

https://github.com/microsoft/vscode/blob/c4a75648e0789ab6c83839165d03403ad24181c6/src/vs/workbench/contrib/terminal/browser/terminalInstance.ts#L1010

not sure how this was working before. I dug through commits and tried reverting this one, which didn't help.
https://github.com/microsoft/vscode/commit/1d0175478873e6ad29033d84925ce5d936032b3c


feat: Allow modifying the iam-github-oidc-role subject condition

Description

Allow modifying the iam-github-oidc-role subject condition

Motivation and Context

Resolves #522

Breaking Changes

How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[ ] I have executed pre-commit run -a on my pull request

This PR is included in version 5.45.0 :tada:


add todo's at the top of the todo-list?

Todo's are added to the bottom by default, which makes it very hard to move them to the top if the list of todo's is long, especially on mobile.
In most cases, newly added todo's are highest prio in case..so is there a way to change this behaviour?
I was poking around, but I couldn't really figure out where the add-to-bottom behaviour is programmed...
any idea?

@coderofsalvation Yes, I think it is good idea.

@coderofsalvation Thank you for feedback, I have pushed a improvement, could you confirm it is ok to you? #9


New source files Import Options

Crowdin Rest API Add File and Update or Restore File now support new ImportOptions types:

Html File Import Options
Html with Front Matter File Import Options
Mdx v1 File Import Options

These new Import Options should be added to this API client as well as the corresponding unit tests.

New task : add support of "Mdx V1 File Import Options"


Openmm with  numpy2

Refs https://github.com/haddocking/haddock3/issues/1115

Runs https://github.com/haddocking/haddock3/blob/main/examples/thirdparty/openmm/openmm-test.cfg example in webapp.

Seems the behavior of openmm82 is different I saw it using 2 x 4 cores instead of just 4 cores.

Superseeded by #167


[Bug]: Correcting name convention of many games in the Repo and also updating the README.md [gssoc23]

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Name convention of many games is not according to the contributing guidelines.
Fixes #2621

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ ] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[ ] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @thevirengarg ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@kunjgit @Arun9739 @gurjeetsinghvirdee sir, please review this pull request

Thank you  @thevirengarg , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀