Add AndroidX Core dependency to Android backend

https://github.com/libgdx/libgdx/pull/7004 introduced a dependency to androidx.core that was not added as a transitive dependency and required users to manually add it to their projects.
The version chosen of AndroidX Core is 1.13.1 which is the latest we can support with out minSDK of 19. This version requires setting targetSdk to, at least, 34 which is something we had to do anyway because Google Play requires 34+ target sdk anyway.
The Android Tests module also requires Kotlin BOM dependency to handle a dependency collision that is well documented and should disappear when we upgrade to newer versions in the future.
Finally I've removed the explicit BuildTools version as it is automatically set by the AGP.

Would you consider targetSdk 35 or is there something blocking that change from happening? Android 15 has been out a few months now and it seems likely that the next libGDX version will be the last before Google requires it for new apps.

Would you consider targetSdk 35 or is there something blocking that change from happening? Android 15 has been out a few months now and it seems likely that the next libGDX version will be the last before Google requires it for new apps.

The idea with this PR is to make the minimum changes to fix 1.13.0. There's a separate versions upgrade PR (https://github.com/libgdx/libgdx/pull/7526) where the upgrades can be more radical. In any case, targetSDK is set by the user projects/Liftoff and what we set here doesn't make a big difference.


MessageFormatter should be public

Allow other Logging integration to use optimised MessageFormatter implementation
Fixes #12129.

Hey you probably want to open this pull request on the official netty Projekt and not your clone


load_stac: scale_and_offset

Proposed Process ID: load_stac
Proposed Parameter Name: scale_and_offset
Optional: yes, default: False
Context
Recently, after the introduction of the new Sentinel-2 processing baseline, an offset has been introduced (additionally to the scale, which was already present). Previously, since the conversion from digital number (DN) (the actual values in the S2 files) to reflectances was performed only by applying the scale factor, for many applications it was the same as using DN (in many indexes, the scale factor is being neglected).
Now, both have to be applied in order to obtain meaningful results.
Some GitHub issues discussing about this topic:
https://github.com/Element84/earth-search/issues/9
https://github.com/Element84/earth-search/issues/23
https://github.com/opendatacube/odc-stac/issues/55
@jdries @dthiex How do you manage this for the SENTINEL2_L2A collections?
Description
if scale_and_offset is True, apply them automatically. They should be available in the raster:bands extension metadata.
Data Type
boolean
Additional changes

In SH itself we follow this approach (we have a harmonization parameter which if set to true will already compensate the offset).
In openEO SH I believe we don't support setting the parameter so we apply the default meaning we request harmonize DN so DN = 10000*Reflectance is still true.
In my feeling this should though not be part of the load_stac process as it's very specific to the case "I load L2A raw DNs but I want to get Reflectance values".

we currently also configure the behaviour per collection, but most of them require the user to explicitly do it, which is annoying.
For Sentinel-2 we make sure to convert to the 'standard' scaling factor of 0.0001, to avoid issues with the new processing baseline.
It would be nice to have a generic solution for load_collection as well.

yeah, it would be nice if this could be addressed the same way in both load_collection and load_stac.
Side note: I wonder if there isn't a more generic or future-proof parameter name than scale_and_offset to not be limited to just scale and offset transforms. For example in the SH link of Daniel I see clamping of negative values.

The original idea was to have these information in metadata and then apply it automatically during data loading, so I assumed that this is already done and doesn't need a parameter.
I don't like adding very specific parameters to load functions, it just bloats the interface and e.g. doesn't apply to vector data... (we already have the issue with bands).

For load_collection the original idea was to have these information in metadata and then apply it automatically during data loading. Is this done? I think I'd assume the same in load_stac by default, if the metadata is given.

Currently it is not specifically mentioned in the load_stac description. We would have to specify that if the raster extension is available and the scale and/or offset values as well, we apply it. However, I would prefer being able to switch it on/off depending on the use case, since applying it automatically several times changes the data type (like from uint8 to float32 or float64) and requires much more space and resources.
For the load_collection process, as @m-mohr mentions, even for me it is enough to document it in the metadata to keep it as simple and efficient as possible.

For load_collection the original idea was to have these information in metadata and then apply it automatically during data loading. Is this done?

You mean "apply automatically" by client or backend?
If it's automatically to be done by the backend, what is the point of exposing this as collection metadata? Or worse: you even risk the user/client doing the normalization again because of the misunderstand about getting raw DN values or physical values.
In any case, in the VITO backend we don't automatically normalize/harmonize for memory/performance reasons (e.g. if the raw data is uint8, we want to have the option to keep that type when it's not necessary to convert to more memory-heavy floats/doubles). For example if you download SENTINEL2_L2A (B02, B03, B04) without processing, you get  values roughly in the [0-10k] range, instead of reflectances in the [0-1] range. This is obviously a basic behavior we can not change suddenly. Backend-side auto-normalization should be an opt-in feature, e.g. with the proposed scale_and_offset parameter.
It could also be a client feature (opt-in again) to automatically add a apply node to do rescaling based on collection metadata.

The load_collection discussion is a bit off topic in my opinion, let's focus on load_stac!
@soxofaan doing it client side seems more a workaround to me, since it wouldn't be documented in the openEO processes docs and also not available in the same way in the other clients.
Anyway, if we can't agree to have an additional parameter, we should at least document what is the default behaviour of load_stac concerning these parameters (which could also be embedded in the geoTIFF metadata, not only the STAC metadata).


ESNRegressor giving IndexError: too many indices for array: array is 1-dimensional, but 2 were indexed

I'm encountering an error with basic regression over 1D data. It is replicated by:
>>> import numpy as np
>>> from pyrcn.echo_state_network import ESNRegressor
>>> x = np.arange(1000)
>>> y = np.random.normal(0, 1, 1000)
>>> reg = ESNRegressor()
>>> reg.fit(X=x.reshape(-1, 1), y=y)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/anaconda3/lib/python3.8/site-packages/pyrcn/echo_state_network/_esn.py", line 168, in fit
    self._regressor.fit(hidden_layer_state[self.node_to_node.wash_out:, :], y[self.node_to_node.wash_out:, :])
IndexError: too many indices for array: array is 1-dimensional, but 2 were indexed.

Is there something simple here I am missing by chance?

If you check out the dev-Branch, it should work now. You can check the new Jupyter Notebook, where the Mackey-Glass timeseries is predicted using the ESNRegressor.


Version 2 on ispindel hardware esp8266 not seeing force gravity mode

my 2.0-beta2 build of the ispindel hardware does not obey the force gravity mode switch and goes to sleep as soon as it moves from the horizontal position

Im aware of this issue and it will be fixed in the be next release, hopefully this week


bookmarks creation dialog is not keyboard accecible in several ways

you can't cancel it with the keyboard (ESC just closes the sidebar, annoyingly)
changing the folder with the keyboard doesn't seem to be possible

Hmm, the ESC problem seems to be a recent bug.
The second issue will be addressed in v1.13, where there are multiple keyboard navigation improvements.


chore: Enable whitespace trimming in JSON files

Meant to set this as true originally, but realized I left it as false when it wasn't trimming on save 😝

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Automation for azure-sdk-for-node

Automation for azure-sdk-for-js

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Can one of the admins verify this patch?


Throw informative exception from the sheet reader

When dealing with large worksheets, it gets harder to spot the parsing
exceptions. This delta handles exception and throws with column/row
numbers and the sheet name where the parser failed.
Diff without indentation/whitespace changes: https://github.com/ExcelDataReader/ExcelDataReader/pull/148/files?w=1

I think this is maybe too defensive: generally the parser shouldn't crash, and if it does, it is prefered to fix the underlying cause. F.ex some xlsx crashes were already fixed. Admittedly, this PR could assist in finding those underlying causes, but probably shouldn't be the default behavior.
If you have an xlsx that throws an "expected" exception - and was better if including column/row numbers - please resubmit the PR against latest develop branch with a test. Thanks


chore: try free disk for linux

Summary
try free disk to workaround no space problem on ci  see https://github.com/actions/runner-images/issues/2875#issuecomment-1167936457
Test Plan
No Need

Require Documentation?

[x] No
[ ] Yes, the corresponding rspack-website PR is __

it save 20G space, so the tests pass now


(multiple) Change Joystick to Gamepad and some russian translation update

Isn't it's that thing?

XD


[WIP] Beautification and docs

[x] Fix jldoctests
[x] finish API reference
[ ] Write example for PSP
[ ] Write an explanation for Dirac vectors and matrices
[ ] Write example for particle interface
[ ] Write example for models
[ ] Write example for processes

Looking at the documentation of the propagator, it seems outdated. It says the mass of the particle is assumed to be zero if it is not given, but QEDcore never accepts a mass parameter at all. I think it does (and should) get the mass from the passed particle type's mass. So it might be a good idea to update the docs while we're at it.

Since there is not much to say about models (at least not currently), I removed the respective (blank) tutorial page. Similarly, I removed the respective pages for Dirac tensors, because there is not really an interface to talk about. I suggest explaining the Dirac algebra in QEDcore, where it is fully implemented.
From my side, I think this reached a state, where we can consider merging it.


UWT: Annotation:Convert File stopped working

This workflow step has always worked for me but now with an existing workflow step it is throwing the following error: The remote server returned an error: (400) Bad Request.  I'm curious if the service you are calling to perform this conversion has expired/deprecated.
Plugin Trace:
[UltimateWorkflowToolkit.CoreOperations: UltimateWorkflowToolkit.CoreOperations.Annotation.ConvertFile]
[UWT: Annotation: Convert File]
Value of 'Resulting File Name' attribute equals to UCO Collection Manifest.pdf
Value of 'Replace Original File' attribute equals to False
Value of 'Record Reference' attribute equals to https://thirdcoastcommodities.crm.dynamics.com:443/main.aspx?etc=10235&id=048d0cc1-d0ab-4d7f-8424-524cd809863c&histKey=536792463&newWindow=true&pagetype=entityrecord
Value of 'Current File Name' attribute equals to UCO Collection Manifest.docx
Value of 'Throw an Exception on Error' attribute equals to True
Error Message:
Exception type: Microsoft.Crm.CrmException
Message: The remote server returned an error: (400) Bad Request.
at Microsoft.Xrm.RemotePlugin.Client.Interceptors.SandboxFabricClientTelemetryInterceptor.<>c__DisplayClass3_0.b__0()
at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action, IEnumerable1 additionalCustomProperties)    at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute(ILogger logger, XrmTelemetryActivityType activityType, Action action)    at Microsoft.Xrm.RemotePlugin.Client.Interceptors.SandboxFabricClientTelemetryInterceptor.Intercept(IInvocation invocation, IExecutionContext context, SandboxFabricCallTracker sandboxFabricCallTracker)    at Microsoft.Xrm.RemotePlugin.Client.Interceptors.SandboxFabricCodeUnitExecuteBaseInterceptor.Intercept(IInvocation invocation)    at Castle.DynamicProxy.AbstractInvocation.Proceed()    at Castle.Proxies.ISandboxFabricCodeUnitProxy.Execute(ILifetimeScope scope, IExecutionContext context, SandboxFabricCallTracker& sandboxFabricCallTracker)    at Microsoft.Xrm.RemotePlugin.Client.SandboxFabricPlugin.<>c__DisplayClass5_1.<Execute>b__3()    at Polly.Policy.<>c__DisplayClass150_01.b__0(Context ctx, CancellationToken ct)
at Polly.Policy.<>c__DisplayClass143_01.<ExecuteInternal>b__0(Context ctx, CancellationToken ct)    at Polly.RetrySyntax.<>c__DisplayClass12_1.<WaitAndRetry>b__1(Context ctx, CancellationToken ct)    at Polly.Retry.RetryEngine.Implementation[TResult](Func3 action, Context context, CancellationToken cancellationToken, IEnumerable1 shouldRetryExceptionPredicates, IEnumerable1 shouldRetryResultPredicates, Func1 policyStateFactory)    at Polly.RetrySyntax.<>c__DisplayClass12_0.<WaitAndRetry>b__0(Action2 action, Context context, CancellationToken cancellationToken)
at Polly.Policy.ExecuteInternal[TResult](Func3 action, Context context, CancellationToken cancellationToken)    at Polly.Policy.Execute[TResult](Func3 action, Context context, CancellationToken cancellationToken)
at Polly.Policy.Execute[TResult](Func1 action)    at Microsoft.Xrm.RemotePlugin.Client.SandboxFabricPlugin.Execute(IServiceProvider serviceProvider)    at Microsoft.Xrm.RemotePlugin.Client.ResilientSandboxPlugin.<>c__DisplayClass13_1.<Execute>b__0()    at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action, IEnumerable1 additionalCustomProperties)
at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute(ILogger logger, XrmTelemetryActivityType activityType, Action action)
at Microsoft.Xrm.RemotePlugin.Client.ResilientSandboxPlugin.Execute(IServiceProvider serviceProvider)
at Microsoft.Xrm.RemotePlugin.CrmProvider.RemotePlugin.RemotePluginExecute(IServiceProvider serviceProvider, ILifetimeScope lifetimeScope, IExecutionContext executionContext, ILogger logger)
at Microsoft.Xrm.RemotePlugin.CrmProvider.RemotePlugin.Execute(IServiceProvider serviceProvider)
at Microsoft.Crm.Workflow.Services.ProxyCustomActivity.Execute(CodeActivityContext executionContext)
-- End stack trace --

Hello,
Is it an error that keeps occurring?
Are you on the free plan or on the paid one?
Andrew

Hi Andrew
Yes, the error is still occurring.  I’m using the free version of UWT, I wasn’t even aware that there was a paid-version.
Thanks!
Craig
From: Andrew Butenko @.>
Sent: Wednesday, January 12, 2022 9:48 AM
To: AndrewButenko/UltimateWorkflowToolkit @.>
Cc: acraigx @.>; Author @.>
Subject: Re: [AndrewButenko/UltimateWorkflowToolkit] UWT: Annotation:Convert File stopped working (Issue #45)
Hello,
Is it an error that keeps occurring?
Are you on the free plan or on the paid one?
Andrew
—
Reply to this email directly, view it on GitHubhttps://github.com/AndrewButenko/UltimateWorkflowToolkit/issues/45#issuecomment-1011120215, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABWJ2QGZIXTKSDE5QDXKNULUVWIAPANCNFSM5LXJEARQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Hello,
There is no paid version of UWT. I'm talking about Cloud Conver API that is used behind the scenes.
https://cloudconvert.com/pricing
Andrew

Thank you – I had completely forgotten about this aspect, problem solved.  Happy New Year!
From: Andrew Butenko @.>
Sent: Wednesday, January 12, 2022 9:55 AM
To: AndrewButenko/UltimateWorkflowToolkit @.>
Cc: acraigx @.>; Author @.>
Subject: Re: [AndrewButenko/UltimateWorkflowToolkit] UWT: Annotation:Convert File stopped working (Issue #45)
Hello,
There is no paid version of UWT. I'm talking about Cloud Conver API that is used behind the scenes.
https://cloudconvert.com/pricing
Andrew
—
Reply to this email directly, view it on GitHubhttps://github.com/AndrewButenko/UltimateWorkflowToolkit/issues/45#issuecomment-1011127212, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABWJ2QEPJK3YEDUJSSVDWCTUVWI3HANCNFSM5LXJEARQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

I spoke too soon.  So I revisited the CloudConvert site, paid for more time and still I get the following error.  The strange thing is that when I changed the API in the solution’s configuration screen from an old API key to a new one I noticed that the length of the key expanded 10 fold.  Probably not an issue but noteworthy.
The remote server returned an error: (403) Forbidden.
Plugin Trace:
[UltimateWorkflowToolkit.CoreOperations: UltimateWorkflowToolkit.CoreOperations.Annotation.ConvertFile]
[UWT: Annotation: Convert File]
Value of 'Resulting File Name' attribute equals to 36346 UCO Collection Manifest.pdf
Value of 'Replace Original File' attribute equals to False
Value of 'Record Reference' attribute equals to https://thirdcoastcommodities.crm.dynamics.com:443/main.aspx?etc=10235&id=048d0cc1-d0ab-4d7f-8424-524cd809863c&histKey=218807458&newWindow=true&pagetype=entityrecord
Value of 'Current File Name' attribute equals to UCO Collection Manifest.docx
Value of 'Throw an Exception on Error' attribute equals to True
Error Message:
Exception type: Microsoft.Crm.CrmException
Message: The remote server returned an error: (403) Forbidden.
at Microsoft.Xrm.RemotePlugin.Client.Interceptors.SandboxFabricClientTelemetryInterceptor.<>c__DisplayClass3_0.b__0()
at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action, IEnumerable1 additionalCustomProperties)    at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute(ILogger logger, XrmTelemetryActivityType activityType, Action action)    at Microsoft.Xrm.RemotePlugin.Client.Interceptors.SandboxFabricClientTelemetryInterceptor.Intercept(IInvocation invocation, IExecutionContext context, SandboxFabricCallTracker sandboxFabricCallTracker)    at Microsoft.Xrm.RemotePlugin.Client.Interceptors.SandboxFabricCodeUnitExecuteBaseInterceptor.Intercept(IInvocation invocation)    at Castle.DynamicProxy.AbstractInvocation.Proceed()    at Castle.Proxies.ISandboxFabricCodeUnitProxy.Execute(ILifetimeScope scope, IExecutionContext context, SandboxFabricCallTracker& sandboxFabricCallTracker)    at Microsoft.Xrm.RemotePlugin.Client.SandboxFabricPlugin.<>c__DisplayClass5_1.<Execute>b__3()    at Polly.Policy.<>c__DisplayClass150_01.b__0(Context ctx, CancellationToken ct)
at Polly.Policy.<>c__DisplayClass143_01.<ExecuteInternal>b__0(Context ctx, CancellationToken ct)    at Polly.RetrySyntax.<>c__DisplayClass12_1.<WaitAndRetry>b__1(Context ctx, CancellationToken ct)    at Polly.Retry.RetryEngine.Implementation[TResult](Func3 action, Context context, CancellationToken cancellationToken, IEnumerable1 shouldRetryExceptionPredicates, IEnumerable1 shouldRetryResultPredicates, Func1 policyStateFactory)    at Polly.RetrySyntax.<>c__DisplayClass12_0.<WaitAndRetry>b__0(Action2 action, Context context, CancellationToken cancellationToken)
at Polly.Policy.ExecuteInternal[TResult](Func3 action, Context context, CancellationToken cancellationToken)    at Polly.Policy.Execute[TResult](Func3 action, Context context, CancellationToken cancellationToken)
at Polly.Policy.Execute[TResult](Func1 action)    at Microsoft.Xrm.RemotePlugin.Client.SandboxFabricPlugin.Execute(IServiceProvider serviceProvider)    at Microsoft.Xrm.RemotePlugin.Client.ResilientSandboxPlugin.<>c__DisplayClass13_1.<Execute>b__0()    at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action, IEnumerable1 additionalCustomProperties)
at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute(ILogger logger, XrmTelemetryActivityType activityType, Action action)
at Microsoft.Xrm.RemotePlugin.Client.ResilientSandboxPlugin.Execute(IServiceProvider serviceProvider)
at Microsoft.Xrm.RemotePlugin.CrmProvider.RemotePlugin.RemotePluginExecute(IServiceProvider serviceProvider, ILifetimeScope lifetimeScope, IExecutionContext executionContext, ILogger logger)
at Microsoft.Xrm.RemotePlugin.CrmProvider.RemotePlugin.Execute(IServiceProvider serviceProvider)
at Microsoft.Crm.Workflow.Services.ProxyCustomActivity.Execute(CodeActivityContext executionContext)
-- End stack trace --
From: Andrew Craig Cross
Sent: Wednesday, January 12, 2022 11:48 AM
To: AndrewButenko/UltimateWorkflowToolkit @.>; AndrewButenko/UltimateWorkflowToolkit @.>
Subject: RE: [AndrewButenko/UltimateWorkflowToolkit] UWT: Annotation:Convert File stopped working (Issue #45)
Thank you – I had completely forgotten about this aspect, problem solved.  Happy New Year!
From: Andrew Butenko<EMAIL_ADDRESS>Sent: Wednesday, January 12, 2022 9:55 AM
To: AndrewButenko/UltimateWorkflowToolkit<EMAIL_ADDRESS>Cc: acraigx<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [AndrewButenko/UltimateWorkflowToolkit] UWT: Annotation:Convert File stopped working (Issue #45)
Hello,
There is no paid version of UWT. I'm talking about Cloud Conver API that is used behind the scenes.
https://cloudconvert.com/pricing
Andrew
—
Reply to this email directly, view it on GitHubhttps://github.com/AndrewButenko/UltimateWorkflowToolkit/issues/45#issuecomment-1011127212, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABWJ2QEPJK3YEDUJSSVDWCTUVWI3HANCNFSM5LXJEARQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


update go assets

Description
Follow up to #29 with updated go assets

For contributor use:

[x] Targeted PR against main branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the standards mentioned here.
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.88%. Comparing base (38f7bcf) to head (99ce71b).
Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #30   +/-   ##
=======================================
  Coverage   81.88%   81.88%
=======================================
  Files           5        5
  Lines         254      254
=======================================
  Hits          208      208
  Misses         46       46

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


Add support for Live++ on Windows

The editor, compile, run iteration times when working on Godot engine or (custom) modules is quite high, ranging from 10-30 seconds on quite capable hardware. This makes working on C++ code less effective than it could be. Also, debug builds take a long time to start up, which further increases the time spent waiting for things to happen before new or fixed code can be evaluated.
Live++ is a proprietary tool for Windows that can help with this by allowing hot swapping code into a running executable like the Godot editor or a Godot game.
This pull request adds support for Live++ to Godot on Windows. It modifies the following files as follows:

platform/windows/detect.py checks if the LIVEPP_PATH environment variable is set, pointing to the Live++ installation, e.g. to c:/tools/LivePP. If set, the build sets a CPPDEFINE and an additional linker flag that adds a trampline area to functions, so Live++ can do its work.
platform/windows/godot_windows.cpp will include the Live++ header, and setup and tear-down Live++ when the LIVEPP_PATH define is set.
platform/windows/os_windows.cpp also evaluates the LIVEPP_PATH define and calls into the Live++ sync point when set. This allows Live++ to swap out any recompiled functions.

I've created a demonstration video to show the improved workflow. Note the first 30 seconds of the video. That's the time it takes on this machine (while screen recording) to make a single line change, rebuild, and restart the Godot editor. Subsequently, code is changed, saved, and handed to Live++ for patching.
https://www.youtube.com/watch?v=2y8s7KZ1R3g&feature=youtu.be
I understand that adding calls to proprietary APIs is not something Godot will do. The reason for this pull request is more informal, so people looking to integrate Live++ with Godot have a starting point.
It might be possible to turn this functionality into a module or native extension. In this pull request's case, deeper integration was chosen, so Live++ can start-up as soon as possible, which is recommended as per the documentation.

Fixed error found by formatting check.

The VS project generator also needs to know about the livepp option. Otherwise the resulting build commands will rebuild Godot without Live++ support. Fixed in latest push.

RCC++ might be an option, too - https://github.com/RuntimeCompiledCPlusPlus/RuntimeCompiledCPlusPlus

Do you think ihttps://github.com/fungos/cr is compatible with your feature set?
Like replace live++ with cr?

Latest merged Updated please @badlogic


knowing when the PDF has finished to generate

Hi,
I have a file system watcher that watch a folder. When a file is detected, I read the file and I convert it into PDF with phantom-html-to-pdf.
My concern is when too many files is handled, Phantomsjs crashs.
I would like tell at phantomjs to  manage a maximum 20 files for exemple. Is it possible?
Or would you advise me how I can make this without this error?
Thanks

hi @rich25200 , if you are experimenting problems with the maximum amount of files that phantomjs can process just implement a basic limit in your code:
// pseudo-code
var currentFilesProcessing = 0;
var MAX_CONCURRENT_FILES = 5;
var pendingFiles = [];

dir.on('watch', function (file) {
  pendingFiles.push(file);
});

setInterval(function () {
  if (currentFilesProcessing >= MAX_CONCURRENT_FILES || pendingFiles.length === 0) {
    return;
  }

  currentFilesProcessing++;

  startConversion(pendingFiles.shift(), function () {
    currentFilesProcessing--;
  });
}, 3000);

function startConversion(file, cb) {
  // ..use phantom-html-to-pdf here..
}

i'm afraid i can't help you more here, i'm going to close the issue since this is not a problem related with the library.


Update: Update supporting svg symbol sizes

This will include SVG symbol size 200

LGTM :see_no_evil:

LGTM

Current coverage is 100% (diff: 100%)

Merging #261 into master will not change coverage

@@           master   #261   diff @@
====================================
  Files          25     25
  Lines         299    299
  Methods        48     48
  Messages        0      0
  Branches       42     42
====================================
  Hits          299    299
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 957f6ba...ff513fb

merging :rocket:


Make Vive emulation just pause the trackers relative to the world.

With the new IK update in VRChat, occluded trackers now pause instead of doing dead reckoning/flying away. Vive emulation thus needs to be adjusted to just randomly pause in place instead of flying away.

VRChat added a slider to keep tracker motion prediction, so I think we should keep it like it is currently (more funny anyways)


Unable to run repo

Hi,
I'm trying to run this repo after forking but unable to do so.
I have tried the steps mentioned in the Readme file..
When I do yarn , I get the following error:

I'm not sure if this is due to yarn itself or something else.
I have also attached the debug log
npm-debug.txt
.

Looks like the rm come isn't working on Windows. I may just need to update rm to a Windows compatible command.

This npm run-script storybook works in Windows.
But once webpack starts building I get

module not not found error
for react-table.css at line no. 9  in .storybook/config.js.

On removing this line import '../react-table.css', webpack builds successfully and I can run open localhost but without styling for the react-table.css

Before you run the storybook, you'll want to watch (yarn run watch:css) or build (yarn run build:css) the styles.  Then the storybook should work just fine.

Closing for now. If you still have issues, reopen.

@tannerlinsley Would like to reopen this issue and want to submit a PR for this.

@tannerlinsley Thanks. Submitted a PR (#124)
rm -rf doesnn't work on Windows. Hence updated it with rimraf package.


[testing-helpers] Allow to inject wrapper element in fixture

Currently there's no way to customize the creation of wrapper element used as parent to the template.
A use case is testing an element that uses the dependency injection technique described by Polymer dev here and here. It relies on a parent element that listen to an event dispatched in the connectedCallback
An actual example of testing is here. app-header element depends on a context provided by a parent element. Currently there's no way to properly test it.
This is something i can work if approved

a context would need to be put onto a dom element right?
so how about something like this?
const wrapper = await fixture(html`
  <my-context .data=${...}>
    <div>
       <my-el></my-el>
    </div>
  </my-context>
`;

const el = wrapper.querySelector('my-el');

as far as I can see such a context system should not require a special way of testing? do you have some more context what would not work that way?)
also as far as I know such a system based on events will not work on IE11 😭

my-el would be empty ( not rendered ) because fixture waits only for top level elements AFAIK

I think the fixture should await all the elements in the fixture, that would make it more flexible. We could even (optionally) do andeep await of all children including in shadow dom

I think It should be optional both because performance and because many times you dont want the content of inner components (kind of implementation detail)

As a user you create the fixture and therefore you should also know if the element needs some more time then the default...
this could mean to await a next frame or a timeout or adding an extra fooComplete (which could be a promiseall of all child's updateComplete)
or by making the updateComplete of you class to include all it's children (lit element has some docs on how to adjust your updateComplete) this would mean the fixture would await it automatically (but might not be doable or practical)
imho doing any of the above sounds like a better solution then to add an extra sync wrapper around

by making the updateComplete of you class to include all it's children

Changing the implementation of the component (with complexity increase and performance penalty) just to allow testing does not sound good

Even considering the above, context provider elements does not deals with children rendering at all

As a user you create the fixture and therefore you should also know if the element needs some more time then the default...

Yes, the solution is to await the rendering for the child element like below:
const wrapper = await fixture(html`
  <my-context .data=${...}>
       <my-el></my-el>
  </my-context>
`;

const el = wrapper.querySelector('my-el');
await el.updateComplete

With the following caveats

adds yet more boilerplate and the whole reason of testing-helpers is to avoid them
it makes harder to visualize what component you are testing. Compare with the below:

const el = await fixture(html`<my-el></my-el>`, { parent: contextEl });

Finally, the code required to implement the ability to define the the wrapper/parent is moving one line in one place (the remaining code just pass options argument down the call stack).
Its less than the required code to implement one test case with the proposed solution

Yeah I dont think changing production code is the right solution, but I really feel that the wrapper should be an implementation detail of the test fixture.
I think the test fixture should await updateComplete (and equivalents of other libs) of all light dom elements, that will fix your situation.
The options object could accept a selector to select the element to return.

I think the test fixture should await updateComplete (and equivalents of other libs) of all light dom elements, that will fix your situation.

I think this should be opt-in because: 1) will break existing tests 2) can slowdown the tests potentially
Regarding the original issue, i'd be using my version for now.
Anyway thanks for all work.

We would just be querying the light dom elements, not the shadow dom elements. So there are no implementation details that we are accessing here.

So there are no implementation details that we are accessing here.

By implementation detail i mean the rendered html tree from the child element.
Say i have an element 'my-form' which renders to DOM (no shadow DOM) ten inputs and i'm testing 'my-el' that have one 'my-form`' element:
const el = await fixture(html`<my-el></my-el>`);
expect(el).to.match.snapshot()

I would expect the following snapshot output (as is today):
<my-el><my-form></my-form></my-el>

If is enabled by default, the output would be
<my-el><my-form><input/><input/><input/><input/><input/><input/>...</my-form></my-el>

So basically, i'm saying i dont care what 'my-form' is rendering i just want to know that i'm rendering an 'my-form' element

If you're not using shadow dom you are leaking implementation details by design, but you're right this does create a change in behavior assuming that both my-el and my-form render async and their timing is consistent.
We may be able to render to a template or document fragment first and check which elements were actually in the fixture, but it gets pretty messy.
Another approach could be to allow setting specific data attributes on elements which need to be awaited.

Allowing setting the wrapper element does seem like a simple solution as well given the complexities. @daKmoR what do you think?


Support youtube link to mp3

I'd like to make this support youtube link to mp3 snippet. Should be pretty straightforward to add

this is basically done with 49413d4 - should clean up the code / readme as a followup

this is doen


AvailabilityParser marks iOSApplicationExtension, unavailable-annotated properties as universally deprecated

Description
When generating our SDK docs with DocC, classes marked as unavailable in Application Extensions are marked as deprecated in the generated docs.

Steps To Reproduce
Generated DocC page for PaymentSheet.FlowController
Class definition for PaymentSheet.FlowController
If we define our class:
@available(iOSApplicationExtension, unavailable)
@available(macCatalystApplicationExtension, unavailable)
public class MyClass: NSObject { }

The Swift compiler will output this in the symbol graph JSON:
"availability":[{"domain":"macCatalystAppExtension","isUnconditionallyUnavailable":true},{"domain":"iOSAppExtension","isUnconditionallyUnavailable":true}]

And Swift-DocC will mark it as deprecated in the docs data JSON:
{"deprecated":true,"role":"symbol","title":"MyClass","fragments":[...]}

I think the issue is that the AvailabilityParser marks a symbol as deprecated if every Availability entry for a symbol is marked as isUnconditionallyUnavailable, even if the symbol is implicitly available in other domains. This final check seems incorrect:
        // Check if the symbol is unconditionally deprecated
        return availability.availability
            .allSatisfy { $0.isUnconditionallyDeprecated || $0.isUnconditionallyUnavailable || $0.deprecatedVersion != nil }

DocC already checks if a "universal deprecation" exists (a deprecation where domain == nil) just above that line, though I think it should also check if the domain is *.
Checklist

[ ] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior
DocC marks it as available, or maybe marks it as "not available in Application Extensions".
Actual behavior
DocC marks the iOSApplicationExtension-unavailable class as Deprecated with a strikethrough effect.

Swift-DocC Version Information
Bundled in Xcode 14.1
Swift Compiler Version Information
swift-driver version: 1.62.15 Apple Swift version 5.7.1 (swiftlang-<IP_ADDRESS>.3 clang-14<IP_ADDRESS>)
Target: arm64-apple-macosx13.0

First of all, thank you for submitting such a detailed bug report.
There is a few thing I'd like to confirm:

Did you make "Expected Behavior" and "Actual behavior" swapped by mistake?
In "Swift-DocC Version Information", did you mean bundled in "Xcode 13.1"?

A strange case I observe is that if you specify your class like SwiftUI's way, swift-doc will not mark it as deprecated 🤔.
@available(macOS 10.15, *)
@available(iOS, unavailable)
@available(tvOS, unavailable)
@available(watchOS, unavailable)
public class MyClass: NSObject { }

Before we fix the issue, in your specific issue, you can workaround by using the following code snippet:
@available(iOSApplicationExtension, unavailable)
@available(iOS 13.0, *) // Or whatever version you like
public class MyClass: NSObject { }

First of all, thank you for submitting such a detailed bug report.
There is a few thing I'd like to confirm:

Did you make "Expected Behavior" and "Actual behavior" swapped by mistake?

Ah, yep! 🤦 Let me fix that.

In "Swift-DocC Version Information", did you mean bundled in "Xcode 13.1"?

Sorry, typo, I meant 14.1 (Build 14B47b).

Before we fix the issue, in your specific issue, you can workaround by using the following code snippet:

Thanks, we'll try that! And thanks for the quick fix!

Fixed by #712


Assert that sample apps work with the latest builders

What happened?

What were you attempting to do?
I was trying to confirm that the set of samples provided in this repo can be built with the current builders.

What did you expect to happen?
I expected that there would be a set of tests that I could run to confirm this.

What was the actual behavior? Please provide log output, if possible.
There are no tests, and so I need to try to confirm this in an ad-hoc manner.

Checklist

[ ] I have included log output.
[ ] The log output includes an error message.
[ ] I have included steps for reproduction.

Testing ca-certificates will be done in issue #70.


Component Icon

Icon Request

Icon name: Component
Use case: Creating a component/displaying that something is a component.
Screenshots of similar icons:

https://www.figma.com/file/fSM8zuFMb8zk9oUPp1GQBI/Component-Icon?node-id=0%3A1

Nice idea!
I think this nice addition.
If you want to submit the icon you self. Please read the Icon design guide to make sure everything in line with the other icons

also maybe a more literal name (for the possible future naming guidelines), e.g squares or something like that

<svg
  xmlns="http://www.w3.org/2000/svg"
  width="24"
  height="24"
  viewBox="0 0 24 24"
  fill="none"
  stroke="currentColor"
  stroke-width="2"
  stroke-linecap="round"
  stroke-linejoin="round"
>
  <path d="M5.5 8.5L9 12L5.5 15.5L2 12L5.5 8.5Z"/>
  <path d="M12 2L15.5 5.5L12 9L8.5 5.5L12 2Z"/>
  <path d="M18.5 8.5L22 12L18.5 15.5L15 12L18.5 8.5Z"/>
  <path d="M12 15L15.5 18.5L12 22L8.5 18.5L12 15Z"/>
</svg>

I think this more or less abides by all of the design guides, apart from the 2px rounded corners, which should be okay, since e.g. layout grid also does not have rounded corners: https://lucide.dev/icon/layout-grid

maybe pixel perfect is better, to make sure it's well rendered everywhere

@karsa-mistmere @delnyn I'm fine with both of them.
Maybe post a 100% of it, and also place it side by side with other icons. Can we compare and choose.

Here's the 100% view. Truth be told, I don't think either work amazingly well. 😅

Yeah, I guess so too, the blurriness is a bit uneven between inner and outer sides, but it's not that horrible (and definitely has a visual weight that's much more consistent with the other icons). PR coming up soon.


oci-image-tool: more verbose output

As per https://docs.google.com/document/d/1bsi9JCnmOMSZCDh3VmDCO1m17w1aNexX09naomcpUOs/edit the oci-image-tool should have more verbose output, more concretely:
Print ...

[ ] the digests of objects
[ ] the version of the spec tested against
[ ] canonical mimetypes and alternative
[ ] the version of the validator code
[ ] a list of tests that were ran
[ ] a list of errors

I did implement the last point ("a list of errors") actually already, so I am wondering what additional requirements are needed here.
/cc @philips

@s-urbaniak If there's anything I can help with this please let me know

@runcom thanks for the help! Sure, just go ahead, I'll try tackle each of those in parallel with other rkt work. Just let me know if you want to tackle all of them or just a subset. Seem like low-hanging fruits to me.

@runcom  If you just tackle a subnet of them, I'd like to help with the rest

@s-urbaniak If it need to be done based on #159 ?
It refactor the image tool completely. If we did before it is merged, we may be meet a big conflict.

On Tue, Aug 30, 2016 at 07:11:01PM -0700, xiekeyang wrote:

@s-urbaniak If it need to be done based on #159 ?
It refactor the image tool completely. If we did before it is
merged, we may be meet a big conflict.

I'm all for avoiding conflicts, but #159 tries to stay away from the
existing image-validation logic.  So I expect you can wade into these issues without butting heads with #159.
My long-term plan was to land #159 and then rewrite the
validation/unpacking logic to use callback registries.  Something
like:
type Validator(ctx context.Context, engine cas.Engine, ref specs.Descriptor, recursive bool) (errors []string)
var Validaters map[string]Validator {
"application/vnd.oci.descriptor.v1+json": ValidateDescriptor,
"application/vnd.oci.image.manifest.v1+json": ValidateManifest,
"application/vnd.oci.image.manifest.list.v1+json": ValidateManifestList,
…
}
But I don't have any work in progress on that front, so there won't be
any conflicts if validation shifts around in the meantime ;).

This issue was moved to opencontainers/image-tools#22


Question: How to embed hand-written C-files as part of the build

To get decent graphics performance out of Nvidia / AMD graphics cards on laptops (e.g. due to the "Nvidia Optimus" tech), it is necessary to specify some specially named constants as part of one of the C/C++ source files that get compiled into the final binary.
For example, you'd need a .c file with contents like:
/* "build_scripts/extras/highperf_gfx_hints_constants.c" */

#ifdef WIN32
  extern "C" {
    _declspec(dllexport) DWORD NvOptimusEnablement = 0x00000001;
  }
#endif

How do I write a plugin that will tell scons to treat this file just like another one of the ".c" files that Nuitka generates for each of the Python modules it encounters (i.e. it should be compiled by gcc/msvc/etc., and then included in the "link_input.txt" list of object files to be linked into the final .exe)?

Plugins have a couple of methods to overload. These are
    def getPreprocessorSymbols(self):
        """Decide which C defines to be used in compilation.

        Notes:
            The plugins can each contribute, but are hopefully using
            a namespace for their defines.

        Returns:
            None for no defines, otherwise dictionary of key to be
            defined, and non-None values if any, i.e. no "-Dkey" only
        """

        # Virtual method, pylint: disable=no-self-use
        return None

    def getExtraIncludeDirectories(self):
        """Decide which extra directories to use for C includes in compilation.

        Returns:
            List of directories or None by default
        """

        # Virtual method, pylint: disable=no-self-use
        return None

    def getExtraCodeFiles(self):
        """Add extra code files to the compilation.

        Notes:
            This is generally a bad idea to use unless you absolutely
            know what you are doing.

        Returns:
            None for no extra codes, otherwise dictionary of key to be
            filename, and value to be source code.
        """

        # Virtual method, pylint: disable=no-self-use
        return None

    def getExtraLinkLibraries(self):
        """Decide which link library should be added.

        Notes:
            Names provided multiple times, e.g. by multiple plugins are
            only added once.

        Returns:
            None for no extra link library, otherwise the name as a **str**
            or an iterable of names of link libraries.
        """

        # Virtual method, pylint: disable=no-self-use
        return None

    def getExtraLinkDirectories(self):
        """Decide which link directories should be added.

        Notes:
            Directories provided multiple times, e.g. by multiple plugins are
            only added once.

        Returns:
            None for no extra link directory, otherwise the name as a **str**
            or an iterable of names of link directories.
        """

        # Virtual method, pylint: disable=no-self-use
        return None

@Maxwell175 i guess nuitka-python can just have it set, there seem to be more flags that are performance relevant: AmdPowerXpressRequestHighPerformance too

@kayhayen it is not a good idea to force every Nuitka application in the world to use a laptop descrete GPU. Only things that actually need to be running on a descrete GPU should be. There is no reason to run every Qt window on anything but the low power GPU.

Is there anythere a list of all of these kinds of toggles?

@Maxwell175 now that we have options in the Yaml config, maybe for OpenGL in Qt, and PyOpenGL at least. can you propose something for the yaml format we have to cover these acceleration flags there?

@kayhayen Perhaps if we want to make this really generic, maybe just the ability to specify an entire extra C code file as a multiline string.

No, I am thinking more of given it a name and attach it to modules, and then give a warning if the new option is not used. In terms of implementation, I am fine with this being done in MainProgram.c simply when the option is on, or not.

@kayhayen Then just a flag like RecommendHighPerformanceGPU


Add FastAPI integration

Let’s build a FastAPI (python) integration. :)
https://fastapi.tiangolo.com/#interactive-api-docs

in progress!
https://github.com/tiangolo/fastapi/pull/10674


Minecraft Logo and images not loading in 1.12.2

Minecraft images don't want to load in the lastest versions of Minecraft 1.12.2. The resources folder isn't recognized by the mod. :/

Do you have Resource Loader installed?

It took me 5 times but I finally got it to recognize the resources folder


[Frontend] Add print for supported features

Supported features were never actually added to
-emit-supported-features, add them.

@swift-ci please test

@swift-ci please test

@swift-ci please test


EH debugging: use a better name for the launch config's preLaunchTask

(from a gitter question)
Currently the generated launch.json for the "hello world" extension uses a "preLaunchTask" named "npm" which confuses users, because they think that this is the raw "npm" command.
But this "npm" refers to the "npm" task configured in the task.json.
Only after understanding this connection it becomes clear what this "npm" really means:
    // we run the custom script "compile" as defined in package.json
    "args": ["run", "compile", "--loglevel", "silent"],

I suggest that we rename the "npm" task to something more expressive like "compileAndWatch".

Moved to https://github.com/Microsoft/vscode-generator-code/issues/83


opam install async fails on debian 9

Hey :) The following error occurs  while I'm trying to install async with opam on a stable debian. I tried the same in the ocaml/opam docker container and it works perfectly there, so it may be something debian specific.
The following actions will be performed:
  ∗  install async_kernel     v0.9.0          [required by async]
  ∗  install async_unix       v0.9.0          [required by async]
  ∗  install async_rpc_kernel v0.9.0          [required by async_extra]
  ∗  install async_extra      v0.9.0          [required by async]
  ∗  install async            v0.9.0
===== ∗  5 =====
Do you want to continue ? [Y/n] y

=-=- Gathering sources =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[async] Archive in cache
[async_extra] Archive in cache
[async_kernel] Archive in cache
[async_rpc_kernel] Archive in cache
[async_unix] Archive in cache

=-=- Processing actions -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[ERROR] The compilation of async_kernel failed at "jbuilder build -p async_kernel -j 4".

#=== ERROR while installing async_kernel.v0.9.0 ===============================#
# opam-version 1.2.2
# os           linux
# command      jbuilder build -p async_kernel -j 4
# path         /home/wojtek/.opam/4.05.0/build/async_kernel.v0.9.0
# compiler     4.05.0
# exit-code    1
# env-file     /home/wojtek/.opam/4.05.0/build/async_kernel.v0.9.0/async_kernel-15945-c61e7b.env
# stdout-file  /home/wojtek/.opam/4.05.0/build/async_kernel.v0.9.0/async_kernel-15945-c61e7b.out
# stderr-file  /home/wojtek/.opam/4.05.0/build/async_kernel.v0.9.0/async_kernel-15945-c61e7b.err
### stderr ###
# [...]
# /usr/bin/ld: /home/wojtek/.opam/4.05.0/lib/ocaml/libasmrun.a(finalise.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
# /usr/bin/ld: /home/wojtek/.opam/4.05.0/lib/ocaml/libasmrun.a(custom.o): relocation R_X86_64_32 against symbol `caml_custom_table' can not be used when making a shared object; recompile with -fPIC
# /usr/bin/ld: /home/wojtek/.opam/4.05.0/lib/ocaml/libasmrun.a(globroots.o): relocation R_X86_64_32 against symbol `caml_global_roots' can not be used when making a shared object; recompile with -fPIC
# /usr/bin/ld: /home/wojtek/.opam/4.05.0/lib/ocaml/libasmrun.a(backtrace.o): relocation R_X86_64_32 against symbol `caml_backtrace_last_exn' can not be used when making a shared object; recompile with -fPIC
# /usr/bin/ld: /home/wojtek/.opam/4.05.0/lib/ocaml/libasmrun.a(spacetime_snapshot.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC
# /usr/bin/ld: /home/wojtek/.opam/4.05.0/lib/ocaml/libasmrun.a(startup.o): relocation R_X86_64_32S against symbol `caml_data_segments' can not be used when making a shared object; recompile with -fPIC
# /usr/bin/ld: final link failed: Nonrepresentable section on output
# collect2: error: ld returned 1 exit status
# File "caml_startup", line 1:
# Error: Error during linking

=-=- Error report -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The following actions were aborted
  ∗  install async            v0.9.0
  ∗  install async_extra      v0.9.0
  ∗  install async_rpc_kernel v0.9.0
  ∗  install async_unix       v0.9.0
The following actions failed
  ∗  install async_kernel v0.9.0
No changes have been performed

@wklm Can you please post the output of gcc -v and the contents of the file /home/wojtek/.opam/4.05.0/lib/ocaml/caml/m.h?

@mshinwell I'm sorry for bothering you, after reinstalling ocaml and opam everything works great, I am no longer able to reproduce the problem. Sorry and many thanks for maintaining this lib.
cheers,
Wojtek


Support OUDSM environments

Add support for OUDSM respectively weblogic environment. Alias, variables etc.

soe@gaia:~/local/dev/oudbase/build/ [ic12201] docker exec -u oracle -it oudsm bash --login
WARN : Could not load OUD list from /u00/app/oracle/local/etc/oudtab
WARN : Fallback to ${OUD_DATA}/*/OUD
ERROR: OUD Instance  does not exits in /u01/instances

Not really fancy when no OUD is configured....

extend Support for OUDSM for oud_up and oud_status.  The current solution does Keep OUDSM as well other Domains under ../domains/...


Unable to write coverage report to /sdcard on Firebase Test Lab emulator

Does anybody else has problem with writing coverage report to /sdcard ?
I see such stacktrace
1-08 12:50:36.434: E/CoverageListener(7255): Failed to generate Emma/JaCoCo coverage.
11-08 12:50:36.434: E/CoverageListener(7255): java.lang.reflect.InvocationTargetException
11-08 12:50:36.434: E/CoverageListener(7255): 	at java.lang.reflect.Method.invoke(Native Method)
11-08 12:50:36.434: E/CoverageListener(7255): 	at androidx.test.internal.runner.listener.CoverageListener.generateCoverageReport(CoverageListener.java:101)
11-08 12:50:36.434: E/CoverageListener(7255): 	at androidx.test.internal.runner.listener.CoverageListener.instrumentationRunFinished(CoverageListener.java:70)
11-08 12:50:36.434: E/CoverageListener(7255): 	at androidx.test.internal.runner.TestExecutor.reportRunEnded(TestExecutor.java:92)
11-08 12:50:36.434: E/CoverageListener(7255): 	at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:65)
11-08 12:50:36.434: E/CoverageListener(7255): 	at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:392)
11-08 12:50:36.434: E/CoverageListener(7255): 	at {stripped_package_name}.test.MockInstrumentationRunner.onStart(MockInstrumentationRunner.java:98)
11-08 12:50:36.434: E/CoverageListener(7255): 	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2145)
11-08 12:50:36.434: E/CoverageListener(7255): Caused by: java.io.FileNotFoundException: /sdcard/tempDir/{stripped_test_name}ec (No such file or directory)
11-08 12:50:36.434: E/CoverageListener(7255): 	at java.io.FileOutputStream.open0(Native Method)
11-08 12:50:36.434: E/CoverageListener(7255): 	at java.io.FileOutputStream.open(FileOutputStream.java:308)
11-08 12:50:36.434: E/CoverageListener(7255): 	at java.io.FileOutputStream.<init>(FileOutputStream.java:238)
11-08 12:50:36.434: E/CoverageListener(7255): 	at com.vladium.emma.rt.RT.dumpCoverageData(RT.java:50)
11-08 12:50:36.434: E/CoverageListener(7255): 	... 8 more

I've tried both
coverageFilePath"     : /sdcard/tempDir/
and
coverageFilePath"     : /sdcard/
there is the same Exception thrown.
Since it's a permission denied I tried
coverageFilePath: /sdcard/Android/data/{packageName}/
And the report was written for only last test. Orchestrator cleans up this directory before each test.
both app and test app apk have
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />

Are you using grant permission rule?

Also see "Android code coverage" in the Flank readme.
Try gcloud CLI to see if that has the same problem. I don't think this issue is a Flank bug. Configuring your app to generate coverage with orchestrator is a bit complex.R
If gcloud CLI has the same issue, feel free to ask in the #test-lab channel on Slack.

It turned to be problem with Runtime Permissions.
I made update to documentation https://github.com/TestArmada/flank/pull/617


Load fileCache on Windows. Fixes #775

Backslashes needed to be unescaped, otherwise the file would not be found in the cache later on.
Fixes #775

This change is

Reviewed 1 of 1 files at r1.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable


Annotation import adds 'default' style

When importing a .json defining annotation styles the "default" style group is automatically added. The checkbox to overwrite existing styles has no effect on this.
Desired behavior - if the "default" style does not exist in the .json, don't create it.

+1: Default style is not needed and confuses the pathologists. We cannot remove it.


Add Ollama Support

Add Support for Ollama
Hey team,
First off, I want to say I’m a big fan of this repo and can't wait to see more of it. I’ve added support for Ollama, which simplifies prototyping on macOS for us GPU/API poor people. Since the OpenAI spec is marked as experimental and subject to change, I opted for a straightforward HTTP client implementation that aligns with your existing parameters.
Overview of Changes

Refactored openai_utils.py into a new module: tinytroupe.clients.
Moved default parameters and config objects into a new tinytroupe/clients/config.py.
Moved client registry into tinytroupe/clients/__init__.py.

Usage Instructions
To get it running, execute the following in your terminal:
ollama pull Gemma-2-Ataraxy-v2-9B-2:latest
ollama serve

Change your config.ini file to reflect
API_TYPE=ollama
MODEL=Gemma-2-Ataraxy-v2-9B-2:latest #Best on leaderboard today https://eqbench.com/creative_writing.html
MAX_TOKENS=8192

Set the API key to
export OPENAI_API_KEY="ollama"

The implementation works well overall, but I’ve noticed occasional JSON parsing failures when retrieving cognitive_state. For example, the issue commonly occurs here:
@repeat_on_error(retries=5, exceptions=[KeyError])
        def aux_act_once():
            role, content = self._produce_message()

            self.episodic_memory.store({'role': role, 'content': content, 'simulation_timestamp': self.iso_datetime()})
            cognitive_state = content["cognitive_state"]

I think maybe we could add guidanceor lm-format-enforcer to help reduce it so you're also not wasting money on API calls to keep retrying due to badly formatted json. We may even be able to get the prompt size down. Let me know if that sounds interesting to you.
Also, in the config.ini you specified MAX_TOKENS=4000, is that related to the agents or content length accepted by the model? The docs  are showing it can be 16384
Cheers,
Paul

@microsoft-github-policy-service agree

either ollama, azure or openai clients require the set_api_cache method, which is not implemented in the Ollama client

Oh, this is very interesting. I'll need to take some time to review it though, as these are substantial changes, so please give us some more time.

This is a great addition to the project. I was about to write something very similar for myself.
Would really appreciate if @paulosalem could give us a time line to merge this.
Looking forward to play around with this on my local computer

@P3GLEG Ollama now support Pydantic Json generators so we don't need to integrate this with guidance or any format enforcer.
I'd be glad to assist and implement the necessary changes to define the Pydantic class to define the general output structure of the models.

@P3GLEG I admittedly did not spent much time with your implementation, but wouldn't it make sense to use https://github.com/andrewyng/aisuite for unifying the LLM calls?


Status

Hi,
I am wondering of the status of the project.
There is currently no documentation, and there have been no commits for a long while...so please take no offence.
Edit: If it is in a proper working state outside the lack of commits, yes I am prepared to help out to improve the situation.

I've actually had a lot of luck using standard LDAP libraries to connect to Active Directory with straight Python. I've been keeping an eye on this project, but in the meantime, I've been using:
git+https://github.com/rbarrois/python-ldap.git@py3
and more recently, also with django-python3-ldap:
https://github.com/cannatag/ldap3

I am not using the library anymore as I changed jobs and we don't use LDAP here. Still, if someone is interested in contributing and maintaining the project I am more then willing to add them full access.

@FlipperPA:
Thanks for your reply, for some reason I haven't seen that until now.
@ssbarnea :
Ok, not now, but I will get back if this becomes relevant again.


feat: add AES encryption key generator

closes #66

Thanks for the PR @dracarys18. Just wondering, transmitting encryption keys that people may use in production, over plaintext UDP, is that a good idea? :cold_face:

Perhaps we can have something like DNS over TLS

Adding HTTP/TLS + DNS defies the purpose of dns.toys though. For that, it's then just easier to setup an HTTP/TLS service that can just be curl'd.

Oh that makes sense! I guess we hit the wall here, Shall I close the PR then?

Yep, I think we should close this. While the PR on its own is perfectly fine, we shouldn't set the precedent of users copy-pasting and using encryption keys transmitted over an unencrypted channel.


ssh:// prefix missing in 1.21.1

Description
I recently upgraded from 1.19 to 1.21.1 and discovered that ssh:// prefix is missing from the clone address section in the web UI. I do not see a setting in app.ini where i would be able to specify or add the prefix, only the ability to change the SSH_DOMAIN.
Screenshots

Gitea Version
1.21.1
Can you reproduce the bug on the Gitea demo site?
Yes
Operating System
No response
Browser Version
Firefox 120

I think it's by design.

->  Improve SSH clone URL generation behavior #28421
As a workaround, you can set [repository].USE_COMPAT_SSH_URI = true in your app.ini to use the full SSH clone URL.

After more thoughts, I would like to keep the old behavior of the SSH clone URL generation in  #28421
Could you show your app.ini? Then we could know how git@domain:port:user/repo.git happened.

I am good setting the USE_COMPAT_SSH_URL to true, I just didn't know it was an option. My app.ini is the standard one with just the URL and SSH_DOMAIN  values modified ( and soon to also include the USE_COMPAT_SSH_URL)).
Thank you all for your help and attention, I will close this one.


Update generator documentation to show non-deprecated examples

Hello,
Supervisor.Spec was deprecated in Elixir v1.5.
Would be cool to update the docs to suggest the new behavior.
There is two ways to add the broker into our application supervision tree:

Map based specification
Module based supervisors

The following code shows the difference:
Current way (deprecated)
Also, add your broker to the supervision hierarchy in your example.ex:

    def start(_type, _args) do
      children = [
        # ...
        supervisor(Example.Broker, [])
      ]

      supervise(children, strategy: :one_for_one)
    end

New way (Map based specification)
Also, add your broker to the supervision hierarchy in your example.ex:

    def start(_type, _args) do
      children = [
        # ...
	    %{
	      id: Example.Broker,
	      start: {Example.Broker, :start_link, []}
	    }
      ]

      supervise(children, strategy: :one_for_one)
    end

Thanks, I'd love a contribution if you're interested. The broker implements child_spec, so the example should be simpler.
children = [
  {Example.Broker, []}
]

Supervisor.init(children, strategy: :one_for_one)

I'd like to make this change.
I'm not aware if you want to support older Elixir versions so I thought on generate the example showing both specs.
Something like this:
Also, add your broker to the supervision hierarchy in your conduit.ex:

Elixir v1.4 or below:

    def start(_type, _args) do
      children = [
        # ...
        supervisor(ConduitQueue.Broker, [])
      ]

      supervise(children, strategy: :one_for_one)
    end

Elixir v1.5 or above:

    def start(_type, _args) do
      children = [
        # ...
        {ConduitQueue.Broker, []}
      ]

      supervise(children, strategy: :one_for_one)
    end

I'm going to open two PR's, one showing newest example and one containing both, ok?


Incorrect external linking on some cards

The external links on two cards do not link correctly. It appears that if you don't have the https:// at the beginning of the URL it is trying to go to https://scrollodex.netlify.app/your-entered-link.com instead of just your-entered-link.com
Cards with issues:

Rachel Thomas @rachael-t
Chay McCormick @chay-chay

hi, can I work on this issue, please?

Hi all,
I’m working on the issue.
Best,
Chay
On Wed, Oct 20, 2021 at 5:21 PM Judit Pacsai @.***>
wrote:

hi, can I work on this issue, please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wwcodecolorado/scrollodex/issues/66#issuecomment-948045833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARLXVCKTPV7JTNILTEA5FQDUH4XENANCNFSM5GMMFGIQ
.


Rough notes as basis for initial dev guidelines

Captures notes in other tickets, intended to be updated/cleaned up based on further discussions.

Let's merge this in and I'll update it according to my comments later.

Yep that was the idea 👍


white headerBackground in v 0.11.14

Ask your Question

i update from 0.11.11 because in some android device it is so slow. It feel faster in 0.11.14 but the header is not in primary color.
Here is the screenshot in android :

And this is the repro :
https://snack.expo.dev/@7marrch/react-native-paper-dates-headerbackground
thank you in advance

The color of the container corresponds to the surface attribute in the theme and is that way so that it adheres to the MD3 date picker.


Compaction tasks fails with index_parallel task type but passes when task type is index

Affected Version
The Druid version where the problem was encountered.
0.19.0
Description
Compaction tasks fails for a specific datasource and specific interval with index_parallel task type but passes when task type is index
we have a specific datasource and for a specific interval (MONTH)
compaction tasks are submitted as index_parallel task. It started failing with all subtasks not showing any log in druid ui and 404 status.
for testing we submitted the same compaction task (for same datasource and interval)with index type and it passed with out any error.
To add to the above, we manually validated the existence of SegmentIDs(from compaction task spec generated by sruid) in the Druid metadata table to rule out presences of non-existent segment in the single_phase_sub_task compaction spec generated by Druid. And all the segments were found

Hi, Thanks for raising the issue. Could you please share the spec for which the compaction task is failing?


destroy dom elements created by detected3d()

detect3d() created elements should be destroyed after function completion

#9


[DOCFIX] Update Chinese document docs/cn/Overview.md to make it more native

Change
阿里巴巴, Alluxio, 百度,
卡内基梅隆大学,Google，IBM，Intel,
南京大学,
Red Hat，UC Berkeley和
to
阿里巴巴、Alluxio、百度、
卡内基梅隆大学、Google、IBM、Intel、
南京大学、
Red Hat、UC Berkeley和

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/898/
Test PASSed.


Roblox

Hello Sensai,
Can you please make this tool for Roblox, when game crash/frozen, close game and enter game?
kind regard.

It's currently not possible for the macro to determine whether the game has crashed or is simply stuck in a waiting state. One way to handle this would be to create a dedicated macro specifically for this purpose, or to try to force quit the game by simulating keyboard events if there is no response after repeatedly clicking a particular button on the screen.

Thanks for reply

this is how it looks when crashed, fps to 0.0

Would you like to capture a screenshot of the frame with 0.0 in the top right corner using a macro, and then try setting it up by moving events?


[BEAM-13229] [Website]

add refresh method to scrollspy on language-switch.js and page-nav.js

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @nausharipov

Can one of the admins verify this patch?

Can one of the admins verify this patch?

We have cherry-picked and squashed commits from this branch into the new branch: https://github.com/apache/beam/pull/17731


Exactly Once V2

Description
For now, Streamiz only support old EOS V1, which means 1 producer per Task.
This issue track EOS V2 with 1 producer per thread which reduce the resources and increase the performance, reduce broker costs and activity.

Plan for 1.7.0


Github Action to check if every commit compiles

Fixes #616
Adds test workflow that checks if every commit in a PR compiles correctly
Implement's @s1ntaxe770r's solution

Forgot to sign off on my commits again 😅

Hi @achrefbensaad , do you mean that we should test commits on pkg/**controllers only?

Hi @Chinwendu20 ,
I meant that we should implement the same logic for controllers changes. as currently we check only for changes under KubeAemor/** .
It would be great if we also check that the controller are compilablle on each commit (if the commit affect them).
I meant by pkg/**controllers pkg/KubeArmorHostPolicy pkg/KubeArmorPolicy and KubeArmorAnnotation .

Let's not run the CI only on main as we need to detect the problem before it reached the main branch.

I didn't understand, can you explain more?

@Ankurk99 , I miss read the ci file. I thought it will only run when merged to main, but in fact it will run for each pull request that targets main.
@AllMight2099 , Please ignore point 1.

Thanks a lot @achrefbensaad. Can I implement the change you suggested a this PR is not assigned to me

Hi @achrefbensaad, I'm still working on the issue, just became a little sick so I was unable to work on it for a bit. Sorry about that

Hi @Chinwendu20 , I'm still working on the issue, just became a little sick so I was unable to work on it for a bit. Sorry about that

@achrefbensaad will do. I'll implement it and push my changes

Hey @AllMight2099! Hope you are doing good, would you be making the requested changes to the PR?

Yup, I'mma push it in a couple of minutes

@Ankurk99 @achrefbensaad I tried using a matrix that keeps a track of changes to the controller and spins up multiple jobs if changes are made to one or more controllers under pkg

@Ankurk99 @achrefbensaad Really sorry, could you review this again, I realized that the action wasn't running and saw that the action would only run if a PR was made, and not if commits were pushed to the PR

@achrefbensaad I think this workflow will need some testing even after the PR is merged, so would recommend closing it only after release v0.6 is done.

@AllMight2099 , can you please rebase your PR and squad your commits to one commit, it will make it easier to test.


Echo not having the same health as duplicated target (OW1 Ult)

When using her ult you don’t receive as much health as the target.

Did echo get full hp in ow1 during copy? I honestly don't remember

She did it was changed to be like how it is now in the OW2 Beta.


[FEATURE]: [Worldpay] Use connector_response_reference_id as reference to merchant

:memo: Feature Description

Reference id are used to map transactions in the connector’s dashboard.
Hyperswitch manages several reference ids, such as payment_id, attempt_id, and connector_transaction_id for a single transaction.
However, merchants may encounter uncertainty when determining which ID to utilize in the connector dashboard to identify the payment.

:hammer: Possible Implementation

When we receive a response from the connector for the payment, we deserialize it and populate the response field in RouterData.
For the TransactionResponse type, we must fill the connector_response_reference_id with a corresponding reference id for the merchant to identify the transaction.
One might need to have exposure to api docs of the connector for which it is being implemented to decide what to fill in connector_response_reference_id.
You can check this PR for further reference https://github.com/juspay/hyperswitch/pull/1735

🔖 Note: All the changes needed should be contained within hyperswitch/crates/router/src/connector/
:package: Have you spent some time checking if this feature request has been raised before?

[X] I checked and didn't find a similar issue

:package: Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

:sparkles: Are you willing to submit a PR?

😊 "I'd be delighted to work on this issue! Could you please assign it to me?"

Hey @TechWizard9999 , sure! I've assigned this to you.
In case you have any queries, you can ask them on this issue thread, or on our discord server, or on slack whichever you are comfortable with

@AkshayaFoiger  I am unable to Find the folder with world pay is it named as Global pay

@AkshayaFoiger I just want to work on this issue! Is it going to be alright if I send a PR or after you assign that to me?

Hello @imSanko,
This issue has already been assigned to @TechWizard9999. However, we have encountered similar issues with different connectors. I would suggest considering an attempt to address one of those.

i want to work on this issue could you please assign me to this issue

Hi @himanshuParashar0101,
This issue has already been assigned to @imSanko. However, we have encountered similar issues with different connectors. I would suggest considering an attempt to address one of these issues.

Hey @TechWizard9999 ,
Let us know if you face any issues. Happy to help! : )

Hey @TechWizard9999 ,
Just checking in - are you working on it or shall we consider reassigning it to someone else?

Can I work on this one if @TechWizard9999 is not currently work on this?

Hey @speedhs  , sure! I've assigned this to you.
In case you have any queries, you can ask them on this issue thread, or on our discord server, or on slack whichever you are comfortable with.

Hey! i went throught the file. I wanted to ask on thing. In the files attached for reference the customer response field is stored in a different way than that for worldpay. Can you clarify on the fields used in response.rs for worldpay?

Hello @speedhs, can be more specific about the "files attached for reference", might be able to help you out better. Anyways, if you are talking about how we are handling the response i.e. the try_from implementation for the response. To simplify it, We take the response from the connector, parsing it, and then convert it into suitable struct for our core to handle the response.  You need to look into what parameters are present while parsing(related struct in response.rs) and which one of those can be used as connector_response_reference_id. (In case such parameter is not present, create on the basis of docs) Hope this helps

Hey @speedhs ,
Are you still working on this issue?
Please let us know if you need any help.

@Sakilmostak @VedantKhairnar @AkshayaFoiger @gorakhnathy7
I would like to work on this issue, Can you assign this to me.

Hey @nabeel001 There is another issue assigned to you, let me know if you want to work on this one instead.

Hi @lsampras @gorakhnathy7 @apoorvdixit88 @Sakilmostak @swangi-kumari ,
I would like to help on this. All my other issues are done, just waiting for code review and merging.

hey @gorakhnathy7 , I have completed the other assigned issue and hence can I take this up now

Sure @nabeel001

@gorakhnathy7 @Sakilmostak
I believe this issue is already been resolved through this PR #6374
https://github.com/juspay/hyperswitch/pull/6374/files#diff-44c4bc1c958aca2577f1238edc431080c039354b65e707ea9bc38618ba3ca665
Line: 488


Allow naming of JSObject method implementations.

Currently any method implementation in a JSObject ends up with an indeterminately generated name in the javascript. It would be useful to specify method identifiers so that when they are transformed to javascript they can be called and used in external javascript code.
I'm not sure whether this already exists and just requires documentation, there appears to be an @Export annotation but this is only for web-assembly.

No, currently there's no solution for this problem. There's one workaround: you can define your own subtype of JSObject like this:
public interface MyExportedObject extends JSObject {
    void foo();
}

And implement it by a regular Java class:
public class ExportedImpl implements MyExportedObject {
    @Override
    public void foo() {
        System.out.println("It works");
    }
}

Now, if you instantiate this class and pass the instance to a JavaScript function, it will be able to call foo method.
This approach does not work for static methods though.
Can you clarify your desired use case? What problem you are going to solve?

That does solve it to some degree. I have a couple of use cases, one is to pass an object defined in Java as the handler in a javascript Proxy. This requires certain methods to be defined that get called by the Proxy wrapper so it would be a bit easier to specify that the name should be used as is rather than needing to create an interface to use first.
The other case is where I want to create objects to be used as a library so it needs to have a defined interface that someone can call.


Edit securityContact swagger for 2020-01-01

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

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

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No, no need to refresh for updates in this PR

Contribution checklist:

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

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

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

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

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

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[x] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

This swagger has not been published yet.
Added another response code to PUT operation and change the name to meet the new capability (from "Create" to "Create Or Update")
Appreciate your approval :)

hi @msyyc could you pls help confirm impact to Python SDK?
hi @ArcturusZhang could you pls help confirm impact to Go SDK?

hi @msyyc could you pls help confirm impact to Python SDK?
hi @ArcturusZhang could you pls help confirm impact to Go SDK?

hi @msyyc Yuchao Yan FTE could you pls help confirm impact to Python SDK?
hi @ArcturusZhang Dapeng Zhang FTE could you pls help confirm impact to Go SDK?

It's ok for python

hi @msyyc Yuchao Yan FTE could you pls help confirm impact to Python SDK?
hi @ArcturusZhang Dapeng Zhang FTE could you pls help confirm impact to Go SDK?

It's ok for python

Go breaking changes are not introduced in this PR

Go breaking changes are not introduced in this PR

communicated with @ovedti over teams, this breaking change is necessary for the team. @ovedti is going through the process

communicated with @ovedti over teams, this breaking change is necessary for the team. @ovedti is going through the process

communicated with @ovedti over teams, this breaking change is necessary for the team. @ovedti is going through the process

Thanks! I created an ADO, waiting for their response 👍

communicated with @ovedti over teams, this breaking change is necessary for the team. @ovedti is going through the process

Thanks! I created an ADO, waiting for their response 👍

unfortunately, adding new statuscode to existing version is also breakingchange :(

unfortunately, adding new statuscode to existing version is also breakingchange :(

hi @msyyc Yuchao Yan FTE could you pls help confirm impact to Python SDK?
hi @ArcturusZhang Dapeng Zhang FTE could you pls help confirm impact to Go SDK?

It's ok for python

HI @ArcturusZhang @msyyc sorry the PR has new commit, which adding a new param to create call https://github.com/Azure/azure-rest-api-specs/pull/12265/files#diff-60a32dc7bc6d8e143ae6ecf7ab442860ae7666a2e0038ade276cf85d7bee3036R136. Could you pls re-evaluate impact to Go and Python SDKs? thanks

hi @msyyc Yuchao Yan FTE could you pls help confirm impact to Python SDK?
hi @ArcturusZhang Dapeng Zhang FTE could you pls help confirm impact to Go SDK?

It's ok for python

HI @ArcturusZhang @msyyc sorry the PR has new commit, which adding a new param to create call https://github.com/Azure/azure-rest-api-specs/pull/12265/files#diff-60a32dc7bc6d8e143ae6ecf7ab442860ae7666a2e0038ade276cf85d7bee3036R136. Could you pls re-evaluate impact to Go and Python SDKs? thanks

hi @msyyc @ArcturusZhang could you pls confirm impact to Python and GO SDK? thanks

@yungezz this PR does not introduce breaking changes to go SDK

Yuchao Yan
Hi, any updates regarding Python SDK?
Appreciate your feedback :)

This PR is ok for Python


[develop] WIP: New User Profile & Topics feature

@devformatters closed since it's stagnant too long.


Change PyG Data Notebook Root from Google Colab

Change PyG data notebook root so it is not Google Colab root

Done


Why not use javapoet to create class file

I suggest that you can use javapoet to create a class file instead of writing byte stream in a class file by self

I don't see a benefit here. What justifies the work of migrating all that code to javapoet? -ut


fix workflow visualization with non existing parent environment

Fixes
https://issues.redhat.com/browse/HACBS-1061
Description

Handle Workflow visualization with environments that has parentEnvironment set to a non-existing environment name.
Type of change

[x] Bugfix

Screen shots / Gifs for design review

Before:

After:

How to test or reproduce?

Create an Environment in an application with invalid parentEnvironment name
apiVersion: appstudio.redhat.com/v1alpha1
kind: Environment
metadata:
  name: poc
spec:
  type: poc
  deploymentController: appstudio
  deploymentStrategy: Manual
  displayName: Test Environment
  parentEnvironment: non-existing-environment
  tags:
    - test
  clusterCredentials:
    apiServerURL: http://example.com/prod
  configuration:
    env:
      - name: env
        value: test

Browser conformance:

[x] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

/assign @christianvogt

works well, but only in cases of a mid-size screen, the viz clips out on the right, without any indicator. Not sure whether related to this bug

/lgtm
ran locally. e2e

dagre layout works this way, you need to click on fit to screen or zoom out to see the full graph

/lgtm

/approve


Edge Functions is mistakenly identified as Serverless Functions after being packaged by rollup.

Edge Functions is mistakenly identified as Serverless Functions after being packaged by rollup.
// api/hello.ts or api/hello.js

export const config = {
  runtime: 'experimental-edge',
};

export default (req) =>
  new Response(`Hello, from ${req.url} I'm now an Edge Function!`);

For example, if I want to use the remote module of the http protocol, I need to package it with rollup.
// api/hello.ts or api/hello.js

export const config = {
  runtime: 'experimental-edge',
};

export {bb as default }

const bb=(req) =>
  new Response(`Hello, from ${req.url} I'm now an Edge Function!`);

An external configuration file should be used to determine if it is edge function.
// api/hello.ts or api/hello.js

export {aa as config}

const aa = {
  runtime: 'experimental-edge',
};

export default (req) =>
  new Response(`Hello, from ${req.url} I'm now an Edge Function!`);

https://vercel.com/docs/concepts/functions/edge-functions