docs: added all contributors (#369)

1. Description

1.1. Checklist

[ ] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[ ] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for ALL new/updated/fixed functionality.
[ ] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[ ] I have updated/added relevant examples in examples.

1.2. Breaking Change

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

1.3. Related Issues

Codecov Report

Merging #375 (254ee37) into main (b995078) will decrease coverage by 0.43%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #375      +/-   ##
==========================================
- Coverage   71.16%   70.74%   -0.43%
==========================================
  Files         139       63      -76
  Lines        1297      769     -528
==========================================
- Hits          923      544     -379
+ Misses        374      225     -149

see 76 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Brent;
Thanks so much for the idea and benchmarking. I swapped over to use samtools depth and also feed the output directly into downstream groupby so it avoids writing one intermediate file to disk. Great to have this simplified and faster, thank you again for identifying the slow point in the process and providing a workaround.

awesome! thanks for implementing!

I haven't groked the existing code fully, but would it be possible to combine this step with the subsequent sambamba depth window step (which, if I understand, is looking for very high-depth regions)?
Maybe instead of using bedtools groupby it could use a python script to do the grouping and also output 250bp regions of sufficient depth to a separate bed file and then those could be checked as needed for really high depth instead of forcing sambamba to re-run on the whole genome?
I can prototype if you think this might work, but I'm not sure of the full use of the sambamba depth output.

I put some of this into python, replacing awk -> bedtools groupby -> cut with a single python snippet.
The comparison looks like this:
time samtools depth -r 1:1-20000000 -Q 1 --reference $fasta $bam \
	| awk '{if ($3 == 0) {print $1"\t"$2-1"\t"$2"\tNO_COVERAGE"} else if ($3 < 4) {print $1"\t"$2-1"\t"$2"\tLOW_COVERAGE"} else {print $1"\t"$2-1"\t"$2"\tCALLABLE"} }' \
	| bedtools groupby -prec 21 -g 1,4 -c 1,2,3,4 -o first,min,max,first \
	| cut -f 3-6 \
	> st.bed
real	1m15.183s
user	2m26.165s
sys	0m2.391s

time samtools depth -r 1:1-20000000 -Q 1 --reference $fasta $bam \
	| python gr.py > gr.bed
real	0m36.280s
user	1m6.930s
sys	0m1.906s

md5sum st.bed gr.bed
beff75c0c3599e125e6b8d22ef3f816f  st.bed
beff75c0c3599e125e6b8d22ef3f816f  gr.bed

so it basically cuts the time in half again and does even better for cpu time. Here is gr.py
import sys

last = (None, None)
cache = []

viter = (l.rstrip("\r\n").split("\t", 3) for l in sys.stdin)
for chrom, pos, depth in viter:
    key = (chrom, "NO_COVERAGE" if depth == "0" else "LOW_COVERAGE" if int(depth) < 4 else "CALLABLE")
    if key != last:
        if last[0] is not None:
            print "\t".join((last[0], str(int(cache[0][1]) - 1), cache[-1][1], last[1]))
        last = key
        cache = cache[:0]
    cache.append((chrom, pos, depth))
print "\t".join((chrom, str(int(cache[0][1]) - 1), cache[-1][1], last[1]))

In addition to the speed benefits, this might make it possible to group into 250 base windows (or any) and output the window information to a separate file so it's not doing per-base samtools depth and then immediately doing sambamba depth window.

Brent -- awesome, thank you. This is a great idea. I'm also working on merging high depth reporting into this as well to avoid the double depth calculation. These are all great suggestions. I'll work on rolling this prototype approach and push a fix soon for testing. Thank you again for all this help and benchmarking.

cool. here's what I just hacked together to do the window-depth in the same pass. Writing the window stuff to stderr currently, but you get the idea.
import sys

WINDOW_SIZE = 250
WINDOW_DEPTH_CUTOFF = 300

last = (None, None)
last_window = -1
depth_cache = []
cache = []

def mean(vals):
    return sum(vals) / float(WINDOW_SIZE)

viter = (l.rstrip("\r\n").split("\t", 3) for l in sys.stdin)
for chrom, pos, depth in viter:

    depth, ipos = int(depth), int(pos)
    if ipos / WINDOW_SIZE != last_window:
        if mean(depth_cache) > WINDOW_DEPTH_CUTOFF:
            sys.stderr.write("%s\t%d\t%d\t%.2f\n" % (chrom, last_window * 250, last_window * 250 + 250, mean(depth_cache)))
            sys.stderr.flush()
        depth_cache = depth_cache[:0]
        last_window = ipos / WINDOW_SIZE

    depth_cache.append(depth)

    key = (chrom, "NO_COVERAGE" if depth == 0 else "LOW_COVERAGE" if depth < 4 else "CALLABLE")
    if key != last:
        if last[0] is not None:
            print "\t".join((last[0], str(int(cache[0][1]) - 1), cache[-1][1], last[1]))
        last = key
        cache = cache[:0]
    cache.append((chrom, pos, depth))
print "\t".join((chrom, str(int(cache[0][1]) - 1), cache[-1][1], last[1]))

Awesome work, guys. Much appreciated.

Brent -- thanks so much for the code and approaches. I've integrated this into the current development pipeline and it's giving the same outputs on my tests. Please let me know if you notice any issues or have other approaches for improving speed. Thanks so much for looking at this and all the suggestions.

So I set my stuff going again with this, it shows in the log that the first thing to run is  multiprocessing: calc_callable_loci using sambamba depth window . I was expecting it to use samtools depth. My algorithm section looks like this:
- algorithm:
    mark_duplicates: false
    realign: false
    recalibrate: false
    svcaller:
    - cnvkit
    - lumpy

ok. I see that was piping to head and finished quicly and now the samtools depth + bcbio.bam.highdepth.bin_depths is running.

Just fyi, the sambamba depth window didn't get logged to log/bcbio-nextgen-commands.log AFAICT.

Hi Brad, I just saw this:
CalledProcessError: Command 'set -o pipefail; /scratch/ucgd/lustre/u6000771/bcbio/galaxy/../anaconda/bin/samtools depth -a -Q 1 -b /scratch/ucgd/lustre/u6000771/bcbio/eiee/work/align/15-0022953/15-0022953-callable-split/15-0022953-NC_007605-callable-coverageregions.bed --reference /scratch/ucgd/lustre/u6000771/bcbio/genomes/Hsapiens/GRCh37/seq/GRCh37.fa /scratch/ucgd/lustre/u6000771/bcbio/eiee/work/align/15-0022953/15-0022953.bam | /uufs/chpc.utah.edu/common/home/u6000771/bcbio/anaconda/bin/python -c 'import bcbio.bam.callable; bcbio.bam.highdepth.bin_depths(4, 1370, 250, "/scratch/ucgd/lustre/u6000771/bcbio/eiee/work/align/15-0022953/15-0022953-callable-split/tx/tmp_wQTbP/15-0022953-NC_007605-callable.bed", "/scratch/ucgd/lustre/u6000771/bcbio/eiee/work/align/15-0022953/15-0022953-callable-split/tx/tmp_wQTbP/15-0022953-NC_007605-highdepth.bed")'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/uufs/chpc.utah.edu/common/home/u6000771/bcbio/anaconda/lib/python2.7/site-packages/bcbio_nextgen-1.0.0a0-py2.7.egg/bcbio/bam/highdepth.py", line 64, in bin_depths
    callable_handle.write("\t".join((chrom, str(int(cache[0][1]) - 1), str(cache[-1][1]), last[1])) + "\n")
UnboundLocalError: local variable 'chrom' referenced before assignment

I guess it was for phix chromosome which apparently had no alignments. So we should prefix that line with if cache: ...

Brent -- thanks for the heads up on the edge case. I pushed the if cache fix to avoid it. Definitely let me know if you run into anything else.
You're right on with the sambamba depth -- it's a short call estimating median depth across windows which we then use to categorize high depth regions. This could probably be done smarter but I replicated what we had before to not make too many changes all that once. Right now we don't have a way to capture output and also log everything so the sambamba call uses standard subprocess instead of our wrapper around it.
Thanks again for all the thoughts and help.

cool. The sambamba depth ran quickly, so I'm not worried about it. I can already tell the pipeline is proceeding much faster with these changes.

Hi Brad, just another clarification. the samtools depth is running with a -b callable-coverageregions.bed argument. That is a single-line bed file that covers the entire chromosome. Is this expected?
Also, will the new CWL stuff parallelize the samtools depth part at a finer level than chromosome?

Brent;
That's right for whole genome runs. For exome/targeted runs it should correspond to the regions on that chromosome. CWL doesn't parallelize in more detail that at the chromosome level, it's replicating what is done in bcbio now. Do you think that's needed?

Hi Brad, I wrote a samtools depth parallelizer here: https://github.com/brentp/goleft/releases/tag/v0.1.0
with docs here: https://github.com/brentp/goleft/tree/master/depth
It's quite fast for WGS or for a target. I can get coverage for a 60X genome in 12 minutes (with 24 cpus). I think the output matches what you're doing in bcbio, including the CALLABLE/LOW_COVERAGE/NO_COVERAGE tag.
It can also output GC content and masked info which I know @etal uses in cnvkit so maybe we could output something that prevents the depth recalculation in cnvkit?
BTW, even if you decide not to use this, samtools depth might be faster without the -b argument for WGS . I found that having a -b argument slows things down somewhat -- though maybe it's not an issue for only a single interval.

Brent -- this is so awesome, thank you. I'll work on incorporating into bcbio, and it would be great to do a single calculation of depth in windows that we can pick up directly with CNVkit, and also downstream coverage assessment done by @rorky and @lpantano in QC. Eric, thinking through this a bit it seems like we'd have to do some upstream binning to output in a format compatible with making target/anti coverage cnns. Then we'd have a more general coverage summary we could evaluation for callable regions by combining overlapping callable regions. Thanks again for working on this, looking forward to getting it implemented.

I haven't tried this out yet, but it seems likely that binning these results with a target BED file would be much faster than repeating the coverage calculation within CNVkit. I'm happy to help with the conversion to .cnn format.
Incidentally, having the average on- and off-target coverages before binning would make it possible to calculate the best average antitarget bin size for the given samples instead of relying on a fixed default. That might improve CNV calls significantly for exomes.

Thanks Eric, that's a great idea for improving anti-target bin sizes as well. Would producing 50bp binned coverage, GC estimates and masking outputs be a good default? Then we could combine and merge as needed to feed into CNVkit cnn calculation. Does that make sense, or were you thinking about another path? Thanks again for helping with this.

Brad, right now, gotleft depth will not parallelize well if you give it a -b with a single interval that covers the whole genome. I can make it split large intervals to the same size it does for whole genome if you need. Also let me know any problems or features you need.

For CNVkit -- for target captures and exomes, I think 50bp is probably too coarse for fitting target bins, but 10bp might be all right. For antitarget intervals and WGS, 50bp or even larger should be OK as those boundaries are arbitrary. The antitarget bins are not necessarily equal size, since CNVkit squeezes them to fit evenly into large introns and small intergenic regions.

Brent;
Thanks again for putting together the goleft depth approach. I've been working on testing this and for some reason can't get goleft to generate any output. I'm not sure what I'm doing wrong and here's a small test case with almost no arguments that generates nothing for me:
wget https://s3.amazonaws.com/chapmanb/testcases/goleft_test.tar.gz
It outputs a depth.pprof file but nothing else, so I'm confused. Can you provide pointers about I'm doing wrong?
Also in thinking through this, would it be possible to calculate coverage with duplicates removed? We could use a samtools view piped to depth, or alternatively use the filters in sambamba depth. I'm not sure how either of those options look in terms of speed. The de-duplicated output would help with more reliable estimates of coverage actually going into variant calling, improve QC metrics and also hopefully be better for CNVkit input.
Thanks again for the help and apologies in advance if I'm doing something wrong with goleft.

Hi Brad, you need to specify --prefix. Otherwise, it's writing to ".depth.bed" and ".callable.bed" which you're not seeing. I'll adjust the code to make that required.
I'll also look into removing duplicates.

It looks like samtools depth already filters on flags. It uses:
if ( b->core.flag & (BAM_FUNMAP | BAM_FSECONDARY | BAM_FQCFAIL | BAM_FDUP) ) continue;

I fixed the goleft depth in master so an error is raised when --prefix is not specified, but could you try the version that you have with a --prefix specified and make sure it outputs what you need?

Brent -- sorry about missing the prefix input, that makes total sense now. I was expecting it to stream so fixated on that. I'm reading the code now and what do you think about merging the depth and callable outputs into a single tab delimited output file (that we could potentially stream into bgzip)? It's not really BED and the callable file will need merging as is since I'm breaking it in a more finely grained way for CNVkit and QC input. Practically I'll be using this to generate a initial tab delimited file and then post-processing it for callability, CNVkit and QC.
Thanks for checking on samtools depth, that is perfect as is. Nice one. Thanks again for all the help.

do you mean to just intermix the lines? or only output fixed regions?
but yes, I'm fine with changing it. I'd be happy to do it, but not sure I grok what you mean.

Brent -- I need to stop requesting things because you've already implemented everything. Apologies, I hadn't realized you were already collapsing from windows into the final callable.bed file. This is great as is and I'll continue to work to integrate into bcbio. Thanks much for listening to my rambling ideas.

no worries. let me know if you have any troubles. I'll make a new release soon as well.

Super valuable work, thanks guys.

Brent;
Thanks again for all the help getting goleft working. I checked in coverage estimation with goleft, replacing the custom python code. Please let me know if you run into any problems at all. I'll work next on cleaning up the older code and then starting to migrate CNVkit, seq2c and coverage QC to use the 10bp binned outputs produced by goleft. Thank you again for helping push this forward.

Brent, Eric and all;
I did some testing with the goleft approach and checked in a couple of fixes to get things working cleanly with the current development version. The biggest hurdle right now is that the depth files are gigantic at 10bp resolution, 100s of Gbs even for exome experiments. Sorry, I severely underestimated that. I turned the bin size up (https://github.com/chapmanb/bcbio-nextgen/commit/a72db6cac37ea1882dce0f261de3ae7692c4f14b) to avoid the issue but we'll have to think of a new approach to prepare coverage binning a single time as this won't work practically with feeding into CNVkit and QC to avoid re-calculating later.
I'm open for suggestions about how best to handle this. We could use some combination of defining target/anti-targets for depth (around genes, CNVkit-style) and a better on-disk representation of depth that is not a gigantic text file full of numbers.
Great to have goleft replacing a lot of bcbio code in the short term, and happy to work on better depth in the longer term.

We could also see how many bins could be merged if the mean is > 50 and within some delta. And we could merge 0 coverage bins? I can probably look into this next week.
Or do those things not work with assumptions in downstream code?

CNVkit: For WGS, the placement of bins doesn't matter much, so a bin size of 500 or 1000 (i.e. the usual in bcbio) should be OK for creating a targetcoverage.cnn file, and would save a lot of time. For captures, the coverage calculation doesn't take an unbearable amount of time in my experience, while the placement of target bins matters a lot. So, for captures, it may be better to use the goleft coverages to generate only the antitargetcoverage.cnn file, and (re)calculate targetcoverage.cnn with CNVkit.
Merging similar-enough bins sounds great to me.

Just a quick aside concerning 'samtools depth', current development version is running an improper command, at least as far as I can tell.
[2016-10-12T15:16Z] depth: invalid option -- 'd'
[2016-10-12T15:16Z] depth: invalid option -- '-'
[2016-10-12T15:16Z] [E::hts_open] fail to open file '1000'
[2016-10-12T15:16Z] samtools: Could not open "1000": No such file or directory
[2016-10-12T15:16Z] /bin/bash: line 1:  4966 Segmentation fault      (core dumped) samtools depth -Q 1 -d 1000 -r 1:14026643-14126642 --reference /home/bwubb/bcbio-nextgen/genomes/Hsapiens/GRCh37/seq/GRCh37.fa /home/bwubb/NGS/MelanomaTargeted/bcbio/data/work/1205-CRT-20Aplin/align/1205-CRT-20Aplin/1205-CRT-20Aplin-ready.bam

samtools depth --help does not show a -d option. At least for the version I am using which is 1.1

Brad -- the samtools in bcbio is 1.3.1. Is it possible to update to use the one installed by bcbio in your PATH first? That should hopefully resolve the problem.

I think it's safe to close this now.

Ah My apologies. I completely forgot to comment on it's success. Thank you
for the help, sorry it was a trivial issue.
-bwubb
On Mon, Oct 24, 2016 at 10:45 AM, Brent Pedersen - Bioinformatics <
<EMAIL_ADDRESS>wrote:

I think it's safe to close this now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chapmanb/bcbio-nextgen/issues/1549#issuecomment-255761174,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANJUxdDGhczUUur28i5Lrh6KvbiK9XQ5ks5q3MR9gaJpZM4J5e7p
.


Very long code block

Thank you for contributing to MarkdownUI!
Before you submit an issue, please complete the report with all the relevant details for your bug and go through every item in the checklist.
Describe the bug
If the code block is very long (this example contains 697 lines) and matches a certain pattern (for example, the first line is long), then the code block is not rendered. It just outputs an empty block.
Checklist

[x] I can reproduce this issue with a vanilla SwiftUI project.
[x] I can reproduce this issue using the main branch of this package.
[x] This bug hasn't been addressed in an existing GitHub issue.

Steps to reproduce
Assign this long string (given at the bottom of this comment) to longText and use Markdown(longText) to see the effect. The code block isn’t rendered.
Version information

MarkdownUI: 2.3.1
OS: iOS 17.5.1, macOS 15.0 beta 2
Xcode: 16.0 beta 2

@gonzalezreal Could you please have a look?


Fixed README.adoc image display issue. Updated DeveloperGuide.adoc

LGTM. CI looks completed? Despite yellow indicator


job launcher - refactor auth

Description
Refactor authentication of job launcher, clean code and fix detected issues
Summary of changes

Generate automatic migration
Remove unused env variables
Use env variables in docker
Remove unnecessary roles guard
Add refresh token inside jwt
Remove duplicated networksMap
Add auth to all controllers that need it

Auth endpoints fixed:

signup

Before returned a JWT. It didn't make sense, after sign up, the user must verify the email. --> Now returns void
The user was created as active --> Now pending

email-verification

Before returned a JWT. It didn't make sense, user should sigin using email and pass. --> Now returns void

signin

It was not checking that the user was active
jwtservice was not configured properly. You don't need to pass expiration time for every sign call.

refresh

It didn't have authentication

logout

It didn't have authentication

How test the changes
unit tests
yarn test
manual testing
yarn docker:db:up && yarn start

@CodiumAI-Agent /review

Preparing review...

PR Analysis

🎯 Main theme: Refactoring authentication of job launcher
📌 Type of PR: Refactoring
🧪 Relevant tests added: Yes
✨ Focused PR: Yes, the PR is focused on refactoring the authentication of the job launcher. All changes in the PR are related to this theme.
🔒 Security concerns: No, the PR does not introduce any obvious security concerns. The use of JWT for authentication is a good practice. However, it's always recommended to thoroughly test all changes related to authentication to ensure there are no security vulnerabilities.

PR Feedback

💡 General PR suggestions: The PR is well-structured and includes a detailed description of the changes made. It is good to see that unused variables have been removed and environment variables are being used in Docker. The refactoring of the authentication endpoints is also well-explained. However, it would be beneficial to include more comments in the code to explain the logic, especially for complex sections. Also, consider using constants for repeated values such as '10', 'ether' in the tests to make the code more maintainable.

How to use

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve: Suggest improvements to the code in the PR.
/ask <QUESTION>: Pose a question about the PR.

To edit any configuration parameter from 'configuration.toml', add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."


auth0 branding templates update throws panic

Checklist

[X] I have looked into the README and have not found a suitable solution or answer.
[X] I have looked into the documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have upgraded to the latest version of this project and the issue still persists.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description
I installed on MacOs using brew, logged in, and ran auth0 branding templates update as per the instructions.
I received:
⣻panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1aa7d1e]

goroutine 66 [running]:
github.com/auth0/auth0-cli/internal/cli.(*cli).obtainCustomTemplateData.func3()
        /home/runner/work/auth0-cli/auth0-cli/internal/cli/branding.go:435 +0x21e
golang.org/x/sync/errgroup.(*Group).Go.func1()
        /home/runner/go/pkg/mod/golang.org/x/sync@v0.1.0/errgroup/errgroup.go:75 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
        /home/runner/go/pkg/mod/golang.org/x/sync@v0.1.0/errgroup/errgroup.go:72 +0xa5

Expectation
I expected the terminal editor to open a custom template as per https://auth0.github.io/auth0-cli/auth0_branding_templates.html
Reproduction
Run auth0 branding templates update
Auth0 CLI version
0.13.1

Thanks for submitting this issue! It is a duplicate of #515 however, so I'm going to close this one out. But note that this has been fixed with v1.0.0-beta.1  if you're so inclined to give that a shot. Otherwise, GA of v1.0.0 is coming up soon!

Happy to report this elsewhere, but  I ran into the same issue, downloaded 1.0.0-beta.1, but when I run ./auth0 universal-login templates update I get the editor in my console but no browser window as expected in these docs
https://auth0.com/docs/customize/universal-login-pages/universal-login-page-templates#using-the-auth0-cli

Can confirm, beta release solves bug, and I see editor but no browser (which is fine by me). Thanks.


DNS record not created in local setup

https://github.com/seung-lab/CAVEdeployment/blob/121bedc6fd32b5c6404d228c5cbaa20116afe16f/environment_examples/local_env_template.sh#L36
should be?
export DNS_ZONES=({{ dns_zone }})

this is now fixed


Completion Items are not Sorted

Description:
Completion Items are not properly sorted and ordered based on the context
Affected Versions:
v0.991.0 at least

Closing since the fixes has been merged for v1.0.0


3.0.0-2.4.0

Release 3.0.0-2.4.0 aka beta freeze
Added

Added Favicon
New and improved primary nav (both look and interaction)
Added expanded-state utility for getting/setting aria-expanded

Changed

Updated Video Code to make it usable on Events pages.
Changed gulp JS unit testing task from gulp:unit:js to gulp:unit:scripts
Updated Meredith Fuchs bio and images.
Added indent rules for var, let, and const in ESLint config file.
Replaced old Grunt legaccsy plugin with Gulp mq-remove plugin
Added ability for acceptance --specs test flag to accept list of test files.
Changes big_radio macro to radio_big and checkbox_bg to checkbox_big.
Updated Dep Dir title to include "Acting"

Removed

Disables tests for landing page events, since we don't currently have events.
Removed Ombudsman from nav for beta freeze.

Fixed

Fixed issue with logic displaying the Event summary state.
Fixed missing IE only stylesheet for older systems/browsers.
Fixed skip-navigation link for keyboard navigation.

Shouldn't this be a PR from refresh to beta?

What the heck, I thought it was! Closing


Issues installing DGL 2.0.0 with CUDA 11.7 support

Thank you for sharing this wonderful project. I am currently trying to set up the environment as specified, but I am encountering issues related to the installation of the DGL library version 2.0.0 with CUDA 11.6 support (dgl==2.0.0+cu116). It seems like this version is not available through the usual channels like conda or pip, which is preventing me from successfully running the training script.
I encountered the following error while executing the command bash scripts/amazon_clothing_20k/train_linkgpt.sh:
(linkgpt) wlhuang@ybcs:~/llm/LinkGPT$ bash scripts/amazon_clothing_20k/train_linkgpt.sh
Traceback (most recent call last):
  File "/home/wlhuang/llm/LinkGPT/linkgpt/train/train.py", line 286, in <module>
    main()
  File "/home/wlhuang/llm/LinkGPT/linkgpt/train/train.py", line 147, in main
    lp_dataset = basics.load_pickle(args.lp_dataset_path)
  File "/home/wlhuang/llm/LinkGPT/linkgpt/utils/basics.py", line 71, in load_pickle
    data = pickle.load(f)
ModuleNotFoundError: No module named 'dgl.heterograph'

It seems the issue is related to the missing DGL library, and I suspect that it's due to an incompatible or missing version of DGL. Could you please share the dgl==2.0.0+cu116 version or guide me on how to install it?
Here are some environment details:
Python version: 3.9
CUDA version: 11.7
Conda environment used: linkgpt
Any help regarding how to correctly set up the environment with the required DGL version would be greatly appreciated!

Thank you for raising the issue. I installed DGL about a year ago, so the specific version might no longer be available via pip or conda. You could try downloading the corresponding .whl file for your Python version (in this case, 3.9) from here and install it locally.


Add 'pretty_print' parameter to JsonFeed.write() method

Currently the 'pretty_print' method doesn't actually do anything. This should be updated so that 'pretty_print' actually applies an indentation with new-lines so that the output file is more readable.

Resolved by #15


python312Packages.coffea: 2024.10.0 -> 2024.11.0

Things done
Changelog: https://github.com/CoffeaTeam/coffea/releases/tag/v2024.11.0
cc @veprbl

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

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

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.coffea
python311Packages.coffea.dist
python312Packages.coffea
python312Packages.coffea.dist

aarch64-linux

:white_check_mark: 4 packages built:

python311Packages.coffea
python311Packages.coffea.dist
python312Packages.coffea
python312Packages.coffea.dist

x86_64-darwin

:white_check_mark: 4 packages built:

python311Packages.coffea
python311Packages.coffea.dist
python312Packages.coffea
python312Packages.coffea.dist

aarch64-darwin

:x: 4 packages failed to build:

python311Packages.coffea
python311Packages.coffea.dist
python312Packages.coffea
python312Packages.coffea.dist

Duplicate of https://github.com/NixOS/nixpkgs/pull/357764


Display issue when turning ON

Hi Armel. I noticed that when you turn on UV K5 with the latest version the screen doesn't display anything (the firmware name version and so on are missing). Could you please have a look

Hello,
Take a look at menu 33/63 PonMsg :

None = Nothing...
Voltage = show battery voltage
Message = show welcome message
Sound = play a sound
All = Voltage + Message + Sound

Regards,
Armel F4HWN.


v4l2_camera: 0.1.1-1 in 'foxy/distribution.yaml' [bloom]

Increasing version of package(s) in repository v4l2_camera to 0.1.1-1:

upstream repository: https://gitlab.com/boldhearts/ros2_v4l2_camera.git
release repository: https://gitlab.com/boldhearts/releases/ros2_v4l2_camera-release.git
distro file: foxy/distribution.yaml
bloom version: 0.9.7
previous version for package: null

v4l2_camera
* Add missing rclcpp_components build dependency
* Contributors: Sander G. van Dijk

@sgvandijk The dev job is failing in camera_calibration (http://build.ros2.org/view/Rdev/job/Fdev__v4l2_camera__ubuntu_focal_amd64/):

multiple deprecation warnings
cc1plus: all warnings being treated as errors

You should have already received email from Jenkins for the failing builds.

I got the emails indeed, this was wrongly released to Foxy, apologies for the noise. It has in the meantime been updated here: https://github.com/ros/rosdistro/pull/25459.

It has in the meantime been updated here: #25459.

@sgvandijk The problem doesn't seem to change with the recent release.
The failing dev job is building the branch mentioned in the source entry (which is master)  which hasn't changed for 4 weeks. Either the problem needs to be fixed in the master branch or you might want to build a different branch for Foxy (and update: https://github.com/ros/rosdistro/pull/25393/files#diff-7cba7649696f12c91c3af0e0d38daad7R2368).


Limit the size of various MAXCHUNK definitions

The current code has issues when sizeof(long) <> sizeof(size_t).  The two types are assumed to be interchangeable and them being different will cause crashes and endless loops.
This fix limits the maximum chunk size for many of the symmetric ciphers to 2³⁰ bytes.  This chunk size limits the amount of data that will be encrypted/decrypted in one lump.  The code internally handles blocks of data later than the chunk limit, so this will present no difference to the caller.  Any loss of efficiency due to limiting the chunking to 1 Gbyte rather than more should be insignificant.
Fixes Coverity issues: 1508498, 1508500 - 1508505, 1508507 - 1508527, 1508529 - 1508533, 1508535 - 1508537, 1508539, 1508541 - 1508549, 1508551 - 1508569, 1508571 - 1508582.

[ ] documentation is added or updated
[ ] tests are added or updated

Hmmm... What is the big idea to have MAXBITCHUNK less (in bytes) than MAXCHUNK?

It was a quarter of the value before, I kept it the same.

Ping for review?

This pull request is ready to merge

Merged, thanks for the reviews.


fixed Same name of Group and same name of Assignments should not be their

Fixes  https://github.com/CircuitVerse/CircuitVerse/issues/1051
Describe the changes you have made in this PR -
Added uniqueness to the Group name and Assignments name
Screenshots of the changes (If any) -
A group name "meet123" already their:

Creating group of same name "meet123" :

Assignment of name "yash123":

Creating same name of Assignment i.e "yash123"

Case Sensitivity check :

Coverage remained the same at 84.266% when pulling 2d01598696c92d4d8d829c5ce0fa28f64f1f4632 on yash15601:no-same-name into 626a0b8ac040b9ee4d2b01108f225981e267eb2a on CircuitVerse:master.

@tachyons  @Ananthavijay  @nitin10s Review please

@Shivansh2407  actually i am  fixing that i m going through some error will commit changes in few min

@Shivansh2407  Done  @tachyons  Review please

Please add updated screenshots @yash15601 👍

This will make it unique across all assignments and all groups, so 2 groups cannot have the same assignment "assignment 1". This is highly undesirable. Also setting uniqueness: { case_sensitive: false } is a very bad idea, this will essentially make a select query on the name every time we save, a better way is to add an index. Read this - https://www.leighhalliday.com/requiring-uniqueness-in-rails

@satu0king will fix this soon

@tachyons  your views on this

@tachyons  i have removed the same names in assignments because it was creating problem in creating Assignment in differnt group but i have fixed the same name issue in groups please Review it will fix for Assignment soon and make pr soon

@tachyons  Review

@satu0king @tachyons   I tryed using adding index in Assignments page but how can i handle the exception i tryed a lot nothing is working can ypu give me suggestion what can i do
Screenshot:


fix: relative link to vpn-gateway-about-vpn-gateway-settings

@nschonni : Thanks for your contribution! The author, @chadmath, has been notified to review your proposed change.

Thanks, @nschonni!  #sign-off

@cherylmc: I'm sorry - only the author of this article, @chadmath, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Array -> Tuple

Address #28

Just wondering, does this show any speed differences?

@oscardssmith
actually not, I ran the benchmark on this branch against master and this is the comparison result
Results
A ratio greater than 1.0 denotes a possible regression (marked with :x:), while a ratio less
than 1.0 denotes a possible improvement (marked with :white_check_mark:). Only significant results - results
that indicate possible regressions or improvements - are shown below (thus, an empty table means that all
benchmark results remained invariant between builds).

ID
time ratio
memory ratio

(the table is empty)
The results for the benchmark are the following

ID
time
GC time
memory
allocations

["perft", "perft1"]
35.629 ms (5%)

26.34 MiB (1%)
339238

["perft", "perft10"]
35.772 ms (5%)

26.34 MiB (1%)
339238

["perft", "perft2"]
35.646 ms (5%)

26.34 MiB (1%)
339238

["perft", "perft3"]
35.547 ms (5%)

26.34 MiB (1%)
339238

["perft", "perft4"]
35.569 ms (5%)

26.34 MiB (1%)
339238

["perft", "perft5"]
35.577 ms (5%)

26.34 MiB (1%)
339238

["perft", "perft6"]
35.589 ms (5%)

26.34 MiB (1%)
339238

["perft", "perft7"]
35.543 ms (5%)

26.34 MiB (1%)
339238

["perft", "perft8"]
35.647 ms (5%)

26.34 MiB (1%)
339238

["perft", "perft9"]
35.643 ms (5%)

26.34 MiB (1%)
339238

["perft", "starting position"]
35.693 ms (5%)

26.34 MiB (1%)
339238

no much difference between them. I'm using a depth of 4 to keep the benchmark time down, but that should be enough to benchmark the entire code


Fix pre-hash calculation: add ctx to M'

Per FIPS 204, M' (mp) should be:
M'  ← BytesToBits(IntegerToBytes(1, 1) ∥ IntegerToBytes(|𝑐𝑡𝑥|, 1) ∥ 𝑐𝑡𝑥 ∥ OID ∥ PH𝑀)
The current implementation is missing the context string. This change fixes it.
Verified changes with KATs from https://github.com/post-quantum-cryptography/KAT

Thanks for spotting this! Too bad we still don't have CAVP test vectors for these in the latest NIST update. Anyway, hopefully addressed in https://github.com/mjosaarinen/py-acvp-pqc/commit/9e0c89a13b77d7af51ab18576a300ae8bfa27d58


HeaderWeb language list has wrong position on mobile

On mobile devices, eg. Safari browser when scrolled down and header is sticky, language menu flows randomly:

You can't have position fixed (language list) inside position sticky (header).
Again, please enable PRs so public can help improve state services.

This has been already fixed (language list position changed to absolute).


Ordering args according to the _message_field_schema

It can be a solution to #135 problem.
What I am doing is simply ordering the alias_args according to the _message_fields_schema.
In case of ancestor path you just set the fields in the correct order in _message_fields_schema.

I don't think this is necessary. Users can handle removing duplicates on their own.

The purpose is not for removing duplicates but for ordering the CombinedContainer fields according to the _message_fields_schema. It will resolve all the issues according to ancestor path.

Right. I'm just not sure it's necessary.

OK thanks danny :)

Sure thing. Sorry.


General fixes for the AnimationTree editor

Fix renaming a node in the BlendTree editor causing it to not respond correctly until the editor is reopened.
Fix undoing a node deletion in the BlendTree editor not placing it back to its original position.
Fix an icon error in BlendSpace1D editor.
Expose GraphNode's "close_color" to the Inspector.
Add missing period in some places.

Thanks!


Document how to use older Nix

When using Nix 2.4 one has to use nix develop .#devShells.<system>.default to run the nix shell.

Don't care about this anymore.


#975 - remove use of the deprecated Felix whiteboard properties

This change impacts the Environment filter and the dispatcher Expires/Cache-Control filters.
Testing looks good on 6.2 and 6.3 for the Environment filter and the Cache-Control filter, but can't get the Expires header to work. I see the filter being registered and called, but the expires header always shows up at Expires: Thu, 01 Jan 1970 00:00:00 GMT
Hoping @bstopp has a better test setup.

LGTM .. will wait for @bstopp to check out the expires; odd that this change would effect that behavior though.

This looks good to me; i think you may have been forgetting to add the header:
Server-Agent: Communique-Dispatcher to your requests. I tested the daily expires via PostMan with:
filter.pattern=/content.*
expries.time=23:00

Header value: Expires →Fri, 21 Apr 2017 23:00:00 GMT

@bstopp the header is definitely there. Do I need to test this on publish maybe?

I tested mine on Author. I saw a Jan 1 1970 date one time, but wasn't able to recreate after I fixed my request. Let me see if i can recreate, i'll spend some time testing possible causes.

hmm. yeah, it works in Postman. I was testing in curl.

Ok yes that is weird, i see it not working in cURL and it should; i'll use that and retest.

I tested it through the dispatcher; it looks to be working correctly:
-rw-r--r-- 1 apache apache 61854 Apr 21 19:08 en.html
-rw-r--r-- 1 apache apache     0 Apr 23  2017 en.html.ttl

The header being wrong via cURL must be a curl issue or some other filter coming into play?

thanks for the review @bstopp


Update dependency version except tap

As title,
By the way, I thought that tap version is too old to update to latest version for reducing vulnerability, but if we can find a version for lowest node version and less vulnerability, it may be a good trade-off?
and CI build pass. https://travis-ci.org/realdennis/nan

Tests seem to pass, but please try the things Ben pointed out.

I'm still interested in the way that some of the tests failed when you upgraded tap to the latest in your previous PR:  https://github.com/nodejs/nan/pull/786 Definitely worth looking at the CI failures there - some may reveal some actual issues in the code, although I still haven't looked any closer at them - will dig deeper in a few days.
I don't know if we really need to stick with "tap": "~0.7.1" - Is there a newer release that doesn't break builds against older Node.js versions?  ...or is ``"~0.7.1"` the latest that works without issue?

It is the last that works, as far as I can remember.

@bnoordhuis Hey, below I list that some dependency I found  we do not use.
request commander glob xtend, and  readable-stream should be using by node v0.8.
By the way, should I need to pull a new request, or just edit the title in this situation?

@mkrufky
Except the oldest node version could not use newest tap (const declare in tap)
(I don't know how to using the higher version of tap but taking care of the old version?)
Build failed(v4-v10) cause some test case did not pass, it maybe reveal some actual issues .

If I remember correctly, the problem with TAP is that later versions throw a hissy fit for anything that is logged to stderr (or was it stdout).

@mkrufky Refer to npm's bundle node gyp , I remove the node-gyp devDependency, and rewrote .travis.yml(add npm install -g node-gyp in before_install, using npm script instead of older version).
Please ignore eb503bb commit, I add it back in next commit.

I've been away, and this PR got a bit more complicated than its original intent.   How about we go back, for now, to whatever it takes for us not to have to modify .travis.yml   If that was a result of removing the node-gyp then let's not remove it just yet.  Let's keep this change simple and handle the rest in a separate PR.


Problems with infer

Thanks for your good implementation. I have run your code on my own dataset. And I want to know, do your code provide multiple images inferring?

No, but you can easily extend for your needs.

Thanks for your codes. May I ask for your help about the following problem:
When I try to evaluate or infer, I meet this error:
1.evaluate:
size mismatch for detection._proposal_transformer.bias: copying a param with shape torch.Size([368]) from checkpoint, the shape in current model is torch.Size([84]).
2.infer:
size mismatch for rpn._anchor_transformer.weight: copying a param with shape torch.Size([48, 512, 1, 1]) from checkpoint, the shape in current model is torch.Size([36, 512, 1, 1]).
Thank you

same problems,have you worked it out?@PaperLamp

@potterhsu

These sorts of errors usually occurred when your configs between training and inference are inconsistent, for example:

You were training with anchor_sizes=[64,128,256,512]
But are inferring with anchor_sizes=[128,256,512]


Adam 10 implementing home page

set up main layout of the page, still unsure of what direction we want to take in terms of design.


First bunch of localization commits (#890)

It's really hard to look at the changes. Could you please sync the latest code and make the PR again so that it does not include merged commits.


feat(Analysis.Seminorm): some results about the order on seminorms

[x] depends on: #5806

This PR/issue depends on:

leanprover-community/mathlib4#5806
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#5806
By Dependent Issues (🤖). Happy coding!

Thanks!
bors merge


feat: Take Into Account Spread Factor for Token Out Value

What is the purpose of the change:
This PR modifies the token out value by subtracting the swap fee, so users can see the true expected outcome of their swap.
Linear Task
Linear Task URL
Testing and Verifying

[ ] Subtracts swap fee from token out and token out fiat value

Summary by CodeRabbit

New Features

Updated the SwapTool component to enhance the accuracy of displayed values by incorporating swap fees into the calculation of token out amounts.

Tests

Added tests for the new getTokenOutMinusSwapFee function to ensure reliable calculation of token amounts post-swap fees.

Refactor

Refined the logic in the use-swap hook to improve the consistency and precision in fee and token value calculations.

Wait, why doesn't SQS return an amount with the swap fee included?

I've also thought about this. Because we need the tokenOutMinusSwapFee to calculate tokenOutFiatValue, moving this to SQS is not straightforward. This PR serves as a temporary solution until we can transition to SQS, which should happen in about two weeks when Roman and I return from vacation. Once back, we plan to tackle the price caching issues, which initially prompted moving the tokenOutFiatValue calculation to the frontend. Once this is resolved, we'll be able to calculate the tokenOutFiatValue and the token out amount minus the swap fee using SQS, allowing us to remove this code

Wait, why doesn't SQS return an amount with the swap fee included?

I agree with this, and it's the correct solution. Unfortunately, the swap tool is currently not delivering accurate data to users, and I don't have the bandwidth or context to implement the necessary changes in SQS. This PR is intended as a temporary fix until we can move this to the server. I plan to make this move in about two weeks, once Roman is back from vacation.

@JoseRFelix this is very surprising to me. I feel like spread factor should be included when swaps are simulated 🤔


(PUP-10148) Add X-Puppet-Profiling for all ca service calls

Prior to this commit, we had added the ability to add the profiling
header to http calls so that we can log profiling data for a given agent
run. However, we forgot to add that capacity everywhere in the ca
service. This commit fixes that omission.

@joshcooper anywhere else we need to add this method?

CLA signed by all contributors.


SEO for homepage

There is already an issue for indexing documents #74, but currently there is no description tag or any SEO for the homepage. Should be an easy fix and quick win.

Might be a good idea, but I'm not sure whether the description tag actually adds value. IIRC, google prefers body text, which is already crawled correctly:

I think it works for Google and such, but I added it as an example on LinkedIn:

I had to type the text myself.

I'll add Helmet and create an image + description for social sharing

Added the tags using helmet, but the facebook crawler requires pre-rendered / hardcoded tags.
Hardcoded is not an option, as the service has two different URLs running on one instance.


Rebased dao

What changed? Why?
Stripped down tcategory and sub to 1
Notes to reviewers
@wbnns got it down to one as per the rules.

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/2

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
1

Sum
2

@iafhurtado Thanks so much for the updates, confirming this is under review by the team


Added easygui based GUI. Added utf-8 support.

Basically, everything happens inside a window now.
easygui was chosen because it is very simple.
Headder specifies interpreter (for unix) and encooding.
I know the initial intention was that IAmBored was to be a web-app, but I don't know anything about the plataforms sugested (Flask and Heroku). Hope this is an improvement.

@tiago-macedo It would look better if the title bar always reads I am bored instead of the title of the idea.


New Feature: Update a Dataset from geospatial features

↪ Pull Request
Update a dataset from geospatial features
Depends on #96
Fix #100
💻 Examples
>>> import geopandas
>>> my_dataset = unify.datasets.by_name('my_dataset')
>>> df=geopandas.GeoDataFrame.from_features(my_dataset)
>>> # Modify df
>>> my_dataset.from_geo_features(df)

✔ PR Todo

[x] Added/updated testing for this change
[x] Included links to related issues/PRs
[x] Update relevant docs + docstrings
[x] Update the CHANGELOG under the current -dev version:

Add changelog entries under any that apply: BREAKING CHANGES, NEW FEATURES, BUG FIXES.
Changelog entry format: [#<issue number>](<link to issue>) <change description>

LGTM


Mm 44417

Summary
Fixing a copy-paste error
Ticket Link
https://mattermost.atlassian.net/browse/MM-44417
Release Note
NONE

NONE

Hello @ctlaltdieliet,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Hi @amyblais,
I fixed the copy-paste error in the  code. I don't know if I have to modify en.json as well. Can you give me a clue on that.
Thank you.

Hi @amyblais,
I fixed the copy-paste error in the  code. I don't know if I have to modify en.json as well. Can you give me a clue on that.
Thank you.

Hi @amyblais, I fixed the copy-paste error in the code. I don't know if I have to modify en.json as well. Can you give me a clue on that. Thank you.

I'm guessing yes, but dev reviewers can confirm on that.


Running rqatrend seems to accumulate memory

Havent investigated but when running the rqatrend for different years and Orbits it fails after a few iterations with an out of memory error.

This might be a threading issue. I found this issue on the Julia repo https://github.com/JuliaLang/julia/issues/40626 and I am currently testing with 14 workers but they are scratching on the total RAM and are also a lot slower than the combination of 3 workers and 10 threads each apparently a factor of 4

After letting it run for a few hours the memory usage accumulates to 11.7 GB per worker and it throws an error indicating that the worker ran out of memory.
I can find the memory when I check the memory usage from the different workers but I can't free it by running GC.gc()
I am still not sure, whether this is the thread issue or a distributed issue or a combination of both.

Have you tried Profile.Allocs.@profile from PProf.jl, e.g. see here?

Running it with Julia 1.11.2 still sees the same problem maybe with a but slower increase and the @time macro before the rqatrend does not indicate any gc time which might be a bad sign:
Progress: 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| Time: 0:36:29
2189.929099 seconds (227.82 k allocations: 13.929 MiB, 0.00% gc time, 28 lock conflicts)
  0.191193 seconds (13.23 k allocations: 1.426 MiB)
path = "/mnt/felix1/worldmap/data/E048N015T3_rqatrend_VH_146_thresh_3.0_year_2018"
outpath = "/mnt/felix1/worldmap/data/E048N015T3_rqatrend_VH_146_thresh_3.0_year_2018.zarr"

I tested it shortly on julia 1.10 because it might also be a regression. This might be related to this issue:
https://github.com/JuliaLang/julia/issues/56759
I will start the process for a longer time with julia 1.10 to see, whether it also slowly fills up the memory.
One suggestions in the linked issue was to take heap_snapshots via Profile.take_heap_snapshot

@felixcremer did switching to 1.10 help? If you think it's the same issue I was seeing, please share on https://github.com/JuliaLang/julia/issues/56759

I think this is not related to https://github.com/JuliaLang/julia/issues/56759 because also in julia 1.10 I get a similar behaviour and after multiple mapCube computations the memory is filled up and the julia process fails with an out of memory error. Even though the memory is accumulating a bit slower than with julia 1.11.

I changed the ArchGDAL finalizer for the IRasterBand to print when it is finalized and this is not shown when setting the gdalcube to nothing and running GC afterwards.

I think this does not work in general, printing to terminal from within finalizers does not work. In the past there was usually a warning saying something like "Task switch from finalizers not allowed". So the missing print is not a proof that the finalizer is not run. However, I agree with Lazaro, just testing this with the YAXArrayBase GDALBand would be a low-effort test to check if this is about a defect IRasterBand finalizer

It seems that this is much better in the current master of julia.
I am not yet sure, whether this is fully fixing it but I am hopeful.


Created and added Header to all current pages

[x] Moved "colors" to the extend module in tailwind cfg file. It was overwriting the default colors when placed directly under "theme", making all the default colors inaccessible.

[x] Added "sans" keyword to fontfamily module's main font.

This keyword makes the browser default to that font. This way we don't have to define the default font everywhere.

[x] Changed the padding settings for the alt-button component

Done in order to center the text vertically. It was slightly offset when using same padding on top and bottom for some reason.

[x] Added two custom css classes in input.css

The first is for animating the language options.

The second for hiding an ugly browser default styling for cancelling user input (in search fields for example).

[x] Created HTML for header and a search drawer that will be triggered using js.

It was neccessary to have the search-drawer code outside the header tag.

[x] Added header code to all available html pages.

The header looks really nice. A few adjustments:

[ ] all img elements must have an alt attribute with text
[ ] Line 57 in the code, section with the id="search-drawer-from-header": Section lacks heading. Consider using a div element or another element instead.
[ ] Line 57 in the code, section with the id="search-drawer-from-header": try using aria-label instead of aria-labelledby. I get an error now because aria-labelledby must point to an element in the same document
[ ] Line 60 in the code, form: Add a label tag to the form. It's recommended for accessibility and usability purposes. You can visually hide it for design purposes, but then it will still be available for screen readers.

[ ] Added alt-attributes to all images

[ ] Created  element for better semantic structuring and screen reader navigation.

[ ] Changed aria-labelledyby attribute of the search section to "search-bar" for clearer screen reader identification.

[ ] Added a  tag on line 62 for the search input field to improve form accessibility, while keeping it visually hidden.

Should be added to all pages now


DISQUSSHORTNAME

Codecov Report

Merging #34 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #34   +/-   ##
=======================================
  Coverage   40.89%   40.89%
=======================================
  Files          27       27
  Lines         269      269
  Branches       28       28
=======================================
  Hits          110      110
  Misses        143      143
  Partials       16       16

Continue to review full report at Codecov.

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


feat: limit num units deployment to 1

Applicable spec: N/A
Overview
Limits the number of units of server charm deployment to 1 since Jenkins does not support multi-controller nodes.
Rationale
Improve UX on accidental multi-unit deployment
Juju Events Changes
None.
Module Changes
state.py changed to check for number of units planned.
Library Changes
None.
Checklist

[x] The charm style guide was applied
[x] The contributing guide was applied
[x] The changes are compliant with ISD054 - Managing Charm Complexity
[x] The documentation is generated using src-docs
[x] The documentation for charmhub is updated.
[x] The PR is tagged with appropriate label (urgent, trivial, complex)

I realise this PR is merged, do you think only the non-leader units should go into blocked state? Since it is valid to have 1 it seems like it would make sense if all but one unit goes into blocked state asking the operator to remove those units?

@jdkandersson That sounds like a good improvement, let me create a bug ticket for that and improve it. Thank you!


Caught mismatch between code and spec: constraints

Documentation [1] and tutorial [2] describe that satisfaction of a
constraint is "c(x) <= 0" where c(x) is a constraint. However, the
real code evaluates "c(x) < 0", which is a mismatch between code and
spec.
[1] https://gpyopt.readthedocs.io/en/latest/GPyOpt.core.task.html?highlight=constraints#module-GPyOpt.core.task.space
[2] https://nbviewer.jupyter.org/github/SheffieldML/GPyOpt/blob/master/manual/GPyOpt_constrained_optimization.ipynb

Codecov Report

Merging #222 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #222   +/-   ##
=======================================
  Coverage   77.36%   77.36%
=======================================
  Files          97       97
  Lines        4603     4603
=======================================
  Hits         3561     3561
  Misses       1042     1042

Impacted Files
Coverage Δ

GPyOpt/core/task/space.py
87.8% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

I just re-runed GPyOpt_constrained_optimization.ipynb, and it seems to be fine.


Static Code Analyzer : Logging Practice with use of system output stream

remove outputs or wrap with
#if DEBUG
#endif

This has been addressed in branch https://github.com/Esri/military-symbol-editor-addin-wpf/tree/csm/%23197-null-dref-and-sca-issues

Addressed in PR #220
Moving to done and will get reviewed/QA/QC with SCA Issue #197


config-linux: mark memory.kernel[TCP] as NOT RECOMMENDED

Per-cgroup kernel memory accounting (and explicit limiting) is
problematic in the Linux kernel for too many reasons to quote here.
Besides, cgroup v2 does not even have a kernel memory limit knob,
and the one in cgroup v1 is made obsoleted in kernel v5.4 [1].
Mark memory.kernel and memory.kernelTCP as NOT RECOMMENDED, in additon
to OPTIONAL. This is a way to say "we do not anyone (runtimes or users)
to set those limits, unless they have good understanding and strong
reasons to do so".
[1]https://github.com/torvalds/linux/commit/0158115f702b0ba208ab0

LGTM


metrics: enable exporting metrics for aggregation

It would be nice to have a way to track metrics around DNS queries and whether they were blocked, and if so, in what manner (default vs. custom list).
Not sure if we should pick one metrics format, need to look into what's common these days (e.g. prometheus vs. statsd, etc.)

Just stumbled onto your plugin, it looks really interesting and I was wondering if there was any metrics exposed by it.
Just my twp cents: it looks like, for CoreDNS at least, the most logical thing to do would be to implement them as Prometheus metrics. This way they would be available directly when using the metrics plugin. It really seems that most other "built-in" plugin relies on it to serve statistics about what they do.
If we take the forward plugin as an example, they do exposes them here and increment them here.
I might take a look at doing a quick implementation of it in your plugin if I get some time to pour into it.

Hi @0rax! Following the forward plugin as an example sounds good to me.
It certainly would be nice to finally have metrics coming out of this thing :slightly_smiling_face:


Unexpected behavior when Status is created for non-existent status code

Framework user reports an incorrect behavior when a Status object is created, and the status and its associated description are not found in the status.yml file

There is an exception happens when the framework tries to construct a Status object from status.yml config file. What would be the best approach to handle this scenario?

Create another error code to indicate that a specific status code is missing from status.yml?
Just log it as an error in the stdout and log file?

A default method has been added into MiddlewareHandler interface to setExchangeStatus. If the status code is not loaded successfully from status.yml file, then an ERROR_NOT_DEFINED will be returned.
    default void setExchangeStatus(HttpServerExchange exchange, String code, final Object... args) {
        Status status = new Status(code, args);
        if(status.getStatusCode() == 0) {
            // There is no entry in status.yml for this particular error code.
            status = new Status(ERROR_NOT_DEFINED, code);
        }
        exchange.setStatusCode(status.getStatusCode());
        exchange.getResponseSender().send(status.toString());
        logger.error(status.toString());
    }


Keys.NumpadEnter [Input]

Release Type: Official Release
Version: <IP_ADDRESS>8
Confirmed Platform(s): Windows (other were not checked for that)
Describe the bug
If you try to check if numpad enter is pressed, the system always returns false no matter if the button is pressed or not.
if (Input.IsKeyDown(Keys.NumPadEnter))
{
    //action
}

However, if you use Keys.Enter instead, both buttons are read like the same button.
Expected behavior
Input.IsKeyDown(Keys.NumPadEnter) returns true only if numpad Enter is pressed.
Input.IsKeyDown(Keys.Enter) returns true only if standard Enter is pressed.

Looks like this is because the game view is launched with WinForms:

The numeric keypad 'enter' key in SDL and RawInput, Winforms forwards it to  instead.

When I switched to SDL, the inputs worked as expected:
game.Run(GameContextFactory.NewGameContextSDL();


Sidebar: scroll to top when exercise change

The current scrollTop doesn't work, but this one work with Chrome and Safari. I haven't tested on non-Chrome browsers yet.

thank you — this was also fixed in #530, so I'll close this


gulp-pugbem

Error in plugin "gulp-pug"
._element.-1

error when the modifier is numeric....

Why did you close it?..


Enter Long Mode using legacy bootloader.

After loading initial 512 bytes it's time for moving forward.
Read required data using BIOS, set stack and GDT then switch to 64-bit. Switching to 32-bit PM shouldn't be necessary.

Progress was made (pm was established).
Related #4 .

it has been done with 3b13c70dba356f1eec4db21a696ba849ec4bff9d commit.


Open account in new tab

Issue
Hi,
I notice that when we click on people account on thread, it will open it in the same page. I think it would be great if we make it to open new tab to see people account.

anyway, nice works!!

The golden rule is by opening new tab for every external URL, that's you can keep the visitor from leaving your page while opening the link.


[Refactor] consolidated tasks tests

Consolidated the testing of tasks to one file. Now a function checks if any task file has changed and if it hasn't then uses the provided default tasks.
Also unit tests run on multiple python versions. Added dependency caching as well, so should run a bit faster.
Lowered the atol for the loglikihood test as noticed it was quite unreliable. Not sure if this a bug or where the discrepancy comes from.

@haileyschoelkopf checked the results after adding torch.use_deterministic_algorithms() for a couple of runs on the CI but they were not consistent. :( Changed the atol to 0.01 for the time being but logging the loglikelihoods of every run on the artefact registry and will come back to it after a while.

Thanks very much! Hmm, sounds like a plan for now.


[feature] Allow non superadmin to create, manage and own org

If a staff user which is not superadmin has permission to create/change/delete organizations, we must make sure that when this user creates an organization, their account is flagged as owner and automatically associated to this org as manager (OrganizationUser(is_admin=True)).

@nemesifier I would like to work on this issue.

@himanshu-sharmav please select an easier issue to start contributing, there's plenty of more entry level issues. Leave this for more experienced contributors, thanks.


Return new description

This works:
#[macro_use] extern crate error_type;

error_type! {
    #[derive(Debug)]
    pub enum MyError {
        StringError(String) {
            desc (msg) msg;
        }
    }
}

fn main() {
    println!("Hello, world!");
}

But if I want to prepend something to the message, I have to allocate a new string:
error_type! {
    #[derive(Debug)]
    pub enum MyError {
        StringError(String) {
            desc (msg) format!("A StringError with the content '{}'", msg);
        }
    }
}

This fails of course, because the description should return a slice and I'm returning a string. Converting it to a slice does not work either:
desc (msg) &format!("A StringError with the content '{}'", msg);

...because:
src/main.rs:7:25: 7:76 error: borrowed value does not live long enough
src/main.rs:7             desc (msg) &format!("A StringError with the content '{}'", msg);

Is there a way to allocate a new string, and return a slice to it with the correct lifetime?

No; this is a fundamental limitation of Error::description.  You can only return a string slice which is either a static string or already stored in the error itself.  You cannot generate a new string.  That's what Display/disp is for.
The Kaboom case in the example from the docs shows a trivial example of adding a Display implementation.


Error connecting to simulator: "Missing the 'authorization' header with security credentials"

Hi I am trying to create a simple environment with:
from android_env import loader

env = loader.load(
    avd_name='Pixel_3a_API_34_extension_level_7_arm64-v8a',
    # avd_name='my_avd',
    android_avd_home='/Users/anujm/.android/avd',
    android_sdk_root='/Users/anujm/Library/Android/sdk',
    emulator_path='/Users/anujm/Library/Android/sdk/emulator/emulator',
    adb_path='/Users/anujm/Library/Android/sdk/platform-tools/adb',
    task_path='/Users/anujm/code/android_env/tasks/mdp/mdp_0000.textproto',
)

but I run into  "Missing the 'authorization' header with security credentials"
ERROR:absl:RpcError caught. Reconnecting to emulator...
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/emulator/emulator_simulator.py", line 87, in wrapper
    return func(*args, **kwargs)  # pytype: disable=missing-parameter  # always-use-return-annotations
           ^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/emulator/emulator_simulator.py", line 373, in _confirm_booted
    emu_status = self._emulator_stub.getStatus(empty_pb2.Empty())
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/grpc/_channel.py", line 1176, in __call__
    return _end_unary_response_blocking(state, call, False, None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/grpc/_channel.py", line 1005, in _end_unary_response_blocking
    raise _InactiveRpcError(state)  # pytype: disable=not-instantiable
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNAUTHENTICATED
	details = "Missing the 'authorization' header with security credentials."
	debug_error_string = "UNKNOWN:Error received from peer  {created_time:"2024-03-27T18:30:09.412245-07:00", grpc_status:16, grpc_message:"Missing the \'authorization\' header with security credentials."}"
>

Below is the caller stack trace:
{
	"name": "SimulatorError",
	"message": "Exception caught in simulator. Please see the simulator logs above for more details.",
	"stack": "---------------------------------------------------------------------------
_InactiveRpcError                         Traceback (most recent call last)
File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/emulator/emulator_simulator.py:87, in _reconnect_on_grpc_error.<locals>.wrapper(*args, **kwargs)
     86 try:
---> 87   return func(*args, **kwargs)  # pytype: disable=missing-parameter  # always-use-return-annotations
     88 except grpc.RpcError:

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/emulator/emulator_simulator.py:373, in EmulatorSimulator._confirm_booted(self, startup_wait_time_sec)
    372 while time.time() < deadline:
--> 373   emu_status = self._emulator_stub.getStatus(empty_pb2.Empty())
    374   logging.info('Waiting for emulator (%r) to start... (%rms)',
    375                self.adb_device_name(), emu_status.uptime)

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/grpc/_channel.py:1176, in _UnaryUnaryMultiCallable.__call__(self, request, timeout, metadata, credentials, wait_for_ready, compression)
   1170 (
   1171     state,
   1172     call,
   1173 ) = self._blocking(
   1174     request, timeout, metadata, credentials, wait_for_ready, compression
   1175 )
-> 1176 return _end_unary_response_blocking(state, call, False, None)

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/grpc/_channel.py:1005, in _end_unary_response_blocking(state, call, with_call, deadline)
   1004 else:
-> 1005     raise _InactiveRpcError(state)

_InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
\tstatus = StatusCode.UNAUTHENTICATED
\tdetails = \"Missing the 'authorization' header with security credentials.\"
\tdebug_error_string = \"UNKNOWN:Error received from peer  {created_time:\"2024-03-27T18:30:09.412245-07:00\", grpc_status:16, grpc_message:\"Missing the \\'authorization\\' header with security credentials.\"}\"
>

During handling of the above exception, another exception occurred:

_InactiveRpcError                         Traceback (most recent call last)
File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/base_simulator.py:32, in _print_logs_on_exception.<locals>.wrapper(*args, **kwargs)
     31 try:
---> 32   return func(*args, **kwargs)
     33 except Exception as error:
     34   # Calls self.get_logs since self is the first arg.

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/base_simulator.py:83, in BaseSimulator.launch(self)
     82 self._num_launch_attempts += 1
---> 83 self._launch_impl()

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/emulator/emulator_simulator.py:250, in EmulatorSimulator._launch_impl(self)
    249 try:
--> 250   self._confirm_booted()
    251 except EmulatorCrashError:

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/emulator/emulator_simulator.py:94, in _reconnect_on_grpc_error.<locals>.wrapper(*args, **kwargs)
     91 emu._emulator_stub, emu._snapshot_stub = emu._connect_to_emulator(  # pylint: disable=protected-access
     92     emu._grpc_port  # pylint: disable=protected-access
     93 )
---> 94 return func(*args, **kwargs)

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/emulator/emulator_simulator.py:373, in EmulatorSimulator._confirm_booted(self, startup_wait_time_sec)
    372 while time.time() < deadline:
--> 373   emu_status = self._emulator_stub.getStatus(empty_pb2.Empty())
    374   logging.info('Waiting for emulator (%r) to start... (%rms)',
    375                self.adb_device_name(), emu_status.uptime)

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/grpc/_channel.py:1176, in _UnaryUnaryMultiCallable.__call__(self, request, timeout, metadata, credentials, wait_for_ready, compression)
   1170 (
   1171     state,
   1172     call,
   1173 ) = self._blocking(
   1174     request, timeout, metadata, credentials, wait_for_ready, compression
   1175 )
-> 1176 return _end_unary_response_blocking(state, call, False, None)

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/grpc/_channel.py:1005, in _end_unary_response_blocking(state, call, with_call, deadline)
   1004 else:
-> 1005     raise _InactiveRpcError(state)

_InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
\tstatus = StatusCode.UNAUTHENTICATED
\tdetails = \"Missing the 'authorization' header with security credentials.\"
\tdebug_error_string = \"UNKNOWN:Error received from peer  {created_time:\"2024-03-27T18:30:09.418329-07:00\", grpc_status:16, grpc_message:\"Missing the \\'authorization\\' header with security credentials.\"}\"
>

The above exception was the direct cause of the following exception:

SimulatorError                            Traceback (most recent call last)
Cell In[1], line 3
      1 from android_env import loader
----> 3 env = loader.load(
      4     avd_name='Pixel_3a_API_34_extension_level_7_arm64-v8a',
      5     # avd_name='my_avd',
      6     android_avd_home='/Users/anujm/.android/avd',
      7     android_sdk_root='/Users/anujm/Library/Android/sdk',
      8     emulator_path='/Users/anujm/Library/Android/sdk/emulator/emulator',
      9     adb_path='/Users/anujm/Library/Android/sdk/platform-tools/adb',
     10     task_path='/Users/anujm/code/android_env/tasks/mdp/mdp_0000.textproto',
     11 )

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/loader.py:72, in load(task_path, avd_name, android_avd_home, android_sdk_root, emulator_path, adb_path, run_headless)
     69   text_format.Parse(proto_file.read(), task)
     71 task_manager = task_manager_lib.TaskManager(task)
---> 72 coordinator = coordinator_lib.Coordinator(simulator, task_manager)
     74 # Load environment.
     75 return environment.AndroidEnv(coordinator=coordinator)

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/coordinator.py:120, in Coordinator.__init__(self, simulator, task_manager, num_fingers, interaction_rate_sec, enable_key_events, show_touches, show_pointer_location, show_status_bar, show_navigation_bar, periodic_restart_time_min, tmp_dir)
    117 self._simulator_start_time = None
    119 logging.info('Starting the simulator...')
--> 120 self._launch_simulator()

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/coordinator.py:223, in Coordinator._launch_simulator(self, max_retries)
    220 self._task_manager.stop()
    222 # Launch the simulator.
--> 223 self._simulator.launch()
    224 self._simulator_start_time = time.time()
    226 # From here on, the simulator is assumed to be up and running.

File /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/android_env/components/simulators/base_simulator.py:37, in _print_logs_on_exception.<locals>.wrapper(*args, **kwargs)
     35 for line in args[0].get_logs().splitlines():
     36   logging.error(line)
---> 37 raise errors.SimulatorError(
     38     'Exception caught in simulator. Please see the simulator logs '
     39     'above for more details.') from error

SimulatorError: Exception caught in simulator. Please see the simulator logs above for more details."
}

Any help would be great,
Thanks

Hi @AnujMahajanOxf,
One internal Google client encountered this a while ago, and it was due to not passing -grpc. Can you set grpc_port when loading the environment? Also, it  seems like you're using an old version of the loader, please use this: https://github.com/google-deepmind/android_env/blob/main/android_env/loader.py (from the github version, not pip. We haven't updated that).
Let me know how it goes. Cheers

Hi again,
I remembered that the port for gRPC is automatically picked, so you shouldn´t need to pass it.
I'd say, try using the version at HEAD and then you can come back with a new stack trace if any. Thanks!

I had this same issue on HEAD, turns out it was occurring since I had the emulator on while trying to start the python script. Should be fixed by simply turning off the emulator first.

This issue will be closed due to inactivity.


#2503 Remove border from gallery & collection item

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[ ] Feature
[x] Refactoring

What's new?

[x] PR closes #2503
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address:
Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

Hey! Why are you removing border-radius?

@roiLeo since we are removing borders, border-radius wont be visible right ?

Woow it looks really nice.

@roiLeo added border radius back, realised it was causing a flicker when hovering

Thinking to replace the the rounded corners with edgy corners
reasoning: whole app has is based on the edges
But love to hear @yangwao 's opinion

Thinking to replace the the rounded corners with edgy corners
reasoning: whole app has is based on the edges
But love to hear @yangwao 's opinion

Actually, it's in issue

Remove radius on corners as well

@prachi00 🥺

which issue? @yangwao
okay I'll replace the rounded corners with edged ones

which issue?

From #2503

Remove radius on corners as well
cc @prachi00

@yangwao @vikiival have removed the corner radius

Kjut

Kjut

🤔

pay 100 usd

😍 Perfect, I’ve sent the payout
💵 $100 @ 128 USD/KSM ~ 0.781 $KSM
🧗 EzGc4s9PgCPx1YnF3fqzhLzVHpHMTL4LWPScwpDrR8JKgSU
🔗 0xf3e95009d3bd024a21aec4553632af616210d9c7459c8d8c0c44ea067d36e2b0
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Add further optmization to coreIssuanceOrder, remove slice

Pull Request Test Coverage Report for Build 1204

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1192:
0.0%

Covered Lines:
333

Relevant Lines:
333

💛  - Coveralls


Set default Bazel versions to be tested

Related https://github.com/bazelbuild/bazel-central-registry/discussions/1332

/cc @alexeagle


Build failed with gcc4.9.3

Compiling a tiny test project consisting only of example1.c++, I get the following error:
In file included from /home/claravu/nonius/include/nonius/configuration.h++:17:0,
from /home/claravu/nonius/include/nonius/benchmark.h++:18,
from /home/claravu/nonius/include/nonius/nonius.h++:18,
from /home/claravu/nonius/include/nonius/nonius_single.h++:14,
from /home/claravu/test_nonius/example1.c++:36:
/home/claravu/nonius/include/nonius/param.h++: In member function ‘nonius::param nonius::param::parse(const string&) const’:
/home/claravu/nonius/include/nonius/param.h++:103:38: error: use of deleted function ‘std::basic_stringstream::basic_stringstream(const std::basic_stringstream&)’
auto ss = std::stringstream{s};
Changing the offending line to:
  std::stringstream ss;
  ss.str(s);

Made the error go away, but I'm not 100% sure this it true to the intent. The error does not occur in v1.1.2.
I'm trying out nonius for benchmarking on a new project, looks pretty good so far!

The same error happens with gcc-4.8.4 as well as clang-3.9 with both std=c++11 and c++14

I changed the line from:
auto ss = std::stringstream{s}
to
std::stringstream ss{s}
And it compiles correctly.


Added a little more information about HubPress

Added a new paragraph to further explain HubPress
Corrected a minor typo

Thanks Russell. Changes merged.


fix: documenting the deprecation of multiple search terms

Description

Removing multiple search term support

Testing required outside of automated testing?

[ ] Not Applicable

Screenshots (if appropriate):

Rollback / Rollforward Procedure

[ ] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.198.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


unable to submit and move to next lesson.

After "Use Hex Code for Specific Colors" when I submit the whole of FCC crashes on my computer. This has not happened before. If i refresh it will come back but as before unable to pass this point. Any ideas?

Is it just stuck on the success pop up?
Are you using Chrome? If so please test it out with FireFox and report back.

I have the same problem, I can not submit in chrome,but it is ok on firefox

Closing as this is the same issue as #6633


Created a secondary button rounded

Here is the component I have built (Secondary button rounded).
Here is a screenshot of the component

Here is a screenshot of the component in hover state

Please remove the border form the button. @Gunika2002

Sure, I will do that @Rajdip019

@Rajdip019 I have removed the border.
Here is a screenshot attached.

Screenshot in hover state

GOOD JOB @Gunika2002
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


mysql-collector: Upgrade to argparse.

optparse is deprecated, replace it with argparse.

This PR tracks this issue: https://github.com/opendns/lemming/pull/70

Closed with https://github.com/opendns/lemming/pull/70


Plantdoc rev

This seems to me as a good change. Any reasons you closed this?

Ow, just saw you opened another one!! =)