feat: reduce bundle size

Removed Metamask SDK(it's quit haevy)
Moved useIntegration hook to integrations package(otherwise importing hooks would also import all of the cosmos stuff)
Changed wasm optimizations for -z or -Oz which means optimization  for size aggressively(not exactly sure how much this will affect performance :( )
now we copy wasm files to extension assets and use fetch to load them in background service worker 👍
I've changed rustopt options to defaults for profile

You can now also run: BUNDLE_ANALYZE=true yarn build:firefox (or chrome) to see bundle size analyzed under: localhost:8888

Aside from removing:
entry: {
    shared: "../../packages/shared/src/init.ts",

everything looks good!

Again 😅 👍


feat: add out_of_range flag to load_cdf

Description
This PR changes load_cdf so:
By default

load_cdf with starting_version out of range returns an InvalidVersion
load_cdf with a starting_timestamp out of range returns a ChangeDataTimestampGreaterThanCommit

And you can use .with_allow_out_of_range() in rust or allow_out_of_range=True in python to make it so that both cases return an empty dataframe.
This aligns it closer with how reading the change feed works in spark and makes the behaviour consistent.
This in contrast to the  current behavior:

load_cdf with starting_version out of range returns an InvalidVersion
load_cdf with a starting_timestamp out of range returns an empty dataframe

Related Issue(s)

closes #3035

Awesome, seems that all the tests passed now

@pblocz if you could sign off on your commits we can get this merged soon

@hntd187 Done. I don't know why, but thought the sign off was something else 😅


Fix recipe references in getRecipe.

The returned object has the recipe under recipes[0].recipe and the
dependencies under recipes[0].modules

Fix in a different way by the metadata fetch refactoring.


Example proxy configuration in Firefox for SOCKS+DNS

After adding this:
  caps := selenium.Capabilities{
    "browserName": "firefox",
    "prefs": map[string]interface{}{
      "network.proxy.type": 1,
      "network.proxy.socks": "<IP_ADDRESS>",
      "network.proxy.socks_port": 9050,
      "network.proxy.socks_version": 5,
      "network.proxy.socks_remote_dns": true,
    },
  }

Proxy is not used for requests.
When i try to use selenium.Proxy , there is no option to configure socksVersion and session initialization hangs and fails.
  proxy := selenium.Proxy{
    Type:  "MANUAL",
    SOCKS: "<IP_ADDRESS>:1080",
  }

  caps := selenium.Capabilities{
    "browserName": "firefox",
    "proxy": proxy,
  }

Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: '5fd3930137d7', ip: '<IP_ADDRESS>', os.name: 'Linux', os.arch: 'amd64', os.version: '4.9.125-linuxkit', java.versi
on: '1.8.0_212'
Driver info: driver.version: unknown
make: *** [run] Error 1

  caps.AddProxy(selenium.Proxy{
    Type: selenium.Manual,
    SOCKS: "<IP_ADDRESS>",
    SocksPort: 9050,
  })

I just added the SOCKSVersion field to the selenium.Proxy type. Please take a look.
The W3C standard does not provide a field for the "remote DNS" attribute:
https://www.w3.org/TR/webdriver/#proxy

The hang in geckodriver when the SOCKSVersion is not supplied is reported in mozilla/geckodriver#1547
I just wrote a test to reproduce this (which will be committed soon). Supplying SOCKSVersion works when using ChromeDriver and Geckodriver directly. It fails with the following error when Selenium WebDriver is used:
wd.NewSession() returned error: unknown error: java.lang.Long cannot be cast to java.lang.Integer

That error is reported in SeleniumHQ/selenium#/6917 and was fixed, but is not yet in a release.


Bitbucket Pipelines Support

Something went wrong with https://github.com/codecov/codecov-bash/pull/135 and now the env file does not contain a check for bitbucket.
I can create a PR if interested.

Hi @KajdeMunter
It seems like it's here: https://github.com/codecov/codecov-bash/blob/master/tests/env#L107-L111
Can you explain more about what you see missing?

Never mind, I missed that #225 was linked, taking a look now.


feat: add hint for using O instead of ko

There is already a hint for using "o" instead of "jO". This adds a hint for using "O" instead of "ko".

Hi @XileonXL, thanks for the feedback! I did consider adding this hint earlier, but I found that the key presses are essentially the same. Both <Shift> o and k o involve two key presses, so I think using k o is perfectly fine.

Hi @m4xshen, I had the same thought as you but participating in vimgolf changed my perspective. It doesn't count Shiftor Ctrlas a keystroke because they are considered modifiers:

Additionally, I think it is a good habit to use O as ko just because there is a dedicated key (O) for creating a new line above, whereas ko is a combination of two different purpose keys (k to move a line up and o to create a new line below). Using the reserved key (O) simplifies the action and aligns with Vim’s philosophy of efficiency.


C# Bond, how to compile the schema definition to a value type (struct) instead of reference type (class)?

I like the bond framework very much.  The following schema definiton is codegen as reference type (class) in C# by default.  Is there a way to codegen it as a value type (struct) instead?
struct Record
{
0: string Name;
1: int32 Age
}

Bond compiler currently doesn't support generating C# structs, although you can annotate your own structs with Bond attributes and Bond runtime does support de/serializing them.


Fuzz test Serializer to decode FiledValue

Initialize a static Serializer object to be used in fuzz testing.
Call Serializer::DecodeFieldValue with the fuzzing inputs.

travis still fails the linting after running the style.sh and lint.sh scripts

travis still fails the linting after running the style.sh and lint.sh scripts

I see "All checks have passed", all should be good.
Thanks for addressing the feedback! I think this can be squashed and merged now.


Progress tracking issue for 1.1 Release Candidate 2

Before the release

[x] Do a fresh clone of the repository
[x] Verify that index.php, SSI.php, install.php and upgrade.php have the correct CURRENT_VERSION and CACHE_STALE.
[x] Write a draft of the release announcement. It should consist of:

a general description of the release
a release notes document including the major changes since the previous version (for development versions like alpha, beta and RC is the previous dev version, for final versions is the previous stable version).
a known issues document listing the major issues affecting the release (i.e. bugs not critical enough to be blocker, but potentially annoying)

The following command helps writing the list of changes used in the release notes:
git log --pretty=format:'[*][bugfix] %s ([url=https://github.com/elkarte/Elkarte/commit/%h]ref[/url]).' --abbrev-commit

Packages creation check list:

[x] Do a fresh clone of the repository
[x] From the root directory, run the release_tools/build.sh (e.g. sh release_tools/build.sh development 1.1 beta2), this will generate the package with the appropriate files

Complete the release

[x] Create a new release at github using the announcement previously drafted, and attach the packed files
[x] ...
[x] Profit!!!

https://github.com/elkarte/Elkarte/releases/tag/v1.1.0-RC.2


User defined window functions

Is your feature request related to a problem or challenge?
When implementing our InfuxQL frontend for DataFusion, we found certain functions we would like to express as window functions (like a specialized interpolation function for example)
We can write user defined aggregates:
select
  x, my_aggregate(x, time)
from t;

But those do not produce the same number of rows that go in (they reduce cardinality)
We would like to use our own window functions like
select
  x, my_interpolation_function(x, time) OVER (PARTITION BY y, ORDER BY time)
from t;

Describe the solution you'd like
I would like the ability to define, and register user defined window functions , like we have for user defined aggregate functions:
https://github.com/apache/arrow-datafusion/blob/8139ed40d06d77498217438ff52fe73a4ea16f61/datafusion-examples/examples/simple_udaf.rs#L18-L19
This would likely involve

[ ] Some sort WindowUDF (like AggregateUDF)
[ ] Register on function registry: https://github.com/apache/arrow-datafusion/blob/8139ed40d06d77498217438ff52fe73a4ea16f61/datafusion/execution/src/registry.rs#L25
[ ] Some sort of WindowExprFunctionImplementation like https://github.com/apache/arrow-datafusion/blob/8139ed40d06d77498217438ff52fe73a4ea16f61/datafusion/expr/src/function.rs#L48
[ ] Expose the WindowExpr trait: https://github.com/apache/arrow-datafusion/blob/8139ed40d06d77498217438ff52fe73a4ea16f61/datafusion/physical-expr/src/window/window_expr.rs#L38-L143

It isn't clear to me if we would want to expose AggregateWindowExpr, for example
Describe alternatives you've considered
No response
Additional context
No response

FYI @mustafasrepo  and @ozankabak  I think @stuartcarnie  is contemplating what implementing user defined window functions might entail. I am not sure if you have any thoughts on this matter you would like to share

Yes, we will be using UDWF too. Is there a design doc we can read and comment on?

How we distinguish UDWF from UDAF since window function already supports AggregateUDF, I mean UDWF is a super set of udaf in window function.

Yes, we will be using UDWF too. Is there a design doc we can read and comment on?

There is no document that I know of -- it is probably time to start one

How we distinguish UDWF from UDAF since window function already supports AggregateUDF, I mean UDWF is a super set of udaf in window function.

@doki23 I am not sure
The current code has this:
https://docs.rs/datafusion-expr/23.0.0/datafusion_expr/window_function/enum.WindowFunction.html
I never really understood why DataFusion makes a distinction between built in aggregate functions and user defined aggregate functions (it would be really nice if all aggregate functions had the same interface)

Unless someone beats me to it I plan to start working on a proposed design for this feature in the next few days

Great stuff, @alamb! I did have similar ideas in my own test branch, but I wasn't sure how to replicate BuiltInWindowFunctionExpr and BuiltinWindowState. Renaming them makes a lot of sense 👍🏻

Looks reasonable to me, thanks @alamb

While working on https://github.com/apache/arrow-datafusion/pull/6592 a key design question about WindowUDF has arisen. Specifically:
Use existing API / Traits
What this would mean:
This would mean exposing (at least)  BuiltInWindowFunctionExpr and PartitionEvaluator directly for people to implement a WindowUDF
This would mean making those traits pub and part of a WindowUDF and
Pros

This is the same pattern used by AggregateUDF (TODO link) that exposes the Accumulator trait directly to implementors
Allow user defined window functions to access all the features and performance as built in window functions (both now and in the future)

Cons
BuiltInWindowFunctionExpr and PartitionEvaluator are are fairly complicated (as they support many features) which could make implementing user defined window functions harder
Also, BuiltInWindowFunctionExpr and PartitionEvaluator would likely need some changes such as:

renamed so they weren't called "BuiltIn*"
Moving the trait definitions into datafusion_expr
Update the state management to be extendable (e.g. the enum for BuiltinWindowState would have to be updated to to allow user defined state somehow)

Make new APIs and traits
What this would mean:
In this case, we would make new traits that are subsets of what is in
BuiltInWindowFunctionExpr and PartitionEvaluator that users would
implement. Internally we would implement BuiltInWindowFunctionExpr
and PartitionEvaluator in terms of these new traits.
Pros

We can tailor the API to precisely the needs of user defined window function writers
Would allow changing the internal APIs without having to change the WindowUDF API

Cons
A new API would mean introducing another api layer that needs to be tested and kept up to date.
The new API also might not expose all the functionality of the built in window functions if such functionality was added at a later date
Discussion
I am going to try and bash out a technical proof of concept of the first approach (exposing the existing APIs) and we can see how it would look. On the balance that is my preferred approach due to the power of the API and the similarities with AggregateUDFs

Here is a proposed API https://github.com/apache/arrow-datafusion/pull/6617 showing how a User Defined Window function would work. Any feedback on the approach would be most appreciated.
While waiting for feedback on https://github.com/apache/arrow-datafusion/pull/6617 I plan to try and simplify some of the window function implementation as some small PRs


Add proper diagnostic when an integer is passed to the magic attribute with an unspecified type

#[binrw]
#[br(little, magic = 1)]
struct Header {
    x: u8,
}

error: expected type, found `;`
 --> src/main.rs:5:1
  |
5 | #[binrw]
  | ^^^^^^^^
  | |
  | expected type
  | while parsing this item list starting here
  | the item list ends here
  |
  = note: this error originates in the attribute macro `binrw` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0046]: not all trait items implemented, missing: `MagicType`, `MAGIC`
 --> src/main.rs:5:1
  |
5 | #[binrw]
  | ^^^^^^^^ missing `MagicType`, `MAGIC` in implementation
  |
  = note: this error originates in the attribute macro `binrw` (in Nightly builds, run with -Z macro-backtrace for more info)
  = help: implement the missing item: `type MagicType = Type;`
  = help: implement the missing item: `const MAGIC: <Self as HasMagic>::MagicType = value;`

binrw version: 0.8.0

Implementation guide for anyone interested:

Relevant code is in this impl
For literals of type Lit::Float or Lit::Int, check if x.suffix().is_empty(). If true, then output a compile_error!() with a span matching that of the literal. This can probably be done by just constructing a syn::Error in the above function.
If for whatever syn::Error isn't enough to get the desired error diagnostic, find the right place for using to_compile_error to actually emit the error.

This was fixed by dd4fa9b4610369f7f9c2034d205563edf468a1f5.


[ENH] Updated How to get data modal

Closes #367

Checklist
This section is for the PR reviewer

[ ] PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF], [MODEL], [DOC]) (see our Contributing Guidelines for more info)
[ ] PR has a label for the release changelog or skip-release (to be applied by maintainers only)
[ ] PR links to GitHub issue with mention Closes #XXXX
[ ] Tests pass
[ ] Checks pass
[ ] If the PR changes the participant-level and/or the dataset-level result file, the query-tool-results files in the  neurobagel_examples repo have been regenerated

For new features:

[ ] Tests have been added

For bug fixes:

[ ] There is at least one test that would fail under the original bug conditions.

Hey @rmanaem, for the sake of re-releasing, I'm going to apply my suggested changes and merge!


Addition of SceneLayer Samples

Added Scene Layer sample for WPF, UWP ,Droid ,iOS and Forms.

@ThadT can you review please?

@ThadT I've made changes in line with review comments. No VB samples as of yet I'm happy to add at a later date if users request


repo-cleanup: We should run the github munger

Once we're running it, we should also add a labels.yaml similar to the one in the k8s repo proper and the bot'll create a bunch of nice labels for us!
There are instructions over here.
@spxtr: Can we point the existing munger or a k8s/goog managed munger at incubator repos?

We're working on making that easier, but it's a little tricky right now. For the munger, I think you need to turn up a new one for each repo, and I'm not sure how easy that is. @apelisse probably knows better than I do.

Yes, we could create a new instance of the mungebot for this repository. Unfortunately, we start to realize that it's not going to scale nicely (we'll end-up with one instance per repo, and that's a little bit too many).
A couple of questions:

What features exactly are you interested in?
What is the timeline?

We are trying to move some of the code to a new bot that will make things much simpler. The more feature you need the more time it would take, so we need to decide if we should create a new instance of the existing bot, or wait for the new bot to be ready.

Sorry for falling off the face of this issue for a bit!
The important ones to me would be the check-labels munger and the submit queue / LGTM merge logic. I know the second of those is much more complicated.
Timeline isn't urgent (obviously if I can forget about this for a month :roll_eyes:).
I'm considering running it manually for the labels.yaml bit if that sounds reasonable.
Are there any others you'd expect I'd want or has anything about how easy this might be changed? @apelisse


Allow setting node labels and taints via chart config for CAPI clusters

towards: https://github.com/giantswarm/roadmap/issues/1583
As a cluster admin, I want to be able to ensure that all nodes in a node pool get a certain set of labels, annotations, or taints, so that I can easily schedule CPU- or memory-intensive workload on nodepools of appropriate instance flavors.
Acceptance Criteria:
Given a Cluster API Workload Cluster, when I create a nodepool X then I should be able to specify annotations/taints/labels to be applied to the nodes in the nodepool X.

this has been already implemented for CAPG and CAPA (reference implementation)
https://github.com/giantswarm/roadmap/issues/1587
https://github.com/giantswarm/roadmap/issues/1586


Bag redraws when transferring or selling items

Addon Version
v0.1.89
World of Warcraft Version
Retail
Describe the bug
On occasion, when I transfer items from bag to bank or sell items, the bag will redraw itself, changing the location of items left in the bag.  This doesn't typically happen, so it's not a consistent bug.  It seems to happen when clicking items quickly in succession, but I haven't pin pointed it yet.
Steps to reproduce
Hard to consistently recreate.  Transfer items from bag to bank, quickly, seems to sometimes do it, but not every time.

I get this relatively consistently, Had a very frustrating time trying to transfer things from bank to bags or bags to bank, since I would redraw every time the numbers went below whatever threshold. I kept almost transferring the wrong items when I went to click on next in the row and the row suddenly wasn't there anymore.
Ideally (to me) redraw shouldn't happen unless I manually click to sort if the bag is already open.


Can it be used to Storyboard? And Is it written by Swift 3.0 now?

Your frameworks are really really awesome ! And I have two questions to ask you.

Can they(KPCxxx UI frameworks) be used to Storyboard ?

Are they written by Swift 3.0 beta now or Swift 2.2 ?

The framework is written in Swift 2.2. Storyboards work just fine -- in fact, @onekiloparsec wrote the demo app with a Storyboard.

@DivineDominion said it all. As for Swift3, we'll wait first it is officially out. No need to rush too soon, it will have some non-trivial impact. See https://twitter.com/siestaframework/status/771117828829175808 and similar.

Thanks for reply. :-) And I want to know do you guys plan to make KPCTabsControl to compatible with the macOS 10.12 native Tabs feature ?

Yeah, I see. Thanks for your efforts. I'm a rookie in macOS development, I prefer macOS dev to iOS dev. :-) And I'll try my best to learn to use your frameworks. I think I'll be happy with using your awesome frameworks. :-)


[@shopify/react-form] Undirty form state

Description
Fixes #1463
Some consumers of @shopify/react-form would like an easier way of "undirtying" their form state, especially after a successful submission. This PR introduces:

An optional boolean param/config makeCleanAfterSubmit (defaults to false) for useSubmit and useForm, which, if true, will clear the dirty state of the fields upon a successful submission (i.e. set default values to be the most recently submitted values)
useForm's returned Form object also now contains a bound makeClean callback in parity with reset
For other use cases, we provide a simple utility makeCleanFields

Minor fixes: Polish docs/tests
Tophatting
Tophatted with the following steps:

Playground code

import {hot} from 'react-hot-loader/root';
import React from 'react';
import {PlaygroundProvider} from 'foundation/PlaygroundProvider';
import {Page, Card, TextField, Button} from '@shopify/polaris';
import {
  useField,
  useForm,
  submitSuccess,
} from '@shopify/react-form';

export default hot(function Playground() {
  const fields = {
    field1: useField('field1_default'),
    field2: useField('field2_default'),
    field3: useField('field3_default'),
  };
  const {
    fields: {field1, field2, field3},
    dirty,
    submit,
    makeClean,
  } = useForm({
    fields,
    onSubmit: async (values) => {
      console.log('You submitted the form!:', values);
      console.log('It should also undirty all the fields in the form');
      return submitSuccess();
    },
    makeCleanAfterSubmit: true,
  });

  return (
    <PlaygroundProvider>
      <Page title="@shopify/react-form: undirtyForm demo">
        <Card title={dirty ? 'This form is dirty' : 'This form is clean'}>
          <Button onClick={makeClean}>Undirty Form</Button>
          <TextField
            autoComplete={false}
            label={`Field 1 (current default: ${field1.defaultValue})`}
            {...field1}
          />
          <TextField
            autoComplete={false}
            label={`Field 2 (current default: ${field2.defaultValue})`}
            {...field2}
          />
          <TextField
            autoComplete={false}
            label={`Field 3 (current default: ${field3.defaultValue})`}
            {...field3}
          />
          <Button onClick={submit}>Submit</Button>
        </Card>
      </Page>
    </PlaygroundProvider>
  );
});

Pull this branch down in quilt
While in quilt, yarn tophat packages/react-form ../web
dev cd web, and paste the code above into playground/Playground.tsx
yarn playground
Go to localhost:8080 in your browser and make sure that the code works as expected. Optionally, mess around with the playground code and check other use cases

Type of change

[x] @shopify/react-form Minor: New feature (non-breaking change which adds functionality)

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above

I'm getting the following error's in the playground when 🎩 ing 🤔

I'm getting the following error's in the playground when 🎩 ing 🤔

I think I also got that earlier. For me, just Ctrl-C and running it again worked for me 🤔


internal dependency conflict appears when compiling google-cloud-pubsub

Reposting this submission to<EMAIL_ADDRESS>as a bug:
The cloud pubsub library is not working with Android Studio 2.2.1 (Build #AI-145.3330264, built on October 6, 2016, JRE: 1.8.0_76-release-b03 amd64, JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o) under Debian (3.2.0-4-amd64 #1 SMP Debian 3.2.81-2 x86_64 GNU/Linux).
I added [compile group: 'com.google.cloud', name: 'google-cloud-pubsub', version: '0.4.0'] to gradle file, but it states the following: "Execution failed for task ':app:prepareDebugAndroidTestDependencies'.>Dependency Error. See console for details."
I checked the console and the output shows the following: "Conflict with dependency 'com.google.code.findbugs:jsr305'. Resolved versions for app (3.0.0) and test app (2.0.1) differ. See http://g.co/androidstudio/app-test-app-conflict for details.".
I tried to solve it by adding the following line to the android{} section of gradle file: "configurations.all { resolutionStrategy.force 'com.google.code.findbugs:jsr305:3.0.0' }", but it resulted in the following output in console(see below):
"Error:FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:transformResourcesWithMergeJavaResForDebug'.

com.android.build.api.transform.TransformException: com.android.builder.packaging.DuplicateFileException: Duplicate files copied in APK META-INF/LICENSE
File1: /home/debi/.gradle/caches/modules-2/files-2.1/com.google.auto.value/auto-value/1.1/f6951c141ea3e89c0f8b01da16834880a1ebf162/auto-value-1.1.jar
File2: /home/debi/.gradle/caches/modules-2/files-2.1/org.codehaus.jackson/jackson-core-asl/1.9.11/e32303ef8bd18a5c9272780d49b81c95e05ddf43/jackson-core-asl-1.9.11.jar
File3: /home/debi/.gradle/caches/modules-2/files-2.1/com.google.inject/guice/4.0/f990a43d3725781b6db7cd0acf0a8b62dfd1649/guice-4.0.jar

Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output. "

What should I do?

@kir-titievsky I'll try to have a look at this. First and second errors appear to be unrelated though. Also please, be aware that we do not explicitly support Android at the moment.

com.android.build.api.transform.TransformException: com.android.builder.packaging.DuplicateFileException: Duplicate files copied in APK META-INF/LICENSE

This kind of duplication errors seems to be quite common in Android. To avoid duplication you could try adding to your build file:
packagingOptions {
    exclude 'META-INF/LICENSE'
}

Hi,
Just want to update it with the recent gradle configuration:
Gradle:
apply plugin: 'com.android.application'
dependencies {
compile fileTree(include: ['*.jar'], dir: 'libs')
androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
exclude group: 'com.android.support', module: 'support-annotations'
})
compile group: 'com.google.cloud', name: 'google-cloud-pubsub', version: '0.4.0'
compile 'com.android.support:appcompat-v7:23.4.0'
testCompile 'junit:junit:4.12'

}
android {
compileSdkVersion 23
buildToolsVersion '24.0.3'
defaultConfig {
applicationId "com.example.debi.pubsub0"
minSdkVersion 15
targetSdkVersion 23
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

configurations.all {
    resolutionStrategy.force 'com.google.code.findbugs:jsr305:3.0.0'
}

packagingOptions {
    pickFirst 'META-INF/LICENSE'
    pickFirst  'META-INF/io.netty.versions.properties'
    pickFirst 'META-INF/INDEX.LIST'
}

/*packagingOptions {
    exclude 'META-INF/LICENSE'
    exclude  'META-INF/io.netty.versions.properties'
    exclude 'META-INF/INDEX.LIST'
}*/

}
Console:

Warning:WARNING: Dependency org.apache.httpcomponents:httpclient:4.0.1 is ignored for debug as it may be conflicting with the internal version provided by Android.
Warning:WARNING: Dependency org.json:json:20151123 is ignored for debug as it may be conflicting with the internal version provided by Android.
Warning:WARNING: Dependency org.apache.httpcomponents:httpclient:4.0.1 is ignored for debug as it may be conflicting with the internal version provided by Android.
Warning:WARNING: Dependency org.json:json:20151123 is ignored for debug as it may be conflicting with the internal version provided by Android.
Error:trouble processing "javax/transaction/HeuristicCommitException.class":
Error:Ill-advised or mistaken usage of a core class (java.* or javax.*)
Error:when not building a core library.
Error:This is often due to inadvertently including a core library file
Error:in your application's project, when using an IDE (such as
Error:Eclipse). If you are sure you're not intentionally defining a
Error:core class, then this is the most likely explanation of what's
Error:going on.
Error:However, you might actually be trying to define a class in a core
Error:namespace, the source of which you may have taken, for example,
Error:from a non-Android virtual machine project. This will most
Error:assuredly not work. At a minimum, it jeopardizes the
Error:compatibility of your app with future versions of the platform.
Error:It is also often of questionable legality.
Error:If you really intend to build a core library -- which is only
Error:appropriate as part of creating a full virtual machine
Error:distribution, as opposed to compiling an application -- then use
Error:the "--core-library" option to suppress this error message.
Error:If you go ahead and use "--core-library" but are in fact
Error:building an application, then be forewarned that your application
Error:will still fail to build or run, at some point. Please be
Error:prepared for angry customers who find, for example, that your
Error:application ceases to function once they upgrade their operating
Error:system. You will be to blame for this problem.
Error:If you are legitimately using some code that happens to be in a
Error:core package, then the easiest safe alternative you have is to
Error:repackage that code. That is, move the classes in question into
Error:your own package namespace. This means that they will never be in
Error:conflict with core system classes. JarJar is a tool that may help
Error:you in this endeavor. If you find that you cannot do this, then
Error:that is an indication that the path you are on will ultimately
Error:lead to pain, suffering, grief, and lamentation.
Error:1 error; aborting
Information:BUILD FAILED

Some warnings have been suppressed using 'pickFirst' or 'exclude' methods, but it doesn't seem to go beyond that. The problem disappears only if "compile group: 'com.google.cloud', name: 'google-cloud-pubsub', version: '0.4.0'" gets removed from dependencies(other libraries work fine).
Thanks.

Hi @jfarkhat,
try replacing:
compile group: 'com.google.cloud', name: 'google-cloud-pubsub', version: '0.4.0'

with:
compile ('com.google.cloud:google-cloud-pubsub:0.4.0') {
    exclude group: 'com.google.api-client', module: 'google-api-client-appengine'
}

This should exclude the dependency that is causing troubles.

Good, but it compiles(and launches) default MainActivity file with the following weird story:

Warning:WARNING: Dependency org.apache.httpcomponents:httpclient:4.0.1 is ignored for debug as it may be conflicting with the internal version provided by Android.
Warning:WARNING: Dependency org.json:json:20151123 is ignored for debug as it may be conflicting with the internal version provided by Android.
Warning:WARNING: Dependency org.apache.httpcomponents:httpclient:4.0.1 is ignored for debug as it may be conflicting with the internal version provided by Android.
Warning:WARNING: Dependency org.json:json:20151123 is ignored for debug as it may be conflicting with the internal version provided by Android.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(autovalue.shaded.org.apache.commons.lang.builder.HashCodeBuilder$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(autovalue.shaded.org.apache.commons.lang.builder.ToStringStyle$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$ClassEmitter$2) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$ClassNameReader$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$DebuggingClassWriter$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$ClassEmitter$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$ClassEmitter$3) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$AbstractClassGenerator$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$10) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$15) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$2) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$4) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$6) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$7) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$8) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$9) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$KeyFactory$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$KeyFactory$2) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$ReflectUtils$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$ReflectUtils$2) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$11) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$12) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$13) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$14) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$16) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$3) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$EmitUtils$5) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$ReflectUtils$4) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.core.$ReflectUtils$3) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$Enhancer$2) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$BridgeMethodResolver$BridgedFinder$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$Enhancer$5) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$Enhancer$6) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$Enhancer$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$Enhancer$3) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$Enhancer$4) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$MethodInterceptorGenerator$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$MethodInterceptorGenerator$2) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.reflect.$FastClassEmitter$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.proxy.$NoOp$1) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.reflect.$FastClassEmitter$2) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.reflect.$FastClassEmitter$3) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.google.inject.internal.cglib.reflect.$FastClassEmitter$4) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is not an inner class.
Information:BUILD SUCCESSFUL
Information:Total time: 1 mins 33.722 secs
Information:352 errors
Information:4 warnings

When 3 lines of code were added to MainActivity(within AsyncTask):
"PubSubOptions.Builder optionsBuilder = PubSubOptions.builder();          optionsBuilder.projectId("some-project-id");
PubSub pubsub = optionsBuilder.build().service();"
it generated the following output:
Caused by: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/api/client/googleapis/json/GoogleJsonResponseException;
at com.google.cloud.pubsub.PubSubOptions$DefaultPubSubRpcFactory.create(PubSubOptions.java:62)
at com.google.cloud.pubsub.PubSubOptions$DefaultPubSubRpcFactory.create(PubSubOptions.java:54)
at com.google.cloud.ServiceOptions.rpc(ServiceOptions.java:399)
at com.google.cloud.pubsub.PubSubImpl.(PubSubImpl.java:115)
at com.google.cloud.pubsub.PubSubOptions$DefaultPubSubFactory.create(PubSubOptions.java:43)
at com.google.cloud.pubsub.PubSubOptions$DefaultPubSubFactory.create(PubSubOptions.java:38)
at com.google.cloud.ServiceOptions.service(ServiceOptions.java:391)
at com.example.debi.pubsub0.MainActivity$PubSubThread.doInBackground(MainActivity.java:35)
at com.example.debi.pubsub0.MainActivity$PubSubThread.doInBackground(MainActivity.java:29)
at android.os.AsyncTask$2.call(AsyncTask.java:288)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.google.api.client.googleapis.json.GoogleJsonResponseException" on path: DexPathList[[dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-support-annotations-23.4.0_83df98ca7e6243483ae2f9dd2c9e743f93dd45d6-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_9-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_8-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_7-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_6-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_5-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_4-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_3-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_2-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_1-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-slice_0-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-protobuf-lite-3.0.1_0a49e23204cfe9faaebba766220490252901c756-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-protobuf-javanano-3.0.0-alpha-5_1793c7359f38eaa2066f295f481359bd93f00f88-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-protobuf-java-util-3.0.0_286e1d408083f2753f6c295d7d8e98af157e2014-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-protobuf-java-3.0.0_2d9d1cd9f42907195ad4221814c8bc9159bbda0d-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-okio-1.6.0_26df68bf1847c37120ee716e3bf798e678d38845-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-okhttp-2.5.0_3acda5262df95f0a5e16db7c6468ae9a84dba0b7-classes.dex", dex file "/data/data/com.example.debi.pubsub0/files/instant-run/dex/slice-netty-transport-4.1.3.Final_1cf15f1ac873d01fbdd0d282f13294e044ec5c12-classes.dex", dex file "/data/data/com.examp

Could you please format your previous posts? Also please don't cut-and-paste these long logs but rather attach a public gist to your post.
Are you excluding other artifacts in addition to the one I suggested you to exclude?

I am sorry :)))
Here is the output2 from adding the 3rd line of the code to MainActivity:
PubSubOptions.Builder optionsBuilder = PubSubOptions.builder();
optionsBuilder.projectId("miniserver17");
PubSub pubsub = optionsBuilder.build().service();
https://gist.github.com/jfarkhat/3fcdce92eba2a918ef6163c89a3f9913

@jfarkhat I had a deeper look at this, try adding this dependency:
compile group: 'com.google.api-client', name: 'google-api-client', version: '1.21.0'

Hi,
Compile group: 'com.google.api-client', name: 'google-api-client', version: '1.21.0' didn't work(the same errors). But the issue is no longer a problem and I found much simpler solution to it. Thanks )

I am still getting this error, any update on this thread ? Please advise. Thanks.


Don't use HistoricalXxxPrototypes in PooledTopNAlgorithm when Cursor's offset is FilteredOffset

Fixes #5132.

👍  thanks @leventov


export function in shell cell?

Hi there, is there a way how to export functions in shell?
So I can define one in the first cell and then use it afterwads in consequent cells ?
function fetch(){
    link=$1

    curl -L \
    -H "Accept: application/vnd.github+json" \
    -H "Authorization: Bearer $TOKEN" \
    -H "X-GitHub-Api-Version: 2022-11-28" \
    $link
}

fetch "https://api.github.com/"

Hi @shafr, Runme currently does not support block-scope sharing of variables and functions. It's a design tradeoff to make Runme work right out of the box, across language runtimes (shell/bash, python, ruby, node/deno/bun etc), without any prerequisite requirements, specifically bash versions and configurations.
Essentially every cell is stateless across the notebook. However, you reference cell outputs (much like piping) and manipulate ENV variables which will be sticky across the whole Runme session and even across notebooks. More details here in our quick start guide.
You could make something similar work by sourcing the functions definitions in every cell block. Here's an example: https://gist.github.com/sourishkrout/f92132a1ec0dc5cbe79c8ffdbe81cbaa#file-exports-01HY1B7ASJ0517Q6FNGQBFWBK3.md
If it'd be helpful we could file a feature request which would allow declaring a script, e.g. exports.sh or a cell ID/name, in Runme's document-/cell-level config that would automatically source the exports ahead of executing every file. This would help reducing "documentation clutter".
Please let me know what you think.


feat: rename running EXE on Windows

This tries to cover for the case where Windows doesn't allow the currently-running EXE to be modified. We instead rename it into a temporary directory, and move it back to where it was if the update failed.

We can also consider doing this on all platforms; it's currently limited to Windows because it's not necessary on Linux or macOS.


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've rerendered the recipe as instructed in #6.
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Whenever possible python packages should use pip. See https://conda-forge.org/docs/maintainer/adding_pkgs.html#use-pip

@conda-forge/colormath could someone merge this please?

@conda-forge/core Could anyone check this please? Looks like maintainer @ewels is busy for a good reason 🍼  (congrats! 😄)


Review support for discovering and running of unit tests

Recently we identified the fact that the extension fails to discover and run unit tests found in the PTVSD project.
At least one bug was identified in the process.
We might want to review this feature against some popular python repos and identify areas that need to be improved.
@brettcannon @ericsnowcurrently @qubitron cc

I am not using PTVSD in my project but discovering and running unit tests was working until I upgrade Code & Python extension last 3 days. I am not sure which one caused the problem.
I am using Python 3.6 and unittest package.
Is there anything I can check and share ?

@mehmetilker
Please could you create a separate issue. Please could you provide a sample repo that I could use to replicate the issue.

https://github.com/Microsoft/vscode-python/issues/1095
Done, thanks.

Closing this as stale.


[Feature][master] When deployed on k8s and yarn, dolphinscheduler supports worker elastic scaling

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
When deployed on cluster managers such as k8s and yarn, dolphinscheduler supports worker elastic scaling
The initial idea is as follows：

Add ResourceManager to the master server.
ResourceManager is responsible for the management and application of worker resources.
ResourceManager perceives the online and offline of worker nodes through the register.
The ResourceManager goes to the cluster manager to apply for resources according to the per workflow. The resources are released at the end of the workflow.

Use case
worker elastic scaling
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The ResourceManager goes to the cluster manager to apply for resources according to the per workflow. The resources are released at the end of the workflow.

Hi @huagetai , in ds, master handle workflow/process and worker handle task, so what about managing resources for pre task?

hi, any progress?

in this picture,  I want to know that how to handle the worker when the task finished in the K8s scene?

hi, any progress?

It seems no progress update. @davidzollo you can try if you are interested.

in this picture, I want to know that how to handle the worker when the task finished in the K8s scene?

I think there're two mode: worker per pod, task per pod, the issue description should be the second one.

Hi @huagetai , may I ask whether there will be any follow-ups for this issue? Thanks : )

BTW, I think we may not put ResourceManager into master. We need more discussions on this point.

BTW, I think we may not put ResourceManager into master. We need more discussions on this point.

Hi, @EricGao888, i think ds should not get involved in executors resource management. BTW, i think we should keep the concept of Master and Worker, still one for handling workflow, one for handling task, then introduce new concept of Executor in charge of actual task execution.
Why separate Executor and Worker?

In current design, many types of task directly runs on worker. I think scheduler have to focus on scheduling, rather execution. So it's better not execute task on ds' Worker node.
Worker receives task from Master and is still in charge of listening to local/remote(corresponding to whether ds is deployed as standalone mode or ds on k8s/yarn) task execution. To be specific, if in standalone mode, Worker directly launch Executor at local, rather, launch remote executor in external k8s or yarn cluster, which is related to this issue.

In a word, this could be a big architectural change. Anyway, just a humble suggestion, feel free to correct me, i'm interested in any further discussion!

BTW, I think we may not put ResourceManager into master. We need more discussions on this point.

Hi, @EricGao888, i think ds should only get involved in executors resource management in standalone mode. BTW, i think we should keep the conception of Master and Worker, and introduce new conception of Executor in charge of actual task execution, like design in Spark.
In current design, many types of task directly runs on worker. I think ds' Master and Worker have to focus on scheduling, only in standalone mode, Worker is in charge of computing resource management and launch Executor. In other modes like DS on K8S / Yarn, Master can directly launch remote Executor in external K8S or Yarn cluster which in charge of resource management now.
In a word, this could be a big architectural change. Anyway, just a humble suggestion, feel free to correct me, i'm interested in any further discussion!

In this Feature, I would like to know how the following three questions are designed

For timed workflow, when will their pod be created?  Because api server takes a certain amount of time to create the pod, will the task start time be delayed
For resource allocation, if PODS are created dynamically based on workflow or task, how do dolphinscheduler specify the number of cpus and memory required by each pod?  Is it specified when workflow is created?
When deploying dolphinscheduler, whether dynamic worker creation is optional and whether the old deployment mode is retained, such as dolphinscheduler on k8s and dolphinscheduler on native k8s

In this Feature, I would like to know how the following three questions are designed

For timed workflow, when will their pod be created?   Because api server takes a certain amount of time to create the pod, will the task start time be delayed
For resource allocation, if PODS are created dynamically based on workflow or task, how do dolphinscheduler specify the number of cpus and memory required by each pod?   Is it specified when workflow is created?
When deploying dolphinscheduler, whether dynamic worker creation is optional and whether the old deployment mode is retained, such as dolphinscheduler on k8s and dolphinscheduler on native k8s

n other modes like DS on K8S / Yarn, Master can directly launch remote Executor in external K8S or Yarn cluster which in charge of resource management now.

@Radeity Thanks for being interested. Actually we haven't decided how to do it yet.
In other modes like DS on K8S / Yarn, Master can directly launch remote Executor in external K8S or Yarn cluster which in charge of resource management now. I'm +1 to this point.
DS should only get involved in executors resource management in standalone mode. For this, I think we do not need to spend time thinking about how to manage executor resource in standalone mode since standalone mode is only for development and experience, not for production.

In this Feature, I would like to know how the following three questions are designed

For timed workflow, when will their pod be created?   Because api server takes a certain amount of time to create the pod, will the task start time be delayed
For resource allocation, if PODS are created dynamically based on workflow or task, how do dolphinscheduler specify the number of cpus and memory required by each pod?   Is it specified when workflow is created?
When deploying dolphinscheduler, whether dynamic worker creation is optional and whether the old deployment mode is retained, such as dolphinscheduler on k8s and dolphinscheduler on native k8s

@hdygxsj Good questions.

I think we could make use of K8S HPA with the number of tasks in TaskPriorityQueue as the metric. DS will scale the worker once the number of queue tasks reaches a threshold. In this way, when task get dispatched, the workers has already been running and there will be no latency.
In the design of elastic worker, we could follow one worker one pod instead of dynamically creating pod based on task, which is another thing stated in #13316 K8S Executor.
IMHO, we could try to make things, e.g. executor, extensible and pluggable. Users will be able to choose which to use. In this way, the design will be compatible.

related: #13316


Searching is Not properly scoped

When i do a search on this page, i get results from many other repositories. It should be limited to SPO documentation

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 65bf2c0b-b0ec-2748-e47e-af66011efe30
Version Independent ID: be3968f4-d766-0b45-384b-c51c47328a86
Content: SharePoint Online PowerShell
Content Source: sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md
Service: sharepoint-powershell
GitHub Login: @techwriter40
Microsoft Alias: kirks

@officedocsbot assign @yogkumgit

Hello @DeanGross
Thanks for your feedback.
If you mean to the functionality of the magnifying glass in the page, that is the behavior of all docs.microsoft.com and is intended to work like that.
Thank you

@get-itips  Thank you very much for the contribution and sharing this explanation. @DeanGross
Hope this comment is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@officedocsbot close


Update to Outdated files in the dev-1.18-ko.6 branch - (1/4)

26 of 47 files to be modified

[ ] content/ko/_index.html > #21723 으로 선 반영되었음
[x] content/ko/docs/concepts/_index.md
[x] content/ko/docs/concepts/architecture/cloud-controller.md
[x] content/ko/docs/concepts/architecture/control-plane-node-communication.md > 라인 맞춤 진행
[ ] content/ko/docs/concepts/architecture/controller.md
[x] content/ko/docs/concepts/architecture/nodes.md > 라인 맞춤, 이전 Update to Outdated files 진행시 누락된 항목 반영
[ ] content/ko/docs/concepts/cluster-administration/addons.md
[ ] content/ko/docs/concepts/cluster-administration/certificates.md
[x] content/ko/docs/concepts/cluster-administration/cloud-providers.md > 라인 맞춤 진행
[ ] content/ko/docs/concepts/cluster-administration/cluster-administration-overview.md
[x] content/ko/docs/concepts/cluster-administration/kubelet-garbage-collection.md > 라인 맞춤 진행
[ ] content/ko/docs/concepts/cluster-administration/logging.md
[x] content/ko/docs/concepts/cluster-administration/manage-deployment.md
[ ] content/ko/docs/concepts/cluster-administration/networking.md
[ ] content/ko/docs/concepts/cluster-administration/proxies.md
[x] content/ko/docs/concepts/configuration/configmap.md
[ ] content/ko/docs/concepts/configuration/manage-resources-containers.md
[ ] content/ko/docs/concepts/configuration/organize-cluster-access-kubeconfig.md
[ ] content/ko/docs/concepts/configuration/overview.md
[x] content/ko/docs/concepts/configuration/pod-overhead.md > 라인 맞춤 진행
[ ] content/ko/docs/concepts/configuration/pod-priority-preemption.md
[ ] content/ko/docs/concepts/configuration/resource-bin-packing.md
[x] content/ko/docs/concepts/containers/container-environment.md > 라인 맞춤 진행
[ ] content/ko/docs/concepts/containers/container-lifecycle-hooks.md
[x] content/ko/docs/concepts/containers/images.md
[x] content/ko/docs/concepts/containers/overview.md > 라인 맞춤 진행
[x] content/ko/docs/concepts/containers/runtime-class.md > 라인 맞춤 진행
[x] content/ko/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation.md
[x] content/ko/docs/concepts/extend-kubernetes/api-extension/custom-resources.md
[ ] content/ko/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
[ ] content/ko/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md
[ ] content/ko/docs/concepts/extend-kubernetes/extend-cluster.md
[ ] content/ko/docs/concepts/extend-kubernetes/operator.md
[x] content/ko/docs/concepts/overview/components.md > 누락 내용 맞춤 및 라인 맞춤 진행
[x] content/ko/docs/concepts/overview/kubernetes-api.md
[ ] content/ko/docs/concepts/overview/what-is-kubernetes.md
[ ] content/ko/docs/concepts/overview/working-with-objects/annotations.md
[x] content/ko/docs/concepts/overview/working-with-objects/common-labels.md > 라인 맞춤 진행
[x] content/ko/docs/concepts/overview/working-with-objects/field-selectors.md
[x] content/ko/docs/concepts/overview/working-with-objects/kubernetes-objects.md > 라인 맞춤 진행
[x] content/ko/docs/concepts/overview/working-with-objects/labels.md > 라인 맞춤 진행
[x] content/ko/docs/concepts/overview/working-with-objects/names.md > 라인 맞춤 진행
[ ] content/ko/docs/concepts/overview/working-with-objects/namespaces.md
[x] content/ko/docs/concepts/overview/working-with-objects/object-management.md > 누락 내용 맞춤 및 라인 맞춤 진행
[x] content/ko/docs/concepts/policy/limit-range.md > 라인 맞춤 진행
[x] content/ko/docs/concepts/policy/pod-security-policy.md
[x] content/ko/docs/concepts/policy/resource-quotas.md > 라인 맞춤 진행

/language ko
from #21677

/assign @pjhwa

@gochist PR 리뷰가 완료되고 나면, 최종적으로 확인 및 승인 부탁드립니다.. ^^
/assign @gochist

리뷰 확인 및 반영 완료했습니다. 최종 확인 부탁드립니다. 😄

/lgtm

@ysyukr 감사합니다! 하나의 커밋으로 squash하고 승인합니다.
/lgtm
/approve


uninitialized constant Mysql2::Client::SECURE_CONNECTION

When I'm trying to set up the database (bundle exec rake db:setup) I get the following error:
Bundler::GemRequireError: There was an error while trying to load the gem 'mysql2'.
Gem Load Error is: uninitialized constant Mysql2::Client::SECURE_CONNECTION
Backtrace for gem load error is:
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2/client.rb:12:in `<class:Client>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2/client.rb:2:in `<module:Mysql2>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2/client.rb:1:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2.rb:10:in `require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2.rb:10:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:86:in `require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:86:in `block (2 levels) in require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `each'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `block in require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `each'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler.rb:102:in `require'
/home/peatio/peatio/config/application.rb:12:in `<top (required)>'
/home/peatio/peatio/Rakefile:5:in `require'
/home/peatio/peatio/Rakefile:5:in `<top (required)>'
/home/peatio/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/rake/rake_module.rb:28:in `load'
/home/peatio/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/rake/rake_module.rb:28:in `load_rakefile'
/home/peatio/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/rake/application.rb:689:in `raw_load_rakefile'
/home/peatio/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/rake/application.rb:94:in `block in load_rakefile'
/home/peatio/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/rake/application.rb:176:in `standard_exception_handling'
/home/peatio/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/rake/application.rb:93:in `load_rakefile'
/home/peatio/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/rake/application.rb:77:in `block in run'
/home/peatio/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/rake/application.rb:176:in `standard_exception_handling'
/home/peatio/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/rake/application.rb:75:in `run'
/home/peatio/.rvm/rubies/ruby-2.2.1/bin/rake:33:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `load'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `kernel_load'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:24:in `run'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli.rb:304:in `exec'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli.rb:11:in `start'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/exe/bundle:27:in `block in <top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/exe/bundle:19:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/bundle:23:in `load'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/bundle:23:in `<main>'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `eval'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `<main>'
Bundler Error Backtrace:
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:89:in `rescue in block (2 levels) in require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:85:in `block (2 levels) in require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `each'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `block in require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `each'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler.rb:102:in `require'
/home/peatio/peatio/config/application.rb:12:in `<top (required)>'
/home/peatio/peatio/Rakefile:5:in `require'
/home/peatio/peatio/Rakefile:5:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `load'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `kernel_load'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:24:in `run'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli.rb:304:in `exec'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli.rb:11:in `start'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/exe/bundle:27:in `block in <top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/exe/bundle:19:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/bundle:23:in `load'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/bundle:23:in `<main>'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `eval'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `<main>'
NameError: uninitialized constant Mysql2::Client::SECURE_CONNECTION
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2/client.rb:12:in `<class:Client>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2/client.rb:2:in `<module:Mysql2>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2/client.rb:1:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2.rb:10:in `require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/mysql2-0.3.15/lib/mysql2.rb:10:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:86:in `require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:86:in `block (2 levels) in require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `each'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:81:in `block in require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `each'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:70:in `require'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler.rb:102:in `require'
/home/peatio/peatio/config/application.rb:12:in `<top (required)>'
/home/peatio/peatio/Rakefile:5:in `require'
/home/peatio/peatio/Rakefile:5:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `load'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `kernel_load'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:24:in `run'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli.rb:304:in `exec'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/cli.rb:11:in `start'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/exe/bundle:27:in `block in <top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
/home/peatio/.rvm/gems/ruby-2.2.1/gems/bundler-1.12.5/exe/bundle:19:in `<top (required)>'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/bundle:23:in `load'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/bundle:23:in `<main>'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `eval'
/home/peatio/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `<main>'
(See full trace by running task with --trace)

Because your ubuntu are ubuntu 16.04. You can replace command line: gem 'mysql' -> gem 'mysql', '~> 0.3.20' in Gemfile. Then you "bundle install".
Next to: you can have more a problem: "PRIMARY KEY must be NOT NULL"
Fix it follow link below:
https://www.alexfilatov.com/2016/04/06/rails-3-migration-fails-after-mysql-upgrade-to-5-7-10/

i have same problem ,too
for ubuntu 16.04^^
would you be my partner to help me???

@songhungbk no my ubuntu version is 14.04.5

Changing the version to ~> 0.3.21 fixed it for me
gem 'mysql2', '~> 0.3.21'

I added the 0.3.21 version as recommended by @deepakmahakale but still not working:
app@e38e3cce70cb:~/peatio$ bundle exec rake db:setup --trace
rake aborted!
Psych::SyntaxError: (): did not find expected key while parsing a block mapping at line 6 column 3
/usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/psych.rb:370:in parse' /usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/psych.rb:370:in parse_stream'
/usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/psych.rb:318:in parse' /usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/psych.rb:245:in load'
/usr/local/rvm/gems/ruby-2.2.5/gems/figaro-0.7.0/lib/figaro.rb:21:in raw' /usr/local/rvm/gems/ruby-2.2.5/gems/figaro-0.7.0/lib/figaro.rb:17:in env'
/usr/local/rvm/gems/ruby-2.2.5/gems/figaro-0.7.0/lib/figaro/railtie.rb:7:in block in <class:Railtie>' /usr/local/rvm/gems/ruby-2.2.5/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:36:in call'
/usr/local/rvm/gems/ruby-2.2.5/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:36:in execute_hook' /usr/local/rvm/gems/ruby-2.2.5/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:45:in block in run_load_hooks'
/usr/local/rvm/gems/ruby-2.2.5/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:44:in each' /usr/local/rvm/gems/ruby-2.2.5/gems/activesupport-4.0.12/lib/active_support/lazy_load_hooks.rb:44:in run_load_hooks'
/usr/local/rvm/gems/ruby-2.2.5/gems/railties-4.0.12/lib/rails/application.rb:67:in inherited' /home/app/peatio/config/application.rb:15:in module:Peatio'
/home/app/peatio/config/application.rb:14:in <top (required)>' /home/app/peatio/Rakefile:5:in require'
/home/app/peatio/Rakefile:5:in <top (required)>' /usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/rake/rake_module.rb:28:in load'
/usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/rake/rake_module.rb:28:in load_rakefile' /usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/rake/application.rb:689:in raw_load_rakefile'
/usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/rake/application.rb:94:in block in load_rakefile' /usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/rake/application.rb:176:in standard_exception_handling'
/usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/rake/application.rb:93:in load_rakefile' /usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/rake/application.rb:77:in block in run'
/usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/rake/application.rb:176:in standard_exception_handling' /usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/rake/application.rb:75:in run'
/usr/local/rvm/rubies/ruby-2.2.5/lib/ruby/gems/2.2.0/gems/rake-10.4.2/bin/rake:33:in <top (required)>' /usr/local/rvm/gems/ruby-2.2.5@global/bin/rake:23:in load'
/usr/local/rvm/gems/ruby-2.2.5@global/bin/rake:23:in <main>' /usr/local/rvm/gems/ruby-2.2.5/bin/ruby_executable_hooks:15:in eval'
/usr/local/rvm/gems/ruby-2.2.5/bin/ruby_executable_hooks:15:in `'

I am having the same problem as @felipecaldas, just the same problem

I. Already fix it !!!
Just take a look on my project
On Tue, 6 Jun 2017 at 11:58 PM Jesus Figueroa<EMAIL_ADDRESS>wrote:

I am having the same problem as @felipecaldas
https://github.com/felipecaldas, just the same problem
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/peatio/peatio/issues/528#issuecomment-306532759, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGitiKqKHA768c2UxffUKSX3dHrXCkzPks5sBXcogaJpZM4J4Uwl
.

Thanks espero poder compilarlo en Ubuntu 16.04
Jesús Figueroa (Shadow Myst)
http://shadowmyst.net
El 6 jun. 2017 11:24 AM, "chuang po chun"<EMAIL_ADDRESS>escribió:
I. Already fix it !!!
Just take a look on my project
On Tue, 6 Jun 2017 at 11:58 PM Jesus Figueroa<EMAIL_ADDRESS>wrote:

I am having the same problem as @felipecaldas
https://github.com/felipecaldas, just the same problem
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/peatio/peatio/issues/528#issuecomment-306532759, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
AGitiKqKHA768c2UxffUKSX3dHrXCkzPks5sBXcogaJpZM4J4Uwl>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/peatio/peatio/issues/528#issuecomment-306540472, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APwg2oDzUbkLRs2CuVnrckCHFJA0QJADks5sBX0-gaJpZM4J4Uwl
.

Are you using Mohammed's fork or not? You should be using his.
On 7 Jun 2017 5:54 AM, "Jesus Figueroa"<EMAIL_ADDRESS>wrote:

Thanks espero poder compilarlo en Ubuntu 16.04
Jesús Figueroa (Shadow Myst)
http://shadowmyst.net
El 6 jun. 2017 11:24 AM, "chuang po chun"<EMAIL_ADDRESS>escribió:
I. Already fix it !!!
Just take a look on my project
On Tue, 6 Jun 2017 at 11:58 PM Jesus Figueroa<EMAIL_ADDRESS>wrote:

I am having the same problem as @felipecaldas
https://github.com/felipecaldas, just the same problem
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/peatio/peatio/issues/528#issuecomment-306532759, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
AGitiKqKHA768c2UxffUKSX3dHrXCkzPks5sBXcogaJpZM4J4Uwl>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/peatio/peatio/issues/528#issuecomment-306540472, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
APwg2oDzUbkLRs2CuVnrckCHFJA0QJADks5sBX0-gaJpZM4J4Uwl>
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/peatio/peatio/issues/528#issuecomment-306598546, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADr4eL8pRDWrBjnaXuRqyxs3aS9_Nm6Bks5sBa5mgaJpZM4J4Uwl
.

I'm trying both, which is the first to work, Mohammed probe it in my old installation and I did not work, right now I'm trying this on a clean Ubuntu

I suggest sticking to Mohammed's fork only. Cheers.
On 7 Jun 2017 10:34 AM, "Jesus Figueroa"<EMAIL_ADDRESS>wrote:

I'm trying both, which is the first to work, Mohammed probe it in my old
installation and I did not work, right now I'm trying this on a clean Ubuntu
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/peatio/peatio/issues/528#issuecomment-306652338, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADr4eJdGCjKCrBzMqXjqhqWpyZBJy_pkks5sBfAfgaJpZM4J4Uwl
.

Well, I'm going to test Mohammed again with a new ubuntu install


App exits with TypeError when attempting to retrieve os_errors values from a cache

This bug was fixed in this commit, which was included in the v6.0.0 Beta 4 release.


Expose triggers for playback stop

I would like to be able to mute/unmute my amp on play/stop events.
So far the source control allows me to use the convenience_switch to unmute the amp on playback start but there doesn't seem to be any event flowing back on playback stop.
I would really like to avoid polling the state of a zone via the transport API every second to get this done.
Thanks!

When you subscribe to the st

Oops sorry, when you subscribe to the state, it'll respond back multiple times on state changes.

Ah, missed that, thanks!
What are the valid zone states? I see playing and paused, is there a case where the state is stopped or something else?

"playing", "paused", "loading", or "stopped"

hit cmd/control-t to stop, or longpress the pause icon
loading is common for slow NAS/network or for TIDAL

Thanks!


[BUG]: CSI Proxy Version Upgrade to v1.1.3 Fails to Update Node, Causing Plan State Error and State Inconsistencies

Rancher Server Setup

Rancher version: v2.8.3
Installation option (Docker install/Helm Chart): v2.16.8-rancher2

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2

Information about the Cluster

Kubernetes version: v1.28.11+rke2r1
Cluster Type (Local/Downstream): Downstream Cluster

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
Admin

Describe the bug
When trying to upgrade the CSI proxy version to v1.1.3 in our downstream cluster, only the Terraform state file updates, but the node itself does not change, resulting in an error applying plan state. This discrepancy creates inconsistencies between the desired and actual states of the cluster.

Temporary Workaround: To successfully apply the CSI proxy upgrade, I need to drain the node and then recreate it. This workaround is not ideal and introduces unnecessary complexity to the management process, I am using Terraform for cluster management.
To Reproduce
Changing the default version of CSI_PROXY_VERSION, whether upgrading or downgrading, results in an error.
Result
Expected Result
CSI_PROXY_VERSION should get upgraded without recreating the node.
Screenshots
Mentioned above

Is there any plan to include this in a future release?