What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi Spryker, here `vendor/spryker/publish-and-synchronize-health-check/src/Spryker/Zed/PublishAndSync
Hi Spryker,
here vendor/spryker/publish-and-synchronize-health-check/src/Spryker/Zed/PublishAndSynchronizeHealthCheck/Persistence/PublishAndSynchronizeHealthCheckPersistenceFactory.php
there is a typo error... Class not found.. wrong use statement.
Thank u!
Fyi: @valerii.trots
Comments
-
Thanks, will check it tomorrow.
0 -
which class?
if from this namespaceOrm\Zed\PublishAndSynchronizeHealthCheck\
you need to executepropel:install
0 -
@UKBTMFXMJ did u seen the content of the file???
0 -
see it right now
0 -
first use statement...
0 -
used then in the return of the function..
the right ORM Class start with Spy...
0 -
try please to remove all orm class and re-run propel:install.. i dont think that the classes are there (they without Spy at the start of name)
0 -
that was renamed in xml schema (of course) but the old ones committed & pushed in suite...
0 -
I see
0 -
in suite there is no BC (when we run test etc..) but in customer project via composer update then I have a BC
0 -
thanks @UL65CH0MC!
0 -
U see.. it happened as said.. the developer at first named the entity without Spy in propel xml schema and generated the orm class.. then he renamed with Spy but he has committed/pushed both and use the old use statement in factory..
U are welcome!
0 -
Maybe u can help me to understand another problem that I have with P+S Health Check..
I executed every project changes as here https://github.com/spryker-shop/suite/pull/798/files but i got an error when i call the health-check in zed
doc id publish-and-synchronize:search:health-check not found
I see that in
spy_publish_and_synchronize_health_check
table is one row written... but _search and _storage tables are empty... and i don't see any event in queuepublish.publish_and_synchronize_health_check
.I missed smth to migrate/update on pyz level?
0 -
maybe i found it.. i had the job event-trigger-timeout disabled (for testing purpose) in jenkins scheduler and of course the created/updated entities events has not consumed and therefore no events etc...
0 -
events are now consumed... i have one row written in _search and _storage table... everything was synced but i have the same error when i try to call the zed health check page... I have to investigate in deeper what is the problem...
0 -
I found @UKBTMFXMJ there is another error
the key generated in _search table and used as document id in Elastica is
publish_and_synchronize_health_check:health-check
but here\Spryker\Shared\PublishAndSynchronizeHealthCheckSearch\PublishAndSynchronizeHealthCheckSearchConfig::PUBLISH_AND_SYNCHRONIZE_HEALTH_CHECK_SEARCH_ID
is configuredpublish-and-synchronize:search:health-check
Ok, i can override on Pyz level, but it should be fixed in core too 😉
0 -
the same happend for storage.. key and check key configured are not the same...
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 75 Spryker News
- 924 Developer Corner
- 783 Spryker Development
- 88 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random