[CERT-TEST-FAILURE] [TC-SC-3.6][TC-RR-1.1] - Test Failed

Description:
1. Tried to validate TC-SC-3.6 and TC-RR-1.1 in V1.3 TH but
After the DUT was paired by a previous script (FAN-3.1),  ran TC-SC-3.6 and TC-RR-1.1, which resulted in failure. However, after running these two scripts, TC-FAN-3.1 passed successfully in V1.3 TH
PFA error log for TC-SC-3.6

[MatterTest] 05-29 15:33:07.955 INFO Reverted Last Known Good Time to previous value
[MatterTest] 05-29 15:33:07.958 ERROR Exception occurred in test_TC_SC_3_6.
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/mobly/base_test.py", line 783, in exec_one_test
test_method()
File "/root/python_testing/scripts/sdk/matter_testing_support.py", line 1547, in async_runner
return asyncio.run(runner_with_timeout)
File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
return future.result()
File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/root/python_testing/scripts/sdk/TC_SC_3_6.py", line 155, in test_TC_SC_3_6
new_admin_ctrl = new_fabric_admin.NewController(nodeId=dev_ctrl.nodeId)
File "/usr/local/lib/python3.10/dist-packages/chip/FabricAdmin.py", line 101, in NewController
controller = ChipDeviceCtrl.ChipDeviceController(
File "/usr/local/lib/python3.10/dist-packages/chip/ChipDeviceCtrl.py", line 1774, in init
).raise_on_error()
File "/usr/local/lib/python3.10/dist-packages/chip/native/init.py", line 87, in raise_on_error
raise self.to_exception()
chip.exceptions.ChipStackError: src/credentials/FabricTable.cpp:815: CHIP Error 0x0000000B: No memory
[MatterTest] 05-29 15:33:07.982 INFO 		***** Test Failure :
[MatterTest] 05-29 15:33:07.982 INFO Finished test in 1110ms
[MatterTest] 05-29 15:33:07.983 INFO [Test] test_TC_SC_3_6 ERROR

PFA error log for TC-RR-1.1

MatterTest] 05-29 15:33:36.459 INFO Reverted Last Known Good Time to previous value
[MatterTest] 05-29 15:33:36.461 ERROR Exception occurred in test_TC_RR_1_1.
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/mobly/base_test.py", line 783, in exec_one_test
test_method()
File "/root/python_testing/scripts/sdk/matter_testing_support.py", line 1547, in async_runner
return asyncio.run(runner_with_timeout)
File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
return future.result()
File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/root/python_testing/scripts/sdk/TC_RR_1_1.py", line 151, in test_TC_RR_1_1
new_admin_ctrl = new_fabric_admin.NewController(nodeId=dev_ctrl.nodeId, catTags=[0x0001_0001])
File "/usr/local/lib/python3.10/dist-packages/chip/FabricAdmin.py", line 101, in NewController
controller = ChipDeviceCtrl.ChipDeviceController(
File "/usr/local/lib/python3.10/dist-packages/chip/ChipDeviceCtrl.py", line 1774, in init
).raise_on_error()
File "/usr/local/lib/python3.10/dist-packages/chip/native/init.py", line 87, in raise_on_error
raise self.to_exception()
chip.exceptions.ChipStackError: src/credentials/FabricTable.cpp:815: CHIP Error 0x0000000B: No memory
[MatterTest] 05-29 15:33:36.471 INFO 		***** Test Failure :
[MatterTest] 05-29 15:33:36.472 INFO Finished test in 1164ms
[MatterTest] 05-29 15:33:36.473 INFO [Test] test_TC_RR_1_1 ERROR
[MatterTest] 05-29 15:33:36.483 INFO Teardown: shutting down all subscription to avoid racy callbacks

GitHub hash of the SDK that was being used
Version: 2.10+spring2024
Sha: 5f28838
PFA Log below for V1.3 TH:
tc-sc-3.6 and tc-rr-1.1 - V1.3 validation log.txt
2. Tried to validate TC-SC-3.6 and TC-RR-1.1 in V1.2 TH, TC-SC-3.6 got passed  but The TC-RR-1.1 is got Failed
PFA error log for TC-RR-1.1

[MatterTest] 05-28 15:21:02.540 ERROR Exception occurred in test_TC_RR_1_1.
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/mobly/base_test.py", line 783, in exec_one_test
test_method()
File "/root/python_testing/scripts/sdk/matter_testing_support.py", line 1547, in async_runner
return asyncio.run(runner_with_timeout)
File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
return future.result()
File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/root/python_testing/scripts/sdk/TC_RR_1_1.py", line 197, in test_TC_RR_1_1
new_controllers = await CommissioningBuildingBlocks.CreateControllersOnFabric(
File "/usr/local/lib/python3.10/dist-packages/chip/utils/CommissioningBuildingBlocks.py", line 140, in CreateControllersOnFabric
newController = fabricAdmin.NewController(nodeId=nodeId, paaTrustStorePath=paaTrustStorePath, catTags=catTags)
File "/usr/local/lib/python3.10/dist-packages/chip/FabricAdmin.py", line 101, in NewController
controller = ChipDeviceCtrl.ChipDeviceController(
File "/usr/local/lib/python3.10/dist-packages/chip/ChipDeviceCtrl.py", line 1576, in init
).raise_on_error()
File "/usr/local/lib/python3.10/dist-packages/chip/native/init.py", line 67, in raise_on_error
raise self.to_exception()
chip.exceptions.ChipStackError: src/credentials/FabricTable.cpp:802: CHIP Error 0x0000000B: No memory
[MatterTest] 05-28 15:21:02.551 INFO 		***** Test Failure :
[MatterTest] 05-28 15:21:02.552 INFO Finished test in 2731ms
[MatterTest] 05-28 15:21:02.553 INFO [Test] test_TC_RR_1_1 ERROR
[MatterTest] 05-28 15:21:02.564 INFO Teardown: shutting down all subscription to avoid racy callbacks

PFA log below for V1.2 :
TC-RR-1.1 and TC-SC-3.6 -V1.2 Execution.txt
3. Tried to validate TC-SC-3.6 and TC-RR-1.1 using master as DUT and CNTR, TC-SC-3.6 got passed  but The TC-RR-1.1 is got Failed
PFA error log for TC-RR-1.1

[MatterTest] 05-29 15:15:41.398 INFO Avahi group established
[MatterTest] 05-29 15:15:41.399 ERROR Exception occurred in test_TC_RR_1_1.
Traceback (most recent call last):
File "/home/ubuntu/May27_dut/connectedhomeip/no/lib/python3.10/site-packages/mobly/base_test.py", line 783, in exec_one_test
test_method()
File "/home/ubuntu/May27_dut/connectedhomeip/src/python_testing/matter_testing_support.py", line 1553, in async_runner
return asyncio.run(runner_with_timeout)
File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
return future.result()
File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/home/ubuntu/May27_dut/connectedhomeip/src/python_testing/TC_RR_1_1.py", line 196, in test_TC_RR_1_1
new_controllers = await CommissioningBuildingBlocks.CreateControllersOnFabric(
File "/home/ubuntu/May27_dut/connectedhomeip/no/lib/python3.10/site-packages/chip/utils/CommissioningBuildingBlocks.py", line 140, in CreateControllersOnFabric
newController = fabricAdmin.NewController(nodeId=nodeId, paaTrustStorePath=paaTrustStorePath, catTags=catTags)
File "/home/ubuntu/May27_dut/connectedhomeip/no/lib/python3.10/site-packages/chip/FabricAdmin.py", line 101, in NewController
controller = ChipDeviceCtrl.ChipDeviceController(
File "/home/ubuntu/May27_dut/connectedhomeip/no/lib/python3.10/site-packages/chip/ChipDeviceCtrl.py", line 1768, in init
).raise_on_error()
File "/home/ubuntu/May27_dut/connectedhomeip/no/lib/python3.10/site-packages/chip/native/init.py", line 87, in raise_on_error
raise self.to_exception()
chip.exceptions.ChipStackError: src/credentials/FabricTable.cpp:815: CHIP Error 0x0000000B: No memory
[MatterTest] 05-29 15:15:41.410 INFO Avahi group established
[MatterTest] 05-29 15:15:41.416 INFO 		***** Test Failure :
[MatterTest] 05-29 15:15:41.417 INFO Finished test in 2511ms

PFA log below for master commit
tc-sc-3.6 and tc-rr-1.1 master.txt

These errors are different than the initial errors reported on slack, which were related to the initial commissioning.
Can you please try removing the TH controller KVS file and re-trying the tests?

After removing the TH controller KVS file, I paired the DUT using a previous script (FAN-3.1).  then ran the scripts TC-SC-3.6, TC-RR-1.1, and TC-FAN-3.1, which resulted in failures in V1.3 image
error log test_TC_RR_1_1

[MatterTest] 05-29 17:40:56.357 ERROR Exception occurred in test_TC_RR_1_1.
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/mobly/base_test.py", line 783, in exec_one_test
test_method()
File "/root/python_testing/scripts/sdk/matter_testing_support.py", line 1547, in async_runner
return asyncio.run(runner_with_timeout)
File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
return future.result()
File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/root/python_testing/scripts/sdk/TC_RR_1_1.py", line 477, in test_TC_RR_1_1
Dict[int, Clusters.GroupKeyManagement.Structs.GroupInfoMapStruct]] = await self.add_all_groups(
File "/root/python_testing/scripts/sdk/TC_RR_1_1.py", line 655, in add_all_groups
add_response: Clusters.Groups.Commands.AddGroupResponse = await client.SendCommand(
File "/usr/local/lib/python3.10/dist-packages/chip/ChipDeviceCtrl.py", line 950, in SendCommand
return await future
chip.exceptions.ChipStackError: src/app/CommandSender.cpp:336: CHIP Error 0x00000032: Timeout
[MatterTest] 05-29 17:40:56.369 INFO 		***** Test Failure :
[MatterTest] 05-29 17:40:56.369 INFO Finished test in 29581ms
[MatterTest] 05-29 17:40:56.370 INFO [Test] test_TC_RR_1_1 ERROR
[MatterTest] 05-29 17:40:56.378 INFO Teardown: shutting down all subscription to avoid racy callbacks
[MatterTest] 05-29 17:40:56.383 INFO Summary for test class TC_RR_1_1: Error 1, Executed 1, Failed 0, Passed 0, Requested 1, Skipped 0
[MatterTest] 05-29 17:40:56.385 INFO Summary for test run MatterTest@05-29-2024_17-40-26-774:
Total time elapsed 29.60804031600128s

PFA log below
V1.3 (RR-1.1,SC-3.6).txt

The test cases passed after removing the KVS file in v1.3 TH.


Tutorial - Developing Your First PowerBI Visual - Building a Static Visual

I am currently mowing my way through the tutorial.
I believed that I followed the instructions on how to  Setting Up Environment.  Therefore I have started on the section on building a bar chart.
On the section that relates to Building a Static Visual I have just cut and pasted the code re Setting up ViewModel section.  So with just this code I tried to package the file (pbiviz package) and I received this error.
error TYPESCRIPT /visualPlugin.ts : <8,56> Property 'visual' does not exist on type 'typeof extensibility'
I should be able to just try to package this section and it should work right?
Secondly, is the visual playground still operational?

Hi,
Please provide some more information (the code that fails) so we can take a look. The packaging should work after each step, as long as you don't have issues.
You can see a link to a full commit at each of those steps (search for the word commit on the page) so you can have a reference to what should be done.
If you still encounter some issues, please reply.
Regarding the visual playground, this feature is deprecated, we are moving away from the old way to create custom visuals, to the new CLI tools which exposes a versioned APIs which will make sure your custom visual will always get a consist set of APIs from Power BI and your code won't break due to internal changes in Power BI code.
You should learn how to develop using the new interfaces, and share your required and missing features from the API so we will go ahead and support them.
You can find a roadmap for the new developer tools here: https://github.com/Microsoft/PowerBI-visuals/blob/master/Roadmap/README.md

I am stuck with the same error:
"error  TYPESCRIPT  /visualPlugin.ts : (8,146) Property 'Visual' does not exist on type 'typeof project_name18E995418150443A8CFACE6D6A95ABA8'."
Below attached my project folder.
pii.zip

@mehulumistry, to compile the project, please change visualClassName to PieChart. And use d3 v3.5


Please update metadata.rb --ruby sdk versions to latest one

Please update metadata.rb -- ruby sdk versions to latest versions

@ARAVINDCSEVIT can you open a PR with the change you'd like to see?


Generate fieldnames as constants

Hi! Thank you for this great framework!
I have a question if I can hook into the generation process in order to generate a constant for every field name.
What I would like to do is the following:
@Getter
@Setter
@Constants
public class StuffDTO implements Serializable {
    private String name;
}

generates
public class StuffDTO {

    public static final String PROPERTY_NAME = "name";

    private String name;

    @SuppressWarnings("all")
    @javax.annotation.Generated("lombok")
    public String getName() {
        return this.name;
    }

    @SuppressWarnings("all")
    @javax.annotation.Generated("lombok")
    public void setName(final String name) {
        this.name = name;
    }

}

Kind regards

+1
It seems like here https://github.com/rzwitserloot/lombok/pull/46 we even have a pull request for this feature.

I think that this feature is very important.
Few popular use cases would be:

You have localization messages and want to bind field names to localization keys
You have bindings DTO<->GUI form and want to bind fields to IDs in form

In this cases I always end up with something like this:
public class LoginForm {
  public static final String FIELD_EMAIL = "email";
  public static final String FIELD_PASSWORD = "password";

  private String email;
  private String password;
}

Having this feature would be a relief...

yes this feature is good to have a generic code with no regression on field renaming

Due to PR #46, something very similar to this (@FieldNameConstants) was already merged. So, I think that this should be closed.

@liemle3893 The last published version is 1.16.20 from January. However, lombok evolved significantly since then, so I'm hoping that @rspilker and @rzwitserloot publishes a new version soon.
In the mean time, get the lombok edge to enjoy the new features and bugfixes, or even build it yourself from the master branch.
To use the edge version (or a version built by yourself from the source files) with maven or gradle, you may need to juggle with some settings to use a locally installed JAR instead of something got from a repository.

Lombok 1.16.22 introduced @FieldNameConstants, so this issue can be closed.
However I suggest minor improvement: https://github.com/rzwitserloot/lombok/issues/1706


Set up GPU CI

Please describe your wishes and possible alternatives to achieve the desired result.
What does GPU CI need?

[x] import anndata, cupy; cupyx.scipy.sparse.random(100, 50, format="csr")
[x] Pytest activation mark, only run gpu tests
[x] When does this run? Start with every time?
[x] How does the secret code work?

It is managed through cirun

[ ] How do images work? https://aws.amazon.com/marketplace/pp/prodview-7ikjtg3um26wq?sr=0-1&ref_=beagle&applicationId=AWS-EC2-Console

Do we need to do our own image? @Zethson is following up with cirun. Could be the reason the test can take a while to start.

[x] Sharing coverage

Will be partially solved by: #1066
cc @Intron7

New issue: caching. My understanding is that all of github actions caching caches data to github servers. This doesn't reduce data ingress when our job isn't running on github servers. Right now this job is downloading about 1gb of data per run.
We should try and enable caching through aws.

So the billing was a little higher than expected. Basically about $2 for the one PR.
Admittedly this PR had a lot of trouble shooting pushes – about 29 commits had checks start. However a number of these checks could have been cancelled by follow up pushes, which I'll add.
Right now the entire CI run (as reported by github actions) takes about 4 minutes:

But on our billing console it says it took about 12 minutes. So what up with that? Is our billing console reporting time in an unexpected way, is the machine running for longer than github actions knows?
Any thoughts @Zethson @aktech?

I wouldn't be surprised if fetching the image and connecting to Github actions takes some time? But I guess @aktech knows this better...

But on our billing console it says it took about 12 minutes. So what up with that? Is our billing console reporting time in an unexpected way, is the machine running for longer than github actions knows?

GitHub only reports the time it took to run the job on it, nothing before or after.
There are the following times to consider:

If you're using NVIDIA images, they take a very long time to start (they have some internal provisioning, I don't know a lot about it)
there is some time to provision/initialize github actions by cirun (less than a minute)
There is some time delay (variable: 10s to 2 min) for github to start the job on it, it's a known github issue: https://github.com/actions/runner/issues/676

Using your custom AMI, (it's just basically spinning up an ubuntu machine with gpu and installing nvidia drivers yourself, and creating and AMI from it), would reduce the spinup time significantly, I can get on a call to help with this, if required.

Here’s the docs on how to set up custom images with CiRun: https://docs.cirun.io/custom-images/cloud-custom-images

You want the second section in that doc: https://docs.cirun.io/custom-images/cloud-custom-images#aws-building-custom-images-with-user-modification (first one ues nvidia image)

Thanks for the info @aktech! I've been able to get something running using that. I had been trying to create a docker file for this from some AWS docs, but it turns out it gets more complicated to generate dockerfiles for GPU setups 😢.

Are you planning to run test inside docker container? You'd still need nvidia/cuda in the base VM image I think.

Right now I am trying to see how long the instance was actually around for, but I'm not actually sure where I can see logs for this. I think our setup is a little obfuscated here, and the view I have doesn't seem to update quickly.

Currently I don't think we have that statistics in the UI anywhere, but I can consider adding it in the check run. Meanwhile, until the instance is visible in the aws dashboard (it is usually visible for sometime in the dashboard), you can run the following command to see how long it was alive for:
aws ec2 describe-instances --instance-ids INSTANCE_ID --query 'Reservations[0].Instances[0].LaunchTime' --region eu-north-1

aws ec2 describe-instances --instance-ids INSTANCE_ID --query 'Reservations[0].Instances[0].StateTransitionReason' --region eu-north-1

I had been trying to create a docker file for this from some AWS docs, but it turns out it gets more complicated to generate dockerfiles for GPU setups 😢.
Are you planning to run test inside docker container?

No, but this was just following the amazon ECR instructions for "how to create an image".
I believe you need nvidia-container-toolkit (an extension to docker) to do this kind of thing.

You'd still need nvidia/cuda in the base VM image I think.

I would like to have a more programatic way to construct these containers, so will look into this. Thanks!

I found out that I had managed to get logged into a scope with very little access, which is what was making it so difficult to see anything... Still no idea how I did that, I think maybe via the rackspace site? But now I can look at CloudTrail and have set up Config so I think we can use that.
I think times are down now. It was taking about 12 min a run last friday (according to rackspace), now it's more like 4.5 (according to aws). Github still says it's more like 2, so there's room for improvement, but still better. Of course will be good to compare measurements from the same place.
@aktech, do you have any suggestions for how we could do caching for our CI? A non-trivial amount of time is spent building wheels and downloading things, which I think we could get down. However, I don't think that Github Actions caching is going to help a ton here since it's on github's servers.

I believe you need nvidia-container-toolkit (an extension to docker) to do this kind of thing.

Yes, correct.

I would like to have a more programatic way to construct these containers, so will look into this. Thanks!

Yep, makes sense. We would have built for customers, but NVIDIA's license doesn't allows distribution, but yeah if we had the CI setup for automating this, you could have used that, but currently we don't have one public, it's a WIP.

@aktech, do you have any suggestions for how we could do caching for our CI? A non-trivial amount of time is spent building wheels and downloading things, which I think we could get down. However, I don't think that Github Actions caching is going to help a ton here since it's on github's servers.

I didn't see that, which workflow? This one seems to take less than 2.5 minutes: https://github.com/scverse/anndata/actions/runs/5716599171/job/15494250907?pr=1084

I didn't see that, which workflow?

It's not that it takes a long time, it's that it takes longer to setup than to run the tests, so I'd like to bring that down.

Triggering GPU CI
So after billing was a little higher than expected (which may be fixed, but need to confirm once billing updates) we decided not to run CI on every commit. We set the action to run on workflow_dispatch so it would be manually triggered, but it seems like we can't use this as branch protection since workflow_dispatch doesn't count towards passing a check.
So, we need something else to trigger this. It seems our options are:

a tag

 Implementation (I think)

https://stackoverflow.com/questions/62325286/run-github-actions-when-pull-requests-have-a-specific-label

on:
  pull_request:
    types:
      - labeled
      - edited
      - synchronize

jobs:
  test:
    if: ${{ contains(github.event.pull_request.labels, 'run-gpu-ci') }}

a comment
approving review
merge queue

Currently thinking a tag makes the most sense, since we can easily enable and disable it, and it isn't neccesarily linked with merging. It could be that either a label or auto merge are enough.

yup, as I thought. except for the merge queue, all of these of course mean that it’ll run for all commits after the label/comment/whatever is added.
one option would be to have the workflow remove the label again:

for each commit, all tests except for GPU tests are run
we add the run GPU tests once label
the workflow first removes the label again, then runs the GPU tests

a comment
@ivirshup the rapids-team does this with a comment from a member. this tiggers a ci run

I think there is value to giving a PR the green light to use paid CI, and not needed to approve each individual commit.
The one off case could be useful too, but I think triggering via a comment makes more sense in this case.

@Intron7, I think rapids are using API calls from checks to trigger workflow_dispatch. But they also have a pretty involved CI system: https://github.com/rapidsai/cudf/blob/branch-23.10/.github/workflows/pr.yaml

We've still got a little room for improvement on GPU CI, but I think it's pretty much set up!
Costs per run are now down to about 1 cent for anndata


Multi-scale testing get worst results on HTC

Hi, thanks your efficient code.
I have some questions when using the mutli-scale testing on HTC. When I use the 5 scales(img_scale=[(1400,1400), (1400,1200),(1400,1000),(1400,800),(1400,600) flip=True]), the mAP decreases 6% from baseline (using img_scale=(1333.800)Flip=false) on HTC.
However, the results will improve 1.0mAP when using two image scales(img_scale=[(1400,1200),(1400,600)]). Is the MultiScaleFlipAug can only using two image scales for resize?
Thank you.

Please use the Reimplementation questions to describe you problem in detail. We are not able to diagnose the issue for now due to limited information.


Add DEFRA Air Quality Sensor Observation Service

Please fill in the following information:
Base URL:
https://uk-air.defra.gov.uk/sos-ukair/service?service=SOS&request=GetCapabilities
Name:
UK-AIR Sensor Observation Service
Description:
This is an OGC standards based Sensor Observation Service interface to Defra's UK Air Information Resource (UK-AIR). The service supports the UK obligations to European air quality e-Reporting initiative & Defra Open Data policy. The SOS provides a machine readable access point for air pollution measurements funded by Defra, Scottish Government, Welsh Government & Department of the Environment Northern Ireland. The service implements INSPIRE guidelines. For more on the European air quality e-Reporting initiative go to http://www.eionet.europa.eu/aqportal.. The OGC SOS 2.0 standard is described at https://www.ogc.org/standards/sos
Documentation URL:
https://uk-air.defra.gov.uk/data/about_sos
Maintainer:
The service provider is described on the Capabilities document as: Ricardo Energy & Environment (http://ee.ricardo.com/cms/). The phone number and email address are on the GetCapabilities response document in the <ows:ServiceProvider> element.
Provider:
Department for Environment, Food and Rural Affairs (https://uk-air.defra.gov.uk)
Area Served:
Optional - The geographic area that the API serves. For example: 'Greater London'.
Start Date:
Optional - The date the API comes into service. For example: '2020-07-01'.
End Date:
Optional - The date the API will be retired. For example: '2022-07-01'.
Alternate Name:
Optional - the acronym of the department or organisation. For example: 'GDS'.
Provider URL:
https://uk-air.defra.gov.uk

Cc: @airqualityanthony

Cc: @airqualityanthony

Hey, thanks for tagging me @ghobona as it's interesting but was there a specific reason?

Hi @airqualityanthony . It was simply to make you aware of the catalogue entry.


Remove TextEncoder polyfill (#779)

TextEncoder is supported in the all browsers for a long time and also in node.js. For some node.js versions it is only available through the util package.
We do not need to support browsers like IE11 because they do not support webassembly.
This PR works on all browsers which support TextEncoding. It also works on all node versions until v8.3.0
Checklist

[x] Change is covered by automated tests
[x] Benchmark results are attached (if applicable)
[x] The coding guidelines are followed
[x] Public API has proper documentation
[x] Example projects and code samples are up-to-date (in case of API changes)
[x] Changelog is updated (in case of notable or breaking changes)

My PR basically replaces that polyfill with the node utils TextEncoder.
That should reduce the bundle size for browsers and still work on node <= 10


CI should use "-prod"

I'm not sure if this is possible during tests? If not a separate build stage to build all the binaries in stricter -prod mode.

This was fixed in #18


Verison issue with windows plugin

#define PAWNREGEX_INCLUDE_VERSION 112
It would not work with windows plugin version as 112  but it would work as #define PAWNREGEX_INCLUDE_VERSION 111
I have tried building the latest files in both windows and linux but no effect in windows while its working with linux.
And this goes opposite for linux. If its 112 then its fine and if its 111 then it dosent.

https://github.com/urShadow/Pawn.Regex/releases/tag/1.1.2


error missing on immutable form

I'm using immutable redux form, and find that the error object is missing from my decorated form  component.
error : any

A generic error for the entire form given by the _error key in the result from the synchronous validation function, the asynchronous validation, or the rejected promise from onSubmit.

I've also confirmed this on redux-form/examples/immutable/ImmutableForm.js
const ImmutableForm = (props) => {
  const { error,handleSubmit, pristine, reset, submitting } = props
  console.log(error)  // <------------------- always undefined! even when user name is empty
  return (
    <form onSubmit={handleSubmit(test)}>
      <Field name="username" type="text" component={renderField} label="Username"/>
      <Field name="email" type="email" component={renderField} label="Email"/>
      <Field name="age" type="number" component={renderField} label="Age"/>
      <div>
        <button type="submit" disabled={submitting}>Submit</button>
        <button type="button" disabled={pristine || submitting} onClick={reset}>Clear Values</button>
      </div>
    </form>
  )
}

ok. seems I have got it wrong.
the error object that redux-form would pass to your decorated component is the SubmissionError object returned in your onSubmit function;
it does NOT propagate the error object returns from validate prop of redux-form.
So how can I get field errors from my wrapped form component??

You could create a selector for it and grab the data using react-redux's connect function.
Use the redux devtools to see the state tree.
I don't use immutable but for me the path is state.form['myformname'].syncErrors or state.form['myformname'].asyncErrors
You could create a selector where you pass in the name of the form and the name of the field and it could return an errors for you.

If anyone looks this up, note that any import from redux-form and not redux-form/immutable in your code will break things like error handling (even if it 'appears to work' at first sight).

Answers include getFormMeta, creating your own custom selector as @kristian-puccio suggested, or using Field or Fields to act as connectors to get the fieldMeta you need.


[Bug]: Dropdown Menu for Services Not Displaying Properly in Membership Page

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When I click on the "Services" menu, the dropdown does not display clearly, showing a white background that makes the text hard to display.

Expected behavior
The dropdown should have a contrasting background color to ensure the text is easily readable.
Add ScreenShots
The dropdown menu appears with a white background, making it difficult to see the text.
On which device are you experiencing this bug?
Chrome
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSOC'24 contributor
[X] I have starred the repository

Kindly assign me this task under Hacktoberfest2024, Thanku.


Add RegML from regulations-schema

This PR relocates the XML from within the schema definition (regulations-schema). This should help clean up the schema definition repo a bit.

yay


Add Api content Pull Request

Implementations in this project

Used [axios] to make your HTTP requests to the backend
Fetch your books from the Bookstore API after the component has rendered
Refactor add book and remove book features to persist your changes in the server
Application should behave the same way after the refactoring

@levy002 adds the first book successfully but when adding the second we receive this error message "'category' is required." is resolved and now when adding a book and need to another book so its working exactly demanded.


fix: update node for build and other ci scripts

size-limit report 📦

Path
Size

dist/es/index.js
-9 B (0%)

dist/cjs/index.js
-32 B (0%)

-52 B (0%)


Bug with anchors and !apply

This minimal example crashes and claims there's duplicate tags:
import hyperpyyaml

yaml_string = """
a: &id010
 - a
 - b

b: &id001 !new:collections.Counter
 - abcd

d: !apply:operator.add
 a: *id010
 b: *id001
"""

print(hyperpyyaml.load_hyperpyyaml(yaml_string))

gives:
yaml.composer.ComposerError: found duplicate anchor 'id001'; first occurrence
  in "<file>", line 1, column 4
second occurrence
  in "<file>", line 5, column 4

It looks like the bug is triggered specifically by the presence of constructors.
This does not trigger the bug
yaml_string = """
a: &id010
 - a
 - b

b: &id001
 - abcd

d:
 a: *id010
 b: *id001
"""

print(hyperpyyaml.load_hyperpyyaml(yaml_string))

Also it appears to be in Hyperpyyaml specifically. The rough pyyaml equivalent does not seem to be triggering the issue
import yaml

class Foo:
    def __init__(self, a, b):
        self.a, self.b = a, b
    def __repr__(self):
        return f'(Foo: a={self.a}, b={self.b})'

yaml_string = """
a: &id010
 - a
 - b

b: &id001 !!python/object:__main__.Foo
 a: 1
 b: 2

d: !!python/object:__main__.Foo
 a: *id010
 b: *id001
"""

print(yaml.load(yaml_string, Loader=yaml.Loader))

Getting this output:
{'a': ['a', 'b'], 'b': (Foo: a=1, b=2), 'd': (Foo: a=['a', 'b'], b=(Foo: a=1, b=2))}

I was able to isolate the issue to resolve_references
yaml_string = """
a: &id010
 - a
 - b

b: &id001 !new:collections.Counter
 - abcd

d: !apply:operator.add
 a: *id010
 b: *id001
"""

# %%
rref = resolve_references(
    yaml_string, None, True
)
print(rref.read())

The output is:

rref = resolve_references(...
a: &id001
- a
- b

b: &id001 !new:collections.Counter
- abcd
d: !apply:operator.add
  a: *id001
  b: *id001

It looks like it's ruamel.yaml that's doing this:
import ruamel.yaml
ruamel_yaml = ruamel.yaml.YAML()
preview = ruamel_yaml.load(yaml_string)
yaml_stream = StringIO()
ruamel_yaml.dump(preview, yaml_stream)
yaml_stream.seek(0)
print(yaml_stream.read())

The output is:
a: &id001
- a
- b

b: &id001 !new:collections.Counter
- abcd
d: !apply:operator.add
  a: *id001
  b: *id001

Bug reported to ruamel.yaml:
https://sourceforge.net/p/ruamel-yaml/tickets/387/

Yes that is caused by ruamel.yaml. It recognizes templated anchors (of the form idNNN), and doesn't set an explicit anchor if those are encountered (resulting in a potential renumbering). It forgot to check for templated anchors in undefined objects (those tagged) nor does it guarantee that all anchors are templated or all are non-templated.
This should be fixed with 0.17.8

Looks like this is solved


Clarify debugger soundness expectations

There is ambiguity about how much the debugger should respect soundness guarantees in Dart.
See https://github.com/dart-lang/sdk/issues/45455#issuecomment-832563934
Example:
void foo(int? x) {
  if (x != null) {
     something(); // <-debugger break here, change x to null.
     x.toRadixString(16); // Soundness breached. If not careful, this can cause a core-dump in native code.
  }
}

The language team perspective is the debugger should probably prohibit assigning null to x there.
Currently it is not possible to modify variables using eval in the debugger so the issue is moot but if that was possible we would need to discuss semantics so we don't crash.

I'd prefer if the debugger cannot crash the program. That is quite possible in this example if the .toRadixString call assumes that the x value has a String V-table, without checking, something that should be a sound implementation choice. That could lead to a core dump.
On the other hand, changing the value of x (if that was possible) is already outside the semantics of the program, and nobody says that crashing the program is necessarily wrong in that case. It's just inconvenient.
An alternative is to disable some optimizations when the debugger is enabled, or recompiling methods when they are entered by the debugger (if it's JIT compiled code). That's still a valid implementation, just a not quite as fast one. It obviously risks hiding bugs in the optimizations from being detected by debugging, but that should not affect end users (we don't ship bugged optimizations, surely.)
What I definitely do not want is disabling optimizations in production mode just because they interact badly with the debugger. Most programs aren't debugged.

Does this happen while running natively on the VM? When breakpoints are set in a method we run unoptimized code and I would be surprised if this crashed.


Check if we should limits the targets we're building

Hint from @kwk :
Check which targets are actually being built. Not setting -DLLVM_TARGETS_TO_BUILD=X86 might cause all of them to be built.
CMakeCache.txt says LLVM_TARGETS_TO_BUILD:STRING=all
And the cmake log output contains:
-- Targeting AArch64
-- Targeting AMDGPU
-- Targeting ARM
-- Targeting AVR
-- Targeting BPF
-- Targeting Hexagon
-- Targeting Lanai
-- Targeting Mips
-- Targeting MSP430
-- Targeting NVPTX
-- Targeting PowerPC
-- Targeting RISCV
-- Targeting Sparc
-- Targeting SystemZ
-- Targeting WebAssembly
-- Targeting X86
-- Targeting XCore

Maybe we could save some build time by restricting the targets to X86...

Will try that

If you build only with X86 you won't cover the other targets though?

I have tried to run with -DLLVM_TARGETS_TO_BUILD=X86 https://buildkite.com/llvm-project/llvm-master-build/builds/930, with all: https://buildkite.com/llvm-project/llvm-master-build/builds/931
So duration Linux changed from 36 to 30m (20%) and Windows from 62m to 54m (13%) for non cached build. Note that this is 1. single run 2. non cached build.

If you build only with X86 you won't cover the other targets though?

Do we have any evidence that building more targets finds more bugs?
Or the other way round: Do we have evidence that a significant amount of bugs only affect a subset of the targets and can be caught this way?
If not I would go for a faster build.

For partially cached build on windows: https://buildkite.com/llvm-project/llvm-master-build/builds/943, 42m to https://buildkite.com/llvm-project/llvm-master-build/builds/946, 35.5m (-15%). That is consistent with the result above.
As for covering other platforms: it would be nice if there were some heuristic to detect if change is potentially non-cross platform. Also, we don't coverall configurations anyway (asan etc.).
I would suggest to set x86 target for pre-merge checks and leave all targets enabled for release / master tests. What do you think?

Or the other way round: Do we have evidence that a significant amount of bugs only affect a subset of the targets and can be caught this way?

All the tests here are exercising code in the backend.
I'm not sure I understand your view here: disabling a feature by building less code always mean faster build, but also means that the code your disabling is not tested. But this is a general property though: if we disable lld we get faster builds/tests, and lld does not contribute to finding a single bug for my patches (mostly MLIR), and vice-versa: for the lld folks we don't need to build MLIR, flang, and clang.
So for the targets it is a choice on what you try to test: folks working on the ARM64 backend won't get any of their code tested at all for example if you don't configure it in.

Oh an there are tests and build target we build in MLIR only if a backend is configured (we have passes that require NVPTX and AMDGPU right now), for example here: https://github.com/llvm/llvm-project/blob/master/mlir/CMakeLists.txt#L36

Yea, I agree that it's better to test more unless we have a good idea of affected projects / architectures and can safely exclude some.


Add logging to app using simple credentials.

Session time - 5 minutes using JWT.
User Data in postgresql database.
Hibernate simple configuration
first docker-compose.yml with postgresql-10 database

Credentials to modify
Docker-compose should build and link everything


Kivy iOS - mediapipe module

Software Versions

Python: 3.10/3.11
OS: MacOS Venture 13.3.1
Kivy installation method: followed exactly this -> https://kivy.org/doc/stable/guide/packaging-ios.html

Describe the bug
I develop python app using kivy and trying to build it as iOS. However, there is always this error when running:
ModuleNotFoundError: No module named 'mediapipe'
Is Mediapipe not yet supported for kivy ios? Thank you!

mediapipe is not a plain-python library, and you'll need a recipe to build it.
Feel free to open a feature-request on kivy/kivy-ios


CS0121 Compilation error with .NET 6 and delegates

Description
I am not sure why I am seeing a CS0121 in the following code snippet taken from a Console application:
MyClass.M1(() => {  });
MyClass.M2(() => {  }); //CS0121 here -- " Error CS0121 The call is ambiguous between the following methods or properties: 'MyClass.M2(MyDelegate)' and 'MyClass.M2<T>(T)"

public delegate void MyDelegate();

public static class MyClass
{
    public static void M1(Action test) { }

    public static void M1<T>(T test) { }

    public static void M2(MyDelegate test) { }

    public static void M2<T>(T test) { }
}

I would expect that both methods M1 and M2 would be treated in the same way, given that Action and MyDelegate have the same signature.
Configuration
Problem is present in .NET 6.0.0-rc.1, but not in .NET 6.0.100-preview.7.21379.14 or .NET 5.

This also affects applications that use NLog's ILogger interface, which has both delegate and generic overloads.

We're hitting this with NUnit assertions which suffer from the same issue.

These might have been fixed by https://github.com/dotnet/roslyn/pull/56341, see linked issues on that PR. /cc @cston


Issues signing into Storage Explorer when using MFA

Storage Explorer Version: 1.13.0
Build Number: 20200430.5
Platform/OS: Windows
Architecture: ia32
Regression From:
Bug Description

When I try to authenticate to pull up Storage Resources I get the following error when signing in while using MFA.
{
"message": ""email address' returned by service does not match user 'userprincipalname' in the request""
}
Steps to Reproduce

User resets Azure Storage Explorer OR uninstall and re-installs it
Click Add an Azure Account
Enter UserPrincipalName
Gets directed to company SSO platform (taking you to your organization's sign-in page)
Successfully authenticates with SSO platform. (administrators can see a successful authentication for Office-365 in SSO platform logs)
User sees warning that UserPrinicipal Name could not be loaded. Please try reentering credentials or removing and re-adding the account.
User authenticates again with SSO platform, this time the Id shows as email instead of userprincipalname
User authenticates again successfully
User is finally presented with error
Unable to sign in: User 'email' returned by service does not match user 'userprincipalname' in the request""
Expected Experience

Actual Experience

Additional Context

@ymaxwell could you please do the following?

Update to version 1.14.0
Enable MSAL and verbose authentication logging. Each can be found under Settings (gear icon on the left) -> Application -> Sign-in
Close Storage Explorer
In file explorer, go to C:\Users<your username>\AppData\Local\Temp\servicehub and delete the folder logs. Leave file explorer open.
Re-open Storage Explorer
Sign in
Once you get to the error message, go back to file explorer, zip up the logs folder, and attach it here.

Closing due to lack of response. Please open a new issue if you are still having problems. Thanks.


x/tools/gopls: Error loading workspace: You are outside of a module and outside of $GOPATH/src

What version of Go are you using (go version)?

$ go version
go version go1.16.2 windows/amd64

Does this issue reproduce with the latest release?
No
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\Anjar\AppData\Local\go-build
set GOENV=C:\Users\Anjar\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\Anjar\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\Anjar\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.16.2
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=D:\Camp Latihan Pemrograman\Heroku\go-getting-started\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\Anjar\AppData\Local\Temp\go-build3937432002=/tmp/go-build -gno-record-gcc-switches

What did you do?

What did you expect to see?
No error and import file using go get depedency found folder to $goroot or $gopath
What did you see instead?
Error on importing file

Can you please share your gopls logs? Information on how to capture them can be found here.

golang.org/x/tools/gopls v0.6.9
<EMAIL_ADDRESS>h1:LBBcE2y3Tb4bp79JVLWCQBbvYCFEs5ADGWsQDoSLk1Q=
<EMAIL_ADDRESS>h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
<EMAIL_ADDRESS>h1:L8R9j+yAqZuZjsqh/z+F1NCffTKKLShY6zXTItVIZ8M=
<EMAIL_ADDRESS>h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
<EMAIL_ADDRESS>h1:Kvvh58BN8Y9/lBi7hTekvtMpm07eUZ0ck5pRHpsMWrY=
<EMAIL_ADDRESS>h1:SQFwaSi55rU7vdNs9Yr0Z324VNlrF+0wMqRXT4St8ck=
<EMAIL_ADDRESS>h1:VwygUrnw9jn88c4u8GD3rZQbqrP/tgas88tPUbBxQrk=
<EMAIL_ADDRESS>h1:O5bm8buX/OaamnfcBrkjn0SPUIU30jFmaS8lP+ikkxs=
<EMAIL_ADDRESS>h1:go1bK/D/BFZV2I8cIQd1NKEZ+0owSTG1fDTci4IqFcE=
<EMAIL_ADDRESS>h1:EVDuO03OCZwpV2t/tLLxPmPiomagMoBOgfPt0FM+4IY=
<EMAIL_ADDRESS>h1:hsVv+Y9UsZ/mFZTxJZuHVI6shSQCtzZ11h1JEFPAZLw=
<EMAIL_ADDRESS>h1:NSZPykBXJFCetGZykLAxaL6SIpvbVy/UFEniIfHAa8A=

Thanks for sharing that, but that's your gopls version output. I'm looking for the logs produced by gopls as it runs--https://github.com/golang/vscode-go/blob/master/docs/troubleshooting.md#collect-gopls-information describes how to gather these logs. Thanks!

I am facing the same issue. Did you find the cause and solution?

I try to select a workplace and type code. on current folder.

@granzginz, @Bittu0184: Please provide your gopls logs so that we can help investigate the issue. Information on how to capture them can be found here.

Closing, as there hasn't been any activity on this issue for a few weeks.


DropDown missing visible outline when in focus

Bug Description

DropDown field is missing visible outline when in focus
Expected Behaviour

It should be visibly understandable where focus is when tabbing to DropDown field.
Steps to Reproduce

Add a Text element
Start tabbin in design panel
See no visibile indication of dropDown being in focus.

Screenshots

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

Consolidating with #737


Remove tests for Neutron API extensions not applicable to contrail

Tempest tests which were trying to validate presence of Neutron API extensions were failing since a few standard extensions are not applicable to contrail. This patch removes them so the tempest tests pass in our production environment.

Merged into branch jiochanges


Search in Launcher

As a user I want to search for specific plugins to be able to find them quickly.

[ ] there is a text-search to find plugins based on their names
[ ] when searching the page of plugins will be reduced to fitting ones
[ ] i can click on the found plugins to open them


NIFI-6576 add basic auth to confluent schema registry service

Description of PR
Adds basic authentication support to the Confluent schema registry controller; fixes bug #4224
A pull request (https://github.com/apache/nifi/pull/4224) was originally created by @teeberg to resolve this issue, and @alopresto provided code review feedback on 27-Apr-2020, however no additional commits were provided to address the code review feedback.
This PR updates the code contributed in https://github.com/apache/nifi/pull/4224 to incorporate the code review changes requested in the original PR.
Current versions of the Confluent Schema Registry only support basic authentication, so support for digest authentication which was present in the original PR has been removed.
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Hi @mark-weghorst and @alopresto - I'm interested by this additional feature.
Mark, do you think you're going to follow up on this (or are you waiting for additional feedback)?

@pvillard31 yes I'm still planning on re-working this to address the code review comments from @alopresto
Unfortunately, I haven't had the time to revisit this due to some more pressing work, I should have some time towards the end of the week to pick back up on this.

awesome, let me know if I can be of any help!

@mark-weghorst Thanks for responding to comments and making updates.  Regarding the dependsOn properties, the current version of the Developer Guide has some helpful documentation under Validating Processor Properties..  Following the example described, the Username and Password properties described could include a dependsOn(PROP_AUTHENTICATION_TYPE, "BASIC") builder method which would make them dependent on selecting BASIC as the Authentication Type property.

This feature would be absolutely amazing. Thanks everyone for the work so far. Hope to use it soon :)

We pushed this over the finish line with @exceptionfactory, thanks for all the work on this PR @mark-weghorst !

We pushed this over the finish line with @exceptionfactory, thanks for all the work on this PR @mark-weghorst !

Thank you @exceptionfactory  for your help getting this pushed over the finishing line over the holidays!

Thank you @exceptionfactory  for your help getting this pushed over the finishing line over the holidays!


Add concat plate LM visualizations

Add concat plate LM visualizations
In this PR, scatter plot visualizations per plate are added where the plate and genotype beta coefficient contributions are compared using the merged plate LM data. We are looking to assess if genotype or plate contributes more to each feature. We are seeing that consistently across plates that ER features are less impacted by plate while many other features look to be more contributed by plate and not genotype.

@axiomcura Thanks for the review! I'll be merging now!


"ReportingServicesMgmt.cs"

Hi,
I tried to compile the code but its referencing "ReportingServicesMgmt.cs", am I doing something wrong? or lacking a step? please help.
Thanks.
Dennis.

Hi,
I have the same error. Any solution?
Thanx

I'm sorry, the file wasn't pushed to the repository.
Should be there now.

THANK YOU!!!!!!!!!!!!!!!!!!! YAY!!!!!!!!!!!!!!!
On Thu, Sep 3, 2015 at 1:54 PM, Philipp Resch<EMAIL_ADDRESS>wrote:

I'm sorry, the file wasn't pushed to the repository.
Should be there now.
—
Reply to this email directly or view it on GitHub
https://github.com/dapaxx/reportsync/issues/1#issuecomment-137416023.


#254 Video Section responsive to all resolutions

The video width and height now adapt to all resolutions. Added bottom padding to the video section and increased the section title font size for smaller resolutions.

@Eldi47 When you are working on the things in the above-mentioned comments, please also work on the following:
(1) Resizing the video for desktop into having more width. We want the video width to be similar to the one from the webpage https://thehub-aubg.com/hackaubg (also check pictures below for reference)
(2) Add height to the overall container. At times, the unassigned height is leading to other sections getting into the video section space.

@Eldi47 please work on the requested changes. Also note that I removed the .video div and moved the class to the iframe, since the div was just holding the iframe and I didnt see its use as necessary.


Add ExtensionGroup API and fix registration of multiple extensions

This PR brings the ExtensionGroup API to the 1.6.0 branch.
It seems that I got it wrong on the current master by assuming that I can do multiple executions of Asciidoctor::Extensions.register with the same groupName.
If I didn't get it wrong it overwrites a previous registration.
Therefore I hopefully fixed it here by collecting all extensions in list or maps per type and the registering them in one go in the Ruby code (asciidoctorclass.rb).
There was also an error with multiple executions of extensions that were registered as instances.
For these it was tried to call setConfig twice which was rejected with an IllegalStateException. I fixed this by adding a method updateConfig that can be executed multiple times and add to the existing config.
In such a case it is probably not clever to use the same Asciidoctor instance concurrently to render documents.
I copied many of the existing extension tests and migrated them to the group API to get a better coverage.

It seems that I got it wrong on the current master by assuming that I can do multiple executions of Asciidoctor::Extensions.register with the same groupName.
If I didn't get it wrong it overwrites a previous registration.

Yes, it overwrites the previous registration. The groupName can only be used to hold a single set of extensions. In Asciidoctor core, and ExtensionGroup is used to bundle extensions together, which then get associated with a group name.

Therefore I hopefully fixed it here by collecting all extensions in list or maps per type and the registering them in one go in the Ruby code (asciidoctorclass.rb).

Yes, that's correct.

In such a case it is probably not clever to use the same Asciidoctor instance concurrently to render documents.

Yes, not unless the extensions are pre-activated. Though we could certainly consider trying to make this possible in the future.

Refactored ExtensionGroupImpl and asciidoctor_module.rb by moving the concrete registration into the java code again and avoid smearing the internals of ExtensionGroupImpl into the Ruby code.


Feat/webtypes default icon

option for adding a default-icon added.
closes #99

Does the icon need to be included in the project or can it reference a URL?

Would you be willing to update the README.md with information about this?

During adding the documentation i spotted that referencesTemplate is wrong documented. The Options type wants a referenceTemplate. And after playing with this option, i realised that the code is never called.
I will file another issue on this.

Would you be willing to update the README.md with information about this?

done

@break-stuff Is there any other actions from my side expected before merge?

I think we're good! Thank you!


[Youtube] ERROR: Incomplete YouTube ID

$ youtube-dl "https://www.youtube.com/watch?v=NBWv5GWODaE"
ERROR: Incomplete YouTube ID NBWv5GWDaE. URL https://www.youtube.com/watch?v=NBWv5GWDaE looks truncated.

youtube-dl with -v flag:
$ youtube-dl -v "https://www.youtube.com/watch?v=NBWv5GWODaE"
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.youtube.com/watch?v=NBWv5GWDaE']
[debug] Encodings: locale UTF-8, fs utf-8, out utf8, pref UTF-8
[debug] youtube-dl version 2017.01.25
[debug] Python version 3.4.5 - CYGWIN_NT-10.0-2.6.1-0.305-5-3-x86_64-64bit-WindowsPE
[debug] exe versions: ffmpeg git-2016-12-10-edb4f5d, ffprobe git-2016-12-10-edb4f5d
[debug] Proxy map: {}
ERROR: Incomplete YouTube ID NBWv5GWDaE. URL https://www.youtube.com/watch?v=NBWv5GWDaE looks truncated.
Traceback (most recent call last):
  File "/usr/lib/python3.4/site-packages/youtube_dl/YoutubeDL.py", line 694, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3.4/site-packages/youtube_dl/extractor/common.py", line 359, in extract
    return self._real_extract(url)
  File "/usr/lib/python3.4/site-packages/youtube_dl/extractor/youtube.py", line 2566, in _real_extract
    expected=True)
youtube_dl.utils.ExtractorError: Incomplete YouTube ID NBWv5GWDaE. URL https://www.youtube.com/watch?v=NBWv5GWDaE looks truncated.

What's this? thanks!

Read the error message. https://www.youtube.com/watch?v=NBWv5GWDaE is not a valid video URL.

Oh, I know what the problem is.
URL is https://www.youtube.com/watch?v=NBWv5GWODaE
But I have this code in my .zshrc
bindkey "OC" forward-word
bindkey "OD" backward-word

So https://www.youtube.com/watch?v=NBWv5GWODaE
becomes https://www.youtube.com/watch?v=NBWv5GWDaE
:p

Facing the same problem on Windows 10 on Powershell with Youtube-DL 2021.03.03. The command was-
 youtube-dl https://www.youtube.com/watch?v=ho91w
The error was-
ERROR: Incomplete YouTube ID ho91w. URL https://www.youtube.com/watch?v=ho91w looks truncated.

I had the same error , and indeed the video URL i passed to youtube-dl by the shell got one or two letters truncated ; due to the fact the URL in my case contained the capital letter "F" which was bound as a key binding within the .bashrc file .

Faced the same issue. Just launch the yt-dlp from cmd, not powershell.


Only a window of VSCode is whitish.

Though the response was normal, only a window of Visual Studio Code seems to be white fog, in every monitor.
That was a sudden affair, but I was doing then, only seeing WEB on GoogleChrome.
The following I had tried, but a result didn't change.
1.OS(Windows 10) restart, included Windows Update.
2.I had uninstalled VSCode, I had deleted all setting files . Next, I had installed VSCode once again.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

Thank you for the information.
I could confirm that there was no problem, I tried using this.

Ok, this will be released as 1.40 this week.


Carthage install isn't doing the complete setup

An EarlGrey user ran into a problem with Carthage installation. They had to follow steps outlined here to fix their issue:
https://github.com/google/EarlGrey/blob/master/docs/install-and-run.md#final-test-configuration-
It seems like the gem isn't automating everything outlined in the Final Test Configuration.
The specific problem was that they weren't able to run tests on devices because they kept getting dyld: warning: could not load inserted library<EMAIL_ADDRESS>because image not found. Manually making modification suggested in Final Test Configuration fixed it for them.

Did doing earlgrey install -T TestTargetName solve the issue?

The command I used was earlgrey install --carthage --swift-version=2.3 --scheme=MyApp --target=MyAppUITests. I was able to run UI tests on the simulator, but wasn't able to until Step 3 in the Final Test Configuration for the manual install process was done


Month View for February/March not displayed properly

When displaying February 2016 month view, the dates are not displayed properly.
Similar issue occurs with subsequent February/March months. May be due to February having  a different number of days each year..?

Hi @sashawilcox, thank you for reporting this.
Unfortunately I am unable to see this issue, as you can see in the demo page February looks correct.
So, could you share your full configuration or provide a working example? Thanks

Hi @indrimuska, I'm a dev on the same project. We're using version 0.1.3 of angular-moment-picker, and version 0.2.2 of angular-momentjs. I'm able to reproduce this with the default configuration and as basic a template as:

(ctrl.date starts null)

Thank you @sroutledge for confirming this bug, but I really can't reproduce that behavior.
This is the plunker I tested, but I can't see anything strange or incorrect in it.
Could you please help me to understand where the problem is, just updating that plunker?
Thanks

@indrimuska
I was able to narrow it down to the version of angular we're using:
http://plnkr.co/edit/TwpUvqD1dQOfU3wIopQ2
Seems that it happens with angular versions 1.3.x (1.3.20 in our case)
Angular version 1.4.0 works as expected. We will look at upgrading our version of angular.
Thank you for your time!!

Adding: since the 1.4.0 update introduced some breaking changes for Angular, we may not be able to upgrade right away. If you can implement a fix for 1.3.x versions of Angular, that would be awesome, too!

Good to know @sroutledge, give me some days to see the difference between these two versions.
@sashawilcox can you confirm that your issue is caused by the version of Angular?

Ok, I think the problem is this (doc):

Angular versions up to and including 1.3 sort the keys alphabetically.

Since Angular Moment picker uses an object of weeks where the keys is the number of the week in the year, and since weeks of February 2016 start from 6th to 11th, I think that Angular sorts the object using this order: 10, 11, 6, 7, 8, 9. That is because it uses an alphabetical sort, not a natural or a similar sort.
Maybe I could release a unique version available even for this version of Angular. :)

Thanks @indrimuska! I can confirm that's it's caused by the Angular version :smile:

FYI this is now available in 0.2.1.
Thank you all for reporting this! :)


*Enhancement: Mob Duplicator - spawn area location

Modpack: Direwolf20 1.12 Version: 1.4.0
Industrial Foregoing: 1.12.2-1.6.3-107
Tesla-core-lib: 1.12-1.0.12
Right now The mob duplicator spawns mobs all around it like a vanilla spawner. However all the other mob/animal blocks in the mod feed/kill/plant/harvest in "front" or on  "top" of the block. To keep the duplicator in line with the rest of the mod why not change it to spawn on top of the block like a Plant Sower or possibly in front like a Animal Rancher/Mob Slaughter Factory/Mob Crusher. Keeping the 9x9x5 isn't a big deal as there are tons of ways to move mobs around. Having to string cables into the middle of a spawning room looks terrible though.
Regardless if you make the change, Thanks for reviving, porting and maintaining the old MFR!!

It is a bit late to change it now, maybe in 1.13

With all the changes to machine ranges, maybe you could consider adding configuration options for the range and offset of the range for each machine?

I might but I don't want to overcomplicate the config.

I understand not wanting to overcomplicate things, but what aspect are you concerned about?
The in-game config gui? The need to read config values for machines? Just trying to understand your line of thought to maybe suggest something.
Maybe config values with current values as defaults, not exposed in the config GUI, editable by people interested and pack makers could be a reasonable choice?
That would only leave the fact of having to read those config values instead of hard coding them.
If I am not wrong, you would only need 3 values:
radius, front/back offset and up/down offset.
You could simplify it to radius if it seems too complicated and hard code offsets maybe?


SPOI-5472 - Undeploy heartbeat requests are not processes if container is idle

SPOI-5472 #resolve

cherry-picked to 3.0


Travis improvements

Main changes are:

Enabled running tests on travis' container based infrastructure
This solves that tests can now be run for forks which default to the container based infrastructure when created after 2015.
Refs:

https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
See eg. https://travis-ci.org/jsor/event-loop/jobs/198781026#L158, builds are failing here

composer install

Moved from travis-init.sh to .travis.yml
Removed deprecated --dev option
Removed --prefer-source not longer required to prevent rate limit issues, see https://github.com/composer/composer/issues/4884#issuecomment-195229989

Run tests on PHP 7.1

For the reference: Updated the milestone to "v0.5.0" because this actually landed in the master branch instead of the "0.4" release branch (because it's been merged after #72).


fetch:cookiecutter: take into account template-local cookiecutter.json

Feature Suggestion
cookiecutter supports features that can be configured in cookiecutter.json, e.g. copy without render.
The suggestion is that fetch:cookiecutter takes a template-local cookiecutter.json into account.
values passed to fetch:cookiecutter will override those in the template-local cookiecutter.json, e.g. use_ci passed in from the scaffolder (UI) will override the static use_ci configured in the template-local cookiecutter.json.
Related discord chat
Possible Implementation
In templater/cookiecutter.ts, lookup templateContentsDir/cookiecutter.json and merge-in the auto-generated templateDir/cookiecutter.json.
Context
I'd like to make use of cookiecutter templates already in use within our organisation (before scaffolder) and keep their current behaviour as far as possible.

This conversation moved slightly ahead in discourse where @benjdlambert mentions:

right now anything that's in the template folder is the template

That's a bit of a surprise as cookiecutter repos are typically structured as https://github.com/spotify/cookiecutter-golang is. I'd love to be able to clone that into the workDir, and finally publish the generated {{cookiecutter.component_id}} directory to a fresh repo. If this has been discussed before, please point me to the conversation so I can catch-up (a quick search didn't reveal anything).

So https://github.com/spotify/cookiecutter-golang is a legacy template still, not in the new v2 format. You'll see that it actually has a cookiecutter.json in it too which is used. https://github.com/spotify/cookiecutter-golang/blob/master/cookiecutter.json. But unfortunately, this wont work for v2 as we build that file automatically, and there's no more {{cookiecutter.component_Id}} as component_id doesn't make sense anymore as you can template anything. So using v1 templates, or the legacy version I think would work, but we need to solve v2.
There's two approaches I can think to solve this, we can place the cookiecutter.json under the ./template directory and just assume that if in the template directory there is a cookiecutter we should move that out of the skeleton and pass it to cookiecutter as config, or we can pass in the cookiecutter.json as options to publish action in v2 schema:
  - id: fetch
     name: fetch
     action: fetch:cookiecutter
     input:
       config:
         _copy_without_render: ["some/glob"]

Or something similar to this?

I see. So for v2 if we're staying with the decision that "./template contains only the template", then I'd vote for you suggestion to pass cookiecutter config as config to fetch:cookiecutter. That keeps it in sync with another design choice mentioned in (https://github.com/backstage/backstage/issues/4824#issuecomment-791045769, hooks as custom actions) where all config / hooks etc. will then be visible from the action config.
If there's more agreement, I'm happy to create a PR to keep moving this forward. In which case, let's head to the bike shed: do we want both config and values:
  - id: fetch
     name: fetch
     action: fetch:cookiecutter
     input:
       config:
         _copy_without_render: ["some/glob"]
       values:
         name: '{{ parameters.name }}'

or, i'm guessing someone with little awareness of cookiecutter (e.g. myself) know that all these end up in a cookiecutter.json, shall we merge these and have:
  - id: fetch
     name: fetch
     action: fetch:cookiecutter
     input:
       config:  // (or explicitly call it cookiecutter.json) description: key-value pairs to be added to the generated cookiecutter.json
         name: '{{ parameters.name }}'
         _copy_without_render: ["some/glob"]

Merging them all under config causes a backwards incompatible change, so i'd like not to do that if possible :) thoughts @freben  @Rugvip ?

ah yes, fair point about backwards incompatible change.

@vinayvinay @benjdlambert I thinking that keeping config separate from the template content is bad because for example _copy_without_render is very coupled to the template contents. We're already setting values in the template definition though, so that point is a bit moot.
It seems like _copy_without_render is the only magic key that cookiecutter has atm, with the rest of the values just being used for the templating? I'd actually suggest the following:
  - id: fetch
     name: fetch
     action: fetch:cookiecutter
     input:
       copyWithoutRender: ["some/glob"]
       values:
         name: '{{ parameters.name }}'

Especially with #4869 I'd argue that this makes it even more discoverable and easy to use than if we send people over to the cookiecutter config docs. It ofc means we need to stay in sync with cookiecutter, but I'd also imagine there's not a lot going on there atm. It also lets us be a bit more explicit about which config options we forward and cookiecutter's way of doing things doesn't always fit well with a templating service from a security point of view.

@rugvip yep fine to me. That was the other way, but wasn't sure it was worth creating a mapping for it. Let's go with that then, copyWithoutRender input argument to the fetch:cookiecutter action 👍

Sounds good @Rugvip. The only other cookiecutter "magic key" i could find is _extensions so might want to add that in too, while we're at it.
Slightly off topic but kinda related, if you have a moment, I'd love to learn more about the decision "./template only has the template" because cookiecutter supports multiple template directories under a single directory or repository. If we assume that the url always points to a single-template, we're forcing one-template-per-repo on the users of this action. Which is not the end of the world, if we support input.cliOptions or similar for this action, so that one can use --directory and use a cookiecutter monorepo.

Isn't it quite unfortunate if you have an existing, actually functioning cookie cutter, but the scaffolder doesn't handle it by default without duplicating things into the template yaml?

@vinayvinay The templater had some quite magic logic to identify the output directory in the old format, it didn't support multiple template directories either. We also didn't want to allow for hooks to be used, as they're executed as scripts on the host machine which isn't ideal. Tbh this new way opens up for more options, because you can now have multiple directories next to the template yaml containing different templates if you need to, and then point to each of them in separate cookiecutter actions using the url input, ./template1, ./template2 etc.
@freben You can use existing ones, just that you need the slightly awkward {{cookiecutter.name}} folder name in the yaml as well as copy over the values from cookiecutter.json if there are any hardcoded ones. If needed we could add a way to import the values from cookiecutter.json, but tbh the template yaml is already not gonna support pointing to an existing cookiecutter template out of the box as you need to configure the parameters, so that'd probably just be bloat.

I see, thanks for the context @Rugvip. I had the same feeling as @freben initially. I now see we want to make config explicit and have more control over the executable.
I'll follow-up with a PR to accept inputs.copyWithoutRender and inputs.extensions for the fetch:cookiecutter action.


Clean PHP syntax (PSR-2)

Clean files using the PSR-2 coding style (https://www.php-fig.org/psr/psr-2/)

Hello,
I'm not planning to merge this. I consider this library to be in maintainance mode given webauthn happening and won't be merging style and structure changes.


cell-hashing pipeline questions

Hi,
maybe this is not the right place to ask, but I seem to be unable to get a response on the cite-seq website and I would really appreciate if you could comment on the following.
I'm about to do a cell hashing with some 10x libraries.
Can you please confirm that the sequencing cycles configuration of the Hashing libraries can be the same of a 10x library? From your script it seems so, as it will look for the classic coordinates of the CellBarcode(1-16) UMI-(17-26) and so on. (Of course, if it was dropseq beads i'd have to use a different sequencing configuration)
Also, in the preprint of the hashing, in the methods : "Fastq files from the 10x libraries with four distinct barcodes were pooled together and processed using the standard Drop-seq pipeline". If you have fastq to start with it means you basecalled them with the 10x pipeline?
Can I  basecall with the cellranger wrapper or do you suggest any other way? (the dropseq paper suggested a couple of other ways, so I'm really just checking what's the best practice)
and then I have to handle the alignment and following steps exactly as in Dropseq pipeline, right?
Any suggestion would be really welcome! And many thanks for such amazing tool.
Best,
biola

Hi @Hoohm, thanks for your reply,
Sorry if my message was unclear.
The hashing experiment consists of a pool of different samples which were incubated with the different oligo-conjugated antibodies, so this multiplexed pool is loaded into one 10x channel. if I generate >1 different pools, (using >1 channels) each of them will have its separate 10x index(es, as those are 4). My sequencer will produce the basecall files for those n>=1 libraries. From the 10x website:
"The cellranger workflow starts by demultiplexing the Illumina sequencer's base call files (BCLs) for each flowcell directory into FASTQ files. 10x recommends using cellranger mkfastq, a pipeline that wraps Illumina's bcl2fastq and provides a number of convenient features in addition to the features of bcl2fastq"
Hence my question, and I assume the answer is yes, I can do base calling with the 10x wrapper and this will handle the demultiplexing of the library indexes. this is just the "outside" demultiplexing, the one that deconvolutes the libraries produced from n>=1 10x channels .
At this stage, I have 3 fastqs for each library (R1,R2, Index). The 10x pipeline would continue with cellranger count, which does the alignment and the feature counting (producing the gene count matrices).
The goal of this analysis is to produce 1) a gene count matrix and 2) a list of the best possible antibodies which were incubated with the multiplexed samples and will deconvolute back, for each library, the multiple samples. (the hashing demultiplexing)
I'm assuming it wouldn't make a difference if I now produced the count matrix with the 10x pipeline, or if I used these Fastq files as the input to the drop seq pipeline- which is what you did given what I get from the paper? What did you use?
I just don't understand what you mean by This probably refers to the 10x indexes. You should pool them together if you run the data on another pipeline than cell ranger. furthermore, this makes the sentence that I quoted from the paper even more obscure. :/
Once I have a list of good barcodes from the count matrix, whatever the way I generated it, I can use this to speed up the cell-hashing demultiplexing (your script) which requires the same fastqs as before (R1 and R2).
Is my interpretation of the flow correct, or can you give me a list of steps cause the paper doesn't really say much?
thank you!

Hello @bio-la

I can do base calling with the 10x wrapper and this will handle the demultiplexing of the library indexes

Yes, this is fine.
Now I have a question. How many different files do you get for one sample? 3 or 6? You should have 3 files from the mRNA and 3 files from the TAG sequences. Right?

Hi @Hoohm ,
you lost me here. are you talking about fastq files per sample? in a normal scenario it's 3 fastq files. if after the cite-seq script then produces 3 other fastq files (from the R1, R2) it's something that I don't know (and it doesn't seem to me it's in the described outputs) as I didn't sequence the hashing experiment yet. Could you give me more details please?
thanks!

@bio-la  You should separate the anti-oligo library from the cDNA library prior to sequencing as described in the CITE-seq paper 1, figure S1d.
If done that way, you can then index the two libraries with different 10X indices, run them in the same lane, then demultiplex via cellranger mkfastq, resulting in 3 fastqs (R1, R2, index) from the transcriptome and 3 fastqs (R1, R2, index) from the hashtags.
Run the first 3 through cellranger count to get a digital gene-cell expression matrix.  You can then use the cell barcodes from the transcriptome as a whitelist when running R1, R2 from the hashtags through CITE-seq-Count to get a hashtag-cell matrix.  Alternatively, you can use as a whitelist the cellranger-barcodes-737K-august-2016.txt that comes included with every cellranger version.

Hi,
I have a similar question. I am working with a case where the barcodes I want to count are in read 2, where I also have the reads coming from regular mRNA.
My question is:
Is it ok to provide to the CITE-seq count script the fastq files I obtain from running "cellranger mkfastq" (which demultiplexes BCL files into fastq files)? Or should I run bcl2fastq with some specific parameters to obtain the files that the CITE-seq count script expects? To clarify, from "cellranger mkfastq" I am obtaining 3 fastq files (I1, R1 and R2), not 6 files, since both the reads coming from mRNAs and those coming from my barcodes of interest are in the same library.
Thanks,
Oana

@oursu-broad @bio-la, In principle, if you just have a combined 10X library and the 3 fastqs associated with it, I think you should be able to proceed as follows:

Run R1, R2, and I1 through cellranger count.  The hashtags shouldn't align and thus those reads will be excluded; note that will subsequently bring down some metrics in the metrics_summary.csv.

Run R1 and R2 through CITE-seq-Count.  It'll take a long time (due to ~100+ fold more reads depending on your tag loadings), but it should work reasonably well if you specify enough As in the polyA tail portion of your tag regex.
You may also want to use the resulting counts matrix from the previous step to create a cell whitelist.  Alternatively, if you want to run both in parallel, you can use the cellranger barcode whitelist I mentioned above.

thanks @wflynny , i don't know why it was unclear to me that the indexes of the hashing library were the same as a normal 10x, just a separate sample. I think I know what to expect now.

thanks @wflynny!

Hello @wflynny  and @bio-la
The new version is out.
Can you please test it out. Let me know how it works for you.
Regex is now optional and it can deal with tags of different lengths.

@Hoohm @wflynny Hi there, just tested the new version of the script. didn't specify the tag regex as per suggestion (do only if you know what you're doing! nice one:) )
I think I should now use the results to classify the barcode depending on the proportion of reads mapping to the Antibody oligo, and define doublets those with no clear dominant proportion?

sorry, obviously found this https://satijalab.org/seurat/hashing_vignette.html
i was just trying to reinvent the wheel.

This might come up later but not here. This is "just" CITE-seq-count.
I'm going to bo adding CITE-seq-count to dropSeqPipe and there I will add this feature.

@Hoohm Hi, I'm just about to try the CITE-seq-count tool for a non-CITEseq hashing experiment.
In our study the reads look different from normal CITE-seq reads. It can be that the read starts with some
random bases before the actually barcode occurs. Can CITE-seq-count manage that or does it assume that the first base in the read is also the first base of the barcode?
I'd be grateful for some advice
all the best
Jan

@Janosch22 normally not. You could simply trim the first few bases and then run it as usual, but it doesn't handle indels, only mismatches for now.

Hi @Hoohm , Thanks for the script! I am just running my first dataset through the script and would like to know the definition of "bad_struct" and "no_match" in the results file. What qualifies a read to go into those counts?
Kind regards,
Ting

Hi @bio-la
Bad_struct was more of a test for the beginning of the protocol to see if those tags were actually there. The first versions had a polyA tail which we checked for. Reads that didn't have those would get flagged as bad struct.
no_match is a "good" struct but that doesn't fit to any given tag sequences. This could be because the number of mutations/sequencing errors is higher than the given hamming distance threshold.
Hope this clears it up. I'll get to some documentation when I have some spare time to give a bit more details on the outputs.

Hi @Hoohm , Thanks for the quick response. I see, so a count in the bad_struct column has no poly A? I'm trying to work out what proportion of the ADT reads are actually carry overs of cDNA reads from when the two libraries were separated in SPRI size selection.
As an aside, I'm also finding that while the script is mostly running perfectly, a couple of the runs yielded a results table that only consists of bad_struct, no_match and total_reads rows. Does this mean that absolutely no reads aligned to any of the antibody barcodes?
Thanks for your help!
Ting

The bad struct could also come from a constant sequence that is present in all of your tags but is not found in read2. It depends a lot on the dataset and the chemistry.
This flag is actually not present in the latest version as it was confusing and not very useful for standard users. Which version are you running?

I'm closing this now.
Feel free to reopen it if necessary.


Lite server not working

i installed lite-server as the only dependency in my project and tried run it but it is failing. The error displayed in the npm debug log is
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli   'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'dev' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for predev, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users****\Desktop\lite\node_modules.bin;C:\Program Files\nodejs; C:\Program Files\nodejs;C:\Program Files\nodejs;C:\ProgramData\Oracle\Java\javapath;C:\oracle\product\11.2.0\client32;C:\oracle;C:\Program Files\Citrix\System32;C:\Program Files\Citrix\ICAService;C:\Program Files (x86)\Common Files\Citrix\System32;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Users**\AppData\Local\Programs\Git\cmd;C:\Users**\AppData\Roaming\npm
10 verbose lifecycle<EMAIL_ADDRESS>CWD: C:\Users**_\Desktop\lite
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c', 'lite-server' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec dev script
14 verbose stack Error<EMAIL_ADDRESS>dev: lite-server
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:245:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:852:16)
14 verbose stack     at Process.ChildProcess.handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd C:\Users**\Desktop\lite
17 error Windows_NT 6.1.7601
18 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "dev"
19 error node v6.2.1
20 error npm  v3.9.3
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>dev: lite-server
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>dev script 'lite-server'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the lite package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     lite-server
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs lite
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls lite
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
Environment

lite-server version: 2.2.0
nodejs version: 6.2.1
npm version: 3.9.3
OS type/version: windows 7 64-bit

I had to install npm into my project directory ("..\Source\Repos\angular2-get-started") before lite-server would work.  I had previously installed npm/node.js outside of the project directory.  Not sure if this will solve your problem or not, but its something else that you can try as it worked for me.


v4 - Is history and/or react-history necessary/recommended to install using the new react-router or not?

While the current v4 README says $ npm install --save react-router@next, the current external v4 docs says npm install react-router history.
In addition, I saw in the package.json, you have installed history and react-history.
"dependencies": {
    "history": "^4.0.0",
    "path-to-regexp": "^1.5.3",
    "query-string": "4.2.3",
    "react-history": "^0.13.0"
  },

Is history and/or react-history necessary/recommended to install using the new react-router or not?

You don't need to install history yourself. That doc can be updated. A PR would be great!


Change release-amd64 to not use static binaries

Vulnerabilities were found with the static binaries being compiled
against old libraries so we install the ones directly from alpine.
Signed-off-by: Eli Uriegas<EMAIL_ADDRESS>

@seemethere Opened #15 that uses alpine binaries but not the full alpine itself

Closing in favor of #15


Remove support for unified monitoring

Checklist

[ ] The PR has a meaningful title. It will be used to auto generate the
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
[x] PR contains a single logical change (to build a better changelog).
[x] Update the documentation.
[x] Categorize the PR by adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.
[x] Link this PR to related issues or PRs.

This reverts #53 since we've decided that we won't support monitoring stacks based on component-prometheus on OpenShift 4.

Technically, this is a breaking change, but since we're not using the feature anywhere, I'm fine with just treating it as a change.

I plan for a 2.0 release, I could change it to breaking.


Infura endpoints are accessible

https://github.com/thirdweb-dev/react/blob/main/src/constants/chain.ts


Create a granular builder for Rust

This issue will track granular builder for Rust.
TODOs:

[ ] Introduce a new translator that will use cargo-lock underneath but will also perform IFD to get cargo metadata for building packages and write it to the dream-lock.json file. This will allow users to choose the tradeoff; either commit the lockfiles to VCS and have no IFD when building (like crate2nix / cargo2nix), or don't commit and have IFD (but also no longer have to update and commit lockfiles).
[ ] What metadata do we need? We already have a dependency tree for Cargo, albeit it's more like source dependency tree. So we should be able to just store what each crate has as features and also target platform "features", then we can perform feature resolution at build time?
[ ] Introduce a new Rust builder that will be able to build granularly at a crate level. It should use buildRustCrate from nixpkgs. How do we perform feature resolution and target platform resolution?

target platform "features"

have no IFD when building (like crate2nix / cargo2nix)

crate2nix can actually also do IFD and per-crate granular builds. Perhaps dream2nix can reuse that?

have no IFD when building (like crate2nix / cargo2nix)

crate2nix can actually also do IFD and per-crate granular builds. Perhaps dream2nix can reuse that?

I'd rather not use crate2nix for this since it uses a Rust-based tool and does way more IFD than i'd like. But regardless it would probably be possible to use it to make a builder since I believe it's modular enough (probably by only using the tool to generate the Cargo.nix file). It could work with both IFD and no IFD too if you embed the Cargo.nix data inside dream-lock.json. Anyone's welcome to try creating a builder using anything and I'd gladly help with that.


Breaking change with encode and decode?

I've recently checked the documentation and notice that the new functions encode and decode are being promoted as a replace for encodeJson and decodeJson.

No example was given on how to use decode
Can you still use encodeJson and decodeJson? If not, it would be better to deprecate methods and create new ones instead of refactoring as to give people a chance to migrate without braking their code.

Actually, encodeJson and decodeJson are newer than decode and encode, and they aren't replacements, but auxiliary functions

encode and decode produces and consumes Map objects
encodeJson and decodeJson produces and consumes String objects. They are useful if you don't want to invoke the JSON codec from dart:convert, to translate between JSON strings and Map objects.

Ohh, great to hear. I was surprise by the change tho. Thanks!


Optimize gc decon preview

Spectral deconvolution preview now displays feature rt range. Spectra and EICs now have some color as grouped features in scatter plot.

Got some questions.
Also: I noticed the SpectralDeconvolutionGCDialog does not use the ParameterSetupDialogWithPreview. So it doesnt have the show preview checkbox as all the other previews. That would be nice to change.

done


HDFS-14989. Add a 'swapBlockList' operation to Namenode.

This is the first patch HDFS-14989 for the In Place Erasure Coding Feature HDFS-14978.
Work Done
The swapBlockList takes two parameters, a source file and a destination file. This operation swaps the blocks belonging to the source and the destination atomically.
The namespace metadata of interest is the INodeFile class. A file (INodeFile) contains a header composed of PREFERRED_BLOCK_SIZE, BLOCK_LAYOUT_AND_REDUNDANCY and STORAGE_POLICY_ID. In addition, an INodeFile contains a list of blocks (BlockInfo[]). The operation will swap BLOCK_LAYOUT_AND_REDUNDANCY header bits and the block lists. But it will not touch other fields. To avoid complication, this operation will abort if either file is open (isUnderConstruction() == true)
Note : This patch is intentionally not exposing the client side API to use this operation. That will be handled in a separate JIRA where the client side API will involve using this operation to carry out EC conversion.
Added unit tests for the operation as well.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
32m 57s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ HDFS-14978_ec_conversion Compile Tests _

+0 :ok:
mvndep
1m  8s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 56s
HDFS-14978_ec_conversion passed

+1 :green_heart:
compile
17m 41s
HDFS-14978_ec_conversion passed

+1 :green_heart:
checkstyle
2m 54s
HDFS-14978_ec_conversion passed

+1 :green_heart:
mvnsite
2m 37s
HDFS-14978_ec_conversion passed

+1 :green_heart:
shadedclient
20m 42s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m 53s
HDFS-14978_ec_conversion passed

+0 :ok:
spotbugs
3m  1s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
5m  1s
HDFS-14978_ec_conversion passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 55s
the patch passed

+1 :green_heart:
compile
19m 16s
the patch passed

+1 :green_heart:
javac
19m 16s
the patch passed

+1 :green_heart:
checkstyle
2m 51s
the patch passed

+1 :green_heart:
mvnsite
2m 36s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 59s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m 51s
the patch passed

+1 :green_heart:
findbugs
5m 26s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
9m 27s
hadoop-common in the patch passed.

-1 :x:
unit
113m 42s
hadoop-hdfs in the patch failed.

+1 :green_heart:
asflicense
0m 52s
The patch does not generate ASF License warnings.

279m  6s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.namenode.TestAddOverReplicatedStripedBlocks

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1819/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1819

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux c66b3e70ecd9 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
HDFS-14978_ec_conversion / 839e607

Default Java
1.8.0_242

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1819/4/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1819/4/testReport/

Max. process+thread count
3014 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1819/4/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Thank you for the review @ayushtkn.


requiresConfirmation doesn't work on suffixActions in Infolists

Package
filament/filament
Package Version
v3.2.113
Laravel Version
11.23.5
Livewire Version
v3.5.8
PHP Version
8.2.18
Problem description
requiresConfirmation doesn't open the confirmation modal when being used on an action inside an infolist text entry
https://github.com/user-attachments/assets/97d64ee0-96fd-4461-9430-af35758a9369
Expected behavior
it should open the confirmation modal
Steps to reproduce
Clone this repo and try it
https://github.com/saeedvaziry/filament-requires-confirmation-issue/blob/81eecb360beddf2a27f4bb0b09e4ee918b395576/app/Filament/Resources/UserResource/Pages/ViewUser.php#L42
Reproduction repository (issue will be closed if this is not valid)
https://github.com/saeedvaziry/filament-requires-confirmation-issue
Relevant log output
No response

Donate 💰 to fund this issue

You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
100% of the funding will be distributed between the Filament core team to run all aspects of the project.
Thank you in advance for helping us make maintenance sustainable!

@zepfietje any clue where the issue relies? would like to work on a PR.

So far I've seen weird behaviour when using suffixActions.
For example: the modal works fine if the suffixAction is in a form field inside a Table action like the video below:
https://share.cleanshot.com/K8nNkV3K
Also works when the suffixAction is in a form inside a Header Action but a bit weird behaviour (closing the original modal):
https://share.cleanshot.com/67TCC265
But when I use it inside a page (Resource page or normal filament page) it responds with open-modal but no modal opens.

I have a similar problem, but with hintAction inside and infolist.
The problem doesn't seem to be with the click detection on the action button.
It even dispatch an 'open-modal' event.
But the modal doesn't seem to be added to the html, so alpineJs x-on "open-modal" is not included in the webpage.

The problem is that the modals html is not loaded.
I added this line in vendor/filament/infolists/resources/views/component-container.blade.php just before the closing DL
<x-filament-actions::modals />
And it worked

@felabrecque great finding! worked for me

If you are not using the Filament <x-filament::page> component as described in the docs, which contains the modals, you need to pull those in yourself. It is the same if you were creating a custom Livewire component. It should be added to the main page view, not the component-container.blade.php.


Missing PartnerClaimType="tfp" from metadata description

Metadata tables entry: AuthenticationContextReferenceClaimPattern has a incorrect description:
..., add this element <OutputClaim ClaimTypeReferenceId="trustFrameworkPolicy" Required="true" DefaultValue="{policy}" />. Also make sure your policy...
The OutputClaim is missing PartnerClaimType="tfp". Correct line is:
<OutputClaim ClaimTypeReferenceId="trustFrameworkPolicy" Required="true" DefaultValue="{policy}" PartnerClaimType="tfp" />
Related fixes

Fixed in merge: #82408 for document Configure tokens - Azure Active Directory B2C (79614f7a-1783-2aaf-1d91-e13d9f37766a)

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 56f5d39a-868b-52a8-8f8c-3a2c33bf5bc0
Version Independent ID: 177b3d83-838a-7bb2-84df-01d2727c59a9
Content: Define a technical profile for a JWT issuer in a custom policy - Azure AD B2C
Content Source: articles/active-directory-b2c/jwt-issuer-technical-profile.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@sebastiandemel
Thanks for your feedback! We will investigate and update as appropriate.

@sebastiandemel
Thanks for reporting this! you have created a PR for this issue and the changes should go live soon.


Bug: Stuck at a prompt command after first initial download.

After a first initial download, i get stuck a the prompt command. Not accepting anything i type. Return key sends "m"'s
Used Raw Protocol and Telnet. Same issue,

+1
I get odd ANSi characters.