[BUG] AzureDatafactory log send to EventHub results in an incorrect JSON Format

I have plug the diagnostic reports to be sent to an event hub (try basic and standard tier).
I choose only "ActivityRuns", "PipelineRuns", "TriggersRun" because we don't have any SSIS.
When I access the hub, and and want to see the preview of the log in JSON, there is a message :
" Source '<unknown_location>' had 1 occurrences of kind 'InputDeserializerError.InvalidData' between processing times '2021-04-20T12:20:35.9747529Z' and '2021-04-20T12:20:35.9747529Z'. Could not deserialize the input event(s) from resource 'Partition: [0], Offset: [114888], SequenceNumber: [62]' as Json. Some possible reasons: 1) Malformed events 2) Input source configured with incorrect serialization format
"
even in CSV, the file is not fomat correctly.
But if I export in a blob storage, json file is correctly formatted.
I've put a zip with csv file out from eventhub.
eventHub_sample.zip

Thanks for your help

Thank you for your feedback.  Tagging and routing to the team best able to assist.

@Pierl0 This is not related to api/sdk/powershell, please go with support ticket for this kind of issue, then we will have more experts  there to help you, thanks!

@Pierl0 Have you got your issue resolved through support system? Thanks!

@jsquire We already suggest customer use the right channel to solve the issue and didn't get more response from customer, could you please help close this for now as I don't have the permission? Thanks!

@shawnxzq:  will do.


Support for Request MetadataKind in InternalUpstreamTransport

Title: Support for Request MetadataKind in InternalUpstreamTransport
Description:
I have a usecase where I am extracting an http header in a Lua filter, setting it in dynamicMetadata and passing it to an internal listener which has a TCPProxy filter configured with tunneling_config. The value that is set in dynamicMetadata needs to be referenced in the  tunneling_config.
It seems there is support for passthrough_metadata for passing information from one listener to the other listener in this case. However, even though the docs seem to suggest that request metadataKind is supported ( which is needed for passing DynamicMetadata ), it seems the internal implementation is missing here and here
Is my understanding correct ? Happy to work on a PR if I can get any pointers!
[optional Relevant Links:]

Any extra documentation required to understand the issue.

@kyessenov Can you please take a look and suggest the path forward here?

Yeah, the assessment is correct. I couldn't make it work with the request metadata because upstream is designed to handle multiplexing, sharing multiple streams from downstream to one stream from upstream. This is done via transport socket options, which are fairly lightweight and miss a lot of info from downstream, that the missing info includes the dynamic metadata.
The most effective way is to create a filter that is explicitly marked as shared with upstream, and which is then propagated to the transport socket options. You can use the freshly added https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/set_filter_state, for example.

I'm trying to do the same. In the docs under https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/tcp_proxy/v3/tcp_proxy.proto#extensions-filters-network-tcp-proxy-v3-tcpproxy-tunnelingconfig they give an example of the following:
tunneling_config:
  hostname: "%DYNAMIC_METADATA(tunnel:address)%"

Does this mean I should use https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/set_filter_state to set an object_key of tunnel.address?

Does this mean I should use https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/set_filter_state to set an object_key of tunnel.address?

I'm guessing that is wrong as I get the following error:
{"level":"info","ts":1717095853.4897122,"msg":"[2024-05-30 15:04:13.489][7538027][warning][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:138] gRPC config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) tcp_<IP_ADDRESS>:16080: 'tunnel.address' does not have an object factory"}

All I'm trying to do is save %REQ(:AUTHORITY)% for use in an internal listener.

I created https://github.com/envoyproxy/envoy/issues/34435 as I think my needs might be a little different. @deveshkandpal1224 if you have any advice please let me know.


Support SSH3

https://github.com/francoismichel/ssh3

I can confirmed OpenPubkey able to support SSH3. No further changes to OpenPubkey needed to support this.


Argument literal parsing is broken.

Using NightCode 2.0.3, when an argument literal (%n) for an anonymous function (#()) is used, errors appear and syntax highlighting is disabled for that line.
To reproduce:
Type "(map #(+ %1 2) '(1 2 3))" in the home page REPL or source file.

Fixed in 52c3ef51fe88e8116d92225472dc6253a930916f

Just released the fix in 2.1.0 so I'll close this.


schemaorg and codemeta shouldnt generate a CreativeWork

Schemaorg and codemeta converters can currently generate data for a CreativeWork, but this should not be possible, since the type from CFF 1.2 has a default value of software. Meaning if you find a CFF 1.2 CITATION.cff that doesnt specify its type, it should be treated as a software.
I think this is a symptom of a larger issue, namely that of generating internally inconsistent files, e.g. when repository-code is converted to Schema.org's codeRepository which is actually not a valid property when @type is a Dataset.

Done, closing


Does PromQL support automated reporting of designated sections?

Proposal
Use case. Why is this important?
“Nice to have” is not a good use case. :)
Bug Report
What did you do?
http_requests_total > 100 && 1=<day_of_week() <=5
This is not supported
What did you expect to see?
from Monday to Friday, the number of HTTP requests is greater than 100.
Alarm for HTTP requests greater than 50 from Saturday to Sunday
Can PromQL do this? If you can write an example，Thanks.
What did you see instead? Under which circumstances?

I'm closing it for now. If you have further questions, please use our user mailing list, which you can also search.


Update sync.py

Added logging for errors in async generator and coroutine execution.
Enhanced exception handling to provide more informative error messages. some threads edits

Thank you, i have fixed and modified something.


pytest not running

Describe the bug
Pytest do not complete the execution, remain "collecting 0 items" forever.
To reproduce current behavior
Steps to reproduce the behavior:

installed lava-dl following the guidelines

Expected behavior
run correctly the tests
Screenshots

Environment (please complete the following information):

Device: Desktop r5 3600 and rtx3070 cuda 11.7
OS: Ubuntu Linux 22.04
Lava version : Lava-nc 0.7.0 lava-dl 0.3.3

Additional context
Add any other context about the problem here. Remove section otherwise.

@franzhd it has been working consistently for our other use cases. Alternatively, you can test your installation using python -m unittest. I suspect it has to do with custom cuda compilation on your system. Perhaps this is useful: https://github.com/lava-nc/lava-dl/issues/55#issuecomment-1076514132

@franzhd if you got it working, can we close this issue?

sorry for the delay, i had no possibility to go back working on this.
I found that the suggested command works but it is not verbose enough, can you help me understand if everything is went well?

Thanks again for your help :D

@franzhd yes it is working. I am closing this issue then.


⚠ SceneTime has degraded performance

In ba03f13, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2431 ms

Resolved: SceneTime performance has improved in f874c53 after 5 minutes.


Implementing a custom ViewResult

It is a question rather than an issue.
Imagine a scenario where you need to have a custom action result type that decides which view to use dynamically. Name it VeryDynamicViewResult :) and it inherits from ViewResult.
The custom view result is smart enough to decide which View to use, having its ViewName property set dynamically - which works perfectly.
As one would expect, it also needs to know what Model data to bind to the view. In MVC 5, achieving that functionality was as easy as below since the ViewResult class had a FindView method.
        protected override ViewEngineResult FindView(ControllerContext context)
        {
            this.ViewName = this.GetType().Name;

            this.ViewData.Model = this.Model;

            return base.FindView(context);
        }

MVC 6 does not have such a method and the only place that seems to be appropriate to set the ViewData.Model is ExecuteResultAsync method.
However, the ViewData property is still null at that point. I tried instantiating the property myself but its parameters are not somewhere easy to find and could not find enough of documentation.
How could I achieve the above functionality using MVC 6?
        public override Task ExecuteResultAsync(ActionContext context)
        {
            ViewName = GetViewNameFromSomewhere();

            ViewData.Model = GetModelFromSomewhere();

            return base.ExecuteResultAsync(context);
        }

The method above fails because the ViewData is still null.
Any help is appreciated.
Thank you in advance.

You'll need to pass in ViewData to your ViewResult type. See - https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.ViewFeatures/Controller.cs#L262-L267
To get to the View instance, you can use IViewEngine.FindView:
https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.ViewFeatures/Controller.cs#L262-L267
var viewEngine = context.HttpContext.RequestServices.GetRequiredService<ICompositeViewEngine>();
var view = viewEngine.FindView(context, viewName);

The issue is that, I am not in a Controller context. I am trying to set the model within the custom ViewResult class.
Just to make it easier for you to imagine, I will try to provide an example:
public class FormModel
{
    public string FormHeading { get; set; }
    public string SubmitButtonText { get; set; }
    public string ResetButtonText { get; set; }
    public bool SupportsReset { get; set; }
}

public class FormResult : ViewResult
{
    public FormResult()
    {
        Model = new FormModel();
    }

    public FormModel Model { get; set; }

    public override Task ExecuteResultAsync(ActionContext context)
    {
        ViewName = "/Custom/Path/FormResult.cshtml";

        ViewData.Model = this.Model;

        return base.ExecuteResultAsync(context);
    }
}

public class SomePageController : Controller
{
    public FormResult Index()
    {
        FormResult form = new FormResult();

        form.Model.FormHeading = "Subscription Form";
        form.Model.SubmitButtonText = "Subscribe";
        form.Model.SupportsReset = false;

        return form;
    }
}

That is so that my developers can easily create a page that contains a form. I am not actually returning a View but a custom ViewResult which I expect to have its ViewName and ViewData.Model set behind the scenes. I was able to set the ViewName but not the ViewData.Model. (Which I was also able to using MVC 5)
The above code fails when I try to set the ViewData using ViewData.Model = this.Model;
I understand that I should probably initialize it myself. I see that the Controller class has the following comment for the ViewData property:
       By default, this property is activated when <see cref="IControllerActivator"/> activates controllers.
        However, when controllers are directly instantiated in user codes, this property is initialized with
        <see cref="EmptyModelMetadataProvider"/>.

Does it actually mean that I should use EmptyModelMetadataProvider to instantiate a ViewDataDictionary instance and assign it to ViewData prior to using ViewData.Model = this.Model;?

@csunali
Wouldn't this work:

public class SomePageController : Controller
{
    public FormResult Index()
    {
        FormResult form = new FormResult();
        form.ViewData = ViewData;
        form.Model.FormHeading = "Subscription Form";
        form.Model.SubmitButtonText = "Subscribe";
        form.Model.SupportsReset = false;

        return form;
    }
}


[OCF-73][OCF-74] core/invoker and core/controller: switch to CentOS 7

https://issues.jboss.org/browse/OCF-73
https://issues.jboss.org/browse/OCF-74

@jcrossley3 I've investigated the failure and reproduced it locally. Unfortunately the same issue exists even with current rhdemo branch, so my changes are not related to this failure.

@goldmann if you run the tools/vagrant/hello script, you'll see that it runs fine with rhdemo, but not with your change. something is different, because the ansible script is unable to recognize that the controller is up.

I can reproduce this error locally with vagrant, I'll try to find the root cause.

Investigation of CI failure below.
Invoker containers are failing on Travis because of file permission issues:
cp: cannot create regular file '/opt/jboss/jmxremote.access': Permission denied
cp: cannot create regular file '/opt/jboss/jmxremote.password': Permission denied
chmod: cannot access '/opt/jboss/jmxremote.*': No such file or directory
Error: Password file not found: /opt/jboss/jmxremote.password

The user that is used to run the copyJMXFiles.sh file is using id 1000 and this is the jboss user:
uid=1000(jboss) gid=1000(jboss) groups=1000(jboss)

Files stored in /conf are owned by user with id 2000, but access is 777, so anyone can read or modify it.
total 16K
drwxrwxrwx 2   2000   2000 4.0K Apr  9 14:13 .
drwxr-xr-x 1<PHONE_NUMBER>16 4.0K Apr  9 14:13 ..
-rwxrwxrwx 1   2000   2000   18 Apr  9 14:13 jmxremote.access
-rwxrwxrwx 1   2000   2000   16 Apr  9 14:13 jmxremote.password

The destination path is owned by (random) user with id 494216:
total 20K
drwxr-xr-x  2<PHONE_NUMBER>16 4.0K Apr  9 14:12 .
drwxr-xr-x  3<PHONE_NUMBER>16 4.0K Apr  9 14:12 ..
-rw-r--r-- 14<PHONE_NUMBER>16   18 Sep  6  2017 .bash_logout
-rw-r--r-- 14<PHONE_NUMBER>16  193 Sep  6  2017 .bash_profile
-rw-r--r-- 14<PHONE_NUMBER>16  231 Sep  6  2017 .bashrc

Considering all above it's obvious that this script cannot work as is since the user that runs the script does not have permissions to write to /opt/jboss directory.


3D Generation: InstantMesh Training, Inference, and Eval Scripts

This PR implements InstantMesh for 3D meshing using multiview images. The torch-cuda version with textures is shown below.

Input is nx3xhxw multiview video and the output is a 3D mesh mesh.obj file with vertices, faces.
HW environment specs are as follows.
Mindspore Version:               2.3.1 release
CANN Version:                    7.3
Ascend Driver:                   23.0.rc3.6

3D Mesh Demos
Inference demos with the pretrained checkpoint can be found in the readme, with any HTML renderer such as VSCode it can be viewed and interacted with smoothly as shown below.

These links can be found here for easy access.

akun
anya

Input multiview images are illustrated here, respectively. Kindly notice that the input multiview images can be either retrieved viav the SV3D pipeline or Zero123++ pipeline as in the original implementation, the paper's core contribution is the process of 3D meshing out of multiview images.
Limitations in Inference
1. Cache Miss in mint.unique() and other ACLNN Operators
As introduced in the Readme, InstantMesh extracts isosurface for meshing using FlexiCubes, which essentially requires a unique  operation to determine the surfaces of an object. Unfortunately, the operator mint.unique() remains not supported by ACLNN but only AICPU, and hence leads to the program being stuck by cache misses, as told by the MindSpore framework colleagues. Once the mint.unique() is fully supported by A+M, we will implement the 3D meshing with FlexiCubes for higher resolution.
(Update on August 1st: Turns out the CANN operator aclnnUniqueDim takes too long. Interacting with the framework and CANN team for solutions.)
Workaround: 3D Meshing with the Raw Triplane Features using Marching Cubes
For the reasons above, we have to find a workaround to extract 3D meshes from multiview images (from SV3D in our case). Here in this PR, since we already have a rough SDF extracted from the SDF MLP heads with the triplane features input, a straightforward way is to take the rough SDF and feed it to the classic isosurface extraction method, such as the Marching Cubes. As the optimization in the Marching Cubes lacks degrees of freedom to represent high-quality meshes, it tends to use more vertices (naturally more faces, triangles) to fit an irregular 3D shape, especially when the 3D shape cannot be approximated to a surface. Details can be found in the FlexiCubes' paper.

FlexiCubes
Marching Cubes

2. CUDA Extension for Rasterization
InstantMesh uses nvdiffrast for uv map rasterization and 2D rendering for the FlexiCube 3D volume. Bypass this for now.

can attach the training results for better reference


Dark theme - unable to login

Steps to reproduce this issue

go to https://news.ycombinator.com in an un-logged in state
Enable Dark Theme
Click on login

Expected result
Should be able to login
Actual result
Login form not visible
Notes and screenshots

Fixed by #113


Component/drawer

Also, you want, you can implement your changes on top of the main branch. We are discontinuing the next-minor branch and starting to work on top of main.

I'm gonna close this, since it does not have the code for Drawer component, if you could then open another PR I would greatly appreciate!


Resolving multiple promises using when(resolved:)

PromiseKit 6
I have a function that fetches a list of alerts from a db, I then need to use the contentId property on each to fetch the content and attach to the appropriate alert item.
Maybe there's a better way (@mxcl you mentioned you hardly use when, and that when(resolved:) is not a good idea since errors get ignored)
But what I came up with is to collect the promises into a list and call when(resolved:). I chose that because if any promise fails, I want to be able to return all those that can pass.
If there's a better approach, I'd be happy to get some pointers. Thanks :)
private func getContent(for alert: Model) -> Promise<ViewModel> {
  return firstly { () -> Promise<Any> in

    if let contentType = AlertContentType(rawValue: alert.type) {
      switch contentType {
      case .news:
        return newsService.get(contentId: contentId, superareaId: superareaId).compactMap { $0 as Any }

      case .insight:
        return insightService.get(contentId: contentId, superareaId: superareaId).compactMap { $0 as Any }
      }
    } else { throw DataError.Missing(error: "Could not retrieve type!") }
  }.compactMap { content in
    var viewModel = alert.toViewModel()
    viewModel.content = content

    return viewModel
  }
}

private func attachContents(to alerts: [Model]) -> Promise<[ViewModel]> {
  return firstly { () -> Guarantee<[Result<ViewModel>]> in
    let contentPromises: [Promise<AlertViewModel>] = alerts.map {
      return self.getContent(for: $0)
    }
    return when(resolved: contentPromises)
  }.map { (vModels: [Result<ViewModel>]) in
    vModels.flatMap { (vm: Result<ViewModel>) in
       //
       let viewModelsWithContent: [ViewModel?] = vModels.flatMap { (vm: Result<ViewModel>) in
            if case let .fulfilled(alert) = vm {
                return alert
            } else {
                return nil
            }
        }
    }
  }
}

Seems like a fine use of when(resolved:).

you mentioned you hardly use when

To be clear, I hardly use when(resolved:), I use the other when variants all the time though.
I cleaned this up, maybe (I had to infer some bits):
private func getContent(for alert: Model) -> Promise<ViewModel> {
    return firstly { () -> AlertContentType in
        switch AlertContentType(rawValue: alert.type) {
        case .news?:
            return newsService.get(contentId: contentId, superareaId: superareaId)
        case .insight?:
            return insightService.get(contentId: contentId, superareaId: superareaId)
        default:
            throw DataError.Missing(error: "Could not retrieve type!")
        }
    }.map { content in
        var viewModel = alert.toViewModel()
        viewModel.content = content
        return viewModel
    }
}

private func attachContents(to alerts: [Model]) -> Promise<[ViewModel]> {
    return firstly {
        when(resolved: alerts.map{ self.getContent(for: $0) })
    }.compactMapValues {
        $0.value
    }
}

Closing but re-open if your question is still not answered.


Fix redundant lint with extract-text-webpack-plugin

When using with extract-text-webpack-plugin, you got redundant lint.
Usage
module.exports = {
  plugins: [
    new sassLintPlugin({
+     ignorePlugins: 'extract-text-webpack-plugin'
    }),
  ]
}

@kentrino Thanks for doing this! Would you mind adding in a test for this, before I approve it?

I've taken and added tests for this in https://github.com/alleyinteractive/sasslint-webpack-plugin/pull/12 which causes this to be duplicated. Thanks for the PR!


[Extended support]

I am working to have support for cdiutils on the engaging MIT cluster.

If you have a gpu available, use Vincent's script to make your env/install pynx, then just pip install cdiutils

I have to submit batch jobs like you on the p9 cluster so I need to figure that out

Oh nice, I see.
So, on the local machine: cdiutils, on the p9: pynx. Then, you have to make your own .slurm file to meet your requirements (config file to handle number of nodes etc + how to load the pynx env, see: template.
I am currently working on a more generic way to handle the phasing, see the commented code block, so it can handle every type of config (phasing on gpu/local machine/ subprocess etc.) See phase retrieval method

Engaging does not offer proper support of GPU, switching to NERSC


  Resource                    Requests          Limits
  --------                    --------          ------
  cpu                         3721m (94%)       7550m (192%)
  memory<PHONE_NUMBER> (47%)<PHONE_NUMBER> (57%)
  ephemeral-storage           0 (0%)            0 (0%)
  hugepages-1Gi               0 (0%)            0 (0%)
  hugepages-2Mi               0 (0%)            0 (0%)
  attachable-volumes-aws-ebs  0                 0
Events:
  Type    Reason              Age   From     Message
  ----    ------              ----  ----     -------
  Normal  NodeNotSchedulable  36s   kubelet  Node ip-10-138-108-104.eu-west-1.compute.internal status is now: NodeNotSchedulable

Consolidation occurring in log:
zone: eu-west-1c, capacityType: on-demand	{"commit": "ea5dc14", "provisioner": "default-ondemand2"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T15:00:12.015Z	INFO	controller.deprovisioning	Deprovisioning via consolidation/delete	{"commit": "ea5dc14"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T15:00:12.050Z	INFO	controller.termination	Cordoned node	{"commit": "ea5dc14", "node": "ip-10-138-108-104.eu-west-1.compute.internal"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T15:00:54.398Z	INFO	controller.termination	Deleted node	{"commit": "ea5dc14", "node": "ip-10-138-108-104.eu-west-1.compute.internal"}

New node:
$ kubectl describe node ip-10-138-109-2.eu-west-1.compute.internal
Name:               ip-10-138-109-2.eu-west-1.compute.internal
Roles:              <none>
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/instance-type=m5a.xlarge
                    beta.kubernetes.io/os=linux
                    failure-domain.beta.kubernetes.io/region=eu-west-1
                    failure-domain.beta.kubernetes.io/zone=eu-west-1c
                    k8s.io/cloud-provider-aws=e86087ba30a6f3944c59fd13e20eff23
                    karpenter.k8s.aws/instance-ami-id=ami-0f4e299f8f4eb0b52
                    karpenter.k8s.aws/instance-category=m
                    karpenter.k8s.aws/instance-cpu=4
                    karpenter.k8s.aws/instance-family=m5a
                    karpenter.k8s.aws/instance-generation=5
                    karpenter.k8s.aws/instance-hypervisor=nitro
                    karpenter.k8s.aws/instance-memory=16384
                    karpenter.k8s.aws/instance-pods=58
                    karpenter.k8s.aws/instance-size=xlarge
                    karpenter.sh/capacity-type=on-demand
                    karpenter.sh/initialized=true
                    karpenter.sh/provisioner-name=default-ondemand2
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=ip-10-138-109-2.els.vpc.local
                    kubernetes.io/os=linux
                    lifecycle=OnDemand
                    node.kubernetes.io/instance-type=m5a.xlarge
                    provisioner=default-ondemand2
                    topology.ebs.csi.aws.com/zone=eu-west-1c
                    topology.kubernetes.io/region=eu-west-1
                    topology.kubernetes.io/zone=eu-west-1c
                    vpc.amazonaws.com/eniConfig=eu-west-1c
Annotations:        csi.volume.kubernetes.io/nodeid: {"ebs.csi.aws.com":"i-0943bcd2a1d1736bc"}
                    node.alpha.kubernetes.io/ttl: 15
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Fri, 23 Dec 2022 14:58:23 +0000
Taints:             <none>
Unschedulable:      false
Lease:
  HolderIdentity:  ip-10-138-109-2.eu-west-1.compute.internal
  AcquireTime:     <unset>
  RenewTime:       Fri, 23 Dec 2022 15:15:15 +0000
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  KernelDeadlock       False   Fri, 23 Dec 2022 15:14:31 +0000   Fri, 23 Dec 2022 15:00:21 +0000   KernelHasNoDeadlock          kernel has no deadlock
  ReadonlyFilesystem   False   Fri, 23 Dec 2022 15:14:31 +0000   Fri, 23 Dec 2022 15:00:21 +0000   FilesystemIsNotReadOnly      Filesystem is not read-only
  MemoryPressure       False   Fri, 23 Dec 2022 15:11:39 +0000   Fri, 23 Dec 2022 14:58:55 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Fri, 23 Dec 2022 15:11:39 +0000   Fri, 23 Dec 2022 14:58:55 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Fri, 23 Dec 2022 15:11:39 +0000   Fri, 23 Dec 2022 14:58:55 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Fri, 23 Dec 2022 15:11:39 +0000   Fri, 23 Dec 2022 15:00:07 +0000   KubeletReady                 kubelet is posting ready status
Addresses:
  InternalIP:   <IP_ADDRESS>
  Hostname:     ip-10-138-109-2.els.vpc.local
  InternalDNS:  ip-10-138-109-2.els.vpc.local
Capacity:
  attachable-volumes-aws-ebs:  25
  cpu:                         4
  ephemeral-storage:           77582316Ki
  hugepages-1Gi:               0
  hugepages-2Mi:               0
  memory:                      16007224Ki
  pods:                        58
Allocatable:
  attachable-volumes-aws-ebs:  25
  cpu:                         3920m
  ephemeral-storage:<PHONE_NUMBER>4
  hugepages-1Gi:               0
  hugepages-2Mi:               0
  memory:                      14990392Ki
  pods:                        58
System Info:
  Machine ID:                 ec2db95a1f859acbc68f184400a10aa1
  System UUID:                ec216cbc-638f-d763-3f4d-a60e6a743134
  Boot ID:                    befe112b-feab-43d6-b3c8-063c0cb4eb30
  Kernel Version:             5.4.209-116.367.amzn2.x86_64
  OS Image:                   Amazon Linux 2
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  docker://20.10.17
  Kubelet Version:            v1.21.14-eks-ba74326
  Kube-Proxy Version:         v1.21.14-eks-ba74326
ProviderID:                   aws:///eu-west-1c/i-0943bcd2a1d1736bc
Non-terminated Pods:          (11 in total)
  Namespace                   Name                                                    CPU Requests  CPU Limits    Memory Requests  Memory Limits  Age
  ---------                   ----                                                    ------------  ----------    ---------------  -------------  ---
  caas-uat01                  caas-nifi-1                                             3030m (77%)   6150m (156%)  6174Mi (42%)     6294Mi (42%)   14m
  infra                       infra-fluent-bit-w2rqz                                  10m (0%)      200m (5%)     8Mi (0%)         500Mi (3%)     16m
  infra                       infra-node-problem-detector-gxj9z                       100m (2%)     200m (5%)     10Mi (0%)        40Mi (0%)      16m
  kube-system                 aws-node-6ddcj                                          25m (0%)      0 (0%)        0 (0%)           0 (0%)         16m
  kube-system                 calico-node-c7lbj                                       0 (0%)        0 (0%)        0 (0%)           0 (0%)         16m
  kube-system                 ebs-csi-node-tdlhh                                      0 (0%)        0 (0%)        0 (0%)           0 (0%)         16m
  kube-system                 kube-proxy-fvdbl                                        100m (2%)     0 (0%)        0 (0%)           0 (0%)         16m
  kube-system                 nvidia-device-plugin-daemonset-42sbm                    0 (0%)        0 (0%)        0 (0%)           0 (0%)         16m
  newrelic                    nri-bundle-nrk8s-kubelet-wjhbn                          100m (2%)     0 (0%)        100M (0%)        1G (6%)        16m
  prometheus                  kube-prometheus-stack-prometheus-node-exporter-82g2z    100m (2%)     100m (2%)     100M (0%)        100M (0%)      16m
  twistlock                   twistlock-defender-ds-89jz9                             256m (6%)     900m (22%)    512Mi (3%)       512Mi (3%)     16m
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource                    Requests          Limits
  --------                    --------          ------
  cpu                         3721m (94%)       7550m (192%)
  memory<PHONE_NUMBER> (47%)<PHONE_NUMBER> (57%)
  ephemeral-storage           0 (0%)            0 (0%)
  hugepages-1Gi               0 (0%)            0 (0%)
  hugepages-2Mi               0 (0%)            0 (0%)
  attachable-volumes-aws-ebs  0                 0
Events:
  Type    Reason                   Age                From     Message
  ----    ------                   ----               ----     -------
  Normal  Starting                 16m                kubelet  Starting kubelet.
  Normal  NodeHasSufficientMemory  16m (x2 over 16m)  kubelet  Node ip-10-138-109-2.eu-west-1.compute.internal status is now: NodeHasSufficientMemory
  Normal  NodeHasNoDiskPressure    16m (x2 over 16m)  kubelet  Node ip-10-138-109-2.eu-west-1.compute.internal status is now: NodeHasNoDiskPressure
  Normal  NodeHasSufficientPID     16m (x2 over 16m)  kubelet  Node ip-10-138-109-2.eu-west-1.compute.internal status is now: NodeHasSufficientPID
  Normal  NodeAllocatableEnforced  16m                kubelet  Updated Node Allocatable limit across pods
  Normal  NodeReady                15m                kubelet  Node ip-10-138-109-2.eu-west-1.compute.internal status is now: NodeReady

Steps to Reproduce the Problem
Unsure. Difficult to reproduce
Resource Specs and Logs
Provisioner spec:
  spec:
    consolidation:
      enabled: true
    kubeletConfiguration:
      containerRuntime: dockerd
    labels:
      lifecycle: OnDemand
      provisioner: default-ondemand2
    limits:
      resources:
        cpu: "600"
        memory: 2450G
    providerRef:
      name: default-ondemand2
    requirements:
    - key: kubernetes.io/arch
      operator: In
      values:
      - amd64
    - key: karpenter.k8s.aws/instance-cpu
      operator: Gt
      values:
      - "3"
    - key: karpenter.k8s.aws/instance-memory
      operator: Gt
      values:
      - "14336"
    - key: karpenter.k8s.aws/instance-cpu
      operator: Lt
      values:
      - "18"
    - key: karpenter.k8s.aws/instance-memory
      operator: Lt
      values:
      - "67584"
    - key: karpenter.k8s.aws/instance-family
      operator: In
      values:
      - c5
      - c5a
      - c6a
      - c6i
      - m5
      - m5a
      - m6a
      - m6i
      - r5
      - r5a
      - r5b
      - r6a
      - r6i
    - key: karpenter.sh/capacity-type
      operator: In
      values:
      - on-demand
    weight: 10

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Which pods are being scheduled to the node that is being consolidated?

karpenter-6cb96795c8-d4md9 controller 2022-12-23T15:00:12.015Z	INFO	controller.deprovisioning	Deprovisioning via consolidation/delete	{"commit": "ea5dc14"}

This line indicates that Karpenter was doing a consolidation by delete, meaning that it thought that either the node was empty (had no pods scheduled to it) or that the pods on that node could schedule to another node.
This assumption looks like it was wrong in someway since we immediately had to launch a new node after deleting this one. Can you also share more logging around launching the node after the delete?

karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:58:21.304Z	INFO	controller.provisioning	Found 1 provisionable pod(s)	{"commit": "ea5dc14"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:58:21.304Z	INFO	controller.provisioning	Computed 1 new node(s) will fit 1 pod(s)	{"commit": "ea5dc14"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:58:21.306Z	INFO	controller.provisioning	Launching node with 1 pods requesting {"cpu":"1721m","memory":"1930150400","pods":"12"} from types m5a.xlarge, m6a.xlarge, m6i.xlarge, m5.xlarge, r6a.xlarge and 25 other(s)	{"commit": "ea5dc14", "provisioner": "default-ondemand2"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:58:23.384Z	INFO	controller.provisioning.cloudprovider	Launched instance: i-0943bcd2a1d1736bc, hostname: ip-10-138-109-2.eu-west-1.compute.internal, type: m5a.xlarge, zone: eu-west-1c, capacityType: on-demand	{"commit": "ea5dc14", "provisioner": "default-ondemand2"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:58:33.639Z	INFO	controller.deprovisioning	Deprovisioning via consolidation/delete	{"commit": "ea5dc14"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:58:33.710Z	INFO	controller.termination	Cordoned node	{"commit": "ea5dc14", "node": "ip-10-138-104-30.eu-west-1.compute.internal"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:59:16.047Z	INFO	controller.termination	Deleted node	{"commit": "ea5dc14", "node": "ip-10-138-104-30.eu-west-1.compute.internal"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:59:21.522Z	INFO	controller.provisioning	Found 1 provisionable pod(s)	{"commit": "ea5dc14"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:59:21.522Z	INFO	controller.provisioning	Computed 1 new node(s) will fit 1 pod(s)	{"commit": "ea5dc14"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:59:21.523Z	INFO	controller.provisioning	Launching node with 1 pods requesting {"cpu":"1721m","memory":"18061443584","pods":"12"} from types r6a.xlarge, r5a.xlarge, r6i.xlarge, r5.xlarge, r5b.xlarge and 17 other(s)	{"commit": "ea5dc14", "provisioner": "default-ondemand2"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T14:59:23.236Z	INFO	controller.provisioning.cloudprovider	Launched instance: i-0ade6ca56af23654a, hostname: ip-10-138-108-252.eu-west-1.compute.internal, type: r6a.xlarge, zone: eu-west-1c, capacityType: on-demand	{"commit": "ea5dc14", "provisioner": "default-ondemand2"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T15:00:12.015Z	INFO	controller.deprovisioning	Deprovisioning via consolidation/delete	{"commit": "ea5dc14"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T15:00:12.050Z	INFO	controller.termination	Cordoned node	{"commit": "ea5dc14", "node": "ip-10-138-108-104.eu-west-1.compute.internal"}
karpenter-6cb96795c8-d4md9 controller 2022-12-23T15:00:54.398Z	INFO	controller.termination	Deleted node	{"commit": "ea5dc14", "node": "ip-10-138-108-104.eu-west-1.compute.internal"}

Can you share the workload manifests that are being scheduled here?

Also, does the pod ever schedule to the node. What looks like is happening is that the memory that we think the node should have is different from the actual launched allocatable memory so after the node launches, we realize the pod can't schedule, re-launch, rinse, repeat.

apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    meta.helm.sh/release-name: caas-nifi
    meta.helm.sh/release-namespace: caas-uat01
  creationTimestamp: "2022-12-23T16:41:07Z"
  generation: 2
  labels:
    app: nifi
    app.kubernetes.io/managed-by: Helm
    chart: nifi-0.6.6
    heritage: Helm
    release: caas-nifi
  name: caas-nifi
  namespace: caas-uat01
  resourceVersion: "1969166950"
  uid: 7546831e-fca4-4911-acc3-72160fb27338
spec:
  podManagementPolicy: Parallel
  replicas: 5
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: nifi
      release: caas-nifi
  serviceName: caas-nifi-headless
  template:
    metadata:
      annotations:
        karpenter.sh/do-not-evict: "true"
        security.alpha.kubernetes.io/sysctls: net.ipv4.ip_local_port_range=10000 65000
      creationTimestamp: null
      labels:
        app: nifi
        chart: nifi-0.6.6
        heritage: Helm
        release: caas-nifi
    spec:
      affinity:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchExpressions:
              - key: app
                operator: In
                values:
                - nifi
            topologyKey: kubernetes.io/hostname
      containers:
      - command:
        - bash
        - -ce
        - |
          prop_replace () {
            target_file=${NIFI_HOME}/conf/${3:-nifi.properties}
            echo "updating ${1} in ${target_file}"
            if egrep "^${1}=" ${target_file} &> /dev/null; then
              sed -i -e "s|^$1=.*$|$1=$2|"  ${target_file}
            else
              echo ${1}=${2} >> ${target_file}
            fi
          }

          mkdir -p ${NIFI_HOME}/config-data/conf
          FQDN=$(hostname -f)

          cat "${NIFI_HOME}/conf/nifi.temp" > "${NIFI_HOME}/conf/nifi.properties"

          if [[ $(grep $(hostname) conf/authorizers.temp) ]]; then
            cat "${NIFI_HOME}/conf/authorizers.temp" > "${NIFI_HOME}/conf/authorizers.xml"
          else
            cat "${NIFI_HOME}/conf/authorizers.empty" > "${NIFI_HOME}/conf/authorizers.xml"
          fi

          if ! test -f /opt/nifi/data/flow.xml.gz && test -f /opt/nifi/data/flow.xml; then
            gzip /opt/nifi/data/flow.xml
          fi

          prop_replace nifi.remote.input.host ${FQDN}
          prop_replace nifi.cluster.node.address ${FQDN}
          prop_replace nifi.zookeeper.connect.string ${NIFI_ZOOKEEPER_CONNECT_STRING}
          prop_replace nifi.web.http.host ${FQDN}

          exec bin/nifi.sh run & nifi_pid="$!"

          function offloadNode() {
              FQDN=$(hostname -f)
              echo "disconnecting node '$FQDN'"
              baseUrl=http://${FQDN}:8080

              echo baseUrl ${baseUrl}
              echo "gracefully disconnecting node '$FQDN' from cluster"
              ${NIFI_TOOLKIT_HOME}/bin/cli.sh nifi get-nodes -ot json -u ${baseUrl} ${secureArgs} > nodes.json
              nnid=$(jq --arg FQDN "$FQDN" '.cluster.nodes[] | select(.address==$FQDN) | .nodeId' nodes.json)
              echo "disconnecting node ${nnid}"
              ${NIFI_TOOLKIT_HOME}/bin/cli.sh nifi disconnect-node -nnid $nnid -u ${baseUrl} ${secureArgs}
              echo ""
              echo "wait until node has state 'DISCONNECTED'"
              while [[ "${node_state}" != "DISCONNECTED" ]]; do
                  sleep 1
                  ${NIFI_TOOLKIT_HOME}/bin/cli.sh nifi get-nodes -ot json -u ${baseUrl} ${secureArgs} > nodes.json
                  node_state=$(jq -r --arg FQDN "$FQDN" '.cluster.nodes[] | select(.address==$FQDN) | .status' nodes.json)
                  echo "state is '${node_state}'"
              done
              echo ""
              echo "node '${nnid}' was disconnected"
              echo "offloading node"
              ${NIFI_TOOLKIT_HOME}/bin/cli.sh nifi offload-node -nnid $nnid -u ${baseUrl} ${secureArgs}
              echo ""
              echo "wait until node has state 'OFFLOADED'"
              while [[ "${node_state}" != "OFFLOADED" ]]; do
                  sleep 1
                  ${NIFI_TOOLKIT_HOME}/bin/cli.sh nifi get-nodes -ot json -u ${baseUrl} ${secureArgs} > nodes.json
                  node_state=$(jq -r --arg FQDN "$FQDN" '.cluster.nodes[] | select(.address==$FQDN) | .status' nodes.json)
                  echo "state is '${node_state}'"
              done
          }

          deleteNode() {
              echo "deleting node"
              ${NIFI_TOOLKIT_HOME}/bin/cli.sh nifi delete-node -nnid ${nnid} -u ${baseUrl} ${secureArgs}
              echo "node deleted"
          }

          trap 'echo Received trapped signal, beginning shutdown...;offloadNode;./bin/nifi.sh stop;deleteNode;exit 0;' TERM HUP INT;
          trap ":" EXIT

          echo NiFi running with PID ${nifi_pid}.
          wait ${nifi_pid}

          /opt/nifi/nifi-toolkit-current/bin/tls-toolkit.sh standalone -n 'caas-nifi-nifi-0.caas-nifi-nifi-headless.caas-uat01.svc.cluster.local' -C 'cn=admin,dc=example,dc=be' -o '/opt/nifi/nifi-current/conf/' -P env:PASS  -S env:PASS  --nifiPropertiesFile /opt/nifi/nifi-current/conf/nifi.properties
          exec bin/nifi.sh run
        env:
        - name: NIFI_ZOOKEEPER_CONNECT_STRING
          value: caas-nifi-zookeeper:2181
        - name: AWS_ACCESS_KEY_ID
          value: AKIAUHE7PE5CO3XV6KXO
        - name: AWS_SECRET_ACCESS_KEY
          value: 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
        image:<PHONE_NUMBER>40.dkr.ecr.eu-west-1.amazonaws.com/apache/nifi:1.13.2
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 3
          initialDelaySeconds: 90
          periodSeconds: 60
          successThreshold: 1
          tcpSocket:
            port: 8080
          timeoutSeconds: 1
        name: server
        ports:
        - containerPort: 8080
          name: http
          protocol: TCP
        - containerPort: 6007
          name: cluster
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          initialDelaySeconds: 60
          periodSeconds: 20
          successThreshold: 1
          tcpSocket:
            port: 8080
          timeoutSeconds: 1
        resources:
          limits:
            cpu: "6"
            memory: 9Gi
          requests:
            cpu: "6"
            memory: 9Gi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /opt/nifi/data
          name: data
        - mountPath: /opt/nifi/nifi-current/auth-conf/
          name: auth-conf
        - mountPath: /opt/nifi/flowfile_repository
          name: flowfile-repository
        - mountPath: /opt/nifi/content_repository
          name: content-repository
        - mountPath: /opt/nifi/provenance_repository
          name: provenance-repository
        - mountPath: /opt/nifi/nifi-current/logs
          name: logs
        - mountPath: /opt/nifi/nifi-current/conf/bootstrap.conf
          name: bootstrap-conf
          subPath: bootstrap.conf
        - mountPath: /opt/nifi/nifi-current/conf/nifi.temp
          name: nifi-properties
          subPath: nifi.temp
        - mountPath: /opt/nifi/nifi-current/conf/authorizers.temp
          name: authorizers-temp
          subPath: authorizers.temp
        - mountPath: /opt/nifi/nifi-current/conf/authorizers.empty
          name: authorizers-empty
          subPath: authorizers.empty
        - mountPath: /opt/nifi/nifi-current/conf/bootstrap-notification-services.xml
          name: bootstrap-notification-services-xml
          subPath: bootstrap-notification-services.xml
        - mountPath: /opt/nifi/nifi-current/conf/login-identity-providers.xml
          name: login-identity-providers-xml
          subPath: login-identity-providers.xml
        - mountPath: /opt/nifi/nifi-current/conf/state-management.xml
          name: state-management-xml
          subPath: state-management.xml
        - mountPath: /opt/nifi/nifi-current/conf/zookeeper.properties
          name: zookeeper-properties
          subPath: zookeeper.properties
        - mountPath: /opt/nifi/data/flow.xml
          name: flow-content
          subPath: flow.xml
      - args:
        - tail
        - -n+1
        - -F
        - /var/log/nifi-app.log
        image:<PHONE_NUMBER>40.dkr.ecr.eu-west-1.amazonaws.com/busybox:1.32.0
        imagePullPolicy: IfNotPresent
        name: app-log
        resources:
          limits:
            cpu: 50m
            memory: 50Mi
          requests:
            cpu: 10m
            memory: 10Mi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/log
          name: logs
      - args:
        - tail
        - -n+1
        - -F
        - /var/log/nifi-bootstrap.log
        image:<PHONE_NUMBER>40.dkr.ecr.eu-west-1.amazonaws.com/busybox:1.32.0
        imagePullPolicy: IfNotPresent
        name: bootstrap-log
        resources:
          limits:
            cpu: 50m
            memory: 50Mi
          requests:
            cpu: 10m
            memory: 10Mi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/log
          name: logs
      - args:
        - tail
        - -n+1
        - -F
        - /var/log/nifi-user.log
        image:<PHONE_NUMBER>40.dkr.ecr.eu-west-1.amazonaws.com/busybox:1.32.0
        imagePullPolicy: IfNotPresent
        name: user-log
        resources:
          limits:
            cpu: 50m
            memory: 50Mi
          requests:
            cpu: 10m
            memory: 10Mi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /var/log
          name: logs
      dnsPolicy: ClusterFirst
      initContainers:
      - command:
        - sh
        - -c
        - |
          echo trying to contact caas-nifi-zookeeper 2181
          until nc -vzw 1 caas-nifi-zookeeper 2181; do
            echo "waiting for zookeeper..."
            sleep 2
          done
        image:<PHONE_NUMBER>40.dkr.ecr.eu-west-1.amazonaws.com/busybox:1.32.0
        imagePullPolicy: IfNotPresent
        name: zookeeper
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext:
        fsGroup: 1000
        runAsUser: 1000
      serviceAccount: caas-nifi-sa
      serviceAccountName: caas-nifi-sa
      terminationGracePeriodSeconds: 30
      volumes:
      - configMap:
          defaultMode: 420
          items:
          - key: bootstrap.conf
            path: bootstrap.conf
          name: caas-nifi-config
        name: bootstrap-conf
      - configMap:
          defaultMode: 420
          items:
          - key: nifi.properties
            path: nifi.temp
          name: caas-nifi-config
        name: nifi-properties
      - configMap:
          defaultMode: 420
          items:
          - key: authorizers.xml
            path: authorizers.temp
          name: caas-nifi-config
        name: authorizers-temp
      - configMap:
          defaultMode: 420
          items:
          - key: authorizers-empty.xml
            path: authorizers.empty
          name: caas-nifi-config
        name: authorizers-empty
      - configMap:
          defaultMode: 420
          items:
          - key: bootstrap-notification-services.xml
            path: bootstrap-notification-services.xml
          name: caas-nifi-config
        name: bootstrap-notification-services-xml
      - configMap:
          defaultMode: 420
          items:
          - key: login-identity-providers.xml
            path: login-identity-providers.xml
          name: caas-nifi-config
        name: login-identity-providers-xml
      - configMap:
          defaultMode: 420
          items:
          - key: state-management.xml
            path: state-management.xml
          name: caas-nifi-config
        name: state-management-xml
      - configMap:
          defaultMode: 420
          items:
          - key: zookeeper.properties
            path: zookeeper.properties
          name: caas-nifi-config
        name: zookeeper-properties
      - configMap:
          defaultMode: 420
          items:
          - key: flow.xml
            path: flow.xml
          name: caas-nifi-config
        name: flow-content
  updateStrategy:
    rollingUpdate:
      partition: 0
    type: RollingUpdate
  volumeClaimTemplates:
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      creationTimestamp: null
      name: data
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 1Gi
      storageClassName: gp2
      volumeMode: Filesystem
    status:
      phase: Pending
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      creationTimestamp: null
      name: flowfile-repository
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 50Gi
      storageClassName: gp2
      volumeMode: Filesystem
    status:
      phase: Pending
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      creationTimestamp: null
      name: content-repository
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 200Gi
      storageClassName: gp2
      volumeMode: Filesystem
    status:
      phase: Pending
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      creationTimestamp: null
      name: provenance-repository
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 200Gi
      storageClassName: gp2
      volumeMode: Filesystem
    status:
      phase: Pending
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      creationTimestamp: null
      name: logs
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 1Gi
      storageClassName: gp2
      volumeMode: Filesystem
    status:
      phase: Pending
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      creationTimestamp: null
      name: auth-conf
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 100Mi
      storageClassName: gp2
      volumeMode: Filesystem
    status:
      phase: Pending

It schedules fine. Think maybe it is something to do with the app, I'll see if it can be replicated with some dummy workload. It isn't very easy to track down problems with the logging not showing pod names or anything when it provisions / consolidates

It schedules fine

To confirm, the sequence is:

Karpenter launches the node
The pod schedules to that node
Consolidation deletes the node while the pod is scheduled
Repeat

@jonathan-innis Yes. I'm encountering the same issue in 0.20.0
{"level":"DEBUG","time":"2022-12-28T21:56:22.811Z","logger":"controller.provisioner","message":"36 out of 335 instance types were excluded because they would breach provisioner limits","commit":"f60dacd"}
{"level":"INFO","time":"2022-12-28T21:56:22.816Z","logger":"controller.provisioner","message":"found provisionable pod(s)","commit":"f60dacd","pods":1}
{"level":"INFO","time":"2022-12-28T21:56:22.816Z","logger":"controller.provisioner","message":"computed new node(s) to fit pod(s)","commit":"f60dacd","nodes":1,"pods":1}
{"level":"INFO","time":"2022-12-28T21:56:22.816Z","logger":"controller.provisioner","message":"launching node with 1 pods requesting {\"cpu\":\"2125m\",\"memory\":\"8Gi\",\"pods\":\"6\"} from types t3a.xlarge, m5a.xlarge, r5a.xlarge, t3a.2xlarge, c5a.2xlarge and 16 other(s)","commit":"f60dacd","provisioner":"default"}
{"level":"INFO","time":"2022-12-28T21:56:25.043Z","logger":"controller.provisioner.cloudprovider","message":"launched new instance","commit":"f60dacd","provisioner":"default","launched-instance":"i-0ddbfa8bd58dca688","hostname":"ip-10-91-7-68.us-gov-west-1.compute.internal","type":"t3a.xlarge","zone":"us-gov-west-1a","capacity-type":"spot"}
{"level":"INFO","time":"2022-12-28T21:57:24.103Z","logger":"controller.deprovisioning","message":"deprovisioning via consolidation delete, terminating 1 nodes ip-10-91-7-68.us-gov-west-1.compute.internal/t3a.xlarge/spot","commit":"f60dacd"}
{"level":"INFO","time":"2022-12-28T21:57:24.149Z","logger":"controller.termination","message":"cordoned node","commit":"f60dacd","node":"ip-10-91-7-68.us-gov-west-1.compute.internal"}
{"level":"INFO","time":"2022-12-28T21:57:24.364Z","logger":"controller.termination","message":"deleted node","commit":"f60dacd","node":"ip-10-91-7-68.us-gov-west-1.compute.internal"}

I think it has something to do with the pod in question not being in the ready state due to the PVC getting into a weird state.

Job is created
Pod is launched
PV Controller creates Volume
PVC Attempts to attach volume, but fails with ProvisioningFailed: failed to get target node: node "ip-10-91-7-68.us-gov-west-1.compute.internal" not found

I think this has to do with the DeprovisioningTTL. My guess is what happening is that karpenter attempts to consolidate the node before the PVC can attach the volume and the pod gets scheduled on the node, so we get into an endless loop where karpenter is consolidating quicker than kubernetes can work.

Have you tried this with the latest version of Karpenter? There was a bug that was causing us to react too quickly to emptiness TTLs if the pod was unable to schedule quickly enough.

@andrewhibbert Have you gotten a chance to test out the latest version?

It schedules fine. Think maybe it is something to do with the app, I'll see if it can be replicated with some dummy workload. It isn't very easy to track down problems with the logging not showing pod names or anything when it provisions / consolidates

Perhaps a feature request, but having logs show the pod names would definitely help. i've had various corner cases where the consolidator never converges and keeps churning the same nodes in and out... endless loop. having a clear log entry with the pod names can help the investigation and point to the app that may be causing this. e.g.: "2023-01-14T11:24:03.497Z        INFO    controller.provisioner  found provisionable pod(s)      {"commit": "c4a4efd-dirty", "pods": 1}" would be so much more informative if it printed the pod name as well.

K8s event on the pods show the nodes that we intend to launch the pods on. You should be able to do a kubectl get events and then grep by the node that we say that we launched to see the pods that we think could launch on the node. Doing it in the log is a little hairy since you could imagine that we launch a node for 2000 pods and we shouldn't log every single pod name there.

For me the observability around consolidations is where it could be improved, it is difficult to figure out if there is a problem with consolidation in a production environment with lots of nodes or if the problem is something else such as the pod crashing and then karpenter consolidating

We're trying to improve the visibility. Recently we added support for recording events on a node regarding why it can't be consolidated.  If there are other parts of consolidation that leave you wondering what is going on, let us know and we can try to add some visibility there as well.

maybe different levels of log verbosity can contain more details?

For consolidation in the logs I would say it should show the node, reason for consolidation, provisioner name, number of running non-daemonset pods, requested cpu+memory


Fix structured data

Google’s Structured Data Testing Tool was returning an error: Missing '}' or object member name..
This fixes that, along with making the indentation consistent and fixing typos.

@whmii and I reviewed this in-person.


Scrollable2.ensureVisible for box-based viewports

This patch makes Scrollable2.ensureVisible with SingleChildScrollView. A future
patch will extend the implementation to work with slivers. (Although the patch
does include some of the infrastructure for that part of the implementation as
well.)

@Hixie


When will the code be open source, please？

2000 years later

When the chicken eats the rice, the dog licks the flour, and the fire breaks the lock, the code is open source.
——《Journey to the West》


pkg/repro: rerun repro when report is corrupted

Fixes #428

All done, PTAL.

Build has failed:
https://travis-ci.org/google/syzkaller/jobs/308456602

LGTM after s/crashed/_/


Lifecycle Observer is not removed in step_4

Here, there is addObserver() call, but there is no removeObserver() call for onDestroy. Is this intentional?

Yes, that's the whole point of the new lifecycle-aware components, no need to unsubscribe/remove observers.

Cool! Thanks :D

Can you please update the docs about it?
As a precaution, I always remove the observer when not needed (even asked about it here), even if I use it just for onDestroy event.
It's especially true for ON_DESTROY , that we don't need to call removeObserver for it, so maybe add a note there:
https://developer.android.com/reference/android/arch/lifecycle/Lifecycle.Event#ON_DESTROY
?

In the event that onDestroy which is not guaranteed to be called, is not called, does the observer ever get removed?


Update German translation

Is it ready to be merged?

Yes...
The spacing after flags translation is maybe not the best, but better than none i hope.
I added "(flag)" so it should be clear.

Thanks!


portico: Minor UI fix in plans page.

Renamed zulip-cloud class to responsive-title so that we can re-use this class in other sections also.
Fixes: #9133.
Before -

After -

Nice, merged, thanks @akashnimare!


[Bug] Reactive pdf export stuck to the first download

Is there an existing issue for this?

[X] Yes, I have searched the existing issues and none of them match my problem.

Product Variant
Self-Hosted
Current Behavior
hello,
I face weird issue when I update a resume, those updates are not in the pdf generated
Expected Behavior
No response
Steps To Reproduce

create a resume and do some stuff
export to pdf
update some content
export to pdf

What browsers are you seeing the problem on?
No response
What template are you using?
None
Anything else?
I use the simple docker compose
I tried to restart chrome container only not work
I tried to restart the full stack, not work
only a full container flush work, I suppose it is some temporary files that stuck the generation

I have checked the code @ronki2304 the data object is coming empty from the server side, when we click on the pdf download it redirects us giving error on the server side 404 not found
which is actually correct because the data object is coming empty
config :  {transitional: {…}, adapter: Array(3), transformRequest: Array(1), transformResponse: Array(1), timeout: 0, …} data :  {} headers :  AxiosHeaders {access-control-allow-origin: '*', content-length: '2', content-type: 'application/json; charset=utf-8', date: 'Thu, 13 Jun 2024 19:17:36 GMT', etag: 'W/"2-vyGp6PvFo4RvsFtPoIWeCReyIC8"', …} request :  XMLHttpRequest {onreadystatechange: null, readyState: 4, timeout: 0, withCredentials: true, upload: XMLHttpRequestUpload, …} status :  200 statusText :  "OK",
so the data:{} object is empty, Please @AmruthPillai  could you please provide any solution to this?

I see but why the first export works?

I see but why the first export works?

because the data object is being returned at the export url
createdAt :  Thu Jun 13 2024 22:51:02 GMT+0500 (Pakistan Standard Time) {} data :  basics :  {name: '345345345', headline: 'Software Developer', email: '345345345', phone: '+923128235333', location: '3453454', …} metadata :  {template: 'gengar', layout: Array(2), css: {…}, page: {…}, theme: {…}, …} sections :  {summary: {…}, awards: {…}, certifications: {…}, education: {…}, experience: {…}, …} [[Prototype]] :  Object id :  "dfgfdgdfgdfy" locked :  false slug :  "unnecessary-brave-squid" title :  "Unnecessary Brave Squid" updatedAt :  Thu Jun 13 2024 22:51:02 GMT+0500 (Pakistan Standard Time) {} userId :  "sdasdas" visibility :  "private" [[Prototype]] :  Object

I get an about:blank page after I click PDF export.

Please pin the browserless/chrome version to v2.13.0. The issue was not related to Reactive Resume.

hello the error remazins even  browserless/chrome version to v2.13.0.
Please reopen the issue


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/846 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit e5205dd:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-05-27-03-24-39 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


new play-Download API response

First thing, PLEASE READ THIS: ReactPlay Code Review Checklist

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

  Snapshot of Play

@abhi-works Have you created an issue for this?

@abhi-works Have you created an issue for this?

Yes Tapas https://github.com/reactplay/react-play/issues/629

@abhi-works Have you created an issue for this?

Yes @atapas #629 .Anything else pending from my side ?

Nope, started the review. Btw, this is an interesting project. Thanks!

@abhi-works One comment on look and feel. I think a lighter background will be better

@abhi-works My reviews are in. All the best.

Thanks @atapas .Changes are pushed and ready for review

You have taken care of all my code review comments @abhi-works Looks good... but you need to take care of the responsiveness too... mostly my last review comment on this PR :)

You have taken care of all my code review comments @abhi-works Looks good... but you need to take care of the responsiveness too... mostly my last review comment on this PR :)

Hope this fix works @atapas .Pushed the changes

Thanks! @atapas .Pushed fix to address the responsive screen  issue with help of material library hook which detects screen size.Hope this media screen fix works


English translation

would be nice

Yes :) but there are a lot of strings... maybe starting with Google/Microsoft Translator.


clock is slower than system time

when use lolex.insatll and set shouldAdvanceTime to true,the clock pass slower than system time.so  it would  cause a litter deviation for a while.

This is true but also by design. Read the documentation and implementation to see why.


UI design for channel sliders

We need something plausible for the demo, and we also want something that can work in Vitessce proper. (The demo slider UI will probably not be exported from Viv, and just recreated in Vitessce... but that might not be the right call.) Some questions:

Horizontal or vertical?
Are the numbers on the endpoint sliders useful?
Which axis direction is increasing?
Would a histogram above the slider be useful?
Should we use the same kind of slider here as we will in a faceted search interface?
What is the wish list in this space? Multiple piecewise ramp functions?
Where should channel names go?

Started a google doc where comparisons can happen: https://docs.google.com/document/d/1zY77lAaMnCTdnIU4QfvWC6zYY6eOOKn7M7UowzA-w-8/edit#heading=h.xfxdg8gx15ze


make password optional in jks.KeyStore.load()

keytool lets you query some information in a password-protected keystore without specifying the password.  I would like to do the same with pyjks.  This would be useful to querying basic information about the keystore, like number of entries, type of entries, alias, etc.
$ keytool -list -keystore keystore.jks -protected

*****************  WARNING WARNING WARNING  *****************
* The integrity of the information stored in your keystore  *
* has NOT been verified!  In order to verify its integrity, *
* you must provide your keystore password.                  *
*****************  WARNING WARNING WARNING  *****************

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 1 entry

myspecialkeyalias, Sep 3, 2020, PrivateKeyEntry,
Certificate fingerprint (SHA-256): EA:54:23:F7:05:04:A1:1F:B8:AA:F3:33:0F:52:77:25:71:15:C1:01:D3:61:F0:C9:42:11:D0:C0:5A:F0:48:5B

Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore keystore.jks -destkeystore keystore.jks -deststoretype pkcs12".
$ keytool -list -keystore keystore.jks -storepass:env STOREPASS
Keystore type: JKS
Keystore provider: SUN

Your keystore contains 1 entry

sova.at.or.at, Sep 3, 2020, PrivateKeyEntry,
Certificate fingerprint (SHA-256): EA:54:23:F7:05:04:A1:1F:B8:AA:F3:33:0F:52:77:25:71:15:C1:01:D3:61:F0:C9:42:11:D0:C0:5A:F0:48:5B

Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore keystore.jks -destkeystore keystore.jks -deststoretype pkcs12".

This is probably related to #36

I think this would be a great feature, unfortunately I don't see us having bandwidth to develop it in the foreseeable future. Any chance you'd be up to making a PR?

There is a chance I could take this on.  If we need it in fdroidserver,
then one of us maintainers would likely want to implement this.  Any
ideas how hard it would be?  In theory it should be easy, since keytool
supports it, so the data should be readable.


Tiled layout for loveit

Hi,
I like the tiled layout for your theme. Could you let me know how one would go about such a layout for the loveit theme. I require it for a collaboration and love everything else about loveit theme. Any advice would be appreciated.
Note: only the arrangement of posts  is what i am asking about. I think it should be pretty simple, but due to my inexperience with web development, Im not able to do it without some help
The related issue in loveit repo
https://github.com/dillonzq/LoveIt/issues/332#issue-613740755

I am not sure if I fully understand what you mean.
Is the tiled layout you described is the archive page of hugo-theme-dream?
Actual effect: https://g1eny0ung.site/posts/

The home page I mean

We are considering the dream theme now. Would have been really great if we could have the best of both worlds!

Thx. It's not difficult to implement this. I use https://masonry.desandro.com/ to implement the home page layout.
The source code can be found in https://github.com/g1eny0ung/hugo-theme-dream/blob/master/src/js/main.js#L8

Thanks for the reply will try it out!


IMU stream not woking in D435i

| Camera Model | { D435i } |
| Operating System & Version | {Ubuntu 18.04} |
| Platform | NVIDIA Xavier |
| Language | {python } |
| Segment | {Robot} |
Issue Description
I want to get the angle of the camera. So I run the following code.
import pyrealsense2 as rs
import numpy as np
import math

#get camera angle

anglepip = rs.pipeline()
angleconfig = rs.config()
angleconfig.enable_stream(rs.stream.accel)
anglepip.start(angleconfig)

camera_angle = 0

try:
    while True:
        f1 = anglepip.wait_for_frames()
        accel = f1[0].as_motion_frame().get_motion_data()

        if not accel:
            print("no frame at cam ")
            continue

        accel_angle_x = math.degrees(math.atan2(accel.y, accel.z))
        accel_angle_x = int(accel_angle_x)
        camera_angle= accel_angle_x
        break

finally:
    anglepip.stop()

print("camera angle = " + str(camera_angle))

But the pipline is not giving any frames. I got this error

Traceback (most recent call last):
File "camera_test.py", line 16, in
f1 = anglepip.wait_for_frames()
RuntimeError: Frame didn't arrived within 5000

It works fine on windows PC. But it doesn't work on NVIDIA Xavier.

@malith1992 , IMU drivers are not included in NVIDIA kernels by default. Support for IMU streaming is provided by an alternative implementation in SDK and requires building CMake with -DFORCE_RSUSB_BACKEND=true.
https://github.com/IntelRealSense/librealsense/issues/6112#issuecomment-603970215

@malith1992 , IMU drivers are not included in NVIDIA kernels by default. Support for IMU streaming is provided by an alternative implementation in SDK and requires building CMake with -DFORCE_RSUSB_BACKEND=true.
#6112 (comment)

I have build the CMake with the mentioned flag. Now it gives the angle only once after I connect the camera. If I run the code again, it gives the same error. If I unplug and replug the camera, it gives the angle again for the fresh start.

@malith1992 hello, we'll look and try to reproduce the issue you describe. What SDK version you're using?
The code that you posted will not calculate the camera angles (I suppose you mention the camera inertial orientation or Euler angles):

The accelerometer measures linear forces , i.e. forces applied along the body axes. So the angle  you extract represents the vector of combined forces (gravity + inertial acceleration) applied to the camera's body. It doesn't reflect the body orientation.
The accelerometer can be used to calculate the camera translation vector w.r.t to an arbitrary start point by using  X=Vt+(at^2)/2.

To track the camera's rotation matrix you actually need to measure and integrate the gyro sensor readings.
Combining those two in theory is sufficient to calculate the objects 6-DOF. In practice the inertial measurements are intrinsically noisy and prone to things such as hysteresis. Therefore filtering and additional sensors are often offered to address this, like a dedicated T265 device by Intel.
To get the orientation matrix take a look at the following Librealsense demo -https://github.com/IntelRealSense/librealsense/tree/master/examples/motion

@malith1992 hello, we'll look and try to reproduce the issue you describe. What SDK version you're using?
The code that you posted will not calculate the camera angles (I suppose you mention the camera inertial orientation or Euler angles):

The accelerometer measures linear forces , i.e. forces applied along the body axes. So the angle  you extract represents the vector of combined forces (gravity + inertial acceleration) applied to the camera's body. It doesn't reflect the body orientation.
The accelerometer can be used to calculate the camera translation vector w.r.t to an arbitrary start point by using  X=Vt+(at^2)/2.

To track the camera's rotation matrix you actually need to measure and integrate the gyro sensor readings.
Combining those two in theory is sufficient to calculate the objects 6-DOF. In practice the inertial measurements are intrinsically noisy and prone to things such as hysteresis. Therefore filtering and additional sensors are often offered to address this, like a dedicated T265 device by Intel.
To get the orientation matrix take a look at the following Librealsense demo -https://github.com/IntelRealSense/librealsense/tree/master/examples/motion

I used Jetpack 4.3 for the Xavier.
It's my mistake to mention it as camera angle. To be honest, I need the Euler angle as written in the code. Thank you for look in to it.

Just curious about the status because the test script seems to work fine here:
nvidia@xavier2:~/work/librealsense$ git log
commit 8e04cdd59276f60dc625cf8ef974daf833bc8d18 (HEAD)
Author: ev-mp<EMAIL_ADDRESS>Date:   Sun Jun 14 09:47:12 2020 +0300

    Fix CUDA compilation. Fix gcc-pedantic remarks. Addresses #6573

commit 8594d09f092347a8b3d832d14e4fb631140620c5 (tag: v2.35.2)
Merge: a9b2615a8 91cc6c73d
Author: ev-mp<EMAIL_ADDRESS>Date:   Tue Jun 9 21:05:47 2020 +0300

    Merge pull request #6557 from IntelRealSense/rc3

    v2.35.2 - Merge to development

nvidia@xavier2:~/github-6385$ uname -ra
Linux xavier2 4.9.140-tegra #1 SMP PREEMPT Mon Dec 9 22:52:02 PST 2019 aarch64 aarch64 aarch64 GNU/Linux
nvidia@xavier2:~/github-6385$ cat /etc/nv_tegra_release
# R32 (release), REVISION: 3.1, GCID: 18186506, BOARD: t186ref, EABI: aarch64, DATE: Tue Dec 10 07:03:07 UTC 2019
nvidia@xavier2:~/github-6385$ rs-enumerate-devices -s
Device Name                   Serial Number       Firmware Version
Intel RealSense D435I<PHONE_NUMBER>92        <IP_ADDRESS>
nvidia@xavier2:~/github-6385$ python3 ./github-6385.py
camera angle = 1
nvidia@xavier2:~/github-6385$ python3 ./github-6385.py
camera angle = -86
nvidia@xavier2:~/github-6385$ python3 ./github-6385.py
camera angle = -179
nvidia@xavier2:~/github-6385$ python3 ./github-6385.py
camera angle = 0

The ticket will be closed in 7 days if no further help is needed. Thank you.


Debug flag

For #391.  Added print of stdout/stderr when --verbose is present on startup commands

+1


log4j-finder will change acces time of a jar file

I know that acces time of a file only gives a mere indication but ik could help a little bit.  On linux  (and aix) you could use the touch command to save the timestamp in a temporary file.  And restore it afterwards.
like:
save_command = "touch -r '{}' /tmp/timestamp.save"
rest_command = "touch -r /tmp/timestamp.save '{}'"

run(save_command.format(<jar_file>))
<do the check>
run(rest_command.format(<jar_file>))

I tried to patch the code with this but I can't.  And I don't really now if it is a good idea to do that anyway
FYI i wrote a run function in python.

Python has an API called os.utime that can set access time on files I believe, of course you will need to have the correct user permissions on the file to be able to do that. This is better than calling subprocesses.

True. Your solution is also more portable.
My solution has another problem. The file /tmp/ may be mounted with the noaitme option on AIX. This prevents updating the atime from a file in the filesystem.  I don't know if touch will update the atime in this case.
linux should have a similar option I suppose.


Update version: Love2d.Love2d version 11.5

Pull request has been created with komac v2.0.0 :tangerine:

Resolve: #133470

Microsoft Reviewers: Open in CodeFlow

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping @Exorcism0666, I'll get a notification.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！


Make ConstProp pass more concise

I was going to augment it, but thought it best to clean it up first.

Merged ecc5c3d0934b11a9b727390853f84996c13dbb42


[ In Complete Docs ]  - Getting SI Running with MI in Five Minutes

Description:
The doc  Getting SI Running with MI in Five Minutes is incomplete and with broken steps.

The siddhi app configuration needs to be updated.
The URL to invoke needs to be updated.
Few pieces of information about respond mediator and etc needs to be updated.

Please re-visit and update them. You may refer https://github.com/wso2/streaming-integrator/tree/master/modules/samples/artifacts/ConnectToMicroIntegratorFromSI

Please check the corrections done via [1].
[1] #1011

Added a comment, please check.

The comments in this thread as well as the related mail are addressed via [1].
[1] https://github.com/wso2/docs-ei/pull/1019

Please note that steps provided in the Triggering Integration Flows tutorial [1] still do not work. Please advise what needs to be changed.
[1] https://ei.docs.wso2.com/en/latest/streaming-integrator/examples/triggering-integrations-via-micro-integrator/

There was a mismatch in the port mentioned in the Siddhi application and the port in the curl command. Also added instructions to install the required Siddhi extensions. Tested the tutorial after making the changes.


incorrect masakari work on centos9

Hello Masakari team! Can you help me? I installed Masakari on centos9, the openstack zen version, when I run the "openstack segment list" command, I get a 'segment' when I should get an empty deadline, I previously deployed Masakari on Ubuntu 22, the openstack yoga version and it worked, tell me what the problem is, how to fix it?

I fixed it, the problem was in endpoint, I replaced my endpoint with "http://:/v1/%(tenant_id)s" to "http://:" and it worked


Generate scoped search key

Typesense allows you to create API Keys with fine-grained access control. You can restrict access on a per-collection, per-action, per-record or even per-field level or a mixture of these.
https://typesense.org/docs/0.22.1/api/api-keys.html#generate-scoped-search-key

Hi @Brent7788, it looks good! Thanks, for the contribution. I'll merge it in and make a new release.


Added Code for fire detection in video and image files

I have added the code for fire detection using OpenCV and Python in images and audio files. Also have provided basic steps to run the code on any image and video file.

Hi Sir, I am new to open source. I see a failed build. Is there any issue with my code?

hey, I would love to work on this project if the issue is still open.


i need to add ionic tags to this editer

is there any way to put the ionic tags to this editer ????????
plz help me with that

Hello @alimuhnad Could you please elaborate more on what you mean when referring to ionic tags?

hi there is ionicframework tags
check this out
https://ionicframework.com/docs/intro/cdn
now if we do it it will be super easy for us to create pages ui

So, you would like to import some Ionic framework scripts and CSS inside the editor, right?

yes plz can we do that ? how ?

hi any idea??


Update node.js.yml

added required library for node-canvas fix to remote pipeline

I have successfully reviewed this change o7


Unknown type name 'CGFloat'

When i pod update and build, i failed and get the message "unknown type name 'CGFloat'" in INTULocationDefines.h. I don't know how to fix it, ty.
The problem code is: static const CGFloat kINTUHorizontalAccuracyThresholdCity =         5000.0;
I fix the bug when i add "~>1.0" in my podfile. But why it didn't work in 2.0.0 version?

Hey, thanks for reporting this!
v2.0.0 changed how some of these constants are defined. I've made a change so that <Foundation/Foundation.h> is now imported at the top of that file, which should fix the issue. Can you please try updating to the latest pod version (v2.0.1) and seeing if the issue is resolved?

Thank you for watching this issue, I resolve the issue by updating. Maybe I can say "thanks" in chinese.

Maybe u need reopen the issue. I find I fix the bug not because updating, the real reason is that I add a pch file in my project. And i add "#include <UIKit/UIKit.h>" in the file. So if I want to use the library, I must add a pch file? Apple remove pch file in Xcode6 project template which means I must add it by manual.

You do not need a PCH file to use INTULocationManager. I just tested creating a new project using Xcode 6, and adding just the INTULocationManager pod, and the project builds & runs successfully.
There must be an issue with your specific build configuration that is causing the problem...I would suggest trying to remove your PCH file, and then doing a full Clean/Clean Build Folder (and/or just delete the DerivedData folder for your Xcode Workspace). Then try building again.
There shouldn't be any changes required to the INTULocationManager pod to fix this.

I success after delete DerivedData, don't notice it before. Thanks a lot for ur help.


The GPU must be Tesla when build container with docker image-gpu?

Question
[A clear, concise description of your setup and question]
When I create the container from the docker image (GPU version), always failed. I was wondering if the GPU must be Tesla or not?
Additional Context
[Add any additional information here]

Thank you for your reply. That works.


No attached service to type named a2lix_translations

sf 2.8
i use sonata admin and A2lixI18nDoctrineBundle
Got htis error when i use  $formMapper->add('translations', 'a2lix_translations');

ok, you must use this only in configureFormFields method


Autocompletion does no longer work with v2

> eval "$(_VIUR_COMPLETE=bash_source viur)"
bash: Syntaxfehler beim unerwarteten Symbol »(«
> echo "$(_VIUR_COMPLETE=bash_source viur)"
ERROR: The configuration in project.json contains invalid JSON: Expecting value: line 1 column 1 (char 0). Please verify right syntax.

I'm using bash.
The viur-cli must not require a project.json when printing the help.
As workaround I've added a project.json into my home dir -- but that's not nice.

Should be fixed with #175 . Please Remember to delete the workaround home dir project.json file, since the searh for the file is done recursively.

Should be fixed with #175 . Please Remember to delete the workaround home dir project.json file, since the searh for the file is done recursively.

Okay, thanks. I'll wait for the release to test it :)


[Bug] Set-DbaPowerPlan fails on WS2019

Environmental information
#### PowerShell version:
Name                           Value
----                           -----
PSVersion                      5.1.17763.1007
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.1007
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

#### dbatools Module version:
Name    : dbatools
Path    : C:\Users\a-bent\Documents\WindowsPowerShell\Modules\dbatools\1.0.107\dbatools.psd1
Version : 1.0.107

LCID             Name             DisplayName
----             ----             -----------
5129             en-NZ            English (New Zealand)

Report
On Windows Server 2019, the Set-DbaPowerPlan command fails as it appears the 'Activate' Cim Method for Win32_PowerPlan appears to be broken.
This seems to be widely reported in other community projects:

ComputerManagementDsc Issue #155
Ansible Issue #43827

Like other projects, it looks like the only option is to use the Windows APIs via powercfg.exe command.
Host used

[x] powershell.exe
[ ] ISE
[ ] VS Code
[ ] Other (please specify)

If anything other than powershell.exe was used, please confirm that you can duplicate the issue with powershell.exe

[ ] Still buggy in powershell.exe

Errors Received
writeErrorStream      : True
PSMessageDetails      :
Exception             : System.Exception: Couldn't set the requested Power Plan 'High Performance' on sqlserver.
TargetObject          : sqlserver
CategoryInfo          : ConnectionError: (sqlserver:PSObject) [Write-Error], Exception
FullyQualifiedErrorId : dbatools_Set-DbaPowerPlanInternal,Stop-Function
ErrorDetails          : Couldn't set the requested Power Plan 'High Performance' on sqlserver.
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at Stop-Function, C:\Users\username\Documents\WindowsPowerShell\Modules\dbatools\1.0.107\allcommands.ps1: line 82910
                        at Set-DbaPowerPlanInternal, C:\Users\username\Documents\WindowsPowerShell\Modules\dbatools\1.0.107\allcommands.ps1: line 65811
                        at Set-DbaPowerPlan<Process>, C:\Users\username\Documents\WindowsPowerShell\Modules\dbatools\1.0.107\allcommands.ps1: line 65849
                        at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {0, 1}

Steps to Reproduce
Run the Set-DbaPowerPlan command on a fresh deployment of Windows Server 2019
Set-DbaPowerPlan -ComputerName sqlserver

Expected Behavior
Windows Power Plan to be set to 'High Performance'
Actual Behavior
Error thrown and Power Plan failed to update.

I just ran into this problem and had a look at the links above.
https://github.com/ansible/ansible/issues/43827 is really helpful if you have a look at the coresponding pull request https://github.com/ansible/ansible/pull/51471 and there the file https://github.com/jborean93/ansible/blob/65a10d21d3ea6424f0d7b162c9b74853cb5b22dc/lib/ansible/modules/windows/win_power_plan.ps1
The code there seems to work (works on my lab with a windows server 2019) and could maybe adopted for dbatools.
@potatoqualitee : As I haved worked with Windows-DDLs and powershell yet - do you have commands in dbatools that allready use Windows-DLLs?

We do not use any Windows DLLs currently.


Option for headers to start collapsed

Adds option for new headers to start out already collapsed/folded. Fixes 'Fold all' and 'Unfold all' buttons to affect everything instead of just dungeons (e.g. Trade, Misc., etc.), for compatibility with new option.
Also adds hotkey (middle click on a header) to toggle collapse/fold on all headers.
I don't speak the other supported languages so I used Google translate for those strings. They should be reviewed.

I feel a Shift+click is a more common gesture for "do something to multiple things". Thoughts?

I feel a Shift+click is a more common gesture for "do something to multiple things". Thoughts?

I think shift + click is associated with getting player info. Thats actually what it currently does if you shift click on a the posters name in BB

I don't have a strong preference on the hotkey, I switched it to Shift+Left-Click. Only Left-Click was bound to anything for headers.


[AlwaysOnTop]Graphical glitches from the border when two always on top Windows intersect

Microsoft PowerToys version
0.53
Running as admin

[ ] Yes

Area(s) with issue?
AlwaysOnTop
Steps to reproduce
If two Always On Top Windows intersect, the borders behavior is not consistent and can be glitchy.
Having two always on top windows, switching between them (without moving them) results in border being visible partially:

Changing the border's thickness in settings makes the intersecting borders glitch a bit too.
✔ Expected Behavior
That the Window that's actually on top still shows its border.
❌ Actual Behavior
That the Window that's actually on top gets its border hidden.
Other Software
No response

Solved a while ago :)


Improvements for Asset Settings

It includes:

Configuration per asset (DAI, USDC).
rateProcessFrequency: frequency (in # blocks) to process the cToken exchange rate (in TheGraph).
maxLendingAmount: max amount to borrow.
Unit tests for new changes.

It was done in #96


remove questionable 100fr dut config

fixes #2977

This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia’s intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind.

Pull Request Functional Test Report for #3153 / 4b2d90bd287670898ebfcd01469eefb7888613b1
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Cisco 8000E

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Cisco XRd

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Juniper ncPTX

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Nokia SR Linux

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Openconfig Lemming

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Cisco 8808

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Juniper PTX10008

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Nokia 7250 IXR-10e

RT-2.13: Weighted-ECMP for IS-ISTE-17.1: VRF selection policy driven TETE-16.1: basic encapsulation testsTE-16.2: encapsulation FRR scenariosTE-16.3: encapsulation FRR scenariosTE-3.2: Traffic Balancing According to WeightsRT-5.7: Aggregate Not Viable All

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls


fix: logging null reference when batch processing

Please provide the issue number

Issue number: #517
Summary
Fix null reference exception on release 1.8.2 when using batch
Changes

Please provide a summary of what's being changed

User experience

Please share what the user experience looks like before and after this change

Checklist
Please leave checklist items unchecked if they do not apply to your change.

[x] Meets tenets criteria
[x] I have performed a self-review of this change
[x] Changes have been tested
[x] Changes are documented
[x] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (712bb96) 72.50% compared to head (888aa19) 72.13%.

Files
Patch %
Lines

...da.Powertools.Logging/Internal/PowertoolsLogger.cs
33.33%
1 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #521      +/-   ##
===========================================
- Coverage    72.50%   72.13%   -0.37%
===========================================
  Files          101      101
  Lines         4106     4106
  Branches       417      418       +1
===========================================
- Hits          2977     2962      -15
- Misses        1017     1030      +13
- Partials       112      114       +2

Flag
Coverage Δ

unittests
72.13% <33.33%> (-0.37%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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