text:
Project Console: "View Companies" table error.

Summary
For some projects, the "View companies" table does not load and an error can be seen in the console. This is happening with specifically with CNCF and with OpenColorIO, but not all projects have this issue.
Background

Go to project.lfcla.com
Click on CNCF or ASWF (OpenColorIO CLA group)
Click on "View Companies"
See error

Screenshots

https://api.lfcla.com/v3/signatures/project/d8cead54-92b7-48c5-a2c8-b1e295e8f7f1?pageSize=100&signatureType=ccla
Environment
PROD
Additional Context

@dealako @WillsonHG @nirupamav above issue not reproducible on Dev Environment but as per the error message in screenshot, issue is in trim function where company name may not come from API. I will write trim pipe for this hope it will solve the issue on Production.

@WillsonHG
Could you please check this in PROD as I do not have access to PROD
I tested in DEV env for CNCF CLA Group and observed that it is working as expected without any errors

This looks to be resolved in production.

authors: WillsonHG amolsontakke3576 nirupamav

repo: communitybridge/easycla


text:
User is able to create CLA Group and generate templates when CLA type (CCLA and ICLA) is not checked

Background

Launch Project Management Console url in dev environment
Login as Project Manager
Click on a project
Click ADD CLA GROUP button
CLA Group popup window is displayed
Enter CLA Group name
Do not check the check boxes for CCLA and ICLA

Issue 1
8. Observed user is able to create CLA group when the CLA type is not selected

Issue 2
9. Also observed that user is able to generate CCLA and ICLA templates when CCLA and ICLA checkboxes are not checked while creating CLA Group

Let's update this logic to allow Project Managers to set/unset these checkboxes as they see fit.  Let's confirm with @swinslow first... We have a long history of debate on this topic.

@dealako Happy to discuss this during the call later today.

Discussed this issue with @swinslow on the weekly EasyCLA Sync meeting:

Verified and observed that the issue is fixed
Observed that the error message "Please select atleast one checkbox." is displayed and user is not able to Save the CLA Group if none of the CCLA type check boxes are checked
Verified in Chrome, Firefox and IE
While Adding CLA Group

While Updating/Editing CLA Group

Also Verified below behavior

Corporate CLA checkbox IS selected and - Individual CLA checkbox IS NOT selected - 'Contributors under Corporate CLA must also sign individual CLA' is disabled and NOT checked.

Corporate CLA checkbox IS NOT selected and - Individual CLA checkbox IS selected - 'Contributors under Corporate CLA must also sign individual CLA' is disabled and NOT checked.

Both Corporate CLA checkbox and Individual CLA checkbox are checked - the 'Contributors under Corporate CLA must also sign individual CLA' is enabled and Project Managers can check/uncheck this checkbox.

source: gharchive/issue

authors: dealako nirupamav swinslow

license: MIT

license_type: permissive

license_source: github-api


text:
make search on /internal/sic-code-search/search

Short description outlining key changes/additions
Altered search url to match terraform config in locals.tf file
JIRA Ticket Number
Type of change

[x] Bug fix
[ ] New feature
[ ] Breaking change

Pull request checklist

[ ] I have added unit tests for new code that I have added
[ ] I have added/updated functional tests where appropriate
[ ] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!

source: gharchive/pull-request

authors: SteveHicksCH ch-code-analysis

repo: companieshouse/sic-code-api


text:
Add from_std methods

Allow to create compio stream objects from std types

thanks! could also make new release for compio-net?

could also make new release for compio-net?

Published.

thanks!

repo: compio-rs/compio


text:
CI: Remove swift-driver from Windows builds

Since swift-driver has no Windows implementation so far, remove it from Windows builds to avoid spoiling the toolchain.

This change is

You cannot remove the checkout step, it breaks the pipelines.
I dont understand the assertion that swift-driver doesnt have a windows implementation.  It absolutely does - otherwise you couldnt build/use swift-package-manager.
Could you please explain what the change is intended to do?

@stevapple - these are now required due to packaging swift-package-manager into the toolchain.  Is there anything that you hope to change here or should this be closed?

Nope. This PR is totally a mistake. I’ll close it now, sorry for troubling you.

No worries, just wanted to make sure that if there was an issue we figured out what was happening.

authors: compnerd stevapple

repo: compnerd/swift-build


text:
RuntimeError for networks

When I run docker run --rm -it -v $(pwd):/in wst24365888/compose-viz -m svg docker-compose.yml
On a docker-compose that contain:
networks:
  ...
  traefik-public:
    external: true

I get the following RuntimeError
RuntimeError: Error parsing file 'docker-compose.yml': 1 validation error for ComposeSpecification
networks -> traefik-public -> external
  value is not a valid dict (type=type_error.dict)
[8] Failed to execute script '__main__' due to unhandled exception!

Thanks, we will fix this in the next version!

repo: compose-viz/compose-viz


text:
Add npm-asset and bower-asset types for frontend libraries

There is a very popular composer repo called https://asset-packagist.org/
to install a library from npmjs.org or bower.io.
To be able to install it in custom path a plugin is needed "oomphinc/composer-installers-extender".
I think it will be better if this two types where recognized in this repo as an "official" type.

I agree, it will be useful.

+1. This would be very helpful!

IMO this is a bad idea and I don't really want to encourage it. Frontend deps should be installed via npm/yarn, not cobbled up together via Composer.

authors: Seldaek espurnes phenaproxima rodrigoaguilera

repo: composer/installers

license: mit

license_source: bigquery


text:
Investigate faster SAM implementations and consider changing the default model

I know there are a whole bunch of projects that popped up after segment-anything was released, but another one we might like to look at and potentially include is FastSAM: https://github.com/CASIA-IVA-Lab/FastSAM
The model checkpoints are linked from the README here: https://github.com/CASIA-IVA-Lab/FastSAM#model-checkpoints
Cross-reference: https://github.com/computational-cell-analytics/micro-sam/pull/174

I changed the title to indicate the broader scope. As mentioned, a student will start to work on this mid of October, and @anwai98 and me are already working on better benchmarks for the models (that reflect interactive segmentation quality).
See this doc for an overview of our (preliminary) plans for evaluating the faster models.

Just came across another potentially interesting project: https://github.com/SysCV/sam-hq
I haven't looked at this yet, but it might be worth figuring out if it could be useful for microscopy datasets (which are often high resolution images with a lot of fine-grained detail).

I tried TinySAM (the method from my previous reply), but it does not work for our data; the bounding box prompt is somehow broken.

However, we now have MobileSAM, which also uses a vit_tiny backbone, integrated nicely. Will summarize this soon.

Just as a follow up here:

We investigated different vit-tiny implementations, including all the ones from the links above. It turns out the original one from the mobile sam publication works best for our use-cases.
We looked into FastSAM (using a conv backbone), but integrating their code would be a bit more difficult, so we will not do this in the short term.
We also did much more thorough investigations regarding different models (both the original models and our finetuned ones).

Based on this I think the best strategy is:

Setting vit_l as the default model. (It's faster than vit_h without any penalty in performance, or even slightly better performance).
Giving a concise recommendation for the best model for a given situation (i.e. when to use our finetuned models).
We will go ahead with this for 0.5 (goal is to get this out within the next 2 weeks), but it's also pending modelzoo integration (because we will upload our finetuned models there), see #227

For the next release we will go with the strategy outlined above, so I removed this issue from the milestone.
Will leave it open though for future discussions.

For 3D, SAM2 seems promising:
https://https//arxiv.org/abs/2408.00756

Thanks @psobolewskiPhD , we are already looking into SAM2 :).

repo: computational-cell-analytics/micro-sam