text:
Mavenisation of YCSB with a (tar ball) distribution packager.

Refactored the whole project structure as a standard maven project, which makes it easier to manage dependencies.
Also, added a YCSB distribution module which packages a tar ball with all libraries, workloads, configurations and executable binary.
To test this, execute this command from top level directory
"mvn clean package"
If the build is successful; you will find a distribution package at
"distribution/target/ycsb-distribution-0.1.3-package.tar.gz"
NOTE :

gemfire, mapkeeper dependencies could not be found in standard maven repositories. So, as of now; they are not included in the distribution package.
If they are available in other external repositories (could not find it), they can be configured and included as well.
For JDBC, this distribution is done with openjpa-jdbc library. For custom JDBC sources, the corresponding maven dependency have to be configured and recompiled.

Hi Hariprasad, this is a great work! Here are my comments:

I got compilation errors about annotations. I added something like this to the top-level pom to fix it:

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>2.3.2</version>
        <configuration>
          <source>1.6</source>
          <target>1.6</target>
        </configuration>
      </plugin>
    </plugins>
  </build>

It would be good to include older versions of Cassandra. Some people might need them to check for performance regression.

I think this patch is ready to go in if you can fix these 2 things. Hariprasad, I'm really excited about this patch!
--Michi

Michi,
Okay. Pushed a new version just now.
Here is the summary of changes

Added the maven-compiler-plugin section in top level pom.
MapKeeper is also included as part of build
Support for older Cassandra Versions until 0.7.0

Notes :

I already tried the link for gemfire. But it seems Gemfire uses older Spring Core version, which is no obsolete and no longer hosted in any maven repositories.
Failed to execute goal on project gemfire-binding: Could not resolve dependencies for project org.apache.ycsb:gemfire-binding:jar:0.1.3: Could not find artifact org.springframework:spring-core:jar:1.0.0.M3 in gemstone (http://dist.gemstone.com.s3.amazonaws.com/maven/release/)

So, it has to be fixed in Gemfire.

Older Cassandra Versions are no longer in standard Maven Repositories. So, I could not add support for 0.5.0 and 0.6.0 clients.

Interestingly, Cassandra 7 Client does not work with latest version. So, right now all Cassandra clients are compiled against 0.7.0 libraries.

I have no problem with third party or external libraries as long as they are trusted and available always.

Hope this is good to go.
Thanks,
Hari

Hi Hariprasad, I merged the patch to the master.

For Gemfire, I'll check with sbawaska if he can help (gh-55).
Let's not worry about Cassandra 5 and 6 for now.

Again, this is a great work. Thank you for your contribution!
Thanks!
--Michi

Hi Hariprasad,
I have been trying to figure out how to include README and CHANGELOG to the distribution. Ideally they should stay in the top-level directory, but I haven't been able to include these files without moving them under distribution/ directory. Any advice?
Thanks!
--Michi

... I think I figured it out. Adding <include>org.apache.ycsb:*</include> under moduleSet in distribution.xml seems to fix the issue.
--Michi

Spoke too soon. It's still not working :(

It surely did! Thank you, Hariprasad.
--Michi

repo: brianfrankcooper/YCSB


text:
Assessment questions should be linked to content

This is a big one, but a huge benefit for the student.
Assessment questions should have a way to link to resources or activities.  This way when the student is reviewing their assessment results they can follow the links back to the content of the questions they got wrong.
This will need a design session to plan correctly.

This is way out for now.. we need to bring assessments back in the mix first before this happens.  Keeping it around so I don't forget.

Legacy.. Closing
Use cases / direction / design to be re-evaluated

source: gharchive/issue

repo: briangormanly/agora

license_type: permissive

license_source: github-api


text:
Strange error:  'mdColorPicker' is non-assignable!

The color picker was working perfectly, then one day the little color icon disappeared. Then today we got a report from a user and here's the message that we're seeing:
vendor.js:25 Error: [$compile:nonassign] Expression 'undefined' in attribute 'mdColorPreview' used with directive 'mdColorPicker' is non-assignable!
Any idea what that might mean?

Can you post any code and/or demo/link?

Unfortunately application is behind auth.
Bower.json
 "dependencies": {
    "angular": "~1.5.*",
    "angular-ui-router": "ui-router#~0.2.15",
    "angular-animate": "~1.4.7",
    "angular-whimsical-ripple": "~0.0.1",
    "angular-sanitize": "~1.4.3",
    "growl": "~1.3.1",
    "angular-ui-sortable": "~0.13.4",
    "ng-file-upload": "~9.1.1",
    "ng-lodash": "~0.3.0",
    "ngstorage": "~0.3.9",
    "es5-shim": "~4.3.1",
    "es6-shim": "~0.35.*",
    "satellizer": "~0.13.4",
    "angular-busy": "~4.1.3",
    "angular-loading-bar": "~0.8.0",
    "angular-ui-tree": "~2.15.0",
    "textAngular": "^1.5.0",
    "angular-material-datetimepicker": "^1.4.0",
    "md-color-picker": "0.2.5",
    "angular-material": "^1.0.7"
  },
  "resolutions": {
    "angular": ">=1.5.x",
    "angular-sanitize": "~1.4.3",
    "angular-animate": "~1.4.7"
  },
  "overrides": {
    "angular": {
      "dependencies": {
        "jquery": "*",
        "jquery-ui": "*"
      }
    }
  }

Markup
 <pick-a-color set="PageFactory.page.content.client_color"></pick-a-color>

can you post the template for the pick-a-color directive?
Is there an 'md-color-preview' attribute anywhere in that directive?
in v0.2.5 I added quite a few new attribute/options to the color picker. mdColorPreview toggles the preview circle next to the input (true to show, false to hide) and defaults to true.

That was dumb -- not sure why I posed our directive rather than yours :)

Color Picker

Ah man, my bad.  Looks like I should have set the options to optional.
I'll try to get a hotfix out tonight or tomorrow.
In the mean time, if you use the non-minified version of mdColorPicker.js and change these lines to '=?' instead of '=' it should work.

We can wait, we're only using this particular directive on our own stuff at the moment. Thank you for your efforts!

authors: brianpkelley mcblum

repo: brianpkelley/md-color-picker

license: mit

license_source: bigquery


text:
fix: allow the user of the container to be set

Fixes: https://github.com/bridgecrewio/checkov-action/issues/58
All for a cleaner solution if you have one but tbh this seems OK to me. It's a docker parameter we're setting. In theory they could deprecate the flag and then the version of docker the host is using is important which isn't ideal but I think that is extremely unlikely.

Having looked at the docs more what would be quite nice is making use of the pre-entrypoint: attribute to fix the folder / file ownership. That would be a much cleaner solution.

I couldn't find any way fo conditionally providing arguments so the argument would have to have its default set in the parameter rather than in the Dockerfile. Any thoughts on where to go from here? Merge this or go down the more native solution within the entrypoint of the container https://github.com/bridgecrewio/checkov?

@schosterbarak bump, any thoughts on a solution?

source: gharchive/pull-request

repo: bridgecrewio/checkov-action


text:
Bug in: ClassAttributeWithStaticValue

this code:
- unless @show_discount == 'dont_show'
      .discount{ class: @show_discount }

throws the error: ClassAttributeWithStaticValue: Avoid defining class in attributes hash for static class names
When we change it to this (add to_s) haml-lint sees that it is a variable containing a string and accepts it
- unless @show_discount == 'dont_show'
      .discount{ class: @show_discount.to_s }

This line is causing the issue.
Instance variable gets parsed as (ivar :@show_discount). So if you do value.children  it would return [:@show_discount].

When we change it to this (add to_s) haml-lint sees that it is a variable containing a string and accepts it

@show_discount.to_s gets parsed as function call over ivar. Thats why it is passing.
Local variables are also passing the test cause they are getting parsed as method calls (oh the ambiguity!! :sweat: ). ie (send nil :show_discount). So here value.children.first.class would return nilClass. ( STATIC_CLASSES.include? => false). It might be worth finding out how rubocop is handling this.
I think a quick fix can be that value.children.first.class is replaced with, value.type instead.
String and Symbol has value.type of str and sym respectively. Is it acceptable?

Thanks for the report @dennisvandehoef, and thank you for investigating @sonalkr132. Your suggested solution sounds great, and I've gone ahead and implemented it in 5b0af87d17b23fc06620a21c17f27e64a1682489.
Thanks for your help!

authors: dennisvandehoef sds sonalkr132

repo: brigade/haml-lint

license: MIT


text:
Sync constantly running out of space

Steps to reproduce:

Create a machine with following resources:
 docker-machine create --driver virtualbox --virtualbox-disk-size 25000 --virtualbox-cpu-count 2 --virtualbox-memory 2048 testmachine

Start a machine

Create docker-compose.yml

Run Compose

Run docker-osx-dev on a project with 10+ GB of data to sync

What happens:  sync runs for a minute and fails with:
2016-02-10 16:41:51 [INFO] rsync: write failed on "/Users/ain/projects/testmachine/shared/docker/assets/global_images/image/file/582/xofoiapdodpoda132.png": No space left on device (28)
2016-02-10 16:41:51 [INFO] rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.1]
2016-02-10 16:41:51 [INFO] rsync: [sender] write error: Broken pipe (32)
2016-02-10 16:41:56 [INFO] Initial sync done

What should happen:  sync should complete successfully.

If you run docker ps -a and docker images, you'll get a list of all the containers and images on your system, all of which are also stored in VirtualBox and take up a lot of room. Between those and the sync data, it's certainly possible you'll be out of space. The only workaround I can think of for now is to either clean up the files or increase the VirtualBox disk size.

I think the problem is that the copy function works with tmpfs (because of tar?) and therefore throws up when the space there gets consumed. To back this speculation up, take a look:
tmpfs                     1.8G      1.8G         0 100% /
tmpfs                  1001.3M    956.0K   1000.3M   0% /dev/shm
/dev/sda1                23.0G      4.4G     17.4G  20% /mnt/sda1
cgroup                 1001.3M         0   1001.3M   0% /sys/fs/cgroup
/dev/sda1                23.0G      4.4G     17.4G  20% /mnt/sda1/var/lib/docker/aufs
none                     23.0G      4.4G     17.4G  20% /mnt/sda1/var/lib/docker/aufs/mnt/0dde036b38ed818d3e439c21290fe6153d2f0bcba5888f003a721448ca8cfdb8
shm                      64.0M         0     64.0M   0% /mnt/sda1/var/lib/docker/containers/56cd6d371e51fe2ead65646df783c80c90e2375d7ecf872a1cbea2301a597335/shm
none                     23.0G      4.4G     17.4G  20% /mnt/sda1/var/lib/docker/aufs/mnt/604e0b2425832218c3178441f90d3c926ca722c54e47e5e7f4b1a51a1afdbcc0
shm                      64.0M      4.0K     64.0M   0% /mnt/sda1/var/lib/docker/containers/2b4bd577c0c5f53c5e5e7975fc41ef4156eefd2f990e222be590cc493c3fc84a/shm
none                     23.0G      4.4G     17.4G  20% /mnt/sda1/var/lib/docker/aufs/mnt/6a89248377d8a1527d9a8410444882b39e2dd881a22602cfeeceb809748f4f3c
shm                      64.0M         0     64.0M   0% /mnt/sda1/var/lib/docker/containers/51c4fa4fdc8e637f08387d5f90ed87657cc571f8a552d47e53ad795e7204aa68/shm

Hm, that could be. Not sure how to change that with tar either. Did you not have the same issue with this same folder before tar was introduced and we were using rsync for the initial sync?

Can't tell. I kept these gigabytes of assets inside another container earlier, didn't have a problem.
We should track down the commit before tar merge and test against that one to clarify.

Reproduced. It's a tar problem, was running without tar last week, all fine, upgraded on Friday and today after rebooting the whole machine, I get this:
2016-02-29 09:45:43 [INFO] Initial sync using tar for /Users/ain/projects/…/frontend
tar: write error: No space left on device
exit status 1

and
$ dockersize
Filesystem                Size      Used Available Use% Mounted on
tmpfs                     1.8G      1.8G     72.0K 100% /
tmpfs                  1001.3M         0   1001.3M   0% /dev/shm
/dev/sda1                27.8G     19.8G      6.5G  75% /mnt/sda1
cgroup                 1001.3M         0   1001.3M   0% /sys/fs/cgroup
/dev/sda1                27.8G     19.8G      6.5G  75% /mnt/sda1/var/lib/docker/aufs

The thing is, tar works with tmpfs which on my Machine instance is 2048. That 72K there is what remained. We can't have tar working in memory here.

I was able to circumvent the problem by applying a better .dockerignore.

I was having the same problem. Constantly getting:
2016-03-16 00:46:09 [INFO] Initial sync using tar for /Users/... tar: write error: No space left on device exit status 1
while running docker-osx-dev even after recreating the docker machine instance.
I was finally able to finish the initial sync and move on to docker-compose after upsizing the memory available to the Docker machine instance from 3GB to 4GB.
I suspect that in fact, tar works with tmpfs and it is limited by memory allocated to the docker machine.

Yup, that is really the case here.

I'm getting this same problem.. but from what's written above, still not sure how to fix.  How do I "increase the memory available to the docmer machine instance"?   Or "apply a better .dockerignore"?

I was able to find an answer that worked for me..
boot2docker stop
VBoxManage modifyvm boot2docker-vm --memory 3500
boot2docker start
See
http://stackoverflow.com/questions/24422123/change-boot2docker-memory-assignment

authors: ain brikis98 snipebin wheelercreek


text:
Composition is not working

The beer hops example is not working and not saving the beer object.

The beer hops example is not working and not saving the beer object.

The beer hops example is not working and not saving the beer object.

repo: brikteknologier/seraph-model


text:
Suggestion: arbitrary page parent files

Currently, _default.* files are special page files that get merged with all named page files. The suggetion is that in addition to _default.* one might use other parents like _my-prefix.* then refer to them instead of _default.* This would allow users to specify groups of pages with common rendering needs within a single application.

I agree.
In the meantime, you can already define multiple defaults that apply to different pages, see https://github.com/brillout/vite-plugin-ssr#_defaultpage.

I agree.
In the meantime, you can already define multiple defaults that apply to different pages, see https://github.com/brillout/vite-plugin-ssr#_defaultpage.

I actually wasn't aware of this feature! cool

authors: brillout gryphonmyers

repo: brillout/vite-plugin-ssr


text:
Timestamp offset ±[hh][mm] notation results in "iso: bad argument"

Repro is with zq commit 4dff9e90.
I wanted to try my hand at some of the basic shaping concepts enabled by #1833, so the first thing I tried was importing a Suricata EVE JSON log. Out-of-the-box, the timestamps in the alert records have the ISO format with the timezone expressed as an offset form UTC. However, when I attempt to apply the iso() function to turn it into a ZNG time value, I get an error.
$ echo '{"timestamp":"2020-03-26T11:03:29.986905-0700"}' | zq -t 'put ts=iso(timestamp)' -
iso: bad argument

I can see the notation with the colon between hours & minutes does appear to work, though.
$ echo '{"timestamp":"2020-03-26T11:03:29.986905-07:00"}' | zq -t 'put ts=iso(timestamp)' -
#0:record[timestamp:string,ts:time]
0:[2020-03-26T11:03:29.986905-07:00;1585245809.986905;]

The summary at https://en.wikipedia.org/wiki/ISO_8601#Time_offsets_from_UTC implies that both syntaxes are legal.

Verified in zq commit 7c7abe9.
Now the conversion is successful.
$ zq -version
Version: v0.29.0-109-g7c7abe91

$ echo '{"timestamp":"2020-03-26T11:03:29.986905-0700"}' | zq -z 'put ts=iso(timestamp)' -
{timestamp:"2020-03-26T11:03:29.986905-0700",ts:2020-03-26T18:03:29.986905Z}

Thanks @henridf!

repo: brimsec/zq


text:
Lockable and example app

Hi!
I'm reviewing this for a project. I wonder if you already have an example app done.
Maybe I could help with that. I don't know if this is what I need yet, or whether will work with what I have already done. It's a Phoenix app with React.js front-end.
Currently, there are features here that I don't need and it's missing what I need: #9  Lockable.
I have not looked into how this was done in Devise, but I guess you need  failed_attempts and locked_at fields
https://github.com/katgironpe/rails_api_template/blob/master/db/schema.rb

@katgironpe - no example app currently. I'd really appreciate you creating one though, although I understand if you need to wait for me to implement lockable first.
Without digging too much into the details I can't imagine why this wouldn't work with your Phoenix/React combo. I've been using it personally as a Phoenix/Vue.js app up to this point. It is worth noting that this isn't a port of Devise, so the database isn't going to match up exactly.
I haven't looked into what else, if anything, would be needed to implement lockable (#9) yet. Right now my next focus will be on adding Ueberauth functionality, which would be an Omniauth equivalent in Rails-land. Based on what I believe the lockable module in Devise includes I don't believe that it would be a huge amount of effort, but it would be a good sized contribution.

@britton-jb I would try to work on it this week.

That will be great. Let me know if you need anything.

authors: britton-jb katgironpe

repo: britton-jb/sentinel


text:
Detect an unsupported root filesystem

Handle the server returning an "unsupported_guest" encryption state.
Sample output:
...
14:38:11 Waiting for encryption service on i-82ebd859 at 52.27.165.218
14:38:50 Creating encrypted root drive.
14:39:00 Terminating encryptor instance i-82ebd859
14:39:00 Waiting for instances to terminate.
14:39:57 Deleting orphaned volume vol-1b32e2fd
14:39:58 Deleting orphaned volume vol-1832e2fe
14:39:58 Deleting orphaned volume vol-f333e315
14:39:58 Deleting orphaned volume vol-8833e36e
14:39:58 Deleting temporary security group sg-8fccb9eb
14:39:58 Deleting snapshot copy of original root volume snap-ec370fae
14:39:58 The specified AMI uses an unsupported operating system
Change-Id: Icecd357f621f08fbc0304e6934018af30f88f843

Closing, will reopen with a new commit.

repo: brkt/brkt-cli


text:
Rev gatk public to 4.alpha.2-127-g3eff9c1-20161220.230220-1

-Upgrade to barclay arg parsing library
-Fix failing HaplotypeCallerIntegrationTest by adjusting command lines
to account for the change in public in commit:
50cb7f70a28e1b7f8821ecfd2d2665aefaaae54d "Change list argument behavior to replace"

@cmnbroad please review. I had to do the barclay refactor from scratch rather than cherry-pick the commit from your branch, as the rebase proved too tricky otherwise. But the final diff is similar.
Not sure I agree with the UserException.BadArgumentValue -> CommandLineException.BadArgumentValue change, by the way. A "bad argument value" seems like the definitely of a "user exception" (an error that is the user's fault). I think we might want to revert this, or possibly make CommandLineException extend UserException.

Uh-oh, just realized that my IDE put fully-qualified names everywhere (eg., @org.broadinstitute.barclay.argparser.Argument). facepalm
Will try to fix -- hold off on review for now.

Yeah, the IDE puts those qualified names in. Interestingly it does so often, but not always...
Also, I agree the BadArgumentValue thing is suboptimal. It was always a subclass of CommandLineException though, even though it was a direct inner class of UserException. We can't make it derive from GATK UserException now though, since it lives in (and is used directly by) Barclay. Not sure what a better proposal is short of restoring the GATK UserException-derived one, but then we'd have two.

@cmnbroad Ok, I've removed the fully-qualified names -- this is ready for review.
I'll open a ticket in gatk public to discuss what to do about CommandLineException -- perhaps we can just wrap in UserException at the top level.

Missed one import in HaplotypeCaller, which was causing tests to fail. Fixed now.
IntelliJ's "migrate" refactor really needs some work :)

Looks like we have some argument-related test failures that we'll have to work through -- @cmnbroad your thoughts on these?
Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.CalculateTargetBaseCallCoverageIntegrationTest.testWithoutTargetFile FAILED
    org.broadinstitute.barclay.argparser.CommandLineException$MissingArgument: Argument targets was missing: Argument 'targets' is required.
        at org.broadinstitute.barclay.argparser.CommandLineArgumentParser.assertArgumentsAreValid(CommandLineArgumentParser.java:442)
        at org.broadinstitute.barclay.argparser.CommandLineArgumentParser.parseArguments(CommandLineArgumentParser.java:393)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.parseArgs(CommandLineProgram.java:213)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:185)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.utils.test.CommandLineProgramTester.runCommandLine(CommandLineProgramTester.java:88)
        at org.broadinstitute.hellbender.tools.exome.CalculateTargetBaseCallCoverageIntegrationTest.testWithoutTargetFile(CalculateTargetBaseCallCoverageIntegrationTest.java:501)
Finished 300 tests
Finished 400 tests

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.CombineReadCountsIntegrationTest.testEmptyInputFileListProvided FAILED
    org.broadinstitute.barclay.argparser.CommandLineException$BadArgumentValue: Argument I has a bad value: there must be at least one input file or a non-empty input file list (arg. -inputList)
        at org.broadinstitute.hellbender.tools.exome.CombineReadCounts.composeAndCheckInputReadCountFiles(CombineReadCounts.java:289)
        at org.broadinstitute.hellbender.tools.exome.CombineReadCounts.doWork(CombineReadCounts.java:178)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.runTool(CommandLineProgram.java:112)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMainPostParseArgs(CommandLineProgram.java:170)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:189)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.tools.exome.CombineReadCountsIntegrationTest.runTool(CombineReadCountsIntegrationTest.java:258)
        at org.broadinstitute.hellbender.tools.exome.CombineReadCountsIntegrationTest.testEmptyInputFileListProvided(CombineReadCountsIntegrationTest.java:54)
Finished 500 tests

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.CombineReadCountsIntegrationTest.testNoInputFileProvided FAILED
    org.broadinstitute.barclay.argparser.CommandLineException$BadArgumentValue: Argument I has a bad value: there must be at least one input file or a non-empty input file list (arg. -inputList)
        at org.broadinstitute.hellbender.tools.exome.CombineReadCounts.composeAndCheckInputReadCountFiles(CombineReadCounts.java:289)
        at org.broadinstitute.hellbender.tools.exome.CombineReadCounts.doWork(CombineReadCounts.java:178)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.runTool(CommandLineProgram.java:112)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMainPostParseArgs(CommandLineProgram.java:170)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:189)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.tools.exome.CombineReadCountsIntegrationTest.runTool(CombineReadCountsIntegrationTest.java:258)
        at org.broadinstitute.hellbender.tools.exome.CombineReadCountsIntegrationTest.testNoInputFileProvided(CombineReadCountsIntegrationTest.java:70)
Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.GetBayesianHetCoverageIntegrationTest.testBadJobArgs_1 FAILED
    org.broadinstitute.barclay.argparser.CommandLineException$BadArgumentValue: Illegal argument value: You must provide at least one normal (argument normal) or tumor (argument tumor) alignment file.
        at org.broadinstitute.hellbender.tools.exome.GetBayesianHetCoverage.doWork(GetBayesianHetCoverage.java:288)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.runTool(CommandLineProgram.java:112)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMainPostParseArgs(CommandLineProgram.java:170)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:189)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.utils.test.CommandLineProgramTester.runCommandLine(CommandLineProgramTester.java:88)
        at org.broadinstitute.hellbender.tools.exome.GetBayesianHetCoverageIntegrationTest.testBadJobArgs_1(GetBayesianHetCoverageIntegrationTest.java:56)

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.GetBayesianHetCoverageIntegrationTest.testBadJobArgs_2 FAILED
    org.broadinstitute.barclay.argparser.CommandLineException: If the normal BAM file is provided, the normal Het pulldown output file (argument normalHets) must also be provided.
        at org.broadinstitute.hellbender.tools.exome.GetBayesianHetCoverage.doWork(GetBayesianHetCoverage.java:294)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.runTool(CommandLineProgram.java:112)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMainPostParseArgs(CommandLineProgram.java:170)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:189)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.utils.test.CommandLineProgramTester.runCommandLine(CommandLineProgramTester.java:88)
        at org.broadinstitute.hellbender.tools.exome.GetBayesianHetCoverageIntegrationTest.testBadJobArgs_2(GetBayesianHetCoverageIntegrationTest.java:67)

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.GetBayesianHetCoverageIntegrationTest.testBadJobArgs_3 FAILED
    org.broadinstitute.barclay.argparser.CommandLineException: If the tumor BAM file is provided, the tumor Het pulldown output file (argument tumorHets) must also be provided.
        at org.broadinstitute.hellbender.tools.exome.GetBayesianHetCoverage.doWork(GetBayesianHetCoverage.java:299)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.runTool(CommandLineProgram.java:112)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMainPostParseArgs(CommandLineProgram.java:170)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:189)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.utils.test.CommandLineProgramTester.runCommandLine(CommandLineProgramTester.java:88)
        at org.broadinstitute.hellbender.tools.exome.GetBayesianHetCoverageIntegrationTest.testBadJobArgs_3(GetBayesianHetCoverageIntegrationTest.java:78)

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.GetHetCoverageIntegrationTest.testGetHetCoverageMissingTumorBAM FAILED
    org.broadinstitute.barclay.argparser.CommandLineException: Must specify both BAM and output files for tumor pulldown.
        at org.broadinstitute.hellbender.tools.exome.GetHetCoverage.doWork(GetHetCoverage.java:136)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.runTool(CommandLineProgram.java:112)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMainPostParseArgs(CommandLineProgram.java:170)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:189)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.utils.test.CommandLineProgramTester.runCommandLine(CommandLineProgramTester.java:88)
        at org.broadinstitute.hellbender.tools.exome.GetHetCoverageIntegrationTest.testGetHetCoverageMissingTumorBAM(GetHetCoverageIntegrationTest.java:116)

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.GetHetCoverageIntegrationTest.testGetHetCoverageMissingTumorOutput FAILED
    org.broadinstitute.barclay.argparser.CommandLineException: Must specify both BAM and output files for tumor pulldown.
        at org.broadinstitute.hellbender.tools.exome.GetHetCoverage.doWork(GetHetCoverage.java:136)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.runTool(CommandLineProgram.java:112)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMainPostParseArgs(CommandLineProgram.java:170)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:189)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.utils.test.CommandLineProgramTester.runCommandLine(CommandLineProgramTester.java:88)
        at org.broadinstitute.hellbender.tools.exome.GetHetCoverageIntegrationTest.testGetHetCoverageMissingTumorOutput(GetHetCoverageIntegrationTest.java:128)

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.pon.coverage.pca.HDF5PCACoveragePoNCreationUtilsUnitTest.testSubsetTargetToUsableOnes SKIPPED
Finished 1400 tests
Finished 1500 tests

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.walkers.haplotypecaller.HaplotypeCallerIntegrationTest.testGVCFModeIsConsistentWithPastResults FAILED
    java.lang.AssertionError: Line number 1239 (not counting comments) expected [20	10077008	.	T	A,<NON_REF>	0	.	BaseQRankSum=-2.307;ClippingRankSum=-3.308;DP=52;ExcessHet=3.0103;MLEAC=0,0;MLEAF=0.00,0.00;MQRankSum=-3.308;RAW_MQ=176164.00;ReadPosRankSum=-2.720	GT:AD:DP:GQ:PGT:PID:PL:SB	0/0:46,4,0:50:42:0|1:10077008_T_A:0,42,2066,148,2078,2184:18,28,4,0] but found [20	10077008	.	T	A,<NON_REF>	0	.	BaseQRankSum=-2.307;ClippingRankSum=-3.308;DP=52;ExcessHet=3.0103;MLEAC=0,0;MLEAF=0.00,0.00;MQRankSum=-3.308;RAW_MQ=176164.00;ReadPosRankSum=-2.628	GT:AD:DP:GQ:PGT:PID:PL:SB	0/0:46,4,0:50:42:0|1:10077008_T_A:0,42,2066,148,2078,2184:18,28,4,0]
        at org.testng.Assert.fail(Assert.java:94)
        at org.testng.Assert.failNotEquals(Assert.java:496)
        at org.testng.Assert.assertEquals(Assert.java:125)
        at org.testng.Assert.assertEquals(Assert.java:178)
        at org.broadinstitute.hellbender.utils.test.IntegrationTestSpec.assertEqualTextFiles(IntegrationTestSpec.java:209)
        at org.broadinstitute.hellbender.utils.test.IntegrationTestSpec.assertEqualTextFiles(IntegrationTestSpec.java:190)
        at org.broadinstitute.hellbender.tools.walkers.haplotypecaller.HaplotypeCallerIntegrationTest.testGVCFModeIsConsistentWithPastResults(HaplotypeCallerIntegrationTest.java:163)

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.walkers.haplotypecaller.HaplotypeCallerIntegrationTest.testGVCFModeIsConsistentWithPastResults_AlleleSpecificAnnotations FAILED
    java.lang.AssertionError: Line number 394 (not counting comments) expected [20	10009883	.	A	G,<NON_REF>	2151.77	.	AS_RAW_BaseQRankSum=|15,1,20,1,29,1,30,1,32,8,33,3,34,1,35,4,36,5,37,15,38,5,39,1,40,1|;AS_RAW_MQ=0.00|127656.00|0.00;AS_RAW_MQRankSum=|29,16,60,29,70,2|;AS_RAW_ReadPosRankSum=|0,2,1,3,4,1,5,1,8,1,9,3,12,3,13,1,14,1,15,1,16,2,18,2,19,1,21,1,22,3,24,1,26,1,27,1,28,1,29,1,30,2,31,2,32,2,34,2,35,3,44,1,45,1,48,1,49,1|;AS_SB_TABLE=0,0|15,32|0,0;DP=50;ExcessHet=3.0103;MLEAC=2,0;MLEAF=1.00,0.00;RAW_MQ=132938.00	GT:AD:DP:GQ:PL:SB	1/1:0,47,0:47:99:2180,147,0,2180,147,2181:0,0,15,32] but found [20	10009883	.	A	G,<NON_REF>	2151.77	.	AS_RAW_BaseQRankSum=|15,1,20,1,29,1,30,1,32,8,33,3,34,1,35,4,36,5,37,15,38,5,39,1,40,1|;AS_RAW_MQ=0.00|127656.00|0.00;AS_RAW_MQRankSum=|29,16,60,29,70,2|;AS_RAW_ReadPosRankSum=|-1,1,0,2,1,3,4,1,5,1,8,1,9,3,12,3,13,1,14,1,15,1,16,2,18,2,19,1,21,1,22,3,24,1,26,1,27,1,28,1,29,1,30,2,31,2,32,2,34,2,35,3,44,1,45,1,48,1,49,1|;AS_SB_TABLE=0,0|15,32|0,0;DP=50;ExcessHet=3.0103;MLEAC=2,0;MLEAF=1.00,0.00;RAW_MQ=132938.00	GT:AD:DP:GQ:PL:SB	1/1:0,47,0:47:99:2180,147,0,2180,147,2181:0,0,15,32]
        at org.testng.Assert.fail(Assert.java:94)
        at org.testng.Assert.failNotEquals(Assert.java:496)
        at org.testng.Assert.assertEquals(Assert.java:125)
        at org.testng.Assert.assertEquals(Assert.java:178)
        at org.broadinstitute.hellbender.utils.test.IntegrationTestSpec.assertEqualTextFiles(IntegrationTestSpec.java:209)
        at org.broadinstitute.hellbender.utils.test.IntegrationTestSpec.assertEqualTextFiles(IntegrationTestSpec.java:190)
        at org.broadinstitute.hellbender.tools.walkers.haplotypecaller.HaplotypeCallerIntegrationTest.testGVCFModeIsConsistentWithPastResults_AlleleSpecificAnnotations(HaplotypeCallerIntegrationTest.java:191)

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.walkers.haplotypecaller.HaplotypeCallerIntegrationTest.testVCFModeIsConsistentWithPastResults FAILED
    java.lang.AssertionError: Line number 109 (not counting comments) expected [20	10012362	.	G	T	835.77	.	AC=2;AF=1.00;AN=2;DP=23;ExcessHet=3.0103;FS=3200.000;MLEAC=2;MLEAF=1.00;QD=35.92;RAW_MQ=66527.00;SOR=4.003	GT:AD:DP:GQ:PL	1/1:0,23:23:69:864,69,0] but found [20	10012362	.	G	T	835.77	.	AC=2;AF=1.00;AN=2;DP=23;ExcessHet=3.0103;FS=0.000;MLEAC=2;MLEAF=1.00;QD=35.92;RAW_MQ=66527.00;SOR=4.003	GT:AD:DP:GQ:PL	1/1:0,23:23:69:864,69,0]
        at org.testng.Assert.fail(Assert.java:94)
        at org.testng.Assert.failNotEquals(Assert.java:496)
        at org.testng.Assert.assertEquals(Assert.java:125)
        at org.testng.Assert.assertEquals(Assert.java:178)
        at org.broadinstitute.hellbender.utils.test.IntegrationTestSpec.assertEqualTextFiles(IntegrationTestSpec.java:209)
        at org.broadinstitute.hellbender.utils.test.IntegrationTestSpec.assertEqualTextFiles(IntegrationTestSpec.java:190)
        at org.broadinstitute.hellbender.tools.walkers.haplotypecaller.HaplotypeCallerIntegrationTest.testVCFModeIsConsistentWithPastResults(HaplotypeCallerIntegrationTest.java:44)
Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.sexgenotyper.TargetCoverageSexGenotyperIntegrationTest.testBadRunMissingAnnotations FAILED
    org.broadinstitute.barclay.argparser.CommandLineException$MissingArgument: Argument contigAnnotations was missing: Argument 'contigAnnotations' is required.
        at org.broadinstitute.barclay.argparser.CommandLineArgumentParser.assertArgumentsAreValid(CommandLineArgumentParser.java:442)
        at org.broadinstitute.barclay.argparser.CommandLineArgumentParser.parseArguments(CommandLineArgumentParser.java:393)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.parseArgs(CommandLineProgram.java:213)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:185)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.utils.test.CommandLineProgramTester.runCommandLine(CommandLineProgramTester.java:88)
        at org.broadinstitute.hellbender.tools.exome.sexgenotyper.TargetCoverageSexGenotyperIntegrationTest.testBadRunMissingAnnotations(TargetCoverageSexGenotyperIntegrationTest.java:101)

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.sexgenotyper.TargetCoverageSexGenotyperIntegrationTest.testBadRunMissingOutput FAILED
    org.broadinstitute.barclay.argparser.CommandLineException$MissingArgument: Argument output was missing: Argument 'output' is required.
        at org.broadinstitute.barclay.argparser.CommandLineArgumentParser.assertArgumentsAreValid(CommandLineArgumentParser.java:442)
        at org.broadinstitute.barclay.argparser.CommandLineArgumentParser.parseArguments(CommandLineArgumentParser.java:393)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.parseArgs(CommandLineProgram.java:213)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:185)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.utils.test.CommandLineProgramTester.runCommandLine(CommandLineProgramTester.java:88)
        at org.broadinstitute.hellbender.tools.exome.sexgenotyper.TargetCoverageSexGenotyperIntegrationTest.testBadRunMissingOutput(TargetCoverageSexGenotyperIntegrationTest.java:110)

Gradle suite > Gradle test > org.broadinstitute.hellbender.tools.exome.sexgenotyper.TargetCoverageSexGenotyperIntegrationTest.testBadRunMissingReadCounts FAILED
    org.broadinstitute.barclay.argparser.CommandLineException$MissingArgument: Argument input was missing: Argument 'input' is required.
        at org.broadinstitute.barclay.argparser.CommandLineArgumentParser.assertArgumentsAreValid(CommandLineArgumentParser.java:442)
        at org.broadinstitute.barclay.argparser.CommandLineArgumentParser.parseArguments(CommandLineArgumentParser.java:393)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.parseArgs(CommandLineProgram.java:213)
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:185)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:96)
        at org.broadinstitute.hellbender.Main.instanceMain(Main.java:103)
        at org.broadinstitute.hellbender.CommandLineProgramTest.runCommandLine(CommandLineProgramTest.java:28)
        at org.broadinstitute.hellbender.utils.test.CommandLineProgramTester.runCommandLine(CommandLineProgramTester.java:88)
        at org.broadinstitute.hellbender.tools.exome.sexgenotyper.TargetCoverageSexGenotyperIntegrationTest.testBadRunMissingReadCounts(TargetCoverageSexGenotyperIntegrationTest.java:91)

And there are some HaplotypeCaller failures again -- they were passing on a pre-barclay snapshot with the patch to HaplotypeCallerIntegrationTest. How about I look into the HC failures, and you have a look at the other (which seem to be arg-parsing related)?

Like tests with expectedException "UserException" that need to now be CommandLineException. Looking more closely...

I think the HC failures are the result of the changes to FisherStrand in https://github.com/broadinstitute/gatk/pull/2307 -- I'm seeing 0.000 for the FS annotation where before we had non-0 values. @davidbenjamin Can you comment?

The non-HC ones (I haven't looked at all but most) just need to have their expectedException class changed to CommandLineException.

Ok, I'll fix the expectedExceptions class for those tests.
The HC output differs in both FS and ReadPosRankSum, but only in a few records.

I suspect the HC differences are due to a combination of https://github.com/broadinstitute/gatk/pull/2307 and https://github.com/broadinstitute/gatk/pull/2318, and may be expected. I'll try to confirm this.

@droazen In broadinstitute/gatk#2307, @meganshand fixed at least one bug in our FisherStrand code and the new value is correct.  The one case in Travis is a site with an AD of 0 ref reads and 23 alt reads.  The p-value for test Fisher Strand test is the probability to see the observed strand counts for alt and ref given a fixed total number of alt and ref reads and forward and reverse strand reads.  In this case, all the reads are alt, hence there is exactly one way to assign strandedness consistent with these ADs, for a p-value of exactly 1.0, hence a phred-scaled p-value of exactly 0.0.  The previous value of 3200 is an absurd numerical instability.

Ok, great, thank you @davidbenjamin! There are also differences in ReadPosRankSumTest, which I assume are due to https://github.com/broadinstitute/gatk/pull/2318 (reviewed by @ldgauthier). I'm inclined to just update the expected outputs for HC, since the differences seem consistent with the changes in public.

I've confirmed that the HC differences are due entirely to those two PRs, and are consistent with the changes in them -- preparing a patch for this branch now.

Pushed a fix for the test failures -- hopefully it will pass now.

authors: cmnbroad davidbenjamin droazen

repo: broadinstitute/gatk-protected


text:
Use joint frequency data consistently

Resolves #1540
Modifies the combineExomeAndGenomeData function to use joint data if theres only exome or genome data, and theres joint data

Thanks for the prompt review -- I addressed the comments and re-tagged you!

repo: broadinstitute/gnomad-browser


text:
Create class to wrap URI and handle URIs to local files automatically

We don't want users to have to prepend "file://" to their input/output files. Let's create a class that wraps URI, and prepends "file://" by default when there's no explicit prefix. It should have a constructor that takes a single String to integrate with our argument parsing system.

And let's also have something like gg://reference/FOOBAR as a shortcut for using the reference id FOOBAR with the Google Genomics API (what the API calls a "reference set"). And gg://readset/BUZ to use readset BUZ.

Closing -- dupe of https://github.com/broadinstitute/gatk/issues/958

authors: droazen jean-philippe-martin

repo: broadinstitute/hellbender


text:
[Bug]: motionDetectionType for eufycam3/Homebase 3 not consistently working

Version
1.6.4
Node version
18
Operating System type
Docker
Operating system version
Debian 12
Describe the bug
For my Eufycam3 on Homebase 3 products:

When turning on motionDetectionTypeHuman or motionDetectionTypeHumanRecognition then motionDetectionTypePet is also turned on
When turning motionDetectionTypeAllOtherMotions, it works fine but you cannot turn it off anymore (false doesn't work)

as example, this is the format I use for the requests:
{     "messageId": "string",     "command": "device.set_property",     "serialNumber": "T8160P21224202E1",     "name": "motionDetectionTypeHuman",     "value": "true" }

[ ]

To reproduce

connect to the ws endpoint

Send the following json to the endpoint:
{  "messageId": "string",  "command": "device.set_property",  "serialNumber": "T8160P21224202E1",  "name": "motionDetectionTypeHuman",  "value": "true" }

Check in the Eufy app on your device, now you can see that the previously motionDetectionTypePet which was false now also is true

connect to the ws endpoint

Send the following json to the endpoint:
{  "messageId": "string",  "command": "device.set_property",  "serialNumber": "T8160P21224202E1",  "name": "motionDetectionTypeAllOtherMotions",  "value": "true" }

you can see now in the Eufy app that this is turned on

Send the following json to the endpoint:
{  "messageId": "string",  "command": "device.set_property",  "serialNumber": "T8160P21224202E1",  "name": "motionDetectionTypeAllOtherMotions",  "value": "false" }

the motionDetectionTypeAllOtherMotions is still true in the eufy app

Screenshots & Logfiles
No response
Additional context
No response

I think something has changed in the firmware since it was implemented here.

authors: bdormael bropat

repo: bropat/eufy-security-ws


text:
crash under windows ?

hi i used you'r mysql async plugin it's awesome but sometime and it's total random, mysql async get crash under windows and linux ( linux is not stable i know ) but befor use that my server was full work and never get crash , but now after the fx and use your plugin some time crash i don't know why , it's make like evry variable is nil but it's dosen't someone know that issue or i'm alone ?
ps : i'm french and dosen't use google tanslate so sorry if i make some error in my report

should be good, reopen if it still crash

authors: bozoweed joelwurtz

repo: brouznouf/fivem-mysql-async


text:
Latest version of caniuse-lite missing ie when property is border-radius

LATEST: caniuse-api  "version": "3.0.0", caniuse-lite "version": "1.0.30001366",
caniuseApi.getSupport('border-radius') ->

{
  and_chr: { y: 103 },
  and_ff: { y: 101 },
  and_qq: { y: 10.4 },
  and_uc: { y: 12.12 },
  android: { y: 2.1, x: 2.1 },
  chrome: { y: 4, x: 4 },
  edge: { y: 12 },
  firefox: { a: 2, x: 3.6, y: 3 },
  ios_saf: { y: 3.2, x: 3.2 },
  kaios: { y: 2.5 },
  op_mini: {},
  op_mob: { n: 10, y: 11 },
  opera: { n: 10, y: 10.5 },
  safari: { y: 3.1, x: 4 },
  samsung: { y: 4 }
}

OLDER: caniuse-api  "version": "3.0.0", caniuse-lite "version": "1.0.30001358",
caniuseApi.getSupport('border-radius') ->

{
  and_chr: { y: 102 },
  and_ff: { y: 101 },
  and_qq: { y: 10.4 },
  and_uc: { y: 12.12 },
  android: { y: 2.1, x: 2.1 },
  chrome: { y: 4, x: 4 },
  edge: { y: 12 },
  firefox: { a: 2, x: 3.6, y: 3 },
  ie: { n: 8, y: 9 },
  ios_saf: { y: 3.2, x: 3.2 },
  kaios: { y: 2.5 },
  op_mini: {},
  op_mob: { n: 10, y: 11 },
  opera: { n: 10, y: 10.5 },
  safari: { y: 3.1, x: 4 },
  samsung: { y: 4 }
}

Seems like the problem with caniuse-api.
When I use caniuse-lite I do not see a problem (also Autoprefixer works perfectly):
let features = require('caniuse-lite/dist/unpacker/feature')
features(require('caniuse-lite/data/features/border-radius'))
/* => {
  status: 'cr',
  title: 'CSS3 Border-radius (rounded corners)',
  stats: {
    ie: {
      '6': 'n',
      '7': 'n',
      '8': 'n',
      '9': 'y',
      '10': 'y',
      '11': 'y',
      '5.5': 'n'
    }, … */

Open a new issue if you find a problem with direct caniuse-lite output.

@ai The problem is that caniuse-apihas not been updated for 4 years.

@ai It's ok, I will try to find a solution. Thank you for your reply :heart:

Ok, I found the reason is that browserslist removed IE 11 from defaults in 4.21, which causes browserslist in caniuse-api does not include IE by default at all.

authors: ai edwardfxiao

repo: browserslist/caniuse-lite


text:
Does brunch need to be a devDependency of a brunch project?

Description
Seemingly, prior to brunch@2.10.0, as long as you had brunch installed globally, then you could build a brunch project without having brunch installed in local node_modules.
For example, with the skeleton brunch/dead-simple.
$ npm uninstall --save-dev brunch
$ npm install --save react
$ echo "require('react');" > app/initialize.js

Expected behavior
With brunch@2.9.1, everything builds…
Actual behavior
With brunch@2.10.0, the browser console shows the following exception:
Uncaught Error: Cannot find module 'process' from '/'
    at require (app.js:62)
    at initialize.js:1
    at initialize.js:1

It seems some shims from brunch/deppack aren't getting packed if brunch isn't there, but I don't know why…  However, if brunch@2.10.0 is installed locally in node_modules then this issue goes away. I've noticed that some skeletons (like brunch/dead-simple) define a brunch as a dependency, however, not all of them do. Is this an intended change/requirement?
Environment

Brunch: 2.10.0
Node: v6.9.3
NPM: 3.10.10
Operating system: macos 10.12.2

package.json contents
{
  "name": "brunch-app",
  "description": "Description",
  "author": "Your Name",
  "version": "0.1.0",
  "repository": {
    "type": "git",
    "url": ""
  },
  "scripts": {
    "start": "brunch watch --server",
    "build": "brunch build --production"
  },
  "dependencies": {
    "react": "^15.4.2"
  },
  "devDependencies": {
    "auto-reload-brunch": "^2.0.0",
    "clean-css-brunch": "^2.0.0",
    "css-brunch": "^2.0.0",
    "javascript-brunch": "^2.0.0",
    "uglify-js-brunch": "^2.0.0"
  }
}

brunch config contents
exports.files = {
  javascripts: {joinTo: 'app.js'},
  stylesheets: {joinTo: 'app.css'},
  templates: {joinTo: 'app.js'}
};

Just for notice, it's better to have brunch in devDependencies, because it's actually a dependency for development. That's might be needed for Travis builds, for example.
In any case, gonna take a look at your problem.

@32bitkid this issue is related to #1593. It's a part of common problems with deppack module and we're working on it. I believe it will be fixed soon.
Here is an explanation why this happens. I can suggest you to list Brunch in your devDependencies until we fix this problem — that will be the simplest solution for you by now.

It does not need to be a devDependency. This is a high-priority bug.

@shvaikalesh This needs to be re-opened since the changes in the commit that closed this issue has been reverted.

@lydell I've send another PR: #1643

authors: 32bitkid denysdovhan lydell paulmillr

repo: brunch/brunch


text:
Re-enable CI for all Rust release channels before 0.16 release

All tests except for those running on nightly channel have been disabled for the v016 branch. This must be reverted before 0.16 is released.

CI is back to normal with aa56a85b85d521bac897493582786aa4d56bf96d. All tests on the v016 branch seem to be passing as well.

repo: brycx/orion


text:
IIS的虚拟路径搭建皮肤站时无法显示网站资源

The Problem 问题描述

Environment 运行环境

Blessing Skin 版本 (Version of Blessing Skin):5.1.0
PHP 版本 (Version of PHP):7.2.33
Apache / Nginx:Microsoft-IIS/10.0
什么浏览器，出现错误时的地址栏 URL 是什么 (Which browser and URL):主流浏览器，地址为正常皮肤站地址

Error Message 错误信息
我使用iis的url重写，在内网的localhost地址可以正常显示皮肤站，但是到外网之后无法显示皮肤站的资源，例如：

小部分人可以打开，不知与何有关，而且app/manifest.json可以打开，url重写的内容为.htaccess导入的，并且使用了虚拟路径，当把皮肤站设置为域名主页时，所有资源可以加载，而皮肤站设置到虚拟路径时，资源无法加载，推测是重写的问题，希望有人能指导我，并且如果是url重写问题，建议添加一个可以使用虚拟路径的配置以供选用。大概就这样了
Steps to Reproduce 重现步骤

不支持  IIS。

IIS是可以搭建的，但是感觉虚拟路径的重写有问题

你可以先试一试。

repo: bs-community/blessing-skin-server


text:
Add some more questions/sections

Some ideas for further questions that came to my mind. Feel free to take them over (or disregard) as you like 😄

Howdy! I’m closing this as I’m doing some spring-cleaning in my Github account. But feel free obviously to re-open or do whatever you want with this branch 😸

repo: bsingr/dev-training


text:
Can two different consumer groups maintain and mark different offsets for the same topic?

Hi,
I tried digging around in the code, but I can't see for sure: could two different consumer groups like group1 and group2 both mark different offsets for the same topic and partition?
For example, suppose that I have a topic topic1 and I want two different consumer groups:

metrics records metrics the topic to Redis
archive logs messages to S3

So suppose the metrics consumer group consumes messages twice as fast as the archive consumer group does.  Will that be a problem?  Could metrics mark its offset in partition 3 of the topic as 400 but group archive mark its offset in that same partition as only 200?
It looked like your mark offsets was marking offsets by topic and partition only, I couldn't see where the consumer group name was used in marking offsets.
Thanks!

No, the scenario you have described works and it's what Kafka was originally intended for. Each consumer is initialised with its own groupID, see here. When offsets are committed, they are always committed for a particular group/topic/partition combination, see here.
The MarkOffsets marks the offset for a

authors: dim joelpresence

repo: bsm/sarama-cluster


text:
testing

testing

just testing


text:
Add Github Actions

Nit: Unfortunately the Github Actions aren't enabled for any repository of the organization

BTW in the future please use commit messages that adhere to the established style

BTW in the future please use commit messages that adhere to the established style

Ok, sorry. Feel free to force push the repository adding this commit message:
ci: add github actions

Too busy to do it, just for the future

Too busy to do it, just for the future

If you give me the push access to all the repos, I could do it, don't worry.


text:
更换主干给实例分割网络

导师好，我想用这个Mobile net在yolact的主干上，我更改了预训练权重为这个mobilenet-yolov4-keras网络的权重，但是训练出来的效果很差，几乎没有预测框，但是我用你的原版yolact可以效果很好，请问这是什么原因，跟数据集格式有关么，yolact那个是基于coco。

你载入的权重，看下方终端，都载入了多少


text:
fit_one_epoch 函数的问题

我用的yolox-nano模型，加载的权重也是B导提供的，在COLAB上跑的。
在训练的时候报错 TypeError: 'bool' object is not callable
查了下说是某些变量身兼数职的原因。
希望B导能够解释解释

数职

还有一个问题是同时报错的
TypeError: Caught TypeError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/torch/utils/data/_utils/worker.py", line 287, in _worker_loop
data = fetcher.fetch(index)
File "/usr/local/lib/python3.7/dist-packages/torch/utils/data/_utils/fetch.py", line 49, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/usr/local/lib/python3.7/dist-packages/torch/utils/data/_utils/fetch.py", line 49, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "", line 40, in getitem
shuffle(lines)

是否因为图片太少？

我今天怀疑是我自己制作的数据集标签啊什么的对不上，所以用了B导提供的VOC那个2W+的数据集，然后裁剪了下，选了前2400张图片和相应的标签文件添加到colab进行训练，同样出现了这个问题，就是TypeError: Caught TypeError in DataLoader worker process 0.+TypeError: 'range' object is not callable。我再试试添加数据，把20000多张图片全部添加。我自己标注的数据集才450多张，后面添加的才2400张（因为我看B导视频里有一段是是2311张进行训练）。可能是图片太少了，我再试试下，感谢回复，明天出结果再回复你！

解决了，老哥。
我去翻需求txt,发现需要的Pillow==8.2.0，在colab上只有Pillow == 7.1.2，pip install之后就解决了

0 0竟然可以这样

authors: bubbliiiing jiangxiaogg

repo: bubbliiiing/yolox-pytorch


text:
🛑 Videoglancer is down

In 2080e59, Videoglancer (https://videoglancer.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Videoglancer is back up in 4245db9.

repo: budlebee/upptime-kundera


text:
Adds an author to blog posts.

See #113
This adds an author to the blog page only.
Implementation mostly based on Docsy's version.
https://github.com/google/docsy/blob/master/layouts/blog/content.html

Hey, @Beanow I'm basically fine with this. Using author could be problematic, because some may use author for something like a taxonomy lookup, but I think it should be okay.
However, could you wrap the entire p tag in the with statement?
So, instead of

    {{ with .Params.author }}By {{ . | markdownify }}{{ end}}

use:
{{ with .Params.author }}

        By {{ . | markdownify }}

{{ end}}

Would have been happy with you making the change, but here you go :+1:

authors: Beanow budparr

repo: budparr/gohugo-theme-ananke


text:
Client-side streams takes 100K Send() calls before failing after server returns error

Describe the bug
When the server side of a client stream returns an error, the Connect client does not report the error for ~100K subsequent Send() calls. The official gRPC client does not exhibit this behaviour.
From the observed behaviour it seems that the Connect client has some internal buffer that has to be exhausted before an error is returned, while the gRPC client errors as soon as the server does. The gRPC client code has a small sleep to highlight this.
I encountered this on a client-streaming endpoint that is used to periodically (every 2-5s) heartbeat to a server.
Example output of the Connect and gRPC clients. "sent N" is the number of Send() calls each client issues.
🐚 ~/dev/connect-bug $ go run ./cmd/connect-client
sent 107762
panic: aborted: an error

goroutine 1 [running]:
main.main()
	/Users/alec/dev/connect-bug/cmd/connect-client/main.go:22 +0x120
exit status 2
🐚 ~/dev/connect-bug $ go run ./cmd/grpc-client
sent 2
panic: rpc error: code = Aborted desc = an error

goroutine 1 [running]:
main.main()
	/Users/alec/dev/connect-bug/cmd/grpc-client/main.go:29 +0x1a8
exit status 2

To Reproduce
I've attached a .zip file with a full reproduction (it also includes all of the versions of tools I'm using in a Hermit environment - . ./bin/activate-hermit to use this, or install the tools via other means).

Run the server in one terminal. go run ./cmd/server
Run connect client in another terminal: go run ./cmd/connect-client
Run gRPC client in another terminal: go run ./cmd/grpc-client

connect-client-streaming-bug.zip

Hey @alecthomas! Thanks for taking a look at Connect - I've used kingpin for many command-line tools :)
The example you uploaded is very helpful in debugging. The problem is that the client is misconfigured: http.DefaultClient doesn't allow h2c connections, so even though you've got an h2c-capable server you end up with an HTTP/1.1 stream. Following https://connect.build/docs/go/deployment#h2c (or enabling TLS on the server) improves the behavior quite a bit - <100 messages before seeing the error, vs. thousands. Adding the same sleep you've got in the grpc-go code brings behavior to parity - you see the error sent by the server after sending two messages.
Unrelated to the specific behavior you're reporting, but possibly of interest, is that your example also has the client using Connect's own protocol instead of gRPC's protocol. If it's important to you that the client uses the gRPC protocol, use the connect.WithGRPC option. Either way, the changes above resolve the behavior you're seeing.
The Connect client code I ended up with looks like this:
package main

import (
	"context"
	"crypto/tls"
	"fmt"
	"net"
	"net/http"
	"time"

	"github.com/alecthomas/connectbug"
	"github.com/alecthomas/connectbug/connectbugconnect"
	"golang.org/x/net/http2"
)

func newInsecureClient() *http.Client {
	return &http.Client{
		Transport: &http2.Transport{
			AllowHTTP: true,
			DialTLS: func(network, addr string, _ *tls.Config) (net.Conn, error) {
				return net.Dial(network, addr) // see docs for some notes about this :)
			},
		},
	}
}

func main() {
	client := connectbugconnect.NewBuggyServiceClient(
		newInsecureClient(),
		"http://127.0.0.1:8999",
		// connect.WithGRPC(),
	)
	stream := client.BuggyMethod(context.Background())
	sent := 0
	for {
		err := stream.Send(&connectbug.BuggyRequest{})
		sent++
		if err != nil {
			fmt.Println("sent", sent)
			_, err := stream.CloseAndReceive()
			panic(err)
		}
		time.Sleep(10 * time.Millisecond)
	}
}

Hope that helps! I'll keep this issue open for a few days (at least until after the US long weekend) in case there's any more discussion.

Oh! If you're looking at client-side Connect behavior, you may want to follow #295 too. As part of that work, we're planning to make it easier and safer to create h2c-capable net/http clients.

Hey @akshayjshah, thanks for that and apologies for not RTFMing sufficiently. I actually read that page to set up the server with h2c, but must have blanked on the client-side 🤦 .
I did also try WithGRPC(), but it failed in the same way for what I now realise were the same reasons.
I'm really enjoying Connect, thanks. It is refreshingly straightforward code unlike the Google gRPC implementation, I really love its use of the standard Go HTTP packages, and how it supports HTTP/1 out of the box.
Speaking of that, has there been any thought to supporting the api.http annotations? Though thinking about it briefly, it could probably be implemented via HTTP middleware that takes the FileDescriptor containing a service, and remapping incoming requests.
PS. I'm happy to hear you're a Kingpin enjoyer :)

Speaking of that, has there been any thought to supporting the api.http annotations? Though thinking about it briefly, it could probably be implemented via HTTP middleware that takes the FileDescriptor containing a service, and remapping incoming requests.

I think you basically nailed it - I'm happy to have support live out in the ecosystem, but it doesn't need to be in connect-go itself.

authors: akshayjshah alecthomas

repo: bufbuild/connect-go


text:
Set max repeated length for DOS protection

Rationale
protobuf is very versatile format and can exacerbate DOS issues with amplification attacks. In Javascript 1 byte of protobuf can expand to ~80 bytes using lists.
In many applications it's unreasonable to allow lists of lengths of hundred thousands, and a sane default is known in advance.
Proposal
Add an option to limit repeated length at decode time. If more items that said length are found, ignore them or throw an error. proto2 or proto3 format could accommodate the feature with:

With custom options

message Sample {
  repeated string str = 1 [max_length_ignore = 100] ;
}

Prepending comments to the field

message Sample {
  repeated string str = 1; // __max_length_ignore=100
}

Hi @dapplion.  Appreciate the issue, but I don't think this is something we plan on implementing any time soon.  We're also not aware of any other implementation providing such a feature.
Just for a possible alternative, you can maybe attempt to write your own parser based on what we have and potentially monkeypatch it?   The relevant code is here.

Just for a possible alternative, you can maybe attempt to write your own parser based on what we have and potentially monkeypatch it? The relevant code is here.

Thanks for the pointer will look into it. For all consumers of the protocol I work with (Rust, Go, Java, Nim) all had to write their own DOS safe protobuf decoders. Currently I use the generator then modify the output since our protobuf structures do not change often.

Hi @dapplion.  Going to close this issue since we don't plan to implement this any time soon.  If you have any problems or questions, though, feel free to open a new issue.

repo: bufbuild/protobuf-es


text:
Added performance module

Now sentry transaction events are also stored.
They are vilible only in performance module.
Added ajax pagination to handle listing them.

Hi. @js361014. Thank you for PR!!! I'm on vacation and will be available in 5 days.

@butschster Do you remember about this PR?

Hi @js361014 !
Sorry, I had to move in another place( I will check it!

repo: buggregator/app


text:
please add Prefix (like "bc" for bugsnag-cocoa) to method names to avoid "multiple methods name error(s)"errors

So in our big project we have a method called "mergeWith:" and we can´t rename our method name(s) quickly. And i see bugsang is very small ;) . SDWebImage adds, for example, the prefix "sd".

I agree with @Mazyod that it doesn't seem directly related to the library - but either way we have re-written the library to use KSCrash now so its likely that will help.

authors: MirkoBrunner snmaynard

repo: bugsnag/bugsnag-cocoa


text:
Set a non zero exit code on upload errors

Fixes #38.
Tested with the following,
bin/bugsnag-dsym-upload --upload-server https://httpstat.us/503 dsym_archive_test.zip && echo success

Uploading UUID: 04E51379-A668-3ECA-975C-50EE0D2921CA (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/04E51379-A668-3ECA-975C-50EE0D2921CA.dSYM/Contents/Resources/DWARF/libswiftCoreImage.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 1066EDB0-4E4E-393D-845B-50BFDE11191A (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/1066EDB0-4E4E-393D-845B-50BFDE11191A.dSYM/Contents/Resources/DWARF/libswiftCoreImage.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 14D5AAC3-E157-3015-9302-442161BA272E (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/14D5AAC3-E157-3015-9302-442161BA272E.dSYM/Contents/Resources/DWARF/libswiftUIKit.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 289F600E-8605-3D5A-89A6-8786BFE2D58D (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/289F600E-8605-3D5A-89A6-8786BFE2D58D.dSYM/Contents/Resources/DWARF/libswiftDarwin.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 3A22AA68-B3B6-3076-AB63-154FE3F0ED0F (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/3A22AA68-B3B6-3076-AB63-154FE3F0ED0F.dSYM/Contents/Resources/DWARF/libswiftDispatch.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 412AD5C2-A5B6-3EC1-8C9C-5629E4D983A6 (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/412AD5C2-A5B6-3EC1-8C9C-5629E4D983A6.dSYM/Contents/Resources/DWARF/libswiftCore.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 4BC83911-F817-3475-BAC9-B154D7C8CF0B (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/4BC83911-F817-3475-BAC9-B154D7C8CF0B.dSYM/Contents/Resources/DWARF/libswiftCore.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 8039D68A-06AA-38B6-AA20-9E48819644D5 (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/8039D68A-06AA-38B6-AA20-9E48819644D5.dSYM/Contents/Resources/DWARF/bugsnag-example
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 8C7ACF0A-DB82-3755-BC7E-A664C7B9B60B (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/8C7ACF0A-DB82-3755-BC7E-A664C7B9B60B.dSYM/Contents/Resources/DWARF/libswiftUIKit.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 9189028A-7DB8-3771-B939-8D6CE575BC9B (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/9189028A-7DB8-3771-B939-8D6CE575BC9B.dSYM/Contents/Resources/DWARF/libswiftCoreGraphics.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 9E90E073-F509-3383-9A11-C86773C680E6 (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/9E90E073-F509-3383-9A11-C86773C680E6.dSYM/Contents/Resources/DWARF/bugsnag-example
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: 9F9D30DF-41B9-3F60-B8A6-8D8353904C22 (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/9F9D30DF-41B9-3F60-B8A6-8D8353904C22.dSYM/Contents/Resources/DWARF/libswiftQuartzCore.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: BDA876C8-6DE3-3A09-BECA-4B29FBE77193 (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/BDA876C8-6DE3-3A09-BECA-4B29FBE77193.dSYM/Contents/Resources/DWARF/libswiftDarwin.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: C92AF44A-6C4A-3057-AFC1-5102CF33739B (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/C92AF44A-6C4A-3057-AFC1-5102CF33739B.dSYM/Contents/Resources/DWARF/libswiftDispatch.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: CA8A2708-2A8A-3404-B5DF-DC044FC8B2C4 (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/CA8A2708-2A8A-3404-B5DF-DC044FC8B2C4.dSYM/Contents/Resources/DWARF/libswiftQuartzCore.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: CF864347-A083-3324-8A74-5B535837EE96 (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/CF864347-A083-3324-8A74-5B535837EE96.dSYM/Contents/Resources/DWARF/libswiftObjectiveC.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: D34FD74B-45C6-3EFB-B665-5D73DC7DAFA6 (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/D34FD74B-45C6-3EFB-B665-5D73DC7DAFA6.dSYM/Contents/Resources/DWARF/libswiftCoreGraphics.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: E24763FA-7629-3669-8678-D6F6DE1451D9 (armv7) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/E24763FA-7629-3669-8678-D6F6DE1451D9.dSYM/Contents/Resources/DWARF/libswiftFoundation.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: EF889A99-DDB5-3264-BDA4-836A39557D0F (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/EF889A99-DDB5-3264-BDA4-836A39557D0F.dSYM/Contents/Resources/DWARF/libswiftObjectiveC.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

Uploading UUID: F88D5870-EA71-3629-BF3E-EC28BED21647 (arm64) /var/folders/0y/bts_0rzj5q91dn9y1wdjgcjh0000gn/T/bugsnag-dsym-upload.XXX.mPkY7YEL/F88D5870-EA71-3629-BF3E-EC28BED21647.dSYM/Contents/Resources/DWARF/libswiftFoundation.dylib
curl: (22) The requested URL returned error: 503 Service Unavailable

20 files failed to upload

Success case also tested and works as expected.
I looked into adding tests but I couldn't see that the testing framework allows verifying exit codes.

@tomlongridge can we get this one merged down so I'm not the person reviewing my own code on the other PR?

repo: bugsnag/bugsnag-dsym-upload


text:
400 RangeError: Maximum Call Stack size exceeded

I get this when uploading A file using POST request.
Using latest Express.js

var express = require('express')
	, routes = require('./routes')
	, http = require('http')
	, path = require('path')
	, mongoose = require('mongoose')
	, MongoStore = require('connect-mongo')(express)
	, mailer = require('nodemailer')

var bugsnag = require("bugsnag");
bugsnag.register("My API Code")

var app = exports.app = express();

// all environments
app.enable('trust proxy');
app.set('port', process.env.PORT || 3000); // Port
app.set('views', __dirname + '/views');
app.set('view engine', 'jade'); // Templating engine
app.set('view cache', true); // Cache views
app.set('app version', '0.0.2'); // App version
app.locals.pretty = process.env.NODE_ENV != 'production' // Pretty HTML outside production mode

app.use(bugsnag.requestHandler); // UnCommenting this line causes RangeError
app.use(express.logger('dev')); // Pretty log
app.use(express.limit('25mb')); // File upload limit
app.use("/", express.static(path.join(__dirname, 'public'))); // serve static files
app.use(express.bodyParser()); // Parse the request body
app.use(express.cookieParser()); // Parse cookies from header
app.use(express.methodOverride());
app.use(express.session({ // Session store
	secret: "mysecret",
	store: sessionStore,
	cookie: {
		maxAge: 604800000 // 7 days in s * 10^3
	}
}));
app.use(express.csrf()); // csrf protection

// development only
if ('development' == app.get('env')) {
	app.use(express.errorHandler()); // Let xpress handle errors
	app.set('view cache', false); // Tell Jade not to cache views
}

var server = http.createServer(app)
server.listen(app.get('port'), function(){
	console.log('Express server listening on port ' + app.get('port'));
});

// routes
//routes.router(app);

app.use(bugsnag.errorHandler);

Am I doing something wrong?

I'm seeing this issue as well. It happens when a file is uploaded through a POST request and Nginx is being used as a reverse proxy. I don't see the issue locally when I access the Node.js app directly on port 3000. But on staging, where Nginx proxies port 80 to the Node app, the RangeError appears.
I'm using Node v0.10.33, but I don't think that's the issue here. I believe BugSnag's Express request handler app.use(bugsnag.requestHandler) is going into some kind of infinite callback loop in this scenario that's exhausting the stack.

@justin uncommenting the app.use fixes this for me, although you lose some
reporting such as request info
On Monday, January 5, 2015, Justin Klemm notifications@github.com wrote:

I'm seeing this issue as well. It happens when a file is uploaded through
a POST request and Nginx is being used as a reverse proxy. I don't see the
issue locally when I access the Node.js app directly on port 3000. But on
staging, where Nginx proxies port 80 to the Node app, the RangeError
appears.
I'm using Node v0.10.33, but I don't think that's the issue here. I
believe BugSnag's Express request handler app.use(bugsnag.requestHandler)
is going into some kind of infinite callback loop in this scenario that's
exhausting the stack.
—
Reply to this email directly or view it on GitHub
https://github.com/bugsnag/bugsnag-node/issues/16#issuecomment-68788554.

@matejkramny Thanks, yea, commenting out that line prevents the issue for me too. I can deal with the lost info.
It's probably worth Bugsnag digging into this though. It look me a little while to track down the issue and it's particularly "dangerous" because the bug seemingly only occurs when a reverse proxy is used (which can mean that things will work fine during local development, then break in production).

Yeah - we have left the issue open as it's one that is hard to reproduce. With this nginx lead though we might be able to track it down! Hopefully I'll get some time soon to take a deeper look. Thanks!

Cool, let me know if I can do anything to help.
You should be able to reproduce it if you setup a simple Express app with a POST route, at say localhost:3000. Then setup Nginx to forward some local domain (ex: http://express.localhost) to it using ngx_http_upstream_module. If you setup an HTML form with a input[type="file"] element and POST to the app's route (through Nginx), you should see it.

+1

I'm trying and failing to replicate this using https://github.com/ConradIrwin/express-eg. I'd love for one of you to take a look and see if you can make it fail.

Hi, just curious, is this problem finally be resolve?
I encountered a same weird problem, and I cannot debug the core reason. and the scenario is very similar with this issue. I hope I can get some inspiration with how this issue got fixed.

I ended up just disabling app.use(bugsnag.requestHandler) and relying on only app.use(bugsnag.errorHandler). This was pretty long time ago and it was while using ExpressJS v3. We've since upgraded to ExpressJS v4. We still have the code commented out because we rarely see any issues where it's necessary. I've been curious as to whether the v4 upgrade fixed it -- but haven't tested.

authors: ConradIrwin emadd justinklemm matejkramny snmaynard xiaoshimimi

repo: bugsnag/bugsnag-node


text:
Taproot Support

Taproot handling.

@mflaxman, you're going to want to start looking at this. It can validate Taproot tx's, not create Taproot tx's yet.

regarding anonymous functions being passed around, it's the only way to handle the hash type. Taproot adds a new sighash, SIGHASH_DEFAULT, which means the same thing as SIGHASH_ALL, but the actual sig hash is different because SIGHASH_XXX gets put into the message that gets hashed. Therefore, I can't just assume SIGHASH_ALL everywhere.
You essentially need a callback from the actual virtual machine to the signature hashing part or pass the transaction object all the way down to the op code level. We can also add a context object or something, but it's all going to be hairy. Signature verification requires the hash type, which is in the signature itself.
That said, this does allow us to handle other SIGHASH types like SIGHASH_SINGLE, SIGHASH_NONE and SIGHASH_ANYONECANPAY. This will prep us for once SIGHASH_ANYPREVOUT makes it in.

Actually, maybe sending the tx object to the script evaluation engine isn't a bad idea. It will clean up the api since that means we no longer need to pass in the witness separately, but we do need to pass in the input index as well. Let me think about this.

Actually, I think there's another way. I can just pass the sigmessage in and add the sig hash stuff at the op code level.

slept on it and you can't just send over the sig message.

I changed the way sig hash works to just pass through the tx object and the input index. The change wasn't that bad, it turns out.

Updating pypi now

Pypi is now up to date

authors: jimmysong mflaxman

repo: buidl-bitcoin/buidl-python


text:
Chapter 2: ROOT_URL introduced without explanation

The following is not explained, and is not motivated at all.
const ROOT_URL = process.env.ROOT_URL || `http://localhost:${port}`;

What is process.env?
Why must we use a default if we have process.env.ROOT_URL?
Do we always have ROOT_URL?
Who provide it to us?
Must we provide to ourselves?
If we always have process.env.ROOT_URL, remove the code.
If not, introduce this code ONLY WHEN NEEDED, not now.

@realtebo Good point.
I think ROOT_URL is used in Chapter 8 when we prepare our app for deployment (https://github.com/builderbook/builderbook/blob/master/book/8-end/lib/api/getRootUrl.js).
I see your point of introducing ROOT_URL in Chapter 8, not Chapter 2.
I'll push changes tomorrow.
Thanks.

repo: builderbook/builderbook


text:
Ensure statsd commands are flushed after each run

This PR updates StatsD client library and flushes statsd commands at the end of Collect call to fix #37 This is something that happened to us while using the statsd backend without the -interval parameter.
I've tested the resulting binary with and without -interval to check that don't change its behaviour.

👌

authors: lox theist

repo: buildkite/buildkite-metrics


text:
Specifying --pipeline option to init causes panic

CLI version: 0.3.0
OS: Arch linux
→ bk init --pipeline=research
Checking for pipeline file: .buildkite/pipeline.yml ✅
Checking for git repository and remote: https://github.com/quantopian/research_env ✅
Enter passphrase to unlock /home/irl/.buildkite/keyring/:
panic: runtime error: index out of range

goroutine 1 [running]:
github.com/buildkite/cli.InitCommand(0xa67ac0, 0xe56ae8, 0xa65020, 0xc00017dd70, 0x0, 0x0, 0x0, 0x7ffe0394a4e7, 0x8, 0x7f3124a12290, ...)
        /Users/lachlan/go/src/github.com/buildkite/cli/cmd_init.go:99 +0x1c5f
main.run.func5(0xc0001ea000, 0x409dc3, 0x936360)
        /Users/lachlan/go/src/github.com/buildkite/cli/cmd/bk/main.go:192 +0xb5
gopkg.in/alecthomas/kingpin%2ev2.(*actionMixin).applyActions(0xc0001b0498, 0xc0001ea000, 0x0, 0x0)
        /Users/lachlan/go/pkg/mod/gopkg.in/alecthomas/kingpin.v2@v2.2.6/actions.go:28 +0x6d
gopkg.in/alecthomas/kingpin%2ev2.(*Application).applyActions(0xc0001e4690, 0xc0001ea000, 0x0, 0x0)
        /Users/lachlan/go/pkg/mod/gopkg.in/alecthomas/kingpin.v2@v2.2.6/app.go:557 +0xdf
gopkg.in/alecthomas/kingpin%2ev2.(*Application).execute(0xc0001e4690, 0xc0001ea000, 0xc000176b50, 0x1, 0x1, 0x0, 0x0, 0x1, 0xc00019c2e8)
        /Users/lachlan/go/pkg/mod/gopkg.in/alecthomas/kingpin.v2@v2.2.6/app.go:390 +0x8f
gopkg.in/alecthomas/kingpin%2ev2.(*Application).Parse(0xc0001e4690, 0xc0000a0010, 0x3, 0x3, 0x1, 0xc00019c2b8, 0x0, 0x1)
        /Users/lachlan/go/pkg/mod/gopkg.in/alecthomas/kingpin.v2@v2.2.6/app.go:222 +0x1fa
main.run(0xc0000a0010, 0x3, 0x3, 0x9f9d88)
        /Users/lachlan/go/src/github.com/buildkite/cli/cmd/bk/main.go:356 +0x2a16
main.main()
        /Users/lachlan/go/src/github.com/buildkite/cli/cmd/bk/main.go:21 +0x6e

Without specifying pipeline:
→ bk init
Checking for pipeline file: .buildkite/pipeline.yml ✅
Checking for git repository and remote: https://github.com/quantopian/research_env ✅
Enter passphrase to unlock /home/irl/.buildkite/keyring/:
Checking for buildkite pipeline: Created https://buildkite.com/quantopian/research-env ✅
Checking github repository config for quantopian/research_env: Created webhook ✅

Ok! Your project is ready to go at https://buildkite.com/quantopian/research-env 🚀

I think this one can be closed with the v3 release, so I'm going to do that but invite it to be re-opened if the issue persists (we don't plan on supporting v2 going forward).

authors: irlevesque mcncl

repo: buildkite/cli


text:
Switch to direct mutations for deleting team members

This fixes various issues with Relay being a bit silly when it tries to reload connections.

Sorry, I should have marked this as WIP - cause it wasn't quite done yet. I actually broke a few things (like numbers in badges updating with this change). We may need to review it!

@keithpitt can do

authors: keithpitt toolmantim

repo: buildkite/frontend


text:
Label selections works randomly

Bug report
label selection works like shit
Steps to reproduce
Not clear yet, but trying to open multiple issues in a row, often causes labels not to be selected properly.

Maybe wait for labels menu to appear in the DOM.
https://github.com/uzairfarooq/arrive

repo: buildo/github-workflow-pal


text:
#68: datepicker layout may break with different fonts (closes #68)

Issue #68
Test Plan
tests performed
layout looks fine in every state:

is flexible (modified width variable to 400px):

tests not performed (domain coverage)

At times not everything can be tested, and writing what hasn't been tested is just as important as writing what has been tested.

An example of partial test is a field displaying 4 possible values. If 3 values are tested, with screenshots, and 1 is not, then it should be mentioned here.}

👍

authors: FrancescoCioria francescogior

repo: buildo/rc-datepicker


text:
Public Gateway Is Not Supported Anymore - Setup a Dedicated Gateway

As we used ipfsinfura link in line number 5.
infura has stopped free gateways as of now unable to upload files from create-product page..
is there any way to over come this issue??
import React, { useState } from "react";
import { create } from "ipfs-http-client";
import styles from "../styles/CreateProduct.module.css";

const client = create("https://ipfs.infura.io:5001/api/v0");

const CreateProduct = () => {

  const [newProduct, setNewProduct] = useState({
    name: "",
    price: "",
    image_url: "",
    description: "",
  });
  const [file, setFile] = useState({});
  const [uploading, setUploading] = useState(false);

  async function onChange(e) {
    setUploading(true);
    const files = e.target.files;
    try {
      console.log(files[0]);
      const added = await client.add(files[0]);
      setFile({ filename: files[0].name, hash: added.path });
    } catch (error) {
      console.log("Error uploading file: ", error);
    }
    setUploading(false);
  }

  const createProduct = async () => {
    try {
      // Combine product data and file.name
      const product = { ...newProduct, ...file };
      console.log("Sending product to api",product);
      const response = await fetch("../api/addProduct", {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
        },
        body: JSON.stringify(product),
      });
      const data = await response.json();
      if (response.status === 200) {
        alert("Product added!");
      }
      else{
        alert("Unable to add product: ", data.error);
      }

    } catch (error) {
      console.log(error);
    }
  };

  return (

Create Product

            <input
              type="file"
              className={styles.input}
              // accept=".zip,.rar,.7zip"
              placeholder="Emojis"
              onChange={onChange}
            />
            {file.name != null &&
{file.filename}
}

              <input
                className={styles.input}
                type="text"
                placeholder="Product Name"
                onChange={(e) => {
                  setNewProduct({ ...newProduct, name: e.target.value });
                }}
              />
              <input
                className={styles.input}
                type="text"
                placeholder="0.01 USDC"
                onChange={(e) => {
                  setNewProduct({ ...newProduct, price: e.target.value });
                }}
              />

              <input
                className={styles.input}
                type="url"
                placeholder="Image URL ex: https://i.imgur.com/rVD8bjt.png"
                onChange={(e) => {
                  setNewProduct({ ...newProduct, image_url: e.target.value });
                }}
              />

            <textarea
              className={styles.text_area}
              placeholder="Description here..."
              onChange={(e) => {
                setNewProduct({ ...newProduct, description: e.target.value });
              }}
            />

            <button
              className={styles.button}
              onClick={() => {
                createProduct();
              }}
              disabled={uploading}
            >
              Create Product
            </button>

  );
};

export default CreateProduct;

Yeah, Just change it from
const client = create("https://ipfs.infura.io:5001/api/v0");

to
const client = create({
  host: 'ipfs.infura.io',
  port: 5001,
  protocol: 'https',
  headers: {
    authorization: 'Bearer ' + btoa(process.env.InfuraIPFSID + ':' + process.env.InfuraIPFSSecret)
  },
 apiPath: '/api/v0'
});

You get the InfuraIPFSID and InfuraIPFSSecret from your Infura dashboard and it is free for up to a size of uploaded/pinned items

repo: buildspace/solana-pay-starter


text:
Minimize main window during training

Minimize main window during training and restore when finished.
If it is restored by hand during training it will not be possible to re-minimize it until the end
(put a button in the "Training progress" window to be able to minimize it on request?)

I like your idea. I hope you don't mind I've implemented it bit differently in the newest version.

I'm closing the request, but please let me know if you'd prefer it working differently.

Well done. Thank you

repo: buliasz/tesstrain-windows-gui


text:
🛑 GOTO Parking is down

In 3f0eb2c, GOTO Parking (https://gotoparking.ro) was down:

HTTP code: 403
Response time: 832 ms

Resolved: GOTO Parking is back up in f2ba822.

repo: buligadragos/UpTime


text:
🛑 VODA-SA is down

In dd8a607, VODA-SA ($SECRET_SITE2) was down:

HTTP code: 403
Response time: 1070 ms

Resolved: VODA-SA is back up in 054b1d1.

repo: buluma/uptime


text:
PWA not available due to failing to load manifest.json

Just started trying out your app, Its great!
I wanted to "install" your app as desktop app, however the option isn't available. I see that the service worker that is packaged with the Create React App exists sw.js, but the manifest.json is missing.
Looking a bit deeper I see that you do have a manifest.json and the file loads correctly on the landing page. But when using the player it does not load the manifest.json. It may be something with being in the /app directory and/or some url rewrite rules in express 🤔

@Khaoz-Topsy Thanks for reporting this issue. Yeah I see that manifest.json is hosted at /app/manifest.json but my manifest "start_url" is set to /app/library which doesn't make sense since the entire app is hosted at /app.
I think this may be the problem but I'm not entirely sure.

@Khaoz-Topsy Thanks for reporting this issue. Yeah I see that manifest.json is hosted at /app/manifest.json but my manifest "start_url" is set to /app/library which doesn't make sense since the entire app is hosted at /app.
I think this may be the problem but I'm not entirely sure.

c18ab3d6491a77e16b46e611fedd1b60458d927b Allows "installation" from the landing page which will redirect to /app/library. Still having trouble getting the manifest to load correctly from /app but this will do for now

c18ab3d6491a77e16b46e611fedd1b60458d927b Allows "installation" from the landing page which will redirect to /app/library. Still having trouble getting the manifest to load correctly from /app but this will do for now

authors: Khaoz-Topsy bundit

repo: bundit/kord-app


text:
Fail gracefully when attempting to request from an unknown URI scheme

Closes #4953

@homu r+

:pushpin: Commit 609f758 has been approved by indirect

:hourglass: Testing commit 609f758 with merge eb20f97...

:sunny: Test successful - status

authors: homu indirect segiddins

repo: bundler/bundler


text:
[SpecSet] Sort by name in #tsort

Closes #5696
This is required for backwards compatibility, see
issue #5696  for an example. The issue is that previous versions of bundler would have the load path in one (correct) order, and master has them in another (correct) order. So some projects depend on the load path ordering when multiple gems have the same requirable file.

[x] Test case

Is the issue here that multiple gems have the same files, and a require needs to hit the correct gem first for things to work?

Is the issue here that multiple gems have the same files, and a require needs to hit the correct gem first for things to work?

Yup! updated PR description

Looks good. @bundlerbot r+

Thanks for the fix!

Released in 1.15.2, sorry for the long delay

No worries, today was the first time I've seen the bug in action. Thanks for the release. I'm going to push this out to Heroku as soon as I can https://github.com/heroku/heroku-buildpack-ruby/pull/602.

authors: indirect schneems segiddins


text:
Fix a typo on a spec comment

What was the end-user problem that led to this PR?
The problem was there's a typo on a comment.
What was your diagnosis of the problem?
My diagnosis was that typos are bad because they difficult reading and distract devs.
What is your fix for the problem, implemented in this PR?
My fix is to spell bundler properly.
Why did you choose this fix out of the possible options?
I chose this fix because bundler is the only word that makes sense in the context :)

@bundlerbot r+


text:
🛑 doubledouble is down

In 34e57da, doubledouble (https://doubledouble.top/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: doubledouble is back up in 86f26d9 after 5 minutes.


text:
Implement missing Optimizers

Read the section on optimization before trying to implement an optimizer: https://github.com/burn-rs/burn/blob/main/ARCHITECTURE.md#optimization

[X] SGD
[X] Adam
[ ] AdamW
[ ] RMSProp
[ ] AdaGrad

Hi, I'm interested in this and working on RMSProp. is there any other guy who has already started on it?

@AuruTus go ahead and claim it. @wdoppenberg currently has an open PR https://github.com/burn-rs/burn/pull/566 for AdamW. You can see how it's been done.

@AuruTus go ahead and claim it. @wdoppenberg currently has an open PR #566 for AdamW. You can see how it's been done.

It's a WIP still, but I'd be happy to collaborate in some way if you're interested. Feel free to message me on discord.

Hello. I'd like to work on AdaGrad if there's no one already working on it.

Hello. I'd like to work on AdaGrad if there's no one already working on it.

go ahead ! happy coding.

hi @CohenAriel , I noticed that the common weight_decay 's transform method has some bugs, so almost all optimizers will be affected. Can use temporary fix to make a workaround now. I think I can fix it later but there are still some bugs in my RMSProp now 😅.
The bug code and discussion can be refered here on discord
and this is my temp impl for ref:
    /// temp fix for Transform.
    pub fn transform_temp_fix<const D: usize>(
        &self,
        grad: Tensor<B, D>,
        tensor: Tensor<B, D>,
        state: Option<WeightDecayState<B, D>>,
    ) -> (Tensor<B, D>, Tensor<B, D>, WeightDecayState<B, D>) {
        let grad = match state {
            Some(state) => state.grad_last_step.mul_scalar(self.penalty).add(grad),
            None => tensor.clone().mul_scalar(self.penalty).add(grad),
        };

        (grad, tensor.clone(), WeightDecayState::new(tensor))
    }

Wow, thanks! I guess I can just not use weight decay in the test until it's fixed

@CohenAriel @wdoppenberg hi masters, there's some transposition behavior of Burn Tensor, which makes the grad passed in is also transposed. Hope you could notice it when testing against PyTorch.
For now, it's much quicker to just change PyTorch script with torch.transpose(linear.weight.data, 0, 1)
disccussion on discord

my new script
import torch
from torch.nn import Linear
from torch.optim import RMSprop

# Define a Linear layer with given weights and biases

def given_linear_layer(weights: torch.Tensor, biases: torch.Tensor) -> Linear:
    out_features, in_features = weights.shape
    layer = Linear(in_features, out_features, bias=True)

    layer.weight.data = torch.FloatTensor(weights)
    layer.bias.data = torch.FloatTensor(biases)

    return layer

def test_rmsprop():
    # torch.set_printoptions(precision=6, sci_mode=True)
    torch.set_printoptions(precision=6, sci_mode=False)

    LEARNING_RATE = 0.01

    prior_weights = torch.tensor([
        [-0.3206, 0.1374, 0.4043, 0.3200, 0.0859, 0.0671],
        [0.0777, -0.0185, -0.3667, 0.2550, 0.1955, -0.2922],
        [-0.0190, 0.0346, -0.2962, 0.2484, -0.2780, 0.3130],
        [-0.2980, -0.2214, -0.3715, -0.2981, -0.0761, 0.1626],
        [0.3300, -0.2182, 0.3717, -0.1729, 0.3796, -0.0304],
        [-0.0159, -0.0120, 0.1258, 0.1921, 0.0293, 0.3833],
    ])
    prior_bias = torch.tensor(
        [-0.3905, 0.0884, -0.0970, 0.1176, 0.1366, 0.0130])

    linear = given_linear_layer(
        torch.clone(torch.transpose((prior_weights), 0, 1)),
        torch.clone(prior_bias)
    )

    x_1 = torch.tensor([
        [0.6294, 0.0940, 0.8176, 0.8824, 0.5228, 0.4310],
        [0.7152, 0.9559, 0.7893, 0.5684, 0.5939, 0.8883],
    ], requires_grad=True)

    x_2 = torch.tensor([
        [0.8491, 0.2108, 0.8939, 0.4433, 0.5527, 0.2528],
        [0.3270, 0.0412, 0.5538, 0.9605, 0.3195, 0.9085],
    ], requires_grad=True)

    RMSPROP_KWARGS = {
        "lr": LEARNING_RATE,
        "alpha": 0.99,
        "eps": 1e-8,
        "weight_decay": 0.05,
        "momentum": 0.9,
        "centered": False,
    }

    optimizer = RMSprop(
        linear.parameters(),
        **RMSPROP_KWARGS
    )

    # First forward-backward pass and optimization step
    optimizer.zero_grad()
    y = linear(x_1)
    y.backward(torch.ones_like(y))
    optimizer.step()

    # Second forward-backward pass and optimization step
    optimizer.zero_grad()
    y = linear(x_2)
    y.backward(torch.ones_like(y))
    optimizer.step()

    # Print updated state
    print(
        f"\nUpdated layer weights: \n{torch.transpose(linear.weight.data, 0, 1)}")
    # print(
    #     f"\nUpdated layer weights: \n{linear.weight.data}")
    print(f"\nUpdated layer bias: \n{linear.bias.data}")

    # Print difference between prior and updated weights
    print(
        f"\nWeight difference: \n{torch.transpose(linear.weight.data - prior_weights, 0, 1)}")
    # print(
    #     f"\nWeight difference: \n{linear.weight.data - prior_weights}")
    print(f"\nBias difference: \n{linear.bias.data - prior_bias}")

@louisfd , @nathanielsimard it seems we completed all the tasks. Can we close it?

Awesome, thanks everyone 🎉

authors: AuruTus CohenAriel antimora louisfd nathanielsimard wdoppenberg

repo: burn-rs/burn


text:
Figure out why tile opacity is nondetermistic

On the client, sometimes a water tile is shown as a solid tile. Not sure why. Might need to just add the boolean flags for nearest neighbor interpolation to the contexts used to store tile information on the client.

This turned out to be a result of browser presampling. I've changed the steganographic logic to only use the RGB channels for the time being. Means one less channel to pack info into, which means two less fields that can be embodied in the same image. That being said, I wasn't using the blue channel for anything, so luckily it was as easy as switching the alpha determination to read from blue instead.
Still, kind of a bummer.
More info here: https://github.com/burninggarden/burninggarden/blob/master/game/system/solids.js#L261

repo: burninggarden/burninggarden

license: isc


text:
🛑 butadora pgae is down

In aa94b7a, butadora pgae (https://butadora.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: butadora pgae is back up in 80a6576.


text:
Setup pre-commit

We decided on using precommit: https://pre-commit.com/
To include:

ES lint
detect secrets

Maybe we should check out the sso-keycloak pre-commit.yml and .pre-commit-config.yaml?

@BCerki proposed splitting GitHub action enforcing pre-commit from this issue. @BryanGK would that change your plans for #13 at all?

@BCerki proposed splitting GitHub action enforcing pre-commit from this issue. @BryanGK would that change your plans for #13 at all?

@wenzowski I don't think so, as my changes are for pre-commit on your local machine

Perfect, let's adopt that split then. Issue breakdown for the win! 🥇

authors: BryanGK mikevespi wenzowski


text:
[建议]老虎机抽奖添加中奖指示器（箭头/线段等）

类似这种多列横向滚动，抽奖结束后没办法表示中奖奖品位置，且其余位置顺序未打乱（竖向滚动如果超出三行同理）

下图是csgo游戏中抽奖界面，黄线在停止滚动后落在奖品上，还有边缘模糊功能

仅仅是建议，自己用css实现会被canvas遮挡，也不懂能不能直接用canvas实现 - 。 -

你可以看一下官网 => 示例 => 完整示例 => 最后一个仿滴滴的demo, 那个指针是通过图片的方式在blocks里面引入的

确实可以,之前有一瞬间想过用背景图片……
还有就是非中奖项乱序显示应该会更好点

可以乱序显示, 请仔细看老虎机提供的测试Demo

我的意思是如果是多列显示的情况，非中奖行/列（上图的电影票和放映带）乱序，可能让滚动逻辑更复杂了...

而且奖品位置也是可以打乱的, 只是你没有配置而已, 也请参考文档!

不过你确实提醒到我了, 现在官网缺少一个打乱奖品排序的demo, 今晚我补充一个

感谢指教🤡

那这样是不是可以在自定义顺序的前提下做个默认的乱序配置

没必要, 你这就把简单的事搞复杂了, order你们可以随便配置

authors: Itswag buuing

repo: buuing/lucky-canvas


text:
When total sum of persisted panel sizes differs from 100, no resize is possible

The issue can be easily reproduced by going to https://react-resizable-panels.vercel.app/examples/persistence and manually altering one of panel percentage sizes inside localStorage's value under PanelGroup:sizes:persistence key.
The tricky question here is how does the app come to such a corrupted state in localStorage? Unfortunately I cannot share any insight at the moment. The only thing I know is that several users came to me complaining about inability to adjust panel sizes and the only thing I found in their browsers were those size discrepancies.

Fixed in #230

authors: bvaughn tsufiev

repo: bvaughn/react-resizable-panels