[WIP] ui trader

Before we can add live trading (tradebot) to the UI, we need to do the following:

[x] register at what prices and times orders where executed at.

[x] poloniex
[ ] kraken
[ ] bitstamp
[ ] bitfinex
[ ] GDAX

[ ] hook into all risk & profit calculation logic (currently inside papertrader)

[x] pull performance/risk calculation logic from paperTrader into new plugin
[x] broadcast paper trader trades as "trade"
[x] broadcast real trader trades as "trade"

[x] expose via web UI
[ ] add web UI control panel where users can set API keys

broadcast those as "trades"

Excited about this! Two questions though... How do I access indicator output via api.. Last I checked it simply isn't possible unless I'm blind... I mean can the ui parse indicator output? Am I blind? I want to contribute but I'm kinda road blocked.. Well not blocked I just find it easier to make forward progress tackling easier tasks. And number two... I saw another member created multi time frame ability... And tied that into strategies. I'm curious if ANYONE here actually makes decisions based on one time frame. Me personally I review 5 15 30 min,  2 and 4 hour candles before I make a decision.. I would think my strategies should do the same!  Are there any plans for the ability to tie different indicators to different candle sizes? I believe this work has already been done... Could we get this implemented?

To answer your questions I have to quickly go over Gekko's architecture. There is a document describing it here, but it's a but out of date. Very simply put this is how Gekko works:

This PR is to break the last part (paper trader) up into two different parts (paper trader & performance analyzer) this way we can use exactly the same code to calculate statistics, results, etc. for both the paper trader and real trader:

This will be necesarry to support live trading in the UI, since we need to display these statistics for the live trader just as the paper trader.

How do I access indicator output via api.. Last I checked it simply isn't possible unless I'm blind... I mean can the ui parse indicator output?

Those are not exposed yet, I have plans to do that (see #690). This is a completely separate issue as it will involve changing some code in the strategy logic (the second last box in the first picture - not the strats, but the wrapper code that registers indicators, updates them every candle, etc).
The live trader has higher priority for me.

I want to contribute but I'm kinda road blocked..

If you want to work on #690 that would be very hard (if you are not familiar with the codebase) since you have to touch the deepest/oldest parts of the codebase as well as the networking/UI logic in order to display the results. The gist is that gekko runs code on every candle (when it executes your update and check methods) here. This is where we need to take indicator output and push it through to the parent process. I am planning to work on that myself, but I want to do this first.

I saw another member created multi time frame ability... And tied that into strategies. I'm curious if ANYONE here actually makes decisions based on one time frame. Me personally I review 5 15 30 min, 2 and 4 hour candles before I make a decision.. I would think my strategies should do the same! Are there any plans for the ability to tie different indicators to different candle sizes? I believe this work has already been done... Could we get this implemented?

That user wanted this to be part of Gekko but I ended up not adding it as is because:
The aim of Gekko is to simplify trading strategies, but the required extra config (for everyone, even people who run simple strategies over a single timeframe) made it very complex to understand how to create a strategy for X timeframes and where to put code that was run under what timeframe. I am very open to a PR or issue discussing integrating that.
That said I think this would be a better approach:
Gekko has code that runs indicators based on candles, but now that is tighly coupled to the strat wrapping code. If we can decouple that as a simple class like so: put candle in --> [  x   ] --> indicator result comes out. Once we have those we can very simply expose them to the strategies (in combination with the candleBatcher, a class that takes 1m candles and spits out Xm candles).

live trading with the UI works for poloniex now:

but keys are required to be set in /api-keys.js (use this as a base)

what do I need to change at the simulation settings(asset, currency, fee,..) if I would like to trade live? or did I miss something? (i edited the code to support live trading (https://github.com/askmike/gekko/commit/e515a39a5477eabc1a6eee9ff73e26253278efe9))could someone post an example pls?  ty for help&time

Those commits are part of a new feature which is not completed yet, it
barely works at this stage (limited to poloniex, no edge case/error
handling, logic needs to be validated, etc). I would highly advice not
running it since this is untested and unstable code - as you might lose
money on bugs, but if you do you can just download that branch instead.
On Wed, Jun 14, 2017 at 11:18 AM, long-einser<EMAIL_ADDRESS>wrote:

what do I need to change at the simulation settings(asset, currency,
fee,..) if I would like to trade live? or did I miss something? (i edited
the code to support live trading (e515a39
https://github.com/askmike/gekko/commit/e515a39a5477eabc1a6eee9ff73e26253278efe9))could
someone post an example pls? ty for help&time
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/pull/737#issuecomment-308388802, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7MDxYTnnk0NVkAUJrYbI7WgUsOedLfks5sD7NbgaJpZM4NRYYN
.

--
PGP key at keybase.io/mikevanrossum
https://keybase.io/mikevanrossum/key.asc

Thank you for your fast reply.
I installd and tried the branch out for some days.
Problems I have now are..
I cant make backtests ( all calculations( show up as nan or nan%), same histroy backtested with branch stable it works.
 I could imagine it but not 100% sure (currency choice?)
No trades in 2days+.
have a nice weekend

That branch is in development and all features are probably broken, it's not meant to be run right now (very unstable). Whenever I have free time I will work on that branch and improve it. Once it is finished it will be part of the develop branch and can be tested (with maybe just a few small bugs).

This is a backtest setting (has no effect on real trading). When you run a backtest you are simulating with virtual money, asset=1 means that your virtual balance includes 1 asset (so bitcoin if you are simulating over a new branch). @long-einser please open a new issue if you have further questions. Your comments have nothing to do with the implementation of this issue.

You can manage your API keys through the gekko UI!
It looks like this:

Only thing left to do before we can merge is:

When you start a trading bot, check whether the API keys are available, if not route to config page.
Test!

@askmike Just to comment about the api-key configuration design... looks like you are developing it so that there is only 1 set of keys per exchange. Other than the fact that some individuals may want to trade on multiple accounts, Bitstamp have an amazing feature were you can set up sub-accounts. They have created this feature specifically with automated traders in mind. Each sub accounts has its own real-currency and cryptocurrency balances and separate API keys. It's great for traders who want to trade multiple cryptocurrencies or run different strategies simultaneously.
I hope more exchanges also develop such features in the future.
But my point is if you are moving towards stored api-keys, it would make sense for them to support multiple sets of keys for each exchange - if that isn't the case already.

@ali1 good point, I will later update this system to be more flexible. But for now I just want to roll this out to start getting some feedback and bug reports.
I was thinking about improving this by allowing users to "name" a set of keys and also set trading limits tied to this name.

But my point is if you are moving towards stored api-keys, it would make sense for them to support multiple sets of keys for each exchange - if that isn't the case already.

You are very right, having to later migrate this might be more work. But having multiple possible keysets per exchange also requires a lot of different updates: users need to specifically select a keypair "name" when starting a gekko, and if you are already running a live gekko on the same exchange (using a different keypair "name") we need to be able to understand whether that is an API key of the same account (something Gekko will not support), or a different account (or subaccount). The UI-trader has been in development long enough, just want to get a feature our first :)

This is what it looks like to run a live trader:

Just to comment about the api-key configuration design... looks like you are developing it so that there is only 1 set of keys per exchange. Other than the fact that some individuals may want to trade on multiple accounts, Bitstamp have an amazing feature were you can set up sub-accounts. They have created this feature specifically with automated traders in mind. Each sub accounts has its own real-currency and cryptocurrency balances and separate API keys. It's great for traders who want to trade multiple cryptocurrencies or run different strategies simultaneously.

If you have multiple accounts trading at once you would need multiple strategies and settings running against those. This makes it a bit more complicated. But if we'll have multiple separate strategies, it would be great to add in there the ability to create a strategy (on a single account) that can run strategies with different candle sizes so you can compare them before signaling a buy/sell. For example: If strategy1 with 1hr candle size says SELL check that Strategy2 with 5min candle says sell as well, wait until it does before selling. Maybe its already possible, but doesn't seem so in the UI.


HELP! datepicker-option lead to [$compile:nonassign]

Angular: 1.4.7
UIBS:1.3.2
Error: [$compile:nonassign] Expression '{formatMonth:'MMMM',datepickerMode:'day',minMode:'day',maxDate:vm.today}' in attribute 'datepickerOptions' used with directive 'uibDatepickerPopup' is non-assignable!

This happens when I get into month-choose-mode and year-choose-mode, when I first open the datepicker-popup, there is no error, I want to know why and a solution.
I have already found that if no maxDate is setted, everything will be ok.
Bellow is my use of datepicker:
<input class="form-control" type="text" id="basicInfo-{{key}}"
                       uib-datepicker-popup="yyyy/MM/dd"
                       datepicker-append-to-body="true"
                       datepicker-options="{formatMonth:'MMMM',datepickerMode:'day',minMode:'day',maxDate:vm.today}"
                       popup-placement="top-left"
                       current-text="{{'currentText' | i18n}}"
                       clear-text="{{'clearText' | i18n}}"
                       close-text="{{'closeText' | i18n}}"
                       ng-model="vm.basicInfos[key]"
                       is-open="open">

The reason for this is that datepicker-options is bound via two-way binding. You should use something like
$scope.options = {
  formatMonth: 'MMMM',
  datepickerMode: 'day',
  minMode: 'day',
  maxDate:vm.today
};

datepicker-options="options"

In the future, please note that the issue queue isn't for support issues, but for legitimate verified bugs/feature requests.

thans!

@wesleycho
Is there a way to avoid this? I have several date pickers on a page. I don't want to create a datepicker -options object for each. So I am adding datepicker-options in the HTML like this
datepicker-options="{maxDate: vm.oGrantData.TotStop, showWeeks:false}"
And since I have not created a datepicker-options object, it throws this error when I am changing the Date enter mode, (Year, month).

@wesleycho Try to assign a variable in your scope or controller to the expression, not literal value.


Adding tweet button helper

I have added a helper called tweet-button.html. Including this in post.html of the theme would have a small tweet button at the end of the post. I am using the tweet-button provided by twitter

I have added a configuration variable called tweet_button in _config.yml and set the default value to false. Setting it to true will enable the tweet button

Modified the themes accordingly.

Usage:
{% if site.tweet_button %}
    {% include helpers/tweet-button.html %}
{% endif %}

Let me know what you think about this feature ? Do you need any changes?

Might I suggest changing the config variable from "tweet_button" to something like show_tweet_button or enable_tweet_button to hint at the fact that is field is a boolean?

Also, do you think there is value in making a new array of config params called sharing to facilitate the addition of other services?
sharing:
    enable_twitter: true
    enable_hacker_news: false
    enable_reddit: true
    enable_gplus: true

Though as I write this, maybe it is worth looking into one of those plugins (e.g. https://github.com/dbushell/Socialite) that lets you share on all the networks instead of reinventing the wheel.

@swanson : I like your idea actually:). We can create a sharing.html helper and which would read the sharing hash config and generate the buttons dynamically. Let me know if you are working on this Or do you want me to work on this?

I'm not working on it - so go ahead if it interests you. I just like doing code reviews :-)

@swanson : Thanks for the reviews, its making me a better developer by the day :)


mvn clean package -pl api docker:build fail with below error .

[INFO] Scanning for projects...
[ERROR] [ERROR] Could not find the selected project in the reactor: api @
[ERROR] Could not find the selected project in the reactor: api -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
ERROR: Service 'ui' depends on service 'api' which is undefined.
host not found in upstream "api" in /etc/nginx/conf.d/default.conf
nginx: [emerg] host not found in upstream "api" in /etc/nginx/conf.d/default.conf
[ERROR] Failed to execute goal on project api: Could not resolve dependencies for project com.capitalone.dashboard:api:jar:3.0.2-SNAPSHOT:

I assume you want to build a docker image for API? Based from this document? https://hygieia.github.io/Hygieia/api.html
I experienced the same error.. what i did was this:

Run 'mvn install' inside /api

you must see a BUILD SUCCESS in the end
then you will see the generated *.jar file inside the /target (this is iimportant)

Use the Dockerfile in the /api folder. Build the image using the docker file

e.g. docker build . -t your_api_image_name


Please add an example for a variable used as a task condition in the same job as it is declared

This is generally an excellent piece of work with many good example of use cases.
It does seem to be missing the use case of a variable declared in a task used as a condition in a following task in the same job.
I think this would be helpful since this syntax isn't obvious to me.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 92ad0d9b-2e51-de2e-a529-6cbe55692023
Version Independent ID: 609b6196-cc6b-677a-c76f-f82bb7cce10a
Content: Set variables in scripts - Azure Pipelines
Content Source: docs/pipelines/process/set-variables-scripts.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@Miles-Davies-HORIBA -- Miles, thank you for your feedback.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@juliakm -- Julia, please look into this issue.

@Miles-Davies-HORIBA Here's an example. The variable isProd is set to false in the variables section of the YAML pipeline. This variable is then used as a condition for the PublishBuildArtifacts task. The task does not run because the condition eq(variables.isProd, true) means that the task will only run if the value of the isProd variable is true.
pool:
  vmImage: ubuntu-latest

variables:
  isProd: false

jobs:
- job: Build
  displayName: 'Build job'
  steps:
  - script: echo 'This is a build job.'
  - task: PublishBuildArtifacts@1
    displayName: 'Publish build artifacts'
    condition: eq(variables.isProd, true) # task skips because of isProd is false

I'll add a similar example to our docs.

@Miles-Davies-HORIBA Here's an example. The variable isProd is set to false in the variables section of the YAML pipeline. This variable is then used as a condition for the PublishBuildArtifacts task. The task does not run because the condition eq(variables.isProd, true) means that the task will only run if the value of the isProd variable is true.
pool:
  vmImage: ubuntu-latest

variables:
  isProd: false

jobs:
- job: Build
  displayName: 'Build job'
  steps:
  - script: echo 'This is a build job.'
  - task: PublishBuildArtifacts@1
    displayName: 'Publish build artifacts'
    condition: eq(variables.isProd, true) # task skips because of isProd is false

I'll add a similar example to our docs.

Hi Julia, thanks for the quick reply. The example you propose is similar to other examples and doesn't address my feedback. I apologise if my feedback was not clear.
I would like an example of a task creating a variable using the logging commands and a following task using that variable as a condition. I think the syntax for this use case is complex and finding the solution was tricky for me. The proposed example doesn't cover my use case and is pretty simplistic. The example below covers my use case I think
`
steps:

powershell: |
Write-Host "##vso[task.setvariable variable=ShouldRun;isoutput=true]$true"
name: CheckShouldRunStep

powershell: |
Write-Host "##[debug]Conditional step is being run"
condition: |
and(succeeded(), eq(variables['CheckShouldRunStep.ShouldRun'], 'true')
`

@Miles-Davies-HORIBA Thanks for the clarification. Here's an updated example.
pool:
  vmImage: ubuntu-latest

jobs:
- job: Build
  displayName: 'Build job'
  steps:
    - task: Bash@3
      inputs:
        targetType: 'inline'
        script: |
          # Create a variable using the logging command
          echo '##vso[task.setvariable variable=isProd;isOutput=true]false'

    - task: PublishBuildArtifacts@1
      displayName: 'Publish build artifacts'
      condition: eq(variables.isProd, true) # task skips because of isProd is false

There are some more detailed examples in our conditions article. I'll add a link to that article.


Create BWC test page

The BWC test page will be a list and must have in each row:

plugin name
security enabled?
distribution
architecture
tests executed
tests passed
tests failed
start time
end time
test log


[IN PROGRESS] Replace build tasks with a Mix plugin

Hi.
I am currently working on a project and decided to take a break and write the Jigsaw build tasks into a mix plugin.
I was curious if there was any interest in doing this in core? I think the end result is rather clean.
I'd gladly transfer ownership and/or contribute / help maintain a repository on tightenco's side & scrap mine.

🎉 I really like this idea; it would give us the the freedom to update the build tasks separately, and it really streamlines the config. I'd definitely take you up on your offer to put this under Tighten's namespace, and would also love if you continued contributing to it!

Glad you like it!
I went ahead and added eslint rules just now to match Laravel Mix's core rules and cleaned up a few things.
Would you prefer to start a new repo and grant me access?
Also, is there any interest in using CircleCI for testing the linting? If so, I can add a config file. Otherwise, writing actual tests falls a little short being that we would need a Jigsaw environment with the bin to actually test– but I don't think that's necessary.

I think we're OK without CircleCI on this. I'll set up a new repo for this shortly.

@Log1x thank you so much for this!
We've set up a repo at tightenco/laravel-mix-jigsaw and I made some updates and restarted the versioning to 1.0.0. I'll PR this repo shortly to update Jigsaw to actually use this package—I've added you to that repo, would you be open to updating the laravel-mix-jigsaw npm package to point to it too?

No problem.
I invited you to the npm package so you can transfer it to the tightenco org.

Thanks! I see it in my account but I'm getting a 403 if I try to publish or do anything on the command line. I think you may need to add me as an owner, not just a collaborator?
npm owner add bakerkretzmar should do it.

npm owner add bakerkretzmar is what I had done after adding you as a maintainer and then removed myself (so you could move it or do whatever with it) – so now I'm also getting a 403 myself. Oops.
I'll toss them an email.

Looks like it's working now actually. Thanks!


When SectionList scrollToLocation function not working

Say you have a SectionList Nested in a SrollView e.g
<ScrollView>
  <SectionList />
<ScrollView>

and you want to scroll to a specific section in the SectionList using scrollToLocation function, it wont work. Any help please

This might be the same problem as #25295 which was never addressed

Specifically, the error looks like this for me:

Any update on this?

@roryabraham not working


patient-ssapp v0.10.10 the PharmaLedger logo should navigate to the dashboard

The PharmaLedger logo at the top right should act as a home button.

c3e58dc does the job, but the mouse over the image does not change to "hand"...

@lehialessandro (low-pri) do you know how to solve the mouse hover change ?
I've tried ion-button around the image, but the colors/bg of the image change.
I've tried ion-anchor, but the mouse-over did not change at all.


uglify-js security issues

[x] I'm reporting a bug, not asking for help
[x] I'm sure this is a Leaflet.MarkerCluster code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[x] I've searched through the issues to make sure it's not yet reported

My GitHub repo notified me that older versions of uglify have security issues

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8857
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8858

... and suggested that uglify be updated to at least version 2.6.0.
uglify-js has a latest version 2.x at 2.8.29 as of this PR. (There is also a v3.x, but is stated to not be backwards compatible with v2.x.)
While this is probably a non-breaking issue as Leaflet.markercluster code is already compiled in the dist folder, I would like the banner warning me about it to go away.

Thanks for reporting! uglify-js is now version 3.4.9. So I guess this can be closed.


How to use karma with code-coverage?

Hi, my lcov file is create by karma and I dont know how send the lcov file as parameter to codacy-coverage.js file because there is no document for karma and codacy-coverage.
how do I use karma to codacy coverage?

Hi, did you try the normal usage? Putting the lcov content in ./node_modules/.bin/codacy-coverage?

How could I do that? is there an example?

You can check how we handle our coverage in https://github.com/codacy/node-codacy-coverage/blob/master/circle.yml
You can pass the conent of the lcov file to codacy-coverage with:
cat ./coverage/lcov.info | node ./bin/codacy-coverage.js

I'd done but it showed me this error input is not a tty

I am not sure about the problem with the tty.
But can you try:
npm install codacy-coverage --save-dev
cat /path/to/your/lcov | ./node_modules/.bin/codacy-coverage

What OS are you using?

yes I shows me no error this time but after execute this commands:
cat shippable/codecoverage/report-lcov/lcov.info | ./node_modules/.bin/codacy-coverage
It shows nothing and my branch still clean, what should I do manually to see coverage report on codacy dashboard?

BTW I use Windows 8.1

@moslemezzati can you send a support ticket so we can check your project?

@rtfpessoa What is "support ticket" do you mean "Project Token"? If it is I'll sent it to you

No. You should never share any tokens with other people.
As we mention in the README, you should always keep it private.
About the support ticket: after you login with your account on Codacy, you should be able to see a question mark in the left lower corner of your screen. Or if you click in your account photo in the top right corner you have an option called support.
That way we can check your account and have more information.

OK thanks I did it

@machadoit I think a karma reporter would be the solution here. I'm searching for it too.

I solved the problem actually there is 2 problem first reporter file must be in a certain structure and second there is no good document to explain this simple point. It's shame!

@moslemezzati What was your solution exactly? Cause I am using karma/webpack and when I send the coverage to Codacy it shows me this error:
X Oops! We weren't able to validate your report. Ping us on the support chat and we will help you figure it out.
What might be wrong?
Outdated reporter: Always make sure you are running an up-to-date version of the reporter.
Inconsistent file paths: Depending on your project structure, we may be unable to automatically detect the files identified in your coverage report. The reporters have special options to normalise the project root folder, check their documentation.

@kavvak @moslemezzati i'm having the same problem with karma/webpack

@a11smiles @kavvak The main problem here is usually the paths that your report has coverage to.
Since you use webpack to pre-process the files before running coverage you usually also change the file paths in the system. Something like src/my/path/to/file.js ends up in something like another/path/to/file.js and since Codacy is running the analysis for src/my/path/to/file.js we wont be able to pair coverage with your files. To make this work you maybe can work around it by replacing the paths.
Can this be your problem?

one of my source files is: /home/travis/build/username/project/src/test.ts
[trace] "2016-11-12T06:03:47.394Z"  'Successfully parsed /home/travis/build/username/project/src/test.ts'

[trace] "2016-11-12T06:03:47.397Z"  { total: 100,
  fileReports:
   [ { filename: 'src/test.ts', coverage: [Object], total: 100 },
     { filename: 'src/polyfills.ts', coverage: [Object], total: 100 },
     { filename: 'src/app/app.component.ts',
       coverage: [Object],
       total: 100 } ] }

I have tried using the prefix parameter and adding /home/travis/build/username/project/ but that doesn't work either.
As nice as everything else is with Codacy, you would think:

Codacy would be smart enough to extract Travis CI's path just like the other coverage tools (Coveralls, CodeCov, etc.)
Your support team would be more responsive.  I reached out yesterday via the 'chat' and still haven't heard anything.

Do you, perhaps, not support typescript?

@a11smiles we do not support Typescript at the moment. But it is in our short roadmap and should be released soon. Check the supported languages here: https://support.codacy.com/hc/en-us/articles/207994735-Supported-Languages

@rtfpessoa Thanks for letting me know about TypeScript.  Regarding my file paths, how does everything look in the debug sample that I sent?  Do I need to do anything to tweak it?

I want to be prepared when you do release support :)

Your report looks OK. The only problem now seems to be the unsupported language.
We will notify you when TS is supported.


Add list of available filenames to /view/routes/list

The list at http://localhost:3000/view/routes/list currently shows the actual routes, and it would be good (and very practical) to also provide a link to the values that are possible

After this fix, this is what /view/routes/list-raw now looks like

and this is what /view/routes/list looks like


Disable appdomains for xunit on Mono

This should fix the instability you're seeing on Travis.
Mono bug is tracked at https://bugzilla.xamarin.com/show_bug.cgi?id=39251

Hmm, looks like some tests can't find views anymore, presumably because without appdomains  shadow-copy is disabled too:
Nancy.Testing.Tests.TestingViewExtensions.GetModuleNameExtensionTests.should_return_name_of_the_module [FAIL]
      System.Exception : ConfigurableBootstrapper Exception
      ---- Nancy.RequestExecutionException : Oh noes!
      -------- Nancy.ViewEngines.ViewNotFoundException : Unable to locate view 'TestingViewExtensions/ViewFactoryTest.sshtml'
      Currently available view engine extensions: sshtml,html,htm
      Locations inspected: views/TestingViewFactoryTest/TestingViewExtensions/ViewFactoryTest.sshtml-en-US,views/TestingViewFactoryTest/TestingViewExtensions/ViewFactoryTest.sshtml,TestingViewFactoryTest/TestingViewExtensions/ViewFactoryTest.sshtml-en-US,TestingViewFactoryTest/TestingViewExtensions/ViewFactoryTest.sshtml,views/TestingViewExtensions/ViewFactoryTest.sshtml-en-US,views/TestingViewExtensions/ViewFactoryTest.sshtml,TestingViewExtensions/ViewFactoryTest.sshtml-en-US,TestingViewExtensions/ViewFactoryTest.sshtml
      Root path: /home/travis/build/NancyFx/Nancy/tools/xunit/

Is there a way to override that?

@akoeplinger override what? The tests uses views, which need to be located on a relative path to the executing application.

@akoeplinger oh @khellang pointed out what I missed.. the invalid root path =)

I think https://github.com/NancyFx/Nancy/blob/4c8d8e7b01d5e58f5e99c91799e06dca63e0bd31/src/Nancy/DefaultRootPathProvider.cs#L19 is the culprit. I assume that when the tests run in a separate AppDomain, that path points to the test dll path, but without it it points to where xunit.console.exe lives.

@akoeplinger yep, that's the same thing I'm looking at right now =)

I pushed a new version which simply copies xunit.console.exe to the test directory so the base directory of the AppDomain is the expected one. Looks like everything is green now :)

Thanks :heart:


not fetching members

FAILED: Members didn't arrive in time.
TASK: {"args":[],"options":{"priority":5,"weight":1,"expiration":null,"id":"-etqf682pnr7"},"retryCount":0}
Error [GuildMembersTimeout]: Members didn't arrive in time.
at Timeout._onTimeout (C:\Users\epicmines33\Desktop\utils discord bot\node_modules\discord.js\src\managers\GuildMemberManager.js:267:16)
at listOnTimeout (node:internal/timers:564:17)
at process.processTimers (node:internal/timers:507:7) {
code: 'GuildMembersTimeout'
}
thats the error i got, am i doing something wrong??

Hey @epicmines33, can you provide a code sample so I can see if the issue is coming from your end, mine, or discords?
Additionally have you configured the GUILD_MEMBERS intent correctly so your bot can fetch guild members?


Master

Added repeating sections for weapons and advanced skills, and a custom template roll

The way to make sure you handle the merge conflicts is to do a pull from master before making a push. If there are conflicts, they will show up there. If they do, you handle the merge and make a new commit with the changes to handle the merge. Then you make the Pull Request, and it should merge automatically with no conflicts.


[test] Invert stdlib_dir conditional sense.

In #32903, a substitution pseudovariable was introduced to refer to the
path containing Swift.swiftmodule. Since builds on Linux put this file
in a path with a subdirectory named after the architecture name -- and
presumably builds on mac OS do not, a conditional was required to
distinguish these two cases.
However, builds on OpenBSD for example also put Swift.swiftmodule in a
similar subdirectory like Linux. Thus, invert the sense of this
conditional: if mac OS, refer to the path without architecture name,
otherwise in all other cases (and therefore all other platforms), refer
to the architecture name subdirectory.

cc @artemcm

Makes sense to me
@swift-ci smoke test

@swift-ci smoke test

@swift-ci Please test Windows platform

Windows CI ran out of disk space. ⛵


how to train our dataset

hi i have my own dataset can someone please provide the procedure for how can we train our dataset

@Helsinki please @veer66 @jorgtied @TommiNieminen @Traubert  please provide support ,i have large dataset i want to train it using OpusMT i did all installation and run server.py for pretrained model now i have to train my own dataset please provide support on that

According to the readme this could be a tricky path :
"... but documentation needs to be improved. Also, the targets require a specific environment and right now only work well on the CSC HPC cluster in Finland."
How about first using MarianMT ?

Hii ,
Thanks for response.
I have trained model for Indian and multiple Asian languages using marianMT
and able to translate text ,PDF file and Docx file and also text file ..
Thanks for providing such an amazing framework you worked great.
Thanks
Regards,
Akshay Bonde
9860737353
Software Engineer, Pune, India
On Sat, Oct 28, 2023, 11:17 PM Pierre @.***> wrote:

According to the readme this could be a tricky path :
"... but documentation needs to be improved. Also, the targets require a
specific environment and right now only work well on the CSC HPC cluster in
Finland."
How about first using MarianMT https://marian-nmt.github.io/docs/ ?
—
Reply to this email directly, view it on GitHub
https://github.com/Helsinki-NLP/OPUS-MT-train/issues/89#issuecomment-1783882275,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5X474O5WZM5K5IQFU6DCTTYBVAL5AVCNFSM6AAAAAAVG4LVDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTHA4DEMRXGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Questions about using caffe-deconvnet

Thanks for releasing your excellent work. I have run the demo in the deconvnet-python-demo file folder ,and I got the outputs. The following pictures are originated from “pool5” as shown in your python code.

Besides, I want know how to get the deconvolutional outputs from other layers’ feature map. I have tried to change some code in line 68 of the test_deconv.py(change pool5 to pool4). However, I met some errors here.

In addition, Could you tell me how to use other models to perform deconvolution and draw the outputs?
Thank you very much.

You'll have to change the model defined in invnet.prototxt to start at the correct layer (for example, pool4 instead of pool 5), which should be as simple as deleting a few extra layers.
To make this work with other models, you'll have to create the inverse model file for it (like the invnet.prototxt file) and connect the switches and other inputs to the model.

Thanks for your codes!I field to modify the new Caffe，got a lot of trouble, Where can I download the Caffe you used for deconvnet？3Q very much！

Hello@w20ss11
I have the same problem with you.Have you already solved it ?And Can you give me some advises to  work it out. 3Q very much.


Support Multiple Selection

Hey this may not be an issue. Does this control support multiple selections?

What features do you want?

Can i select multiple image at one go? Or just one at a time

It's not a good idea for this picker, because it has a crop view. How to show then in crop view when you select multipe images?

https://github.com/uzysjung/UzysAssetsPickerController may help, multiple selections

@Gingit thanks for the link


Uses estuary_client and has CLI

pestuary now uses https://pypi.org/project/estuary-client/
and has it's own pypi release with command line interface https://pypi.org/project/pestuary/

https://github.com/application-research/estuary-clients/tree/main/python

got it! didn't realize i had the other PR open, i'll close this one for the other


Restructuring module 5

BRANCH TEAM 2: Module 5 (Modules/module5_SPDI.py)
API removed. To be reviewed before progressing.
All unnecessary code removed using #, to be deleted once confirmed working then merged into main.

Main updated. Issue resolved


Fran's edits

Choose a PR Template - I did more edits than show here - I want to do a PR from my repo to your users/rahuls/groupquota repo - want to make sure I did this correctly. I fixed a few spelling issues and made a couple grammar fixes.  You said there is a table but I don't see that in the OR
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

HI Rahul- I want to make sure this PR is OK - Let me check the thread and the table - I can see all the thread and let's touch base. At least now I think we are connected. I merged with your group user instead of main repo. There ,is probably more in the scope I can add. Thanks, Fran


Fix example in README file

It was missing referencing request

Thanks @gimenete!!

Trigger happy on that close button, haha...


Automatically set executable permissions on commands

Avoid having to have do:"chmod a=rx *" on every as:command entry.
Signed-off-by: Daniel Bayley<EMAIL_ADDRESS>

Thanks for your contributing, merging.


Commit exceptions from Kafka

I was running multi-cohort tests and then suddenly kafka threw lots of these exceptions:
Wed Feb 10 22:14:31 GMT 2021 cocoMDS3 Exception OCF-KAFKA-TOPIC-CONNECTOR-0017 An unexpected error org.apache.kafka.clients.consumer.CommitFailedException was encountered while committing consumed event offsets to topic egeria.omag.server.cocoMDS3.omas.assetconsumer.outTopic: error message is Offset commit cannot be completed since the consumer is not part of an active group for auto partition assignment; it is likely that the consumer was kicked out of the group.
Wed Feb 10 22:14:31 GMT 2021 cocoMDS3 Exception OCF-KAFKA-TOPIC-CONNECTOR-0017 Supplementary information: log record id b371fb0f-7206-4f0b-b33b-0e059a5c43c3 org.apache.kafka.clients.consumer.CommitFailedException returned message of Offset commit cannot be completed since the consumer is not part of an active group for auto partition assignment; it is likely that the consumer was kicked out of the group. and stacktrace of
org.apache.kafka.clients.consumer.CommitFailedException: Offset commit cannot be completed since the consumer is not part of an active group for auto partition assignment; it is likely that the consumer was kicked out of the group.
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.sendOffsetCommitRequest(ConsumerCoordinator.java:1139)
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(ConsumerCoordinator.java:1004)
	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1495)
	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1443)
	at org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataEventConsumer$HandleRebalance.onPartitionsRevoked(KafkaOpenMetadataEventConsumer.java:528)
	at org.apache.kafka.clients.consumer.ConsumerRebalanceListener.onPartitionsLost(ConsumerRebalanceListener.java:198)
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.invokePartitionsLost(ConsumerCoordinator.java:331)
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.onJoinPrepare(ConsumerCoordinator.java:693)
	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:424)
	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:367)
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:508)
	at org.apache.kafka.clients.consumer.KafkaConsumer.updateAssignmentMetadataIfNeeded(KafkaConsumer.java:1257)
	at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1226)
	at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1206)
	at org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataEventConsumer.run(KafkaOpenMetadataEventConsumer.java:166)
	at java.lang.Thread.run(Thread.java:748)

It looks like it may have recovered - because afterwards I see re-registration and events being processed.
Wed Feb 10 22:17:14 GMT 2021 cocoMDS2 Exception OCF-KAFKA-TOPIC-CONNECTOR-0017 An unexpected error org.apache.kafka.clients.consumer.CommitFailedException was encountered while committing consumed event offsets to topic egeria.omag.server.cocoMDS2.omas.governanceengine.outTopic: error message is Offset commit cannot be completed since the consumer is not part of an active group for auto partition assignment; it is likely that the consumer was kicked out of the group.
Wed Feb 10 22:17:14 GMT 2021 cocoMDS2 Exception OCF-KAFKA-TOPIC-CONNECTOR-0017 Supplementary information: log record id cb38865b-9cfe-4355-a877-afe841364e82 org.apache.kafka.clients.consumer.CommitFailedException returned message of Offset commit cannot be completed since the consumer is not part of an active group for auto partition assignment; it is likely that the consumer was kicked out of the group. and stacktrace of
org.apache.kafka.clients.consumer.CommitFailedException: Offset commit cannot be completed since the consumer is not part of an active group for auto partition assignment; it is likely that the consumer was kicked out of the group.
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.sendOffsetCommitRequest(ConsumerCoordinator.java:1139)
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(ConsumerCoordinator.java:1004)
	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1495)
	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1443)
	at org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataEventConsumer$HandleRebalance.onPartitionsRevoked(KafkaOpenMetadataEventConsumer.java:528)
	at org.apache.kafka.clients.consumer.ConsumerRebalanceListener.onPartitionsLost(ConsumerRebalanceListener.java:198)
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.invokePartitionsLost(ConsumerCoordinator.java:331)
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.onJoinPrepare(ConsumerCoordinator.java:693)
	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:424)
	at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:367)
	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:508)
	at org.apache.kafka.clients.consumer.KafkaConsumer.updateAssignmentMetadataIfNeeded(KafkaConsumer.java:1257)
	at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1226)
	at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1206)
	at org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataEventConsumer.run(KafkaOpenMetadataEventConsumer.java:166)
	at java.lang.Thread.run(Thread.java:748)

Wed Feb 10 22:17:33 GMT 2021 cocoMDS5 Cohort OMRS-AUDIT-0112 A re-registration request has been received for cohort cocoCohort from server cocoMDS1 that hosts metadata collection e89b978d-da68-4aec-8001-3bb46f32aee9
Wed Feb 10 22:17:39 GMT 2021 cocoMDS6 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:17:39 GMT 2021 cocoMDS6 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Element
Wed Feb 10 22:17:39 GMT 2021 cocoMDS5 Information OMRS-AUDIT-0128 Configuration for an existing remote member from server cocoMDS1 for cohort cocoCohort is being refreshed into the enterprise connector manager.  It has a metadata collection id of e89b978d-da68-4aec-8001-3bb46f32aee9, a metadata collection name of Data Lake Catalog, the server type is Metadata Server and its owning organization is Coco Pharmaceuticals
Wed Feb 10 22:17:39 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Repository REST Services
Wed Feb 10 22:17:39 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Repository REST Services
Wed Feb 10 22:17:39 GMT 2021 cocoMDS5 Cohort OMRS-AUDIT-0112 A re-registration request has been received for cohort cocoCohort from server cocoMDS1 that hosts metadata collection e89b978d-da68-4aec-8001-3bb46f32aee9
Wed Feb 10 22:17:39 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Repository REST Services
Wed Feb 10 22:17:39 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Connected Asset Services
Wed Feb 10 22:17:39 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Connected Asset Services
Wed Feb 10 22:17:39 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Connected Asset Services
Wed Feb 10 22:17:39 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Catalog OMAS
Wed Feb 10 22:17:39 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Catalog OMAS
Wed Feb 10 22:17:39 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Catalog OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Consumer OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Consumer OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Consumer OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Owner OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Owner OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Owner OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Community Profile OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Community Profile OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Community Profile OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Glossary View OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Glossary View OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Glossary View OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Science OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Science OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Subject Area OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Subject Area OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Subject Area OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Governance Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Manager OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Manager OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Governance Program OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Governance Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Discovery Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Privacy OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Discovery Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Security Officer OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Project Management OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0130 The enterprise repository services are managing federated queries to the following list of servers: [cocoMDS5, cocoMDS2, cocoMDS1, cocoMDS6]
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Cohort OMRS-AUDIT-0112 A re-registration request has been received for cohort cocoCohort from server cocoMDS1 that hosts metadata collection e89b978d-da68-4aec-8001-3bb46f32aee9
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Manager OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Lineage OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Governance Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for IT Infrastructure OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for IT Infrastructure OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Project Management OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0130 The enterprise repository services are managing federated queries to the following list of servers: [cocoMDS3, cocoMDS5, cocoMDS1, cocoMDS6, cocoMDSx]
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Cohort OMRS-AUDIT-0112 A re-registration request has been received for cohort cocoCohort from server cocoMDS1 that hosts metadata collection e89b978d-da68-4aec-8001-3bb46f32aee9
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Project Management OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0130 The enterprise repository services are managing federated queries to the following list of servers: [cocoMDS3, cocoMDS5, cocoMDS2, cocoMDS1]
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Cohort OMRS-AUDIT-0112 A re-registration request has been received for cohort cocoCohort from server cocoMDS1 that hosts metadata collection e89b978d-da68-4aec-8001-3bb46f32aee9
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0128 Configuration for an existing remote member from server cocoMDS1 for cohort cocoCohort is being refreshed into the enterprise connector manager.  It has a metadata collection id of e89b978d-da68-4aec-8001-3bb46f32aee9, a metadata collection name of Data Lake Catalog, the server type is Metadata Server and its owning organization is Coco Pharmaceuticals
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0128 Configuration for an existing remote member from server cocoMDS1 for cohort cocoCohort is being refreshed into the enterprise connector manager.  It has a metadata collection id of e89b978d-da68-4aec-8001-3bb46f32aee9, a metadata collection name of Data Lake Catalog, the server type is Metadata Server and its owning organization is Coco Pharmaceuticals
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Repository REST Services
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0128 Configuration for an existing remote member from server cocoMDS1 for cohort cocoCohort is being refreshed into the enterprise connector manager.  It has a metadata collection id of e89b978d-da68-4aec-8001-3bb46f32aee9, a metadata collection name of Data Lake Catalog, the server type is Metadata Server and its owning organization is Coco Pharmaceuticals
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Connected Asset Services
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Repository REST Services
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Catalog OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Repository REST Services
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Connected Asset Services
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Consumer OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Connected Asset Services
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Catalog OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Owner OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Catalog OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Consumer OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Community Profile OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Consumer OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Owner OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Glossary View OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Owner OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Community Profile OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Science OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Community Profile OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Glossary View OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Subject Area OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Glossary View OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Subject Area OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Manager OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Science OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Governance Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Governance Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Subject Area OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Governance Program OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Discovery Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Manager OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Privacy OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Project Management OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Information OMRS-AUDIT-0130 The enterprise repository services are managing federated queries to the following list of servers: [cocoMDS5, cocoMDS2, cocoMDS1, cocoMDS6]
Wed Feb 10 22:17:40 GMT 2021 cocoMDS3 Cohort OMRS-AUDIT-0112 A re-registration request has been received for cohort cocoCohort from server cocoMDS1 that hosts metadata collection e89b978d-da68-4aec-8001-3bb46f32aee9
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Discovery Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Security Officer OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Asset Lineage OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Data Manager OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for IT Infrastructure OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Governance Engine OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Project Management OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Information OMRS-AUDIT-0130 The enterprise repository services are managing federated queries to the following list of servers: [cocoMDS3, cocoMDS5, cocoMDS1, cocoMDS6, cocoMDSx]
Wed Feb 10 22:17:40 GMT 2021 cocoMDS2 Cohort OMRS-AUDIT-0112 A re-registration request has been received for cohort cocoCohort from server cocoMDS1 that hosts metadata collection e89b978d-da68-4aec-8001-3bb46f32aee9
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for IT Infrastructure OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0133 Information about remote connector from server cocoMDS1 with metadata collection id e89b978d-da68-4aec-8001-3bb46f32aee9 has been refreshed in enterprise connector for Project Management OMAS
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Information OMRS-AUDIT-0130 The enterprise repository services are managing federated queries to the following list of servers: [cocoMDS3, cocoMDS5, cocoMDS2, cocoMDS1]
Wed Feb 10 22:17:40 GMT 2021 cocoMDS6 Cohort OMRS-AUDIT-0112 A re-registration request has been received for cohort cocoCohort from server cocoMDS1 that hosts metadata collection e89b978d-da68-4aec-8001-3bb46f32aee9
Wed Feb 10 22:18:15 GMT 2021 cocoMDS3 Event OMRS-AUDIT-8006 Processing incoming event of type NewRelationshipEvent for instance c0363127-24fc-4f24-b781-4b08fe1465ed from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:18:15 GMT 2021 cocoMDS3 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:18:15 GMT 2021 cocoMDS3 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Relationship
Wed Feb 10 22:18:15 GMT 2021 cocoMDS5 Event OMRS-AUDIT-8006 Processing incoming event of type NewRelationshipEvent for instance c0363127-24fc-4f24-b781-4b08fe1465ed from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:18:15 GMT 2021 cocoMDS6 Event OMRS-AUDIT-8006 Processing incoming event of type NewRelationshipEvent for instance c0363127-24fc-4f24-b781-4b08fe1465ed from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:18:15 GMT 2021 cocoMDS2 Event OMRS-AUDIT-8006 Processing incoming event of type NewRelationshipEvent for instance c0363127-24fc-4f24-b781-4b08fe1465ed from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:18:15 GMT 2021 cocoMDS2 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:18:15 GMT 2021 cocoMDS6 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:18:15 GMT 2021 cocoMDS2 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Relationship
Wed Feb 10 22:18:15 GMT 2021 cocoMDS6 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Relationship
Wed Feb 10 22:18:24 GMT 2021 cocoMDS6 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:18:24 GMT 2021 cocoMDS2 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:18:24 GMT 2021 cocoMDS3 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:18:24 GMT 2021 cocoMDS5 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:02 GMT 2021 cocoMDS2 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:02 GMT 2021 cocoMDS6 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:02 GMT 2021 cocoMDS3 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:02 GMT 2021 cocoMDS2 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: Updated Classification
Wed Feb 10 22:19:02 GMT 2021 cocoMDS6 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: Updated Classification
Wed Feb 10 22:19:02 GMT 2021 cocoMDS3 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: Updated Classification
Wed Feb 10 22:19:46 GMT 2021 cocoMDS3 Event OMRS-AUDIT-8006 Processing incoming event of type ClassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:46 GMT 2021 cocoMDS2 Event OMRS-AUDIT-8006 Processing incoming event of type ClassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:46 GMT 2021 cocoMDS5 Event OMRS-AUDIT-8006 Processing incoming event of type ClassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:46 GMT 2021 cocoMDS3 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:46 GMT 2021 cocoMDS3 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Classification
Wed Feb 10 22:19:46 GMT 2021 cocoMDS6 Event OMRS-AUDIT-8006 Processing incoming event of type ClassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:46 GMT 2021 cocoMDS2 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:46 GMT 2021 cocoMDS2 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Classification
Wed Feb 10 22:19:46 GMT 2021 cocoMDS6 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:46 GMT 2021 cocoMDS6 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Classification
Wed Feb 10 22:19:47 GMT 2021 cocoMDS6 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:47 GMT 2021 cocoMDS3 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:47 GMT 2021 cocoMDS2 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:47 GMT 2021 cocoMDS5 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:47 GMT 2021 cocoMDS2 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:47 GMT 2021 cocoMDS2 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: Updated Classification
Wed Feb 10 22:19:47 GMT 2021 cocoMDS6 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:47 GMT 2021 cocoMDS6 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: Updated Classification
Wed Feb 10 22:19:47 GMT 2021 cocoMDS3 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:47 GMT 2021 cocoMDS3 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: Updated Classification
Wed Feb 10 22:19:48 GMT 2021 cocoMDS6 Event OMRS-AUDIT-8006 Processing incoming event of type ClassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:48 GMT 2021 cocoMDS3 Event OMRS-AUDIT-8006 Processing incoming event of type ClassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:48 GMT 2021 cocoMDS6 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:48 GMT 2021 cocoMDS3 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:48 GMT 2021 cocoMDS2 Event OMRS-AUDIT-8006 Processing incoming event of type ClassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:48 GMT 2021 cocoMDS2 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:48 GMT 2021 cocoMDS5 Event OMRS-AUDIT-8006 Processing incoming event of type ClassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:48 GMT 2021 cocoMDS5 Event OMRS-AUDIT-8006 Processing incoming event of type ReclassifiedEntityEvent for instance abc58494-e027-4228-95f4-4bb907979803 from: OMRSEventOriginator{metadataCollectionId='e89b978d-da68-4aec-8001-3bb46f32aee9', serverName='cocoMDS1', serverType='Metadata Server', organizationName='Coco Pharmaceuticals'}
Wed Feb 10 22:19:48 GMT 2021 cocoMDS2 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:48 GMT 2021 cocoMDS2 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Classification
Wed Feb 10 22:19:48 GMT 2021 cocoMDS3 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:48 GMT 2021 cocoMDS3 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Classification
Wed Feb 10 22:19:48 GMT 2021 cocoMDS6 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:48 GMT 2021 cocoMDS6 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: New Classification
Wed Feb 10 22:19:48 GMT 2021 cocoMDS3 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:48 GMT 2021 cocoMDS2 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:48 GMT 2021 cocoMDS3 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: Updated Classification
Wed Feb 10 22:19:48 GMT 2021 cocoMDS2 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: Updated Classification
Wed Feb 10 22:19:48 GMT 2021 cocoMDS6 Event OMAS-GOVERNANCE-ENGINE-0019 The Governance Engine Open Metadata Access Service (OMAS) has sent event of type Metadata change event
Wed Feb 10 22:19:48 GMT 2021 cocoMDS6 Information OMAS-GOVERNANCE-ENGINE-0017 The Governance Engine Open Metadata Access Service (OMAS) sent a metadata change event to listening Open Watchdog Governance Action Services: Updated Classification
Wed Feb 10 22:20:38 GMT 2021 cocoMDS3 Security OPEN-METADATA-SECURITY-0011 User calliequartile is not authorized to access asset ab7b053f-e2f1-4d5e-a3b1-ec401fd0f016

It could be that this needs to be a logMessage() rather than a logException() to avoid the stack trace -and/or an additional message to say it is recovering?

I tend to see these when I've had.a server frozen in the debugger for a long time.
These are the exceptions we asked Billy to include - I must admit I have frequently looked at them and wondered whether we got this right - I think a log entry might have been more sensible. ISTR Billy asking whether we really wanted them at the time - sorry @wbittles, I think you were right!

I was using the debugger at the time so that does tally :)

If we can't commit, something didn't get processed - could be reading a message from queue, or sending an update. If the former it will likely be reprocessed when we come back, (or via a replica). if it's an update we should find out at sometime in the future.
So in normal op we should recover.. but at the sametime would we expect it to happen normally? If there are kafka outages do we assume they are known? Or should we log anyway? Is it another level of detail down? Do we just keep counters? I think it's pretty tough to get that right. I think I'd be inclined to go with it as coded....

It's only being thrown when consuming a message, and can be caused by a few different scenarios.
If we end up in this state during a normal use case , with messages actually consumed and in the connectors buffer, will be consumed again and duplicated in the buffer. We should at least log that this has occurred.
However, like Graham, I've only ever seen it during a debugging session but it kills the connector thread I'm trying to debug, so it's worth fixing even if it does only occur during a debug session.In the cases I encounter the transaction is actually empty, so I suspect simply checking if there are actually any messages that need committing, and if there are we will just simply log that the event occurred.

Thanks for fixing this @wbittles


Add test case for JSON resource marshaling

Hi @gmlewis, I have added test case for TeamListTeamMembersOptions. So, pls accept my PR for Hackoctober fest contribution.
Helps: #55

Thank you @gmlewis for all of your support!!!!


Use a standard like printf or cout instead of a class for the information output

An option would be to use our own ostream (a class inheriting from ostream). This way it is possible to use the << operator for output.

Perhaps we should also think about using a BOOST library (boost.org).


Automated Package Upgrade

:tada: This PR is included in version 2.2.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Reviews of input data check and format

Here is an extensive review of common.scad, vectors.scad, arrays.scad and their regression test codes. The changes were mostly in input data check and format. Some few functions got more changes either to adapt them to the new asserts or because a better (faster, simpler) code was found. Some inserted asserts have side effects on other file tests:

test_math.scad fails trying to do a vmul of vectors with different lengths;
the same happens with test_shapes.scad and test_shapes2d.scad;

I believe that trying to multiply vectors of different length should be considered an error. I didn't dig into the offending codes yet to see what is wrong.
Another change was moving add_scalar from vectors.scad to arrays.scad. It is in fact an array operation. Some few documentation examples and test codes were added. Some function argument names were changed to keep them consistent with the names they have in other similar functions. That name changes were not as extensive as I would like but are advisable to favor users.
Most, but not all, changed function codes are followed by a comment with a short summary of the changes done.  Those comments always start with:
//***
I can eliminate those comments before a merge is done.

I did some correction in the code but am unable to submit it again. How I "delete" an unsuccessful PR?

Lemme try deleting it.

I can close it without merging.


chore: allow machine auth to generate CSRF token

The celery task get permissions through machine_auth.
The 'cache-warmup' task needs to call the '/api/v1/chart/warm_up_cache' endpoint .However, this endpoint is non GET requests and is therefore protected by CSRF.
Hence, when machine_auth retrieves the auth cookies, it also needs to generate a CSRF token.
This ensures that the Celery task can operate successfully.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Configure the cache-warmup task.
The Celery task successfully executed the fetch_url action.

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

It's related to #28706


[5.8][Index] Prevent re-indexing system modules repeatedly

If a module was first read using the adjacent swiftmodule and then reloaded using the swiftinterface, we would do an up to date check on the adjacent module but write out the unit using the swiftinterface. This would cause the same modules to be indexed repeatedly for the first invocation using a new SDK. On the next run we would instead raad the swiftmodule from the cache and thus the out of date check would match up.
The impact of this varies depending on the size of the module graph in the initial compilation and the number of jobs started at the same time. Each SDK dependency is re-indexed and reloaded, which is a drain on both CPU and memory. Thus, if many jobs are initially started and they're all going down this path, it can cause the system to run out of memory very quickly.
Resolves rdar://103119964.
(cherry picked from commit 806e6b0b725ccea060cb882ffa4e967b4ea585e5)

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows platform


Allow Embeded Fileter in Sharepoint

I have a great dashboard, but it has alot of data. I would like to embed into SharePoint but Filter to select items and I can via a URL but not via the Embed

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

ID: 0fc5abbd-e082-d1e1-109d-6f6cec8854a1
Version Independent ID: f8affce3-98f2-0cc6-b4de-d9af7ced0fbe
Content: Embed with report web part in SharePoint Online - Power BI
Content Source: powerbi-docs/service-embed-report-spo.md
Service: powerbi
GitHub Login: @markingmyname
Microsoft Alias: maghan

Thanks for your comment, @rosskingplatt . This looks like a support request rather than documentation feedback. You might find a solution in the Power BI Community, found at https://community.powerbi.com. If not, you can get support by going to https://support.powerbi.com.


[GWS 1] browserSync configuration is broken for proxy

@scallemang has found bug after integration starter in Wordpress.
Will be resolved ASAP

related to  #4

Well...
Reason? This bug happen, because HMR can't find hot-update.json.
Why? publicPath is wrong in your case
Solution: if you proxying exist server  where Wordpress installed you need to change publicPath:
publicPath: http://localhost:8080/wp-content/themes/THEME_NAME/assets/js/
You can find related problems and fixes below:
discussion 1
discussion 2


U2Net model (link broken)

Hi team,
Nice work! I am trying to reproduce your results but I can not download the U2Net model from https://github.com/danilodegoede/fact-team3/blob/main/cgn_framework/scripts/download_weights.sh . It seems that the first link is broken. I see that you are using the same link with the original paper. Was it functional when you did this study?
Thank you,
Spyros

Hi Spyros,
It seems that the public access to the link may have been revoked for some reason. Alternatively, you can download the model from U2Net's repository here. The repo link is here. Hope this helps!
(We tried automating this bit via the new link - but gdown causes permission issues so best to download it manually, for now.)

Thank you Piyush!


Typo line 68

Hey,
seems like the line 68 has a typo :
csv_colums instead of csv_columns
init process is crashing because of this.

Thanks!


Differentiate failures when Decrypting a JWE

IDX10609 can be thrown for multiple situations:

algorithm was not supported
no keys were found

Users have hit this, differentiating would make diagnostics simpler.


RING-44448 - export_s3_keys.sh improvements

RING-44448 - keep raw files option
RING-44448 - determine the IP to query for bucketd
RING-44448 - basic error logs for each RID and bucket
I'm opening this as a draft PR for us to discuss and for some initial testing.

It asks about raw files up front and keeps them all or none.
Uses ss to determine if port 9000 is bound to a specific IP or not.

Matches [::]:9000for when ipv6 is enabled, or disabled via sysctl.
Matches <IP_ADDRESS>:9000 when ipv6 is disabled via grub and [::] will not appear in ss output.

There is a very basic log output for INFO, WARNING and ERROR.

A basic RAW_COUNT vs. PROCESSED_COUNT is performed.
Empty buckets are logged as WARNINGS.

Currently the script will report any failures that occurs into the RID_${RID}.log as well as the ${bucket}.log file, then it will exit with a specific RC code as defined in the script. This "fail early" logic will stop the processing of the RAFT session and report back which buckets have not yet been processed at the time of the ERROR and exiting the script.

Currently, the script has a hardcoded s3utils version which has to be bumped when the offline archive bundles a newer version.
Options:

Manage the script by a github action. When the s3utils version is bumped, the export_s3_keys.sh would get a the new versioned hardcoded.
Manage export_s3_keys.sh as a Jinja template. Would make the script deployed/updated by Ansible, potentially having an older version if Ansible is not used.

Check container hosts local registry for all s3utils versions. Determine the highest one, and use it.

Something like:
vercomp () {
    if [[ $1 == $2 ]]; then
        return 0
    fi
    local IFS=.
    local i
    local ver1=($1)
    local ver2=($2)
    for ((i=${#ver1[@]}; i<${#ver2[@]}; i++)); do
        ver1[i]=0
    done
    for ((i=0; i<${#ver1[@]}; i++)); do
        if [[ -z ${ver2[i]} ]]; then
            ver2[i]=0
        fi
        if ((10#${ver1[i]} > 10#${ver2[i]})); then
            return 1
        fi
        if ((10#${ver1[i]} < 10#${ver2[i]})); then
            return 2
        fi
    done
    return 0
}

S3UTILS_VERSION=($(podman images registry.scality.com/s3utils/s3utils --format '{{ .Tag }}'))
echo found versions ${S3UTILS_VERSION[*]}
while [[ ${#S3UTILS_VERSION[@]} -gt 1 ]]; do
    element1=${S3UTILS_VERSION[0]}
    for ((i=1; i<${#S3UTILS_VERSION[@]}; i++)); do
        element2=${S3UTILS_VERSION[i]}
        vercomp $element1 $element2
        case $? in
            1) S3UTILS_VERSION=("${S3UTILS_VERSION[@]:0:$i}" "${S3UTILS_VERSION[@]:$i+1}"); i=$((i-1));;
            2) S3UTILS_VERSION=("${S3UTILS_VERSION[@]:1:$i}" "${S3UTILS_VERSION[@]:$i+1}"); i=$((i-1));;
        esac
    done
done

@scality-fno @fra-scality any additional suggestions before we widen the pool of reviewers?

haven't been able to test this one... do you have a lab handy with everything in place from this "dev" environment? That said, gave a few suggestions (pointless, essentially). Question: is the double tee pipeline used for logging somewhat redundant?

Sort of, but not exactly. There are items that are only in the RID logs because they are not specific to a single bucket. THe RID log however does contain every log entry from each bucket. Below is the breakdown of errors for a bucket log, and then the additional log entries the RID log will have.
TL;DR

The <bucket>.log contains

Everything for its own bucket, including:

INFO about Starting/Completing export of bucket
INFO (or) WARNING about verifyBucketSproxydKeys.js scan completion
ERROR about failed to export keys or process keys
INFO/WARNING about raw and processed count comparisons
INFO about keep/remove of raw files

The PID_<PID>.log contains

Everything inside each <bucket>.log
Only present in the PID logs:

INFO/ERROR about finding bucketd instance (valid IP etc.)
INFO about the list of buckets per Raft ID
ERROR about Raft ID empty (ENOENT / no buckets found)
ERROR list of all unprocessed buckets whenever dumping the entire RID does not end successfully

Opening this up to a wider audience.