text:
🛑 Ada-Net.cz is down

In ef0e0de, Ada-Net.cz (https://www.ada-net.cz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ada-Net.cz is back up in 20e53e4 after 49 minutes.


text:
🛑 tanecni-divadlo.cz is down

In 6572ac2, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in edd0a65.

source: gharchive/issue

repo: cebreus/upptime

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 tanecni-divadlo.cz is down

In b57e2da, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 2874c8e.


text:
🛑 tanecni-divadlo.cz is down

In 4e4208d, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 10ba649.


text:
🛑 tanecni-divadlo.cz is down

In ba39c82, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in d663925.


text:
🛑 tanecni-divadlo.cz is down

In 477febf, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 4afaf30.


text:
🛑 tanecni-divadlo.cz is down

In 73007a9, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in d41a6f6.


text:
🛑 CDN is down

In de31a25, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 522
Response time: 15686 ms

Resolved: CDN is back up in 9e5b00d.

repo: ceccun/status


text:
🛑 CDN is down

In 9dedb27, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 522
Response time: 15243 ms

Resolved: CDN is back up in 79ffe09.


text:
adds missing commas to rules.json

I was just fooling around with the project to see how it works and I ran into syntax issues because of the missing commas in the example rules.json. This change is not super important, but it might help others playing around with the project for the first time.

Coverage remained the same at 95.0% when pulling e50d37cdcacdca9ec083ed9ab8cf610854f00c6a on gedkott:master into 4ef431d0a87c5ed8164c71188f1aa68cb8f9c6cc on ceejbot:master.

source: gharchive/pull-request

authors: coveralls gedkott

repo: ceejbot/jthoober

license: isc

license_source: bigquery


text:
Remove DA header from proposal

Pending acceptance of ADR-006, the PartSetHeader is used to gossip blocks in the consensus reactor, which means there is no need to include the DA header in the proposal since validators don't do DAS.
As per https://github.com/celestiaorg/celestia-specs/issues/180#issuecomment-868548015, consider removing the DA header from proposal, if we use PartSetHeader to gossip blocks.

DAHeader is included in proposal: if validators don't do DAS this is not a strict requirement anymore! Only if the spec wants to very vaguely and very implicitly make assumptions around block propagation during consensus, which indeed is an implementation detail. If we want to keep the DAHeader in the Proposal, we should clarify here why DAHeader is included in the first place (previously for sampling, now for ??). Also if proposal include the DAHeader why don't Votes also include it?

completed in https://github.com/celestiaorg/celestia-core/pull/518
and since this reversion puts on par with tendermint, we should simply point to the tendermint specs

authors: adlerjohn evan-forbes

repo: celestiaorg/celestia-core


text:
share: Implement cacheAvailability

Resolves #180

should we keep a cache as well in the impl tho? but also persist to dis

So to proceed, you need to import Datastore and store there the fact that DASing happened. This might be not the most efficient way to do this, but I have no other ideas right now(cc @liamsi or @adlerjohn). Further, if we make our own protocol for ShareExchange(ShrEx 😄 ) instead of Bitswap along with custom storage for shares this probably won't be needed.
Besides, I would suggest identifying headers by their hashes and not heights.

should we keep a cache as well in the impl tho? but also persist to disk?

No need to. The caching in RAM is helpful when the value is accessed multiple times. In this case, we just need to know if the header was dased or no and DASer will do this once only.

What's the overhead of keeping track of this info? Can't be too much, can it? Bloom filters are...uh, not encouraged lol.

Codecov Report

Merging #786 (de3c057) into main (974e4ef) will decrease coverage by 0.14%.
The diff coverage is 76.92%.

:exclamation: Current head de3c057 differs from pull request most recent head a20269e. Consider uploading reports for the commit a20269e to get more accurate results

@@            Coverage Diff             @@
##             main     #786      +/-   ##
==========================================
- Coverage   52.80%   52.66%   -0.15%
==========================================
  Files         116      117       +1
  Lines        6607     6669      +62
==========================================
+ Hits         3489     3512      +23
- Misses       2753     2797      +44
+ Partials      365      360       -5

Impacted Files
Coverage Δ

cmd/flags_core.go
45.65% <0.00%> (-4.35%)
:arrow_down:

service/share/local_availability.go
77.77% <77.77%> (ø)

node/services/service.go
84.14% <100.00%> (+0.39%)
:arrow_up:

service/share/share.go
81.01% <100.00%> (ø)

service/share/testing.go
100.00% <100.00%> (ø)

node/state/keyring.go
1.96% <0.00%> (-62.75%)
:arrow_down:

cmd/flags_misc.go
54.38% <0.00%> (-8.78%)
:arrow_down:

libs/keystore/map_keystore.go
80.95% <0.00%> (-4.77%)
:arrow_down:

node/services/config.go
46.66% <0.00%> (-3.34%)
:arrow_down:

logs/logs.go
100.00% <0.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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

Another way to think about this is that we are storing the result of the availability, maybe the name can be something result.

Oops, there was some bug on the phone.

authors: Wondertan adlerjohn codecov-commenter renaynay

repo: celestiaorg/celestia-node


text:
chore(p2p): remove TrustedPeersRequestTimeout config field

Implementing this proposal https://github.com/celestiaorg/go-header/pull/28#issuecomment-1509951953 instead of https://github.com/celestiaorg/go-header/pull/28

Codecov Report

Merging #29 (600cf93) into main (a0b2334) will decrease coverage by 0.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #29      +/-   ##
==========================================
- Coverage   65.50%   65.24%   -0.26%
==========================================
  Files          35       35
  Lines        2760     2751       -9
==========================================
- Hits         1808     1795      -13
- Misses        798      801       +3
- Partials      154      155       +1

Impacted Files
Coverage Δ

p2p/exchange.go
78.82% <ø> (-0.38%)
:arrow_down:

p2p/options.go
40.29% <ø> (+1.40%)
:arrow_up:

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: Wondertan codecov-commenter

repo: celestiaorg/go-header


text:
Loading the extension removes icons

Installed the extension (v5) and the icons are all messed up. I guess it's showing the default icons instead of the adwaita ones.

GNOME 47, Bluefin DX Stable (Fedora Silverblue 41).

Yeah, that's because you need Adwaita-colors for it to work, clicking "Download" in extension's settings will do this for you. Sadly I can not make the extension download it without user consent.

clicking "Download" in extension's settings will do this for you

There are no settings, hence no Download button.

Sorry, didn't express correctly, I mean that it will, but for the version that is active on Gnome Extensions, you must get the icons from https://github.com/dpejoh/Adwaita-colors.

Got it. Had to install it into /var/usrlocal/share since i'm on a immutable distro.

authors: DarkGhostHunter celiopy

repo: celiopy/auto-adwaita-colors


text:
Random smart contract should store the randomness of the last epoch's block.

Expected Behavior
With https://github.com/celo-org/celo-blockchain/pull/844, we'll rely on having the last epoch's block randomness to be available in the smart contract.
Current Behavior
We currently only keep a window of blocks' randomness.

As part of this, we should revert https://github.com/celo-org/celo-blockchain/pull/845

repo: celo-org/celo-monorepo


text:
Celo:

Describe your issue here.
Environment

Elixir Version: 1.9.0

Erlang Version: 22

BlockScout Version: 3c418b3df3bb4d38abff295c13fc60c529a59487

User Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 14_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.2 Mobile/15E148 Safari/604.1

Steps to reproduce
Tell us how to reproduce this issue. If possible, push up a branch to your fork with a regression test we can run to reproduce locally.
Expected Behaviour
Tell us what should happen.
Actual Behaviour
Tell us what happens instead.

Can anyone help me with a pending transaction of celo

Can anyone help me with a pending transaction of celo

Can you share your address?

Can you share your address?

Is over 2 months now that is like that
On Fri, 29 Jan 2021 at 21:49, Martín Volpe notifications@github.com wrote:

Can you share your address?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/celo-org/celo-monorepo/issues/6818#issuecomment-770068663,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR6K3YB7QGDLG6WUCIZHLL3S4MUONANCNFSM4WZGS4LQ
.

Is over 2 months now that is like that
On Fri, 29 Jan 2021 at 21:49, Martín Volpe notifications@github.com wrote:

Can you share your address?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/celo-org/celo-monorepo/issues/6818#issuecomment-770068663,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR6K3YB7QGDLG6WUCIZHLL3S4MUONANCNFSM4WZGS4LQ
.

Hi @zimbrix91! Closing this issue as we didn't receive more information, but please feel free to reopen if you're still have this issue and are able to give us more information (address, network, asset, etc). Happy to help!


text:
App get crash when user try to upload profile picture from take photo section

Frequency: 100%
Repro on build version: Test Flight Build V1.10.1(46)
Does not Repro on build version: Android Internal Build V1.10.1(1004294336
Repro on build version: iPhone 6+ (12.4.5)
Does not Repro on devices: iPhone XR(14.2), Samsung Galaxy A5(7.0), iPhone SE 2(14.2)
Repro Steps:

Launch the application & go to Create Account screen.
Tap on Add photo icon.
Select Take photo section
Tap on photo button
Observed ,

Current Behavior: App get crash when try to upload profile picture.
Expected Behavior:  User should able to upload profile picture through Take photo option.
Observation: App get crash when user try to upload profile picture from settings> edit profile
Impact: User get blocked to upload profile picture .
Attachment: CrashonAddphoto.mp4
Crashlogs

Hi @jeanregisser & @isabellewei We have verified this issue on latest  app store build V1.10.1 and observe that issue is still repro.

App get crash user try to upload profile picture from take photo section
LogsonTakePhoto

Hi @jeanregisser & @isabellewei We have verified this issue on Testflight build V1.11.1(48) and observe that issue is fixed so, we are closing this ticket.
Device:- iPhone 6+ (12.4.5)

authors: Celoqa Lss-Ankit


text:
tobikuhlmann/update locked gold rewards docs

Description
This PR adds some details of the voting yield adjustment factor mechanism to the epoch rewards documentation, specifically to the Rewards for Locked Gold Holders page. The documentation has been a little sparse so far and I added some details here.
Other changes

Tested

Related issues

Backwards compatibility
It's just some additional lines of text to the documentation so should be fully backwards compatible.
Documentation

celo-monorepo/packages/docs/celo-codebase/protocol/proof-of-stake/locked-gold-rewards.md

How that would look in the docs and how the equations would render (GitHub doesnt render latex equations) can be seen here: https://app.gitbook.com/@eela/s/forked-monorepo-docs-test/v/docs-test%2Ftobikuhlmann%2FupdateLockedGoldReward/celo-codebase/protocol/proof-of-stake/epoch-rewards/locked-gold-rewards/~/settings/integrations


text:
Some minor README changes

https://github.com/centaurean/density/commit/8de0779c49f334b10890d134db4b02e98944505c Removed unnecessary typecast when using malloc(). See this SO post.
https://github.com/centaurean/density/commit/ec38d6fd9636ff36ce875d91242eef1074be61db Enabled syntax highlighting for the example code.

Otherwise, very useful project :grinning:

Thanks !

authors: gpnuma ryanmjacobs

repo: centaurean/density


text:
XLSX Files, Provider com.bea.xml.stream.EventFactory not found

My simple code:
InputStream myInput;
// initialize asset manager
AssetManager assetManager = getAssets();
//  open excel sheet
InputStream fin = openFileInput("myexcelsheet.xlsx");
// Create a workbook using the File System
XSSFWorkbook myWorkBook = new XSSFWorkbook(fin);
Produces Provider com.bea.xml.stream.EventFactory not found

Please read the main-page/README, especially the section "Necessary System-Properties".

Many thanks...
Il giorno sab 26 ott 2019 alle 21:31 Dominik Stadler <
notifications@github.com> ha scritto:

Please read the main-page/README, especially the section "Necessary
System-Properties".
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/centic9/poi-on-android/issues/69?email_source=notifications&email_token=ANTEWNJUNVUVJZSDNDOBZ4LQQSLIVA5CNFSM4JFM4QH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECKPHZI#issuecomment-546632677,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANTEWNM2AI6UUJZ26DWUT3TQQSLIVANCNFSM4JFM4QHQ
.


text:
[touch] Scrolling Tool Panel on touch devices doesn't work

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/ceolter/ag-grid/blob/master/CONTRIBUTING.md#question

Current behavior
Does not seem to be possible to scroll down with on the tool panel with touch gestures. Similar to:
https://github.com/ceolter/ag-grid/issues/418
https://github.com/ceolter/ag-grid/issues/1585
Expected behavior
Should be possible to scroll the tool panel to make hidden columns visible, or do other tool panel operations that might be hidden below the visible pane of content.
Minimal reproduction of the problem with instructions
Using agGrid demo, attempt to scroll the tool panel with device emulation in Chrome (or use a device).
What is the motivation / use case for changing the behavior?
User feedback
Please tell us about your environment:
Mobile devices tested: iOS, Android, Chrome device emulation

ag-Grid version: 8.2.0

Browser:
Any mobile browser

Language: N/A

Hi
Thanks for reporting this -  I've raised issue AG-432 our side for this. We'll update this thread once we have any updates.
thanks

Hi,
We are changing the process and closing all issues with a ticket number since they can be tracked from our pipeline https://www.ag-grid.com/ag-grid-pipeline/
Thanks
===============
If you are an ag-Grid Enterprise Customer, please raise this in our Zendesk support system - contact info@ag-grid.com for access. This is our primary channel for Support.
Bugs Raised Here:
We will do a periodic review of GitHub issues for any bugs raised and these can be tracked on our pipeline page: https://www.ag-grid.com/ag-grid-pipeline
Feature Requests/Support Raised Here:
We are reviewing how we process Feature Requests that come from GitHub. We currently have a very full pipeline of work which will be our priority for the coming months.
As a result, we don’t have capacity to take feature requests from GitHub.
We will review this as we move through our current backlog.
Thanks for your understanding.
ag-Grid Team.

repo: ceolter/ag-grid

license: mit


text:
Bug: Not Contains does not return blank or null values

I'm submitting a ...  (check one with "x")
[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/ceolter/ag-grid/blob/master/CONTRIBUTING.md#question

Current behavior
When I have a column with blank or filled values, if I type a value and select not contains, blank values do not return despite the fact that they do not contain the typed in value.
Expected behavior
When I filter by not contains, I should see all values that do not contain the value including the blank values.
Minimal reproduction of the problem with instructions
This can be seen on the documentation for the text filter: https://www.ag-grid.com/javascript-grid-filter-text/?framework=all#gsc.tab=0
in order to get it to happen,

sort the athletes (there are 3 with no names)
change sort to "not contains"
type a value (i.e. "aaron")
the values with nothing in them will also fail to show despite not containing "aaron"

What is the motivation / use case for changing the behavior?
I am using the grid to display data for a variety of document sources and some of the fields have the possibility of not being populated
Please tell us about your environment:
Windows 7/10, IE11 (though I can replicate it in Chrome).

ag-Grid version: 10.0.0 & 12.0.0

Browser:
IE11, Chrome 58

Language: ES5

This has been fixed and it will be available in the next release

authors: killyosaur makinggoodsoftware


text:
ERROR: package is not a legal parameter in an Ansible task or handler

I updated my git repo and tried re-execute site.yum because I going add new servers in cluster in two weeks,
root@deploy:/opt/ceph-ansible# git pull
Already up-to-date.
root@deploy:/opt/ceph-ansible# ansible-playbook site.yml
ERROR: package is not a legal parameter in an Ansible task or handler
root@deploy:/opt/ceph-ansible# ansible-playbook --version
ansible-playbook 1.9.4
configured module search path = None
root@deploy:/opt/ceph-ansible#
I need do something ?

Please switch to the ansible-1.9 branch

Or update to at least Ansible 2.0

TASK: [ceph-osd | start and add that the osd service(s) to the init sequence (for or after infernalis)] ***
failed: [osd01] => (item=1) => {"changed": false, "failed": true, "item": "1"}
msg: Job for ceph-osd@1.service failed because a timeout was exceeded. See "systemctl status ceph-osd@1.service" and "journalctl -xe" for details.
failed: [osd01] => (item=5) => {"changed": false, "failed": true, "item": "5"}
msg: Job for ceph-osd@5.service failed because a timeout was exceeded. See "systemctl status ceph-osd@5.service" and "journalctl -xe" for details.
failed: [osd03] => (item=2) => {"changed": false, "failed": true, "item": "2"}
msg: Job for ceph-osd@2.service failed because a timeout was exceeded. See "systemctl status ceph-osd@2.service" and "journalctl -xe" for details.
failed: [osd02] => (item=0) => {"changed": false, "failed": true, "item": "0"}
msg: Job for ceph-osd@0.service failed because a timeout was exceeded. See "systemctl status ceph-osd@0.service" and "journalctl -xe" for details.
failed: [osd02] => (item=3) => {"changed": false, "failed": true, "item": "3"}
msg: Job for ceph-osd@3.service failed because a timeout was exceeded. See "systemctl status ceph-osd@3.service" and "journalctl -xe" for details.
failed: [osd01] => (item=8) => {"changed": false, "failed": true, "item": "8"}
msg: Job for ceph-osd@8.service failed because a timeout was exceeded. See "systemctl status ceph-osd@8.service" and "journalctl -xe" for details.
failed: [osd03] => (item=4) => {"changed": false, "failed": true, "item": "4"}
msg: Job for ceph-osd@4.service failed because a timeout was exceeded. See "systemctl status ceph-osd@4.service" and "journalctl -xe" for details.
failed: [osd02] => (item=6) => {"changed": false, "failed": true, "item": "6"}
msg: Job for ceph-osd@6.service failed because a timeout was exceeded. See "systemctl status ceph-osd@6.service" and "journalctl -xe" for details.
failed: [osd03] => (item=7) => {"changed": false, "failed": true, "item": "7"}
msg: Job for ceph-osd@7.service failed because a timeout was exceeded. See "systemctl status ceph-osd@7.service" and "journalctl -xe" for details.

authors: leseb rlljorge

repo: ceph/ceph-ansible


text:
Common: Do not install ntp when ntp_service_enabled is false

ntp is still installed even if ntp_service_enabled is set to false.
That could be a problem if the time synchronization is managed by
something else than ceph-ansible or if you want to use different NTP
implementation as suggested in #1354.
Fixes: #1354
Signed-off-by: Guillaume Abrioux gabrioux@redhat.com

jenkins test ansible2.2-docker_cluster


text:
ignore error when key is not exist

(cherry picked from commit 027f9aaf09fd63a887a8d725b542930219f43707)
Signed-off-by: Guillaume Abrioux gabrioux@redhat.com

backport of #1500

fix https://bugzilla.redhat.com/show_bug.cgi?id=1452061

authors: guits leseb


text:
roles: remove leftover from pr #4319

pr #4319 introduced some uesless become: true on systemd tasks.
Signed-off-by: Guillaume Abrioux gabrioux@redhat.com

jenkins test centos-non_container-lvm_osds

jenkins test centos-container-all_daemons

jenkins test centos-container-collocation

jenkins test centos-container-all_daemons

jenkins test centos-non_container-collocation

jenkins test centos-non_container-all_daemons

authors: dsavineau guits


text:
Fix cloning of ceph-ansible.

Make sure we are in the right directory when we clone ceph-ansible.
Ceph-ansible clones into ~, and the ansible playbook is run from ~/ceph_ansible
Signed-off-by: Warren Usui wusui@redhat.com

I do not think that this change needs to be made.

repo: ceph/teuthology


text:
Inconsistent formatting of require blocks in go.mod

Currently the go.mod has 3 require blocks, while it should only have two: one for direct dependencies, and another one for indirect dependencies.
This is not a bug, but rather a small consistency issue. I can submit a PR to address this.

Thank you for reporting the problem. You are more than welcome to submit a PR if you would like it fix it.

authors: Juneezee charithe

repo: cerbos/cerbos


text:
Open paths fix

Attempt at fixing open paths getting closed:

check if path d attribute is closed using RegExp, and pass condition as attribute
clone outlinedData object in averageSegmentJoins function, and reference first and last cloned segments' samples instead of  modified outlinedData object, if the path is open

Tested successfully with custom path, the infinity path from the demo, and a circle. Might need some further testing.

@cereallarceny Done.

repo: cereallarceny/gradient-path


text:
peerDependencies - incorrect version number?

Hi, I'm getting the following error when running npm i on a newly cloned repo:
npm WARN peerDependencies The peer dependency cerebral@^0.35.0-0 included from cerebral-module-router will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN deprecated wrench@1.5.8: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN optional dep failed, continuing fsevents@1.0.14
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\benjaminb\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "i"
npm ERR! node v4.5.0
npm ERR! npm  v2.14.3
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package cerebral@1.0.1 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer cerebral-module-devtools@0.7.2 wants cerebral@^0.35.0-0 || ^1.0.0
npm ERR! peerinvalid Peer cerebral-module-recorder@0.6.1 wants cerebral@^0.35.0-0 || ^1.0.0
npm ERR! peerinvalid Peer cerebral-module-router@0.16.1 wants cerebral@^0.35.0-0
npm ERR! peerinvalid Peer cerebral-view-react@0.12.12 wants cerebral@^0.35.0-0 || ^1.0.0
Attempting to install cerebral results in:
$ npm i  cerebral --save
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\benjaminb\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "i" "cerebral" "--save"
npm ERR! node v4.5.0
npm ERR! npm  v2.14.3
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package cerebral@1.0.1 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer cerebral-module-devtools@0.7.2 wants cerebral@^0.35.0-0 || ^1.0.0
npm ERR! peerinvalid Peer cerebral-module-recorder@0.6.1 wants cerebral@^0.35.0-0 || ^1.0.0
npm ERR! peerinvalid Peer cerebral-module-router@0.16.1 wants cerebral@^0.35.0-0
npm ERR! peerinvalid Peer cerebral-view-react@0.12.12 wants cerebral@^0.35.0-0 || ^1.0.0
Any ideas?

Thanks for report.
You can ignore this messages.
Will look to fix dependencies at weekend.
Let me know if it doesn't build anyway

authors: Guria cogwire

repo: cerebral/cerebral-todomvc


text:
custom record_count like methods

How do i make custom methods like record_count? not possible without monkey patching? record_count is hardcoded in FindOperation, any way i can replace with my custom operation?
Say, i want to group results by category and output in total meta information.

I'm also interested for a solution here. I'm using mongoid where the count method do not take any parameter unlike the active-record version.

Yesterday I merged a branch that reworks the operation processing aspect of the gem. The old global OperationsProcessor is out and individual resource processors are in (a default one can be defined as well). See https://github.com/cerebris/jsonapi-resources#operation-processors
I think this should give you the flexibility you need. But please see the note at the end of the section. If you override the find method it may not pickup future changes if we alter how find works.
As of now this is only on the master branch, though I hope to get a beta release out soon.

i'm afraid i phrased it wrong. I was asking for a way to add methods like record_count. So i could have methods like aggregate_by(:field) in FindOperation and then use them in my own operation_processor to say, add faceted search metadata in response.

@Fedcomp I think I understand, but maybe not. The processor replaces the code that was buried on the FindOperation. So it gives you a place to implement your own code to override the default find implementation. You could add your custom methods on a resource specific processor or on a customized default processor. Look at the Api::V4::BookProcessor example in the link above.

@lgebhardt thanks for the clarification. I'm still afraid of this kind of code in master https://github.com/cerebris/jsonapi-resources/blob/master/lib/jsonapi/processor.rb#L163
I think you should have an interface defined on the resource that basically proxy the count call to the records. This way, one, can simply override the method definition in the resource if he needs to:
class FooResource < JSONAPI::Resource
  def self.record_count(*args)
    records.count(*args)
  end
end

Where, in my case would be as simple as records.count

@gottfrois Does #720 work for you? It's a little different than you propose. I might be making a wrong assumption that it's the :all that AR now requires that's messing you up. With the proposed PR you could override this on a resource level, but there isn't the option to pass in custom arguments as you proposed.

This will work fine for now. The PRs does not replace all records.count(:all) occurrences though right?

@gottfrois Thanks, I had missed a call to count in the processor. Now there's one place to override the records.count(:all) for a resource (or all resources).

authors: Fedcomp gottfrois lgebhardt

repo: cerebris/jsonapi-resources


text:
Remove unused @key attribute

It seems that this @key attribute is no longer used (replaced by @foreign_key which is set in the base class from the options hash in https://github.com/cerebris/jsonapi-resources/commit/7b2459a6e83d923572e747b1089b7f7e2de7811d)

Thanks!

authors: lgebhardt pmukerji


text:
Terra form fieldset standalone component.

Summary
Resolves this.
Additional Details
Created a new fieldset component which replicates the already existing form/fieldset component.
Deployment Link
https://terra-core-deployed-pr-1305.herokuapp.com/static/#/site/form-fieldset

I'm hesitant to provide the error prop as it won't be needed for future API. I'm fine leaving if we will remove with major version bump later.

@neilpfeiffer +1 for removing the error prop. I looked through some of the legacy forms in our code companions and wasn't able to find an example of fieldsets needing to display error messages. If this changes, we can add it back in a passive release.

Almost there! Can we reduce the size of those screenshots potentially?

@JakeLaCombe Resized the screenshots.

@neilpfeiffer This is ready for UX review

Tested: PR #1305
Resolves: Issue #1304

Reviewed:

port of fieldset from terra-form/lib/Fieldset into new standalone package
no additional changes to visual or functionality

Verified by @neilpfeiffer, Ready for release after Functional Review by @juliezajic.

Pass

UX Review

Functional verification complete. Fieldset examples display and function as expected.

authors: JakeLaCombe bjankord msaikaushik1992 neilpfeiffer

repo: cerner/terra-core


text:
Update Search Field to consume new Input

Summary
Part of #1650
This PR uplifts search field, as it's not dependent on the forward ref discussions we will have during war room this week.

Displays as intended

Pass

UX Review

authors: JakeLaCombe neilpfeiffer


text:
Add SenseLabs to USERS.md

Pull Request Motivation
We've been using cert-manager for years both internally as well as in your clients' clusters to generate certificates and secure our Ingresses.
Release Note

NONE

Great to hear!
/lgtm
/approve

authors: inteon netthier

repo: cert-manager/cert-manager


text:
Document External Vault secretless auth options (v2)

I reviewed https://github.com/cert-manager/website/pull/1397 and simplified the documentation, while trying to maintain as much of the valuable insights as possible.

/approve
/lgtm

repo: cert-manager/website


text:
Task :react-native-bottom-sheet-behavior:compileDebugJavaWithJavac FAILED

AndroidX seems not supported

Task :react-native-bottom-sheet-behavior:compileDebugJavaWithJavac FAILED
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/
main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:10: error: package android.support.annotation d
oes not exist
import android.support.annotation.NonNull;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:11: error: package android.support.design.widget does not exist
import android.support.design.widget.AppBarLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:12: error: package android.support.design.widget does not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:13: error: package android.support.v4.content does not exist
import android.support.v4.content.ContextCompat;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:14: error: package android.support.v4.widget does not exist
import android.support.v4.widget.NestedScrollView;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:44: error: package AppBarLayout does not exist
public class ScrollingAppBarLayoutBehavior extends AppBarLayout.ScrollingViewBehavior {
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:6: error: package android.support.annotation does not exist
import android.support.annotation.IntDef;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:7: error: package android.support.annotation does not exist
import android.support.annotation.NonNull;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:8: error: package android.support.design.widget does not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:9: error: package android.support.v4.view does not exist
import android.support.v4.view.MotionEventCompat;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:10: error: package android.support.v4.view does not exist
import android.support.v4.view.NestedScrollingChild;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:11: error: package android.support.v4.view does not exist
import android.support.v4.view.ViewCompat;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:12: error: package android.support.v4.widget does not exist
import android.support.v4.widget.ViewDragHelper;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:28: error: package CoordinatorLayout does not exist
public class RNBottomSheetBehavior extends CoordinatorLayout.Behavior {
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:69: error: cannot find symbol
public boolean layoutDependsOn(CoordinatorLayout parent, View child, View dependency) {
^
symbol:   class CoordinatorLayout
location: class ScrollingAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:81: error: cannot find symbol
public boolean onDependentViewChanged(CoordinatorLayout parent, View child, View dependency) {
^
symbol:   class CoordinatorLayout
location: class ScrollingAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:92: error: cannot find symbol
public Parcelable onSaveInstanceState(CoordinatorLayout parent, View child) {
^
symbol:   class CoordinatorLayout
location: class ScrollingAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:97: error: cannot find symbol
public void onRestoreInstanceState(CoordinatorLayout parent, View child, Parcelable state) {
^
symbol:   class CoordinatorLayout
location: class ScrollingAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:103: error: cannot find symbol
private boolean init(CoordinatorLayout parent, View child, View dependency) {
^
symbol:   class CoordinatorLayout
location: class ScrollingAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:125: error: cannot find symbol
public void setAppBarVisible(final AppBarLayout appBarLayout, final boolean visible){
^
symbol:   class AppBarLayout
location: class ScrollingAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutBehavior.java:204: error: cannot find symbol
private void getBottomSheetBehavior(@NonNull CoordinatorLayout coordinatorLayout) {
^
symbol:   class CoordinatorLayout
location: class ScrollingAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:113: error: cannot find symbol
private ViewDragHelper mViewDragHelper;
^
symbol:   class ViewDragHelper
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:144: error: cannot find symbol
public Parcelable onSaveInstanceState( CoordinatorLayout parent, V child ) {
^
symbol:   class CoordinatorLayout
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:149: error: cannot find symbol
public void onRestoreInstanceState( CoordinatorLayout parent, V child, Parcelable state ) {
^
symbol:   class CoordinatorLayout
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:163: error: cannot find symbol
public boolean onLayoutChild( CoordinatorLayout parent, V child, int layoutDirection ) {
^
symbol:   class CoordinatorLayout
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:201: error: cannot find symbol
public boolean onInterceptTouchEvent( CoordinatorLayout parent, V child, MotionEvent event ) {
^
symbol:   class CoordinatorLayout
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:262: error: cannot find symbol
public boolean onTouchEvent( CoordinatorLayout parent, V child, MotionEvent event ) {
^
symbol:   class CoordinatorLayout
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:294: error: cannot find symbol
public boolean onStartNestedScroll( CoordinatorLayout coordinatorLayout, V child, View directTargetChild, View target, int nestedScrollAxes ) {
^
symbol:   class CoordinatorLayout
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:326: error: cannot find symbol
public void onNestedPreScroll( CoordinatorLayout coordinatorLayout, V child, View target, int dx, int dy, int[] consumed ) {
^
symbol:   class CoordinatorLayout
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:381: error: cannot find symbol
public void onStopNestedScroll( CoordinatorLayout coordinatorLayout, V child, View target ) {
^
symbol:   class CoordinatorLayout
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:471: error: cannot find symbol
public boolean onNestedPreFling(CoordinatorLayout coordinatorLayout, V child, View target,
^
symbol:   class CoordinatorLayout
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:682: error: package ViewDragHelper does not exist
private final ViewDragHelper.Callback mDragCallback = new ViewDragHelper.Callback() {
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/FloatingActionButtonView.java:10: error: package android.support.design.widget does not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/FloatingActionButtonView.java:11: error: package android.support.design.widget does not exist
import android.support.design.widget.FloatingActionButton;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/FloatingActionButtonView.java:19: error: cannot find symbol
public class FloatingActionButtonView extends FloatingActionButton {
^
symbol: class FloatingActionButton
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BackdropBottomSheetBehavior.java:4: error: package android.support.annotation does not exist
import android.support.annotation.NonNull;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BackdropBottomSheetBehavior.java:5: error: package android.support.design.widget does not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BackdropBottomSheetBehavior.java:6: error: package android.support.v4.widget doesnot exist
import android.support.v4.widget.NestedScrollView;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BackdropBottomSheetBehavior.java:39: error: package CoordinatorLayout does not exist
public class BackdropBottomSheetBehavior extends CoordinatorLayout.Behavior {
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BackdropBottomSheetBehavior.java:57: error: cannot find symbol
public boolean layoutDependsOn(CoordinatorLayout parent, View child, View dependency) {
^
symbol:   class CoordinatorLayout
location: class BackdropBottomSheetBehavior
where V is a type-variable:
V extends View declared in class BackdropBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BackdropBottomSheetBehavior.java:70: error: cannot find symbol
public boolean onDependentViewChanged(CoordinatorLayout parent, View child, View dependency) {
^
symbol:   class CoordinatorLayout
location: class BackdropBottomSheetBehavior
where V is a type-variable:
V extends View declared in class BackdropBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BackdropBottomSheetBehavior.java:109: error: cannot find symbol
private void getBottomSheetBehavior(@NonNull CoordinatorLayout coordinatorLayout) {
^
symbol:   class CoordinatorLayout
location: class BackdropBottomSheetBehavior
where V is a type-variable:
V extends View declared in class BackdropBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BottomSheetBehaviorView.java:4: error: package android.support.design.widget doesnot exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BottomSheetBehaviorView.java:5: error: package android.support.v4.widget does notexist
import android.support.v4.widget.NestedScrollView;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BottomSheetBehaviorView.java:12: error: cannot find symbol
public class BottomSheetBehaviorView extends NestedScrollView {
^
symbol: class NestedScrollView
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BackdropBottomSheetManager.java:3: error: package android.support.design.widget does not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/CoordinatorLayoutView.java:4: error: package android.support.design.widget does not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/CoordinatorLayoutView.java:7: error: cannot find symbol
public class CoordinatorLayoutView extends CoordinatorLayout {
^
symbol: class CoordinatorLayout
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BottomSheetBehaviorManager.java:3: error: package android.support.annotation doesnot exist
import android.support.annotation.NonNull;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BottomSheetBehaviorManager.java:4: error: package android.support.v4.view does not exist
import android.support.v4.view.ViewCompat;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BottomSheetBehaviorManager.java:5: error: package android.support.v4.widget does not exist
import android.support.v4.widget.NestedScrollView;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/BottomSheetBehaviorManager.java:144: error: cannot find symbol
private void attachNestedScrollChild(final BottomSheetBehaviorView parent, final NestedScrollView nestedScroll){
^
symbol:   class NestedScrollView
location: class BottomSheetBehaviorManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/RNBottomSheetBehavior.java:87: error: cannot find symbol
@IntDef({STATE_EXPANDED, STATE_COLLAPSED, STATE_DRAGGING, STATE_ANCHOR_POINT, STATE_SETTLING, STATE_HIDDEN})
^
symbol:   class IntDef
location: class RNBottomSheetBehavior
where V is a type-variable:
V extends View declared in class RNBottomSheetBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:6: error: package android.support.design.widget does not exist
import android.support.design.widget.AppBarLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:7: error: package android.support.design.widget does not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:8: error: package android.support.v7.widget does not exist
import android.support.v7.widget.Toolbar;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:18: error: cannot find symbol
public class MergedAppBarLayoutManager extends ViewGroupManager {
^
symbol: class AppBarLayout
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:11: error: package android.support.annotation does not exist
import android.support.annotation.NonNull;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:12: error: package android.support.design.widget does not exist
import android.support.design.widget.AppBarLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:13: error: package android.support.design.widget does not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:14: error: package android.support.v4.content does not exist
import android.support.v4.content.ContextCompat;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:15: error: package android.support.v4.widget doesnot exist
import android.support.v4.widget.NestedScrollView;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:16: error: package android.support.v7.widget doesnot exist
import android.support.v7.widget.Toolbar;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:52: error: package AppBarLayout does not exist
public class MergedAppBarLayoutBehavior extends AppBarLayout.ScrollingViewBehavior {
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:36: error: cannot find symbol
public AppBarLayout createViewInstance(ThemedReactContext context) {
^
symbol:   class AppBarLayout
location: class MergedAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:51: error: cannot find symbol
public void setTranslucent(AppBarLayout view, boolean translucent) {
^
symbol:   class AppBarLayout
location: class MergedAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:60: error: cannot find symbol
public void setBarStyle(AppBarLayout view, String barStyle) {
^
symbol:   class AppBarLayout
location: class MergedAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:65: error: cannot find symbol
public void setBarStyleTransparent(AppBarLayout view, String barStyle) {
^
symbol:   class AppBarLayout
location: class MergedAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:70: error: cannot find symbol
public void setMergedColor(AppBarLayout view, String mergedColor) {
^
symbol:   class AppBarLayout
location: class MergedAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:78: error: cannot find symbol
public void setToolbarColor(AppBarLayout view, String toolbarColor) {
^
symbol:   class AppBarLayout
location: class MergedAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:88: error: cannot find symbol
public void setStatusBarColor(AppBarLayout view, String statusBarColor) {
^
symbol:   class AppBarLayout
location: class MergedAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:97: error: cannot find symbol
public void setHeight(AppBarLayout view, int height) {
^
symbol:   class AppBarLayout
location: class MergedAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutManager.java:104: error: cannot find symbol
public void addView(AppBarLayout parent, View child, int index) {
^
symbol:   class AppBarLayout
location: class MergedAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:70: error: cannot find symbol
private Toolbar mToolbar;
^
symbol:   class Toolbar
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:87: error: cannot find symbol
public boolean layoutDependsOn(CoordinatorLayout parent, View child, View dependency) {
^
symbol:   class CoordinatorLayout
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:99: error: cannot find symbol
public boolean onDependentViewChanged(CoordinatorLayout parent, View child, View dependency) {
^
symbol:   class CoordinatorLayout
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:143: error: cannot find symbol
private void init(@NonNull CoordinatorLayout parent, @NonNull View child){
^
symbol:   class CoordinatorLayout
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:176: error: cannot find symbol
private void getBottomSheetBehavior(@NonNull CoordinatorLayout coordinatorLayout) {
^
symbol:   class CoordinatorLayout
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:193: error: cannot find symbol
private boolean isDependencyYBelowAnchorPoint(@NonNull CoordinatorLayout parent, @NonNull View dependency){
^
symbol:   class CoordinatorLayout
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:199: error: cannot find symbol
private boolean isDependencyYBetweenAnchorPointAndToolbar(@NonNull CoordinatorLayout parent, @NonNull View child, @NonNull View dependency){
^
symbol:   class CoordinatorLayout
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:240: error: cannot find symbol
private View findTitleTextView(Toolbar toolbar){
^
symbol:   class Toolbar
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:346: error: cannot find symbol
public void setToolbar(Toolbar toolbar) {
^
symbol:   class Toolbar
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:371: error: cannot find symbol
public Parcelable onSaveInstanceState(CoordinatorLayout parent, View child) {
^
symbol:   class CoordinatorLayout
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/MergedAppBarLayoutBehavior.java:376: error: cannot find symbol
public void onRestoreInstanceState(CoordinatorLayout parent, View child, Parcelable state) {
^
symbol:   class CoordinatorLayout
location: class MergedAppBarLayoutBehavior
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutManager.java:6: error: package android.support.design.widgetdoes not exist
import android.support.design.widget.AppBarLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutManager.java:7: error: package android.support.design.widgetdoes not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutManager.java:15: error: cannot find symbol
public class ScrollingAppBarLayoutManager extends ViewGroupManager {
^
symbol: class AppBarLayout
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutManager.java:27: error: cannot find symbol
public AppBarLayout createViewInstance(ThemedReactContext context) {
^
symbol:   class AppBarLayout
location: class ScrollingAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutManager.java:40: error: cannot find symbol
public void setTranslucent(AppBarLayout view, boolean translucent) {
^
symbol:   class AppBarLayout
location: class ScrollingAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutManager.java:49: error: cannot find symbol
public void setBarStyle(AppBarLayout view, String barStyle) {
^
symbol:   class AppBarLayout
location: class ScrollingAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutManager.java:54: error: cannot find symbol
public void setBarStyleTransparent(AppBarLayout view, String barStyle) {
^
symbol:   class AppBarLayout
location: class ScrollingAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutManager.java:59: error: cannot find symbol
public void setStatusBarColor(AppBarLayout view, String color) {
^
symbol:   class AppBarLayout
location: class ScrollingAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollingAppBarLayoutManager.java:64: error: cannot find symbol
public void setHeight(AppBarLayout view, int height) {
^
symbol:   class AppBarLayout
location: class ScrollingAppBarLayoutManager
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollAwareFABBehavior.java:4: error: package android.support.annotation does notexist
import android.support.annotation.NonNull;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollAwareFABBehavior.java:5: error: package android.support.design.widget does not exist
import android.support.design.widget.AppBarLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollAwareFABBehavior.java:6: error: package android.support.design.widget does not exist
import android.support.design.widget.CoordinatorLayout;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollAwareFABBehavior.java:7: error: package android.support.design.widget does not exist
import android.support.design.widget.FloatingActionButton;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollAwareFABBehavior.java:8: error: package android.support.v4.view does not exist
import android.support.v4.view.ViewCompat;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/main/java/com/bottomsheetbehavior/ScrollAwareFABBehavior.java:9: error: package android.support.v4.widget does not exist
import android.support.v4.widget.NestedScrollView;
^
/home/ubuntu/MyApp/node_modules/react-native-bottom-sheet-behavior/android/src/

I know this is already a very old question, but the solution is to run npx jetify before building the app.

authors: Hukutus neerajemorphis


text:
Add candidates' answers to their card in Results

Based on user feedback – several users expected individual answers there (and found the additional info useless), not everyone notices/wants the whole comparison.
Can provide a Figma design.

Duplicitní #505. Zavírám.

authors: klarasch krystof-k


text:
Release version 3.0.1 to production

Original report on BitBucket by John Shepherdson (GitHub: john-shepherdson).

Included issues are https://github.com/cessda/cessda.cvs.two/issues?q=is%3Aissue+milestone%3A3.0.1
Target date is 21 Feb 2023, subject to fixes being tested and signed off before then.
Release checklist: https://docs.google.com/spreadsheets/d/1KzLWKT7ZIPoQfBnuNYmqyex_fsASqASp3MUCLVp1ix8/edit#gid=1324600836
Release report: https://docs.google.com/document/d/1O1P3bT9I2P_LRrLtnyXCNPl05URPc0_LyaddKhR5Gn0/edit#heading=h.bxl4rzqycrnr

I have checked all user-facing issues for 3.0.1 and seem to be ok on staging. I created a separate issue for the citations that are currently not updating with the version number - I guess we can push that to the next release since it is of minor importance.
I approve the release for 7 March.
I will send an email to all editors tomorrow morning that the content is locked from 7 Marc 12 CET onwards.

CVS version 3.0.1 is released. @MajaDolinar please check if everything is okay on production.

I would not close this issue, since not everything is fine on production. I have reported a new issue this morning.
See https://github.com/cessda/cessda.cvs.two/issues/558

Closing the issue, everything is functioning properly on production. I will send an email to the Editors that the CVS is available again.


text:
Nullability for return values of Java methods with generic type.

Given a method of a Java class (and the used interface)
public <T> T performInTransaction(TransactionalOperation<T> op);

public interface TransactionalOperation<T> {
    T perform();
}

The method is visible in Ceylon as
shared T performInTransaction<T>(TransactionalOperation<T> op)
    given T satisfies Object;

which inhibits return value null.
A Java library might not provide an additional implementation for return type void, because that can be "emulated" using Java's Void type with its null value. Using it this way with Ceylon callables returning null (or void functions) is not possible, but should be.

I believe the general problem is that given the way interop model loading works, you cannot use an optional type as a type argument to a Java method. You can however use optionals as type arguments to types, which seems fine.
A couple notes:
@dlkw confirmed on gitter that the same problem exists when attempting to pass a TransactionalOperation<String?> to performInTransaction().
Renato also ran into this restriction attempting to call ExecutorService.submit(). See https://gitter.im/ceylon/user?at=567076228b28de8704521446

I just noticed the very strange error message:
Argument must be assignable to parameter op of performInTransaction in ServerRuntime: Result() is not assignable to <Result&Object>?()
in the following code:
shared Result execute<Result>(callable)
{
    Result() callable;
    value result = performInTransaction(()
    {
        Result result = callable();
        return result;
    });
}

The following does compile, I'm wondering what's happening here:
shared Result execute<Result>(callable)
{
    Result() callable;
    value result = performInTransaction(()
    {
        Result result = callable();
        if (is Null result) {
            return result;
        }
        return result;
    });
}

Rejoiced too early: it gives a backend error:
Ceylon backend error: incompatible types: java.lang.Object cannot be converted to Result

authors: dlkw jvasileff

repo: ceylon/ceylon


text:
serial tests

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

test


text:
Test share_the_page Wagtail hook and associated functions

This is the start of the unit testing. For now, this takes care of the v1/wagtail_hooks.py hook called share_the_page and its associated functions.
Additions

Tests for share_the_page wagtail hook and associated functions

Changes

Refactored share_the_page

Testing

Run tox

Review

@kave
@richaagarwal

Notes

Should be 18 additional tests for a total of 42

Todos

Keep on testin'

Checklist

[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Passes all existing automated tests
[x] New functions include new tests
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Testing this now

:+1:

👍

Should this be merged or closed?

Call me overly paranoid, but since this is touching the share logic I wanted to leave this alone until after launch. I'll close this for now to remove clutter, but please DO NOT DELETE THE BRANCH.

Reopening for review

@kurtw If nothing has changed, my 👍 is still valid

Hmm, actually I get this error ImportError: No module named cfpb_common inside this branch

@richaagarwal you'll need to install django-commons in your project to get it work

Fixed.

Which tests need leadership calendar and agreement datavase repos? I think we're supposed to avoid including internal URL's in the external project (and that's why we have the OPTIONAL_APPS system).
cfpb_common, I think, needs to be brought in to this repo. (because we do now have code in the repo that depends on it)

That last commit has been removed as of Friday. @rosskarchner should we pause this PR again until we've merged common in?

This PR would allow that  merge to go forward: https://github.com/cfpb/cfgov-refresh/pull/2067

#2067 has been merged

Ready again.

👍

👍

authors: kave kurtw richaagarwal rosskarchner

repo: cfpb/cfgov-refresh


text:
Adds delay to search test to allow transition to complete

Changes

Adds delay to search test to allow transition to complete

Testing

gulp build && gulp test:acceptance --sauce=false --specs=organisms/global-search.js should pass

Review

@richaagarwal
@jimmynotjim
@sebworks

👍

👍

authors: anselmbradford jimmynotjim sebworks


text:
Geocoding API docs

Public documentation for developers

Reference to checklists, best practices, standards, usability testing for APIs, etc…
http://18f.github.io/API-Usability-Testing/pages/lessons_learned

Here's the "HMDA API Docs" site mentioned at today's standup:

http://cfpb.github.io/api/hmda/

Plenty of good examples:
https://stripe.com/docs/api#intro
https://docs.connect.squareup.com/
https://dev.twitter.com/overview/documentation

And don't forget MailChimp...
https://apidocs.mailchimp.com/gettingstarted/connectivity.php

:+1: Thanks @netplusdesign

authors: awolfe76 hkeeler jmarin netplusdesign

repo: cfpb/grasshopper


text:
Activator incompatibility

On occasion VolumeBar9 and Activator will crash the Springboard, I think because of the hook on VolumeControl.
Hard to test; hard to reproduce.
Log files:

SpringBoard-2016-08-31-071058.symbolicated.ips.txt
SpringBoard-2016-08-31-071058.syslog.txt

Probably not a incompatibility? All the logs I've seen crash on -[VolumeBar resetTimer]

Logs with activator uninstalled:

SpringBoard-2016-08-31-212650.symbolicated.ips.txt
SpringBoard-2016-08-31-212650.syslog.txt

This confirms that it's definitely something with only VolumeBar9.

When adding logging to the tweak, the problem seems to disappear. Still hard to know for sure. Below is what was added.
VolumeBar.xm
-(void)resetTimer {
  HBLogDebug(@"in resetTimer");
  if(hide != nil) {
    HBLogDebug(@"hide exists");
    [hide invalidate];
    HBLogDebug(@"hide invalidated");
    hide = nil;
    HBLogDebug(@"hide = nil now");
    hide = [NSTimer scheduledTimerWithTimeInterval:_delayTime target:self selector:@selector(_hideHUD) userInfo:nil repeats:NO];
    HBLogDebug(@"new hide created");
  }
}

Tweak.xm
%hook VolumeControl

-(void)increaseVolume {
  HBLogDebug(@"hooked increaseVolume");
  if(active && vbar != nil) {
    HBLogDebug(@"calling resetTimer");
    [vbar resetTimer];
  }

  %orig;
}

%end

One report has come in that the crash is actually from pressing the volume buttons and calling resetTimer while the banner is animating away.

I was able to reproduce it in this way! Sweet, should be a relatively easy fix to disable any functionality of resetTimer after hideHUD has been called.


text:
Address --noincompatible_disallow_empty_glob that was added to rules_xcodeproj due to issue in bzlformat_pkg.bzl

rules_xcodeproj PR: https://github.com/buildbuddy-io/rules_xcodeproj/pull/380#discussion_r863010450
Related to buildbuddy-io/rules_xcodeproj#380
Tasks

[ ] Update bazel-starlib to support flag. Will need to disable items related to rules_nodejs and rules_bazel_integration_test.

[ ] Need to allow a client to specify the deps that they will use. Allows us to avoid items related to rules_nodejs.
[ ] Temporarily disable integration tests

[ ] Create a bazel-starlib release.
[ ] Update rules_bazel_integration_test to support flag.

[ ] Update to use latest bazel-starlib
[ ] Update to use latest bazel-skylib

[ ] Create a rules_bazel_integration_test release.
[ ] Update bazel-starlib to use latest rules_bazel_integration_test

[ ] Enable integration tests

[ ] Create a bazel-starlib release.
[ ] Update rules_xcodeproj to use latest bazel-starlib.
[ ] Update rules_nodejs to support flag.

[ ] May need to transition to use rules_bazel_integration_test

[ ] Update bazel-starlib to use updated rules_nodejs
[ ] Create a bazel-starlib release.

To enable flag:
# Don't allow empty glob patterns by default
build --incompatible_disallow_empty_glob

repo: cgrindel/bazel-starlib


text:
What hosting service do you use?

I'm at just wondering what you use to host the demo?

Hey, for the backend I use Google Cloud Platform - one vm instance. For the frontend I use Firebase hosting

is it free? do you know working free alternitives?


text:
🛑 Personal is down

In 8d8907b, Personal (https://chadburrus.com) was down:

HTTP code: 403
Response time: 131 ms

Resolved: Personal is back up in 66624df.

repo: chadburrus/upptime


text:
Prevent ZeroDivisionError in softmax_cross_entropy when input size is 0

Fix #3311
This error often happens when all the inputs are masked, and shape is like (0, 512, 16, 16)

jenkins, test this please

LGTM!
Thank you very much!

repo: chainer/chainer


text:
[WIP] Replace get_device

This PR replaces get_device because it is deprecated in new version of Chainer.

Is this still WIP? Changes seems good to me.

I have not confirmed the execution of all examples yet. I will change it after confirming them.

c.f. https://docs.chainer.org/en/v4.0.0/reference/util/generated/chainer.backends.cuda.get_device.html#chainer.backends.cuda.get_device

Examples have been all tested.

repo: chainer/chainermn


text:
Empty styles when adding container queries to staticCss

Description
When adding a staticCss config in the panda.config.ts I expect the styles to be generated correctly.
For this staticCss config:
    staticCss: {
        css: [
            {
                properties: {
                    fontSize: [
                        'sm',
                        'base',
                        'lg',
                        'xl',
                        '2xl',
                        '3xl',
                        '4xl',
                        '5xl',
                        '6xl',
                        '7xl',
                        '8xl',
                    ],
                    fontWeight: ['*'],
                },
                conditions: ['@pb/sm', '@pb/md', '@pb/lg', '@pb/xl'],
            },

The generated css styles look incomplete:

 ._\@pb\/sm_sm {_@pb/sm: sm;
}

 ._\@pb\/md_sm {_@pb/md: sm;
}

 ._\@pb\/lg_sm {_@pb/lg: sm;
}

 ._\@pb\/xl_sm {_@pb/xl: sm;
}

 ._\@pb\/sm_base {_@pb/sm: base;
}

 ._\@pb\/md_base {_@pb/md: base;
}

 ._\@pb\/lg_base {_@pb/lg: base;
}

 ._\@pb\/xl_base {_@pb/xl: base;
}

 ._\@pb\/sm_lg {_@pb/sm: lg;
}

 ._\@pb\/md_lg {_@pb/md: lg;
}

 ._\@pb\/lg_lg {_@pb/lg: lg;
}

 ._\@pb\/xl_lg {_@pb/xl: lg;
}

 ._\@pb\/sm_xl {_@pb/sm: xl;
}

 ._\@pb\/md_xl {_@pb/md: xl;
}

 ._\@pb\/lg_xl {_@pb/lg: xl;
}

 ._\@pb\/xl_xl {_@pb/xl: xl;
}

 ._\@pb\/sm_2xl {_@pb/sm: 2xl;
}

 ._\@pb\/md_2xl {_@pb/md: 2xl;
}

 ._\@pb\/lg_2xl {_@pb/lg: 2xl;
}

 ._\@pb\/xl_2xl {_@pb/xl: 2xl;
}

 ._\@pb\/sm_3xl {_@pb/sm: 3xl;
}

 ._\@pb\/md_3xl {_@pb/md: 3xl;
}

 ._\@pb\/lg_3xl {_@pb/lg: 3xl;
}

 ._\@pb\/xl_3xl {_@pb/xl: 3xl;
}

 ._\@pb\/sm_4xl {_@pb/sm: 4xl;
}

 ._\@pb\/md_4xl {_@pb/md: 4xl;
}

 ._\@pb\/lg_4xl {_@pb/lg: 4xl;
}

 ._\@pb\/xl_4xl {_@pb/xl: 4xl;
}

 ._\@pb\/sm_5xl {_@pb/sm: 5xl;
}

 ._\@pb\/md_5xl {_@pb/md: 5xl;
}

 ._\@pb\/lg_5xl {_@pb/lg: 5xl;
}

 ._\@pb\/xl_5xl {_@pb/xl: 5xl;
}

 ._\@pb\/sm_6xl {_@pb/sm: 6xl;
}

 ._\@pb\/md_6xl {_@pb/md: 6xl;
}

 ._\@pb\/lg_6xl {_@pb/lg: 6xl;
}

 ._\@pb\/xl_6xl {_@pb/xl: 6xl;
}

 ._\@pb\/sm_7xl {_@pb/sm: 7xl;
}

 ._\@pb\/md_7xl {_@pb/md: 7xl;
}

 ._\@pb\/lg_7xl {_@pb/lg: 7xl;
}

 ._\@pb\/xl_7xl {_@pb/xl: 7xl;
}

 ._\@pb\/sm_8xl {_@pb/sm: 8xl;
}

 ._\@pb\/md_8xl {_@pb/md: 8xl;
}

 ._\@pb\/lg_8xl {_@pb/lg: 8xl;
}

 ._\@pb\/xl_8xl {_@pb/xl: 8xl;
}

 ._\@pb\/sm_thin {_@pb/sm: thin;
}

 ._\@pb\/md_thin {_@pb/md: thin;
}

 ._\@pb\/lg_thin {_@pb/lg: thin;
}

 ._\@pb\/xl_thin {_@pb/xl: thin;
}

 ._\@pb\/sm_extralight {_@pb/sm: extralight;
}

 ._\@pb\/md_extralight {_@pb/md: extralight;
}

 ._\@pb\/lg_extralight {_@pb/lg: extralight;
}

 ._\@pb\/xl_extralight {_@pb/xl: extralight;
}

 ._\@pb\/sm_light {_@pb/sm: light;
}

 ._\@pb\/md_light {_@pb/md: light;
}

 ._\@pb\/lg_light {_@pb/lg: light;
}

 ._\@pb\/xl_light {_@pb/xl: light;
}

 ._\@pb\/sm_normal {_@pb/sm: normal;
}

 ._\@pb\/md_normal {_@pb/md: normal;
}

 ._\@pb\/lg_normal {_@pb/lg: normal;
}

 ._\@pb\/xl_normal {_@pb/xl: normal;
}

 ._\@pb\/sm_medium {_@pb/sm: medium;
}

 ._\@pb\/md_medium {_@pb/md: medium;
}

 ._\@pb\/lg_medium {_@pb/lg: medium;
}

 ._\@pb\/xl_medium {_@pb/xl: medium;
}

 ._\@pb\/sm_semibold {_@pb/sm: semibold;
}

 ._\@pb\/md_semibold {_@pb/md: semibold;
}

 ._\@pb\/lg_semibold {_@pb/lg: semibold;
}

 ._\@pb\/xl_semibold {_@pb/xl: semibold;
}

 ._\@pb\/sm_bold {_@pb/sm: bold;
}

 ._\@pb\/md_bold {_@pb/md: bold;
}

 ._\@pb\/lg_bold {_@pb/lg: bold;
}

 ._\@pb\/xl_bold {_@pb/xl: bold;
}

 ._\@pb\/sm_extrabold {_@pb/sm: extrabold;
}

 ._\@pb\/md_extrabold {_@pb/md: extrabold;
}

 ._\@pb\/lg_extrabold {_@pb/lg: extrabold;
}

 ._\@pb\/xl_extrabold {_@pb/xl: extrabold;
}

 ._\@pb\/sm_black {_@pb/sm: black;
}

 ._\@pb\/md_black {_@pb/md: black;
}

 ._\@pb\/lg_black {_@pb/lg: black;
}

 ._\@pb\/xl_black {_@pb/xl: black;
}

Link to Reproduction

Steps to reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

JS Framework
No response
Panda CSS Version
0.46.0
Browser
No response
Operating System

[ ] macOS
[ ] Windows
[ ] Linux

Additional Information
No response

I just pushed a fix for this. We'll release an update shortly.
If the issue persists after upgrading, I'll re-open it.

authors: omeroy segunadebayo

repo: chakra-ui/panda


text:
260 image hotspots create image crop field and map it

…pot mapper

Q
A

Branch
master

Bug fix?
no

New feature?
yes

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed issues
chameleon-system/chameleon-system#260

License
MIT

Adding an image crop field for image hotspots in preparation for https://github.com/chameleon-system/chameleon-shop-theme-bundle/issues/16
ATTENTION: This PR requires the ImageCropBundle to be integrated in chameleon-base.

Thanks @fabianbarth-esono

authors: fabianbarth-esono umulmrum

repo: chameleon-system/chameleon-shop


text:
Make auto reloader work on Mac

The existing version relies on the /proc filesystem so it doesn't work on Mac. This adds a version that uses pkill.

Nice, thank you!

repo: channelcat/sanic


text:
Add check for nil annotation in amr results

Description
Meant to handle this error in pipeline_run.rb, method db_load_amr_counts:
irb(main):003:0> Sample.find(26995).pipeline_runs[0].db_load_amr_counts
Traceback (most recent call last):
        3: from (irb):3
        2: from app/models/pipeline_run.rb:552:in `db_load_amr_counts'
        1: from app/models/pipeline_run.rb:558:in `block in db_load_amr_counts'
NoMethodError (undefined method `split' for nil:NilClass)

It appears that there are sequences without annotations in the ARG Annot database. This pr handles that case.
Tests

Rpsec test to be added. Should add one for the whole function.

What was the test plan on this PR?

What was the test plan on this PR?

@cdebourcy I tested it manually in irb but I regretted merging this PR as soon as I did, because I realized that it fixes the problem but introduces another bug. You're right to bring up test plan, will make sure the fix for this fix is comprehensive

Ok, can you revert this commit?

authors: cdebourcy lvreynoso

repo: chanzuckerberg/idseq-web


text:
Add button color prop and new error style button

title: "type_of_change(scope_of_work): ticket title"
reviewers: "sds-eng, sds-design"
Summary
Structural Element (Base, Gene, DNA, Chromosome or Cell)
Shortcut ticket: sh-XXXX
Copy ticket descirption here
Checklist

[ ] Default Story in Storybook
[ ] LivePreview Story in Storybook
[ ] Test Story in Storybook
[ ] Tests written
[ ] Variables from defaultTheme.ts used wherever possible
[ ] If updating an existing component, depreciate flag has been used where necessary
[ ] Chromatic build verified by @sds-design

So, I'm having some concerns around this approach where we are trying to generalize the code around colors.  I'm running into some conflicts between the secondary and error styles that can't seem to be resolved.  Basically, to get the error button to display correctly, I need to add this CSS to the base button:
      background-color: ${color[400]};
      border: ${border[400]};
      color: white;

Those attributes weren't set before.  I believe we were basically relying on passing color to MUI, and allowing their defined primary and secondary to set those attributes.  But when I set those attributes, it breaks the secondary button (it basically turns it into the primary button).
The other thing that breaks the secondary button is that we have to pass through the color prop to MUI as well, because we were relying on styling from that.
Due to these issues, I don't think we can generalize the base button code to support the new error type, and I think it may be easier and clearer to just add error button blocks in the switch statement in src/core/Button/index.tsx.
However, that leads to some other issues, and we'd have to check specifically for color in addition to sdsType and sdsStyle, and make sure it's done in the right order so it doesn't fall through to the wrong part of the switch statement.  I'm thinking that we actually should just add error as an sdsType option, but the switch statement can create it with the needed style

Hey Jerry! Thanks so much for your detailed investigation and writeup 🙏 Updating the button to support more color variants is definitely way more work than expected 😭
I happened to find a thread talking about the same problem and their solution seems to work for us too!
I opened a new draft PR to test it out 🙆♂
PTAL thank you!

Thanks for taking a look and putting the other PR together!  I'll check it out!

Real PR: https://github.com/chanzuckerberg/sci-components/pull/113

repo: chanzuckerberg/sci-components


text:
refactor(button,chip,menuselect): Consolidate one-time warnings and remove deprecated code in docs

Summary

Consolidate deprecation warnings / and logic
Update storybook examples that use deprecated Button syntax
Shortcut ticket: sh-171875

From Vincent: https://github.com/chanzuckerberg/sci-components/issues/88
getSpacings() is dealt with but hasn't been released yet (oct 29th). We should find a way to only show warnings once on initial load and not every time a component with a warning is rendered
ideas:

add a warning ID and only show new IDs when rendering
have a Set of warnings and only print that set to the console on render

Checklist

[ ] Default Story in Storybook
[ ] LivePreview Story in Storybook
[ ] Test Story in Storybook
[ ] Tests written
[ ] Variables from defaultTheme.ts used wherever possible
[ ] If updating an existing component, depreciate flag has been used where necessary
[ ] Chromatic build verified by @chanzuckerberg/sds-design

@mmmmmmaya I made some substantive changes, because we expanded the scope of the story to include consolidating the deprecation warnings.
Do we have a pattern / requirement for testing code outside components?  I started working on tests for the new code in warnings.ts

I don't believe we have an existing convention for that, but I think it would be ok to include a test file in the same directory as the file you are testing. That's how we do it for components, and it feels good to me to stay consistent in that pattern with non-component cases as well. So, a warning.test.ts file in src/common.


text:
Refactor process.py for use in decomposed step function

Refactor proccess.py to split out individual tasks that can be orchestrated by the forthcoming decomposed step function.

Closing this story as the work was merged into ebezzi's branch and this story's PR was closed. The decomposed step function work will be published in a separate PR.

repo: chanzuckerberg/single-cell-data-portal


text:
fix: Correctly update revised_at when publishing Collection revision

This commit fixes a bug that allowed the revised_at column to sometimes
not be updated even when there were changes (revisions) to a
Collection's datasets.
Reviewers
Functional:
@ebezzi
Readability:
@metakuni
Changes

add
remove
modify

Definition of Done (from ticket)
QA steps (optional)
Known Issues

Previously, if the last dataset checked 1) was not new, and 2) did not have changes, then the Collection would not update its revised_at date.

Which story is this for? 🤔
P.S. Your branch is out-of-date, but I'm not pushing that button! 😆

authors: danieljhegeman metakuni


text:
添加文章，界面出现post嵌套

BUG现象：

文章里 有  这个，页面上就会出现文章之间相互嵌套的BUG，

是因为从博客园导出的文章，里面有html标签；more在标签里，就不能辨别，会出现文章嵌套BUG；不过我看有的hexo主题可以分辨

上面图片没显示出来，我现在还不清楚具体怎样的嵌套。

不过我刚去你博客看了是正常的啊，已经解决了？

嗯，算是迂回解决吧，我把more从md文章里的div或者code 标签里提出来，放到外面，就可以正常显示了。不过要是more功能的兼容性好点就好了，
下面是more出BUG时，在md文章中的情形：

直接再 .md文件里写<div>是有问题的吧。

理论上应该不推荐的，不过实际上也是可以的，具体效果 http://localhost:4000/2017/02/24/6522011/

解决了就好，你这本地链接我是没法看的。

嗯嗯，我刚才也发现了发的本地链接，现在改了；其实是原来在博客园里的文章，然后导出的，有标签，懒得改；

repo: chaooo/hexo-theme-BlueLake


text:
Move student program related files to mentorship folder

Closes https://github.com/chaoss/community/issues/320
Signed-off-by: Venu Vardhan Reddy Tekula venu@chaoss.community

Thanks @vchrombie

authors: germonprez vchrombie

repo: chaoss/community


text:
Release Candidate Link

I added a comment link to all of the release candidate detail pages.

issue links are from #187 and #188

repo: chaoss/wg-evolution


text:
🛑 Silky.Network - br-4 is down

In 6a515ca, Silky.Network - br-4 (https://gru-br-mirror.silky.network) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Silky.Network - br-4 is back up in 7931457 after 1 hour, 29 minutes.

repo: chaotic-aur/chaotic-uptimes


text:
🛑 Silky.Network - br-4 is down

In b7bbe3c, Silky.Network - br-4 (https://gru-br-mirror.silky.network) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Silky.Network - br-4 is back up in f7a1b04 after 1 hour, 12 minutes.


text:
Possible ways to hide node pages on Drupal side

If I create a content type on the Drupal side, it's content will have a node page generated by default like http://site/node/6221
I just need to retrieve data from this node. But when visitor visits this node page on Drupal, they will see an unstyled ugly page. Is there a way to hide these node pages? Thanks.

I’ve personally approached this by keeping the content locked down Drupal side with node_view_permissions , and only my Next specific configured user role has access to view the specific content types, which generally keeps my /node content unavailable to the public. Curious what others approaches might be.

@twfahey1 I think we could also tell Drupal site search engine to not index the node page & create a robots.txt to tell public search engines to not index the page. Effectively, the page is hidden from the public who do not have the URL. But this is just a good-will/soft approach.

@fnick851 Another option that we've been using is the Require Login module. You can use this to lock down all pages behind a login.
Note: If you're using this module, you will need to whitelist a few paths:
/jsonapi
/jsonapi/*
/oauth
/oauth/*
/next/preview-url
/router/*
/subrequests

repo: chapter-three/next-drupal


text:
Status code not set in response

In case of 404 status_code is not getting set in response. Im are using api_v2 branch.
chargify = Chargify2::Client.new(api_id: <masked>, api_password: <masked>,  base_uri: 'https://api.chargify.com/api/v2')
chargify.customers.read(1)
<Chargify2::Response:0x007f8c1d878ec0 @resource=#<Chargify2::Customer>, @meta=#<Hashie::Mash errors=[#<Hashie::Mash attribute=nil kind="not_found" message="The requested Customer could not be found.">]>, @status_code=nil, @errors=[#<Hashie::Mash attribute=nil kind="not_found" message="The requested Customer could not be found.">]>
When I tried to hit the api directly, i could see status_code being sent in the chargify api response. So guessing the issue to be in the gem.
curl -v -u  <api_id>:x -H Accept:application/json -H Content-Type:application/json https://mavenhive-ghuk.chargify.com/customers/1
* Hostname was NOT found in DNS cache
*   Trying 54.244.7.151...
* Connected to mavenhive-ghuk.chargify.com (54.244.7.151) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
* Server certificate: *.chargify.com
* Server certificate: COMODO RSA Organization Validation Secure Server CA
* Server certificate: COMODO RSA Certification Authority
* Server certificate: AddTrust External CA Root
* Server auth using Basic with user 'dvLih3EFHkpluaBrGP7A'
> GET /customers/1 HTTP/1.1
> Authorization: Basic ZHZMaWgzRUZIa3BsdWFCckdQN0E6eA==
> User-Agent: curl/7.37.1
> Host: mavenhive-ghuk.chargify.com
> Accept:application/json
> Content-Type:application/json
>
< HTTP/1.1 404 Not Found
< Cache-Control: no-cache, private
< Content-Type: application/json; charset=utf-8
< Date: Wed, 04 Mar 2015 11:27:09 GMT
< P3p: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
* Server nginx + Phusion Passenger is not blacklisted
< Server: nginx + Phusion Passenger
< Set-Cookie: _chargify_session=BAh7CEkiD3Nlc3Npb25faWQGOgZFVEkiJTRlMjNlMGVjZGYzOWRkZDAyYmVlZDViOGJmNGM2MzhjBjsAVEkiF3NlbGxlcl9jcmVkZW50aWFscwY7AEZJIgGAZTJlYjBjOTViOWRkZWY2NWYwYTNlZDk4NDYwYmNjN2FlYzFmNzJmNjgxNWRmOWYyMTI4MGJjODgzMmY2NzIyNTczMzlhMjA2NzI5YjU4Y2RiM2RlOWY3YjJhN2YwZTIwMDQ2NzE5YmY0YTM5M2IxYjVlMmY0MzY4MTE0YjU2YzAGOwBGSSIac2VsbGVyX2NyZWRlbnRpYWxzX2lkBjsARmkCsjw%3D--b0cc8c93ff92f3de8d3abf63671acb887fa8b82b; domain=.chargify.com; path=/; secure; HttpOnly
< Status: 404 Not Found
< X-Frame-Options: SAMEORIGIN
< X-Powered-By: Phusion Passenger
< X-Rack-Cache: miss
< X-Ratelimit-Limit: 1000000
< X-Ratelimit-Remaining: 999982
< X-Ratelimit-Reset: 1425513600
< X-Request-Id: f2ab412e-9ab7-464a-88df-695e555b852a
< X-Runtime: 0.029060
< X-Ua-Compatible: IE=Edge,chrome=1
< Content-Length: 1
< Connection: keep-alive
<
* Connection #0 to host mavenhive-ghuk.chargify.com left intact

Hello Chargify team,
I am @MonikaMahanthappa's colleague and I ran into same issue (nil @status_code resulting in response.successful? to be false even though the API call was successful). This time, it was the POST /allocations API of V2.
When I switched our code to hit API V1 Allocations endpoint, it started working.
I suspect something has changed recently in API V2 which is causing this bug in this gem. I will try to report to Chargify support and see what I can find.
Meanwhile, we have stopped using this gem and fallen back to our custom Chargify api client.

Thanks for the report @bhavinjavia. We will look into the issue further. If you find any more information please let us know.


text:
绘图

陈师兄您好，我想请教一下，论文里面神经网络的图是用什么软件绘制出来的呢？

您好，用的是 draw.io 这个在线绘图工具，也有桌面版。

多谢师兄的帮助，我的本次写作也会引用到师兄的两篇文章。以后我会持续关注您的工作。


text:
keys: properly support the alt modifier

Fixes  #427.
cc @muesli @meowgorithm

Also added a unit test.

Thank you, @knz!

authors: knz muesli

repo: charmbracelet/bubbletea


text:
Adding templates necessary to support kube-state-metrics

Part of the fix for https://bugs.launchpad.net/charmed-kubernetes-bundles/+bug/1850710
This provides scrape jobs for prometheus to scrape kube-state-metrics endpoints.
Tested by deploying to AWS with https://github.com/charmed-kubernetes/cdk-addons/pull/156 and verifying I could create graphs with kube-state-metrics data.

LGTM


text:
feat: draft ssh subcommand

Just added the ssh function in cli.py
Note: Need to test with a remote host, however, I need to set up a VM to test it out (wip)

It may be easier to test this with an OpenSSH docker image. But then you have to do at least two steps: one to upload the keys and one to test. Read their README carefully. It's up to you. Please document whatever route you choose.

This implementation looks reasonable; let me know when you can run tests.

For the Docker, you would need to generate the rsa key pair in order for the ssh wrapper to work

authors: Acesif charmoniumQ

repo: charmoniumQ/PROBE


text:
Time X axis week rendering wrong on bar charts, correct on line charts with same data

Expected behavior
I'd expect the bar on a bar chart to be in the same place as the dot on a line chart for the same dataset and axis config. In my example below, the bar chart has bars showing in the wrong month., for example, the below screenshot shows a March figure plotted in April.

Current behavior
They're not in the same place.
Reproducible sample
https://jsfiddle.net/fje5wrav/3/
Optional extra steps/info to reproduce
This should explain the issue I think, but please let me know if not.
Also, interestingly, I noticed that re-using the chart_options object in both charts makes them both wrong! See this block and try the other option.
var chart_options2 = Object.assign({}, chart_options);
// todo: Try commenting the line above and using the below instead, I give the wrong result too in that case!
//var chart_options2 = chart_options;

Possible solution
No response
Context
No response
chart.js version
v3.7.1
Browser name and version
Firefox (Dev edition v99) and Chrome
Link to your project
No response

In bar charts, the scale and grid are offset by default. Using same offset settings for both chart types gives same results:
https://jsfiddle.net/zb0rfgdq/1/

Thanks, I can confirm this did the trick in our live use-case too 👍

That didn't work in this example (Chart.js v4.4.3). Any suggestion?
  options: {
    scales: {
      x: {
        type: 'time',
        time: {
          unit: 'month'
        },
        offset: true,
        grid: {
           offset: false
        }
      },
      y: {
      	type: "linear",
        position: "left",
        beginAtZero: true
      }
    }
  }

JSFiddle code example

authors: filipecarneiro kurkle violuke


text:
[FEATURE]: Mixed chart types: Fix center of right y-axis to zero

Expected Behavior

I need to fix the center of the right y-axis to zero so it is easier to compare data when switching the pages.
Current Behavior

It changes the devision dynamically with the data.
On one page zero is on top, on one page its on bottom.
Context

compare data when switching the pages
Environment

Chart.js version: 2.5.0
Browser name and version: Firefox 45.9

@teery1 I think the best way to do this would be to set the range for each axis to be the same values that way the 0 will always be in the same place.

Thanks for the feedback.
It works, but it's no more dynamic.
If the chart extend the suggested min/max it's like it was before.
If not, the chart is very uncomfortable to read because the data for the right y-axis is very different for each page (low to high).

The only other option I can think of is to use the axis callbacks http://www.chartjs.org/docs/latest/axes/#callbacks look at the axis range and change it to be so that min = -max which should put 0 in the center

Closing since my answer above is the best solution to this


text:
Documentation: Example charts on CodePen

Hello chaps!
I think your library is awesome
One thing that I think will help people like me to use your library is creating CodePen examples of all your [Charts section[(https://www.chartjs.org/docs/latest/charts/), these pens could then be embedded into your documentation.
This would be helpful because it would allow users to see the full configuration for that chart.
For eg in your Radar chart example under 'Example usage' you have:
var myRadarChart = new Chart(ctx, {
    type: 'radar',
    data: data,
    options: options
});

But I don't know what the dataset should look like.
On your Scatter example you have the full configuration with dataset displayed:
var scatterChart = new Chart(ctx, {
    type: 'scatter',
    data: {
        datasets: [{
            label: 'Scatter Dataset',
            data: [{
                x: -10,
                y: 0
            }, {
                x: 0,
                y: 10
            }, {
                x: 10,
                y: 5
            }]
        }]
    },
    options: {
        scales: {
            xAxes: [{
                type: 'linear',
                position: 'bottom'
            }]
        }
    }
});

But there is no visual example here, so it is inconsistent.
Adding CodePen examples to all chart types will allow the user to see the full configuration for each chart and also keep this section of documentation consistent.
What do you think?
Edit
Just to say I am creating a kind of WYSIWYG and I am creating a UI editor to allow the user to build a chart configuration, so I am looking at looping round each dataset and I need to know if the data is a list of numbers (bar, line) or list of points (scatter) so I can handle it and show the correct edit form.

Please take a look at docs of the current development:
https://www.chartjs.org/docs/master/
Also take a look to the data structures page. Anything like you are suggesting?

Thanks for that, I hadn't seen your new doc.
Yes they do look better, the 'Data Structures' section is the kind of thing I was looking for.
Embedded CodePens would be simulair to the 'Live Edit' you have on some Chart Types, I guess the advantage with CodePen is you could create collections for Chart Types and Axis... But the updated docs satisfy me so you can close this issue if you like.

This would be a huge improvement for Chart.js users especially for new comers like me, coming from ECharts, the interactive examples there was incredibly helpful for trying out things and developing.

authors: LukeTOBrien kurkle wenfangdu


text:
IE 11 Compatibility

Has Internet Explorer 11 support been discontinued? There's lots of lambda functions in the beta version which isn't supported by IE 11..?
e.g. on line 19 in chartjs-plugin-annotation.esm.js:
hooks.forEach(hook => {
    if (typeof options[hook] === 'function') {
      state.listened = true;
      state.listeners[hook] = options[hook];
    }
});

@elitastic the plugin is based on CHARTJS v3 which dropped the compatibility on IE 11.
See https://github.com/chartjs/Chart.js/issues/8042

@elitastic the plugin is based on CHARTJS v3 which dropped the compatibility on IE 11.
See https://github.com/chartjs/Chart.js/issues/8042

Oh I somehow missed that, thanks for your quick reply!

Oh I somehow missed that, thanks for your quick reply!

authors: elitastic stockiNail

repo: chartjs/chartjs-plugin-annotation