Fix flaky tests in create-ponder

The create-ponder tests use the Etherscan API which has an annoyingly strict 5 req/second limit, even with an API key. This leads to occasional test failures.
One idea would be to test all of the Etherscan API routes that we use only once in a ~unit test style, and then mock the responses for all of the end-to-end tests. This would also speed up the tests quite a bit.

Fixed at some point by increasing the timeout


Add sam flags to filter non-primary hits and supplementary hits

Hi Ben,
Sometimes more than one hits of a read will be kept, and chimeric alignment  also does occur during the mapping process, so I added two more flags that will filter non-primary and supplementary hits in bam file for downstream bedtools analysis. If you also think this is feasible, you can merge this branch.
Cheers,
Jie

Thanks. I made it a bit more general and pushed v0.4.0.


Delete service when every role have been terminated

Description
As a result of charters or scheduled actions the VMs within a role can be automatically terminated. It would be useful to have an option for terminating the service when all the roles have been terminated (i.e all the VMs within each role are terminated).
Use case
It avoid to have empty, not used, services without any VM.
Interface Changes
This option needs to be set from Sunstone interface or directly modifying the Service template via CLI.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

PRs to merge in master:

code
docs
tests

@tinova PRs to be approved:

code
docs
tests

@tinova PRs to be approved:

code
docs
tests


:w "E212 Can't open file for writing" when directory is not exists

Vim really cannot create a directory? Or as minimum I think that we can say to the user that he must create a directory manually.

The error is correct.  Quite often when this happens there is a mistake in the command, creating the directory would be the wrong solution.
There can be other reasons, such as the directory not being readable.  It's hard to give a better error message that is accurate.


Sequence contains more than one matching element

I'm using MSBuild.SonarQube.Runner.Tool via Cake.Sonar, apparently the latest version uses a deprecated parameter to get the list of QualityProfiles, projectKey. Is a new version planned?
begin /d:sonar.host.url="https://sonarqube.cgm.ag/" /k:"cgm.fr.axisante.Hydra" /d:sonar.qualitygate.wait="true" /d:sonar.login="[REDACTED]" /d:sonar.password="[REDACTED]" /d:sonar.verbose=true
SonarScanner for MSBuild 4.8
Using the .NET Core version of the Scanner for MSBuild
Default properties file was found at C:\Developments\products\axisante5\tools\MSBuild.SonarQube.Runner.Tool.4.8.0\tools\sonar-scanner-msbuild-<IP_ADDRESS>08-netcoreapp3.0\SonarQube.Analysis.xml
Loading analysis properties from C:\Developments\products\axisante5\tools\MSBuild.SonarQube.Runner.Tool.4.8.0\tools\sonar-scanner-msbuild-<IP_ADDRESS>08-netcoreapp3.0\SonarQube.Analysis.xml
sonar.verbose=true was specified - setting the log verbosity to 'Debug'
Pre-processing started.
Preparing working directories...
Using environment variables to determine the download directory...
11:57:29.022  11:57:29.017  Loading analysis properties from C:\Developments\products\axisante5\tools\MSBuild.SonarQube.Runner.Tool.4.8.0\tools\sonar-scanner-msbuild-<IP_ADDRESS>08-netcoreapp3.0\SonarQube.Analysis.xml
11:57:29.023  11:57:29.022  sonar.verbose=true was specified - setting the log verbosity to 'Debug'
11:57:29.027  Updating build integration targets...
11:57:29.03  The file SonarQube.Integration.ImportBefore.targets is up to date at C:\Users\Laurent.Bensch\AppData\Local\Microsoft\MSBuild\4.0\Microsoft.Common.targets\ImportBefore
11:57:29.03  The file SonarQube.Integration.ImportBefore.targets is up to date at C:\Users\Laurent.Bensch\AppData\Local\Microsoft\MSBuild\10.0\Microsoft.Common.targets\ImportBefore
11:57:29.031  The file SonarQube.Integration.ImportBefore.targets is up to date at C:\Users\Laurent.Bensch\AppData\Local\Microsoft\MSBuild\11.0\Microsoft.Common.targets\ImportBefore
11:57:29.032  The file SonarQube.Integration.ImportBefore.targets is up to date at C:\Users\Laurent.Bensch\AppData\Local\Microsoft\MSBuild\12.0\Microsoft.Common.targets\ImportBefore
11:57:29.032  The file SonarQube.Integration.ImportBefore.targets is up to date at C:\Users\Laurent.Bensch\AppData\Local\Microsoft\MSBuild\14.0\Microsoft.Common.targets\ImportBefore
11:57:29.033  The file SonarQube.Integration.ImportBefore.targets is up to date at C:\Users\Laurent.Bensch\AppData\Local\Microsoft\MSBuild\15.0\Microsoft.Common.targets\ImportBefore
11:57:29.033  The file SonarQube.Integration.ImportBefore.targets is up to date at C:\Users\Laurent.Bensch\AppData\Local\Microsoft\MSBuild\Current\Microsoft.Common.targets\ImportBefore
11:57:29.035  Installed SonarQube.Integration.targets to C:\Developments\products\axisante5.sonarqube\bin\targets
11:57:29.035  Creating config and output folders...
11:57:29.036  Creating directory: C:\Developments\products\axisante5.sonarqube\conf
11:57:29.037  Creating directory: C:\Developments\products\axisante5.sonarqube\out
11:57:29.044  Fetching analysis configuration settings...
11:57:29.045  Downloading from https://sonarqube.cgm.ag/api/server/version...
11:57:29.468  Fetching properties for project 'cgm.fr.axisante.Hydra' from https://sonarqube.cgm.ag/api/settings/values?component=cgm.fr.axisante.Hydra...
11:57:29.469  Downloading from https://sonarqube.cgm.ag/api/settings/values?component=cgm.fr.axisante.Hydra...
11:57:30.165  Downloading from https://sonarqube.cgm.ag/api/languages/list...
11:57:30.546  Fetching quality profile for project 'cgm.fr.axisante.Hydra' from https://sonarqube.cgm.ag/api/qualityprofiles/search?projectKey=cgm.fr.axisante.Hydra...
11:57:30.549  Downloading from https://sonarqube.cgm.ag/api/qualityprofiles/search?projectKey=cgm.fr.axisante.Hydra...
11:57:31.472  Failed to request and parse 'https://sonarqube.cgm.ag/api/qualityprofiles/search?projectKey=cgm.fr.axisante.Hydra': Sequence contains more than one matching element
Unhandled exception. System.InvalidOperationException: Sequence contains more than one matching element
at System.Linq.ThrowHelper.ThrowMoreThanOneMatchException()
at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable1 source, Func2 predicate)
at SonarScanner.MSBuild.PreProcessor.SonarWebService.<>c__DisplayClass6_0.b__0()
at SonarScanner.MSBuild.PreProcessor.SonarWebService.DoLogExceptions[T](Func1 op, String url, Action1 onError)
at SonarScanner.MSBuild.PreProcessor.SonarWebService.TryGetQualityProfile(String projectKey, String projectBranch, String organization, String language, String& qualityProfileKey)
at SonarScanner.MSBuild.PreProcessor.TeamBuildPreProcessor.FetchArgumentsAndRulesets(ISonarQubeServer server, ProcessedArgs args, TeamBuildSettings settings, IDictionary2& serverSettings, List1& analyzersSettings)
at SonarScanner.MSBuild.PreProcessor.TeamBuildPreProcessor.DoExecute(ProcessedArgs localSettings)
at SonarScanner.MSBuild.PreProcessor.TeamBuildPreProcessor.Execute(String[] args)
at SonarScanner.MSBuild.BootstrapperClass.PreProcess()
at SonarScanner.MSBuild.BootstrapperClass.Execute()
at SonarScanner.MSBuild.Program.Execute(String[] args, ILogger logger)
at SonarScanner.MSBuild.Program.Execute(String[] args, Boolean showDeprecatedWarning)
at SonarScanner.MSBuild.Program.Main(String[] args)

Could you kindly format your question and code properly? It would be helpful for those who are trying to assist you. As someone who is seeking help, it would be appreciated if you could put in a minimum effort.
I think MSBuild.SonarQube.Runner.Tool is a different project and outdated. You can use dotnet-sonarscanner and set the SonarBeginSettings.UseCoreClr property to true. This will use Sonar's official scanner.

@lbensch MSBuild.SonarQube.Runner.Tool in version 4.8 is outdated. Please use the latest scanner from https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarscanner-for-dotnet/ as @HofmeisterAn mentioned in this comment.

@HofmeisterAn Sorry, it's not code that I posted but a log. As for my question, it seemed to me that it was clear, sorry if you didn't understand it, I understand why you don't bring any interesting element to my problem.
@twenzel Thank you very much, you saved me! it works perfectly well.


AVRO-2925: add support for UUID in compiler

Jira

[x] My PR addresses the following Avro Jira issues

https://issues.apache.org/jira/browse/AVRO-2925

Tests

[x] My PR adds the following unit tests
unit tests to validate compiling idl file with uuid to avpr according to Avro 1.10.0 UUID logical type.

Commits

[x] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x]  No new documentation needed

+1 from me


Missing key(s) in state_dict

From yesterday I'm receiving this message:
File "inference_video.py", line 81, in <module>     model.load_model(os.path.join(os.path.dirname(os.path.realpath(__file__)), 'train_log'), -1)   File "/content/arXiv2020-RIFE/model/RIFE_HDv2.py", line 164, in load_model     convert(torch.load('{}/flownet.pkl'.format(path), map_location=device)))   File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 1052, in load_state_dict     self.__class__.__name__, "\n\t".join(error_msgs))) RuntimeError: Error(s) in loading state_dict for IFNet: 	Missing key(s) in state_dict:
The main problem is: copying a param with shape torch.Size([8]) from checkpoint, the shape in current model is torch.Size([4]).
Does anyone changed the shape of the model ?
EDIT:
on line 79 of inference_video.py I changed RIFE_HDv2 to from model.RIFE_HD import Model and it works as before.

Hello, I updated the model to HDv2, so you need to download new zip of parameters to fit the new code.


Also support arrays wherever $ supports variadic parameters

For example I cannot currently do this:
$.omit(myDictionary, keys: ["one", "two", "three"])
But must instead do this:
$.omit(myDictionary, keys: "one", "two", "three")
For lots of design paradigms (e.g. my blacklisted set of keys is shared and represented as an array, or I've derived the list of keys from an API and don't have them as individual values), this is frustrating.
This thread indicates that there is no language-specific way to pass an array into a variadic parameter. Thus I think $ should support this (the variadic versions can call into the array versions)

Good idea. Will add.

awesome

+1


tests: add defrag datalink tests

Bug: 6887. https://redmine.openinfosecfoundation.org/issues/6887
Bug: 6932. https://redmine.openinfosecfoundation.org/issues/6943
Includes a disabled test for https://redmine.openinfosecfoundation.org/issues/6942

Includes a disabled test for https://redmine.openinfosecfoundation.org/issues/6942

Why ?
Should not this test be included when you get a PR to fix this ?
Otherwise, it looks like you should set min-version to 8 for the first round ;-)


Thank you!

Not an issue, just wanted to thank you! It builds and works very fine!
Removing my tasmota wall sockets from the lighthouses now :)

I use tasmota and homeassistant to control the hmd socket power

Me too :)

whoops, didn't mean to leave this open for so long - sry...


simulator can take user-defined random number generator

StableRNG used in tests and doc

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (056794b) to head (34600eb).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #12   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          243       247    +4
=========================================
+ Hits           243       247    +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Can't Use FontAwesome Icon

I am not able to use fontawesome icon. Because You override Icon css.

I didn't overwrite any font-awesome icon class as my icon class name is icon-* which is different from font-awesome ('fa-*')

There are some icons in fontaewsome which uses icon- Please provide some solution .

@shubh4git
Which ones use icon-?

There is icon-star, icon-speedometer

Thank You For this Wonderfull DatePicker I have solved my problem By Overiding Your picker.css File.


Cannot be accessed using chrome as https,but firefox is fine.

$ docker version

Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 15:54:52 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 15:54:52 2016
 OS/Arch:      linux/amd64

Absolutely you can use chrome to access harbor.You need click "advanced"
then click "Proceed to <IP_ADDRESS> (unsafe)"

@zzwangsh , does it solve your problem?

No response after nearly a month, close.

@reasonerjt ,sorrry for the late reply, Updated version works without errors,thanks.


Getting the import error

python bin/run_analysis.py
Traceback (most recent call last):
File "bin/run_analysis.py", line 7, in
from src.run_analysis import analyze, render_results_as_images
File "/DeepOSM/src/run_analysis.py", line 6, in
import label_chunks_cnn_cifar
File "/DeepOSM/src/label_chunks_cnn_cifar.py", line 11, in
import tflearn
File "/usr/local/lib/python2.7/dist-packages/tflearn/init.py", line 21, in
from .layers import normalization
File "/usr/local/lib/python2.7/dist-packages/tflearn/layers/init.py", line 10, in
from .recurrent import lstm, gru, simple_rnn, bidirectional_rnn,
File "/usr/local/lib/python2.7/dist-packages/tflearn/layers/recurrent.py", line 8, in
from tensorflow.contrib.rnn.python.ops.core_rnn import static_rnn as _rnn,
ImportError: No module named core_rnn
and this
File "bin/run_analysis.py", line 7, in
from src.run_analysis import analyze, render_results_as_images
File "/DeepOSM/src/run_analysis.py", line 6, in
import label_chunks_cnn_cifar
File "/DeepOSM/src/label_chunks_cnn_cifar.py", line 11, in
import tflearn
File "/usr/local/lib/python2.7/dist-packages/tflearn/init.py", line 4, in
from . import config
File "/usr/local/lib/python2.7/dist-packages/tflearn/config.py", line 5, in
from .variables import variable
File "/usr/local/lib/python2.7/dist-packages/tflearn/variables.py", line 7, in
from tensorflow.contrib.framework.python.ops import add_arg_scope as contrib_add_arg_scope
ImportError: cannot import name add_arg_scope
while running the github project https://github.com/zilongzhong/DeepOSM
In this one I am able to create training data successfully but not able to run_analysis.py and while running I'm getting this error and

That looks like an old fork.


sim: Add print support

Ping @jix since they expressed interest in this support.
Ping @kivikakk, @mwkmwkmwk should they want to double check the triggering semantics.

Changed this from being a draft since it could be ready for all I know.


descriptor: drop to_string_no_chksum method

This method has been made redundant by the {:#} display specifier since 7577e8ceda6d7c83be4f4422ec9be39c11f9050c two years ago. It is poorly named, inefficient since it always requires allocating a String, and also broken because it uses debug display for keys.
All of our unit tests were converted over to use :# which is why it wasn't noticed that this method didn't work.
Fixes #34
Fixes #85

@apoelstra I can't merge here

Added your ability to merge. Merged this after testing merge commit. There are linter failures on master right now which I'll fix in another PR (for now I disabled the doc lints for my local tests).


Cannot create manifest files to be used with kustomize

Hello Team,
I would like to use kustomize for managing the external secrets and so I wanted to have the manifest files.
I tried creating them using helm template but I am getting below error:
Error: chart requires kubeVersion: >= 1.19.0-0 which is incompatible with Kubernetes v1.16.0
What can I do to generate files?

What is your helm version? It is compiled against a specific version of kubernetes. Try using the latest helm version.
You can also try helm template --validate to pull the Kubernetes version from the kube-apiserver via kubeconfig.
Please Let me know if that helps.

Hi @moolen ,
upgrading helm version fixed this issue. Thank you.


After command "ng update" from 11 to 12: mixin typography-hierarchy undefined

I'm trying to update our Angular application with Material to version 12.0.1. For this I use the update docs/steps from Angular (https://update.angular.io/?l=3&v=11.0-12.0). Everthing is successfull, but I still have one error. During the update some files has been changed automatically. In one of the files this happend:
Added:
@use '~@angular/material' as mat;
Changed from:
@include mat-base-typography($my-sass-var, 'body');
Into:
@include mat.typography-hierarchy($my-sass-var, 'body');
Result:
typography-hierarchy mixin undefined
Environment

Angular: 12.0.1
CDK/Material: 12.0.1

It looks like we forgot to expose the mixin through the new theming entry point. We'll have a fix for this in the next patch version.

It looks like we forgot to expose the mixin through the new theming entry point. We'll have a fix for this in the next patch version.

Thank for adding.


Validation does not work properly in Version 4.0.0

In Version 4.0.0 the validation of the ChipCombobox does not work if you use it with a binder and configure it with asRequired().
The field isn't marked red and doesn't show any error on tab change, but if you select a value and clear the box afterwards it seems to work again.
Could it be connected to the initial value setting?
Details on UI:

simple form with ChipCombobox, Textfields, etc.
bound with Binder
shown in a dialog

The problem is caused by setting a HashSet as the component has an ArrayList as default. When comparing both collections a difference is detected, which should not be the case.

Fixed by https://github.com/xdev-software/vaadin-chip-combobox/commit/eb52f76fc29f5d2a60c9868d53fe673aaf78ac9a


[FS] Removed dedupe code as it filters out legit transactions

Found an original PR that added Distinct() to dedupe transactions: https://github.com/stratisproject/StratisBitcoinFullNode/pull/3362. Not sure why it was needed. Investigating why it was needed.

I'm going to suggest that any change to the history method needs to be tested manually with Stratis Core.
Receive, send, stake, send to self etc.
The proposed PR will break history.

It sounds to me like we need to group UTXO that are part of the same TRX id this will solve both stake and split.

It sounds to me like we need to group UTXO that are part of the same TRX id this will solve both stake and split.

Grouping won't help as it will still include all split outputs and we only want stake to be included. Output index gives us a uniqueness and code quoted above already handles removing coinstake split outputs

Grouping won't help as it will still include all split outputs

Yes that's what we want no? If a trx is sent to us with more then one UTXO we want to show it as one trx, this is what I understand at least.

Yes that's what we want no? If a trx is sent to us with more then one UTXO we want to show it as one trx, this is what I understand at least.

Are you suggesting to remove the current dedupe (line that uses Distinct() and do Group instead using the same criteria as a comparer? This dedupe code was added there originally for a reason, I am not sure what other scenarios it might cover.

Are you suggesting to remove the current dedupe (line that uses Distinct() and do Group instead

yes that's what I am suggesting

I think that we need some elements of both points of view here.

Staking outputs seem to be handled fine - only the +1 portion will get shown in the history. The split UTXOs of a staking transaction are ignored by the code.
I agree that it would be best if the related amounts are grouped. These could occur in either a sending or receiving transaction, so the summation of related amounts could either occur within the loop (i.e. extract all related sends/receives at once and sum amounts), or as a post-process on the resulting list.
There is one strange aspect of the pre-PR code that I am investigating for correctness. If anything comes of it I'll open a PR.

@zeptin @dangershony Updated code to do running totals of the outputs, see if it makes sense

Why are we only showing total of the outputs?
@fenix2222 I talked to you about a potential solution in private, have you tried it?

@bokobza This was proposed by @dangershony and confirmed by @zeptin. See comments above. I don't really have a strong opinion on this one. Either case makes sense, the main thing is to fix reported issue.

This relates to: https://github.com/stratisproject/StratisBitcoinFullNode/pull/3362


Add spectral fitting notebook for 511 line

Great job on this, @eneights! I was able to successfully run everything. Below are some comments to address before merging your PR.
Can you please briefly specify in the notebook which mass model is being used (I guess the Compton sphere), and what the data files are. Most people might not know what these are.
The detector response files should be publicly accessible. They are currently only available on the google drive, which is only accessible for members of the COSI collaboration. Likewise, example notebooks should be easily accessible to everyone. Where will the response files be stored for DC2 (this is probably a question for Andreas)?
This example notebook should be in its own directory:
docs/tutorials/spectral_fits/line_fit
This directory should contain everything needed to run the example, except for files that are too large to store. This is related to the issue that I open here:
https://github.com/cositools/cosipy/issues/81#issue-1922321607
Also, the data files should be publicly available. For now, I think this means putting them on wasabi, and providing the link (but again we’ll need to double check with Andreas).
Can you also move your other spectral fit example to its own directory:
docs/tutorials/spectral_fits/continuum_fit
Why is the orientation file and yaml files in cosipy/cosipy/test_data? The test_data directory should only be for data that is used for testing the code. It should not have data for example notebooks. Please move everything to the directory for this specific example. @israelmcmc Do you agree, or what is your vision on how this should be organized?
“and, for extended sources, shape…” —> and, for extended sources, morphology…
“where $B*b_i$ are the estimated counts due to background in each bin…” I think we need to specify here that ‘i’ is in index for energy.
“Finally, we will fit a Band function:” I’m confused why this is here. Are you really fitting a band function in this example? I thought the example fits a constant source and a Dirac Delta function.
Everything is currently defined relative to test_data.path, including the binned data, which actually isn’t there. It’s better to define everything relative to the specific example directory. This can be easily accomplished as follows:
import os
wd = os.getcwd() # working directory
ori = SpacecraftFile.parse_from_file(os.path.join(wd,”20280301_first_2hrs.ori"))
You can do the same for the yaml files and the binned data. In this case the user just needs to copy the needed files to the example directory. Even better, we should eventually include a line in the notebook that will automatically copy the needed files from wasabi to the users directory.
On my system I need to add the following line in order for the plots to be shown:
%matplotlib inline
This is probably going to be dependent on the user’s system, but it might be good to note that somewhere. This can be included as an option with the imports at the top of the notebook.
Bin data from .tra files: I don’t think this needs to be here. It would be better to just refer to the dataIO example for this.

I agree @ckarwin about the organization of the files. It's not @eneights though, we just haven't been careful about this.
Ideally, the files in test_data should be light-weighted, just what is necessary for the unit tests (most of which we still need to write). Some of these files might be good enough for the examples, so it's fine to use them for that purpose as well. However, if we need bigger files, we should put them on wasabi and provide the link to them. The filenames in the notebooks can be with respect to an arbitrary root folder where the users downloaded the files.
Ideally this should be done programatically. We can make awscli part of the dependencies so the notebooks download the necessary files and setup everything for the user. But that's for later, for now the links to the files is fine.

Sounds good, @israelmcmc. Thanks for the feedback. Indeed, it's not @eneights, I was just meaning in general, but it's good to fix it early.

Thanks @ckarwin and @israelmcmc! I think I implemented all of the changes, but let me know if I missed anything.

Hi Eliza, Thanks for making the changes. There are actually still some comments which haven't been addressed yet.
General users don't have access to the google drive, and so they won't be able to easily run this example without making a big effort to track down the needed files. I just uploaded all the needed data files to wasabi. Please add the following to the notebook:
All needed data files are available on wasabi in cosi-pipeline-public/ComptonSphere/mini-DC2. They can easily be downloaded by running:
python get_data.py (which I sent on slack)
Or if you want, you can probably just put the code in get_data.py directly in your notebook. That will make things very convenient.
Please copy the needed yaml files, ori files, and get_data.py (unless putting in notebook) directly to tutorials/spectral_fits. I actually think it's better to make separate sub-directories for SpectralFit and SpectralFit_Line:
docs/tutorials/spectral_fits/line_fit
docs/tutorials/spectral_fits/continuum_fit
This way each respective directory has all the associated files, and it's very clear what belongs to what.
Once all these files are in place, it will make running the example very convenient and user-friendly.
"The goal is to find the values of X = ..." double check your parameters here. I think you still have the ones for the Band function, which have been removed.
Before you commit the notebook you should collapse the output cell after like.fit(). It's super long!

Also, I already tested the get_data.py script and it's working fine for me. If you end up adding this directly in the notebook, it would be good to test. I think it should be ok, but you never know.

For reference, here is the content of get_data.py:
import os

file_list = ['bkg_binned_data_full_511.hdf5','grb_binned_data_511.hdf5','grb_bkg_binned_data_511.hdf5','Isotropic.511keV.p.binnedimaging.imagingresponse_nside16.area.h5']
for each in file_list:
os.system("AWS_ACCESS_KEY_ID=GBAL6XATQZNRV3GFH9Y4 AWS_SECRET_ACCESS_KEY=GToOczY5hGX3sketNO2fUwiq4DJoewzIgvTCHoOv aws s3api get-object  --bucket cosi-pipeline-public --key ComptonSphere/mini-DC2/%s --endpoint-url=https://s3.us-west-1.wasabisys.com %s" %(each,each))

Will also need awscli:
pip install awscli

Made those changes! I included the code to download the data from wasabi in the notebook, and it seems to be working. The files needed for the continuum fitting still need to be added to wasabi.
The output cell of like.fit() is already collapsed for me.

One more thing, can you go ahead and add 'awscli' to setup.py (https://github.com/cositools/cosipy/blob/main/setup.py), in the list, "install_requires", right after 'threeml'? This will take care of the dependency for copying the files.

@ckarwin Done!


Customise looks

Since FZF_DEFAULT_OPTS is emptied by fzf-lua, is there a way to customise colors of fzf UI elements and pass additional parameters to fzf, such as --margin?

Added an option to specify additional args to fzf with the fzf_args option, can either be specified globally (see the updated README) or per call as below:
lua require('fzf-lua').files({fzf_args = '--margin 10%'})

Btw, tysm for the extensive QA and suggestions :-)

Haha, no problem at all! :)

If you want to add something to FAQ. Came up with this little thing that I am very happy with!
A mapping executing
lua require('fzf-lua').oldfiles({cwd_only = function() return vim.api.nvim_command('pwd') ~= vim.env.HOME end})

Will show all old files when in ~, otherwise it will filter by current dir. :)

If you want to add something to FAQ. Came up with this little thing that I am very happy with!
A mapping executing
lua require('fzf-lua').oldfiles({cwd_only = function() return vim.api.nvim_command('pwd') ~= vim.env.HOME end})

Will show all old files when in ~, otherwise it will filter by current dir. :)

This is quite a cool addition, I was actually planing to work on the README later today, this will def be in it :)

There might be better way to get pwd than vim.api.nvim_command('pwd') but did not look yet.

vim.loop.cwd()


fixing issue while locking elements with bind to single property and async loading

_uiSelectChoiceLocked cannot be assigned to primitive type

Superseded by #1712


Add the ability to use Jurassic as an engine to execute scripts

Since sebastienros/jint has been in beta for 2 years, it will be useful to add the ability to connect other engines. Good alternative - Jurassic. Implementation to be done in separate assembly. You need to add two methods UseJint and UseJurassic to the EngineBuilder.

Added #18 and #19.


Create codeOfConduct.md

This references issue #38

Just realized a duplicate issue was already opened on this at #41

I'm closing this because there is a duplicate at PR #41

I reopened this branch since the header and links were not added in PR #41


Checkmodupdate issue and more

When i write arkmanager checkmodupdate thats come out-
Error: /home/ark/steamcmd/steamapps/workshop does not exist
And i need a cronjob for restart everyday but doesnt work. No warnreason
arkmanager install-cronjob --hour=20 restart --warnreason
thanks for help :)

Please check if ~/.steam/steamapps/workshop or ~/Steam/steamapps/workshop exist.

Please try setting steamdataroot=/home/ark/Steam in arkmanager.cfg

No output when all mods up to date ?

And can you help me pls with the restart ;/

No output when all mods up to date ?

Correct, there is currently no output when no mods need updating.
fcdbe68 adds an "All mods are up to date" output when all mods are up to date.

And i need a cronjob for restart everyday but doesnt work. No warnreason
arkmanager install-cronjob --hour=20 restart --warnreason

--warnreason expects an argument specifying the reason for the restart, and only takes effect if --warn is also specified.


[LiveComponent] Emitting Event to specific instance

Hi,
I have 10 instances of same component in page with live prop $id. I want emit event to only one instacne of this component with specific $id.
Is something like this possible?

It is not possible no, but they maybe can "do" something if they match the id of the event ?

Yes, bud this is trigered reload all 10 instances and i want avoid it because render this component is heavy. Maybe not heavy, but now I have 60 instances on page, Ind i need reload only one.

As Event are really just "strings", did you try to emit something like "foo_42" where 42 is the id in question, and listen to this event in your component 42 ?

Im still not understand what you mean..
I can listen to specific event "foo" like:
#[LiveListener('foo')]
public function foo(#[LiveArg] int $id){}

I can't add id to listener name  like #[LiveListener('foo_42')]. And if all instacnes of compoent have same listener name, then all will be listened for event, that means for all instances of component will be called http request individualy

So there is nothing like that in LiveComponent sorry. The compote works around events, delegation or "in-scope" actions.

Yesm this custom stimulus controller is  good enough for me. thanks


autotools-non-release-build ?

Can someone tell me what this means?
flatpak run --command=flatpak-builder-lint org.flatpak.Builder --exceptions com.dosbox_x.DOSBox-X.yaml
 in dir /srv/buildbot/worker/build-x86_64-5/build (timeout 1200 secs)
 watching logfiles {}
 argv: b'flatpak run --command=flatpak-builder-lint org.flatpak.Builder --exceptions com.dosbox_x.DOSBox-X.yaml'
 using PTY: False
{
    "errors": [
        "module-dosbox-x-autotools-non-release-build"
    ]
}
If you think problems listed above are a false positive, please report it here:
  https://github.com/flathub/flatpak-builder-lint
program finished with exit code 1
elapsedTime=1.308365

https://github.com/flathub/com.dosbox_x.DOSBox-X/pull/10

Found the issue by searching through the linter source code. Had to disable the debugger. This means dosbox-x flatpak will no longer have a DOS debugger.
https://github.com/flathub/flatpak-builder-lint/blob/master/flatpak_builder_lint/checks/modules.py
elif opt.startswith("--enable-debug") and not opt.endswith("=no"):
                        self.errors.add(f"module-{name}-autotools-non-release-build")

dosbox-x uses that flag to enable the debug option for debugging not dosbox-x, but rather dos programs running inside. e.g., this is what you get when debug is enabled:

Please submit a PR to https://github.com/flathub/flatpak-builder-lint/blob/master/flatpak_builder_lint/staticfiles/exceptions.json to exclude your app.


the-foundation: 1.7.0 -> 1.8.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/the-foundation/versions.
meta.description for the-foundation is: Opinionated C11 library for low-level functionality
meta.homepage for the-foundation is: https://git.skyjake.fi/skyjake/the_Foundation
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.8.1 with grep in /nix/store/gnpc1qmr1dy4qzy8sqfg3vhggaa0l5cb-the-foundation-1.8.1
found 1.8.1 in filename of file in /nix/store/gnpc1qmr1dy4qzy8sqfg3vhggaa0l5cb-the-foundation-1.8.1

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

lagrange
lagrange-tui
sealcurses
the-foundation

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gnpc1qmr1dy4qzy8sqfg3vhggaa0l5cb-the-foundation-1.8.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A the-foundation https://github.com/r-ryantm/nixpkgs/archive/4e5e98a3989265af204eac29f93e1c5012506887.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4e5e98a3989265af204eac29f93e1c5012506887#the-foundation

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gnpc1qmr1dy4qzy8sqfg3vhggaa0l5cb-the-foundation-1.8.1
ls -la /nix/store/gnpc1qmr1dy4qzy8sqfg3vhggaa0l5cb-the-foundation-1.8.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages built:

lagrange
lagrange-tui
sealcurses
the-foundation

Maintainer pings
cc @sikmir for testing.

Result of nixpkgs-review pr 307617 run on x86_64-darwin 1

4 packages built:

lagrange
lagrange-tui
sealcurses
the-foundation


Remove default dataproc init script

The script will do this by default, with support for different hail versions.
Relies on: https://github.com/populationgenomics/analysis-runner/pull/644

In the linked PR it looks like the get_init_script_from_hail_version gets a folder, not a script. Does --init just run everything found in that folder?
return f'gs://cpg-common-main/hail_dataproc/{hail_version}/'

Nice catch, that was definitely supposed to return a file. I'll submit a fix.

D'oh saw that on my first pass through but then forgot about it again :-(


Fix/test aws

This PR includes fixes for :

EventBridge setup with multiple triggers to single worker queue.
Deserialisation fixes for Trigger message.
atlantic service endpoint updated
atlantic service's type updated
atlantic get_job_status test added

coverage: 67.965% (-0.05%) from 68.015%
when pulling bce2bf8001d7b8cb5347610272e0d18f9e5af90b on fix/test-aws
into 4b0fce444c65c3217a4094bdcc5955f5d77c97c6 on main.

A few things that I noticed:

Shall we add more informational statements while setting up the cloud? Currently it shows setting up [x] and then setup of [x] complete?
While creating the jobs, we are not saving it in the metrics but we are saving it if the job creation fails. I understand we have metrics on successful completion of the job but shall we have it for creation of the job as well?
Currently in our cloud setup if something breaks in between we have start again, and this would create additional resources on the cloud. I understand this might not be the priority as of now, just putting it out here.

1 & 3. We can for sure, let's take up 1 and 3 together in a separate PR, here's the issue to track this.
2: we are taking metrics on successful as well as failed creation on jobs,
The screenshot below shows sending metrics on completion of a create job of any operation type.


Build multi-platform docker images

Also fixes bug with "/" characters in image names, although chaincode labels now have the same issue since they are used in filenames!
Signed-off-by: James Taylor<EMAIL_ADDRESS>

❤


Setup project structure on Linux

Set up project directories and a Gradle build to begin development.

Done.


Combo Restored

What is your question?
Hello, I actually want to restore the combo text and, in the settings of combo delay and that stuff, change or move the combo text to the position I want. If someone can help me, pls tell me how. I would aprecciate it a lot.

NOTE: I am using the source code.

add(comboSpr);
under
comboSpr.velocity.x += FlxG.random.int(1, 10) * playbackRate;

add(comboSpr); under comboSpr.velocity.x += FlxG.random.int(1, 10) * playbackRate;

But in which hx file???

add(comboSpr); under comboSpr.velocity.x += FlxG.random.int(1, 10) * playbackRate;

I just put add(comboSpr) and in the settings dosen't appear for change the postions

add(comboSpr); under comboSpr.velocity.x += FlxG.random.int(1, 10) * playbackRate;

It dosen't see the combo text on the settings of combo offset for change the position

because it ain't in there at all

because it ain't in there at all

Oh... ok. Thanks for the help anyways, ty 😊

yeah, np


Fix mff crop no preload

closes #6031
ok for you @petergrey75 ?

Works for me too 👍, thnx @agramfort and @petergrey75!


Move to Lerna

Lays the groundwork for a port to lerna, which makes it easier to support things like Preact (#194) as additional packages and splits up the current packages (#83). PRing for visibility and comment.

Currently leaving "global dev tools" in root package.json (karma, eslint)
Karma tests have been split per-package, but are still triggered via npm test

Right now this will install all global dev tools, bootstrap the packages and run the karma tests:
npm i
lerna bootstrap
npm test

Bootstrapping builds and links glamor into three other packages for tests, providing a nice proving point for how cross-project dependencies will work when developing.
current packages are:
babel-plugin-glamor glamor-jsxstyle     glamor-reset
glamor              glamor-ous          glamor-styled
glamor-aphrodite    glamor-raw-css      glamor-utils
glamor-autoprefixer glamor-react

I hope we can review that next week. Thank you so far!

@donaldpipowitch @threepointone Since this is a fairly impactful PR, what can I do to make this easier on you all? Happy to write more documentation, go into more detail on what's happening in the PR, etc.

Coincidentally I looked into your PR some hours ago and I'd like to use it as a new starting point for a new major version of glamor. I just recently got push rights to glamor so I don't want to go all in without asking @threepointone for some higher picture, because he already started a v3 branch some months ago.
I sketched out what I would like to do with @otbe here https://github.com/threepointone/glamor/issues/83#issuecomment-278260043. As far as I understand @threepointone would like to take a little break from this project at least for now (- please clarify this, if I misunderstood this). So I guess he'll be fine with https://github.com/threepointone/glamor/issues/83#issuecomment-278260043. If he doesn't respond in the next days I'll probably just create a new-v3 branch or something like that and just start with the ideas from https://github.com/threepointone/glamor/issues/83#issuecomment-278260043 and see how far we can get with that.

@donaldpipowitch Sounds good. I was under the impression that most of the v3 branch stuff was merged into master (the v3 branch is 122 commits behind and 0 ahead).
I'm happy to take on more with regards to #83 and a 3.0 push. My previous thinking was that splitting the packages up was the most impactful thing I could do for 3.0, then could move more easily on the rest. I also use TypeScript at work these days, so would by happy to help port the codebase.

I was under the impression that most of the v3 branch stuff was merged into master (the v3 branch is 122 commits behind and 0 ahead).

Yeah, that is my impression, too. Good to hear the same from someone else. I guess we can just remove the old branch then :)

@ChristopherBiscardi I've created a new v3 branch based on your PR. I cherry picked two commits (only for docs) since the beginning of your PR - I think these two were the only new ones. I also added a postinstall to bootstrap lerna. I have little to no experience with lerna, so maybe this is some bad practice or something, but from my point of view it looked useful. I also updated the .gitignore to match the new project structure.
I hoped GitHub would notice that a new branch based on the PR exists and it would offer me to close this PR. Sadly this is not the case, so I'll close this PR manually. But your commits and history is preserved in the v3 branch of course which will be merged into master someday when https://github.com/threepointone/glamor/issues/83 is finished.
Going on from here I'll try to write a small migration guide to the new package structure, deprecate the old modules and publish a new v2 patch version and a v3 prerelease. 👍


Failing to optimize getprop

Closure Compiler with advanced optimizations fails to optimize the expression {a:0}.a to 0 in some cases.
When running:
echo console.log({a:0}.a) | java -jar closure-compiler-v20191027.jar -O ADVANCED

I get console.log({a:0}.a);
but when running:
echo console.log({a:0}.a===0) | java -jar closure-compiler-v20191027.jar -O ADVANCED

I get console.log(!0);.
It seems that the compiler knows that {a:0}.a can be reduced to 0, but doesn't always do it for no apparent reason.

Internal issue created: b/144415023.


CDNS API returns a 404 when there are no SSL Keys

The API method: /api/1.2/cdns/name/{cdn_name}/sslkeys.json returns a 404 if there are no SSL keys defined for the CDN. This should probably return an empty list or an error message. If the CDN does include 'https' delivery services then it should probably return an error.

a 404 implies "bad route" and i'd only expect to see that if you put in an invalid cdn_name
if the cdn_name is valid and there are no ssl keys, then an empty array would be expected.

may need to research if this is still applicable in API 2.x+

It does look as though there's no situation in which Traffic Ops would return a 404 from that endpoint; @ajschmidt can you confirm if this is still an issue?

i'll close. @ajschmidt can reopen if necessary. thanks for checking @ocket8888


Add vision support

Since the OpenAI API now has vision in beta, and we could use LLaVa locally.
Might be a lot of work, or might be super easy.
Question is, what would it be useful for?

#51: Xvfb to understand display/output and make a E2E desktop agent
#52: Screenshot with browser tool

Can be used to take screenshots of developed webapps for visually-aided autodebugging

Have it review plot outputs for correctness and to inspect results

Could be useful for data science, but reading a good plain text output might still be superior

Now works after adding the vision tool: https://github.com/ErikBjare/gptme/commit/597c66c5ad5860b92e022634e551659629b3b80e
Also merged the screenshot tool: https://github.com/ErikBjare/gptme/pull/92

Anthropic just announced their computer use stuff: https://www.anthropic.com/news/3-5-models-and-computer-use
Basically same thing lol, although I should implement clicks and input (with pynput?), and let it run in Docker at 1280x800 resolution.

I saw that @simonw had implemented support for not only images, but also video and audio in https://github.com/simonw/llm/releases/tag/0.17: https://x.com/simonw/status/1851280825662521370


EPERM errors with Forge v7 on Windows CI

We are experiencing EPERM errors on Windows CI with the restructured repo (#623).  The workaround currently in place is a downgrade to Forge v6.4.2, we should investigate why the errors were not observed before the restructuring - possibly caused indirectly by turborepo?
Example run: https://github.com/webdriverio-community/wdio-electron-service/actions/runs/9625513133/job/26550474379?pr=623
Forge issue: https://github.com/electron/forge/issues/3448

Fixed by ensuring the forge builds are not parallelized.


Grammatical and spelling errors in the Terms of Service and Privacy Policy section

Grammatical and spelling errors in the Terms of Service and Privacy Policy section, I want to resolve them, Kindly assign me this issue
Add Screenshot

assigned @HimanshuNarware
Make sure on creating PR branch name should be of specific format,
VOVOCA-issueNumber
e.g for this issue number is 5 so
VOVOCA-5

@varun-singhh sir i want to work on this issue under gssoc'23


@deprecated annotation

Hi Minko,
Are you planning to implement the generic decorators? What features you're planning to add here?
I thought of implementing (Sending PR) the @deprecated to console.warn a deprecation warning on the console since it globally used in Aspect oriented languages like: Java.
Any interest in that?
Thanks

Or https://github.com/jayphelps/core-decorators should be the answer?

Yes, use core-decorators. You can take advantage of aspect.js in order to use the AOP paradigm in your application development.


compute sanitizers

We should add CI runs that check the kernels and the end-to-end model using compute sanitizers

@ngc92 - do you have some command line/options in mind that you'd like to try first?


galer: 0.1.0 -> 0.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dwisiswant0/galer/releases.
meta.description for galer is: Tool to fetch URLs from HTML attributes
meta.homepage for galer is: https://github.com/dwisiswant0/galer
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.2.0 with grep in /nix/store/lx7b7swvj2j46xnbyb3f182pxh719imr-galer-0.2.0
found 0.2.0 in filename of file in /nix/store/lx7b7swvj2j46xnbyb3f182pxh719imr-galer-0.2.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

galer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lx7b7swvj2j46xnbyb3f182pxh719imr-galer-0.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A galer https://github.com/r-ryantm/nixpkgs/archive/ab58dc04c31544b159691cc9c1146f6e5a389b2a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ab58dc04c31544b159691cc9c1146f6e5a389b2a#galer

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lx7b7swvj2j46xnbyb3f182pxh719imr-galer-0.2.0
ls -la /nix/store/lx7b7swvj2j46xnbyb3f182pxh719imr-galer-0.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

galer

Maintainer pings
cc @fabaff for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 357561

x86_64-linux

:white_check_mark: 1 package built:

galer


Fine tuning joystick parameters to reduce miskeys.

Keith, here is the PR we discussed the last days.
Thank you for all the support! Hope it helps.

Looks good to me! @SeedSigner and @newtonick, give these updated settings a try. Nearly imperceptible longer delay for long joystick hold before it starts continuously moving across the keyboard or down a list. But that tradeoff should make individual joystick moves less likely to accidentally trigger the repeat mode.
tldr: less fiddly joystick action.
If it gets the thumbs up, merge this into 0.5.0-pre1 and then I'll pull it into my 0.5.0-pre2 branch.

Thank you for your work on this mauricio! I was able to load your patch-1 branch and played around with it, mostly in Settings > Advanced, to get a feel for the revised mechanics. I think the slight delay before proceeding to a sustained press is perfect. This will be especially useful in the keyboard UI, where I've encountered double-presses in the past. Thank you again, seems great, going to let @newtonick chime in as well if he wants.

Glad to hear it! Keith taught me a lot in the process, and came up with the final value as well, but I'm happy to help with my grain of sand :)

Looks like we're good on our end, appreciate this.


Won't compile on ZNC 1.6.1

I am getting loads of errors trying to compile the cpp file on ZNC 1.6.1. If needs be I will submit the entire failure log from the compilation.

Use the python module instead, https://github.com/jreese/znc-push/raw/python/push.py as last time I checked the cpp branch wasn't going to get any new features.
@jreese could you change python as the default branch?

Also duplicate of at least https://github.com/jreese/znc-push/issues/143 and https://github.com/jreese/znc-push/issues/141

Well how would I then build Push.py so that it works?. I am only used to working with .so modules.

You don't build python modules, you just drop the .py to either module folder and /msg *status loadmod push or check the box at webadmin.
You must load the global modpython module first for Python modules to appear (same with modperl), it's a global module. If you don't have it, recompile ZNC with --enable-pythonor install some package from repos of your distribution, probably znc-pythonor something.

FWIW, I was able to compile the C module against 1.6.1 without any errors.  There were warnings from some of the ZNC libraries, but nothing that prevented znc-push from building and loading into ZNC.


HTTP 404 Not Found: https://packages.microsoft.com/config/debian/10/packages-microsoft-prod.deb

[Enter feedback here]

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

ID: 7c3310a1-6a2e-ca98-9618-8f3d729eafdd
Version Independent ID: ab01f0aa-d1c0-df64-b0f9-ee211d45001f
Content: Install .NET on Debian - .NET
Content Source: docs/core/install/linux-debian.md
Product: dotnet
Technology: dotnet-install
GitHub Login: @adegeo
Microsoft Alias: adegeo

This should have been fixed now per https://github.com/dotnet/core/issues/6381#issuecomment-863274298

😊 Thanks a lot for the reply!
✅ I do confirm the issue is resolved.


Allow passing extra arguments to node with project start command

I hope you find this feature useful.
In the current implementation this overrides the other nodeArgs like "debug" and "debug-brk", which is something I can approve if you intend on merging this at some point.

Yes, I think this would a useful addition if we can make it play nice with the other options. Thanks!


What is the Node.js version requirement for 4.x?

First, I want to start off with a thanks for all the work you guys do.
I have a question that came up after I tried upgrading to the latest 4.x patch version of 4.7.4: what Node.js versions does this module actually support? This is because suddenly it seems there is a dependency in handlebars that requires Node.js 8+, but the declaration in handlebars is still quite low, at Node.js 0.4.7+ (https://github.com/wycats/handlebars.js/blob/v4.7.4/package.json#L21).
Now, I certainly have not tried to run this module with Node.js 0.4, haha, but I seem to be suddenly having CI failures with Node.js 6, related to the yargs package.

@ErisDS hey👋 I'm the maintainer of yargs. I saw the recent handlebars update that migrates from optimist to yargs (which is exciting) ... but<EMAIL_ADDRESS>requires Node 6, so might be breaking for some handlebars users (based on your engines field).
yargs@15 should work for Node.js 6 (we haven't dropped Node 8 yet).
What are the version support goals for handlebars, I could work with you to target a slightly older version of yargs (but can't support all the way back to 0.4).
I might just be tempted to call this a major change for people.

There are actually tests that should have failed in this case, but even though I can see the error messages hidden in the Travis log, the build itself did not fail.
The test tries to use the handlebars CLI with node versions starting at 0.10.
@ErisDS I didn't see this coming. Shall we revert?

@nknapp @ErisDS I think it could be fairly disruptive to folks if you don't revert, what if you reverted, and made it a major with an engines update?
You could install yargs@14 which is not vulnerable, and supports back to Node 6.... But both Node 6 and 8 are EOL, and will no longer take patches. So I would put some thought into what your version support goals are (0.4 is unlikely to be able to be targeted by a patched version of optimist or yargs without a good chunk of work).

@ErisDS I have fixed the integration tests in #1669

@dougwilson thanks for bringing this to our attention ❤ Could you explain where and why you're running against Node v6 just so we have a better understanding?
Me and @nknapp have had a chat and think that it's time for Handlebars' extensive Node compatibility  to end as there aren't enough maintainers and quite frankly, I doubt there's any need for support < v6.
What I'm going to do today is update the compatibility to be minimum Node.js v6 for now.
I'll also downgrade yargs to v14 and merge @nknapp's changes to fix the tests.
This should give us a working version that supports a sensible but very wide range of Node versions and doesn't have the minimist issue.
We'll support v6 & v8 for a short while longer and determine a strategy and timeline for dropping those internally that we are comfortable with, based on any feedback from the community.
@bcoe there's no expectation on our part that you would do any extra work to continue to support us on yargs v14. We really, really appreciate you showing up here today, joining the conversation and clarifying that yargs v14 would work and is secure. It has been immensely helpful ❤

Also came here since we are experiencing issues on node v6.. our deps:
<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>Thanks for the solution you are proposing @ErisDS, that should work for us too!

To be clear, I am fine with whatever your support plan is, but to put it another way: can you please release the requirement of 6+ as a new major version of this module? Releasing as a path is very painful, as we have so many things that are using ^ in package.json files thanks to that being the default npm behavior.

The changes discussed here have been made and shipped in 4.7.5. Node.js support is now set to v6+ for 4.x, yargs is pinned to v14.
Are you still using <v6 somewhere that this will actively impact?
The idea of this change, rather than going straight to v10+ is that it should be enough to provide realistic compatibility within the constraints we have.
I'm under instruction not to do major releases, so it's this or going back to having insecure dependencies unless someone else has a bright idea.

Are you still using <v6 somewhere that this will actively impact?

Yea, I have a bunch of apps on an internal PaaS that this has been breaking on, since these apps all were just made a long time ago, with defaults of using ^ by people... Some of the instances of handlebars I can go through and pin, which I've been trying to do all day today, but others are through sub dependencies that I still need to figure out what the course of action is.
The worse thing about this is the security issue wasn't really an issue with this particular module, just flagged due to the use of a dependency... I would have taken that risk :) Now my next few weeks are just going to be the tedious work of trying to make our apps deployable again... I really wish you guys would be sympathetic with the work this is adding here, and I think I am likely just the tip of the iceberg here (someone posted in the thread on their own accord so far, even), as it's only been like 1 day...

@dougwilson I'm not unsympathetic to that at all. I'm genuinely sorry that this has caused you so much pain.
Ultimately, all this new security reporting tooling is nice but it's definitely overbearing. Pretty much every piece of software I maintain now has multiple flags against it, largely for dev dependencies that affect no one. There's months of work needed to swap dependencies like was done here and I was incredibly grateful that in this case the work was done for us. So I think our pain is coming from the same place...
With this module, we're stuck between a rock and a hard place. Do we favour the people whose builds are failing on npm audit or do we favour people whose builds are failing because we fixed the audit issue by dropping compat for (very) out-of-date software?
Also, I understood from what you were saying that v6 support was going to be enough. Again, I'm sorry that it's not enough in your case. As I said I'm pretty out of ideas for what to do.

I mean, if you just release as a major version, then everyone wins, right? Just bump your major of handlbars if you don't want the warning, otherwise you now can make the decision to ignore it?

Or, maybe an alternative solution: if I could put together a pull request that both fixes the security alert and restores the former Node.js version support to the 4.x line, would it be accepted in the general sense? Obviously it'd have to be reviewed and live up to whatever the requirements are, but perhaps if you're unwilling to just publish as a new major version, and since I already have a lot of work ahead of me on my side, if you're open to such a pull request I can move my efforts to pursue that course?

@ErisDS thanks for your hard work here ❤
I tend to agree with @dougwilson, that it's probably worth releasing this as a 5.x, with an explicit commit that updates the engines field (like this.
truly appreciate the hard work that you're doing for the community.

Hi @ErisDS I'm sorry if you believed that Node 6+ was the only thing I was needing -- I don't believe I said anywhere that Node 6 was my only issue. At the time I posted, I noted that I was having CI failures with Node.js 6. You then did ask if Node.js 6 was all I needed, but then before I had the chance to respond, it seems you took my non-immediate-response as an affirmative? I was trying to gather the data you asked for on the versions, and there are a lot of apps I need to go through...
So my response was to please do a major release, but now it feels like I am to blame for not responding before you made the Node.js 6 release? That makes me feel bad...

I'm going to assume my proposal in https://github.com/wycats/handlebars.js/issues/1668#issuecomment-608071911 is going to be rejected, so I'm going to step away from participation in this thread... I'm sorry for the trouble I caused by what I thought was an honorable request. Please forgive me for stirring this up.

We have discussed this and agreed that we want to support Node.js LTS and current versions in general and that dropping older Node.js versions should not be considered to be a breaking change.
I think it was good to raise the issue (but it wasn't me who had the extra work due to the misunderstanding, so @ErisDS might have another opinion here). But this topic would have come up anyway at some point and at least now, we have a common point-of-view towards this. It will be documented in the README as well, when #1671 will be merged.
So, even if the solution is not the one you wished for, some good has come out of it.

@dougwilson you don't need to apologize for raising the issue!
As @nknapp pointed out, had you not raised it, we wouldn't have clarified our policy. Hopefully clarifying the policy will help a future person like you avoid some frustration.
Seriously, great thanks for bringing up your real-world pain and helping us work through it.

I would recommend against treating bumping the supported Node.js runtime anything but a breaking change. FWIW, Node.js does not do this.

The conversation is a bit confusing now since @dougwilson removed his messages, but I want to also add that the inability to both bump the dependencies to a version without the minimist CVE and maintain semver with regards to node version support is NOT a problem with this package, it is a problem with the reporting of the minimist dep.  We should fight for removal of that  CVE over breaking an important dependency's ability to follow semver properly.

It's a bit impossible to adequately weigh in on this issue but from the conversation it would appear to be a combination of issues stemming from the minimist fiasco and figuring out which Node.js LTS version to support?
To be honest, at this point, I'd be very happy for the CVE for minimist to be revisted and revoked. That said, as @mcollina recommends, bumping the minimally supported Node.js version should always be a breaking semver-major change.

The CVE for minimist is hugely disruptive. It has flagged almost every single package I maintain whilst (to the best of my knowledge so far) being exploitable in none of them.

To be honest, at this point, I'd be very happy for the CVE for minimist to be revisted and revoked.

Is this a genuine possibility?

I don't know. It is worth looking into.

@isaacs or @darcyclarke, is there something we can do on the registry reporting side here?  Assuming that revoking the actual CVE is not an option (as it is probably valid), can we stop reporting on it in npm audit?  What can be fixed from this seems to have been taken care of, but continuing to report on this is just causing unnecessary pain.

@wesleytodd we've got an "Open RFC - Deep Dive" call queued up for today at 2pm ET about "resolutions". I imagine the conversation will touch on the existing proposal for us to support resolving/ignoring audit notices as well as the broader topic of resolving peer/unlisted deps. I encourage folks to join the call if their interested or just want to sit in.
Circling back to the question speicifically though, no I don't think there's anything we'd do on the registry side to revoke a valid CVE. Again, I believe a better way forward would be to provide a mechanism for the community - especially maintainers - to ignore/whitelist their usage of a dep against unnecessary noise.

This particular CVE, combined with the fact that mkdirp 0.5.1's dep on minimist was pinned to an unpatched version, and that mkdirp is so widely used, highlighted a shortcoming in the current npm audit fix capabilities, where it is unable to properly diagnose the problem as being resolvable.  (In this case, npm update mkdirp --depth=9999 would fix all cases that I've seen so far.)
The good news is that npm audit in npm v7 will diagnose this properly, and thus npm audit fix in npm v7 will fix the situation in this class of cases.
Another aspect to this is that npm audit fix in v6 does not automatically fix some nested metadependency issues that are defined in a package-lock.json or npm-shrinkwrap.json file, and improperly implicates top level deps that originally triggered those metadeps to be loaded, even if they did so with a version range that includes the fix.  So, it looks like nyc is wrong for depending on a vulnerable version of minimist, even though it's several levels deep, and fully upgradable.
One thing we are considering is actually creating an advisory against mkdirp 0.4.1 - 0.5.1, so that users of mkdirp will see that they can update, but it's not entirely clear that this will address the issue, and implementing this "meta-advisory" in a general way can be both tricky and extremely time consuming, given the scope of our registry and the interconnectedness of the dependency graph.  There are technical solutions to be able to address this more elegantly, which we'll be exploring in the near future, I'm sure.

Since this is dying down now, and is fixed in this library via #1672, it seems fine to forego more conversation here.  In the future hopefully the changes in npm will help make this not as painful of an issue!

@wesleytodd totally get not carrying on the conversation here, but I'm still fighting the minimist CVE across countless packages, and so would be interested to know where I can follow along with what happens with this.


Ability to save macros in .vimrc

Please make sure this feature request is within the scope of this plugin.

[ x ] I understand that if my request is about supporting some Vim feature, it probably belongs here.

Describe the feature that you'd like:
A clear and concise description of what you want to happen.
let @a = "dw"
Additional context:
Add any other context or screenshots about the feature request here.

I found a workaround. You can bind vim with singular commands and then use the "shell commands" community plugin to run a zsh script that keystrokes your vim binding for you, and this plugin has the ability create hotkeys which you can use obcommand for.

why don't you just bind this to a keymap?
eg nmap A dw or maybe it's `nmap  dw'

Some macros are more complex than that. For example, in my normal .vimrc I have a macro to surround a single word with code quotes, as follows:
let @c='i`^[wea`^['

where ^[  is the special escape character, entered using ctrl+v -> esc.
Currently, every time I launch obsidian I have to save it manually into the reg, since I use it so much. This feature would be extremely useful, since I have plenty more macros like this one coming from my time using vimwiki. Thanks.


connection gets repeatedly closed

Description
Even when there are no requests coming, it repeatedly closes and opens connection.
Then you get output like this:
INFO servicex-fab rucio_did_finder None Stack terminated due to StreamLostError: ("Stream connection lost: ConnectionResetError(104, 'Connection reset by peer')",) INFO servicex-fab rucio_did_finder None Closing transport socket and unlinking: state=2; <socket.socket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('<IP_ADDRESS>', 60114)> ERROR servicex-fab rucio_did_finder None Unexpected connection close detected: StreamLostError: ("Stream connection lost: ConnectionResetError(104, 'Connection reset by peer')",) ERROR servicex-fab rucio_did_finder None Failed to connect to RabbitMQ. Giving Up after 13 tries Traceback (most recent call last):   File "/usr/lib/python3.9/site-packages/servicex_did_finder_lib/communication.py", line 197, in init_rabbit_mq     _channel.start_consuming()   File "/usr/lib/python3.9/site-packages/pika/adapters/blocking_connection.py", line 1866, in start_consuming     self._process_data_events(time_limit=None)   File "/usr/lib/python3.9/site-packages/pika/adapters/blocking_connection.py", line 2027, in _process_data_events     self.connection.process_data_events(time_limit=time_limit)   File "/usr/lib/python3.9/site-packages/pika/adapters/blocking_connection.py", line 825, in process_data_events     self._flush_output(common_terminator)   File "/usr/lib/python3.9/site-packages/pika/adapters/blocking_connection.py", line 522, in _flush_output     raise self._closed_result.value.error pika.exceptions.StreamLostError: Stream connection lost: ConnectionResetError(104, 'Connection reset by peer')
This happen due to work being done in the main thread.
Here example how it should be done:
https://github.com/pika/pika/blob/0.12.0/examples/basic_consumer_threaded.py

Fixed with migration to celery


feat: create Expression type to store operators with expression and parse_expression to have robust parsing

Expressions
This creates the Expression and AbstractExpression type for attaching operators and potentially other metadata to the expression itself.

Expression{T, N, O, V} <: AbstractExpression{T, N}
Defines a high level, user-facing, expression type that encapsulates an
expression tree (like Node) along with associated metadata for evaluation and rendering.
Fields

tree::N: The root node of the raw expression tree.
operators::O: Operators indexed by the expression tree.
variable_names::V: A vector of variable names used when printing the expression.

This is a user-facing type. It should not be used inside a symbolic regression search code because it results in redundant allocations. However, for returning expressions to the user, it is nicer to have "self-contained" structs.
This means you can do things like
expression = Expression(tree, operators, variable_names)
# ^ Low-level way; but see next section!

expression(X)
# ^ Evaluate

println(expression)

without needing to provide the operators or variable names – they are stored inside the Expression struct.
Previously you needed to keep track of these yourself which is a bit of a pain if you aren't deeply knowledgeable about how everything works.
Parsing
In addition to this, I also add @parse_expression macro. This is a safer and easier alternative to operator overloading for creating Node types.
Basically it works as follows:
using DynamicExpressions

my_op(x) = cos(x^2)

operators = OperatorEnum(binary_operators=[+, -, *, /], unary_operators=[my_op])
variable_names = [:α, :β]  # Or strings

expr = @parse_expression(
    my_op(2.3 * α - β) / (0.5 * β * β),  # Pass an expression that will be parsed into an equivalent `Node`
    operators = operators,
    variable_names = variable_names,
)

X = randn(2, 100)

expr(X)
# ^ This is now valid, because `expr.operators` points to the operator enum.
# Also valid: `eval_tree_array(expr, X)`

println(expr)
# ^ Has the `α` and `β` despite everything being stored as the lightweight `Node` type!

expr'(X)
# ^ Forward-mode gradient with respect to inputs

You can also optionally provide a node_type argument to specify e.g., use of a GraphNode instead of a Node.
This is much nicer because it means you can have multiple sets of operator enums, and generate expressions without worrying about overwriting the global mapping from function to index.

Tagging in case of interest @avik-pal @AlCap23 @rikhuijzer @Moelf

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

4 of 80 (5.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.2%) to 90.5%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Node.jl
4
5
80.0%

src/Parse.jl
0
17
0.0%

src/Expression.jl
0
58
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-4.2%

Covered Lines:
1610

Relevant Lines:
1779

💛  - Coveralls

With my very limited Julia knowledge, this looks like solving the issues I have and probably allowing the end user to later easily create a backbone expression from a parsed formula to feed the search with a seed. I like it.

Tagging in case of interest @avik-pal @AlCap23 @rikhuijzer @Moelf

Thanks indeed for the reminder that I should try out this package. I do have some use-cases where it would be useful for

I'm also thinking about just ditching the @parse_expression altogether in favor of a parse_expression(::Expr, ...) function. It doesn't actually need to have a block of code as input so not sure there is need.


⚠ PrivateHD has degraded performance

In c87aa6b, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2205 ms

Resolved: PrivateHD performance has improved in 1f5349a.


Browser testing (new hotness)

dont worry about old IE

Tested in Chrome 16 (my development browser). Works.

Tested in Firefox 9 (latest stable as of now). Works.

IE9 does not run on XP, so I have no way of testing it.

Works in IE9.


Embrace duel wielding characters (UI)

gm
Most highly active players are using multiple screens or squeezing two tabs into one pane. It might be a good idea to embrace this style of play until the block times are drastically reduced.

Would it be possible to add a tab section near the top of the main page allowing you to segment out different adventurers and quickly switch out runs? This would for sure make the whole experience a lot more engaging.

Thinking about it maybe a way to remove the waiting block when switching characters would actually do the exact same thing

Currently the loading state is attached to adventurer, so It should be possible to switch adventurer while another TX is ongoing.
Are you able to try this?


exportTheme

This PR reverts the change workaround for the absence of a .exportTheme() API.

Coverage decreased (-0.3%) to 97.222% when pulling 4ef152e0f1d12137a43925da56f7d495d86b41a1 on feature/exportTheme into c146fcbcd3449f1c4b60961a99bd1fbb5de601c6 on master.

Coverage decreased (-0.3%) to 97.222% when pulling 4ef152e0f1d12137a43925da56f7d495d86b41a1 on feature/exportTheme into c146fcbcd3449f1c4b60961a99bd1fbb5de601c6 on master.


⚠ ClamAV has degraded performance

In 42639fa, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 463 ms

Resolved: ClamAV performance has improved in 42cdbed.


feature: development to main branch CI

Description
CI flows are required to update main branch.
Criteria:

[ ] Code shouldn't have lint issues
[ ] Deploying in stage server successfully
[ ] Test cases passing (or up-to a threshold)
[ ] Test case coverage report

Approach considered:

Create release branch from the tags created.
Pull request should be made from release branch to the main branch.
Necessary Pull Request Guard Rails should pass.

Lint checks
Testing

This is in short, will update soon.
Additional:
Plan to dockerize entire CI/CD.

Currently putting on hold


Metadata: Preserve FK property name when setting Principal Key

Issue: In this case, the FK property was in shadow state. So when defining the shadow property, we used the principal key's type. Later, HasPrincipalKey changed the principal key properties changing its type but we were losing information about FK properties set explicitly since they were not compatible.
Fix: Preserve old FK properties and reuse them if they were set explicitly and does not have type configured.
Resolves #13300

Updated.

Updated.


Add timelocks module to replace u32 in After/Older

Draft for comments on the approach please. Just the last patch, the rest are other work as I was exploring the space.
Makes an attempt at adding a timelocks module to replace the u32 as described in https://github.com/rust-bitcoin/rust-miniscript/issues/270.

Nice! concept ACK.

Patch 9 could actually go in rust-bitcoin, there is nothing specific to miniscript in it?

Oh, yeah, nice idea. I'd be in favor of bringing timelocks into rust-bitcoin. Not sure how the other maintainers would feel.
Then we could add accessor functions to Transaction that can read the sequence numbers and locktime..

Then we could add accessor functions to Transaction that can read the sequence numbers and locktime..

Please review patch 2 of https://github.com/rust-bitcoin/rust-bitcoin/pull/994, is this what you meant?

This looks great! I did not review it in detail.

Thanks for the review @Kixunil, I believe you may now start to see some of my pain in doing this work :) Its not trivial to code up the LockTime API using miniscript code without knowing miniscript well (which I do not).

LockTime has merged already, closing.


Inline LexiconNER changes

I made a temporary work around to extend the functionality of LexiconNER aux classes in REACH to support the creation of in-memory lexicons, specifically:
https://github.com/clulab/reach/blob/decouple_kb/processors/src/main/scala/org/clulab/processors/sequences/FastInlineLexiconNERBuilder.scala#L10-L23
https://github.com/clulab/reach/blob/decouple_kb/processors/src/main/scala/org/clulab/processors/sequences/InlineLexiconNer.scala
The main "enhancement" was to pass the lexicon as an Map instead of sequence of paths to files. @MihaiSurdeanu suggest the method signature should instead receive an iterator that produces the tuples of the map, which could be already in memory or can be produced lazily.
While they work, they most be ported back here in such a way to reduce code duplication.
For context of the changes, please look at: https://github.com/clulab/reach/pull/750

Thanks @enoriega !
@kwalcock: can you please move this functionality into the LexiconNER classes? Maybe as an iterator rather than a prebuilt Map? But that is not that important, since these lexicons are not huge. Thanks!

I finally saw this and it looks very useful.  So there are three kinds: standard on disk, override on disk, and in memory.  It looks like the in memory version replaces the standard version in this example.  Might it have some other precedence instead?  Should there be a method in which all three are allowed and something to say how the new one relates to the other three, like something for first, middle, or last?

@kwalcock : what do you mean by "override on disk"?
In any case, I think we need to support two functionalities in parallel: load from disk (or resource rather), and load from memory.

IDK what mihai thinks, but that sounds like overkill to me, personally
On Thu, Apr 29, 2021 at 9:36 AM Keith Alcock @.***>
wrote:

External Email
I finally saw this and it looks very useful. So there are three kinds:
standard on disk, override on disk, and in memory. It looks like the in
memory version replaces the standard version in this example. Might it have
some other precedence instead? Should there be a method in which all three
are allowed and something to say how the new one relates to the other
three, like something for first, middle, or last?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/processors/issues/471#issuecomment-829405220,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCMIF6BTTVXUWMGQ47LTLGDHPANCNFSM43NSPP7A
.

I believe @kwalcock means to the two different formats: The "standard" KB file format and the "NER override" file format.
What I did was an adaptation only to the standard file format, the NER is still being loaded directly from disk

For "override on disk" I meant an override KB that is in a file/resource.

I see.
I think we should expect either all of them on disk, or all of them in memory.

It might be done so that you can mix and match.  There are still only two slots, one for standard and one for override, but for each you can choose between memory and file.

I did start working on this last week.  If the situation or context changes, please let me know.

The circumstances remain the same. I will use these changes on reach when you're done. Thanks!

I'm not quite sure why kbs: Map[String, Seq[String]] but then later this inside information about the order:
val order = Seq("Gene_or_gene_product", "Family", "Cellular_component", "Simple_chemical", "Site", "BioProcess", "Disease", "Species", "CellLine", "TissueType", "CellType", "Organ")

Will starting out with a Seq[String, Seq[String]] in which the Seq determines the order not work?  I guess that means there could be duplicates, but an assertion can rule that out.

This is a left over of a debug session. I was controlling for the order, but forgot to delete it

Good point.
On Mon, May 3, 2021 at 5:24 PM Keith Alcock @.***>
wrote:

I'm not quite sure why kbs: Map[String, Seq[String]] but then later this
inside information about the order:
val order = Seq("Gene_or_gene_product", "Family", "Cellular_component", "Simple_chemical", "Site", "BioProcess", "Disease", "Species", "CellLine", "TissueType", "CellType", "Organ")
Will starting out with a Seq[String, Seq[String]] in which the Seq
determines the order not work? I guess that means there could be
duplicates, but an assertion can rule that out.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/processors/issues/471#issuecomment-831615442,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI75TTJPIYR4OS35LHQOETTL45D7ANCNFSM43NSPP7A
.

@kwalcock @MihaiSurdeanu Fixed

Don't try too hard.  I was replacing/converting/porting the whole thing to processors.

Reach is using processors 8.2.6.  Should I make the processors changes to that version as well, perhaps bumping it up to 8.2.7 so as not to force reach to update to the current version of processors?

@kwalcock I had to change the signature to receive a Seq instead of a Map to fix a bug introduced by removing that order sequence. I hope this doesn't affect to much the port code you may already had in place

That was handled in #477, I believe.


 Clients: 270 - Devices: 36

Were you able to get your graphs working? I'm curious how things are working out. You have a lot of devices and I'm curious if things are working ok or not..

Please let me know if I can provide additional assistance to get this working in your environment.

I think this is because some of Grafana plugins were not installed.


Code Examples of priority queue in a DQN

Would you be willing to share a few lines of the NLP DQN code that show the storing of a (s,a,r,s') tuple as well as the portion code where a stored memory is updated with the delta value to change the queue priority for subsequent sampling?
If you have a separate github for the NLP DQN code, I would love to see it.
Thanks for sharing this priority queue code. It looks well implemented.

The code is released now. The link is https://github.com/Damcy/cascadeLSTMDRL


Added outputs for examples

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[ x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @mistymayem for your contribution and congratulations on your first PR merge to this repo!


add tests for convert, save, resource, create

Pull Request Test Coverage Report for Build 389

48 of 83 (57.83%)  changed or added relevant lines in 9 files are covered.
13 unchanged lines in 4 files lost coverage.
Overall coverage increased (+8.7%) to 75.419%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/logic/commands/CreateConvertCommand.java
6
7
85.71%

src/main/java/seedu/address/logic/commands/SaveCommand.java
6
7
85.71%

src/main/java/seedu/address/logic/parser/ConvertCommandParser.java
5
6
83.33%

src/main/java/seedu/address/model/transformation/Transformation.java
5
6
83.33%

src/main/java/seedu/address/commons/util/ImageMagickUtil.java
7
38
18.42%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/seedu/address/commons/util/ImageMagickUtil.java
1
35.33%

src/main/java/seedu/address/commons/util/FileUtil.java
2
66.67%

src/main/java/seedu/address/logic/commands/CdCommand.java
4
72.41%

src/main/java/seedu/address/ui/CommandBox.java
6
67.68%

Totals

Change from base Build 380:
8.7%

Covered Lines:
1801

Relevant Lines:
2388

💛  - Coveralls


Doesnt work properly with multiple columns

In my webpage, I have lot of paragraphs of text, split into columns. When I apply your dotdotdot plugin to it, it doesnt work as expected. The overflowing text is not really hiding.
This is happening on Firefox v35  on Windows 8.1.
Snapshot: http://i.imgur.com/Yf5HzrF.png

I'd say the script should work when using css columns. Does it only not work on FireFox? Or haven't you checked other browsers?
Is there an online demo I could have a look at?


Update composer, remove submodule & ClassLoader component.

Hey, any prob with this PR ?

Sorry for long time to respond.
How can it work for people wich don't composer in their project but only submodules ? should we create two versions or a tag before merge ?

Drop submodules, it's a pain anyway.

Yes but we have some projects with submodule and some of them use this lib how they can get this repo with his deps ?

Ok so i've created the tag v1.0.0-submodules

Cool thx.


nm ovs: Enable connection.autoconnect-ports for OVS port

We forgot to enable connection.autoconnect-ports for OVS ports in NM
code as the iface.is_controller() is false for
InterfaceType::Other("ovs-port")
Extend verify retry to 30 seconds, as NM takes longer time after enabled
connection.autoconnect-ports due to extra reactivations in NM internal.
With this change, we can also skip activation on OVS interface as OVS
port will activate its subordinates.
Fixed and added integration test case.

The CI failure is caused by https://issues.redhat.com/browse/RHEL-50747 . Please wait NetworkManager fixing the bug.

NetworkManager has fixed, patch is ready for review.


Fix PartitionIdGenerator for BOOLEAN partition keys

For BOOLEAN type, change PartitionIdGenerator to call VectorHasher::enableValueRange() instead of enableValueIds() during rehash. For BOOLEAN type VectorHasher only supports isRange mode. Calling enableValueIds on BOOLEAN vector throws error currently.
Also add validation to the PartitionIdGenerator constructor for current support for partition key types. It is based on VectorHasher support for value id types. We currently do not support all partition types supported by Presto, ex., double.

Thank you, @mbasmanova @xiaoxmeng , for the quick review! Revised according to comments.


Gardena/lw/block wise transfer tests

Some unit tests were refactored and improved.
Added also some new tests.

@LukasWoodtli You will need to sign the Eclipse contributor agreement and rebase on #683 (once merged) to get CI to pass.


CollectionFS working?

THANK YOU for the GREAT documentation made so far on using Angular-meteor and Angular2-meteor.
Steps 16 and up have not been written yet for angular 2.0 tutorial and I can seem to integrate CollectionFS or understand how I can do it in angular 2.0 (Step 20).
Is CollectionFS (and other unwritten steps like ionic, gMaps...) not implemented in angular2-meteor yet?
Where can I find bare documentation/example on it ?
Thank you !!

I was trying to work with CollectionFS and it seems that it is very hard to use that in angular2-meteor. the reason is helpers that do lots of things and are not available in angular2-meteor.
I wanted to ask if any temporary solution exists for now.
I am developing some kind of social network and CollectionFS would be very helpful.
thanks a lot

Step about CollectionFS is not written yet, hence, CollectionFS is not tested with Angular2-Meteor.
Since we are moving step by step in the tutorial, and there are like 3 steps left before the one with CollectionFS, I expect it to be done within next 2-3 weeks or so. This's what I can say.

hello! I was trying to use gridFS or collectionFS to angular2. So angular-meteor com step 20 is not written yet, when we can use collectionFS, it is possible now use angular2. If it is possible, can you explain how to use it for some example. Thank you!


bgpv2: Introduce NoMatchingNode condition to CiliumBGPClusterConfig

Introduce a new condition to report the error that the given node selector selects nothing. This is the first condition we introduce in the CiliumBGPClusterConfig. Therefore, this PR also introduces an update for the CRD and an internal infra to set conditions.
apiVersion: cilium.io/v2alpha1
kind: CiliumBGPClusterConfig
metadata:
  name: cilium-bgp
spec:
  bgpInstances:
  - localASN: 65000
    name: instance0
  nodeSelector:
    matchLabels:
      select: nothing
status:
  conditions:
  - lastTransitionTime: "2024-10-24T07:34:05Z"
    message: spec.nodeSelector selects nothing
    observedGeneration: 3
    reason: NoMatchingNode
    status: "True"
    type: cilium.io/NoMatchingNode

bgpv2: Introduce NoMatchingNode condition to CiliumBGPClusterConfig

/test

/test

/test

I see this was labeled as release-note/misc, but it's changing APIs. Should this be labeled at least as release-note/minor? We also may want to think about whether to increase the version (eg v1alpha1 -> v1alpha2) when making changes to the APIs. Not sure if that strictly applies when only adding new fields like status, but we have had complaints from users recently when making changes to existing APIs (even alpha ones) since users do not expect a specific version of an API to change---that's why versions exist :sweat_smile: .

I think that for those users we did actually make a breaking change, that's fair. I'm not sure I understand @cilium/sig-k8s quite well enough to really determine the consequences if we're only adding new fields.


refactor(evaluators): shift evaluator code into the table package

Split out from #118.
Shifting code for the manifest evaluator visitor and metrics to the table package rather than being in the top level iceberg package to reduce how much we need to export as we don't want to export these visitors anyways. They should be internal only and will be need for future development of the Scanner.

CC @Fokko @nastra


[youtube] HTTP Error 403: Forbidden

For any video tried today 2020-04-13. On latest version 2020.03.24.

Yes, in videos with drm it is happening

Not sure if it it related to DRM because my browser do not have DRM and previously downloaded videos are failing. Any how I close this issue because I opened issue #24760 filling the template.

See #24760

I too am having the same problem - easily recreateable - recent update to youtube causing this?
Verbose error attached
403error.txt


Core crate merge

A ton of refactoring to allow for the development of source-modeled compression schemes. Also added rudimentary documentation throughout the public interface.


Investigate usage with SELINUX policies

I don't use slack yet. I am just posting this for discussion or thought at present.
SELINUX is a security mechanism used to authorise system calls and other things on Cent OS systems. It is most useful when used to create profiles for specific applications or containers.
I prefer using Nomad when running containers. In such cases where name spacing or other security enhancements may not be available. It is useful to utilise such tools.
Since SELINUX policies can use JSON would it be possible or useful to have such an implementation.
This would mean using Kapitan to generate policies or to group security concerns into components.
I am not entirely familiar with the usage of SELINUX and I understand that most people do not like it. To be honest due to the environment I have never fully had to consider it. I think it might be a cool thing to detail some where else though.
I would like to get peoples opinions or thoughts on this matter.

It wouldn't hurt to add an (small) example selinux policy generation under the examples/. Given that it doesn't have that many differences from other json file generation (like terraform) I'm not sure if I'd add other docs regarding this. An example would be nice though. :)

That is great to hear and I may add that. I think at this point it is still kind of a theory. I am wondering if it would be a good use case.
I would not want to add saturation to the uses for this tool, however considering Android supports SELINUX we can increase the possible use cases.

I looked this over and I noticed that SELINUX does not support JSON. I initially thought that it did but I was greatly mistaken. I don't believe this would be the best use case at present. I will close this out for now.
@uberspot  great talk the day it was delivered very well & clearly conceptualised kapitan


docs(stable/concourse): update instructions to generate secrets

The readme advises to use ssh-keygen -t rsa -f host-key  -N '' to generate keys for concourse. However, some ssh-keygen implementations will generate keys that make concourse crash with ugly SIGSEGV errors.
This has already been reported upstream: https://github.com/concourse/concourse/issues/2779
I propose changing the instructions to match the official docs, slightly adapted for filenames

Ooooh great catch, concourse generate-key is definitely the way to go 😁
Would you mind updating a few things?

the commit must be signed,
the patch part of the Chart version under stable/concourse/Chart.yaml must be bumped

Thanks!

Hi @JohannesRudolph ,
would you mind checking https://github.com/helm/charts/pull/14383#issuecomment-497837536?
Thank you!


Offline mode

Is there a way to use the Storage constructs with Serverless offline?
I ran the deployment so the bucket was created correctly. But if I run sls offline the bucket name comes as the string [object Object], when set in a env via: BUCKET_NAME: '${construct.someBucket.bucketName}'.

Hi, unfortunately this is a limitation of serverless-offline for all CloudFormation references (which Lift uses): https://github.com/dherault/serverless-offline/issues/1149
By the way, I realized that our very own @fredericbarthelet was the one who implemented resolution of these references in sls invoke local (https://github.com/serverless/serverless/pull/8198), but that is not supported by sls offline.

Just to clarify, would it be accurate to say that until dherault/serverless-offline#1149 is addressed, lift will not work with serverless-offline in general? Or does this only pertain to specific resources, such as Storage (mentioned by the OP)?
I came here because I'm trying to use an SQS (queue) construct with serverless-offline, but am getting the following error:
 Error: Constructs are already initialized: this should not happen
   at _LiftPlugin.loadConstructs (.../node_modules/serverless-lift/dist/src/plugin.js:178:13)

@zmk-punchbowl I think this is correct, I would not expect serverless-offline to work fine in several cases until dherault/serverless-offline#1149 is fixed

Thank you for confirming, @mnapoli

Sorry if I misunderstand but was this plugin related to this https://www.npmjs.com/package/serverless-pseudo-parameters which seems to be built in to serverless framework now?

+1


[INLONG-8150][Manager] Optimize InlongClusterServiceImpl#getClusterNodes

Prepare a Pull Request
(Change the title refer to the following example)

Title Example: [INLONG-XYZ][Component] Title of the pull request

(The following XYZ should be replaced by the actual GitHub Issue number)

Fixes #8150

Motivation
this method throw too much exceptions when group is not found or deleted
Modifications
return emtpy list when group is not found or deleted
Verifying this change
(Please pick either of the following options)

[ ] This change is a trivial rework/code cleanup without any test coverage.

[ ] This change is already covered by existing tests, such as:
(please describe tests)

[ ] This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

Please git rebase master and exec mvn spotless:apply to solve code style error.