Exclusion filters won't take effect with resource sharing if resource is already processed
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- performance
Research direction
Start by locating the resource-sharing cache and the exclusion-filter handling in the Combinator module. Reproduce the issue with resource sharing enabled, an exclusion filter of ".*", and a previously processed jQuery resource set; done means excluded resources are not reused from the resource share.
Written by the indexing model from the issue text.
Description
@Piedone created on Jul 3, 2014:
https://combinator.codeplex.com/workitem/60
With resource sharing enabled if you set up exclusion filters to exclude a set of resources then if that set was already processed and is saved to the resource share than exclusion filters won't take effect and the saved resource will be used.
E.g. set exclusion filter to ".*". If jQuery (let's assume there's a set of resources that solely consists of jQuery) was already processed and is saved to the resource share than it will be taken, despite the exclusion filter.
- Dominant language
- C#
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Lombiq/Combinator
-
File is being used by another process (COLI-1216)May be free again @aracsibalint claimed this 1050 days ago, and no pull request is open. Open
Lombiq/Combinator#22 · 1 comment · 1 assignee ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Lombiq/Combinator#17 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Lombiq/Combinator#15 · 19 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
Lombiq/Combinator#10 · 11 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Lombiq/Combinator#8 ·
All issues in Lombiq/Combinator
Similar issues
-
bug 優先: 低
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
.NET area: storage bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Larson-Logan/medal-sync#61 ·
Maintainers usually reply within 1 day
-
area-ai bug untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
dotnet/extensions#7893 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100