[test] Integration test coverage

Motivation
Improve integration test coverage https://github.com/apache/pulsar/tree/master/tests/integration
The integration test will run on a real cluster, not a mock environment like the unit test does.
Tools

[ ] Integration test for Admin CII
[ ] Integration test for client tool https://github.com/apache/pulsar/pull/17616
[ ] Integration test for perf tool

Security

[ ] Integration test for TLS https://github.com/apache/pulsar/pull/17141

Websocket service

[x] With broker https://github.com/apache/pulsar/pull/17843
[x] With proxy https://github.com/apache/pulsar/pull/17843
[x] Separated service https://github.com/apache/pulsar/pull/17843

Plugins

[x] Integration test for Protocol handlers #17350 @andrasbeni
[x] Integration test for Broker interceptors #17515
[x] Integration test for Broker message filters #17396
[x] Integration test for Additional servlet (broker/proxy) #17450

@nodece Is handling the integration test of security

@codelipenghui , can you please what tests you would like to see for the admin CLI? As I can see, runAdminCommandOnAnyBroker does use the admin cli and is used extensively by integrations tests. And there are some more usages through the constant ADMIN_SCRIPT. So it's not a dedicated test, but I think it already has some coverage.

@andrasbeni Most of the admin CLI integration tests are under tests/integration/cli and yes we already have some coverage for this part. I think we should also consider the improve the coverage for this part to avoid someone changing the output format or introducing new incompatible options. But it's not a very strong opinion, we need to maintain so many test codes in the future. WDYT?

@codelipenghui , I believe integration tests are too expensive to do a full validation of output and command line parameters. Having taken a quick look at admin command implementations and PulsarAdminToolTest, it looks to me that admin commands are designed to be easily unit tested: the PulsarAdmin can be mocked by setting a Supplier and CaptureStdOut makes their output verifiable.  So, in my opinion, we would be much better off writing unit tests for all these.

@andrasbeni Sound good to me.


Cannot submit form in category

Broke it

I'm not sure where I was having this issue - seems to be resolved?


test failures in client orgs in HH_OppContactRoles_TEST.cls

I have seen frequent test failures from this class in client orgs, often w/ some governor going over limit.  Today it's the following:

This is an issue b/c when we move to NPSP3 for a client, we always review NPSP3 tests to make sure there's not an incompatibility w/ their custom code/WF.  But when we get errs like this it's very hard to tell if something is really wrong, or if it's just a fragile test.
I can't debug this because there's a good dozen tests in here and the debug log craps out before it gets to the ones that are failing.
The one suggestion I have is to use start/stop test in all your tests so that you get the extra overhead on governors.

**lurch: attach W-007372

Tracking W-007372

We were unable to reproduce the problem at the Spring 16 NPSP Sprint.  Since the test class was updated in December, it may be that the updates fixed this problem.  Otherwise, we need more instruction to reproduce this problem in a developer org so we can investigate more.

Closing until we have a reproducible case.


fix: don't interpret simple parameter as deepObject

Fixes #1565

@RobbeSneyders Here is my take on a fix. It works fine in our application:
$ http :8080/api "filter[surname]_bogus"=="greinacher"
HTTP/1.1 400 Bad Request
Content-Length: 235
Content-Type: application/vnd.api+json; charset=utf-8
Date: Tue, 02 Aug 2022 14:56:31 GMT

{
    "errors": [
        {
            "code": "xrn:err:core:invalidRequestParameter",
            "detail": "Extra query parameter(s) filter[surname]_bogus not in spec",
            "id": "a6a0b17e-e52f-37e4-a7d9-6c2e926ed4f8",
            "status": "400",
            "title": "Invalid Request Parameter"
        }
    ]
}

Thanks @fgreinacher!
I've submitted a PR to fix the failing tests due to a new Flask version: https://github.com/spec-first/connexion/pull/1572. I'd like to merge that one first. Feel free to review it.

Thanks @fgreinacher! I've submitted a PR to fix the failing tests due to a new Flask version: #1572. I'd like to merge that one first. Feel free to review it.

Thanks @RobbeSneyders, I was wondering how this failure could be related to my change :)
The other MR looks good to me!

@RobbeSneyders I'm planning the last days before my summer vacation. Do you think we could get this in early next week so I can verify it with our services? 🙇

Sorry for the delay, I was on vacation myself :)
Should be good to go now. I'll prep a release.


Integration test command should run all integration tests

We agreed on this with Andreas here https://kubernetes.slack.com/archives/CG3HTFCMV/p1603361976115700?thread_ts=1603360951.111500&cid=CG3HTFCMV
Context: There was a PR that has splitted KUTTL tests out of integration-test command. The reason was to be easily able to run just a single test. But as a result, command that's named integration-test now runs only a subset of integration tests and I think that's very confusing. The solution is to keep kuttl test separate for whoever needs it but have all integration tests again under one makefile command.

I prefer to think of "integration" as Go integration tests... and kuttl as mainly e2e tests. this blurs that.

@kensipe yeah I see how that can be confusing but these tests are really integration tests (and yes, we have kuttl e2e tests as well)
I would actually say that for kuttl integration and e2e are on the same level, it just depends whether you use startControlPlane flag or not (if yes, you're doing integration not e2e in the sense it's commonly defined)


Has anyone achieved using yolov8 with this package?

I have succesfully implemented yolov5 with this package, however i can't make it work with yolov8.
I don't have problems running the inference, but the results I obtain do not make sense, I always get way to many detections that forms a diagonal in the image. And what it's crazier is that if I use a black image as input, I get detections.
Im going crazy with this implementation. There is the code, I can't see what im doing wrong.
    final labels = (await rootBundle.loadString('assets/ai/labels.txt')).split('\n');
    final interpreter = await Interpreter.fromAsset('assets/ai/yolov8n.tflite');
    final imageData = await rootBundle.load('assets/ai/image.jpg');
    final capturedImage = img.decodeImage(imageData.buffer.asUint8List());

    const inputSize = 640;

    final resizedImage = img.copyResize(
      capturedImage!,
      width: inputSize,
      height: inputSize,
      // maintainAspect: true,
      // backgroundColor: img.ColorRgb8(0, 0, 0),
    );

    final imageMatrix = List.generate(
      inputSize,
      (y) => List.generate(
        inputSize,
        (x) {
          final pixel = resizedImage.getPixel(x, y);
          return [pixel.rNormalized, pixel.gNormalized, pixel.bNormalized];
        },
      ),
    );

    final output = List<num>.filled(1 * 84 * 8400, 0).reshape([1, 84, 8400]);

    interpreter.run([imageMatrix], output);

    final results = output.flatten();
    const offset = 4;
    for (var i = 0; i < results.length; i += (offset + labels.length)) {
      var maxClassConfidence = -1.0;
      var maxClassIndex = -1;
      for (var j = i + offset; j < i + offset + labels.length; j++) {
        if (results[j] > maxClassConfidence) {
          maxClassConfidence = results[j];
          maxClassIndex = j - (i + offset);
        }
      }

      final score = maxClassConfidence;
      if (score < 0.4) continue;

      final label = labels[maxClassIndex];

      var x = results[i] * inputSize;
      var y = results[i + 1] * inputSize;
      var w = results[i + 2] * inputSize;
      var h = results[i + 3] * inputSize;

      final resizedRect =
          Rect.fromCenter(center: Offset(x, y), width: w, height: h);
    }

Nvm, yolov5 output matrix was, [1, 25500, labels + 5], and yolov8 is [1, labels + 4, 8400].
Detections are in last position and not second.

Oh I saw, I did it.
Could you tell me how I can find the description about the meaning of output shape, such as
yolov5 output matrix was, [1, 25500, labels + 5], and yolov8 is [1, labels + 4, 8400] ?
Thank you very much !

Oh I saw, I did it.
Could you tell me how I can find the description about the meaning of output shape, such as yolov5 output matrix was, [1, 25500, labels + 5], and yolov8 is [1, labels + 4, 8400] ?
Thank you very much !

@loveoverflowdev I did not find it, I inferred it, however this thread can help you to understand it better https://github.com/ultralytics/ultralytics/issues/7231, the creator himself replied with the explanation.
Hope it helps, and sorry with the late reply.


Don't count '/' in division as a completions trigger

@mjbvz Currently vscode doesn't seem to trigger at all on '/', but maybe it should as in <div> foo </ completing with div.

Thanks. We have a logic that only treats / as a trigger character if it looks like we are in an import path. I'll remove that


Improve documentation for advanced features of BuildStream

See original issue on GitLab
In GitLab by [Gitlab user @LaurenceUrhegyi] on Jun 21, 2018, 17:50
Background
Now that we have improved the documentation for newcomers to the project, we should focus on improving the documentation for the more advanced features that BuildStream has.
Task description
We already have the basics of creating and building a project, and use of bst shell.
Important topics still to cover are:

workspaces
junction elements
split rules
filter elements - also see further details at https://gitlab.com/BuildStream/buildstream/issues/278

Each item should be a stand-alone tutorial.
We should also include more examples, but I think that should be covered separately to this issue.
Acceptance Criteria
There should probably be a corresponding MR to match each of the sub-headings above, ie:

[x] workspaces - see !519
[x] junction elements - see !550
[ ] split rules
[ ] filter elements

In GitLab by [Gitlab user @LaurenceUrhegyi] on Jun 22, 2018, 10:41
marked this issue as related to #434

In GitLab by [Gitlab user @phildawson] on Jun 25, 2018, 17:34
I'm working on documenting "Developing with BuildStream". I have a draft of a tutorial for development using workspaces. This needs a bit more polishing but I'll have an MR for this tomorrow. I'll then move onto a tutorial for setting up an artifact cache.

In GitLab by [Gitlab user @phildawson] on Jun 25, 2018, 17:37
assigned to [Gitlab user @phildawson]

In GitLab by [Gitlab user @phildawson] on Jun 27, 2018, 12:25
mentioned in commit<PHONE_NUMBER>427f7408c540b9870a0da0207a9117

In GitLab by [Gitlab user @phildawson] on Jun 27, 2018, 12:25
mentioned in commit 9544dc42647d6e3ce946fc53ddcd691141933ff9

In GitLab by [Gitlab user @phildawson] on Jun 27, 2018, 12:25
mentioned in commit 4478c57df497d3229441a44d8d02d650b5e4d66b

In GitLab by [Gitlab user @phildawson] on Jun 28, 2018, 09:48
mentioned in commit 6acd71717e47d5206d90d609ebeacb36717978cc

In GitLab by [Gitlab user @phildawson] on Jun 28, 2018, 09:48
mentioned in commit f8220d7fa422a64c0456199df2c4959eb2fb100e

In GitLab by [Gitlab user @phildawson] on Jun 28, 2018, 09:48
mentioned in commit da0c4bf1159192a4e03b938d0192c0269e5022fc

In GitLab by [Gitlab user @phildawson] on Jun 28, 2018, 09:48
mentioned in commit 91974d19a98703eb4d11b8a97b18a75e515330c1

In GitLab by [Gitlab user @phildawson] on Jun 28, 2018, 09:55
mentioned in merge request !519

In GitLab by [Gitlab user @phildawson] on Jun 29, 2018, 14:45
mentioned in commit 32505e72e291a5498cdc1a09acf2428812a32f7e

In GitLab by [Gitlab user @phildawson] on Jun 29, 2018, 14:45
mentioned in commit fbdd24226980f6bd12030e2d89542c47c425d5ca

In GitLab by [Gitlab user @toscalix] on Jul 2, 2018, 16:42
assigned to [Gitlab user @tristanvb]

In GitLab by [Gitlab user @toscalix] on Jul 2, 2018, 16:42
unassigned [Gitlab user @phildawson]

In GitLab by [Gitlab user @phildawson] on Jul 3, 2018, 11:21
marked the task Developing a project as completed

In GitLab by [Gitlab user @phildawson] on Jul 3, 2018, 11:21
marked the task Working with Buildstream in a team as completed

In GitLab by [Gitlab user @tristanvb] on Jul 3, 2018, 17:24

A suggestion of the way to do this is to split up and re-name the Running Commands section into several self-contained tutorials, like so:

Note that the above is a bit misguided, the section in the tutorial Running Commands is about running commands in the sandbox environment, not a section specifically about running the BuildStream CLI at all.
Looking at how things are evolving, I'm gravitating towards opening up a second tutorial focusing on more advanced topics like development of software using BuildStream.

In GitLab by [Gitlab user @phildawson] on Jul 4, 2018, 15:39
mentioned in commit df636434d04b7f635b644fde7a9a0889fa5533bd

In GitLab by [Gitlab user @phildawson] on Jul 4, 2018, 15:39
mentioned in commit facca01d07e3aa11c77d4ec4cd504e4cccf77fa5

In GitLab by [Gitlab user @phildawson] on Jul 4, 2018, 15:39
mentioned in commit 61e104b363e581527797e9449aa35df8e25b4a20

In GitLab by [Gitlab user @phildawson] on Jul 17, 2018, 17:18
mentioned in commit d6dd57f2bb5b3bc2b11d13801fe0baf14da7451e

In GitLab by [Gitlab user @phildawson] on Jul 17, 2018, 17:18
mentioned in commit bf98921bc162836b20c2c36af995e1a5b632a66f

In GitLab by [Gitlab user @phildawson] on Jul 17, 2018, 17:18
mentioned in commit a64f671a459db357891706b2a15d9749ee253ea7

In GitLab by [Gitlab user @phildawson] on Jul 17, 2018, 17:18
mentioned in commit 60e91e789dc1bc564c68552535d992f680a91ea2

In GitLab by [Gitlab user @phildawson] on Jul 17, 2018, 17:18
mentioned in commit 64685be6170598457672ccdcd845a66af4d8cd9b

In GitLab by [Gitlab user @phildawson] on Jul 17, 2018, 17:18
mentioned in commit eddab8f781c38ae9b9866cd5e7f8c65d4f685718

In GitLab by [Gitlab user @phildawson] on Jul 18, 2018, 09:39
mentioned in commit 0e6c36b683cce973643d03652911e2611c0fb085

In GitLab by [Gitlab user @phildawson] on Jul 18, 2018, 09:39
mentioned in commit eb9a194082dc90d999ed528e613968a11658fa59

In GitLab by [Gitlab user @phildawson] on Jul 18, 2018, 09:39
mentioned in commit 66da252ffeb022c740ecf2202a93739be6d264f8

In GitLab by [Gitlab user @phildawson] on Jul 18, 2018, 17:42
mentioned in merge request !550

In GitLab by [Gitlab user @phildawson] on Jul 18, 2018, 17:48
changed the description

In GitLab by [Gitlab user @phildawson] on Jul 19, 2018, 11:20
mentioned in commit 1828ae2a7e5f8a429aa5ee06b1e76f4db63d11db

In GitLab by [Gitlab user @phildawson] on Jul 19, 2018, 11:20
mentioned in commit 53f5361873c513112a7256b0e099335614ddcb7d

In GitLab by [Gitlab user @phildawson] on Jul 19, 2018, 11:31
mentioned in commit 5158c9972c5ae2a4bbacc66e00806f48df114d59

In GitLab by [Gitlab user @phildawson] on Jul 19, 2018, 11:31
mentioned in commit 8c5f081239b1ca15a438d42f1345f81116f42f27

In GitLab by [Gitlab user @phildawson] on Jul 19, 2018, 11:31
mentioned in commit 38abd5ba528c5e5975052e11a4e8ff96a8c45681

In GitLab by [Gitlab user @phildawson] on Jul 20, 2018, 09:44
mentioned in commit c77e589eee814f25479dd0406f96e1b9ff99a41b

In GitLab by [Gitlab user @phildawson] on Jul 20, 2018, 09:44
mentioned in commit 5e862ff53021e5f86508aa76cb37cf51a77199bf

In GitLab by [Gitlab user @phildawson] on Jul 20, 2018, 09:44
mentioned in commit 2798bbcfc0905ba8bfc69dd5376432d00acb99f2

In GitLab by [Gitlab user @phildawson] on Jul 23, 2018, 11:26
mentioned in commit f8fdee9b1dafa6d94c47064a48e2cb1522aa1eb0

In GitLab by [Gitlab user @phildawson] on Jul 23, 2018, 11:26
mentioned in commit 97d3e23948de5e27f99a1d69396bd4732ae2058e

In GitLab by [Gitlab user @phildawson] on Jul 23, 2018, 11:26
mentioned in commit 1c56b8e923d88d6e931c646b45807384cb3cb2f1

In GitLab by [Gitlab user @phildawson] on Jul 23, 2018, 12:01
mentioned in commit b6e484fabfd2a5adff49229b74376e04527ebdcb

In GitLab by [Gitlab user @phildawson] on Jul 23, 2018, 16:17
mentioned in commit 5f0c3479ce5b42ab8b5a22afcea5d578084ac093

In GitLab by [Gitlab user @phildawson] on Jul 23, 2018, 17:01
mentioned in commit 4d2c0e04dd1a352e3c0f1df3967a8c4e14569c62

In GitLab by [Gitlab user @jennis] on Jul 25, 2018, 16:20
mentioned in commit b3f7b29278d687ed31ff42c7e3698ad4e6bf20e1

In GitLab by [Gitlab user @jennis] on Jul 25, 2018, 16:20
mentioned in commit 8267b870e3c73d49ee23f41971242db41e344090

In GitLab by [Gitlab user @jennis] on Jul 25, 2018, 16:20
mentioned in commit c6222c415255fd1c661919c96266ddb653718317

In GitLab by [Gitlab user @jennis] on Jul 25, 2018, 16:20
mentioned in commit da1a22916ddf19894be111a6dda0a3f8e8c78266

In GitLab by [Gitlab user @jennis] on Jul 25, 2018, 16:47
mentioned in commit 77bd14abc5ec32299273741e7ef8c5393ef3e7c1

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 11:53
mentioned in commit 7e5520651bbba37f834e243fa19479e936d56f2c

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 11:53
mentioned in commit 8746cae493db215efd482908d6295e3eb31ccc91

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 11:53
mentioned in commit cf112ddebdfb9f77c3f7645baba09c86add90bf1

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 11:53
mentioned in commit 56f35570982235d34b613d5c7d7ac6d229abed59

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 12:39
mentioned in commit 57c7b458d182e68d728f3da7fda6dfea625ecf43

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 12:39
mentioned in commit 76eb65c4a7389c1a54e5ecfef458fc558a97be9c

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 12:39
mentioned in commit 08d56ea348262c4e9b977b36cebdee81b4efe23e

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 16:23
mentioned in commit d83712b73aab69ca0c4a4bcd930be49644d21a44

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 16:23
mentioned in commit 13dab494e26188496d8d47ace9ea8792c02d3330

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 16:23
mentioned in commit 968d98b8219aa49b9d1d2af043c5edc0bec024a0

In GitLab by [Gitlab user @phildawson] on Jul 26, 2018, 16:23
mentioned in commit ddea84afdea85ed35d8e5e29696cf530d8eaaa28

In GitLab by [Gitlab user @jennis] on Jul 27, 2018, 09:32
mentioned in commit 1f63dc8ffa8233335562f741ba929a42b17ff8bd

In GitLab by [Gitlab user @jennis] on Jul 27, 2018, 09:32
mentioned in commit 43120391ba14ec604102c84ee2776c2f593ec21f

In GitLab by [Gitlab user @jennis] on Jul 27, 2018, 09:32
mentioned in commit 3fe4895131b649a12fc5d6000080003f5e2c56c0

In GitLab by [Gitlab user @jennis] on Jul 27, 2018, 09:32
mentioned in commit 8961042cc42e81bd4509d35372cb9e7ba6b68f1e

In GitLab by [Gitlab user @phildawson] on Jul 27, 2018, 12:01
mentioned in commit 7f0f90e6d81fd22e16e8889b9923be0039bc65f6

In GitLab by [Gitlab user @phildawson] on Jul 27, 2018, 12:01
mentioned in commit 114c76f9e79ee7a029eeb6ab8967f6ac938a238b

In GitLab by [Gitlab user @phildawson] on Jul 27, 2018, 12:01
mentioned in commit 05546fbd6aec030be0bdbdbaaa058b017861452d

In GitLab by [Gitlab user @phildawson] on Jul 27, 2018, 12:01
mentioned in commit b78941b54e6b1df823a7517b4e487080b583438c

In GitLab by [Gitlab user @phildawson] on Jul 27, 2018, 13:49
mentioned in commit 711ecb4a2b3087b133f394e991006d7faf62007d

In GitLab by [Gitlab user @phildawson] on Jul 27, 2018, 13:49
mentioned in commit dd8ca14a26018770e89ae4907ee3dc9627affe4a

In GitLab by [Gitlab user @phildawson] on Jul 27, 2018, 13:49
mentioned in commit 34b95776d7776639965c9820715d5b4785a27ec2

In GitLab by [Gitlab user @phildawson] on Jul 30, 2018, 08:58
mentioned in commit efa24e7e633d9ede4edaff80eef707f089950907

In GitLab by [Gitlab user @phildawson] on Jul 30, 2018, 08:58
mentioned in commit b4f2519091a94d05cdc17f6fc21c856b45e2316a

In GitLab by [Gitlab user @phildawson] on Jul 30, 2018, 08:58
mentioned in commit bf175bf78f5a1c3392d979182440858cd43054fc

In GitLab by [Gitlab user @phildawson] on Jul 30, 2018, 08:58
mentioned in commit 8568d27248336555073a92b05958d097de14170c

In GitLab by [Gitlab user @phildawson] on Jul 30, 2018, 11:46
mentioned in commit c33e85fc019aca1c3c979656060ee90966aff300

In GitLab by [Gitlab user @phildawson] on Jul 30, 2018, 11:46
mentioned in commit 20a5ec2c6e2e91ce76cdc5513a50eaae486d750d

In GitLab by [Gitlab user @phildawson] on Jul 30, 2018, 11:46
mentioned in commit 0afffeab284c2fadbf97252ed7cf40e69a7d2b8b

In GitLab by [Gitlab user @phildawson] on Aug 1, 2018, 09:04
mentioned in commit b883a053eb5552ad501a135fca6def50755ad5eb

In GitLab by [Gitlab user @phildawson] on Aug 1, 2018, 09:04
mentioned in commit 35049f2db3ff7161eeb6f6d5b2cc770ea4ba58ac

In GitLab by [Gitlab user @phildawson] on Aug 1, 2018, 09:04
mentioned in commit ab7c05f04b6db1179d0e92c37d6679bd48b5d2ec

In GitLab by [Gitlab user @phildawson] on Aug 1, 2018, 09:06
mentioned in commit dc60b71303eb9f69d32be7874fd3fefbe841dc30

In GitLab by [Gitlab user @phildawson] on Aug 1, 2018, 09:06
mentioned in commit 6cd3df09f36df55b28b613c8fcee48bae6722244

In GitLab by [Gitlab user @phildawson] on Aug 1, 2018, 09:06
mentioned in commit 8c0522adde2a1dac10d52171cee701068e74631e

In GitLab by [Gitlab user @phildawson] on Aug 1, 2018, 10:04
closed via merge request !519

In GitLab by [Gitlab user @phildawson] on Aug 1, 2018, 10:04
mentioned in commit 480565c2ee6c7684c1d48cd518893ce12fc2f58d

In GitLab by [Gitlab user @toscalix] on Aug 1, 2018, 10:14
reopened

In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 1, 2018, 12:22
unassigned [Gitlab user @tristanvb]

In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 1, 2018, 12:23
marked this issue as related to #278

In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 1, 2018, 12:24
changed the description

In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 1, 2018, 12:24
changed the description

In GitLab by [Gitlab user @jennis] on Aug 1, 2018, 15:48
assigned to [Gitlab user @jennis]

In GitLab by [Gitlab user @jennis] on Oct 2, 2018, 17:51
unassigned [Gitlab user @jennis]


Feature: Add language type to file component

Instead of this:
(lol couldn't get the formatting right)

I'd love to write:
<File name='dbt_project.yml', language='yml'>

data-paths: ["data", "seeds"]

</File>

#wontfix because then it doesn't render nicely in my code editor


Remove masking

Masking is not quite possible yet, so remove and we will add it back when we complete the feature.

Would we use a feature flag for this or just remove?

I'm not sure what to do about some of these yeah. Does it make sense to feature flag? We'd like to add them back, but I also dont want to get stuck with dead code that we're moving bits around when they're not going to be implemented in the short term and we're not actively testing.


password_authentication support for databaseSecretEngineConfig

Hello,
we would like to set password_authentication to "scram-sha256" through databaseSecretEngineConfig ressources but current CR and controller don't support this parameter yet.
How handle it properly ?
We can try to provide a MR in the next days

Please go ahead with the PR.
On Wed, Feb 7, 2024, 5:44 AM Vincent Hurtevent @.***>
wrote:

Hello,
we would like to set password_authentication to "scram-sha256" through
databaseSecretEngineConfig ressources but current CR and controller don't
support this parameter yet.
How handle it properly ?
We can try to provide a MR in the next days
—
Reply to this email directly, view it on GitHub
https://github.com/redhat-cop/vault-config-operator/issues/230, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPERXFPBFSYAUO57VQ232TYSOANPAVCNFSM6AAAAABC53NHSSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZDGMBXGQZDCOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Post-install kubectl example shows full path

Maybe File.basename it.

Actually btw it looks like it has loaded the wrong binary too. I ran that using bundle exec bin/pharos-cluster. Probably linked to #533


Not saving positions

Checklist:

[X] I updated to the latest version available
[X ] I cleared the cache of my browser

Release with the issue: 0.4
Last working release (if known):
Browser and Operating System: Windows 10
Microsoft Edge (66%)
Version 88.0.705.50 (Official build) (64-bit)

Description of problem:
After saving, the locations change.

Javascript errors shown in the web inspector (if applicable):

Additional information:

I was also able to duplicate this in Chrome.

I was also able to duplicate this in Chrome.

yeah seeing this in Edge (Chromium) also

yeah seeing this in Edge (Chromium) also

Seems you have to edit all in one go or lose layout on the next edit

Seems you have to edit all in one go or lose layout on the next edit

Hey, I think I have a workaround. Basically, after a while, it seems to fix itself.  From there it should just stick for the most part.

Hey, I think I have a workaround. Basically, after a while, it seems to fix itself.  From there it should just stick for the most part.

I'm having the same issue. Using Chrome, it won't save the layout.

I am having the same issue, this is a great tool please fix the Save Layout button, thank you

Same here, not saving positions in my browser using chrome. I fear adding new cards because every time I need to reposition the cards as position is not saved. Cheers

@Norgan: Could not reproduce your fix. When I click save multiple times it actually destroys my layout.


editable installs for pycharm

https://github.com/pypa/setuptools/issues/3557#issuecomment-1226582406

its not an issue with this repo (with pycharm, rather), so closing


Mention that we don't support Advisory Lock Functions

We defined some builtins around pg_advisory locks, but they are no-ops, and some functions are not even defined. This commit adds this limitation to unsupported postgres features.
See https://github.com/cockroachdb/cockroach/issues/13546.

Thanks for the review!


Add support for python 3.7 in travis ci

#206
The sudo and dist must be true and xenial explicitely for python3.7 (see https://github.com/travis-ci/travis-ci/issues/9815)

There's one issue with the Sphinx install here:
https://travis-ci.org/astropy/regions/jobs/418661367#L946
That looks unrelated to our package. @sushobhana - unless you know how to fix or work around that issue, or want to engage with pip or Sphinx to fix it upstream, you could just keep the docs build / test on Python 3.6 for now, and then this can go in.
Could you try to change one Mac and / or Windows build to 3.7 as well?

Re: regions 0.2 not being able to install via pip with Python 3.7:
This is a known issue with Cython and Python 3.7.  Basically, the distribution currently on PyPI was built with an older version of Cython (and that version is incompatible with Python 3.7).  If it gets rebuilt with a newer Cython it should work.

As a workaround, you should be able to install directly from the github tarball.

Thanks @bsipocz and @larrybradley . @cdeil - Added support for windows and osx as well.

@sushobhana - Thanks for setting this up, and @mwcraig - thanks for the advice!


Restarting Kernel infintely

Hi,
Just tried new python 3.6 jupyter lab install (latest) and Matlab 2018b kernel install (.egg is 2018a however). In any case, I'm getting infinite restarts of the kernel with any notebook.
I am able to start matlab from python prompt:
from matlab.engine import start_matlab; start_matlab()
<matlab.engine.matlabengine.MatlabEngine object at 0x10b39bc18>
However when looking at output of Jupyter lab, any  notebook with a MATLAB kernel, outputs the following...
[I 16:58:06.979 LabApp] Kernel started: 4c2f8e57-56aa-4776-a345-fb9304f224d3
[I 16:58:21.980 LabApp] KernelRestarter: restarting kernel (1/5), keep random ports
[I 16:58:36.993 LabApp] KernelRestarter: restarting kernel (1/5), keep random ports
... and it just continues and locks any interactivity with any working kernel. Any suggestions on what might be causing the problem?
Thank you!

I don't use jupyterlab myself, so no idea, sorry.

This also happens in Juypter notebook:
[W 19:51:56.927 NotebookApp] Notebook Dropbox/MATLAB/Jupyter/notebooks/190705.ipynb is not trusted
[I 19:51:57.571 NotebookApp] Kernel started: 156c0411-a639-4548-a3f7-a84714d18745
[I 19:52:09.572 NotebookApp] KernelRestarter: restarting kernel (1/5), keep random ports
[I 19:52:21.582 NotebookApp] KernelRestarter: restarting kernel (1/5), keep random ports
[I 19:52:36.590 NotebookApp] KernelRestarter: restarting kernel (1/5), keep random ports
[I 19:52:51.601 NotebookApp] KernelRestarter: restarting kernel (1/5), keep random ports
^C[I 19:52:57.641 NotebookApp] interrupted

Hard to tell, as I cannot repro this locally :( Perhaps mention this on the notebook tracker?

After reinstalling the MATLAB engine, and pip installing imatlab as admin, it appears to be working again without infinite kernel crashing/looping. Unclear why this occurs, but seems to happen every once in a while and needs a reinstall to fix.
Python3.7/MATLAB2019a/Win10x64

Raising this again (now for Mac OSX). Kernel isn't working with fresh conda environment builds, getting:
[I 10:44:00.602 LabApp] Kernel started: b28e09df-0d75-4741-9908-67120e875197
[I 10:44:12.600 LabApp] KernelRestarter: restarting kernel (1/5), keep random ports
[I 10:44:24.608 LabApp] KernelRestarter: restarting kernel (1/5), keep random ports
and continues to restart.
Jupyter Notebook 6.0.1
Jupyter lab 1.0.2
Python 3.6
Matlab 2018b
On MacOSX 10.14.6
Python kernel works without restarting.
Any suggestions on how to debug this?
Thanks.

Okay, I'm pretty sure of the newer commits this year broke the kernel. When I installed an older commit from last year (last commit of 2018), the kernel crash and restart doesn't occur. What I did to install: python -mpip install git+git://github.com/imatlab/imatlab@7c5d095931
The older and less well maintained Calysto kernel also doesn't crash/reboot continuously.

can you bisect (https://git-scm.com/docs/git-bisect) it?

Hi Anntzer,
It's a bit perplexing, now installing from current master branch works. I had been manually reinstalling the matlab kernel (ls /Applications/MATLAB_R2018b.app/extern/engines/python/) uninstalling ('pip uninstall imatlab') and reinstalling ('pip install imatlab' then 'python -mimatlab install') and various deleting of /usr/local/share/jupyter/kernel/imatlab to no avail. Only after I reinstalled Calysto and then the older imatlab branch, is the problem 'fixed' itself. Now the kernel doesn't continuously restart. I can even uninstall and reinstall from the current imatlab branch, so I can't reproduce the restarting kernel problem at the moment. I'll have to probably wait a few weeks/months of use before the restarting comes up again.
While it probably won't fully solve the issue, if you could update the installation so that it supports conda environments (e.g. install kernelspec in /Users/anntzer/anaconda3/envs/share/jupyter/kernels) rather than install in /usr/local/share/jupyter/kernels this may help to isolate kernel issues.
I'm wondering if uninstalling and reinstalling from older kernels updated or downgraded a dependency which was causing the kernel to restart.

Installing is provided by ipykernel (via https://github.com/imatlab/imatlab/blob/master/lib/imatlab/_kernel.py#L48); I don't know how ipykernel plays with conda envs but you may want to investigate that.

FWIW, this happens reasonably often for me when I've updated juptyerlab or one of its dependencies. After setting up a debug environment where I can hook into the imatlab kernel with PyCharm, the problem has been related to parsing the history file. I find that deleting my Matlab history in ~/.matlab/R2019b/history.m and ~/.matlab/R2019b/History.xml often fixes this issue (these are for Linux, swap in your version). I'm not sure what's causing it, but I do often get warnings from Matlab if I open the desktop environment about the history file being corrupted by concurrent access, and I think the XML parser in the kernel chokes on this corrupted history file.

I also get the warning but there's a button "Accept history as is", clicking on it seems to make things work just fine...

Agreed. I don't know if they are connected. I think that Matlab itself may occasionally leave the history file in bad shape, but I cannot explain why the xml parsing routine called by imatlab would crash specifically when updating the jupyter packages via conda. All I'm saying is that sometimes on updates, imatlab crashes on startup and restarts indefinitely, and that in my case, deleting the history has fixed the issue. If I can reproduce the issue with a History file sometime, I will send it along, but it happens rarely enough that once I found this fix I stopped digging.
Thanks!


Answer are comming from outside the document how to configure to receive answers only from the document

Is there any settings i need to follow to pick answers from the documents only rather than localGPT forming more of its sentence.
When i asked what is seasonality which was there in my document, the model started answering irrelevant
This is the answer in the document which i have given,
Seasonality
Our revenue fluctuates quarterly and is generally higher in the second and fourth quarters of our fiscal year. Second quarter revenue is driven by corporate year-end spending trends in our major markets and holiday season spending by consumers, and fourth quarter revenue is driven by the volume of multi-year on-premises contracts executed during the period.
But localGPT is giving a different answer!!!!!!!!!

Question:
what is sesonality?

Answer:

Seasonality is a business term that refers to the tendency of certain business activities to occur at certain times of the year. For example, sales of winter clothing may be higher in the winter months, while sales of swimsuits may be higher in the summer months. Seasonality can be used to identify patterns in business activity and can be used to develop strategies for managing and optimizing business operations.
----------------------------------SOURCE DOCUMENTS---------------------------
> /home/appuser/localGPT-falcon/SOURCE_DOCUMENTS/2022_Annual_Report.pdf:

@vdeeplearn
The problem of large language models providing irrelevant answers to questions is a common issue. However, in your case, I noticed that the question 'What is seasonality?' is not very clear. Please try to provide a clearer question.


update stack_trace dep (and others)

Description
Updates the stack_trace dep to the latest so that the Dart->Engine->Flutter rolls can succeed.
Also updates other deps since there is no way to not do that, although it seems minimal.
Tests
None
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

Ah crap of course it auto-formatted update_packages.dart 😭 . I will push a new commit to revert that...


Style/MutableConstant should be aware of # shareable_constant_value (Ruby 3.0)

The following should not generate an offense:
# shareable_constant_value: literal (or experiemental_everything)

MY_CONSTANT = %w[anything here is fine even non-literals]

Here's a link to some documentation on the feature, https://docs.ruby-lang.org/en/3.0.0/doc/syntax/comments_rdoc.html#label-shareable_constant_value+Directive.
I hadn't heard of this being added before so I found it to be an interesting feature. It seems like the intent is to be used with Ractors

Here's a link to some documentation on the feature, https://docs.ruby-lang.org/en/3.0.0/doc/syntax/comments_rdoc.html#label-shareable_constant_value+Directive.
I hadn't heard of this being added before so I found it to be an interesting feature. It seems like the intent is to be used with Ractors

It seems like the intent is to be used with Ractors

That's one way to view it. The other way is the general position that constants should be immutable, and clearly when we say that we never mean actual classes. So in effect that is pretty much what "Ractor-shareable" means.

It seems like the intent is to be used with Ractors

That's one way to view it. The other way is the general position that constants should be immutable, and clearly when we say that we never mean actual classes. So in effect that is pretty much what "Ractor-shareable" means.

I created https://github.com/rubocop-hq/rubocop/pull/9410 to add shareable_constant_value methods to the MagicComment class.

I created https://github.com/rubocop-hq/rubocop/pull/9410 to add shareable_constant_value methods to the MagicComment class.


Add TFTPD option

Hello,
In these past few days, I've been working on the potential integration of a TFTP service within the addon, allowing users to enable or disable it through the configuration panel (disabled by default).
As I own Cisco devices, I realized the need to configure an external server for configuration uploads. However, the idea of having everything "at hand" seemed like the sensible approach.
After understanding the mistake in my last pull request, I conducted a significant number of tests (^^'). It appears that everything is functioning correctly. However, due to the nature of the UDP protocol, I'm encountering difficulties in reaching the container.
I'm wondering if it might be a good idea to integrate this service directly into the addon. In such a case, before submitting another potentially non-functional pull request, I would appreciate it if you could guide me on the requirements to set in the development environment to allow UDP traffic.
Thank you in advance,
DD

Can you elaborate on the relationship between TFTPD with Asterisk? I don't understand what one thing has to do with another.

Didn't asterisk also had a build-in tftp server for this?

@TECH7Fox on a quick look up I could not find anything like that. But maybe I didn't search correctly.
If there is no built-in TFTP server in Asterisk, then I would say your request is out of scope for this add-on.
If you want a TFTP server, you can create a standalone add-on for TFTPD. That's my recommendation.
But feel free to elaborate otherwise.

Also can't find it. Must have been freepbx then.
@Danny89530 if your just gonna use it once, I used tftpd64. Very easy to use and debug.

Can you elaborate on the relationship between TFTPD with Asterisk? I don't understand what one thing has to do with another.

The relationship between TFTPD and Asterisk isn't directly intertwined, except for a specific use case involving various devices, such as Cisco phones. These devices require a TFTP server to facilitate functions like downloading license files, firmware updates, or even simple configuration files (for instance, in my case, I have Enterprise devices converted to 3PCC). One example specific to Cisco is the need for an XML configuration file.
In essence, the connection lies in the shared requirement of certain devices for a TFTP server to enable these essential functions.

Also can't find it. Must have been freepbx then.
@Danny89530 if your just gonna use it once, I used tftpd64. Very easy to use and debug.

My intention was merely to put forward an idea; if you believe it's unnecessary, I can step back :).
Nonetheless, I would appreciate it if you could guide me on enabling the UDP protocol in the development environment.
I don't have much familiarity with VSCode and don't know how to adjust this setting..

Anyway, I have the changes published in a fork available here:
https://github.com/Danny89530/asterisk-hass-addons
Feel free to take a look if you'd like.

Honestly I don't use the development environment... I would recommend you try these changes outside of the development environment.
You can for example, build and push the image to ghcr.io or docker hub and then adjust the config.yaml:image key to point to your new image for testing. Or you can comment the image line in the config.yaml so that Home Assistant will build the dockerfile (I am imagining that you already have cloned this repo to /addons/).

The relationship between TFTPD and Asterisk isn't directly intertwined, except for a specific use case involving various devices, such as Cisco phones. These devices require a TFTP server to facilitate functions like downloading license files, firmware updates, or even simple configuration files (for instance, in my case, I have Enterprise devices converted to 3PCC). One example specific to Cisco is the need for an XML configuration file.

Ok, thanks for explaining.
My suggestion for you is to build your own TFTPD add-on and share it with the community. I'm sure it will be useful for others.
Add-ons usually have a single purpose, and I believe TFTPD would make a great add-on.
https://developers.home-assistant.io/docs/add-ons/tutorial/

Anyway, I have the changes published in a fork available here: https://github.com/Danny89530/asterisk-hass-addons Feel free to take a look if you'd like.

I checked it, things looks good. But if you make your own add-on you will be able to simplify a lot of things.


World Information

VRCX has not been showing me my latest feed for who joins and leaves and it doesn't show what world I'm in.

as natsumi said above
Quick menu > Settings > Debug > Logging
as set like this.

Alright, that fixed it. Thank you!


Python3 support

This change is

Superseded by https://github.com/heremaps/oss-review-toolkit/pull/1146.


Add gauges to track per-request failures

https://github.com/astriaorg/astria/pull/771 reworked metrics in sequencer-relayer, but mostly built on top of existing metrics. As mentioned in that PR, it would be useful to also track per-request failures in the form of gauges for fetching blocks from sequencer and for submitting blobs to celestia (as opposed to global counters, as is done right now).

This issue is stale because it has been open 45 days with no activity. Remove stale label or this issue
be closed in 7 days.

This issue was closed because it was stale


Add awesome-analyzers

Other Lists/awesome-analyzers - https://github.com/Cybermaxs/awesome-analyzers
A curated list of .NET Compiler Platform ("Roslyn") diagnostic analyzers and code fixes.

awesome-analyzers OR awesome-linq ?

@devkhan
Oops, copied the wrong line into template :facepalm:
Fixed.

Thx!


[FEATURE] journey high priority selection?

#summer24release

turns out this is stored in journey.metaData.highThroughputSending.email (boolean) and therefore already available (at least on 7.0.0)


Feature/migrate symbols

Changes proposed in this Pull Request:

Take the symbols and move them somewhere else

You are ahead of us :P
There is a PXBLUE-2275 to spit out the symbols, but it looks like you are advancing further. I just dragged that story to the current sprint and assigned to you


Require file paths to be short enough to not cause failures on windows

What does this PR do?
Add step in unit tests to check for filename length
Motivation
Avoid situations when we can't build the windows agent anymore
Additional Notes
Last time it happened there was a cache issue, we should check that the cache is not updated if this ci step is failing.

This task is invoked on gitlab, you can check the pipeline corresponding to this PR if you want


Replied Message Is not properly formatted

Describe the bug
In reply to message , along with the message URL also come with it . This makes the chat unclear
To Reproduce

Go to 'Any Room or Group'
Reply to any message
URL also come with message

Expected behavior
URL shouldn't come with replied message
Screenshots

Devices and Versions
Your Rocket.Chat.Android version: (e.g. 2.1.0)
Your Rocket.Chat Server version: (e.g. 0.63.1-develop)

Mobile device model and OS version: Nokia 6.1 (Android Pie)

I am working on this issue

@theLimitBreaker, I guess this is same as #1899. If so, please close this one and continue over there.


Re-enable CMP test for AIX, but remove tests which are not consistent across all platforms

I've removed some tests which simulate a write to a directory by using a path ending in '/' as this is not compatible with fopen() on all platforms. On AIX the trailing '/' is removed and the path opened as a file.

[X] tests are added or updated

Well that failed pretty well :)

@paulidale - any ideas what this means?

@paulidale - any ideas what this means?

Looks like a bad merge of libcrypto.num, with duplicate numbering

@DDvO are you ok with this..

FYI @t-j-h

This pull request is ready to merge

Merged - thanks @jon-oracle for the contribution..


Move valid and invalid fixtures to separate directories

Currently, valid and invalid bags are in the same directory. Creating valid and invalid directories will help with unit tests.

This may not be necessary after all, as long as fixtures are consistently named.


Add support for GNU Social URL/verification

This one might be a bit trickier than usual since, like email addresses, there could be any number of domains on which a user may have a GNU Social account. Compounding matters is that while most GNU Social instances are federated with each other, some may be standalone.


Fix params for a controlled - UnitaryGate

Summary
Resolves #5750.
Details and comments
While building a controlled UnitaryGate, the control_matrix was given as a parameter in ControlledGate.  But params attribute of a ControlledGate corresponds to parameters of its base_gate (see L199).
Effectively, it changed the matrix of the base UnitaryGate andinverse was building the inverse of this larger control matrix.

Thanks for the fix! Could you add a bugfix releasenote?

Could you elaborate on the release note a bit so someone familiar with the effect would recognize its description? Thanks!

@georgios-ts are you still pursuing this? 🙂

@Cryoris @georgios-ts Thanks, it fixes my bug report  #5750.


[2.9.1] AKS: Autogenerated nodepool name generated after deleting all nodepools and adding a new one does not comply with the naming convention

Setup

Rancher version: v2.9-7bc90dd10e937ca1b7c03e217b884a863dcc8eb5-head
Rancher UI Extensions: release-2.9 7296914
Browser type & version: Firefox

Describe the bug

When all the nodepools of a cluster are deleted and a new one is added, the name used for it is agentPool which does not comply with the naming rule convention 'Node pool names must be 1-12 characters long, consist of only lowercase letters and numbers, and start with  a letter'.
To Reproduce

Edit an existing cluster or create a new one.
Remove all the existing nodepools and add a new one.
Result
The new nodepool is called 'agentPool'.
Expected Result

The new nodepool name must be 'agentpool'.
Screenshots

Screencast from 08-14-2024 03:25:03 PM.webm
Additional context

@mantis-toboggan-md This feels borderline for a 2.9.1 release blocker (code freeze is tomorrow)?

/backport v2.9.next1

Unit tests seem sufficient. also did a quick manual check, all looks good in:

v2.9-63d8298029ce22942459eaaf0dbe084963c234c5-head
release-2.9 37abd4d


Providing access to the translator so that custom rule objects can be…

… used and translated

I have added some tests and also refactored the code to use return ValidatorFactory::$translator->trans($key); rather than having a trans() method on the ValidatorFactory as you requested.


Add "identity" scales

"Identity" scale is a scale that takes aesthetics values directly and does not change them
For example:
color(listOf(Color.RED, Color.GREEN, Color.BLUE)) {
   scale = identity()
}

I think this behavior is default

Do you mean that this scale should be used by default when a required type is detected?

Yes
And what is the motivation to add identity at all?

Example above - sometimes user uses aesthetics values directly in the input data.


chore(deps): replace tipsi with official stripe lib

This PR resolves PHIRE-1018
Description

PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against ef01f568556a928c9fa79443c371f4da4cddb341

Maybe we can also remove this extra call, I'm pretty sure it was there just because of tipsi


support u128

Change-Id: I0971cd274c3d7d563d23d919ece5bb8eec4b6b61

Thanks for your change! Please leave the Cargo.toml unchanged for the time being, I will bump up the version number appropriately.


Update weighting.md

Fix class name, WeightingMap has been removed to be replaced by HintsMap in 0.8

Thanks!
I know this feels like a bit overhead - but as we encourage contributing, would you mind signing our CLA and send it to us (or we send it to you and you sign electronically, therefor please send us your email)

Also we need here an update of the current master.


deployments: Add new example for authelia

This is still WIP:

[ ] There's a startup issue as authelia errors out when the LDAP server is not reachable (we should address that upstream)
[ ] Too much hardcoded configuration and secrets
[ ] Logout does not work yet

Partial-Fix: #5740

Hooking myself in to notification on changes.

That is great! Can’t wait to try it. Thanks

Exposing can connect to each separately without any issues multiple ways to skin this particular expected server providing application and security. Business listings

[ ]  Logout does not really work. Authelia does not support session management yet. It doesn't provide a end_session_uri nor a check_session_iframe via the metadata. It neither support backchannel or frontchannel logout.  (All of these are on the roadmap.

We've merged https://github.com/owncloud/web/pull/10974 in web, which checks if an end_session_uri was provided by the openid-configuration of the IdP. If that's not the case, web just forgets the current access token and redirects the user to a logged out confirmation page with a re-login button. As soon as authelia comes up with a proper logout and announces it via the end_session_uri, our normal logout process is in place already.


[Feature Request] Add intent to view restricted folders

Hello! I've got a programming app which saves its data to /Android/Data, however its builtin editor is rather garbage (and does not have git). I was hoping to use this to edit those files, but it seems this app does not have a way to declare intent for accessing those restricted folders.
The top answer on this StackOverflow question explains how one would declare the intent and access those folders without the "Administrate all files and folders" permission being required. I would love to help further than this (if I could have came here with a PR instead of an issue I'd have been quite happy), but unfortunately I am not very well versed in JS / Java yet.
This will potentially help with issues like #401.

Unable to fix it. Sorry. May be I'll look into it again in future.


Adding a Line README.md

#Add a Line in README.md
This Git is useful to Beginner Programmer

Hello, I can resolve the issue. You can assign me this issue.

@zhackerloopback can you assign me this issue? I would love to resolve this issue.


FocusNode and FocusScopeNode should take debug labels.

Currently printing the focus tree results in something like this:
[00059.830] 10004.10040> FocusScopeNode#5f96b
[00059.830] 10004.10040>  child 1: FocusScopeNode#6de7b
[00059.830] 10004.10040>      focus: FocusNode#96399
[00059.830] 10004.10040>

It would better to have names for each of these.

I am triaging our bug database, and found this from 2017. Is this still relevant? Can we close this now?


Strict Cache-Control HTTP header sent forcibly

It seems that Symphony CMS pages are sent with the following HTTP header:
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0

It's likely that this has several unwanted consequences. One use case I can think of is refreshing pages with user data (in HTML forms). For instance:

With Firefox (any version), go to http://symphony-cms.com/discuss/new/
Enter some data in the form.
Reload the page. Your input disappears.

Normal behavior in Firefox is to keep the user input for simple page refreshes (only “hard refresh”, with Ctrl/Command + R, does away with user input). But when a page declares Cache-Control: no-store, Firefox will keep nothing. This is true as well when coming back to a page with the browser's Back button.
I've tried with other browsers (including Opera, Safari and Chrome) and they all seem to discard the user input for simple page reloads, and to keep it when going back to a previous page, ignoring Cache-Control for this. I didn’t test with Internet Explorer.
There might be other use cases that make the very strict Cache-Control value a problem. Also, it might be better to leave Cache-Control settings to the website developers (through server config or a hypothetic Symphony extension).

Had another look into this tonight. Symphony->initialiseCookie is necessary at this stage.
It is used by Symphony for:

determining whether to announce the FrontendDevKitResolve delegate
whether to append the Events XML as a comment to the page source
determine if an event should fail because it is admin-only
whether the GenericExceptionHandler is enabled or not
determine if a user can access the backend
determine if a user can see alerts in the backend
show users the /symphony/login page if they try to access the backend and they aren't logged in
allow's login from ?auth-token.

Long story short, we have a lot of things at the moment that depend on $this->Cookie being available. We also have a lot of things that need this check to happen first, and not 'lazy loaded'.
This issue is almost closed IMO. We can look at adjusting the session_cache_limiter value, but we will need to test in unusual scenarios as described, SSL, proxies and older versions of IE.
I for one don't have easy access to these scenarios, so this issue is not of high priority to me. That said, Firefox 10 will no longer show the warning described by @fvsch as a popup window, instead it will a dedicated page, which won't be an amazing user experience IMO.

Given the dependency Symphony has Cookie class, this is not something that will be addressed in the near future.
If someone wants to investigate further what is involved in decoupling Symphony from this class, you are more than welcome to!


Memory usage causing problems for Angular 4+

Some issues in webpack causes Angular AOT builds to require extreme amounts of memory.
https://github.com/angular/angular-cli/issues/5618
Is there any way for you guys to co-operate with the Angular team to solve this serious problem?

I guess google can solve this problem on it's own...


When using as reporter for gunt-contrib-jshint it breaks grunt watch

I have a problem using this package as reporter for gunt-contrib-jshint, when I save a js file that has a jshint error in it jshint-stylish causes the whole grunt process to crash so that I manually need to restart it in the terminal. gunt-contrib-jshint without jshint-stylish does not crash the process.

Never mind, I think this problem was with grunt-contrib-jshint when I tried again.


feat: redesign landing page

Description
Implement new designs: https://www.figma.com/file/58fRuJvFJsNOvbaHOyVb59

The changes look great, @hugocaillard. Thank you. I will pull these changes to my branch and update the top links in the Getting started section and the language in the product-specific sections.

Thanks @LakshmiLavanyaKasturi
Let me know if you have any question regarding the content editing 👍


Work around razor bug in layout

Fixes https://github.com/aspnet/AspNetCore/issues/14064

We want this fix for 3.1. Shouldn't this need to target a 3.1 specific branch?

Also, I may be confused by the working here, but I assume this is the proper fix, and not simply a work around, isn't it?

For 3.1 - it should be cherry-picked.

Based on https://github.com/aspnet/AspNetCore/issues/14064#issuecomment-532420102 it sounds like this is indeed a work around. @NTaylorMullen what is the bug being referred here?

The root bug is https://github.com/aspnet/AspNetCore/issues/10811

@NTaylorMullen I prefer we fix the root cause, rather than making this change. Given it's S let's just do it now. I'm bringing the root-cause issue to 3.1 now. Any objections?

@NTaylorMullen I prefer we fix the root cause, rather than making this change. Given it's S let's just do it now. I'm bringing the root-cause issue to 3.1 now. Any objections?

It's a super edge case so i'm not convinced it's worth the time. I think it makes more sense just to special case this here given it's already done.

Aren't there any other side effects similar to this, caused by the actual root cause?

Aren't there any other side effects similar to this, caused by the actual root cause?

Nope

Let's move forward with this change then, @HaoK!

What's the 3.1 branch to cherry pick to?  I only see 3.0 and 3.0-preview9 I think

https://github.com/aspnet/Scaffolding/tree/release/3.1
Just created one off release/3.0


Disabling SSL Verify Peer

How do you use Sentry?
Self-hosted / on-premises
SDK version
4.2.0
Steps to reproduce
Hello, i want to ask about how to disable ssl_verify_peer?

I tried putting this value on config/sentry.php
'http_ssl_verify_peer' => false,
and then i add this line on Sentry\Laravel\Console\TestCommand to check if its getting the config. It does giving me the correct config
after that i add this on Sentry\Laravel\Console\TestCommand to check if its still showing the same config
hmm, thats odd. Why its suddenly change? I decide to check on Sentry\ClientBuilder if its changing on that class. It does not change here, so why its suddenly change on number 3?

Expected result
http_ssl_verify_peer should be changing when configure on config/sentry.php
Actual result
For Number 2:

For Number 3:

For Number 4:

The php artisan sentry:test uses it's own options and ignores most user-defined options.
See: https://github.com/getsentry/sentry-laravel/blob/2c70e34ee8227559b4710602409f94658f0d989a/src/Sentry/Laravel/Console/TestCommand.php#L92-L97
So this is why the http_ssl_verify_peer is not picked up when running php artisan sentry:test.
That being said, I think we should not ignore any transport options so I've opened #859 to resolve that oversight and that PR should solve the issue you are seeing.

A fix was released in 4.3.0.


Birdsong currently expects all tweets to have media

If they don't, the code currently runs into a NilError

Addressed in #4


Proposal: Add "lock" or "no delete" flag to container

Sometimes you have really important containers, like data only containers, that you don't want accidentally deleted.  docker rm -f $(docker ps -qa) is just too easy to type sometimes and then, "oh !@#!", it's all gone.  (Well not really because you can find your data in /var/lib/docker/vfs).  Anyhow, I propose we add the following:
docker run/create --lock=true ...
docker lock CID
docker unlock CID
If one was to do docker rm CID and CID was locked it wouldn't delete and exit with an error code.  Start/stop/restart should still work.  This flag is the equivalent of EC2's DisableApiTermination flag.  In order to delete a locked container you must first run docker unlock CID.

A PR for this was created some time ago, but voted against by Solomon; https://github.com/docker/docker/pull/7523#issuecomment-59592874 not sure if he's still against it?

Thanks @thaJeztah, you're an encyclopedia of Docker PRs.

@shykes You already said no to this in https://github.com/docker/docker/pull/7523#issuecomment-59592874, but I'd like you to reconsider.  We could use a special label for this, but just as you said you don't like "pin" as it seem very specific, along the some lines, I don't really like magic label names.  Labels should really be used for things above/outside of Docker engine.
I usually look at AWS for a good litmus test as whether a specific piece of API functionality is a good idea.  While AWS isn't perfect, they have a very good track records of making extremely thoughtful changes to their API.  EC2 has this similar concept with DisableApiTermination but I think we can make this a bit more generic with "lock".  With "lock" meta data of any kind (nothing is really all that changeable at the moment) should not be modifiable.  This is really no different than when you do chmod 400 on a file.  As the owner, you could change the file, but you want to put a little bit of a safety net around modifications.

This is definitely a big one for clean up. There is otherwise no way to do clean up operations when you are running multiple things on the same host and too much cruft builds up quickly when continuously deploying things.

+1

+1

This would be really nice for swarm clusters so that users/operators don't accidentally delete the swarm daemons.

:+1: @rgbkrk

:+1:
This is something that's necessary to avoid the dreaded Fat Finger Error.

USER POLL
The best way to get notified when there are changes in this discussion is by clicking the Subscribe button in the top right.
The people listed below have appreciated your meaningfull discussion with a random +1:
@cecitorres
@flaccid
@alanfung

+1

Definitely a way to protect volumes from deletion is a feature that I personally need before using volumes to host production data. Otherwise the risk of accidentally deleting them while removing a container is too high.
TLDR: :+1:

@nivox Deleting a container does not delete its volumes unless you do so explicitly docker rm -v.

@cpuguy83 I'm aware of that, but when you have a production servers with tens of container, some of which have unimportant volumes associated with them while others have volumes hosting production data, using the -v flag on the wrong container is not an unthinkable occurrence.
Furthermore the current  approach doesn't work all that well in case you have a Dockerfile extending a third party image defining a bunch of volumes that, for whatever reason, you don't really care about. In your Dockerfile however you define a volume that will hold production data.
 Right now you have to manually delete volumes (i.e. docker volume rm baseVolume) and then remove the container without the -v flag.
An explicit way of marking a volume as protected (i.e. docker volume pin <volume-id>) would prevent accidental deletion due to distraction (i.e. docker rm -v <wrong-container>) as well as making life easier in cleaning up unimportant volumes.

+1

Where are we now with this proposal?
I'm also in favour of having a lock mechanism, despite this seems controversial. I disagree with the fact that further level of classification (multiple security levels) might be required, since removal is a binary operation (possible/not possible).
Another permission-managed operation could be read vs. write but I'm not sure it makes sense regarding docker, so for now the deletable seems to do the trick.

Yes, I support a more explicit lock mechanism. However, an implicit mechanism was added in #19568 so that --rm will not remove named volumes. A note was added to the docs to explain, but it's still a confusing/surprising and sometimes dastardly behavior to have volumes (even inherited ones) destroyed unexpectedly.
As a result, newcomers to docker must understand more of the counterintuitive intricacies of docker volumes and docker data containers. From what I've seen, this behavior may have been part of the reason for the rise of data containers -- an additional abstraction around volumes -- when volumes with an explicit lock would have been sufficient.
tl;dr: use names for your volumes.

LOL, got a email notification about somebody talking about "locking" containers and was like, "I'm totally going to plus 1 that issues/PR."  Come to find out, it's mine from 2 years ago :(

Following this discussion, and others (w.r.t. docker system prune), perhaps it should be looked at in a wider scope; being able to lock other objects (volumes, networks, secrets, containers, images)

test

:+1:

+1, this is a major problem with using docker system prune to clean up. It removes any volumes not attached to a container, so if for some reason your container happens to have stopped when you prune, your data is gone. I've already lost data to this more than once. A feature to mark volumes as important, so they aren't removed during normal cleanup, would solve this problem.

@ryannoblett docker system prune will no longer automatically prune volumes (you have to specify it with a flag). You can also provide filters to the prune command. You can specify a default set of filters in your CLI config.
Not a 100% perfect solution, but should be ok for most scenarios.

+1 I use Docker for development purposes in my computer and I do a lot of testing (a hell lot of testing) with containers. BUT I keep a few untouched, like databases and libraries. Sometimes I do some cleaning but it's a PITA to cherry pick the ones that should not be touched. This feature would really save some time among dev teams.

+1 I use Docker for development purposes in my computer and I do a lot of testing (a hell lot of testing) with containers. BUT I keep a few untouched, like databases and libraries. Sometimes I do some cleaning but it's a PITA to cherry pick the ones that should not be touched. This feature would really save some time among dev teams.

@pepBR

You can also provide filters to the prune command. You can specify a default set of filters in your CLI config.

@cpuguy83 Couldn't find an example of how to prevent deleting containers using prune filters and using CLI config. Can you point me to the right direction?

docker container prune --filter label!=foo=bar -- This would filter out containers that have a label where foo=bar
You can also do label!=foo (no value) and it would filter out any container that has a foo label regardless of the value.
You can also add this to your ~/.docker/config.json
{
  "pruneFilters": ["label!=foo"]
}

The filter is a little non-intuitive unfortunately, but at least it works.

@cpuguy83 is there a way to test run without removing stuff? If i use label!=container_id=123456abc, would that preserve one container? It's not intuitive at all... and there's no easy to find examples out there.

@pepBR

is there a way to test run without removing stuff?

No, there was a contributor working on a dry-run mode, however I think they had to work on other things.

If i use label!=container_id=123456abc, would that preserve one container?
If you set a container that has a label container_id=123456abc, then yes, it would skip over that container.

It's not intuitive at all
Yeah, it's a bit weird... I think the issue is the --filter nomenclature where it's really more of a "include only" rather than "filter out"

@cpuguy83 I believe I understand about the label stuff now. But apparently you have to set this inside the Dockerfile, right?
What I would like to do is mark containers by ID. The real important ones here don't have a Dockerfile, I use them directly from the hub.
Thanks a lot for your patience.

you can set the labels on docker run; also, the prune commands don't delete running containers, so you don't have to worry about those.
If you still need finer-grained filtering, it's still possible to combine docker ps --filter with docker rm

@thaJeztah Thank you. I'll play a bit inside a VM to better understand how to get what I want. Thank you too @cpuguy83 .

Oh it's 2022 and i need this too!

Solution is 3.6 not great, not terrible.

People mighty be interested to know, we merged this to main: https://github.com/moby/moby/pull/44216
New volumes that were created as "anonymous" volumes (e.g. docker volume create with no --name) are labeled as such, and docker volume prune only  considers those volumes for pruning by default.
Unfortunately no solution for volumes created before that PR, which will not have the "anonymous" label applied.

How can Docker devs have such a sheer negligence for 10 years? Please keep this open, just because it isn't "pruned by default" doesn't mean there can't be ways to actively protect resources from removal even by explicit commands.
I'd further suggest that Docker could support some form of access control. You may not realize it, but any application / script you ever run has the access to delete all your Docker data. The API isn't protected by anything. For starters, we may want to require admin access for certain containers to be accessed or removed. This may be UAC on Windows or root on Linux. Unless the application has full access to the entire hard drive, some resources could be also protected by a simple PIN/password (which admin can reset at any time). This would go a long way toward making Docker user-friendly on any installation that isn't just a single-purpose, security-hardened server managed by experts.

I want to experiment with using a docker container as a persistent development environment, as a transition away from a large monolithic host installation. The notion of fully "dockerizing" this large monolithic environment is unappealing due to the environment's size and complexity.
I just want the ability to flag a container to prevent it from getting deleted by a prune command when it is stopped (or the ability to mount a volume to the container root, sigh...).
I tried and failed to understand why this is closed, when this is the behaviour I am observing:
$ docker --version
Docker version 27.1.2, build d01f264
$ docker container prune
WARNING! This will remove all stopped containers.
Are you sure you want to continue? [y/N]

I want a flag I can set that must be unset before the container can be removed.
I have no relation to the commenter from 2 hours ago. That's just serendipity from my perspective.

Another possible solution could be trying to run another, personal instance of docker daemon on the same machine with separate settings file and cache directory. I read it should work for some cases. I think I'll try that.


Docker build results in "chown: changing ownership of '/build': Permission denied"

I'm trying to build the latest release (v1.29.1) of Envoy with BoringSSL FIPS-compliant mode. But regardless of what flags I'm using, or how simple the build params are, I always receive this error: chown: changing ownership of '/build': Permission denied.
This seems to be coming from envoy-build-ubuntu container that ./ci/run_envoy_docker.sh spins up to perform the build.
Repro steps:
Environment is CentOS 7.9
Docker version 20.10.17
Running the following commands as root. It's very simple, just cloning branch v1.29.1 to source code and then running the build as described in https://www.envoyproxy.io/docs/envoy/latest/start/building/local_docker_build
mkdir src/envoy

cd src/envoy

git clone --depth 1 --branch v1.29.1 https://github.com/envoyproxy/envoy.git .

./ci/run_envoy_docker.sh 'BAZEL_BUILD_EXTRA_OPTIONS="--define boringssl=fips" ./ci/do_ci.sh release.server_only'

Even if I just run ./ci/run_envoy_docker.sh './ci/do_ci.sh release.server_only' it still results in the same error:
chown: changing ownership of '/build': Permission denied

The default build temp directory is /tmp/envoy-docker-build, is that directory writable in your host machine? If not set ENVOY_DOCKER_BUILD_DIR to somewhere writable.

Hi @lizan, thanks for the reply! That directory does exist and is writable to root:
[root@host envoy-docker-build]# pwd
/tmp/envoy-docker-build
[root@host envoy-docker-build]# ls -al
total 4
drwx------.  2 root root    6 Feb 21 13:59 .
drwxrwxrwt. 19 root root 4096 Feb 22 15:16 ..


block-indentation required handlebars-expressions to be on their own line

With block-indentation, the following throws an error:

  {{t 'Use the following ID:'}}
  {{t 'id-prefix-'}}{{id}}

However, in some cases this can be necessary, e.g. if you do not want to have whitespace between two elements or translated strings. I feel that non-block handlebars expressions should not be required to be in their own lines.

@mydea you can always use whitespace control, and should!

  {{t 'Use the following ID:'}}
  {{t 'id-prefix-' ~}}
  {{id}}

Additionally, you should be able to disable this rule per template and project wide.
I'm going to close that since I think this should be sufficient, but we can always re-open if there are further thoughts. /cc @rwjblue

Oh, I did not know about that. Great to know! Thanks for pointing this out to me.
As a side note, it might be nice to add this to the Ember guides.


bbox_inside_weights, bbox_outside_weights

Hi,
Thanks for sharing the code for this simple and interesting contribution. I have a conceptual question (not an actual issue) and I'd appreciate some insight.
I am able to understand the compute_iou function directly from the paper and it seems to correspond to the source, with the exception of the appearance of bbox_inside_weights and bbox_outside_weights in line 67 of lib/utils/net.py (and its use in 68,69).
Would you mind explaining this?

In the original formulation of detectron, the final bounding box regression smooth l1 loss is bbox_outside_weights * smooth_l1(bbox_inside_weights * bbox_diff). bbox_inside_weights sets the weight of positive examples to 1 and 0 otherwise. bbox_outside_weights is used to scale loss according to the number of positive samples. Furthermore, bbox_outside_weights is used to apply different scaling factor to different components of the bounding box loss, for example, multiplying (5, 5, 10, 10) to (dx, dy, w, h). I applied bbox_inside_weights outside the loss function and took mean of component-wise scale factors because it makes less sense in IoU/GIoU which outputs a single value.
Closing the question. Please feel free to reopen it if you have any concerns or other questions


Image broken on the Map

After searching for a class, the image on the map will be broken if you click on the classroom where the class will be held

Can't reproduce, can you give an example?

Looks like it's fixed now lol, kind weird


Can this be implemented with SwiftUI?

Can this be implemented with SwiftUI?  I tried for a long time with no result.

I'm not as familiar with SwiftUI as I am with Swift.
I've only used SwiftUI to build widgets, however I believe I've seen SwiftUI tutorials on YouTube on how to build the App Store and the transition. I think it's worth a try.

Yes, I am mainly having problems in UIScrollview and haven't found a proper way to judge and set bounce properties in swiftUI yet.


add default.nix

Also sources a local.nix if present, calling it to allow users to make personal additions or modifications to the derivation attrset.
This behaves basically the same way as I set up in the DMP nix files, documented at https://alphagov.github.io/digitalmarketplace-manual/developing-the-digital-marketplace/nix.html#local-nix, and a local.example.nix is provided for reference.

Just checked, this works on macos as well as linux 🕺

This package gets built into a BOSH release and will presumably, once #3 is merged, have the go dependencies vendored in the repo, like the other brokers.
(The blobs specify what the external dependencies are, as per BOSH - Packaging software - Create release)

Backstory: I mentioned I was setting up my local dev env under nix, @philandstuff said it might be worth sticking my default.nix in the repo because he might like to use it too.
It's just for local dev. I was going to just keep it to myself, but :shrug:

I guess it depends what you expect from this - it's meant to give you the ability to get up and running with the core actions needed by all devs quickly (also keep in mind you don't actually have to run everything from within a nix-shell: you can always do a nix-shell . --pure --run 'make test' from pretty much anywhere). If you want a fancier environment, that's really up to you - I'm not sure I'm expecting to cover people who want fancy IDE integration etc.

No I definitely don't expect you to fix my environment for me!  It's just I'm settled in my ways (even if I see the benefits of nix) so I'm unlikely to use this at present unless and until I get enough tuits to do the IDE integration thing.