How to use this plugin with client version 5.0

Hello,
I was exploring this tool and got this error while trying to migrate:
Unexpected exception com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: com.ibm.team.filesystem.cli.core.util.CLIFileSystemClientException: Status ERROR: com.ibm.team.filesystem.cli.core code=2 Could not log in to https://url/: Your client is version 5.0.1, and the server is version 5.0.  These versions are not compatible. Your client is version 5.0.1, and the server is version 5.0.  These versions are not compatible. Check the log for details about the error at "C:\Users\user\AppData\Local\jazz-scm". If you have configured custom logging check your log configuration settings for the path to the log file. null
Is there plugin versions for client 5.0?

Hi Raagun,
This tool is an extension of the scm commandline provided by ibm. We included the link to version 5.0.1 in our readme (allthough version 6.0.1 is already out :) )
Long story short, you can find the scmTools for version HERE :+1:
Please give us feedback, if it worked out for you. :smiley:

Yes, but plugin does not compile with 5.0 and our server uses version 5.0.
Versions 5.0 and 5.0.1 are incompatible, produces the error.

Could you try it with the a prebuilt docker image rtcto/rtc2git:5.0 and check if you still got the same problem?

Removed explicit versions for required RTC plugins. That way the build worked for me and Version 5.0


kdePackages.fcitx5-configtool: 5.1.5 -> 5.1.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/fcitx5-configtool/versions.
meta.description for kdePackages.fcitx5-configtool is: Configuration Tool for Fcitx5
meta.homepage for kdePackages.fcitx5-configtool is: https://github.com/fcitx/fcitx5-configtool
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
fcitx result is not automatically checked because some binaries stick around

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath

kdePackages.fcitx5-configtool
kdePackages.fcitx5-with-addons
libsForQt5.fcitx5-configtool
libsForQt5.fcitx5-with-addons
plasma5Packages.fcitx5-configtool
plasma5Packages.fcitx5-with-addons
qt6Packages.fcitx5-configtool
qt6Packages.fcitx5-with-addons

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ppqaaa6c0qdmvz53lyiva0fp346vpd74-fcitx5-configtool-5.1.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kdePackages.fcitx5-configtool https://github.com/r-ryantm/nixpkgs/archive/299f8c21a3313d90cb24d6978294d64e5b6046d9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/299f8c21a3313d90cb24d6978294d64e5b6046d9#kdePackages.fcitx5-configtool

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ppqaaa6c0qdmvz53lyiva0fp346vpd74-fcitx5-configtool-5.1.6
ls -la /nix/store/ppqaaa6c0qdmvz53lyiva0fp346vpd74-fcitx5-configtool-5.1.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages built:

kdePackages.fcitx5-configtool
kdePackages.fcitx5-with-addons
libsForQt5.fcitx5-configtool
libsForQt5.fcitx5-with-addons

Maintainer pings
cc @poscat0x04 for testing.

Superseded by https://github.com/NixOS/nixpkgs/pull/316403


Joints are complete now

This clean ups the last things with the joints, they work properly now.
Issue #56 has been solved meanwhile

Actually, since this is straightforward, I'm merging it directly otherwise the other changes are blocked

Pull Request Test Coverage Report for Build 117

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 31.53%

Totals

Change from base Build 115:
0.0%

Covered Lines:
169

Relevant Lines:
536

💛  - Coveralls


Fix va_list processing in test_note()

Checklist

[x] tests are added or updated

(how this function could work is beyond me...  and why it built as well)

Merged. 7b4d323092bd44bbca8f8cd96709dff89277f930


Add per ENI DSCP setting

By default, use DSCP from the original outer packet.

hi @marian-pritsak - is this ready for a Merge?  Let me know :)


[docs] Fix migration experience from Material UI v4

I have just noticed how broken the migration experience from v4 is.
Open https://v4.mui.com/components/container/ 🙈.

We say "migrate to v5, go to mui.com". meaning v5 is called MUI.
We don't say anything on how to migrate", good luck

"Preparing for v6" issue (https://github.com/mui/material-ui/issues/30660)

@danilo-leal For me, this issue is about working on "MUI Core" v6, meaning coordinating Joy UI, Base UI, Material UI, MUI System to 1. all work well together and 2. without one doing a local optimization that goes against the global optimization.

but then it would contradict this PR

The way I see it, if someone using Material UI v4 cares about migrating to Material UI v5, he might not care about the extra projects that come alongside it.

The root issue for me is that we use "MUI Core v6" and "Material UI v6" interchangeably, deepening the confusion of MUI = Material UI. This is a larger versioning convo (like, why brand new packages/products are starting from v5?). (And I'd probably change the issue title if we're referring to the Core products to alleviate it a bit).

Deploy live https://v4.mui.com/components/container/

like, why brand new packages/products are starting from v5?

@danilo-leal The value could be to communicate clearly which versions are compatible together, and which versions use the same conventions. Similar to Qt whole stack being a single version: https://www.qt.io/product/features.
For example, Radix starts to feel a bit strange, they have Radix Themes, Radix Primitives, Radix Icons, Radix Colors now. They could have kept Radix for the headless UI components only. They take the risk of confusing their users but they sell the value of one ecosystem that works well together.
I wonder if we are not looking where we shouldn't. We might be over-indexing the value of isolating product names and discounting too much the value of a stable version, and the need for great execution.


App opens to landing page despite having existing device ID

I was unable to reproduce the bug - I tried the following with main branch with a physical phone (and browser):

Reinstall device id app
Complete device id wizard and create claims QR
Scan claims with holder app and issue VP
Reopen device id app and scan the VP (DataWedge flow also tested)
Save - credential is on home screen
Reset device id app
Complete wizard
Credential is not on home screen (no bug)

In the process of investigating this issue I came across a separate, but related issue (see #91)


Added support for const generics in impl generation

Closes #8211

bors r+
changelog fix impl generation not generating const generics


Command ctrl+shift+t doesn't work on atom start up

Environment:
Operation System: Win7
atom-terminal version: 0.8.0
Steps to reproduce:
0. Close atom (if it is already open);

Restart atom;
Click a file in one project;
Press  ctrl+shift+t.

Result:
nothing happened.
Note:
But, when after press alt+shift+t, then press ctrl+shift+t , it works.
Thanks!

Same problem here.
Environment:
OS: Linux Mint 18 (fully updated)
Atom: 1.10.2
atom-terminal: 0.8.0
ctrl+shift+t won't work until I press alt+shift+t first, then it works just fine.

I have probalby found a solution/workaround, at least for Linux. The problem is, that (on Linux) there is a shortcut ctrl+T which is colliding with atom-terminal's shortcut.
You can take a look at this screenshot:

So the solution would be to change atom-terminal's shortcut to something else.

I have same problem.
Environment:
OS: Windows 7 Pro
Atom: 1.11.2
atom-terminal: 0.8.0

Fix in new version. 8.1.
on archlinux i did. version 8.0.
goto package , atom-terminal , viewcode
then select package.json file, line 40 add ("atom-terminal:open",) without braces.
and it work for me.
"activationCommands": {
"atom-workspace": [
"atom-terminal:open",
"atom-terminal:open-project-root"
]
},

@DrakeMagi  Could you please clarify? the snippet you provide is identical to current code

It identical to current code version 0.8.1.
but in version 0.8.0 he forgot to add "atom-terminal:open", .
changes made in May 27, 2015 commit and merge June 2, 2015.
but only problem with commit was
surpressDirectoryArgument: default to false did not work for me. I kept my true.

@DrakeMagi thank'you!

Is v0.8.1 going to be released any time soon so this goes out to everybody?

@tech4him1,  @DrakeMagi 's fix worked for me

Between lines 40 and 41 of package.json, add:
"atom-terminal:open",

It looks @karan has abandoned this project - nearly 2 years, no commits. @drelyn86 has forked the project and is ahead about 18 commits, but has similarly abandoned repo a year ago as well.
OTOH, @blueimp's 'open-terminal-here' seems lively, provides the same functionality as atom-terminal, also adds a very handy context menu item to the workspace and tree view. I've personally jumped ship for that package in the middle of writing this note, lol.
... And of course, you may always fork karan's project ;)

If you are on WIndows like me and still looking for a fix, line 25 on package.json, add
'atom-terminal:open',
It should look like this:
"activationCommands": {
"atom-workspace": [
"atom-terminal:open",
"atom-terminal:open-project-root"
]
},


Incorrect parameters extracting on PKCE flow

Bug report

[✔] I confirm this is a bug with Supabase, not with my own application.
[✔] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Seems iOS Supabase SDK incorrectly extracting URL parameters in some cases.
Example of URL: appscheme://login-callback?code=ecd160cb-bb4a-4db2-be0c-bcf0b3abe496#_=_
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Make sure you are already logged in Facebook in mobile Safari
Try to link Facebook identity to some Supabase account using ASWebAuthenticationSession (prefersEphemeralWebBrowserSession = false)
See error of updating auth session with callback URL (invalidPKCEFlowURL)

Expected behavior
Such URLs should be handled properly
System information

OS: iOS 17.4.1
Browser: ASWebAuthenticationSession
Version of supabase-swift: 2.8.2

Additional context
func extractParams(from url: URL) -> [Params] {
  guard let components = URLComponents(url: url, resolvingAgainstBaseURL: false) else {
    return []
  }

  if let fragment = components.fragment {
    return extractParams(from: fragment)
  }

  if let queryItems = components.queryItems {
    return queryItems.map {
      Params(name: $0.name, value: $0.value ?? "")
    }
  }

  return []
}

According to the existing implementation fragment parameters will be returned immediately without merging with query items. Probably it's wrong (or maybe I just don't know the reason of such behavior)
Also not sure if it's correct from Facebook to respond with such callback URL but anyway seems we have all what we need there to proceed correctly.

Thanks @ypotsiah you're right we need to extract both fragment and query, I'll PR a fix for it ASAP.


bug: adding a new coin - (currency) account in mysql db is only created after user wants to ...

scenario:

exchange adds a new coin (eg. Litecoin)
the balance is not visible for all existing users which had an account before the new currency was added by the exchange under "settings" / acocunt balance until the user is generating a payment address.

This should be fixed so all currency accounts are created/checked if they exist when the user is logging in each time.

It's not a bug at all. You have to add currencies record for existing accounts in mysql. You can do it manually.


Faraday::Request::TokenAuthentication

Anyone know how I can use Faraday::Request::TokenAuthentication? I'm trying this:
Her::API.setup url: "http://thing:880/api/" do |c|

  c.use Faraday::Request::TokenAuthentication, :token => "320932222222"
  c.use Faraday::Request::UrlEncoded
  c.use Her::Middleware::AcceptJSON
  c.use Her::Middleware::DefaultParseJSON

  # Adapter
  c.use Faraday::Adapter::NetHttp
end

tcpdump request:

Authorization: Token token="{:token=>\320932222222\"}"

need:

Authorization: Token<PHONE_NUMBER>22

but doing a tcpdump my token ends up being: Authorization: Token token="{:token=>"320932222222""}"

Figured it out... using the totally wrong class:

  c.use Faraday::Request::Authorization, 'Token', "9234bca04b2b9aaceab919770528af13a92447ff"

works fine


update hive config to prevent memory leaks

This is a workaround to prevent memory leaks in hiveserver.

Can we move these new parameters to attributes?

@amithkanand I think this is no longer needed?

Closing for cleanup. Feel free to reopen if this work gets picked up later on.


Separate page for each student

Instead of a drop down menu, redirect to a new student page..

New student page for each advisee has been created.


Enable setLogLevel

Right now the logLevel defaults to DEBUG which floods the console with messages.
Exporting the setLogLevel function would let us customize determine the level we want when developing.

Hi @mikeeus thanks for the PR. We already have a default export for AgoraRTC. We'd expect users to set the log level like so:
import AgoraRTC, {createClient} from "agora-rtc-react";
...
AgoraRTC.setLogLevel(3)

Does that solve your issue?

Yes that should work, thanks!

Anyone kn ow why I get this error when trying to build in production? Attempted import error: 'agora-rtc-sdk-ng' does not contain a default export (imported as 'AgoraRTC__default').


Implement TLP Prefix to CxlIoBasePacket

Signed-off-by: Kyeyoon Park<EMAIL_ADDRESS>

Signed-off-by: Kyeyoon Park<EMAIL_ADDRESS>


Preventing a possible inconsistency from the integer-based Rank that implements precedes.

Hi. I'm not sure this is exploitable via an F* file, but the encoding of precedes (<<) via an integer rank function (such that a << b if and only if rank a < rank b) is not sound.
There's an example file in the PR that proves false from the assumption that such a function exists. The idea is basically to create something that is above every integer, and noticing this "thing" must have a rank. In particular I use Mk id where id is the identity and Mk is some constructor, and hence we know from the axiom generated for Mk that f x << Mk f for any x. See #2069 and #2205 for references on that axiom.
Now, the Rank function actually exists in the SMT encoding. I'm not sure I could get Z3 to use it to instantiate this proof, but potentially it could.
Anyway, this PR removes Rank and introduces a relation Prec in the encoding such that a << b if and only if Prec a b. Further, Prec is assumed to be a strict partial order, but crucially 1) not total and 2) of Terms instead of integers or any other limited-size set.
No regressions observed. (Notably, also, I attempted a run without the antisymmetry axiom and only got a handful of failures

FYI, I'm working on trying to get this one in. Trying to put a pattern on the transitivity axiom for Prec


Question. Is there a workaround for empty object type?

The elassandra doc says: "Because Elasticsearch nested and object types are backed by a Cassandra User Defined Type, it requires at least one sub-field in the mapping.";
My app currently works with Elasticsearch v5+ and v6+ and object type mapping is used.
For example
{
  "properties": {
    "input": {
      "type": "object",
      "enabled": false
    }
  }
}

There are fields where I have a lot of deeply nested objects I don't know beforehand their names or the level of deepness. For example, the input above has to support any Elasticsearch query syntax.
{
  "properties": {
    "search": {
      "query": {
        Elasticsearch query is here
      }
    }
  }
}

That's why I need to add the new properties dynamically to the input.
Is there any workaround to support my case?
PS
I know that the property can be stringified.

I’m not sure to understand your issue.
Disabled fields are stored in a C* text columns, this is JSON not interpreted by elasticsearch, so in this case, there is no UDT involved at all, and it can be as deep as you want, this is just a string form C* and ES.
(See org.elassandra.ObjectNotEnabledTests.java for example)
Does this clarify the topic for you ?

Le 6 déc. 2017 à 14:36, Sergii Bondarenko<EMAIL_ADDRESS>a écrit :
The elassandra doc http://elassandra.readthedocs.io/en/latest/limitations.html#nested-or-object-types-cannot-be-empty says: "Because Elasticsearch nested and object types are backed by a Cassandra User Defined Type, it requires at least one sub-field in the mapping.";
My app currently works with Elasticsearch v5+ and v6+ and object type https://www.elastic.co/guide/en/elasticsearch/reference/current/object.html mapping is used.
For example
{
"properties": {
"input": {
"type": "object",
"enabled": false
}
}
}
There are fields where I have a lot of deeply nested objects I don't know beforehand their names or the level of deepness. For example, the input above has to support any Elasticsearch query syntax.
{
"properties": {
"search": {
"query": {
Elasticsearch query is here
}
}
}
}
That's why I need to add the new properties dynamically to the input.
Is there any workaround to support my case?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmdxhsgPhEeeO5rR5GJ0dWlXWXgoJks5s9phWgaJpZM4Q361E.

@vroyer
The actual error I get is
elassandra-kibana    | {"type":"log","@timestamp":"2017-12-07T08:27:03Z","tags":["status","error","Sentinl"],"pid":12,"message":"[i_o_exception] Cannot create an empty nested type (not supported)"}

And I found where the problem is. In one of my mappings I have enabled: true (default). And this prevents me to create index.
  "properties": {
    "payload": {
      "type": "object"
    }
  }
}

I can create the index if I put enabled: false under payload.
  "properties": {
    "payload": {
      "type": "object",
      "enabled": false
    }
  }
}

But this prevents me to index payload data and I'll not be able to query it. Is there any workaround to have the payload data indexed?

@vroyer You can use the following JavaScript code to reproduce the issue. Run it like this node script.js
const Elasticsearch = require('elasticsearch');

const es = {
  host: 'localhost',
  index: 'spaceship',
  port: 9200,
  log: 'trace'
};

const mappings = {
  mappings: {
    'ship-engine': {
      properties: {
        input: {
          type: 'object'
        }
      }
    }
  }
};

const client = new Elasticsearch.Client({
  host: `${es.host}:${es.port}`,
  log: es.log
});

client.indices.exists({
  index: es.index
})
.then(function(exists) {
  if (exists) {
    console.log('SUCCESS', `Index ${ES_INDEX_NAME} already exists!`);
    return null;
  }

  return client.indices.create({
    index: es.index,
    body: mappings
  })
  .then(function(response) {
    console.log('SUCCESS', response);
  });
})
.catch(function(error) {
  console.log('FAIL', error);
});

Result:
FAIL { Error: [i_o_exception] Cannot create an empty nested type (not supported)
    at respond (/home/trex/dev/kibi/elassandra_test/node_modules/elasticsearch/src/lib/transport.js:307:15)
    at checkRespForFailure (/home/trex/dev/kibi/elassandra_test/node_modules/elasticsearch/src/lib/transport.js:266:7)
    at HttpConnector.<anonymous> (/home/trex/dev/kibi/elassandra_test/node_modules/elasticsearch/src/lib/connectors/http.js:159:7)
    at IncomingMessage.bound (/home/trex/dev/kibi/elassandra_test/node_modules/lodash/dist/lodash.js:729:21)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
  status: 500,
  displayName: 'InternalServerError',
  message: '[i_o_exception] Cannot create an empty nested type (not supported)',
  path: '/spaceship',
  query: {},
  body:
   { error:
      { root_cause: [Object],
        type: 'i_o_exception',
        reason: 'Cannot create an empty nested type (not supported)',
        caused_by: [Object] },
     status: 500 },
  statusCode: 500,
  response: '{"error":{"root_cause":[{"type":"i_o_exception","reason":"Cannot create an empty nested type (not supported)"}],"type":"i_o_exception","reason":"Cannot create an empty nested type (not supported)","caused_by":{"type":"invalid_request_exception","reason":"Cannot create an empty nested type (not supported)"}},"status":500}',
  toString: [Function],
  toJSON: [Function] }

Expected result
SUCCESS { acknowledged: true,
  shards_acknowledged: true,
  index: 'spaceship' }

Ok, but why do you create an empty object with enable=true ?
Is it to later add sub-field in that object ?

Le 7 déc. 2017 à 12:07, Sergii Bondarenko<EMAIL_ADDRESS>a écrit :
@vroyer https://github.com/vroyer You can use the following JavaScript code to reproduce the issue. Run it like this node script.js
const Elasticsearch = require('elasticsearch');
const es = {
host: 'localhost',
index: 'spaceship',
port: 9200,
log: 'trace'
};
const mappings = {
mappings: {
'ship-engine': {
properties: {
input: {
type: 'object'
}
}
}
}
};
const client = new Elasticsearch.Client({
host: ${es.host}:${es.port},
log: es.log
});
client.indices.exists({
index: es.index
})
.then(function(exists) {
if (exists) {
console.log('SUCCESS', Index ${ES_INDEX_NAME} already exists!);
return null;
}
return client.indices.create({
index: es.index,
body: mappings
})
.then(function(response) {
console.log('SUCCESS', response);
});
})
.catch(function(error) {
console.log('FAIL', error);
});
Result:
FAIL { Error: [i_o_exception] Cannot create an empty nested type (not supported)
at respond (/home/trex/dev/kibi/elassandra_test/node_modules/elasticsearch/src/lib/transport.js:307:15)
at checkRespForFailure (/home/trex/dev/kibi/elassandra_test/node_modules/elasticsearch/src/lib/transport.js:266:7)
at HttpConnector. (/home/trex/dev/kibi/elassandra_test/node_modules/elasticsearch/src/lib/connectors/http.js:159:7)
at IncomingMessage.bound (/home/trex/dev/kibi/elassandra_test/node_modules/lodash/dist/lodash.js:729:21)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
status: 500,
displayName: 'InternalServerError',
message: '[i_o_exception] Cannot create an empty nested type (not supported)',
path: '/spaceship',
query: {},
body:
{ error:
{ root_cause: [Object],
type: 'i_o_exception',
reason: 'Cannot create an empty nested type (not supported)',
caused_by: [Object] },
status: 500 },
statusCode: 500,
response: '{"error":{"root_cause":[{"type":"i_o_exception","reason":"Cannot create an empty nested type (not supported)"}],"type":"i_o_exception","reason":"Cannot create an empty nested type (not supported)","caused_by":{"type":"invalid_request_exception","reason":"Cannot create an empty nested type (not supported)"}},"status":500}',
toString: [Function],
toJSON: [Function] }
Expected result
SUCCESS { acknowledged: true,
shards_acknowledged: true,
index: 'spaceship' }
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-349936061, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmcp4PJZBW2uKjNUlxu4nKCyFiDQ_ks5s98b1gaJpZM4Q361E.

@vroyer I create it to add multiple sub-fields.

The issue comes from Cassandra because an UDT must have at lear on sub-field.
So I can delay the creation of the C* UDT type till there is at least one subfield.

Le 7 déc. 2017 à 14:08, Sergii Bondarenko<EMAIL_ADDRESS>a écrit :
@vroyer https://github.com/vroyer I create it to add multiple sub-fields.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-349961862, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmax_t6OADin9CNvOnwbrentui9gGks5s9-NAgaJpZM4Q361E.

I have released a fix on branch #146-branch

Building a release to validate outcome and will report here, thanks @vroyer

On Create:
elassandra-kibana    | {"type":"log","@timestamp":"2017-12-10T10:20:22Z","tags":["status","error","Sentinl"],"pid":12,"message":"[index_not_found_exception] no such index, with { resource.type=\"index_or_alias\" & resource.id=\"watcher\" & index_uuid=\"_na_\" & index=\"watcher\" }"}

elassandra-seed-node | 2017-12-10 10:20:22,805 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.StorageService.setLoggingLevel(StorageService.java:3817) set log level to TRACE for classes under 'index.search.slowlog.query.watcher_alarms' (if the level doesn't look like 'TRACE' then the logger couldn't parse 'TRACE')

elassandra-seed-node | 2017-12-10 10:20:22,806 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.StorageService.setLoggingLevel(StorageService.java:3817) set log level to TRACE for classes under 'index.search.slowlog.fetch.watcher_alarms' (if the level doesn't look like 'TRACE' then the logger couldn't parse 'TRACE')

elassandra-seed-node | 2017-12-10 10:20:22,811 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.MigrationManager.announceNewKeyspace(MigrationManager.java:310) Create new Keyspace: KeyspaceMetadata{name=watcher_alarms, params=KeyspaceParams{durable_writes=true, replication=ReplicationParams{class=org.apache.cassandra.locator.NetworkTopologyStrategy, DC1=1}}, tables=[], views=[], functions=[], types=[]}

elassandra-seed-node | 2017-12-10 10:20:23,190 WARN  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.elasticsearch.cluster.service.ClusterService.updateTableSchema(ClusterService.java:1244) Ignoring enabled object with no sub-fields

On Writes:
elassandra-kibana    | {"type":"log","@timestamp":"2017-12-10T10:24:32Z","tags":["status","info","Sentinl"],"pid":12,"message":"Saving Watcher with ID: dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o"}

elassandra-seed-node | 2017-12-10 10:24:32,545 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.StorageService.setLoggingLevel(StorageService.java:3817) set log level to TRACE for classes under 'index.search.slowlog.query.watcher' (if the level doesn't look like 'TRACE' then the logger couldn't parse 'TRACE')

elassandra-seed-node | 2017-12-10 10:24:32,546 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.StorageService.setLoggingLevel(StorageService.java:3817) set log level to TRACE for classes under 'index.search.slowlog.fetch.watcher' (if the level doesn't look like 'TRACE' then the logger couldn't parse 'TRACE')

elassandra-seed-node | 2017-12-10 10:24:32,558 WARN  [elasticsearch[<IP_ADDRESS>][bulk][T#2]] org.elasticsearch.rest.BytesRestResponse.build(BytesRestResponse.java:133) path: /watcher/sentinl-watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o, params: {index=watcher, id=dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o, type=sentinl-watcher}

elassandra-seed-node | org.elasticsearch.transport.RemoteTransportException: [<IP_ADDRESS>][<IP_ADDRESS>:9300][indices:data/write/bulk[s][p]]

elassandra-seed-node | Caused by: org.elasticsearch.common.util.concurrent.UncategorizedExecutionException: Failed execution
elassandra-seed-node | 	at org.elasticsearch.action.support.AdapterActionFuture.rethrowExecutionException(AdapterActionFuture.java:93)
elassandra-seed-node | 	at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:47)
elassandra-seed-node | 	at org.elasticsearch.action.ActionRequestBuilder.get(ActionRequestBuilder.java:62)
elassandra-seed-node | 	at org.elasticsearch.cluster.action.index.MappingUpdatedAction.updateMappingOnMaster(MappingUpdatedAction.java:89)
elassandra-seed-node | 	at org.elasticsearch.cluster.action.index.MappingUpdatedAction.updateMappingOnMaster(MappingUpdatedAction.java:80)
elassandra-seed-node | 	at org.elasticsearch.action.bulk.TransportShardBulkAction.executeIndexRequestOnPrimary(TransportShardBulkAction.java:476)
elassandra-seed-node | 	at org.elasticsearch.action.bulk.TransportShardBulkAction.executeBulkItemRequest(TransportShardBulkAction.java:150)
elassandra-seed-node | 	at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:120)
elassandra-seed-node | 	at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:72)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryShardReference.perform(TransportReplicationAction.java:965)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryShardReference.perform(TransportReplicationAction.java:934)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.ReplicationOperation.execute(ReplicationOperation.java:113)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$AsyncPrimaryAction.doRun(TransportReplicationAction.java:291)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:260)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:252)
elassandra-seed-node | 	at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:69)
elassandra-seed-node | 	at org.elasticsearch.transport.TransportService$7.doRun(TransportService.java:656)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:638)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
elassandra-seed-node | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
elassandra-seed-node | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
elassandra-seed-node | 	at java.lang.Thread.run(Thread.java:748)
elassandra-seed-node | Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Unknown type watcher.sentinl_watcher_input_search_request
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:262)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:249)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:91)
elassandra-seed-node | 	at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:42)
elassandra-seed-node | 	... 21 common frames omitted
elassandra-seed-node | Caused by: java.io.IOException: Unknown type watcher.sentinl_watcher_input_search_request
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.updateTableSchema(ClusterService.java:1383)
elassandra-seed-node | 	at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.applyRequest(MetaDataMappingService.java:387)
elassandra-seed-node | 	at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.execute(MetaDataMappingService.java:268)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService.executeTasks(BaseClusterService.java:631)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService.calculateTaskOutputs(BaseClusterService.java:608)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService.runTasks(BaseClusterService.java:567)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService$ClusterServiceTaskBatcher.run(BaseClusterService.java:263)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService$ClusterServiceTaskBatcher$UpdateTask.run(BaseClusterService.java:266)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:247)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:210)
elassandra-seed-node | 	... 3 common frames omitted
elassandra-seed-node | Caused by: org.apache.cassandra.exceptions.InvalidRequestException: Unknown type watcher.sentinl_watcher_input_search_request
elassandra-seed-node | 	at org.apache.cassandra.cql3.CQL3Type$Raw$RawUT.prepare(CQL3Type.java:768)
elassandra-seed-node | 	at org.apache.cassandra.cql3.CQL3Type$Raw$RawCollection.prepare(CQL3Type.java:684)
elassandra-seed-node | 	at org.apache.cassandra.cql3.CQL3Type$Raw$RawCollection.prepare(CQL3Type.java:651)
elassandra-seed-node | 	at org.apache.cassandra.cql3.CQL3Type$Raw.prepare(CQL3Type.java:530)
elassandra-seed-node | 	at org.apache.cassandra.cql3.statements.CreateTypeStatement.createType(CreateTypeStatement.java:116)
elassandra-seed-node | 	at org.apache.cassandra.cql3.statements.CreateTypeStatement.announceMigration(CreateTypeStatement.java:130)
elassandra-seed-node | 	at org.apache.cassandra.cql3.statements.SchemaAlteringStatement.execute(SchemaAlteringStatement.java:93)
elassandra-seed-node | 	at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:224)
elassandra-seed-node | 	at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:255)
elassandra-seed-node | 	at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:270)
elassandra-seed-node | 	at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:265)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.buildUDT(ClusterService.java:980)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.buildCql(ClusterService.java:880)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.buildUDT(ClusterService.java:910)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.buildCql(ClusterService.java:880)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.updateTableSchema(ClusterService.java:1278)
elassandra-seed-node | 	... 15 common frames omitted
elassandra-kibana    | {"type":"error","@timestamp":"2017-12-10T10:24:32Z","tags":[],"pid":12,"level":"error","message":"[uncategorized_execution_exception] Failed execution","error":{"message":"[uncategorized_execution_exception] Failed execution","name":"Error","stack":"[uncategorized_execution_exception] Failed execution :: {\"path\":\"/watcher/sentinl-watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o\",\"query\":{},\"body\":\"{\\\"title\\\":\\\"watcher_title\\\",\\\"disable\\\":false,\\\"report\\\":false,\\\"trigger\\\":{\\\"schedule\\\":{\\\"later\\\":\\\"every 1 mins\\\"}},\\\"input\\\":{\\\"search\\\":{\\\"request\\\":{\\\"index\\\":[],\\\"body\\\":{}}}},\\\"condition\\\":{\\\"script\\\":{\\\"script\\\":\\\"payload.hits.total > 100\\\"}},\\\"actions\\\":{\\\"email_admin\\\":{\\\"throttle_period\\\":\\\"0h15m0s\\\",\\\"email\\\":{\\\"to\\\":\\\"alarm@localhost\\\",\\\"from\\\":\\\"sentinl@localhost\\\",\\\"subject\\\":\\\"Sentinl Alarm\\\",\\\"priority\\\":\\\"high\\\",\\\"body\\\":\\\"Found {{payload.hits.total}} Events\\\"}}},\\\"transform\\\":{}}\",\"statusCode\":500,\"response\":\"{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"uncategorized_execution_exception\\\",\\\"reason\\\":\\\"Failed execution\\\"}],\\\"type\\\":\\\"uncategorized_execution_exception\\\",\\\"reason\\\":\\\"Failed execution\\\",\\\"caused_by\\\":{\\\"type\\\":\\\"execution_exception\\\",\\\"reason\\\":\\\"java.io.IOException: Unknown type watcher.sentinl_watcher_input_search_request\\\",\\\"caused_by\\\":{\\\"type\\\":\\\"i_o_exception\\\",\\\"reason\\\":\\\"Unknown type watcher.sentinl_watcher_input_search_request\\\",\\\"caused_by\\\":{\\\"type\\\":\\\"invalid_request_exception\\\",\\\"reason\\\":\\\"Unknown type watcher.sentinl_watcher_input_search_request\\\"}}}},\\\"status\\\":500}\"}\n    at respond (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:295:15)\n    at checkRespForFailure (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:254:7)\n    at HttpConnector.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:159:7)\n    at IncomingMessage.bound (/usr/share/kibana/node_modules/elasticsearch/node_modules/lodash/dist/lodash.js:729:21)\n    at emitNone (events.js:91:20)\n    at IncomingMessage.emit (events.js:185:7)\n    at endReadableNT (_stream_readable.js:974:12)\n    at _combinedTickCallback (internal/process/next_tick.js:80:11)\n    at process._tickDomainCallback (internal/process/next_tick.js:128:9)"},"url":{"protocol":null,"slashes":null,"auth":null,"host":null,"port":null,"hostname":null,"hash":null,"search":"","query":{},"pathname":"/api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o","path":"/api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o","href":"/api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o"}}
elassandra-kibana    | {"type":"response","@timestamp":"2017-12-10T10:24:32Z","tags":[],"pid":12,"method":"post","statusCode":500,"req":{"url":"/api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o","method":"post","headers":{"host":"xxxx:19061","connection":"keep-alive","content-length":"540","accept":"application/json, text/plain, */*","origin":"http://xxxx:19061","kbn-version":"5.5.0","user-agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36","content-type":"application/json;charset=UTF-8","dnt":"1","referer":"http://xxxx:19061/app/sentinl","accept-encoding":"gzip, deflate","accept-language":"en-US,en;q=0.9"},"remoteAddress":"xxxx","userAgent":"xxxx","referer":"http://xxxx:19061/app/sentinl"},"res":{"statusCode":500,"responseTime":50,"contentLength":9},"message":"POST /api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o 500 50ms - 9.0B"}

Mind we're not expecting you to resolve this for us necessarily, rather suggest how we can modify our App queries to work around those limitations and be compatible with both, if possible, or swap to more generic methods - SENTINL (the App generating the interaction here) has thousands of deployments on regular ES (everything in between 4.x, 5.x) without issues and its considered stable.
Any comment appreciated - Thanks for your time in advance!

Hi Lorenzo,
There’s a mapping issue with type watcher.sentinl_watcher_input_search_request
Would you have your CQL schema and ES mapping for watcher ?
Thanks.
Vincent.

Le 10 déc. 2017 à 11:42, Lorenzo Mangani<EMAIL_ADDRESS>a écrit :
On Create:
elassandra-kibana    | {"type":"log","@timestamp":"2017-12-10T10:20:22Z","tags":["status","error","Sentinl"],"pid":12,"message":"[index_not_found_exception] no such index, with { resource.type="index_or_alias" & resource.id="watcher" & index_uuid="na" & index="watcher" }"}
elassandra-seed-node | 2017-12-10 10:20:22,805 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.StorageService.setLoggingLevel(StorageService.java:3817) set log level to TRACE for classes under 'index.search.slowlog.query.watcher_alarms' (if the level doesn't look like 'TRACE' then the logger couldn't parse 'TRACE')
elassandra-seed-node | 2017-12-10 10:20:22,806 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.StorageService.setLoggingLevel(StorageService.java:3817) set log level to TRACE for classes under 'index.search.slowlog.fetch.watcher_alarms' (if the level doesn't look like 'TRACE' then the logger couldn't parse 'TRACE')
elassandra-seed-node | 2017-12-10 10:20:22,811 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.MigrationManager.announceNewKeyspace(MigrationManager.java:310) Create new Keyspace: KeyspaceMetadata{name=watcher_alarms, params=KeyspaceParams{durable_writes=true, replication=ReplicationParams{class=org.apache.cassandra.locator.NetworkTopologyStrategy, DC1=1}}, tables=[], views=[], functions=[], types=[]}
elassandra-seed-node | 2017-12-10 10:20:23,190 WARN  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.elasticsearch.cluster.service.ClusterService.updateTableSchema(ClusterService.java:1244) Ignoring enabled object with no sub-fields
On Writes:
elassandra-kibana    | {"type":"log","@timestamp":"2017-12-10T10:24:32Z","tags":["status","info","Sentinl"],"pid":12,"message":"Saving Watcher with ID: dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o"}
elassandra-seed-node | 2017-12-10 10:24:32,545 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.StorageService.setLoggingLevel(StorageService.java:3817) set log level to TRACE for classes under 'index.search.slowlog.query.watcher' (if the level doesn't look like 'TRACE' then the logger couldn't parse 'TRACE')
elassandra-seed-node | 2017-12-10 10:24:32,546 INFO  [elasticsearch[<IP_ADDRESS>][clusterService#updateTask][T#1]] org.apache.cassandra.service.StorageService.setLoggingLevel(StorageService.java:3817) set log level to TRACE for classes under 'index.search.slowlog.fetch.watcher' (if the level doesn't look like 'TRACE' then the logger couldn't parse 'TRACE')
elassandra-seed-node | 2017-12-10 10:24:32,558 WARN  [elasticsearch[<IP_ADDRESS>][bulk][T#2]] org.elasticsearch.rest.BytesRestResponse.build(BytesRestResponse.java:133) path: /watcher/sentinl-watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o, params: {index=watcher, id=dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o, type=sentinl-watcher}
elassandra-seed-node | org.elasticsearch.transport.RemoteTransportException: [<IP_ADDRESS>][<IP_ADDRESS>:9300][indices:data/write/bulk[s][p]]
elassandra-seed-node | Caused by: org.elasticsearch.common.util.concurrent.UncategorizedExecutionException: Failed execution
elassandra-seed-node | 	at org.elasticsearch.action.support.AdapterActionFuture.rethrowExecutionException(AdapterActionFuture.java:93)
elassandra-seed-node | 	at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:47)
elassandra-seed-node | 	at org.elasticsearch.action.ActionRequestBuilder.get(ActionRequestBuilder.java:62)
elassandra-seed-node | 	at org.elasticsearch.cluster.action.index.MappingUpdatedAction.updateMappingOnMaster(MappingUpdatedAction.java:89)
elassandra-seed-node | 	at org.elasticsearch.cluster.action.index.MappingUpdatedAction.updateMappingOnMaster(MappingUpdatedAction.java:80)
elassandra-seed-node | 	at org.elasticsearch.action.bulk.TransportShardBulkAction.executeIndexRequestOnPrimary(TransportShardBulkAction.java:476)
elassandra-seed-node | 	at org.elasticsearch.action.bulk.TransportShardBulkAction.executeBulkItemRequest(TransportShardBulkAction.java:150)
elassandra-seed-node | 	at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:120)
elassandra-seed-node | 	at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:72)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryShardReference.perform(TransportReplicationAction.java:965)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryShardReference.perform(TransportReplicationAction.java:934)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.ReplicationOperation.execute(ReplicationOperation.java:113)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$AsyncPrimaryAction.doRun(TransportReplicationAction.java:291)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:260)
elassandra-seed-node | 	at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:252)
elassandra-seed-node | 	at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:69)
elassandra-seed-node | 	at org.elasticsearch.transport.TransportService$7.doRun(TransportService.java:656)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:638)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
elassandra-seed-node | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
elassandra-seed-node | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
elassandra-seed-node | 	at java.lang.Thread.run(Thread.java:748)
elassandra-seed-node | Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Unknown type watcher.sentinl_watcher_input_search_request
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:262)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:249)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:91)
elassandra-seed-node | 	at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:42)
elassandra-seed-node | 	... 21 common frames omitted
elassandra-seed-node | Caused by: java.io.IOException: Unknown type watcher.sentinl_watcher_input_search_request
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.updateTableSchema(ClusterService.java:1383)
elassandra-seed-node | 	at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.applyRequest(MetaDataMappingService.java:387)
elassandra-seed-node | 	at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.execute(MetaDataMappingService.java:268)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService.executeTasks(BaseClusterService.java:631)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService.calculateTaskOutputs(BaseClusterService.java:608)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService.runTasks(BaseClusterService.java:567)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService$ClusterServiceTaskBatcher.run(BaseClusterService.java:263)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.BaseClusterService$ClusterServiceTaskBatcher$UpdateTask.run(BaseClusterService.java:266)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:247)
elassandra-seed-node | 	at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:210)
elassandra-seed-node | 	... 3 common frames omitted
elassandra-seed-node | Caused by: org.apache.cassandra.exceptions.InvalidRequestException: Unknown type watcher.sentinl_watcher_input_search_request
elassandra-seed-node | 	at org.apache.cassandra.cql3.CQL3Type$Raw$RawUT.prepare(CQL3Type.java:768)
elassandra-seed-node | 	at org.apache.cassandra.cql3.CQL3Type$Raw$RawCollection.prepare(CQL3Type.java:684)
elassandra-seed-node | 	at org.apache.cassandra.cql3.CQL3Type$Raw$RawCollection.prepare(CQL3Type.java:651)
elassandra-seed-node | 	at org.apache.cassandra.cql3.CQL3Type$Raw.prepare(CQL3Type.java:530)
elassandra-seed-node | 	at org.apache.cassandra.cql3.statements.CreateTypeStatement.createType(CreateTypeStatement.java:116)
elassandra-seed-node | 	at org.apache.cassandra.cql3.statements.CreateTypeStatement.announceMigration(CreateTypeStatement.java:130)
elassandra-seed-node | 	at org.apache.cassandra.cql3.statements.SchemaAlteringStatement.execute(SchemaAlteringStatement.java:93)
elassandra-seed-node | 	at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:224)
elassandra-seed-node | 	at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:255)
elassandra-seed-node | 	at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:270)
elassandra-seed-node | 	at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:265)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.buildUDT(ClusterService.java:980)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.buildCql(ClusterService.java:880)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.buildUDT(ClusterService.java:910)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.buildCql(ClusterService.java:880)
elassandra-seed-node | 	at org.elasticsearch.cluster.service.ClusterService.updateTableSchema(ClusterService.java:1278)
elassandra-seed-node | 	... 15 common frames omitted
elassandra-kibana    | {"type":"error","@timestamp":"2017-12-10T10:24:32Z","tags":[],"pid":12,"level":"error","message":"[uncategorized_execution_exception] Failed execution","error":{"message":"[uncategorized_execution_exception] Failed execution","name":"Error","stack":"[uncategorized_execution_exception] Failed execution :: {"path":"/watcher/sentinl-watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o","query":{},"body":"{\"title\":\"watcher_title\",\"disable\":false,\"report\":false,\"trigger\":{\"schedule\":{\"later\":\"every 1 mins\"}},\"input\":{\"search\":{\"request\":{\"index\":[],\"body\":{}}}},\"condition\":{\"script\":{\"script\":\"payload.hits.total > 100\"}},\"actions\":{\"email_admin\":{\"throttle_period\":\"0h15m0s\",\"email\":{\"to\":\"alarm@localhost\",\"from\":\"sentinl@localhost\",\"subject\":\"Sentinl Alarm\",\"priority\":\"high\",\"body\":\"Found {{payload.hits.total}} Events\"}}},\"transform\":{}}","statusCode":500,"response":"{\"error\":{\"root_cause\":[{\"type\":\"uncategorized_execution_exception\",\"reason\":\"Failed execution\"}],\"type\":\"uncategorized_execution_exception\",\"reason\":\"Failed execution\",\"caused_by\":{\"type\":\"execution_exception\",\"reason\":\"java.io.IOException: Unknown type watcher.sentinl_watcher_input_search_request\",\"caused_by\":{\"type\":\"i_o_exception\",\"reason\":\"Unknown type watcher.sentinl_watcher_input_search_request\",\"caused_by\":{\"type\":\"invalid_request_exception\",\"reason\":\"Unknown type watcher.sentinl_watcher_input_search_request\"}}}},\"status\":500}"}\n    at respond (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:295:15)\n    at checkRespForFailure (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:254:7)\n    at HttpConnector. (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:159:7)\n    at IncomingMessage.bound (/usr/share/kibana/node_modules/elasticsearch/node_modules/lodash/dist/lodash.js:729:21)\n    at emitNone (events.js:91:20)\n    at IncomingMessage.emit (events.js:185:7)\n    at endReadableNT (_stream_readable.js:974:12)\n    at _combinedTickCallback (internal/process/next_tick.js:80:11)\n    at process._tickDomainCallback (internal/process/next_tick.js:128:9)"},"url":{"protocol":null,"slashes":null,"auth":null,"host":null,"port":null,"hostname":null,"hash":null,"search":"","query":{},"pathname":"/api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o","path":"/api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o","href":"/api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o"}}
elassandra-kibana    | {"type":"response","@timestamp":"2017-12-10T10:24:32Z","tags":[],"pid":12,"method":"post","statusCode":500,"req":{"url":"/api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o","method":"post","headers":{"host":"xxxx:19061","connection":"keep-alive","content-length":"540","accept":"application/json, text/plain, /","origin":"http://xxxx:19061","kbn-version":"5.5.0","user-agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36","content-type":"application/json;charset=UTF-8","dnt":"1","referer":"http://xxxx:19061/app/sentinl","accept-encoding":"gzip, deflate","accept-language":"en-US,en;q=0.9"},"remoteAddress":"xxxx","userAgent":"xxxx","referer":"http://xxxx:19061/app/sentinl"},"res":{"statusCode":500,"responseTime":50,"contentLength":9},"message":"POST /api/sentinl/watcher/dqu5lvjnav7-ba1pmznqeu4-cudsrw0hs7o 500 50ms - 9.0B"}
Mind we're not expecting you to resolve this for us necessarily, rather suggest how we can modify our App queries to work around those limitations and be compatible with both, if possible, or swap to more generic methods - SENTINL (the App generating the interaction here) has thousands of deployments on regular ES (everything in between 4.x, 5.x) without issues and its considered stable.
Any comment appreciated - Thanks for your time in advance!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-350539297, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmTHlJjDeH5X0ePdAad5G4zZMiMCIks5s-7WigaJpZM4Q361E.

Hi Vincent, sure - all our mappings are available fore review here: https://github.com/sirensolutions/sentinl-private/tree/master/server/mappings

Sorry, this repo is private.

Le 10 déc. 2017 à 14:20, Lorenzo Mangani<EMAIL_ADDRESS>a écrit :
Hi Vincent, sure - all our mappings are available fore review here: https://github.com/sirensolutions/sentinl-private/tree/master/server/mappings https://github.com/sirensolutions/sentinl-private/tree/master/server/mappings
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-350547973, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmWKlQuJCvVvJbGySyaqQ7S6NMMyAks5s-9qbgaJpZM4Q361E.

Sorry wrong paste indeed. https://github.com/sirensolutions/sentinl/tree/master/server/mappings

Ok, i got it !
There is no document type « watcher » , how can reproduce your issue ?

Le 10 déc. 2017 à 14:58, Lorenzo Mangani<EMAIL_ADDRESS>a écrit :
Sorry wrong paste indeed. https://github.com/sirensolutions/sentinl/tree/master/server/mappings https://github.com/sirensolutions/sentinl/tree/master/server/mappings
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-350550203, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmbfX5UReiTQQxhafIL8TPAliquJ5ks5s--NugaJpZM4Q361E.

Sure - the below compose should reproduce it, using this sequence:

start the containers in foreground with docker-compose up
wait for Kibana to come alive (logs will show SENTINL creating indices, etc)
open Kibana, switch to SENTINL App (Clock Icon)
Add a New Alert w/ defaults, and click SAVE (top right)

The same error in the report should appear on any save/edit actions.
NOTE: I've used a local image build from the Fix Branch for the Elassandra container, sent a PR to gradle build it but I think you'll trust your own best
version: '2.1'
services:
  elassandra-seed:
    container_name: elassandra-seed-node
    image: strapdata/elassandra:<IP_ADDRESS>
    ports:
      - "9042:9042"   # Native transport
      - "7199:7199"   # JMX
      - "9160:9160"   # Thrift clients
      - "9200:9200"   # ES clients
    healthcheck:
        test: cqlsh -e "?" --cqlversion="3.4.4"
        interval: 5s
        timeout: 10s
        retries: 10

  elassandra-kibana:
    container_name: elassandra-kibana
    image: qxip/kibana-steroids:master
    ports:
      - "5601:5601"
    environment:
      - "ELASTICSEARCH_URL=http://elassandra-seed:9200"
      - "XPACK_MONITORING_ENABLED=false"
      - "SERVER_NAME=ELASSANDRAK"
    depends_on:
      elassandra-seed:
        condition: service_healthy

I'm available to join you anytime if useful - Thanks in advance!

Watcher, is a kibana 5.5+ plugin that should work with elassandra ?
So i can install this plugin for kibana 5.5 to test it ?
kibana-plugin install https://github.com/sirensolutions/sentinl/releases/download/tag-5.5/sentinl-v5.5.1.zip

Le 10 déc. 2017 à 16:13, Lorenzo Mangani<EMAIL_ADDRESS>a écrit :
Sure - the below compose should reproduce it, using this sequence:
start the containers in foreground with docker-compose up
wait for Kibana to come alive (logs will show SENTINL creating indices, etc)
open Kibana, switch to SENTINL App (Clock Icon)
Add a New Alert w/ defaults, and click SAVE (top right)
The same error in the report should appear on any save/edit actions.
NOTE: I've used a local image build from the Fix Branch for the Elassandra container, sent a PR to gradle build it but I think you'll trust your own best
version: '2.1'
services:
elassandra-seed:
container_name: elassandra-seed-node
image: strapdata/elassandra:<IP_ADDRESS>
ports:
- "9042:9042"   # Native transport
- "7199:7199"   # JMX
- "9160:9160"   # Thrift clients
- "9200:9200"   # ES clients
healthcheck:
test: cqlsh -e "?" --cqlversion="3.4.4"
interval: 5s
timeout: 10s
retries: 10
elassandra-kibana:
container_name: elassandra-kibana
image: qxip/kibana-steroids:master
ports:
- "5601:5601"
environment:
- "ELASTICSEARCH_URL=http://elassandra-seed:9200"
- "XPACK_MONITORING_ENABLED=false"
- "SERVER_NAME=ELASSANDRAK"
depends_on:
elassandra-seed:
condition: service_healthy
I'm available to join you anytime if useful - Thanks in advance!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-350555073, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmUjeo6x8AbPm-l0Wox9ZlmPeUUKdks5s-_UqgaJpZM4Q361E.

@vroyer correct, absolutely. We should have releases for all versions of Kibana on the repository.
Just to be clear, SENTINL is working entirely inside Kibana and does not require the Elasticsearch Watcher plugin, xpack crap, etc. It should work fine with Elassandra as it only stores/reads from the ES API its own data but we do make some dynamic usage as you will see. Happy to adjust things on our to support both should plain compatibility not be possible, too.

Hi Lorenzo,
I have reproduced your issue with sentinl and partially fixed it on branch #146.
You can now save watcher or report definition, but there is still an issue when executing a watcher.
Sentinl try to write an alert in index  watcher_alarms-2017.12.11 in a dedicated document type ra9k12g85xo-1qd0zo4yjd5-2t4jv1527id_alerte with a field « message », but elasticsearch complains because there is already a message field in this index (type report_admin).
This is a pure elasticsearch check, so i don’t know how this can works with elasticsearch 5.5.0 ?
java.lang.IllegalArgumentException: [message] is defined as a field in mapping [ra9k12g85xo-1qd0zo4yjd5-2t4jv1527id_alerte] but this name is already used for an object in other types
at org.elasticsearch.index.mapper.MapperService.checkFieldUniqueness(MapperService.java:709)
at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:540)
at org.elasticsearch.index.mapper.MapperService.internalMerge(MapperService.java:482)
at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:414)
at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.applyRequest(MetaDataMappingService.java:353)
at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.execute(MetaDataMappingService.java:268)
at org.elasticsearch.cluster.service.BaseClusterService.executeTasks(BaseClusterService.java:631)
at org.elasticsearch.cluster.service.BaseClusterService.calculateTaskOutputs(BaseClusterService.java:608)
at org.elasticsearch.cluster.service.BaseClusterService.runTasks(BaseClusterService.java:567)
at org.elasticsearch.cluster.service.BaseClusterService$ClusterServiceTaskBatcher.run(BaseClusterService.java:263)
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150)
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188)
at org.elasticsearch.cluster.service.BaseClusterService$ClusterServiceTaskBatcher$UpdateTask.run(BaseClusterService.java:1)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:247)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:210)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
get "watcher_alarms-2017.12.11?pretty"
{
"watcher_alarms-2017.12.11" : {
"aliases" : { },
"mappings" : {
"report_admin" : {
"properties" : {
"@timestamp" : {
"type" : "date"
},
"action" : {
"type" : "text",
"fields" : {
"keyword" : {
"type" : "keyword",
"ignore_above" : 256
}
}
},
"level" : {
"type" : "text",
"fields" : {
"keyword" : {
"type" : "keyword",
"ignore_above" : 256
}
}
},
"message" : {
"type" : "object"
},
"payload" : {
"type" : "object"
},
"report" : {
"type" : "boolean"
},
"watcher" : {
"type" : "text",
"fields" : {
"keyword" : {
"type" : "keyword",
"ignore_above" : 256
}
}
}
}
}
},
"settings" : {
"index" : {
"keyspace" : "watcher_alarms_2017_12_11",
"number_of_shards" : "2",
"provided_name" : "watcher_alarms-2017.12.11",
"creation_date" : "1512953514915",
"number_of_replicas" : "0",
"uuid" : "k8GcMsXuQRm-QtvKBwx-Xg",
"version" : {
"created" : "5050099"
}
}
}
}
}

Le 10 déc. 2017 à 16:37, Lorenzo Mangani<EMAIL_ADDRESS>a écrit :
@vroyer https://github.com/vroyer correct, absolutely. We should have releases for all versions of Kibana on the repository.
Just to be clear, SENTINL is working entirely inside Kibana and does not require the Elasticsearch Watcher plugin, xpack crap, etc. It should work fine with Elassandra as it only stores/reads from the ES API its own data but we do make some dynamic usage as you will see. Happy to adjust things on our to support both should plain compatibility not be possible, too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-350556650, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmc_4Pf2IU0ccSFnToIBwzrijS892ks5s-_q_gaJpZM4Q361E.

@vroyer @lmangani
Guys, ES doesn't allow to have different mappings for two fields with the same name under the same index.
The possible solutions are:

Don't index field data, only store it. For this, you need to put enabled: false inside mapping. For example

    "transform": {
      "type": "object",
      "enabled": false
    }

But in this case, you can't query the not indexed data.
2. Rename one of the fields, and you can have a different mapping for it.
3. Put one of the fields in a different index.
Here is a reply from a ES developer https://discuss.elastic.co/t/are-not-allow-to-have-the-same-field-name-in-different-elastic-types-with-differents-types-string-nested-json-number-what-would-be-the-solution-with-elastic-search-for-this-issue/73914/2

Hi Sergii, Lorenzo
Finally, it work’s fine in elassandra (the issue was coming from a wrong mapping generated when the bug was not yet fixed).
This only limitation comes from Cassandra with table name < 48 characters, so sentinel action names should be shorter than 11 characters, because for each action definition, sentinl defines an ES type _<action_name> mapped to a cassandra table.
Let me know if it’s okay from your side, it would be a great to support sentinl+elassandra !
Thanks,
Vincent.

Le 11 déc. 2017 à 09:40, Sergii Bondarenko<EMAIL_ADDRESS>a écrit :
@vroyer https://github.com/vroyer @lmangani https://github.com/lmangani
Guys, ES doesn't allow to have different mappings for two fields with the same name under the same index.
The possible solutions are:
Don't index field data, only store it. For this, you need to put enabled: false inside mapping. For example
"transform": {
"type": "object",
"enabled": false
}
But in this case, you can't query the not indexed data.
2. Rename one of the fields, and you can have a different mapping for it.
3. Put one of the fields in a different index.
Here is a reply from a ES developer https://discuss.elastic.co/t/are-not-allow-to-have-the-same-field-name-in-different-elastic-types-with-differents-types-string-nested-json-number-what-would-be-the-solution-with-elastic-search-for-this-issue/73914/2 https://discuss.elastic.co/t/are-not-allow-to-have-the-same-field-name-in-different-elastic-types-with-differents-types-string-nested-json-number-what-would-be-the-solution-with-elastic-search-for-this-issue/73914/2
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-350656982, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmdma7F807yFv3yq64wHmYsyVQ07Wks5s_OqagaJpZM4Q361E.

Thank You so much, Vincent! I'm excited to get this working.
We'll implement a limiter for the name lengths in SENTINL and confirm here with a full blown execution. Shall I rebuild from the patch branch to confirm or will this fix be merged back in <IP_ADDRESS>?

So am i ! You can build from the dedicated branch and i will merge-it to quickly release <IP_ADDRESS> everything works fine for you.

Le 11 déc. 2017 à 11:45, Lorenzo Mangani<EMAIL_ADDRESS>a écrit :
Thank You so much, Vincent! I'm excited to get this working.
We'll implement a limiter for the name lengths in SENTINL and confirm here with a full blown execution. Shall I rebuild from the patch branch to confirm or will this fix be merged back in <IP_ADDRESS>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-350687959, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmdJDF-bQuMliVKHVfebR7Abj4lu1ks5s_QfRgaJpZM4Q361E.

Seems to work with the patched Elassandra and with SENTINL ids shortened as you suggested. Will do some deeper testing tomorrow but definitely a GO and looking forwar to <IP_ADDRESS> :) Thansk @vroyer
To reproduce w/ stock SENTINL:
sed -Ei "s/substr(2, 100)/substr(2, 3)/g" ${KIBANA_PLUGIN_PATH}/sentinl/public/services/watcher.js

Fine !
As explain in a previous mail, i have a glitch when SSL+Authentication are in place on elasticsearch (traces in my mail).
Does sentinl work properly with the Pack or search guard with authentication ?
Thanks.
Vincent Royer
<EMAIL_ADDRESS>+33 7 83 18 25 40
http://www.strapdata.com

Le 12 déc. 2017 à 00:45, Lorenzo Mangani<EMAIL_ADDRESS>a écrit :
Seems to work with the patched Elassandra and with SENTINL ids shortened as you suggested. Will do some deeper testing tomorrow but definitely a GO and looking forwar to <IP_ADDRESS> :) Thansk @vroyer https://github.com/vroyer
To reproduce w/ stock SENTINL:
sed -Ei "s/substr(2, 100)/substr(2, 3)/g" ${KIBANA_PLUGIN_PATH}/sentinl/public/services/watcher.js
https://user-images.githubusercontent.com/1423657/33859729-8d0b6fdc-ded5-11e7-853f-355a0035d447.gif
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/146#issuecomment-350896160, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmSwli6mJuGg8wCr9faRqlUIzD9Kdks5s_b6fgaJpZM4Q361E.

Let's arrange a small workshop, we can iron all those issues and preferences out together?

@vroyer SG should work with the right configs: https://github.com/sirensolutions/sentinl/wiki/SENTINL-FAQ#q-how-can-i-use-sentinl-with-searchguard-authentication


Enhancement: Retarget view after move

Calling view.retarget() rather than closing and reopening avoids flicker effects and improves user experience.

👍


Cython closures cannot capture const or reference types.

E.g.
cdef int foo(const int& i):
  def bar():
    return i
  return bar()

produces invalid assignment code when creating the closure.

I've hit this while trying to get https://github.com/cython/cython/pull/3323 working again with the most recent master (but may end up working around it there irrespective of this).
It seems like there are three options:

Capture by value (i.e. make a copy of i in the closure of bar) - this is the safest option.
Capture by "fake reference" (i.e. pointer really) - this breaks if the closure outlives whatever i is, but it is arguably doing what the user asked.


Add /time command to change/freeze time of day, nighttime/daytime and/or server-side time

Sometimes you want to see better but it is nighttime, all you can do now that I have found is to wait until the time changes. A command such as /time to alter the time would be indeed useful. Possible aliases /time day, /time night, /day, /night, perhaps even an option to freeze time and disable the daylight cycle.

Time from glfw time is problematic, see also GH-10, native vs web connecting to same server (GH-36):

https://github.com/satoshinm/NetCraft/commit/d545011ce268dbfff6601b1788b8dcd2ad9a60c2 adds "LAN mode with fixed hour (option)"

There is already some support for "server-side time", via the "E" command: src/main.c:
        if (sscanf(line, "E,%lf,%d", &elapsed, &day_length) == 2) {
            glfwSetTime(fmod(elapsed, day_length));
            g->day_length = day_length;
            g->time_changed = 1;
        }


Update pkg list for ubuntu2404

Updates package list for Ubuntu Server 24.04 LTS
Avoids following error(s)
The following packages have unmet dependencies:
 satisfy:command-line : Depends: python3-pip (= 22.0.2+dfsg-1ubuntu0.4) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Hey @raul-marquez-csa,
There's a commit in this PR Update User Guide For Fall2024 that was added by mistake.
If you fetch the newest version of the v2.11-beta2+fall2024 you'll see that this commit was removed from the branch.
 Sorry for the inconvenience


Fix standby namenode restart.

This commit prevents a restart of the standby namenode.   If the restart is executed on a fresh cluster, the standby namenode halts with an error.

Ray's pointed out moving this to a subscription would be better and allow for cluster upgrades to bounce the secondary namenode.


demo-image-full: add tensorrt-tests to image

which will pull in tensorrt-samples
Signed-off-by: Ilies CHERGUI<EMAIL_ADDRESS>

This PR need meta-tegra-community repo updates.


Cloud Script ScenarioGrabber failing to update quest list

In some cases, the scenario Grabber script can throw an exception and stop without updating the quest list.
This should not be the case, the script should be more reliable, even if some content grabbed is invalid.

Fixed.
The script also sends an email for every scenario having an error in description.


Custom confirmation message

Enables custom form submission success confirmation messages in markdown.
I have verified this PR works with

[x] Online form submission
[x] Offline form submission
[x] Saving offline drafts
[x] Loading offline drafts
[ ] Editing submissions
[ ] Form preview
[ ] None of the above

What else has been done to verify that this works as intended?
This PR is being tested in integration with Kobo by the Kobo team.
Why is this the best possible solution? Were any other approaches considered?
We discussed this solution at length. Key aspects of the implementation are:

Looks for a submitMessage node in the form before rendering a custom message node to ensure backward compatibility with forms that already have a message node but don't expect this behavior.
Renders markdown
Visually hides the success dialog title but leaves it available in the DOM for assistive technologies.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
If you opt into this feature with a form, submitters will see a custom submit message.
Do we need any specific form for testing your changes? If so, please attach one.
You need a form with a submitMessage node and a message node. I have been testing with centro. An example message response is available at jnm/centro/.../app/controllers/submission.js#L51.

Some related background... this custom confirmation message necessitated being able to add a custom instance attribute in the original form with which to specify (to the backend...) what field in the form to use to populate the desired response. This in turn requires, preferably, being able to specify a usual ${foo} identifier in the associated XLSForm as the value for this custom attribute. However, presently pyxform does not correctly parse and resolve ${foo} strings in custom attribute value to their XML element path; instead it merely copies the string "${foo}" as-is. This is discussed in some depth on the ODK Forum here as a desired fix - or new feature depending on your view - to pyxform: https://forum.getodk.org/t/xlsform-spec-also-resolve-foo-names-in-custom-settings-attributes/48735
There is a open issue against pyxform to address this: https://github.com/XLSForm/pyxform/issues/717

Thank you, @lognaturel, for your review. We're going to continue revising this PR significantly, so please consider it to be a draft at this time—and @boazsender will mark it as such :)

Marked this back to draft. I'm moving this work to the single route, and will address your other comments when I do @lognaturel. Thanks for the great review!

I was confused when I said I was moving this work to the single route. I was trying to figure out why my implementation wasn't working in the single route before I realized that my test form had a redirect url, which this implementation didn't account for. I'm working on an update that supports redirect urls.
I also know we're having a broader conversation about whether this work would be accepted at all. Completely understand your concerns. I'm going to update my branch (and this PR) to include my new implementation so that Kobo can use it. We can continue the conversation about whether this code makes sense here. Just didn't want you to be surprised by the changes to the branch.

Pushed a new commit which adds support for custom messages to forms with redirects, and addressed the type integrity feedback (thanks for that @lognaturel). I also rebased from main to keep this PR up to date. I can also address the markdown sanitization feedback with a little more guidance on how that's done in this project.

Oh, and I also made some styling changes for custom messages in this latest commit.

And one more commit for tidier scroll bars.

I'm closing this PR for now based on the discussion above and to improve the proposed functionality based on initial testing. We'll make a new PR once these things have been addressed and to allow for upfront discussions on the forum.


Study Period- Day of the Week provided in PIR and COE

Is Day of the Week (Mon-Sunday) Needed? Necessary to remove for MVP

Await user testing to determine if we proceed with this change.


Apparent mod incompatibility between Achtung and BuildProductive

Rimworld version 0.14.1249
Achtung by @pardeike
Version used: https://github.com/pardeike/RimWorld-Achtung-Mod/commit/8a237f92b2c3c0b9ab675a678d5f6f9dd9b592a8
Direct download: https://github.com/pardeike/RimWorld-Achtung-Mod/archive/8a237f92b2c3c0b9ab675a678d5f6f9dd9b592a8.zip
BuildProductive by @micktu
Version used: https://github.com/micktu/RimWorld-BuildProductive/tree/0.30
Direct download: https://github.com/micktu/RimWorld-BuildProductive/releases/download/0.30/BuildProductive-0.30.zip
Replication steps: Attempt to start a new colony with both mods enabled (mod order and/or presence of CCL or other mods has no discernible effect).
Error log:
Initializing new game with mods Core, AchtungMod, and BuildProductive-0.30
...
Exception from asynchronous event: System.StackOverflowException: The requested operation caused a stack overflow.

These next 2 lines repeat 599 times in the error log.
  at AchtungMod.MapIniterUtility_Patch.MapIniterUtility_FinalizeMapInit () [0x00000] in <filename unknown>:0
  at BuildProductive.InitScript.MapIniterUtility_FinalizeMapInit () [0x00000] in <filename unknown>:0

Ref: https://github.com/micktu/RimWorld-BuildProductive/issues/1

See my comment in the other repo.

I finally found a new way to patch Rimworld code. With this, any number of mods can inject code that runs at the beginning or end of an existing method and even has the ability to skip the original code if necessary. I do it by creating dynamic code and compile it at runtime, then patch the routine to that new code. Side effect: everyone can use the lib to compile stuff at runtime for their own purpose.
Just fixing the last few quirks and adding some sort of importance factor to each patch so the lib can order them in a custom order that is independent of mod load order.
I will create a repo here that will allow everyone to contribute and drive this into a direction that everyone could benefit from.

Totally makes sense. Good job! Unfortunately, I cannot contribute, as I'm not supporting my mod anymore.

Hi micktu. Not sure if you're interested but I think you might find it interesting that I have released a general c# patching library called "Harmony". Works with Unity mods (not Rimworld only) and is totally non-destructive. Check it out at https://github.com/pardeike/Harmony and feel free to contribute if you're into such a thing :-)
Cheers!


README: avoid unintended #smooth-scroll-top scrolls

In the WordPress world, occasionally external plugins have admin menu items with # anchors, which will trigger unintended smooth scrolling if we blindly follow README.md. I would recommend adding an example for ignoring links that are exactly #, and explicitly recommend against using such an anonymous target as a scroll to top mechanism. Then the default example configuration could become:
<script>
	var scroll = new SmoothScroll('a[href^="#"]', ignore: 'a[href="#"]');
</script>

Wasn't able to think of a selector that would do this in a single expression.
Your thoughts?

I've added a setting option for this in v14.x, currently in testing and awaiting release.
{
    topOnEmptyHash: true, // If true, scroll to the top of the document on `href="#"`
}


Support subgraph studio subgraphs (backend)

In order to keep the DApp running, we should need to our studio-deployed subgraph as soon as possible. The hosted version that we are using now will not be supported indefinitely and is actually past its announced date of support.
We also need this on the frontend - the relevant issue is being created. Please notify devops once the changes can be merged, so we can have a seamless transition!
Link to issue for frontend: issue #2836 in different repo

@CarlosQ96 @aminlatifi
what happened to this, I remembered we rolled it back, is it safe we test one more time?

@CarlosQ96 @aminlatifi what happened to this, I remembered we rolled it back, is it safe we test one more time?

It has been rolled back, you are right.
we must coordinate with devops team for it to provide us the studio links. Though, by integrating givpower balance aggregator we won't need subgraph link in impact-graph AFAIK

@aminlatifi what happened to their bug,  did they respond?

@aminlatifi what happened to their bug, did they respond?

Our last message to them is unresponded!
https://discord.com/channels/438038660412342282/1142798258364747898/1144262860525015181

@CarlosQ96 @aminlatifi is this issue still relevant?

@CarlosQ96 @aminlatifi is this issue still relevant?

yes, it can be closed.


Better PSR-3 message formatting

Successor of #972
Does two things:

Include milliseconds in the default date format
Show actual content of the array

Thanks


RDCMan - Support for AAD auth

The Remote Desktop Client supports AAD auth by adding enablerdsaadauth in the connection file. Would be nice if RDCMan would have an option to enable this in connections.
Even better if we could supply a login_hint to the process, but I think that's not an option available in mstsc.
Source: https://learn.microsoft.com/en-us/windows/client-management/client-tools/connect-to-remote-aadj-pc

See  - RDCman 2.93 does allow some Azure VMs to connect with Azure creds.

still an issue as of 10/8/2024 - Azure based VM's using SSO do work with RDCMan - Intune/Autopiloted devices do not.


tx not found

Summary of Bug
Hi, After testing, we found that there are many txs not found, such as the hash ba68a0fbb70b062f1a3452dda918c75cddbdb2bdc8f7eb34ee91d42e8e505326. Our wallet program decoded and detected this transaction, but could not obtain the detailed information.
curl -X 'GET' 'https://api.celestia.pops.one/cosmos/tx/v1beta1/txs/ba68a0fbb70b062f1a3452dda918c75cddbdb2bdc8f7eb34ee91d42e8e505326'
{
"code": 5,
"message": "tx not found: ba68a0fbb70b062f1a3452dda918c75cddbdb2bdc8f7eb34ee91d42e8e505326",
"details": [
]
}
What causes this transaction? Is it a special transaction? Can your team help to check it? Thanks!
Version
v1.3.0
Steps to Reproduce

Get the data of block height 408
curl https://api.celestia.pops.one/cosmos/base/tendermint/v1beta1/blocks/408
Use program decoding to obtain the transaction list
ba68a0fbb70b062f1a3452dda918c75cddbdb2bdc8f7eb34ee91d42e8e505326 in block
Report an error after obtaining transaction details
curl -X 'GET' 'https://api.celestia.pops.one/cosmos/tx/v1beta1/txs/ba68a0fbb70b062f1a3452dda918c75cddbdb2bdc8f7eb34ee91d42e8e505326'
{
"code": 5,
"message": "tx not found: ba68a0fbb70b062f1a3452dda918c75cddbdb2bdc8f7eb34ee91d42e8e505326",
"details": [
]
}

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Can you please elaborate on

Use program decoding to obtain the transaction list

https://www.mintscan.io/celestia/block/408 contains 100 txs but I can't find the tx hash you pasted. For example https://www.mintscan.io/celestia/tx/ba68a0fbb70b062f1a3452dda918c75cddbdb2bdc8f7eb34ee91d42e8e505326?height=408 does not display a result.

Use program decoding to obtain the transaction list --- You can find a Cosmos SDK to parse out the transactions contained in block 408.
Yes, that's the problem, the transaction cannot be found on the node and block explorer. But the txs field in the block 408 information contains the transaction hash.

Sorry to repeat this but can you please expand on

You can find a Cosmos SDK to parse out the transactions contained in block 408.

I'm not convinced that the tx hash in the issue description actually exists in block 408 so I think the mechanism you're using to parse out the transaction hashes is flawed. Can you link to the code you're using or a Go playground that reproduces it?

Sorry to repeat this but can you please expand on

You can find a Cosmos SDK to parse out the transactions contained in block 408.

I'm not convinced that the tx hash in the issue description actually exists in block 408 so I think the mechanism you're using to parse out the transaction hashes is flawed. Can you link to the code you're using or a Go playground that reproduces it?

Sorry, I'm busy today. Tomorrow I will use a test code to completely reproduce the issue. Thank you for your reply and your patience.

package main
import (
"crypto/sha256"
"encoding/base64"
"encoding/hex"
"encoding/json"
"fmt"
"net/http"
"strings"
)
type BlockResponse struct {
Block Block json:"block"
}
type Block struct {
Data BlockData json:"data"
}
type BlockData struct {
Txs []string json:"txs"
}
func sum(bz []byte) []byte {
h := sha256.Sum256(bz)
return h[:]
}
func main() {
blockHeight := 408
apiURL := fmt.Sprintf("https://api.celestia.pops.one/cosmos/base/tendermint/v1beta1/blocks/%d", blockHeight)
response, err := http.Get(apiURL)
if err != nil {
	fmt.Println("Unable to get block data:", err)
	return
}
defer response.Body.Close()

var blockResponse BlockResponse
if err := json.NewDecoder(response.Body).Decode(&blockResponse); err != nil {
	fmt.Println("Unable to parse block data:", err)
	return
}

fmt.Println("block height:", blockHeight)
txCount := 0

for _, rawTx := range blockResponse.Block.Data.Txs {
	txCount++
	fmt.Println("Transaction #", txCount)
	fmt.Println("rawTx:", rawTx)
	txBytes, err := base64.StdEncoding.DecodeString(rawTx)
	if err != nil {
		fmt.Println(err)
		return
	}
	txHash := hex.EncodeToString(sum(txBytes))

	fmt.Println("txHash (lowercase):", txHash)
	fmt.Println("txHash (uppercase):", strings.ToUpper(txHash))
	fmt.Println()
}

}

The above is the golang test code. You can see the results by running it locally. Since the log is too long, I didn't upload it.
You can see that the last transaction parsed out is:
txHash (lowercase): ba68a0fbb70b062f1a3452dda918c75cddbdb2bdc8f7eb34ee91d42e8e505326
txHash (uppercase): BA68A0FBB70B062F1A3452DDA918C75CDDBDB2BDC8F7EB34EE91D42E8E505326
But via curl -X 'GET' 'https://api.celestia.pops.one/cosmos/tx/v1beta1/txs/ba68a0fbb70b062f1a3452dda918c75cddbdb2bdc8f7eb34ee91d42e8e505326'
Obtained in this way, the returned message is tx not found.

the transactions found in the comet block are encoded as protobuf encoded BlobTx, which contains both the blob and the transaction that pays for that blob. The hashes stored and returned by comet (for example when I submit a tx) have been modified to only represent the transaction that the user signs over, not the BlobTx. More information can be found in our in various portions of our spec, but I can see how this has not been communicated clearly enough.
if we are only interested in the transactions, then we can use the encoding config to decode transactions in golang. The canonical way of getting blobs is from celestia-node, but if we're also interested in the blob then we can parse BlobTxs in this functions. After parsing the blobtx, then we simply hash the tx in the Tx field and get the actual hash.

@hot-westeros does this make sense? have any further questions? I (and our docs) might not be explaining it well enough
I would like to close this issue since it is not a bug, although it has been very valuable feedback for improving devX

OK, you can close, thanks for your follow-up and reply.

Sorry I'm late to this but if it's helpful, I modified your code snippet and pasted https://go.dev/play/p/89hzCtbwrY3. When I run it, I observe the last tx hash as:
tx 273
txHash: C55BDD3DF3348A9F8D9206528051804754F009A1B9D0F69CCC2F9D4334215D21

which is available at https://api.celestia.pops.one/cosmos/tx/v1beta1/txs/C55BDD3DF3348A9F8D9206528051804754F009A1B9D0F69CCC2F9D4334215D21. The major difference between your code and the revised code in my Go playground is the getTxBytes behavior.


Input norm + dilution plate functions?

Hello Developers!
We've been having to dilute our gDNA plates a lot recently and would like the following line of code to be added to Section 2.5 Step 4 of the metagenomics_pipeline_MiniPiconorm notebook:

The technicians have been adding this line in by hand but it would be nice to codify it. It allows us to feed in a dilution plate into the echo in addition to the sample and water plates.
Many thanks!
.
.
.
Also on the topic of dilution plates - the input norm transfer file generated by the format_dna_norm_picklist function currently spits out a file that looks like this with the water transfers on top:

If it could spit a file with the DNA additions prior the water additions, that would allow the wetlab technicians to visually check that all the DNA actually transfered prior to initiating the water transfer. It's a nice QC. Pretty sure all you need to do is flip the order of these two code snippets:

Many many many thanks,
Helena T.

Hello
I discussed this with Helena.
We will be testing which Source Plate order is optimal for DNA Input Normalization.
Once we come to a a decision, I can make the necessary changes to the repository and do a pull request.
Thanks,
Rodolfo

On Oct 28, 2022, at 1:02 AM, DrCletusSpucklerMD @.***> wrote:
Hello Developers!
We've been having to dilute our gDNA plates a lot recently and would like the following line of code to be added to Section 2.5 Step 4 of the metagenomics_pipeline_MiniPiconorm notebook:
https://user-images.githubusercontent.com/22571541/198531559-11636ae7-313d-45ce-9c99-24a4b0c2315b.png
The technicians have been adding this line in by hand but it would be nice to codify it. It allows us to feed in a dilution plate into the echo in addition to the sample and water plates.
Many thanks!
.
.
.
Also on the topic of dilution plates - the input norm transfer file generated by the format_dna_norm_picklist function currently spits out a file that looks like this with the water transfers on top:
https://user-images.githubusercontent.com/22571541/198532067-300117e4-3107-4731-8aaa-203d3a1888a3.png
If it could spit a file with the DNA additions prior the water additions, that would allow the wetlab technicians to visually check that all the DNA actually transfered prior to initiating the water transfer. It's a nice QC. Pretty sure all you need to do is flip the order of these two code snippets:
https://user-images.githubusercontent.com/22571541/198535721-31f9cd8a-628c-4c32-9e6a-73ff2b52d3d2.png
Many many many thanks,
Helena T.
—
Reply to this email directly, view it on GitHub https://github.com/biocore/metagenomics_pooling_notebook/issues/84, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADEVFI25OKQ45NCMSA6O4NLWFOB7RANCNFSM6AAAAAARQ2BIZU.
You are receiving this because you are subscribed to this thread.

Thanks for helping guide me through this Github "Issues" process here,
Rodolfo! I didn't know Github "Issues" existed and got a little overzealous
trying to find a use for it! Exciting.
Thank you both,
Helena
On Fri, Oct 28, 2022 at 1:31 PM RodolfoSalido @.***>
wrote:

Hello
I discussed this with Helena.
We will be testing which Source Plate order is optimal for DNA Input
Normalization.
Once we come to a a decision, I can make the necessary changes to the
repository and do a pull request.
Thanks,
Rodolfo

On Oct 28, 2022, at 1:02 AM, DrCletusSpucklerMD @.***> wrote:
Hello Developers!
We've been having to dilute our gDNA plates a lot recently and would
like the following line of code to be added to Section 2.5 Step 4 of the
metagenomics_pipeline_MiniPiconorm notebook:
<
https://user-images.githubusercontent.com/22571541/198531559-11636ae7-313d-45ce-9c99-24a4b0c2315b.png>
https://urldefense.com/v3/__https://user-images.githubusercontent.com/22571541/198531559-11636ae7-313d-45ce-9c99-24a4b0c2315b.png*3E__;JQ!!Mih3wA!CPqiyDH4-A4h-aSM9J4lwvrG5joISQ1CSOgCCvckTxaBh8-bmoYEMGnjGsPbXJ_fHOcEc-BIfLW0Kge0oPr_wHA$
The technicians have been adding this line in by hand but it would be
nice to codify it. It allows us to feed in a dilution plate into the echo
in addition to the sample and water plates.
Many thanks!
.
.
.
Also on the topic of dilution plates - the input norm transfer file
generated by the format_dna_norm_picklist function currently spits out a
file that looks like this with the water transfers on top:
<
https://user-images.githubusercontent.com/22571541/198532067-300117e4-3107-4731-8aaa-203d3a1888a3.png>
https://urldefense.com/v3/__https://user-images.githubusercontent.com/22571541/198532067-300117e4-3107-4731-8aaa-203d3a1888a3.png*3E__;JQ!!Mih3wA!CPqiyDH4-A4h-aSM9J4lwvrG5joISQ1CSOgCCvckTxaBh8-bmoYEMGnjGsPbXJ_fHOcEc-BIfLW0Kge06Tbfpn4$
If it could spit a file with the DNA additions prior the water
additions, that would allow the wetlab technicians to visually check that
all the DNA actually transfered prior to initiating the water transfer.
It's a nice QC. Pretty sure all you need to do is flip the order of these
two code snippets:
<
https://user-images.githubusercontent.com/22571541/198535721-31f9cd8a-628c-4c32-9e6a-73ff2b52d3d2.png>
https://urldefense.com/v3/__https://user-images.githubusercontent.com/22571541/198535721-31f9cd8a-628c-4c32-9e6a-73ff2b52d3d2.png*3E__;JQ!!Mih3wA!CPqiyDH4-A4h-aSM9J4lwvrG5joISQ1CSOgCCvckTxaBh8-bmoYEMGnjGsPbXJ_fHOcEc-BIfLW0Kge0m_BN56A$
Many many many thanks,
Helena T.
—
Reply to this email directly, view it on GitHub <
https://github.com/biocore/metagenomics_pooling_notebook/issues/84>
https://urldefense.com/v3/__https://github.com/biocore/metagenomics_pooling_notebook/issues/84*3E__;JQ!!Mih3wA!CPqiyDH4-A4h-aSM9J4lwvrG5joISQ1CSOgCCvckTxaBh8-bmoYEMGnjGsPbXJ_fHOcEc-BIfLW0Kge0czst8hI$,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/ADEVFI25OKQ45NCMSA6O4NLWFOB7RANCNFSM6AAAAAARQ2BIZU>
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ADEVFI25OKQ45NCMSA6O4NLWFOB7RANCNFSM6AAAAAARQ2BIZU*3E__;JQ!!Mih3wA!CPqiyDH4-A4h-aSM9J4lwvrG5joISQ1CSOgCCvckTxaBh8-bmoYEMGnjGsPbXJ_fHOcEc-BIfLW0Kge0BMwOWJo$
.
You are receiving this because you are subscribed to this thread.

—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/biocore/metagenomics_pooling_notebook/issues/84*issuecomment-1295436398__;Iw!!Mih3wA!CPqiyDH4-A4h-aSM9J4lwvrG5joISQ1CSOgCCvckTxaBh8-bmoYEMGnjGsPbXJ_fHOcEc-BIfLW0Kge0lMPLfmc$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AFMGUFLYH6FEQQ2UCFHJ7LLWFQZ2DANCNFSM6AAAAAARQ2BIZU__;!!Mih3wA!CPqiyDH4-A4h-aSM9J4lwvrG5joISQ1CSOgCCvckTxaBh8-bmoYEMGnjGsPbXJ_fHOcEc-BIfLW0Kge04AtEdtQ$
.
You are receiving this because you authored the thread.Message ID:
@.***>

Just to keep everyone on the same page, @charles-cowart (thank you!) issued a PR solving this: https://github.com/biocore/metagenomics_pooling_notebook/issues/84. @RodolfoSalido / @DrCletusSpucklerMD , could you take a look/review? Thank you.


Update to iOS 15 deployment target

Task/Issue URL: https://app.asana.com/0/414235014887631/1207384568093628/f
Tech Design URL:
CC:
Description:
This PR updates the app to use an iOS 15 deployment target.
I've intentionally avoided cleaning up availability checks to keep this PR small and simple, in case it needs to be reverted last-minute. After the change has been released and looks good, I'll clean up the availability checks.
Each target in the app had overridden the deployment target, so I removed those overrides in favour of having each target inherit the deployment target from the parent project settings. Now we only have to change one value to set the deployment target across the board.
Workflow Runs:

Alpha Build
E2E Tests

Steps to test this PR:

Check the the deployment target on each target in the app is iOS 15
Check that the app builds and runs fine, and that CI passes

Definition of Done (Internal Only):

[ ] Does this PR satisfy our Definition of Done?

Device Testing:

[ ] iPhone SE (1st Gen)
[ ] iPhone 8
[ ] iPhone X
[ ] iPhone 14 Pro
[ ] iPad

OS Testing:

[ ] iOS 15
[ ] iOS 16
[ ] iOS 17

Theme Testing:

[ ] Light theme
[ ] Dark theme

Internal references:
Software Engineering Expectations
Technical Design Template

@samsymons Changes looks ok, maybe we should try running some flows (e2e tests, ad hoc build) from this branch?

@bwaresiak I've updated the description to links of successful workflow runs. The remaining one I haven't tested is the Nightly Alpha workflow, but there's no good way to test it without publishing a real build to the alpha channel, and because the ad-hoc pipeline works (proving the ad-hoc target archives successfully) I feel it's acceptable.

@samsymons yes that's great, thank you :)