text:
can use docker compose deploy?

Proposal
one docker-compose deploy all service open : 4200
Use-Case
No response
Is this a feature you are interested in implementing yourself?
No

Hi, please provide more details in the issue - I'm not sure what exactly you're looking for.
We currently have a docker-compose file in the repo for both local development and production.
Have you tried running it? If so, are you getting any errors? If you do, share them please.

原諒我用中文
英文不好怕有誤會
一開始使用docker dev
只會啟動部分服務
轉成不使用dev
開始測試每個問題
針對.env的參數慢慢了解跟修改
有不少的問題
但是後來我解決
直到全部的服務都能啟動成功
但是實際上並非真的成功
pezzo_pezzo-server_1  log
Prisma onModuleInit error PrismaClientInitializationError: Database pezzo does not exist on the database server at postgres:5432.
at kr. (/app/node_modules/@prisma/client/runtime/binary.js:157:3075)
$ at kr.emit (node:events:513:28)
at addChunk (node:internal/streams/readable:324:12)
? at readableAddChunk (node:internal/streams/readable:297:9)
= at Readable.push (node:internal/streams/readable:234:10)
at kr._pushBuffer (/app/node_modules/@prisma/client/runtime/binary.js:75:369)
at kr._transform (/app/node_modules/@prisma/client/runtime/binary.js:75:199)
@ at Transform._write (node:internal/streams/transform:175:8)
= at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10) {
 clientVersion: '5.1.1',
 errorCode: 'P1003'
}
�[Nest] 1 - 09/03/2023, 9:56:09 AM  LOG [NestApplication] Nest application successfully started +113ms
�[Nest] 1 - 09/03/2023, 9:56:09 AM  LOG 🚀 Application is running on: http://localhost:3000/api
直到server started
再開啟 pezzo_pezzo-console_1 log
LReplacing environment variable "[object Object]" with value [object Object]
Updated environment variables
2023/09/03 09:58:40 [notice] 1#1: using the "epoll" event method
/2023/09/03 09:58:40 [notice] 1#1: nginx/1.20.2
2023/09/03 09:58:40 [notice] 1#1: built by gcc 10.3.1 20210424 (Alpine 10.3.1_git20210424)
>2023/09/03 09:58:40 [notice] 1#1: OS: Linux 5.15.0-79-generic
2023/09/03 09:58:40 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2023/09/03 09:58:40 [notice] 1#1: start worker processes
:2023/09/03 09:58:40 [notice] 1#1: start worker process 18
:2023/09/03 09:58:40 [notice] 1#1: start worker process 19
:2023/09/03 09:58:40 [notice] 1#1: start worker process 20
:2023/09/03 09:58:40 [notice] 1#1: start worker process 21
我就到這步驟失敗了
再請幫忙找原因
謝謝

Two questions come to mind:

Have you applied the database migration after spinning up the Docker images (as shown in the readme)?

Perhaps you already have a Postgres DB running on the same port?

猜測
我的postgres是否需要重新使用，還是一切都要重新使用，因為好像DB沒有自動建立??找不到DB
docker-compose.yaml
`
version: "3"
services:
postgres-pezzo:
image: postgres:latest
restart: always
environment:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: postgres
ports:
- "5433:5432"
volumes:
- postgres_data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U postgres"]
interval: 5s
timeout: 5s
retries: 3
supertokens:
image: supertokens/supertokens-postgresql:5.0
restart: always
ports:
- "3567:3567"
environment:
POSTGRES_CONNECTION_URI: postgres://postgres:postgres@postgres-pezzo:5432/supertokens
pezzo-server:
image: ghcr.io/pezzolabs/pezzo/server:latest
restart: always
env_file:
- ./.env
- ./apps/server/.env
environment:
- DATABASE_URL=postgres://postgres:postgres@postgres-pezzo:5432/pezzo
- SUPERTOKENS_CONNECTION_URI=http://supertokens:3567
- OPENSEARCH_URL=http://opensearch-node1:9200
- REDIS_URL=redis://redis-stack-server:6379
ports:
- "3000:3000"
depends_on:
postgres-pezzo:
condition: service_healthy
healthcheck:
test: ["CMD-SHELL", "curl 'http://pezzo-server:3000/api/healthz'"]
interval: 5s
timeout: 5s
retries: 3
pezzo-console:
image: ghcr.io/pezzolabs/pezzo/console:latest
restart: always
env_file:
- ./.env
- ./apps/console/.env
ports:
- "4200:8080"
depends_on:
pezzo-server:
condition: service_healthy
opensearch-node1:
image: opensearchproject/opensearch:2.5.0
container_name: opensearch-node1
environment:
- cluster.name=opensearch-cluster
- node.name=opensearch-node1
- discovery.type=single-node
- bootstrap.memory_lock=true
- "plugins.security.disabled=true"
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
volumes:
- opensearch-data1:/usr/share/opensearch/data
ports:
- 9200:9200 # REST API
- 9600:9600 # Performance Analyzer
deploy:
resources:
limits:
memory: 3g
opensearch-dashboards:
image: opensearchproject/opensearch-dashboards:2.5.0
container_name: opensearch-dashboards
ports:
- 5601:5601
expose:
- "5601"
environment:
- "DISABLE_SECURITY_DASHBOARDS_PLUGIN=true"
- "OPENSEARCH_HOSTS=http://opensearch-node1:9200"
redis-stack-server:
image: redis/redis-stack-server:7.2.0-v0
container_name: redis-stack-server
ports:
- "6379:6379"
volumes:
postgres_data: ~
opensearch-data1:
`
server
Prisma onModuleInit error PrismaClientInitializationError: Database pezzodoes not exist on the database server atpostgres-pezzo:5432`.
at kr. (/app/node_modules/@prisma/client/runtime/binary.js:157:3075)
$ at kr.emit (node:events:513:28)
at addChunk (node:internal/streams/readable:324:12)
? at readableAddChunk (node:internal/streams/readable:297:9)
= at Readable.push (node:internal/streams/readable:234:10)
at kr._pushBuffer (/app/node_modules/@prisma/client/runtime/binary.js:75:369)
at kr._transform (/app/node_modules/@prisma/client/runtime/binary.js:75:199)
@ at Transform._write (node:internal/streams/transform:175:8)
= at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10) {
 clientVersion: '5.1.1',
 errorCode: 'P1003'
}
�[Nest] 1 - 09/04/2023, 3:50:26 AM  LOG [NestApplication] Nest application successfully started +130ms
�[Nest] 1 - 09/04/2023, 3:50:26 AM  LOG 🚀 Application is running on: http://localhost:3000/api`
console
`
LReplacing environment variable "[object Object]" with value [object Object]
Updated environment variables
2023/09/04 03:50:54 [notice] 1#1: using the "epoll" event method
/2023/09/04 03:50:54 [notice] 1#1: nginx/1.20.2
2023/09/04 03:50:54 [notice] 1#1: built by gcc 10.3.1 20210424 (Alpine 10.3.1_git20210424)
>2023/09/04 03:50:54 [notice] 1#1: OS: Linux 5.15.0-79-generic
2023/09/04 03:50:54 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2023/09/04 03:50:54 [notice] 1#1: start worker processes
:2023/09/04 03:50:54 [notice] 1#1: start worker process 18
:2023/09/04 03:50:54 [notice] 1#1: start worker process 19
:2023/09/04 03:50:54 [notice] 1#1: start worker process 20
:2023/09/04 03:50:54 [notice] 1#1: start worker process 21
�192.168.1.1 - - [04/Sep/2023:03:51:28 +0000] "GET / HTTP/1.1" 200 1074 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36 Edg/116.0.1938.69" "-"
192.168.1.1 - - [04/Sep/2023:03:51:28 +0000] "GET /main.b6486433444435ff.css HTTP/1.1" 200 5809 "http://192.168.1.103:4200/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36 Edg/116.0.1938.69" "-"
192.168.1.1 - - [04/Sep/2023:03:51:28 +0000] "GET /runtime.4566db95c916845e.js HTTP/1.1" 200 2215 "http://192.168.1.103:4200/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36 Edg/116.0.1938.69" "-"
192.168.1.1 - - [04/Sep/2023:03:51:29 +0000] "GET /main.88f9fa1f9fe10527.js HTTP/1.1" 200 3703844 "http://192.168.1.103:4200/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36 Edg/116.0.1938.69" "-"
�192.168.1.1 - - [04/Sep/2023:03:54:44 +0000] "GET / HTTP/1.1" 304 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36 Edg/116.0.1938.69" "-"
`

Apologies, but I cannot understand much from this. Are you able to communicate in English? Are you still facing issues?

可以参考这个步骤，我这边已经运行起来了。用最新版本的镜像就行了，但是为了防止未来的更新引入bug 。可以修改  docker-compose.yaml 固定 server 和 console 的版本

安装环境
启动docker compose
迁移数据库
重启 cokercompose

Just use the latest version of the image, but to prevent future updates from introducing bugs. You can modify 'docker-compose.yaml' to fix the server and console versions

迁移数据库
這段我缺少在哪看呢?

项目首页，参考一下 dev那块，我电脑已经关机了
明天找找
---Original---
From: @.>
Date: Wed, Sep 6, 2023 19:46 PM
To: @.>;
Cc: @.@.>;
Subject: Re: [pezzolabs/pezzo] can use docker compose deploy? (Issue #181)
迁移数据库
這段我缺少在哪看呢?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

我開始懷疑我自己有誤解的地方了
是不是要按照他全部的動作執行??
我以為是一個docker-compose up -d
就能跑 4200了??

不是。除了这个。还需要进行两个操作

在 .env加入  openai key(具体是啥忘了，看报错)
数据库迁移

最重要的一点是，使用最新版本的镜像。前几个版本的镜像都有bug,已经在最新版本修复了
---Original---
From: @.>
Date: Wed, Sep 6, 2023 20:02 PM
To: @.>;
Cc: @.@.>;
Subject: Re: [pezzolabs/pezzo] can use docker compose deploy? (Issue #181)
我開始懷疑我自己有誤解的地方了
是不是要按照他全部的動作執行??
我以為是一個docker-compose up -d
就能跑 4200了??
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

恩 .env  TESTER_OPENAI_API_KEY確實是作者漏掉的重點
這個我一開始有看影片確定過
但是數據庫遷移
哈 我還是找不到 那我應該就是缺這個而已
畢竟我在怎麼搞 他都告訴我他找不到DB
我就是在是不是他沒有初始化DB的動作
應該在docker啟動的時候連上DB就應該要做初始化就好了
這只是我的想法
感謝你的回復

The conclusion here based on my understanding is:

Adding the TESTER_OPENAI_API_KEY to the documentation so it's clearer that it's in use.
An idea to automatically run DB migrations when running docker-compose. I think that's a good idea.

I'll close this for now, and address the issues separately. Thank you for the discussion!

repo: pezzolabs/pezzo


text:
why use YUV instead of RGB

Can anyone tell me why not use RGB ?

Actually, I am curious about why you expand the one channel to 3 channels by filling them with the -512 or 128
what do the numbers mean?
and what does the 1st to 4th channels mean?

Y channel is black and white, so it has more clear relation with line drawing input channel. ( maybe
see also http://tinyclouds.org/colorize/

I got you. Thank you very much.

source: gharchive/issue

authors: czxrrr taizan

repo: pfnet/PaintsChainer

license: mit

license_type: permissive

license_source: bigquery


text:
Use keyword argument

compiler is a keyword argument.
fix #1557

LGTM

source: gharchive/pull-request

authors: gwtnb unnonouno

repo: pfnet/chainer

license: MIT

license_source: github-api


text:
QA and deploy of Arrival Advisor currently in staging

ACs:

When in surrey and looking up Public Libraries, manual recommendations include
When in Burnaby and looking up , manual recommendations include

TODO

Find new services in BC211.

Then:

Update recommendation files

Run the server side prepare deploy script with the correct client and server versions, and recommendation files

Upload data.json to AWS

Log into heroku (staging) $ heroku ps:exec -a fierce-ravine-89308

Set environment variables per the server side README: Take the variables from export DJANGO_SETTINGS_MODULE=co..., copy into pico, edito the value for DATABASE_URL to the value from the correct heroku instance -> Settings -> Reveal config vars -> database url, copy paste into the heroku shell.
heroku$ wget <s3-url-to-data.json>
heroku$ ./manage.py flush
heroku$ ./manage.py loaddata data.json

Test in staging, if all is good

Make a new client build, publish it to both stores with Ben's help
When review is passed and we're ready to publish the client:
On heroku web site, promote staging to production
Log into production server and update DB as above, * Log into heroku (production) $ heroku ps:exec -a pathways-production, and follow the same steps as above.

why only Surrey and Burnaby?

authors: ArtiBPG rasmus-storjohann-PG

repo: pg-irc/pathways-frontend


text:
Remove answer Id from google analytics event

There is no reason to be collecting ids of chosen answers in google analytics.
Acceptance Criteria

[ ]  Answer Id is no longer collected through google analytics.

@rasmus-storjohann-PG Please reverse this ASAP. This was not approved.
We need that data to know general demographics and status of our users. It was discussed yesterday that the messaging on our presentation will be updated to reflect what how we treat data collected through .

Note: I asked Ian to close this issue.


text:
add cson parser

add cson parser -   I'll do this PR when I get a chance just making an issue as a reminder

no need for special parser just need to a cson as ext of coffee parser (works with -A).  That;s an easy PR

Awesome! Awaiting the PR

thx for doing this...been busy

No problem

authors: dkebler pgilad

repo: pgilad/leasot


text:
Issue all around - package conflict.

Hello.
Since the last Xamarin / Android SDK update seems like the package failed on every VS installation, and it is incompatible practically with anything anymore..
Please Panagiotis Georgiou Stathopoulos help with solving this issue.
This is a copy/past from the Error list from a blank Android app with just this package on it.
Severity	Code	Description	Project	File	Line	Suppression State
Warning		Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Configuration" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Data.SqlXml" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Security" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Xml" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Core" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="mscorlib" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding>	App5	C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets	2113
Severity	Code	Description	Project	File	Line	Suppression State
Warning		Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Configuration" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Data.SqlXml" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Security" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Xml" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Core" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="mscorlib" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" /></dependentAssembly></assemblyBinding>	App5	C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets	2113

I did not had the opportunity to test it. You are referring to the nuget package? I can not read the Error information.

authors: YordanYanakiev pgstath


text:
visual feature extraction

"When using different splits to train a visual feature extractor (e.g., ST-GCN), do you use the entire visible feature test set as the validation set? How can we ensure that, while training solely on the visible feature training set, the accuracy on the visible feature test set reaches around 93% instead of around 82% (as reported in the ST-GCN paper)? If you can see this, please address my concerns. Thank you."

Hi,
Thanks for your question. We only use seen classes extracted from the entire validation set to test our model. As we use only the seen classes to train and test our model, this makes the problem simpler or harder depending on the selection of the unseen classes. Thus you can't directly compare these two performance numbers.
Thanks,
Oscar

Hello, first of all, thank you for your response. Perhaps due to the lack of clarity in my initial question, I’ll try to express it more thoroughly this time.
I noticed that in the visual feature files, there is a val.npy file, whose size matches the size of the test set after excluding the unseen classes. I assume you trained the skeleton feature extraction module on all seen classes in the training set and then validated it on all seen classes in the test set. However, I also noticed another file, val_out.npy, which should represent the classification scores of the validation set. Comparing this with the real labels of the validation set’s seen classes in the val_label.npy file, I found that the accuracy is close to 93%. If you trained only on all seen classes in the training set, the model should not reach such high accuracy.
Could you clarify if the skeleton extraction framework is trained solely on all seen class data from the original training set? Or does it also include some seen class data from the original test set?


text:
pullRequest' returns a Parse Error

Hi,
I've been trying to use the GitHub API to get the SHA of the head commit for every pull request in a repo. However, the function pullRequest' has a run-time error which returns:

ParseError "Error in $['mergeable_state']: expected MergeableState, encountered String"

When I create my own request using pullRequestR and run it with executeRequestWithMgr, I get the same error. I have not managed to find a solution. Could this be a bug?
Thanks

Can you try with a master branch version, iirc something like that is fixed, and I'm soon (this week) making a release

Hi!
I have indeed tried it with the most recent version, and it works as expected.
Thank you very much!

authors: nicaudinet phadej

repo: phadej/github


text:
Consider dropping PHP 7.0 support for Zephir/Phalcon before Phalcon 4 is released

Consider cutting PHP 7.0 support for the Phalcon 4.0 release.  Currently CentOS/RHEL only has PHP 5.4 and so an updated package would already be needed and its likely that they would skip straight to PHP 7.2.  It appears that Debian is the only significant distro that is back on specifically 7.0 and they will be releasing a new version with probably 7.2 by the middle of 2019.
If PHP 7.0 is dropped then its less conditionals in the code and more time to support future PHP versions and more possibilities for taking advantage of newer PHP internals.
PHP Supported Versions
It doesn't seem to me that you will be missing much by dropping PHP 7.0 for a mid 2019 release.  If CentOS was already on PHP 7.0 by default then I'd say that it was good reason to stay back but its already incompatible as it is now.
You will pay a maintenance and development cost for support 7.0 and I don't believe that you will get much out of it other than the marketing jingle "PHP 7".  You seem to have a lot of time now but what about tomorrow?  Something could happen in your life and then you will have very limited time.  Its better to think of the future IMO.
CentOS
PHP 5.4.16
https://distrowatch.com/table.php?distribution=centos
Debian
PHP 7.0.19
Debian 10 is expected around 2019-06
https://distrowatch.com/table.php?distribution=debian
Ubuntu 18.04
PHP 7.2.10
https://distrowatch.com/table.php?distribution=ubuntu

I want to add that Phalcon 3 already supports PHP 7.1 and 7.2 so the more conservative people already have quite a lot of room to get onto recent PHP versions and they can continue using Phalcon 3 just the same.  Considering that Phalcon 4 will be coming off a Phalcon LTS I think that you have room to be edgier with this next release.
Look at this article about PHP 7.1 features. That looks like a hell of a lot of internal PHP changes to me.  Are you prepared to not be able to offer great new Zephir constructs and operators because you need to support PHP 7.0?

The only version really tying our hands is 5.6, right now.

Has anyone investigated the internals of PHP 7.0 vs 7.1 in terms of new operators?  How much actual investigation has gone into getting an idea of how to add newer features into modern PHP Zephir?  It seems to me that 97% of that work goes back to the Andres days of PHP 5 and that PHP 7.0 was just shoe horned in and left to bit rot.  I see it that PHP 7.0 was a pretty boring feature release but it had a radically new engine but PHP 7.1 brought in tons of new operators and language features.  I find it unlikely that none of those new code paths have any value.

We will consider your proposal. Thank you for reaching out to us to point this.

RHEL 8.0 beta is out and it supports PHP 7.2.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html-single/8.0_beta_release_notes/

authors: danhunsaker dschissler sergeyklay

repo: phalcon/zephir


text:
Nesting inUnitOfWork: [] produces no errors

The code for inUnitOfWorkDo: [ ] contains a guard (myUnitOfWork) to avoid creating a new UnitOfWork object to track object changes.

With this code, nested calls to inUnitOfWork: will work just fine as they will use the outer most UOW object created.
The Glorp booklet also mentions this briefly:

BUT
the code for beginUnitOfWork states that nesting is not possible yet.

Questions:

Will there be errors if creating nested units of work due to something else?
If so, the code should emit an error if a UOW already exist.

It's ok to have nesting UOW's as in reality, only the most outer one will control comit/rollback.
if so, then simply updating the error to: ' Cannot create a new UOW when one is already created' would be sufficient to clarify the situation.

Please comment.

I think the valid option is 2. beginUnitOfWork should be a private method, because idiomatically speaking, what you end up using is something like inUnitOfWorkDo: which if it's called within an existing UOW will use the outermost (as in, the existing) one.

@eMaringolo I don't think the assumption about inUnitOfWorkDo: is valid.
It would require to build an extra level of mementos in an application for GUI applications. We do use beginUnitOfWork and don't use inUnitOfWorkDo: because that would mean you have to "buffer" all modifications to objects until you do an  inUnitOfWorkDo:.
The way I understand @lopezca the change suggested in option 2 is to just change the error text, right? If so, I don't think the suggested text would be an improvement. I think the term "nested transactions" is common enough to make this error message clear. Maybe the suggested text can be added to the existing one, but I wouldn't like to see the word "nested" or "nesting" disappear .

@eMaringolo I'd like to understand why you think reusing the outer context/uow is a valid thing. It's been a while since I learned about databases, but in my memories, a nested transaction/uow can be rolled back without affecting its outer transaction/uow. In case of Glorp, this is simply not implemented (by design / unfinishedness), so acting "as if" is probably a misleading approach. You shouldn't be able to "create" an inner uow without being informed that this is probably not what you think it is. If Glorp creates a nested uow without protesting, you may end up rolling back the outer uow when you think you just roll back the inner uow. So I guess an exception is the only correct thing you can get.
In the end you must design your application in a way that doesn't require nested transactions/uow's and in order to make sure you do, Glorp should make it very clear if you try to use a non-existing feature.
So the only way out is to either throw an exception (status quo) or implement nesting transactions (who dares?)

Carlos, could you add a comment on what the conclusion of this discussion is? In how far is this issue completed?

authors: JoachimTuchel eMaringolo lopezca

repo: pharo-rdbms/glorp


text:
Tiled 1.9 support

Changelog of Tiled (25th of June 2022):
https://doc.mapeditor.org/en/stable/reference/tmx-changelog/#tiled-1-9
Tiled had a 1.9 release which changes a few things, most notably:

type has been renamed to class in tile and object (Phaser.Types.Tilemaps.TiledObject)
class has been added to a variety of types
New properties for tile and tileset (Phaser.Tilemaps.Tile and Phaser.Tilemaps.Tileset)

Adding those new properties should be sufficient, given most of the code only translates the .json to objects and it's up to the developer from there to call the correct properties. This should also ensure backward compatibility with Tiled < 1.8 as I suspect plenty of people are still using it.
Example with filtering data
The following works with Tiled 1.8 (objects: Phaser.Types.Tilemaps.TiledObject in ObjectLayer):
const doors = this.map.getObjectLayer('Areas').objects.filter((zone) => zone.type === 'Door');

Tiled 1.9 expects:
const doors = this.map.getObjectLayer('Areas').objects.filter((zone) => zone.class === 'Door');

Found in the release notes of 1.9.x :
In addition, the “Type” property previously available only for objects and tiles is now available for all data types as the new “Class” property. For consistency, this value is written out as “class” also for objects and tiles, but a project-wide compatibility option is provided to make it still write out as “type”:
https://www.mapeditor.org/2022/06/25/tiled-1-9-released.html
Tested and it's work and let you go with the older method "type" rather than "class".

Was there any updates in Phaser regarding 'class' property in Tiled? I'm using Tiled 1.9 because I thought someday Tiled might remove the switching compatibility to 1.8.

@TorbenTK Thank you for the answer. I didn't know there was Tiled 1.10 released! I should just update my Tiled. Thanks!

As this is solved in 1.10, we are closing this issue.

authors: TorbenTK buzzjeux jhoryong rgk

repo: phaserjs/phaser


text:
Other DATUM

Hello,
I tried to make the migration:
$ table-> point ('point', 31982) -> nullable ();
$ table-> polygon ('drawing', 31982);
My Datum is SIRGAS 2000, but the bank is:
geography point (Point, 4326)
geography drawing (Polygon, 4326) NOT NULL,
You have no way to change the DATUM for what I need?

We're using geographies in Postgis, and Postgis only supports SRID 4326 for geography types.
http://postgis.net/docs/manual-1.5/ch04.html#Geography_Basics
In the future, if we decide to support geometries as well, or if Postgis finally gets support for other SRIDs, it'll make sense to specify other SRID.
For now I can only recommend you convert to 4326 if you want to use this package.

There is some foresight to launch a version with support for geometry?

Not at the moment, but if you make a pull request I'll merge it.
Basically you'll only need to change the blueprint and postgis grammar I think.
Everything else should work out of the box.

authors: daniloaluiz phaza

repo: phaza/laravel-postgis


text:
Share Current Note to Discord (Content)

This adds the Share Current Note to Discord (Content) command. The command will share an embed to Discord with the title as the note's title and the description as the content body of the note. A few things to keep in mind:

The feature will not share frontmatter or properties.
The feature will try to remove wiki links ([[This]] becomes This)
The feature will try to replace link aliases ([[Link|This]] becomes This)
The feature will try to remove Obsidian comments (%% This %% would be removed)

This PR also made some changes to esbuild to upgrade them to more modern practices.

Initial testing looks good. Will release after a bit of regression testing.

Regression testing revealed that the ShareAttachment command is broken on this branch. I'm assuming it's related to some of the esbuild changes becuase nothing else should've affected that workflow. Will continue to investigate.


text:
Versão alternativa

Fiz uma versão alternativa (não está finalizada ainda) que contém além da funcionalidade de fugir do “não”, um contador de “sim”.
Ainda tenho em mente criar um easter egg para quando o contador chegar a 10 por exemplo 😬

Opa, obrigado por contribuir! :)
Pode publicar essa branch no remoto?

repo: phedrakeson/love


text:
Join on year and mismatching geometry

Join in #109 now works when geometry is exactly the same left and right. Would be nice if some mismatch is allowed.

relates #87, see my comment

In #167  now uses year and exact wkt string to join datasets.

authors: SarahAlidoost sverhoeven

repo: phenology/springtime


text:
[Request]: Stripe logo

🔎 Information:

All fields are required:

Title:
Category (check categories):
Source (.svg) (type the link of the svg):
Company/Product Website:

📝 Checklist:

Make sure that you have completed the following steps:

[x] I have permission to use this logo.
[x] The link I have provided is optimized for web use.
[x] The size of the SVG is less than 20kb.

Ready 🚀
https://svgl.app/?search=stripe

authors: NadaaFarook pheralb

repo: pheralb/svgl


text:
Add Download SVG &  Drop down menu title

Add Download SVG title for the SVG with Light & Dark variants, and also give the title of the drop down menu items.

Thanks 🚀✨

authors: pheralb ridemountainpig


text:
CT: Cannot read property 'createTandem' of undefined

May be related to https://github.com/phetsims/scenery/commit/68d2f5af9bf0b62b3fefbc0f87df71cef3574eee
scenery : pageload : /doc/a-tour-of-scenery.html : load
Uncaught TypeError: Cannot read property 'createTandem' of undefined
TypeError: Cannot read property 'createTandem' of undefined
    at new e (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/scenery/build/scenery.min.js:1:581741)
    at e.initializeEvents (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/scenery/build/scenery.min.js:1:662012)
    at HTMLDocument.<anonymous> (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/scenery/doc/a-tour-of-scenery.html:586:17)
    at j (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/sherpa/lib/jquery-2.1.0.min.js:2:26676)
    at Object.fireWith [as resolveWith] (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/sherpa/lib/jquery-2.1.0.min.js:2:27489)
    at Function.ready (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/sherpa/lib/jquery-2.1.0.min.js:2:29283)
    at HTMLDocument.I (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/sherpa/lib/jquery-2.1.0.min.js:2:29453)
Approximately 9/20/2018, 8:41:00 AM
scenery : pageload : /examples/sprites.html : load
Uncaught TypeError: Cannot read property 'createTandem' of undefined
TypeError: Cannot read property 'createTandem' of undefined
    at new e (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/scenery/build/scenery.min.js:1:581741)
    at e.initializeEvents (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/scenery/build/scenery.min.js:1:662012)
    at window.onload (https://bayes.colorado.edu/continuous-testing/snapshot-1537454460688/scenery/examples/sprites.html:77:15)
Approximately 9/20/2018, 8:41:00 AM

Noticed in https://github.com/phetsims/scenery/issues/861.

Thanks @KatieWoe, I pushed a proposed fix in https://github.com/phetsims/scenery/issues/861, on hold until that is resolved.

authors: KatieWoe jonathanolson samreid

repo: phetsims/scenery


text:
fixing Heroku deployment

This fixes issues when deploying to Heroku, #41

import for ES6 modules is not supported yet natively, but server.js has import statement. This project does not build server.js with any build tool to augument import, so nodejs fails on that import line, had to fix it

if you deploy to Heroku from command line, environment variables in app.json are ignored, so you need to set them manually

Changes Unknown when pulling c36e3627628fdb3297998b938ca5a876516ad82e on sizov:master into ** on pheuter:master**.

@coveralls looks fine here, I've tried to git clone original repo from scratch, then add my remote as upstream and was able to fetch and merge changes from my repo into this.

@sizov Thank you! This was extremely helpful to get things working on Heroku.

authors: coveralls mdoerneman sizov

repo: pheuter/essential-react


text:
Iobroker objects will not be updated after update to 0.8.0

Hi,
I have installed the sainlogic adapter a few days ago in combination with my weather station running the FW WH2650A_V1.6.8. All was woriking and i smoothly got all the values.
Today i updated the sainlogic adapter to 0.8.0, and after that the objects will no longer be updated, even if i got valid data from the weather station:
2022-01-13 14:50:29.526 - debug: sainlogic.0 (5150) Listener received WU update: {"ID":"123","PASSWORD":"12345","tempf":"69.3","humidity":"32","dewptf":"38.1","windchillf":"69.3","winddir":"83","windspeedmph":"0.00","windgustmph":"0.00","rainin":"0.000","dailyrainin":"0.031","weeklyrainin":"0.031","monthlyrainin":"0.031","yearlyrainin":"0.031","solarradiation":"0.00","UV":"0","indoortempf":"70.0","indoorhumidity":"33","baromin":"30.499","lowbatt":"0","dateutc":"now","softwaretype":"WH2650A_V1.6.8","action":"updateraw","realtime":"1","rtfreq":"5"} 2022-01-13 14:50:29.529 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(ID) 2022-01-13 14:50:29.531 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(PASSWORD) 2022-01-13 14:50:29.532 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(tempf) 2022-01-13 14:50:29.533 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(humidity) 2022-01-13 14:50:29.535 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(dewptf) 2022-01-13 14:50:29.536 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(windchillf) 2022-01-13 14:50:29.537 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(winddir) 2022-01-13 14:50:29.538 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(windspeedmph) 2022-01-13 14:50:29.539 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(windgustmph) 2022-01-13 14:50:29.541 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(rainin) 2022-01-13 14:50:29.542 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(dailyrainin) 2022-01-13 14:50:29.543 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(weeklyrainin) 2022-01-13 14:50:29.544 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(monthlyrainin) 2022-01-13 14:50:29.551 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(yearlyrainin) 2022-01-13 14:50:29.553 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(solarradiation) 2022-01-13 14:50:29.557 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(UV) 2022-01-13 14:50:29.559 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(indoortempf) 2022-01-13 14:50:29.560 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(indoorhumidity) 2022-01-13 14:50:29.562 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(baromin) 2022-01-13 14:50:29.563 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(lowbatt) 2022-01-13 14:50:29.564 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(dateutc) 2022-01-13 14:50:29.566 - debug: sainlogic.0 (5150) Extracting value for info.softwaretype(softwaretype) 2022-01-13 14:50:29.567 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(action) 2022-01-13 14:50:29.569 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(realtime) 2022-01-13 14:50:29.571 - debug: sainlogic.0 (5150) Extracting value for weather.maxvalues.daily.UVraw_time(rtfreq) 2022-01-13 14:50:29.572 - debug: sainlogic.0 (5150) Extracting value for info.last_listener_update(last_listener_update) 2022-01-13 14:50:29.574 - debug: sainlogic.0 (5150) Setting value from data for weather.maxvalues.daily.UVraw_time to 5 2022-01-13 14:50:29.575 - debug: sainlogic.0 (5150) Setting value from data for info.softwaretype to WH2650A_V1.6.8 2022-01-13 14:50:29.576 - debug: sainlogic.0 (5150) Setting value from data for info.last_listener_update to {"ID":"123","PASSWORD":"12345","tempf":"69.3","humidity":"32","dewptf":"38.1","windchillf":"69.3","winddir":"83","windspeedmph":"0.00","windgustmph":"0.00","rainin":"0.000","dailyrainin":"0.031","weeklyrainin":"0.031","monthlyrainin":"0.031","yearlyrainin":"0.031","solarradiation":"0.00","UV":"0","indoortempf":"70.0","indoorhumidity":"33","baromin":"30.499","lowbatt":"0","dateutc":"now","softwaretype":"WH2650A_V1.6.8","action":"updateraw","realtime":"1","rtfreq":"5"}
Only objects are up to date are the the "Info" section:

Best Regards,
Stefan

Hello,
the same problem.  No values since update 0.8.0. I delete the object tree, but no change...
Regards
lhoem

I did a further test, and downgraded the adapter to version 0.7.3. After that it is working again.

Thanks for letting me know as well as the debug log. I'll check into this tomorrow and try to get an update ready.

0.8.1 has just been released and this should be fixed again.
Thanks for reporting.

I can confim that it is working now with 0.8.1.
Thanks for the quick BugFix.

authors: lhoem onki2 phifogg


text:
HELP error: unknown --json option future-incompat

When I start study VGA Text Mode  and add dependency for volatile, My project start got error like this
 │WARNING: You're currently building for the host system. This is likely an error and will cause build scripts of dependencies to break.
 │
 │To build for the target system either pass a `--target` argument or set the build.target configuration key in a `.cargo/config` file.
 │
 │   Compiling core v0.0.0 (/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core)
 │   Compiling compiler_builtins v0.1.70
 │error: unknown `--json` option `future-incompat`
 │error: unknown `--json` option `future-incompat`
 │error: unknown `--json` option `future-incompat`
 │
 │
 │
 │error: could not compile `compiler_builtins`
 │warning: build failed, waiting for other jobs to finish...
 │error: build failed

Even if I delete the volatile dependency, or even delete the entire project and start all over again, it will not return to normal, and my project can successfully print characters in pemu before the volatile event follows the tutorial
Please HELP~
My .cargo/config.toml in project
cfg(target_os = "linux")']
rustflags = ["-C", "link-arg=-nostartfiles"]

[target.'cfg(target_os = "windows")']
rustflags = ["-C", "link-args=/ENTRY:_start /SUBSYSTEM:console"]

[target.'cfg(target_os = "macos")']
rustflags = ["-C", "link-args=-e __start -static -nostartfiles"]

[unstable]
build-std-features = ["compiler-builtins-mem"]
build-std = ["core", "compiler_builtins"]

[build]
target = "x86_64-blog_os.json"

My main.rs

#![no_std]
#![no_main]

use core::panic::PanicInfo;

#[panic_handler]
fn panic(_info: &PanicInfo) -> ! {
    loop {}
}

#[no_mangle]
pub extern "C" fn _start() -> ! {
    loop {}
}

My Cargo.toml
[package]
name = "blog_os_study"
version = "0.1.0"
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]

[profile.dev]
panic = "abort"

[profile.release]
panic = "abort"

my json

{
    "llvm-target": "x86_64-unknown-none",
    "data-layout": "e-m:e-i64:64-f80:128-n8:16:32:64-S128",
    "arch": "x86_64",
    "target-endian": "little",
    "target-pointer-width": "64",
    "target-c-int-width": "32",
    "os": "none",
    "executables": true,
    "linker-flavor": "ld.lld",
    "linker": "rust-lld",
    "panic-strategy": "abort",
    "disable-redzone": true,
    "features": "-mmx,-sse,+soft-float"
}

What confuse me the most was the error: unknown '--json' option 'future-incompat'  this error, which I had never seen before and did not get much help from searching
My computer is Macbook Pro
Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
macOS Monterey 12.21
By the way, A Freestanding Rust Binary This chapter is consistent with the tutorial and the correct output

Which rustc and cargo version are you using? You can see this with rustc -V and cargo -V.

$ rustc -V --verbose
rustc 1.61.0-nightly (63b8f01bb 2022-03-24)
binary: rustc
commit-hash: 63b8f01bb5ca277e7df8d7efe094ed4244c1790c
commit-date: 2022-03-24
host: x86_64-apple-darwin
release: 1.61.0-nightly
LLVM version: 14.0.0

$ cargo -V --verbose
cargo 1.61.0-nightly (109bfbd05 2022-03-17)
release: 1.61.0-nightly
commit-hash: 109bfbd055325ef87a6e7f63d67da7e838f8300b
commit-date: 2022-03-17
host: x86_64-apple-darwin
libgit2: 1.4.2 (sys:0.14.2 vendored)
libcurl: 7.77.0 (sys:0.4.51+curl-7.80.0 system ssl:(SecureTransport) LibreSSL/2.8.3)
os: Mac OS 12.2.1 [64-bit]

$ rustup -V
rustup 1.24.3 (ce5817a94 2021-05-31)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.61.0-nightly (63b8f01bb 2022-03-24)`

What is the exact command you are using to build it?

What is the exact command you are using to build it?

just follow the tutorial, use cargo build --target x86_64-blog_os.json

$ cargo build --target x86_64-blog_os.json
   Compiling compiler_builtins v0.1.70
   Compiling core v0.0.0 (/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core)
error: unknown `--json` option `future-incompat`
error: unknown `--json` option `future-incompat`

error: could not compile `compiler_builtins`
warning: build failed, waiting for other jobs to finish...
error: build failed

rustc --json future-incompat was introduced four months ago in https://github.com/rust-lang/rust/pull/91535 which is part of rustc 1.59. What does cat target/.rustc_info.json show? That should show which rustc version is actually used by cargo.

$ cat target/.rustc_info.json
{
    "rustc_fingerprint":10704764349668684348,
    "outputs":{
        "931469667778813386":{
            "success":true,
            "status":"",
            "code":0,
            "stdout":"___\nlib___.rlib\nlib___.dylib\nlib___.dylib\nlib___.a\nlib___.dylib\n/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin\ndebug_assertions\npanic=\"unwind\"\nproc_macro\ntarget_abi=\"\"\ntarget_arch=\"x86_64\"\ntarget_endian=\"little\"\ntarget_env=\"\"\ntarget_family=\"unix\"\ntarget_feature=\"cmpxchg16b\"\ntarget_feature=\"fxsr\"\ntarget_feature=\"llvm14-builtins-abi\"\ntarget_feature=\"sse\"\ntarget_feature=\"sse2\"\ntarget_feature=\"sse3\"\ntarget_feature=\"ssse3\"\ntarget_has_atomic=\"128\"\ntarget_has_atomic=\"16\"\ntarget_has_atomic=\"32\"\ntarget_has_atomic=\"64\"\ntarget_has_atomic=\"8\"\ntarget_has_atomic=\"ptr\"\ntarget_has_atomic_equal_alignment=\"16\"\ntarget_has_atomic_equal_alignment=\"32\"\ntarget_has_atomic_equal_alignment=\"64\"\ntarget_has_atomic_equal_alignment=\"8\"\ntarget_has_atomic_equal_alignment=\"ptr\"\ntarget_has_atomic_load_store=\"128\"\ntarget_has_atomic_load_store=\"16\"\ntarget_has_atomic_load_store=\"32\"\ntarget_has_atomic_load_store=\"64\"\ntarget_has_atomic_load_store=\"8\"\ntarget_has_atomic_load_store=\"ptr\"\ntarget_os=\"macos\"\ntarget_pointer_width=\"64\"\ntarget_thread_local\ntarget_vendor=\"apple\"\nunix\n",
            "stderr":""
        },
        "1412545348552125361":{
            "success":false,
            "status":"exit status: 1",
            "code":1,
            "stdout":"",
            "stderr":"error: `-Csplit-debuginfo` is unstable on this platform\n\n"
        },
        "1825251703565484386":{
            "success":true,
            "status":"",
            "code":0,
            "stdout":"___\nlib___.rlib\nlib___.a\n/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin\ndebug_assertions\npanic=\"abort\"\nproc_macro\ntarget_abi=\"\"\ntarget_arch=\"x86_64\"\ntarget_endian=\"little\"\ntarget_env=\"\"\ntarget_feature=\"llvm14-builtins-abi\"\ntarget_has_atomic=\"16\"\ntarget_has_atomic=\"32\"\ntarget_has_atomic=\"64\"\ntarget_has_atomic=\"8\"\ntarget_has_atomic=\"ptr\"\ntarget_has_atomic_equal_alignment=\"16\"\ntarget_has_atomic_equal_alignment=\"32\"\ntarget_has_atomic_equal_alignment=\"64\"\ntarget_has_atomic_equal_alignment=\"8\"\ntarget_has_atomic_equal_alignment=\"ptr\"\ntarget_has_atomic_load_store=\"16\"\ntarget_has_atomic_load_store=\"32\"\ntarget_has_atomic_load_store=\"64\"\ntarget_has_atomic_load_store=\"8\"\ntarget_has_atomic_load_store=\"ptr\"\ntarget_os=\"none\"\ntarget_pointer_width=\"64\"\ntarget_vendor=\"unknown\"\n",
            "stderr":"warning: dropping unsupported crate type `dylib` for target `x86_64-blog_os-14647065019002254224`\n\nwarning: dropping unsupported crate type `cdylib` for target `x86_64-blog_os-14647065019002254224`\n\nwarning: dropping unsupported crate type `proc-macro` for target `x86_64-blog_os-14647065019002254224`\n\nwarning: 3 warnings emitted\n\n"
        },
        "17598535894874457435":{
            "success":true,
            "status":"",
            "code":0,
            "stdout":"rustc 1.61.0-nightly (63b8f01bb 2022-03-24)\nbinary: rustc\ncommit-hash: 63b8f01bb5ca277e7df8d7efe094ed4244c1790c\ncommit-date: 2022-03-24\nhost: x86_64-apple-darwin\nrelease: 1.61.0-nightly\nLLVM version: 14.0.0\n",
            "stderr":""
        },
        "2797684049618456168":{
            "success":true,
            "status":"",
            "code":0,
            "stdout":"___\nlib___.rlib\nlib___.dylib\nlib___.dylib\nlib___.a\nlib___.dylib\n",
            "stderr":""
        }
    },
    "successes":{

    }
}

:confused:

:confused:

How's that...Please help

I have no clue what the issue is unfortunately.

It's a regrettable, but still thank you for your REPLY!

I just try to use the origin repo post-02 and follow the README.md
but still got this as follow
$ rustup update nightly --force
info: syncing channel updates for 'nightly-x86_64-apple-darwin'

  nightly-x86_64-apple-darwin unchanged - rustc 1.61.0-nightly (d53246fed 2022-03-25)

info: checking for self-updates

$ cargo build
   Compiling compiler_builtins v0.1.53
   Compiling core v0.0.0 (/Users/xunjunjie/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/library/core)
error: unknown `--json` option `future-incompat`
error: unknown `--json` option `future-incompat`

error: could not compile `compiler_builtins`
warning: build failed, waiting for other jobs to finish...
error: build failed

$ cargo install bootimage
    Updating `ustc` index
error: failed to update replaced source registry `crates-io`

Caused by:
  failed to fetch `git://mirrors.ustc.edu.cn/crates.io-index`

Caused by:
  process didn't exit successfully: `git fetch --force --update-head-ok 'git://mirrors.ustc.edu.cn/crates.io-index' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128)
  --- stderr
  fatal: read error: Connection reset by peer

$ cargo bootimage
WARNING: `CARGO_MANIFEST_DIR` env variable not set
Building kernel
   Compiling compiler_builtins v0.1.53
   Compiling core v0.0.0 (/Users/xunjunjie/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/library/core)
error: unknown `--json` option `future-incompat`
error: unknown `--json` option `future-incompat`

error: could not compile `core`
warning: build failed, waiting for other jobs to finish...
error: build failed
Error: Kernel build failed.
Stderr:

I felt like I was going to surrender
It's too much of a blow to self-confidence
The point is that the code from yesterday's second lesson still ran successfully

@kaixinbaba Could you try running cargo clean and then cargo b -vv? This should give you verbose output, where we see the exact rustc command that is being invoked.

@phil-opp Thank you for REPLY!
Here is my output for code from post-02 branch
$ cargo b -vv
   Compiling compiler_builtins v0.1.70
   Compiling core v0.0.0 (/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core)
     Running `CARGO=/usr/local/bin/cargo CARGO_CRATE_NAME=build_script_build
CARGO_MANIFEST_DIR=/Users/xunjunjie/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/compiler_builtins-0.1.70
CARGO_PKG_AUTHORS='Jorge Aparicio <japaricious@gmail.com>'
CARGO_PKG_DESCRIPTION='Compiler intrinsics used by the Rust compiler. Also available for other targets
if necessary'\!'
'
CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/compiler-builtins'
CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE=''
CARGO_PKG_NAME=compiler_builtins
CARGO_PKG_REPOSITORY='https://github.com/rust-lang/compiler-builtins'
CARGO_PKG_VERSION=0.1.70
CARGO_PKG_VERSION_MAJOR=0
CARGO_PKG_VERSION_MINOR=1
CARGO_PKG_VERSION_PATCH=70
CARGO_PKG_VERSION_PRE=''
DYLD_FALLBACK_LIBRARY_PATH='/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/deps:/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib:/Users/xunjunjie/lib:/usr/local/lib:/usr/lib'
RUSTC_BOOTSTRAP=1 rustc --crate-name build_script_build /Users/xunjunjie/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/compiler_builtins-0.1.70/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C split-debuginfo=unpacked -C debuginfo=2 --cfg 'feature="compiler-builtins"' --cfg 'feature="core"' --cfg 'feature="default"' --cfg 'feature="mem"' --cfg 'feature="rustc-dep-of-std"' -C metadata=c7a24f5a423a70c0 -C extra-filename=-c7a24f5a423a70c0 --out-dir /Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/build/compiler_builtins-c7a24f5a423a70c0 -Z force-unstable-if-unmarked -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/deps --cap-lints warn`
     Running `CARGO=/usr/local/bin/cargo
CARGO_CRATE_NAME=core
CARGO_MANIFEST_DIR=/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core
CARGO_PKG_AUTHORS='' CARGO_PKG_DESCRIPTION='The Rust Core Library'
CARGO_PKG_HOMEPAGE=''
CARGO_PKG_LICENSE='MIT OR Apache-2.0'
CARGO_PKG_LICENSE_FILE=''
CARGO_PKG_NAME=core
CARGO_PKG_REPOSITORY='https://github.com/rust-lang/rust.git'
CARGO_PKG_VERSION=0.0.0
CARGO_PKG_VERSION_MAJOR=0
CARGO_PKG_VERSION_MINOR=0
CARGO_PKG_VERSION_PATCH=0
CARGO_PKG_VERSION_PRE=''
DYLD_FALLBACK_LIBRARY_PATH='/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/deps:/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib:/Users/xunjunjie/lib:/usr/local/lib:/usr/lib'
RUSTC_BOOTSTRAP=1 rustc --crate-name core --edition=2021 /Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C metadata=dea57f7448780fea -C extra-filename=-dea57f7448780fea --out-dir /Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps --target /Users/xunjunjie/IdeaProjects/RustHome/blog_os/x86_64-blog_os.json -Z force-unstable-if-unmarked -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/deps --cap-lints warn`
error: unknown `--json` option `future-incompat`
error: unknown `--json` option `future-incompat`

error: could not compile `core`

Caused by:
  process didn't exit successfully: `CARGO=/usr/local/bin/cargo
CARGO_CRATE_NAME=core
CARGO_MANIFEST_DIR=/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core CARGO_PKG_AUTHORS=''
CARGO_PKG_DESCRIPTION='The Rust Core Library'
CARGO_PKG_HOMEPAGE=''
CARGO_PKG_LICENSE='MIT OR Apache-2.0'
CARGO_PKG_LICENSE_FILE=''
CARGO_PKG_NAME=core
CARGO_PKG_REPOSITORY='https://github.com/rust-lang/rust.git'
CARGO_PKG_VERSION=0.0.0
CARGO_PKG_VERSION_MAJOR=0
CARGO_PKG_VERSION_MINOR=0
CARGO_PKG_VERSION_PATCH=0
CARGO_PKG_VERSION_PRE=''
DYLD_FALLBACK_LIBRARY_PATH='/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/deps:/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib:/Users/xunjunjie/lib:/usr/local/lib:/usr/lib' RUSTC_BOOTSTRAP=1 rustc --crate-name core --edition=2021 /Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C metadata=dea57f7448780fea -C extra-filename=-dea57f7448780fea --out-dir /Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps --target /Users/xunjunjie/IdeaProjects/RustHome/blog_os/x86_64-blog_os.json -Z force-unstable-if-unmarked -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/deps --cap-lints warn` (exit status: 1)
warning: build failed, waiting for other jobs to finish...
error: build failed

Thanks! Could you try running the first rust command manually. I.e. run the following in your shell:
rustc --crate-name core --edition=2021 /Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C metadata=dea57f7448780fea -C extra-filename=-dea57f7448780fea --out-dir /Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps --target /Users/xunjunjie/IdeaProjects/RustHome/blog_os/x86_64-blog_os.json -Z force-unstable-if-unmarked -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/deps --cap-lints warn

If it still throws the "unknown --json option" error, then try running rustc --version again in the same directory to see whether it is invoking the right rustc.

Thanks! Could you try running the first rust command manually. I.e. run the following in your shell:
rustc --crate-name core --edition=2021 /Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C metadata=dea57f7448780fea -C extra-filename=-dea57f7448780fea --out-dir /Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps --target /Users/xunjunjie/IdeaProjects/RustHome/blog_os/x86_64-blog_os.json -Z force-unstable-if-unmarked -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/deps --cap-lints warn

If it still throws the "unknown --json option" error, then try running rustc --version again in the same directory to see whether it is invoking the right rustc.

It return
{"artifact":"/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps/core-dea57f7448780fea.d","emit":"dep-info"}
{"artifact":"/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps/libcore-dea57f7448780fea.rmeta","emit":"metadata"}
{"artifact":"/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/x86_64-blog_os/debug/deps/libcore-dea57f7448780fea.rlib","emit":"link"}

And I try another rust command
rustc --crate-name build_script_build /Users/xunjunjie/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/compiler_builtins-0.1.70/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C split-debuginfo=unpacked -C debuginfo=2 --cfg 'feature="compiler-builtins"' --cfg 'feature="core"' --cfg 'feature="default"' --cfg 'feature="mem"' --cfg 'feature="rustc-dep-of-std"' -C metadata=c7a24f5a423a70c0 -C extra-filename=-c7a24f5a423a70c0 --out-dir /Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/build/compiler_builtins-c7a24f5a423a70c0 -Z force-unstable-if-unmarked -L dependency=/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/deps --cap-lints warn

and it return
{"artifact":"/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/build/compiler_builtins-c7a24f5a423a70c0/build_script_build-c7a24f5a423a70c0.d","emit":"dep-info"}
{"artifact":"/Users/xunjunjie/IdeaProjects/RustHome/blog_os/target/debug/build/compiler_builtins-c7a24f5a423a70c0/build_script_build-c7a24f5a423a70c0","emit":"link"}

What's these two mean? Ask for guidance
@phil-opp Thank you for REPLY~

The output shows that the rustc version that you invoked manually understands the future-incompat JSON option, which makes sense as your rustc --version output seems to be new enough for that. So something seems to go wrong when cargo invokes rustc, not sure why.
Could you try running RUSTFLAGS="--version" cargo b and paste the output here?

The output is
RUSTFLAGS="--version --verbose" cargo build
error: output of --print=file-names has changed in the compiler, cannot parse
command was: `rustc - --crate-name ___ --print=file-names --version --verbose --target /Users/xunjunjie/IdeaProjects/RustHome/blog_os/x86_64-blog_os.json --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg`

--- stdout
rustc 1.61.0-nightly (d53246fed 2022-03-25)
binary: rustc
commit-hash: d53246fedde4c193eae8a003546a8f0f9f85d223
commit-date: 2022-03-25
host: x86_64-apple-darwin
release: 1.61.0-nightly
LLVM version: 14.0.0

I'm not familiar with the way Rustup works on MacOS. On Linux and Windows, it would usually install binaries in your home directory (in ~/.cargo).
From the output above, however, it seems like cargo is being invoked from /usr/local/bin.
Do you have any other versions of Rust installed, e.g. through Homebrew?

$ whereis cargo
# there is noting output

$ which cargo
/usr/local/bin/cargo

$ cargo -V
cargo 1.61.0-nightly (109bfbd05 2022-03-17)

$ cargo build
   Compiling compiler_builtins v0.1.70
   Compiling core v0.0.0 (/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core)
error: unknown `--json` option `future-incompat`
error: unknown `--json` option `future-incompat`

Then I try to use $HOME/.cargo/bin/cargo
$ ~/.cargo/bin/cargo build
   Compiling compiler_builtins v0.1.70
   Compiling core v0.0.0 (/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core)
   Compiling bootloader v0.9.21
   Compiling rustc-std-workspace-core v1.99.0 (/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/rustc-std-workspace-core)
   Compiling blog_os v0.1.0 (/Users/xunjunjie/IdeaProjects/RustHome/blog_os)
    Finished dev [unoptimized + debuginfo] target(s) in 14.90s

AMAZING!
Then I add ~/.cargo/bin to PATH at first manually
$ cargo build
   Compiling compiler_builtins v0.1.70
   Compiling core v0.0.0 (/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core)
   Compiling bootloader v0.9.21
   Compiling rustc-std-workspace-core v1.99.0 (/Users/xunjunjie/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/rustc-std-workspace-core)
   Compiling blog_os v0.1.0 (/Users/xunjunjie/IdeaProjects/RustHome/blog_os)
    Finished dev [unoptimized + debuginfo] target(s) in 15.15s

I think this issue resolved!
THANK YOU!
@phil-opp

authors: bjorn3 elaforma kaixinbaba phil-opp


text:
there's unstable feature no_core

There's unstable feature
#![no_core]

Is it useful for developing OS?

No, not at all. It is completely useless for any code that a user of rust will write. #![no_core] is super unstable and requires defining a ton of language items and compiler intrinsics with any mistake potentially causing the compiler itself to crash. The only reason it exists at all is because libcore needs it to avoid depending on itself.

Can this issue be closed?

authors: ChocolateLoverRaj bingmatv bjorn3


text:
Update README.md

Added IDbyDNA
Adds the following events or companies:

Checklist

[] I have updated the event or company counts
[] I have put the most recent relevant date in the "Last Update" column
[] I have linked to the article about the change, not the company's website

I only added one line about my company "IDbyDNA". What do I need to do to get the update to the web page? Thanks.

repo: phildini/stayinghomeclub


text:
Added introspection support in OIDC provider

In Oidc provider, currently there is no support for introspection.
Extended the enrich session method to add the introspection claims.
How to use:
Pass the introspect url of your provider, and set_introspect_response_header to true to add the claims in response header 'X-Auth-Introspect-Response'

I think you need to open up some issues on the upstream repo to start off the conversation about the additions you are making here.
We need to make sure that what we do here is inline with what would be accepted by the upstream. There is no sense in doing all this work and then having to change it to get it merged,.
let me know if you need help with this.

Looks like this will be in principle accepted into the upstream
There are some comments that we should deal with and make sure they are integrated, then we can use the upstream master once merged.

For the future i would also merge the same development branch into both the local integration branch and upstream. That way the changes can be tracked and re-integrated better than using different branches. But YMMV..

For the future i would also merge the same development branch into both the local integration branch and upstream. That way the changes can be tracked and re-integrated better than using different branches. But YMMV..

Sure, will take this into consideration next time

authors: ScottGuymer prince-melvin


text:
Peter is Slovenian

Hi!
According to the campaign and his Facebook profile, Peter is from Slovenia.
Thanks.

Thanks for the correction!

Thanks for the correction!

authors: philipsharp smugphilip spaze

repo: philipsharp/afieldguidetoelephpants


text:
Warn if no  present

As noted by @ellismarkf in https://github.com/phoenixframework/phoenix_live_reload/issues/134#issuecomment-1471167134 , this library requires <body> to be present in root.html.heex for the browser to refresh following a detected code change and subsequent reload.
It would be useful to warn if <body> is not present due to e.g. developer shenangians with the template structure.

Proposal: <body> is checked for within before_send_inject_reloader/3 at https://github.com/phoenixframework/phoenix_live_reload/blob/e8a8d800e63c34fabb217af480b742af78a35872/lib/phoenix_live_reload/live_reloader.ex#L152C7-L152C7 so we could log a warning in the else case of the check.

Please do submit a PR!

Ok, I got bitten by this, so I tried implementing a PR, but it is more subtle that I anticipated. In before_send_inject_reloader/3 we get the full response, with a <body> tag even if it was added elsewhere that in the root layout.
The problem, is, I think, that when live view kicks in, it re-renders everything, including the app layout, this re-render removes the injected live reload tags. That is why the body tag needs to be in the root layout which is untouched by the live view.
So to warn the user, we have to get the root layout in before_send_inject_reloader/3, read the file and check for <body>.
It is not hard to implement, but it adds a file read on each request.
Something like:
        layout = Phoenix.Controller.root_layout(conn)
        if not layout_contains_body_tag?(layout) do
          IO.warn(
            "Your root template does not contain a <body> tag. " <>
            "The <body> tag is required for the live reload plug to work"
          )
        end

and layout_contains_body_tag? would need to find the template file and read it and search for <body> in it.
The other approach would be to inject some JS in the <head> tag, something like setInterval() that checks every second if the live reload tag is present in the page, a simple query selector would work, and this would console.error() on the browser side.
Last but not least, add a comment in the root.html.heex template when doing phx.new, add same comment in the dev.exs config above live reload section, as those are the two places where we look in case of issues. Something like: # If using live view, ensure your <body> tag is located in your root template.
Let me know what you think.

Thanks for looking into this, @kuon !
Are you saying that has_body?/1 at https://github.com/phoenixframework/phoenix_live_reload/blob/e8a8d800e63c34fabb217af480b742af78a35872/lib/phoenix_live_reload/live_reloader.ex#L157 always returns true then? Arguably that would be a bug in its own right.

add a comment in the root.html.heex ...

That's a good stopgap IMHO.

Yes has_body? always return true, because it is called on the fully rendered page, so the html actually have a body, even if this body is not within the root template.
I also think the comment is enough.

We can't guarantee that the user has a root layout, or a root layout file, so that unfortunately is not going to work.

We can't guarantee that the user has a root layout, or a root layout file, so that unfortunately is not going to work.

We could just add a comment in the generated dev.exs, like this:
# Note: The browser reloading code will not work if the
# <body> tag is rendered with live view. In typical situation
# it means to keep the <body> inside your root layout.
config :book, BookWeb.Endpoint,
  live_reload: [
    patterns: [
      ~r"priv/static/.*(js|css|png|jpeg|jpg|gif|svg)$",
      ~r"priv/gettext/.*(po)$",
      ~r"lib/book_web/.*/.*(ex)$"
    ]
  ]

Another idea would be to add an attribute that live view would understand, similar to `phx-update="ignore"`` but stronger, it would tell live view to keep the tag even if the parent is removed, then the generated tag from this library would include it and be protected. But I don't know how feasible and desired this would be.

A LV wrapping the entire body is a pretty large edgecase that I'm not overly worried about. A better way to handle this would be to open a public function on the LV side (like making the current private reload_assets_tag public with a better name) and having folks call that in their live layout to embed the LR iframe.

authors: chrismccord josevalim kuon wodow


text:
confused,how to solve this problem?

Property or method "id" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option. (found in component )

Duplicate with #10


text:
My name is Joel Kreider

My name is Joel Kreider and I am ready for the semester, I and my whole family love computers and all that comes with them. looking forward to this class.

welcome!

welcome!


text:
WP8 push notification issue - An unknown error has occurred. Error: 80020101

Hi,
I am trying to get the push plugin working in wp8. Paste my code below:
var winConfig = {
"channelName" : "test",
"ecb" : "onNotificationWP8",
"uccb" : "channelHandler",
"errcb" : "jsonErrorHandler"
};
pushNotification.register(wpSuccessHandler, wpErrorHandler, winConfig);
But I always am getting an empty uri in the data from the callback wpSuccessHandler.
With the following exception:
A first chance exception of type 'System.SystemException' occurred in Microsoft.Phone.Interop.ni.dll
ERROR: Exception in InvokeScriptCallback :: An unknown error has occurred. Error: 80020101.
Can anyone advise/help with this ?

Just tried a couple of times, sometimes return empty uri, sometimes return the valid uri.
Not sure what's wrong here

I have the same problem, are you fix the problem?

I did, trying using $interval until you got the uri.

Funcionou uma versão quando publiquei na WP loja na segunda tentativa, porém alguma atualização que fiz deixou de funcionar. Você pode enviar o seu código, pois algum detalhe deve estar fazendo a diferença.

It worked when I published a version in WP store on the second try, but I did some updating crashed. You can send your code because some detail should be making a difference.

It always works for me for the second time. First time is always empty, simply ignore it and try one more time.

Very interesting this repo/plugin looks like no longer being supported !!! Everyone trying to use a walk around to solve this problem !

Make sure the date and time settings are correct on your device and then try. This issue has been addressed.

authors: MingxuanLi fabiofapeli qiqbal rakatyal

repo: phonegap-build/PushPlugin


text:
FCM error in IOS

Hello sir,  because I want to only use APNS for IOS and I have removed the GoogleService-Info.plist file according to what you have told me.
Now the APNS is working, I can receive the notification.
But I see some errors in the console, paste it below. Is there any way to avoid it?
2017-09-22 10:15:48.436 eNoteMobile[884:8147] 2017-09-22T02:15:48.435Z  Title=On Push Error  Msg=push error:  - REMOTE_NOTIFICATION_SIMULATOR_NOT_SUPPORTED_NSERROR_DESCRIPTION
2017-09-22 10:15:48.437 eNoteMobile[884:8147] 2017-09-22T02:15:48.436Z  Title=Toast Time  Msg=needTime=3000, extraTime=1000, keepTime=4000, str=Push notification init failed. Detail:  - REMOTE_NOTIFICATION_SIMULATOR_NOT_SUPPORTED_NSERROR_DESCRIPTION
2017-09-22 10:15:48.443 eNoteMobile[884:9625] FCM Sender ID 647571745247
2017-09-22 10:15:48.443 eNoteMobile[884:9625] Using FCM Notification
2017-09-22 10:15:48.443 eNoteMobile[884]  [Firebase/Core][I-COR000003] The default Firebase app has not yet been configured. Add [FIRApp configure]; (FirebaseApp.configure() in Swift) to your application initialization. Read more: https://goo.gl/ctyzm8.
2017-09-22 10:15:48.444 eNoteMobile[884]  [Firebase/Core][I-COR000008] The project's Bundle ID is inconsistent with either the Bundle ID in 'GoogleService-Info.plist', or the Bundle ID2017-09-22 10:15:48.471 eNoteMobile[884:8147] FCM token is null
in the options if you are using a customized options. To ensure that everything can be configured correctly, you may need to make the Bundle IDs consistent. To continue with this plist file, you may change your app's bundle identifier to 'xxx'. Or you can download a new configuration file that matches your bundle identifier from https://console.firebase.google.com/ and replace the current one.
2017-09-22 10:15:48.480 eNoteMobile[884]  [Firebase/Analytics][I-ACS023007] Firebase Analytics v.40003000 started
2017-09-22 10:15:48.481 eNoteMobile[884]  [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2017-09-22 10:15:48.482 eNoteMobile[884]  [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. Add "FirebaseAppDelegateProxyEnabled" to your Info.plist and set it to NO
2017-09-22 10:16:48.462 eNoteMobile[884:8147] <Firebase/Network/ERROR> Encounter network error. Code, error: -1001, Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://play.googleapis.com/log, NSErrorFailingURLKey=https://play.googleapis.com/log, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2103, NSLocalizedDescription=The request timed out.}
2017-09-22 10:16:48.463 eNoteMobile[884]  [Firebase/Core][I-NET901017] <Firebase/Network/ERROR> Encounter network error. Code, error: -1001, Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://play.googleapis.com/log, NSErrorFailingURLKey=https://play.googleapis.com/log, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2103, NSLocalizedDescription=The request timed out.}
2017-09-22 10:16:48.463 eNoteMobile[884]  [Firebase/InstanceID][I-IID003009] Failed to fetch default token Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://device-provisioning.googleapis.com/checkin, NSErrorFailingURLKey=https://device-provisioning.googleapis.com/checkin, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2103, NSLocalizedDescription=The request timed out.}
2017-09-22 10:16:48.463 eNoteMobile[884]  [Firebase/Core][I-COR000020] Error posting to Clearcut: Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://play.googleapis.com/log, NSErrorFailingURLKey=https://play.googleapis.com/log, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2103, NSLocalizedDescription=The request timed out.}, with Status Code: 0
2017-09-22 10:17:50.465 eNoteMobile[884]  [Firebase/InstanceID][I-IID003009] Failed to fetch default token Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://device-provisioning.googleapis.com/checkin, NSErrorFailingURLKey=https://device-provisioning.googleapis.com/checkin, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2103, NSLocalizedDescription=The request timed out.}

@xiaoaowanghu try removing the ios platform and adding it back in again. It looks like an issue with the GoogleService-Info.plist  still hanging around.
Also, sorry to be a jerk but I'm now closing issues that don't follow the issue submission guidelines. This plugin takes a lot of work to maintain and I can't afford the time required to solicit the required info from everyone.
I'm closing this issue but please feel free to re-open the issue if you provide the requested details from the new issue submission guidelines.
https://github.com/phonegap/phonegap-plugin-push/blob/master/.github/ISSUE_TEMPLATE.md

authors: macdonst xiaoaowanghu

repo: phonegap/phonegap-plugin-push


text:
Instructions on local builds?

Can you share a bit more about your build process?
I tried to dockerize this and am getting:
 => ERROR [builder 8/8] RUN echo "Compiling for darwin-amd64..." &&     glide novendor &&     env GOOS=darwin GOARCH=amd64 go build -ldflags "-s" -o build/goexpose-darwin-amd64-1.0.0 ./cmd/goexpose                                             0.3s
------
 > [builder 8/8] RUN echo "Compiling for darwin-amd64..." &&     glide novendor &&     env GOOS=darwin GOARCH=amd64 go build -ldflags "-s" -o build/goexpose-darwin-amd64-1.0.0 ./cmd/goexpose:
#15 0.153 Compiling for darwin-amd64...
#15 0.244 ./cmd/...
#15 0.244 .
#15 0.253 go: cannot find main module, but found glide.lock in /go/src/app
#15 0.253 	to create a module there, run:
#15 0.253 	go mod init
------

Heres my Dockerfile
# Build stage
FROM golang:latest as builder

RUN apt-get update && \
    apt-get install -y git

WORKDIR /go/src/app

# Install Glide
RUN curl -sL https://github.com/Masterminds/glide/releases/download/v0.13.2/glide-v0.13.2-linux-amd64.tar.gz | tar -xz && \
    mv linux-amd64/glide /usr/local/bin/glide

# Copy the source code and Glide files
COPY . .
COPY glide.* ./

# Install the project dependencies
RUN glide install

# Set environment variables
ARG version=1.0.0

# Run the build script
#RUN echo "Compiling for darwin-amd64..." && \
#    env GOOS=darwin GOARCH=amd64 go build -ldflags "-s" -o build/goexpose-darwin-amd64-$version ./cmd/goexpose

# Run the build script with Glide
RUN echo "Compiling for darwin-amd64..." && \
    glide novendor && \
    env GOOS=darwin GOARCH=amd64 go build -ldflags "-s" -o build/goexpose-darwin-amd64-$version ./cmd/goexpose

# Final stage
FROM alpine:latest

WORKDIR /root/

# Copy the binary from the builder stage
COPY --from=builder /go/src/app/build/goexpose-darwin-amd64-$version .

# Add any other necessary setup or runtime dependencies here

# Run the binary
CMD ["./goexpose-darwin-amd64-$version"]

Hi,
There is release with precompiled binary. I haven't converted goexpose to modules yet, I started to work on it.
I can have a look and provide version that supports modules if necessary.
Regards,
Peter

authors: jondkelley phonkee

repo: phonkee/goexpose


text:
Lotion bottle

Describe the requested icon(s)
🧴 A bottle of lotion for the skin, such as moisturizer or sunscreen (sunblock). May be used for other hygienic liquids, including shampoo and body wash), as well as beauty products.
References
https://emojipedia.org/lotion-bottle
https://www.shutterstock.com/fr/image-vector/body-lotion-icon-outline-glyph-style-2311155853
Additional context
May be used for every cosmetic product

hand-soap should work for this purpose, no? I'll add some tags to make it easier to search.

@rektdeckard Yes it does the job. Thanks, I'll close the issue

repo: phosphor-icons/homepage


text:
Ability to use icons via Name parameter

We want to save the icon names as strings in our db, then use them via a name option, this is not currently possible via importing each icon seperatly.
E.g.

Is this something that could be implemented?

You can use require.context, like this:
const icons = require.context('./node_modules/phosphor-vue/src/components', true, /\.vue$/i)
icons.keys().map((icon) => {
  const component = icons(icon).default
  console.log(component.name)
  // Load components
  Vue.component(component.name, component)
})

Hi @Lewitje thanks for opening this issue. It's currently not possible to import a icon manifest that links a icon name to the actual component. What you can do, and what I'd suggest, is that you create a spearate mapping table that maps your custom names to the icon component:
import { markRaw } from 'vue'
import { PhAirplaneLanding } from '@phosphor-icons/vue'

const iconMap = new Map()
map.set('ph-airplane-landing', markRaw(PhAirplaneLanding))

// or

const iconMap = {
  'ph-airplane-landing': markRaw(PhAirplaneLanding))
}

you could also do this:
import * al icons from  '@phosphor-icons/vue'

which will result in a key-value pairing of the module name e.g.
{
... ,
PhAirplaneLanding: <component>
}

authors: Lewitje dnlsndr hypernova7

repo: phosphor-icons/phosphor-vue


text:
removing useless cache key

Quick fix to remove test cache key

Codecov Report

Merging #216 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #216   +/-   ##
========================================
  Coverage      82.2%   82.2%
  Complexity      601     601
========================================
  Files            33      33
  Lines          1540    1540
========================================
  Hits           1266    1266
  Misses          274     274

Continue to review full report at Codecov.

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

authors: Korbeil codecov-io

repo: php-cache/cache


text:
As a developer, it would be awesome if this DDEV plugin set up my phpunit for me

Is there an existing issue for this?

[X] I have searched the existing issues

Are you sure that this bug is related to this DDEV Integration Plugin?

[X] I am sure

Enter your error report ID (If available)
No response
Describe the bug
When using DDEV in PhpStorm there is a bug that is caused by how the tool decides to set the path mapping for a DDEV-driven project.  PhpStorm appears to discover that there is a path mapped to /var/tmp/html when mutagen is enabled.  The expected directory to map for the project root is /var/www/html.  Through debugging the issue with DDEV developers, we discovered the workaround is easy, just manually set the path mapping for project root to be /var/www/html, manually.
I'm hoping the plugin can help make this workaround be a part of the help and assistance that is provided.  I've been thinking about the plugin as the thing that makes using DDEV with PhpStorm easy.  Fixing a flaw that is seemingly caused by how PhpStorm decides to create these mappings would be a great thing to "patch".
Related DDEV troubleshooting: https://github.com/ddev/ddev/issues/4697
Fix to DDEV Documentation: https://github.com/ddev/ddev/pull/4732
Steps to reproduce
Setup a Drupal site using a modified version of the Drupal 10 quickstart.  This adds in Selenium for functional testing and phpstorm dependencies.

cd ~/Sites
mkdir my-drupal10-site
cd my-drupal10-site
ddev config --project-type=drupal10 --docroot=web --create-docroot
ddev get ddev/ddev-selenium-standalone-chrome
ddev start
ddev composer create drupal/recommended-project
ddev composer require drupal/core-dev --dev --update-with-all-dependencies
ddev composer require drush/drush
ddev drush site:install --account-name=admin --account-pass=admin -y

Add Mutagen

ddev config --mutagen-enabled=true
ddev start

Testing the bug

Open the project in PhpStorm
Open preferences and navigate to PHP to view the interpreter that this plugin setup.
Click the folder icon in the Path Mappings for the interpreter
Observe that the project root is mapped to /var/tmp/html

Additional context
No response

I'm not sure this is in scope for the plugin, but if it is, always making the default project root mapping be Project Root -> /var/www/html would make everything work always.

@cosmicdreams please change the title; Maybe "Wrong project root mapping provided by default set when Mutagen enabled"

title fixed.

Hey @cosmicdreams,
Thanks for reporting this!
If there is something the plugin can do to avoid manual configuration steps, this is something we should definitely look into further!
Could you please show a screenshot of the wrong mapping path? Currently the project root inside the container is set statically, as it is always the same for ddev containers, see:
https://github.com/php-perfect/ddev-intellij-plugin/blob/c83e5d0ab467e09d767ce6a221cc28c4756dacce/src/main/java/de/php_perfect/intellij/ddev/php/server/ConfigureServerListener.java#L39
Thanks in advance!

Here's a screenshot of what my "fix" had to be.  It shows how I manually set the path to project root to /var/www/html AND how the system set the project root to /var/tmp/html

Here's a screenshot of the config that I believe led the system into thinking that was the right thing to do

You see here that it's setting a path binding to /var/tmp/html
Desired fix:

Within the plugin's logic.
Check if mutagen is enabled
Check what the project's path mapping for the project root is (within PhpStorm's path mapping config)
if it's set to /var/tmp/html, override it to be /var/www/html.

The tmp directory is supposed to be read only, and shouldn't be the point of interaction for phpstorm because running tests sometimes means creating folders, files, screenshots, etc.  All of which need write access.

Mappings for all DDEV projects should be Project Root -> /var/www/html

@rfay the line of code that @nico-loeber showed seems to be doing that, and yet the bug occurred.  I wonder if there is an order of operations issue here.  Does the plugin's attempt to set the path mapping occur after something else that sets the path based upon the discovered bindings?

AFAIK this plugin doesn't manage mappings for phpunit.

Oh that too.  The phpunit configuration could be managed as the settings are the same each time, well for Drupal configs that is.  Here's a screenshot and let me break it down what the config normally looks like:

Get rid of the local interpreter settings that are normally associated with phpunit
Set up a remote interpreter to use the one that is already configured by the plugin.
Use PHAR method of finding phpunit
Set the path to the command to /var/www/html/vendor/bin/phpunit
Finally, for me (because I'm using the ddev-selenium-standalone-chrome library, I can just use the /var/www/html/web/core/phpunit.xml.dist default config file.  Maybe that would be fine for most scenarios.  Something to talk through.

Having the plugin properly setup EVERYTHING you need to get tests running would be great, but feels like a separate issue from what the purpose of this issue is about.

I think it's really cool that this plugin sets up your database connection, that's a huge "selling point" for when I advocate for DDEV and this plugin as core tools for our local development.  ALSO being able to have your test runner setup when a DDEV project using Drupal is discovered would be awesome.

Having the plugin properly setup EVERYTHING you need to get tests running would be great, but feels like a separate issue from what the purpose of this issue is about.

There are other mappings that could be set up, for example, phpcs. But AFAICT this issue should be retitled and the summary fixed, as I think it is exactly about running phpunit. It's not about the regular mapping, which I think is done correctly.
That's also the same thing that https://github.com/ddev/ddev/pull/4732 is waiting for you on.

@cosmicdreams, everything that is required to run PHPUnit, in PHPStorm should already be configured by the plugin.

clone https://github.com/php-perfect/ddev-integration-demo in PHPStorm
Click ddev start in phpstorm
open WorldTest.php and click one of the play buttons
the test suit should be run and succeed

If this does not work in the example project please let me know.

As I mentioned in the Discord channel, I am waiting for my colleague to independently retest the error to see if they encounter it.  But I have not been able to get the error to recur myself.
I've come around to the idea that this issue needs to be retitled and focus instead on having the plugin set up configuration for phpunit.

@nico-loeber Are we aligned on whether this plugin should establish phpunit config during it's initialization / discovery phase? Or whatever the phase is called when it's creating the interpreter config.

Hi @cosmicdreams,
Thanks for summarizing!
Regarding the bug you were experiencing, please let me know if this happens to you or one of your colleagues again!
I am always willing to improve the plugin for a better integration of DDEV, this means to me, to reduce repetitive setup that is always the same for a DDEV environment, like configuring PHP Interpreters and database connections.
In my opinion the phpunit setup is none of them.
First of all you need to tell PHPStorm if you are using PHPUnit installed in your vendor directory or if you are using it as a phar installed by phive or maybe donwloaded manually. Both ways to setup phpunit are valid and they are not DDEV related. It is a project specific decission.
Also the location of your phpunit.xml might differ depending on your project structure. It is most common to store it in the project root of course.
In case you you have installed phpunit in your vendor using composer and your phpunit.xml(.dist) is located in your project root, PHPStorm will already detect it automatically and no PHPUnit configuration is required.
This is tested with the ddev integration demo project. If this is not working for you we can take a look at it, if you like. But please note this is a phpstorm feature and none of the plugin.
As there is no single "right" configuration for PHPUnit I would like to keep this out of the ddev setup process as this configuration would override the auto detection of PHPstorm that might give better results for people, sorry.

That would be excellent, we can cut down the communication loop and be able to point to configs from newly setup sites and stuff.
I will have time on Friday, April 15th to do such a screenshare.  What time / timezone would work best for you?

Note also that the internal mapping to /var/tmp/html is likely to go away in next DDEV version, so the confusing mapping might go away, but PhpStorm also might not be able to guess the correct mapping at all.

That would be excellent, we can cut down the communication loop and be able to point to configs from newly setup sites and stuff.
I will have time on Friday, April 15th to do such a screenshare. What time / timezone would work best for you?

Sorry, I'm a bit late...
I'm in UTC+2 (Europe/Berlin). Please write me at nico@php-perfect.de so we can find a date without sapmming this discussion, thanks!

I'm not sure this is in scope for the plugin, but if it is, always making the default project root mapping be Project Root -> /var/www/html would make everything work always.

Apologies for asking what might be a very basic question, but I'm setting up ddev, PhpStorm, Mutagen, and when I run the tests, I encounter problem:
HP Warning:  file_put_contents(/var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/../../../../../../sites/simpletest/Assert.php): failed to open stream: Read-only file system in /var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/ClassWriter.php on line 115

Warning: file_put_contents(/var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/../../../../../../sites/simpletest/Assert.php): failed to open stream: Read-only file system in /var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/ClassWriter.php on line 115
PHP Warning:  include(/var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/../../../../../../sites/simpletest/Assert.php): failed to open stream: No such file or directory in /var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/ClassWriter.php on line 60

Warning: include(/var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/../../../../../../sites/simpletest/Assert.php): failed to open stream: No such file or directory in /var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/ClassWriter.php on line 60
PHP Warning:  include(): Failed opening '/var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/../../../../../../sites/simpletest/Assert.php' for inclusion (include_path='/var/tmp/html/vendor/pear/archive_tar:/var/tmp/html/vendor/pear/console_getopt:/var/tmp/html/vendor/pear/pear-core-minimal/src:/var/tmp/html/vendor/pear/pear_exception:.:/usr/share/php') in /var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/ClassWriter.php on line 60

Warning: include(): Failed opening '/var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/../../../../../../sites/simpletest/Assert.php' for inclusion (include_path='/var/tmp/html/vendor/pear/archive_tar:/var/tmp/html/vendor/pear/console_getopt:/var/tmp/html/vendor/pear/pear-core-minimal/src:/var/tmp/html/vendor/pear/pear_exception:.:/usr/share/php') in /var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/ClassWriter.php on line 60
PHP Warning:  file_put_contents(/var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/../../../../../../sites/simpletest/TestCase.php): failed to open stream: Read-only file system in /var/tmp/html/web/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/ClassWriter.php on line 115

From my research, I found that this could be due to the mapping being in /var/tmp/html, but I can't find where to manually change this in PhpStorm when using the ddev plugin for PhpStorm. Is there any documentation available on this integration that I can review?

@Gonzalo2683 you must remove the mapping that uses /var/tmp/html and use the mapping of Workspace->/var/www/html.
That's what this issue is about, trying to get the plugin to do this for you.

Hey @cosmicdreams,
Finally I had some time to investigate this a bit further.
The problem was not related to the phpunit configuration at all. The source of the problem is that the manually set path Mapping when configuring the interpreter (Code referenced aboth) is ignored by PHPStorm if it detects the path mapping from the docker-compose file. This causes not only problems for phpunit but for all cli executions like composer installs.
Enabling mutagen changed the docker-compose file in a way that phpstorm can no longer find a path mapping for /var/www/html as @rfay already mentioned. The solution for this problem is setting the additional path mapping not on interpreter level but on project level in the configuration.
This is done in https://github.com/php-perfect/ddev-intellij-plugin/commit/c07efcb48ee4b691f282c441e35c17ab06fe3d1e.
This fix should be released as soon as I have finished another feature I am currently working on (Within the next few days).
Sorry for the waiting time. Feedback is welcome.

The fix is relased in version 1.1.0 (pending JetBrains review). Please let me know if still have any issues, @cosmicdreams.

I just had a slight issue with getting PHPUnit to run via DDEV/Docker. It worked fine with the "Always start a new container" CLI lifecycle configuration but failed when I switched to "Connect to existing container". The error that popped up mentioned that the name did not match a regex. It turned out that the DDEV project name needs to be all lowercase and I had one uppercase character in it.

authors: Gonzalo2683 cosmicdreams nico-loeber rfay shochdoerfer

repo: php-perfect/ddev-intellij-plugin


text:
🛑 phpMyFAQ Password Hash Generator Tool is down

In 0f23b1e, phpMyFAQ Password Hash Generator Tool (https://password.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Password Hash Generator Tool is back up in e5c65f0.


text:
🛑 phpMyFAQ Password Hash Generator Tool is down

In 6d2d71d, phpMyFAQ Password Hash Generator Tool (https://password.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Password Hash Generator Tool is back up in 77200d4.


text:
🛑 phpMyFAQ Demo is down

In 910f52e, phpMyFAQ Demo (https://demo.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Demo is back up in 450bf35.


text:
🛑 phpMyFAQ Demo is down

In e224849, phpMyFAQ Demo (https://demo.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Demo is back up in e573ecd.


text:
🛑 phpMyFAQ Demo is down

In 6be3745, phpMyFAQ Demo (https://demo.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Demo is back up in 6d0325c.


text:
🛑 phpMyFAQ Password Hash Generator Tool is down

In 2dadb99, phpMyFAQ Password Hash Generator Tool (https://password.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Password Hash Generator Tool is back up in 7a2d986.


text:
🛑 phpMyFAQ Demo is down

In 6677a8c, phpMyFAQ Demo (https://demo.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Demo is back up in 5f3cf77 after 4 minutes.


text:
🛑 phpMyFAQ Password Hash Generator Tool is down

In c9f82b1, phpMyFAQ Password Hash Generator Tool (https://password.phpmyfaq.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: phpMyFAQ Password Hash Generator Tool is back up in d7cca07 after 13 minutes.


text:
New Expression BeAnnotatedWith

Feature Request
Add BeAnnotatedWith Expression.

Q
A

New Feature
yes

RFC
yes/no

BC Break
yes/no

Summary
Use case:
yield Rule::allClasses()
        ->that(new Implement(App\Shared\Domain\Event\Event::class))
        ->should(new BeAnnotatedWith('@psalm-immutable'))
        ->because('we want to enforce immutability');

As class naming I suggest HaveAnnotationMatching or HaveAnnotations (this last one is my preferred) instead of BeAnnotatedWith.

Closed by #255

authors: AlessandroMinoccheri pfazzi ricfio

repo: phparkitect/arkitect


text:
style: add border to logo

The image blended in when the background was white.

Pull Request Test Coverage Report for Build 4333085063

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 4296084987:
0.0%

Covered Lines:
60

Relevant Lines:
60

💛  - Coveralls

authors: coveralls ericfortmeyer

repo: phpolar/csv-file-storage