text:
sps or pps is null when work with MediaProjection

Hi @pedroSG94
I copied  ScreenActivity And ScreenService from the master branch.
switch Kotlin to java.
I run my code on an Android TV
Any suggestion for me. Thanks!

Solved by foring software encoding.
genericStream.forceCodecType(CodecUtil.CodecType.SOFTWARE, CodecUtil.CodecType.SOFTWARE); prepared = genericStream.prepareVideo(width, height, vBitrate, rotation) &&  genericStream.prepareAudio(sampleRate, isStereo, aBitrate);

Hello,
If the demo is working and you code is not working fine. I can't tell you the reason without without check your code.
For now, my only suggestion without check the code is that you should make sure that you added this line:
https://github.com/pedroSG94/RootEncoder/blob/master/app/src/main/java/com/pedro/streamer/screen/ScreenService.kt#L77
As you can read in the comment, this is important using mediaprojection because that api only render if you update the screen content. This line force the library to render in a constant interval no matter if the screen content change.
This could be related with your case because if you never update the screen, maybe you encoder never produce the sps or pps because need more frames to do it.

I did not realize the named parameters of kotlin
genericStream.prepareVideo(width, height, vBitrate, rotation)
should be
genericStream.prepareVideo(width, height, vBitrate, 15, 2, rotation)

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Stream contents of GLSurfaceView

Is there an example to stream contents of a GLSurfaceView over RTSP?
Only relevant code I could find is from commit a3ff2ca07cf0952b1d68ab655f1d04b08804a90d in 2018. Why is this removed? seems to be a handy feature.
Also as others have said great work! Thank you!

Hello,
I removed that example because OpenGlView class is similar to GLSurfaceView and I can personalyze more OpenGlView.
In both cases you have a SurfaceTexture that you need to render.


text:
Tap to focus functionality to Camera1

Not very sensitive and need to little long press but we can tweak it later.

Hello,
This a good funcionality and is working for camera1.
Also, this value, I'm not sure if this should be constant (I wrote it only for testing purposes):
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/blob/master/encoder/src/main/java/com/pedro/encoder/input/video/Camera1ApiManager.java#L485
After that, the only problem is camera2.

I am currently working on camera2, then we will discuss about the correct weight of Camera.area

Why do I run demo tips Disconnect

Do I have to write my user name and password

I merged this because it is 20 days without update. Please, open other MR if you finally update it for camera2

source: gharchive/pull-request

authors: iqiluwxy mustafaboleken pedroSG94


text:
Small things

Couple of things when GitHub-installing the package on another system. Just works in general but small glitches

There is no vignette to describe the PMML export functionality, only the scripts in "extra" which should probably go there
The main README should probably list the (few) vignettes that we support if not a quick example straight there
The import of XML or jsonlite is for some reason required when running the adm2pmml code; something funky with the dependencies somewhere
ADM-Reporting vignette has an ugly header showing the vignette meta data
The graphs in the adm-datasetanalysis vignette are really small (too small) but the ones in reporting are ok - probably because the header got screwed up as per previous point
[FIXED] Filtering in the JSON export version is currently not supported
It looks like import of "fasttime" is also mandatory when using getModelsFromDatamart - should not be the case
A bunch of palette functions would be nice see https://drsimonj.svbtle.com/creating-corporate-colour-palettes-for-ggplot2
options that take the last snapshot only should do group by model ID not assume all snapshots are the same

Obsolete mostly - will file separate issues

repo: pegasystems/cdh-datascientist-tools


text:
Removal of pega7-tomcat-ready from DockerHub

The pega7-tomcat-ready image needs to be removed from DockerHub to avoid confusion and the possibility of users deploying an unsupported version of the Docker image.
Removal is scheduled for Sept 1, 2019.

Closing as duplicate of #25

repo: pegasystems/docker-pega-web-ready


text:
jsDump bug

The following grammar entered into the online version:
start = { return { item: 'abc' }; }

produces output [] for an empty input, instead of correct { item: 'abc' }.
The following grammars don't have this problem:
start = { return { item: 0 }; }

start = { return { index: 'abc' }; }

Debugging points to a bug in the jsDump library. I need to look whether this is fixed in a newer version. If not, I need to report it/fix it.
Originally reported in the Google Group.

According to this post this bug can be fixed by using a jsDump fork.

Hmm, I thought upgrading jsDump solved the problem, but it did that only for item. Dumping still misbehaves in presence of the callee property, as demonstrated by the following grammar:
start = "" { return { callee: 0 }; }

With empty input, it produces [].

I reported the bug at the jsDump fork the website uses and provided a PR with a fix. I’ll apply the fix locally too.

repo: pegjs/website

license: mit

license_source: bigquery


text:
Push with Websocket works?

HI, I was just playing around and at least in my simple example push works with your library with websocket if I add
@WebListener
public class AtmosphereSessionSupport extends SessionSupport {
}

@eiswind Curious to see an actual working sample.
Are you able to provide a fully working class ?
If possible could you provide an basic working sample ?

@GJRTimmer I will publish the source on github as soon as saturday is here. I'll drop you a link as soon as its online.

@GJRTimmer I just opened a pull request with a working example. Feel free to have a look at it :)

I will look at it this weekend.

Fixed the pull request. In Spring Boot, servlet listeners are registered as ordinary Spring beans.

And web socket pull does indeed seem to work. We should try it out with some more advanced samples as well, though.

Works with the EventBus sample as well, which indicates that at least the scopes work properly.

Nice to learn about the ServletListener. I just stumbled into this "by accident".

@eiswind @GJRTimmer  I want to test this with all the scopes and the security features enabled. If it works as expected, we should document this and maybe even enable the SessionSupport listener by default if server push is enabled.

Go ahead;
@peholmst might it be an idea to create a test for this within the spring-vaadin-test package.

@GJRTimmer The more tests we write, the better. We've (or at least I've) been too lazy in that department during this project. I just don't really know how you'd set up a reliable test for this. Any ideas?

authors: GJRTimmer eiswind peholmst


text:
add soulmask

Description
Closes #25
Checklist for all submissions

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you tested and reviewed your changes with confidence that everything works?
[x] Did you branch your changes and PR from that branch and not from your master branch?

If not, why?:

New egg Submissions

[ ] Does your submission pass tests (server is connectable)?
[ ] Does your egg use a custom docker image?

[ ] Have you tried to use a generic image?
[ ] Did you PR the necessary changes to make it work?

[x] Have you added the egg to the main README.md and any other README files in subdirectories of the egg (e.g /game_eggs) according to the alphabetical order?
[x] Have you added a unique README.md for the egg you are adding according to the alphabetical order?
[x] You verify that the start command applied does not use a shell script

[ ] If some script is needed then it is part of a current yolk or a PR to add one

[x] The egg was exported from the panel

Tested and demonstrated working in the Pelican Panel discord.
-Vyrus

Server doesnt show up in the list, Am I doing something wrong, I know the ports are open

repo: pelican-eggs/games-steamcmd

license: MIT


text:
🛑 HOSS-PAGE is down

In 1cc6d64, HOSS-PAGE ($PAGE_HOSS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: HOSS-PAGE is back up in 8c377eb.


text:
Turkish detection takes longer than others

Hi!
we're using your wonderful language detection package :)
We're consuming version 1.0.0
However,  it seems that Turkish is causing a lag:
Took 0.982967443 seconds to detect language of DANISH
Took 0.013375939 seconds to detect language of GERMAN
Took 0.00895221 seconds to detect language of ENGLISH
Took 0.004931715 seconds to detect language of SPANISH
Took 0.007953544 seconds to detect language of FRENCH
Took 0.004886938 seconds to detect language of ITALIAN
Took 0.003902518 seconds to detect language of JAPANESE
Took 0.002207307 seconds to detect language of KOREAN
Took 0.01076291 seconds to detect language of MALAY
Took 0.004513402 seconds to detect language of DUTCH
Took 0.005380963 seconds to detect language of NORWEGIAN
Took 0.009575043 seconds to detect language of POLISH
Took 0.004399465 seconds to detect language of PORTUGUESE
Took 0.00420948 seconds to detect language of SWEDISH
Took 0.001934336 seconds to detect language of THAI
Took 6.708378177 seconds to detect language of TURKISH
Took 8.58397E-4 seconds to detect language of CHINESE_SIMPLIFIED
Took 7.28538E-4 seconds to detect language of CHINESE_TRADITIONAL
any idea what causing this issue?
Thank you!
Elisheva.

Hi Elisheva, thanks for using my library.

any idea what causing this issue?

No. How could I? You haven't shown me a single line of your code, so I'm not able to help you. But if you do, there will be a chance. :)

hi!
we're initializing once the detector:
LanguageDetector detector = LanguageDetectorBuilder.fromAllLanguages().build();
and calling it using:
SortedMap<Language, Double> languageToConfidenceMap = detector.computeLanguageConfidenceValues(text);
and that's it :)
nothing else.
Thanks

Alright, but this is still too little information. Please show me the code of your benchmark, too. And the context of your text files, if possible.

hi
we're running this:
@Test
public void testTurkishStrings()
{

    String[] turkishStrings = {"Bu uzun bir paragraf olacak. Çok uzun değil ama Türkçe çeviriyi Lingua kütüphanesini kullanarak test etmek için yeterince uzun olmalı. Bazı testlerimiz, kitaplığın belirli bir dizenin Türkçe olduğunu algılaması için geçen süre içinde başarısız oluyor. Umarım sorunu çözebiliriz.","Bu yerli bir metin dizesinde bir dil bulmak yeteneği bizim doğrulamak gereken bir testtir. Ben iyi çalışıyor umuyoruz.","Merhaba. Markete gidiyorum. Yarın sahile gideceğim. Biraz havlu almak istiyorum.", "Bu uzun bir paragraf olacak. Çok uzun değil ama Türkçe çeviriyi Lingua kütüphanesini kullanarak test etmek için yeterince uzun olmalı. Bazı testlerimiz, kitaplığın belirli bir dizenin Türkçe olduğunu algılaması için geçen süre içinde başarısız oluyor. Umarım sorunu çözebiliriz."};

    LanguageDetector detector = LanguageDetectorBuilder.fromAllLanguages().build();

    StopWatch stopWatch = new StopWatch();

    for (int i = 0; i < turkishStrings.length; i++)
    {
        stopWatch.start();
        detector.computeLanguageConfidenceValues(turkishStrings[i]);
        stopWatch.stop();
        System.out.println("Took " + ((double)stopWatch.getNanoTime()/1_000_000_000) + " seconds to detect Turkish for String No. " + (i+1));
        stopWatch.reset();
    }
}

Lingua is struggling to detect a particular Turkish string : Bu yerli bir metin dizesinde bir dil bulmak yeteneği bizim doğrulamak gereken bir testtir. Ben iyi çalışıyor umuyoruz.
first time it takes 6-7 seconds. But if you give the same string again, to the same lingua instance, it takes less than a second
other sentences are detected in less than a second.
Thanks!

ok, thanks!
would it make all 75 languages available all the time?
wouldnt it make the package very heavy?

No, the detection won't be slower. If you load all languages models at once, they will just consume more memory. For version 1.2.0, I'm currently working on improving performance and reducing the memory footprint, so this will become even better in the future.

repo: pemistahl/lingua


text:
🛑 Sekretariat Daerah is down

In 99b667b, Sekretariat Daerah (https://setda.bekasikota.go.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sekretariat Daerah is back up in 725a83b.

repo: pemkotbekasi/website-status


text:
263 add optimizations audit recommendations

Some notable mentions:

LIY-04/LIT-05 was already solved since audit.

LIV-01 "Duplicated Helper Function Call" -> I left this unchanged. In my opinion cannot be optimized without modifying (splitting) try_deposit_collateral from pallet vault-registry. Although in deposit_collateral extrinsic it is duplicated the active vault check, this function is used also externally outside the pallet.

IMP-02 "Empty Strings as prefixes" -> I also left this unchanged. I believe this could be useful in the future, since it is already coded and works, for extension purposes.

HOR-01/HOI-01 Unnecessary Variable cloning -> the code seems to have changed since then. Couldn't find that specific reference.

EXC-02/EXU-03 Double filter() calls can be reduced with filter_map() -> Is addressed along with RPC-01, where the use of closures filter and transform the into Request type inside both  get_vault_redeem_requests and get_old_vault_replace_requests.

I looked through the changes and think you did a great job @gianfra-t. I left some nitpicky comments but also one more severe issue related to changes for 'LBS-01 - Duplicated condition check'. At least I think it is, let me know your thoughts.

Regarding LBS-01 (090c314ebae8398223c07dec77a0d2276d8fa476), I understood that get_active_vault_from_id will match if vault if active already, if not return an error (which I mapped to the desired one in the second check). Let me know if I am missing something.

I looked through the changes and think you did a great job @gianfra-t. I left some nitpicky comments but also one more severe issue related to changes for 'LBS-01 - Duplicated condition check'. At least I think it is, let me know your thoughts.

Regarding LBS-01 (090c314), I understood that get_active_vault_from_id will match if vault if active already, if not return an error (which I mapped to the desired one in the second check). Let me know if I am missing something.

Never Mind, it is matching Active(_) not Active(true). Will rollback in that one too.

Never Mind, it is matching Active(_) not Active(true). Will rollback in that one too.

Exactly. A small but important difference. I thought I left a review comment on that specific line but maybe I accidentally discarded it again. At least I can't find it anymore haha.
Anyways, it's actually an oversight of the auditors and not on you since you just did what they asked us to do.

@gianfra-t the CI job threw some warning because clippy failed, can you please add the suggested change and re-run the job?

authors: ebma gianfra-t

repo: pendulum-chain/spacewalk


text:
Item icon bugs

Environment
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36
URL
http://localhost:8083/result/stage/main_3/main_03-02
Steps to reproduce

Sort the stats table by clicking on any header
Item icon will show weird sprite images
Furniture icon wil disappear

What is expected?
N/A
What is actually happening?
N/A

The bug of disappeared furniture icon has not been resolved.


text:
Specifying update type in network_updates (v. 0.3.6)?

I'm probably missing something, but I'd like to be able to specify a network update type in a call to network_updates.  I guessed it would be something like: client.network_updates(:type => 'SHAR')
but that returns all update types in the stream - CONN, PROF, STAT, etc.  Ideally, I'd like to require multiple types such as SHAR and STAT.
Perhaps this is related to Issue #76 since specifying a count parameter doesn't seem to work either?

I'm running into the same thing. Would like to specify an update type.

authors: Rustin cander

repo: pengwynn/linkedin


text:
[BISERVER-14843] - Error in pentaho.log when accessing kettle status page after starting Pentaho 9.x as a Windows Service

@smmribeiro
@bcostahitachivantara
@renato-s

:white_check_mark: Build finished in 24m 44s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3634, Failures: 0, Skipped: 4    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 26m 12s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3634, Failures: 0, Skipped: 4    Test Results

:information_source:  This is an automatic message

:warning: Build finished in 27m 42s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 1 test(s) failed:
org.pentaho.di.trans.TransTest.testPDI12424ParametersFromMetaAreCopiedToTrans (click to expand)

Transformation was unable to open [null]

The transformation path ram:///parameters_4fa79c66-6be9-11ed-9180-f3fdb827d72a.ktr is invalid, and will not run successfully.

Tests run: 3752, Failures: 1, Skipped: 4    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 24m 37s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 2366, Failures: 0, Skipped: 4    Test Results

:information_source:  This is an automatic message

repo: pentaho/pentaho-kettle


text:
Nested Sort Fields

Primary Key Fields in TableSpec
erg...
List Filter at Request Object
Bool Filter
Failing Test
Sometimes... go... really
Fix JSONB Path Builder

Merge too hard, replace with #37

repo: pentops/protostate


text:
Swap alt fee tokens into the native token prior to fee burn

As described in #4320, the initial implementation of multi-asset fee support burns the alt fee tokens. This is incorrect, since the chain should only be minting/burning native assets. The correct behavior is that the fees paid in alt fee tokens should be converted to the native token.  However, since the DEX is batched, we need some plumbing to collect fee amounts, include them in batch swaps, and then handle the resulting fee payments. This overlaps with work we'd thought about (but haven't done, and deferred) as part of #3666 and we should think about them at the same time.

However, since the DEX is batched, we need some plumbing to collect fee amounts, include them in batch swaps, and then handle the resulting fee payments.

Should we add an additional fee multiplier to fees paid in the non-native asset to account for the additional work of swapping?

I don't think so, since that cost isn't really attributable to a psecific transaction.
I'm also not sure it's necessary. In this V0 design, there's no connection between the different prices, all of which are fixed -- so the values of the different fee tokens could float around and cause pricing disparities. To address this, I think that the fixed fees for alternative gas tokens should be significantly higher (10x). This way, users can come into the chain and use it, but they're incentivized to use the native fee token which will protect their privacy.

The issue here is primarily that we don't currently have any plumbing set up to move the values of the fees around and then swap them, and doing that will require some design work. Maybe we don't get to doing this pre-mainnet.

Sounds like we need to discuss & clarify which part of this ticket is in scope for V1 - @hdevalence when you say "maybe we don't get to doing this pre-mainnet", do you mean this ticket generally? Will burning the alt fee tokens cause issues for users?

what does it mean if this ticket is tagged as `v1  and removed from the current sprint, specifically in the context of the upcoming code freeze?

authors: TalDerei aubrika hdevalence zbuc

repo: penumbra-zone/penumbra


text:
Denom refactoring

Follows discussion in #178 and https://github.com/penumbra-zone/penumbra/issues/178#issuecomment-992214707
This PR doesn't make use of the new DisplayDenoms, but just replaces everything with BaseDenom. Adding support for doing unit conversions is not included.
This code has a nice external API but is a bit tricky internally, and it would be good to test it.

After discussion in Discord, merging this optimistically, please open followup issues if you find problems with this

authors: hdevalence redshiftzero


text:
dex: add DexParameters, remove RoutingParams::default()

This commit adds a DexParameters section to the app parameters and removes the previous RoutingParams::default().
The DEX's path search considers two kinds of candidates during routing: dynamically-chosen candidate assets indexed by liquidity, and fixed candidates that provide the "spine" of the liquidity graph.  Previously, these fixed candidates were literally hardcoded into the test code, which wouldn't work on mainnet. Now, they're configurable parameters.

Added consensus-breaking label, for bookkeeping purposes. Please remove if I'm wrong about that.

authors: conorsch hdevalence


text:
Solves the issue for undefined gates (cr2, cr4, cr8, crz)

Hi @perak,
This PR solves the issues mentioned in #21. Please let me know if there are mistakes/other workarounds! :)

Hi @Kaustuvi
Thank you very much for the PR, but problem is that almost entire file is changed and it is hard for review:

Looks like you (or your editor) changed coding style and there is more than 2k changes.
Can you pls change only code where you find bugs and make new PR?

Plus, my latest commit is shown in diff, so looks like something is messed up with git.
I will merge your changes, but please try to make new clean branch and modify code there.
Thanks!

I probably formatted the file and that's why there are so many changes. Also, I merged your latest commit after raising the PR and that probably messed up something! I am sorry for this mistake. :(
Should I make a new PR now?

It is best if you make new one. Thanks!

Okay! I am making a new one! :)

authors: Kaustuvi perak

repo: perak/quantum-circuit


text:
K8SPXC-838: Compute requests are inherited by log containers

Test name
Status

haproxy
passed

recreate
passed

scaling
passed

big-data
passed

upgrade-haproxy
failed

scheduled-backup
passed

storage
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
failed

restore-to-encrypted-cluster
passed

security-context
passed

self-healing-chaos
passed

upgrade-proxysql
failed

limits
passed

demand-backup
passed

self-healing-advanced
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

self-healing-advanced-chaos
passed

smart-update
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

users
passed

operator-self-healing-chaos
passed

demand-backup-encrypted-with-tls
passed

upgrade-consistency
failed

tls-issue-self
passed

tls-issue-cert-manager
failed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1005/commits/1e4101177e732d40ac247e6ee2ee123072c1de90
image: perconalab/percona-xtradb-cluster-operator:PR-1005-1e410117

Test name
Status

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1005/commits/d06bed1c12b2fb0b9a759123a9a6b46524723fae
image: perconalab/percona-xtradb-cluster-operator:PR-1005-d06bed1c

Test name
Status

haproxy
passed

recreate
failed

scaling
failed

big-data
failed

storage
passed

upgrade-haproxy
failed

scheduled-backup
failed

self-healing
passed

self-healing-chaos
failed

scaling-proxysql
passed

init-deploy
failed

security-context
passed

limits
failed

upgrade-proxysql
failed

monitoring-2-0
failed

affinity
passed

one-pod
passed

smart-update
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
failed

tls-issue-self
passed

tls-issue-cert-manager
failed

restore-to-encrypted-cluster
failed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

tls-issue-cert-manager-ref
failed

demand-backup
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

validation-hook
failed

pitr
failed

demand-backup-encrypted-with-tls
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1005/commits/bf8a99c1312c5ac10df3ca8f52e66c910a5f57ba
image: perconalab/percona-xtradb-cluster-operator:PR-1005-bf8a99c1

Test name
Status

storage
passed

recreate
passed

upgrade-haproxy
failed

scheduled-backup
passed

big-data
passed

scaling
passed

haproxy
passed

self-healing
passed

self-healing-chaos
passed

scaling-proxysql
passed

init-deploy
passed

security-context
passed

restore-to-encrypted-cluster
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

limits
failed

upgrade-proxysql
failed

demand-backup
passed

monitoring-2-0
failed

operator-self-healing
passed

operator-self-healing-chaos
passed

affinity
passed

one-pod
passed

smart-update
passed

pitr
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

upgrade-consistency
failed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1005/commits/1cfd8ea9fff4816f875c5e7e0ef63a2f0b8670a2
image: perconalab/percona-xtradb-cluster-operator:PR-1005-1cfd8ea9

Test name
Status

scaling
passed

scaling-proxysql
passed

security-context
passed

haproxy
passed

scheduled-backup
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

storage
passed

self-healing
passed

upgrade-haproxy
failed

self-healing-chaos
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

big-data
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

pitr
passed

demand-backup-encrypted-with-tls
passed

upgrade-proxysql
failed

smart-update
passed

upgrade-consistency
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1005/commits/24936e1cf45c147f1c34d5341285ec572fb8ff42
image: perconalab/percona-xtradb-cluster-operator:PR-1005-24936e1c

Test name
Status

scheduled-backup
passed

storage
passed

self-healing
passed

self-healing-chaos
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

haproxy
passed

operator-self-healing
passed

init-deploy
passed

operator-self-healing-chaos
passed

big-data
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

scaling
passed

upgrade-haproxy
passed

recreate
passed

auto-tuning
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

proxysql-sidecar-res-limits
passed

security-context
passed

demand-backup
passed

users
passed

pitr
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1005/commits/3b8a23dca0b432668452c8ec9702d25a3036175b
image: perconalab/percona-xtradb-cluster-operator:PR-1005-3b8a23dc

authors: JNKPercona defbin

repo: percona/percona-xtradb-cluster-operator


text:
🛑 Libreddit is down

In 02bccbc, Libreddit (https://libreddit.perennialte.ch) was down:

HTTP code: 404
Response time: 874 ms

Resolved: Libreddit is back up in 2202303 after 8 minutes.

repo: perennialtech/upptime


text:
Icon not showing up

The icon in the url bar stopped showing up recently. I de/reactiviated the extension and cleared my chromium settings. Neither worked.

Can you provide more details?  Chromium version, example website where it does not appear?

Sorry to piggyback on thread, but I have same problem.
Works 1st time when extension installed.  Icon does not show up after restart of computer.
Detail:  45.0.2422.6 (Developer Build 4bbc55206b39e2dbecefed256d99f1fd16a22b36 Chromium OS)

When you look in chrome extensions, is the extension still installed and not disabled?

Extension is enabled.
Tried a windows 7 machine with Chrome browser.  The extension CKP works correctly on windows.
Still no icon on machine with Chromium OS.

I was not able to reproduce the problem in Chromium 45.0.2454.101

I am having the same issue with the icon not showing up.  I'm using Chrome Version 47.0.2526.80 m on Windows 7 Professional.  I don't think I have Chromium installed - is that needed?

For me CKP is working on a macbook and windows 7 computers.  No luck on Chromium.
Chromium is the same OS that is used on Chrome books, but is the free version.  I re-purposed an old windows computer by deleting the windows OS and installed Chromium.
in your chrome's address bar put:  chrome://extensions/
check that all options are set correctly.

authors: DukeyToo fracturing noflag poppy-seed

repo: perfectapi/CKP


text:
Seafile support

Based on issue #68 my understanding is that a HTTP API for accessing metadata + file contents is required for new store implementations. I did a quick check and it looks like this is indeed possible using Seafile (file API), hence this issue to support Seafile as a file cloud service.

I would love that too. It would allow to store data on our own private cloud space, on our own server.

authors: tiramiseb xintron


text:
proto methods in signatures

Do we really need them? I mean cases like that:
    proto method from-loop(|)  Seq:D
    multi method from-loop(&body)
    multi method from-loop(&body, &cond, :$repeat)
    multi method from-loop(&body, &cond, &afterward)

The first signature just shows internal implementation detail, not a usage interface(if I'm correct). Isn't it would be better to remove it and add --> Seq:D to the other three signatures?
➜  doc git:(consistent-return-types) ✗ grep -I -r 'proto method' doc/Type/ | wc -l
7

And it doesn't seems to be popular in the docs. Should be removed?

The only thing that the proto brings to the party is the return value.  This could be copied to the other signatures.

I am not sure about this. Look:
multi method from-loop(&body --> Seq:D)
multi method from-loop(&body, &cond, :$repeat --> Seq:D)
multi method from-loop(&body, &cond, &afterward --> Seq:D)

Somehow I don't think it looks better.
Maybe this?
multi method from-loop(&body                    --> Seq:D)
multi method from-loop(&body, &cond, :$repeat   --> Seq:D)
multi method from-loop(&body, &cond, &afterward --> Seq:D)

The question about indentation here is not so important, the main question is proto presence, imho.
About the return type... While I worked with our signatures, I find out a terrifying thing that our return type notion is totally random. I mean, some methods have it, some methods not without any system. So maybe it's a question for a next big(I mean, really big) issue. But this proto thing just looks like it was copied from the rakudo code in some places.

If there are only 7 instances, just remove it.

I think in a lot of cases they have been copied from the source yes,

authors: AlexDaniel Altai-man jonathanstowe


text:
sample output typo in Language/functions.pod

Defining Operators > Precedence
https://doc.perl6.org/language/functions#Precedence
Sample output:
say 1 + 2 * 3 !! 4;     # 29
Correct output is 1 + ((2 * 3) !! 4)
= 1 + (6 !! 4)
= 1 + (2 * (6 + 4))
= 1 + (2 * 10)
= 21

It looks like it was meant to be is tighter(&infix:<*>)

Changed the result to 21. Now the text and result shown match.
https://github.com/perl6/doc/commit/ab41b988af

Oh, now I've noticed that it mentions is tighter(&infix:<*>) too, so indeed, it looks like the comment was wrong.
@dogbert17 Good, but now there's a problem with this phrase:

The same effect could have been achieved with

What does it mean now? What kind of “same effect”?

Can we close this?


text:
method rand() (Range) is not documented

method rand() (Range) is tested here
https://github.com/perl6/roast/blob/master/S02-types/range.t#L347-L352

https://docs.perl6.org/type/Range#(Cool)_method_rand - isn't it documented here? We shouldn't duplicate inherited method descriptions.

@Altai-man
See Rakudo
Range overrides rand method
https://github.com/rakudo/rakudo/blob/nom/src/core/Range.pm#L613-L645

It is, but does the semantic changes?
> '3'.rand;
0.896857413511574
> 3.rand;
1.78286226375614
> (0..3).rand;
0.0179161736188595
>

In all this cases value was coerced to Num type and rand was called.

@Altai-man
It has at least two different points compared to rand (Cool).
offset

rand (Range) could handle offset

$ perl6 -e '(10..15).rand.say'
10.1978593725124 # it computes (15 - 10).rand + 10

Str

rand (Range) couldn't handle Str

$ perl6 -e '("10"..15).min.WHAT.say'
(Str)
$ perl6 -e '("10"..15).rand.say'
Can only get a random value on Real values, did you mean .pick?
  in block <unit> at -e line 1

Actually thrown at:
  in block <unit> at -e line 1

rand (Cool) could handle Str

$ perl6 -e '"10".rand.say'

@titsuki
This both cases are arguable, so I still think that we'd better to extend our documentation of Cool type method. Since many types are inherited from it, it will be good to document many cases with examples in the basic function definition.
Maybe someone else has different opinion, but as for me, bugfix should be send to Cool.pod6 file, not Range.pod6.

@Altai-man
I think that it shouldn't be documented in Cool.pod, because more widely used methods such as elems, new, ACCEPTS and so on, are documented in the class that overrides them.

For example, both Map and List override Any.elem method.

https://docs.perl6.org/type/Any#method_elems
https://docs.perl6.org/type/Map#method_elems
https://docs.perl6.org/type/List#routine_elems

However, if almost all users can expect what Range.rand returns as similar to Range.perl, the priority of documenting Range.rand is low IMHO.

Range overrides Mu.perl

$ perl6 util/missing-methods.p6 --type-name=Range
Range.is-lazy
Range.iterator
Range.reverse
Range.first
Range.fmt
Range.clone-with-op
Range.push
Range.append
Range.unshift
Range.prepend
Range.shift
Range.pop
Range.sum
Range.rand
Range.in-range
Range.item
Range.of
Range.race
Range.lazy
Range.hyper
Range.lazy-if
Range.new
Range.WHICH
Range.EXISTS-POS
Range.Str
Range.ACCEPTS
Range.AT-POS
Range.perl # Here
Range.Numeric

This cases seem redundant for me too. In all three descriptions it says only "You will get the number of elements". The fact that in the case of Map it will return a key-value is the part of Map semantic.
Perhaps, I'm sticking too much to this opinion, though, so I'll shut up until some exploration of this question come.

@Altai-man
It is not a completely predictable behavior that Map returns the number of the key-value pairs.
Firstly, Map overrides Any.elems, so insisting "Map calls Any.elems" is the not good thing to do.
Secondly, Map overrides Any.elems, so there is no restrictions of what Map returns.
For example, overrided elems method can return a List instance instead of an Int instance.
$ perl6 -e 'class A { method elems(::?CLASS:D:){ (1,2,3)} }; say A ~~ Any;' # A is Any
True
$ perl6 -e 'class A { method elems(::?CLASS:D:){ (1,2,3)} }; A.new.elems.say;' # A overrides Any.elems
(1 2 3)

Therefore, we should explicitly state what Map.elems returns, when Map override Any.elems.

Do we have a decision on this? Should we try and document it?

authors: Altai-man JJ titsuki


text:
Update testcontainers-scala-scalatest to 0.39.8

Updates com.dimafeng:testcontainers-scala-scalatest from 0.39.7 to 0.39.8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.dimafeng", artifactId = "testcontainers-scala-scalatest" } ]

labels: test-library-update, semver-patch

Codecov Report

Merging #307 (3e35d87) into master (c3afb67) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #307   +/-   ##
=======================================
  Coverage   34.89%   34.89%
=======================================
  Files          29       29
  Lines         298      298
  Branches        8        6    -2
=======================================
  Hits          104      104
  Misses        194      194

Continue to review full report at Codecov.

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

authors: codecov-commenter scala-steward


text:
Can not play a rtsp URL on Android

Please give me some advices for the bug when running rtsp url on Android
"error": "com.google.android.exoplayer2.ExoPlaybackException: net.butterflytv.rtmp_client.RtmpClient$RtmpIOException: RTMP error: -12"

react-native: 0.61
ext {
        buildToolsVersion = "28.0.3"
        minSdkVersion = 17
        compileSdkVersion = 28
        targetSdkVersion = 28
        exoPlayerVersion = "2.10.5"
    }

This looks like an exoplayer issue --
https://github.com/ant-media/LibRtmp-Client-for-Android/issues/65
You could try using a new or different version of ExoPlayer with this library.

@esilverberg Thanks for your answer. I've tried latest version of ExoPlayer which is 2.10.5, but it seem doesn't work.

What about an older version of ExoPlayer?

@esilverberg I've tried several versions from 2.9.6 to 2.10.5, but it seems doesn't work

@esilverberg I found that it works for normal RTSP link like rtmp://fms.105.net/live/rmc1. But it is not works with url like rtsp://admin:admin@xxx.xxx.

https://github.com/google/ExoPlayer/issues/55

authors: esilverberg nhiicts


text:
Improve the CUE-originated errors returned to the frontend

Proposal
Context: we had an issue of misalignment between FE & BE datamodel, but I believe this problem can occur in other, more legit situations (i.e user input error).
On frontend side was displayed this not-very-intelligible message:
bad request: invalid panel 1_3: spec.thresholds.mode: 2 errors in empty disjunction: (and 2 more errors)
..while on backend side we had a more accurate error (that in the end led us to the root cause):
spec.thresholds.mode: conflicting values \"percent\" and \"Percent\"
The goal would be to find a solution to have the latter being returned to the frontend instead of the current, more (too) high-level error.

This was fixed by https://github.com/perses/perses/pull/1470

This was fixed by https://github.com/perses/perses/pull/1470.

repo: perses/perses


text:
Add metadata provider

Adds definitions for the NFTMetadataProvider.
Currently blocked.

Two mentionable points:

I think it would be nice to create a solidity contract defining an "umbrella" interface for metadata stuff. We are currently abusing the fact, that the metadata of all contracts for which metadata is requested, implements the ERC721IMetadata interface. Any opinions?

I fixed a typo in our naming and I am certain it will break stuff in other repositories.

repo: perun-network/erdstall-ts-sdk


text:
Test case finding does not work when using __DIR__

When using __DIR__ syntax for in parameter in the pest.php file, it does not know how to resolve it.

An eap is ready for this.
PEST PHP-1.2.2-EAP.1.zip
Install it manually using
Preferences > Plugins > ⚙ > Install plugin from disk...

repo: pestphp/pest-intellij


text:
esm包中中发现require引入

目前集成过程中，发现引用报错。esm的包里也包含了require引入

感谢回复，新版本确实可以，目前使用vite-plugin-commonjs插件，配合过滤也能构建成功了

repo: petercat-ai/petercat


text:
Causes regen of other packages using build_runner

Returning to an older project, and running
flutter pub run build_runner build
And running into an issue with other files that get regenerated by this command too. I was wondering if this package could be specifically passed as argument so that it only this package was rebuilt with build_runner?
eg
flutter pub run build_runner build envied
Or similar?
Apologies if that's not feasible or how build_runner should be used, but I hope you see the issue - it would be ideal to be able to specifically regenerate the env, and not affect anything else.

I think you can use filtering to achieve what you want as explained here https://github.com/dart-lang/build/issues/2815

authors: mobikats techouse

repo: petercinibulk/envied


text:
I am getting an error ie Unexpected exception in Dalli: ArgumentError: dump format error for symbol(0x46)

I am getting this error. Any suggestions:
	Unexpected exception in Dalli: ArgumentError: dump format error for symbol(0x46)
This is a bug in Dalli, please enter an issue in Github if it does not already exist.
/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/dalli/server.rb:423:in `load'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/dalli/server.rb:423:in `deserialize'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/dalli/server.rb:479:in `generic_response'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/dalli/server.rb:256:in `get'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/dalli/server.rb:60:in `request'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/dalli/options.rb:18:in `block in request'
	/Users/me/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/dalli/options.rb:17:in `request'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/dalli/client.rb:348:in `perform'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/dalli/client.rb:62:in `get'
	(eval):7:in `block in get_with_newrelic_trace'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/method_tracer.rb:235:in `trace_execution_scoped'
	(eval):4:in `get_with_newrelic_trace'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/active_support/cache/dalli_store.rb:229:in `read_entry'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/cache/strategy/local_cache.rb:129:in `read_entry'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/active_support/cache/dalli_store.rb:66:in `block in fetch'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/active_support/cache/dalli_store.rb:291:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/active_support/cache/dalli_store.rb:291:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/dalli-2.6.4/lib/active_support/cache/dalli_store.rb:65:in `fetch'
	/Users/me/projects/=myapplication/app/models/submission.rb:77:in `cached_questions'
	/Users/me/projects/=myapplication/app/views/reports/_submission.html.erb:30:in `_app_views_reports__submission_html_erb__1296693083777323766_70359193223000'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:145:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:143:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-mini-profiler-0.1.26/Ruby/lib/mini_profiler/profiling_methods.rb:90:in `block in profile_method'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/xray-rails-0.1.5/lib/xray/engine.rb:29:in `render_with_xray'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:265:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:238:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:237:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:176:in `block in render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/method_tracer.rb:235:in `trace_execution_scoped'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:175:in `render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/renderer.rb:41:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/helpers/rendering_helper.rb:27:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/haml-3.1.8/lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml'
	/Users/me/projects/=myapplication/app/views/reports/_submissions.html.erb:6:in `block in _app_views_reports__submissions_html_erb___2876368633201457327_70359176046540'
	/Users/me/projects/=myapplication/app/views/reports/_submissions.html.erb:5:in `each'
	/Users/me/projects/=myapplication/app/views/reports/_submissions.html.erb:5:in `_app_views_reports__submissions_html_erb___2876368633201457327_70359176046540'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:145:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:143:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-mini-profiler-0.1.26/Ruby/lib/mini_profiler/profiling_methods.rb:90:in `block in profile_method'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/xray-rails-0.1.5/lib/xray/engine.rb:29:in `render_with_xray'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:265:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:238:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:237:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:176:in `block in render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/method_tracer.rb:235:in `trace_execution_scoped'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:175:in `render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/renderer.rb:41:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/helpers/rendering_helper.rb:27:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/haml-3.1.8/lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml'
	/Users/me/projects/=myapplication/app/views/reports/_report.html.erb:5:in `_app_views_reports__report_html_erb__1624076841980906978_70359175219340'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:145:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:143:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-mini-profiler-0.1.26/Ruby/lib/mini_profiler/profiling_methods.rb:90:in `block in profile_method'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/xray-rails-0.1.5/lib/xray/engine.rb:29:in `render_with_xray'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:265:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:238:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:237:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:176:in `block in render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/method_tracer.rb:235:in `trace_execution_scoped'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:175:in `render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/renderer.rb:41:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/helpers/rendering_helper.rb:27:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/haml-3.1.8/lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml'
	/Users/me/projects/=myapplication/app/views/reports/_reports.html.erb:4:in `block in _app_views_reports__reports_html_erb___48310801989303024_70359175197400'
	/Users/me/projects/=myapplication/app/views/reports/_reports.html.erb:3:in `each'
	/Users/me/projects/=myapplication/app/views/reports/_reports.html.erb:3:in `_app_views_reports__reports_html_erb___48310801989303024_70359175197400'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:145:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:143:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-mini-profiler-0.1.26/Ruby/lib/mini_profiler/profiling_methods.rb:90:in `block in profile_method'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/xray-rails-0.1.5/lib/xray/engine.rb:29:in `render_with_xray'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:265:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:238:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:237:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:176:in `block in render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/method_tracer.rb:235:in `trace_execution_scoped'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:175:in `render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/renderer.rb:41:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/helpers/rendering_helper.rb:27:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/haml-3.1.8/lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml'
	/Users/me/projects/=myapplication/app/views/reports/_reports_view.html.erb:10:in `_app_views_reports__reports_view_html_erb__4504399296607044907_70359175105400'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:145:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:143:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-mini-profiler-0.1.26/Ruby/lib/mini_profiler/profiling_methods.rb:90:in `block in profile_method'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/xray-rails-0.1.5/lib/xray/engine.rb:29:in `render_with_xray'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:265:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:238:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/partial_renderer.rb:237:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:176:in `block in render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/method_tracer.rb:235:in `trace_execution_scoped'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:175:in `render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/renderer.rb:41:in `render_partial'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/helpers/rendering_helper.rb:27:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/haml-3.1.8/lib/haml/helpers/action_view_mods.rb:13:in `render_with_haml'
	/Users/me/projects/=myapplication/app/views/reports/index.html.erb:12:in `_app_views_reports_index_html_erb__1386373112483753566_70359156266820'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:145:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/template.rb:143:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-mini-profiler-0.1.26/Ruby/lib/mini_profiler/profiling_methods.rb:90:in `block in profile_method'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/xray-rails-0.1.5/lib/xray/engine.rb:29:in `render_with_xray'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/template_renderer.rb:47:in `block (2 levels) in render_template'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/abstract_renderer.rb:38:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/template_renderer.rb:46:in `block in render_template'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/template_renderer.rb:54:in `render_with_layout'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/template_renderer.rb:45:in `render_template'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/template_renderer.rb:18:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:160:in `block in render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/method_tracer.rb:235:in `trace_execution_scoped'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:159:in `render_with_newrelic'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/renderer.rb:36:in `render_template'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_view/renderer/renderer.rb:17:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/abstract_controller/rendering.rb:110:in `_render_template'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/streaming.rb:225:in `_render_template'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/abstract_controller/rendering.rb:103:in `render_to_body'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/renderers.rb:28:in `render_to_body'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/compatibility.rb:50:in `render_to_body'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/abstract_controller/rendering.rb:88:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/rendering.rb:16:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/instrumentation.rb:40:in `block (2 levels) in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/core_ext/benchmark.rb:5:in `block in ms'
	/Users/me/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/core_ext/benchmark.rb:5:in `ms'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/instrumentation.rb:40:in `block in render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/instrumentation.rb:83:in `cleanup_view_runtime'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activerecord-3.2.13/lib/active_record/railties/controller_runtime.rb:24:in `cleanup_view_runtime'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/thinking-sphinx-2.0.11/lib/thinking_sphinx/action_controller.rb:12:in `cleanup_view_runtime'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/instrumentation.rb:39:in `render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/remotipart-1.0.5/lib/remotipart/render_overrides.rb:14:in `render_with_remotipart'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/implicit_render.rb:10:in `default_render'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/implicit_render.rb:5:in `send_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/abstract_controller/base.rb:167:in `process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/rendering.rb:10:in `process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/abstract_controller/callbacks.rb:18:in `block in process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:459:in `block in _run__3645815306200921146__process_action__3044817955259643074__callbacks'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:215:in `block in _conditional_callback_around_4422'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/core_ext/time/zones.rb:45:in `use_zone'
	/Users/me/projects/=myapplication/app/controllers/application_controller.rb:26:in `set_time_zone'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:214:in `_conditional_callback_around_4422'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:436:in `_run__3645815306200921146__process_action__3044817955259643074__callbacks'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:405:in `__run_callback'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:385:in `_run_process_action_callbacks'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:81:in `run_callbacks'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/abstract_controller/callbacks.rb:17:in `process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/rescue.rb:29:in `process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/instrumentation.rb:30:in `block in process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `block in instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/notifications.rb:123:in `instrument'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/instrumentation.rb:29:in `process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/params_wrapper.rb:207:in `process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activerecord-3.2.13/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:38:in `block in process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/controller_instrumentation.rb:272:in `block in perform_action_with_newrelic_trace'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/method_tracer.rb:235:in `trace_execution_scoped'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/controller_instrumentation.rb:267:in `perform_action_with_newrelic_trace'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/rails3/action_controller.rb:37:in `process_action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/abstract_controller/base.rb:121:in `process'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/abstract_controller/rendering.rb:45:in `process'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-mini-profiler-0.1.26/Ruby/lib/mini_profiler/profiling_methods.rb:90:in `block in profile_method'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal.rb:203:in `dispatch'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_controller/metal.rb:246:in `block in action'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/routing/route_set.rb:73:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/routing/route_set.rb:73:in `dispatch'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/routing/route_set.rb:36:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/journey-1.0.4/lib/journey/router.rb:68:in `block in call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/journey-1.0.4/lib/journey/router.rb:56:in `each'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/journey-1.0.4/lib/journey/router.rb:56:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/routing/route_set.rb:612:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/xray-rails-0.1.5/lib/xray/middleware.rb:37:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/omniauth-1.1.4/lib/omniauth/strategy.rb:184:in `call!'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/omniauth-1.1.4/lib/omniauth/strategy.rb:164:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-webconsole-0.1.2/lib/rack/webconsole/assets.rb:26:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-webconsole-0.1.2/lib/rack/webconsole.rb:63:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/meta_request-0.2.1/lib/meta_request/middlewares/app_request_handler.rb:11:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-contrib-1.1.0/lib/rack/contrib/response_headers.rb:17:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/meta_request-0.2.1/lib/meta_request/middlewares/headers.rb:16:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/meta_request-0.2.1/lib/meta_request/middlewares/meta_request_handler.rb:13:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/bullet-4.5.0/lib/bullet/rack.rb:8:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/rack/error_collector.rb:12:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/rack/agent_hooks.rb:18:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/rack/browser_monitoring.rb:16:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/newrelic_rpm-3.6.0.83/lib/new_relic/rack/developer_mode.rb:28:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/client_side_validations-3.2.5/lib/client_side_validations/middleware.rb:21:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/warden-1.2.1/lib/warden/manager.rb:35:in `block in call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/warden-1.2.1/lib/warden/manager.rb:34:in `catch'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/warden-1.2.1/lib/warden/manager.rb:34:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/etag.rb:23:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/conditionalget.rb:25:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/head.rb:14:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/remotipart-1.0.5/lib/remotipart/middleware.rb:30:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/params_parser.rb:21:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/flash.rb:242:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/session/abstract/id.rb:210:in `context'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/session/abstract/id.rb:205:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/cookies.rb:341:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activerecord-3.2.13/lib/active_record/query_cache.rb:64:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:479:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/callbacks.rb:28:in `block in call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:405:in `_run__2072116922479195046__call__1450984874222397856__callbacks'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:405:in `__run_callback'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:385:in `_run_call_callbacks'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:81:in `run_callbacks'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/reloader.rb:65:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/remote_ip.rb:31:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/airbrake-3.1.11/lib/airbrake/rails/middleware.rb:13:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/better_errors-0.8.0/lib/better_errors/middleware.rb:84:in `protected_app_call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/better_errors-0.8.0/lib/better_errors/middleware.rb:79:in `better_errors_call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/better_errors-0.8.0/lib/better_errors/middleware.rb:56:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/rack/logger.rb:32:in `call_app'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/rack/logger.rb:16:in `block in call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/tagged_logging.rb:22:in `tagged'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/rack/logger.rb:16:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/quiet_assets-1.0.2/lib/quiet_assets.rb:18:in `call_with_quiet_assets'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/request_id.rb:22:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/methodoverride.rb:21:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/runtime.rb:17:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/activesupport-3.2.13/lib/active_support/cache/strategy/local_cache.rb:72:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/lock.rb:15:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/actionpack-3.2.13/lib/action_dispatch/middleware/static.rb:63:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-cache-1.2/lib/rack/cache/context.rb:136:in `forward'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-cache-1.2/lib/rack/cache/context.rb:245:in `fetch'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-cache-1.2/lib/rack/cache/context.rb:185:in `lookup'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-cache-1.2/lib/rack/cache/context.rb:66:in `call!'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-cache-1.2/lib/rack/cache/context.rb:51:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/airbrake-3.1.11/lib/airbrake/user_informer.rb:16:in `_call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/airbrake-3.1.11/lib/airbrake/user_informer.rb:12:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-mini-profiler-0.1.26/Ruby/lib/mini_profiler/profiler.rb:278:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/engine.rb:479:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/application.rb:223:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/content_length.rb:14:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/rack/log_tailer.rb:17:in `call'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/thin-1.5.1/lib/thin/connection.rb:81:in `block in pre_process'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/thin-1.5.1/lib/thin/connection.rb:79:in `catch'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/thin-1.5.1/lib/thin/connection.rb:79:in `pre_process'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/thin-1.5.1/lib/thin/connection.rb:54:in `process'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/thin-1.5.1/lib/thin/connection.rb:39:in `receive_data'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run_machine'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/thin-1.5.1/lib/thin/backends/base.rb:63:in `start'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/thin-1.5.1/lib/thin/server.rb:159:in `start'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/handler/thin.rb:13:in `run'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/rack-1.4.5/lib/rack/server.rb:268:in `start'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/commands/server.rb:70:in `start'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/commands.rb:55:in `block in <top (required)>'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/commands.rb:50:in `tap'
	/Users/me/.rvm/gems/ruby-1.9.3-p392@=myapplication.com/gems/railties-3.2.13/lib/rails/commands.rb:50:in `<top (required)>'
	script/rails:6:in `require'
	script/rails:6:in `<main>'
127.0.0.1:11211 is down
#<Dalli::NetworkError: 127.0.0.1:11211 is down: ArgumentError dump format error for symbol(0x46)>
retrying request with new server
down_retry_delay not reached for 127.0.0.1:11211 (0.996 seconds left)
DalliError: No server available

Closing this as an old issue.  If you run into a similar Unmarshal problem, please open with a new issue.

authors: mohitjain petergoldstein

repo: petergoldstein/dalli


text:
Does not work with TypeScript

I think forbidExtraProps is interfering with TypeScript
Type checking in progress...
/Users/fang/choice-kittens/node_modules/airbnb-prop-types/src/forbidExtraProps.js:1
(function (exports, require, module, __filename, __dirname) { import forbidExtraProps from 'prop-types-exact';
                                                                     ^^^^^^^^^^^^^^^^

SyntaxError: Unexpected identifier
    at new Script (vm.js:84:7)
    at createScript (vm.js:264:10)
    at Object.runInThisContext (vm.js:312:10)
    at Module._compile (internal/modules/cjs/loader.js:684:28)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:732:10)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
    at Function.Module._load (internal/modules/cjs/loader.js:552:3)
    at Module.require (internal/modules/cjs/loader.js:657:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/Users/fang/choice-kittens/node_modules/react-bnb-gallery/dist/react-bnb-gallery.js:5:40)
    at Module._compile (internal/modules/cjs/loader.js:721:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:732:10)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
    at Function.Module._load (internal/modules/cjs/loader.js:552:3)
/Users/fang/choice-kittens/node_modules/airbnb-prop-types/src/forbidExtraProps.js:1
(function (exports, require, module, __filename, __dirname) { import forbidExtraProps from 'prop-types-exact';

@fandy This is why my tests are not working right now, I don't know if I missing some configuration for Babel 7, but when I run the tests, Jest give me the same error.

@peterpalau Hope you find a fix soon. I haven't had any luck fixing it so I'm just converting everything to TS manually on my app. Cool repo! :)

@fandy I think I was able to fix this error in the last update, reviewing all the configuration of babel, jest, babel-jest and rollup packages.
I will keep the issue open in case it happens again in another environment.

authors: fandy peterpalau

repo: peterpalau/react-bnb-gallery


text:
Only 10 Devices from Hub working simultaneously

After the integration of S210 Switches I noticed that only 10 devices work at a time. I digged a bit around and I think the issue is that hub.get_children() only returns the first 10 jsons responses despide giving the correct total of devices.
Could you please have a look at this?

Bug confirmed, I'm working on a fix

I think it was working fine before the update in the Tapo app but I am not sure. I suspect some sort of pagination in the request since having exactly 10 is somewhat suspicious.
I hope this helps.

I tested it just now. It works better but still not perfect. Now all but one devices are listed.

Unfortunately, I am also now coming across this issue.  I thought it was something I was doing wrong

authors: DimiTerz Saftlad petretiandrea


text:
Is it just me, off by 1 stop?

Thanks so much for making this plugin. It's amazing more designers don't understand/have tools to use the LaB space. So much manual tuning!
Small thing here, perhaps just perception, but fading between a red and a blue, it feels like the stops are weighted a little heavy to the red side. However, if I move over the stops as though there was another stop to be inserted on the blue (left) side, it seems more balanced to my eye.
Any chance an off-by-1 error slipped in, resulting in slightly skewed gradient stops?
Hopefully attached image can make the perceived balance issue clear.

@songcarver Thanks for the kind words!
I've also noticed the gradients being weighted towards red. However, I'm not sure it's a bug. When I switch to use RGB for the interpolation, the gradient gets perfectly weighted. That should indicate that it's not an error in the color stop calculation.
My current belief is that this is a drawback of the Lab model, and how it treats certain colors. Gradients with red seems to be affected the most, while other color combinations seems to create more equally weighted gradients.
I'll look into this a bit more though, maybe something clever can be done to improve it. Thanks for creating the issue!

authors: petterheterjag songcarver

repo: petterheterjag/chromatic-sketch

license: ISC


text:
Part of answers are out of reach for some questions

I was curious to try this quite interesting game.
By the way, I was trapped in a case where part of the answers was not visible since were below the bottom point of the screen and I wasn't able to scroll to it.

I am opening this issue to help enhance this game and give more fun to players. Looking forward to more questions.
P.S. Also looking forward for the final prize screen)

Hey, thanks for your interest in this.
I'm aware of this problem and planned to fix it shortly. Actually, it's not finished yet. The only reason that it's public coz I wanted to try to publish it with gh-pages and check in-live.

Answers visibility fixed, added sounds for more involvement to the game.
PS. I'd appreciate new comments or issues if you'd have one.

authors: WorldThirteen petulant-annie

repo: petulant-annie/millionaire-game


text:
"Cândești", "Călinești", "Talpa" and "Vițcani" are listed in the drop-down menu

Description:
"Cândești", "Călinești", "Talpa" and "Vițcani" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Cândești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Cândești, Botoșani (Cândești)".

Step 3
Type "Călinești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Călinești, Botoșani (Cândești)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Type "Vițcani" in the search bar.

Expected results
The location is listed in the drop-down menu as "Vițcani, Botoșani (Cândești)".

ATTENTION:
STEP1:
Request - "Cândești, Botoșani (Cândești)"
In dropbox, the request is displayed correctly. - "Cândești, Botoșani (Cândești)"
After you click on the text, what is displayed in the window this is different - "Cândești, BOTOȘANI (Cândești)"
STEP3:
Request - "Călinești, Botoșani (Cândești)"
In dropbox, the request is displayed correctly. - "Călinești, Botoșani (Cândești)"
After you click on the text, what is displayed in the window this is different - "Călinești, BOTOȘANI (Cândești)"
STEP5:
Request - "Talpa, Botoșani (Cândești)"
In dropbox, the request is displayed correctly. - "Talpa, Botoșani (Cândești)"
After you click on the text, what is displayed in the window this is different - "Talpa, BOTOȘANI (Cândești)"
STEP7:
Request - "Vițcani, Botoșani (Cândești)"
In dropbox, the request is displayed correctly. - "Vițcani, Botoșani (Cândești)"
After you click on the text, what is displayed in the window this is different - "Vițcani, BOTOȘANI (Cândești)"


text:
"Fișer" is listed in the drop-down menu

Description:
"Fișer" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Fișer" in the search bar.
Expected results
The location is listed in the drop-down menu as "Oraș Fișer, BRAȘOV (RUPEA)".


text:
"Drăgănești" and "Malu Alb" are listed in the drop-down menu

Description:
"Drăgănești" and "Malu Alb" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Drăgănești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Drăgănești, GALAȚI".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type again "Drăgănești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Drăgănești, GALAȚI (Drăgănești)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Malu Alb" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Malu Alb, GALAȚI (Drăgănești)".


text:
"Dobrețu", "Curtișoara", "Horezu" are listed in the drop-down menu

Description:
When user writes "Dobrețu", "Curtișoara" and "Horezu" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Dobrețu"
Expected results
The location appears in the drop-down menu as "Sat Dobrețu, OLT (Dobrețu)"

Step 2
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Curtișoara"
Expected results
The location appears in the drop-down menu as "Sat Curtișoara, OLT (Dobrețu)"

Step 4
Press "x" button.
Expected results
The location was deleted from the search bar.


text:
Add TransformDataset

This PR adds a general dataset class called TransformDataset.
This class lets users to apply a function to a indexed data.
It becomes handy in the case when a user wants to write a custom data augmentation code on top of the prepared dataset class.
This class decouples implementation of data augmentation code and a code to retrieve data from filesystem or from web, making it a lot easier to reuse datasets across different tasks.
The class is already used in ChainerCV, an extension library to Chainer.

Thanks for reviewing!
I fixed points you pointed out.

LGTM

repo: pfnet/chainer


text:
Order DNS provider instructions alphabetically

Hi! I stumbled upon the weird order of these instructions a couple of times meanwhile, I think it makes sense to order them alphabetically.

[x] Redmine Issue: minor textual change, so none
[x] Ready for review

You are right, no idea how these slipped into the initial commit. Fixed by last commit!

You are right, no idea how these slipped into the initial commit. Fixed by last commit!

Good find, no idea how these slipped into the commit.. Fixed!

Good find, no idea how these slipped into the commit.. Fixed!

@jim-p can you check this PR? Thanks.

repo: pfsense/pfsense


text:
List related projects

e.g. https://github.com/Calpano/graphinout for converting between graph formats.

https://python.igraph.org/

repo: pg-format/pgraphs


text:
Left alignment on dynamic content

The title and the body text in the dynamic content card is misaligned, and should be realigned so the left sides match up.

Acceptance Criteria

[ ]  The title and body text on the dynamic content card are aligned on all devices

Steps for QA:

@ian-lin-PG taking this issue from you

Pass with release 1.56.1

Pass with release 1.56.1

authors: cherrielam ian-lin-PG tomy-pg

repo: pg-irc/pathways-frontend


text:
Mark some articles and tasks as recommended to all

ACs: Some articles and tasks are recommended to all users, using the taxonomy term recommendation:recommendToAll

Three PRs related to this story, but they're all trivial: https://github.com/pg-irc/pathways-backend/pull/236, https://github.com/pg-irc/pathways-frontend/pull/221, https://github.com/PeaceGeeksSociety/content/pull/109/files

@bensinjin please have a look