text:
refactor: use StringBuilder instead of List

Replace List<string> with StringBuilder in Htmlizer
The PR replaces the current List<string> with a StringBuilder.  This brings mainly 3 advantages:

Make the intent better visible
Less allocations
Better performance

I know the original implementation comes from @SteveSandersonMS, but not sure what the motivation was.
Anyway I thought I take the lead and propose a different approach with the given advantages on the top.
Feedback very welcome.
Rendering a sample component
The test just renders a rather small component. The results will be even better when we render bigger components.
For the test I used the MultipleChildContent as reference.
Old
|          Method |     Mean |   Error |   StdDev |   Gen 0 |   Gen 1 | Allocated |
|---------------- |---------:|--------:|---------:|--------:|--------:|----------:|
| RenderComponent | 388.9 us | 7.72 us | 19.07 us | 42.9688 | 14.1602 |    179 KB |

New
|          Method |     Mean |   Error |   StdDev |   Gen 0 |   Gen 1 | Allocated |
|---------------- |---------:|--------:|---------:|--------:|--------:|----------:|
| RenderComponent | 368.3 us | 7.77 us | 22.03 us | 41.0156 | 13.6719 |    170 KB |

General
In general StringBuilder is faster and uses less allocations than a List<string>.
I built a small sample benchmark with the following results:
|          Method |       Mean |    Error |   StdDev |     Median | Ratio | RatioSD |  Gen 0 | Allocated |
|---------------- |-----------:|---------:|---------:|-----------:|------:|--------:|-------:|----------:|
|          ByList | 1,993.5 ns | 58.49 ns | 167.8 ns | 1,988.0 ns |  1.00 |    0.00 | 0.7744 |      3 KB |
| ByStringBuilder |   896.6 ns | 78.55 ns | 231.6 ns |   811.9 ns |  0.45 |    0.12 | 0.5980 |      2 KB |

Great idea, really like that you find these relatively low hanging fruits. Lets use a StringBuilder pool for even better performance (https://www.meziantou.net/stringbuilder-performance-pitfalls.htm#use-a-pool-of-string).
Ps. I have been meaning to set up it would be a great idea to set up micro performance tests to (benchmark.net) to start monitoring the speed of bUnit, and potentially in the future, try to optimize it. Looks like you have something set already here.

Good idea. I will create a separate PR for the setup... that was rather quick and dirty and should not be commited at all :D
Anyway I added the StringBuilderPool.

Might be interesting to do some benchmarking to see if an object pool is always better. Perhaps it only really matter if a TestContext is used with 20-30 re-renders.

I can do some testing later today or tomorrow to verify that.
Maybe it would even be worth to even tackle #703 to some extend with this PR as well... what do you think?

One thing I noticed when running the benchmarks, if we "reuse" the TestContext like this:
public void Benchmark
{
    private readonly TestContext context = new();

    [Benchmark]
    public IRenderFragmentBase Render() => context.RenderComponent<Component>();
}

It becomes slower and slower and slower. Only if I create the TestContext and dipose it directly after use the runtime is const.
You can super easily reproduce this via:
var ctx = new TestContext();

var stopwatch = Stopwatch.StartNew();
for (var i = 0; i < 100_000; i++)
{
    _ = ctx.RenderComponent<Counter>();

    if (i % 1000 == 0)
    {
        Console.WriteLine($"Average run took: {stopwatch.ElapsedMilliseconds / 1000} ms");
        stopwatch.Restart();
    }
}

Output for me:

Average run took: 0 ms
Average run took: 0 ms
Average run took: 2 ms
Average run took: 4 ms
Average run took: 6 ms
Average run took: 9 ms
Average run took: 10 ms
Average run took: 13 ms
Average run took: 15 ms
Average run took: 19 ms
Average run took: 19 ms
Average run took: 20 ms

I render here multiple 1000 components, so that is something normal users will most likely never experience, but when we want to benchmark certain aspect we might want to investigate what is pilling up here.

I think it makes sense that it becomes slower, since there is some internal dictionaries/arrays in the TestRenderer and Renderer that grows whenever we render a component. I am surprised. But it might be worth bringing up in the docs as another good reason not to reuse the TestContext between tests (ive seen people do this).

I checked with some benchmark. The StringBuilderPool causes a bit more memory with almost the same performance.
I guess we could drop the pooling.. or maybe I did a major flaw with those few lines of code.

Its a balancing act between maintainable code and perf. Fine to drop StringBuilderPool if there is little benefit at the typical usage pattern. ValueStringBuilder sounds interesting. If its an easy thing to try, it would be fun to do.

The last commit adds the ValueStringBuilder. I took only the necessary parts from my own library here.
The results are pretty nice. Again I use the MultipleChildContentas reference.
The test looks like this:
[Benchmark]
public IRenderedFragmentBase RenderCounter()
{
    using var ctx = new TestContext();
    return ctx.RenderComponent<MultipleChildContent>();
}

Using List<T>
|          Method |     Mean |   Error |   StdDev |   Gen 0 |   Gen 1 | Allocated |
|---------------- |---------:|--------:|---------:|--------:|--------:|----------:|
| RenderComponent | 388.9 us | 7.72 us | 19.07 us | 42.9688 | 14.1602 |    179 KB |

Using StringBuilder
|          Method |     Mean |   Error |   StdDev |   Gen 0 |   Gen 1 | Allocated |
|---------------- |---------:|--------:|---------:|--------:|--------:|----------:|
| RenderComponent | 368.3 us | 7.77 us | 22.03 us | 41.0156 | 13.6719 |    170 KB |

Using ValueStringtBuilder
|        Method |     Mean |   Error |   StdDev |   Median |   Gen 0 |   Gen 1 | Allocated |
|-------------- |---------:|--------:|---------:|---------:|--------:|--------:|----------:|
| RenderCounter | 309.9 us | 8.97 us | 25.45 us | 301.0 us | 40.5273 | 13.1836 |    166 KB |

Now the major downside of a ValueStringBuilder is the fact that it is a ref struct which forces passing the object around a lot via ref.

Seems like some tests are failing. I'll investigate that later. From my point of view the "normal" StringBuilder would be a nice middleground. Basically adds no more complexity than the solution before and we get some performance improvements. The ValueStringBuilder is quite deep into the code.

Agreed, lets stick with a regular StringBuilder. Good work btw.!

Thanks. I dropped the last commit and added the change to CHANGELOG.md

Feel free to merge when you have the tests passing. If they fail for the usual reason, just rerun the tests.

Has to re run it twice but I could merge :)

authors: egil linkdotnet

repo: bUnit-dev/bUnit


text:
trying XML RPC client with an https request

Hi,
I'd like to use your node xmlrpc module to make requests to a Odoo server
http://www.odoo.com/documentation/10.0/api_integration.html
I've tried :
const client = xmlrpc.createClient("https://[myOdooServer]/xmlrpc/2/common")
client.methodCall('version ', [], function (error, value) {
console.log('Method response for 'version': ' + value)
})
And I've got the following error :
http_client.js:55
throw new Error('Protocol "' + protocol + '" not supported. ' +
^
Error: Protocol "https:" not supported. Expected "http:"
Do I miss something or is this module not adapted for https requests ?

you need to use:
const client = xmlrpc.createSecureClient("https://[myOdooServer]/xmlrpc/2/common")

(I also found that confusing)

This one works for me (v15) enterprise:
const client = xmlrpc.createSecureClient(url+"/xmlrpc/2/common");
client.methodCall('version', [], function (error, value) {
  if (error){
    console.log('Error when calling a method: '+ error);
    return;
  }
  console.log('Method response for version: ', value);
});

client.methodCall('authenticate', [db, username, password, {}], function (error, uid) {
  if (error){
    console.log('Error when calling a method: '+ error);
    return;
  }
  console.log('uid:', uid);
});

source: gharchive/issue

authors: bitsnaps grahamrhay natoine

repo: baalexander/node-xmlrpc

license: mit

license_type: permissive

license_source: bigquery


text:
Document v6 API

This issue is to track items that need more documentation and will be updated as time goes on. Items can be split off into their own issues as necessary.
NOTE: To anyone reading this: There is some degree of speculation here about what is public API. This is not the documentation. None of this is confirmed public API until and unless it's documented.

[ ] Plugins

[ ] inherits (confirmed public by sebmck on slack). Example:
module.exports = function SomePlugin () {
  return {inherits: require("some-syntax-plugin")};
}

@jmm There's already a list of methods to be documented that @sebmck and I when through. It's everything on this page: https://gist.github.com/thejameskyle/ccc0811f6c8ab4f73ee4
I want to setup documentation.js in the normal codebase to generate API documentation for these methods.

@thejameskyle Oh cool, thanks for the link. Would it be better for me to add stuff that's not on that list here, or comment on the gist? For example, inherits|manipulateOptions|pre|post keys on the object returned by a plugin?

I want to setup documentation.js in the normal codebase to generate API documentation for these methods.

I haven't tried it yet, but it sounds interesting.

Ah, that will be covered by the handbook I'm writing right now on writing babel plugins. It's just taking a while because writing is hard.

@thejameskyle That's awesome! Can't wait to see it.
I need to keep a running list of undocumented parts of the API because it tends to just come out in bits and pieces looking through the source, looking at existing plugins, on slack, etc. If it's not going to bother you I'll do it here (and then when your handbook or whatever documentation comes out boxes can get ticked). If it's somehow unhelpful to you to do it here I'll just create my own repo or something, although if it's here other people can find some of the stuff too.

I think the most helpful thing would be documenting the APIs in https://gist.github.com/thejameskyle/ccc0811f6c8ab4f73ee4. That's going to take the bulk of the time.
I'll open a PR tonight or tomorrow to setup documentation.js in the Babel codebase. (You can also take a crack at it if you want).
I'm also going to try powering through the handbook this weekend, at least enough for an initial version.

https://github.com/thejameskyle/babel-handbook/blob/master/translations/en/plugin-handbook.md is out and I added info on inherits specifically so going to close this one.
Yes we still need some actual docs though

authors: hzoo jmm thejameskyle

license: MIT

license_source: github-api


text:
Document refresh

It is possible to change the flight option in the configuration scout_elastic => document_refresh ??
I currently use 'wait_for' but when I try to import an xls file into the queue it is slow because we have to wait for the indexing in elasticsearch.

@yashiroiori, you can use Config::set('scout_elastic.document_refresh', 'false') to change configuration on the fly.

@babenkoivan this only affect at the moment are run queue?? Or all system are affected??

authors: babenkoivan yashiroiori

repo: babenkoivan/scout-elasticsearch-driver


text:
🛑 SM Service is down

In 0fd5735, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 1e07496 after 10 minutes.

repo: bachmannschumacher/upptime


text:
🛑 SM Service is down

In a67af6a, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 8892514 after 31 minutes.


text:
A quesion about the arch of resnet50

https://github.com/backseason/PoolNet/blob/cf8ae8f5bc7a4a894f6d8755b5475e7856a253d2/networks/deeplab_resnet.py#L104
Hi, would you like to tell why you set ceil_mode to True? is it that a trick to get better performance or some other reason?

It's a simple copy of https://github.com/isht7/pytorch-deeplab-resnet/blob/839bdcec7814be52498f2c22b1020d7d2e9f4d16/deeplab_resnet.py#L134

Thanks

authors: backseason hideonInternet

repo: backseason/PoolNet


text:
[GitHub Actions Plugin] Support mono repos with multiple components with distinct workflows

We've had users come to us asking for better support for monorepos where different components have their own workflows. As is (AFAICS) the plugin fetchs all workflow runs for the repo.
Feature Suggestion
Support specifying which workflows relate to a given component.
Possible Implementation
Could use listWorkflowRuns with a workflow ID to list only runs for a given workflow. Downside is this would lead to multiple calls if several workflows are required. Alternatively, we could filter after the fact. This requires the user to know the numeric ID (where the API accepts filename also but perhaps we can do this translation at the cost of a request).
Perhaps this would require a new annotation (e.g. github.com/workflow-ids: 'one.yaml,two.yaml')? This would need to be a list to be useful but that could be difficult to manage (especially as file path is the easiest way to specify workflow ID). Alternatively, these could be passed as props (like branch for example).
Context
I can work on this if there's an acceptable way to implement this.
I came across this look for an existing issue but I believe it's different.
[GitHub Actions Plugin]

Sounds like a good area for improvement, and I think we could go either in a more generic direction with a solution that might apply to all CI/CD plugins, or something that only works for GitHub actions, or a bit of both.
One thing to consider here could be to use the workflow files to derive the information, basically by matching the path patterns against the source locations of the entities. May be best to add a backend plugin if we want to do that though.
Tbh I somewhat feel that a refactor of the API might make sense here as well. Right now the React code is unpacking the information in the entity and passing it to the API, which makes it impossible to inject different behavior at that point. If the API was closer to listWorkflowRuns({entity}) then we'd be able to provide a lot more flexibility in how the mapping to workflow runs is handled

Hi!
Sorry about the delay replying here I went on PTO for a couple of weeks shortly after creating this.
Using the workflow files does seem like it'd be robust though you'd really wish that data was available through the API (though it doesn't look like it is).

I think we could go either in a more generic direction with a solution that might apply to all CI/CD plugins, or something that only works for GitHub actions, or a bit of both.

I'm curious about this are we talking about simply a common approach or a shared interface for the API that CI plugins could implement? Or do I misunderstand?

@iain-b Yep could be a common approach across CI plugins. That's ofc very tricky though which is why it could make sense to at least start with something GH specific

Hi guys @iain-b @Rugvip! I'm interested in this. I have a monorepo with multiple components inside, and it would be very useful to be able to filter the specific workflow of the component. Is this currently possible?

authors: MnLujan Rugvip iain-b

repo: backstage/backstage


text:
🐛 Bug Report: empty alert message after 60+ seconds

📜 Description
When a scaffolder action is running and doesn't provide a message to display in the UI for more than 60 seconds, then an empty alert message will be displayed and no further progress for the task activity will be reported in the UI.
👍 Expected behavior
There should be no empty alert messages displayed in the UI.
👎 Actual Behavior with Screenshots
Although the UI no longer reports any task activity messages or progress, the task does actually continue running in the background and subsequent scaffolder actions will be executed.
UI showing a blank alert message:

👟 Reproduction steps
A testcase to reproduce the behavior is described below.  Using this testcase, execute the template and specify input parameters for interval and delaySeconds to ensure that an info message is not sent to the UI for 60 seconds or more (e.g. delaySeconds=10 and interval=6)
❗ This behavior has not been reproducible when running Backstage locally, nor when running the built container locally.  This behavior has only been observed, so far,  with the built container deployed to AWS running behind an ALB:

In backstage/packages/backend/src/plugins/scaffolder.ts:

import { createTestLoggerAction } from './scaffolder/actions/create-testlogger.ts';
...
const actions = [
   ...builtInActions,
   createTestLoggerAction(),
];

Create a backstage/packages/backend/src/plugins/scaffolder/actions/create-testlogger.ts file with the following content:

import { createTemplateAction } from "@backstage/plugin-scaffolder-backend";

export function createTestLoggerAction() {

  return createTemplateAction<{ interval: number; maxSeconds: number, delaySeconds: number }>({
    id: 'test:slowAction',
    schema: {
      input: {
        required: ['interval', 'maxSeconds', 'delaySeconds'],
        type: 'object',
        properties: {
          delaySeconds: {
            type: 'number',
            title: 'Delay time',
            description: 'The number of seconds a "setTimeout" should run',
          },
          interval: {
            type: 'number',
            title: 'Interval',
            description: 'The number of setTimeouts to run in between info log messages.',
          },
          maxSeconds: {
            type: 'number',
            title: 'Maximum',
            description: 'The maximum number of seconds that this action should run',
          },
        }
      },
    },
    async handler(ctx) {
      const { interval, maxSeconds, delaySeconds } = ctx.input;
      ctx.logger.info("Entering the slow action with delayed logger.");
      ctx.logger.info(`Interval between "Status" info log messages is ${interval * delaySeconds} seconds.`);
      ctx.logger.info(`The amount for a timeout is ${delaySeconds} seconds.`);

      let index = 0;
      let status: string | undefined = 'RUNNING';
      while (status === 'RUNNING') {
        if (index % interval === 0) {
          ctx.logger.info(`Status: ${status}`);
        }
        await new Promise(resolve => setTimeout(resolve, delaySeconds * 1000));
        if ((index * delaySeconds) >= maxSeconds) {
          status = 'DONE';
        }
        index++;
      }
      ctx.logger.info("Action is completed.");
    },
  });
}

Create a test-logger-template.yaml file with the following content and make it available to Backstage through app-config.yaml or host it somewhere and import via URL.

apiVersion: scaffolder.backstage.io/v1beta3
kind: Template
metadata:
  name: slow-action-template
  title: Slow Action Template
  description: An example template to reproduce delayed logging behavior due to a long action
spec:
  owner: group:everyone
  type: service
  parameters:
    - title: Provide some test parameter information
      required:
        - delaySeconds
        - interval
        - maxSeconds
      properties:
        delaySeconds:
          title: Seconds to delay
          type: number
          description: The number of seconds to run a setTimeout delay
        interval:
          title: Interval
          type: number
          description: Number of setTimeouts between issuing an info-level log message
        maxSeconds:
          title: Maximum Seconds
          type: number
          description: The maximum number of seconds to run the test

  steps:
    - id: slowactiontest
      name: Slow Action Logging test
      action: test:slowAction
      input:
        delaySeconds: ${{ parameters.delaySeconds }}
        interval: ${{ parameters.interval }}
        maxSeconds: ${{ parameters.maxSeconds }}

📃 Provide the context for the Bug.
A custom scaffolder action may have justification to run for several minutes between meaningful updates to the UI.  For example, it may invoke an external API which needs to be restricted due to cost reasons or throttling by the 3rd party.
Workarounds are easy to implement by ensuring that some information is sent to the UI at least once every <60 seconds; however, without knowing about this behavior, it is difficult to debug.
🖥 Your Environment
tested with Chrome browser Version 110.0.5481.177 (Official Build) (arm64)
yarn backstage-cli info output:
yarn run v1.22.19
$ /backstage/node_modules/.bin/backstage-cli info
OS:   Darwin 22.3.0 - darwin/arm64
node: v18.14.2
yarn: 1.22.19
cli:  0.22.1 (installed)
backstage:  1.10.0

Dependencies:
  @backstage/app-defaults                          1.1.0
  @backstage/backend-app-api                       0.3.1
  @backstage/backend-common                        0.18.1
  @backstage/backend-plugin-api                    0.3.1
  @backstage/backend-tasks                         0.4.2
  @backstage/catalog-client                        1.3.0, 1.3.1
  @backstage/catalog-model                         1.1.5, 1.2.0
  @backstage/cli-common                            0.1.11
  @backstage/cli                                   0.21.1, 0.22.1
  @backstage/config-loader                         1.1.8
  @backstage/config                                1.0.6
  @backstage/core-app-api                          1.4.0
  @backstage/core-components                       0.12.3, 0.12.4
  @backstage/core-plugin-api                       1.3.0, 1.4.0
  @backstage/dev-utils                             1.0.11
  @backstage/errors                                1.1.4
  @backstage/integration-aws-node                  0.1.1
  @backstage/integration-react                     1.1.9
  @backstage/integration                           1.4.2
  @backstage/plugin-api-docs                       0.8.14
  @backstage/plugin-app-backend                    0.3.41
  @backstage/plugin-auth-backend                   0.17.4
  @backstage/plugin-auth-node                      0.2.10
  @backstage/plugin-catalog-backend                1.7.1
  @backstage/plugin-catalog-common                 1.0.10, 1.0.11
  @backstage/plugin-catalog-graph                  0.2.26
  @backstage/plugin-catalog-import                 0.9.4
  @backstage/plugin-catalog-node                   1.3.2
  @backstage/plugin-catalog-react                  1.2.4, 1.3.0
  @backstage/plugin-catalog                        1.7.2
  @backstage/plugin-github-actions                 0.5.14
  @backstage/plugin-org                            0.6.4
  @backstage/plugin-permission-common              0.7.3
  @backstage/plugin-permission-node                0.7.4
  @backstage/plugin-permission-react               0.4.10, 0.4.9
  @backstage/plugin-proxy-backend                  0.2.35
  @backstage/plugin-scaffolder-backend             1.10.1
  @backstage/plugin-scaffolder-common              1.2.4
  @backstage/plugin-scaffolder-react               1.0.1
  @backstage/plugin-scaffolder                     1.10.1
  @backstage/plugin-search-backend-module-pg       0.5.2
  @backstage/plugin-search-backend-node            1.1.2
  @backstage/plugin-search-backend                 1.2.2
  @backstage/plugin-search-common                  1.2.1
  @backstage/plugin-search-react                   1.4.0
  @backstage/plugin-search                         1.0.7
  @backstage/plugin-tech-radar                     0.6.0
  @backstage/plugin-techdocs-backend               1.5.2
  @backstage/plugin-techdocs-module-addons-contrib 1.0.9
  @backstage/plugin-techdocs-node                  1.4.5
  @backstage/plugin-techdocs-react                 1.1.2
  @backstage/plugin-techdocs                       1.4.3
  @backstage/plugin-user-settings                  0.6.2
  @backstage/release-manifests                     0.0.7, 0.0.8
  @backstage/test-utils                            1.2.4
  @backstage/theme                                 0.2.16, 0.2.17
  @backstage/types                                 1.0.2
  @backstage/version-bridge                        1.0.3
Done in 0.67s.

👀 Have you spent some time to check if this bug has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Hmm so first thoughts are that this is something to do with the ALB, maybe timing out or killing the eventsource connection.
When you have this running and switch to the network tab do you see anything suspicious when it throws the error? I wonder if the error is also not been transformed properly, which is why we get an empty error message.
Theres workaround that you could use, which would basically fall back to long polling instead, but would like to narrow down the problem here as to what is going on.

Hmm that error parsing logic seems to be here: https://github.com/backstage/backstage/blob/bc3308947fbd3a81921499bd9aec298bbf14e58c/plugins/scaffolder/src/components/TaskPage/TaskPage.tsx#L365
Which basically renders the message property. https://github.com/backstage/backstage/blob/5fa20eb07cc6b4ee7f49018790951e3a828ed3a1/plugins/scaffolder/src/components/TaskPage/TaskErrors.tsx#L35
Theres an experimental scaffolder version that has actually these pages re-written with different components and that seems to use the ErrorPanel component instead.
https://github.com/backstage/backstage/blob/c9a5a8fcad2af54effd8d380d2e108f4d6aa7961/plugins/scaffolder/src/next/OngoingTask/OngoingTask.tsx#L128-L131
I wonder if you wanted to try and use the experimental scaffolder to see if you still get an empty error message? Looks like a bit of a bug that we don't catch this, but the error panel also does things with the stack trace to show you that too, so it might be better.
There's (https://backstage.io/docs/features/software-templates/testing-scaffolder-alpha/)[some docs here if you wanted to give it a try], because that's gonna be easier to deploy than addition additional logging into node_modules at least I think! 🙇

@benjdlambert  - I saw that there was a new experimental scaffolder in the docs and had it on my list to give it a try.  I probably won't get to it for another week or so, but I'll try the new scaffolder and report back here.  Thanks for the pointers 🙏

authors: benjdlambert jmcvea


text:
🚀 Feature: Kubernetes Plugin not showing up ResourceQuotas

📜 Description
Kubernetes plugin doesn't show resourcequotas informations in UI
I can see that in the API we have the data being retrieved, but it does't show on interface.
👍 Expected behavior
ResourceQuota component being showed in Kubernetes Page
👎 Actual Behavior with Screenshots

My API return:
{
   "items":[
      {
         "cluster":{
            "name":"poc-cluster"
         },
         "podMetrics":[

         ],
         "resources":[
            {
               "type":"pods",
               "resources":[

               ]
            },
            {
               "type":"services",
               "resources":[

               ]
            },
            {
               "type":"configmaps",
               "resources":[

               ]
            },
            {
               "type":"limitranges",
               "resources":[

               ]
            },
            {
               "type":"resourcequotas",
               "resources":[
                  //details about resourcequotas
               ]
            },
            {
               "type":"deployments",
               "resources":[
                  //infos about deployment
               ]
            },
            {
               "type":"replicasets",
               "resources":[

               ]
            },
            {
               "type":"horizontalpodautoscalers",
               "resources":[

               ]
            },
            {
               "type":"jobs",
               "resources":[

               ]
            },
            {
               "type":"cronjobs",
               "resources":[

               ]
            },
            {
               "type":"ingresses",
               "resources":[

               ]
            },
            {
               "type":"statefulsets",
               "resources":[

               ]
            },
            {
               "type":"daemonsets",
               "resources":[

               ]
            }
         ],
         "errors":[

         ]
      }
   ]
}

👟 Reproduction steps
Followed the tutorial at this link to connect my Backstage instance with my AKS Cluster Kubernetes Installation
1.1. My cluster is a AKS
1.2. I using the assume role option to connect to my cluster
Setup my Backstage component manifest with this two labels:
2.1. backstage.io/kubernetes-label-selector: app=app-name,
2.2. backstage.io/kubernetes-id: app-name
Setup my K8S Resourcequotas and components with label: app=app-name
📃 Provide the context for the Bug.
No response
🖥 Your Environment
yarn run v1.22.21
OS:   Darwin 23.3.0 - darwin/arm64
node: v18.19.0
yarn: 1.22.21
cli:  0.25.2 (installed)
backstage:  1.23.3
Dependencies:
@backstage/app-defaults                                          1.5.0
@backstage/backend-app-api                                       0.5.13
@backstage/backend-common                                        0.21.2
@backstage/backend-dev-utils                                     0.1.4
@backstage/backend-openapi-utils                                 0.1.5
@backstage/backend-plugin-api                                    0.6.12
@backstage/backend-tasks                                         0.5.17
@backstage/catalog-client                                        1.6.0
@backstage/catalog-model                                         1.4.4
@backstage/cli-common                                            0.1.13
@backstage/cli-node                                              0.2.3
@backstage/cli                                                   0.25.2
@backstage/config-loader                                         1.6.2
@backstage/config                                                1.1.1
@backstage/core-app-api                                          1.12.0
@backstage/core-compat-api                                       0.2.0
@backstage/core-components                                       0.14.0
@backstage/core-plugin-api                                       1.9.0
@backstage/e2e-test-utils                                        0.1.1
@backstage/errors                                                1.2.3
@backstage/eslint-plugin                                         0.1.5
@backstage/frontend-plugin-api                                   0.6.0
@backstage/integration-aws-node                                  0.1.9
@backstage/integration-react                                     1.1.24
@backstage/integration                                           1.9.0
@backstage/plugin-api-docs                                       0.11.0
@backstage/plugin-auth-backend-module-atlassian-provider         0.1.4
@backstage/plugin-auth-backend-module-aws-alb-provider           0.1.3
@backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.7
@backstage/plugin-auth-backend-module-github-provider            0.1.9
@backstage/plugin-auth-backend-module-gitlab-provider            0.1.9
@backstage/plugin-auth-backend-module-google-provider            0.1.9
@backstage/plugin-auth-backend-module-microsoft-provider         0.1.7
@backstage/plugin-auth-backend-module-oauth2-provider            0.1.9
@backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.1.5
@backstage/plugin-auth-backend-module-oidc-provider              0.1.2
@backstage/plugin-auth-backend-module-okta-provider              0.0.5
@backstage/plugin-auth-backend                                   0.21.2
@backstage/plugin-auth-node                                      0.4.7
@backstage/plugin-catalog-backend-module-bitbucket-server        0.1.25
@backstage/plugin-catalog-backend-module-msgraph                 0.5.19
@backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.9
@backstage/plugin-catalog-backend                                1.17.2
@backstage/plugin-catalog-common                                 1.0.21
@backstage/plugin-catalog-graph                                  0.4.0
@backstage/plugin-catalog-import                                 0.10.6
@backstage/plugin-catalog-node                                   1.7.2
@backstage/plugin-catalog-react                                  1.10.0
@backstage/plugin-catalog                                        1.17.0
@backstage/plugin-events-node                                    0.2.21
@backstage/plugin-github-actions                                 0.6.11
@backstage/plugin-home-react                                     0.1.8
@backstage/plugin-home                                           0.6.2
@backstage/plugin-jenkins-backend                                0.3.6
@backstage/plugin-jenkins-common                                 0.1.24
@backstage/plugin-jenkins                                        0.9.5
@backstage/plugin-kubernetes-backend                             0.15.2
@backstage/plugin-kubernetes-common                              0.7.4
@backstage/plugin-kubernetes-node                                0.1.6
@backstage/plugin-kubernetes-react                               0.3.0
@backstage/plugin-kubernetes                                     0.11.5
@backstage/plugin-org                                            0.6.20
@backstage/plugin-permission-backend                             0.5.35
@backstage/plugin-permission-common                              0.7.12
@backstage/plugin-permission-node                                0.7.23
@backstage/plugin-permission-react                               0.4.20
@backstage/plugin-proxy-backend                                  0.4.10
@backstage/plugin-scaffolder-backend-module-azure                0.1.4
@backstage/plugin-scaffolder-backend-module-bitbucket-cloud      0.1.2
@backstage/plugin-scaffolder-backend-module-bitbucket-server     0.1.2
@backstage/plugin-scaffolder-backend-module-bitbucket            0.2.2
@backstage/plugin-scaffolder-backend-module-cookiecutter         0.2.36
@backstage/plugin-scaffolder-backend-module-gerrit               0.1.4
@backstage/plugin-scaffolder-backend-module-gitea                0.1.2
@backstage/plugin-scaffolder-backend-module-github               0.2.2
@backstage/plugin-scaffolder-backend-module-gitlab               0.2.15
@backstage/plugin-scaffolder-backend                             1.21.2
@backstage/plugin-scaffolder-common                              1.5.0
@backstage/plugin-scaffolder-node                                0.3.2
@backstage/plugin-scaffolder-react                               1.8.0
@backstage/plugin-scaffolder                                     1.18.0
@backstage/plugin-search-backend-module-catalog                  0.1.16
@backstage/plugin-search-backend-module-pg                       0.5.21
@backstage/plugin-search-backend-module-techdocs                 0.1.16
@backstage/plugin-search-backend-node                            1.2.16
@backstage/plugin-search-backend                                 1.5.2
@backstage/plugin-search-common                                  1.2.10
@backstage/plugin-search-react                                   1.7.6
@backstage/plugin-search                                         1.4.6
@backstage/plugin-tech-radar                                     0.6.13
@backstage/plugin-techdocs-backend                               1.9.5
@backstage/plugin-techdocs-module-addons-contrib                 1.1.5
@backstage/plugin-techdocs-node                                  1.11.4
@backstage/plugin-techdocs-react                                 1.1.16
@backstage/plugin-techdocs                                       1.10.0
@backstage/plugin-user-settings                                  0.8.1
@backstage/release-manifests                                     0.0.11
@backstage/repo-tools                                            0.6.2
@backstage/test-utils                                            1.5.0
@backstage/theme                                                 0.5.1
@backstage/types                                                 1.1.1
@backstage/version-bridge                                        1.0.7
Done in 1.07s.
👀 Have you spent some time to check if this bug has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

@matdtr
It is available in POD. Once you expand the pods, open the respective pod it will show the Resource Utilization both requested and limit.
Just make sure skipMetricsLookup: false in your Kubernetes Cluster configuration in app-config.yaml.

Hi @deepan10 I'am talking about namespace resource quotas.


text:
feat: added import entity analytics event

Hey, I just made a Pull Request!
Hi, I added an analytics event for the import button. For me can be a helpful metric.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Updates for this MR? @Rugvip

Done @Rugvip

Done!

source: gharchive/pull-request


text:
Introduced UtilityAPI for Pinniped

Introduced UtilityAPI for Pinniped, which presents the getClusterScopedIdToken fuction to get a Cluster Scoped ID Token which can be passed to backend services to exchange it for mTLS x509 client certs
Hey, I just made a Pull Request!
Fixes #21484
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hello @Rugvip, This month will be my last month at VMware, so I’m trying to finish all my tasks and PRs if it is possible. I still believe core-plugin-api is a good place for pinnipedSupervisorAuthApiRef . When I tried to moved it to kubernetes-react or any other package, I had to modify multiple files to export classes and types from core-plugin-api, so a new AuthConnector and AuthAPIRef could be implemented outside core-plugin-api , you can see those modifications on my last commit cee4fde. If you think this is still a hard requirement, another coworker will take the PR, otherwise let me know, and I can delete the last commit


text:
feat: add catalog ingestion processor for indexing AWS accounts

Signed-off-by: Jonah Back jback@legalzoom.com
Hey, I just made a Pull Request!
This PR adds a processor for ingesting AWS account data from AWS Organizations. It is a very basic processor, but it ingests the minimal amount of data (account name / accound id) for it to be useful for other applications (we are using it to power cost insights for our aws accounts - hopefully that's coming later in another PR :) )
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[] Added or updated documentation
[X] Tests for new functionality and regression tests for bug fixes
[X] Screenshots attached (for UI changes)

This is aws-e-some (ughh, sorry)! A number of review comments but don't let that put you off; a lot of them are discussion pieces / questions :)

authors: backjo freben


text:
Implement DefaultTechDocsCollator

Hey, I just made a Pull Request!
Ref: https://github.com/backstage/backstage/issues/4568

Implements a collator for tech docs.

Retrieves mkdocs created search index for entities that have documentation configured

Registers collator to expose tech docs content to be searchable
Modifies example search to contain tech docs

Displays docs results with link to docs and the entity name as title.

Adds pagination to example search
Creates a reusable type filter to be located in the search package.

Screenshot:

This unblocks: https://github.com/backstage/backstage/issues/4781
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

If we want to include all searchables on that single search screen (which I assume we do right?) we could probably create a new DocumentationResultListItem component to display these documentation searches as a one clump per entity. Mkdocs search_index includes some duplication on texts that have subtitles (parent item contains texts from subitems).

If we want to include all searchables on that single search screen (which I assume we do right?) we could probably create a new DocumentationResultListItem component to display these documentation searches as a one clump per entity. Mkdocs search_index includes some duplication on texts that have subtitles (parent item contains texts from subitems).

^ Indeed.  We've found that filtering out subtitles on the search page (by e.g. tweaking the query in that context such that results with location containing a # are filtered out) while only including the subtitles on an individual TechDocs site (by doing the inverse) offers a decent experience.

Thanks for the comments @iamEAP && @Fox32. I've addressed those and this should be ready for another look through. A bit of a scope creep on the original item but we'll get an e2e document search functionality with this one.
Type filter looks like so:

I will leave this one as inspiration (for the multi select and the length of text in the items). This from our internal instance. We choose to go with a bit different design for the items and have an icon for each entry. We also have breadcrumbs to show the nested structure of docs inside an entity.

Note to myself: Maybe we should filter our ¶ from the text.

Thanks @Fox32 for the screenshot. I modified this open source side as well to have a multiselect possibility when searching. @iamEAP, I think this PR is probably worth another look now to see if we can merge this in or if there are few more tweaks that we should make.

Thanks @iamEAP, I've addressed those comments now.

@benjdlambert when you have a moment ^

Don't want to block this for much longer - let's get it in and iterate. 👍

authors: Fox32 Xantier benjdlambert iamEAP


text:
Feature/gitlab auth provider

Hey, I just made a Pull Request!
Implement auth handler and sign-in resolvers for GitLab auth providers, as described in #6245
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Tests for new functionality and regression tests for bug fixes
[x] All your commits have a Signed-off-by line in the message. (more info)

Hey I've just added the after-vacation label here, as I want to get some extra eyes from the other maintainers when they're back off holiday, although I think it's on the right lines! 🎉

@Rugvip cleaned this pr up based on your feedback. Should be more in line with the github provider now (as opposed to the MS provider I based this on initially).

Looks like API reports are missing which causes the build to fail. Please run yarn build:api-reports and commit the files.

authors: benjdlambert jhaals tom-odb


text:
Add Via as a backstage adopter

Add Via as a backstage adopter
Signed-off-by: Vagner Guedes vagnerguedes@gmail.com
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

@vagnerguedes Sorry - the signoff goes inside the commit body. The text you put in the comment looks correct (when editing it - so that the <> are there), but it needs to be in git's history.
If you are doing this change by editing the file in GitHub's web page, a tip is that you can put that signoff line in the second edit box here, BEFORE pressing Propose changes:

tks a lot @benjdlambert

authors: freben vagnerguedes


text:
Assemble multiple deps

Simple step to (optionally) remove jQuery from lean core as discussed in https://github.com/baconjs/bacon.js/issues/449

Rebased on current master. Mergeable again.


text:
Zenodo is using a god awful Shields-like

My poor little heart.

See: https://guides.github.com/activities/citable-code/
Let's home we can get @lnielsen-cern on board to fix that up.

FYI you can now now pass ?style= to badges on Zenodo.

authors: lnielsen olivierlacan

repo: badges/shields


text:
Jitpack: custom domain for organization

:clipboard: Description
Jitpack.io allows custom domains to be used, but shields.io allows only VCS ones.
It would be nice to add a "custom" or "organization" endpoint to use them (eg: https://img.shields.io/jitpack/v/custom/com.open-meteo/open-meteo-api-kotlin.svg).

This sounds like a reasonable request. Just to flesh out how this would work a bit..
At the moment, if you request https://img.shields.io/jitpack/v/github/jitpack/maven-simple then we call https://jitpack.io/api/builds/com.github.jitpack/maven-simple/latestOk to get the version.
How would your example translate to a JitPack API call?

How would your example translate to a JitPack API call?

You may replace com.github.jitpack with the domain name reverse (io.jitpack); hence:  https://jitpack.io/api/builds/io.jitpack/maven-simple/latestOk

I feel like we've had some past discussions around just requesting the group id (or equivalent) as a free form route parameter instead of trying to do the version control to group id mapping, but my GitHub search skills are failing me. I would much rather we not be in the business of trying to support auto mappings

Yeah it would be nice if we could change this so that the canonical jitpack badge URLs become:

/jitpack/v/com.github.jitpack/maven-simple
/jitpack/v/com.open-meteo/open-meteo-api-kotlin

and then set up redirects so that a request to /jitpack/v/github/jitpack/maven-simple redirects to /jitpack/v/com.github.jitpack/maven-simple. I think the existing redirect we have on this probably prevents us from doing that though: https://github.com/badges/shields/blob/master/services/jitpack/jitpack-version-redirector.service.js . Any other ideas on how we could restructure it?

I think the existing redirect we have on this probably prevents us from doing that though: https://github.com/badges/shields/blob/master/services/jitpack/jitpack-version-redirector.service.js . Any other ideas on how we could restructure it?

I can only think of these possible solutions:
Not-at-all safe
Ditch the /jitpack/v/${user}/${repo} redirect to /jitpack/v/github/${user}/${repo} (terrible idea, imho, as it breaks old badges)
Safest
Implement a new /jitpack/v/any/${group}/${artifact} (or /jitpack/v/custom/${group}/${artifact}?) endpoint

Redirect /jitpack/v/${user}/${repo} to /jitpack/v/any/com.github.${user}/${repo}
Redirect /jitpack/v/${vcs}/${user}/${repo} to /jitpack/v/any/com.${vcs}.${user}/${repo}
/jitpack/v/any/${group}/${artifact} gets data from https://jitpack.io/api/builds/${group}/${artifact}/latestOk

Nicest
Use /jitpack/v/${group}/${artifact}. After the artifact a /{repo} block may be present (see points 1. and 4.)

Does ${group} match github|bitbucket|gitlab|gitee? If so it's a "new-ish" request: redirect to /jitpack/v/com.${group}.${artifact}/${repo} (group is a vcs, artifact is a user name)
Does ${group} start with com.${vcs} (with regex /^com.(github|bitbucket|gitlab|gitee)/.test(group))? If so skip to 5.
Reverse the ${group} to get a ${domain} (like .split('.').reverse().join('.'); com.domain.sub becomes sub.domain.com)
Does git.${domain} DNS redirect to a github repo (no idea how to check this like dig txt)? If not, try as last resort the old /jitpack/v/${user}/${repo} (hence redirect to /jitpack/v/com.github.${group}/${artifact}
Perform the query to https://jitpack.io/api/builds/${group}/${artifact}/latestOk

Please note that points 3. and 4. might not be required, as it's unlikely that a github user has a domain starting with a TLD (it may even be disallowed, as github.com/com.google and similars lead to a blank page; no information about that in the username policies :no_mouth:).

Its all fun games until someone turns up and says "my github username is com.bitbucket.steve"
I think I'm inclined to go with some variation of the 'safe' option. Another variation of that we could do is switch from /jitpack/v to /jitpack/version. It breaks with convention but gives us a 'clean start'. That might be the least worst option.

Its all fun games until someone turns up and says "my github username is com.bitbucket.steve"

I was thinking the same, so I decided to just test it, and the signup page throws the following error:

Username may only contain alphanumeric characters or single hyphens, and cannot begin or end with a hyphen.

We can safely assume that usernames with dots are not allowed to be registered. With that said, I had found some old issues that talked about usernames with dots: probably GitHub disallowed them somewhere in the past, but I didn't find any reference of when it happened, but most importantly if GitHub forced users to change username or simply disabled new ones from signing up with them.

I think I'm inclined to go with some variation of the 'safe' option. Another variation of that we could do is switch from /jitpack/v to /jitpack/version. It breaks with convention but gives us a 'clean start'. That might be the least worst option.

Yep, and it would also mean less risky redirects (no infinite redirect loops or similar bugs)

I have never worked with Angular, so I would prefer if someone else could test this code (I coded a lot with JavaScript, so I know the language itself, but I have never used/setup Angular).
The jitpack-version-redirector.service would become:
export default [
  redirector({
    category: 'version',
    route: {
      base: 'jitpack/v',
      pattern: ':groupId/:artifactId',
    },
    transformPath: ({ groupId, artifactId }) =>
      `/jitpack/version/com.github.${groupId}/${artifactId}`, // this change is recommended (-1 redirect)
    dateAdded: new Date('2022-08-21'),
  }),
  redirector({
    category: 'version',
    route: {
      base: 'jitpack/v',
      pattern: ':vcs(github|bitbucket|gitlab|gitee)/:user/:repo',
    },
    transformPath: ({ vcs, user, repo }) =>
      `/jitpack/version/com.${vcs}.${user}/${repo}`,
    dateAdded: new Date('2022-08-21'),
  }),
]

And the service would become:
// ...
  static route = {
    base: 'jitpack/version',
    pattern: ':groupId/:artifactId'
  }

  static examples = [
    {
      title: 'JitPack',
      namedParams: {
        groupId: 'github',
        artifactId: 'maven-simple',
      },
      staticPreview: renderVersionBadge({ version: 'v1.1' }),
      keywords: ['java', 'maven'],
    },
  ]

  static defaultBadgeData = { label: 'jitpack' }

  async fetch({ groupId, artifactId }) {
    const url = `https://jitpack.io/api/builds/${groupId}/${artifactId}/latestOk`

    return this._requestJson({
      schema,
      url,
      errorMessages: { 401: 'project not found or private' },
    })
  }

  async handle({ groupId, artifactId }) {
    const { version } = await this.fetch({ groupId, artifactId })
    return renderVersionBadge({ version })
  }
}

That looks roughly right to me - certainly a solid basis for a PR. It will be easier to test and review if you submit a PR.
The one thing I'd pick out is in your example, I think groupId: 'github', should be groupId: 'com.github',
Btw, where have you got angular from? We don't use angular in shields, so fortunately that won't be a barrier :)

That looks roughly right to me - certainly a solid basis for a PR. It will be easier to test and review if you submit a PR.

I'll fork the project and make a pull request :+1:

The one thing I'd pick out is in your example, I think groupId: 'github', should be groupId: 'com.github',

Yep, I forgot that I needed to change from the old vcs value to the full groupId: 'com.github.jitpack'. Thank you!

Btw, where have you got angular from? We don't use angular in shields, so fortunately that won't be a barrier :)

Oops, VS code automatically showed the Angular icon, because the file names matches *.service.js lol

authors: DadiBit calebcartwright chris48s


text:
Fixed usage anonymous class before 7.0 php

subject

Thank you @KonstantinKuklin.

authors: KonstantinKuklin mougrim

repo: badoo/soft-mocks


text:
No interpreter directive found for (zsh)

For scripts with the shebang line of #!/bin/zsh — performing a download yields the following message:

No interpreter directive found for:

Can you download the latest master version and give it a try?

This should be resolved, going to go ahead and close this.

authors: badstreff cmaliwat


text:
Issue during exporting Customers data

Bug report
Title
When customer create an account using a special character in the first name and last name then during the exporting customer's data an error occurs kindly fix this issue
https://www.loom.com/share/9f03fa0b14114d55b018534c4d6c7c39

Special characters like-->

GDgE>naitD
$/$5$\'%`$6'
$8$>$$\Z%\0$9$0 \'$8$$8%\n$%$$'
$(%\0$2$>`$-
$6%\n$0%\0$5$>$8%\n$$$5'
$*%\n$0$5%\0$#
$%$.$>`$0

repo: bagisto/bagisto


text:
Login as customer icon should be change in the admin panel.

Is your feature request related to a problem? Please describe.
The log-in as customer icon should be changed in the admin panel.
Describe the solution you'd like
There should be a signout icon instead of a lock icon if the admin is trying to log in as admin.
Describe alternatives you've considered
Please find the below screenshot

Additional context
No response

please assign me this issue

@jitendra-webkul
Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.

authors: Sanjaybhattwebkul shivamtiwariwebkul


text:
Fixed calender icon issue customer profile at velocity theme

#5785
Fixed calender icon is not properly visible in arabic

working now


text:
Final Issues for latest version of personal portfolio

Final To-Do List for dev and prod branch
Info from previous issues
#7 Chrome dev tools feedback
#8 Fixes for dev branch
Additional Info for rxt-ecrive and react-boiler repos
React Template/Boilerplate Repo
React Business Landing Page
ToDo List for optimization and finishing touches

[ ] Add Tests
[x] Fix Asset sizing and optimize
[x] Add unique project descriptions and remove test components
[ ] Create a Full Doc How-To from all the info learned updating repo
[x] Deploy to Azure and Netlify to compare
[ ] Lazy Load components
[ ] Refactor a dev branch for react-ded-boiler
[ ] Refactor a prod branch w/ new UI for rxt-ecrive

Form Addition + Options

[x] Microsoft 365 and Google review Forms (add in addition to below options
[x] Formik/Formspree
[ ] Nodemailer with Express Backend

Remaining and New to-do
6 tasks left from pre Tech job

finish refactor for evrivé and react boiler

Update GCP ref, and footer

[ ] refactor

[ ] Clean up and simplify

Project was successfully deployed with 90+ lighthouse scoring and planned functionality. Stopped working on it due to new job and learning other skills. Will begin adjustments and make changes to the other 2 react projects and 2 nextJS projects.

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
safronizator, @sumonst21, @ianpetrarca, @francofabio, @sailor95, @ryan1000, @zaendev, @morphizm, @rowanu, @daniilkk, @CacaoRick, @vijayrajasekaran, @mdLn1, @paulwongx, @xwartz, @paulcpro, @AxelBrinck, @imgntn, @CTOlet, @psurma, @gritchou, @joeyenouy007, @primexdev, @Ebi-Tendon, @sarmel, @billyriantono, @teodoraispas, @vitorroliveiraa, @hmborges, @btwotwo, @0x5e5e, @SalmonDaze, @akshayraje, @dogagenc, @youfoundron, @vilyia, @muoi, @Meeken1998, @simonpallister, @alechp, @WilsonWu315, @rmit-s3660109-lorenc-pekaj, @power-jun, @apocoder, @bhram, @HappyOcean, @slinker-hiwa, @davilee103, @gromatluidgi, @ali-master


text:
[WIP] Add Rocm support

Add ROCm support for warp-ctc.

这里hiprand_LIBRARY_DIRS的定义，确认在hip.cmake里面能找到

确认是能找到的
(base) windstamp@rocm35:/opt/rocm/hiprand/lib/cmake/hiprand ls
hiprand-config.cmake  hiprand-config-version.cmake  hiprand-targets.cmake  hiprand-targets-release.cmake
(base) windstamp@rocm35:/opt/rocm/hiprand/lib/cmake/hiprand grep hiprand_LIBRARY_DIRS -r *
hiprand-config.cmake:#   hiprand_LIBRARY_DIRS     - Link directory for hipRAND library.
hiprand-config.cmake:set_and_check(hiprand_LIBRARY_DIRS "${PACKAGE_PREFIX_DIR}/hiprand/lib" )

多余不需要的库删掉
done, thanks.

这里不需要改成hip_add_executable，正常.cpp或者.cc结尾的文件用add_executable就可以了
done, thanks.

这里把CUstream命名为GPUstream会更加合适一点，因为typedef struct CUstream_st* CUstream;是CUDA本身的一个定义，以防万一和这个头文件被其他文件include之前或者之后引用了cuda的头文件，会导致这个定义失效，最好定义成GPUstream就可以避免这个问题。
done, thanks.

repo: baidu-research/warp-ctc


text:
gcc versions later than 4.9 are not supported

Cannot compile paddle on Ubuntu 16.04.1 LTS becauseof gcc-5.4

Sorry, cuda-7.5 donot support gcc-5 ,not paddle

repo: baidu/Paddle


text:
Sqlite3

This pr is inspired by SGX_SQLITE
#110
Support create db and load from dbfile.
create db base test:
dbfile not existed
[+] Home dir is /root
[-] Open token file /root/enclave.token error! Will create one.
[+] Init Enclave Successful 2!
start_db
This is a in-Enclave
sqlite opening test:
----------------teacher base operation ------------------
----------------------------------
table not existed!
crete teacher table
----------------------------------
----------------------------------
insert bench data success
----------------------------------
----------------------------------
delete data FROM teacher
delete success
----------------------------------
----------------------------------
SELECT sum(clientid) FROM teacher
clientid sum is 90000
----------------------------------
----------------------------------
SELECT * FROM teacher
Ok: [Teacher { id: 0, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 0, clientid: 10000, indexid: 0 }, Teacher { id: 1, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 1, clientid: 10000, indexid: 1 }, Teacher { id: 2, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 2, clientid: 10000, indexid: 2 }, Teacher { id: 3, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 3, clientid: 10000, indexid: 3 }, Teacher { id: 4, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 4, clientid: 10000, indexid: 4 }, Teacher { id: 6, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 6, clientid: 10000, indexid: 6 }, Teacher { id: 7, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 7, clientid: 10000, indexid: 7 }, Teacher { id: 8, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 8, clientid: 10000, indexid: 8 }, Teacher { id: 9, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 9, clientid: 10000, indexid: 9 }]
----------------student base operation ------------------
----------------------------------
table not existed!
crete student table
----------------------------------
----------------------------------
insert bench data success
----------------------------------
----------------------------------
delete data FROM student
delete success
----------------------------------
----------------------------------
SELECT sum(clientid) FROM student
clientid sum is 90000
----------------------------------
----------------------------------
SELECT * FROM student
Ok: [Student { id: 0, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 0, clientid: 10000, indexid: 0 }, Student { id: 1, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 1, clientid: 10000, indexid: 1 }, Student { id: 2, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 2, clientid: 10000, indexid: 2 }, Student { id: 3, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 3, clientid: 10000, indexid: 3 }, Student { id: 5, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 5, clientid: 10000, indexid: 5 }, Student { id: 6, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 6, clientid: 10000, indexid: 6 }, Student { id: 7, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 7, clientid: 10000, indexid: 7 }, Student { id: 8, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 8, clientid: 10000, indexid: 8 }, Student { id: 9, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 9, clientid: 10000, indexid: 9 }]
----------------database operations end------------------
[+] say_something success...

load db from dbfile
dbfile existed
[+] Home dir is /root
[-] Open token file /root/enclave.token error! Will create one.
[+] Init Enclave Successful 2!
start_db
This is a in-Enclave
sqlite opening test:
----------------------------------
SELECT sum(clientid) FROM teacher
clientid sum is 90000
----------------------------------
----------------------------------
SELECT * FROM teacher
Ok: [Teacher { id: 0, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 0, clientid: 10000, indexid: 0 }, Teacher { id: 1, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 1, clientid: 10000, indexid: 1 }, Teacher { id: 2, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 2, clientid: 10000, indexid: 2 }, Teacher { id: 3, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 3, clientid: 10000, indexid: 3 }, Teacher { id: 4, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 4, clientid: 10000, indexid: 4 }, Teacher { id: 6, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 6, clientid: 10000, indexid: 6 }, Teacher { id: 7, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 7, clientid: 10000, indexid: 7 }, Teacher { id: 8, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 8, clientid: 10000, indexid: 8 }, Teacher { id: 9, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 9, clientid: 10000, indexid: 9 }]
----------------student base operation ------------------
----------------------------------
SELECT sum(clientid) FROM student
clientid sum is 90000
----------------------------------
----------------------------------
SELECT * FROM student
Ok: [Student { id: 0, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 0, clientid: 10000, indexid: 0 }, Student { id: 1, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 1, clientid: 10000, indexid: 1 }, Student { id: 2, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 2, clientid: 10000, indexid: 2 }, Student { id: 3, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 3, clientid: 10000, indexid: 3 }, Student { id: 5, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 5, clientid: 10000, indexid: 5 }, Student { id: 6, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 6, clientid: 10000, indexid: 6 }, Student { id: 7, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 7, clientid: 10000, indexid: 7 }, Student { id: 8, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 8, clientid: 10000, indexid: 8 }, Student { id: 9, street: "streett", city: "cityt", sendstatus: "sendstatust", datatype: "datatypet", ops: "insert", age: 9, clientid: 10000, indexid: 9 }]
----------------database operations end------------------

thanks! do you think it’s ready to be merged, or prefer continue working on this pr?

The insert transaction is unstable in testcase.
I would like to work on it. :smile:

We have found many problems when we try to insert lots of  data into sqlite3.
It is very unstable.I think this is caused by sqlite3_stmt and maybe take a long time to solve it.
So I plan to close this pr and replace it with EnclaveDB (merklebtree )
@dingelish
Thanks!

authors: bradyjoestar dingelish

repo: baidu/rust-sgx-sdk


text:
[patch] Corrected the way to actually pass the files to evaluate during eslinting

It specifies the exact folders, and the globbing works on more files, raising the issues to a lot more, unfortunately (or fortunatelly??)
Also, as specific folders are set, node_modules are not evaluated, and it does fail like it fails in Travis, trying to lint node_modules

@mikermcneil
Also note, if you run ...
node ./node_modules/eslint/bin/eslint accessible bin errors lib --fix

... it wil automatically fix what can be fixed according to your .eslintrc config

finally, that eslint version seems to NOT be compatible with 0.10 and 0.12, it uses const

@luislobo we added this line to the scripts in some of the adapters to handle the case of earlier versions of node:
"pretest": "nodever=`node -e \"console.log('\\`node -v\\`'[1]);\"` && if [ $nodever != \"0\" ]; then npm run lint; fi",

This was so we can still have Travis fail if the lint fails so that any PR's will fail for invalid syntax.
https://github.com/balderdashy/sails-postgresql/blob/bdf2b7d7e05b8a85cc0f79918d8add0c88a28298/package.json#L31-L34

@particlebanana yeah, that works, the only drawback is that you don't have linting on older versions but anyway, in my opinion, those versions should not be supported anyway (although code might anyway be compatible with 0.1x)

authors: luislobo particlebanana

repo: balderdashy/sails


text:
Can't open a frame caputured.

Description
I can't open a frame caputrued, there was such a message in the Diagnostic log:
"Error Can't verify the digital signature of the D3D12Core.dll embedded in capture, it won't be loaded. If the capture came from a trusted source and you want to load unsigned dll's, set D3D12.Debug.IgnoreSignatureCheck to true."
But I don't know how to set D3D12.Debug.IgnoreSignatureCheck to true.  can someone help me?

Steps to reproduce

Environment

RenderDoc version: 1.19
Operating System: Windows10
Graphics API: d3d12

Hi there, your issue has been closed due to not correctly following the issue template. Please read the documentation about filing issues and open a new issue which does follow the issue template. Do not reply to this issue with more information or with a correctly formatted issue, as that will only lead to confusion.
I try to address all github issues and fix bugs quickly, but badly formatted issues or poorly described bug reports especially are a significant drain on project resources. Taking a few minutes to file a good issue makes a huge difference and will get it addressed faster - everybody wins!
In github when you first create a new issue the form is pre-populated with a template which you should read over and follow. As linked above there is documentation going into more detail about what makes a good issue.

Tools->Settings->Core->ConfigerEditor->D3D12->Debug->IgnoreSignatureCheck

authors: 10yac baldurk defcool

repo: baldurk/renderdoc


text:
D3D8 Driver

Would you accept a PR for a D3D8 driver?
I know there's a D3D9 driver stub, but it doesn't do capture, so it would be a bit weird to have a D3D8 driver that's more complete than the D3D9 one. And obviously there's a maintenance cost.
My motivation is that I want to do a graphics study for C&C Generals, in the same style as Adrian
Courrèges's awesome frame breakdowns of popular games like GTA V. But C&C Generals is a D3D8 title, which very few frame debuggers support (really just apitrace, but apitrace's UI doesn't give me pretty partially-rendered screenshots that I can put on my blog).
I've already matched the D3D9 driver, so my D3D8 driver can render the overlay as below. I'll probably carry on with the capture code regardless of your answer, but it would be extra motivation if there was the thought that this code could be merged and / or useful to others.

I can't answer the question but would like to chip in just to say how it looks from my side.
I started the D3D9 driver but then, unfortunately, lost a large chunk of my free time to other activities. Since the D3D9 and D3D8 interfaces are exact matches in many cases, it would be great to make progress on either implementation, because this would mean much easier progress for the other. If I will have any more free time in the near future I will certainly return to the D3D9 driver which I very much regret abandoning.
As for your concerns, I think it's not a problem to have a D3D8 driver, even if the D3D9 one is not functional yet and you shouldn't worry about this. Especially since all this development would probably happen in a branch.
Obviously, all this is just my opinion and Baldur has the last word on all matters renderdoc related :)

@moradin thanks for the reply, and your work on the D3D9 driver - it made the initial D3D8 work pretty straightforward.
Let's see what Baldur says.

This is certainly unexpected :smile:.
At this point I don't get many requests about D3D9 support, although there are still a few people shipping programs on D3D9. D3D8 is only of historical interest I imagine. However I don't mind merging the API support into the codebase in principle.
My main concerns are maintenance like you mention - I don't really want to have a driver that is just left to rot and bugs aren't fixed, but equally I don't have the familiarity or realistically the time/priorities to fix anything. There's also a question of controlling expectations - when new features are added or changes are made, D3D8 is definitely going to get the short end of the stick. Many features will probably be impossible to implement without maybe doing some kind of dual-API path where you share textures with a more capable API like D3D11 and do the work there. In general though, I don't want to give people the expectation that D3D8 is fully supported without being able to back it up.
As long as it is simply merged into the code without being 'public-facing' until it's ready, I think it should be fine.
I guess although D3D8 and D3D9 are similar, all of the versioned COM interfaces make code sharing kind of difficult? If the APIs are close enough and it's feasible then it would be nice to share some code if possible, but if that's more trouble than it's worth doing the gymnastics to merge things then it's not important.
For a procedural thing I'd strongly recommend PR'ing with what you have now already, and then PR'ing at a regular basis after that. Realistically I can't review and merge a whole back-end at once, so if there's a PR that's too big then that might be something I'd reject. Instead if you do it in bite-sized chunks then it's easier to review and fix any issues sooner rather than later. As long as it compiles there's no harm in merging it any time, it doesn't have to work until we decide to publicise it and make it an official backend.

when new features are added or changes are made, D3D8 is definitely going to get the short end of the stick

That makes complete sense - I wouldn't be surprised or upset if, at some point in the future, there are enough changes or new features that you decide to remove D3D8 support. But if there's at least some version of RenderDoc that supports D3D8, that ought to be enough for people like me who just want to better understand an old game.

As long as it is simply merged into the code without being 'public-facing' until it's ready, I think it should be fine.

Great!

If the APIs are close enough and it's feasible then it would be nice to share some code if possible

In my opinion, it's not worth trying to share code, at least at this stage, because of the versioned COM interfaces you mentioned. Perhaps after the capture code is implemented I can revisit that opinion.

For a procedural thing I'd strongly recommend PR'ing with what you have now already

Will do.

As for code sharing, most of the code would compile if a define would be added for each API object. Now I'm not saying that I like such code but something like this would work:
#if DX9
#define D3DTexture IDirect3DTexture9
#elif DX8
#define D3DTexture IDirect3DTexture8
#else
#error
#endif

The same idea could be implemented with typedefs or templates.
There are certainly objects that are different or functions that exist only in one API but the similarity is really huge.

Closing this for now as the initial PR is merged, feel free to open new issues if there are specific things that should be discussed.

Where to vote for D3D9 support? My game defaults to DX9 suddenly and I can not force it to work with DX11, so I can't use RenderDoc for it anymore.

There is no voting. D3D9 support is unlikely to be implemented unless someone else contributes it as it's not high priority for me.

My game defaults to DX9 suddenly and I can not force it to work with DX11

I'm not sure if it's what you mean, but capturing commercial or copyrighted programs that are not your own is not supported or condoned. I provide no support for that. If it's your own project and you have a DX11 backend then it's up to you to use DX11, it's not something I can help with.

authors: Skybladev2 baldurk moradin tgjones


text:
Initial action commit

Co-authored-by: esulej esulej@users.noreply.github.com

@Bucknalla is this PR still relevant?

@ab77 nope, closing

repo: balena-io/deploy-to-balena-action


text:
workflows: Update build and deploy

This adds support for ESR releases build and deploy.
Change-type: patch
Signed-off-by: Alex Gonzalez alexg@balena.io

Superseded by https://github.com/balena-os/balena-connectcore/pull/198

repo: balena-os/balena-connectcore


text:
Add Twilio subscription via websub

Purpose
Add Twilio subscription via websub
Goals
Resolves https://github.com/wso2-enterprise/choreo/issues/14190
Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Test environment
2201.2.1

Since this involves an API change we have to update related samples with this PR. And need to do a major version bump with it for the trigger.

Closing as per https://github.com/wso2-enterprise/choreo/issues/14190#issuecomment-2329032315

authors: Chuhaa Drifftr NipunaRanasinghe

repo: ballerina-platform/asyncapi-triggers


text:
Remove carbon message dependacies

Description:

$Title as HTTP-Transport provides the necessary dependency.
Refactor test cases to use org.wso2.transport.http.netty.message.HttpCarbonMessage
Close Dependabot version resolved PRs

Fixed in https://github.com/ballerina-platform/ballerina-lang/pull/14313, hence closing the issue

repo: ballerina-platform/ballerina-lang


text:
Automate publishing grafana dashboard to grafana store

Description:
At the moment we do it manually.

We don't release this along with Ballerina releases anymore. Hence i am closing this issue


text:
Dynamic Endpoint support

Requirement

Creating endpoints on global level irrespective of the services deployed in ballerina server.
Use the existing endpoint created by name of the endpoint from a Service.

Can we do this requirement from existing ballerina version ?, Or is this coming in later version ?

Hi, This can be done in the latest pack.


text:
if .. is ..{} statements not working for records with same properties.

Description:
I have defined two records with same properties. But I can not check for their types with if .. is.. statement. After that I used different property names as a boilerplate. But I think the record name should also be added to the token.
Steps to reproduce:
import ballerina/io;

public type Github record {
    int bar;
    string foo;
};

public type Twitter record {
    int bar;
    string foo;
};

public function main() {
    Twitter twitter = {bar: 20, foo: "asa"};

    Twitter | Github twitterOrGithub = twitter;

    if twitterOrGithub is Github {
        io:println("Github");
    } else {
        io:println("Twitter");
    }
}

https://play.ballerina.io/?gist=06500ef4c555034b08a1316ecd172482&file=play.bal
Error:-
Compiling source
        app.bal
error: .::app.bal:18:8: unnecessary condition: expression will always evaluate to 'true'

Affected Versions:
jBallerina 1.2.0
Language specification 2020R1
Ballerina tool 0.8.5

Ballerina is a structurally typed language hence this is the expected behavior.
Ballerina does not consider name of the type as part of the type.
In Ballerina swanlake track there is a new feature that allow us to distinguish type by name. This is called distinct types and only supported for object and error.

Thank you @rdhananjaya for the response. I will close this. Because I can handle it by using different property names and this is not a bug.

authors: rdhananjaya whizsid


text:
Strings are not enclosed by " in error messages

Description:

$title

In compilation errors:

public function main() {
    "1" var1 = 1;
    1 var2 = "1";
}

gives
ERROR [main.bal:(4:16,4:17)] incompatible types: expected '1', found 'int'
ERROR [main.bal:(5:14,5:17)] incompatible types: expected '1', found 'string'
error: compilation contains errors

In runtime errors

public function main() {
    [1|"1"|"2", 2|"2"|"3"] tupleVal = [1, 2];
    ["1", "2"] ans = checkpanic tupleVal.cloneWithType();
}

gives
Running executable

error: {ballerina/lang.value}ConversionError {"message":"'[(1|1|2),(2|2|3)]' value cannot be converted to '[1,2]':
                tuple element '[0]' should be of type '1', found '1'
                tuple element '[1]' should be of type '2', found '2'"}
        at ballerina.lang.value.0:cloneWithType(value.bal:86)

Steps to reproduce:
Depicted above.
Affected Versions:
slbeta6
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/34534.


text:
Error not returned from select clause

Description:
public function main() returns error? {
    do {
        var res = from string v in []
            select check someFunction(v);
        io:println(res);
    }
}

function someFunction(string input) returns string|error {
    return error("dummy error");
}

Steps to reproduce:
Affected Versions:
SL GA
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Dulpicate of https://github.com/ballerina-platform/ballerina-lang/issues/34894. Hense closing.


text:
Compile time error when indexing into a tuple with rest

import ballerina/io;
public type IntArr [int...];
public function main() {
    IntArr x = [1, 2];
    foreach var i in 0 ..< x.length() {
        io:println(x[i]);
    }
}

org.wso2.ballerinalang.compiler.semantics.model.types.BTypeReferenceType cannot be cast to class org.wso2.ballerinalang.compiler.semantics.model.types.BTupleType (org.wso2.ballerinalang.compiler.semantics.model.types.BTypeReferenceType and org.wso2.ballerinalang.compiler.semantics.model.types.BTupleType are in unnamed module of loader 'app')
java.lang.ClassCastException: class org.wso2.ballerinalang.compiler.semantics.model.types.BTypeReferenceType cannot be cast to class org.wso2.ballerinalang.compiler.semantics.model.types.BTupleType (org.wso2.ballerinalang.compiler.semantics.model.types.BTypeReferenceType and org.wso2.ballerinalang.compiler.semantics.model.types.BTupleType are in unnamed module of loader 'app')
        at org.wso2.ballerinalang.compiler.semantics.analyzer.TypeChecker.checkTupleIndexBasedAccess(TypeChecker.java:8130)
        at org.wso2.ballerinalang.compiler.semantics.analyzer.TypeChecker.checkListIndexBasedAccess(TypeChecker.java:8097)
        at org.wso2.ballerinalang.compiler.semantics.analyzer.TypeChecker.checkIndexAccessExpr(TypeChecker.java:7891)
        at org.wso2.ballerinalang.compiler.semantics.analyzer.TypeChecker.visit(TypeChecker.java:2901)

I will work on this.

This happen when accessing a member on a type reference type for a tuple type using a variable expression.
public type IntArr [int...];
public function main() {
    int i = 0;
    IntArr x = [1, 2];
    io:println(x[0]); //No error, Expected Behaviour
    io:println(x[i]); // Compile time error
}

authors: SasinduDilshara manuranga


text:
[Bug]: Ballerina bindgen not support for custom maven repositories.

Description
When bindgen  ava code which contains dependencies from custom maven repository. it's not retrieve from there due to hardcoded repositories.
https://github.com/ballerina-platform/ballerina-lang/blob/master/misc/maven-resolver/src/main/java/org/ballerinalang/maven/MavenResolver.java#L80-L87
Steps to Reproduce
No response
Affected Version(s)
2201.3.0
OS, DB, other environment details and versions
UBUNTU
Related area
-> Other Area
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

This is fixed in following PR
https://github.com/ballerina-platform/ballerina-lang/pull/39659


text:
When using a function the package is imported but when removing the particular function the  import statement doesn't get removed.

 Issue by Sewmi
Saturday Feb 18, 2017 at 10:19 GMT
Originally opened as https://github.com/ballerina-lang/composer/issues/868

Environment
OS: Mac OS (version 10.12.3)
Browser: Safari (varsion 10.0.3 )
Steps

Access Ballerina editor (graphical view)
Add a service
Use a function in another package. (e.g. 'copy of' in 'ballerina.lang.arrays' package)
Check source view. (import statement should be added)
Then remove added functions. (no other functions from the imported package should be there)
Import statement added as a result of the added function is still there.

Issue
Import statement doesn't get removed when the functions of the particular package are no longer using in the design.

This issue is no longer valid, since the automatic import functionality etc. are no longer there.


text:
Endpoint metadata is not cleared properly when a service is stopped

Description:
In testerina we allow users to start/stop endpoints. If users try to start a service, stop the service and try to start the same service again following error is thrown. The reason for this is, the service registry is not being cleared. The network interface stops but the registry is not cleaned.
Listening for transport dt_socket at address: 5005
Failed to execute the test function [testAirlineReservationService] of test suite package [airline_reservation]. Cause: error: error, message: error: error, message: service registration failed: two services have the same basePath : /airline
	at ballerina.http:register(<native>)

	at ballerina.test:startServices(<native>)

Steps to reproduce:
Execute a similar testerina program as below.
import ballerina/test;
import ballerina/http;

// Function to test Airline reservation service
@test:Config
function testAirlineReservationService() {
    _ = test:startServices("airline_reservation");
    test:stopServices("airline_reservation");
    _ = test:startServices("airline_reservation");
    test:stopServices("airline_reservation");
}

Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

This issue cannot be reproduced in ballerina 0.975.1-SNAPSHOT, hence closing this issue.


text:
Move type-init logic to separate functions

Purpose
$subject
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #16172 into jballerina will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             jballerina   #16172   +/-   ##
=============================================
  Coverage          9.73%    9.73%
  Complexity         2272     2272
=============================================
  Files              1468     1468
  Lines             71541    71541
  Branches           8552     8552
=============================================
  Hits               6968     6968
  Misses            63963    63963
  Partials            610      610

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0b77cfb...03da681. Read the comment docs.

authors: SupunS codecov-io


text:
[WIP] Query Action implementation & related refactoring

Purpose

Initial PR for the Query Do action implementation. This also contains the refactoring changes of query desuagr.

Fixes #20726
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #20975 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #20975   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1398     1398
  Branches      214      214
=======================================
  Hits          204      204
  Misses       1178     1178
  Partials       16       16

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 471438c...66334d2. Read the comment docs.

authors: codecov-io mohanvive


text:
Fix is type check for readonly fields

Purpose
$title. Fixes #24495 - Runtime is checks should change for readonly fields
This PR also
Fixes #24858 - Stack overflow error with checkIsType for objects with fields of the same type
Fixes #24752 - Object sub-typing checks produce incorrect results
Fixes #24739 - Issue in object sub-typing checks with finite-typed fields
Fixes #25199 - org.ballerinalang.jvm.types.BType's equals() method only looks at the module name and not the org-name/version
Approach
When the is check is used with records or objects, we pass the value also, to do the is like check for readonly fields since such fields cannot change.
Samples
import ballerina/io;

const HUNDRED = 100;

type Foo record {
    HUNDRED i;
};

type Bar record {
    readonly string|int i;
};

public function main() {
    Bar b1 = {i: 123};
    io:println(<any> b1 is Foo); // prints `false`

    Bar b2 = {i: 100};
    io:println(<any> b2 is Foo); // prints `true` now, since the `i` field of `b2` is and will continue to be `100`
}

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@Kishanthan, addressed the suggestions. Thank you!


text:
Incorporate suggestions in PR  #27464 and #27410

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes https://github.com/ballerina-platform/ballerina-lang/issues/27799
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@rdhananjaya, shall we resync this with master? Nothing should break AFAICT, but just to be on the safe side.

authors: MaryamZi rdhananjaya


text:
Fix type narrowing issue in match-statement

Purpose
Fixes #31587

We can add this to the patch branch instead, right?

Created a PR https://github.com/ballerina-platform/ballerina-lang/pull/36591

We can add this to the patch branch instead, right?

Created a PR #36591

We can close this PR since the changes will be merged to master via the patch branch sync once it is merged.

Changes are covered in https://github.com/ballerina-platform/ballerina-lang/pull/36591

authors: KavinduZoysa MaryamZi


text:
Concurrent calls warning when using this module

I've got the following warning when using this module.
HINT [ballerinax/prometheus/0.2.0::metric_reporter.bal:(63:13,63:13)] concurrent calls will not be made to this method since the method is not an 'isolated' method

This seems to be a blocker for performance.

This issue occurs since the methods used in prometheus module (methods of ballerina/observe modules) are not isolated.
We need to make them isolated.

authors: NipunaMadhushan sameerajayasoma


text:
Update staging URL

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

Closing this since this was branched off the wrong branch

repo: ballerinax/docker


text:
Add callback parameter when keycloak is initialized

Hi thanks for the vue 3 integration of the keycloak-js adapter.
I registered the adapter as mentioned in the documentation and it works fine.
However I observed, that my application is already loaded/visible when the adapter performs it's sso-check (redirection to the keycloak instance, check and come back to the application). This results in "Application is visible", "Redirect", "Application is visible again"  i.e. reloading the whole page. Would it be possible to add callback to the plugin to determine when the keycloak adapter is initialized, so that I can only load the the remaining parts of the application after that?
In terms of usage my idea would look like:
  const app = createApp(App)
  app.use(vueKeycloak, {
      initOptions: {...},
      config: {...},
      onReady: function()  {
        app.[...].mount("#app");
      },
      onError: function(error)  {...}
    })

Alternatively a isInitialized export would be good.

I implemented the isInitialized variant and I am pleased with it. Now I can display a loading screen as long keycloak is not initialized. See merge request #3

I just realized that isPending does exactly the same and is implemented 🤦 So the issue and the pull request can be closed.
Maybe it would be good to change the documentation of that variable to If true the keycloak initialization and the authentication request are still pending.?

@lukasjelonek how did you implement the loader with is pending? Do you mount the app once keycloak has been initialized? Do you check this in your router layer?
Thanks for the help in advance.

@habrigo I check if keycloak is isPending and based on that my app either displays a loading-panel or the application.
  <div id="app">
    <template v-if="isLoading">
      <!-- loading information/panel -->
    </template>
    <template v-else>
      <router-view />
    </template>
  </div>

setup() {
    const { keycloak, isPending } = useKeycloak();
    const isLoading = computed(() => keycloak != null && isPending.value);

    return {
      isLoading,
    };
}

Hallo @lukasjelonek  can you please share ur main.ts or the part in which u initialized and configured Keycloak instance.
Or can u please provide here a small working Sandbox link or anything?
Because i am not able to get it working properly with vue3 Typescript.
Thanks in advance.

Dear @DnD2k21,
I am not sure what is missing for you. I configured keycloak pretty much the same as described in the Readme file of vue-keycloak. Maybe you can provide your non-working example and I can see if there is something obviously wrong?

authors: DnD2k21 habrigo lukasjelonek

repo: baloise/vue-keycloak


text:
v0.3.12 not available on extensions store

https://marketplace.visualstudio.com/items?itemName=banacorn.agda-mode only has v0.3.11, are there any plans to publish the latest version?

Sorry for the wait and thanks for asking. The latest verison 0.3.12 has now been published.

Thank you!

authors: L-TChen nicolo-ribaudo

repo: banacorn/agda-mode-vscode


text:
🛑 MXN Scroll On-ramps is down

In 0d1fb53, MXN Scroll On-ramps ($QUOTE_ENDPOINT) was down:

HTTP code: 500
Response time: 568 ms

Resolved: MXN Scroll On-ramps is back up in 1eed8ff after 10 minutes.

repo: bandohq/upptime-monitor


text:
webhook: for run-as-user use whatever is definied in config or the de…

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
fixes https://github.com/banzaicloud/bank-vaults/issues/1761

License
Apache 2.0

What's in this PR?
Removed the code section for the vault-agent use that overwrites the runAsUser value in the securityContext always with 0. Instead now the value from the config (if annotation run-as-user specified this will be used or the default which is 0) will be used
Checklist

[X] Code meets the Developer Guide

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Sorry, I mistakenly closed this issue via Github automation, but now it is up and running!

authors: CLAassistant bonifaido jochen-schreiber

repo: banzaicloud/bank-vaults