I got this warning on my Ember App :
DEPRECATION: Versions of modifier manager capabilities prior to 3.22 have been deprecated. You must update to the 3.22 capabilities. [deprecation id: manager-capabilities.modifiers-3-13] See https://deprecations.emberjs.com/v3.x#toc_manager-capabilities-modifiers-3-13 for more details.
at logDeprecationStackTrace (http://localhost:4200/assets/vendor.js:36552:21)
at HANDLERS. (http://localhost:4200/assets/vendor.js:36685:9)
at raiseOnDeprecation (http://localhost:4200/assets/vendor.js:36579:9)
at HANDLERS. (http://localhost:4200/assets/vendor.js:36685:9)
at invoke (http://localhost:4200/assets/vendor.js:36697:9)
at deprecate (http://localhost:4200/assets/vendor.js:36653:28)
at modifierCapabilities$1 (http://localhost:4200/assets/vendor.js:11678:62)
at http://localhost:4200/assets/vendor.js:99939:46
at CustomModifierManager.getDelegateFor (http://localhost:4200/assets/vendor.js:44817:20)
I visited the link https://deprecations.emberjs.com/ recommended for updating, I didn't really understand how to make this update, any help please .
Related
Trying to configure a .Net Core service to talk to an AmazonMQ - RabbitMQ instance. This is the config I'm using:
https://masstransit-project.com/usage/transports/rabbitmq.html#amazonmq-rabbitmq
cfg.Host(new Uri("amqps://b-mdefg-ff37-4e33-855c-577a0c749659.mq.us-westeast-2.amazonaws.com:5432/"), h =>
{
h.Username("MyUsername");
h.Password("XXXXXXXXX");
});
Nuget packages are:
MassTransit.AspNetCore v5.5.6
MassTransit.Autofac v5.3.2
MassTransit.RabbitMQ v5.3.2
MassTransit.SerilogIntegration v5.1.5
The exception being thrown is:
MassTransit.RabbitMqTransport.RabbitMqAddressException: 'The invalid scheme was specified: amqps'
Upgrading to the latest MassTransit caused a lot of unrelated issues. Any clues as to a workaround?
OK, solution was fairly straightforward, but google gave me nothing so perhaps this will save someone some time. I simply upgraded MassTransit.RabbitMQ to v5.5.6 and it all works now.
I would like to use rollbar.com in my Crystal project.
I can not find crystal integration with rollbar.com or any other error trackers.
Is there a shard for the Rollbar or similar services (error tracking)?
I don't know anything about Rollbar. But there's a client for Sentry which should have similar features: https://shardbox.org/shards/raven
DryIoc can't seem to Resolve a IAsyncRequestHandler.It throws"An exception of type 'DryIoc.ContainerException' occurred in DryIoc.dll but was not handled in user code Additional information: Unable to resolve MediatR.IRequestHandler.
Where no service registrations found
and number of Rules.FallbackContainers: 0
and number of Rules.UnknownServiceResolvers: 0"which is weird because it should be resolving a IAsyncRequestHandler.Another weird thing is that the code runs well on Net.Fiddle (check here)
I'm using VS 2015 Update 3 in Windows 10 Home, MediatR 3.0.0, DryIoc.dll 2.10.0, .Net framework 4.5 (also tried with 4.6.1).Am I registering it in a wrong way? This should be straightforward.Related: What is the best way to register all handlers?
Background
I am currently working on a Clojure wrapper of Sony Remote Camera Control API Beta.
API : https://developer.sony.com/develop/cameras/
Wrapper: https://github.com/hammartap/facet
Symptom
Some functions, which getAvailableApiList function says "available" looks unavailable.
(Returns IllegalArgumentException No matching field found error.)
Question
Am I missing API documentation?
If so, someone could guide me to the corresponding section of the document?
If not, I would like to know in which version these functions will be implimented.
Especially, I am interested in "(get|set)BeepMode", "(get|set)StillSize", setExposureMode, and so on.
I attached complete list of functions which looks unavailable for reference.[1]
Best.
Development environment
OS
Mac OSX 10.7.5
Language
Clojure 1.4.0 with Leiningen2
Java
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609) Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
Editor
Emacs 23.3
[1] Functions which seems to be unavailable
"getMethodTypes",
"setSelfTimer",
"getSelfTimer",
"getSupportedSelfTimer",
"getAvailableSelfTimer",
"setPostviewImageSize",
"getPostviewImageSize",
"getSupportedPostviewImageSize",
"getAvailablePostviewImageSize",
"setExposureMode",
"getExposureMode",
"getSupportedExposureMode",
"getAvailableExposureMode",
"setBeepMode",
"getBeepMode",
"getSupportedBeepMode",
"getAvailableBeepMode",
"setCameraFunction",
"getCameraFunction",
"getSupportedCameraFunction",
"getAvailableCameraFunction",
"setStillSize",
"getStillSize",
"getSupportedStillSize",
"getAvailableStillSize",
"actFormatStorage",
"getStorageInformation",
"setTouchAFPosition",
"cancelTouchAFPosition",
"getTouchAFPosition",
"getSupportedExposureCompensation",
"getSupportedWhiteBalance",
"getVersions",
Some undocumented API becomes avaliable after auth. You can see how it is done on QX100 here from line 144 to 151: https://github.com/Tsar/sony_qx_controller/blob/master/sony_qx_controller.py#L144
You may not be using a camera that supports those features. Here is Sony's capability chart
I'm trying to set the logging level to DEBUG in an embedded Jetty instance.
The documentation at http://docs.codehaus.org/display/JETTY/Debugging says to -
call SystemProperty.set("DEBUG", "true") before calling new
org.mortbay.jetty.Server().
I'm not sure what the SystemProperty class is, it doesn't seem to be documented anywhere. I tried System.setProperty(), but that didn't do the trick.
My question was answered on the Jetty mailing list by Joakim Erdfelt:
You are looking at the old Jetty 6.x docs at docs.codehaus.org.
DEBUG logging is just a logging level determined by the logging
implementation you choose to use.
If you use slf4j, then use slf4j's docs for configuring logging level. http://slf4j.org/manual.html
If you use java.util.logging, use the JVM docs. http://docs.oracle.com/javase/6/docs/technotes/guides/logging/overview.html
If you use the built-in StdErrLog, then there is a pattern to follow.
-D{classref}.LEVEL={level}
Where {classref} is the class reference you want to set the level on,
and all sub-class refs. and {level} is one of the values ALL, DEBUG,
INFO, WARN
Example:
-Dorg.eclipse.jetty.LEVEL=INFO - this will enable INFO level logging for all jetty packages / classes.
-Dorg.eclipse.jetty.io.LEVEL=DEBUG - this will enable DEBUG level logging for IO classes only
-Dorg.eclipse.jetty.servlet.LEVEL=ALL - this will enable ALL logging (trace events, internally ignored exceptions, etc..) for servlet
packages.
-Dorg.eclipse.jetty.util.thread.QueuedThreadPool.LEVEL=ALL - this will enable level ALL+ on the specific class only.
Add this
-Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog
-Dorg.eclipse.jetty.LEVEL=DEBUG
In case you just want to quickly get log messages to stderr add something like this to java command line:
-Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog -D{classref}.LEVEL=DEBUG
You can use this snippet to enable logging:
import org.eclipse.jetty.util.log.Log;
import org.eclipse.jetty.util.log.StdErrLog;
.
.
.
StdErrLog logger = new StdErrLog();
logger.setDebugEnabled(true);
Log.setLog(logger);