text:
Terminal font rendering bug in Firefox and Chrome.

OS/Web Information

Web Browser: Firefox, Google Chrome, Microsoft Edge
Local OS: Linux, Windows 10
Remote OS: Amazon Linux 2
Remote Architecture: x86_64
code-server --version:  3.11.1 c680aae973d83583e4a73dc0c422f44021f0140e

Steps to Reproduce

open code-server tab in Firefox
open terminal
type _______

Expected
The underscore characters are visible.
Actual
The underscore characters are not visible, leaving what appears to be blank spaces.  In Chrome based browsers, adjusting the terminal's line spacing to 1.1 makes the underscores visible, but this does not work in Firefox.
Logs
Console stdout/stderr:
[2021-08-30T20:58:55.509Z] info    - Not serving HTTPS
[2021-08-30T21:02:15.733Z] debug forking vs code...
[2021-08-30T21:02:16.096Z] debug setting up vs code...
[2021-08-30T21:02:16.099Z] debug vscode got message from code-server {"type":"init"}
[2021-08-30T21:02:18.976Z] debug vscode got message from code-server {"type":"socket"}
[2021-08-30T21:02:18.979Z] debug protocol Initiating handshake... {"token":"aae87521-0bbb-4f11-9aac-5b37061ad123"}
[2021-08-30T21:02:19.040Z] debug protocol Handshake completed {"token":"aae87521-0bbb-4f11-9aac-5b37061ad123"}
[2021-08-30T21:02:19.041Z] debug management Connecting... {"token":"aae87521-0bbb-4f11-9aac-5b37061ad123"}
[2021-08-30T21:02:19.042Z] debug vscode 1 active management connection(s)
[2021-08-30T21:02:20.647Z] debug vscode got message from code-server {"type":"socket"}
[2021-08-30T21:02:20.647Z] debug protocol Initiating handshake... {"token":"1e6492e6-71b6-4fda-bf1e-5a1e11924ca3"}
[2021-08-30T21:02:20.884Z] debug got latest version {"latest":"3.11.1"}
[2021-08-30T21:02:20.884Z] debug comparing versions {"current":"3.11.1","latest":"3.11.1"}
[2021-08-30T21:02:20.919Z] debug protocol Handshake completed {"token":"1e6492e6-71b6-4fda-bf1e-5a1e11924ca3"}
[2021-08-30T21:02:20.920Z] debug exthost Connecting... {"token":"1e6492e6-71b6-4fda-bf1e-5a1e11924ca3"}
[2021-08-30T21:02:20.921Z] debug exthost Getting NLS configuration... {"token":"1e6492e6-71b6-4fda-bf1e-5a1e11924ca3"}
[2021-08-30T21:02:20.921Z] debug vscode 1 active exthost connection(s)
[2021-08-30T21:02:20.921Z] debug exthost Spawning extension host... {"token":"1e6492e6-71b6-4fda-bf1e-5a1e11924ca3"}
[2021-08-30T21:02:20.925Z] debug exthost Waiting for handshake... {"token":"1e6492e6-71b6-4fda-bf1e-5a1e11924ca3"}
[2021-08-30T21:02:21.328Z] debug exthost Handshake completed {"token":"1e6492e6-71b6-4fda-bf1e-5a1e11924ca3"}
[2021-08-30T21:02:21.328Z] debug exthost Sending socket {"token":"1e6492e6-71b6-4fda-bf1e-5a1e11924ca3"}
terminate called after throwing an instance of 'Napi::Error'
  what():  Inotify limit reached
IPC "File Watcher (nsfw)" crashed with exit code null and signal SIGABRT
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
terminate called after throwing an instance of 'Napi::Error'
  what():  Inotify limit reached
IPC "File Watcher (nsfw)" crashed with exit code null and signal SIGABRT
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
terminate called after throwing an instance of 'Napi::Error'
  what():  Inotify limit reached
IPC "File Watcher (nsfw)" crashed with exit code null and signal SIGABRT
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
terminate called after throwing an instance of 'Napi::Error'
  what():  Inotify limit reached
IPC "File Watcher (nsfw)" crashed with exit code null and signal SIGABRT
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
terminate called after throwing an instance of 'Napi::Error'
  what():  Inotify limit reached
IPC "File Watcher (nsfw)" crashed with exit code null and signal SIGABRT
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
terminate called after throwing an instance of 'Napi::Error'
  what():  Inotify limit reached
IPC "File Watcher (nsfw)" crashed with exit code null and signal SIGABRT
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
  ERR [File Watcher (nsfw)] terminated unexpectedly and is restarted again...
terminate called after throwing an instance of 'Napi::Error'
  what():  Inotify limit reached
IPC "File Watcher (nsfw)" crashed with exit code null and signal SIGABRT
  ERR [File Watcher (nsfw)] failed to start after retrying for some time, giving up. Please report this as a bug report!
  ERR [File Watcher (nsfw)] failed to start after retrying for some time, giving up. Please report this as a bug report!
^C[2021-08-30T21:02:59.332Z] debug child:72071 disposing {"code":"SIGINT"}

Screenshot

The "command not found" error was produced by typing several underscores and hitting enter.
Notes
This issue can be reproduced in VS Code: No

I can't reproduce this in Firefox + macOS. Are you using a custom font in your terminal by chance?
https://user-images.githubusercontent.com/3806031/131408401-dfb9fbd3-54b8-4cbe-b98f-5bd9ecaab881.mov

No, default options.  Please test on a non-retina display.

Underscore is not visible in firefox on 133% zoom:
https://user-images.githubusercontent.com/76137/131497615-2398d771-046a-41f2-9b5b-490c2404c239.mp4
Underscore is not visible in firefox when it's on the last row:
https://user-images.githubusercontent.com/76137/131498038-4310f522-29db-4476-aeea-ab901e724c8f.mp4

Underscore is not visible in firefox on 133% zoom:

I can't reproduce this unfortunately. Are you using a custom font?

I can reproduce it on latest linux mint and fedora. Changing the font to custom made underscore visible all the time and by visible I mean:

there's something wrong in how the underscore is rendered.

Got it!
"terminal.integrated.gpuAcceleration": "off"
fixes the issue:

authors: jsjoeio senyai tidux

repo: cdr/code-server


text:
EKS Upgrade to 1.30 in Staging

Summary | Résumé
New version of EKS - 1.30
Verified that there are no deprecations we need to worry about.
Release notes: https://kubernetes.io/blog/2024/04/17/kubernetes-v1-30-release/
Upgraded and working in dev.
Related Issues | Cartes liées
Chore
Test instructions | Instructions pour tester la modification
Smoke test/perf test staging
Release Instructions | Instructions pour le déploiement
None.
Reviewer checklist | Liste de vérification du réviseur

[ ] This PR does not break existing functionality.
[x] This PR does not violate GCNotify's privacy policies.
[x] This PR does not raise new security concerns. Refer to our GC Notify Risk Register document on our Google drive.
[x] This PR does not significantly alter performance.
[x] Additional required documentation resulting of these changes is covered (such as the README, setup instructions, a related ADR or the technical documentation).

⚠ If boxes cannot be checked off before merging the PR, they should be moved to the "Release Instructions" section with appropriate steps required to verify before release. For example, changes to celery code may require tests on staging to verify that performance has not been affected.

tbh, I'd say that we can't really check off all these, at least "This PR does not break existing functionality." should be checked before release 👍

source: gharchive/pull-request

repo: cds-snc/notification-terraform

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 tanecni-divadlo.cz is down

In 5c9156e, 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 d42fc34.

source: gharchive/issue

repo: cebreus/upptime


text:
🛑 tanecni-divadlo.cz is down

In f02f99e, 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 9de881a.


text:
🛑 Bali 2017 is down

In d1eac63, Bali 2017 ($SITE_BALI) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bali 2017 is back up in 39fc0b5.


text:
🛑 tanecni-divadlo.cz is down

In 3bf2e0c, 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 3a4f32d.


text:
🛑 tanecni-divadlo.cz is down

In 3e532f5, 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 d1c3833.


text:
🛑 tanecni-divadlo.cz is down

In 40a39b6, 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 7775498.


text:
🛑 tanecni-divadlo.cz is down

In 564fc72, 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 9fe0b08.


text:
🛑 CDN is down

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

HTTP code: 522
Response time: 15582 ms

Resolved: CDN is back up in 9863df2.

repo: ceccun/status


text:
🛑 CDN is down

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

HTTP code: 522
Response time: 15433 ms

Resolved: CDN is back up in 85afe92.


text:
🛑 CDN is down

In e7ae9eb, CDN (https://cdn.ceccun.com) was down:

HTTP code: 403
Response time: 518 ms

Resolved: CDN is back up in 0280423.


text:
🛑 CDN is down

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

HTTP code: 522
Response time: 15367 ms

Resolved: CDN is back up in df74161.


text:
🛑 CDN is down

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

HTTP code: 522
Response time: 15296 ms

Resolved: CDN is back up in b14fb76.


text:
🛑 CDN is down

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

HTTP code: 525
Response time: 275 ms

Resolved: CDN is back up in df6eca1.


text:
🛑 CDN is down

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

HTTP code: 525
Response time: 244 ms

Resolved: CDN is back up in 12b435c after 792 days, 15 hours, 19 minutes.


text:
chore(main): release 0.37.1

:robot: I have created a release beep boop
0.37.1 (2024-07-24)
Bug Fixes

bump guzzlehttp/guzzle from 7.9.1 to 7.9.2 (#639) (61de914)
bump laravel/framework from 11.16.0 to 11.17.0 (#640) (2c7a8c4)
bump league/commonmark from 2.5.0 to 2.5.1 (#638) (549978c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

0.37.1
:sunflower:

repo: cedricziel/faro-shop


text:
Startup time is high

numbat-collector is one of the larger chunks of the startup time of my module.
It clocks in at 800ms to require on my machine.

It's a dep of newww, and I was mechanically going through deps with require-time to see what's slow. It's got a 3+ second startup time.

Though looking deeper, it looks like it depends on it but never uses it.

repo: ceejbot/numbat-collector

license: isc

license_source: bigquery


text:
Decide on governance

Summary
Currently, we stripped the gov module entirely from celestia-app. We should decide on the gov mechanism if any.
Problem Definition
There is no way to vote on (parameter) changes currently.
Proposal
@musalbas proposed to only have signalling text governance proposals on chain.
The upgrade path must be clearly defined for various scenarios and what role governance should play in this if any.
E.g. should coin holders vote on a block size increase? On upgrading to a new software release? On other params? Only on non-binding signalling text proposals?
Action Items

[ ] Decide on if we want any governance in the sense of "coin-voting" at all
[ ] Decide on what kind of proposals governance can vote
[ ] Summarize findings and decision in a brief ADR
[ ] then: implement changes in app
[ ] add a more fine-grained document about various upgrade-paths including what can be voted on but also beyond what is covered by governance

Related:

https://www.figment.io/resources/cosmos-parameter-change-documentation, https://github.com/gavinly/CosmosParametersWiki/blob/master/param_index.md
https://github.com/celestiaorg/celestia-specs/issues/128
https://github.com/celestiaorg/celestia-specs/issues/171
some SDK discussions and issues to keep an eye on:

https://github.com/cosmos/cosmos-sdk/discussions/9066
https://github.com/cosmos/cosmos-sdk/discussions/9913
https://linktr.ee/cosmos_gov

code that (currently) handles text proposals: https://github.com/cosmos/cosmos-sdk/blob/5725659684fc93790a63981c653feee33ecf3225/x/gov/types/proposal.go#L249-L253, code that (currently) handles param changes: https://github.com/cosmos/cosmos-sdk/blob/58a6c4c00771e766f37f0f8e50adbbfe0bc7362d/x/params/proposal_handler.go#L26

The decision for now:

we will add back the full governance module for the next testnet
if we want to limit anything we should figure this out between testnet and mainnet

IMHO, we should simply use the full governance module at launch. If we ever want to move away from signalling/coin-voting, there either needs to be a governance proposal to do that, or, a coordinated hard-fork. cc @musalbas @adlerjohn

Sounds good

authors: adlerjohn liamsi

repo: celestiaorg/celestia-app


text:
Orchestrator and relayer client

Description
This PR is the first of three PRs to add the MVP orchestrator and relayer. It contains the various rpc clients used by both the relayer and orchestrator to communicate with celestia-app, celestia-core, and ethereum.
part 1/3 of the orchestrator/relayer MVP

Codecov Report

:exclamation: No coverage uploaded for pull request base (qgb-integration@6d78b9b). Click here to learn what that means.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##             qgb-integration     #255   +/-   ##
==================================================
  Coverage                   ?   14.77%
==================================================
  Files                      ?       42
  Lines                      ?     8576
  Branches                   ?        0
==================================================
  Hits                       ?     1267
  Misses                     ?     7223
  Partials                   ?       86

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 6d78b9b...8a63b4e. Read the comment docs.

there's still a lot of unused code that will get used later, so the linter is failing

authors: codecov-commenter evan-forbes


text:
fix: specs for MaxDepositPeriod and VotingPeriod

Closes https://github.com/celestiaorg/celestia-app/issues/2624

Codecov Report

Merging #2626 (caa5c07) into main (44be82a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2626   +/-   ##
=======================================
  Coverage   20.63%   20.63%
=======================================
  Files         133      133
  Lines       15346    15346
=======================================
  Hits         3166     3166
  Misses      11877    11877
  Partials      303      303

authors: codecov-commenter rootulp


text:
Cut a v0.1.0 Release

Since we have reached a state where we can send transactions, deploy contracts, and call contracts using Optimint as a backend we should create a v0.1.0 release.
Depends on

[x] https://github.com/celestiaorg/ethermint/issues/3
[x] https://github.com/celestiaorg/optimint/issues/310
[x] https://github.com/celestiaorg/optimint/issues/323
[x] https://github.com/celestiaorg/evmos/pull/32

All pre tasks are done. A release can be cut.

repo: celestiaorg/evmos


text:
WIP: Feat/bootstrap from previously seen peers

Overview
This PR contains the imlpementation of ADR-14
Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #35 (cc4d2b0) into main (4a93da2) will decrease coverage by 0.04%.
The diff coverage is 76.00%.

@@            Coverage Diff             @@
##             main      #35      +/-   ##
==========================================
- Coverage   66.22%   66.18%   -0.04%
==========================================
  Files          35       36       +1
  Lines        2768     2827      +59
==========================================
+ Hits         1833     1871      +38
- Misses        785      801      +16
- Partials      150      155       +5

Impacted Files
Coverage Δ

p2p/options.go
44.44% <50.00%> (+0.78%)
:arrow_up:

p2p/exchange.go
78.86% <69.69%> (-2.39%)
:arrow_down:

p2p/peer_tracker.go
77.39% <86.36%> (+1.20%)
:arrow_up:

p2p/peerstore/peerstore.go
100.00% <100.00%> (ø)

sync/sync_head.go
62.03% <100.00%> (ø)

... and 1 file with indirect coverage changes

Closed in favor of:

https://github.com/celestiaorg/go-header/pull/36
Incoming

authors: codecov-commenter derrandz

repo: celestiaorg/go-header


text:
panic: op-batcher flag redefined: namespace-id

When running on latest commit (c0bd1b58912d183d0d708d56bd3d5ca271cb132e) of celestia branch on this repo, I encounter this error:
op-batcher flag redefined: namespace-id
panic: op-batcher flag redefined: namespace-id

goroutine 1 [running]:
flag.(*FlagSet).Var(0xc0001aa300, {0x13077a0, 0xc000198db0}, {0xff7cd1, 0xc}, {0x100a033, 0x1c})
        /usr/local/go/src/flag/flag.go:980 +0x2f9
flag.(*FlagSet).StringVar(...)
        /usr/local/go/src/flag/flag.go:845
flag.(*FlagSet).String(0x10000005828b3?, {0xff7cd1, 0xc}, {0xc00003e1f8, 0x10}, {0x100a033, 0x1c})
        /usr/local/go/src/flag/flag.go:858 +0xac
github.com/urfave/cli.StringFlag.ApplyWithError.func1({0xff7cd1?, 0xc?})
        /go/pkg/mod/github.com/urfave/cli@v1.22.9/flag_string.go:67 +0x94
github.com/urfave/cli.eachName({0xff7cd1?, 0x0?}, 0xc0000ad750)
        /go/pkg/mod/github.com/urfave/cli@v1.22.9/flag.go:130 +0x93
github.com/urfave/cli.StringFlag.ApplyWithError({{0xff7cd1, 0xc}, {0x100a033, 0x1c}, {0xc000473050, 0x17}, {0x0, 0x0}, 0x0, 0x0, ...}, ...)
        /go/pkg/mod/github.com/urfave/cli@v1.22.9/flag_string.go:62 +0xe9
github.com/urfave/cli.flagSet({0xff5a50, 0xa}, {0xc000232b00, 0x2d, 0x7efef5dd5c80?})
        /go/pkg/mod/github.com/urfave/cli@v1.22.9/flag.go:115 +0x170
github.com/urfave/cli.(*App).newFlagSet(...)
        /go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:185
github.com/urfave/cli.(*App).Run(0xc00054d340, {0xc0001981e0, 0x1, 0x1})
        /go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:205 +0xea
main.main()
        /app/op-batcher/cmd/main.go:39 +0x334

Resolved in https://github.com/celestiaorg/optimism/commit/34352c423a6c95b3e04115e91c5c690259283a73

repo: celestiaorg/optimism


text:
Setting up dev environment

I'm trying to get this app setup properly for a project I'm working on.
I've cloned the repo, run npm i (though it appears Lerna is the only dependency), then npm run build. I get a bunch of errors, most related to missing modules. Fixing one only brings another one up, so I figured the fastest way to fix that would be to ask here what the proper setup steps are to get Celluloid working.
What packages am I missing / what steps should I take?
Thanks!

Why was this closed @3rwww1 ? I'd appreciate help on what dependencies are required for the project to run in development

Hi Eric,
Erwan, our IT developer, is about to answer you :-) We've talked about that
just this morning.
All the best,
Michaël
Le lun. 27 août 2018 à 14:54, Eric Han Liu notifications@github.com a
écrit :

Why was this closed @3rwww1 https://github.com/3rwww1 ? I'd appreciate
help on what dependencies are required for the project to run in development
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/celluloid-edu/celluloid/issues/39#issuecomment-416216850,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhumWdnvyt-W5r6mqbdoJ3B2tGppzsnYks5uU-wdgaJpZM4WGT9G
.

--
Le cinéma Utopia... Une histoire de militantisme culturel et politique en
vente ici
https://warm-ed.fr/fr/cinema/33-le-cinema-utopia-a-avignon-de-1976-a-1994-de-michael-bourgatte-97829556759.html
Michaël Bourgatte
Maître de Conférences à l'Institut Supérieur de Pédagogie
http://www.icp.fr/a-propos-de-l-icp/decouvrez-l-icp/facultes-et-instituts/isp-faculte-d-education-1600.kjsp
Directeur du département Humanités Numériques et Innovations Educatives
Responsable de l'Atelier du Numérique
http://www.icp.fr/a-propos-de-l-icp/decouvrez-l-icp/campus-numerique/atelier-du-numerique-26791.kjsp
Institut Catholique de Paris
 |
Bureau E-63 | 74, Rue de Vaugirard 75270 Paris Cedex 06
✆
+
33 (0)1.70.64.29.92 |

+33
(0)
6.87.23.66.8
7
Twitter :
@michaelbourgatt https://twitter.com/michaelbourgatt
Blog : http://celluloid.hypotheses.org/
http://celluloid.hypotheses.org/

Hi @EricHanLiu !
Sorry for closing the issue, I was doing a bit of "housekeeping" on this repository, and for some reason I didn't see this new issue, nor was I notified by mail when you opened it, nor did I check I wasn't the author when closing it.
I'm in the process of writing an extensive README for the project, but in the meantime, here is an excerpt
Prerequisites

using an OSX or Linux operating system is highly recommended. With a bit of tweaking, windows will work too, albeit you'll have to do to a bit more searching on how to install and configure the following tools.
download Yarn and use it instead of NPM. The project is organized as a monorepo so it needs yarn to leverage Yarn workspace
install a local postgresql server, version 9.6 or later, for your environment, optionally using a docker image. Then, create a user for celluloid and then create a database owned by this user. You can follow this tutorial to get setup quickly.
finally, you'll need an SMTP server to send emails for account confirmation. For development purpose, you could use your email account SMTP credentials, for instance gmail, or a dedicated service, such as mailtrap

Configuration

create a .env file at the root of your repository, with the following contents:

  1 NODE_ENV=development
  2 CELLULOID_LISTEN_PORT=3001
  3 CELLULOID_PG_HOST=celluloid-db-postgres.cticqmujyhft.eu-west-1.rds.amazonaws.com
  4 CELLULOID_PG_PORT=5432
  5 CELLULOID_PG_DATABASE=celluloid
  6 CELLULOID_PG_USER=celluloid
  7 CELLULOID_PG_PASSWORD=8H#Cjvp!ZmY#!h6p
  8 CELLULOID_PG_MAX_POOL_SIZE=20
  9 CELLULOID_PG_IDLE_TIMEOUT=30000
 10 CELLULOID_JWT_SECRET="bhN63!4A^CAnn@xe53s7d8uD1jCXbMXPtU6H*a0*YZ%Z1#2!C95hgJv7i#53NU1d"
 11 CELLULOID_SMTP_USER=AKIAILSQA6FHHYZ24IMA
 12 CELLULOID_SMTP_PASSWORD='AjCjLRwqAMudLq62oKksUin6kscuHnP5bE+ieE/ssf3b'
 13 CELLULOID_SMTP_HOST=email-smtp.eu-west-1.amazonaws.com
 14 COOL_INFRA_PATH=../cool/infra/celluloid```

## Installation
- setup a local database with postgresql and restore

authors: 3rwww1 EricHanLiu michaelbourgatt

repo: celluloid-edu/celluloid


text:
LoadError: cannot load such file -- win32ole on OSX - celluloid-essentials-0.20.1

@digitalextremist Thanks for the hard work !
However I get a new error now.
You asked me which operating system and RVM I am using:
rvm 1.26.11
OSX Yosemite

Here is the error :
namespace should be set in your ruby initializer, is ignored in config file
config.redis = { :url => ..., :namespace => 'namespace_dev' }
D, [2015-07-20T12:17:14.819053 #84626] DEBUG -- : Celluloid 0.17.0 is running in BACKPORTED mode. [ http://git.io/vJf3J ]
2015-07-20T10:17:15.564Z 84626 TID-ovftx0h60 INFO: [Sidetiq] Sidetiq v0.6.3 - Copyright (c) 2012-2013, Tobias Svensson <tob@tobiassvensson.co.uk>
2015-07-20T10:17:15.564Z 84626 TID-ovftx0h60 INFO: [Sidetiq] Sidetiq is covered by the 3-clause BSD license.
2015-07-20T10:17:15.564Z 84626 TID-ovftx0h60 INFO: [Sidetiq] See LICENSE and http://opensource.org/licenses/BSD-3-Clause for licensing details.
2015-07-20T10:17:15.564Z 84626 TID-ovftx0h60 INFO: [Sidetiq] Sidetiq::Supervisor start
2015-07-20T10:17:15.565Z 84626 TID-ovfu2yi9c INFO: [Sidetiq] Sidetiq::Actor::Clock id: 70170397578020 initialize
2015-07-20T10:17:15.565Z 84626 TID-ovfu2yi9c DEBUG: [Sidetiq] Sidetiq::Clock looping ...
2015-07-20T10:17:15.568Z 84626 TID-ovfu2vc6o ERROR: Actor crashed!
LoadError: cannot load such file -- win32ole
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:43:in `require'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:43:in `from_win32ole'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:12:in `count_cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:6:in `cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid.rb:96:in `cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-pool-0.20.0/lib/celluloid/supervision/container/pool.rb:22:in `initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `public_send'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:16:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:50:in `block in dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:76:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:363:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task.rb:57:in `block in initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task/fibered.rb:14:in `block in create'
2015-07-20T10:17:15.568Z 84626 TID-ovfu309eo ERROR: Actor crashed!
LoadError: cannot load such file -- win32ole
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:43:in `require'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:43:in `from_win32ole'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:12:in `count_cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:6:in `cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid.rb:96:in `cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-pool-0.20.0/lib/celluloid/supervision/container/pool.rb:22:in `initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `public_send'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:16:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:50:in `block in dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:76:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:363:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task.rb:57:in `block in initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task/fibered.rb:14:in `block in create'
	(celluloid):0:in `remote procedure call'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:45:in `value'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/proxy/sync.rb:40:in `method_missing'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/proxy/cell.rb:20:in `_send_'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid.rb:204:in `new_link'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container/instance.rb:34:in `start'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container/instance.rb:29:in `initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container.rb:73:in `new'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container.rb:73:in `add'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/deprecate/supervise.rb:96:in `supervise'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-pool-0.20.0/lib/celluloid/supervision/container/behavior/pool.rb:29:in `pool'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `public_send'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:16:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:50:in `block in dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:76:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:363:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task.rb:57:in `block in initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task/fibered.rb:14:in `block in create'
2015-07-20T10:17:15.569Z 84626 TID-ovfu2vc6o ERROR: thread crashed
LoadError: cannot load such file -- win32ole
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:43:in `require'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:43:in `from_win32ole'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:12:in `count_cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:6:in `cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid.rb:96:in `cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-pool-0.20.0/lib/celluloid/supervision/container/pool.rb:22:in `initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `public_send'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:16:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:50:in `block in dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:76:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:363:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task.rb:57:in `block in initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task/fibered.rb:14:in `block in create'
	(celluloid):0:in `remote procedure call'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:45:in `value'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/proxy/sync.rb:40:in `method_missing'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/proxy/cell.rb:20:in `_send_'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid.rb:204:in `new_link'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container/instance.rb:34:in `start'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container/instance.rb:29:in `initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container.rb:73:in `new'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container.rb:73:in `add'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/deprecate/supervise.rb:96:in `supervise'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-pool-0.20.0/lib/celluloid/supervision/container/behavior/pool.rb:29:in `pool'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `public_send'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:16:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:50:in `block in dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:76:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:363:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task.rb:57:in `block in initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task/fibered.rb:14:in `block in create'
2015-07-20T10:17:15.570Z 84626 TID-ovfu2yi9c INFO: [Sidetiq] Sidetiq::Actor::Clock id: 70170397578020 shutting down ...
2015-07-20T10:17:15.571Z 84626 TID-ovfu309eo WARN: Terminating task: type=:call, meta={:dangerous_suspend=>true, :method_name=>:initialize}, status=:callwait
	Celluloid::Task::Fibered backtrace unavailable. Please try `Celluloid.task_class = Celluloid::Task::Threaded` if you need backtraces here.
2015-07-20T10:17:15.571Z 84626 TID-ovfu309eo ERROR: thread crashed
LoadError: cannot load such file -- win32ole
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:43:in `require'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:43:in `from_win32ole'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celltask was terminateduloid/internals/cpu_counter.rb:12:in `count_cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/cpu_counter.rb:6:in `cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid.rb:96:in `cores'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-pool-0.20.0/lib/celluloid/supervision/container/pool.rb:22:in `initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task/fibered.rb:35:in `terminate'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:347:in `block in cleanup'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:345:in `each'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:345:in `cleanup'
/Users/mickael/.rv.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `public_send'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:16:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:50:in `block in dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/cellum/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:331:in `shutdown'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:323:in `handle_crash'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:171:in `rescue in run'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:150:in `run'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/loid-0.17.0/lib/celluloid/cell.rb:76:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:363:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task.rb:57:in `block in initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task/fibered.rb:14:in `block in create'
	(celluloid):0:in `remote procedure call'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:45:in `value'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/proxy/sync.rb:40:in `method_missing'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/proxy/cell.rb:20:in `_send_'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid.rb:204:in `new_link'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container/instance.rb:34:in `start'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container/instance.rb:29:in `initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/container.rb:73:in `new'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:132:in `block in start'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-essentials-0.20.1/lib/celluloid/internals/thread_handle.rb:14:in `block in initialize'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor_system.rb:76:in `block in get_thread'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/group/spawner.rb:54:in `call'/lib/celluloid/supervision/container.rb:73:in `add'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/deprecate/supervise.rb:96:in `supervise'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-pool-0.20.0/lib/celluloid/supervision/container/behavior/pool.rb:29:in `pool'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `public_send'
	/Users/mickael/.rvm/rub
/Useries/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/calls.rb:28:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:16:in `dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:50:in `block in dispatch'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/cell.rb:76:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/actor.rb:363:in `block in task'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task.rb:57:in `block in initialize'
	/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/task/fibered.rb:14:in `block in create'
s/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/group/spawner.rb:54:in `block in instantiate'
(celluloid):0:in `remote procedure call'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/call/sync.rb:45:in `value'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/proxy/sync.rb:40:in `method_missing'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid/proxy/cell.rb:20:in `_send_'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-0.17.0/lib/celluloid.rb:193:in `new'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/celluloid-supervision-0.20.0/lib/celluloid/supervision/deprecate/supervise.rb:61:in `run!'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/sidetiq-0.6.3/lib/sidetiq/supervisor.rb:33:in `run!'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/sidetiq-0.6.3/lib/sidetiq.rb:65:in `<top (required)>'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/bundler-1.7.12/lib/bundler/runtime.rb:76:in `require'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/bundler-1.7.12/lib/bundler/runtime.rb:76:in `block (2 levels) in require'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/bundler-1.7.12/lib/bundler/runtime.rb:72:in `each'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/bundler-1.7.12/lib/bundler/runtime.rb:72:in `block in require'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/bundler-1.7.12/lib/bundler/runtime.rb:61:in `each'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/bundler-1.7.12/lib/bundler/runtime.rb:61:in `require'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/bundler-1.7.12/lib/bundler.rb:134:in `require'
/Users/mickael/Documents/folder/projectname/config/application.rb:7:in `<top (required)>'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/sidekiq-3.3.4/lib/sidekiq/cli.rb:236:in `require'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/sidekiq-3.3.4/lib/sidekiq/cli.rb:236:in `boot_system'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/sidekiq-3.3.4/lib/sidekiq/cli.rb:50:in `run'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/gems/sidekiq-3.3.4/bin/sidekiq:8:in `<top (required)>'
/Users/mickael/.rvm/gems/ruby-2.1.5/bin/sidekiq:23:in `load'
/Users/mickael/.rvm/gems/ruby-2.1.5/bin/sidekiq:23:in `<main>'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/bin/ruby_executable_hooks:15:in `eval'
/Users/mickael/.rvm/rubies/ruby-2.1.5/lib/ruby/gems/2.1.0/bin/ruby_executable_hooks:15:in `<main>'
2015-07-20T10:17:15.573Z 84626 TID-ovftx0h60 DEBUG: Terminating 5 actors...

referencing https://github.com/celluloid/celluloid/issues/650 for follow up.

@Micka33 we can keep this in the celluloid-essentials gem. I've posted a patch there.

Ignore previous commit message.

repo: celluloid/celluloid

license: mit


text:
[cli] Prevent releasegold:withdraw if a ReleaseGold contract has a cEUR balance

Expected Behavior
We currently check to see if a RG contract would self-destruct and take a cUSD balance with it.  We should add a similar check for cEUR.
Current Behavior
Someone can send cEUR to a RG contract, then withdraw all remaining CELO, and lose the cEUR.

@gastonponti is this still being worked on or complete?
If not started, I don't think we need to do this now. There's an open question around there being no way to get cEUR or any other token back from the RG contract now. Which means users would be blocked on withdrawing their CELO with this change

Yes, I've asked that in the cap channel
I didn't create the PR until having a clearer answer.
Are just a few changes, I could add a branch to this issue with something like "to be merged when this was fixed"

authors: aslawson gastonponti timmoreton

repo: celo-org/celo-monorepo


text:
wrong metric for ServerResponseCountByStatusCode view

https://github.com/census-instrumentation/opencensus-go/blob/6ddd4bcc9c808594ec82377ce4323c3f7913be6d/plugin/ochttp/stats.go#L263-L269
The ServerLatency metric seems wrong, since there's no ServerResponseCount metric defined nor used. Given that I guess the view was meant to be ServerRequestCountByStatusCode.
Since server latency by status code feels like not that useful view, I was wondering whether ServerResponseCountByStatusCode should be replaced by ServerRequestCountByStatusCode:
	ServerRequestCountByStatusCode = &view.View{
		Name:        "opencensus.io/http/server/request_count_by_status_code",
		Description: "Server request count by status code",
		TagKeys:     []tag.Key{StatusCode},
		Measure:     ServerRequestCount,
		Aggregation: view.Count(),
	}

Looks like the same issue as #995...

authors: bvwells rjeczalik

repo: census-instrumentation/opencensus-go


text:
Exporter/Metrics/OcAgent: Add integration test.

Metrics counterpart of https://github.com/census-instrumentation/opencensus-java/pull/1776.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b552db4). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1786   +/-   ##
=========================================
  Coverage          ?   83.89%
  Complexity        ?     2020
=========================================
  Files             ?      291
  Lines             ?     9219
  Branches          ?      890
=========================================
  Hits              ?     7734
  Misses            ?     1171
  Partials          ?      314

Impacted Files
Coverage Δ
Complexity Δ

...porter/metrics/ocagent/OcAgentMetricsExporter.java
69.04% <ø> (ø)
4 <0> (?)

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 b552db4...cd82544. Read the comment docs.

one nit. LGTM otherwise.

authors: codecov-io rghetia songy23

repo: census-instrumentation/opencensus-java


text:
Package the classes that need to be loaded by the bootstrap classes i…

…n a separate JAR file, bootstrap.jar, and bundle that with the agent's JAR file.

Codecov Report

Merging #400 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #400      +/-   ##
============================================
+ Coverage     90.56%   90.61%   +0.04%
  Complexity      595      595
============================================
  Files           100      100
  Lines          2078     2078
  Branches        208      208
============================================
+ Hits           1882     1883       +1
  Misses          142      142
+ Partials         54       53       -1

Impacted Files
Coverage Δ
Complexity Δ

...a/io/opencensus/trace/export/SpanExporterImpl.java
91.66% <0%> (+1.66%)
6% <0%> (ø)
:arrow_down:

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 286ab5a...f69cfce. Read the comment docs.


text:
jewel: remove rbd check

The value of doing this is fairly low compare to the added value.
So we remove these tasks, if rbd pool on Jewel doesn't have the right PG
value you can always increase it.
Signed-off-by: Sébastien Han seb@redhat.com

jenkins test luminous-ansible2.3-centos7_cluster

repo: ceph/ceph-ansible


text:
rbd: have dummy attacher implementation

previously, it was a requirement to have attacher sidecar for CSI
drivers and there had an implementation of dummy mode of operation.
However skipAttach implementation has been stabilized and the dummy
mode of operation is going to be removed from the external-attacher.
Considering this driver  work on volumeattachment objects for NBD driver
use cases, we have to implement dummy controllerpublish and unpublish
and thus keep supporting our operations even in absence of dummy mode
of operation in the sidecar.

This commit make a NOOP controller publish and unpublish for RBD driver.

CephFS driver does not require attacher and it has already been made free
from the attachment operations.

Ref# https://github.com/ceph/ceph-csi/pull/3149
Ref# https://github.com/kubernetes-csi/external-attacher/issues/226

Signed-off-by: Humble Chirammal hchiramm@redhat.com

Why?

/retest all

/retest all

Please don't do this for PRs that are not completely ready, or do not require exhaustive testing yet. The CI environment is rather busy already, re-testing like this just prevents other PRs from getting merged sooner.

/retest ci/centos/mini-e2e/k8s-1.22

/retest ci/centos/k8s-e2e-external-storage/1.23

/retest ci/centos/mini-e2e-helm/k8s-1.22

@nixpanic added the details to the commit and PR. Also tests are passing ! ptal.. thanks..

all the test failures are on ```Errors during downloading metadata for repository 'tcmu-runner':

Status code: 404 for https://3.chacra.ceph.com/r/tcmu-runner/master/245914c1446dddf07d5b58b0a7b2060b50fde4d7/centos/8/flavors/default/x86_64/repodata/repomd.xml (IP: 158.69.93.173)

Error: Failed to download metadata for repo 'tcmu-runner': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Error: error building at STEP "RUN dnf -y install 	librados-devel librbd-devel 	/usr/bin/cc 	make 	git 	&& dnf clean all 	&& rm -rf /var/cache/yum     && true": error while running runtime: exit status 1
make: *** [Makefile:233: image-cephcsi] Error 1
script returned exit code 2```

@Mergifyio rebase

@nixpanic comments are addressed.. ptal.. thanks

/retest ci/centos/k8s-e2e-external-storage/1.22

/retest ci/centos/mini-e2e/k8s-1.23

/retest ci/centos/k8s-e2e-external-storage/1.22

@nixpanic can you revisit as I have addressed the changes requested here ?

Is there a reason to keep ControllerPublishVolume in internal/csi-common/controllerserver-default.go? Or does it make sense to move this dummy implementation there instead?
If ControllerPublishVolume is only needed for NBD support, it should probably be reported as a feature only for NBD backed volumes. But, I guess the controller does not report the capabilities depending on the parameters for the volume?

Is there a reason to keep ControllerPublishVolume in internal/csi-common/controllerserver-default.go? Or does it make sense to move this dummy implementation there instead?

in this case, it default to not implemented ( inherited for cephfs) and only get an implementation in case of RBD.

If ControllerPublishVolume is only needed for NBD support, it should probably be reported as a feature only for NBD backed volumes. But, I guess the controller does not report the capabilities depending on the parameters for the volume?

Yeah, this return fall into get caps call for the controller..

@nixpanic I have answered the queries.. ptal. thanks.

@nixpanic ptal

@nixpanic ptal. Thanks

@humblec is this a preparation for removing the registry.k8s.io/sig-storage/csi-attacher sidecar from RBD provisioner in the future?

@humblec is this a preparation for removing the registry.k8s.io/sig-storage/csi-attacher sidecar from RBD provisioner in the future?

This is not related to that @pkalever

@Mergifyio refresh

@Mergifyio rebase

@humblec is this a preparation for removing the registry.k8s.io/sig-storage/csi-attacher sidecar from RBD provisioner in the future?

This is not related to that @pkalever

Then I'm confused.

previously, it was a requirement to have attacher sidecar for CSI
drivers and there had an implementation of dummy mode of operation.

Well even now we have the csi-attacher sidecar, right?
Don't know what I'm missing here, could you please help me understand?

authors: humblec nixpanic pkalever

repo: ceph/ceph-csi


text:
playbooks: add cephadm-distribute-ssh-key.yml

This playbooks helps to distribute an SSH public key to hosts.
Signed-off-by: Guillaume Abrioux gabrioux@redhat.com

jenkins test unittests

repo: ceph/cephadm-ansible


text:
Allow specifying a mode for templates

Currently, there's no clean way inside of cerner_tomcat to specify the mode that a file from a template should be created with, forcing the user to either accept the default mode of 750 or use a file block to manually set the created file's mode later in the recipe.

This is duplicate of #4

Was this actually duplicated in #4? It appears in the 3.0.0 version of the cookbook, which includes #4 changes, it doesn't allow you to specify, and rather sets the permissions to 600 (which was previously 750). If so, I can submit a PR to update the README to further clarify how to set this, but wasn't seeing examples, or documentation on how to control this (as this changes from the 2.x -> 3.x behavior).

To clarify, seeing 600 on files being managed for resources used with template (ex. landing in conf) and seeing 644 for remote files landing in the lib directory.

authors: Iggnsthe bbaugher cchesser


text:
[terra-tabs] Overflow in icon-only collapsible tabs.

Bug Report
Description
This issue occurs only when all tabs are icon-only. In a scenario when some tabs need to be collapsed into a menu due to unavailability of space, container supposedly appears to overflow — few tabs that needed to be actually hidden are visible pushing the "More" button to the right and causing an overflow.
Steps to Reproduce

Display, let's say, 50 icon-only tabs.

Additional Context / Screenshots

Repro
import React from 'react';
import IconSearch from 'terra-icon/lib/icon/IconSearch';
import Tabs from 'terra-tabs';

const createTabPanes = () => {
  const tabPanes = [];
  for (let i = 0; i < 50; i += 1) {
    const tabPane = (
      <Tabs.Pane label={`Search${i}`} icon={<IconSearch />} isIconOnly key={`Search${i}`} id={`search${i}`} />
    );

    tabPanes.push(tabPane);
  }
  return tabPanes;
};

const IconOnlyTabs = () => (
  <Tabs id="icononlytabs" responsiveTo="none">
    {createTabPanes()}
  </Tabs>
);

export default IconOnlyTabs;

Expected Behavior
Horizontal scroll should not appear, 'More' button should not look cut off.
Possible Solution
The minimum width set to icon-only tab affects the logic that we have to calculate the hideStateIndex that decides how many tabs to show and how many to collapse into the menu. Increasing the min-width fixes this issue.
https://github.com/cerner/terra-framework/blob/6cf7f8722f57836915c06589297b30efd09fb1df/packages/terra-tabs/src/Tabs.module.scss#L58-L62
Environment

Component Name and Version: terra-tabs v6.18.0
Browser Name and Version: All browsers.

@ Mentions
@neilpfeiffer

@neilpfeiffer, thoughts?

Not fully understanding why min-width fixes the dynamic handleResize calculation, but would interested to see the change applied in PR and evaluate.

@neilpfeiffer
Draft PR - https://github.com/cerner/terra-framework/pull/984
Deployment - [WIP]

Not fully understanding why min-width fixes the dynamic handleResize calculation, but would interested to see the change applied in PR shown with a new test case and evaluate.

I don't understand how it affects that either. But it seems to work.

authors: jeremyfuksa neilpfeiffer nramamurth

repo: cerner/terra-framework


text:
Update on click outside

Summary
Resolves #237
Deployed URL
https://terra-framework-deploye-pr-327.herokuapp.com/#/tests/terra-hookshot/hookshot/hookshot-close-behaviors

Functional verification completed. The hookshot popup examples display and function as expected.

authors: bjankord mmalaker


text:
fix the open graph tag "og:title"

The og:title is important because that's the first thing people see when they share a cert-maanger.io link in Twitter or on Slack. Today, all the pages have the same og:title:
cert-manager - Documentation
The title of the page that we set in each front matter is discarded. This change fixes that.
To reproduce the before and after commands below, first run:
./scripts/server-netlify

Before:
$ curl -sL localhost:8888/docs/tutorials/getting-started-with-cert-manager-on-google-kubernetes-engine-using-lets-encrypt-for-ingress-ssl | htmlq meta | grep og:title
<meta content="cert-manager - Documentation" property="og:title">

After:
$ curl -sL localhost:8888/docs/tutorials/getting-started-with-cert-manager-on-google-kubernetes-engine-using-lets-encrypt-for-ingress-ssl | htmlq meta | grep og:title
<meta content="Deploy cert-manager on Google Kubernetes Engine (GKE) and create SSL certificates for Ingress using Let's Encrypt" property="og:title">

Maybe we should append — cert-manager documentation to the titles?

repo: cert-manager/website


text:
🛑 echo-server.madacluster.tech is down

In 1901a1d, echo-server.madacluster.tech (https://echo-server.madacluster.tech) was down:

HTTP code: 0
Response time: 0 ms

Resolved: echo-server.madacluster.tech is back up in 7c00152 after 4 minutes.

repo: cesarempathy/upptime


text:
LOON-491: native splash screen

JIRA: https://cesko-digital.atlassian.net/browse/LOON-491

myslím, že pokud jsi přihlášenej a otevřeš appku, tak je tam nekonečný Splash screen
měl by se ještě odstranovat asi tady: https://github.com/cesko-digital/loono/blob/master/lib/router/guards/check_is_logged_in.dart#L13

design splashe myslím není, ale tu barvu pozadí bych dal asi stejnou takovou tu béžovou jak je na WelcomeScreen

@mzdm diky za tip, adjusted :D

repo: cesko-digital/loono


text:
Added global flag for watching chmod only changes

this fixes #32

As I mentioned on #32, I don't want a flag for this if we can avoid it. I'd still need to see the research I mentioned in https://github.com/cespare/reflex/issues/32#issuecomment-187435532.

authors: cespare jdoklovic

repo: cespare/reflex


text:
Update About text for version 3.4.0

Change "This is the CESSDA Data Catalogue (CDC) version 3.2.0, released on 2022-12-08."

Incorporate updates made by Service Owner (see https://docs.google.com/document/d/1XzBC65fvuNqCNhctJgDicPKqNWh0DsPucVByly9kiU0/edit)

See https://github.com/cessda/cessda.cdc.searchkit/pull/154


text:
Button for code sharing

We need a button that somehow stores the code that is currently in the editor and creates a link to show that code again. This allows for on-the-fly sharing of examples.

maybe we could store the code as gists here in github, if the API's not too convoluted. Anyway this is nice too have but low priority

repo: ceylon/ceylon-web-ide-backend


text:
createJavaObjectArray() is allowed without explicit type arguments

As discussed on gitter, it's possible to call createJavaObjectArray without explicit type arguments, which might lead to ClassCastExceptions at runtime:
typeParameters => createJavaObjectArray({}); // expected to return `ObjectArray<PsiTypeParameter>`

java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to [Lcom.intellij.psi.PsiTypeParameter;
	at org.intellij.plugins.ceylon.ide.ceylonCode.lightpsi.CeyLightToplevelFunction.getTypeParameters(CeyLightToplevelFunction.ceylon:155)

Related to https://github.com/ceylon/ceylon/issues/6160

Perhaps related, when I have a createJavaObjectArray() that is in fact a createJavaObjectArray<CeyLightToplevelFunction|CeyLightClass>(), I also get a CCE:
java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to [Lcom.intellij.psi.PsiClass;
	at org.intellij.plugins.ceylon.ide.ceylonCode.lightpsi.CeylonElementFinder.getClasses(CeylonElementFinder.ceylon:85)

Both CeyLightToplevelFunction and CeyLightClass satisfy PsiClass.

This is an SDK issue that was misfiled against the typechecker! Now https://github.com/ceylon/ceylon-sdk/issues/606.

I thought he wanted a type checker error, not a runtime one.

Well, I want a pony, but that doesn't mean you're going to buy me one...
I'm strongly against special casing stuff from ceylon.interop.java in the typechecker.

Even if I ship you 400g of Poney?

Here, have a Pony http://www.ponylang.org/

Even if I ship you 400g of Poney?

http://www.urbandictionary.com/define.php?term=poney
Is that what you mean?

Damnit. This is how we spell it in French :(

authors: FroMage bjansen gavinking

repo: ceylon/ceylon


text:
Java EE-friendly compiler mode

Thinking further about #6609 #6610, I now think we should go down a slightly different path.
The original mapping of Ceylon->Java was designed to be as "strict" as possible, allowing the minimum possible "misuse" of Ceylon APIs called from Java. More recently we weakened it slightly to make Ceylon objects serializable-by-default, which I still think was the right call.
However, the current mapping is still not perfect in the Java EE universe, where there are a bunch of patterns/rules that both our mapping, and our language defaults, get in the way of. For example,

Several Java EE specs won't let you define final members.
Some Java EE specs don't know what to do with ceylon.language.Integer, ceylon.language.String, and friends.
Some Java EE specs have problems with our late initialization checking.
JAX-RS likes having public default constructors. Grrr.

Therefore, I propose a separate mode where:

We never generate final on methods, even if they're not marked default.
We store Integer?, Float?, String?, Byte?, Boolean? fields as java.lang's Long, Double, String, Byte,  Boolean.
We disable runtime assignment checking for late fields. (Hat tip: @jvasileff.)
We make the secret default constructor public instead of protected, since JAX-RS likes it that way.

Now, what triggers this mode? There's a number of possibilities I can think of. For example, it might be triggered by a persistence.xml or beans.xml in META-INF, or it might be triggered by an @Entity annotation.
On the other hand, there should probably also be a commmand line option, because "Java EE-friendly" is also probably "Spring EE-friendly".
I think this is better than what I had proposed earlier, and so I'm going to close the other issues.

@tombentley How much work is involved in what is outlined above?

Potential enhancement to this: we could even somehow mess with the mapping for collection-typed fields, to transform Ceylon collection-typed fields into Java collection types.
Actually we should definitely do this, though it's a little more work.

How much work is involved

1, 3 and 4 are relatively easy. 2 is going to be more fiddly. Maybe a week in total. It should be do-able for 1.3.2. Collection conversion is way harder.
We need to put more work into figuring out when to trigger this stuff. I don't think a compiler options is the right thing, because it doesn't apply to specific program elements at all, just on whatever elements are involved in a particular compilation.

I have the feeling this is something where we should think hard and long about the possible consequences of suddenly having several different mapping from Ceylon types to the types we finally generate. Right now it's two-pronged: boxed or unboxed, which already creates a lot of complexity. It would now become 3-pronged (while hopefully keeping compatibility with old code).
I'd almost be more inclined to just break and switch to using Java types for our boxed types. Except that would introduce the possibility of double boxing perhaps.

2 is going to be more fiddly

Just "more fiddly"? Seems like a pretty big change to me?

We need to put more work into figuring out when to trigger this stuff.

Yeah, let me do a little research on that. I have to re-familiarize myself with some of the specs in this area (some of which I helped write, but still don't remember).
In the meantime...

1, 3 and 4 are relatively easy.

Alright, could you make a start on this bit while I figure out some rules for how it gets turned on?

2 is going to be more fiddly.

Yes, of course. We don't have to deliver this whole issue in 1.3.1 though. So let's play it by ear. It would be great to have it in but we can live without it.

Collection conversion is way harder

I think it's a bit harder, for sure, but I don't think it's all that different from 2.

Yeah, OK maybe I was a little hasty. "Quite a lot more fiddly". It's actually an opportunity to improve the compiler backend if we can make this more pluggable and less hard-coded.

Aren't our fields always protected by getters/setters?

Aren't our fields always protected by getters/setters?

Ah, not quite because they're set directly from the constructor. Still, that's only three locations per field to worry about:

the constructor
the getter
the setter

I don't see how that's an enormous impact.

Quite a lot more fiddly

The English and their understatements! rolls eyes

I don't see how that's an enormous impact.

Famous last words ;)
I hope you're right but I doubt it. I'm sure we'll need changes in the model loaders for one.

I'm sure we'll need changes in the model loaders for one.

Not true. The metadata is read from the getter, not from the field.

Does this have any implications for libraries? Should we, for example, compile future SDK releases in EE mode?

Does this have any implications for libraries? Should we, for example, compile future SDK releases in Java EE mode?

No.

Still, that's only three locations per field to worry about:

I think we also do direct access whenever we know the getter/setter is/are final.

If it's true, I wasn't aware of that @quintesse.

@quintesse not that I have observed.

We disable runtime assignment checking for late fields.

Would we do that for all late fields, or just those where we would otherwise generate an initialized flag field?

we could even somehow mess with the mapping for collection-typed fields, to transform Ceylon collection-typed fields into Java collection types.

So I assume you mean something like:

c.l.Sequential (or c.l.List-c.l.String?) →j.u.List
c.l.Map →j.u.Map
c.l.Set →j.u.Set

Obviously we'd lose identity if we're wrapping and unwrapping these things.

Would we do that for all late fields, or just those where we would otherwise generate an initialized flag field?

Great question ... I'm gunna go with .... um ... (flips coin) ... all of them? For now?

So I assume you mean something like:

List -> j.l.List
Set -> j.l.Set
Map -> j.l.Map
String -> j.l.String (as today)

And optional types:

String? -> j.l.String
Integer? -> j.l.Long
Float? -> j.l.Double
Byte? -> j.l.Byte
Boolean? -> j.l.Boolean
Character? -> j.l.Integer

Obviously we'd lose identity if we're wrapping and unwrapping these things.

Not a problem, since the containder tends to wrap and unwrap them anyway.

We make the secret default constructor public instead of protected, since JAX-RS likes it that way.

Even for a non-shared class (where the initializer constructor would be package access)?

Even for a non-shared class (where the initializer constructor would be package access)?

Not sure, we need to check what the JAX-RS spec says. Perhaps resources have to be public.

They must be public, FTR

They must be public, FTR

Then in that case it would only be necessary to do this for shared classes, it seems. And for un-shared classes we leave them package-access.

For model loading we've previously set the Declaration.isDefault() flag when the method mirror is non-final. But in EE mode all methods are non-final, which means we should fallback to using the @Default annotation, but only when loading EE-mode classes. Which means we need to know a class was compiled in EE mode. Annoying. Or we add a @Final annotation in lieu of final. I think I prefer the latter option.

Or we add a @Final annotation in lieu of final. I think I prefer the latter option.

I think that's reasonable. It will be more reusable if there are other cases in future where we need to suppress the final modifier.

I have items 1 – 4 pretty much working on the ee-mode branch @gavinking, if you want to try it out. You'll need --ee on your command line (or ee in your config).
I still have to do the collection mapping. Presumably we map c.l::List<c.l::Integer> →j.l.List<j.l.Long>? What about List<List<Integer>>?

@tombentley fantastic! That's great news.

@tombentley it did not appear to like the default argument.
Gavins-MacBook-Pro-2:ceylon-wildfly-swarm-jaxrs gavin$ ceylon compile --ee && ceylon swarm --provided-module javax:org.wildfly.swarm:jaxrs jaxrs.example && java -jar jaxrs.example-1.0.0-swarm.jar
source/jaxrs/example/entity/Employee.ceylon:15: error: Ceylon backend error: no suitable method found for valueOf(Integer)
shared entity class Employee(name, year=null) {
                                   ^
    method Long.valueOf(String) is not applicable
      (argument mismatch; Integer cannot be converted to String)
    method Long.valueOf(long) is not applicable
      (argument mismatch; Integer cannot be converted to long)
Note: Created module jaxrs.example/1.0.0
ceylon compile: Fatal error: The compiler exited abnormally (4) due to a bug in the compiler.
Please report it:
 https://github.com/ceylon/ceylon/issues/new
Please include:

* the stacktrace printed below
* a description of what you were trying to compile.

Thank you!
com.redhat.ceylon.compiler.CompilerBugException: Bug
        at com.redhat.ceylon.compiler.CeylonCompileTool.handleExitCode(CeylonCompileTool.java:668)
        at com.redhat.ceylon.compiler.CeylonCompileTool.run(CeylonCompileTool.java:650)
        at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:524)
        at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:405)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:115)
        at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:41)
        at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:34)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.redhat.ceylon.launcher.Bootstrap.runVersion(Bootstrap.java:162)
        at com.redhat.ceylon.launcher.Bootstrap.runInternal(Bootstrap.java:117)
        at com.redhat.ceylon.launcher.Bootstrap.run(Bootstrap.java:93)
        at com.redhat.ceylon.launcher.Bootstrap.main(Bootstrap.java:85)
Caused by: java.lang.ClassCastException: com.redhat.ceylon.langtools.tools.javac.code.Symbol$ClassSymbol cannot be cast to com.redhat.ceylon.langtools.tools.javac.code.Symbol$MethodSymbol
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.visitApply(Gen.java:1847)
        at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1464)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genExpr(Gen.java:949)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.visitAssign(Gen.java:1988)
        at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCAssign.accept(JCTree.java:1685)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genExpr(Gen.java:949)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.visitExec(Gen.java:1779)
        at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCExpressionStatement.accept(JCTree.java:1295)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genDef(Gen.java:739)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genStat(Gen.java:774)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genStat(Gen.java:760)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genStats(Gen.java:811)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.visitBlock(Gen.java:1159)
        at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:908)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genDef(Gen.java:739)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genStat(Gen.java:774)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genMethod(Gen.java:1033)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.visitMethodDef(Gen.java:996)
        at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:777)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genDef(Gen.java:739)
        at com.redhat.ceylon.langtools.tools.javac.jvm.Gen.genClass(Gen.java:2461)
        at com.redhat.ceylon.compiler.java.tools.LanguageCompiler.genCodeUnlessError(LanguageCompiler.java:806)
        at com.redhat.ceylon.compiler.java.tools.LanguageCompiler.genCode(LanguageCompiler.java:772)
        at com.redhat.ceylon.langtools.tools.javac.main.JavaCompiler.generate(JavaCompiler.java:1575)
        at com.redhat.ceylon.compiler.java.tools.LanguageCompiler.generate(LanguageCompiler.java:942)
        at com.redhat.ceylon.langtools.tools.javac.main.JavaCompiler.generate(JavaCompiler.java:1539)
        at com.redhat.ceylon.langtools.tools.javac.main.JavaCompiler.compile2(JavaCompiler.java:904)
        at com.redhat.ceylon.langtools.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:862)
        at com.redhat.ceylon.compiler.java.tools.LanguageCompiler.compile(LanguageCompiler.java:271)
        at com.redhat.ceylon.compiler.java.launcher.Main.compile(Main.java:658)
        at com.redhat.ceylon.compiler.java.launcher.Main.compile(Main.java:564)
        at com.redhat.ceylon.compiler.java.launcher.Main.compile(Main.java:556)
        at com.redhat.ceylon.compiler.java.launcher.Main.compile(Main.java:545)
        at com.redhat.ceylon.compiler.CeylonCompileTool.run(CeylonCompileTool.java:649)
        ... 17 more

That's with this:
shared entity class Employee(name, year = null) {

	generatedValue id
    shared late Integer id;

	column { length = 50; }
	shared String name;

	column
	shared variable Integer? year;

}

@tombentley mind if I add an additional requirement at this point?

Store late primitive values using a Java wrapper class instead of an extra field. For example, late Integer id would be persistent as java.lang.Long id.

Well, wait, perhaps that's not what I want after all. The issue is this warning:

source/jaxrs/example/entity/Employee.ceylon:10: warning: the 'late' attribute 'id' cannot be properly initialised just by setting the field value because it is erased to a primitive type: depending on the semantics of 'generatedValue' consider annotating the JavaBean Property getter with generatedValue__GETTER or its setter with generatedValue__SETTER or making it non-'late'
  generatedValue id

That's not quite right, since it can be properly initialized now that we got rid of the initialization checking. And I'm not sure if it merits a warning at all now.

figure out some rules for how it gets turned on?

So this isn't actually very easy, but here's a couple of heuristics that might work:

Enable it at the class level if the class is annotated entity or xmlAccessorType,  or if it has a constructor, field, or method annotated inject.
Enable it at the package level if the package is annotated xmlAccessorType.
Enable it at the module level if the module imports javax.javaeeapi or maven:"javax:javaee-api", or if it has a beans.xml or persistence.xml file in WEB-INF or META-INF.

WDYT, @tombentley?

Perhaps also turn it on for stateless, stateful, messageDriven, and singleton.

Or perhaps we just autoenable it at the module level whenever the module directly imports:

Java EE,
JPA or Hibernate,
JAXB, or
JAX-RS.

That's much simpler.
Any others that should be on that list, DYT?

I like the idea of enabling it on a per-class basis according to annotations present. That's because we could easily make the enabling annotations configurable, so if people want EE-mode for Spring or any other thing it's not difficult for them to do it. It also means that only the required classes get EE-mode, and the rest still benefit from the ("better") default transformations. Obviously when I say "make it configurable" we could have sensible defaults so that in the usual case it "just works".

I like the idea of enabling it on a per-class basis according to annotations present.

I agree that would be nice, but after some research I don't think it's really workable. It works well for JPA because you have the entity annotation. Also works for EJB, since you have component-defining annotations. Doesn't really work well for CDI, nor for JAXB.

The issue is this warning ... That's not quite right, since it can be properly initialized now that we got rid of the initialization checking.

@tombentley, what's your reaction to this?

@gavinking I'll be pushing fixes to the branch shortly.

@gavinking I've updated the branch:

We now enable EE mode automatically when: javaee-api is a direct dependency of the module, or a class is annotated with any of various annotations.
The enabling module imports and annotations are configurable via --ee-import and --ee-annotation respectively. Setting these replaces (rather than adds to). --ee is still supported.
The warning about late won't be shown in EE mode.
Your other Employee example should now work.

Do we need to mention EE mode as a possible alternative solution in the annotated+late warning?

@tombentley can't we do something like --ee=import and  --ee=annotation where --ee would be the same as specifying  --ee=import,annotation? All these extra options seem to me will only muddle the help/docs.

Sorry forget that, I hadn't understood they took arguments.

@tombentley excellent, thanks, I will try it out!

@gavinking we now wrap List, Set and Map.

Alright! Fantastic 👍

So DYT this is finished now, @tombentley, or is there still additional work to do?
Perhaps if there is missing functionality, we should open separate issues.

I'm happy to close this if you are @gavinking.
The only thing I think we've not done which you mentioned is to activate EE-mode based on the presence of persistence.xml or beans.xml in META-INF. If you still want this, we can open a separate issue.

OK. So what precisely are the activation rules today? I just want to see them written down ;-)

Ah, that's great that this is actually documented :-)
However, you say:

EE mode is usually activated automatically, in the presence of certain annotations on classes, or certain imports

I would like to see these "certain" things enumerated on that page ;-)

@gavinking done

OK, thanks, that looks good. Thanks for your hard work on this!

@gavinking @tombentley the EE activation works for javax.persistence.Entity but should we also add javax.persistence.Embeddable ?

@sgalles @tombentley yes, of course, +1.

authors: gavinking lucaswerkmeister quintesse sgalles tombentley


text:
Wrong value when coercing an ObjectArray type literal to a j.l.Class

In 1.3.1, when coercing to a java.lang.Class, the metamodel literal `ObjectArray<String>` results in the value java.lang.Object[].class. It should have the value ceylon.language.String[].class.

Discovered during #6818


text:
Inconsistent behaviour

Thanks for this life saving nuget! :))
I'm using the nuget version with Rider. And in some situations it works, in some, it doesn't.
I use Alt + Enter.
It's ok.

It should display the Initialize with local variables and use the properties of the class.

Also, it doesn't show the Implement Clone method when I select/set the cursor on the class name.

Ad1. I need to check that, can you provide a sample solution?
Ad2. "Implement Clone metho" - I don't provide such functionality. You probably confused MappingGenerator with something else.

Ad2. In the project wiki there is a paragraph

Generate ICloneable interface implementation - with a gif.

I don't see any problem with "Implement clone" options, works fine in any "space" configuration.

Tested on Rider 2020.2.1

"Initialize with local values" - this action is using only local variables and method parameters. It's not using enclosing type members. This is the current behavior.

Ok, I'm getting the menu when I have the cursor on the class name. Previously I had the cursor just at the end of class name.
But when I try to invoke the action, the IDE freezes. I have to close it from Task Manager. I'm using Rider 2020.2.4

How large is your solution and how complex is the cloned class?

Some classes have around 750 lines, including curly braces and empty lines. Other classes have 45 or 75 lines, with just 2 to 10 properties.

does it hang on that sample solution too?

Nope.

So I guess this is due to solution size. This problem is already reported here https://github.com/cezarypiatek/MappingGenerator/issues/115
I tried to profile MappinGenerator several times but I wasn't able to find anything suspicions. Without real example I'm not able to diagnose this problem.

Alright, in the meantime I will try a workaround.

@bdaniel7 might I ask you to test it once again using v1.19.452?

First, the compilation for the entire solution become waaay slower - when using dotnet watch run.
Even when just a file is modified.
Which makes the CPU and the fans go crazy...
Then, I got all kinds of warnings that I didn't get before, and that I had to disable with VSTHRD200,VSTHRD103,VSTHRD002,VSTHRD110,VSTHRD003.

Thanks for quick reply. It's my mistake, the analyzers were referenced incorrectly, shold be fixed in v1.19.454

I'm closing this issue. The case with performance can be tracked here #115

repo: cezarypiatek/MappingGenerator


text:
Wrong animation on iPad

On iPad it's showing wrong animation while disappearing text.

Me Too

authors: amitk-virtueinfo gbawa

repo: cezarywojcik/CWStatusBarNotification


text:
subscription form error

form-validation.js is throwing Uncaught TypeError: Cannot read property 'message' of undefined when subscribing to the form. Possibly an issue between handlebars and webpack.

Fixed! Magic!

repo: cfpb/cfgov-refresh


text:
Fix current openings query

@richaagarwal
@kave

lol love this :+1:

authors: kurtw richaagarwal


text:
Fix sheer indexing error in views and fix some formatting

This relieves this issue and fixes some formatting issues in the View processor. Basically, a View post would have a Hero's slug saved in a custom field. That slug is used to lookup and serve the content of the Hero, but when the Hero is deleted an indexing error occurs. That's because the slug used to do the lookup does not exist but the code does not account for this. Now it does.
@dpford @jimmynotjim @sebworks @anselmbradford @KimberlyMunoz

:+1:

This is going to need an update to fixe the conflicts in CHANGELOG.md. Feel free to merge it as soon as it's fixed so it doesn't end up in a new conflict when another PR gets merged.

authors: dpford jimmynotjim kurtw


text:
Ensure regulation section labels are unique within their version

This change validates that a section's label is unique to the version of the regulation it belongs to.
This means that instead of creating a section that then results in 500 errors, content editors will see an error like this:

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)

@willbarton, is it worth mentioning the uniqueness constraint in the label field's help text (cfgov/regulations3k/models/django.py L224-L226)? Maybe something like:
help_text='Labels must be unique and always require at least 1 '
          'alphanumeric character, then any number of alphanumeric '
          'characters and hyphens, with no spaces.'

@niqjohnson excellent idea! Included in eec8619.

authors: niqjohnson willbarton


text:
Inactive users cron job

Created a cronjob for our inactive users audit. Scheduled to run weekly on Prod and will never run locally as its not really needed for local development.

Additions

New Cronjob to audit inactive users, suspended locally and run weekly on prod

Removals

Changes

How to test this PR

Screenshots
Notes and todos

Checklist

[ ] PR has an informative and human-readable title

PR titles are used to generate the change log in releases; good ones make that easier to scan.
Consider prefixing, e.g., "Mega Menu: fix layout bug", or "Docs: Update Docker installation instructions".

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code follows the standards laid out in the CFPB development guidelines
[ ] Future todos are captured in comments and/or tickets
[ ] Project documentation has been updated, potentially one or more of:

This repo’s docs (edit the files in the /docs folder) – for basic, close-to-the-code docs on working with this repo
CFGOV/platform wiki on GHE – for internal CFPB developer guidance
CFPB/hubcap wiki on GHE – for internal CFPB design and content guidance

Front-end testing

Browser testing
Visually tested in the following supported browsers:

[ ] Firefox
[ ] Chrome
[ ] Safari
[ ] Edge 18 (the last Edge prior to it switching to Chromium)
[ ] Internet Explorer 11 and 8 (via emulation in 11's dev tools)
[ ] Safari on iOS
[ ] Chrome on Android

Accessibility

[ ] Keyboard friendly (navigable with tab, space, enter, arrow keys, etc.)
[ ] Screen reader friendly
[ ] Does not introduce new errors or warnings in WAVE

Other

[ ] Is useable without CSS
[ ] Is useable without JS
[ ] Does not introduce new lint warnings
[ ] Flexible from small to large screens

I'm going to close this PR for now. We're moving to Single Sign-On, and our inactive user audit is only relevant for production, and we won't be in production in EKS for a while. If we're not on SSO by then, we'll revisit this.

authors: baruva willbarton


text:
Missing spaces in hmda 2023 fig

Many edit texts have some words that are run together without spaces, like invalidIncomewas in V654 and V655.

Above issue has been fixed along with other found formatting issues: https://github.com/cfpb/hmda-frontend/issues/2263

authors: Michaeldremy jmurphy-asurity

repo: cfpb/hmda-combined-documentation


text:
[Update your financial institution profile] Send full institution data with every requests

Every submission to the mail api should include the full data of the institution to minimize the amount of research required to address issues.

We'll be releasing this one after the bug bash next Thursday (November 7th 2024)

repo: cfpb/sbl-frontend


text:
关于论文中Effectiveness of the Hybrid Anchor System消融实验的修改步骤

作者您好，我想问一下复现Effectiveness of the Hybrid Anchor System消融实验时，数据集是Tusimple的话需要修改哪些代码。期待您的回复

@Fakeisall
你可以根据这个地方的mode进行修改：
https://github.com/cfzd/Ultra-Fast-Lane-Detection-v2/blob/c903880678454dfd9b55a63022368db05c00bc6d/evaluation/eval_wrapper.py#L695

好的，我试试，感谢作者回复

明白了，谢谢作者

你好，请问一下此处具体是怎么修改的呢

你好，请问一下此处具体是怎么修改的呢

https://github.com/cfzd/Ultra-Fast-Lane-Detection-v2/blob/c903880678454dfd9b55a63022368db05c00bc6d/evaluation/eval_wrapper.py#L810
我是把他的mode改成对应模式

好的，谢谢你！

authors: Fakeisall cfzd layfolk001


text:
In publish/2: keep the existing Sample File field and add a Datastream API Docs URL field

It was a mistake to use the Sample File field for the API docs URL. We should have kept it to be consistent with the Market, and added another field for the API docs. Easy to say in retrospect, but it'll be better functionality.

After adding the field we'll need to re-activate the Sample File field in the public view, which displays below the asset description.

The mockup will be updated to reflect these changes and specify the page layout.

Here's the updated mockup of publish/2:
https://htmlpreview.github.io/?https://github.com/chaineresearch/assets/blob/main/market_mockups/publish.html
Besides adding the original "Sample File" field back in, nothing else has changed.

Here's the updated mockup of the Preview (which contains the public page layout too):
https://htmlpreview.github.io/?https://github.com/chaineresearch/assets/blob/main/market_mockups/preview.html
Changes:

The original SAMPLE DATA element needs to be turned on again.
The DATASTREAM API DOCUMENTATION element has moved to under the SAMPLE DATA element.
The DATASTREAM API DOCUMENTATION element title has changed (to "DATASTREAM API DOCUMENTATION").
The content of the link to the API docs is no longer a URL. It's a text description, following the Ocean format.
No CSS adjustments should be needed, it's all default Ocean housestyle.

Noted

authors: kitblake okpoEkpenyong

repo: chaineresearch/datastreams


text:
Multi-arch build fails in GitHub action with /bin/busybox: Exec format error

config:
contents:
  repositories:
    - https://dl-cdn.alpinelinux.org/alpine/latest-stable/main
    - https://dl-cdn.alpinelinux.org/alpine/latest-stable/community
  packages:
    - alpine-baselayout
    - ffmpeg
accounts:
  groups:
    - groupname: svc
      gid: 10000
  users:
    - username: svc
      uid: 10000
  run-as: svc

archs:
  - amd64
  - arm64

workflow file: https://github.com/MemeLabs/strims/actions/runs/2922854653/workflow
logs: https://github.com/MemeLabs/strims/runs/8005777547?check_suite_focus=true#step:4:244
relevant part:
Aug 24 23:06:05.423 [INFO] [arch:aarch64] creating group 10000(svc)
Aug 24 23:06:05.425 [INFO] [arch:aarch64] [cmd:/bin/busybox] [use-proot:false] [use-qemu:] running: /usr/sbin/chroot /tmp/apko-1875477164/aarch64 /bin/busybox --install -s
Aug 24 23:06:05.427 [DEBUG] [arch:aarch64] [cmd:/bin/busybox] [use-proot:false] [use-qemu:] chroot: can't execute '/bin/busybox': Exec format error
Error: failed to build layer image for "arm64": failed to install busybox symlinks: failed to install busybox symlinks: exit status 126
2022/08/24 23:07:02 error during command execution: failed to build layer image for "arm64": failed to install busybox symlinks: failed to install busybox symlinks: exit status 126

Running the same command locally works as expected.

You need to do the docker/setup-binfmt-action before using apko on github actions, or pass --arch x86_64.

authors: SoMuchForSubtlety kaniini

repo: chainguard-dev/apko


text:
WIP: add logstash image

New Image Pull Request Template

Image Size

[ ] The Image is smaller in size than its common public counterpart.
[ ] The Image is larger in size than its common public counterpart (please explain in the notes).

Notes:
Image Vulnerabilities

[ ] The Grype vulnerability scan returned 0 CVE(s).
[ ] The Grype vulnerability scan returned > 0 CVE(s) (please explain in the notes).

Notes:
Image Tagging

[ ] The image is not tagged with version tags.
[ ] The image is tagged with :latest
[ ] The image is not tagged with :latest (please explain in the notes).

Notes:
Basic Testing - K8s cluster

[ ] The container image was successfully loaded into a kind cluster.
[ ] The container image could not be loaded into a kind cluster (please explain in the notes).

Notes:
Basic Testing - Package/Application

[ ] The application is accessible to the user/cluster/etc. after start-up.
[ ] The application is not accessible to the user/cluster/etc. after start-up. (please explain in the notes).

Notes:
Helm

[ ] A Helm chart has been provided and the container image can be used with the chart.  If needed, please add a -compat package to close any gaps with the public helm chart.
[ ] A Helm chart has been provided and the container image is not working with the chart (please explain in the notes).
[ ] A Helm chart was not provided.

Notes:
Processor Architectures

[ ] The image was built and tested for x86_64.
[ ] The image could not be built for x86_64 (please explain in the notes).
[ ] The image was built and tested for aarch64.
[ ] The image could not be built for aarch64. (please explain in the notes).

Notes:
Functional Testing + Documentation

[ ] Functional tests have been included and the tests are passing.  All tests have been documnted in the notes section.

Notes:
Environment Testing + Documentation

[ ] There has not been a request and/or there is no indication that this image needs tested on a public cloud provider.
[ ] The container image has been tested successfully on a public cloud provider (AWS, GCP, Azure).
[ ] The container image has not been tested successfully on a public cloud provider (AWS, GCP, Azure) (please explain in the notes).

Notes:
Version

[ ] The package version is the latest version of the package.  The latest tag points to this version.
[ ] The package version is the not the latest version of the package (please explain in the notes).

Notes:
Dev Tag Availability

[ ] There is a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base')
[ ] There is not a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base') (please explain in the notes).

Notes:
Access Control + Authentication

[ ] The image runs as nonroot and GID/UID are set to 65532 or upstream default
[ ] Alternatively the username and GID/UID may be a commonly used one from the ecosystem e.g: postgres
[ ] The image requires a non-standard username or non-standard GID/UID (please explain in the notes).

ENTRYPOINT

[ ] applications/servers/utilities set to call main program with no arguments e.g. [redis-server]
[ ] applications/servers/utilities not set to call main program with no arguments e.g. [redis-server] (please explain in the notes)
[ ] base images leave empty.
[ ] base image and not empty (please explain in the notes).
[ ] dev variants is set to entrypoint script that falls back to system.
[ ] dev variants is not set to entrypoint script that falls back to system (please explain in the notes).

CMD

[ ] For server applications give arguments to start in daemon mode (may be empty)
[ ] For utilities/tooling bring up help e.g. –help
[ ] For base images with a shell, call it e.g. [/bin/sh]

Environment Variables

[ ] Environment variables added.
[ ] Environment variables not added and not required.

SIGTERM

[ ] The image responds to SIGTERM (e.g., docker kill $(docker run -d --rm cgr.dev/chainguard/nginx))

Logs

[ ] Error logs write to stderr and normal logs to stdout. Logs DO NOT write to file.

Documentation - README

[ ] A README file has been provided and it follows the README template.

Superseded by chainguard-images/images#2197

repo: chainguard-images/images


text:
Hi,doccano local host page doesnt open up once machine is powered off and powered on again. PLease help me out.

If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Python version:

Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug or a feature request.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

Please follow the  ISSUE_TEMPLATE.

repo: chakki-works/doccano


text:
Missing strokeWidth from SystemProperties type

Description
I'm styling an SVG element and the strokeWidth property seems to be missing from the SystemProperties type definition that's generated by the codegen command:

Link to Reproduction
https://stackblitz.com/edit/vitejs-vite-eqkrvv?file=src/App.tsx&terminal=dev
Steps to reproduce
Write a strokeWidth property in a cva/css declaration and see the TS error popping up in the IDE.
I tried to reproduce in a StackBlitz container but TypeScript is not as picky there.
JS Framework
React (TS)
Panda CSS Version
0.9.0
Browser
Not relevant
Operating System

[X] macOS
[ ] Windows
[ ] Linux

Additional Information
No response

Hi @rudeayelo,
Kindly update the latest version. Svg properties are supported there.
Thanks

authors: rudeayelo segunadebayo

repo: chakra-ui/panda


text:
pkg:cli missing ./bin.js in exports

Affected Packages

pkg:cli

Problem
I'm getting this error in GitHub Actions after upgrading @changesets/cli to 2.27.0:
Error: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './bin.js' is not defined by "exports" in /home/runner/work/***/***/node_modules/@changesets/cli/package.json
Error: Package subpath './bin.js' is not defined by "exports" in /home/runner/work/***/***/node_modules/@changesets/cli/package.json

This is when changeset tag is called.
Proposed solution
Add ./bin.js in the exports in the package.json file.

I get the same error

Thanks for the info - I located the problem to be located here.

Great, thanks for the quick fix! 👍

authors: Andarist alvesvaren ludovicm67

repo: changesets/changesets


text:
bug(duplicate detection): Etags cannot be used to compare objects

Describe the bug
Duplicate detection does not detect duplicated when publishing a collection.
Current we use AWS S3 Etags to determine if two object in are identical. However since we are using KMS to encrypt our object in place, AWS does not guarantee that Etags will be identical for identical objects in S3.
Expected behavior
Duplicates should be caught before publishing a collection
Solution
Add a custom tag to objects upload to s3 which represents the hash of the upload object. This tag will be used compare objects uploaded to S3. Alternatively this tag can be store in the database rather than on the S3 object.
Whatever implementation we go with, we should generate tags for all previously uploaded dataset.

Unable to use the hash generated by dropbox because we are using a shared link to a file. https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/API-to-get-content-hash-of-shared-file-link/td-p/458942

repo: chanzuckerberg/single-cell-data-portal