Better Marshalling of WinRT Types in Win32 Methods

At the moment,  methods with WinRT types are generated like this:
	 [DllImport("CoreMessaging.dll", ExactSpelling = true)] 		[DefaultDllImportSearchPaths(DllImportSearchPath.System32)] 		internal static extern winmdroot.Foundation.HRESULT CreateDispatcherQueueController(winmdroot.System.WinRT.DispatcherQueueOptions options, [MarshalAs(UnmanagedType.CustomMarshaler,MarshalCookie = "Windows.System.DispatcherQueueController",MarshalType = "Windows.Win32.CsWin32.InteropServices.WinRTCustomMarshaler")] out global::Windows.System.DispatcherQueueController dispatcherQueueController);
Where WinRTCustomMarashaler is a piece of generated code that uses reflection and MethodInfo.invoke.
Surely, it would be more efficient to do something like this:
     [DllImport("CoreMessaging.dll", ExactSpelling = true)]     [DefaultDllImportSearchPaths(DllImportSearchPath.System32)]     private static extern Windows.Win32.Foundation.HRESULT CreateDispatcherQueueController(         DispatcherQueueOptions options, out nint dispatcherQueueController);
    public static Windows.Win32.Foundation.HRESULT CreateDispatcherQueueController(         DispatcherQueueOptions options, out DispatcherQueueController? dispatcherQueueController) {         var result = CreateDispatcherQueueController(options, out nint dispatcherQueueControllerNative);         dispatcherQueueController = result.Succeeded             ? DispatcherQueueController.FromAbi(dispatcherQueueControllerNative)             : null;         return result;     }
The main difference is that for each type there is a FromAbi static method that can be called. Given that the type is known at code generation time surely that is more efficient.

Please excuse the formatting.

@smj389 use triple backticks for better formatting. Add cs after them for colorization.


⚗✨♻ Support bundled transforms

What do these changes do?
This PR implements

loading pre-processing transforms from the config file (using monai.bundle)
implements loading yml (and json) config files
adds tests to check/understand behavior of bundle.ConfigParser
removes save_nifti branch during training, i.e. automatic predicting based on validation data
default pre-processing/augmentation now moves data to GPU after CropForegroundd

Related issue/s

#34
#31

How to test

Checklist

[x] Non-breaking change (fix or new feature that would not break existing functionality).
[x] Breaking change (fix or new feature that would cause existing functionality to change).
[x] Unit tests for the changes and run locally with the command pytest tests
[x] Documentation reflects the changes

Thanks @pcrespov for your review!


[Bug]  ERROR :"UNSUPPORTED_OPERATION","operation":"getAddress"

EVM Bug on the back-end blocks repayments and TWAPs.
May 21 14:31:08 bots-server start.sh[189172]: executeWithdraw(withdraws) []
May 21 14:31:10 bots-server start.sh[189172]: processWithdrawEvents(withdrawn_events)
May 21 14:31:11 bots-server start.sh[189172]: getNextBotArgs {"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}
May 21 14:31:11 bots-server start.sh[189172]: {"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}
May 21 14:31:11 bots-server start.sh[189172]: cycleDeposits [{"id":830,"deposit_id":0,"token0":"0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2","token1":"0xf939e0a03fb07f59a7331>
May 21 14:31:11 bots-server start.sh[189172]: Health updated successfully.
May 21 14:31:11 bots-server start.sh[189172]: id health health_threshold:  830 4549.993063435179 200

@taariq @rootedbox If you share the backend code where this issue is appearing, I will confirm it.

@jamie088 the issue is also referenced here with links to the code: https://github.com/VolumeFi/paloma/issues/1393#issuecomment-2121374350

@taariq @rootedbox I checked why this issue occurs on the server and it is from when init the crvusd (from curvefi npm) in the backend code.
In this line:
      "JsonRpc",
      { url: NODE },
      { gasPrice: 0, maxFeePerGas: 0, maxPriorityFeePerGas: 0, chainId: 1 }
    );```

It has nothing to do with FE, I am curretnly thinking 3 solutions.

- [ ] First, we need to upgrade the curvefi npm package version in all backend repos. This also resolves the `multicall` issue that was previously happening.

@curvefi/api: `2.53.6` -> `2.58.10`
@curvefi/stablecoin-api: `1.5.2` -> `1.5.3`
I already confirmed these versions on FE and no issue so far.

- [ ] Second, if the above solution is not correct, we should check with the curve team that the curvefi API works on node backend server. In curve doc example, say only in FE(react)

- [ ] Third, check the rpc endpoint
backend is using `liquify` rpc url on eth
frontend is using `quiknode` rpc url but no issue.

@jamie088 Thanks for this write-up.
To Reflect:
This is a back-end library and RPC endpoint issue.

Upgrade libraries
Curve team on node
RPC endpoint (why is this an issue?)

NOTE: front is not supposed to be using Quicknode. All production need to be on Liquify. Quicknode is emergency backup only.

@jamie088 @taariq @verabehr I've upgraded the libraries on all twaps.. updated the server and restarted all services. I'm not seeing any getAddress at this time.. so should probably put this on a wait and see for now.

moving to blocked until we see this again or it's been a week.

This is still happening. Last observed on the curve-healthy-bot on May 28

Errors today:
{"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}
May 29 18:41:29 bots-server start.sh[1369661]: {"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}
May 29 18:41:31 bots-server start.sh[1369661]: processWithdrawEvents(withdrawn_events)
May 29 18:41:31 bots-server start.sh[1369661]: getNextBotArgs {"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}
May 29 18:41:31 bots-server start.sh[1369661]: {"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}
May 29 18:41:32 bots-server start.sh[1369661]: processWithdrawEvents(withdrawn_events)
May 29 18:41:32 bots-server start.sh[1369661]: cycleDeposits []
May 29 18:41:32 bots-server start.sh[1369661]: executeWithdraw(withdraws) []
May 29 18:41:33 bots-server start.sh[1369661]: processWithdrawEvents(withdrawn_events)
May 29 18:41:34 bots-server start.sh[1369661]: getNextBotArgs {"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}
May 29 18:41:34 bots-server start.sh[1369661]: {"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}
May 29 18:41:34 bots-server start.sh[1369661]: processWithdrawEvents(withdrawn_events)
May 29 18:41:34 bots-server start.sh[1369661]: cycleDeposits []
May 29 18:41:34 bots-server start.sh[1369661]: executeWithdraw(withdraws) []
May 29 18:41:36 bots-server start.sh[1369661]: processWithdrawEvents(withdrawn_events)
May 29 18:41:36 bots-server start.sh[1369661]: {"data":null}
May 29 18:41:37 bots-server start.sh[1369661]: getNextBotArgs {"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}
May 29 18:41:37 bots-server start.sh[1369661]: {"reason":"unknown account #0","code":"UNSUPPORTED_OPERATION","operation":"getAddress"}

The endpoint was the culprit. Need to confirm and check all bot services that need to be upgraded.

[ ] llmalend
[ ] limit-order-bot-v3
[ ] curve-dca-bot-service (curve TWAP)
[ ] curve-leverage-lending-bot
[ ] curve-squeeze-leverage-bot
[ ] curve-healthy-bot

all service endpoints updated and servers restarted


upgrade to java11 + maven

Last years I upgraded platinum to Java11 + updated maven builds as 'reference' example. Would be nice to merge it with the NLeSC repository...


Serialization for deferred_transaction_request

In libraries/chain/include/eosio/chain/contracts/abi_serializer.hpp
template<typename Resolver, typename... Args>
      static void add( mutable_variant_object &mvo, const char* name, const fc::static_variant<Args...>& v, Resolver resolver )
      {
         //TODO: implement deserialization for static_variant
      }

There should be serialization code for either static_variant in general or for fc::static_variant<deferred_transaction, deferred_reference> which we use in apply_context.hpp.

@moskvanaft is this done?

I see implementation in the code.


Update dependencies 2024/03

This PR completes most open dependency updates, most notably removing the pin on pandas < 2.2.0.
Two notes:

It doesn't bump httpx to 0.27 yet because that introduces a DeprecationWarning in an upstream dependency. Starlette already has a release resolving this issue (v0.37), but fastpi still pins starlette to below this version. Thus, I think it's fine if we keep from updating httpx just yet.
I'm not happy with my current workaround for an upcoming pandas deprecation. In two places in the code, I've seen the same DeprecationWarning:

/home/fridolin/ixmp4/ixmp4/data/db/meta/repository.py:175: DeprecationWarning: DataFrameGroupBy.apply operated on the grouping columns. This behavior is deprecated, and in a future version of pandas the grouping columns will be excluded from the operation. Either pass `include_groups=False` to exclude the groupings or explicitly select the grouping columns after groupby to silence this warning.
    return df.groupby("type").apply(map_value_column)

So I started tinkering with the options, but I couldn't figure out how to successfully select the grouping columns so that apply works on them. groupby(as_index=False, ...) doesn't seem to have an effect, which might suggest that pandas is treating our apply call as a transformation in the background. Simply including apply.(include_groups=False, ...) resulted in an error that the 'type' column was missing from the dataframe. Finally, I came across this suggestion: https://stackoverflow.com/a/78100669/23037943 (see in particular the first reply). The suggested workaround copies the column we want to groupby and then group(s)by the copied column, thus leaving the original open to be passed to apply as usual. Of course, this is temporarily creating extra data columns which we don't need, so it very much feels like there should be a better solution hiding somewhere. @meksor and @danielhuppmann, please let me know if you have any idea.
Apart from this, we probably want to release 0.7.4 after merging this PR to resolve the issue @phackstock had downstream.
FYI @pmussak

Thanks a lot for the quick fix @glatterf42 👍

Hello I removed the copied columns and put them back in each map function. From my side this looks good and can be merged!

Has something changed from my last comment 3d ago?

Yes, we now support some older versions, i.e. several dependencies are now not as strict as they used to be.

Also, I removed essentially all upper version bounds.

Ah I see, well if the tests pass its fine with me, but then daniels suggestion for nightly builds seems even more salient now!

But we can do that in another PR :)


Where to put a function to trigger on exit/stop/close event of flutter/dart application using Desktop Shell?

I have a simple greeter gRPC example server code written in go and exported as C library that I'm trying to run with a flutter app using go-flutter desktop engine via ffi and dart Isolates.
I have made a StopGrpc() function, which works if I call it to stop gRPC server.
But if I don't manually first trigger the StopGrpc() function before exiting the application I keep getting the following waiting for isolates _startGrpc to check in which never ends, and I have to force quit the application.
An Observatory debugger and profiler on Flutter test device is available at: http://<IP_ADDRESS>:50300/
go-flutter: closing application
Attempt:11 waiting for isolate _startGrpc to check in
Attempt:12 waiting for isolate _startGrpc to check in

Steps to Reproduce

install Hover from here: https://github.com/go-flutter-desktop/hover#install

git clone https://github.com/satindergrewal/flutter-practice/
cd flutter-practice/flutter_isolates/
hover run -v

Hit play floating button at bottom to start gRPC server service in background.
Close application using title bar close button.
You'll start getting Attempt:11 waiting for isolate _startGrpc to check in and unable to close the application.

Here's the full copy of lib/main.dart file for reference:
https://github.com/satindergrewal/flutter-practice/blob/master/flutter_isolates/lib/main.dart
If I first trigger StopGrpc() to stop gRPC server by first pressing the stop floating button at bottom, and then close the application, the application exits without any issue.
Normal exit looks like this in debug console:
An Observatory debugger and profiler on Flutter test device is available at: http://<IP_ADDRESS>:50300/
Greet function was invoked with greeting:<first_name:"Satinder" last_name:"Grewal" >
flutter: done!
go-flutter: closing application
Lost connection to device.
hover: App 'flutter_isolates' exited.
hover: Closing the flutter attach sub process..

So, I need to know where to put StopGrpc() function to trigger on application close/exit action.
Can someone please tell me how can I trigger a function to stop the server when exiting the application?
This is the go-grpc code that I'm compiling for this go-flutter application as a C library:
https://github.com/satindergrewal/flutter-practice/blob/master/go_dart_ffi_c_shared/greet/greet_server/server.go
And this is the flutter code that I'm using to test flutter Isolates: https://github.com/satindergrewal/flutter-practice/tree/master/flutter_isolates
I have already asked for help from go-flutter and they pointed me to ask in flutter/flutter help channels. Here's the github issue for reference:
https://github.com/go-flutter-desktop/go-flutter/issues/489#issuecomment-655604583
Also asked this issue on StackOverflow, for which I tried different ideas to solve this issue, but those seems to be specific to mobile, and and did not work with Desktop Shell or using flutter-go based Desktop shell. For reference here's the link:
https://stackoverflow.com/questions/62800770/where-to-put-a-function-to-trigger-on-exit-stop-close-event-of-flutter-dart-appl/62808897
Tried dispose() and didChangeAppLifecycleState() as per the example/help from https://medium.com/flutter-community/build-a-lifecycle-manager-to-manage-your-services-b9c928d3aed7
pushed this code update in this git commit: https://github.com/satindergrewal/flutter-practice/compare/5e4704ff8cad...c18e15dcc9b8
Same behaviour as before. No change. :(
Here's the video of showing LifeCycleState does not print anything on app exit/close:
https://youtu.be/MZjpzAvTBoc
And this one shows the actual problem:
https://youtu.be/rYXoVDAKBqg
Would really appreciate help on it.
Thanks,
Satinder
Expected results:

Start the application to the step where gRPC server service is started in background using Isolates.
Click on the close button in title bar of to exit/quit/close the application.
Trigger the stopGrpc() function upon this closing application event to stop the background running gRPC server service, and wait till it stops, and then complete the exit process.

Logs
With gRPC server service start, and then stopped using floating button, application exits without issue
➜  flutter_isolates git:(master) hover run -v
06:12:38 build.go:335: hover: Building flutter bundle
Font subetting is not supported in debug mode. The --tree-shake-icons flag will be ignored.
06:12:49 cache.go:229: hover: Using engine from cache
06:12:49 version.go:59: hover: Checking available release on Github
06:12:50 version.go:126: hover: The core library 'go-flutter' has an update available. (v0.41.1 -> 0.41.2)
06:12:50 version.go:127: hover:               To update 'go-flutter' in this project run: `hover bumpversion`
06:12:50 version.go:59: hover: Checking available release on Github
06:12:50 build.go:450: hover: Compiling 'go-flutter' and plugins
06:12:50 build.go:456: hover: Successfully compiled executable binary for darwin
06:12:50 run.go:82: hover: Build finished, starting app...
06:12:50 run.go:126: hover: Running flutter_isolates in debug mode
go-flutter: WARNING error creating the resource window: VersionUnavailable: NSGL: Failed to create OpenGL context
[ERROR:flutter/shell/platform/embedder/embedder_surface_gl.cc(107)] Could not create a resource context for async texture uploads. Expect degraded performance. Set a valid make_resource_current callback on FlutterOpenGLRendererConfig.
[ERROR:flutter/shell/platform/embedder/embedder_surface_gl.cc(107)] Could not create a resource context for async texture uploads. Expect degraded performance. Set a valid make_resource_current callback on FlutterOpenGLRendererConfig.
flutter: Observatory listening on http://<IP_ADDRESS>:50300/
06:12:53 run.go:114: hover: Connecting hover to 'flutter_isolates' for hot reload
Waiting for Flutter test device to report its views...               7ms
Syncing files to device Flutter test device...
 6,436ms (!)

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h Repeat this help message.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).
An Observatory debugger and profiler on Flutter test device is available at: http://<IP_ADDRESS>:50300/
flutter: RECEIVED: Started gRPC server...
Hello world
Greet function was invoked with greeting:<first_name:"Satinder" last_name:"Grewal" >
flutter: done!
go-flutter: closing application
Lost connection to device.
06:14:42 run.go:138: hover: App 'flutter_isolates' exited.
06:14:42 run.go:139: hover: Closing the flutter attach sub process..

With gRPC server start with floating button, but not stopped, and closing the application:
➜  flutter_isolates git:(master) hover run -v
06:32:32 build.go:335: hover: Building flutter bundle
Font subetting is not supported in debug mode. The --tree-shake-icons flag will be ignored.
06:32:43 cache.go:229: hover: Using engine from cache
06:32:43 build.go:450: hover: Compiling 'go-flutter' and plugins
06:32:44 build.go:456: hover: Successfully compiled executable binary for darwin
06:32:44 run.go:82: hover: Build finished, starting app...
06:32:44 run.go:126: hover: Running flutter_isolates in debug mode
go-flutter: WARNING error creating the resource window: VersionUnavailable: NSGL: Failed to create OpenGL context
[ERROR:flutter/shell/platform/embedder/embedder_surface_gl.cc(107)] Could not create a resource context for async texture uploads. Expect degraded performance. Set a valid make_resource_current callback on FlutterOpenGLRendererConfig.
[ERROR:flutter/shell/platform/embedder/embedder_surface_gl.cc(107)] Could not create a resource context for async texture uploads. Expect degraded performance. Set a valid make_resource_current callback on FlutterOpenGLRendererConfig.
flutter: Observatory listening on http://<IP_ADDRESS>:50300/
06:32:46 run.go:114: hover: Connecting hover to 'flutter_isolates' for hot reload
flutter: RECEIVED: Started gRPC server...
Hello world
Waiting for Flutter test device to report its views...               8ms
Syncing files to device Flutter test device...
 6,876ms (!)

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h Repeat this help message.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).
An Observatory debugger and profiler on Flutter test device is available at: http://<IP_ADDRESS>:50300/
flutter: done!
flutter: RECEIVED: Started gRPC server...
Hello world
go-flutter: closing application
Attempt:11 waiting for isolate _startGrpc to check in
Attempt:12 waiting for isolate _startGrpc to check in
Attempt:13 waiting for isolate _startGrpc to check in
Attempt:14 waiting for isolate _startGrpc to check in
Attempt:15 waiting for isolate _startGrpc to check in
Attempt:16 waiting for isolate _startGrpc to check in
Attempt:17 waiting for isolate _startGrpc to check in
Attempt:18 waiting for isolate _startGrpc to check in
Attempt:19 waiting for isolate _startGrpc to check in
06:33:29 run.go:135: hover: App 'flutter_isolates' exited with error: signal: terminated
Lost connection to device.
➜  flutter_isolates git:(master)

➜  flutter_isolates git:(master) flutter analyze
Analyzing flutter_isolates...

   info • The declaration '_checkTimer' isn't referenced • lib/main.dart:60:15 • unused_element

1 issue found. (ran in 1.9s)
➜  flutter_isolates git:(master)

➜  flutter_isolates git:(master) flutter doctor -v
[✓] Flutter (Channel beta, 1.19.0-4.3.pre, on Mac OS X 10.15.5 19F101, locale en-AU)
    • Flutter version 1.19.0-4.3.pre at /Users/satinder/development/flutter
    • Framework revision 8fe7655ed2 (12 days ago), 2020-07-01 14:31:18 -0700
    • Engine revision 9a28c3bcf4
    • Dart version 2.9.0 (build 2.9.0-14.1.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/satinder/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] Connected device (2 available)
    • Web Server • web-server • web-javascript • Flutter Tools
    • Chrome     • chrome     • web-javascript • Google Chrome 83.0.4103.116

• No issues found!
➜  flutter_isolates git:(master)

➜  flutter_isolates git:(master) hover doctor -v
hover doctor -v
06:35:23 doctor.go:39: hover: Hover version v0.42.0 running on darwin
06:35:23 doctor.go:41: hover: Sharing flutter version
Flutter 1.19.0-4.3.pre • channel beta • https://github.com/flutter/flutter.git
Framework • revision 8fe7655ed2 (12 days ago) • 2020-07-01 14:31:18 -0700
Engine • revision 9a28c3bcf4
Tools • Dart 2.9.0 (build 2.9.0-14.1.beta)
06:35:26 doctor.go:51: hover: Flutter engine commit: https://github.com/flutter/engine/commit/9a28c3bcf40ce64fee61e807ee3e1395fd6bd954
06:35:27 doctor.go:63: hover: Finding out the C compiler version
Apple clang version 11.0.3 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin19.5.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
06:35:27 doctor.go:70: hover: Sharing the content of go.mod
module flutter_isolates/go

go 1.14

require (
        github.com/go-flutter-desktop/go-flutter v0.41.1
        github.com/pkg/errors v0.9.1
)
06:35:27 doctor.go:84: hover: Sharing the content of hover.yaml
application-name: ""
executable-name: ""
package-name: ""
license: ""
target: lib/main_desktop.dart
branch: ""
cache-path: ""
opengl: ""
engine-version: ""
06:35:27 doctor.go:93: hover: Sharing the content of go/cmd
go/cmd/main.go  go/cmd/options.go
➜  flutter_isolates git:(master)

I’m unable to reproduce the issue to pinpoint the cause. The issue needs further investigation.

@TahaTesser you mean you followed the "Steps to Reproduce" and closed the application without stopping gRPC server service, and couldn't reproduce the issue?
Also have video links of issue:

Here's the video of showing LifeCycleState does not print anything on app exit/close:
https://youtu.be/MZjpzAvTBoc

And this one shows the actual problem:
https://youtu.be/rYXoVDAKBqg

Can also make another video if helps explaining.

Also, note that that .so file which is being used with Isolates is compiled on MacOS, so if you tested it on other OS, it will probably won't behave the same way. I just made this test application to test my scenario, so didn't add OS specific conditions etc.
You'll need this file to compile for Windows and Linux:
https://github.com/satindergrewal/flutter-practice/blob/master/go_dart_ffi_c_shared/greet/greet_server/server.go
compile it with this command
go build -o greeter.so -buildmode=c-shared server.go

it will give two files: greeter.so and greeter.h
copy the greeter.so to the flutter_isolates and replace existing file, and then you can test the application to replicate issue.

A Dart hook that would allow you to know when the app is exiting falls under https://github.com/flutter/flutter/issues/30735; closing as a duplicate.
Note that there's no reason you (or go-flutter) couldn't write this functionality in the short term for your application using native code and method channels. The only thing that go-flutter would need Flutter support for is having a standard API already defined. (And if/when such an API is defined, go-flutter will still have to implement support for it.)


something wrong with the new version (game HOT), cannot claim.

Step 107 - An error occurred while trying to click the 'storage' link: unsupported operand type(s) for +: 'float' and 'str'
63|HOT:164 | Step 107 - Attempted to select storage again...

Hi,
Please update your games folder and restart the processes.
Thanks

I'm using Docker on Windows, how should I update?

./pull-games.sh

Will manually get the latest versions. Your daily updater must have pulled in the short times the bugged code was in the repository.
Thanks

Also, once the new code is pulled, I imagine the scripts will automatically restart.
If for whatever reason they don't, you can always use
pm2 restart all

I have restarted 1 of 2 container successfully. The 2nd container is still 100% CPU, waiting for restart all.
Thank you.
If for some reasons, the PC is restart, can I use the above commands to restart all processes or need to set up telegram from the begining?

Thanks


Warsaw Hackerspace moved to Libera

Already listed under [hackerspace.pl] -- looks like Warsaw Hackerspace is the right name. I suggest pushing a replacement commit that changes [hackerspace.pl] to [Warsaw Hackerspace]

Good catch. PTAL.

Thanks :-)


Rebuild of a solution with multiple references to the SqlClient fails with Unable to delete file "bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.dll". Access to the path 'bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.dll' is denied.

Describe the bug
We have solution with 60+ projects and 30+ of them reference Microsoft.Data.SqlClient. Rebuild from VS 2022 fails with error like:
C:\Users\<username>\.nuget\packages\microsoft.data.sqlclient.sni\5.1.1\buildTransitive\net462\Microsoft.Data.SqlClient.SNI.targets(151,5): error
 MSB3061: Unable to delete file "<solution>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.dll".
Access to the path '<solution>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.dll' is denied.

Microsoft.Data.SqlClient.SNI.targets(151,5) which is part of the SNI NuGet package looks like:
  <Target Name="CleanSNIFiles"
          Condition="'$(CleanSNIFiles)' != 'false' And
                     '$(OutDir)' != '' And
                     HasTrailingSlash('$(OutDir)') And
                     Exists('$(OutDir)')">
    <!--
        NOTE: Delete "Microsoft.Data.SqlClient.SNI.dll" and all related files, for every
              architecture that we support, from the build output directory.
    -->
    <Delete Files="@(SNIFiles -> '$(OutDir)%(RecursiveDir)%(Filename)%(Extension)')" /> -- Line 151
  </Target>

My guess is that VS 2022 runs build of multiple projects in parallel and hits race condition:

SNIFiles calculated for multiple projects at the same time as not empty
Build for one project deletes files and build from other projects fail to build as file was already deleted

I ran VS 2022 with verbose logging and see multiple places like:
11>    Target CleanSNIFiles:
11>      Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.arm64.dll".
11>      Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.arm64.pdb".
11>      Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x64.dll".
11>      Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x64.pdb".
11>      Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.dll".
11>      Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.pdb".

14>  Target CleanSNIFiles:
14>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.arm64.dll".
14>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.arm64.pdb".
14>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x64.dll".
14>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x64.pdb".
14>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.dll".
14>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.pdb".

19>  Target CleanSNIFiles:
19>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.arm64.dll".
19>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x64.dll".
19>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x64.pdb".
19>    Deleting file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.pdb".
19>    C:\Users\<username>\.nuget\packages\microsoft.data.sqlclient.sni\5.1.1\buildTransitive\net462\Microsoft.Data.SqlClient.SNI.targets(151,5): error MSB3061: Unable to delete file "<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.pdb". Access to the path '<solution path>\bin\Debug\net48\Microsoft.Data.SqlClient.SNI.x86.pdb' is denied.
19>  Done building target "CleanSNIFiles" in project "StateMachine.csproj" -- FAILED.

Notice that CleanSNIFiles executed from multiple parallel builds (11, 14, 19)
I think TreatErrorsAsWarnings="true" show solve that issue. At least it's how it's done in Microsoft.Common.CurrentVersion.targets:
    <!-- Delete those files. -->
    <Delete
        Files="@(_CleanPriorFileWritesInOutput);@(_CleanPriorFileWritesInIntermediate)"
        TreatErrorsAsWarnings="true">

      <Output TaskParameter="DeletedFiles" ItemName="_CleanPriorFileWritesDeleted"/>

    </Delete>

Expected behavior
Clean rebuild without errors.
Further technical details
Microsoft.Data.SqlClient version: 5.1.5 (tried with 5.2 and got the same error)
.NET target: net48
SQL Server version: 2022
Operating system: Windows 11

The MSB3061 error can be tricky because it’s often related to environmental issues, such as files being locked by other processes or antivirus software. Can you try forcing MSBuild to use only one thread by setting the environment variable MSBUILD_PROCESSES to 1 or by passing the -maxCpuCount:1 flag directly to MSBuild?

Can you try forcing MSBuild to use only one thread by setting the environment variable MSBUILD_PROCESSES to 1 or by passing the -maxCpuCount:1 flag directly to MSBuild?

Running it single threaded eliminates that issue, however it's huge slow down.

The MSB3061 error can be tricky because it’s often related to environmental issues, such as files being locked by other processes or antivirus software.

It observable for multiple machines and multiple developers.

@kosinsky the fix is merged in SNI package and will be available in next SNI release, v6.0-preview1.
Closing as the issue is addressed.

@JRahnama Was this issue present in older version? So we can resolve it other way than lowering paralelization to 1 or that local modification above.

@cts-tradeit I think so. The fix is the exact implementation described here, adding TreatErrorsAsWarnings="true". That does not exist in previous versions.

@JRahnama Hi, when is the new version gonna be available at least as preview on nuget org?

When the 6.0.0-preview1.24226.4 will be released as stable version? We are hitting this issue as well on our 250+projects solution.........

The current due date seems to be December 9th:
https://github.com/dotnet/SqlClient/milestone/64


Thx! Fixed.


Highlight executor args/kwargs in the docs

What should we add?
In the list of executor plugins, several of them do not have a description of the available args and kwargs to the excecutor. The Dask executor is a good example that does have them here, although they do not have docstrings and are not documented. Note that for many of these executors, we will want to highlight not just the parameters but also the default values pulled from the default config.
In testing Covalent out with some colleagues, I realized they weren't used to inspecting functions/classes for the possible input parameters and were solely relying on what was in the RTD/repo READMEs, which meant they were missing out on any args/kwargs not directly described in the docs. The docs could better reflect this, particularly since it is under the API section.

Criteria for Completion
In the documentation files for plugins inside the directory doc/source/api/executors, add the required changes needed to generate API documentation for the following plugins:

[ ] SSH
[ ] Slurm
[ ] AWS Braket
[ ] AWS Lambda
[ ] AWS EC2
[ ] AWS Batch
[ ] Google Batch

Note that the method used for one can be applied to the others.  Documentation can be built locally by following the instructions here and can be tested on ReadTheDocs using the GitHub actions provided in this repository.

@wjcunningham7  I would like to take a stab at this issue. Could you assign it to me?

@wjcunningham7 Hi there! I would like to try this issue, it would be great if you can assign me!
I have some questions, while the docs about available args and kwargs of Dask executor is generated using autoclass, I noticed SSH, Slurm, and other executors are implemented in different repos: covalent-ssh-plugin and covalent-slurm-plugin, do we need to manually write docs for these executors or use autoclass too?🤔

@ErikQQY for this issue we want to use the autoclass for the other plugins as well so that the docs remain up to date with changes in the other repositories.

Hi @wjcunningham7 can I work on this issue ?

Hey unitaryHACK participants @WingCode @ErikQQY @aryanguptaaa! Thanks for your participation! As a reminder being assigned only indicates interest. You do not need to be assigned in order to work on the issue. Only once an issue is closed by a contribution will the bounty winner be finalized.
It doesn't look like there are any attached PRs for this yet, so it's still up for grabs!

This was wrongly closed, in fact it requires merging of #1680 in order to be closed and marked as completed.


Slash in query param not being encoded as %2F

Sorry if I am way off on this as far as the http spec goes but query params containing the "/" character are not being encoded as expected. In the below example, I would expect the output to be: /?key=value1%2Fvalue2 however the output is actually /?key=value1/value2
#include <boost/url.hpp>
#include <iostream>

int main() {
	boost::urls::url url("/");
	url.params().append({"key", "value1/value2"});
	std::cout << url << std::endl;
}

What makes you think these need to be escaped? They are not ambiguous, as they are not part of the target.

To complement the answer, the only possible component after the query is a fragment. So the only delimiter after the query is a #. That's why ? and / are allowed in the query.

@vinniefalco ok makes sense. I was going off this link:
https://en.m.wikipedia.org/wiki/Percent-encoding
additionally, the AWS S3 rest API requires it:
https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html

Yes. Unreserved Characters can be used in any component, although individual components can allow more than the unreserved set. For instance:
$> node
new URL('http://www.example.com/a/s/b?f=g/s')
URL {
  href: 'http://www.example.com/a/s/b?f=g/s',
  origin: 'http://www.example.com',
  protocol: 'http:',
  username: '',
  password: '',
  host: 'www.alan.com',
  hostname: 'www.alan.com',
  port: '',
  pathname: '/a/s/b',
  search: '?f=g/s', // <--------
  searchParams: URLSearchParams { 'f' => 'g/s' },
  hash: ''
}

Whoever wrote the AWS tutorial got that wrong if it's meant as a requirement. I'd be surprised if the server rejects a request because a "/" in the query is unencoded.

@vinniefalco its not that the AWS server rejects explicitly if slashes aren’t escaped but the issue is that the authorization signature is calculated based on what they call uri-encoded query params. So if we don’t escape the slash when calculating the signature, their signature won’t match and then they reject.
Anyway, topic for another forum. Thanks for the help


When using the "Back" button in a browser, the page gets stuck at the IAF_Util tab

Current Behavior
When visiting a page with tabs where ?configuration= is missing, ?configuration=IAF_Util will be set. This will also happen when going back, breaking the build-in back button of the browser.
Expected Behavior
Going back to the previous page. (Not same URL without ?configuration=IAF_Util)
Environment Information
Local development on master
Steps To Reproduce

Go to Monitors page
Press "Back"

Configuration
No response
Input
No response
What database are you using?
No response
What browsers are you seeing the problem on?
Firefox, Chrome
Relevant Log Output
No response
Anything else?
No response

This happens because the console keeps track of the latest used tab or uses the first one when it cant find a previous state, this messes with when going back through browser history since the state isn't going back to a previous state


container_opts.go: add WithAdditionalContainerLabels

WithAdditionalContainerLabels() preserves the existing entries in c.Labels.
OTOH, WithContainerLabels() clears them.

LGTM


Fix issues #4, #10, #25, #27

I deprecate firepad-lib and implement the functions with firebase only. Thus issues and bugs caused by firepad-lib are solved. Moreover the unshare feature finally can be implemented.

So after the deprecation, how does this package resolve OT problems?


My automatic install stopped working

Gitea version (or commit ref): docker hub's gitea:latest
Operating system: docker in Ubuntu 16.04
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Description
So I've been using ansible to automatically install and configure Gitea. I build my own docker image from gitea and have an entrypoint that creates the admin if necessary.
As you can see in my docker-compose file, the INSTALL_LOCK variable is always set to true.
However, I end up on the Gitea install web page.
As you can see in my Dockerfile, I only append app_custom.ini to the original default template. This was working before (around may 30 according to my git log).
However, after starting the container, the configuration file only contains the INTERNAL_KEY.
Finally, here is my docker-entrypoint.sh. I haven't changed it since the time it worked. When it worked, it would show "Generating secret key" then start the server. Then when my CREATE_ADMIN variable was set in docker-compose.yml it would show in parallel "Creating admin user".
However, now I see only "Generating secret key" then your /usr/bin/entrypoint serves. It appears like it ignores every environment variable, and my admin generation code never runs.
I do not have any idea about where it comes from :worried:
Thank you by advance.

What's your latest work instance gitea version?

If you're asking what is the latest with which it was working, I have been trying to find it but I cannot manage to find it. The problem might come from outside of gitea (docker-compose, the s6 image, etc.), I am just not experienced enough to actually have an idea which is why I am asking the question.
If you're asking what is the latest version I tested, I am testing right now.
WUT! So today's version is 6efdcae, and I don't understand my install worked...
I have another issue but I will file it separately.
Do you have any idea what could be causing this change? I am really surprised...


[GEN-1170] Add missing profile to data guide

Purpose: Adds the missing center profile for our GOLD center. The docker image tagged at sagebionetworks/genie-data-guide:latest on dockerhub needs to be rebuilt in order for this to work on Nextflow Workflow Tower.
I don't have the permissions to push to sagebionetworks on dockerhub, but tested consortium_release on nf-genie on the rebuilt image locally and it works (data guide on test pipeline gets outputted): https://www.synapse.org/#!Synapse:syn21895009

@thomasyu888 Could you add me as admin or add @Sage-Bionetworks/genie-reviewers to have write access to the repo?

🔥 LGTM! Just a comment, but going to pre-approve. Ill leave it to you to decide whether you want to push this when processing is still happening

Good point, I'll wait for now.


[MINOR] Fix testUpdateRejectForClustering

Change Logs
There is a writing error in commitTime, which may not cause test failure here, but may cause problems in the future (we are currently developing our hudi metastore, and found this small error during our test)
Impact
none
Risk level: none | low | medium | high
none
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Test fix works. CI failure is irrelevant. Landing this.


Assign rubygem owner to Solistra

Just filing this so it will fill my github inbox until I set you as the upstream owner of the rubygem

Also, the gemspec file needs to be updated to reflect the new ownership as well (emails, etc).

I'll take the gemspec into account -- for now, I'm mostly waiting for the dust to settle before doing much work on rvpacker itself.

Closing this issue since we have successfully moved the gem ownership to you


perf(head): drop #head and #app for auto-imports

🔗 Linked issue

❓ Type of change

[x] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[x] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

For some context, Nuxt 3 was initially built to support different head providers. Initially, it was providing support for @vueuse/head and Vue meta (although there was no way to opt-in to it).
With @vueuse/head moving towards deprecation and Nuxt going all-in on Unhead, it makes sense to clean up some of the technical debt introduced in supporting multiple head providers.
This technical debt can be summarised as:

#head alias - pointed towards where the head composables where for
#app re-exporting the #head composables - allowed nuxt internally to use any head provider

With this PR we move all head composables to the auto imports. For the Nxut app internal useHead calls, we import directly from @unhead/vue.
Inadvertibly we also are adding support for the new composable useHeadSafe so I have provided doc and tests for it.
:warning: There are some very minor breaking changes here. If users imported useHead from #head or #app they will need to import from #imports. Also, we no longer export HeadAugmentations, instead, we can directly augment the Unhead schema if we want to add custom completions.
📝 Checklist

[ ] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

This is great! To reduce breaking changes, do you think we can keep an export from #app that is marked as deprecated - and likewise, for HeadAugmentations - mark it as deprecated? We can then remove both in next minor: v3.4.

I've tentatively pushed a reversion of the breaking change in favour of deprecating the exports/interface, but happy to rethink if you think this isn't sensible. 🙏


Update domains.json

Addition to domains.json for ecc.capital - empire-capital.eth

Closing this PR for now, feel free to open it again once you've done the changes.


Enum support branch

UPDATE: enum type checking is now implemented.

internally all enum values are converted to integer as soon as they are observed
there is a weird side effect now that enum literals or pvariables could be used in arithmetic expressions as integer: blocking such behaviour explicitly is possible but will probably come with a performance cost, we can discuss it later
enum-valued actions and observables should probably be returned/provided by the user as strings not integers, but for now they are integers
switch short circuit now is stupid because it only does it if the switch condition tensor has the same value throughout. an optimal short circuit strategy would run np.unique and then only evaluate the resulting case branches. however, i suspect the constant cost of np.unique might outweigh the cost of evaluating all branches in many cases, so for now we can leave it as is.

This branch is now obsolete as many changes were made in a downstream branch. Closing and reopening the correct request...


Tutorial coverage section needs update

This issue tracker is a tool to address bugs in Flask itself.
Please use the #pocoo IRC channel on freenode or Stack Overflow for general
questions about using Flask or issues not related to Flask.
If you'd like to report a bug in Flask, fill out the template below. Provide
any extra information that may be useful / related to your problem.
Ideally, create an MCVE, which helps us
understand the problem and helps check that it is not caused by something in
your code.

Expected Behavior
$ coverage run -m pytest
Name                 Stmts   Miss Branch BrPart  Cover
------------------------------------------------------
flaskr/__init__.py      22      0      2      0   100%
flaskr/auth.py          54      0     22      0   100%
flaskr/blog.py          54      0     16      0   100%
flaskr/db.py            24      0      4      0   100%
------------------------------------------------------
TOTAL                  154      0     44      0   100%

Actual Behavior
$ coverage run -m pytest
============================================================== test session starts ==============================================================
platform darwin -- Python 2.7.10, pytest-3.9.1, py-1.7.0, pluggy-0.8.0
rootdir: /Users/adamg9999/Development/flask-tutorial, inifile: setup.cfg
collected 24 items

tests/test_auth.py ........                                                                                [ 33%]
tests/test_blog.py ............                                                                                [ 83%]
tests/test_db.py ..                                                                                [ 91%]
tests/test_factory.py ..                                                                                [100%]

=========================================================== 24 passed in 1.15 seconds ===========================================================

for coverage > 4.0 need to first run coverage run -m pytest this will print the pytest output to STDOUT, then a followup coverage report will output the expected report:
Name                 Stmts   Miss Branch BrPart  Cover
------------------------------------------------------
flaskr/__init__.py      22      0      2      0   100%
flaskr/auth.py          54      0     22      0   100%
flaskr/blog.py          54      0     16      0   100%
flaskr/db.py            24      0      4      0   100%
------------------------------------------------------
TOTAL                  154      0     44      0   100%```

### Environment

$ python --version
Python 2.7.10 :: Continuum Analytics, Inc.
(py2.7.10) adamg9999 flask-tutorial
$ flask --version
Flask 1.0.2
$ coverage --version
Coverage.py, version 4.5.1 with C extension

IMO, coverage run $ coverage report is the normal usage.
See  Coverage documentation for more detail.

On Tue, Oct 23, 2018 at 6:01 PM Grey Li<EMAIL_ADDRESS>wrote:

Closed #2959 https://github.com/pallets/flask/issues/2959.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pallets/flask/issues/2959#event-1922109944, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAibkiNr4YNxAD-nfXei4TTHzO6x_OYjks5un7v7gaJpZM4X0RJS
.

The roles of “expected” & “actual” are reversed in context of the tutorial.
The tutorial needs update according to your comment.
On Tue, Oct 23, 2018 at 6:24 PM Grey Li<EMAIL_ADDRESS>wrote:

I didn't receive your reply and it's one day long, so I closed this. BTW,
you can reopen it anytime at your will. Sorry for the inconvenience, so
what do you mean actually?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pallets/flask/issues/2959#issuecomment-432478397, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAibkk-0ta5DbrlreZLnT-ttz_Jh4sbWks5un8FSgaJpZM4X0RJS
.

Sorry for the harshness. Thank you for supporting the flask package.
On Tue, Oct 23, 2018 at 6:24 PM Grey Li<EMAIL_ADDRESS>wrote:

I didn't receive your reply and it's one day long, so I closed this. BTW,
you can reopen it anytime at your will. Sorry for the inconvenience, so
what do you mean actually?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pallets/flask/issues/2959#issuecomment-432478397, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAibkk-0ta5DbrlreZLnT-ttz_Jh4sbWks5un8FSgaJpZM4X0RJS
.

The behavior described by the document  seems to be consistent with what you describe. Are you reading the latest documentation？


Can we use SCA for oligomeric protein ?

Main idea of SCA is to use MSA as a foundation stone. My question does it equally reliable for oligomeric protein?

I don't think so if you can't get MSA of oligomeric proteins. BTW SCA is quite sensitive to quality of the data.


strange kb_generic_cmp function

Hello,
In kbtree.h why
#define kb_generic_cmp(a, b) (((b) < (a)) - ((a) < (b)))
is not simply
#define kb_generic_cmp(a, b) ((a) - (b))

To avoid number under/over-flow

Also, a and b could be unsigned. Then a-b is always non-negative.

OK, thanks!


external tomcat_test failed with both jdk11 and jdk17

external tomcat_test failed with both jdk11 and jdk17 and believe failed with jdk8.
8: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/470/
11: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/459/
17: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/469/
01:30:24      [junit] 03-Mar-2022 06:30:24.258 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testOptions[201]]
01:30:24      [junit] 03-Mar-2022 06:30:24.259 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector[org.apache.coyote.http11.Http11AprProtocol-auto-202]]
01:30:24      [junit] 	org.apache.catalina.LifecycleException: The configured protocol [org.apache.coyote.http11.Http11AprProtocol] requires the APR/native library which is not available
01:30:24      [junit] 		at org.apache.catalina.connector.Connector.initInternal(Connector.java:1036)
01:30:24      [junit] 		at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
0
...
01:30:30      [junit] 03-Mar-2022 06:30:29.759 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
01:30:30      [junit] 03-Mar-2022 06:30:29.759 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.0.7]
01:30:30      [junit] 03-Mar-2022 06:30:29.764 INFO [main] org.apache.catalina.startup.ContextConfig.getDefaultWebXmlFragment No global web.xml found
Cancelling nested steps due to timeout
09:50:25  Sending interrupt signal to process
09:50:37  Terminated
09:50:37
09:50:37  tomcat_test_0_FAILED

Looks like setting issue.

Couple notes:

https://github.com/apache/tomcat supports four different version Tomcat 8, 9, 10.0, 10.1
Originally tests was added for Tomcat 8 with version 8.5
Recently tests changed with tag_version="10.0.7" so it changes to test Tomcat 10.0 instead of 8. ,Latest Tomcat 10.0 version is 10.0.17
The failure shows it has the dependency of APR/native. So it might be setting up issue. Looking at travis setup there are extra steps need to setup the environment. Or
Try to run specific jobs as setting in the workflow file

@yinggzz see if you could help with couple issues mentioned in https://github.com/adoptium/aqa-tests/issues/3398#issuecomment-1058325633

More notes to clarify steps 4 and 5 in https://github.com/adoptium/aqa-tests/issues/3449#issuecomment-1069844385:
4. Comparing https://github.com/apache/tomcat/blob/10.0.17/.travis.yml#L28-L38 with what is installed in the container https://github.com/adoptium/aqa-tests/blob/master/external/tomcat/test.properties#L6 (confirming by looking at the generated Dockerfile that is now attached to the test job).
5. The tomcat project is running https://github.com/apache/tomcat/blob/main/.github/workflows/ci.yml#L47 with ANT_OPTS set as https://github.com/apache/tomcat/blob/main/.github/workflows/ci.yml#L49, where as we are currently running this https://github.com/adoptium/aqa-tests/blob/master/external/tomcat/dockerfile/tomcat-test.sh#L26

I would like to work on this

Since original grinder test results expired, rerun to look at the dockerfile generated;
jkd8: https://ci.adoptopenjdk.net/job/Grinder/3860/
jkd11: https://ci.adoptopenjdk.net/job/Grinder/3861/

step 4:
looking at dockerfile in jdk8 tomcat test link
the below are installed:
RUN apt-get update \
	&& apt-get install -y --no-install-recommends git wget tar make gcc linux-libc-dev libc6-dev perl \
	&& rm -rf /var/lib/apt/lists/*

compared to travis.yml

step 5:
tomcat run on jdk11 after adding ant_opts as shown in workflow file:
https://ci.adoptopenjdk.net/job/Grinder/3881/
old failure still persists:
20:09:27      [junit] 	org.apache.catalina.LifecycleException: The configured protocol [org.apache.coyote.http11.Http11AprProtocol] requires the APR/native library which is not available
...
20:09:42  FAILED test targets:
20:09:42  	tomcat_test_0

tomcat run on jdk 11 after adding "install" section of travis setup in tomcat/test.sh: https://ci.adoptopenjdk.net/job/Grinder/4149/console
same error:
13:25:56      [junit] 28-Mar-2022 17:25:56.325 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector[org.apache.coyote.http11.Http11AprProtocol-auto-1]]
13:25:56      [junit] 	org.apache.catalina.LifecycleException: The configured protocol [org.apache.coyote.http11.Http11AprProtocol] requires the APR/native library which is not available

@yinggzz For step 4 if there are different packages installed for travis job we'd like to install them in our environments. That is installing the packages build-essential, automake, autoconf, libssl-dev, subversion, libtool-bin, which can be done by update the test.properties.
The failure you mentioned in https://github.com/adoptium/aqa-tests/issues/3398#issuecomment-1081070334 shows  APR/native library which is not available. That means we need to probably either install or build APR/native library, something similar to
git clone -q -b 1.6.x --single-branch https://github.com/apache/apr.git $HOME/tmp/apr
cd $HOME/tmp/apr
./buildconf
./configure --prefix=$HOME/tmp/apr-build
make
make install
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$HOME/tmp/apr-build/lib"

@yinggzz For step 4 if there are different packages installed for travis job we'd like to install them in our environments. That is installing the packages build-essential, automake, autoconf, libssl-dev, subversion, libtool-bin, which can be done by update the test.properties.
The failure you mentioned in #3398 (comment) shows APR/native library which is not available. That means we need to probably either install or build APR/native library, something similar to
git clone -q -b 1.6.x --single-branch https://github.com/apache/apr.git $HOME/tmp/apr
cd $HOME/tmp/apr
./buildconf
./configure --prefix=$HOME/tmp/apr-build
make
make install
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$HOME/tmp/apr-build/lib"

@sophia-guo Thank you for the clarifications, for installing APR/native library, should I add it to test.sh?


[Bug Report] Can't release app on the iOS App Store

Hello,
I've integrated media_kit in an iOS app and when I upload the binary to the iOS App Store, I receive an email saying that my app has an issue :

ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswift_Concurrency.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreData.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftAVFoundation.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftMediaPlayer.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/Runner.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it.

I tried some workarounds I found on StackOverflow like:

Set "Always Embed Swift Standard Libraries = YES"
Set "Strip Siwft Symbols = NO"
But I always get the same error message from ASC

Do you know how I can fix it?

I would like to specify (as I told to @JulienDev on Discord) that I have no experience of publishing apps on the App Store. If anyone has any ideas, they are welcome.
Also, there is no problem to build an iOS app in ipa format and install it with AltStore. Only when publishing on the App Store.
We don't know yet whether the resolution of this issue is the responsibility of the app developer or media_kit.

I'm posting here what I've found since the discussion with @HankG on Discord about build problems for the simulator.
I think the two problems are related, using a .xcframework should fix both problems.

From the Apple doc:

Dynamic libraries outside of a framework bundle, which typically have the file extension .dylib, are not supported on iOS, watchOS, or tvOS, except for the system Swift libraries provided by Xcode.

I also inspected the structure that the MobileVLCKit cocoapod follows, it embeds a single dynamic lib for each arch / platform. Except that the current build of libmpv creates several dylib, I think it is possible to create as many frameworks as there are dylib, to check:
MobileVLCKit.xcframework
├── Info.plist
├── ios-arm64_armv7
│   ├── MobileVLCKit.framework
│   │   ├── Headers
│   │   │   ├── MobileVLCKit.h
│   │   │   ├── …
│   │   ├── Info.plist
│   │   ├── MobileVLCKit                     # dylib
│   │   ├── Modules
│   │   │   └── module.modulemap
│   │   └── PrivateHeaders
│   │       ├── VLCCustomDialogProvider.h
│   │       ├── …
│   └── dSYMs
│       └── MobileVLCKit.framework.dSYM
│           └── Contents
│               ├── Info.plist
│               └── Resources
│                   └── DWARF
│                       └── MobileVLCKit
└── ios-arm64_x86_64-simulator
    ├── MobileVLCKit.framework
    │   ├── Headers
    │   │   ├── MobileVLCKit.h
    │   │   ├── …
    │   ├── Info.plist
    │   ├── MobileVLCKit                     # dylib
    │   ├── Modules
    │   │   └── module.modulemap
    │   ├── PrivateHeaders
    │   │   ├── VLCCustomDialogProvider.h
    │   │   ├── …
    └── dSYMs
        └── MobileVLCKit.framework.dSYM
            └── Contents
                ├── Info.plist
                └── Resources
                    └── DWARF
                        └── MobileVLCKit

I think only dylib, folders and Info.plist are required.
The following command may be useful to create the .xcframework:
$ xcodebuild -create-xcframework \
    -framework /path/to/MPV.framework \
    -framework /path/to/SSL.framework \
    -output /path/to/MPV.xcframework


The problem with parentheses in the password (Special characters) is very severe

We have talked about the problem with frogeth in this issue.
I've tried almost everything to resolve it. The issue with parentheses seems to be a severe problem.
I also tried this trick:
PARENTHESIS="("
NODE_ECDSA_KEY_PASSWORD=something${PARENTHESIS}
NODE_BLS_KEY_PASSWORD=something${PARENTHESIS}else

test.sh:
. ./.env
echo $NODE_ECDSA_KEY_PASSWORD

$ chmod +x test.sh
$ ./test.sh
something(

Everything seems ok, but the problem is still there.
Error: failed to read or decrypt the BLS private key: could not decrypt key with the given password
Message on Discord

Thanks for reporting this issue. I will try to look into what is happening. I am wondering if there's an issue with how docker-compose file reads the password with parentheses and try to find this issue out.

@eferbarn Have you tried single quotes around password with special characters? Looking at this issue - https://github.com/docker/compose/issues/8607
maybe worth trying and see if it resolves. I will also try on my side when I have some cycles.

Yes! I tried lots of solutions. They didn't work at all! Assume that my password is blah(blah!
I tried all of these potential solutions:

"blah(blah"
'blah(blah'
blah\(blah

Finally, I just used these commands to change my passwords:

$ cd .eigenlayer/operator_keys
$ rm <keyname>.bls.key.json
$ rm <keyname>.ecdsa.key.json
$ ./eigenlayer operator keys import --key-type ecdsa <name> <ecdsa_private_key>
$ ./eigenlayer operator keys import --key-type bls <name> <bls_private_key>

Thanks for checking. this is weird. I will dig deeper into it as I think it's important to support any passwords.


az rest does not work against dogfood

Describe the bug
I registered and used the dogfood environment (steps in the how to reproduce section below).
After this, az rest to even do a List Resource groups does not work.
Command Name
az rest --method get --uri "https://api-dogfood.resources.windows-int.net/subscriptions/d48566a8-2428-4a6c-8347-9675d09fb851/resourcegroups?api-version=2019-10-01"
Errors:
The endpoint 'active_directory_data_lake_resource_id' for this cloud is not set but is used.
/home/hitesh/.azure/clouds.config may be corrupt or invalid.
Resolve the error or delete this file and try again.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az cloud register --name Dogfood --endpoint-active-directory-graph-resource-id https://graph.windows-ppe.net/ --endpoint-active-directory-resource-id https://management.core.windows.net/ --endpoint-gallery https://df.gallery.azure-test.net/ --endpoint-resource-manager https://api-dogfood.resources.windows-int.net/ --endpoint-active-directory https://login.windows-ppe.net/
az cloud set --name Dogfood
az login

Expected Behavior
Environment Summary
Linux-4.4.0-18362-Microsoft-x86_64-with-debian-buster-sid
Python 3.6.5
Shell: bash

azure-cli 2.0.72 *
azure-cli-iot-ext 0.7.1

Extensions:
azure-cli-iot-ext 0.7.1
interactive 0.4.3

Additional Context

HI @zhoxing-ms could you pls have a look? thanks.

@hiteshmadan The error message means that the parameter --active-directory-data-lake-resource-id is not set in the command az cloud register. May I ask if this setting is not required in your dogfood environment?

@hiteshmadan any update?

Because there is no reply to this question for a long time, I will close it temporarily. If you have any questions, please feel free to let us know.

Tested with latest Azure CLI 2.31.0 and couldn't repro (following https://github.com/Azure/azure-cli/issues/20846#issue-1089659664):
$ az cloud register --name Dogfood --endpoint-active-directory-resource-id https://management.core.windows.net/ --endpoint-gallery https://df.gallery.azure-test.net/ --endpoint-resource-manager https://api-dogfood.resources.windows-int.net/ --endpoint-active-directory https://login.windows-ppe.net/ --endpoint-active-directory-graph-resource-id https://graph.ppe.windows.net/

$ az cloud set -n Dogfood

$ az login

$ az rest --method get --uri "https://api-dogfood.resources.windows-int.net/subscriptions/e4ced903-171b-4a34-a408-1b7185ea530a/resourcegroups?api-version=2019-10-01"
{
  "value": [
    {
      "id": "/subscriptions/e4ced903-171b-4a34-a408-1b7185ea530a/resourceGroups/yishitest",
      "location": "eastus",
      "name": "mytest",
      "properties": {
        "provisioningState": "Succeeded"
      },
      "tags": {},
      "type": "Microsoft.Resources/resourceGroups"
    }
  ]
}


[SR-13262][Sema] Adding contextual type purpose for where clause expression in constraint system

Making sure that we set the condition contextual type purpose for the contextual type conversion to bool on for statements where clause.

Resolves SR-13262.

@swift-ci Please smoke test

@swift-ci Please smoke test Linux platform


Implement support for labels on modules

This is POC and intended for brainstorming only
It introduces ability to add labels on resources and use labels as filters.
ATM it labels are only implemented on compose Modules, plan is to add it to almost every other resource (where reasonable)
Examples of possible usages:

group resources (so we do not have to reply on handle prefixes)
mark federated records
store import references (ext ID)
mark resources that could be preloaded in Corredor
marking dependencies by automation scripts, workflow
....

I'm also experimenting with ModuleLabelResourceType format, not sure were it will land (this is a bigger problem that touches RBAC resources as well...) might just be that we'll end up (for now) with RBAC-like format for label resources.

@tjerman I have a feeling you're not reading this right -- might be due to badly chosen var/prop names or poor docs in this POC.
Label struct is general -- and will be reused for ALL kinds of resources -- so labels for modules will have kind=module and labels for records will have kind=record etc.
ResourceID is self explanatory.
Name and value are the actual pairs that go to a specific resource (module, record...).
And there is intentional limitation of having unique labels per name per resource.
Having multiple labels with same name would introduce more complexity: we would need label IDs to properly manage the labels, updating/creating would not be as simple as using key-val struct etc.
Yes, we loose the ability to "define multiple groups" (from your example), but such examples might raise questions if we should no implement this "multiple groups" directly (w/o labels) in the first place.
Labels are just that -- simple pieces of data that allow us some filtering and labeling of our resources for distinction and faster/easier lookups.

@darh
Do we then really need to have a { k: v } pair for each label? Wouldn't a simple v be enough? Do you have a real world example where this would be useful? One place where this might be helpful is for system label translations, but that could also be solved with the simplified structure.
With the additional simplification, you could have something in the lines of:
// -----------
{
  "moduleID": "...",
  "name": "M1",
  "handle": "M1_h",
  "labels": [ "federated", "crm", "case management" ],
  ...
}
// -----------
{
  "moduleID": "...",
  "name": "M2",
  "handle": "M2_h",
  "labels": [ "crm", "case management" ],
  ...
}
// -----------
{
  "moduleID": "...",
  "name": "M3",
  "handle": "M3_h",
  "labels": [],
  ...
}
// -----------

To go back to the module, or rather resource grouping, we could then have this as a pure front-end feature instead of something the server should care about.


Accepts (and prints) invalid additional rules in strict mode

According to the specification https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification#explain:additional_rule_separator , the additional rule separator may only follow after either of a time selector, a rule modifier or a comment.
For example Mo-Th, Jun-Jul Fr is parsed without error in strict mode. It is also printed the same.
The opening hours evaluation tool is unable to deal with this (not even with the lenient parsing it does by default)
There are several avenues how to deal with this:

allow this syntax only in non-strict mode

if such rules are encountered, append open to the rule that would otherwise cause the following rule to be invalid when pretty-printing it , e.g. Mo-Th, Jun-Jul Fr -> Mo-Th open, Jun-Jul Fr

Cause: The opening [hours evaluation tool](https://openingh.openstreetmap.de/evaluation_tool/?EXP=Mo-Th%2C%20Jun-Jul%20Fr) is unable to deal with this (not even with the lenient parsing it does by default)
Effect: According to the specification https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification#explain:additional_rule_separator , the additional rule separator may only follow after either of a time selector, a rule modifier or a comment.
We, some exceptions noted, use
https://wiki.openstreetmap.org/w/index.php?title=Key:opening_hours/specification&oldid=1075290 as the base line for the parser,

Hm, I see. I don't like that it seems that the spec was changed unilaterally because one's own parser is not able to deal with the syntax.
On the other hand, that tool is a bit of the reference implementation, and is not one goal of the pretty-printing to generate a opening hours string in a syntax that will be understood by the largest set of interpreters? E.g. this parser changes TH to Th for this reason, no?

That was a good decade ago and subsequentially I was able to convince ypid to do things in a fashion that was more compatible with wider use, for example versioning.
I haven't closed the issue because you do have a point with at least having the facility to produce output that is compatible with later versions.

FWIW a lot of rules that are invalid as per this restrictions actually do have problems, i.e. were simply written erronously. E.g.

Apr 01-May 31, 08:00-19:00 probably didn't mean to add a comma in the first place
Mo-Su, 07:00-23:00 same as above
Jun 15-Mar 14, 24/7 same as above
Tu-Su 10:00-17:30; Mo, Jan 01, May 01, Dec 25 off meant to express that every Monday is off
well, etc.


Get rid of most uses of Val{} types

According to this I've been killing performance by using Val types.
Currently, we have ExprDist{V <: Val} <: Distribution, but it's probably better just to find a way to define a unique typename for each ExprDist using a heuristic that can be relied on.
Also, the Val trick is used to dispatch update! on the method argument, but this is easier to fix.

This is also used all over the place in _simplify_call to break up logic based on the type of function call being simplified. This is probably just a matter of refactoring.
Thankfully, the only things really broken (or hobbled by this are ExprDists, which don't fully work yet anyway.


Adding request id to evm log

We are adding the letter r plus request_id as a prefix of tracking_label. With this change we are able to find all related tasks in the log by a single request_id.
Logs:
before:

after:

filter command: grep "Q-task_id(\[.*\])" log/evm.log

cc @jcarter12 @math3matical

The code changes look good.  Still would like to review the concept with @jcarter12 and @math3matical to get their feedback before merging.

ping @jcarter12 @math3matical Look good to you?

@kbrock @jcarter12 and @math3matical are good with the changes.  Because this is an important change, I've reached out to the field for feedback and expect to hear back shortly.

@pkomanek We requested community feedback because this is a really important change.  One great suggestion we'd like to implement is add the tracking label to the request line as well:
before:
Q-task_id([service_template_provision_request_r99000000000003]) and
Q-task_id([r99000000000003_service_template_provision_task_99000000000004])
after:
Q-task_id([r99000000000003_service_template_provision_request_99000000000003]) and
Q-task_id([r99000000000003_service_template_provision_task_99000000000004])
Can you implement this change?

@tinaafitz PTAL

@pkomanek Can you update the screen shot to reflect the request log changes?

@tinaafitz sure, is it ok?

@pkomanek Looks great. :-)
@gmcculloug Can we merge this?


[HUDI-7470] Compaction completed not need write to mdt if mdt is disable

Change Logs
Compaction completed not need write to mdt if it is disable.
when sparksql is set hoodie.metadata.enable=false and execute compaction，it would also execute metadata update. It is not fitable if need disable mdt. describle in https://issues.apache.org/jira/browse/HUDI-7470

Impact
low
Risk level (write none, low medium or high below)
low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Hi @xuzifu666 , could you please help me understand the problem a bit more? Or could you post a screenshot of comparison between patched/original queries?
Based on my understanding, writeTableMetadata would try getting metadataWriterOpt, and when using Spark this LOC would check if MT is enabled already and try deleting MT if it's disabled


etcdserver: Automated cherry pick of detailed "took too long" warnings to release-3.1

Same as #9821 but to 3.1.

@gyuho Okay to backport this one all the way to 3.1?

@jpbetz Sure, let's merge on greens. Thanks.


Openstack Juno

Hi, I'm Vincenzo and I've installed in my company OpenStack(Juno) with 5 compute node, 1 network node, 1 controller node and 1 storage node using CentOS 7...
hi try ospurge...but after pip install virtualenvwrapper...mkvirtualenv ospurge not works...What is wrong?

Thank you for contributing to stackforge/ospurge!
stackforge/ospurge uses Gerrit for code review.
Please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Noresult link ...

How to add link to no-result msg

Is this a standard option that can be set in select2?  I don't see it anywhere on the select2 pages.


Javascript Curriculum should alert camper that they're trying to print the page

Describe the Issue
It's not exactly common, but it's an extremely easy mistake to make. In Python, you would use the print function to print things out. However in our JavaScript lessons; it prompts the camper to print out the current page they're in within the curriculum. There should be some kind of universal check tied to this type of challenge that determines if the code in the challenge contains the print function instead of console.log.
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-introductory-javascript-by-building-a-pyramid-generator/step-4
Your code
print("This is a test");

Expected behavior
Rather than the print page prompt showing up, the test once evaluated should tell me that I've made a mistake and should be using console.log.
Screenshots
No response
System

Device: Desktop
OS: Windows 10
Browser: Firefox
Version: 125.0.2

Additional context
Appears on this thread.
https://forum.freecodecamp.org/t/stuck-on-step-32-print-i-is-going-to-my-printer/686617

Interesting. I'm not a fan of overwriting the built-in print, personally.

Hey @a2937,
Thanks for bringing this to our intention. I think this is mostly because the user is new to programming. We should allow them to make mistakes!
We already have an example in the instructions of how to "print" something to console. I do not think we can make it any easier without over-engineering the test evaluator.
Thus I am closing this as not planned. Feel free to reopen if you feel like doing so.


Home screen view

can we reduce the size of the left part of the screen so the right calendar is fully viewed

@Nayer-Sobhy
Can you tell me what is your screen size, also you sure you are not on zoom mode!

14inch
Not zoom mode
Google chrome
On Mon, 31 Oct 2022 at 12:09 PM Thunder @.***> wrote:

@Nayer-Sobhy https://github.com/Nayer-Sobhy
Can you tell me what is your screen size, also you sure you are not on
zoom mode!
—
Reply to this email directly, view it on GitHub
https://github.com/codescalersinternships/CSHR/issues/185#issuecomment-1296867179,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADROEC3BIRQRSABWBYZME5LWF6LEVANCNFSM6AAAAAARP6WWVY
.
You are receiving this because you were mentioned.Message ID:
@.***>


How to add puppeteer launch options?

now i want to use launch to add same options ,like
puppeteer.launch({             args: [                 '--disable-web-security'               ],         })
How can I do ? need help
Thanks

You can do this entirely outside of the puppeteer-in-electron framework by doing:
const {BrowserWindow, app} = require("electron");
app.commandLine.appendArgument("disable-web-security");


Add "port" config option

Hey, I'm not maintaining this nowdays since I've moved away from Puma and Mina as well. New maintainer here: https://github.com/untitledkingdom/mina-puma


Terminals are named kernel_task

Use insiders-1.78 or run out of source
start a terminal
the name is "kernel_task"
start a long running task, like yarn watch, press ctrl+c and see it's not terminating

https://user-images.githubusercontent.com/1794099/228880022-344ef467-c338-4a74-8c2a-a28e7cb090a5.mov

same question

Same issue on my brand new Apple M2 Mac Mini. Running latest Insiders. I thought I was going crazy.

Works fine on latest version of insiders.

Yeah fixed now. Thanks everybody!

Not working for me. I am using CTRL+Z

Not working for me after updating today (May 09, 2023)
Version: 1.78.0 (Universal)
Commit: 252e5463d60e63238250799aef7375787f68b4ee
Date: 2023-05-03T20:11:00.813Z
Electron: 22.4.8
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 18.7.0
Sandboxed: Yes

Not working for me. I am using CTRL+Z

That doesn't kill the process. It just suspends it. Just be aware of that (if you do it a lot ;)

same for me, no control-c or any kill commands will work:
Version: 1.78.1
Commit: 6a995c4f4cc2ced6e3237749973982e751cb0bf9
Date: 2023-05-04T09:57:42.343Z (5 days ago)
Electron: 22.5.1
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 18.7.0
Sandboxed: No

It stopped working for me due to an extension which had created a key binding starting with ctrl + c so I removed the key binding and it started working. This SO answer helped me.

@gitSambhal what extension was causing the issue?

@Tyriar I forgot the name but you can check your keyboard bindings.

@gitSambhal I don't have the same extensions as you?

Hi, this "Ctrl+C" (terminate task) feature suddenly stopped working a few days ago for us as well:

the "^C" still displays in the terminal but without any effect
and there is not a single shortcut associated to Ctrl+C and no way to add one

This is a huge pain as we simply cannot work anymore using vs-code, this was such a central feature
There is SO MUCH content on the topic online, yet no simple solution:

What happened? Why did vs-code team do this?
How is there not a SIMPLE option in Keyboard Shortcuts (JSON) to add it back?

We won't be able to ship our work this weekend solely because of the delay caused by this.
Thanks in advance to those currently working on a solution

@Tyriar what is shown in the vscode status bar when you press ctrl + c ?

@loicguichaoua it was a bug we introduced and fixed shortly afterwards, see https://github.com/microsoft/vscode/issues/181939. One of the downsides of using Insiders is occasionally things like this slip in.

Still no update to fix it. How do we opt OUT of Insiders. I never have opted in!


actionNameAttribute support for tracking user actions

Describe the solution you'd like
Would it be possible to add support for actionNameAttribute which can be seen in browser rum documentation here. We would like to tie action names to testID's.
Describe alternatives you've considered
We have considered writing a utility function to pass both testID and data-dd-action-name to a component, but it would be nice to avoid having to do {...getTestID("blah")} every time as add an id.

Hi @akinzalowevidation, thanks for reaching out!
This sounds like a good addition, we've added it to our backlog and I'll let you know once it's released :)

Hi @akinzalowevidation,
I'll close this issue since this has been released in SDK version 1.8.0 :)


Support for Security Devices

Would it be possible to add support for the Secure Contact Sensor (https://www.philips-hue.com/en-us/products/all-products/product-page/secure-contact-sensor#overview)? I would like to use it for other purposes than real security alarms, more like a sensor on my garage door to trigger an event in Node-Red when the door is opened/closed.

Hello +1 for this feature from me :-)

I'd very much appreciate support for secure contact sensors!

Looking for this as well

@mauricedominic Would that be a lot of work to implement?


Updated the Copyright note in the LICENSE

Based on the quick feedback trying to clarify Copyright so that
it doesn't imply assigning the copyrights if you contribute.
Currently policy is that you indicate or imply to distribute your
contribution under tha project license or attach the license of
your choice to your contribution. if your license is compatible
with the main license the this project can be distributed and
used whole.
Further Copyright transfer & assignment is unnecessary and this
I propose that misleading Copyright notice to be corrected. I
recommend alwayd distributing the project in a form that either
includes backreference to the project repository or at least
identifies the list of individual contributors so that
original Copyrights can be backtracked if necessary and
parental right gets respected.

We also had a discussion if the copyright -row could be removed altogether.  However, that might be considered as breaking the form of the standard license, and thus could cause trouble at minimum to the license scanners. Thus we will keep the change minimal, but have less misleading pointer in it.


Merge from integration_2023-08-02_11.47 to main (Cray-HPE/prodmgr) 08-02

CRAYSAT-1219 Allow arbitrary podman arguments to prodmgr (#18)

Thank you for the review @sravani-sanigepalli. I would like to delete the integration branch in this repository and switch to instead using main as the default branch. The integration branch is sort of a relic of the past. In a previous product, we used to do integration testing across the whole product by using the integration branch of every component. We are not doing anything like that here, so this really just adds an extra step.
Do you have any objections to me removing the integration branch and changing the default branch to main?
I would also like to consider using tags for releases. I will let you know about that. I'm working on this in CRAYSAT-1754 since this repo originated from the SAT team.

@sravani-sanigepalli, since the integration branch was simply behind the main branch now, I just went ahead and deleted the integration branch and made main the default branch for this repository. You shouldn't need to do anything to your existing branches in this repository which were based off integration, but if you want, you can rebase them on the latest main branch. Any future PRs can be made directly to the main branch. Let me know if you run into any issues. Thanks!

Also FYI, @jsollom-hpe and @sravani-sanigepalli, I did go ahead and create the release/1.2 branch for this repository to get a stable build of the prodmgr RPM. You can find that here in artifactory:
https://artifactory.algol60.net/ui/repos/tree/General/csm-rpms/hpe/stable/sle-15sp4/cray-prodmgr/x86_64/cray-prodmgr-1.2.1-1.x86_64.rpm
In this repo, builds off the release/* branches go to that stable repository. Builds off of main go to an unstable repository in Artifactory. We may switch to tags in the near future, but I wanted to make sure we had a stable build with the changes to use product-deletion-utility for now.

Also FYI, @jsollom-hpe and @sravani-sanigepalli, I did go ahead and create the release/1.2 branch for this repository to get a stable build of the prodmgr RPM. You can find that here in artifactory:
https://artifactory.algol60.net/ui/repos/tree/General/csm-rpms/hpe/stable/sle-15sp4/cray-prodmgr/x86_64/cray-prodmgr-1.2.1-1.x86_64.rpm
In this repo, builds off the release/* branches go to that stable repository. Builds off of main go to an unstable repository in Artifactory. We may switch to tags in the near future, but I wanted to make sure we had a stable build with the changes to use product-deletion-utility for now.

Sure. This should work for now. Thanks @haasken-hpe


sig#805 - Align portal-assets documentation structure with updated TRG 1

Description
To enhance the consistency and ease of understanding of our products for the open community, TRG 1 was updated.
Make sure to comply with the updated structure:
repository
└─── docs/
    └─── architecture/
    └─── admin/
    └─── user/
    └─── api/
    └─── README.md

Please TRG 1.05-1.08 for more information:
https://eclipse-tractusx.github.io/docs/release/trg-1/trg-1-05
https://eclipse-tractusx.github.io/docs/release/trg-1/trg-1-06
https://eclipse-tractusx.github.io/docs/release/trg-1/trg-1-07
https://eclipse-tractusx.github.io/docs/release/trg-1/trg-1-08
Acceptance Criteria

[ ] Adjust the repo related documentation based on trg 1.05 - gather all architecture documentations into docs/architecture
[ ] Adjust the repo related documentation based on trg 1.06 - gather admin related docu into docs/admin
[ ] Adjust the repo related documentation based on trg 1.07 - gather end-user related documentation into doc/user
[ ] Adjust the repo related documentation based on trg 1.08 - Clarify the setup with Evelyn ;)
[ ] Adjust the docs/README.md regarding your changes
[ ] Ensure that all documentation is in English

Additional Information

@oyo  assigned it to you please take a look. we need to start with this TRG adjustments

@evegufy @MaximilianHauer currently we only have user and developer docs. So I suggest to rename developer to architecture and create empty folders for admin and api with README files saying content will follow (admin) or doesn't apply (api)

sounds fine for me

@oyo as discussed yesterday, there's architecture docs https://github.com/eclipse-tractusx/portal-assets/tree/v2.2.0/docs/developer/Technical Documentation


[docs] Add example yamls

Changes
close #238

Submitter Checklist

[x] Docs included if needed
[ ] Tests included if needed
[x] Follows the good commit messages standard

/approve


No useMutation

Cant seem to access the useMutation method in trpc https://trpc.io/docs/client/react/useMutation

Yeah, useQuery uses the built-in Nuxt useAsyncData and there's no way to mutate the data without messing with the global cache. For now, you can use mutate and refresh:
const { $client } = useNuxtApp()

const { data, refresh } = await $client.todo.getTodos.useLazyQuery()

const addTodo = async () => {
  await $client.todo.addTodo.mutate({
    userId: 69,
    title: 'Buy a milk',
    completed: false
  })

  refresh()
}

yes but this assumes that your mutation function / component has access to the refresh method from the original query... guess I need to change the structure of my app

Thanks @aaronksaunders!

I solved my problem by just emitting refresh events from my components for
now, will probably figure out a strategy for using a composable, but it all
works now so ready to put together a tutorial video and blog post your
module and drizzle
On Mon, Aug 28, 2023 at 10:40 PM Robert Soriano @.***>
wrote:

Thanks @aaronksaunders https://github.com/aaronksaunders!
—
Reply to this email directly, view it on GitHub
https://github.com/wobsoriano/trpc-nuxt/issues/119#issuecomment-1696684293,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEAFGJOIXKWHAKLWYV6LETXXVJCFANCNFSM6AAAAAA4AIQ2OI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @DarraghOFlaherty, I'm closing this for now.
I really want this module to use built-in Nuxt composables, and until Nuxt releases a mutation composable, you'll need to follow my solution to this question (for now).
If you really want to do mutations, there's a trpc-vue-query package that might help.
Thanks!

You are right, @BitRayDev. There's a composable that will let us mutate the cached value of useAsyncData - useNuxtData, and I'm currently in the process of adding a mutation feature using that.


export fails with multiple remotes

With two remotes foo and bar:
$ vcs export
Could not determine remote url: error: invalid key (newline): remote.foo
bar.url

Duplicate of #8.

@NikolausDemmel Feel free to try out my fix-git-multiple-remotes branch, which handles this situation: https://github.com/jbohren-forks/vcstool/tree/fix-git-multiple-remotes


flatsurf 3.15.2

Merge only after success.
This pull request was auto-generated by rever

@conda-forge-admin, please rerender


What is the PySOL package and where can it be found?

In the Megatron-LM docker README file, the following instructions can be found:
Note that as of now you need to have PySOL cloned to the directory here before building the container.
What is "PySOL" referring to? I assume we are not talking about http://www.pysol.org/, and I can't find any other relevant reference on a short Google search.

@drfinkus Thanks for reporting this typo. We will fix as soon as possible.

@drfinkus We have traced this confusion to https://github.com/NVIDIA/Megatron-LM/issues/4. Please ignore the requirement.


Shouldn't perplexity range from [1 to inf)?

https://github.com/huggingface/evaluate/blob/8dfe05784099fb9af55b8e77793205a3b7c86465/metrics/perplexity/README.md?plain=1#L60
perplexity = e**(sum(losses) / num_tokenized_tokens)
If sum(losses) = 0, then perplexity = 1.

Perplexity ranges between zero and inf because the exponent can be negative (The sum of negative log likelihoods).
Check out the following blog post for a better understanding.
Perplexity of fixed-length models.

Thanks, will take a look.


NodeJS release index for 10.8.0 and 10.9.0 is fubar so NVM appears to be broken

Expected Behavior

nvm install 10.9.0

should install NodeJS version 10.9.0 and its associated NPM
Actual Behavior
NPM install fails with:

Downloading npm version 6.2.0... Download failed. Rolling Back.
Rollback failed. remove C:\Users\Marnott\AppData\Roaming\nvm\temp\npm-v6.2.0.zip: The process cannot access the file because it is being used by another process.

Steps to reproduce the problem:
The problem comes from the node release index file found here:
https://nodejs.org/download/release/index.json
That index specifies NPM version 6.2.0, for both NodeJS 10.9.0 and 10.8.0 but no such NPM version exists
https://github.com/npm/npm/releases
Work Around

nvm install 10.7.0

and wait for Node 10.10.0 which hopefully will be fixed

Upgrade to 1.1.7. npm changed their repo.


[FR] Editor API: add an edge change method

We currently emit two events for changing an edge: one to remove the old edge and one to add a new edge. That said it's possible that one of those operations could fail, so I'm wondering if we want something more atomic from the Editor API: a change method which takes from and to params? wdyt?

Yeah, that seems right. And the from object identity doesn't change in this case, just the values? This way, it's still the same edge in the graph? Would that work? Or would you rather change identity?


Instrument updates, add KoalaContext

what
Adding and implementing new events for updates, which includes a new KoalaContext enum class in Kotlin.
here's why i chose enum class
tl;dr using sealed class would be a smidge faster but enum class is much cleaner. both sealed and enum are faster than static java classes.
We typically use enums sparingly in Java since they are costly and don't provide us with much more functionality than if we were to use static classes to hold global values. We use enums quite a bit in Swift because they are first class and have type inference, i.e. a perfect use case for koala contexts.
Kotlin seemed like a natural choice for recreating our contexts, and there are in fact enum classes that provide the exact functionality that we would like. Docs:
https://kotlinlang.org/docs/reference/enum-classes.html
I was skeptical about performance so I did some research and manual benchmarking to see how enum class performance would hold up to static classes in Java and sealed classes as suggested by a few posts on the internet.
An example of a sealed class KoalaContext implementation is:
sealed class KoalaContext {
  sealed class Comments {
    object PROJECT : Comments()
    object UPDATE : Comments()

    fun trackingString(): String = when(this) {
      is PROJECT -> "project"
      is UPDATE -> "update"
    }
  }
}

// accessed in Java as:
KoalaContext.Comments.PROJECT.INSTANCE;

(Note: using the convert-to-Kotlin tool on the static java class returned a bunch of nested objects that looked something like this:
object KoalaContext{
  object Comments {
    val PROJECT = "project"
    val UPDATE = "updates"
  }
}

// accessed in Java as as:
KoalaContext.Comments.INSTANCE.getPROJECT();

but the type would ultimately be a String.)
In the end, when "benchmarking" (measuring the time it takes to print each sealed, static, and enum Comments.Project context value 100_000 times), resulted in:
sealed class: 		28373ms 🥇
static class: 		30956ms 🥉
enum class: 		29766ms 🥈

Yep, the sealed class approach is technically the winner, but in terms of readability and ease of use I think it's worth continuing with enum class. Plus it's faster than using static java classes anyways!
The downsides are of course the slight performance ding and the inability to mix associated value types (i.e. if we also want an enum class to hold String and Int values), but that's something we can keep in mind for future implementations (all of our Koala contexts are strings).

Hey @luoser,
is the benchmark sealed class vs. enum vs. static field open source too? Didnt expected such a result, would like to take a closer look. Don't get me wrong, I do believe that your results are correct although I'm surprised. I would like to take a look at kotlins byte code tweaks for sealed classes vs. static fields in a clean environment (which I'm obviously too lazy to write my own tests / benchmark for :smile:)

Hi @sockeqwe, the results were indeed surprising.
The "benchmark" test I ran does come with a caveat since I lazily ran them in our app--not an ideal clean environment to really analyze the differences between the Kotlin byte code differences.
Please excuse the noise in this branch, but it contains the code I used to measure the times, namely

this is the sealed class context
this is the enum class context
this is the static class context
and this is the very lazy benchmarking code that i actually ended up running 100_000 times rather than 1_000_000

Definitely not the most scientific approach, and I would also love to do a more in-depth analysis at some point :neckbeard:

Unsubscribed me
On 21-Mar-2017 9:09 PM, "lisa luo"<EMAIL_ADDRESS>wrote:

Hi @sockeqwe https://github.com/sockeqwe, the results were indeed
surprising.
The "benchmark" test I ran does come with a caveat since I lazily ran them
in our app--not an ideal clean environment to really analyze the
differences between the Kotlin byte code differences.
Please excuse the noise in this branch
https://github.com/kickstarter/android-oss/compare/context-benchmarking,
but it contains the code I used to measure the times, namely

this is the sealed class context
https://github.com/kickstarter/android-oss/blob/b1b0f2ba9067ce5e8afdc953792ec47033accf8d/app/src/main/java/com/kickstarter/libs/ConvertedKoalaContext.kt
this is the enum class context
https://github.com/kickstarter/android-oss/blob/b1b0f2ba9067ce5e8afdc953792ec47033accf8d/app/src/main/java/com/kickstarter/libs/KoalaContext.kt
this is the static class context
https://github.com/kickstarter/android-oss/blob/b1b0f2ba9067ce5e8afdc953792ec47033accf8d/app/src/main/java/com/kickstarter/libs/StaticKoalaContext.java
and this is the very lazy benchmarking code
https://github.com/kickstarter/android-oss/blob/b1b0f2ba9067ce5e8afdc953792ec47033accf8d/app/src/main/java/com/kickstarter/ui/activities/CommentsActivity.java#L155-L184
that i actually ended up running 100_000 times rather than 1_000_000

Definitely not the most scientific approach, and I would also love to do a
more in-depth analysis at some point [image: :neckbeard:]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kickstarter/android-oss/pull/59#issuecomment-288119314,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUB0eNaXmx3dbk_HOCaTZXbqVf7rXM0vks5rn-84gaJpZM4MCWiS
.

Thank you so much @luoser !


Add support for Bicep template and parameters highlight to highlight.js

Is your feature request related to a problem? Please describe.
Highlight,js https://github.com/highlightjs/highlight.js is popular library for code syntax highlight. It is used by many developers and documentation applications like Wiki.js. It would be nice if there is support for highlighting Bicep template and parameters code syntax.

@anthony-c-martin implemented our highlight.js support, but it may be missing parameters support, so I'll let him comment more.

FYI it is not listed as supported language in the official docs - https://highlightjs.readthedocs.io/en/latest/supported-languages.html

Nice catch. I think we never told highlight.js folks that we added support.

For sure it does not work in wiki.js latest build but my knowledge is not broad enough to know if wiki.js does not use latest highlightjs yet or something additional needs to be done in highlightjs to work.

Nice catch. I think we never told highlight.js folks that we added support.

Their official stance is that they longer take contributions to the core library, and we haven't published a 3rd party NPM package:  https://highlightjs.readthedocs.io/en/latest/language-contribution.html

The current process is pretty manual - you've motivated me to improve our docs + process. PR here: https://github.com/Azure/bicep/pull/11614

@slavizh I've added a build step with #11614 to generate a Bicep highlight.js plugin - instructions and examples available here: https://github.com/Azure/bicep/blob/main/docs/highlighting.md#highlightjs