[TGL] gst-msdk decode vc1 cmd runtime hang on TGL

System information

CPU information(cat /proc/cpuinfo | grep "model name" | uniq):11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
GPU information(lspci -nn | grep -E 'VGA|isplay):0000:00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01)
Display server if rendering to display(X or wayland):

Issue behavior
Describe the current behavior
gst-launch-1.0 -vf filesrc location=input.vc1 ! 'video/x-wmv,profile=(string)advanced',width=176,height=144,framerate=14/1 ! msdkvc1dec ! videoconvert chroma-mode=none dither=0 ! video/x-raw,format=I420 ! checksumsink2 qos=false file-checksum=false frame-checksum=false plane-checksum=false eos-after=15 dump-output=true dump-location=output.yuv
Describe the expected behavior
pass
Debug information
reproduce commit:
libva : ef1df02f3ad4
gmmlib : 4552654ed52f
intel-media-driver : c7132d869bed
onevpl : 250d806b5867
onevpl-gpu : ab051c80094c
cartwheel-gstreamer:36e60d64d1a6

debug from @mengker33

Actually, this hang issue occurred on all platforms which support vc1 decode, i.e. ICL, CFL, ADL, etc.

Could you check if it is same issue mentioned in https://github.com/oneapi-src/oneVPL-intel-gpu/issues/230?

Could you check if it is same issue mentioned in #230?

It might not be the same issue. The hang mentioned in #230 happened when we pass MFX_IOPATTERN_OUT_SYSTEM_MEMORY type output mfxFrameSurface1, and I didn't see the same gdb debug log as this one shown in the pic above. The hang occurred in this ticket occurred using our cartwheel-gstreamer repo, in which we pass MFX_IOPATTERN_OUT_VIDEO_MEMORY type for output mfxFrameSurface1.

@Jexu, can anyone help with this issue? Thanks

@mengker33 Yeah, the issue is on track and i will let you know if having any finding.

Are there any updates? thanks

skip test decode vc1, so close this ticket.


[angle] Add egl renderer to list of files compiled for linux

For linux builds add egl to the list of files compiled.
Not including them causes linking issues on linux with the following undefined reference
rx::DisplayEGL::DisplayEGL
as per the following code snippet from
rc/libANGLE/Display.cpp:287
#    elif defined(ANGLE_PLATFORM_LINUX)
#        if defined(ANGLE_USE_OZONE)
            impl = new rx::DisplayOzone(state);
#        else
            if (deviceType == EGL_PLATFORM_ANGLE_DEVICE_TYPE_EGL_ANGLE)
            {
                impl = new rx::DisplayEGL(state);
            }
#            if defined(ANGLE_USE_X11)
            else
            {
                impl = new rx::DisplayGLX(state);
            }
#            endif

Fixes # 12110 https://github.com/microsoft/vcpkg/issues/12110

/azp run

Could you also update the version to '2020-05-15-1' in CONTROL file?

@ankurverma85, why do you close this PR?

Sorry that was accidental.
New to github ux.

Is there something blocking this pr?

Can you merge this pull requeat. I can't see any options to complete the pull request.
Maybe I'm not allowed to?

@BillyONeal, could you please help review and merge this PR?

LGTM, thanks for the improvement!


the pagenation is strange; at Media Overlays, page-progression-direction="rtl" and writing-mode:vertical-rl;

Test file(s)
https://github.com/toshiakikoike/epub_file/blob/master/readium_test/moby-dick-mo-v.epub
This EPUB is modified from epub3-samles; moby-dick-mo,page-progression-direction="rtl" and writing-mode:vertical-rl;
Product:
readium-js-viewer(master branch)
Bug:
After opening above file,  jump to "CHAPTER 1. LOOMINGS." from navigation, then play audio.

At the page last, page turn;

After page turn, screen show teh next page ("men fixed in ocean ....) ,but playback section returns to previous page, play from  "CHAPTER 1. LOOMINGS.".

cannot get epubcfi when page-progression-direction="rtl"?
after page turn, the value of epubcfi is the same as prev page.

cannot get epubcfi when page-progression-direction="rtl"?
after page turn, the value of epubcfi is the same as prev page.


add v2 documentation

In this PR I added the v2 documentation to our existing swagger file.

We have a flaky test with a race condition that needs to be fixed. This PR is unrelated.


Enhancement request - Screen sleep timeout - Turn down option, rather than Turn off

Currently the noActivitySecondsToSleep parameter sets a timeout till the screen backlight is 'Turned off'.
Is it possible to enhance this function such that the screen backlight can be turned down, rather than only turned off. In dark, no light, situations it would be a huge boon to the utility of these screens to be able reduce the backlight illumination to a very low level - in the region 1 - 5% - in order that users can locate a screen in total darkness?
I acknowledge that illumination even at this low level could mean screen life extension is significantly compromised versus completely switching the screen off. However, there are other methods for contending with this, such as area proximity sensors in entrances or hallways that can be used to 'wake' a number of screens from complete blackness within in a designated area, if potential users enter that region. And then, once the area is 'empty' again, the screens can all be turned off.

See https://oxrs.io/docs/firmware/touch-panel-esp32.html#control-the-backlight.
You can set the backlight level via an MQTT command - I am using this for example, to constantly update the screen backlight level depending on the time of day.

Yep - I’m across that and have been using that command to recreate thenoActivitySecondsToSleep timeout functionality in node red, which has turned out to be pretty involved.
Ultimately I’m suppose I’m a self interested advocate of seeing that all the OXRS ecosystem kit is sufficiently ‘clever’ to cover most of what I’d characterise as basic hygiene functions, like product life extension and energy efficiency tasks, in firmware, cognisant, of course, that RAM on these devices is extremely limited leading to the "thin client” ethos.
The other driver is striving to reduce the complexity overheads for new adopters to the degree that sensibly can be achieved, so ‘out of the box’ the user is focussing on and receiving core utility benefit with the least overhead in depth of knowledge.
If it's a bridge too far to add ’Turn down’ to the ’Turn off’ device level functionality on ’sleep’, so be it.

On 25 Oct 2022, at 10:25, Ben Jones @.***> wrote:
See https://oxrs.io/docs/firmware/touch-panel-esp32.html#control-the-backlight https://oxrs.io/docs/firmware/touch-panel-esp32.html#control-the-backlight.
You can set the backlight level via an MQTT command - I am using this for example, to constantly update the screen backlight level depending on the time of day.
—
Reply to this email directly, view it on GitHub https://github.com/OXRS-IO/OXRS-IO-TouchPanel-ESP32-FW/issues/47#issuecomment-1289773908, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2DSJV76QWRMYPE7WIPXDWE4LHJANCNFSM6AAAAAARNOC76M.
You are receiving this because you authored the thread.

This firmware is not really designed to work that way. It is more of a set of tools, which can be used with an external rules engine or server backend, to perform the clever stuff. So very little "smarts" or logic is built in, by design. Hope that makes sense.

Indeed I well understand and support that “thin client” ethos.
Its just that the config options do currently allow for a variability in time till sleep, so I figured that adding one additional config variable defining the sleep backlight level would not impose too onerous an overhead, given that the code to actually implement the backlight level change on sleep timeout is already there. Yes it does involve declaring an extra settings variable, and a few extra lines of code to extract and update that additional variable from the config mqtt payload. I think the following suggestions would do it:
"uint32_t _noActivitySleepScreenLevel  = 0L;
"
and
“  if (json.containsKey("noActivitySleepScreenLevel"))
{
_noActivitySleepScreenLevel = json["noActivitySleepScreenLevel"].as();
}
"
Which, from the extent my lay comprehension of these things goes, would seem to be the extent of it, save for the change required to add the new variable in place of the ‘0’ in the function call _setBackLight() in this section:
“  if (_noActivityTimeOutToSleep != 0)
{
// is in sleep allready ?
if (_actBackLight > 0)
{
// time elapsed, jump to HomeScreen
if (lv_disp_get_inactive_time(NULL) > _noActivityTimeOutToSleep)
{
_retainedBackLight = _actBackLight;
_setBackLight(_noActivitySleepScreenLevel);
}
}
}
"
Forgive my ignorance if I’ve missed something here. I don’t have the dev environment set-up to suggest these changes in GitHub.

On 25 Oct 2022, at 19:56, Ben Jones @.***> wrote:
This firmware is not really designed to work that way. It is more of a set of tools, which can be used with an external rules engine or server backend, to perform the clever stuff. So very little "smarts" or logic is built in, by design. Hope that makes sense.
—
Reply to this email directly, view it on GitHub https://github.com/OXRS-IO/OXRS-IO-TouchPanel-ESP32-FW/issues/47#issuecomment-1290216806, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2DSLVCQXYFYSEI6NKJKDWE6ODHANCNFSM6AAAAAARNOC76M.
You are receiving this because you authored the thread.

You raise a valid point - I will let @moinmoin-sh have a look and comment.

The backlight now has 2 clear operational states :
0 -> sleep (only set when timed out to sleep or set to sleep via cmnd/)
1 .. 100 -> awake (set by the slider or via cmnd/)
This results in  a retained backlight always in the range 1.. 100. (higher than sleep value)
When the sleep level would be adjustable things ar less distinct. Lets say the sleep level was set to 10 and the user set the actual backlight to 5. Now timeToSleep elapsed and the level would be set to 10 (so higher than it was set by the user). This could be intended behavior but also couldn't. To avoid such situations I would prefer to stay with the simple but easily predictable FW behavior and leave everything more advanced to the user (automation).
Sumnerboy has already explained our design goals.
I definately see your point but not sure how smart the TP schould be. We can leave this issue open and see if others jump in and vote for having this feature built in.

No activity for 10 months. I close it for now.


Exception from 'wallet'

Hi, I am getting this error after command farm summary:
Exception from 'wallet' {'error': '', 'success': False}
Farming status: Farming
Total achi farmed: Unknown
User transaction fees: Unknown
Block rewards: Unknown
Last height farmed: Unknown
Plot count: 100

I got the same exception


ANR with support library 26.1.0

This might have something to do with #116, or it may not. I get this just after adding the 0.2.0-SNAPSHOT dependency to the gradle.build file, without even having to create an instance of the LocationLayerPlugin.
A few notes
Since I moved to 26.1.0 I'm just extending a android.support.v4.app.Fragment instead of the LifecycleFragment. But I'm still using the following architecture components libraries:
// Architecture components
compile "android.arch.lifecycle:extensions:1.0.0-rc1"
compile "android.arch.persistence.room:runtime:1.0.0-rc1"
annotationProcessor "android.arch.persistence.room:compiler:1.0.0-rc1"

The problem happens when I get out of the app by pressing the back button and then come back to the app. The screen is white, nothing loads and eventually I get an "Application Not Responding" dialog.
This problem is not happening if I go back to support library 25.3.1.
If it helps, here's the ANR dump file.

We updated to the latest lifecylce components in 0.2.0 of the LocationLayerPlugin:
 lifecycleCompiler  : '1.0.0',
 lifecycleRuntime   : '1.0.3'

This version also contains 26.1.0 as a support lib version. Closing.


With multiple definitions "Go to definition" shows peek definition popup instead of going to definition

VSCode Version: 1.32.1 (1.32.1)
OS Version: 10.14.3 (18D109)

Steps to Reproduce:

happens sometimes when I work with JS files. I couldn't find a pattern in when it works and when it does not... It's extremely frustrating

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

Also happening on insiders.

It happens for TS files as well. Click to Go to Definition from context menu also shows definition popup.

That's the outcome of https://github.com/Microsoft/vscode/pull/68023. When having multiple definition of a symbol the following change was made:

before: open the nearest symbol and show peek at its position
after: show peek at position of request

So, this happens whenever multiple definitions of a symbol exist. Instead of making a decision where to go to first, VS Code now shows peeks without revealing one. After reading/hearing feedback I was under the assumption that is wanted but we can consider an options if people feel strong about restoring the previous, jump to nearest, definition behaviour.

"Go To" should work as "go to" I guess. Jumping to a nearest definition was the well-worked thing for me. Right now I always need to one additional mouse move + click every time I'm navigating to definitions. That's happening very often because jumping, for example, to any styled component in react application with types from DT always have two references, one reference is mine and one reference from DT:

Obviously the second one isn't interesting for me. So please add the option to restore the previous behaviour.

Shouldn't it go to the definition of the variable?
if I have declared a function/variable and exported, it seems going to the declaration make more sense no?

IMO, these changes are making VSCode less convenient.

Also what's the difference between "Goto Definition" and "Pick Definition" now, it seems they both do the same thing.

"Peek Definition" always shows the peek window, "Go To Definition" shows it when having multiple definitions. We didn't change that, what we have changed is that peek opens at the position of the request, not at the position of the first definition.
I will add a setting that allows to restore the old behaviour, to workaround until then, hit Enter and the the first definition will be revealed.

@jrieken I don't get the

"Go To Definition" shows it when having multiple definitions

part...
I don't see how a symbol (an import in JS in my case) can have multiple definitons.
for example:
export { Cart: createIcon(Cart) }

where createIcon is a HOC, that takes svg from elsewhere, and wraps it in some wrappers.
It seems to me that Cart's go to definition would take me to where Cart is defined, but instead this shows up:

I don't see how a symbol (an import in JS in my case) can have multiple definitons.

Let's keep that out of this issue. Generally, a symbol can have multiple definitions and this issue is about the UI for that case, e.g where to show peek for multiple symbols. If you disagree with how TypeScript computes definitions for a certain symbol and if you think it should be 1, not more, then we should move that into a separate issue.

With next Insiders build (tomorrow or sooner) there will be a new setting: editor.gotoLocation.many which controls what happens when encountering multiple definition/declarations of a symbols. Possible values are

'peek' (default) - Open peek with all results at the position of the request
'revealAndPeek' - Reveal the first result and open peek with all results there
'reveal' - Reveal the first result and ignore others


[FP]: CVE-2020-5408 on spring-security-crypto-5.7.8.jar

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:pivotal_software:spring_security:5.7.8:*:*:*:*:*:*:*
CVE
CVE-2020-5408
ODC Integration
{"label"=>"Maven Plugin"}
ODC Version
8.2.1
Description
I noted few False Positives, but it still get reported on maven plugin
Also there is another cpe cpe:2.3:a:vmware:spring_security:5.7.8:*:*:*:*:*:*:*

Sonatype's security team disagrees with Spring on whether this is fixed
See https://github.com/jeremylong/DependencyCheck/issues?q=is%3Aissue+CVE-2020-5408
The code was not removed nor disabled, but only 'deprecated for removal and documented to be insecure'. Only Spring 6.x includes a fix (removal of the code)


Make compilation files created by neuron_parallel_compile when used in real training.

As per title.

Additional context - for multi-node training with neuronx-nemo-megatron and neuronx-distributed, precompilation with neuron_parallel_compile is required (JiT compilation is not sufficient in these cases).
This enhancement will be required for larger models where multi-node will be the required setup.

Closing since this is available now.


Not working on IOS.

I am using the background mode plugin to send the notification(using Cordova local notification plugin) every hour to the user.
It is working brilliantly on the android. It sends me notification every hour.
But IOS is not doing so. Can somebody help me in solving the problem.

I am also using the background-mode plugin to send notification (using cordova local notification plugin) while the app is in the background. But this is not working on my iPod Touch 6Gen (iOS10)
Please help!!!

@preethu2325, @synfony I am going to fix iOS10 now.

So far it's working pretty well with iOS 10.x and the default web view, but not with the WKWebView-Engine.

Its just a single line of code but it cannot be done by plugin. When the native site of the plugin is created, it is already to late.
Inside the CDVWKWebViewEngine.m plugin file you have to add a line to the createConfigurationFromSettings method.
// CDVWKWebViewEngine.m

- (WKWebViewConfiguration*) createConfigurationFromSettings:(NSDictionary*)settings
{
    ...

    // add these line
    [configuration performSelector:NSSelectorFromString(@"_setAlwaysRunsAtForegroundPriority:")
                        withObject:[NSNumber numberWithBool:YES]
                        afterDelay:0];

    return configuration;
}

@preethu2325, @synfony From my side iOS seems to be fixed, especially WKWebView. Its also possible to schedule and trigger local-notification in background.

still not working on iOS 10.2. i'm i do something wrong?
here is the code:
cordova.plugins.backgroundMode.enable();
cordova.plugins.backgroundMode.onactivate = function () {
console.log('Background Mode');
};
i can't see any logs on safari web inspector console when press home button

problem solved.
it's because in ionic2, onactive() returns an observable, should use observable.subscribe()

Still not working in my ionic 1 app with iOS 10.x. Here there is my code in the app.js:
$ionicPlatform.ready(function () {

        try {

            document.addEventListener('deviceready', function () {

                // Enable background mode
                cordova.plugins.backgroundMode.enable();

                // Called when background mode has been activated
                cordova.plugins.backgroundMode.onactivate = function () {

                    // Set an interval of 3 seconds (3000 milliseconds)
                    setInterval(function () {
                        console.log('BACKGROUND SERVICE');

                        // The code that you want to run repeatedly

                    }, 3000);
                }
            }, false);

        }catch(e){
          /*discard*/
      }
    });


#723 Add breaking change to changelog

A breaking change, moving thumbnail_url and thumbnail_info inside content.info was merged without updating the changelog. This pull request updates the changelog.

Thanks for taking a look at this. I believe I've addressed the comments. Have I?


microsoft-edge: 119.0.2151.44 -> 119.0.2151.72

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for microsoft-edge is: The web browser from Microsoft
meta.homepage for microsoft-edge is: https://www.microsoft.com/en-us/edge
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 119.0.2151.72 with grep in /nix/store/bl4i90r7phcfhdmpq2l9fb1immswj8ia-microsoft-edge-stable-119.0.2151.72
found 119.0.2151.72 in filename of file in /nix/store/bl4i90r7phcfhdmpq2l9fb1immswj8ia-microsoft-edge-stable-119.0.2151.72

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
microsoft-edge
microsoft-edge-beta
microsoft-edge-dev

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bl4i90r7phcfhdmpq2l9fb1immswj8ia-microsoft-edge-stable-119.0.2151.72 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A microsoft-edge https://github.com/r-ryantm/nixpkgs/archive/e16bd4bfee30f8bba0315a98b2d1d2c85634fd57.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e16bd4bfee30f8bba0315a98b2d1d2c85634fd57#microsoft-edge

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bl4i90r7phcfhdmpq2l9fb1immswj8ia-microsoft-edge-stable-119.0.2151.72
ls -la /nix/store/bl4i90r7phcfhdmpq2l9fb1immswj8ia-microsoft-edge-stable-119.0.2151.72/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

microsoft-edge-beta
microsoft-edge-dev

1 package built:

microsoft-edge

Maintainer pings
cc @zanculmarktum @kuwii @rhysmdnz for testing.

done in https://github.com/NixOS/nixpkgs/pull/270331


Allow to set Ghost configuration in main script, when using npm module

Hi,
I'm using Ghost as an npm module to run different blogs on the same server. Each blog has its own script. I think it's unconvenient though to be forced to have the configuration in a separate file.
I would like to be able to have this code:
var ghost = require('ghost');
var path = require('path');

// Configuration parameters
var conf = {
  production: {
    url: 'http://myblog.com', // Blog url
    server: {
      host: '<IP_ADDRESS>', // Port that the server instance will be listening to
      port: '3000'
    },
    database: {
      client: 'sqlite3',
      connection: {
        filename: path.join(__dirname, '/content/data/ghost.db') // Database storage path
      },
      debug: false
    },
    paths: {
      contentPath: path.join(__dirname, '/content/') // Content storage path
    }
  }
};

// Start Ghost server
ghost({config: conf}).then(function (ghostServer) {
  ghostServer.start();
});

If I do it this way though I get this error: Possibly unhandled TypeError: path must be a string, which I think originates from the fact that the config property of the object passed to ghost() needs to be a string representing a path to the config file. Why not allowing though to directly pass the config object itself? Having both options would be the best imho.
Even better I'd like this API:
// Start Ghost server
ghost(conf).then(function (ghostServer) {
  ghostServer.start();
});

Where conf is the object defined in the first example.
Any chance this could be changed to avoid being forced to create multiple files when it's not needed?
If you'd like I can create a pr for this  :)
Thanks for putting together this awesome project!

Hi there @pensierinmusica, this issue is already raised here: #4731 and has 2 open pull requests: #4732 & #5047. Closing this as a duplicate, but please join the discussion on the other threads :+1:

@ErisDS thanks!


👾 [BUG] SkinnedMeshImporter - Liru3D dll does not work with Rider or Destop App (MonoGame pipline Loader)!

Describe the bug
Hello!
I tried to set my FBX Model to your SkinnedMeshImporter but it is not listen up.

I installed the Reference to:

Desktop (please complete the following information):

Windows
Version: 1.0.2

Error that i get:
 : warning : Failed to load assembly 'C:/Users/Elias/.nuget/packages/lovebirb.monogame.skinnedmeshimporter/1.0.2/lib/netstandard2.0/SkinnedMeshImporter.dll': Mindestens ein Typ in der Assembly kann nicht geladen werden.

Small Update:
If i open the Content Editor with VS it does work!
But allot of users don't use VS, so pls support by open the Editor with anything else like Rider or by default the MonoGame self (on destop)

With VS:

With Rider or Destop APP:

VS has 1 option more then Rider and Destop:
MGCB Editor (If you open the Editor with that it works fine)

But Rider and Destop don't have this, we just have (With that works it not, on VS to not(i tested it))

Rider / Destop

Setup a MonoGame Project the packet dotnet-mgcb-editor-windows get automatically created after setup your workspace.

Select your Content.mgcb and press for 2 Times Shift and go to the Actions Tabe and write in Associate with File Type  then select  Open matching files in associated application and press OK

Open your workspace in the Explorer and open the folder Content.

Open the Content.mgcb with C:\Users\Elias\.nuget\packages\dotnet-mgcb-editor-windows\<IP_ADDRESS>3\contentFiles\any\net6.0.mgcb-editor-windows.exe (If you not open with that one it not get listen up)

(FIXED)


Closing connection to ViGEmBus error

Describe the bug
I can connect the controller and it'll work for a while. Yet after a while the controller will loose connection and a message appears on the left side of the bottom bar, it reads "closing connection to ViGEmBus
To Reproduce
Steps to reproduce the behavior (example):

Start program
Plug in device '....'
See error after a bit

System details (please complete the following information):

OS: Fresh install of Windows 7 Ultimate
Feeder software: DS4Windows
Driver Version: 1.7.9

Additional context
I've never had this issue before reinstalling Windows.

Driver version 1.7.9, what? That's none of my released version numbers...

Whoops. Wrong ds4windows.


Bump dependencies related to 'Update framework version range'

$subject
Related issue

https://github.com/wso2/product-is/issues/15612

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4466376264


Unit test together client

There are currently no unit tests for the Together client.
This should be fixed.

I'll submit a PR if you're still looking for contributors!


Feature -> Add support for Live Activities for iOS

Proposal
Apple recently announced that iOS 16 Live Activities API is now available in beta for developers.
Source: https://developer.apple.com/news/?id=hi37aek8
It would be awesome if Flutter could add support for this feature for iOS users.

That will be awesome ! :D

It might make more sense to add support for this in a third party library like flutter_local_notifications

Yea you're right

If you didn't need Flutter in the extension it's pretty trivial to open `ios/Runner.xcworkspace and follow the instructions in https://developer.apple.com/documentation/activitykit/displaying-live-data-on-the-lock-screen-with-live-activities.
If you do want to use Flutter in the extension embedding it would be similar to https://docs.flutter.dev/development/platform-integration/ios/ios-app-clip.  Not sure if the live activities bundle has a size restriction though.

Hello 👋
I created a plugin to support iOS 16.1+ live activities & iPhone 14 Pro Dynamic Island feature 🙂
https://pub.dev/packages/live_activities
Any suggestion are welcome to improve this package 📦 !

live_activities has not been updated for a long time
Inspired by @istornz ,I created a more complete plugin: flutter_live_activities


Allocator shouldn't use drop to free itself

The Allocator struct using Rust dropping rather than manually freeing can have issues if it's dropped after the Vulkan instance, device, etc.. is dropped.
For example, say a program stored all of the Vulkan objects in a struct
struct VulkanThing{
  device: ash::Device
  allocator: vk_mem::Allocator
  ...
}

And the struct used a method to cleanup the program rather than using a drop
impl VulkanThing{
  pub fn cleanup(&mut self){
    self.device.destroy_device(...);
    ...
  }
}

This would result in an error as in this scenario below:
VulkanThing::init() // An allocator is created and put into struct
VulkanThing::cleanup() // Vulkan is unloaded

// Allocator is dropped here and an ERROR is raised

The error I get is User-mode data execution prevention (DEP) violation at 0x...
Instead of dropping, the option to manually free the allocator should be added such that the programmer can free the allocator in their cleanup method when the time is right.

It's also worth mentioning that a Vulkan Validation Layer will report unfree'd DeviceMemory if the Allocator is dropped after the device,

A user normally does this by wrapping their Allocator in ManuallyDrop.

Correct me if I'm wrong but that isn't documented anywhere right?
Perhaps users should be notified in the readme of this behavior?

If this library is well written it should have an unsafe constructor stating that vk::Device must not be destroyed before the Allocator to guarantee safe behaviour.

Like @MarijnS95 pointed out, the best way to resolve this issue is

In your VulkanThing, define the allocator to be before the device.

struct VulkanThing{
  device: ash::Device
  allocator: vk_mem::Allocator
  ...
}

Or even better, use ManuallyDrop.

It's inappropriate for vk-mem-rs to take ownership of the device because well, it's just the wrong place to own the device.
vk-mem-rs largely has the same level of memory safety guarantees as ash, so it's really the users responsibility to ensure that things are dropped in the correct order.
However, @MarijnS95  did have a point. I've marked the Allocator::new function as unsafe and documented the expected lifetime for the device and instance handles.
I will be closing this for now. If you have a better solution for this, feel free to open a PR.

Struct definition order makes no difference because ash::Device intentionally doesn't implement Drop semantics. When calling instance.destroy_device() in impl Drop for VulkanThing you still have to manually make sure vk_mem::Allocator is dropped beforehand via ManuallyDrop<>.

@Neo-Zhixing you might want to look at how your docs render. Not having an empty newline makes the text render as one crammed-together paragraph.
Safety docs typically use a heading like # Safety anyway.

That's a good point. Thanks


Looking for a ChromaDB Client Similar to pgAdmin or MongoDB Studio

I am currently working with ChromaDB for a project and I'm in need of a user-friendly client tool that can provide a graphical interface for managing and interacting with my ChromaDB instance. Much like pgAdmin for PostgreSQL and MongoDB Studio for MongoDB, I'm hoping to find a dedicated client that offers features like browsing, querying, and modifying data, as well as managing database configurations.
If anyone is aware of a ChromaDB client that fits this description, I would greatly appreciate your recommendations. Open-source options are preferred, but any suggestions for reliable client tools that streamline ChromaDB administration would be incredibly valuable. Thank you in advance for your assistance!

@dineshsonachalam check out https://twitter.com/tcarambat/status/1684614486798565376!


Setup project environment

Introduce more branches

main
backend-testing
frontend-testing

Create a skeleton of the code

Initialize an empty buildable project running on OpenJDK 18.0.1, Maven 4.0.0 and Springboot
Configure pom.xml: Add JUnit 5.8 and log4j2 dependencies, create Application class with main() method
Add .gitignore, README.md and LICENSE files

Setup GitHub repository

Configure project deployment with Maven in GitHub Actions
Configure repository security features in GitHub Security

Setup WebServer and DataSource

Download, install PostgreSQL 14.3 and latest JDBC
Integrate empty datasource into the project locally
Download Apache tomcat 10 and configure it

Done

Done


Carthage

Leave branch open until next major release to allow carthage to build shared target directly from this branch.


window.menuBarVisibility="hidden" opens with Alt+F and stays open

When the menu bar is configured to be hidden, I'd expect it to stay hidden and to disappear, after I accessed the File menu directly with Alt+F (or Alt+E for Edit, or Alt+S for Selection, ...; you know, the underlined letter in the menu items name—I'm sure this feature has a name).
I could use "toggle" visibility, but that interacts annoyingly with desktop switching (#22488) and accidental Alt key presses (#35010). My current workaround is to set menuBarVisibility to "visible" or "toggle", save config, change menuBarVisibility back to "hidden" and save again. But that just takes too much time, even if I only need to access the menu every once in a while.

VSCode Version: 1.23.1 (d0182c3417d225529c6d5ad24b7572815d0de9ac)
OS Version: Debian Linux, Stretch, 9.4

Steps to Reproduce:

Configure window.menuBarVisibility to "hidden".
Press Alt+F (File menu opens)
Press Esc (or close the menu otherwise, i.e. by clicking into to editor, Alt-Tabbing to other applications)
Menu stays open, can't be closed ("View: Toggle Menu Bar" command does nothing)

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

I believe, #22487 covers it.


Add BPF and kvstore count/latency metrics

This change is

test-me-please

Coverage increased (+0.04%) to 43.051% when pulling 49e1587017b6e2e9841ea4ba2fe716718fe5c928 on pr/tgraf/more-metrics into b20b8e52fd5b4cfd48840f3f85e011d3af8dcd47 on master.

Coverage increased (+0.04%) to 43.055% when pulling 49e1587017b6e2e9841ea4ba2fe716718fe5c928 on pr/tgraf/more-metrics into b20b8e52fd5b4cfd48840f3f85e011d3af8dcd47 on master.


I stuck in "make"

cc  -O3  jpeg.o codec.o huffman.o io.o chendct.o leedct.o lexer.o marker.o stream.o transform.o -lm -o jpeg
lexer.o: file not recognized: 不可识别的文件格式
collect2: error: ld returned 1 exit status
makefile:30: recipe for target 'jpeg' failed
make: *** [jpeg] Error 1

I got similar error. Try the command "make clean" before "make".

I got similar error. Try the command "make clean" before "make".

Thanks. I have fixed it


Requests

(can post requests here)
Some ideas for now

Stringbuilder example for concatenation without garbage collection problems
Camera controllers for common use (like: orbit, fly, lookaround, follow..)
Mathi. library (same as Mathf. but just for ints, should be faster without using System.Math. that Mathf. uses) *maybe can use SIMD later also?

old post cleanup, and better to have separate issues for each topic

@unitycoder Nice job. i wanted to suggest you.


Make simple url rule with default parameter

Currently, to make url rule with default parameter, we must do this
'rules' => [
    ...
    [
        'pattern' => 'about',
        'route' => 'site/page',
        'defaults' => ['view' => 'about']
    ]
]

IMO, its more simple if we just do this
'rules' => [
    'about' => ['site/page', 'view' => 'about']
]

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Fixed issues

I am against introducing another way of expressing the same thing. There are already two different syntaxes for Url rules. A third one just makes it even more complicated.

Agree. Let's not introduce it.


Rw expand x axis capabilities

diff starts here https://github.com/eventbrite/britecharts/compare/master...ryanwholey:rw-expand-x-axis-capabilities#diff-1be418fa346b7410a50fd56a54f59ff4
we need to fix this build system :(

LGTM


Misspelling in Sentence

Changed "Additonally" to "Additionally,".

Hi @mikhailalmeida, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@mikhailalmeida : Thanks for your contribution to the Azure documentation! The author, @telmosampaio, has been notified to review your proposed change.

@telmosampaio
Simple typo fix. I confirmed nothing else was done. I'm accepting this.

@mikhailalmeida
Good catch! Thank you for your contribution to Azure documentation.
--Carolyn

@sign-off


Add setting to skip hosted cluster chart installation

In the current implementation, it's not possible to install a custom helm chart for hosted providers. When a cluster is created,   helm chart from the upstream repo will be installed.
We need a way to install custom charts that are built for every PR as part of our e2e test suite https://github.com/rancher/aks-operator/blob/master/.github/workflows/e2e.yaml.
Providing an alternative helm chart repository will not work for us.
This PR adds a new setting for skipping helm chart installation and will be used for development purposes only.
Issue: https://github.com/rancher/highlander/issues/4

CI needs to be fixed on this one, I can't re-run it though for some reason, can someone else try?

The job that fails breaks during the build, it doesn't even start the tests. It's likely not caused by this PR.

The tests are flakey. I had to restart them multiple times to get them green.


Freerdp2-wayland crashes when scrolling

Describe the bug
When connected to my windows 11 machine from my Artix laptop, when I scroll using either the trackpad or a mouse freerdp immediately crashes. This only happens on wayland mode. xfreerdp does not crash while scrolling. This error happens no matter the command line arguments.
To Reproduce
Steps to reproduce the behavior:

Connect to remote machine using wlfreerdp /u:username /p:password /v:<IP_ADDRESS>
Scroll using either the trackpad or mouse

Expected behavior
Whatever window is open scrolls and freerdp does not crash.
Screenshots
If applicable, add screenshots to help explain your problem.
Application details

FreeRDP version 2.11.1
wlfreerdp /u:username /p:password /v:<IP_ADDRESS>
Build options: https://gist.github.com/karstenes/e97e546803657b9d193b0bd4f1999713
Connecting to Windows 11 22H2 22621.2283
Log: https://gist.github.com/karstenes/2b483c1600eb216e5b39662774837548
Default arch linux build of freerdp

Environment (please complete the following information):

OS: Linux
Version/Distribution: Artix Linux, Open-RC
Architecture: amd64
Kernel: 6.5.2-artix1-1 #1 SMP PREEMPT_DYNAMIC Fri, 08 Sep 2023 13:16:06 +0000 x86_64 GNU/Linux

duplicate #9377


Infrastructure creation failed. Reason: null

Hi,
I am currently trying to deploy a Hadoop Cluster using Cloudbreak 1.2.1 with the blueprint hdp-small-default over Openstack and I get the following errors in logs.
I have observed there is Java NullPointerException during the process but not sure to what extent this is relevant to the issue.
Any idea how could I fix that ?
Thanks!
Erwan
================
cloudbreak_1 | 2016-04-15 08:58:28,761 [reactorDispatcher-52] accept:47 DEBUG c.s.c.c.f.Flow2Handler - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] flowcontrol event arrived: key: LAUNCHSTACKRESULT_ERROR, flowid: 2786c842-bf9f-45ab-b33a-837cb01c90fe, payload: LaunchStackResult{status=FAILED, statusReason='', errorDetails=java.lang.NullPointerException, request=CloudStackRequest{, cloudStack=CloudStack{groups=[com.sequenceiq.cloudbreak.cloud.model.Group@1ced9003, com.sequenceiq.cloudbreak.cloud.model.Group@3089c3cb, com.sequenceiq.cloudbreak.cloud.model.Group@24955d52, com.sequenceiq.cloudbreak.cloud.model.Group@4a21c541, com.sequenceiq.cloudbreak.cloud.model.Group@6f1d546c, com.sequenceiq.cloudbreak.cloud.model.Group@6e91b771], network=com.sequenceiq.cloudbreak.cloud.model.Network@20a2946d, security=Security{rules=[SecurityRule{cidr='<IP_ADDRESS>/0', ports='[Ljava.lang.String;@11be90d8', protocol='tcp'}]}, image=com.sequenceiq.cloudbreak.cloud.model.Image@76175e01}}, results=null}
cloudbreak_1 | 2016-04-15 08:58:28,803 [reactorDispatcher-52] getResourceDefinition:28 DEBUG c.s.c.s.s.r.d.ResourceDefinitionService - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Sending request for OPENSTACK credential resource property definition
cloudbreak_1 | 2016-04-15 08:58:28,804 [reactorDispatcher-53] buildLogContextForReactorHandler:54INFO  c.s.c.l.LogContextAspects - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] A Reactor event handler's 'accept' method has been intercepted: execution(Consumer.accept(..)), MDC logger context is built.
cloudbreak_1 | 2016-04-15 08:58:28,805 [reactorDispatcher-53] accept:30 INFO  c.s.c.c.h.ResourceDefinitionHandler - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Received event: Event{id=null, headers=null, replyTo=null, key=RESOURCEDEFINITIONREQUEST, data=GetResourceDefinition{platform='{platform='OPENSTACK', variant=''}', resource='credential'}}
cloudbreak_1 | 2016-04-15 08:58:28,805 [reactorDispatcher-52] getResourceDefinition:34 INFO  c.s.c.s.s.r.d.ResourceDefinitionService - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Resource property definition: ResourceDefinitionResult{definition='{"values":[{"name":"userName","type":"String","encrypted":true},{"name":"password","type":"String","encrypted":true},{"name":"endpoint","type":"String"},{"name":"keystoneVersion","type":"String"}],"selectors":[{"name":"cb-keystone-v2","values":[{"name":"tenantName","type":"String"}]},{"name":"cb-keystone-v3","values":[{"name":"userDomain","type":"String"},{"name":"keystoneAuthScope","type":"String"}]},{"name":"cb-keystone-v3-default-scope","parent":"cb-keystone-v3","values":[]},{"name":"cb-keystone-v3-domain-scope","parent":"cb-keystone-v3","values":[{"name":"domainName","type":"String"}]},{"name":"cb-keystone-v3-project-scope","parent":"cb-keystone-v3","values":[{"name":"projectDomainName","type":"String"},{"name":"projectName","type":"String"}]}]}'}
cloudbreak_1 | 2016-04-15 08:58:28,824 [reactorDispatcher-52] getImage:57 DEBUG c.s.c.s.i.ImageService - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Image found! stackId: 3, component: Component{id=2, componentType=IMAGE, name='IMAGE'}
cloudbreak_1 | 2016-04-15 08:58:28,839 [reactorDispatcher-52] handleStackCreationFailure:152 ERROR c.s.c.c.f.s.p.a.StackCreationService - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Error during stack creation flow:
cloudbreak_1 | java.lang.NullPointerException: null
cloudbreak_1 |  at com.sequenceiq.cloudbreak.cloud.openstack.heat.OpenStackResourceConnector.launch(OpenStackResourceConnector.java:68) ~[cloud-openstack-1.2.4.jar!/:na]
cloudbreak_1 |  at com.sequenceiq.cloudbreak.cloud.handler.LaunchStackHandler.accept(LaunchStackHandler.java:69) ~[cloud-reactor-1.2.4.jar!/:na]
cloudbreak_1 |  at com.sequenceiq.cloudbreak.cloud.handler.LaunchStackHandler.accept(LaunchStackHandler.java:33) ~[cloud-reactor-1.2.4.jar!/:na]
cloudbreak_1 |  at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source) ~[na:na]
cloudbreak_1 |  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_79]
cloudbreak_1 |  at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_79]
cloudbreak_1 |  at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
cloudbreak_1 |  at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
cloudbreak_1 |  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
cloudbreak_1 |  at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:52) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
cloudbreak_1 |  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
cloudbreak_1 |  at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
cloudbreak_1 |  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
cloudbreak_1 |  at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:208) ~[spring-aop-4.2.4.RELEASE.jar!/:4.2.4.RELEASE]
cloudbreak_1 |  at com.sun.proxy.$Proxy199.accept(Unknown Source) ~[na:na]
cloudbreak_1 |  at reactor.bus.EventBus$3.accept(EventBus.java:317) [reactor-bus-2.0.7.RELEASE.jar!/:na]
cloudbreak_1 |  at reactor.bus.EventBus$3.accept(EventBus.java:310) [reactor-bus-2.0.7.RELEASE.jar!/:na]
cloudbreak_1 |  at reactor.bus.routing.ConsumerFilteringRouter.route(ConsumerFilteringRouter.java:72) [reactor-bus-2.0.7.RELEASE.jar!/:na]
cloudbreak_1 |  at reactor.bus.routing.TraceableDelegatingRouter.route(TraceableDelegatingRouter.java:51) [reactor-bus-2.0.7.RELEASE.jar!/:na]
cloudbreak_1 |  at reactor.bus.EventBus.accept(EventBus.java:591) [reactor-bus-2.0.7.RELEASE.jar!/:na]
cloudbreak_1 |  at reactor.bus.EventBus.accept(EventBus.java:63) [reactor-bus-2.0.7.RELEASE.jar!/:na]
cloudbreak_1 |  at reactor.core.dispatch.AbstractLifecycleDispatcher.route(AbstractLifecycleDispatcher.java:160) [reactor-core-2.0.7.RELEASE.jar!/:na]
cloudbreak_1 |  at reactor.core.dispatch.MultiThreadDispatcher$MultiThreadTask.run(MultiThreadDispatcher.java:74) [reactor-core-2.0.7.RELEASE.jar!/:na]
cloudbreak_1 |  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_79]
cloudbreak_1 |  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_79]
cloudbreak_1 |  at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
cloudbreak_1 | 2016-04-15 08:58:28,839 [reactorDispatcher-52] fireEventAndLog:203 DEBUG c.s.c.c.f.s.p.a.StackCreationService - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] STACK_INFRASTRUCTURE_CREATE_FAILED [STACK_FLOW_STEP].
cloudbreak_1 | 2016-04-15 08:58:28,839 [reactorDispatcher-52] fireCloudbreakEvent:51 INFO  c.s.c.s.e.DefaultCloudbreakEventService - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Firing Cloudbreak event: CloudbreakEventData{entityId=3, eventType='UPDATE_IN_PROGRESS', eventMessage='Infrastructure creation failed. Reason: null'}
cloudbreak_1 | 2016-04-15 08:58:28,840 [reactorDispatcher-52] handleFailure:188 DEBUG c.s.c.c.f.s.p.a.StackCreationService - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Nothing to do. OnFailureAction DO_NOTHING
cloudbreak_1 | 2016-04-15 08:58:28,840 [reactorDispatcher-54] accept:33 INFO  c.s.c.s.e.CloudbreakEventHandler - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Handling cloudbreak event: Event{id=null, headers=null, replyTo=null, key=CLOUDBREAK_EVENT,data=CloudbreakEventData{entityId=3, eventType='UPDATE_IN_PROGRESS', eventMessage='Infrastructure creation failed. Reason: null'}}
cloudbreak_1 | 2016-04-15 08:58:28,841 [reactorDispatcher-54] accept:36 INFO  c.s.c.s.e.CloudbreakEventHandler - [owner:undefined] [type:CLOUDBREAKEVENTDATA] [id:undefined] [name:undefined] Persisting data: CloudbreakEventData{entityId=3, eventType='UPDATE_IN_PROGRESS', eventMessage='Infrastructure creation failed. Reason: null'}
cloudbreak_1 | 2016-04-15 08:58:28,841 [reactorDispatcher-54] createStackEvent:66 DEBUG c.s.c.s.e.DefaultCloudbreakEventService - [owner:undefined] [type:CLOUDBREAKEVENTDATA] [id:undefined] [name:undefined] Creating stack event from: CloudbreakEventData{entityId=3, eventType='UPDATE_IN_PROGRESS', eventMessage='Infrastructure creation failed. Reason: null'}
cloudbreak_1 | 2016-04-15 08:58:28,883 [reactorDispatcher-54] createStackEvent:71 INFO  c.s.c.s.e.DefaultCloudbreakEventService - [owner:undefined] [type:CLOUDBREAKEVENTDATA] [id:undefined] [name:undefined] Created stack event: CloudbreakEvent{id=4, eventType='UPDATE_IN_PROGRESS', eventTimestamp=Fri Apr 15 08:58:28 UTC 2016, eventMessage='Infrastructure creation failed. Reason: null',owner='a3beda67-ebbb-4bba-b16c-ca7d73e26e88', account='seq1234567', cloud='OPENSTACK', region='local', blueprintName='hdp-small-default', instanceGroup='null', blueprintId=1', stackId=3', clusterId=2', clusterName=demo-cluster-2}
cloudbreak_1 | 2016-04-15 08:58:28,884 [reactorDispatcher-54] accept:38 INFO  c.s.c.s.e.CloudbreakEventHandler - [owner:undefined] [type:CLOUDBREAKEVENTDATA] [id:undefined] [name:undefined] Sending notification with data: CloudbreakEvent{id=4, eventType='UPDATE_IN_PROGRESS', eventTimestamp=Fri Apr 15 08:58:28 UTC 2016, eventMessage='Infrastructure creation failed. Reason: null', owner='a3beda67-ebbb-4bba-b16c-ca7d73e26e88', account='seq1234567', cloud='OPENSTACK', region='local',blueprintName='hdp-small-default', instanceGroup='null', blueprintId=1', stackId=3', clusterId=2', clusterName=demo-cluster-2}
cloudbreak_1 | 2016-04-15 08:58:28,899 [reactorDispatcher-52] fireEventAndLog:203 DEBUG c.s.c.c.f.s.p.a.StackCreationService - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] STACK_INFRASTRUCTURE_CREATE_FAILED [STACK_FLOW_STEP].
cloudbreak_1 | 2016-04-15 08:58:28,899 [reactorDispatcher-52] fireCloudbreakEvent:51 INFO  c.s.c.s.e.DefaultCloudbreakEventService - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Firing Cloudbreak event: CloudbreakEventData{entityId=3, eventType='CREATE_FAILED', eventMessage='Infrastructure creation failed. Reason: null'}
cloudbreak_1 | 2016-04-15 08:58:28,899 [reactorDispatcher-52] sendEvent:56 INFO  c.s.c.c.f.AbstractAction - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2]Triggering event: com.sequenceiq.cloudbreak.core.flow2.stack.FlowFailureEvent@54075261
cloudbreak_1 | 2016-04-15 08:58:28,900 [reactorDispatcher-55] accept:33 INFO  c.s.c.s.e.CloudbreakEventHandler - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] Handling cloudbreak event: Event{id=null, headers=null, replyTo=null, key=CLOUDBREAK_EVENT,data=CloudbreakEventData{entityId=3, eventType='CREATE_FAILED', eventMessage='Infrastructure creation failed. Reason: null'}}
cloudbreak_1 | 2016-04-15 08:58:28,900 [reactorDispatcher-55] accept:36 INFO  c.s.c.s.e.CloudbreakEventHandler - [owner:undefined] [type:CLOUDBREAKEVENTDATA] [id:undefined] [name:undefined] Persisting data: CloudbreakEventData{entityId=3, eventType='CREATE_FAILED', eventMessage='Infrastructure creation failed. Reason: null'}
cloudbreak_1 | 2016-04-15 08:58:28,900 [reactorDispatcher-55] createStackEvent:66 DEBUG c.s.c.s.e.DefaultCloudbreakEventService - [owner:undefined] [type:CLOUDBREAKEVENTDATA] [id:undefined] [name:undefined] Creating stack event from: CloudbreakEventData{entityId=3, eventType='CREATE_FAILED', eventMessage='Infrastructure creation failed. Reason: null'}
cloudbreak_1 | 2016-04-15 08:58:28,900 [reactorDispatcher-52] stateChanged:82 INFO  c.s.c.c.f.s.p.StackCreationFlowConfig - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] StackCreationFlow changed from ObjectState [getIds()=[START_PROVISIONING_STATE],getClass()=class org.springframework.statemachine.state.ObjectState, hashCode()=689975318, toString()=AbstractState [id=START_PROVISIONING_STATE, pseudoState=null, deferred=null, entryActions=[com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StartProvisioningAction@350972], exitActions=null, regions=[], submachine=null]] to ObjectState [getIds()=[STACK_CREATION_FAILED_STATE], getClass()=class org.springframework.statemachine.state.ObjectState, hashCode()=1600144645, toString()=AbstractState [id=STACK_CREATION_FAILED_STATE, pseudoState=null, deferred=null, entryActions=[com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationFailureAction@7ea50c74], exitActions=null, regions=[], submachine=null]]
cloudbreak_1 | 2016-04-15 08:58:28,901 [reactorDispatcher-56] accept:47 DEBUG c.s.c.c.f.Flow2Handler - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] flowcontrol event arrived: key: FAILHANDLED, flowid: 2786c842-bf9f-45ab-b33a-837cb01c90fe, payload:com.sequenceiq.cloudbreak.core.flow2.stack.FlowFailureEvent@54075261
cloudbreak_1 | 2016-04-15 08:58:28,901 [reactorDispatcher-56] sendEvent:56 INFO  c.s.c.c.f.AbstractAction - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2]Triggering event: com.sequenceiq.cloudbreak.core.flow2.stack.FlowFailureEvent@54075261
cloudbreak_1 | 2016-04-15 08:58:28,902 [reactorDispatcher-56] stateChanged:82 INFO  c.s.c.c.f.s.p.StackCreationFlowConfig - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] StackCreationFlow changed from ObjectState [getIds()=[STACK_CREATION_FAILED_STATE], getClass()=class org.springframework.statemachine.state.ObjectState, hashCode()=1600144645, toString()=AbstractState [id=STACK_CREATION_FAILED_STATE, pseudoState=null, deferred=null, entryActions=[com.sequenceiq.cloudbreak.core.flow2.stack.provision.action.StackCreationFailureAction@7ea50c74], exitActions=null, regions=[], submachine=null]] to ObjectState [getIds()=[FINAL_STATE], getClass()=class org.springframework.statemachine.state.ObjectState, hashCode()=3095445, toString()=AbstractState [id=FINAL_STATE, pseudoState=org.springframework.statemachine.state.DefaultPseudoState@1cf0b34b, deferred=null, entryActions=[com.sequenceiq.cloudbreak.core.flow2.FlowFinalizeAction@3a04c35d], exitActions=null, regions=[], submachine=null]]
cloudbreak_1 | 2016-04-15 08:58:28,902 [reactorDispatcher-56] stop:127 INFO  o.s.s.s.LifecycleObjectSupport - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] stopped org.springframework.statemachine.support.DefaultStateMachineExecutor@1eb53f7b
cloudbreak_1 | 2016-04-15 08:58:28,902 [reactorDispatcher-57] accept:56 DEBUG c.s.c.c.f.Flow2Handler - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] flowfinalizing arrived: id: 2786c842-bf9f-45ab-b33a-837cb01c90fe
cloudbreak_1 | 2016-04-15 08:58:28,902 [reactorDispatcher-56] stop:127 INFO  o.s.s.s.LifecycleObjectSupport - [owner:a3beda67-ebbb-4bba-b16c-ca7d73e26e88] [type:STACK] [id:3] [name:demo-cluster-2] stopped PROVISIONING_FINISHED_STATE START_PROVISIONING_STATE SETUP_STATE IMAGE_CHECK_STATE IMAGESETUP_STATE STACK_CREATION_FAILED_STATE TLS_SETUP_STATE FINAL_STATE INIT_STATE COLLECTMETADATA_STATE  /  / id=b08412b4-ab37-40d5-a19b-d53f2e923bdf
cloudbreak_1 | 2016-04-15 08:58:28,930 [reactorDispatcher-55] createStackEvent:71 INFO  c.s.c.s.e.DefaultCloudbreakEventService - [owner:undefined] [type:CLOUDBREAKEVENTDATA] [id:undefined] [name:undefined] Created stack event: CloudbreakEvent{id=5, eventType='CREATE_FAILED', eventTimestamp=Fri Apr 15 08:58:28 UTC 2016, eventMessage='Infrastructure creation failed. Reason: null', owner='a3beda67-ebbb-4bba-b16c-ca7d73e26e88', account='seq1234567', cloud='OPENSTACK', region='local',blueprintName='hdp-small-default', instanceGroup='null', blueprintId=1', stackId=3', clusterId=2', clusterName=demo-cluster-2}
cloudbreak_1 | 2016-04-15 08:58:28,930 [reactorDispatcher-55] accept:38 INFO  c.s.c.s.e.CloudbreakEventHandler - [owner:undefined] [type:CLOUDBREAKEVENTDATA] [id:undefined] [name:undefined] Sending notification with data: CloudbreakEvent{id=5, eventType='CREATE_FAILED', eventTimestamp=Fri Apr 15 08:58:28 UTC 2016, eventMessage='Infrastructure creation failed. Reason: null', owner='a3beda67-ebbb-4bba-b16c-ca7d73e26e88', account='seq1234567', cloud='OPENSTACK', region='local', blueprintName='hdp-small-default', instanceGroup='null', blueprintId=1', stackId=3', clusterId=2', clusterName=demo-cluster-2}

Which version of Openstack are you using?

This is Openstack Juno.
Also one information in case it can help : we have a proxy and need to do some special configuration in Openstack in case the deployment needs to do connection to internet. Is it the case or everything happens internal ?

deployment needs connection with you openstack cluster. The internet needs just for the deployed nodes because ambari installing the packages from the central yum repositories.
Could you please send us the whole log ? my mail is<EMAIL_ADDRESS>Br,
R

Ok, I have just sent you the complete log to your mail. Hope this will help.

If you are using Openstack there are two option to provision a VM.
First when you provision a VM with heat templates. As I see your Openstack not supporting Heat templates or it is just simply not enabled.
If you dont want to enabled this feature in Openstack, then use the native implementation option which is available if you clicking on the 'Show Advanced Options' button on the cluster creation form.
Br,
R

Thank you for your answer. You are right that Heat templates are not enabled on this Openstack so this was the reason.
I used the "native" option as suggested which sorted out the issue. I faced few other issues due to setup of network and instances definition (size of disk had to be 100GB) which was not due to Cloudbreak but only configuration on the side of Openstack and finally it all worked fine and could deploy the first cluster successfully!


[Feature Request] More complete Rust SDK Workflow Options

Is your feature request related to a problem? Please describe.
Many options for starting workflows are missing.
Describe the solution you'd like
More of the options made available through the WorkflowOption struct.

closing for now after #365


Laggy First Keyboard Open (Physical iOS Device)

Steps to reproduce
checkout https://github.com/willsmanley/flutter-textfield-keyboard-ios-bug
run on a physical ios device (with either impeller or skia)
press the textfield to focus it and trigger a keyboard open. the first time during app run takes 2 second lag. every subsequent time is immediate.
note: it only happens the very first time you open the keyboard. hot restarting and hot reloading will not reset this. only by rebuilding can you experience the lag again.
Expected results
should open immediately like native swift apps
Actual results
opens keyboard after 1-2 second delay
Code sample
https://github.com/willsmanley/flutter-textfield-keyboard-ios-bug
Screenshots or Video
No response
Logs
n/a
Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.27.0, on macOS 15.1 24B2082 darwin-arm64, locale en-US)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/to/macos-android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[!] Android Studio (not installed)
[✓] Connected device (6 available)
[✓] Network resources

! Doctor found issues in 2 categories.

Hi @willsmanley, do you get the same issue in release mode or is this only in debug mode?

Also in profile/release mode


Graphical glitches in search

When typing in a search term, sometimes graphical glitches on the command line occur; e.g. when typing "/acdc", it displays "/ac█c" sometimes.

There have been major improvements on the line editor lately.  Can you still reproduce this?

@johannes87 I can't reproduce this.  Please re-open if it's still an issue.


Add domain ktepcknute.kyiv.ua

@PrimeGlorious I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host ktepcknute.ua not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Is 'trade --buy_pct X' doing what it's supposed to do?

Hi,
I'm trading with the option --buy_pct 50. I was expecting that this would use 50% of the balance in my account to buy cryptocurrency. Apparantly, it's still using 100%. Am I doing something wrong or did I misunderstand this option (or could it be a bug)? Thanks in advance!

This is discussed in https://github.com/carlos8f/zenbot/issues/174
The current implementation uses 50% (from your example) per trade.


How to update typeahead list when click on show more button?

Questions of this nature are best posted to StackOverflow as explained here.
In the future, please do not use the issues forum for support related requests.

:-1:


Clarify backup structure

We no longer require the use of subfolders for files in Cloud v4, though we still generate backups in that format to be compatible with Cloud v3. I don't know whether the phrasing I've used is clear enough, but at least this should make life a lot easier for customers migrating from on-prem / Mendix Private Cloud to Cloud v4.

Hi Joey (@jeohist)
This section is specifically about the format of the backup file, so even for Cloud V4 the format of the backup will be as described in the documentation, if I understand what you say above.
Are you saying that when the backup is restored to Cloud V4 that this folder structure is not implemented as it is stored in the backup file but that the files are flattened out and all put in the same folder in the blob storage? In other words, that the restored backup won't look the same as the backup?
What happens when the backup is restored to a non-Mendix cloud - such as Mx4PC? Does it flatten the structure or keep it?

@jeohist - can you let me know about the comment above. I'd like to improve the documentation, but I need to be clearer what we are saying about the structure of the backup file and how it relates to the structure in the deployed app.
Thanks

@MarkvanMents This PR was intended more as a way to show that the tree structure is optional for Cloud v4. I don't know whether this also applies to Mendix for Private Cloud. The reason for this PR was to make it easier for people to migrate from Mendix for Private Cloud to Cloud v4 (putting backups into the tree structure is a bit of an annoyance), maybe we can rewrite the text to reflect that.

@jeohist So is the structure of the S3 files in the backup just the same as the structure that it had on disk (whatever that was)? Or does the Mendix backup create this structure in case the backup needs to be restored to a V3 node?
I was under the (probably mistaken) impression that the backup was created in this format on purpose, but are you saying that the backup was only in this format because it was a V3 backup and I would have seen something different for a V4  backup?
(I'm all for making things easier for customers - which is why I want to make it as clear as possible).
Thanks for getting back to me on this.

@jeohist
Hi Joey,
Can we have a quick call about this. I think we can resolve it in 10 minutes rather than having discussions here and in Slack?


Fix: Code block color to improve contrast

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #37153

Hey @dboydgit thanks for the pull-request, do you mind posting a screenshot in here, in the comments for a quick look for us?

Sure, here is what the code blocks look like after the updates

I've made those updates, layout now looks like

You may need to run a check on the linting.

I think there was an errant } in the first commit. Second commit should be OK.

I think there was an errant } in the first commit. Second commit should be OK.

Great thanks for confirming and fixing it :)

:sparkles: :sparkles: AWESOME! LGTM. :sparkles: :sparkles:
Thanks @dboydgit, for this pull request and contributing to the code-base for the first time.
We will be looking forward for more contributions in future.
Cheers and happy contributing!


add app.openshift.io/runtime label to resources created by odo

/kind user-story
User Story
As an odo and ODC user, I want to see language/framework icons in ODC topology view So that I can quickly recognize what is running and so that I have a consistent view with components created by ODC.

The left is the component with the correct labels deployed with ODC, the right is nodejs component deployed using odo dev
Acceptance Criteria

[ ] odo dev should add app.openshift.io/runtime label  to all resources created with value of metadata.language field in devfile.yaml
[ ] odo deploy should add app.openshift.io/runtime label  to all resources created with value of metadata.language field in devfile.yaml

/kind user-story
/priority medium

What value should be assigned to the label? Language? Project Type? Some devfiles have icon matching language, some with project type.


Fix wording of default behavior for namespaces option

What does this PR do?
Fix the wording of the default behaviour for the namespaces config key for the K8s provider.
Motivation

More

[ ] Added/updated tests
[X] Added/updated documentation

Additional Notes

Congrats on merging your first pr with us @markormesher! Thanks!


[Cosmos DB] Adding the extension for cosmosdb point in time restore

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

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

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

Cosmos DB

Seeing the other names in this file, I think we can name ours as cosmosdb-preview

Refers to: .github/CODEOWNERS:172 in 07dbfe4. [](commit_id = 07dbfe47291c4b0933f379ec4092954c69356ba0, deletion_comment = False)

https://github.com/Azure/azure-cli-extensions/pull/2791/#issuecomment-748396090
@MehaKaushik, I can see multiple extensions to the same component.
For example, az monitor has multiple extensions.
It might be easier for us to have separate extensions for each feature.
@Juliehzl, do you have any suggestion here?
Do you recommend us to have just one extension for whole cosmosdb? Or create one extension for a specific feature?


Heads-up - Code upload to ASF early next week (2016/03/07).

FYI
Now that the CCLA has be received by the ASF the code can be uploaded to the ASF repo.
I'm planning to do this early next week (March 7th or 8th).
There may still be a short period while this Quarks github repo is the one to use for active development, until we understand the process of making changes using git at the ASF (and mirroring of the repo to github). Any changes made in that period here after the initial code drop to the ASF would be migrated to the ASF repo.
Code being at the ASF is one of the requirements to fulfill before the project can use the Apache name.
http://mail-archives.apache.org/mod_mbox/incubator-quarks-dev/201603.mbox/<CAFFD%2B2zNBLF7fvz4bnasMM_0d4PvMot%3DySVx-MpL940LCDYjMA%40mail.gmail.com>

Code is now uploaded to ASF - details at:
https://issues.apache.org/jira/browse/QUARKS-1


Name input support

name field does not support the following names:

J.P. Morgan
D’Angelo
Mary-Jane Thompson
X Æ A-12 Musk.

Not gonna allow X Æ A-12 Musk, let's focus on English support first.


Recursive layout in app/src/main/res/layout/content_another.xml

content_another.xml in the sample app includes itself
https://github.com/Countly/countly-sdk-android/blob/master/app/src/main/res/layout/content_another.xml#L23
This will cause build process daemon crashes with cryptic error messages

Fixed, thank you!


[FEATURE REQUEST] Feedback upon pressing "Reset" button

v1.6.0
There are a number of buttons that do not provide any feedback when pressed, which is quite confusing.

Settings - Package Manager - Chocolatey - Reset cache
Settings - Experimental - Reset WingetUI Icon cache
WingetUI Log - Copy log to clipboard
WingetUI Log - Reload log

One can press these buttons, but one will never know if anything happened

Reload log does update the text, but if the log hasn't changed nothing will happen.
The other ones, it is true that they could do something

this actually happens, but it is so instantaneous that it does not show as a noticeable change

Gone are the days that computers were slower than the blink of an eye.  😉


Improve basic button and label styles

Simplify disabled styling of label by matching for the disabled attribute.
Raise fomantic disabled opacity from .45 to .55 to for more contrast.
Use CSS vars for basic button styles.
Consolidate basic label and button styles.

I think I'll do another rework of the colors in use here so that labels and basic buttons get to use the same colors.

Vars consolidation done. Basic labels and basic buttons now use the exact same color in all their state. Also applied these colors to the unsigned commit labels. Screenshots updated.

conflicts

rebased


HS_SYMBOLS_URL 404

🐛 Bug Description
The URL used in scripts/data_collector/utils.py is dead.
To Reproduce
Steps to reproduce the behavior:

run collector.py under scripts/data_collector/pit
it gets stuck after logging "get cn stock symbols....."
debug finds that requests.get(HS_SYMBOLS_URL.format(s_type=_k), timeout=None) gets 404 response.

Expected Behavior
HS_SYMBOLS_URL return right symbols
Environment
Note: User could run cd scripts && python collect_info.py all under project directory to get system information
and paste them here directly.

Qlib version: "<IP_ADDRESS>"
Python version: 3.8
OS (Windows, Linux, MacOS):MacOS

Additional Notes

I encountered the same issue. Excuse me, have you resolved it?


UI customization via environment variables works locally but not when deployed via azure cli

Describe the bug
Per the README I've created a .env file using the env.sample file and modified the UI_ variables to change the logo, title, and description. I've run bash start.sh to build and run the app successfully. I can see the UI modifications when hitting the app locally (http://<IP_ADDRESS>:50505).
After building the app I have deployed it to Azure using the instructions in the README.
The app is deployed successfully and It works when I go to the URL for the web app. However, it does not show my UI modifications. It still shows the stock "Contoso" branding.
Is the README incorrect? Is there something else I need to do to get my local modifications deployed to the webapp in azure?
To Reproduce
Steps to reproduce the behavior:

clone the repo locally
copy .env.sample to .env
update the UI_ env variables in the .env file
run bash start.sh to build and run the app
browse to the app running locally and verify the UI changes were made
kill the locally running app and run the two az cli commands here
configure an identity provider for the newly created app in the azure cli
browse to the web app URL
verify standard "Contoso" branding

Expected behavior
The UI modifications that work locally should be reflected in the deployed web app.
Configuration: Please provide the following

Azure OpenAI model name and version (e.g. 'gpt-35-turbo-16k, version 0613')
gpt-35-turbo
Is chat history enabled?
no
Are you using data? If so, what data source? (e.g. Azure AI Search, Azure CosmosDB Mongo vCore, etc)
no

Additional context
None

When you deploy the app, the new configuration keys don't get exported to the existing app. Make sure you have the keys in the configurations, if not add them and restart the app.

can you please clarify: only the keys, or the values included?
im asking because i´m not sure if you mean the values will be synched from the code
thank you

@Richard-ANX You need to add both the keys and values. For example, the UI configuration keys were recently added and you could see them in the .env.sample but when you deploy the app, these keys don't get exported. So, you need to go to the Configuration in Azure and add these key and values for the application to use it. You may need to restart the app service.

thank you for your reply!
that worked for me!


Computed properties to convert integers to bytes

Hello Samuele,
thank you for the first PR.
I have just 2 things that I'd like to discuss with you.
Splitting the protocol
While I do agree that is correct to divide the protocol in ByteRepresentable  and BytesConvertible , I would remove the inheritance between the two using and approach more similar to swift Encodable and Decodable that is typealised as:
public typealias Codable = Decodable & Encodable
Using a similar approach we would respect also the Interface Segregation Principle avoiding unnecessary requirements, that probably was the reason in the first place for the split due to the numeric extension.
I'm very bad at naming but could be public typealias ByteRepresentable = BytesConvertible & BytesInitiable
What do you think?
Endianess
This is more a help, I see a possibile critical point. Now swift is really multi-platform and the type of endianness should be given for granted. Are you using littleEndian in the numeric extension because it already puts them in correct order independently on the machine?
Thank you so much for your help.
Andrea

Hello Andrea, the PR is still in draft because still misses Unit Tests.
About splitting the protocol I agree we should compose two interfaces to satisfy the SOLID principles avoiding inheritance, but I minimized at the moment the number of changes and I was out of names too, 😅. I’ll improve it.

Endianess. Are you using littleEndian in the numeric extension because it already puts them in correct order independently on the machine?

Yes, it happened that on macOS the behavior was different so littleEndian should ensure that it works regardless the target device.
We can add some unit tests even for Linux to verify by using Github Actions

Awesome! thank you.
I did some research about Endianness so it does seem that Intel architectures are little endian while ARM architectures are BI-endian and it seems that the decision about which one to pick is left to the OS. More complex if we need to take into account also Float as some architectures use a hybrid approach.
To check the endianness I've found this interesting comment on Apple Doc.

If necessary, the byte order of this value is reversed from the typical byte order of this integer type. On a little-endian platform, for any integer x, x == x.littleEndian.

This translates to:
let int: UInt16 = 0x00_01
if int == int.littleEndian {
 print("Is Little")
} else {
 print("Is Big")
}

It could be useful as bool check to understand the type.


Feature Idea / Discussion: Action Groups / Toggle Frame Visibility

Feature Request

I have several animations that I want to blend from one to the other (for instance, a walk cycle that loops, as well as intro / exit frames from the loop).  I want to be able to isolate the walk cycle so that I can make sure that it loops well, but I also want to be able to pair it with the intro / outtro to make sure that those blend correctly.
I've tried to think of a few ways to handle this.
Option 1 - more complicated:
Add a way to group frames together into an "action group", such as "walk", "punch", "kick", "walk start", etc.  However, this feels like a "heavyweight" option.
Option 2 - less complicated (perhaps less intuitive?):
Add a visibility icon on each frame that will let me toggle its inclusion in the current animation preview loop.  This would let me temporarily hide / remove the "walk intro" and "walk outtro" frames while working on the walk loop, and let me bring them back when I want to pair things together.
At first blush, I'm leaning towards the second option, but I'd love to hear others' opinions before I begin on a PR.

hey, just found piksel and playing around just now. might not be the exact work around you need, but you can set the opacity of a frame to zero. on the right hand side of the screen about half way down you will see the alpha symbol; click on it and set to zero.


Video effects conceptual docs in storybook

What
Video effects conceptual docs in storybook
Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

Looks great overall!


Fix extension services registration and documentation link

Overview
Extension services would all register under the interface type key IMixedRealityExtensionService. The MixedRealityServiceRegistry would only check under the interface key provided. This is problematic as a service may inherit and extend multiple interface types. Usage of GetService() and similar usage of TryGetService were broken.
This change extends the internal Registry TryGet* path to search all bins and return the first service found that matches the interface type and name query given.
Furthermore, the tests were modified to check for more variety of GetService requests as well as the extension service documentation link fixed.
Changes

Fixes: #5644 , #5653

Verification

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run


ims/volte stops working after expiry of timers (4g setup)

Volte calls between phones work fine after starting the containers, but after 1-2 minutes one of the configured expiry timers in kamailio_pcscf.cfg appears to trigger something and at that point volte calls stop working.
my current, very hacky "fix":
 modparam("ims_registrar_pcscf", "is_registered_fallback2ip", 1)
 modparam("ims_registrar_pcscf", "ignore_reg_state", 1)
 modparam("ims_registrar_pcscf", "ignore_contact_rxport_check", 1)
-modparam("ims_registrar_pcscf", "pending_reg_expires", 30)
-modparam("ims_registrar_pcscf", "subscription_expires", 36000)
-modparam("ims_registrar_pcscf", "delete_delay", CONTACT_DELETE_DELAY)
-modparam("ims_usrloc_pcscf", "expires_grace", 120)
+modparam("ims_registrar_pcscf", "pending_reg_expires", 99999)
+modparam("ims_registrar_pcscf", "subscription_expires", 99999)
+modparam("ims_registrar_pcscf", "delete_delay", 5)
+modparam("ims_usrloc_pcscf", "expires_grace", 9999999)

 #!ifdef WITH_REGINFO
 modparam("ims_registrar_pcscf", "subscribe_to_reginfo", 1)
@@ -428,7 +428,7 @@ modparam("ims_qos", "confirmed_qosrelease_headers", "X-Reason: QoS failed\r\n")
 modparam("ims_qos", "authorize_video_flow", 1)
 modparam("ims_qos", "af_signaling_ip", RX_AF_SIGNALING_IP)
 modparam("ims_qos", "include_rtcp_fd", 1)
-modparam("ims_qos", "rx_auth_expiry", 36000)
+modparam("ims_qos", "rx_auth_expiry", 999999999)
 modparam("ims_qos", "recv_mode", 1)
 modparam("ims_qos", "dialog_direction", RX_IMS_REG_DIALOG_DIRECTION)
 #!endif

Those diff does not make sense. Please post a pcap of the issue you are facing and I can take a look.

Which parts do you need? It appears to be a pcscf issue, only half of the deregistration happens, the other half is perpertually stuck in a pending state, while the "valid" contacts on the scscf  side keep piling up with the expiry supplied by the ue, which is 600000 seconds.
Maybe related: https://github.com/kamailio/kamailio/issues/3570

pending_reg_expires

The above modparam related to UE whose IMS registration remain in pending state and not for UEs who register with the IMS successfully i.e. 200 OK for SIP REGISTER is received.

subscription_expires

This is when the subscription of the UE expires at P-CSCF. 36000 equates to 10hrs

delete_delay

This is the time after which IPSec connection is removed once the UE de-registers from the network
so I am not sure its a P-CSCF issue

Which parts do you need?

I suggest taking the pcap on the 'any' interface without any filters. The scenario should be as follows

Start the trace
Register two UEs
Wait for 1-2 mins
Attempt a call
Stop the trace and post it here

The packets in the pcap file didnt feel to be in right order I saw diameter UAR request before even receiving SIP REGISTER. Can you please ensure that time stamps on the machine running EPC + IMS and UE are the same? And, UE is set to receive time from the network?
Also, can you tell me which eNB you are using?
Sorry, cant be of much help on this. But all I can confirm is that its not due to those values in modparam you are facing this issue.

Just increasing pending_reg_expires is enough to "fix" the issue, for some reason waiting longer than (pending_reg_expires + expires_grace) appears to be time stuff starts failing. It can also be "fixed" by putting the phones in airplane mode, and turning them on again (unitl it fails again). No idea what is going on with the timestamps tbh.. I usually don't look at all interfaces because I don't want to see everything five times, so I never noticed that ;)

Can you post a pcap of the working call scenario with increased pending reg expire timer?

enb is srsenb, btw.
One "fixed" attempt:
pending_9999999_callfix.pcapng.zst.zip
And another try, I can basically watch it fail really fast even before making a call by doing this:
--- a/pcscf/kamailio_pcscf.cfg
+++ b/pcscf/kamailio_pcscf.cfg
@@ -309,7 +309,7 @@ modparam("uac","restore_mode","none")

 # ----------------- Settings for RTimer ---------------
 # time interval set to 60 seconds
-modparam("rtimer", "timer", "name=NATPING;interval=60;mode=1;")
+modparam("rtimer", "timer", "name=NATPING;interval=2;mode=1;")
 modparam("rtimer", "exec", "timer=NATPING;route=NATPING")
 #!endif

@@ -398,7 +398,7 @@ modparam("ims_registrar_pcscf", "ignore_contact_rxport_check", 1)
 modparam("ims_registrar_pcscf", "pending_reg_expires", 30)
 modparam("ims_registrar_pcscf", "subscription_expires", 36000)
 modparam("ims_registrar_pcscf", "delete_delay", CONTACT_DELETE_DELAY)
-modparam("ims_usrloc_pcscf", "expires_grace", 120)
+modparam("ims_usrloc_pcscf", "expires_grace", 12)
 modparam("ims_usrloc_pcscf", "timer_interval", 2)

The point at which a call will fail is basically as soon as the OPTIONS "nat ping" breaks, which is pretty much after 30+12s after the succesful registration according to the second pcap (below), pcscf log for that point in time:
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786 via sip:<IP_ADDRESS>:41786;transport=tcp...
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643 via sip:<IP_ADDRESS>:40643;transport=tcp...
pcscf      | 107(144) ERROR: <script>: request sent to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786 completed with code: 200, Type 1
pcscf      | 104(141) ERROR: <script>: request sent to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643 completed with code: 200, Type 1
pcscf      | 85(122) INFO: cdp [authstatemachine.c:292]: auth_client_statefull_sm_process(): after callback of event 1
pcscf      | 94(131) INFO: cdp [authstatemachine.c:292]: auth_client_statefull_sm_process(): after callback of event 17
pcscf      | 94(131) INFO: cdp [authstatemachine.c:463]: auth_client_statefull_sm_process(): state machine: AUTH_EV_RECV_STA about to clean up
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786 via sip:<IP_ADDRESS>:41786;transport=tcp...
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643 via sip:<IP_ADDRESS>:40643;transport=tcp...
pcscf      | 107(144) ERROR: <script>: request sent to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786 completed with code: 200, Type 1
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786 via sip:<IP_ADDRESS>:41786;transport=tcp...
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643 via sip:<IP_ADDRESS>:40643;transport=tcp...
pcscf      | 107(144) ERROR: <script>: request sent to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786 completed with code: 200, Type 1
pcscf      | 85(122) ERROR: <script>: request sent to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643 completed with code: 408, Type 2
pcscf      | 85(122) ERROR: <script>:   request sent to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643: Fail Counter is 1
pcscf      | 85(122) INFO: cdp [authstatemachine.c:292]: auth_client_statefull_sm_process(): after callback of event 1
pcscf      | 94(131) INFO: cdp [authstatemachine.c:292]: auth_client_statefull_sm_process(): after callback of event 17
pcscf      | 94(131) INFO: cdp [authstatemachine.c:463]: auth_client_statefull_sm_process(): state machine: AUTH_EV_RECV_STA about to clean up
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786 via sip:<IP_ADDRESS>:41786;transport=tcp...
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643 via sip:<IP_ADDRESS>:40643;transport=tcp...
pcscf      | 85(122) ERROR: <script>: request sent to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643 completed with code: 408, Type 2
pcscf      | 85(122) ERROR: <script>:   request sent to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643: Fail Counter is 2
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786 via sip:<IP_ADDRESS>:41786;transport=tcp...
pcscf      | 98(135) ERROR: <script>: OPTIONS to sip:35209fe7-17dc-4c3d-a820-f52a974b9a6c@<IP_ADDRESS>:40643 via sip:<IP_ADDRESS>:40643;transport=tcp...
pcscf      | 85(122) ERROR: <script>: request sent to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786 completed with code: 408, Type 2
pcscf      | 85(122) ERROR: <script>:   request sent to sip:c9eff664-ce1b-474d-abbe-6ef092aa1b8c@<IP_ADDRESS>:41786: Fail Counter is 1

fail_natping2_grace12.pcapng.zst.zip

Hey @Hoernchen , thank you very much for details pcaps and logs. I think its a bug in kamailio P-CSCF code. I will see whether I can fix it. In my opinion, wrong Contact of the UE is deleted after pending expires + expire grace.

@Hoernchen Please pull the latest changes from this repo and re-build kamailio images and give it a try (no modifications to expires values is required).

I have been watching and "secretly" using your branch since tuesday, and can confirm that the current repo appears to have fixed the issue and calls just keep working, thanks for your very fast fix!
Just one minor complaint: the new much lower nat ping leads to a lot of "spam" in the docker compose output, it would be great to suppress that in some way unless it fails, because even with just two active phones I kind of mostly just see option messages and have to scroll forever to find anything...

Thanks for confirming the fix.

Just one minor complaint: the new much lower nat ping leads to a lot of "spam" in the docker compose output

Point noted. I will fix the interval.


Create a data bucket that is publicly available/available to partners on Sanger Farm (OTG)

Following up from the feedback on OTG functionalities provided by BMS on 8-6-22.
Request from partners:

[] Create a bucket that is publicly available/available to partners on Sanger Farm where the team can share the existing fine-mapping and coloc data for studies without sumstats.

Acceptance tests
How do we know the task is complete?

When requested data is successfully shared on Sanger Farm.

Unfortunately, I don't believe this is possible. Sanger policy does not allow partner access to the Sanger Farm - only those with an @sanger email. The current process is that they request the data and I provide it to them via a wget url. Is this an ok solution for this, as well? Happy to change to whatever is easier!

Thanks @sarahyoung3, I also add @MayaGhoussaini to this conversation

All genetics portal runs in Google Cloud now. There is no need to deal with the Sanger farm

Does it mean that it would be enough for Jack @xyg123 to create a directory on the Cloud with the requested fine-mapping and coloc data and provide access to the BMS data team? @d0choa

Ideally, we should not create anything new. Just grant access to the relevant person (hopefully one) that would pull the data.
Just to say, this data is not produced to be shared so it lacks documentation and it requires some understanding of how the pipelines work.

V2D in the FTP is the result of joining all the variant-to-disease information. Therefore, it contains data from studies with and without summary statistics.
Generally speaking, everything on the FTP is the result of data joining steps that are generated for the benefit of the genetics portal application. The intermediate outputs are on other locations e.g. gs://genetics-portal-dev-staging/ that are not publicly available for operative reasons.
In some cases (e.g. coloc), the datasets suffer not much transformation and it's exposed to the FTP in a similar format to the intermediate result. But that's not the case for most of the datasets including V2D.
Long-term we can work out what is the set of relevant datasets that are meaningful and have a reasonable size to be shared. In the meantime, we can provide selective access to the relevant individuals in GCP once the datasets they are interested in have been identified.

@d0choa @MayaGhoussaini do you think this can be closed for now?

For the time being, we can make any data available to partners upon request.
It will take us some time to organise everything, so we are in a state in which we can share intermediate datasets that are not necessarily the inputs or outputs of our pipelines and still be able to communicate that properly


encoding/gob: encode zero will get the previous value.

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
Just playing with playground.
Does this issue reproduce with the latest release?
N/A
What operating system and processor architecture are you using (go env)?
N/A
What did you do?
https://play.golang.org/p/_nm1UhGT67
What did you expect to see?
1
0
-1
What did you see instead?
1
1
-1
As I read through some similar issues, it seems that when decoding, the object buffer will not be cleared out. So I guess this may be a expected outcome as in language spec. Then I think in example code, it should be strongly discouraged to reuse the object buffer.
But, as I was reading examples (https://golang.org/src/encoding/gob/example_test.go). The example clearly reuse the object q to read decoded value twice. As a C/C++ programmer, there is strong inclination to reuse a buffer if possible.
This behavior is much more deadly as I was transmitting a boolean, a false never reaches if the previous value is true. This means this library is very easy to use wrongly.

IINM, this is working as intended and cannot be changed. It's how zero-values handling were designed to work and it saves wire-data when there's a lot of them. I think the designer(s) had experienced zero-values being common enough to justify this.

Working as intended. Start with a clean, zeroed item before decoding.


Context menu extension doesn't seem to work reliably

So, this will be a writeup of things I've tried, things that have worked in the past, and things that don't work as of now. Hoping for some help!
First of all, the source code of my Context Menu extension is available here: https://github.com/NimbleTools/Clipupload/tree/master/ClipUploadShellExtension
A while ago, this extension worked perfectly on my development machine, but not on any of my other machines or any of my end-users. After a Windows re-install it stopped working for me as well. (Both installs were Windows 8.1.) After having a lot of trouble trying to get it to work, I've followed this guide and I still haven't gotten it to work yet.
In my application, I call srm.exe to register the extension in the registry, which seems to not do much on the system, as the extension doesn't work.
This is how it looks in the registry:

I tried making a test shell extension and register it both with srm.exe and ServerManager.exe, to no avail. According to the server manager, the extension was registered and installed for both 32 bit and 64 bit.
I made the CanShowMenu and CreateMenu write to a file to see if it would get called, and they don't appear to be called at any point in time. Both the ClipUpload4 and ClipUploadShellExtension projects have strong names, and so does my test project.
Is there anything else I can try, or am I missing something obvious?
Edit: Forgot to mention that without -codebase it also doesn't work.

Update: My test extension seems to sometimes work in those Open File Dialogs, but not always. (eg. it works in Firefox's file dialog, but not in Notepad's file dialog...?)

So I did some more research, and after some trying I managed to find the fool-proof solution.
The assembly must be set to "Any CPU" for the 64 bit to work in the first place, and it must be registered with RegAsm.
The following code installs any extension just fine:
  Process.Start(new ProcessStartInfo() {
    FileName = System.Runtime.InteropServices.RuntimeEnvironment.GetRuntimeDirectory() + "RegAsm.exe",
    Verb = "runas",
    Arguments = "ClipUploadShellExtension.dll"
  });
  Process.Start(new ProcessStartInfo() {
    FileName = "srm.exe",
    Verb = "runas",
    Arguments = "install ClipUploadShellExtension.dll -codebase"
  });
  Process[] explorers = Process.GetProcessesByName("explorer");
  foreach (Process explorer in explorers) {
    try {
      explorer.Kill();
    } catch { }
  }

Thanks for updating the issue with your findings. This suggests there is a problem with the srm. In theory, the srm should be doing the same as regasm (first registering the assembly's com servers) then running specific shell extension registration. However I have found:
http://msdn.microsoft.com/en-us/library/system.runtime.interopservices.registrationservices.registerassembly(v=vs.90).aspx
Which suggests I can implement srm using this, meaning the regasm step becomes unnecessary. I'll raise a separate issue for this.


.co.uk nameservers parsing - only first record parsed

WHOIS returns NSes in separate lines, but python-whois gets only first line:
$ whois test.co.uk

    Domain name:
        test.co.uk

    Data validation:
        Nominet was not able to match the registrant's name and/or address against a 3rd party source on 27-Jul-2020

    Registrar:
        CSC Corporate Domains, Inc [Tag = CSC-CORP-DOMAINS]
        URL: https://www.cscdbs.com

    Relevant dates:
        Registered on: 21-Aug-1996
        Expiry date:  21-Aug-2023
        Last updated:  17-Aug-2022

    Registration status:
        Registered until expiry date.

    Name servers:
        dns1.cscdns.net
        dns2.cscdns.net

    WHOIS lookup made at 11:23:09 14-Oct-2022

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

    Copyright Nominet UK 1996 - 2022.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

{'domain_name': 'test.co.uk',
 'registrar': 'CSC Corporate Domains, Inc [Tag = CSC-CORP-DOMAINS]',
 'registrar_url': 'https://www.cscdbs.com',
 'status': 'Registered until expiry date.',
 'registrant_name': None,
 'registrant_type': None,
 'registrant_street': None,
 'registrant_city': None,
 'registrant_country': None,
 'creation_date': datetime.datetime(1996, 8, 21, 0, 0),
 'expiration_date': datetime.datetime(2023, 8, 21, 0, 0),
 'updated_date': datetime.datetime(2022, 8, 17, 0, 0),
 'name_servers': 'dns1.cscdns.net'}

The parser for this must be broken. I would be happy to get a PR to fix this.

Closing due to inactivity


Added TC-ACL-2-11 test script

Implement the M-ACL / Managed NIM / ARL test plan.
The test plan (currently in review form) can be found here:
https://github.com/CHIP-Specifications/chip-test-plans/pull/4316

Approved based on follow-ups happening.

Are the follow-ups tracked on another PR? And will they be for 1.4?

Approved based on follow-ups happening.

Are the follow-ups tracked on another PR? And will they be for 1.4?
Follow ups:

Managed ACL can block access to critical global attributes CHIP-Specifications/connectedhomeip-spec#10341
[TC-ACL-2.11] Improve test plan for MACL feature CHIP-Specifications/chip-test-plans#4560
verify subscriptions are not broken when there are ARLs in place

The follow-up test script changes would fall out of updates to the test plan.  Do we need another issue for the test script, or just let the test plan issue cover it all?


Fix typing of MapData objects

Please do not update the README or Change Log, we will do this when we merge your PR.
This PR (delete as applicable)

Updates the Documentation

Describe the changes below:
I believe that objects is going to be an array as the result of calling this function: https://github.com/photonstorm/phaser/blob/7834095789fd3ac24ee0146e65eefa096b22b1d6/src/tilemaps/parsers/tiled/ParseObjectLayers.js#L20
I'm not 100% sure on the type of the array elements (Phaser.Types.Tilemaps.ObjectLayerConfig), but that appears to be what ParseObjectLayers returns.

👍


Backend/user auth

Summary is coming.

This PR includes:

Token based user authentication
User signup
User profile
Event related endpoints and mixins, by and thanks to @mertakozcan