Create topcis.json
{
"version": 1,
"topics": [
{ "topic": "my-sample-topic"
| public class CustomLayout extends LinearLayout { | |
| @SuppressWarnings("unchecked") @Override public Parcelable onSaveInstanceState() { | |
| Parcelable saveInstanceState = super.onSaveInstanceState(); | |
| SavedState savedState = new SavedState(saveInstanceState); | |
| savedState.childrenStates = new SparseArray(); | |
| for (int i = 0; i < getChildCount(); i++) { | |
| getChildAt(i).saveHierarchyState(savedState.childrenStates); | |
| } | |
| return savedState; |
Assuming that the following environment variables are set:
KAFKA_HOME where Kafka is installed on local machine (e.g. /opt/kafka)ZK_HOSTS identifies running zookeeper ensemble, e.g. ZK_HOSTS=192.168.0.99:2181KAFKA_BROKERS identifies running Kafka brokers, e.g. KAFKA_BROKERS=192.168.0.99:9092Start Zookepper and Kafka servers
Hello, brethren :-)
As it turns out, the current version of FFmpeg (version 3.1 released earlier today) and libav (master branch) supports full H.264 and HEVC encode in VAAPI on supported hardware that works reliably well to be termed "production-ready".
| { | |
| "_description: Name of City, or Town": { | |
| "State": "The Indian State under which this City/Town exists.", | |
| "GeoCode": [ | |
| "Latitude", | |
| "Longitude" | |
| ], | |
| "PinCodes": [ | |
| "All", | |
| "The", |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent| buildscript { | |
| ext { | |
| springBootVersion = '1.2.5.RELEASE' | |
| } | |
| ext['spring.version'] = '4.2.1.RELEASE' | |
| repositories { | |
| mavenCentral() | |
| } |
If you have a package where a lot of people are still using a legacy version of it you might want to keep pushing (security-)fixes to that "branch".
Let's say the "latest" version of your package is "5.4.0", but there is as significant amount of people still using "4.7.4" – the last version you released before doing "5.0.0".
You found a critical bug in "5.4.0" and push it as out as "5.4.1", but it applies to "4.7.4" as well and so you want to do "4.7.5".
Assuming you have semantic-release already set up, you can follow these steps to get that "4.7.5" legacy support release out.
git checkout v4.7.4git checkout -b 4.x (You can choose any branch name, just make sure to use the same in step 3)Please create an Issue in the transport-apis repo instead. 🙏