Feature request - Add coverage analysis for Jest

Summary
Is it possible to add coverage analysis, to provide a better experience on mutation testing with jest ?
For now, stryker-jest-runner create mutants on every single part of code, even if statement or branch are not reach.
I would like to add my contribution to stryker, to help bigger application to use stryker, without to add mutation on unreachable statement during initial test run.
Stryker config

module.exports = function(config) {
  config.set({
    testRunner: "jest",
    mutator: "javascript",
    transpilers: [],
    reporter: ["html", "clear-text", "progress"],
    coverageAnalysis: "all",
    mutate: ["src/**/*.js"]
  });
};

Stryker environment

    "jest": "^23.2.0",
    "stryker": "^0.24.1",
    "stryker-api": "^0.17.2",
    "stryker-html-reporter": "^0.14.2",
    "stryker-javascript-mutator": "^0.7.2",
    "stryker-jest-runner": "^0.7.0"

Your Environment

software
version(s)

node
10.4

npm
6.1

Operating System
OSX

@Tobino thanks for creating this issue.
We've chatted about this on Gitter, I'll include the explanation I gave there here as a reference for anyone interested.
You've shown interest to help us crack this nut. Thanks a lot in advance! I've created a branch ("965-jest-coverage-analysis") and added one integration test ('Integration test for Strykers Jest runner should be able to retrieve code coverage results'). It uses a reference jest test project located in the testResources: packages/stryker-jest-runner/testResources/exampleInstrumentedProject. This reference project represents the state that a project will be in after Stryker intrumented the code, when coverageAnalysis is "all",  at the start of the initial test run (using istanbul). The tests expects there to be a coverage result (which there isn't at the moment). I've also added a line of code that retrieves the __coverage__ object from global scope in the JestTestRunner (packages\stryker-jest-runner\src\JestTestRunner.ts). The __coverage__ variable is missing from global scope because it is cleaned after the tests by Jest.
This is the problem we're currently facing. This should be a good starting place to help you on you're journey.
My remark from Gitter (as a reference):

@Tobino setups where the test runner does the transpiling (i.e. jest, or karma with preprocessors) will not work. Istanbul simply does not support anything else but javascript.
If you configure a transpiler in the transpilers array, it can work if the transpiler produces sourcemaps (i.e. only stryker-typescript a.t.m.). Stryker will instrument the resulting js code from the transpiler output and use the source maps to correlate the mutants. To support webpack, we need the stryker-webpack-transpiler to support producing sourcemaps as well (which can be done, simply didn't have time yet).
If you than use a test runner that supports reporting of coverage result (i.e. stryker-karma-runner, stryker-mocha-runner or stryker-jasmine-runner), coverageAnalysis: "all" can be supported. This is the main problem with jest, I'll come back to that later.
If you than also use a test framework that supports test filtering (i.e. stryker-mocha-framework or stryker-jasmine) you can support the coverageAnalysis: "perTest".
This is a complex setup, and for the mid-term we're thinking of a new way to instrumenting code with babel7 (still in beta), as it supports parsing of javascript, typescript and flow natively (pretty awesome). That way we can instrument the source code and directy correlate them to the mutants. No need for source map support by transpilers, and we can support testrunners that transpile code themselfs (i.e. jest and karma with preprocessors).
Even with the new setup, we need to have coverage reporting from the jest runner (be it istanbul coverage, or future stryker instrumented coverage).  We need a way for the stryker-jest-runner to report the global object: __coverage__. The problem there is that jest works really hard to not make you use global variables. If you want to help, please create an issue for it over at stryker-jest-runner and I'll explain further what is needed.

Hello,
It seems that Jest deep clone coverage on each testSuite, and push this result on coverage field. I guess coverage is the result of each worker from Jest, and I don't know if Stryker is able to use this format directly or a merge of coverage with istanbul-lib-coverage ?
PR: https://github.com/stryker-mutator/stryker/pull/1003

Thanks for your update, I will take a look next week. Just to be clear, is Jest itself also instrumenting the code?

I think Jest use istanbulJs to instrument the code, but I am not sure if it's the right answer.

Yeah, that isn't what we want. We now use istanbul to instrument the code our selves before the initial test run (based on the coverageAnalysis setting). However, this could change in the future our own instrumentation.
We're actually looking for a way to mark a global variable as "don't touch this one" in jest. Do you know if that's possible? I have looked at this problem before, but usually was looking on the global scope. I haven't thought to look at testResults array, so that's still hopeful...

I think testResult.coverageis untouch by jest, and then coverage report is generate using this field.  Maybe there is a chance to improve stryker.

I believe this is implemented with this PR: https://github.com/stryker-mutator/stryker/pull/1235
I'm closing this issue for now. If the problem is still there, let us know!

@simondel I don't think that this PR is related to the issue. For example, I have a lot of tests for my Vue component. And even with --findRelatedTests Jest will run all of this tests. So, coverage analysis is still required

I believe this is implemented with this PR: #1235
I'm closing this issue for now. If the problem is still there, let us know!

I agree with @Djaler , this issue is related for Coverage analysis for Jest, this PR is for fixing JestTestRunner. I believe this should be reopened, or if we're wrong the Readme at least should be updated here.


2.46 to master

See detailed description in the commit message.

pls wait with merge until i test ccmv2jumpgate repair for HA DL


I can specify a referenced global { Message, Error, Signal } with an event definition template

Event definitions may reference global shared entities, namely bpmn:Message, bpmn:Signal and bpmn:Error elements. As part of an event definition, configured via a element template (https://github.com/camunda/camunda-modeler/issues/343) a user should be able to create and wire these globale entities.
To be Defined

What are the relevant properties that a user should be able to define
What are the properties that should be fixed by the element template creator?
How to template (nested scoped binding)?

Relevant Entities to be Templated

[ ] bpmn:Message(name) referenced via bpmn:MessageEventDefinition#messageRef
[ ] bpmn:Signal(name) referenced via bpmn:SignalEventDefinition#signalRef
[x] bpmn:Error(name, errorCode) referenced via bpmn:ErrorEventDefinitionerrorRef

Context
https://jira.camunda.com/browse/SUPPORT-11968

Per camunda forum topic (https://forum.camunda.org/t/element-template-support-for-message-throw-catch-events/30104) advise, adding the details here.
We have a requirement to create multiple element-templates around the message (throw and catch) events (including start/intermediate and end), so that our business partners could use the templates and modify the workflow.
Can we please prioritize this and have this feature as part of camunda-modeler?
Thanks in advance!

@sovanmishra Thanks for your bump on this issue. If you are a Camunda Enterprise user, please file this issue as a support ticket, too.

Any news on this?


Fire extinguisher/spray refactor

About the PR

Fire extinguisher spray properly applies touch reactions
Fire extinguishers can now be refilled from anything that is drainable, not just reagent tanks (yes, beakers too)
Fixes bug where safety wouldn't stop you from spraying
ECSes fire extinguisher + spray

https://user-images.githubusercontent.com/19853115/151109115-5a117e52-ff73-4943-9aef-77b90a92ce43.mp4
:cl:

add: Fire extinguisher spray now applies touch reactions.
tweak: Fire extinguishers can be refilled from any source now.

cries in starting fires with a tampered fire extinguisher and a candle


Odd bug when updating to master

Getting build errors that default isn't implemented for AccountId causing a myriad of other errors. Any idea why this occurs when updating to the master branch?
161 |     #[pallet::storage]
    |               ^^^^^^^ the trait `std::default::Default` is not implemented for `<T as frame_system::Config>::AccountId`

This PR is the reason: https://github.com/paritytech/substrate/pull/10403
TLDR: AccountId should not have a default value, so it was removed.

So the recommendation is convert all instantiations to Option<T::AccountId> in the pallet's storage?

Many things were updated in that PR, just follow those examples. In some cases Option<T::AccountId> might make sense, in other cases something different, all depends on the use case.


Request for Textual Annotations File for Applying LangCell to New Datasets

Hello,
First, thank you for your excellent work on LangCell. We are currently working on applying LangCell to new datasets for cell annotation. To proceed, we require the textual annotations file, which appears to be missing from the provided resources.
Could you please provide the necessary textual annotations file or guide us on how to generate or obtain it? Any assistance or direction you can provide would be greatly appreciated.
Thank you for your time and help.

Thank you for your interest in LangCell! We have now uploaded the OBO Foundry file "obo.json" here, which contains textual descriptions of common cell identities. You can use these as examples to write textual descriptions for new cell types.


Error on helm init: error executing access token command "/google/google-cloud-sdk/bin/gcloud ": exit status 2

Hi, helm init fails with error:
Error: error installing: Post https://<IP_ADDRESS>/apis/extensions/v1beta1/namespaces/kube-system/deployments: error executing access token command "/google/google-cloud-sdk/bin/gcloud ": exit status 2
Patform: Google Cloud Platform, Cluster version is 1.6.0, Environment is Google Cloud Shell, Helm version is 2.3.1.
After manual tiller installation helm version shows: Error: cannot connect to Tiller.
kubectl version shows:
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.0", GitCommit:"fff5156092b56e6bd60fff75aad4dc9de6b6ef37", GitTreeState:"clean", BuildDate:"2017-03-28T16:36:33Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.0", GitCommit:"fff5156092b56e6bd60fff75aad4dc9de6b6ef37", GitTreeState:"clean", BuildDate:"2017-03-28T16:24:30Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

Thanks in advance
Gus

Is this a duplicated of #2249?
It seems that GKE recently switched to expiring tokens. See that issue for details.

This is preventing me from upgrading to the bugfix release. I'm unable to connect to tiller.

This is preventing me from upgrading to the bugfix release. I'm unable to connect to tiller.

I have the same issue..

did you both try the instructions in https://github.com/kubernetes/helm/issues/2249#issuecomment-294793552 like @technosophos pointed out, or is there something else going on?

@bacongobbler I've tried both of those. Haven't really had the time to dig and and get any debugging tho...

I believe you need to run gcloud container clusters get-credentials <cluster_name> again after setting the env variable or setting.

@Draiken 🙈 Oh wow. Thank you for that. Figured I had tried doing that already. Works for me now! 🙊

@Draiken's instructions worked, but in my case I had to exit kubectl proxy first before it worked.

@Draiken
It doesn't work for me even on new cluster and new Cloud shell.
$ terraform apply
$ gcloud config set compute/zone <zone> && gcloud container clusters get-credentials <project_name>
$ curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > get_helm.sh
$ chmod 700 get_helm.sh
$ ./get_helm.sh
gcloud container clusters get-credentials <project_name>
$ helm init
Error: error installing: Post https://<ip>/apis/extensions/v1beta1/namespaces/kube-system/deployments: error executing access token command "/google/google-cloud-sdk/bin/gcloud ": exit status 2
$ sudo helm init
Error: error installing: Post http://localhost:8080/apis/extensions/v1beta1/namespaces/kube-system/deployments: dial tcp [::1]:8080: getsockopt: connection refused

Can somebody test it on a new cluster please?

closing as resolved.

@Draiken env or setup you referred to resembles the following screenshot, doesn't it?


Update exchange-online-powershell-v2.md

Docs Build status updates of commit 5309140:
:clock10: Full build: the average full build time is 12 min(s) 10 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 5309140:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 99d8b15:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 8f6ad97:
:clock10: Full build: the average full build time is 12 min(s) 10 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 8f6ad97:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 3758702:
:clock10: Full build: the average full build time is 12 min(s) 10 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 3758702:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit ad96495:
:clock10: Full build: the average full build time is 12 min(s) 12 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit ad96495:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[OSGi] Streamline ManagementContext injection in REST resources

Makes ManagementContextProvider the single source of ManagementContext in REST code, abstracting away the different methods for accessing it.
Discussed in https://github.com/apache/brooklyn-server/pull/34
Depends on #41

nice job.  a few comments but nothing which needs addressed.


Add instructions for installing via scoop on Windows

Hi @roboll, do you mind having a look at this?
I think having a scoop installer makes life much easier for Windows users :wink:

@nightscape Hey! Thanks for sending this.
Two things I'm afraid before merging this is that I'm not aware of to whom I should ask for updating the scoop pkg when new versions of helmfile are released. Would you mind becoming the one?

The cool thing about scoop is that it automatically updates the package definitions by checking the Github release page:
https://github.com/lukesampson/scoop-extras/blob/master/helmfile.json#L22-L33
In case you should move from Github to Gitlab or use different file names for the executables I'll happily make the corresponding changes 😃


Add extra default Parquet serialisers

Add extra default Parquet serialisers for common classes used as identifiers or properties, such as:

TypeSubTypeValue
Arrays
Sets
other sketches

Merged into develop.


sqlite build error

新手指教
Describe the bug
Caused by: java.lang.Exception: No native library is found for os.name=Mac and os.arch=aarch64. path=/org/sqlite/native/Mac/aarch64
at org.sqlite.SQLiteJDBCLoader.loadSQLiteNativeLibrary(SQLiteJDBCLoader.java:333)
at org.sqlite.SQLiteJDBCLoader.initialize(SQLiteJDBCLoader.java:64)
at androidx.room.verifier.DatabaseVerifier.(DatabaseVerifier.kt:71)
... 50 more

查出的資訊似乎是跟m1有衝突，但不知道該怎麼修

It seems to be Room bug on Mac M1. Can you try to fix this on your Mac to upgrade Room verions to 2.4.0 and above since I don't have Mac machine with M1 chip. If this can be fixed by upgrading the Room version, feel free to submit PR. That would be nice :)
Source: https://stackoverflow.com/a/69142381/2279285

Hi, did you fix this issue from the link I provided above?

I will close this issue since there is no further update information, feel free to re-open if you still have some problem.

yes,it's fixed thank you


Report fields - The report field after deleted offline is still clickable

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Found when validating  https://github.com/Expensify/App/pull/44493
Version Number: 9.0.5-3
Reproducible in staging?: y
Reproducible in production?: no, this is new feature
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com
Go to workspace settings > Report fields (Enable on More features if not yet).
Add any type of report field.
Go offline.
Click on the report field.
Click Delete.
Delete the field.
Click on the deleted report field.

Expected Result:
The report field after deleted offline should no longer be clickable.
Actual Result:
The report field after deleted offline is still clickable.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/38435837/ef989d7d-2a63-4a86-b4ef-0b84e2f48cfd

View all open jobs on GitHub

@strepanier03 FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #wave-collect - Release 1

Taking to over as I work on the project, this is still behind beta so not a blocker
@waterim @rezkiy37 who can take this?

Hello, Im Artem from Callstack and this one will addressed here

PR reviewed and merged


Perf: Reuse AST passed from bultin:swc_loader to avoid double parse

span is not valid after transformation
currrently Rspack will do double parse for all file processed by builtin:swc-loader, the reason Rspack do double parse is caused by swc transform will make the origin span invalid which cause it's bad for following dependency generation

before transformed by builtin:swc-loader

import { b }  from './b';
const  a = b;  // now AstNode('b') span is 37-38

after transformed by builtin:swc-loader

import { b }  from './b';
var a = b; // the span in ast is still 37-38 but after codegen the valid span is actually 34-35

span can be fixed by srcmapbuf generated by codegen
so the span in ASTNode is not valid after transformation, but we can fix the span use src_map generated by emitter, the src_map contains the right mapping from span in ast to span after codegen
https://github.com/web-infra-dev/rspack/blob/9112e35f97eeac430691e15c0305763fec56e890/crates/rspack_plugin_javascript/src/ast/stringify.rs#L79-L84
we fix ast span using visit_mut_span in SpanFixerVisitor
struct SpanFixerVisitor {
   src_map_buf: SrcMapBuf
};
impl VisitMut for SpanFixerVisitor {
   fn visit_mut_span(&mut self, span: &mut Span){
             let codegen_span = self.src_map_buf.get(span);
             span.start = codegen_span.start;
             span.end = codegen_span.end;
   }
}

ast invalidation
we should mark the ast dirty | invalid, if the code is modified by following loader
reuse span in module.build
if the AST contains the valid span, then parse can reuse ast passing from builtin:swc-loader, no need to do double parse in module.build
https://github.com/web-infra-dev/rspack/blob/9112e35f97eeac430691e15c0305763fec56e890/crates/rspack_core/src/normal_module.rs#L542

Except fix the span, we need pass ast from swc_loader to JavaScriptParserAndGenerator.
We can use additional_data: anymap::Map<dyn CloneAny + Send + Sync> to pass ast.
// swc_loader
fn run(loader_context) {
 ....
 let mut additional_data = Default::default();
 additional_data.insert(ast);

 loader_context.finish((code, map, additional_data))
}

then get ast from additional_data
// parser_and_generator
fn parse(parse_context) {
   let ParseContext { additional_data } = parse_context;

   let ast = additional_data.get::<SwcAst>();

   ....
}

We can use additional_data: anymap::Map<dyn CloneAny + Send + Sync> to pass ast.

Voting for this solution.
Given the status-quo, AdditionalData is replaced by each loader, so there's no need to introduce the mental model to even invalidating the AST.

Actually, we can't get mapping that from source span to transformed span using src_map_buf.
The src_map_buf is used for generate source_map, It only maps a portion of the span's start or end positions to the corresponding source line and column numbers.
We need other way.

It would set some zero-span node.

Is this a bug of swc ?

It would set some zero-span node.

Is this a bug of swc ?

I don't think, swc can't get the span information util ast generate actual code.

Oh I see, it uses DUMMY_SP everywhere to generate extra AST during transform

I do some simple bench test. It's not too optimistic to reuse ast now.
I run rspack-ecosystem-benchmark first job 10000_development-mode in my macbook(M1 Pro 32G).
The result bellow:

Case
median
mean

Not reuse ast(parse twice)
10.6s
9.96s

Reuse ast and fix span info
9.37s
9.9s

Only reuse ast not fix span info
9.11s
9.02s

I guess that fix span info need rewrite almost all ast node span status. It's will cost many time.
I do not think we should reuse ast now. We like webpack take transformer as loader.
We handle the js code in string layer. In the future, if we can handle js code in ast layer, reuse ast is more useful.


Feature request: Add ability to categorize installed extensions

At the moment all installed extensions are listed in alphabetical order. I find myself scrolling through the list to enable/disable some extensions. It would be nice to have them in categories – something like:

Themes
Tools
Language based etc.

/duplicate


IRGen: Weakly link symbols for unavailable declarations

When computing linkage, the compiler would treat unavailable declarations as if they were "always available" if they also lack an introduced: version:
// Library
@available(macOS, unavailable)
public func foo() {
  // …
}

// Client
import Library

@available(macOS, unavailable)
func bar() {
  // Even though foo() and bar() are unavalable on macOS the compiler still
  // strongly links foo().
  foo()
}

This created an unnecessary dependency between libraries and their clients and also can interfere with back deployment, since unavailable declarations may not be present in a library on all OS versions. Developers could work around these
issues by conditionally compiling the code that references an unavailable declaration, but they shouldn't have to given that unavailable code is meant to be provably unreachable at runtime. Additionally, in the future it could improve library code size if we allowed the compiler to strip unavailable declarations from a binary completely.
Resolves rdar://106673713

@swift-ci please test

I tweaked this a bit to allow unavailable declarations with an introduced: version to be treated as ABI and linked accordingly (e.g. Float16 https://github.com/apple/swift/pull/35997/).

@swift-ci please test

@swift-ci please test

I believe that this is causing a regression for Windows:
DateComponentsFormatter.swift.obj : fatal error LNK1227: conflicting weak extern definition for '$s10Foundation9FormatterC11objectValueyypSgSSKF'.  New default '.weak.$s10Foundation9FormatterC11objectValueyypSgSSKF.default.$s10Foundation23DateComponentsFormatterC10UnitsStyleO8rawValueAESgSi_tcfC' conflicts with old default '.weak.$s10Foundation9FormatterC11objectValueyypSgSSKF.default.$s10Foundation18ByteCountFormatterC5UnitsV8rawValueSuvg' in ByteCountFormatter.swift.obj

https://ci-external.swift.org/job/oss-swift-windows-toolchain-x86_64-vs2019/2829/console


Create grouping classes via hallmark phenotypes

From @cmungall on July 24, 2015 23:54
From @mellybelly on March 6, 2015 19:6
It would be great if we could autopopulate any missing intermediate nodes based upon anatomical classification of hallmark phenotypes. Basically, for 'Enlarged hippocampus', you know that hippocampal formation is part of 'pallium' and 'cerebral cortex'. If Enlarged hippocampus is a hallmark for a disease (for some reason in our site I don't see any diseases with mophological abnormality of the hippocampus...hm) then we'd autoclassify that disease under the seeded intermediate nodes 'abnormal pallium phenotype' and 'abnormal cerebral cortex phenotype' or some such.
Copied from original issue: monarch-initiative/human-disease-ontology#7
Copied from original issue: monarch-initiative/monarch-disease-ontology-RETIRED#11

@mellybelly is this still something that you want?

closing, please reopen if needed


Understanding output columns

Hello! I was able to get the tool to work and have analyzed two Hugo et al., 2016 patients. I am reviewing the outputs from frequency_stage3_verbosity1_uid_gene_symbol_coord_mean_mle.txt and have a quick question regarding what each column is describing.
For reference, I am using GATK's Homo_sapiens.assembly38.fasta reference fasta for alignment and GENCODE's v37, v43, and v45 GTFs to determine exonic coordinates.
With that in mind, here is a line from the file:
EKDTPRYSF,ENSG00000004846:E15.1-E16.1   ['HugoLo_IPRES_2016-Pt01-ar-279.Aligned.sortedByCoord.out.bed', 'HugoLo_IPRES_2016-Pt02-ar-280.Aligned.sortedByCoord.out.bed']  2   ABCB5   chr7:20658676-20659066(+)   0.5102824568748474  0.9999946440084598

The peptide of interest is EKDTPRYSF which is from gene ENSG00000004846. The chr7:20658676-20659066(+) should be genomic coordinates containing the peptide of interest.
If I pull chr7:20658676-20659066 from Homo_sapiens.assembly38.fa and then translate it through ExPASy's web service, the peptide of interest, EKDTPRYSF doesn't appear to be present:
samtools faidx Homo_sapiens.assembly38.no_ebv.fa chr7:20658676-20659066
>chr7:20658676-20659066
GGTAAGTGAGCAGAAACGTTTCTTATTTCCATACTCCTGGTTCATTATTGTTTTGAAGTA
CAAGAAAGTATAGATCTGTAATAGATTACTCAAGTTGAGAGCCCTCTTAAGGTATAAAGG
CAGGATGTTAATCCACTGAGAACTTACGTGATGGCTATAGGAAGTGGTTTAGAGGACAGA
AGGAGATGCTGTGGTTGGTTGGTGTAAAAATATATACATGAGGCTGATACACAAGCAATC
ATCCAGTCTATACCTCCATTCCAAGTGGTTTGCACTTTCCACCTCCCTAGAGTGGCCCAC
CACTATCATCACTATTATAACCATGCCCACCCTTTGCTTCTTCTACATACACCTGTGGGA
TTCTCTTCTCTGACCACTTTTCTTCTTTAGG

Can you please help me understand these columns so I may better understand my results?
Thanks,
Steven P. Vensko II

Hi @spvensko,
Glad the tool ran smoothly on your end, the chromsome coordinate is the 5' splicing site and 3' splicing site, so the junction jump from 20658676 to 2065066, instead of taking the prat in between, if that makes sense.
Please see below screenshot for the peptide generated from this junction:

Best,
Frank

Thank you for the excellent explanation!
Another oddity I noticed:
AADVSGLPL,ENSG00000110427:E1.1-I1.1     ['HugoLo_IPRES_2016-Pt01-ar-279.Aligned.sortedByCoord.out.bed'] 1       KIAA1549L       chr11:33542146-33542147(+)      0.03866191580891609     0.9999941348374569
In this case, the 5' and 3' splice sites are neighboring bases, correct?
I checked the SJ.out.tab file, but wasn't able to find any evidence for this junction:
chr11   33531115    33533544    2   2   1   1   0   43
chr11   33542147    33542920    1   1   1   2   1   22
chr11   33542147    33544766    1   1   1   11  0   43
chr11   33544337    33544766    1   1   1   18  0   47

Hi @spvensko,
Thanks for bringing this up, this is an intron retention (intron 1), meaning the whole intron 1 is not properly excised but retained in the transcript, resulting in a read-through. That's why this is only one base difference.
It won't be reported in STAR SJ.out.tab, as far as I understand, only reports junctions but not intron retention. In our Supplementary figure 1, we illustrated how we define the Exon ID and segment ID (the question you asked), I also pasted below hoping that can clarify some confusion:

In our Supplementary Figure 2, we showed a benchmark my lab mate conducted before for intron retention prediction against other tools using simulated data.
Let me know if I can help answering any question!
Best,
Frank


add a GEOS-CF background file for testing in fv3-jedi

Description
add a GEOS-CF background file for testing in fv3-jedi
Dependencies
https://github.com/JCSDA-internal/fv3-jedi/pull/405
Impact
fv3-jedi

https://github.com/JCSDA-internal/fv3-jedi/pull/405 was merged in before this was approved/merged... develop is currently broken

Thank you @CoryMartin-NOAA!


Where's the INSTALL file?

In project README file:

There is additional information in the INSTALL and FEATURES files ...

But where is this INSTALL file? I cannot find it in this github repo.

There is none, and it has been asked before
https://github.com/trusteddomainproject/OpenARC/issues/10#issuecomment-472957709

No way to install it then.

No way to install it then.

This is incorrect

Anyone has a tutorial/guide to install it?

Anyone has a tutorial/guide to install it?

Currently at work and can't contribute much. Basically configure, make, make install and then modify the documents which, if initial configuration was done correctly, should be in /etc

I'll be reviewing the PR, and will merge this into the develop branch for testing and integration into the next release.

I found a build script for Ubuntu/Debian here:
https://github.com/ValiMail/OpenARCDev/blob/master/bootstrap.sh


Can not get gmail to work, thus breaking notifications

Description
Hello,
I apologize because I am not very code-savvy.
I am entering my gmail password and email correctly, but Google keeps blocking the bot from having access to my email. I approved the log-in, but it still does not work correctly.
I keep getting the following error when testing:
[5:40:35 PM] error :: Invalid login: 535-5.7.8 Username and Password not accepted. Learn more at
535 5.7.8  https://support.google.com/mail/?p=BadCredentials 17sm950114oth.70 - gsmtp
[5:40:35 PM] error :: Invalid login: 535-5.7.8 Username and Password not accepted. Learn more at
535 5.7.8  https://support.google.com/mail/?p=BadCredentials w12sm8423824oow.22 - gsmtp

I do not have MAP turned on.
Any advice would be great.
Possible solution

Are you using 2FA on your gmail account?

Are you using 2FA on your gmail account?

Nope/

Are you positive your email and password are right?
<EMAIL_ADDRESS>EMAIL_PASSWORD="mypassword"

Both of them are in quotes?  This functionality works, so it's on your end.

Are you positive your email and password are right?
<EMAIL_ADDRESS>EMAIL_PASSWORD="mypassword"

Both of them are in quotes? This functionality works, so it's on your end.

Extremely positive.

Are you positive your email and password are right?
<EMAIL_ADDRESS>EMAIL_PASSWORD="mypassword"

Both of them are in quotes? This functionality works, so it's on your end.

Believe me, I wouldn't be posting if it was that simple. I am just at a loss. Like I said, Google was blocking it, but once I whitelisted it, nothing happened still.

Try making a throwaway Gmail.  The problem isn't within the Gmail function.  If Google blocked it at some point I would check to make sure it's not automatically blocking attempts or something.

Try making a throwaway Gmail. The problem isn't within the Gmail function. If Google blocked it at some point I would check to make sure it's not automatically blocking attempts or something.

Tried that too.

Try making a throwaway Gmail. The problem isn't within the Gmail function. If Google blocked it at some point I would check to make sure it's not automatically blocking attempts or something.

Clearly there is something I am missing at some point, but I have whitelisted it both on my main and throwaway account. Still nothing.

Definitely something on your end then.
Whats your OS and can you take a screenshot of your directory with all the files in it?

Definitely something on your end then.
Whats your OS and can you take a screenshot of your directory with all the files in it?

Windows 10 NT 10.0

Here is this as well, just to prove I am not going crazy... I think...

Sorry, just one more:

Can you paste your .env minus your private information

Can you paste your .env minus your private information

#DISCORD_NOTIFY_GROUP="@here" #DISCORD_WEB_HOOK="https://discordapp.com/api/webhooks/23123123123/5dfsdfh3h2j5hdfhsdfsdhj55jf"<EMAIL_ADDRESS>EMAIL_PASSWORD="XXXXXXXXXXXXXX" HEADLESS="true" IN_STOCK_WAIT_TIME="30" LOG_LEVEL="info" OPEN_BROWSER="true" PAGE_TIMEOUT="30000" PHONE_NUMBER="15134035152" PHONE_CARRIER="verizon" #PLAY_SOUND="false.mp3" #PUSHOVER_TOKEN="123pushover-token456" #PUSHOVER_USER="123pushover-user-key" PAGE_SLEEP_MIN="5000" PAGE_SLEEP_MAX="10000" SHOW_ONLY_BRANDS="evga" SHOW_ONLY_SERIES="3080" #SLACK_CHANNEL="SlackChannelName" #SLACK_TOKEN="slack-token" STORES="amazon,bestbuy,bandh,nvidia,evga,microcenter,newegg" COUNTRY="usa" SCREENSHOT="true" #TELEGRAM_ACCESS_TOKEN="" #TELEGRAM_CHAT_ID="1234" USER_AGENT="Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0"

The only other thing I can think of is that I have 2 PiHoles running off of my Unraid server. But that wouldn't have anything to do with it, would it?

I think PiHole is inbound isn't it?  You could try using the PiHole admin page to disable temporarily and see if that resolves it.  I'm also assuming you aren't running headless so you can disable HEADLESS="true" as well.

I mean you're not lacking the information here... I also don't know if commenting works in .env files. Could be very wrong. Shouldn't have to do anything with it though.
As for the PiHole, that's out of my scope. I wouldn't imagine it being a problem though.

I was having the same problem until I found the actual setting to allow less secure apps.  Try this:
https://www.google.com/settings/security/lesssecureapps

I was having the same problem until I found the actual setting to allow less secure apps. Try this:
https://www.google.com/settings/security/lesssecureapps

BOOM! Nailed it. You the man!

Solved!

I was having the same problem until I found the actual setting to allow less secure apps. Try this:
https://www.google.com/settings/security/lesssecureapps

Thanks, I had same problem and this fixed it.

Do not set your account to less secure. Use the app password.


Receiving a 'this tool requires the "new ARN resource ID format"' error on setup in Linux

Running docker (19.03.12) on Linux (Ubuntu xenial) with ecs plugin (1.0.0-beta.2).
Following the steps for docker ecs setup:
Enter context name: aws
new profile
Enter profile name: awssandbox
Enter region: us-east-1
Enter credentials: y
Enter AWS Access Key ID: **********
Enter AWS Secret Access Key: ****************************************
this tool requires the "new ARN resource ID format"

docker context ls doesn't display the context I attempted to create and docker context use awssandbox reports context not found.
Also, I used aws configure --profile pname to create a profile for docker ecs to use. Docker ecs still failed to create the context.

You will need to log in to the AWS console and opt in to the new arn and resource format. You can read more here:
https://aws.amazon.com/blogs/compute/migrating-your-amazon-ecs-deployment-to-the-new-arn-and-resource-id-format-2/
Or just go here:
https://console.aws.amazon.com/ecs/home?#/settings

Thank you! That worked when I logged in as the IAM user of the AWS access keys I was using.

Awesome. We'll get this into the docs as a requirement. //cc @usha-mandya

@metcalfc PTAL - https://github.com/docker/docker.github.io/pull/11170

@usha-mandya Thanks. @mtyler68 thanks for the report. This is in the docs now!

I am actually continuing to experience this after updating the Account Settings on AWS and additionally matching the permissions listed in the documentation.
Is it possible there is some other missing piece that is required to get passed this error?
Currently on a Mac.
Verified that the user is attached to the correct policy.
Verified that the Account ID and Key are correct. AWS shows ECS is accessed.
Verified the permissions match the list here:
https://github.com/docker/ecs-plugin/blob/master/docs/requirements.md

@tperry-aadya : If you're getting the error that reads, this tool requires the "new ARN resource ID format", then the user your using is not configured for the new ARN format.
Otherwise, what error are you getting?

@tperry-aadya : If you're getting the error that reads, this tool requires the "new ARN resource ID format", then the user your using is not configured for the new ARN format.
Otherwise, what error are you getting?

That is the error I am getting, however the user I am using is configured for the new ARN format. Or at least I think it is! I'll go back again and rebuild the user from scratch just in case.

I believe you will have to opt into the new format in every region individually. So also check if you opted into the specific region. I don't believe there is a way to opt in across the board.

I've done the steps described above but I can't use the context, does anyone know why this happens?
% docker context ls
NAME                TYPE                DESCRIPTION                               DOCKER ENDPOINT               KUBERNETES ENDPOINT   ORCHESTRATOR
ecs                aws
default *           moby                Current DOCKER_HOST based configuration   unix:///var/run/docker.sock                         swarm

% docker context use ecs
context "ecs": not found

Same here, I've "Enabled" each new ARN ID type on the selected region (eu-west-1) and I still get the error his tool requires the "new ARN resource ID format" on the docker ecs setup command.

For me I created new root user credential in IAM and was able to connect, I'm not sure why I received this other error once I'd made the selection.


Input not anymore an alias

See https://github.com/laravel/laravel/commit/2adbbbd91e9d6e2d569cc56f138b7273efe25651
It could be useful to put full path and not alias because Taylor changes his mind often.
In ApiGuardController and ApiGuard, it is needed to declare the full path for Input : use Illuminate\Support\Facades\Input.

Alternatively, you can just add this to your aliases array in config/app.php:

Can you make PR for this?

Yes I just did one. Do you know if someone managed to make the package work on L5.2 ?
I'm having problems with a T_PAAMAYIM_NEKUDOTAYIM error (which means double colon in Hebrew) line 197 of Middleware\ApiGuard

oh. it has been fixed as per 3.0.1


feat(transformer-dts): report error for invalid signature property key

#3698  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


Issue 1456: Standardize tests assertions to AssertJ

Pull Request Description
This pull request closes #1456
Acceptance Test

[x] Building the code with mvn clean install -Dintegration.tests still works.
[x] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[x] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[ ] The tests in the strongbox-web-integration-tests still run properly.

Questions

Does this pull request break backward compatibility?

[ ] Yes
[x] No

Does this pull request require other pull requests to be merged first?

[x] Yes, please see https://github.com/strongbox/strongbox-npm-metadata/pull/11
[ ] No

Does this require an update of the documentation?

[ ] Yes, please see strongbox/strongbox-docs#{PR_NUMBER}
[x] No

I think it is ready for review @carlspring, @fuss86

@mslowiak could you also run mvn dependency:tree -Dverbose -Dincludes=org.hamcrest command on the root of the project and show us the result ?
We should exclude it from other modules than web (where we decided to leave it).
Please follow https://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html#Dependency_Exclusions

hamcrest should be excluded from strongbox/strongbox-parent project?

hamcrest should be excluded from strongbox/strongbox-parent project?

it can't be excluded from strongbox/strongbox-parent since we need to use it strongbox-web-core module. it should be excluded in every module other than strongbox-web-core

hamcrest should be excluded from strongbox/strongbox-parent project?

it can't be excluded from strongbox/strongbox-parent since we need to use it strongbox-web-core module. it should be excluded in every module other than strongbox-web-core

In every module hamcrest is included in spring-boot-starter-test which is dependent (I guess) from strongbox-parent.
Maybe will be better to exclude it from strongbox-parent and make include dependency in pom.xml in web module?

Ok, please try to exclude org.hamcrest from spring-boot-starter-test in https://github.com/strongbox/strongbox-parent and add it in the strongbox-web-core explicitly.
Once you'll get a PR for https://github.com/strongbox/strongbox-parent change the parent version to the PR version (similarly to https://github.com/strongbox/strongbox-parent/pull/38/files#diff-600376dffeb79835ede4a0b285078036R9). And then update your branch of strongbox project to use the proper parent version (see for example https://github.com/strongbox/strongbox/pull/1440/files). Once we decide to merge it, we will first merge strongbox-parent and then strongbox, reverting versions to 1.0-SNAPSHOT

@mslowiak - I've updated your pom.xml files to use the proper versions of the strongbox-parent. However, it looks like there are a few test cases which are still failing. Would you mind having another look? :)

Sure thing, I will look on it today evening :)

Thanks! :)


cmd/go: go vet does not support -overlay

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

$ go version
go version go1.16 darwin/arm64

Does this issue reproduce with the latest release?

Consider the following txtar:
-- go.mod --
module test.pkg
-- foo/foo_test.go --
package foo

import "testing"

func TestFoo(t *testing.T) { }
-- tmp/bar.go --
package foo
-- foo/overlay.json --
{"Replace": {"bar.go": "../tmp/bar.go"}}

I ran cd foo && go test -overlay=overlay.json . and expected the tests to pass.
What did you expect to see?
$ go test -overlay=overlay.json .
ok  	test.pkg/foo 0.123s

What did you see instead?
$ go test -overlay=overlay.json .
# test.pkg/foo
vet: open bar.go: no such file or directory
FAIL	test.pkg/foo [build failed]
FAIL
exit status 2

The issue is because the overlay is added to GoTestFiles but go vet does not support (or receive information about) overlays, so it tries to read the overlaid file directly from the filesystem where it does not exist.

cc @matloob @bcmills

Hi, alldocs.go says this:
// 	-overlay file // 		read a JSON config file that provides an overlay for build operations. // 		The file is a JSON struct with a single field, named 'Replace', that // 		maps each disk file path (a string) to its backing file path, so that // 		a build will run as if the disk file path exists with the contents // 		given by the backing file paths, or as if the disk file path does not // 		exist if its backing file path is empty. Support for the -overlay flag // 		has some limitations: importantly, cgo files included from outside the // 		include path must be in the same directory as the Go package they are // 		included from, and **overlays will not appear when binaries and tests are // 		run through go run and go test** respectively.
Is the above description saying that this is not an issue? I am new, so I could be getting it wrong

Also: go vet accepts a -overlay <file> flag, but seems to ignore it:
$ go vet -overlay=overlay.json .

We should implement this for Go 1.24.


Creation wizard position change on window when inactive for a long time

Describe the issue:
Creation wizard position change on window when inactive for a long time.
https://github.com/wso2/product-is/assets/39077751/331cf326-6b68-499c-ba0c-dfceab87a00c
How to reproduce:

Login to console
Go to user store creation page
Click new user store
Idle until show warning message inactive for long time
Click go back

Expected behavior:
Once click the go. back will refresh the page and there, UI popup wizards positioning should be correct.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

This is not reproducible for Application creation wizard.
https://github.com/wso2/product-is/assets/39077751/3788cdfd-5cbe-40bc-b7fc-31d3af525581

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


No results

Hi,
I'm trying to use your plugin with qBittorrent v3.3.14 but I get no results.
Can you check is all work on your side ?
Thanks :)

Hi! I can't reproduce it on my end: it seems to be working fine on 3.3.14 with Python2 and Python3.

Did you install it before or is it your first time using the plugin?
What's your OS and Python version?

Hi !
I just did'nt have notice I need to write my credentials in the script (yes, I'm foolish) x), thanks for you script it's perfect ^^.


Problems debugging on MacOS-Catalina

Opening a new issue for the last comment in https://github.com/microsoft/vscode-cmake-tools/pull/988 (from @coppersoft)
I'm sorry, but this workaround didn't work for me.
OS: MacOS X Catalina: 10.15.4
Visual Studio Code: 1.44.2
ms-vscode.cpptools: 0.27.0
ms-vscode.cmake-tools: 1.3.1
I downloaded Xcode 10.3, extracted llvm-mi from it and put it inside
/Applications/Xcode.app/Contents/Developer/usr/bin/
Then I added this to settings.json
"cmake.debugConfig": {
"miDebuggerPath": "/Applications/Xcode.app/Contents/Developer/usr/bin/lldb-mi"
}
But nothing changes. I launch the debug, but everything hangs, no breakpoint hit and it seems that nothing is executed.
I tried also setting "miDebuggerPath" to the llvm-mi bundled in the cpptools
~/.vscode/extensions/ms-vscode.cpptools-0.27.0/debugAdapters/llvm-mi
But nothing changes...
Am I doing something wrong?
Thank you

Same problem here

macOS Mojave, Version: 10.14.6
Visual Studio Code, Version: 1.44.2
CMake Tools, Version: 1.3.1
cpptools, Version: 0.27.0

My settings.json. I built lldb-mi from source.
{
    "cmake.debugConfig": {
        "miDebuggerPath": "/usr/local/bin/lldb-mi"
    }
}

And output output when I click "Debug"
[proc] Executing command: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lldb --version

I don't know what am I doing wrong.

I checked and turned out that I was doing nothing wrong, it was just a bug in v1.3.1. Seems like this bug was already fixed in 70e935ba8acf5fcf16f1f46dc497a943e231dd22.

Oh, that is great. Thank you for digging through our last months commits and for identifying the fix for this problem. It will be released with CMake Tools 1.4.

Duplicate of #1060


Suggest groups for sides based on existing groups

+1 This sounds super useful!

Could be a column in the table showing whether it's in the same group as the Current Glyph or not. And a button or two added to the bottom to quickly add it to the group.

It could mark which glyphs are as yet unclaimed.
It could also show which existing groups are relevant


Doc polish

Is this what you had in mind @joshproehl? Theres not much to say, we've only got 5 general codes.

fixed the accidental commits

@joshproehl: is this ready to be merged? :)

FYI @pgicking when you're doing a PR like this it's fair game to force-push an update, i.e. simply remove the offending changes and force push. No harm in having "revert" commits in general, but sometimes it's nice to keep the history clean. :smile:
Closing, will be merged in at 78cdf7b35903cc0abfb9ca2e42969c56bce0f445


presence of SDL2 not checked?

It appears the package happily installs if only libSDL but not libSDL2 is installed, but then crashes on .init().
[Ubuntu 16.4, julia 0.7 beta 2]

Maybe it's the libSDL alias here:
https://github.com/jonathanBieler/SimpleDirectMediaLayer.jl/blob/master/deps/build.jl#L6
Can you check what the proper name of the library on your system ? (apt-cache search sdl)

I have libsdl1.2debian:amd64 and libsdl1.2-dev (and various sdl-* packages of course) installed.
I vaguely remember having had a similar issue with a CMAKE based project a while ago where we ended up concluding that SDL versioning has some serious issues.

I mean the name of the one that should be installed, we basically need to make sure the version 2 get installed instead of the 1, but for that we need the correct name that your package manager expect.

Ok, I'm not entirely sure which information you need, so here's the full dump:
dpkg -l *sdl*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                 Version                 Architecture            Description
+++-====================================-=======================-=======================-=============================================================================
ii  freeciv-client-sdl                   2.5.3-1                 amd64                   Civilization turn based strategy game (SDL client)
un  libsdl-1.3-0                         <none>                  <none>                  (no description available)
un  libsdl-1.3-dev                       <none>                  <none>                  (no description available)
un  libsdl-dev                           <none>                  <none>                  (no description available)
rc  libsdl-gfx1.2-4:amd64                2.0.23-3                amd64                   drawing and graphical effects extension for SDL
ii  libsdl-gfx1.2-5:amd64                2.0.25-5                amd64                   drawing and graphical effects extension for SDL
ii  libsdl-image1.2:amd64                1.2.12-5+deb9u1build0.1 amd64                   Image loading library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-mixer1.2:amd64                1.2.12-11build1         amd64                   Mixer library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-net1.2:amd64                  1.2.8-4                 amd64                   Network library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-sound1.2:amd64                1.0.3-7build1           amd64                   Sound library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-ttf2.0-0:amd64                2.0.11-3                amd64                   TrueType Font library for Simple DirectMedia Layer 1.2, libraries
un  libsdl1.2                            <none>                  <none>                  (no description available)
un  libsdl1.2-all                        <none>                  <none>                  (no description available)
ii  libsdl1.2-dev                        1.2.15+dfsg1-3          amd64                   Simple DirectMedia Layer development files
un  libsdl1.2-esd                        <none>                  <none>                  (no description available)
un  libsdl1.2-nas                        <none>                  <none>                  (no description available)
un  libsdl1.2-oss                        <none>                  <none>                  (no description available)
ii  libsdl1.2debian:amd64                1.2.15+dfsg1-3          amd64                   Simple DirectMedia Layer
un  libsdl1.2debian-all                  <none>                  <none>                  (no description available)
un  libsdl1.2debian-alsa                 <none>                  <none>                  (no description available)
un  libsdl1.2debian-esd                  <none>                  <none>                  (no description available)
un  libsdl1.2debian-nas                  <none>                  <none>                  (no description available)
un  libsdl1.2debian-oss                  <none>                  <none>                  (no description available)
un  libsdl1.2debian-pulseaudio           <none>                  <none>                  (no description available)
ii  libsdl2-2.0-0:amd64                  2.0.4+dfsg1-2ubuntu2.16 amd64                   Simple DirectMedia Layer
ii  libsdl2-dev                          2.0.4+dfsg1-2ubuntu2.16 amd64                   Simple DirectMedia Layer development files
ii  libsdl2-mixer-2.0-0:amd64            2.0.1+dfsg1-1           amd64                   Mixer library for Simple DirectMedia Layer 2, libraries
ii  libsdl2-mixer-dev:amd64              2.0.1+dfsg1-1           amd64                   Mixer library for Simple DirectMedia Layer 2, development files
ii  libsdl2-ttf-2.0-0:amd64              2.0.14+dfsg1-1          amd64                   TrueType Font library for Simple DirectMedia Layer 2, libraries
ii  libsdl2-ttf-dev:amd64                2.0.14+dfsg1-1          amd64                   TrueType Font library for Simple DirectMedia Layer 2, development files


Support executions on only changed files(for PR checks)

Describe the feature
It would be better to use this in CI(PR check) if this plugin supports executions on only changed files like in sonar analysis.
Currently my project takes 20mins to execute for the whole file.
cc @minwoox
Any alternative you've considered ?
None yet.

Agree this would be great to have, the plugin is slow especially if using git to determine timestamps.

Such mechanism would require maintaining a sort of cache, and then comes the complexity to know when to invalidate this cache. There is no trivial rules here, and computing a hash would be as slow as checking licenses.
@uyw4687 : the plugin already has some concurrency mechanism in place that you can control with license.concurrencyFactor and license.nThreads. If doing a lot of I/O with git, maybe you can try increasing the numbers especially if the number of cores of your system is low (i.e. in containers or VM)

Thanks @mathieucarbou I was actually talking about Git diff. Sorry for not elaborating on this.
So we can make a feature that performs the license validity check only with changed files which we can know by git diff.
This way, we can limit the responsibility of the failure to the extent of the files changed by a pull request.

Thanks @mathieucarbou I was actually talking about Git diff. Sorry for not elaborating on this.
So we can make a feature that performs the license validity check only with changed files which we can know by git diff.
This way, we can limit the responsibility of the failure to the extent of the files changed by a pull request.

Yes! It is definitely a good idea to use the git extension to filter the files to scan.


RFP - beekeeper-studio

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts with 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://www.beekeeperstudio.io
Direct download URL for the software / installer :  https://github.com/beekeeper-studio/beekeeper-studio/releases/download/v1.9.1/Beekeeper-Studio-Setup-1.9.1.exe
Software summary / short description: Open Source SQL Editor and Database Manager

doh, didn't search very well!

doh, didn't search very well!


Allow adding multiple issues to a project

Adds an option like for adding multiple issues to a milestone.
Closes #17216

Codecov Report

Merging #17226 (2fedb27) into main (f2e7d54) will decrease coverage by 0.70%.
The diff coverage is 49.78%.

@@            Coverage Diff             @@
##             main   #17226      +/-   ##
==========================================
- Coverage   45.31%   44.60%   -0.71%
==========================================
  Files         773      779       +6
  Lines       86873    87303     +430
==========================================
- Hits        39366    38945     -421
- Misses      41151    42007     +856
+ Partials     6356     6351       -5

Impacted Files
Coverage Δ

cmd/admin.go
0.00% <0.00%> (ø)

models/action.go
48.86% <0.00%> (ø)

models/avatar.go
35.38% <0.00%> (ø)

models/error.go
39.83% <ø> (+0.29%)
:arrow_up:

models/fixture_generation.go
70.00% <0.00%> (ø)

models/gpg_key_verify.go
13.46% <0.00%> (ø)

models/helper.go
52.94% <0.00%> (ø)

models/issue_lock.go
0.00% <0.00%> (ø)

models/migrate.go
0.00% <0.00%> (ø)

models/pull_sign.go
37.64% <0.00%> (ø)

... and 220 more

Continue to review full report at Codecov.

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

:rocket:


[BUG] collision problem with Random* Function

Describe the bug
RandomNum and RandomString functions produce the same result when different Bots call the function at the same time
To Reproduce
Run this with 10 or more Bots and you'll see in hits that some Bots have the same result:
FUNCTION RandomString "?u?u?u?u?d?d" -> CAP "result"
SET STATUS SUCCESS
Expected behavior
No collision
Screenshots

Version
1.1.3#267

fixed with https://github.com/openbullet/openbullet/commit/22f1adbf1707c0218197d9c59c133256fc41e320


[DOCS] Update Hudi support versions for Redshift Spectrum in the current doc.

…ent doc.
Change Logs
[DOCS] Update Hudi support versions for Redshift Spectrum in the current doc.
Impact
One doc file changed: query_engine_setup.md.
Risk level: none | low | medium | high
None
Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

[DOCS] Update Hudi support versions based on the recent field tests for Redshift Spectrum in the current doc.

@pomaster Thanks for your first contribution!


Error when accessing gradients in AGS

Hi,
Thanks for your excellent code! I'm new to julia. When I run the training code in ags.jl file (by changing the ars function in ant_ars.jl to ags), I get the error ERROR: BoundsError: attempt to access 0-element UnitRange{Int64} at index [0], which traces back to this line. Could anyone help me with this?
Ian

The AGS example was removed in the latest version to keep the examples rather simple. A proper implementation of such algorithms should probably be in its own package.


Update Development Environment

As a Developer
I need to upgrade to Python 3.11 and change requirements.txt, Makefile and setup.cfg
So that the project uses the most to up to date stable build of Python and the one used for the class
Assumptions:

We will directly follow the directions given in Slack by Professor Rofrano

Acceptance Criteria:
- requirements.txt, Makefile and setup.cfg match the versions in [this repo](https://github.com/nyu-devops/project-template)
- A pull request identical [to this pull request](https://github.com/nyu-devops/project-template/pull/11) is made

https://github.com/CSCI-GA-2820-SU23-001/promotions/pull/12


Manual tracing for auto-instrumentation-enabled Lambda fuctions

I enabled the auto-instrumentation support by following the instructions on ADOT Lambda Support For JavaScript in my TypeScript Lambda functions. The auto-instrumentation is enabled successfully as follow:

However, when I manually create spans following instructions from here, the information seems not reported to the CloudWatch X-Ray.
My operations exactly

I added this layer to my Lambda function: arn:aws:lambda:us-west-2:901920570463:layer:aws-otel-nodejs-amd64-ver-1-15-0:2
I enabled the active tracing in my AWS Lambda function
I added some manual instrumentations, code:
const sdk = new NodeSDK({
  resource: new Resource({
    [SemanticResourceAttributes.SERVICE_NAME]: 'echo-handler',
    [SemanticResourceAttributes.SERVICE_VERSION]: '1.0',
  }),
  traceExporter: new OTLPTraceExporter(),
  }),
});

sdk.start();
const tracer = api.trace.getTracer('echo-handler-tracer');

module.exports.handler = async (
  event: APIGatewayProxyEvent,
  context: Context,
  callback: Callback<APIGatewayProxyResult>,
): Promise<APIGatewayProxyResult> => {
  return tracer.startActiveSpan('echo API handler', async (span) => {
    ... some logics
    span.end();
    return {
      statusCode: 200,
      body: JSON.stringify({
        message: requestBody.message,
        tables: tables,
      }),
    };
  });
};

Question
I'm unable to find any information about this, is manually instrumenting not supported when the auto-instrumentation is enabled?

This is the code I tried later, still doesn't work:

const _traceExporter = new OTLPTraceExporter();
const _spanProcessor = new BatchSpanProcessor(_traceExporter);
const sdk = new NodeSDK({
  textMapPropagator: new AWSXRayPropagator(),
  resource: new Resource({
    [SemanticResourceAttributes.SERVICE_NAME]: 'echo-handler',
    [SemanticResourceAttributes.SERVICE_VERSION]: '1.0',
  }),
  instrumentations: [
    new AwsLambdaInstrumentation({
      requestHook: (span, { event, context }) => {
        span.setAttribute('faas.name', context.functionName);
        span.setAttribute('event', event);
      },
      responseHook: (span, { err, res }) => {
        if (err instanceof Error) span.setAttribute('faas.error', err.message);
        if (res) span.setAttribute('faas.res', res);
      },
    }),
    new HttpInstrumentation(),
    new AwsInstrumentation({
      suppressInternalInstrumentation: true,
    }),
  ],
  traceExporter: _traceExporter,
  spanProcessor: _spanProcessor,
  idGenerator: new AWSXRayIdGenerator(),
});

sdk.start();

const tracer = api.trace.getTracer('echo-handler-tracer');

module.exports.handler = async (
  event: APIGatewayProxyEvent,
  context: Context,
  callback: Callback<APIGatewayProxyResult>,
): Promise<APIGatewayProxyResult> => {
  return tracer.startActiveSpan('echo API handler', async (span) => {
    ... some logics
    span.end();
    return {
      statusCode: 200,
      body: JSON.stringify({
        message: requestBody.message,
        tables: tables,
      }),
    };
  });
};

When I turn the activate trace option on, only traces provided by the layer (from my perspective) is exported to the X-Ray, and the traces from the code is not.

I took a log to check if the default URL is correct:
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http';

const _traceExporter = new OTLPTraceExporter({});
console.log(`using default OTLP TraceExporter URL: ${_traceExporter.getDefaultUrl({})}`);

The log:

From ADOT document

Also note that, the OTEL_EXPORTER_OTLP_ENDPOINT environment variable does not need to be set. The default value is http://localhost:4318, as the ADOT Node.JS lambda layer only supports OTLP over HTTP.

This seems to be right.

were you able to get this working? I am running into the same issue

were you able to get this working? I am running into the same issue

Are you also using the layer from the ADOT document?

were you able to get this working? I am running into the same issue

Are you also using the layer from the ADOT document?

Yes -- I was able to get manual instrumentation working for other backends like New Relic, so been working with that. Could not get xray to pick up any of my spans/attributes

I turned to use PowerTools instead of the ADOT layer FYI @ferdy-roz

Could it be because you're not awaiting your async callback?


SUBS requires a lo register, so sepcify that in assembler constraints

I saw this cause a compile failure in the wild (surprised it hasn't before)


Docker support

Adding support for production based docker container ,
Can be discussed for more ideas if required on this.

Can we add support for running the container in watch mode also?

@tanmaymohan please let us know if there is any update on this.

Please explain in detail the requirement , I'll try adding it soon.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/46 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 58b9bcd:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-25-02-16-02 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-25-02-16-02

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Is it possible to make split window scaled seperately ?

As all windows with the same scale, not well.

/needsMoreInfo


[YUNIKORN-1415] Adding Chinese translation of ACLs

What is this PR for?
Adding Chinese translation of ACLs
What type of PR is it?

[ ] - Bug Fix
[ ] - Improvement
[ ] - Feature
[x] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

@0yukali0 Thanks for checking the grammer!


UserManager.IsLockedOutAsync is always returning false

Hi,
I am trying to retrieve user locked out status and it seems that IsLockedOutAsync method always returns false, even if the user is locked out.
Also, please note that "summary" of the method is incorrect. It should read as: "Returns a flag indicating whether the specified user his is locked out, as an asynchronous operation."
Similarly, "summary" is incorrect for GetLockoutEnabledAsync: "Retrieves a flag indicating whether user lockout can be enabled for the specified user."
Also, "summary" is incorrect for GetLockoutEndDateAsync: "Gets the last DateTimeOffset a user's last lockout expired, if any. Any time in the past should be indicates indicate that a user is not locked out."
Please help to resolve IsLockedOutAsync issue.

LockoutEnabled is set to 1 and LockoutEnd is set to date: 2018-05-10 06:09:04.571204.
I just locked the user out by entering incorrect password, so the date above is current. Also, I am using MySQL database, does it have anything to do with how this date is treated?

Yeah the expectation is that the date is in UTC I believe, is there any issues with MySql and dates?

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


Notifications: allow disable latest and/or non-stable

Closes #133
Requires https://github.com/readthedocs/readthedocs.org/pull/11718

Backend and frontend PRs are already approved. This is only one missing for review to be able to merge them all.


AWS Instances are not Auto-assigned Public IPs

When an AWS server is provisioned through MIQ it is does not receive an auto-assigned public IP, even though the subnet the server is being launched into has Auto-assign Public IP enabled. This causes issues if the subnet is a public subnet because the server cannot communicate out to the internet until it receives an elastic ip. This also causes issues when launching amis that have boot scripts that download packages from the internet. Is there any way to add an option into the flow or enable Auto-assign Public IP by default for orders, unless an elastic IP is selected.

@mandeep170
Any updates on this?

I will try this today and get back to you.

@mkanoor In step 3, when I select the security group, it does not automatically select a subnet. It still says . I am using the Anand build of MIQ.

@mandeep170
Can you confirm that you have same subnet in multiple availability zones? From the UI if you select the AZ does it show all the valid subnets or is it empty?

@mkanoor i can't confirm that. I need to redo this test. The same subnet cannot span multiple Availability Zones (AZ). Subnets are bound by an AZ. I can try to recreate this test again but I don't believe by default when you provision a VM using the aws-sdk you receive a public ip address. Usually you have send another attribute in the request (:associate_public_ip_address (Boolean) — default: false). I don't think all instances should get a public address when they are being provisioned but I think there should be an option to enable this attribute when provisioning a machine.

@mkanoor
Can you please re-check
Steps I followed(no public IP was assigned to instance on AWS console):

Within 'Environment' tab in "Provision Instances" form, select AZ, and VPC
Do not select Cloud Subnet
Select Security Group(I selected default VPC security group). Cloud subnet will be auto-assigned.
Leave EIP as

As described in the issue, server cannot communicate out to the internet until it receives an EIP
Steps I followed(Public IP was assigned to instance on AWS console and visible in instance summary page next to private IPaddress):

Within 'Environment' tab in "Provision Instances" form, select AZ, and VPC
Do not select Cloud Subnet
Select Security Group(I selected default VPC security group). Cloud subnet will be auto-assigned.
Select EIP

@mandeepbal seems this issue is stale, can you close.

@mkanoor Can you follow up here?


Quasar I dont have any client files and i can't build

I have set up everything fine, but I can't build because I don't have client.bin or any client files

https://github.com/quasar/QuasarRAT#building-a-client
Build with release configuration.

Be sure to check the closed issues since this has been asked quite a few times.
Have you checked your antivirus?

Even my all anti virus are disabled but still not found client.cin

Hi There! have you solved the problem as i have faced the same issue here! thank you.

Windows has an own antivirus software included called Windows Defender, be sure to add an exception for Quasar. Then build the project as usual.

hi... i still got this issue client.bin could not be licated it should bein the same folder as quasar


No module named tqdm

Last login: Fri Oct 20 21:44:40 on ttys001
MBP-de-iran:~ iran$ cd '/Users/iran/Desktop/instabot-master/examples/' && '/usr/bin/pythonw'  '/Users/iran/Desktop/instabot-master/examples/like_hashtags.py'  && echo Exit status: $? && exit 1
Traceback (most recent call last):
File "/Users/iran/Desktop/instabot-master/examples/like_hashtags.py", line 12, in
from tqdm import tqdm
ImportError: No module named tqdm
How do I solve this problem?

@iransales try it

pip install tqdm

I'm also having this issue
pip install tqdm doesn't help (says already satisfied..)

Same here


Better TA Hashing

Currently the hashing of TA objects happens here. As the hash functions currently stand, the functions attempt to take into account the type by hashing a string representation of the type. However, the string representations do not include the template parameters (for example here the types of the tile/policies are not included). This can conceivably result in erroneous hash collisions if the types convey additional state not captured by the literal elements. Admittedly the damage from such a collision is probably pretty minimal (most likely collisions will occur along the lines of an empty Tensor of Tensors comparing equal to an empty Tensor).
Note that resolving NWChemEx-Project/ParallelZone#30 will enable a more robust solution to this issue.

This is a TensorWrapper problem now.


Update ma-subscription-signup.md

Docs Build status updates of commit 53ae925:
:warning: Validation status: warnings

File
Status
Preview URL
Details

academic-services/includes/ma-subscription-signup.md
:warning:Warning

Details

academic-services/includes/ma-subscription-signup.md

Line 14, Column 335: [Warning-file-not-found] Invalid file link: './resources-pricing'.
Line 99, Column 122: [Warning-file-not-found] Invalid file link: './get-started-receive-data'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

very specific.


Common: update CONTRIBUTING.md (closes #4380)

Hi @RohanMenon , thank you for the PR but I'm closing it at this fix already got merged into the branch of the next release : https://github.com/snowplow/snowplow/pull/4352/commits/2f72b0989c8beb9ab9840f7f5648bf6fa0d03a79
Cheers !


series_regular information is missing on /shows/:id/people

As described in #74, we can access boolean value series_regular if we call /people/:id/shows, example:
/people/aaron-paul/shows
{
    "character": "Jesse Pinkman",
    "characters": [
        "Jesse Pinkman"
    ],
    "episode_count": 62,
    "series_regular": true,
    "show": {
        "title": "Breaking Bad",
        "year": 2008,
        "ids": {
            "trakt": 1388,
            "slug": "breaking-bad",
            "tvdb": 81189,
            "imdb": "tt0903747",
            "tmdb": 1396,
            "tvrage": null
        }
    }
}

But we can't get that information if we call /shows/:id/people with guest stars:
/shows/breaking-bad/people?extended=guest_stars
{
    "character": "Jesse Pinkman",
    "characters": [
        "Jesse Pinkman"
    ],
    "episode_count": 62,
    "person": {
        "name": "Aaron Paul",
        "ids": {
            "trakt": 415249,
            "slug": "aaron-paul",
            "imdb": "nm0666739",
            "tmdb": 84497,
            "tvrage": null
        }
    }
}

Not including guest stars only returns regular cast, so we can distinguish non-regular people by checking if they exist on the list without guest stars but that would mean making two requests for this purpose, one with extended=guest_stars and one without.

I didn't notice that the guest stars are on a separate list, my apologies.


[corechecks/snmp] Add interface_configs to override interface speed

What does this PR do?
[corechecks/snmp] Add interface_configs to override interface speed

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

Replaced by https://github.com/DataDog/datadog-agent/pull/15721


Does not contain password validation enabled by default

Describe the bug
on the change password screen, the validation "does not contain password" is enabled
What is the expected behavior?
What are the steps to reproduce?

Login and then select change password.
does not contain password is enabled

Screenshots or links to minimum reproduction example

Environment

Anything else to add?

This is just an example in demo app, not in default validations.


Gradle 6 support

Gradle 6 doesn't like you creating a task with overwrite:true if the task doesn't already exist. I don't think the task would already exist so the fix here is simply to stop passing overwrite:true.
Also a few other tweaks to resolve some warnings for Gradle 7 - the is one remaining about the use of the maven plugin but I don't really know what I'm doing there so leaving it.

Are you able to execute the test after your changes?  I'm having trouble
running it.
On Mon, Nov 18, 2019 at 7:34 AM Nick Howes<EMAIL_ADDRESS>wrote:

Gradle 6 doesn't like you creating a task with overwrite:true if the task
doesn't already exist. I don't think the task would already exist so the
fix here is simply to stop passing overwrite:true.
Also a few other tweaks to resolve some warnings for Gradle 7 - the is one
remaining about the use of the maven plugin but I don't really know what
I'm doing there so leaving it.
You can view, comment on, or merge this pull request online at:
https://github.com/james-bryant/gradle-aspectj/pull/3
Commit Summary

Gradle 6 support.

File Changes

M build.gradle
https://github.com/james-bryant/gradle-aspectj/pull/3/files#diff-0
(21)
M gradle/wrapper/gradle-wrapper.jar
https://github.com/james-bryant/gradle-aspectj/pull/3/files#diff-1
(0)
M gradle/wrapper/gradle-wrapper.properties
https://github.com/james-bryant/gradle-aspectj/pull/3/files#diff-2
(2)
M gradlew
https://github.com/james-bryant/gradle-aspectj/pull/3/files#diff-3
(18)
M gradlew.bat
https://github.com/james-bryant/gradle-aspectj/pull/3/files#diff-4
(18)
M src/main/groovy/aspectj/AspectJPlugin.groovy
https://github.com/james-bryant/gradle-aspectj/pull/3/files#diff-5
(4)
M src/test/resources/project1/build.gradle
https://github.com/james-bryant/gradle-aspectj/pull/3/files#diff-6
(2)

Patch Links:

https://github.com/james-bryant/gradle-aspectj/pull/3.patch
https://github.com/james-bryant/gradle-aspectj/pull/3.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/james-bryant/gradle-aspectj/pull/3?email_source=notifications&email_token=ADKSO72O54UGPY3IFY42DOTQUKKX5A5CNFSM4JOTTPG2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H2BJCSA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKSO7Z24ZOQC5SPZ66JZCDQUKKX5ANCNFSM4JOTTPGQ
.

Hey @james-bryant, yep it is working okay for me locally and GitHub is running it okay . I'm doing ./gradlew clean test -PossrhUsername=x -PossrhPassword=x (the fake properties specified here just because I don't have any real credentials and they're not needed for the test)

Yea, something must be off with my local environment.  I see the test works
fine on GitHub as well.  Thanks for setting that up BTW.  And thanks again
for your contribution.  I don't have as much time to keep things up to date
lately.
I've gone ahead and published version 2.5 with your changes (
https://search.maven.org/artifact/net.uberfoo.gradle/gradle-aspectj/2.5/jar
).
On Tue, Nov 19, 2019 at 5:34 AM Nick Howes<EMAIL_ADDRESS>wrote:

Hey @james-bryant https://github.com/james-bryant, yep it is working
okay for me locally and GitHub is running it okay
https://github.com/james-bryant/gradle-aspectj/commit/773a883f4b78b6c00fff429330f8576a865e5ca1/checks?check_suite_id=316778867.
I'm doing ./gradlew clean test -PossrhUsername=x -PossrhPassword=x (the
fake properties specified here just because I don't have any real
credentials and they're not needed for the test)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/james-bryant/gradle-aspectj/pull/3?email_source=notifications&email_token=ADKSO75SWXGXWZC4OSXAAQ3QUPFLFA5CNFSM4JOTTPG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEN4III#issuecomment-555467809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKSO736C2EAZIT4X7NYR6DQUPFLFANCNFSM4JOTTPGQ
.


Issues with responsive layout not "snapping in the place" after browser resize

Hi. This is maybe an odd question, but I experience , when resizing browser window, that all elements doesn't fluidly snap in place like they should. I suspect this has something to do with duplication of code and that I might be using Jeet in the wrong way. Has anyone else experienced this issue?
I know this probably isn't an issue, since no one sits around resizing a browser window when visiting a page, but fixing this would certainly get the functionality "under my skin" and thus understanding more of the techniques in use.
I might add that I'm using sass-mq as my breakpoint system. Maybe I'm using this wrong?
Last but not least; I don't suspect anyone knowing what the hell I'm talking about and it's probably difficult to diagnose it without code, but someone might have experienced this too? :dancer:
Thanks

I have not experienced this problem first hand myself. Care to explain the steps that lead you to finding this?

This has been fixed, user mistake. Case closed. You can close thread :) Thanks for the followup.


[BEAM-9118] Increase portable_runner_test timeout.

The default pytest timeout is 600s. Once all portable runner tests are migrated to pytest, we can use the pytest timeout instead of portable_runner_test's bespoke implementation. See #12385.
R: @udim

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Looks like the unit test failure is a flake. Filed BEAM-10768


Split Demo Project and Plugin folder

It would be pretty useful if you split the plugin folder in one repo and the project in another with the plugin as git submodule
otherwise it's troublesome to contribute without using the integrated demo project

Done
https://github.com/midgen/GOAPerDemo
https://github.com/midgen/GOAPer


fix: increase versions to use latest and fix label lookup on namespaces

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents

Related Issue # (issue)
Closes # (issue)
Fixes # (issue)

Remove if not applicable

Screenshots

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help
[ ] Separate ticket for tests # (issue/pr)

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added e2e-tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help
[ ] Separate ticket for e2e-tests

Added to documentation?

[ ] 📜 README.md
[ ] 🙅 no documentation needed

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

hum, sometimes the e2e setup fails because of a timeout... 🤔

huh, timed out again, will run locally

Oh fuck. This was buried in the logs... :D
 ./hack/prime_test_cluster.sh: line 32: ./bin/mkcert: No such file or directory

Okay, I added the missing mkcert definition. This didn't stop this thing from dying before BTW. So I'm not sure if this is going to do anything, hahaha. Let's see...


feat(body): reexport http_body::SizeHint

Fix a minor papercut: you can't implement hyper::body::HttpBody::size_hint without importing SizeHint from another crate.

I can't tell what it doesn't like about the commit message

I can't tell what it doesn't like about the commit message


Add --strict-cap-defaults

Changes the default CRI-O capabilities by adding the missing ones
from the docker container engine. In this way the customers will
be able to run the same containers that were working on v3
without any need for modification. At the same time though,
we are adding a new option at skuba '--strict-cap-defaults'.
This option will not copy the docker defaults into CRI-O. Use
this option if you want a vanilla CRI-O experience.
Why is this PR needed?
It fixes https://bugzilla.suse.com/show_bug.cgi?id=1142552
Fixes https://github.com/SUSE/avant-garde/issues/638
What does this PR do?
By default it creates the dockerfied crio-configuration file during skuba init and it replaces the node's crio.conf with this file during bootstrap or join. The file can be found locally inside the addons/cri/crio.conf.
e.g.
statesToApply[0]: kernel.load-modules
statesToApply[1]: kernel.configure-parameters
statesToApply[2]: apparmor.start
statesToApply[3]: cri.start
statesToApply[4]: kubelet.configure
statesToApply[5]: kubelet.enable
statesToApply[6]: kubeadm.join
statesToApply[7]: cni.cilium-update-configmap
statesToApply[8]: skuba-update.start

statesToApply[0]: kernel.load-modules
statesToApply[1]: kernel.configure-parameters
statesToApply[2]: apparmor.start
statesToApply[3]: cri.configure // this is now by default
statesToApply[4]: cri.start
statesToApply[5]: kubelet.configure
statesToApply[6]: kubelet.enable
statesToApply[7]: kubeadm.join
statesToApply[8]: cni.cilium-update-configmap
statesToApply[9]: skuba-update.start

However, if someone wants pure CRI-O experience, they can use --strict-cap-defaults during skuba init. This will do use the CRI-O default configuration.
Long story short, now the v3 containers will work to v4 as well without any need for modification in terms of capabilities.
Anything else a reviewer needs to know?
Here's my testcase:
---
apiVersion: v1
kind: Pod
metadata:
  name: leap
spec:
  containers:
  - name: app
    image: opensuse/leap:latest
    command: ['/bin/sh', '-c', 'sleep 3600']
---
apiVersion: v1
kind: Pod
metadata:
  name: sle12sp4
spec:
  containers:
  - name: app
    image: registry.suse.com/suse/sles12sp4:latest
    command: ['/bin/sh', '-c', 'sleep 3600']
---
apiVersion: v1
kind: Pod
metadata:
  name: sle15
spec:
  containers:
  - name: app
    image: registry.suse.com/suse/sle15:latest
    command: ['/bin/sh', '-c', 'sleep 3600']
---
apiVersion: v1
kind: Pod
metadata:
  name: sle15sp1
spec:
  containers:
  - name: app
    image: registry.suse.de/suse/containers/sle-server/15/containers/suse/sle15:15.1
    command: ['/bin/sh', '-c', 'sleep 3600']

kubectl apply -f test.yaml
declare -a arr=("sle12sp4" "leap" "sle15" "sle15sp1")
for pod in "${arr[@]}"; do echo -n "$pod: "; kubectl exec -it $pod -- su root -c id; done
for pod in "${arr[@]}"; do echo -n "$pod: "; kubectl exec -it $pod -- useradd panos; done

There must be no error from the above commands. Without this PR, the sles12sp4 containers fails due to PAM.

The implementation looks fine, except...
I understand that we're shooting for compatibility with insecure-by-default Docker and that bsc#1142552 exists, but I'm specifically concerned by (re)adding the cap_audit_write permission to default containers.  That one means that an ostensibly unprivileged container which is either malicious or misconfigured can potentially cause host system audit logs to become unavailable -- and, because the audit log daemon operates at an elevated priority, means that a container flooding audit logs can also cause resources to be consumed on the host system which exceed the limits configured for that container.
The other capabilities can admittedly be a part of a multi-step exploit in certain scenarios, but that one in particular concerns me because of how it facilitates direct impact outside the container.  I really wish we'd get an opinion from Security on that to weigh against the Sales opinion; shipping with insecure defaults can very quickly become a bigger black eye on a product than "you need to provide a command line option to retain backwards compatibility".

Thanks everyone :)

I understand the hesitancy, especially Danny's. And we will hit the desired security target... in time.


node - fixed broken path of tsconfig translation

Apparently when inheriting tsconfig, everything is happening in the folder of the parent-file, so paths etc. are  base on where the parent file located, which broke the importing of index file for different arch'
Plus - the index file was written in a way that can work just with esm, so translated it to fit both.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

how was this tested?
how are you planning to test against a similar break in the future?

sorry - better than leaving the fields empty, it would be best to comment out the fields, and explain why they're commented out and where are their actual values.

how was this tested? how are you planning to test against a similar break in the future?

@shachlanAmazon
It was tested by npm pack command, and checking results.
@barshaul mentioned today that she's working on adding testing to the release so it will solve this issue in the future.

how was this tested? how are you planning to test against a similar break in the future?

@shachlanAmazon It was tested by npm pack command, and checking results. @barshaul mentioned today that she's working on adding testing to the release so it will solve this issue in the future.

It would give us a way to test an already released versions, but it wouldn't catch it beforehand. Maybe you can add tests using npm pack to run as a part of the CI?


node-nfc upstream why not?

Is there any reason for not trying to upstream the changes you did on node-nfc ?
https://github.com/hardillb/node-nfc/commits/master?author=hardillb

No idea, it was nearly 3 years ago and the whole node was a quick hack to solve a problem in an afternoon.
Feel free to fork my changes and bring the up to date with the head node and stick a pull request in


Static Pages to Create/Edit

About Us
Funding
Projects
Contact Us
Help
Credits
Visiting the Archives

Also, Media Production Organizational Tools page

sent email with content text and images 12/24/2015

[ ] about -> /pdf/WGBHMLAAssessment.pdf

[ ] media-production-organizational-tools -> * (all links are dead)

[ ] credits (missing logos / out of date)

@caseyedavis12 : There don't seem to be "funding" or "projects" pages on the old site. If I'm missing it, where is it? If it wasn't there, do we need a new page on the new site?

@mccalluc: I am in the process of editing all of the static pages. The funding a projects pages will be new pages.

From: mccalluc<EMAIL_ADDRESS>Sent: Tuesday, February 16, 2016 10:09 AM
To: WGBH/openvault3
Cc: Casey Davis
Subject: Re: [openvault3] Static Pages to Create/Edit (#7)

about -> /pdf/WGBHMLAAssessment.pdf

media-production-organizational-tools -> * (all links are dead)

credits (missing logos / out of date)

@caseyedavis12https://github.com/caseyedavis12 : There don't seem to be "funding" or "projects" pages on the old site. If I'm missing it, where is it? If it wasn't there, do we need a new page on the new site?

Reply to this email directly or view it on GitHubhttps://github.com/WGBH/openvault3/issues/7#issuecomment-184719750.

@caseyedavis12 : Summarizing the current state:

about -> /pdf/WGBHMLAAssessment.pdf
Legal is doing a review.
credits (missing logos / out of date)
Pages are in, imgs commented out, pending review
Funding
Projects
Are more pages necessary than what we already have?

@mccalluc: I have a branch open titled "credits-tweaks."
The content of the credits pages have been updated and approved.
I have received approval from most foundations for logos, and am waiting on approval from two foundations. When we receive approval from the last two foundations, I will remove the comments from the imgs and add the three Mellon reports within the md and on s3.
Then I will issue a PR.
Funding and Projects pages are no longer necessary.
This is not a blocker on making the switch today. Please note that a markdown redeploy will be requested probably next week, once we have received approval from the last two foundations.

I think these have been resolved, reopen if that is not the case.


grpcproxy: split out / tighten up leadership detection

Move leadership detection out of watch code since it will be shared with
lease code. Also stricter: assumes leader does not exist unless watch can
be successfully created.

lgtm

/cc @xiang90

LGTM

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ad1b754). Click here to learn what that means.
The diff coverage is 1.78%.

@@            Coverage Diff            @@
##             master    #7314   +/-   ##
=========================================
  Coverage          ?   64.43%
=========================================
  Files             ?      231
  Lines             ?    20750
  Branches          ?        0
=========================================
  Hits              ?    13371
  Misses            ?     6380
  Partials          ?      999

Impacted Files
Coverage Δ

proxy/grpcproxy/watch.go
0% <ø> (ø)

proxy/grpcproxy/leader.go
0% <ø> (ø)

proxy/grpcproxy/kv.go
23.01% <100%> (ø)

Continue to review full report at Codecov.

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