Rewrite and restructure

Rewrite basically from scratch with simpler implementation and organization, improved types, and tests.  Switch to yarn.
Removed all examples except one, and planning to reinstate them in another PR.

Hello @briancavalier,  I'm learning about Yampa and AFRP in general and found this project to be a great example, actually the only good example in JS. I was wondering if you're planning to finish this PR (or perhaps you've abandoned this in favor of some other project). I just couldn't decide which branch to inspect. Thanks for the great work!


[Event Request] Codeunit 11000011 Check SEPA Pain 008.001.02 - OnBeforeOnRun

Please add a new publisher event to the function OnRun as follows:
OnRun(VAR Rec : Record "Proposal Line")
//>> Start New Publisher Call
OnBeforeOnRun(Rec);
//<< End New Publisher Call

IF "Account Type" = "Account Type"::Customer THEN BEGIN
  TransactionMode.GET(TransactionMode."Account Type"::Customer,"Transaction Mode");
.
.

New Publisher Event:
LOCAL [IntegrationEvent] OnBeforeOnRun(VAR ProposalLine : Record "Proposal Line")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


One byte fix to fix OSS Fuzz AFL support

"x$LIB_FUZZING_ENGINE" is not the correct filename to test for - remove the x!

(@coreyfarrell this will fix the build failure in https://github.com/google/oss-fuzz/pull/2622)

Coverage increased (+0.08%) to 95.507% when pulling 6e2659998037e8ed31a4ec4437ae34c09bb567fc on cmeister2:cmeister2/fixossafl into 3bfa3f1946a8afe0d9ad3082ebfe6a8dd3346814 on akheron:master.


Adding logo assets

Adding here the finalized logo. This is almost identical to the one posted on Slack, except:

extremely small adjustment to the arrow head, to make it perfectly centered on and orthogonal to the stroke

SVG was optimized to remove redundant elements (e.g. gradients). Main logo is now only 10Kb. PNGs exported at 800dpi.

Assets

White paper

README

An admin is needed to change the project icon to the OpenPBR glyph.

Some alternative layouts for the title and logo placement.
I like the second version the most, with the logo+text used for the title, and the subtitle giving the detailed "OpenPBR Surface specification" and the version/date.
**OpenPBR Surface**
*Specification v1.1, 2024-06-28*.

<bigger>OpenPBR Surface specification v1.1, 2024-06-28</bigger>

In aea298251776e719e9da6fd0801cf79cec59a70c added simplified forms of the logo suitable for icons, as requested/discussed on Slack.

In 54474ff8268725f84b852e027c29e7b755326beb updated the spec to use the logo (glyph next to text form) for the title, with the subtitle giving the full "OpenPBR Surface" (+version/date) wording.

Added proposed 128x128 favicon in 95cc4baf477684eeedcf3f5657078b861b58271e

looking good!


Updated meson build files to ease API version change.

meson build files have been changed to include a variable with graphene string to be used instead of hard coded strings.
Fixes #101
Proposed changes:

Changed the version number handling for generated files and directories in the meson build files.

Benchmark results:

Before: ...
After: ...

Test suite changes:

...

Thanks for the patch, it looks good and simplifies a bunch of redundant bits.

I'm very sorry about the update regarding your comments. I tried to update them using the edit option, but I haven't found any way to edit multiple files at the same time, so I had to edit them one by one. Also, the web editor search option doesn't work very well here, and I missed some of the variables when updating one of the files :(.
I expect the files to be properly updated now.

@inigomartinez No worries; I've squashed the commits on merge, it's perfectly fine.
Thanks again for your contribution!


The balance is being set to zero.

Unable to replicate this issue.Verified on staging app v2.0.5(382)

Have requested Brad to confirm if the issue still persists.


how to get the cover

$ ./youtubedr.exe info https://www.youtube.com/watch?v=gHM3LOZM93g
Title:       Stay [8 Bit Tribute to The Kid LAROI & Justin Bieber] - 8 Bit Universe
Author:      8 Bit Universe
Duration:    2m18s

+------+-----+---------+---------+----------+-----------+---------+--------------------------------------------+
| ITAG | FPS |  VIDEO  |  AUDIO  |  AUDIO   | SIZE [MB] | BITRATE |                  MIMETYPE                  |
|      |     | QUALITY | QUALITY | CHANNELS |           |         |                                            |
+------+-----+---------+---------+----------+-----------+---------+--------------------------------------------+
|  251 |   0 |         | medium  |        2 |       2.6 |  159778 | audio/webm; codecs="opus"                  |
|  140 |   0 |         | medium  |        2 |       2.1 |  129510 | audio/mp4; codecs="mp4a.40.2"              |
|  137 |   6 | 1080p   |         |        0 |       1.8 |  109828 | video/mp4; codecs="avc1.640028"            |
|   18 |   6 | 360p    | low     |        2 |       2.0 |  123173 | video/mp4; codecs="avc1.42001E, mp4a.40.2" |
|  250 |   0 |         | low     |        2 |       1.4 |   82938 | audio/webm; codecs="opus"                  |
|  136 |   6 | 720p    |         |        0 |       1.2 |   74378 | video/mp4; codecs="avc1.64001f"            |
|  248 |   6 | 1080p   |         |        0 |       1.3 |   77823 | video/webm; codecs="vp9"                   |
|  249 |   0 |         | low     |        2 |       1.1 |   64024 | audio/webm; codecs="opus"                  |
|  247 |   6 | 720p    |         |        0 |       1.0 |   58315 | video/webm; codecs="vp9"                   |
|  135 |   6 | 480p    |         |        0 |       0.9 |   53036 | video/mp4; codecs="avc1.4d4016"            |
|  134 |   6 | 360p    |         |        0 |       0.7 |   40892 | video/mp4; codecs="avc1.4d4016"            |
|  244 |   6 | 480p    |         |        0 |       0.6 |   39123 | video/webm; codecs="vp9"                   |
|  278 |   6 | 144p    |         |        0 |       0.5 |   28753 | video/webm; codecs="vp9"                   |
|  243 |   6 | 360p    |         |        0 |       0.5 |   30176 | video/webm; codecs="vp9"                   |
|  133 |   6 | 240p    |         |        0 |       0.5 |   28318 | video/mp4; codecs="avc1.4d4015"            |
|  242 |   6 | 240p    |         |        0 |       0.3 |   20441 | video/webm; codecs="vp9"                   |
|  160 |   6 | 144p    |         |        0 |       0.3 |   18016 | video/mp4; codecs="avc1.4d400b"            |
+------+-----+---------+---------+----------+-----------+---------+--------------------------------------------+

If I use the youtbe-dl could do this

Do you need the video too? or just the image?

could add an option to enable the  pic
---Original---
From: @.>
Date: Thu, May 5, 2022 08:52 AM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [kkdai/youtube] how to get the cover (Issue #245)
Do you need the video too? or just the image?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Add boilerplate for screen switching

Everywhere I've found tutorials, this is the way they do it. I figured it would be nice to have it built in.

Realized workarounds


h3: refactor Config API and remove priority placeholder setting

HTTP/3 draft-23 removed prioritization. This change
removes the "num placeholders" settings which
means that we slightly modify the public API for HTTP/3
config: h3::Config::new() and quiche_h3_config_new()
by removing that parameter.
Placeholders were a server-advertised feature, so this
change has the nice effect of making the API more sane
for clients.

LGTM however only concern I have is API change. This will break existing applications which use libquiche (I don't know how many in the field). Of course QUIC/H3 draft is still evolving so expecting a few more change like this, I think it's good time to think about how we keep backward compatibility of APIs or making APIs more extensible with such changes.

@junhochoi I agree with your concerns.
Since we are making a breaking change, I decided to go the whole hog and make the creation of the h3::Config option more extensible by adding functions to change specific properties. This gives us better granularity over changes to the properties available today, and sets a framework for future additions.

This looks great, though we can probably avoid calling set_max_header_list_size() explicitly in most places (benchmarks, examples, tests, ...). We were setting an explicit size before because we had to, but we don't need to anymore.

Good point!

LGTM. I think this API style is better.

Thanks to @LPardue's PR, curl is ready for the API change.


Fixed typos and features

Good for all the features, thanks a lot!
However I'm not gonna add an auto gold to the bot and never will. The goal of the bot is to make high level game accessible to every player even without paying the subscription to a bot. The features are thought to be helpful to reduce the boring tasks of the game and allow to more focus on what is really funny that is strategy, attacks and conquests.
Adding a way to obtain gold, will result in people starting to abuse it and this will damage the gold system and the game itself.
If you want the merge to be done, please remove that feature

Thanks all good, I did not realize that I published a test, removed now.

Thank you!


Fix threads race condition in handling of job completion

A race condition was possible where two (or more) threads would be executing JobCompletionService::handleJobCompletion.
The threads would disturb eachother by deleting files and archiving the job twice.
This is possible if JobMonitor, which emits JobFinishedEvent runs (and emits) twice before getting cancelled.

Coverage decreased (-0.05%) to 92.627% when pulling 13c63cb8134e62cc9ae0dc18ebd49c4861a290f7 on mprimi:GENIE-537-post-execution-errors into c2a74f251d723819b07f2fa3c0ceeb5f1d597983 on Netflix:master.


Availability at MELPA stable

Is it possible to make this package available at MELPA stable? Thanks.

Please, Can you add this to MELPA stable repository?

I might be mistaken, but I'm pretty sure packages must be licensed under the GPL in order to get added to elpa. As this package is currently licensed under the MIT license, this may not be possible. It's a fairly large challenge to relicense a package because you need the permission of all contributors.

This should be resolved as soon as the next stable build happens.

There's now a stable package. I'll try to keep it updated, but feel free to ping me if it needs to be synced up.


Thank you!

No issue, i'll close it down once you see it, just wanted to say thank you for forking the old library and resurrecting it! :)

Spoke too soon haha, when testing on iOS and trying to run pod update i get the follow error
[!] No podspec found for `wavenet` in `.symlinks/plugins/wavenet/ios`

Any idea how i can resolve?

Hi, can you try again.
wavenet: ^2.0.4

Perfect thanks! Resolved :)


Return Values

It'd be good to also specify that dotnet test will return 0 if all tests were run successful and 1 if any test failed.

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

ID: 61ca4064-7481-a263-60fc-c70127f2ad16
Version Independent ID: 2878af44-8208-7bd8-46d4-3acda3e82ce0
Content: dotnet test command - .NET Core CLI
Content Source: docs/core/tools/dotnet-test.md
Product: dotnet-core
GitHub Login: @mairaw
Microsoft Alias: mairaw

Thanks for the feedback @zihotki
That would be a useful change. We've added it to our backlog. If you'd like, you can submit a PR to update this as well.


IntEnum as array index? No implementation of getitem found for signature

Reporting a bug

[X] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[X] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.
advent_2021_15.zip

I have an observably bad Python program that I tried to apply Numba to. Unfortunately, JIT fails with some arcane reason that could be related to trying to use an IntEnum as an array index.
Traceback (most recent call last):
  File "advent_2021_15.py", line 194, in <module>
    (width + height) * pages - 2, # heuristic
  File "C:\Users\Haley\AppData\Roaming\Python\Python37\site-packages\numba\core\dispatcher.py", line 482, in _compile_for_args
    error_rewrite(e, 'typing')
  File "C:\Users\Haley\AppData\Roaming\Python\Python37\site-packages\numba\core\dispatcher.py", line 423, in error_rewrite
    raise e.with_traceback(None)
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<built-in function getitem>) found for signature:

 >>> getitem(reflected list(int32)<iv=None>, IntEnum<int32>(Route))

There are 22 candidate implementations:
      - Of which 22 did not match due to:
      Overload of function 'getitem': File: <numerous>: Line N/A.
        With argument(s): '(reflected list(int32)<iv=None>, IntEnum<int32>(Route))':
       No match.

During: typing of intrinsic-call at advent_2021_15.py (170)
During: typing of static-get-item at advent_2021_15.py (170)

File "advent_2021_15.py", line 170:
def push_route(route):
    <source elided>
 for i, r in enumerate(frontier):
  if r[Route.X] == route[Route.X] and r[Route.Y] == route[Route.Y]:
  ^

I've begrudgingly removed the enum and I get this error:
The use of a reflected list(reflected list(int32)<iv=None>)<iv=None> type, assigned to variable 'frontier' in globals, is not supported as globals are considered compile-time constants and there is no known way to compile a reflected list(reflected list(int32)<iv=None>)<iv=None> type as a constant.

For the original reported issue, this can be reproduced with:
from numba import njit
from enum import IntEnum

@njit
def f(x, i):
    return x[i]

class Channel(IntEnum):
    RED = 0
    GREEN = 1
    BLUE = 2
    ALPHA = 3

f([1, 2, 3, 4], Channel.RED)

which produces:
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<built-in function getitem>) found for signature:

 >>> getitem(reflected list(int64)<iv=None>, IntEnum<int64>(Channel))

There are 22 candidate implementations:
  - Of which 22 did not match due to:
  Overload of function 'getitem': File: <numerous>: Line N/A.
    With argument(s): '(reflected list(int64)<iv=None>, IntEnum<int64>(Channel))':
   No match.

During: typing of intrinsic-call at /home/gmarkall/numbadev/issues/7662/repro.py (7)

File "repro.py", line 7:
def f(x, i):
    return x[i]
    ^

I'll mark this as a bug rather than a feature request, as it does seem that IntEnum members ought to be supported as list indices. A similar problem exists for typed lists:
from numba import njit
from numba.typed import List
from enum import IntEnum

@njit
def f(x, i):
    return x[i]

class Channel(IntEnum):
    RED = 0
    GREEN = 1
    BLUE = 2
    ALPHA = 3

f(List([1, 2, 3, 4]), Channel.RED)

giving:
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
list indices must be integers or slices
During: typing of intrinsic-call at /home/gmarkall/numbadev/issues/7662/typed.py (8)

File "typed.py", line 8:
def f(x, i):
    return x[i]
    ^

I've begrudgingly removed the enum and I get this error:

Can you try using a typed list and see if you get the same result? If you still have a problem, could you open a new issue with a small executable sample of code that reproduces the error please? (reflected lists are deprecated and the use of Typed lists is the preferred way to go in the future).


Update README.md

would remove the sections that have nothing in them.

I think this is an old PR and will close this now


Add cesil

Language name
Cesil (Computer Education in Schools Instruction Language)
URL of example repository
https://github.com/danik4985/cesilc
See tests/ directory
URL of syntax highlighting grammar
https://github.com/danik4985/cesil-vscode/blob/main/syntaxes/cesil.tmLanguage.json
Most popular extensions
.ces

Detected language
None

Note
See https://en.wikipedia.org/wiki/CESIL if you never heard of cesil.

Language name
Cesil (Computer Education in Schools Instruction Language)
URL of example repository
https://github.com/danik4985/cesilc See tests/ directory
URL of syntax highlighting grammar
https://github.com/danik4985/cesil-vscode/blob/main/syntaxes/cesil.tmLanguage.json
Most popular extensions
.ces
Detected language
None
Note
See https://en.wikipedia.org/wiki/CESIL if you never heard of cesil.

please do it


BLC test config and remove SIMDEM_CWD

@rgardler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Is this project still active? Unable to open dongle.

I'm encountering an error, Just getting a generic "Unable to open dongle device", I am using a supported dongle, its quite literally the same Cycplus dongle of that I'm positive.
I don't have any logs or anything to go off of.

I'm using the one from Zadig?? im uncertain as to whats going on

Wait hang on, realized i was using WinUSB and not libusb lemme swap it and see

Okay yeah, was using WinUSB and not libusb, didn't realize that you could change whichever one was installed


gplates: 2.4 -> 2.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/GPlates/GPlates/releases.
meta.description for gplates is: Desktop software for the interactive visualisation of plate-tectonics
meta.homepage for gplates is: https://www.gplates.org
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.5 with grep in /nix/store/3k93xp6ycd91l6rp9g1hz3db68zyvd4d-gplates-2.5
found 2.5 in filename of file in /nix/store/3k93xp6ycd91l6rp9g1hz3db68zyvd4d-gplates-2.5

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
gplates

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/2ff5b02ffe7a4e5fec26cae59d3710f3fd3ade80#gplates

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3k93xp6ycd91l6rp9g1hz3db68zyvd4d-gplates-2.5
ls -la /nix/store/3k93xp6ycd91l6rp9g1hz3db68zyvd4d-gplates-2.5/bin

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

1 package built:

gplates

Maintainer pings

Result of nixpkgs-review pr 304273 run on x86_64-linux 1

1 package built:

gplates


Memory leak issue on iOS for Image

The app crashes while using Image.network() & Image.file()
Here is the bit of code that causes the memory leak:
Scaffold(
backgroundColor: Colors.black87,
body: Center(
child:  Image.network(
url,
fit: BoxFit.cover,
cacheWidth: 600,
)
),
);

@AatishGeek
You are on older version of stable. Current version is 2.0.3. Please upgrade to latest and try again to see if issue persists or not.
Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


issue-791: include server payload on StatusLocked

We were seeing errors:
{"l":"fatal","t":"2020-09-17T02:37:29.858Z","m":"Unable to retrieve enforcer configuration","mPid":13842,"error":"unable to retrieve data path certificate: Cannot communicate: The api has been locked down by the server."}
But losing the server reason, i.e. the payload message that indicated why the server returned http.StatusLocked
This patch attempts to save the server payload at the time of the error.
Caveat:
This patch only concerns itself with http.StatusLocked in the RETRY loop.  The other errors in that loop are less likely to have server payloads, but this patch could be generalized to cover all errors and attempt to extract  any payload it can.

/build

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "18567e603d099c0d9557dd6dfccf38830a3d5ade",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2874",
    "commit-sha": "dff23bf6f82ce6e89ccfc840a951373aba1d9db1",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "6ee056896898072242659f4871102ab50b1fa02a",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "906bc615fc3bbff1858f284695bb2bfe61feda8e",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "8c470dfbbc44f151d745c21931911df2735ea891",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "8c470dfbbc44f151d745c21931911df2735ea891",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2874",
    "commit-sha": "d5853f5f94f0378b80350fca4c2b2c47d43a14db",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "18567e603d099c0d9557dd6dfccf38830a3d5ade",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "ae642d45cfdcc76ddf1f453419fbcdc587cf6434",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "f040193c66a8bd1d111180f83a73c9dc07198818",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "ae642d45cfdcc76ddf1f453419fbcdc587cf6434",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "18567e603d099c0d9557dd6dfccf38830a3d5ade",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "ee14ec15e34846ac0711dd5f6ade921f42ffc1f5",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "8c470dfbbc44f151d745c21931911df2735ea891",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2874",
    "commit-sha": "d5853f5f94f0378b80350fca4c2b2c47d43a14db",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "ee14ec15e34846ac0711dd5f6ade921f42ffc1f5",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "8c470dfbbc44f151d745c21931911df2735ea891",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2874",
    "commit-sha": "d5853f5f94f0378b80350fca4c2b2c47d43a14db",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "03654c0348ff7c0020e1b6dcb1132f71b92a5ecc",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "18567e603d099c0d9557dd6dfccf38830a3d5ade",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "03654c0348ff7c0020e1b6dcb1132f71b92a5ecc",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "ee14ec15e34846ac0711dd5f6ade921f42ffc1f5",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "8c470dfbbc44f151d745c21931911df2735ea891",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2874",
    "commit-sha": "d5853f5f94f0378b80350fca4c2b2c47d43a14db",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "ee14ec15e34846ac0711dd5f6ade921f42ffc1f5",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "8c470dfbbc44f151d745c21931911df2735ea891",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2874",
    "commit-sha": "d5853f5f94f0378b80350fca4c2b2c47d43a14db",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "6fd24a7428d3cef8f8629ba3eaed6ae32282fcf8",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "18cc3ddf5371e625ba225b33921a19624f75d31b",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "f08c3b93d96beb65e3d2fe9a550256e0863978f4",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "8c470dfbbc44f151d745c21931911df2735ea891",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "20848d89a7bc21d1263118a3d8c6ee75c7576608",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "e08fc7efb0dabf994bb38b0d3b1d4b90a26ea1e5",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "f08c3b93d96beb65e3d2fe9a550256e0863978f4",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "bd31ee829ead9c8f85f679af392c57830efd721a",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "20848d89a7bc21d1263118a3d8c6ee75c7576608",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "50ebe397daccedbf2fdab197eacfe7bb4f7a5d51",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "1e78e2e0372edb26b454dea6a3f3528d9ad1d2ad",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "f08c3b93d96beb65e3d2fe9a550256e0863978f4",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "bd31ee829ead9c8f85f679af392c57830efd721a",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "068430439659d75a744c0c0a02986e3a30735c3b",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "f08c3b93d96beb65e3d2fe9a550256e0863978f4",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "a82f3b11418bdfabfe02d34017c92e701e34c83b",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "50ebe397daccedbf2fdab197eacfe7bb4f7a5d51",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "6c79e524565a6dd9b6b16b71fef5551d2dfd8f25",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "61734553956251838de32a641b733a45ac7f3770",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "a82f3b11418bdfabfe02d34017c92e701e34c83b",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "50ebe397daccedbf2fdab197eacfe7bb4f7a5d51",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "61734553956251838de32a641b733a45ac7f3770",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "a82f3b11418bdfabfe02d34017c92e701e34c83b",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "50ebe397daccedbf2fdab197eacfe7bb4f7a5d51",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "7b57ebc4c0dabf63a4e850b5975c095e97c4d683",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "7b57ebc4c0dabf63a4e850b5975c095e97c4d683",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "61734553956251838de32a641b733a45ac7f3770",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "a82f3b11418bdfabfe02d34017c92e701e34c83b",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "50ebe397daccedbf2fdab197eacfe7bb4f7a5d51",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "50ebe397daccedbf2fdab197eacfe7bb4f7a5d51",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "backend",
    "pr-id": "868",
    "commit-sha": "8dc617b186d922bb5ddea4737eb2e7d5a08fdb75",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "7b57ebc4c0dabf63a4e850b5975c095e97c4d683",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "61734553956251838de32a641b733a45ac7f3770",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "a82f3b11418bdfabfe02d34017c92e701e34c83b",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "0012560d280ab5eb065911f1adcfb0fd86edfb0f",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "61734553956251838de32a641b733a45ac7f3770",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "a82f3b11418bdfabfe02d34017c92e701e34c83b",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "50ebe397daccedbf2fdab197eacfe7bb4f7a5d51",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "backend",
    "pr-id": "868",
    "commit-sha": "8dc617b186d922bb5ddea4737eb2e7d5a08fdb75",
    "pipeline": "master"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "issue-791",
    "component": "apotests-lib",
    "pr-id": "373",
    "commit-sha": "61734553956251838de32a641b733a45ac7f3770",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "integrations-lib",
    "pr-id": "191",
    "commit-sha": "a82f3b11418bdfabfe02d34017c92e701e34c83b",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apotests",
    "pr-id": "2881",
    "commit-sha": "50ebe397daccedbf2fdab197eacfe7bb4f7a5d51",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "backend",
    "pr-id": "868",
    "commit-sha": "8dc617b186d922bb5ddea4737eb2e7d5a08fdb75",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "enforcerd",
    "pr-id": "2001",
    "commit-sha": "0012560d280ab5eb065911f1adcfb0fd86edfb0f",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "manipulate",
    "pr-id": "128",
    "commit-sha": "fbf0322cf3602aeb2a0152b4f6b17436fd5574c3",
    "pipeline": "master"
  },
  {
    "project": "issue-791",
    "component": "apoctl",
    "pr-id": "279",
    "commit-sha": "3663ac7073eb92f822494c5980ef069f820c9eab",
    "pipeline": "master"
  }
]

Closing. This was only needed for tracing a backend api locked error received in enforcerd.
a more complete and better fix is implemented in https://github.com/aporeto-inc/backend/pull/869


cli creates service with vip mode by default, while api created service without endpoint mode by default

Description
When we use docker service create ubuntu:14.04 sleep 10000 to create a service, the service created has a endpoint mode of vip by default, even though we did not specify it. I think this is not reasonable.
When we call  POST /services/create api with the following request body (without endpintSpec in request body), no endpoint mode will created in the created service:
{
        "Mode": {
            "Replicated": {
                "Replicas": 1
            }
        },
        "TaskTemplate": {
            "RestartPolicy": {
                "Window": 0,
                "MaxAttempts": 0
            },
            "Placement": {
                "Constraints": []
            },
            "ContainerSpec": {
                "Command": [],
                "User": "",
                "Image": "ubuntu:14.04",
                "Args": [
                    "sleep",
                    "100000"
                ],
                "Dir": ""
            }
        }
    }

Incompatibility happens, since endpointSpec is optional in service, I think we should change that style in docker cli.
Steps to reproduce the issue:

create a service via docker service create ubuntu:14.04 sleep 10000,
create a service with request body

{
        "Mode": {
            "Replicated": {
                "Replicas": 1
            }
        },
        "TaskTemplate": {
            "RestartPolicy": {
                "Window": 0,
                "MaxAttempts": 0
            },
            "Placement": {
                "Constraints": []
            },
            "ContainerSpec": {
                "Command": [],
                "User": "",
                "Image": "ubuntu:14.04",
                "Args": [
                    "sleep",
                    "100000"
                ],
                "Dir": ""
            }
        }
    }

Describe the results you received:
service created in step 1 has endpoint mode of vip
service created in step 1 has no endpoint mode
Describe the results you expected:
both services created in step 1 and step 2 have no endpoint mode
Output of docker version:
root@ubuntu:~# docker version
Client:
 Version:      1.12.1
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   23cf638
 Built:        Thu Aug 18 05:22:43 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.1
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   23cf638
 Built:        Thu Aug 18 05:22:43 2016
 OS/Arch:      linux/amd64

Output of docker info:
root@ubuntu:~# docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 61
Server Version: 1.12.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 449
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host null overlay bridge
Swarm: active
 NodeID: bwhn25sl7f3ajxqn0m8dpv825
 Is Manager: true
 ClusterID: b680epf619kiccm7lswsmd1ux
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
Runtimes: runc
Default Runtime: runc
Security Options: apparmor
Kernel Version: 3.19.0-25-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.954 GiB
Name: ubuntu
ID: HRBI:EV6M:3NAC:CXZ3:BDS7:UOKL:PD6Y:ZCK4:V3PF:V7MR:CU2Y:3LGG
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 31
 Goroutines: 113
 System Time: 2016-09-26T11:05:03.096768981+08:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):

/cc @vieux @dnephin @mrjana

@aluzzardi what is the correct behaviour? should both default to VIP?

@vieux Can you take a look at this one? It seems there might be a problem with the API translation

ping

@allencloud What's the correct behavior?
If the CLI didn't set the endpoint to VIP then you would need to set it every time you create a service which can be bothersome - why shouldn't there be a default?

@aluzzardi

If the CLI didn't set the endpoint to VIP then you would need to set it every time you create a service which can be bothersome - why shouldn't there be a default?
Yeah, I think what cli did via a default is definitely good for users. My point is that if we could make engine's api a default to vip. Then if a user does not use cli but pure api call, and he does not take an endpoint mode, api will add a vip default mode for it.
Then api and cli are consistent for using. Just my point.

If I understand correctly, even though you are not passing --endpoint-mode to the CLI, the CLI is still creating an EndpointSpec and sending it to the API. Correct?
@allencloud The behavior between API/CLI is consistent - if you don't pass an endpoint spec it will default to VIP. Therefore, passing mode=vip or passing nothing results in the same behavior.
I do agree that that perhaps the CLI should not send an EndpointSpec if --endpoint-mode was not set in the CLI - @dnephin thoughts?

The behavior between API/CLI is consistent - if you don't pass an endpoint spec it will default to VIP. Therefore, passing mode=vip or passing nothing results in the same behavior.
I am afraid my test does not show the same result. Below is my test:

create a service with no endpoint spec in body:

REQUEST URL: POST <IP_ADDRESS>:2375/services/create
REQUEST BODY:
{
    "TaskTemplate": {
    	"ContainerSpec": {
			"Image": "ubuntu:14.04",
			"Args": [
				"sleep",
				"100000"
			],
			"Dir": ""
		}
	}
}

Here is the response:
{
  "ID": "3j9pwc7qru9g07qpvhu2gpcon"
}

inspect this service to check whether it has a resolution mode.

REQUEST: GET <IP_ADDRESS>:2375/services/3j9pwc7qru9g07qpvhu2gpcon

Response:
RESPONSE:
{
  "ID": "3j9pwc7qru9g07qpvhu2gpcon",
  "Version": {
    "Index": 34
  },
  "CreatedAt": "2016-11-02T07:28:27.659976711Z",
  "UpdatedAt": "2016-11-02T07:28:27.659976711Z",
  "Spec": {
    "Name": "admiring_panini",
    "TaskTemplate": {
      "ContainerSpec": {
        "Image": "ubuntu:14.04",
        "Args": [
          "sleep",
          "100000"
        ]
      }
    },
    "Mode": {
      "Replicated": {
        "Replicas": 1
      }
    }
  },
  "Endpoint": {
    "Spec": {}
  },
  "UpdateStatus": {
    "StartedAt": "0001-01-01T00:00:00Z",
    "CompletedAt": "0001-01-01T00:00:00Z"
  }
}

IIRC, docker service inspect currently shows the spec as is provided when creating the service, but does not show the defaults for options that were not specified.
There's a proposal to merge the defaults when inspecting a service, so that the active configuration is visible in inspect

I do agree that that perhaps the CLI should not send an EndpointSpec if --endpoint-mode was not set in the CLI

EndpointSpec includes ports, so setting any port would require a value for Mode

ping @aluzzardi what's the status on this one?


:: brack  autocomplete prosses

the sign ' : ' break the autocomplete prosses
for example
Closure Closure::bind

have run into this issue too while trying out the snippets for language-laravel. is there any way to fix this?
after we type ':' the autocomplete think that we're trying to type a completely new snippets and didn't take into consideration about what was written before the ':' character

Can you please post the full snippet text for a snippet that exhibits this behavior?

of course!
it's part of the atom package here https://atom.io/packages/laravel
when i try to use the snippet for Route::get snippet, i need to type ro:g for it to work.
but if autocomplete-snippets and autocomplete-plus is on, it consider the g as a new autocomplete keyword / search

Yes, it is an autocomplete-plus bug. https://github.com/Cronos87/atom-laravel/blob/cebcc3174c5d1d8834eebc674708f270749a0c53/snippets/laravel.cson#L24-L27 seems to capture a test case that we can use.

Your Route::get snippet is here: https://github.com/Cronos87/atom-laravel/blob/cebcc3174c5d1d8834eebc674708f270749a0c53/snippets/laravel.cson#L451-L454. I'll use that.

hi, i've found out the modification needed to allow autocomplete-plus to recognize snippets with colon characters.
it's these
https://github.com/atom-community/autocomplete-plus/blob/master/lib/autocomplete-manager.coffee#L34-L35
https://github.com/atom-community/autocomplete-plus/blob/master/lib/fuzzy-provider.coffee#L11
should i do a pull request? since this modifies the fuzzy provider which, according to the wiki, is already deprecated

@benogle is it valid for a snippet's groups to be nested like this: Route::input(${1:'${2:name}'})$3 (i.e. group 2 is nested inside of 1). I have replicated a failure in our autocomplete-snippet parsing if the groups are nested. The double :: doesn't cause any issues.


Project Status History Log drawer

Monday Task

@CarsonF I confirmed with Amy that what is the current Drawer display is what she wants.


Orientation wrong in some Vessels

First: Amazing work! Thank you so much, I've been waiting for this for ages!
I've noticed that in some cockpits the orientation is rotated upwards (as if you're lying on the ground on your back). Examples are the ALCOR Landing Capsule and the Lander Can for 2 Kerbals.
Is there any way to fix this?

I didn't realize certain capsules had a different internal orientation. Fixed! Closed via #34
See latest release (v3.1.2).


[VS Code] Cannot read property 'sessionId' of undefined

Error:
Cannot read property 'sessionId' of undefined
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.1151

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.30.2

platformName
MacOS

platformVersion
17.6.0

Closing due to inactivity. Please re-Open if you’re still encountering this issue. Thanks!


[AutoPR netapp/resource-manager] add netapp 2019-06-01 to Go SDK

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6495

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/5155


feat: Ability to manage worker groups as maps

PR o'clock
Description
Resolves #774
The change is intended to improve the ability to manage worker groups using maps. Which should allow to more flexibly add/remove worker groups (improve this: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/faq.md#how-do-i-safely-remove-old-worker-groups).
The change includes suggested in #774 changes which include:

create separate submodule for worker_groups
the submodule includes only LaunchTemplate support

Change to the worker groups definitions:

to use new worker groups definitions use:

worker_groups = {}

old worker groups definitions should be renamed as below to avoid resources destruction (and allow migration)

worker_groups = [...] => worker_groups_legacy = [...]

worker_groups_launch_template = [...] => worker_groups_launch_template_legacy = [...]

Checklist

[ ] CI tests are passing
[x] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-eks/#doc-generation

Thanks @grzegorzlisowski for opening this PR. Actually, this is something we want to add into this module and totally drop the loop with count in favor of for/for_each.
With that said, it would be nice to split the feature into a new submodule. We started some discussion at https://github.com/terraform-aws-modules/terraform-aws-eks/issues/774.
@js-timbirkett is maybe busy actually, so if you can open a PR to address https://github.com/terraform-aws-modules/terraform-aws-eks/issues/774 it would be very appreciated.

the old way of defining worker groups still possible for some backward compatibility and easier migration to the new version (after some time old way of defining worker_groups could be dropped entirely)

I was wondering if we shouldn't drop this directly. Because for existing worker group, users will have to move resources in the state. So why not move them directly into a map ?
For locals, shouldn't we move https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/local.tf#L34-L100 and into the submodule ?

My assumption was that users could apply the new module and add new worker groups using maps then migrate K8S resources to new nodes and then remove old groups simply by removing the list.
Those locals I have left in the original place as I assumed we still use them in "legacy" worker definitions. If we will just drop old worker_groups definitions then those should be moved.

Do we know what is blocking this?

I presume review and approval? I'm not sure why this "Semantic Pull Request" check is not passing

we can use worker_groups as a list instead of map so that it would be more cleaner and we can do ..
locals {
worker_groups = { for worker_group in var.worker_groups : worker_group.name => worker_group : {} }
worker_group_configurations = {
for k, v in local.worker_groups : k => merge(
local.workers_group_defaults,
v,
) if var.create_workers
}
}
`

we can use worker_groups as a list of maps with unique key name.. instead of map so that it would be more cleaner and we can do ..
worker_groups = { for worker_group in var.worker_groups : worker_group.name => worker_group }

worker_group_configurations = {
    for k, v in local.worker_groups : k => merge(
      local.workers_group_defaults,
      v,
    ) if var.create_workers
  }
}

It could be done but I presume it might make sense to keep the same approach as for node_groups where maps are used as an input.

Error sometimes appear randomly without changing anything in code.
Error: Inconsistent conditional result types

  on .terraform/modules/eks_0/modules/worker_groups/data.tf line 5, in data "aws_iam_instance_profile" "custom_worker_group_iam_instance_profile":
   5:   for_each = var.manage_worker_iam_resources ? {} : local.worker_group_configurations
    |----------------
    | local.worker_group_configurations is object with 3 attributes
    | var.manage_worker_iam_resources is false

The true and false result expressions must have consistent types. The given
expressions are object and object, respectively.

Error sometimes appear randomly without changing anything in code.
Error: Inconsistent conditional result types

  on .terraform/modules/eks_0/modules/worker_groups/data.tf line 5, in data "aws_iam_instance_profile" "custom_worker_group_iam_instance_profile":
   5:   for_each = var.manage_worker_iam_resources ? {} : local.worker_group_configurations
    |----------------
    | local.worker_group_configurations is object with 3 attributes
    | var.manage_worker_iam_resources is false

The true and false result expressions must have consistent types. The given
expressions are object and object, respectively.

Issues happen when adding a second group to worker_grpups

@ZeroDeth
Could you share your setup so I will try to recreate the issue?

Thanks @grzegorzlisowski for working on this. We have an terraform-aws-modules working session this friday. We'll discuss about the direction we want to take about this feature. We'll come back to you pretty soon.

@barryib @grzegorzlisowski Any update on the state of this change?

We'll work on this soon and It'll be the next breaking change. But I want to release first https://github.com/terraform-aws-modules/terraform-aws-eks/pull/997 and https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1067.

@ZeroDeth
Could you share your setup so I will try to recreate the issue?

Apologise for late respond and now we moved away from manage worker groups. Thanks

I missed this PR when I wrote https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1132 , but if you check it out it's possible to convert the list passed by the caller into a map internally, without changing the module's API surface

I missed this PR when I wrote #1132 , but if you check it out it's possible to convert the list passed by the caller into a map internally, without changing the module's API surface

There was such comment earlier: https://github.com/terraform-aws-modules/terraform-aws-eks/pull/858#issuecomment-648444111
I just wanted to stick with a single convention of defining resources

Lin/Code Forma is failing as workflow is using terraform:latest which is now 0.14.0 which seems to have some problems with formating

Any updates on this? I'd be more then happy to help with getting this pushed through.

Any updates on this? I'd be more then happy to help with getting this pushed through.

We'll work on this soon and It'll be the next breaking change. But I want to release first #997 and #1067.

How are you planning on rolling this out without instantly replacing existing worker groups?
I was thinking, when doing these types of breaking changes (Like moving from lists to maps, or moving worker groups into a submodule, replacing every resource), wouldn't it be possible to include a version or implementation variable in the worker_group definition, or specify the new worker groups using a different variable name?
Then you can have a release flow like:

vN: Add worker_group module
vN+1: Remove old implementation

Using vN, users can duplicate the workgroups they already had, using the new implementation, and then tear down the original ones. After that they're good to move to module vN+1.

We'll work on this soon and It'll be the next breaking change. But I want to release first #997 and #1067.

How are you planning on rolling this out without instantly replacing existing worker groups?
I was thinking, when doing these types of breaking changes (Like moving from lists to maps, or moving worker groups into a submodule, replacing every resource), wouldn't it be possible to include a version or implementation variable in the worker_group definition, or specify the new worker groups using a different variable name?
Then you can have a release flow like:

vN: Add worker_group module
vN+1: Remove old implementation

Using vN, users can duplicate the workgroups they already had, using the new implementation, and then tear down the original ones. After that they're good to move to module vN+1.

@TBeijen That was my original plan but got suggested that this interim step might not be needed and state might be just migrated: https://github.com/terraform-aws-modules/terraform-aws-eks/pull/858#issuecomment-625898612
So I have dropped support for this.

@TBeijen That was my original plan but got suggested that this interim step might not be needed and state might be just migrated: https://github.com/terraform-aws-modules/terraform-aws-eks/pull/858#issuecomment-625898612
So I have dropped support for this.

@TBeijen That was my original plan but got suggested that this interim step might not be needed and state might be just migrated: #858 (comment)
So I have dropped support for this.

Ok. Since I use Terraform via an in-house service, I think I can't modify tfstate. So probably I need to create a temp. fork supporting both mechanisms, if at all possible. Or switch to managed nodes, which we're considering anyway.
Otoh: Migrating all of the current resources locks us out of certain clean-up & simplifications in the old worker group implementation. Moving all code based on maps into a submodule could be a good moment to do so. I'm mainly thinking of sticking to the EKS-created security_group and ditching the now redundant sg created by this module. See https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1196#issuecomment-769665986 and my follow up comment.
@barryib What's your thought on this? I know this has the risk of re-activiting long done discussions, which can slow down momentum. That's obviously not my intention so I'm fine with any answer.

@TBeijen That was my original plan but got suggested that this interim step might not be needed and state might be just migrated: #858 (comment)
So I have dropped support for this.

Ok. Since I use Terraform via an in-house service, I think I can't modify tfstate. So probably I need to create a temp. fork supporting both mechanisms, if at all possible. Or switch to managed nodes, which we're considering anyway.
Otoh: Migrating all of the current resources locks us out of certain clean-up & simplifications in the old worker group implementation. Moving all code based on maps into a submodule could be a good moment to do so. I'm mainly thinking of sticking to the EKS-created security_group and ditching the now redundant sg created by this module. See https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1196#issuecomment-769665986 and my follow up comment.
@barryib What's your thought on this? I know this has the risk of re-activiting long done discussions, which can slow down momentum. That's obviously not my intention so I'm fine with any answer.

In the additional commit, I have added the option to migrate from old (legacy) worker groups to the new one.
It requires introducing some mess but it could be clean up when the old way of managing worker groups will be dropped.
examples/basic and examples/launch_templates contains proper examples.
The module migrates existing variables (lists) appropriately:
worker_groups -> worker_groups_legacy
worker_groups_launch_template - > worker_groups_launch_template_legacy
This way existing users could upgrade to the new module version and slowly migrate compute to the new approach with the map via:
worker_groups
Not sure if this approach is acceptable...

@barryib is this something that is likely to happen soon?

Any chance for a review and merge?

This issue has been resolved in version 18.0.0 :tada:


Fix snackbar position

Before:

After:

I got the problem in 2 cases:

standard behaviour but message too long
when I tried to use the default slot to customize the display message with a v-html attribute
<template v-slot:default="{ message }">
 <v-layout v-html="message"></v-layout>
</template>

There are cases where it won't work…
Using your code with "random toast" button:

When it should look like the below:

Each toast should stack in its own location.
You can test with https://codesandbox.io/s/v-snackbars-tests-forked-fojh0?file=/src/App.vue:1514-1517 by changing the component source from yours (v-snackbars_new.vue) and the original one (v-snackbars_new.vue).
I'll see if I have some time later today or during the week-end to see if I find a solution, but it's tricky!

I've just published v3.2.0 that should fix the issue.


I am also facing the same issue

ValueError: Tensor Tensor("fc1/Relu:0", shape=(?, 4096), dtype=float32) is not an element of this graph.

Hi,
Could you give me more context, such as your OS, version of TF, version of Keras.


python_qt_binding: 0.3.6-2 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository python_qt_binding to 0.3.6-2:

upstream repository: https://github.com/ros-visualization/python_qt_binding.git
release repository: https://github.com/ros-gbp/python_qt_binding-release.git
distro file: melodic/distribution.yaml
bloom version: 0.8.0.dev0
previous version for package: 0.3.6-1

python_qt_binding
* convert cmake targets to plain libraries (#68 <https://github.com/ros-visualization/python_qt_binding/issues/68>)
* add Python 3 dependency with condition (#75 <https://github.com/ros-visualization/python_qt_binding/issues/75>)
* if present, use the sipconfig suggested sip program (#70 <https://github.com/ros-visualization/python_qt_binding/issues/70>)
* check for Homebrew's PyQt5 install path (#57 <https://github.com/ros-visualization/python_qt_binding/issues/57>)
* modifying sip_configure (#54 <https://github.com/ros-visualization/python_qt_binding/issues/54>)
* replace Qt variable in generated Makefile (#64 <https://github.com/ros-visualization/python_qt_binding/issues/64>)
* fixing trivial accidental string concatenation (#66 <https://github.com/ros-visualization/python_qt_binding/issues/66>)
* Windows: handling build configuration keywords before passed to SIP (#60 <https://github.com/ros-visualization/python_qt_binding/issues/60>)
* cherry-pick windows port from crystal-devel (#61 <https://github.com/ros-visualization/python_qt_binding/issues/61>)

This was created with a locally modified bloom version based on 0.8.0 which provides the ROS_PYTHON_VERSION=2 package condition until a more general solution can be implemented.
Before: https://github.com/ros-gbp/python_qt_binding-release/blob/346c7a51b4e91b6d751f019ebf726024a335297d/debian/control#L11
After: https://github.com/ros-gbp/python_qt_binding-release/blob/08ad25fdb40e1be25b56d5ccf55e4b6ed28f4875/debian/control#L11
cc @dirk-thomas; closes https://github.com/ros-visualization/python_qt_binding/issues/76


Animation input in safari is not smooth

Hi
I ask this question because I'm trying to figured out why the inputs animations are not smooth in safari ? but this happend only in safari but not in chrome or mozilla.
Any help ?
Thanks

Closed due inactivity, feel free to reopen it if it is still necessary.


WARNING: Multiple instances of Three.js being imported.

Latest builds with three-pathfinding 0.14.0 or 1.1.0 produces
WARNING: Multiple instances of Three.js being imported.
Probably need to update the build stack to define three as AFRAME.THREE external. I know how to do that with webpack.

There is also #252 to switch the build to microbundle but I don't know how to define externals with that I don't have experience with it.
With webpack I'm using this:
  externals: {
    // Stubs out `import ... from 'three'` so it returns `import ... from window.THREE` effectively using THREE global variable that is defined by AFRAME.
    three: "THREE",
  },

There is an example actually here for microbundle :)
https://github.com/donmccurdy/three-pathfinding/blob/a63301b523f85b8f578474c092460710bfed1146/package.json#L25

I think I will go with webpack here because the tests are using karma. I'll update the test stack like I already did with networked-aframe and aframe. Also add CI with GitHub Actions.

We solved the problem in our project by aliasing three to super-three with pnpm alias feature (https://pnpm.io/aliases).
We are using CRA, Webpack with TypeScript.
By the way the root cause of the problem IMHO is that aframe is using a forked version of three (super-three (I think it's a terrible solution)) as you may know: https://github.com/aframevr/aframe/issues/4898, https://github.com/aframevr/aframe/issues/4806 but aframe-extras is not using a forked version of three-pathfinding (something like super-three-pathfinding which is using super-three instead of three (just to have more mess))
I hope this informations will help you!

Thanks for sharing your experience.
The alias tip is indeed correct if you have aframe and aframe-extras as a npm dependency (because the main entry point points to index.js) and you want the three import to point to the super-three dependency.
If you use a build of aframe and aframe-extras via a CDN, you just want for libs (third party components) to create a umd build without three code, so using an external to point to the THREE global variable like I said in https://github.com/n5ro/aframe-extras/issues/389#issuecomment-1336369777

@vincentfretin - I think this is the only thing blocking us releasing a 7.0.0 release now.
How soon do you think you might be able to look at this?

I was swamped the last two weeks, I'm starting to catch up with what I put aside. I'm hoping to have some time next week to work on all the webpack config in all repos. I also really need motivation to look into it. ;-)
There is actually another issue that is blocking #380 we should revert startAt option or fix the issue.

I released 7.0.0 with the warning. I figured I'd release it in this state and release another version when I'll figure out how to update to webpack to replace this scripts/dist.js script.

We solved the problem in our project by aliasing three to super-three with pnpm alias feature (https://pnpm.io/aliases). We are using CRA, Webpack with TypeScript.
By the way the root cause of the problem IMHO is that aframe is using a forked version of three (super-three (I think it's a terrible solution)) as you may know: aframevr/aframe#4898, aframevr/aframe#4806 but aframe-extras is not using a forked version of three-pathfinding (something like super-three-pathfinding which is using super-three instead of three (just to have more mess))
I hope this informations will help you!

I tried doing this but it looks like maybe webpack can't resolve the aliased module.  Can you elaborate more on how you got this to work?

With aframe 1.6.0/master, I made this much easier, the dependency is now called three, not super-three anymore, see my comment https://github.com/aframevr/aframe/pull/5522#issuecomment-2122573248 how I use npm and webpack to have aframe with a specific version of three and aframe-extras.
So if you want to use latest version today, it would be in package.json
{
  "overrides": {
    "three"<EMAIL_ADDRESS>  },
  "dependencies": {
    "aframe": "aframevr/aframe#4449ed5",
    "aframe-extras": "^7.5.1",
    "three"<EMAIL_ADDRESS>  }
}

With aframe 1.6.0/master, I made this much easier, the dependency is now called three, not super-three anymore, see my comment aframevr/aframe#5522 (comment) how I use npm and webpack to have aframe with a specific version of three and aframe-extras. So if you want to use latest version today, it would be in package.json
{
  "overrides": {
    "three"<EMAIL_ADDRESS>  },
  "dependencies": {
    "aframe": "aframevr/aframe#4449ed5",
    "aframe-extras": "^7.5.1",
    "three"<EMAIL_ADDRESS>  }
}

@ericwood73 Yeah, we had a similar solution.

Anybody managed to fix this with Parcel?
Unlike webpack, the overrides in package.json does not work.

The overrides in package.json is a npm feature to be sure you end up with a single node_modules/three that is super-three if any dependencies has a three dependency. This has nothing to do with webpack or any bundler.
For pnpm that's a different syntax https://pnpm.io/package_json#pnpmoverrides
I'm not familiar with Parcel.


Update bonzai to remove external dependencies that are already included in bonzai.

@rwxrob Can you check this?


refactor(golint): put the files inside cmd/foo and add more go style

Hi, I add a more go style project style (put the executable files inside cmd/foo)

Ewww are those tabs?

Closed because tabs make me cry.

Hi, according the Go docs, the indent should be tabs, go has gofmt tool that help to auto format the code
https://golang.org/cmd/gofmt/
Gofmt formats Go programs. It uses tabs (width = 8) for indentation and blanks for alignment

So I know this now, but this makes me sad. Tabs make me sad, and knowing that go supports tabs makes me think of them like <insert political candidate you don't like here>. If tabs become our president I'm moving to Canada.

I felt the same at the beginning, but after a few days and seeing the power of go and their community I chose to stay in the same country


Frontend issue

My setup is on php 5.6 on ubuntu 16.04
I have set up backend and now I have issue on front end. When run I have empty indexes (no text values) and this following errors
Warning: array_merge(): Argument #2 is not an array in
/var/www/html/wlox/frontend/htdocs/index.php on line 25
Warning: Invalid argument supplied for foreach() in /var/www/html/wlox/frontend/lib/Lang.php on line 100
Any help is welcome...
also I would like invite to slack for this project
Thanks and best regards

I have the same problem

@nklak thank you for your reply.
Which whitelabeled fork do you propose ?

depends what you want to do...
You can mail me on<EMAIL_ADDRESS>


Workaround to enable mongodb_user/database to work with authentication.

To manage mongodb users the mongo utility needs to authenticate to the db, as soon as the first user has been created. As the .mongorc.js is not run in case of non-interactive use of the mongo utility, i had to use a workaround.
Further this changes allow to list users/databases with puppet resource mongodb_user

@hunner this issues isn't fixed.. https://tickets.puppetlabs.com/browse/MODULES-534


[url_launcher] Add a web only windowName param

Use case

Browser APIs allow users to open urls in multiple ways:

same window
new window
new window with an specific name
an already existing window

Currently we don't provide mechanisms to specify those behaviors, instead we force users to open all urls always in a new tab.
Proposal

To give users control about how they believe an specific url should be opened, my proposal is to add a new windowName web-only param to the launch method.
Future<bool> launch(
  String urlString, {
  bool forceSafariVC,
  bool forceWebView,
  bool enableJavaScript,
  bool enableDomStorage,
  bool universalLinksOnly,
  String windowName,
  Map<String, String> headers,
  Brightness statusBarBrightness,
})

That will be used by the web implementation like this
  html.WindowBase openNewWindow(String url, String windowName = '') {
    return _window.open(url, windowName);
  }

cc @ditman

https://github.com/flutter/flutter/issues/54281#issuecomment-616803870 is related

@tugorez: How will this interact with the current platform detection code?

@ditman that's a great question. Thanks for asking.
IMHO we should give users total control in how to open their urls. In that sense I propose:

If provided, always use this windowName
otherwise, use the default behavior https://github.com/flutter/flutter/issues/51461

Sounds good to me!

(Unassigning this unless we are actually working on it)

This has been implemented by @balvinderz, and published in the latest version of url_launcher:

https://pub.dev/packages/url_launcher/changelog#551

The implementation follows @tugorez's proposal.
The new parameter name is webOnlyWindowName.


[KYUUBI #1992] Remove SPARK_HOME predication.

Why are the changes needed?
Users who use Flink or Trino need not set SPARK_HOME, so I remove SPARK_HOME predication in bin/kyuubi script.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

@SteNicholas Please review it. Thank you a lot.

The change makes sense to me, thanks for contribution!

the HudiTestFailure is not related, it's good to go. see #1988

thanks @deadwind4 for the contribution and @pan3793 @SteNicholas for the check. merged to master


Report slow zipping to maven

In the BOM I find this comment:
       <!--
          maven-source-plugin-3.0.0 exhibits the zipping behavior on ubuntu that was seen in
          maven-jar-plugin with version < 2.5 (https://issues.apache.org/jira/browse/MJAR-188).
          Until that is fixed we should stick to 2.4.
        -->

Could someone who understands it report this upstream to Maven so it can be worked on and tracked? This may not be on their radar.

Bumped the source plugin to 3.0.1.


Sharing doesn’t work with specific feed

App Store Connect report:
“For some reason I have one feed t3n (https://t3n.de/tag/gadgets-lifestyle/rss.xml) where I could not use the share function. In the list view the share button is missing entirely and in the article view the share button has no function.”

Many articles in this feed contain malformed URLs that include spaces that have not been percent encoded between query parameters if they have multiple attached keywords. For instance:

This string returns nil when NetNewsWire attempts to create a URL for it:
guard let preferredLink = currentArticle?.preferredLink, let url = URL(string: preferredLink) else { 	return }
It would be possible to fix this bug by explicitly fixing any extant spaces in strings that are supposed to already be URL encoded:
let sanitizedLink = preferredLink.replacingOccurrences(of: " ", with: "%20")
The best way to do this I think would be to centralise it as a new article?.preferredURL property as there are multiple places in the iOS app where the same guard statement above is used and so must be failing with these same feeds.
I'd be happy to implement that, a simple fix. The question is—does the team have a view on whether NetNewsWire should be fixing broken URLs in feeds?


Question related to target extraction and classification

Hi @Franck-Dernoncourt I want to use this system for my research and perform target extraction from input opinionated sentences by BiLSTM-CRF, all opinionated sentences will be classified into non-target sentences, one-target sentences and multi-target sentences or / non-target sentences, one-target sentences, 2-target sentences, 3-target sentences, and multi-target sentences according to the number of targets extracted from them.
I wanted to ask that is NeuroNER able to perform that above stated tasks and at the end produce an output file for the processed sentences?
Kindly respond asap, Thanks in-advance....

Hi @Franck-Dernoncourt  i am waiting for your response. please respond.....


Update Character “the-blight-sisters”

Automatically generated by Netlify CMS

👷 Deploy Preview for dynamic-cheesecake-5fbd8b processing.

Name
Link

🔨 Latest commit
0a1530a77872fcc747fc1b50d678ce389e81045b

🔍 Latest deploy log
https://app.netlify.com/sites/dynamic-cheesecake-5fbd8b/deploys/633443ecf7e791000830de3c


Setup.py improvements

Make "python setup.py install" actually work.

@twiecki can you take a look at this and let me know if I did anything stupid?

This was prompted by the email last night to the zipline mailing list about installing the package not working properly.

@jikamens I think there's a fair amount of overlap between this and https://github.com/quantopian/zipline/pull/678/.

conda build zipline worked with the following changes to setup.py:
Source:
git_url: https://github.com/quantopian/zipline.git
git_tag: setup_py_improvements
Build needed:
numpy
Run needed:
contextlib2
numexpr
networkx
diff meta.yaml meta.yaml.bak:
6,7c6,8
<   git_url: https://github.com/quantopian/zipline.git
<   git_tag: setup_py_improvements
---
>   fn: zipline-0.8.0rc1.tar.gz
>   url: https://pypi.python.org/packages/source/z/zipline/zipline-0.8.0rc1.tar.gz
>   md5: f23bdd0a8671b3b297072391fc817097
13d13
<     - numpy
24,26d23
<     - contextlib2
<     - numexpr
<     - networkx
zipline/examples/dual_moving_average.py worked without issue.
The 'examples' directory was not installed with zipline.
Thanks...

I'm looking at merging the lazy-Cythonization and find_packages changes into my branch that generates install_requires from our requirements.txt.

@jikamens I think there's a fair amount of overlap between this and #678

This is #678, so not clear what you meant to refer to here.

I'm looking at merging the lazy-Cythonization and find_packages changes here into my branch that generates install_requires from our requirements.txt.

:+1: but please keep my name on the commits kthnxbye.

@jikamens Looks good to me. The alternative is to include the .c files in the packaged version (http://docs.cython.org/src/reference/compilation.html#distributing-cython-modules). Since we also don't peg the Cython version here this might cause some issues with version incompatibilities.

@jikamens @ssanderson What is the status of this, I need a solution so that we can deploy zipline on the databazaar box.

Closing in favor of #681


[Sea of Claws] Crew Tests Bugs

Crew Test Fire Battery does not detect the Helm role (probably due to the period at the end; it works fine after removing it).
https://gyazo.com/1593e8ef42f101c6a44ef7e565fb5359

Several Crew Tests use the Entertain (Sing) skill, but it should be Entertain (Singing); otherwise, it is not detected

When doing Crew Tests, it requires performing tests with all roles to calculate Total SL. I think it should count each test and its SL even if not all roles are performed (If this is intentional, you can ignore this.)
https://gyazo.com/68c19e2b74e1bdf8edf6e4669f80b313From: jtsmirrorfoundry: 11.315wfrp4e: 7.2.4wfrp4e-archives1: 5.0.2wfrp4e-archives2: 5.0.1wfrp4e-core: 5.0.7wfrp4e-dotr: 5.0.5wfrp4e-eis: 5.0.3wfrp4e-horned-rat: 5.0.4wfrp4e-middenheim: 5.0.2wfrp4e-rnhd: 5.0.2wfrp4e-salzenmund: 5.0.4wfrp4e-soc: 5.0.1wfrp4e-up-in-arms: 5.0.3wfrp4e-wom: 5.0.4wfrp4e-zoo: 5.0.2Active Modules: Border-Control, CautiousGamemastersPack, _CodeMirror, _chatcommands, advanced-macros, alternative-rotation, autoanimations, chat-commander-wfrp4e, cleaner-sheet-title-bar, color-picker, colorsettings, combat-tracker-dock, compact-scene-navigation, custom-css, dice-calculator, dice-so-nice, drag-all-to-hotbar, drag-ruler, easy-target, fa-battlemaps, filepicker-plus, force-client-settings, forge-vtt-shared-compendiums-warhammer-4ed, forien-ammo-swapper, forien-armoury, forien-copy-environment, foundryvtt-simple-calendar, fxmaster, gm-vision, hide-gm-rolls, inactive-tokens-lmao, jb2a_patreon, lib-blockly, lib-wrapper, limithron-pirateportkit, metric-ruler-labels, module-credits, monks-active-tiles, monks-combat-details, monks-combat-marker, moulinette-core, moulinette-sounds, moulinette-tiles, multi-token-edit, permission_viewer, popout, popout-resizer, quick-insert, remote-highlight-ui, rolladvantage-token-stamp-2-foundry, sequencer, silence-compatibility-warnings, simple-quest, socketlib, status-halo, tagger, times-up, token-action-hud-core, token-action-hud-wfrp4e, token-attacher, token-hud-wildcard, tokenmagic, tokenmagic-automatic-wounds, wfrp4-wfrp4e-npc-generator, wfrp4e-gm-toolkit, wfrp4e-night-vision, world-scripter

Attacking a ship (with a cannon) causes normal critical damage, not the critical damage specifically intended for ships.
https://gyazo.com/b9f0d1334250d58a43a5f3e75496324b
During ship combat, the distance between ships is not factored into the roll modifier. The distance is only calculated after placing the weapon user's token.
https://i.imgur.com/3RiYCPI.png (ships tokens)
https://i.imgur.com/i7JR2qf.png (ships tokens + canonn user token)

When you have a cannon on board a vehicle and reload it, from the GM's perspective everything looks normal:
(GM) https://i.gyazo.com/3e1bd7fdbff4dc17d09c6a9f6eaff82c.png
But when you reload it from the player's perspective, it only shows this one reloading option, even if there are other cannons on the ship that are already reloaded
(Player) https://gyazo.com/20301190723208807bda82bb7feaf8f8
Additionally, I noticed that from the player's perspective, when the situation above occurs (when the weapon is being reloaded), the cargo screen gets messed up, but from the GM's perspective everything looks normal:
(player) https://gyazo.com/5eed12e0a18415339940310dc35a578e (white text, misplaced, etc)


bump gomod deps with konvoy deps

https://jira.d2iq.com/browse/D2IQ-74231
Only change the minimum required dependencies.
I don't expect this to break anything since the Konvoy e2e tests are already working with Kubernetes 1.20. Mainly using this as an opportunity to update the Konvoy APIs.
Signed-off-by: Dimitri Koshkin<EMAIL_ADDRESS>

The build passed https://teamcity.mesosphere.io/buildConfiguration/ClosedSource_Konvoy_AutoscalerKonvoyBuild/3066883


Upgrade to latest generator build

General Support Request
The scope of this issue is to address needed upgrades for Auro Accordion.
Recommended to create a new repo with the installer and port over the core functional component code.
NOTE: There was a test with migrating the demo page to markdown and the <auro-accordion-group> was not operating as expected. This may need to be investigated prior to doing the work.
Prior to next major release
It is important that we communicate prior to the next major release that we will be changing the npm namespace.
$ npm deprecate<EMAIL_ADDRESS>"v1.x is no longer supported. Please see @aurodesignsystem/auro-accordion for further updates"

On hold until WC-Generator 3.0 is released

should be completed in coordination with #70


Slow publishing rate since update

Slow publishing since upgrade.

Hardware description: ESP32 Wroom
RTOS: FreeRTOS
Installation type: micro_ros_espidf_component
Version or commit hash: foxy (latest)
esp-idf: release/v4.3

Since upgrading to the latest micro_ros_espidf_component we are seeing a large performance drop on the ros publishing side.
We previously were able to publish sensor data at around 150hz (~32byte message at 1'000'000 baud). However now since upgrading, we are only seeing around 10hz.
We are connecting to the micro_ros_agent via serial.
Does anyone know what the possible cause and potential solution could be?
Thanks!

Which was your previous commit and the current one? I need this to check the changes.
Also, can you share your code so we can check how you are creating the entities?

We also just tried increasing the frequency of the int32_publisher_custom_transport example and it seems to be capped at 10hz.
Have you been able to increase that?

We are also a bit confused on the micro_ros source/build process, it seems that even if we check out the earlier commit, we are still obtaining a new version when building.
For example, the old  <rmw_uros/options.h> is not available even after checkout. It seems as tho micro_ros_component will always pull the latest repos it needs to compile?

I have been able to replicate the problem, working on that.

okay great, thanks
btw we also noticed that when using a similar paradigm to your multithread example we then get a split of 5hz per publisher. Might help you narrow down the issue.

This should solve your issue: https://github.com/micro-ROS/micro_ros_espidf_component/pull/91
It is related with the heartbeat process in reliable communications. In fact with your current setup, if you make a best effort publisher (which is recommended for those rates), it will be faster than 10 Hz. With the patch that I'm applying the reliable publisher should reach at least 60 Hz.

Okay thanks
So if I'm understanding you correctly, using the best effort publisher we will be able to reach the 150hz we were able to achieve previously?

Awesome, this fixed our problem.
We have a quick follow-up question tho, is there any documentation on these flags?
We were not aware of "-DUCLIENT_MIN_HEARTBEAT_TIME_INTERVAL=1" and are also wondering what                 "-DUCLIENT_PROFILE_MULTITHREAD=ON" this does exactly?
We do have a mutlithreaded publisher running and would like to make it as stable as possible.
Thanks

UCLIENT_MIN_HEARTBEAT_TIME_INTERVAL is documented here: https://micro-xrce-dds.docs.eprosima.com/en/latest/client.html?highlight=UCLIENT_MIN_HEARTBEAT_TIME_INTERVAL#configurations
DUCLIENT_PROFILE_MULTITHREAD allows to use an XRCE-DDS session (the micro-ROS middleware) from different threads or tasks using internal mutexes. By default the middleware is not locked and access from multiple threads will cause probrems.
Regarding best-effort vs reliable in the XRCE-DDS protocol, you can check here: https://micro-xrce-dds.docs.eprosima.com/en/latest/client.html?highlight=reliable#streams

I'm closing, do not hesitate to reopen if you have more problems.

Thanks for the info and your help! All good for now :+1:


Ethnic group appearing as UK on candidate summary of application

Describe the bug
When teams download the diversity report the ethnicity says UK where a candidate has not answered the question rather than remaining blank or indicating the question was not answered.
To Reproduce
Steps to reproduce the behavior:

Go to: https://apply-staging.judicialappointments.digital
Edit profile to leave Ethnic profile blank on equality and diversity
Make an application
Go to: https://apply-staging.judicialappointments.digital
View your application
Go to Equality and Diversity
It will say 'Ethnic group	UK'

Expected behavior
The team would either expect the candidate to see 'Prefer not to say'
Screenshots

Desktop (please complete the following information):

OS X 10.14.6
Chrome
Version 79

Additional context

cannot reproduce this locally has it since been fixed?


Update kyverno and starboard-exporter

Checklist

[x] Update changelog in CHANGELOG.md.
[x] Make sure values.yaml and values.schema.json are valid.

Will do this as 0.8.1


IAPP species on site

EDIT:  Breaking this one up as much is done, making remaining work obvious.

[x] do ticket #843   first
[x] ensure IAPP points of interest can be viewed with the species code as labels on a public facing map accessed via a website
Edit see comment below for the ticket for this task:
- [ ] When a user clicks on an iapp point of interest, the following information shows in a pop up: species (one or more), date created, jurisdiction(s), area in most recent survey attached to site, ever treated or not (no details of treatment except whether it was mechanical, chemical or biological).
[x] ensure public users (without access) cannot open the records.

IAPP map on click behaviour:

[ ] When a user clicks on an iapp point of interest, the following information shows in a pop up: species (one or more), date created, jurisdiction(s), area in most recent survey attached to site, ever treated or not (no details of treatment except whether it was mechanical, chemical or biological).


No CSS?

I followed the instructions and keep getting "Failed to load resource: the server responded with a status of 404 (Not Found)"

Can you share a screenshot with the error message?

https://hampton.pw/jekyll/ its right here the scss file is not compiling

I thinks its because I remove

Only the main Sass file needs front matter (the dashes are enough)

from the top because when that is there I then get
nverting 'css/main.scss':
Invalid US-ASCII character "\xC2" on line 22
...error:
Error: Invalid US-ASCII character "\xC2" on line 22
Error: Run jekyll build --trace for more information.

I needed to add
if locale -a | grep -qF 'C.UTF-8'; then
loc="C.UTF-8"
else
loc="en_US.UTF-8"
fi
export LANG=$loc
export LC_ALL=$loc
to my .bashrc


listener: create generic listener filter timeout

Move the hard-coded 15s timeout in TLS inspector into
the connection handler such that it covers all listener
filters. Also make it configurable as well as add useful
stats to see how many connections are currently undergoing
listener filter processing.
Fixes https://github.com/envoyproxy/envoy/issues/5217
Risk Level: Medium
Testing: Unit tests
Docs Changes: Done
Release Notes: Done

@ggreenway @PiotrSikora PTAL


Should the proof be part of the MTXQ proper?

Currently just being passed in the MatchEven (payload) so as not to decrypt the MTXQ.

Not at this time


Remove segment open fellowship

Segment Open Fellowship is no longer from 2017.

@tapaswenipathak Check this out!

Please post your PR's on https://github.com/deepanshu1422/List-Of-Open-Source-Internships-Programs as this current repository is not merging any pull request since November 2019


feature: create directory as part of unpacking

As a user, I would like dcp to be able to create a directory (a subdirectory of the current working directory, for example) when unpacking contents, so I don't need to create the directory manually before hand.
One option is to introduce a new flag, -o, that when set creates a directory on the local filesystem.
Another option is to use the existing -d flag to create a directory if one does not exist already.

Another option is to use the existing -d flag to create a directory if one does not exist already.

I believe right now if you use the --content-path option right now, it will create the directory for you if it doesn't already exist based on the path you provided. That being said, I agree that having this default to something that create the directory inside of relative path would make sense. Perhaps something like ./output would be a logical default and you can specify --content-path to change that.


Research into how to "get" the call and how to access the Email.

Integrating Voice Calls into System:
Twilio Voice: Twilio provides APIs that allow you to receive, make, and manage voice calls programmatically. Here's a simple approach using Twilio:
Set up Twilio: Sign up for a Twilio account, and purchase a phone number.
Recording: You can instruct Twilio to record the call using  in your TwiML response.
Voice-to-Text: Once the call is recorded, you can use Twilio's transcription service or another third-party service to convert the call recording into text.
Asterisk: This is an open-source framework for building communications applications. With Asterisk, you can handle calls, but the setup is more complex compared to Twilio:
Setting Up Asterisk: Install Asterisk on a server.
Integration with SIP: You'll need a SIP (Session Initiation Protocol) provider to handle the telephony side.
Recording: Asterisk allows for call recording.
Voice-to-Text: Post-recording, integrate with a transcription service to convert the voice recording to text.

Automatically Processing Incoming Emails:
Mailgun: Offers powerful set of APIs to send, receive, and track email.
Set Up Mailgun: After signing up for Mailgun, configure it to handle incoming emails.
Routes: Create routes in Mailgun. When an email is received, Mailgun can forward it to your server via a webhook.
Webhook Handling: Your backend will then receive the email content, including headers, body, attachments, etc., and process it accordingly.
IMAP Integration: If you're using an existing email service (like Gmail), you can use IMAP to fetch and process emails:
IMAP Library: Use libraries like imapclient for Python to connect to your mailbox.
Fetching: Regularly fetch unread emails and mark them as read once processed.
Processing: Extract content and any necessary metadata from the email to create tickets or take other actions in your system.

@garvinkon and i did this together
Accessing_Data.pptx


How to get Poll options from a tweet

Hi,
I am trying to retrieve the options from a poll in a tweet, which should be possible according to Twitters Docs: https://developer.twitter.com/en/docs/tweets/enrichments/overview/poll-metadata
However when I get a tweet that has a poll in it, the poll attribute doesn't appear in the information returned.
This is what I am currently using
status = api.get_status(status_id)
Any suggestions?

As that documentation says, it's:

Available across all enterprise APIs

The GET statuses/show/:id endpoint that API.get_status uses is not an enterprise API.
For more information, see https://twittercommunity.com/t/idea-adding-polls-api-support-for-3rd-party-clients/127837, https://twittercommunity.com/t/poll-support/78235, and https://twittercommunity.com/t/poll-support-for-rest-api/54775.


Correct spelling mistake

'Seconday' is misspelled - should be 'Secondary'

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@CHDAFNI-MSFT : Thanks for your contribution to the Azure documentation! The author, @ryansoc, has been notified to review your proposed change.