When i tried to add "Add-CORS" Assign message policy to an existing API proxy i got this Error repeatedly.
I tried to undeploy and re-deploy the App but none worked.
This is issue is because of bundle size and not because of CORS policy. Check if bundle size can be reduced. Or else please log a ticket with support to get help on the resolution of the bundle size.
It is something to do with the package size. If you are using NodeJS to develop your bundle:
Reduce your API Proxy bundle size by removing unnecessary files and un-used modules.
Import resources separately through the Management API
Run NPM install on the server through the Management API
[Replace the placeholders in URL with actual value]
See the discussion here.
Related
I have a Next.js 13 app that was deployed to the Edge on Cloudflare Pages with experimental: { runtime: 'experimental-edge' }, but requirements were updated and I need to include our feature flag dependency LaunchDarkly - and retrieve the feature flags via getServerSideProps.
Inside getServerSideProps I tried launchdarkly-node-server-sdk, launchdarkly-node-client-sdk, and launchdarkly-js-client-sdk, but they either require a Node specific library (fs and others) or window.
launchdarkly-cloudflare-edge-sdk with #cloudflare/kv-asset-handler looks promising, so I followed the template, but I'm not sure how to extend a Next.js app to have this functionality. For example, do I put the worker into a middleware.ts function or somehow extend the vercel build step to include this functionality.
I haven't tested this out but I am guessing you may need to use the Cloudflare SDK throughout since Cloudflare would deploy the functions as Cloudflare Workers, which is a non-Node runtime.
In a typical Next.js deployment, you'd use the Node server SDK for any server side code (like getServerSideProps) but my assumption is that this may cause errors due to the fact that it relies upon some Node-specific APIs that I am not sure the Workers runtime supports. We (LaunchDarkly) are working on updates to our JavaScript SDKs to better support non-Node runtimes but I don't have an ETA on their release.
In a Symfony 5.x project I use knplabs/knp-snappy-bundle.
Having private data-folders for different users results in generating PDF-documents that require images from folders which are not publicly accessable.
When trying to generate a PDF-document with an image in such a folder knpsnappy runs into a 60 sec timeout. The Symfony log says
Guard authenticator does not support the request.
I assume something regarding the "external" tool knpsnappy calling from outside the application but from the same server but does not triggering any security definition I defined.
I am unsure on how to allow knpsnappy to access a specific route.
Maybe someone can lead me into the right direction...?
I was misslead.
The cause of the problem wasn't access rights but the way the img-pathes were defined.
knp snappy wont be able to render images with URL-routes.
I switched the pathes to be absolut server pathes and now it works.
Found the solution here:
KnpSnappyBundle and Symfony 3.4 : images and/or css cause timeout
Hybris: 6.3.0.25
When initializing Hybris 6.3.0.25 with platformbackoffice extension, the initialization never finishes.
Is there a workaround to fixing this issue?
STEPS TO REPLICATE:
Download and Extract ZIP file of Hybris 6.3.0.25
In platform folder, do ant all using default settings
In localextensions.xml, make sure platformbackoffice is the only extension
In platform folder, do ant initialize
Start Hybris
Open HAC and do Platform Intialize
NOTES:
Nothing is added in local.properties. So, Platform Initialize will use in-memory DB. However, the same issue also happens with mySQL 5.6.42.
Issue also happens with Hybris 6.3.0.24
The issue does not happen in Hybris 6.3.0.0-SNAPSHOT
I am planning to upgrade from Hybris 6.3.0.0-SNAPSHOT to the latest 6.3, which would be 6.3.0.25 at the time of this writing. Before that, I also tested with 6.3.0.24 and the upgrade didn't go so well.
ACTUAL RESULT:
Hybris hangs.
EXPECTED RESULT:
Platform Initialize finishes successfully
LOGS:
https://pastebin.com/Sx0223UM
I don't think so, only platformbackoffice can be running. You need more modules then it. I haven't got exact list, you can check dependencies in module config xml file (extensioninfo.xml). It is giving error about missing cockpit config with below message in your log file.
[DefaultCockpitConfigurationService] Could not load cockpit configuration root element; creating new one
What is your aim for running only platformbackoffice?
Given a feature with a <configfile> and a <bundle>, how can I ensure that the file is deployed before the bundle? What I'm seeing is that my bundle gets started first and the file deployed second (even if <configfile> is the first tag).
I guess this is could be the <bundle> being considered a pre-requisite so it makes sense to start that before processing the rest of the <feature>?
Actually if you are doing it right, your bundles shouldn't care if the configuration is available or not. The service should either not be started or with a default setting in case no "external" configuration has been set. In case of a new configuration the service will be restarted with the new configuration.
I am just starting with Meteor and working on an existing project. I am running into an issue with one of the packages(observatory-apollo) that's has the following line:
__meteor_bootstrap__.app.use Observatory.logger #TLog.useragent
It is complaining that __meteor_bootstrap__.app is undefined.
What is __meteor_boostrap__ exactly? I can't seem to find a description of what it is but from threads, people seem to know how to use it. I can only see it defined in boot.js, but it doesn't really tell me much...
Meteor uses connect npm module under the hood for various reasons, to serve static files, for example. __meteor_bootstrap__.app was the reference to connect app instance.
Before it was __meteor_bootstrap__.app but it changed couple of releases ago and became WebApp.connectHandlers object and is part of WebApp package.
WebApp is a standard package of Meteor, core package for building webapps. You don't usually need to add explicitly as it is a dependency of standard-app-packages.
Example of usage the connectHandlers is to inject connect middlewares in the same way as you would use any connect middleware (or some express middlewares, express is built on top of connect):
WebApp.connectHandlers
.use(connect.query())
.use(this._config.requestParser(bodyParser))
You can look at meteor-router Atmosphere package and take it as an example: https://github.com/tmeasday/meteor-router/blob/master/lib/router_server.js
More about connect: https://npmjs.org/package/connect