MINOR: Update Scala to 2.12.7, lz4-java to 1.5 and others

Highlights:

10% compilation speed improvement in Scala 2.12.7:
https://www.scala-lang.org/news/2.12.7
10% decompression speed in LZ4 1.8.2 (lz4-java 1.5.0
includes lz4 1.8.3):
https://github.com/lz4/lz4-java/blob/master/CHANGES.md#150
https://github.com/lz4/lz4/releases

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc @cmccabe @hachikuji @xvrl


Creating new field with unique index with condition failing

GORM Playground Link

https://github.com/go-gorm/playground/pull/570
Description
As per the documentation on https://gorm.io/docs/indexes.html#Index-Tag gorm supports conditional indexing using a where condition. But it seems to be not respected in MSSQL / TSQL

type User struct {
    Abc string `gorm:"index:unique_abc,class:UNIQUE,where: abc IS NOT NULL"`
}

creating this field results in failure.
It tries alter table add column "abc" unique.
But this fails.
Is there any work around where this can be created in single migration?

If I am right this is occuring not during table create but at table alter while adding a column with constraint is added?

If I am right this is occuring not during table create but at table alter while adding a column with constraint is added?

yes, @jozephp
it applies ALTER TABLE  ADD COLUMN  UNIQUE instead of CREATE UNIQUE INDEX "unique_issuer" ON "users"("issuer_id") where issuer_id IS NOT NULL

Hi @jinzhu,
is there any way we can achieve this?

Hi @black-06 , @jinzhu
We have also observed that migration fails on this field as it queries
ALTER TABLE <table_name> ALTER COLUMN <column_name> nvarchar(256) NULL;
this is not acceptable on unique indexes with condition it seems

Hi @black-06,
Yeah we have pre-populated table, hence we would need the where clause to apply the constraint except for

I'm simply trying to create a partial unique index with deleted_at NOT NULL. (pgsql)
I'm able to achieve this using following raw sql
CREATE UNIQUE INDEX idx_tgc_workspaces_domain ON tgc_workspaces (domain) WHERE deleted_at IS NULL;
I'm unable to do the same with gorm tag. I tried these tags:

gorm:"index:idx_table_domain,class:UNIQUE,where:deleted_at IS NULL"
gorm:"uniqueIndex:idx_table_domain,where:deleted_at IS NULL"
gorm:"index:idx_table_domain,unique,where:deleted_at IS NULL"

it produces constraint without condition: ALTER TABLE "table" ADD CONSTRAINT "table_domain" UNIQUE("domain")

Aftert upgrading GORM to v1.25.9 and Postgres SQL driver to v1.5.7 now it works using the format below:
type MyModel struct {
	ID        uint `gorm:"primarykey"`
	CreatedAt time.Time
	UpdatedAt time.Time
	DeletedAt gorm.DeletedAt `gorm:"index:;uniqueIndex:idx_my_model_my_field_deleted_at,priority:2,where:deleted_at IS NOT NULL"`
	MyField   string         `gorm:"not null:idx_my_model_my_field,unique,where:deleted_at IS NULL;uniqueIndex:idx_my_model_my_field_deleted_at,where:deleted_at IS NOT NULL"`
}


Please help test new Tor broadcasting feature

Right now on the bitcoin network, there are a large number of fake bitcoin nodes which aggressively announce themselves in an effort to attract more people to connect to them. They are run by transaction surveillance companies and they spy on every newly-broadcasted transaction, tracking it as it propagates through the p2p network giving them an idea of the IP address that originally broadcasted that transaction.
One way to beat this is by broadcasting unconfirmed transactions through Tor. A new feature of Electrum Personal Server allows for this. When the user presses "Send" or "Broadcast" their transaction will transparently be broadcast through Tor and so will not leak their real IP address.
 Here's how:

Add walletbroadcast=0 to your bitcoin.conf file.
Update to the master branch of EPS from github
Run Tor
Edit the config.ini file to enable tor broadcasting, with broadcast-method = tor and set tor_host and tor_port to point to your Tor application
Send transactions

Tell me or someone if you need help. Let us know how it goes. If there's no problem then soon they'll be a new release with this feature included.
For more information read https://github.com/chris-belcher/electrum-personal-server/issues/52 or https://en.bitcoin.it/wiki/Privacy#Countermeasures_to_traffic_analysis
Technical explanation: This feature works by making its own connections to peers over tor and sending the transaction via that. It uses the RPC call getnodeaddresses to obtain addresses from bitcoind's addrman, and so it doesnt rely on centralized DNS seeds.

Is this making ephemeral identities each time it wants to send out a set of transactions, or a long-running hidden service connection?

The first one. It makes connections over tor to push a transaction and then disconnects.

Might be a dumb question, but arn't there also al lot of fake tor exit nodes that can also identify tx's ?

@Coinomatron it only matters that the sending node isn't fingerprintable in any way, aside from the tx data itself.

I was also quite surprised that the fake Bitcoin nodes can identify IP's. My understanding was they couldn't.

Do I have to tell the electrum wallet to use tor too?

Do I have to tell the electrum wallet to use tor too?

No, tell Electrum to connect to Electrum Personal Server as normal.

Hi. Just pulled the 0.1.7dev version down and sudo pip install . and ran. Failed with error related to str.fromhex as below. I run it as a service so that's why various service details but it was working fine before pull (0.1.6). Any suggestions?
Jun 25 07:20:15 pixie electrum-personal-server[6534]:   File "/usr/local/lib/python2.7/dist-packages/electrumpersonalserver/server/__init__.py", line 1, in <module>
Jun 25 07:20:15 pixie electrum-personal-server[6534]:     from electrumpersonalserver.server.merkleproof import (
Jun 25 07:20:15 pixie electrum-personal-server[6534]:   File "/usr/local/lib/python2.7/dist-packages/electrumpersonalserver/server/merkleproof.py", line 6, in <module>
Jun 25 07:20:15 pixie electrum-personal-server[6534]:     from electrumpersonalserver.server.hashes import Hash, hash_encode, hash_decode
Jun 25 07:20:15 pixie electrum-personal-server[6534]:   File "/usr/local/lib/python2.7/dist-packages/electrumpersonalserver/server/hashes.py", line 44, in <module>
Jun 25 07:20:15 pixie electrum-personal-server[6534]:     bfh = bytes.fromhex
Jun 25 07:20:15 pixie electrum-personal-server[6534]: AttributeError: type object 'str' has no attribute 'fromhex'
Jun 25 07:20:15 pixie systemd[1]: electrum.service: Main process exited, code=exited, status=1/FAILURE
Jun 25 07:20:15 pixie systemd[1]: electrum.service: Unit entered failed state.
Jun 25 07:20:15 pixie systemd[1]: electrum.service: Failed with result 'exit-code'.

Setup seems to have worked. If I do a transaction, can I check if it went through tor?

@Coinomatron You should see logs similar to this:
INFO:2019-06-23 23:58:32,416: Broadcasting tx 7f2efb7b622dfc1a418ff1503925ab0be18d93d47005ac5cf1e974d67bab5bb2 with broadcast method: tor
INFO:2019-06-23 23:58:33,668: Uploaded transaction via tor to node ('<IP_ADDRESS>', 8333)
INFO:2019-06-23 23:59:04,140: Uploaded transaction via tor to node ('<IP_ADDRESS>', 8333)
INFO:2019-06-23 23:59:04,388: Uploaded transaction via tor to node ('2406:da18:f7c:4351:591b:4881:3986:3703', 8333)
INFO:2019-06-23 23:59:08,175: Uploaded transaction via tor to node ('<IP_ADDRESS>', 8333)
INFO:2019-06-24 00:00:38,826: Uploaded transaction via tor to node ('<IP_ADDRESS>', 8333)

Works well with given instructions.

Hi, if I have my bitcoin core running with config file below, do I still need to use the tor option in eps? If I broadcast right now with eps will I be any less private than if I did it with eps tor option switched on? thanks
server=1
daemon=1
txindex=1
disablewallet=0
proxy=<IP_ADDRESS>:9050
bind=<IP_ADDRESS>
listenonion=1
onlynet=onion
dnsseed=0
dns=0
dbcache=100
maxorphantx=10
maxmempool=50
maxconnections=10
maxuploadtarget=50
Security
banscore=50
bantime=172800

@3ntranced Your node connects to the bitcoin network entirely over tor. This tor broadcasting feature doesn't change your privacy. Read these two comments to understand why https://github.com/chris-belcher/electrum-personal-server/issues/52#issuecomment-419881541

Hi @chris-belcher. Im gonna try this because I want to help out. I dont think I need it thou because like @3ntranced I run my node over tor. I was wondering thou, I have my node on a dedicated PC, and I use "ssh username@host -L 50002:localhost:50002" from my laptop to use electrum.EPS is installed on my node PC, and electrum wallet is on my laptop, im I still doing it all over TOR with this method?
Thanks / B

Works fine thou =)
INFO:2019-07-25 23:54:09,166: Broadcasting tx XXXXXXXXXX with broadcast method: tor
INFO:2019-07-25 23:54:10,404: Uploaded transaction via tor to peer at ('<IP_ADDRESS>', 8333)
INFO:2019-07-25 23:54:14,421: Uploaded transaction via tor to peer at ('g3xgqirastjhpsn6.onion', 8333)
INFO:2019-07-25 23:54:14,742: Uploaded transaction via tor to peer at ('vvh7lqlciohttabh.onion', 8333)
INFO:2019-07-25 23:54:17,419: Uploaded transaction via tor to peer at ('y27gfcs7mvdcpcf2.onion', 8333)

Thanks for the help @permabull

I have my node on a dedicated PC, and I use "ssh username@host -L 50002:localhost:50002" from my laptop to use electrum.EPS is installed on my node PC, and electrum wallet is on my laptop, im I still doing it all over TOR with this method?

Yes you are broadcasting over tor. Your SSH line is related to how Electrum connects to EPS, the transaction broadcasting is related to how EPS communicates with the bitcoin p2p network, and whether that happens over Tor or not.

Thanks for the help @permabull

I have my node on a dedicated PC, and I use "ssh username@host -L 50002:localhost:50002" from my laptop to use electrum.EPS is installed on my node PC, and electrum wallet is on my laptop, im I still doing it all over TOR with this method?

Yes you are broadcasting over tor. Your SSH line is related to how Electrum connects to EPS, the transaction broadcasting is related to how EPS communicates with the bitcoin p2p network, and whether that happens over Tor or not.

Thanks very much for reply. If you need help testing anything out just say the word!

This feature is now in the new release 0.2.0, closing


Add support for epicscorelibs and CI pypi publishing

Docs won't publish until we merge this to master, and a PyPI deployment won't go until we tag and push, but everything else should be done.
Fixes #6, supersedes #4

ok, ready for review now...

Looks like there's a spurious .coverage database file introduced in commit b1a7ee264992bb49ea5a17202e0e8d717032fe3f

Can you please rebase out .coverage from commit b1a7ee264992bb49ea5a17202e0e8d717032fe3f, then we're good to go.

Can you please rebase out .coverage from commit b1a7ee2, then we're good to go.

done

Looks good, think I'm hapy


Colored vs white rect

I noticed that some logos (examples: twitter, stack overflow, instagram, skype) have been changed from the reference to be a white path on a colored rect.
Some others (examples: android, disqus, docker, npm) have kept the white rect & colored path.
I personally like the colored rect versions and have tweaked several of them accordingly for myself.  If you want these updates, let me know & I will minimize them & submit a PR.

I think the iconset should be standardised to prefer white/official colours. At this point, the convention seems to be more leaning towards coloured backgrounds but is still quite varied.

Yup. They're mostly using whatever the official logo uses.


monitoring does not always record task_time_running and hostname fields (on short jobs?)

I see missing hostname and task_time_running for the first task, create_empty_repo, which runs extremely fast.
sqlite> select run_id, task_func_name, hostname, task_time_submitted, task_time_running, task_time_returned from task;
37cb5ae7-f4f9-40a7-86ec-9457760344f7|create_empty_repo||2019-06-04 04:13:31.476801||2019-06-04 04:13:31.553611
37cb5ae7-f4f9-40a7-86ec-9457760344f7|install_transmission_curves|cori06|2019-06-04 04:13:31.554481|2019-06-04 04:13:31.644297|2019-06-04 04:13:36.155113
37cb5ae7-f4f9-40a7-86ec-9457760344f7|import_ci_hsc|cori06|2019-06-04 04:13:31.560238|2019-06-04 04:13:31.650255|2019-06-04 04:18:30.889769
37cb5ae7-f4f9-40a7-86ec-9457760344f7|pccd_show|cori06|2019-06-04 04:18:30.891500|2019-06-04 04:18:30.989590|2019-06-04 04:18:49.810345
37cb5ae7-f4f9-40a7-86ec-9457760344f7|pccd_process|cori06|2019-06-04 04:18:30.898264|2019-06-04 04:18:31.031377|2019-06-04 05:26:59.966683
37cb5ae7-f4f9-40a7-86ec-9457760344f7|makeDiscreteSkyMap|cori06|2019-06-04 05:26:59.968017|2019-06-04 05:27:00.054919|2019-06-04 05:27:08.146285

The two fields are from the first message from the monitoring wrapper of task. I guess the task is too short - so there is not enough time to run psutil and send message to hub.

I also am seeing this issue.  Don't know whether it is related or not, but I also see situations where SLURM (at NERSC) claims a job has been running for 5-10 minutes, but there is not yet any confirming information in the monitoring DB.

@benclifford Not sure what the ideal fix here is. How about adding mechanism to guarantee the monitoring wrapper sends out the first message?

I think making the code always send start and end messages would be a good thing

@TomGlanzman Not quite sure this is related. I think this issue only happens to the tasks that are very short (like a no-op). If the DB does not receive that message, then there might be some other issues though. Could you please post the runinfo dir?

Make a new issue for the slurm related problem - that probably isn't this one.


Basic Steam Turbine recipe consumes steam to produce destilled water. But water isn't produced

A simple setup: Create Copper tank with steam -> Basic Steam Turbine. Steam is consumed, but no water is output to be reused.
Recipe in Steam Turbine says 640mB of steam converts to 4mB of destilled water, which I was planning to feed back into the solar boilers.

also the recipe you see only works in The steam turbine multiblock


Include lockfile

Including a lockfile means that dependencies can be expressed in a more stable manner. Especially when pushing to Heroku.

Not meant for this repo (unless you want). When I'm done I'll link a ticket to the heroku one-click deploy.


add naive check for presence of state string

Some entries that locationtagger misses seem pretty obvious to me:

New Mexico’s state land office brought in more than $2 billion in oil and gas royalty revenue over the last 12 months, a record high.
Wyoming conservationists urge state and federal regulators to tax and further restrict oil and gas facilities’ methane emissions.

Lets add a string comparison check against a list of states and also tag based on that.

closed via #8


initial RDS controller - DBSubnetGroup

check in the initial RDS controller with support for only the
DBSubnetGroup resource for now. e2e test upcoming to the community
repository.
aws-controllers-k8s/community#237

Reviewers: please see passing e2e smoke test for DB subnet group here: https://github.com/aws-controllers-k8s/community/pull/724


Update travis.yml to works with stack

travis.yml file updated.

@CristhianMotoche Looks good to me.

@CristhianMotoche Thanks!


Add subkey option to connect

This PR added an option subkey to connectAdvanced.
Currently, the createProvider accepted the second optional argument subKey, It seems like has no real usage for now. Providing the custom subscription key only to Provider is not sufficient for using this feature, connect components need to know the custom subscription key to access the subscription corresponding to custom store. By adding a new option subKey, connect can be able to access the specific subscription.

Add an option subKey to connectAdvanced
Add tests to Provider
Delete extra whitespaces / Identing lines in codebase.

Btw I would like to know if it's possilbe to add .editorconfig and .prettierrc.json to this project. For a consistent code style.

I'd argue we can just get rid of subKey. It doesn't get you anything. You know the subscription key because it follows a specific pattern. It's just extra complexity without any benefits.

@timdorr That's a good point. I will send a pr to remove the subKey another day. We can close this one now.

Yeah I don't like subKey, the sub and the store are supposed to go together. I would've made them a single thing if there was a way to do it that was backwards compatible.


Stop getting a subject descriptor from a gone-async command in Darwin OTA

Fast-tracking platform-specific change with platform owner review.


verbose stack Error: sagan@ build: webpack

C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master>gradlew :sagan-site:bootRun

Configure project :sagan-site
For project [sagan-site] with version [1.0.0.BUILD-SNAPSHOT] the resolved Artifactory repo is [libs-snapshot-local]

Task :sagan-client:npmBuild

sagan@ build C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client
webpack

Hash: f6b99e83826fa8c234d5
Version: webpack 4.41.6
Time: 6052ms
Built at: 23/02/2020 9:42:19 pm
19 assets
Entrypoint main = css/main.css js/main.js
Entrypoint guide = css/guide.css js/guide.js
Entrypoint project = css/project.css js/project.js
Entrypoint team = css/team.css js/team.js
Entrypoint profile = css/profile.css js/profile.js
Entrypoint blog = css/blog.css js/blog.js
Entrypoint admin = css/admin.css js/admin.js
Entrypoint run_prettify = js/run_prettify.js
[10] ./src/app/main.js 8.95 KiB {3} [built]
[13] ./src/css/main.css 1.84 KiB {3} [built] [failed] [1 error]
[14] ./src/app/guide.js 1.14 KiB {2} [built]
[27] ./src/css/guide.css 39 bytes {2} [built]
[28] ./src/app/project.js 1.75 KiB {5} [built]
[29] ./src/css/project.css 39 bytes {5} [built]
[30] ./src/app/team.js 3.96 KiB {7} [built]
[31] ./src/css/team.css 39 bytes {7} [built]
[32] ./src/app/profile.js 3.66 KiB {4} [built]
[33] ./src/css/profile.css 39 bytes {4} [built]
[34] ./src/app/blog.js 24 bytes {1} [built]
[35] ./src/css/blog.css 39 bytes {1} [built]
[36] ./src/app/admin.js 105 bytes {0} [built]
[38] ./src/css/admin.css 39 bytes {0} [built]
[39] ./src/app/run_prettify.js 18 KiB {6} [built]
+ 33 hidden modules
WARNING in configuration
The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment.
You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/
ERROR in ./src/css/main.css
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleParseError: Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
at handleParseError (C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19)
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3
at iterateNormalLoaders (C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
at Array. (C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4)
at Storage.finished (C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16)
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\graceful-fs\graceful-fs.js:115:16
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:61:3)
@ ./src/app/main.js 6:0-24
ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleParseError: Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
at handleParseError (C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:469:19)
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:503:5
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\webpack\lib\NormalModule.js:358:12
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:373:3
at iterateNormalLoaders (C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
at Array. (C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\loader-runner\lib\LoaderRunner.js:205:4)
at Storage.finished (C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16)
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9
at C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client\node_modules\graceful-fs\graceful-fs.js:115:16
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:61:3)
@ ./src/app/main.js 4:0-50
Child mini-css-extract-plugin<EMAIL_ADDRESS>1 asset
Entrypoint mini-css-extract-plugin = *
2 modules
Child mini-css-extract-plugin<EMAIL_ADDRESS>1 asset
Entrypoint mini-css-extract-plugin = *
18 modules
ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>7:36-76

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>12:36-77

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>17:37-76

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>5:36-78

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>6:36-77

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>10:36-79

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>11:36-78

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>15:37-78

ERROR in<EMAIL_ADDRESS>1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>16:37-77

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>14:37-76

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected character '∩┐╜' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>4:36-76

ERROR in<EMAIL_ADDRESS>1:1
Module parse failed: Unexpected character '∩┐╜' (1:1)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
<EMAIL_ADDRESS><EMAIL_ADDRESS>9:36-77

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.12.1 by @fontawesome - https://fontawesome.com
<EMAIL_ADDRESS><EMAIL_ADDRESS>13:36-77

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.12.1 by @fontawesome - https://fontawesome.com
<EMAIL_ADDRESS><EMAIL_ADDRESS>8:36-76

ERROR in<EMAIL_ADDRESS>1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!--
| Font Awesome Free 5.12.1 by @fontawesome - https://fontawesome.com
<EMAIL_ADDRESS><EMAIL_ADDRESS>18:37-76

Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/bulma/css/bulma.css:
1 asset
Entrypoint mini-css-extract-plugin = *
2 modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/admin.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/admin.css 1.46 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/blog.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/blog.css 4.61 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/guide.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/guide.css 3.58 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/main.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/main.css 94.3 KiB {0} [built]
[3] ./src/fonts/metropolis-regular-webfont.woff2 284 bytes {0} [built] [failed] [1 error]
[4] ./src/fonts/metropolis-regular-webfont.woff 284 bytes {0} [built] [failed] [1 error]
[5] ./src/fonts/metropolis-bold-webfont.woff2 284 bytes {0} [built] [failed] [1 error]
[6] ./src/fonts/metropolis-bold-webfont.woff 284 bytes {0} [built] [failed] [1 error]
[7] ./src/fonts/metropolis-extrabold-webfont.woff2 284 bytes {0} [built] [failed] [1 error]
[8] ./src/fonts/metropolis-extrabold-webfont.woff 284 bytes {0} [built] [failed] [1 error]
[9] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 271 bytes {0} [built] [failed] [1 error]
[10] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 284 bytes {0} [built] [failed] [1 error]
[11] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 284 bytes {0} [built] [failed] [1 error]
[12] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 284 bytes {0} [built] [failed] [1 error]
[13] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 424 bytes {0} [built] [failed] [1 error]
[14] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 281 bytes {0} [built] [failed] [1 error]
[15] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 284 bytes {0} [built] [failed] [1 error]
[16] ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 284 bytes {0} [built] [failed] [1 error]
+ 24 hidden modules
ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 13:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 18:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 23:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 28:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 33:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.ttf 1:0
Module parse failed: Unexpected character ' ' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 38:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 20:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.eot 1:2
Module parse failed: Unexpected character ' ' (1:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 30:37-106

ERROR in ./src/fonts/metropolis-regular-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 4:36-88

ERROR in ./src/fonts/metropolis-regular-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 5:36-87

ERROR in ./src/fonts/metropolis-bold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 6:36-85

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 8:36-90

ERROR in ./src/fonts/metropolis-bold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 7:36-84

ERROR in ./src/fonts/metropolis-extrabold-webfont.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 9:36-89

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 12:36-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 11:36-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 16:37-109

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 17:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 21:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 22:37-105

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 26:37-106

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 27:37-105

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 31:37-108

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 32:37-107

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff2 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 36:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.woff 1:4
Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 37:37-103

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.eot 1:0
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 35:37-102

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.eot 1:0
Module parse failed: Unexpected character '∩┐╜' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 15:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.eot 1:0
Module parse failed: Unexpected character '∩┐╜' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 25:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.eot 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 10:36-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 14:37-108

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-italic.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 19:37-107

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-600.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 24:37-104

ERROR in ./src/fonts/open-sans-v17-latin/open-sans-v17-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 29:37-104

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-regular.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 34:37-106

ERROR in ./src/fonts/work-sans-v5-latin/work-sans-v5-latin-700.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <?xml version="1.0" standalone="no"?>
| <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
| <svg xmlns="http://www.w3.org/2000/svg">
 @ ./src/css/main.css (./node_modules/css-loader/dist/cjs.js!./src/css/main.css) 39:37-102

Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/profile.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/profile.css 3.83 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/project.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/project.css 10.3 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!src/css/team.css:
1 asset
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./src/css/team.css 1.9 KiB {0} [built]
+ 1 hidden module
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! sagan@ build: webpack
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the sagan@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\akashdeep\AppData\Roaming\npm-cache_logs\2020-02-23T16_12_19_594Z-debug.log
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':sagan-client:npmBuild'.

Process 'command 'C:\Users\akashdeep\eclipse-workspace\sagan-master\sagan-master\sagan-client.gradle\npm\npm-v6.13.1\npm.cmd'' finished with non-zero exit value 2

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 12s
4 actionable tasks: 1 executed, 3 up-to-date
node v13.9.0
npm 6.13.7

it's fixed, just pull.

Fixed with #963


Fix #208

Just a quick fix for #208.

hey, man, thank you for your fix! I double checked and it works!
Thank you!


Lokalise: Translations update

This pull request was initiated by Lokalise (user Peter Murray) at 2024-08-14 14:45:11

I think one of the @folio-org/spitfire-backend team members will need to merge requests from Lokalise. From the perspective of the script that is moving changes from Lokalise into GitHub, it looks like the merge can't happen because of the branch protections on the master branch. The API doesn't show that bypass branch protections is an option. The script will time out and close the pull request automatically, but anyone can re-open the pull request and merge it.


refactor: adjust installer.sh to possible reuse

Improve the shell scripts according to shellcheck + allow vars
like PRODUCT_NAME, LATEST_VERSION or REPO_PREFIX to be
provided in advance.
Set fallback for $ARCH variable value to amd64
Did you sign your commit? Instructions: 👍
Have you read Contributing guidelines?: 👍

I know it's not in CI but did you run the tests located in https://github.com/kumahq/kuma-website/blob/master/tests/test-installer.sh ? Also do you think we should hook those up to CI?

Also do you think we should hook those up to CI?

Yes :)

Yes, tests are passing:
…/kuma-website [refactor/installer(d4b90ba)] ❯ ./tests/test-installer.sh
running test for amazonlinux:2022
running test for debian:bookworm
running test for centos:7
running test for redhat/ubi8:8.6
running test for ubuntu:22.10
debian:bookworm passed
centos:7 passed
ubuntu:22.10 passed
redhat/ubi8:8.6 passed
amazonlinux:2022 passed
All distros succeeded

Also do you think we should hook those up to CI?

Yes :)

I agree, and I think we should configure github action to run whenever this file changes only

Great! 🎉 Sorry that I did not hook it up on the previous PR, I just did not want my PR to fix the minor issues with the installer to grow indefinitely.


fix be crash while read orc with mismatch types #30738

Proposed changes
cherry-pick https://github.com/apache/doris/pull/30738
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

@cambyzju  I think we should first push the PR to master branch and then pick to other branch.  Then we will not miss any bugs that is fixed in lower version.

@cambyzju I think we should first push the PR to master branch and then pick to other branch. Then we will not miss any bugs that is fixed in lower version.

@yiguolei master already change to dynamic_cast, and remove down_cast for performance reason.
It is a very big pr, not suitable to cherry-pick it directly.


mismatch in actual width and line_size causing encoder to return jumbled output

Creating a black VideoFrameMut ( https://docs.rs/ac-ffmpeg/latest/ac_ffmpeg/codec/video/frame/struct.VideoFrameMut.html#method.black ) of width: 1200 and height: 800 with libx264rgb as the encoder and pixel_format as rgb24 results in a frame having line_size of 1216. The data buffer is also greater than expected ( 2918400 instead of 2880000 ). This results in the encoding to fail ( or if by some workaround, I'm able to get the video to compile, it appears distorted ).
What's the best way to handle these differences?
If I capture at 1216 by 800. Everything works as expected.

That's a correct behavior. Actually, the line size is supposed to be 3648 bytes (1216 pixels, each pixel is 24 bits). In any case this crate is just a wrapper over FFmpeg libraries. The frame allocation itself is done using av_frame_get_buffer which calculates the buffer size and line size based on the target frame width, height and pixel format (more details here).
Line size is usually larger than the actual frame width because some video encoders require the line buffers to be correctly aligned. All video encoders available via the FFmpeg API (even third party libraries) can handle this and some even require it. If you are using a third party encoder directly (i.e. not via the FFmpeg API), you'll need to adjust the code to take this into account. It all depends on the library. There is no general advice.
When you fill the video frame with image data, you also need to take the line size into account. If you copy the image data from another buffer where the stride (or line size) is different, you can't simply copy the image data as it is into the plane and expect that everything will be fine. It would produce a distorted frame (as you mentioned). Usually, you need to copy the image data line by line. The code could look like this:
fn fill_rgb24_frame(mut input: &[u8], width: usize, height: usize, stride: usize, frame: &mut VideoFrameMut) {
    let plane = &mut frame.planes_mut()[0];

    // we need the width in bytes
    let w = width * 3;

    assert!(stride >= w);
    assert!(plane.line_size() >= w);
    assert!(plane.line_count() >= height);

    for y in 0..height {
        plane
            .line_mut(y)
            .unwrap()[..w]
            .copy_from_slice(&input[..w]);

        input = &input[stride..];
    }
}

The asserts are there mostly for you to understand the invariants.

@operutka
Got it! Thank you!
I read the ffmpeg source code as well but couldn't figure out where the extra buffer was being added.
In any case, this is how I've done it [ For anyone else stumbling on this issue ]
                let mut data_ptr: usize = 0;
                let line_size_to_be_written = (frame.width * 3) as usize;
                for mut line in new_frame.planes_mut()[0].lines_mut() {
                    let _ = line.write(&frame.data[data_ptr..(data_ptr + line_size_to_be_written)]);
                    data_ptr += line_size_to_be_written;
                }

Do you think this is as good as the solution you suggested?
Also do you think there's a performance hit to copying the data line by line rather than all at once? ( Should we only do a line by line copy if the line-size and the width don't match ?
Thanks for all your help and for maintaining this library

Do you think this is as good as the solution you suggested?

I suppose it's good. Provided that the source frame has the same height as new_frame and the source frame stride is equal to the frame width times 3.

Also do you think there's a performance hit to copying the data line by line rather than all at once?

Slice write and copy_from_slice get both optimized down to a memcpy call. Performance wise there really isn't much of a difference between a single memcpy call to copy 2880000 bytes or 800 memcpy calls to copy 3600 bytes. It all depends on the target CPU architecture but, generally, I wouldn't be worried about any performance impact if the line size is 512 bytes or more. And if it's less than 512 bytes then the overall frame size is usually too small to be worried about performance at all.
You can benchmark it if you want. That would probably give you a better answer. In any case, filling the frame with image data does not really cost much compared to video encoding.

Should we only do a line by line copy if the line-size and the width don't match ?

I wouldn't worry about it. Copying image data line by line is quite common. The FFmpeg does the same thing internally: https://ffmpeg.org//doxygen/6.0/imgutils_8c_source.html#l00344


Activating Cluster level logging sends lots of backslashes on fluentd target

Activating Cluster level logging sends lots of backslashes making impossible to read the logs.
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Spin up a new cluster using rancher 2.3-head. I used [INFO] Rancher version 59110e936
Activate cluster logging using fluentd as target. I've used fluentd:v1.7.4-debian-2.0
fluent.conf:
<source>
  @type forward
  port 9881
  bind <IP_ADDRESS>
</source>
<match **>
  @type stdout
</match>

Result:
Many backslashes send in the logged events to fluentd.
Other details that may be helpful:
Environment information

Rancher version : Rancher version` 59110e936
Installation option (single install/HA): Single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): GKE
Machine type (cloud/VM/metal) and specifications (CPU/memory): cloud
Kubernetes version (use kubectl version):

v1.14.8-gke.17

Docker version (use docker version):

18.9.7

Validated Rancher version: 2.3.3 I didn't reproduce the issue.

This seems to happen more often with the "enableJSONParsing": bool cluster level settings enabling and disabling it with the API seems somehow trigger this behavior. @dramich

https://github.com/rancher/rancher/issues/24157

It doesn't seem to be the same scenario. The result is the same for sure but not enabling the enableJSONParsing in 2.3.4-rc3 Makes the logs to behave as expected but as soon as I turn it to true the backslash started flowing. @dramich

Root Cause
Cluster logging will collect logs from many components not all of the logs are in JSON format.
So fluentd will throw a warning level log when we do the parse if it is not a JSON format log. This is expected.
However, rancher fluentd is picking up and processing its own logs, which is causing a feedback loop - every time it reads a log with JSON escaped strings, it has to escape it again before printing, which leads to lots of backslashes to escape other backslashes.
Solution
Use multi_format plugin to avoid fluentd logging warning when parsing the log to JSON if it's not in JSON format.
Step 1: Release a new rancher/fluentd image with multi_format plugin installed
Step 2: Add a new version of logging in system chart to bump the rancher/fluentd version
Step 3: Create a rancher PR to switch to use multi_format.
  <parse>
    @type multi_format
    <pattern>
      format json
    </pattern>
    <pattern>
      format none
    </pattern>
  </parse>

Other
Maybe we should disable it by hiding the Enable JSON Parsing option in UI in 2.3.4

@izaac Just FYI
If you deploy the target fluentd in the k8s cluster, please use file instead of stdout.  Otherwise, you will still hit the similar feedback loop issue even with the fix.
<source>
  @type forward
  port 9881
  bind <IP_ADDRESS>
</source>
<match **>
  @type file
  path /tmp/file
</match>

@izaac, I think we should hold this open until we can add the multiformat plugin and log the fluentd pods to a file. The file should be rotated either by date and/or size so that it doesn't overrun the underlying filesystem.

PRs for fixing this issue
https://github.com/rancher/system-charts/pull/141
https://github.com/rancher/rancher/pull/24763

These issues were validated working after these fixes:
https://github.com/rancher/rancher/issues/24367
https://github.com/rancher/rancher/issues/23646
2.3-head
2019/12/27 16:05:06 [INFO] Rancher version e9a549e59 is starting

Master-head
2019/12/27 16:33:53 [INFO] Rancher version 189e4337c is starting

I'm still going to do a couple of tests on windows nodes as that was also updated as part of these set of changes.

Rancher version: 2.3-head e9a549e59
EC2 setup with

1 master node (etcd/control plane) Ubuntu 18.04.3
1 Linux worker - Ubuntu 18.04.3
1 Windows worker  - Windows_Server-2019-English-Full-ContainersLatest-2019.12.16 (ami-0ff0566e781481cd9)

I activate the fluentd logging and it seems normal, it's no longer showing the backslashes in the logs but the rancher-logging-fluentd-windows pod keeps crashing it stays in Available state for a little while but then it shows:
CrashLoopBackOff: back-off 5m0s restarting failed container=rancher-logging-fluentd pod=rancher-logging-fluentd-windows-gkpmm_cattle-logging(5169351f-9fac-4d53-b077-cd4b58a8f732) |

logging only works in host gw mode. It’s a known issue. I guess you are using vxlan

@loganhz oh yes, I was using vxlan

Verified on 2.3-head latest - commit id: ed6537bfa
Windows setup - AWS nodes
1 all-roles node (etcd/control plane/worker) Ubuntu 18.04.3
1 Windows worker - Windows_Server-2019 container

Fluentd logging was enabled on the cluster
No longer showing the backslashes in the logs - rancher-logging-fluentd


remove code deprecated after 0.7 release

Summary
Removed deprecated code from estimator, sampler, and qiskit_runtime_service.

Removed circuits, observables, and parameters args from sampler and estimator. Also, removed backend_name from runtime_options.
Do we need to remove auth arg from qiskit_runtime_service

Do we need to remove auth arg from qiskit_runtime_service?

Yeah we can remove the auth param - can you also add a release note that highlights all the removals

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 10 (100.0%)  changed or added relevant lines in 2 files are covered.
31 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.8%) to 67.423%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_runtime/utils/deprecation.py
6
50.0%

qiskit_ibm_runtime/runtime_session.py
25
0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
3357

Relevant Lines:
4979

💛  - Coveralls


fix: Split out mria_condition_var to a separate repo

Merging w/o review because this feature is needed fast.


How to use Tailwind CSS?

I installed Tailwind CSS as a PostCSS plugin in Nextra, but when I try to import the .css file inside pages/_app.{mdx|tsx}, I get the following error:
error - ./pages/_app.mdx:7:0
Module not found: Can't resolve '../styles/globals.css'
   5 | /*@jsxRuntime automatic @jsxImportSource react*/
   6 | import $NextImageNextra from "next/image";
>  7 | import '../styles/globals.css';
   8 | const MDXLayout = function App({Component, pageProps}) {
   9 |   return <Component {...pageProps} />;
  10 | };

https://nextjs.org/docs/messages/module-not-found

error - ./pages/_app.tsx:1:0
Module not found: Can't resolve '../styles/globals.css'
> 1 | import '../styles/globals.css';
  2 |
  3 | export default function App({ Component, pageProps }) {
  4 |   return <Component {...pageProps} />;

https://nextjs.org/docs/messages/module-not-found

And if I try to import it in any other file:
./styles/global.css
Global CSS cannot be imported from files other than your Custom <App>. Due to the Global nature of stylesheets and to avoid conflicts, Please move all first-party global CSS imports to pages/_app.js. Or convert the import to Component-Level CSS (CSS Modules).
Read more: https://nextjs.org/docs/messages/css-global
Location: theme.config.tsx

take a look of working example https://github.com/shuding/nextra/blob/main/examples/swr-site/tailwind.config.js

The "working exemple" provided by @B2o5T doesn't work anymore (at least not with the docs theme). Because they removed the prefix from the dark selector. Today, dark selectors most likely look like this "dark:nx-...". Notice there is a prefix on the class name, but not on the dark selector.
Solution
In addition to the steps described in tailwind's documentation Install Tailwind CSS with Next.js. You will have to configure the dark theme selector to work properly. Depending on the theme you chose it may vary but it should look something like (/tailwind.config.js):
/** @type {import('tailwindcss').Config} */
module.exports = {
  prefix: "nx-",
  darkMode: ["class", 'html[class~="dark"]'],
  content: [
    "./components/**/*.{ts,tsx}",
    "./pages/**/*.{md,mdx}",
    "./theme.config.tsx",
  ],
};

Don't remove the nx- prefix (as it would create duplicated CSS classes).
Instead have a look at your theme's tailwind config, for exemple in the docs theme the config is here, and look at how the dark theme selector is defined, copy it to your config.
If needed, here is a more detailed explanation.

Using the above mentioned configuration there is still an issue but I think the problem comes from the docs theme. If I use the nx- prefix and that I use nx-hidden anywhere in my own files it breaks the docs theme (search bar/toc/ and some other components not visible anymore).


Financial examples for SMA and Bollinger don't work

The Cookbook examples PlotTypes: Finance - Simple Moving Average (SMA) and PlotTypes: Finance - Bollinger Bands on the 4.0.44 version don't plot the lines for the indicators.
Runnnig it from Visual studio shows en exception on the output window:
Excepción producida: 'System.OverflowException' en System.Drawing.dll
OverflowException plotting: PlottableScatter (8 day SMA) with 75 points

The exception comes from this line on PlottableScatter.cs:
gfx.DrawLines(penLine, points);
The points array have values like this: {X = 25.7 Y = NaN} May this be the problem?
It works ok on version 4.0.40

By the way, this is a great project, congratulations and thank you very much for your work

Hey @Saklut, thanks for reporting this!
I just noticed that a lot of the latest ScottPlot 4.0 cookbook recipes have issues, usually relating to validation and/or handling of NaN. SMA functions return an array with NaN, causing this problem. I'll leave this issue open reminding me to pull these features out of 4.0 (since they're more fully implemented in 4.1, #639 and #578) and to improve the cookbook.
For a quick fix, I think can you trim-off the values containing NaN like this and it should work 🤞
var plt = new ScottPlot.Plot(600, 400);

// generate sample stock prices
OHLC[] ohlcs = DataGen.RandomStockPrices(null, 75);
double[] xs = DataGen.Consecutive(ohlcs.Length);

// calculate SMAs of different durations using helper methods
double[] sma8xs = xs.Skip(8).ToArray();
double[] sma8ys = Statistics.Finance.SMA(ohlcs, 8);
double[] sma20xs = xs.Skip(20).ToArray();
double[] sma20ys = Statistics.Finance.SMA(ohlcs, 20);

// plot technical indicators as scatter plots above the financial chart
plt.AddCandlesticks(ohlcs);
plt.PlotScatter(sma8xs, sma8ys, markerSize: 0, color: Color.Blue, lineWidth: 2, label: "SMA 8");
plt.PlotScatter(sma20xs, sma20ys, markerSize: 0, color: Color.Navy, lineWidth: 2, label: "SMA 20");

plt.Legend();

Hello,
It works now (first time I use Skip()), I just made a couple of changes to your code above:
// generate sample stock prices
ScottPlot.OHLC[] ohlcs = DataGen.RandomStockPrices(null, 75, sequential: true);    //----
double[] xs = DataGen.Consecutive(ohlcs.Length);

// calculate SMAs of different durations using helper methods
double[] sma8xs = xs.Skip(8).ToArray();
double[] sma8ys = Statistics.Finance.SMA(ohlcs, 8).Skip(8).ToArray();    //----
double[] sma20xs = xs.Skip(20).ToArray();
double[] sma20ys = Statistics.Finance.SMA(ohlcs, 20).Skip(20).ToArray();     //----

// plot technical indicators as scatter plots above the financial chart
plt.PlotCandlestick(ohlcs);
plt.PlotScatter(sma8xs, sma8ys, markerSize: 0, color: Color.Blue, lineWidth: 2, label: "SMA 8");
plt.PlotScatter(sma20xs, sma20ys, markerSize: 0, color: Color.Navy, lineWidth: 2, label: "SMA 20");

plt.Legend();

Thank you very much!

Thanks for following-up @Saklut! I used your code to help improve the Bollinger recipes in the ScottPlot cookbooks:

ScottPlot 4.0 https://swharden.com/scottplot/cookbooks/4.0.47/#plottypes-finance-bollinger-bands

ScottPlot 4.1 https://swharden.com/scottplot/cookbooks/4.1.2-beta/plottable_finance.html#finance_bollinger


Investigate hosting yjs server within GraalJS

Gui2 decided to bet on y.js. In order to avoid back and forth sending of package between processes, let's investigate hosting of the y-websocket server in language server process itself.
Language server process is capable to execute Graal.js - compliant EcmaScript implementation on top of JVM. All that is needed is to polyfill the WebSocket server API.
Initial polyfill is available at https://github.com/JaroslavTulach/graaljs-websocket

Loading y-websocket Server
There is a graalvm/bin/js command to launch Graal.js in the GraalVM. If not, try graal/bin/gu install js. I am able to use that support with:
$ git clone https://github.com/yjs/y-websocket.git
$ cd y-websocket
$ rm -rf *; git checkout -f 05b2f894d5237005b70a3d3ab01f040111371506

$ npm install
$ npm run dist

$ cat >fill.js
function clearTimeout() {
}
function clearInterval() {
}
^D
$ /graalvm/bin/js --experimental-options --js.commonjs-require --js.commonjs-require-cwd=. fill.js ./dist/y-websocket.cjs

e.g. Graal.js (without node.js support) can load y-websocket.cjs and its dependencies.

Using WebPack.js to generate single JavaScript file to send to Graal.js - easier than trying to convince Graal.js to understand mixture of CommonJS and ES6 modules.
See the commit
I assume packing things via webpack is OK, @Frizi? A standard thing among JavaScript developers, right?

A meeting discussing Yjs synchronization with Engine has just finished. Here the meeting notes. Feel free to update them to be more accurate:

Issue: versioning of AST between engine & IDE
@Frizi: can IDE send the code for the y.js to run on the engine side?
is the API going to be simpler if it is AST?
@4e6: gradually move...

step #1: Add UUID to each AST element & use UUIDs in other protocols/places

Question: y.js server in JVM. Good or bad? Proceed?

Pros: eliminates one element of the infrastructure

step #1: run current y.js server in JVM (almost) unchanged

Cons: question of compatibility still remains
Need batch changes without engine seeing "middle stages"

@4e6 prepares a PR to move the server into the JVM.

The strategic vision document has just been written. It describes why this hosting of y.js server in Graal.js is an important enabler.

Everything is ready for consumption by @PabloBuchu & co.


scroll wheel zoom slow?

The scroll wheel zoom in the FormsPlot control feels less responsive than it used to.
Does passing the event to the base control slow it down?

It doesn't feel slow to me anymore. Problem solved? (or never existed)


Feature: Namespace and Name List

what

supports a list of any or all value list

why

Allows multiple various namespace and name patterns that couldn't be matched except with a singular *:*

/test all

/test all

/test all

/test all


Unable To Use In China

Describe the bug

Though chosing CN as server in config UI, it still calls for api.homeconnect.com which won't be able to access data from api.homeconnect.cn
Version of the custom_component

Latest 1.0.0 to 1.1.6

Can confirm the issue.
The API Host should be change to api.home-connect.cn

Actually I manually replace all .com with .cn，which works well.

Please provide the debug log.

i have the same problem even after reboot my home assistant, api.home-connect.cn in configuration.yaml doesn't work


Use bundler for dependencies

Hello @vasile!
Super useful project. Just thought it would be easier for others to get started using Bundler.

Looks good, thank you @pichot !
Any other feedback related with this project or the transit visualizer is welcomed :+1:


Melee/Brawn weapons need editable damage field

[1.5]
Though the latest update to allow characteristic-selection for damage is awesome (:D), weapons that are designated as Melee- or Brawn-based still have their damage field greyed out and forced to 0, which is incorrect for the vast majority of those weapon classes.
For example: a hit with a Melee-skill "Combat Knife" is +1 base weapon damage (before the addition of Brawn) while a "Cortosis Sword" is +2 base weapon damage, etc. Even "Brass Knuckles," which use Brawl, have a +1 base weapon damage.
Having this field unlocked for all weapons would solve the issue. (:

You can add a weapon damage modifier which will give that extra damage.

Greatly appreciate that workaround and, indeed, that's how I'm wrangling it right now. (:
That's a distinctly indirect solution, though, and likely not obvious to anyone that hasn't dug into the Modifiers tabs and all the available options. ):
It also displays inconsistently on the equipment sheet, depending on whether the weapon uses a Characteristic to add damage or not: given a Characteristic, it shows up as a calculated damage base (e.g. "5"); but for weapons that ignore Characteristics (such as lightsabers), you get a crazy value like "0 (6)"?! :D
Additionally, if you open the weapon's sheet, it will still always show "0" for the damage box, which is both inconsistent with other non-Brawl/Melee weapons and unhelpful when attempting to quick-reference, especially for non-technically-adept players. As an added bonus quirk, you sometimes get a little green superscript number above the 0 in the damage box (denoting the damage Modifier), but that only seems to happen for unspecified-Characteristic weapons? :>
I'm still not entirely sure why the "forced to 0" was ever a thing (as melee/brawl weapons have always had a damage value, even when we had the BRAWN? option?) but it's definitely outdated now that you've made the new skill/characteristic separation feature available. (:

Looks like this was done at some point and the issue never got updated. Yay, less work for me!
Thanks for the suggestion and for apparently convincing someone to make the change.


Address mcapp RBAC changes

Address issue:
https://github.com/rancher/rancher/issues/17147
https://github.com/rancher/rancher/issues/17981
Related types PR: https://github.com/rancher/types/pull/726

Add subcommand for updating target projects
Add subcommand for updating members
Add --member, --member-access-type option on install
Add --role option on install/upgrade
Add member/role details in show-app command

Examples:
#update targets command:
1. rancher mcapp add-project myapp mycluster:Project1 mycluster:Project2
2. rancher mcapp delete-project myapp mycluster:Project1 mycluster:Project2
# update member command:
3. rancher mcapp add-member myapp owner user1 user2
4. rancher mcapp delete-member myapp user1 user2
# set members on installation
5. rancher mcapp install --member user1 --member-access-type member --target mycluster:Default mysql myapp
# set roles on install/upgrade
6. rancher mcapp install --role project-owner --target mycluster:Default mysql myapp
7. rancher mcapp upgrade --role project-owner myapp 0.3.8
# show app command
8. rancher mcapp sa myapp
CURRENT   REVISION              CREATED
*         mcapprevision-rhcw9   18 Feb 2019 05:10:39 UTC
          mcapprevision-gmzgh   18 Feb 2019 05:10:00 UTC

CURRENT   VERSION
          0.3.7
*         0.3.8

MEMBER_NAME     MEMBER_TYPE   ACCESS_TYPE
Default Admin   Local User    owner

ROLE_NAME
cluster-owner
project-owner

LGTM

Types RP is merged. Rebased.

@dramich to review

@dramich Addressed above comments.

@dramich Updated

LGTM

Squashed

LGTM


Update mono-mdk to <IP_ADDRESS>

Update url
Reverts https://github.com/caskroom/homebrew-cask/pull/39495

Verified locally.


FloatDomainError (NaN) error if all words have same count or array contains only one word.

words = [   [Apple, 10], [Banana, 10] ]
cloud = MagicCloud::Cloud.new(words, rotate: :none, scale: :log)
img = cloud.draw(800, 600)
file_path = Rails.root.join("tmp", "#{id}.png")
img.write(file_path)
Error performing GenerateWordCloudJob (Job ID: 51ca485a-0dd0-4d75-90b5-30d896165f7b) from Async(default) in 1.1ms: FloatDomainError (NaN):

Fixed by #22 and released as 0.0.5


Not set corectly the home directory

What steps will reproduce the problem?
1.When use protocol SCP with pscp.exe putty not set the home directory
correctly. For Linux System it's ok, so use LINUX system the home directory is
/export/home/userid and this, is seted /home/userid this one not is correct.

What is the expected output? What do you see instead?
pscp.exe, args=-ls -load "" -pw XXXXX -P 22 uiserid@XXX.XXX.XXX.XX:/home/userid

BrowserPresenter - Unable to open /home/xcomgtw: no such file or directory
because the correct is /export/home/userid on LINUX System Sun Solaris 10

What version of the product are you using? On what operating system?
SuperPutty-<IP_ADDRESS> and SuperPutty-<IP_ADDRESS>
Running on Windows 8.

Please provide any additional information below.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 6 Apr 2015 at 8:21

A fix has been committed for this issue. There is now an option in Tools->Options->GUI->File Transfer Options to allow user to define prefix for home directories.


[0.9.4b2] If you have fixed all the UI scaling issues, then another beta for testing please...

I really want to start to use 0.9 in production, but I can't until there is a version whose UI is usable on my Surface 3 Pro...

The remaining scaling "issues" have been addressed with PR 2394. There's a very ugly bug in wxpython that does not properly set bitmaps with a defined size on systems with a display user scale of more than 150% (at least that's the boundary on my system). Out of a sudden bitmaps are used and displayed enlarged....
I had to circumvent this by scaling some images down to counterbalance that unwanted blowup to achieve a defined pixel size. So on systems with scaling beyond that boundary images actually look again a bit more pixely than you would expect. Even with the current beta you can achieve correct sizing if you would reduce the user scale below the 150% threshold.

Then can I please have a new executable to test with?

I'll push up the beta stuff. Gotta do some bug fixes and a version bump. And the numba dither stuff needs to be tested in .exe form to make sure it's fine.

https://github.com/meerk40t/meerk40t/releases/tag/0.9.3020

I'll try the new beta next time I am burning.


PR committees

There are issues related to both committee names and urls here, it will be quicker to fix it in the scraper and run a new import and push that up, so that's what I will do.

Made a mistake by accidentally deleting a few files, and some other issues during lint fixes. Closing this PR and will push a fresh data collection and make a new PR where lint fixes can be resolved correctly.


This package installs and launches normally in a Windows 10 VM.


Refactor state space using a graph approach

I refactored the state space using a graph-based approach to increase the use of different maps. You can now incorporate any map, including maps with obstacles, by passing in a string representing the map (x = obstacle, o = open space).

Codecov Report
Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (91e71f7) 84.74% compared to head (8e92121) 96.17%.

Files
Patch %
Lines

src/transition.jl
94.44%
4 Missing :warning:

src/visualization.jl
97.22%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main       #6       +/-   ##
===========================================
+ Coverage   84.74%   96.17%   +11.43%
===========================================
  Files           7        8        +1
  Lines         295      340       +45
===========================================
+ Hits          250      327       +77
+ Misses         45       13       -32

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update stable version in repo from 0.0.3 to 0.1.7

Think about update stable version to 0.1.7
Version: stable=0.0.3 (556 days old) => latest=0.1.7 (15 days old)
Installs: stable=685 (75.61%), latest=83 (9.16%), total=906
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 0.1.7 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

see https://github.com/TA2k/ioBroker.bosch-ebike/issues/17

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 0.1.7 but in the meantime an update to version 0.1.9 is suggested.
So this issue will be closed and replaced by an updated one.
@mcm1957 for evidence


Add SpringBoot demo instrument with otel.

Add springboot demo, the same application with skywalking-demo, but trace data with otel-agent.
otel-agent build from https://github.com/open-telemetry/opentelemetry-java-instrumentation, and use as a sidecar.(auto instrument)

@mytting please review


Add Storybook

Current broken look:

While adding Storybook is more achievable and important now than ever before, this PR isn't going to be more helpful than starting from scratch.


A11y_SQL database projects extension_Create Project From Database_Create Project_Status Message: NVDA is not announcing the loading message which is appearing after activating the create button.

GitHub Tags
#A11yTCS; #A11ySev2; #DesktopApp; #Status Message; #WCAG4.1.3; #Win11; #SH-SQL Azure Data Studio-Win32-March23; #Win32; #SQL Azure Data Studio; #NVDA; #A11yWCAG2.1; #Screenreader;
Environment Details
Application Name: SQL Azure Data Studio
Version: 1.41.2 (user setup)
Microsoft Windows 11 Enterprise 10.0.22621 Build 22621
Screen reader: NVDA
Repro Steps

Turn on NVDA.
Launch Azure Data Studio
Tab till extension and search for “SQL Database Projects” and install it.
Tab till database project and press enter. “Database Project” panel will open.
Tab till “View and More Action” button and press enter.
Tab till “Create Project From Database” and press enter.
Tab till server field and press enter. “Connection” dialog will open. Fill the details for SQL server and connect.
Tab till Create button and press enter.
Verify whether the NVDA is announcing the loading message which is appearing after activating the create button or not.

Actual Result
NVDA is not announcing the loading message which is appearing after activating the create button.
Note
Similar issue observed in the below screen.

Database project->Publish project-> Generate script

Expected Result
NVDA should announce the loading message which is appearing after activating the create button.
User Impact
Screen reader user will not be able to get the proper information like whether the data base is created or still it is creating or not.
Attachment

@Samhitha66 this has been fixed in the latest version of the sql database projects extension (0.23.0). Please download the latest insiders build and verify this is fixed. Thanks!


Fix #1127 Revert sort activities

Due to #1127 and the complications of the fix, we are reverting #1107 for now.

Self-approving reverts.


New sample - Unique Reaction - Like or Dislike (similar to YouTube)

New sample - Unique Reaction - Like or Dislike (similar to YouTube reactions)

Q
A

Bug fix?
no

New sample?
yes

Related issues?
none

What's in this Pull Request?
This is a sample demonstrates the usage of the setValue action and array manipulation using removeFrom and appendTo on multiple fields at the same time, by creating buttons to like/dislike an item and updating two multi-person fields, one used to save the likes (people who liked), the other one to save the dislikes (people who disliked).
A user can only either like or dislike an item, if an item is liked by the current and is disliked, the like is undone and vice-versa (similar to what happens in YouTube).

Thank you @michelcarlo. Awesome stuff! 👏👏💜🧡

Thank you @michelcarlo. Awesome stuff! 👏👏💜🧡

No worries, thanks for approving my sample😁😁


The setting.toml file is really not aligned with current code version

When tryin to use the current madninja/hpr branch, the setting.toml is nt compatibe with the current branch version

update block is missing
packet_router does not exists
potnetially some otehr

When tryin to use the current madninja/hpr branch, the setting.toml is nt compatibe with the current branch version

update block is missing
packet_router does not exists
potnetially some otehr

gateway-rs no longer supported the self-updater and releases only compiled application binaries.
packet_router does not exist because it's under [router] in settings.toml. https://github.com/helium/gateway-rs/blob/main/config/settings.toml#L46-L51

Do you actually see it not working?

Yes, sorry for this, that was a problem in my build, I was still using the previous version with the new setting file.
Now it's working, but I did note another change than can impact people migrating, -c was getting a directory and now, it seems that you need to pass the setting.toml file directly.
The previous approach with a default.toml file overrided by the settings.toml file was really usefull when manging mulitple gateway-rs in a single serve to be used with classicla loRaWn gateways. It would be great to keep this previous behavior

Yes, sorry for this, that was a problem in my build, I was still using the previous version with the new setting file.
Now it's working, but I did note another change than can impact people migrating, -c was getting a directory and now, it seems that you need to pass the setting.toml file directly.
The previous approach with a default.toml file overrided by the settings.toml file was really usefull when manging mulitple gateway-rs in a single serve to be used with classicla loRaWn gateways. It would be great to keep this previous behavior

Having the file file setup was only useful because the previous release mode included packaged releases which meant it required a baseline settings followed by override. Since this repo no longer ships packaged releases, the dual file setup caused too many issues for folks not knowing which file needed to be edited. For your configuration, you would use your own settings.toml.template and replace attributes during a deploy step?

Closing this as unplanned.
You can use environment variables to override settings.toml entries


Bump coffeescope2

Due to a coffeescope2 regression in coffeescript 1.11 some scoping errors might not have been
caught

Landed in<EMAIL_ADDRESS>


Changelog of Major Revisions

Just noticed that the root key was changed from a pluralized resource name to data. At first I thought I was going crazy. It would be very nice to have a list of the major revisions to the spec.

We had https://github.com/json-api/json-api/pull/341 as a huge discussion about all these changes.
We will be updating http://jsonapi.org/#update-history with any changes that happen post 1.0, which are expected to be entirely additive, and very, very few. but pre 1.0 it's very difficult to maintain one, so we haven't.


Global dev mode

Closes #91

Only just realised there was more commits in here than there should've, oh well xD


ref(scheduler): clean up scheduler with better organisation

This doesn't touch logic, only moves things around within the k8s.py in the first commit and then in turn makes it the __init__
It's a very simplified version of #48 - again, no code modifications here. Just sets the stage for more refactoring down the line

Do you need me to test this?

I'd love if you could throw it on your cluster and run the integration tests against a real k8s cluster since we have no k8s tests, barely any mocking for it even.

@helgi ok, will test shortly

@helgi I built and pushed my own image with make docker-build docker-push and replaced the existing workflow RC with mine in a stock helm cluster. Seems to fail to come up:
ENG000656:example-go aaronschlesinger$ kd logs -f deis-workflow-zsg3a
Syncing...
Creating tables ...
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
Migrating...
Running migrations for authtoken:
- Nothing to migrate.
 - Loading initial data for authtoken.
Installed 0 object(s) from 0 fixture(s)
Running migrations for api:
 - Migrating forwards to 0026_auto__chg_field_config_tags__chg_field_config_values__chg_field_config.
 > api:0001_initial
Traceback (most recent call last):
  File "./manage.py", line 13, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 415, in handle
    return self.handle_noargs(**options)
  File "/usr/lib/python2.7/site-packages/south/management/commands/syncdb.py", line 103, in handle_noargs
    management.call_command('migrate', **options)
  File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 159, in call_command
    return klass.execute(*args, **defaults)
  File "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/site-packages/south/management/commands/migrate.py", line 111, in handle
    ignore_ghosts = ignore_ghosts,
  File "/usr/lib/python2.7/site-packages/south/migration/__init__.py", line 220, in migrate_app
    success = migrator.migrate_many(target, workplan, database)
  File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 256, in migrate_many
    result = migrator.__class__.migrate_many(migrator, target, migrations, database)
  File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 331, in migrate_many
    result = self.migrate(migration, database)
  File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 133, in migrate
    result = self.run(migration, database)
  File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 106, in run
    south.db.db.current_orm = self.orm(migration)
  File "/usr/lib/python2.7/site-packages/south/migration/migrators.py", line 281, in orm
    return migration.orm()
  File "/usr/lib/python2.7/site-packages/south/utils/__init__.py", line 62, in method
    value = function(self)
  File "/usr/lib/python2.7/site-packages/south/migration/base.py", line 443, in orm
    return FakeORM(self.migration_class(), self.app_label())
  File "/usr/lib/python2.7/site-packages/south/orm.py", line 48, in FakeORM
    _orm_cache[args] = _FakeORM(*args)
  File "/usr/lib/python2.7/site-packages/south/orm.py", line 127, in __init__
    self.models[name] = self.make_model(app_label, model_name, data)
  File "/usr/lib/python2.7/site-packages/south/orm.py", line 324, in make_model
    field = self.eval_in_context(code, app, extra_imports)
  File "/usr/lib/python2.7/site-packages/south/orm.py", line 235, in eval_in_context
    raise ValueError("Cannot import the required field '%s'" % value)
ValueError: Cannot import the required field 'json_field.fields.JSONField'

@arschles I did some fixes in there but I haven't had time to properly test it myself

@arschles I did some fixes in there but I haven't had time to properly test it myself

@helgi did some testing with this. TL;DR is LGTM
Longer explanation: it starts up fine from an empty DB (migrations don't seem to work, but that's expected afaik), and registering, adding keys and git push all work.
However, the app doesn't seem to be running after the git push. deis info says the app is up and a domain exists for it of the expected name, but the app is inaccessible via curl.
Upon talking with you and @krancour I understand this bug may be happening because router and workflow don't agree on the annotations used for domain handling. Is that issue tracked somewhere (perhaps here?) Logs below.
Startup:
ENG000656:example-go aaronschlesinger$ kd logs -f deis-workflow-3uhat
system information:
Django Version: 1.9
Python 2.7.10
Operations to perform:
  Apply all migrations: authtoken, sessions, admin, guardian, sites, auth, contenttypes, api
Running migrations:
  Rendering model states... DONE
  Applying contenttypes.0001_initial... OK
  Applying auth.0001_initial... OK
  Applying admin.0001_initial... OK
  Applying admin.0002_logentry_remove_auto_add... OK
  Applying api.0001_initial... OK
  Applying api.0002_auto_20151215_0352... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0002_alter_permission_name_max_length... OK
  Applying auth.0003_alter_user_email_max_length... OK
  Applying auth.0004_alter_user_username_opts... OK
  Applying auth.0005_alter_user_last_login_null... OK
  Applying auth.0006_require_contenttypes_0002... OK
  Applying auth.0007_alter_validators_add_error_messages... OK
  Applying authtoken.0001_initial... OK
  Applying guardian.0001_initial... OK
  Applying sessions.0001_initial... OK
  Applying sites.0001_initial... OK
  Applying sites.0002_alter_domain_unique... OK
[2016-01-05 00:27:25 +0000] [132] [INFO] Starting gunicorn 19.4.1
[2016-01-05 00:27:25 +0000] [132] [INFO] Listening at: http://<IP_ADDRESS>:8000 (132)
[2016-01-05 00:27:25 +0000] [132] [INFO] Using worker: sync
[2016-01-05 00:27:25 +0000] [139] [INFO] Booting worker with pid: 139
[2016-01-05 00:27:25 +0000] [140] [INFO] Booting worker with pid: 140
[2016-01-05 00:27:25 +0000] [141] [INFO] Booting worker with pid: 141
Publishing DB state to etcd...
Done Publishing DB state to etcd.
deis-controller running...

Registering, saving key, pushing:
ENG000656:example-go aaronschlesinger$ deis register deis.<IP_ADDRESS>.xip.io
username: arschles
password:
password (confirm):
email<EMAIL_ADDRESS>Registered arschles
Logged in as arschles
ENG000656:example-go aaronschlesinger$ deis apps
=== Apps
ENG000656:example-go aaronschlesinger$ deis keys:add ~/.ssh/id_rsa.pub
Uploading id_rsa.pub to deis... done
ENG000656:example-go aaronschlesinger$ deis create gotest
Creating Application... done, created gotest
Git remote deis added
remote available at ssh://git@deis.<IP_ADDRESS>.xip.io:2222/gotest.git
ENG000656:example-go aaronschlesinger$ git push deis master
The authenticity of host '[deis.<IP_ADDRESS>.xip.io]:2222 ([<IP_ADDRESS>]:2222)' can't be established.
ECDSA key fingerprint is SHA256:LU+BUQcukbLu72ab+Q8hgTCfFzKYgUk2R7S5pJq+scg.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[deis.<IP_ADDRESS>.xip.io]:2222,[<IP_ADDRESS>]:2222' (ECDSA) to the list of known hosts.
Counting objects: 273, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (128/128), done.
Writing objects: 100% (273/273), 3.02 MiB | 669.00 KiB/s, done.
Total 273 (delta 151), reused 241 (delta 131)
-----> Starting build
-----> Go app detected
-----> Checking Godeps/Godeps.json file.
-----> Installing go1.4.2... done
-----> Running: godep go install -tags heroku ./...
-----> Discovering process types
       Procfile declares types -> web
-----> Compiled slug size is 4.7M
-----> Build complete.
-----> Launching app.
-----> Launching...
       done, gotest:v2 deployed to Deis

       http://gotest.localhost

       To learn more, use `deis help` or visit http://deis.io

To ssh://git@deis.<IP_ADDRESS>.xip.io:2222/gotest.git
 * [new branch]      master -> master
ENG000656:example-go aaronschlesinger$ deis info
=== gotest Application
updated:  2016-01-05T00:29:55UTC
uuid:     05325e2e-58be-49b3-b2d4-8df7bbc4de42
created:  2016-01-05T00:28:43UTC
url:      gotest.localhost
owner:    arschles
id:       gotest

=== gotest Processes
--- web:
web.1 up (v3)

=== gotest Domains
gotest

also @helgi can you remove the in progress label before you merge?

Is that issue tracked somewhere?

No... it was a transient issue that occurred because there was a router PR and a workflow PR that were complimentary and should have been merged in tandem, but were not.

Ah ok. Ran into the router issue...
Created, scaled up/down, created config... Looks ok

@krancour I see, makes sense.


Create a Glyph component

The Text component is not well suited to glyph positioning. Create a new component specifically for individual glyphs.

Just playing around:
>>> font.glyph_metrics("A").y_min.units()
0
>>> font.glyph_metrics("a").y_min.units()
-20
>>> font.glyph_metrics("y").y_min.units()
-437
>>> font.glyph_metrics("A").y_max.units()
1456
>>> font.glyph_metrics("a").y_max.units()
1102
>>> font.glyph_metrics("W").y_max.units()
1456
>>> font.glyph_metrics("t").y_min.units()
-20

I guess y_min and y_max are relative to the base line.

And here we can compare the font ascent/descent to our glyph y_min and y_max
>>> font._pil_font.getmetrics()
(28, 8)
>>> font.glyph_metrics("M").y_max.to_points(30)
21.328125
>>> font.glyph_metrics("y").y_min.to_points(30)
-6.4013671875

Glyph.width() is implemented now.
Todo:

Glyph.width()
Glyph.draw() x offset is x_min.
Glyph.draw() y offset is font ascent minus y_max converting design units to pixels as required.
Create a bounding box test to make sure draw() is aligning properly.
Check in icon grid demo and icon size demo.

Height works. Now for offsets.

Implemented draw(). Still looks weird.

Yeah, not working. Width includes space to right of glyph.

Ahh, was using "width" not "fullwidth"

Seems to work perfectly now. Might need to choose another font.


update repo to conform to org standards

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Swagger2Markup 1.3.4 jar is missing in maven central

👋  just a reminder that Swagger2Markup 1.3.4 jar does not exist in maven central. Thanks!

Hello @chenrui333, Are you talking about this --> https://search.maven.org/search?q=g:io.github.swagger2markup

I can see the the new 1.3.4 under maven repository also -->https://mvnrepository.com/artifact/io.github.swagger2markup/swagger2markup , and I am also able to download jar from there

I was referring to this one, https://repo1.maven.org/maven2/io/github/swagger2markup/swagger2markup-cli/

update my issue title to avoid confusion.

Actually I haven't made a new release for the swagger2markup cli yet, only the new release for swagger project is out

So its not exactly missing, the bits related to the swagger2markup projects are out, on the other hand swagger2markup cli is a different project

@chenrui333 I hope it answers your question

I see, that makes sense. 😅  Thanks for clarifying so responsively!


Feature/git lab

This fixes a part of issue #669 .  It seems the files weren't being read properly from gitlab.  Changing to the new V4 API solves this and is more future proof.

Bumped the builds (both of the pr builds failed due to time limits, we may need to audit our tests and determine which ones can run too long)

Changes Unknown when pulling f2320a7caa42a6a2880dea9dd9b99f90ac571443 on feature/gitLab into ** on develop**.