Building the query in stages

How Is it possible to build my query using multiple statements?  I would like to do something like this:
var provider = new RedisConnectionProvider("redis://localhost:6379");
var collection = provider.RedisCollection<Transaction>();
var query = collection.Where(q=>q.Account == "1234");

// Do some logic tests here
if (activeOnly) query = query.Where(q=> q.Active == true);  // originally (q=> q.Active)

var totalCount = query.Count();
var pagedResults = query.Skip(skip).Take(take).ToList();
return {Total = totalCount, Results = pagedResults};

Update 1:  It appears the issues is with the Boolean parsing.  When I change to (q.Active == true) I get more milage.
Update 2:  I think maybe it's joining the two expressions as an OR, and not an AND, as I am getting back too many results.
Update 3:  Depending on the dataset, my milage varies, but I could definitely see a need for a way to build a query.  If not this way outlined above, some QueryBuilder object that allows to string together various Func<T,bool> expressions into one logical query that the backend will understand.
Thoughts?

RedisCollection only supports a single Where clause at the moment. Interesting point about the q.Active == true vs. q.Active, realistically it's mostly meant for string matching but there should be something we can do to get it to pick up on boolean expressions like so. Might be an enhancement worth making.
I'd contest that if you've already done collection.Where(q=>q.Account == "1234");, and need to apply some intermittent logic before applying the q.Active == true, that you've already had a need for materializing the results, and therefore should just be able to build your results off of the materialized results, otherwise, you should just have it all in the same Where clause.

So, my query is complicated slightly with the paging aspect, in that I need to get a count of all items returned by the query, as well as just the paged result, so I was trying to do that all in the DB and only pull back the page worth of actual results.
But yes, I think in its current form it will be a two-step process, requiring I bring a lot of data down, then perform additional filtering.
Question:  Is it OM library that only supports the single where clause, or is it not supported upstream?  And if the former, how big of a lift is it to get multiple where clauses (or some form of builder that can eventually build the single where clause)?

Issue with Count
It looks like Count is ignoring the predicate passed into it, however, if you send an empty count after your where clause, it works as expected
var muppets = provider.RedisCollection<Muppet>();

await muppets.InsertAsync(kermit);
await muppets.InsertAsync(beaker);
await muppets.InsertAsync(bunsen);

Console.WriteLine(muppets.Where(x=>x.FirstName == "kermit").Count());
Console.WriteLine(muppets.Count(x=>x.FirstName == "Kermit"));

results in:
1
3

The arching assumption is that you'll primarily use the Where clause for filtering, but we do have precedent for other cases, e.g. [Any](https://github.com/redis/redis-om-dotnet/blob/main/src/Redis.OM/Searching/RedisCollection.cs#L80). So this should be something relatively easy to fix.
Pagination

So, my query is complicated slightly with the paging aspect, in that I need to get a count of all items returned by the query, as well as just the paged result, so I was trying to do that all in the DB and only pull back the page worth of actual results.

I think I should probably point out to you, that Redis.OM will automatically paginate for you based on the chunk size you requested when initializing the collection.
Single where clause
The rationale behind the single where clause has to do with the way queries work in RediSearch. This isn't SQL after all, you can't do any sort of table-joins or any cross-index querying, and the FT.SEARCH command that the RedisCollection operates off of only takes a single query string. So it's basically a reflection of the way the server operates. If we were going to allow multiple where clauses, it would effectively just be extending the same expressions .Where(x=>x.FirstName == "kermit").Where(x=>x.LastName == "the frog") is effectively the same as .Where(x=>x.FirstName == "Kermit" && x.LastName == "the frog");,  with the Predicate builder you are using, it looks like it should be producing the binary expressions that Redis.OM expects.

Pagination

So, my query is complicated slightly with the paging aspect, in that I need to get a count of all items returned by the query, as well as just the paged result, so I was trying to do that all in the DB and only pull back the page worth of actual results.

I think I should probably point out to you, that Redis.OM will automatically paginate for you based on the chunk size you requested when initializing the collection. It's an async enumerable so you can just await it, Redis.OM will take care of it for you, I would encourage you to lean towards larger chunk sizes if you can.

So, I think with the Count issue resolved, I can move forward.  What I meant about the paging is not all in one call, but from the web UI client, the ability to page through the results back form the DB.  i.e., each page is a single request received and fulfilled by the back-end Api. So, it would not be a case of holding a connection open while we page the results down, so to speak.
Yes, I have been having luck with the Predicate Builder, and your example of multiple .Where() clauses would be what I would expect to be able to do.  Check some logic, add a .Where(), further down, check some logic, continue building the .Where() clause.  Maybe you see the value in adding the functionality natively?
Thank-you again for your detailed response. 👍

Interesting point about the q.Active == true vs. q.Active, realistically it's mostly meant for string matching but there should be something we can do to get it to pick up on boolean expressions like so. Might be an enhancement worth making.

Yeah, now my tests are showing no valid results with a Boolean in the search.  How big of a lift is it to get boolean checking working?

So yeah, skip/take for pagination is the right route then,
RE folding together Where queries, I think if you have an API with a more complex conglomeration of things you might be combining this probably has a lot of merit as a nice-to-have, but the problem would happen down-stream as you start building anon types on top of whatever the type of the collection is, could probably validate, not certain how difficult this would be, probably would have to do something similar to the expression building library you pointed to.

Going to be working on this one today on stream if anyone's interested: https://www.twitch.tv/redisinc


Support right and left ?

Hi, I have a simple style:
LTE

RTL

With this code:

It is worked with lte but rtl the right arrow does not work!

There's no lte variant. Only ltr and rtl
If it doesn't work, make sure you added the 'direction' variant to the rules you need. By default the README's example config only adds those variants for float, margin and padding.

@RonMelkhior  Sorry for the typo, I added the right and left in variant:
variants: {
        right: ['responsive', 'direction'],
        left: ['responsive', 'direction'],
        float: ['responsive', 'direction'],
        margin: ['responsive', 'direction'],
        padding: ['responsive', 'direction'],
    },

Instead of right & left in the config, do inset: ['responsive', 'direction'],. Should work then

THANKS 👍


remap: panic on source osd missing from up set

When the cluster is not in a happy state, and the source OSD is not in the up set, pgremapper remap will panic, preventing the user from trying to reconstruct data from a down OSD on a specific target.

Some years ago, pgremapper have many of panics, see https://github.com/digitalocean/pgremapper/issues/10#issuecomment-945648879
Today, the master code works for us in every-day usage. So, if you think you find the new bug, lease read, how to Bug Reports
For a quick fix you can use this shell function
function fix_pgremapper_panic() {
  # function fix situations when pgremapper is crashed on some osdmaps
  local pg
  local upmap_cmd
  upmap_cmd="--verbose"

  if [[ -n "${UPMAP_POOL}" ]]
    then
      upmap_cmd="${upmap_cmd} --include-pools ${UPMAP_POOL}"
  fi

  # shellcheck disable=SC2086
  until ${PG_REMAPPER} cancel-backfill ${upmap_cmd} > /dev/null 2>&1
    do
      pg="$(${PG_REMAPPER} cancel-backfill ${upmap_cmd} 2>&1 >/dev/null | \
        grep "panic" | tr -d '\n' | awk '{print $3}' | sed 's|:||g')"
      echo -e "Fix pgremapper panic for PG ${pg}"
      ceph osd rm-pg-upmap-items "${pg}"
      sleep 1s
    done
}

Thanks @k0ste! @Matt1360 is actually one of the pgremapper devs; we noticed this issue last week and wanted to make sure we didn't lose track of it.


NuGet package: release notes to link

This change is

Codecov Report

Merging #1974 into master will increase coverage by 1%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #1974    +/-   ##
=======================================
+ Coverage      82%     82%    +1%
=======================================
  Files         286     286
  Lines       19658   20387   +729
  Branches     2296    2474   +178
=======================================
+ Hits        16042   16766   +724
- Misses       3047    3052     +5
  Partials      569     569

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 586a737...4dbac78. Read the comment docs.

Travis is unstable at +22:00 (UTC)


Determining closed connections using PQstatus rather than matching on message strings

Addresses https://github.com/diesel-rs/diesel/issues/2957
Description
This PR makes it so that errors reported for the PgResult need to match on message strings directly from libpq. Instead we call PQstatus directly and attempt to match against the ConnStatusType::CONNECTION_BAD variant.
Testing
cargo test --no-default-features --features "extras postgres" passes

Note: I read through the context on (in order of most recent to oldest):

https://github.com/diesel-rs/diesel/pull/2935
https://github.com/diesel-rs/diesel/pull/2911
https://github.com/diesel-rs/diesel/pull/2860

And tried to determine why string matching was performed in the first place but couldn't so for full transparency I'm only doing what was suggested in this comment. I did a little research by trying to pull down the postgres repo but didn't get far trying to grok C code 😅 to the point I was particularly confident about what I was reading
https://github.com/postgres/postgres/blob/42dbbca58e8e87e461bb0a4fe48a450e90e1e932/src/interfaces/libpq/fe-misc.c#L753-L764

Okay as far as testing that this is exhaustive, I'm still not entirely sure as I think there are a lot of failure cases, but I did add one test, inspired by this PR. Steps to reproduce:
1/ Add following code to this commit:
@ diesel [stevenchu]$ git diff
diff --git a/diesel/src/pg/connection/mod.rs b/diesel/src/pg/connection/mod.rs
index c1a6cf3c8b..58f26e236d 100644
--- a/diesel/src/pg/connection/mod.rs
+++ b/diesel/src/pg/connection/mod.rs
@@ -264,6 +264,15 @@ mod tests {
     use crate::sql_types::{Integer, VarChar};
     use std::num::NonZeroU32;

+    #[test]
+    fn wait_a_looooong_time() {
+        let connection = &mut connection();
+
+        crate::sql_query("SELECT pg_sleep(100.0);")
+            .execute(connection)
+            .unwrap();
+    }
+
     #[test]
     fn malformed_sql_query() {
         let connection = &mut connection();
diff --git a/diesel/src/pg/connection/result.rs b/diesel/src/pg/connection/result.rs
index f751b861ad..689d720f36 100644
--- a/diesel/src/pg/connection/result.rs
+++ b/diesel/src/pg/connection/result.rs
@@ -71,8 +71,14 @@ impl PgResult {
                     };
                 let error_information = Box::new(PgErrorInformation(internal_result));
                 let conn_status = conn.get_status();
+                println!("The conn_status object is: {:?}", conn_status);
+                println!(
+                    "And error_information.message() is: {:?}",
+                    error_information.message()
+                );
                 if conn_status == ConnStatusType::CONNECTION_BAD {
                     error_kind = DatabaseErrorKind::ClosedConnection;
+                    println!("Yes we're inside here! {:?}", error_kind);
                 }
                 Err(Error::DatabaseError(error_kind, error_information))
             }

2/ Run the test
@ diesel [stevenchu]$ cargo test --no-default-features --features "postgres" wait_a_looooong_time
   Compiling diesel v2.0.0 (/Users/stevenchu/personal_projects/rust/diesel/diesel)
    Finished test [unoptimized + debuginfo] target(s) in 2.48s
     Running unittests (/Users/stevenchu/personal_projects/rust/diesel/target/debug/deps/diesel-56765496a50953ec)

running 1 test
...

3/ Shell into the postgres DB you are running locally (either on your machine directly or via docker)
4/ Find the pid
diesel_test=# SELECT pid, usename, application_name, query FROM pg_stat_activity;
  pid  |  usename  | application_name |                                query
-------+-----------+------------------+---------------------------------------------------------------------
   873 |           |                  |
   875 | stevenchu |                  |
 41521 | postgres  |                  | SELECT pg_sleep(100.0);
 41252 | postgres  | psql             | SELECT pid, usename, application_name, query FROM pg_stat_activity;
   871 |           |                  |
   870 |           |                  |
   872 |           |                  |
(7 rows)

5/ Kill it
diesel_test=# select pg_terminate_backend(41521);
 pg_terminate_backend
----------------------
 t
(1 row)

6/ Watch for test output:
@ diesel [stevenchu]$ cargo test --no-default-features --features "postgres" wait_a_looooong_time
   Compiling diesel v2.0.0 (/Users/stevenchu/personal_projects/rust/diesel/diesel)
    Finished test [unoptimized + debuginfo] target(s) in 2.48s
     Running unittests (/Users/stevenchu/personal_projects/rust/diesel/target/debug/deps/diesel-56765496a50953ec)

running 1 test
test pg::connection::tests::wait_a_looooong_time ... FAILED

failures:

---- pg::connection::tests::wait_a_looooong_time stdout ----
The conn_status object is: CONNECTION_BAD
And error_information.message() is: "FATAL:  terminating connection due to administrator command\nserver closed the connection unexpectedly\n\tThis probably means the server terminated abnormally\n\tbefore or while processing the request.\n"
Yes we're inside here! ClosedConnection
thread 'pg::connection::tests::wait_a_looooong_time' panicked at 'called `Result::unwrap()` on an `Err` value: DatabaseError(ClosedConnection, "FATAL:  terminating connection due to administrator command\nserver closed the connection unexpectedly\n\tThis probably means the server terminated abnormally\n\tbefore or while processing the request.\n")', diesel/src/pg/connection/mod.rs:273:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    pg::connection::tests::wait_a_looooong_time

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 58 filtered out; finished in 7.32s

error: test failed, to rerun pass '--lib'

Note that this is a different error message from the one originally being matched against (perhaps because there's a difference when an admin PG user kills a process vs a network disconnect via the Docker example), but either way seems promising since I'd hope that this too would get caught as an unexpected close (and now does!)
https://github.com/diesel-rs/diesel/blob/d285ebd7768330e5abc31abc1d0c3a29f5261e09/diesel/src/pg/connection/result.rs#L15-L17

Thanks for the update + doing the necessary tests. Generally speaking: If you are unsure if something addresses my remarks just push it anyways. It's always good to know how the code looks like to give specific comments + my remarks are sometimes neither clear nor the best solution. That means if you feel that you could implement a better solution just do it :wink:


Housing counselor: Update sharing text

Changes

Adjusts erroneous sharing text in sharing buttons.

Testing

Pull branch and visit http://localhost:8000/find-a-housing-counselor/?zipcode=20002
Click social media sharing links at the bottom of the page and check output.

Screenshots

Notes

I'm not logged into Facebook and Linkedin on my work machine so can't verify these. Anyone else logged in? I'll be able to check on another machine after this hits prod.

@marteki is the live site any different? Is it different for e.g. the share on https://www.consumerfinance.gov/about-us/blog/servicemembers-arm-yourself-basic-car-buying-skills-stand-your-guard-when-it-comes-add-products/ ? Thanks in advance!

@anselmbradford It is! 🎉 Content is pre-populating as expected. Good catch!
Facebook:

LinkedIn:


Show example of citus.multi_task_query_log_level

We discuss the valid options for this enum in https://docs.citusdata.com/en/v7.3/reference/configuration.html#citus-multi-task-query-log-level-enum
However Craig suggested that we also give examples of what appears in the logs as a result of setting the GUC.

Somewhat related observation, just adding it to this issue as a place to take care of it:
A lot of people seem to run set foo = bar when they should run alter database set foo = bar. Find where to clarify this in the docs.


EBV selector can now work with regular and irregular time steps

I needed to model the enum for regular time series or irregular time series as list.

bors merge


make dualline thumbnail have consistent size as other thumbnails

Thumbnails all have size 1024x1024 except for dualline (1024x1014).

Thank you for taking the time


[Dashobard] Fix bad merge

Fixing a bad code merge in dashboard save function 😖

LGTM

Codecov Report

Merging #5624 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5624      +/-   ##
==========================================
- Coverage   63.48%   63.48%   -0.01%
==========================================
  Files         360      360
  Lines       22889    22888       -1
  Branches     2547     2547
==========================================
- Hits        14531    14530       -1
  Misses       8343     8343
  Partials       15       15

Impacted Files
Coverage Δ

superset/views/core.py
73.97% <ø> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 763eeca...f0b0d51. Read the comment docs.


Hard to find an existing entry

If you try to add an entry that already exists, we should return the index or UUID to that entry somehow.
Right now, if you try to add an entry we return an error, with no way to find the existing entry.

Fixed with https://github.com/sigstore/rekor/pull/226
prints out entry URL if already exists


Multiple file selection does not work if mode="server" in ajaxfileupload

Hi @rshahLS
I successfully selected multiple files using Mode="Server" and uploaded them:

Please check my sample project: AjaxFileUploadMultipleSelection.zip
If it does not reflect your case, please update it and attach the modified version to this thread.

Tried running your project but I am unable to select multiple files at once using ctrl+select

Hi @rshahLS
The AjaxFileUploadMode setting description is confusing, so I'll explain what really happens when you set it.
If you set it to Auto or Client, AjaxFileUpload will use HTML 5 for file uploading, if the browser supports it. Otherwise, it will use HTML 4.
The key difference here is that input does not have the multiple attribute in HTML 4. So, AjaxControlToolkit will not render it and will not try to process multiple file selection.
If you set AjaxFileUploadMode to Server, AjaxFileUpload will force HTML 4-like processing. That means it will use input without multiple attribute and this attribute will not affect control's logic even if we add it.
So, if you set AjaxFileUploadMode to Server, you are limited to single file selection.
I recommend omit this setting, so the control will use Auto by default.
I also would like to thank you, that you revealed this inconsistency in our documentation.
I created new issue for documentation update, so you can track its progress.
As I mentioned above, this control's behavior is intended, so I marked this issue as by design and closed it.
If you have any info on this, please don't hesitate to post a new comment.


hotfix: Example, ReduxExample and depencies fixes for Android

Probably fixes #3174 (if that's really a bug);
Update dependencies;
Uses babel-preset-react-native instead of metro (due lots of other packages it loads right now);
Fixes both Examples that were broken.

@daviscabral  i am not saying that it is a bug, that is what LOG says.

@daviscabral Is using  babel-preset-react-native will resolve it?

@Abhishekgarg727 there were more changes - not just that. The preset was to solve some incorrect version dependency during the development.

@daviscabral  Is those changes are available in example . i really need to use RNRF in my current project , any boilerplate or example will thankful .

@Abhishekgarg727 ReduxExample uses it.


[Build] Pin rubocop version <= 0.81

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1561/1/console in case of problems.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
14m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
hadolint
0m  0s
hadolint was not available.

+0 :ok:
shelldocs
0m  0s
Shelldocs was not available.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-1 Compile Tests _

+0 :ok:
mvndep
1m 26s
Maven dependency ordering for branch

_ Patch Compile Tests _

+0 :ok:
mvndep
0m  9s
Maven dependency ordering for patch

+1 :green_heart:
shellcheck
0m  0s
There were no new shellcheck issues.

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

_ Other Tests _

+0 :ok:
asflicense
0m  0s
ASF License check generated no output?

17m  6s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1561/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1561

Optional Tests
dupname asflicense hadolint shellcheck shelldocs

uname
Linux b733171d89da 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1561/out/precommit/personality/provided.sh

git revision
branch-1 / 74faa26

Max. process+thread count
36 (vs. ulimit of 10000)

modules
C:  U:

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1561/1/console

versions
git=1.9.1 maven=3.0.5 shellcheck=0.7.0

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

@Reidddddd Jira number is missing in the title :)


Long-clicking a rippled button and then hiding it crashes MDC

This might be an MDC issue but it's serious so I thought I'd log it here too. Long-clicking on a ripple-enabled button/FAB and then immediately hiding it will cause an MDC crash.
Here is an example. Long click on the button (so you get a full ripple and then release the mouse button):
https://codesandbox.io/s/qzwm42p1vw
The code is:
class App extends React.Component {
  state = { show: true };

  render() {
    return (
      <React.Fragment>

Long click on the button below (so you get a full ripple)

        {this.state.show && (
          <Button
            raised
            onClick={() => {
              this.setState({ show: false });
            }}
          >
            Long click me
          </Button>
        )}
      </React.Fragment>
    );
  }
}

The crash occurs in this MDC code (mdc.ripple.js)
removeClass: function removeClass(className) {
  return instance.root_.classList.remove(className);
}

The issue is that root_ is undefined as the button is no longer being rendered.
Any advice is welcome. I will log this on the MDC issues page but if anyone can think of a workaround then I'm all ears.

I updated the code sandbox in your comment. I've been moving some pieces around for a 2.0 alpha and just need to get it working again.
There are many places like this in the MDC api that assume the DOMnode will always be there, I'll hack around it.

Fixed this with 2.0.0. Don't let the major version scare you, read the updated installation guide.


phone data recording website

show qr code on edge-ml that opens a website which has the js library and accesses the phone's sensors

see also https://github.com/riedel/css22-browser


Speed up filters aggregation

Filter request times out on our staging server with half a million of execution records (more precisely, it takes him 220 seconds to complete while default http timeout is 30).
This PR reverts the changes done in 8307cf7 since we don't have compound keys anymore.

I'm a bit confused - we still have compound fields AFAIK.


7.0 refactoring

commit to merge with master branch

This change is

no pull to master from 7.0-refactoring


Guiding users and search engines to latest docs

With the switchover to ReadTheDocs for Numba documentation hosting (https://numba.readthedocs.io/en/stable/), we need to figure out what to do with the historical docs hosted on gh-pages: http://numba.pydata.org/numba-doc/latest/
The latest doc on gh-pages is a symlink to http://numba.pydata.org/numba-doc/0.50.0/, and all past versions of the Numba docs have that same URL pattern.  Due to the age of the project, there is substantial search engine preference for the old docs, which leads users to outdated information.  For posterity, I think it would be good to preserve the old docs at their original URLs, but try to guide users (and search engines) to the new docs.  Since the likelihood of being able to regenerate 6+ years of historical documentation is low, we should plan to make changes to the HTML in place on the gh-pages  branch.  Also, I'm not aware of a way to implement an HTTP redirect for an entire subdirectory in gh-pages.
Following some out-of-band discussion, I can capture the suggestions here:

For all latest/ doc pages, insert a <meta http-equiv="refresh" content="0; URL=https://numba.readthedocs.io/en/stable/[rest of url]"> tag in the header to bounce browsers to the current docs.  Any pages linking to latest/ should be prepared for docs that will change over time.
For all versioned docs (0.50.0/ etc) we should insert a notification banner at the top (like RTD does: https://numba.readthedocs.io/en/0.51.1/) with a link to the RTD stable docs.
For all HTML pages, insert a <link rel="canonical" href="https://numba.readthedocs.io/en/stable/[rest of url]"> tag to the RTD site.

Given the huge number of individual HTML pages, the above will require a script (that someone will have to create).

Note that because latest/ is a symlink currently, step 0 is to remove the link and make latest/ a copy of 0.50.0, but with the meta refresh tags inserted, as described in step 1.

See https://github.com/numba/numba-doc/pull/2


Update npm-scripts to support Windows

This pull-request removes all Unix-specific commands from the NPM-scripts and replace them with cross-platform commands, thereby allowing this project to built on Windows.
I have tested these changes on Windows and they produce a package.zip.
Since I currently do not have access to a Unix-system I can neither verify if the changes also altered the behaviour nor if this is still working on Unix, so this should be tested before merging.
Fixes #6 and fixes #14.

I have deployed this package over to lambda and I get the following error!
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Failed to launch chrome! spawn /tmp/headless_shell ENOENT
I had chrome working when deploying from a unix based system.


How to merge a bunch of Streams into a single Stream of the last changed value from any?

Hi - I can't seem to find a merge function (as in here) for Streams, but maybe I'm thinking about it wrong:
Say I have a bunch of streams which send UIColor events. I'm interested in the latest value coming from any of them, I don't care which Stream it is, only the value sent most recently.
        let streamA: Stream<UIColor> ...
        let streamB: Stream<UIColor> ...
        let streamC: Stream<UIColor> ...
        let streamC: Stream<UIColor> ...
        let streamE: Stream<UIColor> ...

How would can I combine these streams together in a way that would achieve that? I have an inkling that it would involve a flatMap of type StreamFlatMapStrategy.Merge, but the transform block for that is of type: <(UIColor, UIColor, UIColor, UIColor, UIColor) -> StreamType, i.e. all the UIColor values together, where it's unclear which one changed.
Thanks in advance,

I'll need to add this to ReactiveKit, but would be very simple function. Here, you can define it in your project unit I add it here.
public func merge<S: StreamType>(streams: [S]) -> Stream<S.Event> {
  return Stream { observer in
    let compositeDisposable = CompositeDisposable()
    for stream in streams {
      compositeDisposable += stream.observe(on: nil) { event in
        observer(event)
      }
    }
    return compositeDisposable
  }
}

You can then do:
let anyColor = merge([streamA, streamB, streamC...])

Awesome - thanks man, I'll use that.


SC-200 violation

RE: #sc-200-never-store-secrets
Stripe secret key: This lives in the secrets world
https://github.com/Lambda-School-Labs/story-squad-be/wiki/Setup-Guide

 Address SC-200 Violation

Removed from wiki and code in b6eb53d80610df71edd3d2841ee7a3b1212bbf51 & wiki:de692af


Syn.click does not fire focus event

The event focus is not fired when using Syn.click. This should be the default behaviour because a user click will also trigger a focus.
Although the blog says: "A click is the following sequence of events followed by the event’s default actions:

mousedown
focus (Called only if the element was focusable, and mousedown’s default actions were not prevented)
mouseup
click"

this is not true. Notice the JavaScriptMVC documentation states: "Clicks an element by triggering a mousedown, mouseup, and a click event." (http://v3.javascriptmvc.com/docs.html#&who=Syn.prototype.click). This is indeed how it is implemented now, but a focus should be fired too.

Seems like this is still the case 4 months later.

@aristotelos I'm confused by what you are reporting.  What isn't true?  You are calling Syn.click on a focus-able element and there is no focus event?  I'm certain this was working.  What browser are you using? cc @fresheneesz

Here's a test:
<body>
    <input id='b'>
    <input id='c'>
</body>

<script src="http://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js"></script>
<script src="Syn.js"></script>

<script>

    $("#b").keydown(function(event) {
        console.log("keydown b")
    })
    $("#b").keyup(function(event) {
        console.log("keyup b")
    })
    $("#b").change(function(event) {
        console.log("change b")
    })
    $("#b")[0].addEventListener('onfocus', function(event) {
        console.log("FOCUS b")
    })
    $("#b").click(function(event) {
        console.log("click b")
    })

    $("#c")[0].addEventListener('onfocus', function(event) {
        console.log("FOCUS c")
    })
    $("#c").click(function(event) {
        console.log("click c")
    })

    syn.type($("#b")[0], "x", function() {
        syn.click($("#b")[0], function() {
            syn.click($("#c")[0])
        })
    })

</script>

In chrome I get (in the console):
keydown b
keyup b
click b
click c

Oops, lol, change that to addEventListener('focus' - I'm just getting all confused trying to figure out what's working properly and what isn't. NEVERMIND!

syn.type doesn't fire focus tho. That's a problem right? There's no manual way to type in something without focusing on it right? @justinbmeyer

Added tests for a bunch of focus event scenarios, so this should be locked-down now.
Scenarios now include:

click
dblclick
rightClick
tab into (focus)
tab out (blur)
anti-tab into
anti-tab out
tab wrap (last focusable element on the page) into
tab wrap out
anti-tab wrap (first focusable element on the page)
anti-tab wrap out

Confirmed that these are working on Firefox and Chrome. If there are any scenarios that you would like to see added to the list, please feel free to open a new issue or drop me a line in gitter. Or if you have any problems with these, let me know. Thanks!


[Enhancement] - Remove unused util functions

Describe the Current Behavior/Feature:
At this time, there had been many functions that have been migrated out of utils into our custom hooks, React Contexts, and model-helpers. However, the older functions in utils remained. For those functions that had been migrated out, we could remove them from utils.
Rationale:
Cleaning up the codebase.

PR related to issue merged into Development (PR #507). Closing issue.


chore: transpile esm in tests

With this PR, we let @swc/jest always transpile everything in node_modules for the tests since we don't suffer from memory issues any longer, so now we can afford to enable this. I have updated two deps to esm as proof for the reviewers.
Turns out this this is just the first step in the right direction for jest to be able to run tests. While that can work in the tests, it does not mean we will produce a valid package. In fact esbuild produces invalid javascript (currently emits require(<esm>)). So we need to switch the codebase to ESM first.

FYI prettier team does the similar thing https://github.com/prettier/prettier/pull/12217
They convert ESM-only modules to CJS and commit those files under /vendor/ directory

Thanks for sharing!


Fix readme and update SDK

Fixed readme, added logic for ping status and updated SDK changes
Signed-off-by: Aneesh Puttur<EMAIL_ADDRESS>

/test e2e-aws

/test e2e-aws

Make this debug: https://github.com/redhat-cne/cloud-event-proxy/blob/main/cmd/main.go#L234

/lgtm


Repackage io.spine.gradle.* to io.spine.tools.gradle.*

Currently model-compiler and plugin-base use io.spine.gradle as a base package. However, Gradle is just one of the alternative solutions, that we currently use. In future we add support for Bazel and Maven and the essence of the plugins will remain.
In order to emphasize that Gradle is just one of potential options (even if that's the only option for Spine users at the moment) we need to repackage the codebase to io.spine.tools.gradle.

Already solved by on of the recent PRs.


Using hbs with i18n and express

I am trying to use i18n with hbs and express.
I tried to register a i18n helper for the translation, but I don't seem to manage to have both the request (to get the locale of the request) and the text to be translated in the same place.
I have tried two different ways to do that:
the first (have the request but not the text, from the i18n-node project examples):
// binding template helpers to request (Credits to https://github.com/enyo #12)
    app.use(function(req, res, next) {
      res.locals.__ = function() {
        return i18n.__.apply(req, arguments);
      };
      res.locals.__n = function() {
        return i18n.__n.apply(req, arguments);
      };
      // do not forget this, otherwise your app will hang
      next();
    });

The second (have the text but no the request):
hbs.registerHelper '__i', (options)->
    if i18n?
      return i18n.__.apply this, [options.fn this]
    return options.fn this

  hbs.registerHelper '__n', (options)->
    if i18n?
      return i18n.__n.apply this, [options.fn this]
    return options.fn this

What I am currently doing, is defining a middleware that sets the locale of the i18n object on every request, and using the second way for registering the partial:
app.use (req, res, next) ->
    i18n.setLocale i18n.getLocale req
    do next

It works, but I am worried from concurrency issues.
Am I doing it wrong or is this the intended way of doing it?
Is there really a concurrency issue?
Should the hbs module be adjusted so that registering the partials work like other templating engines (the first example)
Thanks.

I am using the helper below and I am having serious concurrency issues. I am not sure what is causing it (the i18n library or handlebars or my implementation). I tried to register this helper with both hbs and express-handlebars but the result is the same. I thought I might have more luck with hbs because it seems to create an instance of handlebars for each request...
app.use(function(req, res, next) {
  hbsInstance.registerHelper('i18n', function() {
    return i18n.__.apply(req, arguments);
  });
  next();
  });

I posted all the details here in case you're interested: https://github.com/mashpie/i18n-node/issues/209
Please let me know if you found a good solution :)


#815 fix docker build

See #815
Signed-off-by: Nigel Jones<EMAIL_ADDRESS>

thanks... will merge. however the build infrastructure is stalled again, so have chased support team and will merge once able to. thanks for testing.


Get rid of SparkMaxVelocityController::SparkMaxVelocityController(int deviceID) constructor

This constructor is not needed. I will get rid of it. This is a note to self.

@ADawesomeguy I am having trouble getting rid of these constructors as the DriveSubsystem uses these constructors. You won't be able to switch to the other constructor until Sam pushes the changes on his computer, but after that, could you please use the better constructor?
Thanks,
Aiden

I'll give it a shot, yep.

ok boomer


CSS Networking-AZFW update StartStop note

adding additional information to the note field of the stop/start command.  Start/Stop has the possibility of changing the Private ip address of the azfw upon reallocation.  There is not a way to guarantee it will get the previous assigned value.

@vhorne
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Auto adjust video quality to maintain fluid video playback

Hi, is there a way we can adjust the video quality to maintain fluid video playback over a given connection?
It would be good if it can do it automatically.
So on slow connections the video bitrate would be lowered until fluid video playback is achieved.

There are pull requests under review that add the SCReAM congestion control algorithm. This algorithm identifies congestion in the network and adjusts the bitrate accordingly.
The signalling and feedback formats are being standardised so it will only be usable between two OpenWebRTC clients currently. Later, when those parts are standardised and Google have implemented their own algorithm in the webrtc.org stack, we should be able to have interoperability with Chrome and Firefox, with very good bitrate adaptation.

A required GStreamer plugin for SCReAM: https://github.com/EricssonResearch/openwebrtc-gst-plugins/pull/43
The OpenWebRTC parts of SCReAM: https://github.com/EricssonResearch/openwebrtc/pull/413

“add the SCReAM congestion control algorithm”
Would this be added to the web server end “channel_server.js” or the client end Bowser app?
Would this also take into account max CPU usage for a client?
Example
Client 1 has a 1920x1080p Webcam.
Client 2 has a low end smart phone or tablet.
Lan connection.
In this example the data rate is not the bottleneck but rather the processing power of client 2, would the video quality be able to downgrade to a level in which client 2 would be able to play the video from client 1?

It would be part of OpenWebRTC (or any other WebRTC stack that cares to implement the algorithm) and it communicates necessary information directly to other clients. Nothing to do with the web server.
There are other mechanisms for clients to specify their capabilities - this is also part of the WebRTC client software stack. I believe it is now possible to signal (via SDP) the maximum supported resolution and frame rate, as well as other things. This should be implemented and exposed to applications I think.

Sorry I am not understanding, is SCReAM done on the client side or server side?
If client 1 is Firefox and client 2 is Chrome and they connect to a private webserver (channel_server.js). If the clients are communicating directly and SCReAM is not done by the web server but by the clients how is this going to be implemented?
I can understand that if both clients are using Bowser than that would work, but what about other web browsers?

The current bitrate adaptation algorithms all work in the clients.
The web server is only used by an application as a known point to which clients can connect in order to send information to each other about how to connect to each other directly and what data each other support for audio, video formats and so on. This is called signalling.
As part of the signalling, each client will express that it supports certain types of feedback or perhaps that it uses some bitrate adaptation algorithm. Then when the media is flowing between the two clients peer to peer (not via the signalling server) they can send metadata or feedback to each other about the data flow of the streams so that they can figure out how to adapt and adjust the encoder bitrate or use other adaptation mechanisms.
SCReAM is one algorithm that works by the receiving client sending feedback about whether packets have been received or not. If not, this is most often due to congestion (buffering due to inability to send the data through) in the network. A strategy then is to reduce the bitrate in order to try to get all of the data through.
The Google congestion control (bitrate adaptation) algorithm, that is the current one being used by Firefox and Chrome, adds a send time header to the sent RTP packets so that the receiver can work out how long the packet took to get through the network. When it sees any delay, it observes that as congestion and sends a feedback message to the sender requesting that it send with a specific lower bitrate that it thinks could work for the channel. It keeps observing and adjusts the bitrate up or down as necessary.
SCReAM will initially only be implemented in OpenWebRTC so initially it will only work between OWR clients. Google has a new algorithm that works similarly to SCReAM and multiple parties including Google and Ericsson are working on standardizing the signalling part and the feedback part so that even if the clients use different algorithms, as long as they support the signaling and feedback, they can be interoperable.

Thanks for very thorough summary. Could you please give an update on progress of the standardization process?

I don't know about the standardization part but that shouldn't require much adjustment once it is ready.
The algorithm, elements and integration should be landing soon with support for OWR <-> OWR calls.

What is the status of SCReAM?

SCReAM is merged. Standardisation of feedback and as SDP signalling ongoing.

Read more here http://www.openwebrtc.org/blog/2015/11/19/your-openwebrtc-calls-are-now-congestion-controlled

Does SCReAM work the same with:
Chrome calling bowser (tried a test call over the internet and the video was laggy, fine on lan).
Firefox calling bowser (not yet tested).
IE calling bowser (not yet tested).
Bowser calling Bowser (not yet tested).


kubeservice logs loads of failures

When automating default/authfe. default/users works fine, so there is something about authfe.
Seems to have worked ok, though...
Logs below:
ts=2016-12-08T14:13:50Z caller=releaser.go:351 instanceID=2 description="Release latest images to default/authfe"
ts=2016-12-08T14:13:50Z caller=releaser.go:351 instanceID=2 description="Service default/authfe image quay.io/weaveworks/logging:master-6c541b4 is already the latest one; skipping."
ts=2016-12-08T14:13:50Z caller=releaser.go:351 instanceID=2 description="Clone the config repo."
Cloning into '/tmp/flux-gitclone307041432/repo'...
Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
ts=2016-12-08T14:13:51Z caller=releaser.go:351 instanceID=2 description="Update 1 images(s) in the resource definition file for default/authfe: authfe (quay.io/weaveworks/authfe:master-d04ca57 -> quay.io/weaveworks/authfe:master-ac75c5d)."
Args: [/usr/local/bin/kubeservice ./billing-api-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/billing
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/billing/billing-api-dep.yaml -> billing/billing-api
Args: [/usr/local/bin/kubeservice ./billing-api-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/billing

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./billing-ui-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/billing
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/billing/billing-ui-dep.yaml -> billing/billing-ui
Args: [/usr/local/bin/kubeservice ./billing-ui-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/billing

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./billing-usage-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/billing
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/billing/billing-usage-dep.yaml -> billing/billing-usage
Args: [/usr/local/bin/kubeservice ./billing-usage-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/billing

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./quay-secret.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/billing

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./simpledb-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/billing
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/billing/simpledb-dep.yaml -> billing/simpledb
Args: [/usr/local/bin/kubeservice ./simpledb-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/billing

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./billing-ns.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./consul-config.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./consul-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex/consul-dep.yaml -> cortex/consul
Args: [/usr/local/bin/kubeservice ./consul-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./dev-grafana-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex/dev-grafana-dep.yaml -> cortex/dev-grafana
Args: [/usr/local/bin/kubeservice ./dev-grafana-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./distributor-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex/distributor-dep.yaml -> cortex/distributor
Args: [/usr/local/bin/kubeservice ./distributor-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./ingester-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex/ingester-dep.yaml -> cortex/ingester
Args: [/usr/local/bin/kubeservice ./ingester-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./memcached-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex/memcached-dep.yaml -> cortex/memcached
Args: [/usr/local/bin/kubeservice ./memcached-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./prod-grafana-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex/prod-grafana-dep.yaml -> cortex/prod-grafana
Args: [/usr/local/bin/kubeservice ./prod-grafana-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./quay-secret.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./ruler-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex/ruler-dep.yaml -> cortex/ruler
Args: [/usr/local/bin/kubeservice ./ruler-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/cortex

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./cortex-ns.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./authfe-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/default/authfe-dep.yaml -> default/authfe
Args: [/usr/local/bin/kubeservice ./authfe-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./bigquery-secret.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./configs-db-exporter-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/default/configs-db-exporter-dep.yaml -> default/configs-db-exporter
Args: [/usr/local/bin/kubeservice ./configs-db-exporter-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./configs-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/default/configs-dep.yaml -> default/configs
Args: [/usr/local/bin/kubeservice ./configs-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./frontend-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/default/frontend-dep.yaml -> default/frontend
Args: [/usr/local/bin/kubeservice ./frontend-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./proxy-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/default/proxy-dep.yaml ->
Args: [/usr/local/bin/kubeservice ./quay-secret.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./tls-secret.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./ui-server-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/default/ui-server-dep.yaml -> default/ui-server
Args: [/usr/local/bin/kubeservice ./ui-server-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./users-db-exporter-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/default/users-db-exporter-dep.yaml -> default/users-db-exporter
Args: [/usr/local/bin/kubeservice ./users-db-exporter-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./users-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/default/users-dep.yaml -> default/users
Args: [/usr/local/bin/kubeservice ./users-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/default

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./api-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy/api-dep.yaml -> deploy/api
Args: [/usr/local/bin/kubeservice ./api-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./deploy-db-exporter-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy/deploy-db-exporter-dep.yaml -> deploy/deploy-db-exporter
Args: [/usr/local/bin/kubeservice ./deploy-db-exporter-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./quay-secret.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./scheduler-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy/scheduler-dep.yaml -> deploy/scheduler
Args: [/usr/local/bin/kubeservice ./scheduler-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./worker-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy/worker-dep.yaml -> deploy/worker
Args: [/usr/local/bin/kubeservice ./worker-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/deploy

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./deploy-ns.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./demo-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/extra
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/extra/demo-dep.yaml -> extra/demo
Args: [/usr/local/bin/kubeservice ./demo-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/extra

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./launch-generator-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/extra
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/extra/launch-generator-dep.yaml -> extra/launch-generator
Args: [/usr/local/bin/kubeservice ./launch-generator-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/extra

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./pr-assigner-config.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/extra

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./pr-assigner-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/extra
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/extra/pr-assigner-dep.yaml -> extra/pr-assigner
Args: [/usr/local/bin/kubeservice ./pr-assigner-secret.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/extra

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./pr-assigner-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/extra

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./quay-secret.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/extra

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./extra-ns.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./fluxd-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/fluxy
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/fluxy/fluxd-dep.yaml -> fluxy/fluxd
Args: [/usr/local/bin/kubeservice ./fluxd-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/fluxy

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./fluxsvc-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/fluxy
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/fluxy/fluxsvc-dep.yaml -> fluxy/fluxsvc
Args: [/usr/local/bin/kubeservice ./fluxsvc-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/fluxy

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./fluxy-ns.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./kube-dns-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system/kube-dns-dep.yaml -> kube-system/kube-dns
Args: [/usr/local/bin/kubeservice ./kube-dns-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./kubernetes-dashboard-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system/kubernetes-dashboard-dep.yaml -> kube-system/kubernetes-dashboard
Args: [/usr/local/bin/kubeservice ./kubernetes-dashboard-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./scope-app-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system/scope-app-dep.yaml -> kube-system/scope
Args: [/usr/local/bin/kubeservice ./scope-probe-ds.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./scope-probe-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./scope-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/kube-system

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./alertmanager-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/alertmanager-dep.yaml -> monitoring/alertmanager
Args: [/usr/local/bin/kubeservice ./alertmanager-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./ansiblediff-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/ansiblediff-dep.yaml -> monitoring/ansiblediff
Args: [/usr/local/bin/kubeservice ./ansiblediff-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./compare-images-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/compare-images-dep.yaml -> monitoring/compare-images
Args: [/usr/local/bin/kubeservice ./compare-images-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./dev-retrieval-config.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./dev-retrieval-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/dev-retrieval-dep.yaml -> monitoring/dev-retrieval
Args: [/usr/local/bin/kubeservice ./dev-retrieval-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./fluentd-loggly-config.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./fluentd-loggly-ds.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./grafana-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/grafana-dep.yaml -> monitoring/grafana
Args: [/usr/local/bin/kubeservice ./grafana-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./kube-api-exporter-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/kube-api-exporter-dep.yaml -> monitoring/kube-api-exporter
Args: [/usr/local/bin/kubeservice ./kube-api-exporter-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./kubediff-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/kubediff-dep.yaml -> monitoring/kubediff
Args: [/usr/local/bin/kubeservice ./kubediff-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./metrics-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/metrics-dep.yaml ->
Args: [/usr/local/bin/kubeservice ./prod-retrieval-config.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./prod-retrieval-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/prod-retrieval-dep.yaml -> monitoring/prod-retrieval
Args: [/usr/local/bin/kubeservice ./prod-retrieval-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./prom-node-exporter-ds.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./prometheus-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/prometheus-dep.yaml -> monitoring/prometheus
Args: [/usr/local/bin/kubeservice ./prometheus-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./quay-secret.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./terradiff-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring/terradiff-dep.yaml -> monitoring/terradiff
Args: [/usr/local/bin/kubeservice ./terradiff-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/monitoring

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./monitoring-ns.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./collection-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/scope/collection-dep.yaml -> scope/collection
Args: [/usr/local/bin/kubeservice ./collection-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./consul-config.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./consul-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/scope/consul-dep.yaml -> scope/consul
Args: [/usr/local/bin/kubeservice ./consul-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./control-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/scope/control-dep.yaml -> scope/control
Args: [/usr/local/bin/kubeservice ./control-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./memcached-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/scope/memcached-dep.yaml -> scope/memcached
Args: [/usr/local/bin/kubeservice ./memcached-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./nats-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/scope/nats-dep.yaml -> scope/nats
Args: [/usr/local/bin/kubeservice ./nats-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./pipe-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/scope/pipe-dep.yaml -> scope/pipe
Args: [/usr/local/bin/kubeservice ./pipe-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./query-dep.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope
kubeservice SUCCESS: /tmp/flux-gitclone307041432/repo/k8s/dev/scope/query-dep.yaml -> scope/query
Args: [/usr/local/bin/kubeservice ./query-svc.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev/scope

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
Args: [/usr/local/bin/kubeservice ./scope-ns.yaml]
Dir: /tmp/flux-gitclone307041432/repo/k8s/dev

Traceback (most recent call last):
  File "/usr/local/bin/kubeservice", line 93, in <module>
    for service in service_for_file(args[0]):
  File "/usr/local/bin/kubeservice", line 63, in service_for_file
    raise Kubeimage("Not a ReplicationController or Deployment")
__main__.Kubeimage: Not a ReplicationController or Deployment

kubeservice FAILED: exit status 1
ts=2016-12-08T14:14:03Z caller=releaser.go:351 instanceID=2 description="Commit and push the config repo."
[master 7c3bc28] Release latest images to default/authfe
 1 file changed, 1 insertion(+), 1 deletion(-)
Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
To git@github.com:weaveworks/service-conf
   d3fa344..7c3bc28  master -> master
ts=2016-12-08T14:14:05Z caller=releaser.go:351 instanceID=2 description="Regrade 1 service(s): default/authfe."

Update: Seems intermittent. I've also seen it on default/configs once or twice.

Maybe it is to do with the order it reads the files?

It looks at every file, every time, so far as I know.
Marking as duplicate of #254.


Ensure that cancelled tasks in queues have promises rejected

Tasks in a TaskQueue may be cancelled via the skip, clear, or shift methods. The promises associated with any cancelled tasks should be settled via a rejection (if they haven't been settled already).
By default, settling is done with a default error, although a custom error may alternatively be passed as an argument.
Fixes #653

I understand the intention and it is very well tested. This is a part of the code I know very little about, but I learned a lot by reading through :+1:


[SWN] Unarmed Attack Damage Miscalculation

Unarmed attacks should add the Combat/Unarmed skill to the damage  (Star Without Number Core Rules p60), currently when selected the Combat/Unarmed skill on the sheet it does not add this value to the damage.

I'll include this in the next release.

This is resolved as of the 0.1.6 update.

Can you set this to Closed?


issue #52 rises again: jtermios.windows.JTermiosImpl under 1.0.0 causes 996 (ERROR_IO_INCOMPLETE) #83

Reason/Solution can be found in my comment to issue #52

I just pushed the changes:
https://github.com/nyholku/purejavacomm/blob/master/src/jtermios/JTermios.java
can you please test that, I don¨t have working Windows setup with serial port atm.
If it works I will make a proper release.
br Kusti

I changed the following files and now it works smooth on Windows with JNA 4.2.2
windows.zip
Kind Regards,
Bernd

Can you just post the diff or preferably do this on github and create pull request ... working with files is a chore...

Hi, my changes are now comitted to the fork bmeierh/purejavacomm. These are my first code changes on GitHub. Please be patient with me and sorry if I did something wrong.
Kind Regards,
Bernd

Hi, thanks for that but you've made quite a lot changes (360 additions and 114 deletions) and a lot of white space changes so it is next to impossible to reliably see what is relevant and what is not.
Please start afresh and make minimal changes that are necessary to make it work and don't allow your IDE to mess up the formatting of the source files. Don't spell out the imports etc, don't delete functions you think are not necessary, just make the changes that are necessary to make the code work so I can see what is the problem with my code.
Thanks.

Hi, now only the minimal changes are committed. I changed my IDE not to organize the imports and not to add the @Override annotations. Nevertheless I think using some static code analysis tool (e.g. FindBugs) will be a good idea to find such errors:
JTermiosImpl.java:717, RV_EXCEPTION_NOT_THROWN, Priorität: Hoch

RV: new RuntimeException(String) not thrown in jtermios.windows.JTermiosImpl.write(int, byte[], int)

This code creates an exception (or error) object, but doesn't do anything with it. For example, something like

    if (x < 0)
      new IllegalArgumentException("x must be nonnegative");

It was probably the intent of the programmer to throw the created exception:

    if (x < 0)
      throw new IllegalArgumentException("x must be nonnegative");

Kind Regards,
Bernd

Sure, static code analysis tools are good. At least up to a point. Like the example you gave, this most likely an error (would have to be a really bizarre 'IllegalArgumentException' constructor if it threw something useful ;)
But I fail to see the connection here. You/we have a clearly a problem and most likely a solution, and we want to apply that, and only that, cleanly to the codebase so that we see what is going on.
If you/we want to do some other bug fixes we should do them as one or more separate issues. Preferably more than one if there are more than one type of issues. Otherwise changes get easily rejected, some people have done big reorganisation of the codebase to please themselves and because part of the changes are not something I agree with they get rejected. Better have small changes to have a better chance of getting them accepted.
For example: I like adding @Override but I do not like having separate import for each and every class. So these changes are lumped together the changes will get rejected.
(As an asside 'import everything individually', I don't agree with that policy because very, very seldom have I seen  in my +15 year Java career a problem with 'import *' where as every time my IDE does 'import somepackage.someclass' in the next few minutes an other import is needed of the same package is needed so it is annoying waste of time).

Hi, I totally agree with you. I see the problem if my commit contains further changes. Sorry!!! With my last commit only the necessary changes in the select(int, FDSet, FDSet, FDSet, TimeVal) method are included. In addition to the OVERLAPPED pointer the following code changes are necessary:
Line 847 -old:
GetOverlappedResult(port.m_Comm, port.m_SelOVL, port.m_SelN, false);
Line 847 -new:
if (!GetOverlappedResult(port.m_Comm, port.m_SelOVL, port.m_SelN, false)) {
   int lastError = GetLastError();
   if (lastError != ERROR_IO_INCOMPLETE) {
      port.fail();
   }
}

The Windows documentation says, that in case of a negative result, the GetLastError method always has to be called.
Line 876 -old:
if (GetLastError() != ERROR_IO_PENDING)
   port.fail()

Line 876 -new:
int lastError = GetLastError();
// Under Windows sometimes the error code 87 (ERROR_INVALID_PARAMETER) is returned.
// I have not investigated why, but it is also a valid reply
if (lastError != ERROR_IO_PENDING && lastError != 87) {
  port.fail();
}

Hi, will you add this changes?
Kind Regards,
Bernd

Hi, I've added the changes but:

I have no working Windows setup with a serial port so I cannot test this
Even when I did, I never saw this error so could not test it anyway
Not sure I changed the correct lines as the line numbers did not match mine,
your code was probably not virgin from github when you made the changes.

So please test, I will not make a release before I hear back from you.
For the future, please 'diff' against the github code to produce patches or,
preferably, clone the repo and create a pull request, that is the github
workflow way of doing things.
And many thanks for contributing.

Hi, Thank you for the changes! I did some testing (with JNA 4.2.2 and your new code) and had no problems anymore. In the future I will act on your advice. But as already mentioned I'm an absolut github novice.
I don't want to be pushy but published releases (e.g. Maven Central) would be great (refer to issue#82). What is your intention?
Kind Regards,
Bernd

Hi, thanks for the report. I will try to do a release within a week or two.
As to maven central, I looked at the process and while pretty straightforward on the face of it my experience tells me it will take a good afternoon and then some iteration to get it to work and can't prioritise that time usage atm. So yes, but not now.


roar-rails with swagger-ui and Content-Type application/x-www-form-urlencoded

Hi,
I' having problems getting swagger-ui running with roar-rails. I'm trying to use AJAX to talk to the API. I'm using the following setup:
roar-rails 1.0.1
swagger-ui_rails 0.1.7
The problem is that this version of the swagger UI is using AJAX together with Content-Type application/x-www-form-urlencoded to talk to the API endpoints POST/PUT. This is leading to an error:
undefined method from_url_encoded_form
I know that it supports from_json or from_xml. Is there a way to enable support for this content type or should I always use JSON? Any ideas?
Thanks!

In your controller, you can override #compute_parsing_method.
class ApplicationController < ..
  def compute_parsing_method(format)
    "from_json"
  end

Perfect, thanks!

Anytime! :stuck_out_tongue_winking_eye: Please close the ticket if it works! :beers: