[custom-devices] general improvements, add custom-devices subcommand, better error handling

generally improves the custom devices feature
adds flutter subcommand for custom-devices management:

flutter custom-devices list lists the configured custom devices

can be used to check for errors
will also output the path of the config

flutter custom-devices reset

resets the configured custom devices config to default & creates a backup

flutter custom-devices add

either supply a json-formatted string as an argument to the --json parameter
or configure using an interactive, guided device setup
that guided setup will by default setup a ssh device, i.e. it won't ask for the values of every custom device config option, but rather for things like the ssh username & hostname and generally provide some good defaults for ssh devices

flutter custom-devices delete

deletes a custom-devices file based on the device id

better error checking when loading the config & better error messages
if anything goes wrong while loading a CustomDeviceConfig, a JsonRevivalException will be thrown with an error message describing the error (like Expected 'pingSuccessRegex' to be null or string-ified regex.)
that error will also be catched and expanded a bit by CustomDevicesConfig.devices so the outputted error message may look like this: Could not load custom device from config index 0: Expected 'pingSuccessRegex' to be null or string-ified regex.

fixes #79406
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

Great work! I have one feedback about custom-devices.schema.json. There may be some reason, but I thought enabled is more intuitive than disabled ｗhen I first saw it.
          "disabled": {
            "description": ~,
            "type": "boolean"
            "type": "boolean",
            "default": false
          },

Great work! I have one feedback about custom-devices.schema.json. There may be some reason, but I thought enabled is more intuitive than disabled ｗhen I first saw it.

Thanks! Yeah, the style guide also mentions this, I chose to ignore it because I thought it'd be weird for a field to default to "true" if omitted, but you're probably right I should've called it enabled instead. Also leads to some awkward double negatives in the code
I'll change it 👍

this should be ready to be reviewed now @jonahwilliams (just fyi)

Awesome, will take a look at this tomorrow!

FallThroughError should be an Exception type if it is intended to be caught.

I see, in the one instance where I throw it, it's not intended to be caught (I mean I don't know what to do when the command is run on something other than macOS, windows or linux)
Also I did something wrong while rebasing (somehow I rebased master on top of custom-device-improvements instead of the other way around), all the master commits showed up in this PR and somehow the bot requested two authors of the commits for review. Maybe you can remove the two from the reviewer list? @jonahwilliams

@ardera Is this ready for another review pass?
FYI @eseidel

@zanderso yep it's ready

@ardera I would love to see an article in our Wiki (to start) with a tutorial on how to use this.

@ardera I would love to see an article in our Wiki (to start) with a tutorial on how to use this.

sure, good idea!


Updates the title and lints the AutoML text classification model evaluation notebook

This PR is being made to resolve the review issues being faced with the notebook "official/model_evaluation/automl_text_classification_model_evaluation.ipynb" and includes the following updates:

Updates the title of the notebook
Lints the notebook

REQUIRED: Fill out the below checklists or remove if irrelevant

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[ ] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

Just saw the commit with gcpc version 1.0.25. The latest version is 1.0.26. Please update accordingly.

Just saw the commit with gcpc version 1.0.25. The latest version is 1.0.26. Please update accordingly.

Please ignore this PR. This PR was made to try to resolve the review issues being faced on another PR(#1195) related to linting. The final version on the notebook would based on the PR #1195.


Domain name change for serial console

Hi team, on the cell that explains what to do when the client-side error is "Web socket is closed or could not be opened.", it is pointed out to enable ".console.azure.com" on the customer firewall however, lately we are finding there was a domain name change on this and now the entry that needs to be added on the firewall is ".serialconsole.azure.com".
Can this be updated? Also, can you notify all the customers about this? we are having support volume getting raised due to this.
Thanks.
[Enter feedback here]

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

ID: 7579df88-20c0-3b86-dcd3-50c4a3ff8da7
Version Independent ID: 6fc4aa33-9ca4-e3c6-6e62-393142880647
Content: Azure Serial Console errors - Virtual Machines
Content Source: support/azure/virtual-machines/serial-console-errors.md
Service: virtual-machines
GitHub Login: @genlin
Microsoft Alias: genli

@glimoli, I will update the article as soon as possible.


fix seeds route and add guideline

Basics

[ ] I added a line to changelog.md
[ ] The PR is rebased with current master.
[ ] Details of what you changed are in commit messages.
[ ] References to issues, e.g. close #X, are in the commit messages and changelog.
[ ] The buildserver is happy.

Checklist

[ ] I have installed and I am using pre-commit hooks
[ ] I fully described what my PR does in the documentation
[ ] I fixed all affected documentation
[ ] I fixed the introduction tour
[ ] I wrote migrations in a way that they are compatible with already present data
[ ] I fixed all affected decisions
[ ] I added automated tests or a manual test protocol
[ ] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[ ] I mentioned every code or binary not directly written or done by me in reuse syntax
[ ] I created left-over issues for things that are still to be done
[ ] Code is conforming to our Architecture
[ ] Code is conforming to our Guidelines
[ ] Code is consistent to our Design Decisions
[ ] Exceptions to any guidelines are documented

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] I've read through the whole documentation
[ ] I've checked conformity to guidelines

jenkins build please

jenkins build please

jenkins build please

jenkins build please

jenkins build please

rebasing was missing, so hopefully the flaky e2e test is now fixed (#746)

@4ydan is the route maybe used somewhere in the tests? Already failing 4x

i think a new test has been added after creating this PR that references on /seeds/new. i changed the test and hopefully all of them will pass now

Superb! :heart:


Fix Version for Piriform.CCleaner

Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

Faulting application name: CCleaner64.exe, version: <IP_ADDRESS>58, time stamp: 0x656f370a
Faulting module name: CCleaner64.exe, version: <IP_ADDRESS>58, time stamp: 0x656f370a
Exception code: 0xc0000005
Fault offset: 0x000000000035bda4
Faulting process id: 0x26a4
Faulting application start time: 0x01da2ed68849a3f2
Faulting application path: C:\Program Files\CCleaner\CCleaner64.exe
Faulting module path: C:\Program Files\CCleaner\CCleaner64.exe
Report Id: 4ec01e5f-7567-46aa-9410-06db1b9892e9
Faulting package full name:
Faulting package-relative application ID:

Unfortunately it did not run when launched.

@stephengillie - I'm certain this has to be a pipelines error, because the only change is to the version, and in Windows Sandbox (usng Tools/PRTest.ps1) installs and launches it properly

Hi @Trenly,

Current manifest version 6.19 has 2 parameters, which is greater than this PR's version number 's 1 parameters.

Is this intentional?
(Automated response - build 486)


Registers templates with setuptools

See issue #37 for details.

@domenkozar You closed the related issue but did nor merge. What is the plan ?


Performance : Prevent DOM reflow on import preview

Currently, when the import preview is huge (i.e. thousands of rows), it forces the browser to do substantial DOM reflow. This greatly slows down the browser as it tries to resize the preview table (and the whole page) over and over again as it prints new DOM elements.
To improve performance, you can set table.import-preview's display to none first, and then set it to table later on after the whole table has been loaded.
That is, add this before the table is loaded
<style>
  table.import-preview {
    display:none;
  }
</style>

(or add this in import.css), and then add at the end of import_export/import.html
  <script type="text/javascript">
    (function() {
      var import_previews = document.querySelectorAll('table.import-preview')
      for (var i = 0; i < import_previews.length; i++) {
        import_previews[i].style.display = 'table'
      }
    })();
  </script>

You lost me at DOM (🤣 ), but anything to speed up table rendering sounds great! Anybody care to submit a PR for this?

Any idea what the downsides to this would be?

I understand there can be a lot of reflow but not sure about hiding and displaying table.  Could table-layout: fixed; help?

@andrewgy8 the down side is if javascript is disabled, then the preview will never show up :)

@bmihelac i'll try that out and will let you know how it goes :) thanks !

@bmihelac i just tried
<style>
  table.import-preview {
    table-layout: fixed;
  }
</style>

but the whole page was still getting longer and longer as new rows are being flushed by the HTTP response

How about setting table.import-preview's display to none using JS, so nothing changes for JS-disabled users, but everyone else gets smoother loading?


Month is -1 after setting local time, for what?

i see this in code:
void ESP32Time::setTime(int sc, int mn, int hr, int dy, int mt, int yr, int ms) {
   // seconds, minutes, hours, days, months, years $ microseconds(optional)
   // ie setTime(20, 34, 8, 1, 4, 2021) = 8:34:20 1/4/2021
   struct tm t = {0}; // Initialize it to all 0's
   t.tm_year = yr - 1900; // This is year-1900, so 121 = 2021
   t.tm_mon = mt - 1;
   t.tm_mday = dy;
   t.tm_hour = hr;
   t.tm_min = mn;
   t.tm_sec = sc;
   time_t timeSinceEpoch = mktime(&t);
   setTime(timeSinceEpoch, ms);
}

for how reason is t.tm_mon = mt - 1;?
If I set the date, I read a date with last month...

https://www.cplusplus.com/reference/ctime/tm/
tm_mon range is 0 - 11
#13


Schedule task for one-off execution at specified time

 Issue by magaton
Monday Nov 22, 2021 at 13:16 GMT
Originally opened as https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/2373

Guidelines
Feature description (Mandatory)
There is currently no way to schedule a statement to be executed at the specified time
Considered alternatives
apoc.perodic.submit, does not accept time
apoc.periodic.countdown requires statement to return 0.
How this feature can improve the project?
I would like to schedule an update in the graph.

Yes, there is no proper job scheduling facility.
However, you can use apoc.cypher.doIt in combination with apoc.util.sleep and Cypher temporal functions to schedule something like this:
WITH
  localdatetime({
    year: 2024, month: 11, day: 19,
    hour: 11, minute: 7, second: 0
  }) AS target,
  localdatetime() AS now
WITH now, target, duration.inSeconds(now, target).milliseconds AS inMillis
CALL apoc.cypher.doIt("CALL apoc.util.sleep($inMillis) CREATE (w:WaitForMe) RETURN w", {inMillis: inMillis}) YIELD value
RETURN value

cf.

https://neo4j.com/docs/cypher-manual/current/functions/temporal/#functions-localdatetime
https://neo4j.com/docs/cypher-manual/current/functions/temporal/duration/#functions-duration-inseconds
https://neo4j.com/docs/cypher-manual/current/values-and-types/temporal/#cypher-temporal-accessing-components-durations

I recommend to check the times first to see if the timezone work out as expected, e.g. like this:
WITH
  localdatetime({
    year: 2024, month: 11, day: 19,
    hour: 11, minute: 7, second: 0
  }) AS target,
  localdatetime() AS now
WITH now, target, duration.inSeconds(now, target).milliseconds AS inMillis
RETURN RETURN *


Move documentation to mdBook

Installing dependencies
cargo install mdbook
cargo install mdbook-katex
cargo install mdbook-linkcheck

Locally serving the book
mdbook serve --open

Potentially, ~/.cargo/bin needs to be added to the PATH.

@sshine, perhaps we can figure out (or you already know) how to automatically build and deploy the mdBook. I think it'd be nice if it were hosted on triton-vm.org/specs.

For PRs, there's this CI hook.
The deployment hooks on that page speak only of GitHub/GitLab Pages.
As for deployment on self-hosted infrastructure, both neptune.cash and triton-vm.org get polled with a frequency, fetch the git repository and run make, hence this empty Makefile. Adding the Triton VM docs as another hook here just requires running mdBook in that Makefile (and making sure it's installed on the web server).


Mux error logging & cardano-client ChangeLog.md file

This PR contains two small changes:

network-mux: don't wrap MuxErrors inside them selves.
cardano-client: removed ChangeLog.md from cabal

bors merge


Fix CommanderAgent

Not working when it is scheduled or manually run(check function typo).

...so it was a bug!  I thought I'd screwed up some of my detection and triggering logic elsewhere in the agent network!

Just fixed a similar bug in the SchedulerAgent.
Also, made it so that CommanderAgent can "configure" options containing nested hashes(see DataOutputAgent).

Both good catches, thank you for fixing these!


KOGITO-5574 - Dump persistence generated classes to disk with Quarkus

KOGITO-5574
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Your code is properly formatted according to this configuration
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

How to retest this PR or trigger a specific build:

Run all builds
Please add comment: Jenkins retest this

Run (or rerun) specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] tests

Quarkus LTS checks
Please add comment: Jenkins run LTS

Run (or rerun) LTS specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] LTS

Native checks
Please add comment: Jenkins run native

Run (or rerun) native specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

The (build) Runtimes check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

Jenkins run apps tests
Jenkins run runtimes tests

Jenkins rerun apps tests
Jenkins rerun runtimes tests

The (build) Apps check has failed. Please check the logs.

Jenkins rerun apps tests

The (build) Examples check has failed. Please check the logs.

Jenkins rerun examples tests

Everything green.


Graphs

How can I "create" and "update" graphs in an xlsx files?

@dlion Thanks for your issue, this library doesn't support to create or update charts in xlsx. I intend to add this function next. Try to open a pre-designed document that includes the chart, modify the value referenced by the chart if you can in current.

I need to write a tool to automatize some steps.
I need to add a value in a row on the sheet1, looking for a certain sheet (by name for example), adding in it some values, update a chart, switch to another sheet, add the same values and update 2 charts, switch to another sheet and modify some values.
Is an huge job so I wish to automatize it.
Do you have any documentation to read how xlsx files works? Thanks in advantage!

The xlsx file follows the OOXML specification. XML is compliant with part 1 of the 4th edition of the ECMA-376 Standard for Office Open XML. Use DrawingML to generate charts.

@dlion Hi, I have added new function AddChart() to use this please reference godoc. This is just an initialization of the chart support and I'll continue to optimize this.

Is there any functionality for changing the chart? For example, the ChangeChart () function?


Support Laravel 5.5 to 6.0

Drop support for PHP 7.0, as the newer PHPUnit versions need the : void return type hint
Include time measurement functionality from newer Laravel
Pass \Illuminate\Contracts\Events\Dispatcher to parent constructor

Travis seems not to run anymore, can you re-enable it?

@svenluijten can you take a look?

Hi @spawnia! I'm not employed at OnlinePets anymore, so I don't have write-access to this repository. Maybe @thomasmoors or @MartijnBastiaansen can help you 🙂

Hi @spawnia ,
We aren't maintaining this module anymore. Please feel free to pick it up and maintain it yourself, I will put this one into archive
Best regards,
Martijn

Thanks, I will publish my fork, keeping a reference to and license of your package.

Would you be so kind and include a reference to https://github.com/mll-lab/laravel-conditional-migrations at the top of your README? I plan to maintain this package further over there.
Thanks for the original, it has served us well.

Added a reference at the top of the readme.


Fix Ansible Driver's Vulnerabilities Issues

Creating this issue to fix the vulnerabilities for given below (Ansible) CVE's:-

CVE-2021-20191 : A flaw was found in ansible. Credentials, such as secrets, are being disclosed in console log by default and not protected by no_log feature when using those modules. An attacker can take advantage of this information to steal those credentials. The highest threat from this vulnerability is to data confidentiality. Versions before ansible 2.9.18 are affected.

CVE-2021-20178 : A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality.

CVE-2020-14365: A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x before 2.9.13, when installing packages using the dnf module. GPG signatures are ignored during installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability.

CVE-2021-3583 : A flaw was found in Ansible, where a user's controller is vulnerable to template injection. This issue can occur through facts used in the template if the user is trying to put templates in multi-line YAML strings and the facts being handled do not routinely include special template characters. This flaw allows attackers to perform command injection, which discloses sensitive information. The highest threat from this vulnerability is to confidentiality and integrity.

Ansible driver tested with 3.3.1.dev1 image and run 41 BVTAnsible suite successful.
https://eu.artifactory.swg-devops.com/artifactory/alm-docker-local/ansible-lifecycle-driver/3.3.1.dev1
Test results - http://testrail.mul.ie.ibm.com/testrail/index.php?/runs/view/4151.


use this model to noise reduction

I used this project for noise reduction, this was what I got, Its really amazing!!! Thanks for your implement.
|-samples
|-mix: mixture audio (clean speech + noise)
|-speech-actual: clean audio
|-speech-separated: separated audio
all the audios are from test set.
samples.zip

Thank you for your evaluation of this repository and keep in touch.

您好，我想问下您，您是用的多少张卡，每张卡多少batch_size，以及前几代你的loss大概是多少，我一直loss在17左右，我觉得应该是负数呀。


Add opt-in defaults, templates, type-checking

A prototype of a few different Task option declarative features:

type checking and coercion using Click's checkers.

value defaulting.

very simple templating language based on format-strings

The basic principle is that all features are opt-in, so there SHOULD be generally no change for tasks that do not opt-in. (Brian's robot linter did actually have a latent bug in it which was exposed by my code: he had specified incorrect defaults even though there was no default-handling mechanism that I am aware of. My code turned his incorrect, ignored defaults into real defaults and tests failed.)

Closing for now. We intend to revisit this but there are some additional considerations based on our conversation today.


connection refused

最近出现好多这个，一天得三四个邮件推送了，是接口问题吗，佬
Collecting requests
Downloading requests-2.32.3-py3-none-any.whl.metadata (4.6 kB)
Collecting charset-normalizer<4,>=2 (from requests)
Downloading charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (33 kB)
Collecting idna<4,>=2.5 (from requests)
Downloading idna-3.9-py3-none-any.whl.metadata (10 kB)
Collecting urllib3<3,>=1.21.1 (from requests)
Downloading urllib3-2.2.3-py3-none-any.whl.metadata (6.5 kB)
Collecting certifi>=2017.4.17 (from requests)
Downloading certifi-2024.8.30-py3-none-any.whl.metadata (2.2 kB)
Downloading requests-2.32.3-py3-none-any.whl (64 kB)
Downloading certifi-2024.8.30-py3-none-any.whl (167 kB)
Downloading charset_normalizer-3.3.2-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (141 kB)
Downloading idna-3.9-py3-none-any.whl (71 kB)
Downloading urllib3-2.2.3-py3-none-any.whl (126 kB)
Installing collected packages: urllib3, idna, charset-normalizer, certifi, requests
Successfully installed certifi-2024.8.30 charset-normalizer-3.3.2 idna-3.9 requests-2.32.3 urllib3-2.2.3
已设置为随机步数(24500~28000)
Traceback (most recent call last):
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/connection.py", line 199, in _new_conn
sock = connection.create_connection(
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/util/connection.py", line 85, in create_connection
raise err
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/util/connection.py", line 73, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/connectionpool.py", line 789, in urlopen
response = self._make_request(
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/connectionpool.py", line 495, in _make_request
conn.request(
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/connection.py", line 441, in request
self.endheaders()
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/http/client.py", line 1251, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/http/client.py", line 1011, in _send_output
self.send(msg)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/http/client.py", line 951, in send
self.connect()
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/connection.py", line 279, in connect
self.sock = self._new_conn()
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/connection.py", line 214, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f5126734190>: Failed to establish a new connection: [Errno 111] Connection refused
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/requests/adapters.py", line 667, in send
resp = conn.urlopen(
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/connectionpool.py", line 843, in urlopen
retries = retries.increment(
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/urllib3/util/retry.py", line 519, in increment
raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='api.m.taobao.com', port=80): Max retries exceeded with url: /rest/api3.do?api=mtop.common.getTimestamp (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f5126734190>: Failed to establish a new connection: [Errno 111] Connection refused'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 240, in
getBeijinTime()
File "main.py", line 98, in getBeijinTime
msg_mi += main(user_mi, passwd_mi, min_1, max_1)
File "main.py", line 193, in main
t = get_time()
File "main.py", line 224, in get_time
response = requests.get(url, headers=headers).json()
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/requests/api.py", line 73, in get
return request("get", url, params=params, **kwargs)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/requests/api.py", line 59, in request
return session.request(method=method, url=url, **kwargs)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/requests/sessions.py", line 589, in request
resp = self.send(prep, **send_kwargs)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-

一样的问题，最近几天都刷不了，也不知道是什么导致的。

taobao获取时间戳的API用不了了，换个获取时间戳的API或者本地获取就行了

taobao获取时间戳的API用不了了，换个获取时间戳的API或者本地获取就行了

这里是在哪里改呢，大佬

taobao获取时间戳的API用不了了，换个获取时间戳的API或者本地获取就行了

找到了找到了， 我先改上然后看看还会不会提示错误，谢谢！

怎么我获取了最新的代码还是运行失败，提示
Traceback (most recent call last):
File "main.py", line 240, in
getBeijinTime()
File "main.py", line 98, in getBeijinTime
msg_mi += main(user_mi, passwd_mi, min_1, max_1)
File "main.py", line 193, in main
t = get_time()
File "main.py", line 224, in get_time
response = requests.get(url, headers=headers).json()
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/requests/models.py", line 978, in json
raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

怎么我获取了最新的代码还是运行失败，提示 Traceback (most recent call last): File "main.py", line 240, in getBeijinTime() File "main.py", line 98, in getBeijinTime msg_mi += main(user_mi, passwd_mi, min_1, max_1) File "main.py", line 193, in main t = get_time() File "main.py", line 224, in get_time response = requests.get(url, headers=headers).json() File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/requests/models.py", line 978, in json raise RequestsJSONDecodeError(e.msg, e.doc, e.pos) requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

建议直接把时间戳改成从本地获取
run.yml：
- name: 开始
        run: |
          ...
          pip3 install pytz
          ...

main.py：
def get_time():
    utc_now = datetime.datetime.utcnow()
    beijing_tz = pytz.timezone('Asia/Shanghai')
    beijing_now = utc_now.replace(tzinfo=pytz.utc).astimezone(beijing_tz)
    t = int(beijing_now.timestamp() * 1000)
    return t


Instructions to add a loop are out of date.

Add a loop no longer appears on the design surface.  Loops, switches and conditions now appear under the Control grouping in Add an Action.

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

ID: f0c62935-f980-a27c-883b-bd826c5b327f
Version Independent ID: 5fc1bf17-8cd9-8cdb-72df-1c6a544a677a
Content: Add loops that repeat actions or process arrays - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-control-flow-loops.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Thanks @Johns-305! I have seen reports of this change on the forums today as well and confirmed it as such with the respective product group. We have now assigned this issue to the content author of this documentation to investigate further and take the right course of action.

@Johns-305 Thanks for your feedback! We have a work item on our backlog to update this content.
#please-close


Hybrid Azure AD join License requiered

I need to implement Hybrid Azure AD join in order to use SSO in Office 365 applications. What license do I need to get? If Azure AD Free enough or Azure AD P1 is required?.

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

ID: 72cdc251-618a-e84e-f40d-960b0ac69f99
Version Independent ID: 8cbaba3c-e883-2c71-28fb-f88db3fcaf7d
Content: How to plan hybrid Azure Active Directory join implementation in Azure Active Directory (Azure AD)
Content Source: articles/active-directory/devices/hybrid-azuread-join-plan.md
Service: active-directory
Sub-service: devices
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@javirivas80 Thanks for your feedback! We will investigate and update as appropriate.

Hey @javirivas80 please take a look at the pricing docs for more information on this.
https://azure.microsoft.com/en-us/pricing/details/active-directory/
Per the P1 summary :

Premium P1
Designed to empower organizations with more demanding identity and access management needs, Azure Active Directory Premium edition adds feature-rich enterprise-level identity management capabilities and enables hybrid users to seamlessly access on-premises and cloud capabilities. This edition includes everything you need for information worker and identity administrators in hybrid environments across application access, self-service identity and access management (IAM), and security in the cloud.

@javirivas80 So you will need premium p1 if you want seamless access on premise and cloud capabilities, which is sso with o365 apps.
Please let us know if there are anymore questions within the scope of this git issue. If not, I will be closing out this git issue by end of day today. Please reopen this git issue if you have anymore concerns. Thanks


AMD (requirejs) not working

I defined the path for require in the config.
require(['csv'], function (csv) { /* csv = undefined */ })
Added csv to the shim object, made it export 'CSV' as it is in the source code..
Require still not recognising csv for some reason

Its really strange, has CSV.js been tried with require.js?
Thanks!

To be honest I've never tried Require.js, so I just copied the output format that I think underscore.js uses. Let me look into this.

Ok thank you!

Could you by any chance throw me a skeleton RequireJS project with CSV loaded up? I'm lost :smile:

Ok will do.. I have been meaning to set up an empty skeleton project anyway.
(i'll let you know, should be done by end of day UK time)

Here you go as promised :).
https://github.com/matejkramny/angular-requirejs-starter

Thanks for the starter :+1: :smiley: :shipit:

Thanks god this bug fix 19 days ago.
@knrz When you release a version to bower?

@muzuiget 2 weeks ago. Version 3.6.3 has the fix.

@knrz But https://github.com/knrz/CSV.js/releases doesn't has the version tag, so bower can't install by #3.6.3

Oh whoops.

:+1:


newspaper library is not working

I want to use newspaper library for my rails project.
So I tried to use this gem but I got an error.
This is my code
require 'pycall/import'
include PyCall::Import

pyimport 'newspaper'

url = 'http://www.bbc.co.uk/zhongwen/simp/chinese_news/2012/12/121210_hongkong_politics.shtml'

article = newspaper.Article(url)
article.download()
article.parse()
print(article.text)

I got a following error
~/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/pycall-1.0.3/lib/pycall/pyobject_wrapper.rb:43:in `download': <class 'TypeError'>: download() missing 1 required positional argument: 'self' (PyCall::PyError)
        from ~/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/pycall-1.0.3/lib/pycall/pyobject_wrapper.rb:43:in `method_missing'
        from newspaper.rb:9:in `<main>'

Other libraries like math, pandas are working.
I have no idea if this is caused due to this gem, But native python code can be working.
OS: OSX High Sierra
Python: 3.6.4
Ruby: ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16
echo $PYTHON => /usr/local/bin/python3
newspaper3k (0.2.5)
pycall (1.0.3)

Hi. change your code newspaper.Article(url) to newspaper.Article.new(url) or newspaper.Article.(url) (dot after Article).

@umlx5h Rewrite newspaper.Article(url) to newspaper.Article.new(url) as @mephistobooks said.
@mephistobooks Thank you for your assistance.


--useSeparateProcesses

Hey! This plugin is awesome. I'm just having a little issue where I have a persistent DB connection between lambda invocations. So on the second invocation I get an error saying my DB connection already exists. With serverless-offline they have a --useSeperateProcesses flag described here that allows for seperate node process's to be run for each invocation. Is this possible with this plugin as well?

I haven’t come across this or worked it out yet.
Is it possible to only create the connection if it doesnt already exist? Since a node process could be reused on subsequent lambda invocations in AWS anyway.
Otherwise any suggestions on how this feature could work?

I actually just removed the dependency I had causing this issue, so I'll close for now :)


Rewrite all github.com/magma/community documents and community-related documents in the magma repository.

Most of the governance documents should live in the magma/community repository, not in the magma/magma repository, which is for code. However the community repo:

Has been archived since 2022
Hasn't been updated in a long time
Needs to host the charter

Tasks:

[x] Unarchive
[x] Check each document for stale data
[ ] Update TSC membership listing
[x] Migrate charter into this repository
[ ] Move community-related documents in the magma repo to the community repo

As I get deeper into the project I am rethinking it. The documents in the community repo are years behind the documents in the magma repo. What I should do is

review every community-related document in the magma repo
update the text of the README in the community repo to explain that the contents are useless
unarchive the community repo
verify that all files in the community repo also exist in the magma repo

Review each of the following:

[ ] ../community/CODE_OF_CONDUCT.md
[ ] ../community/CONTRIBUTING.md
[ ] ../community/Governance.md
[ ] ../community/Organization_of_Work.md
[ ] ../community/README.md
[ ] ../community/Reviewing.md
[ ] ../magma/CODE_OF_CONDUCT.md
[ ] ../magma/CONTRIBUTING.md
[ ] ../magma/DCO.md
[ ] ../magma/README.md
[ ] ../magma/REWARDS_PROGRAM.md
[ ] ../magma/SECURITY.md

Resolved: use a monorepo instead of a multirepo.

Code of conduct files have only a trivial syntax difference.

CONTRIBUTING.md:

big differences between the repos
the version in the magma repo is much more up to date

WTF: there also exists a repo called https://github.com/magma/Governance

The state of this list is a mess. I need to re-review and document every item.

Archived /magma/community repo

All remaining items have been reviewed and either implemented or I have decided they were defined before I full understood the project structure.


START_TIME and STOP_TIME in wrong order for COUVIS and COVIMS

2018-08-03 18:59:17 | pds.opus_import.main |--| ERROR | [COUVIS_0001 index row 892] time1 (2000-180T15:16:21.813) and time2 (2000-177T13:43:26.901) are in the wrong order - setting equal
2018-08-03 18:59:17 | pds.opus_import.main |--| ERROR | [COUVIS_0001 index row 893] time1 (2000-180T15:16:21.813) and time2 (2000-177T13:43:26.901) are in the wrong order - setting equal
2018-08-03 19:02:25 | pds.opus_import.main |--| ERROR | [COUVIS_0003 index row 12364] time1 (2001-333T00:08:16.120) and time2 (2001-330T19:00:25.208) are in the wrong order - setting equal
2018-08-03 20:13:16 | pds.opus_import.main |--| ERROR | [COVIMS_0001 index row 2448] time1 (2000-09-18T07:57:57.444) and time2 (2000-09-18T07:57:57.438) are in the wrong order - setting equal
2018-08-03 20:13:16 | pds.opus_import.main |--| ERROR | [COVIMS_0001 index row 2448] time1 (2000-09-18T07:57:57.444) and time2 (2000-09-18T07:57:57.438) are in the wrong order - setting equal
2018-08-03 20:13:53 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 1264] time1 (2000-12-17T03:40:45.506) and time2 (2000-12-17T03:40:45.503) are in the wrong order - setting equal
2018-08-03 20:13:53 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 1264] time1 (2000-12-17T03:40:45.506) and time2 (2000-12-17T03:40:45.503) are in the wrong order - setting equal
2018-08-03 20:13:54 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 1324] time1 (2000-12-17T06:25:39.438) and time2 (2000-12-17T06:25:39.435) are in the wrong order - setting equal
2018-08-03 20:13:54 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 1324] time1 (2000-12-17T06:25:39.438) and time2 (2000-12-17T06:25:39.435) are in the wrong order - setting equal
2018-08-03 20:14:06 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 1938] time1 (2001-01-01T23:50:18.045) and time2 (2001-01-01T23:50:18.039) are in the wrong order - setting equal
2018-08-03 20:14:06 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 1938] time1 (2001-01-01T23:50:18.045) and time2 (2001-01-01T23:50:18.039) are in the wrong order - setting equal
2018-08-03 20:14:13 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2336] time1 (2001-01-05T04:50:55.116) and time2 (2001-01-05T04:50:55.113) are in the wrong order - setting equal
2018-08-03 20:14:13 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2336] time1 (2001-01-05T04:50:55.116) and time2 (2001-01-05T04:50:55.113) are in the wrong order - setting equal
2018-08-03 20:14:20 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2717] time1 (2001-01-07T05:11:27.736) and time2 (2001-01-07T05:11:27.715) are in the wrong order - setting equal
2018-08-03 20:14:20 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2717] time1 (2001-01-07T05:11:27.736) and time2 (2001-01-07T05:11:27.715) are in the wrong order - setting equal
2018-08-03 20:14:20 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2719] time1 (2001-01-07T05:11:36.783) and time2 (2001-01-07T05:11:36.762) are in the wrong order - setting equal
2018-08-03 20:14:20 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2719] time1 (2001-01-07T05:11:36.783) and time2 (2001-01-07T05:11:36.762) are in the wrong order - setting equal
2018-08-03 20:14:20 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2721] time1 (2001-01-07T05:11:45.830) and time2 (2001-01-07T05:11:45.809) are in the wrong order - setting equal
2018-08-03 20:14:20 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2721] time1 (2001-01-07T05:11:45.830) and time2 (2001-01-07T05:11:45.809) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2738] time1 (2001-01-07T05:13:02.728) and time2 (2001-01-07T05:13:02.708) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2738] time1 (2001-01-07T05:13:02.728) and time2 (2001-01-07T05:13:02.708) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2740] time1 (2001-01-07T05:13:11.775) and time2 (2001-01-07T05:13:11.754) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2740] time1 (2001-01-07T05:13:11.775) and time2 (2001-01-07T05:13:11.754) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2742] time1 (2001-01-07T05:13:20.822) and time2 (2001-01-07T05:13:20.801) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2742] time1 (2001-01-07T05:13:20.822) and time2 (2001-01-07T05:13:20.801) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2761] time1 (2001-01-07T05:14:46.766) and time2 (2001-01-07T05:14:46.746) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2761] time1 (2001-01-07T05:14:46.766) and time2 (2001-01-07T05:14:46.746) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2763] time1 (2001-01-07T05:14:55.813) and time2 (2001-01-07T05:14:55.793) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2763] time1 (2001-01-07T05:14:55.813) and time2 (2001-01-07T05:14:55.793) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2782] time1 (2001-01-07T05:16:21.760) and time2 (2001-01-07T05:16:21.739) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2782] time1 (2001-01-07T05:16:21.760) and time2 (2001-01-07T05:16:21.739) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2784] time1 (2001-01-07T05:16:30.807) and time2 (2001-01-07T05:16:30.786) are in the wrong order - setting equal
2018-08-03 20:14:21 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2784] time1 (2001-01-07T05:16:30.807) and time2 (2001-01-07T05:16:30.786) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2803] time1 (2001-01-07T05:17:56.751) and time2 (2001-01-07T05:17:56.730) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2803] time1 (2001-01-07T05:17:56.751) and time2 (2001-01-07T05:17:56.730) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2805] time1 (2001-01-07T05:18:05.798) and time2 (2001-01-07T05:18:05.777) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2805] time1 (2001-01-07T05:18:05.798) and time2 (2001-01-07T05:18:05.777) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2807] time1 (2001-01-07T05:18:14.845) and time2 (2001-01-07T05:18:14.824) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2807] time1 (2001-01-07T05:18:14.845) and time2 (2001-01-07T05:18:14.824) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2824] time1 (2001-01-07T05:19:31.743) and time2 (2001-01-07T05:19:31.723) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2824] time1 (2001-01-07T05:19:31.743) and time2 (2001-01-07T05:19:31.723) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2826] time1 (2001-01-07T05:19:40.790) and time2 (2001-01-07T05:19:40.770) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2826] time1 (2001-01-07T05:19:40.790) and time2 (2001-01-07T05:19:40.770) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2828] time1 (2001-01-07T05:19:49.837) and time2 (2001-01-07T05:19:49.817) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2828] time1 (2001-01-07T05:19:49.837) and time2 (2001-01-07T05:19:49.817) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2845] time1 (2001-01-07T05:21:06.735) and time2 (2001-01-07T05:21:06.714) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2845] time1 (2001-01-07T05:21:06.735) and time2 (2001-01-07T05:21:06.714) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2847] time1 (2001-01-07T05:21:15.782) and time2 (2001-01-07T05:21:15.761) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2847] time1 (2001-01-07T05:21:15.782) and time2 (2001-01-07T05:21:15.761) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2849] time1 (2001-01-07T05:21:24.828) and time2 (2001-01-07T05:21:24.808) are in the wrong order - setting equal
2018-08-03 20:14:22 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2849] time1 (2001-01-07T05:21:24.828) and time2 (2001-01-07T05:21:24.808) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2866] time1 (2001-01-07T05:22:41.728) and time2 (2001-01-07T05:22:41.708) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2866] time1 (2001-01-07T05:22:41.728) and time2 (2001-01-07T05:22:41.708) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2868] time1 (2001-01-07T05:22:50.775) and time2 (2001-01-07T05:22:50.754) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2868] time1 (2001-01-07T05:22:50.775) and time2 (2001-01-07T05:22:50.754) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2870] time1 (2001-01-07T05:22:59.822) and time2 (2001-01-07T05:22:59.801) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2870] time1 (2001-01-07T05:22:59.822) and time2 (2001-01-07T05:22:59.801) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2889] time1 (2001-01-07T05:24:25.766) and time2 (2001-01-07T05:24:25.746) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2889] time1 (2001-01-07T05:24:25.766) and time2 (2001-01-07T05:24:25.746) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2891] time1 (2001-01-07T05:24:34.813) and time2 (2001-01-07T05:24:34.793) are in the wrong order - setting equal
2018-08-03 20:14:23 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 2891] time1 (2001-01-07T05:24:34.813) and time2 (2001-01-07T05:24:34.793) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3445] time1 (2001-01-07T09:28:27.630) and time2 (2001-01-07T09:28:27.615) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3445] time1 (2001-01-07T09:28:27.630) and time2 (2001-01-07T09:28:27.615) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3447] time1 (2001-01-07T09:28:36.677) and time2 (2001-01-07T09:28:36.662) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3447] time1 (2001-01-07T09:28:36.677) and time2 (2001-01-07T09:28:36.662) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3449] time1 (2001-01-07T09:28:45.724) and time2 (2001-01-07T09:28:45.706) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3449] time1 (2001-01-07T09:28:45.724) and time2 (2001-01-07T09:28:45.706) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3451] time1 (2001-01-07T09:28:54.767) and time2 (2001-01-07T09:28:54.752) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3451] time1 (2001-01-07T09:28:54.767) and time2 (2001-01-07T09:28:54.752) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3453] time1 (2001-01-07T09:29:03.814) and time2 (2001-01-07T09:29:03.799) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3453] time1 (2001-01-07T09:29:03.814) and time2 (2001-01-07T09:29:03.799) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3455] time1 (2001-01-07T09:29:12.861) and time2 (2001-01-07T09:29:12.843) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3455] time1 (2001-01-07T09:29:12.861) and time2 (2001-01-07T09:29:12.843) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3457] time1 (2001-01-07T09:29:21.905) and time2 (2001-01-07T09:29:21.890) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3457] time1 (2001-01-07T09:29:21.905) and time2 (2001-01-07T09:29:21.890) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3466] time1 (2001-01-07T09:30:02.622) and time2 (2001-01-07T09:30:02.608) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3466] time1 (2001-01-07T09:30:02.622) and time2 (2001-01-07T09:30:02.608) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3468] time1 (2001-01-07T09:30:11.669) and time2 (2001-01-07T09:30:11.654) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3468] time1 (2001-01-07T09:30:11.669) and time2 (2001-01-07T09:30:11.654) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3470] time1 (2001-01-07T09:30:20.716) and time2 (2001-01-07T09:30:20.699) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3470] time1 (2001-01-07T09:30:20.716) and time2 (2001-01-07T09:30:20.699) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3472] time1 (2001-01-07T09:30:29.760) and time2 (2001-01-07T09:30:29.745) are in the wrong order - setting equal
2018-08-03 20:14:33 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3472] time1 (2001-01-07T09:30:29.760) and time2 (2001-01-07T09:30:29.745) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3474] time1 (2001-01-07T09:30:38.807) and time2 (2001-01-07T09:30:38.792) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3474] time1 (2001-01-07T09:30:38.807) and time2 (2001-01-07T09:30:38.792) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3476] time1 (2001-01-07T09:30:47.854) and time2 (2001-01-07T09:30:47.836) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3476] time1 (2001-01-07T09:30:47.854) and time2 (2001-01-07T09:30:47.836) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3478] time1 (2001-01-07T09:30:56.898) and time2 (2001-01-07T09:30:56.883) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3478] time1 (2001-01-07T09:30:56.898) and time2 (2001-01-07T09:30:56.883) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3480] time1 (2001-01-07T09:31:05.945) and time2 (2001-01-07T09:31:05.930) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3480] time1 (2001-01-07T09:31:05.945) and time2 (2001-01-07T09:31:05.930) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3489] time1 (2001-01-07T09:31:46.660) and time2 (2001-01-07T09:31:46.646) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3489] time1 (2001-01-07T09:31:46.660) and time2 (2001-01-07T09:31:46.646) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3491] time1 (2001-01-07T09:31:55.707) and time2 (2001-01-07T09:31:55.690) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3491] time1 (2001-01-07T09:31:55.707) and time2 (2001-01-07T09:31:55.690) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3493] time1 (2001-01-07T09:32:04.751) and time2 (2001-01-07T09:32:04.737) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3493] time1 (2001-01-07T09:32:04.751) and time2 (2001-01-07T09:32:04.737) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3495] time1 (2001-01-07T09:32:13.798) and time2 (2001-01-07T09:32:13.784) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3495] time1 (2001-01-07T09:32:13.798) and time2 (2001-01-07T09:32:13.784) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3497] time1 (2001-01-07T09:32:22.845) and time2 (2001-01-07T09:32:22.828) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3497] time1 (2001-01-07T09:32:22.845) and time2 (2001-01-07T09:32:22.828) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3499] time1 (2001-01-07T09:32:31.889) and time2 (2001-01-07T09:32:31.875) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3499] time1 (2001-01-07T09:32:31.889) and time2 (2001-01-07T09:32:31.875) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3501] time1 (2001-01-07T09:32:40.936) and time2 (2001-01-07T09:32:40.921) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3501] time1 (2001-01-07T09:32:40.936) and time2 (2001-01-07T09:32:40.921) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3510] time1 (2001-01-07T09:33:21.654) and time2 (2001-01-07T09:33:21.639) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3510] time1 (2001-01-07T09:33:21.654) and time2 (2001-01-07T09:33:21.639) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3512] time1 (2001-01-07T09:33:30.701) and time2 (2001-01-07T09:33:30.686) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3512] time1 (2001-01-07T09:33:30.701) and time2 (2001-01-07T09:33:30.686) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3514] time1 (2001-01-07T09:33:39.745) and time2 (2001-01-07T09:33:39.730) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3514] time1 (2001-01-07T09:33:39.745) and time2 (2001-01-07T09:33:39.730) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3516] time1 (2001-01-07T09:33:48.792) and time2 (2001-01-07T09:33:48.777) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3516] time1 (2001-01-07T09:33:48.792) and time2 (2001-01-07T09:33:48.777) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3518] time1 (2001-01-07T09:33:57.839) and time2 (2001-01-07T09:33:57.821) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3518] time1 (2001-01-07T09:33:57.839) and time2 (2001-01-07T09:33:57.821) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3520] time1 (2001-01-07T09:34:06.882) and time2 (2001-01-07T09:34:06.867) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3520] time1 (2001-01-07T09:34:06.882) and time2 (2001-01-07T09:34:06.867) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3522] time1 (2001-01-07T09:34:15.929) and time2 (2001-01-07T09:34:15.914) are in the wrong order - setting equal
2018-08-03 20:14:34 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3522] time1 (2001-01-07T09:34:15.929) and time2 (2001-01-07T09:34:15.914) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3531] time1 (2001-01-07T09:34:56.645) and time2 (2001-01-07T09:34:56.630) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3531] time1 (2001-01-07T09:34:56.645) and time2 (2001-01-07T09:34:56.630) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3533] time1 (2001-01-07T09:35:05.692) and time2 (2001-01-07T09:35:05.677) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3533] time1 (2001-01-07T09:35:05.692) and time2 (2001-01-07T09:35:05.677) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3535] time1 (2001-01-07T09:35:14.739) and time2 (2001-01-07T09:35:14.721) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3535] time1 (2001-01-07T09:35:14.739) and time2 (2001-01-07T09:35:14.721) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3537] time1 (2001-01-07T09:35:23.783) and time2 (2001-01-07T09:35:23.768) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3537] time1 (2001-01-07T09:35:23.783) and time2 (2001-01-07T09:35:23.768) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3539] time1 (2001-01-07T09:35:32.830) and time2 (2001-01-07T09:35:32.812) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3539] time1 (2001-01-07T09:35:32.830) and time2 (2001-01-07T09:35:32.812) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3541] time1 (2001-01-07T09:35:41.873) and time2 (2001-01-07T09:35:41.858) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3541] time1 (2001-01-07T09:35:41.873) and time2 (2001-01-07T09:35:41.858) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3543] time1 (2001-01-07T09:35:50.920) and time2 (2001-01-07T09:35:50.905) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3543] time1 (2001-01-07T09:35:50.920) and time2 (2001-01-07T09:35:50.905) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3552] time1 (2001-01-07T09:36:31.637) and time2 (2001-01-07T09:36:31.623) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3552] time1 (2001-01-07T09:36:31.637) and time2 (2001-01-07T09:36:31.623) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3554] time1 (2001-01-07T09:36:40.684) and time2 (2001-01-07T09:36:40.670) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3554] time1 (2001-01-07T09:36:40.684) and time2 (2001-01-07T09:36:40.670) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3556] time1 (2001-01-07T09:36:49.731) and time2 (2001-01-07T09:36:49.714) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3556] time1 (2001-01-07T09:36:49.731) and time2 (2001-01-07T09:36:49.714) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3558] time1 (2001-01-07T09:36:58.775) and time2 (2001-01-07T09:36:58.761) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3558] time1 (2001-01-07T09:36:58.775) and time2 (2001-01-07T09:36:58.761) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3560] time1 (2001-01-07T09:37:07.822) and time2 (2001-01-07T09:37:07.808) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3560] time1 (2001-01-07T09:37:07.822) and time2 (2001-01-07T09:37:07.808) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3562] time1 (2001-01-07T09:37:16.866) and time2 (2001-01-07T09:37:16.852) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3562] time1 (2001-01-07T09:37:16.866) and time2 (2001-01-07T09:37:16.852) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3564] time1 (2001-01-07T09:37:25.913) and time2 (2001-01-07T09:37:25.898) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3564] time1 (2001-01-07T09:37:25.913) and time2 (2001-01-07T09:37:25.898) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3573] time1 (2001-01-07T09:38:06.629) and time2 (2001-01-07T09:38:06.614) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3573] time1 (2001-01-07T09:38:06.629) and time2 (2001-01-07T09:38:06.614) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3575] time1 (2001-01-07T09:38:15.676) and time2 (2001-01-07T09:38:15.661) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3575] time1 (2001-01-07T09:38:15.676) and time2 (2001-01-07T09:38:15.661) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3577] time1 (2001-01-07T09:38:24.723) and time2 (2001-01-07T09:38:24.705) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3577] time1 (2001-01-07T09:38:24.723) and time2 (2001-01-07T09:38:24.705) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3579] time1 (2001-01-07T09:38:33.767) and time2 (2001-01-07T09:38:33.752) are in the wrong order - setting equal
2018-08-03 20:14:35 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3579] time1 (2001-01-07T09:38:33.767) and time2 (2001-01-07T09:38:33.752) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3581] time1 (2001-01-07T09:38:42.814) and time2 (2001-01-07T09:38:42.799) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3581] time1 (2001-01-07T09:38:42.814) and time2 (2001-01-07T09:38:42.799) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3583] time1 (2001-01-07T09:38:51.861) and time2 (2001-01-07T09:38:51.843) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3583] time1 (2001-01-07T09:38:51.861) and time2 (2001-01-07T09:38:51.843) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3585] time1 (2001-01-07T09:39:00.905) and time2 (2001-01-07T09:39:00.890) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3585] time1 (2001-01-07T09:39:00.905) and time2 (2001-01-07T09:39:00.890) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3594] time1 (2001-01-07T09:39:41.622) and time2 (2001-01-07T09:39:41.608) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3594] time1 (2001-01-07T09:39:41.622) and time2 (2001-01-07T09:39:41.608) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3596] time1 (2001-01-07T09:39:50.669) and time2 (2001-01-07T09:39:50.654) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3596] time1 (2001-01-07T09:39:50.669) and time2 (2001-01-07T09:39:50.654) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3598] time1 (2001-01-07T09:39:59.716) and time2 (2001-01-07T09:39:59.699) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3598] time1 (2001-01-07T09:39:59.716) and time2 (2001-01-07T09:39:59.699) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3600] time1 (2001-01-07T09:40:08.760) and time2 (2001-01-07T09:40:08.745) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3600] time1 (2001-01-07T09:40:08.760) and time2 (2001-01-07T09:40:08.745) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3602] time1 (2001-01-07T09:40:17.807) and time2 (2001-01-07T09:40:17.792) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3602] time1 (2001-01-07T09:40:17.807) and time2 (2001-01-07T09:40:17.792) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3604] time1 (2001-01-07T09:40:26.854) and time2 (2001-01-07T09:40:26.836) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3604] time1 (2001-01-07T09:40:26.854) and time2 (2001-01-07T09:40:26.836) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3606] time1 (2001-01-07T09:40:35.898) and time2 (2001-01-07T09:40:35.883) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3606] time1 (2001-01-07T09:40:35.898) and time2 (2001-01-07T09:40:35.883) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3608] time1 (2001-01-07T09:40:44.945) and time2 (2001-01-07T09:40:44.930) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3608] time1 (2001-01-07T09:40:44.945) and time2 (2001-01-07T09:40:44.930) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3617] time1 (2001-01-07T09:41:25.660) and time2 (2001-01-07T09:41:25.646) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3617] time1 (2001-01-07T09:41:25.660) and time2 (2001-01-07T09:41:25.646) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3619] time1 (2001-01-07T09:41:34.707) and time2 (2001-01-07T09:41:34.690) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3619] time1 (2001-01-07T09:41:34.707) and time2 (2001-01-07T09:41:34.690) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3621] time1 (2001-01-07T09:41:43.751) and time2 (2001-01-07T09:41:43.737) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3621] time1 (2001-01-07T09:41:43.751) and time2 (2001-01-07T09:41:43.737) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3623] time1 (2001-01-07T09:41:52.798) and time2 (2001-01-07T09:41:52.784) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3623] time1 (2001-01-07T09:41:52.798) and time2 (2001-01-07T09:41:52.784) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3625] time1 (2001-01-07T09:42:01.845) and time2 (2001-01-07T09:42:01.828) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3625] time1 (2001-01-07T09:42:01.845) and time2 (2001-01-07T09:42:01.828) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3627] time1 (2001-01-07T09:42:10.889) and time2 (2001-01-07T09:42:10.875) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3627] time1 (2001-01-07T09:42:10.889) and time2 (2001-01-07T09:42:10.875) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3629] time1 (2001-01-07T09:42:19.936) and time2 (2001-01-07T09:42:19.921) are in the wrong order - setting equal
2018-08-03 20:14:36 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 3629] time1 (2001-01-07T09:42:19.936) and time2 (2001-01-07T09:42:19.921) are in the wrong order - setting equal
2018-08-03 20:15:42 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 7328] time1 (2001-01-14T23:40:46.936) and time2 (2001-01-14T23:40:46.934) are in the wrong order - setting equal
2018-08-03 20:15:42 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 7328] time1 (2001-01-14T23:40:46.936) and time2 (2001-01-14T23:40:46.934) are in the wrong order - setting equal
2018-08-03 20:15:42 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 7332] time1 (2001-01-14T23:50:36.932) and time2 (2001-01-14T23:50:36.918) are in the wrong order - setting equal
2018-08-03 20:15:42 | pds.opus_import.main |--| ERROR | [COVIMS_0002 index row 7332] time1 (2001-01-14T23:50:36.932) and time2 (2001-01-14T23:50:36.918) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28079] time1 (2001-09-24T00:03:56.368) and time2 (2001-09-24T00:03:56.365) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28079] time1 (2001-09-24T00:03:56.368) and time2 (2001-09-24T00:03:56.365) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28080] time1 (2001-09-24T00:04:27.349) and time2 (2001-09-24T00:04:27.346) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28080] time1 (2001-09-24T00:04:27.349) and time2 (2001-09-24T00:04:27.346) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28081] time1 (2001-09-24T00:04:59.354) and time2 (2001-09-24T00:04:59.346) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28081] time1 (2001-09-24T00:04:59.354) and time2 (2001-09-24T00:04:59.346) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28082] time1 (2001-09-24T00:05:33.354) and time2 (2001-09-24T00:05:33.351) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28083] time1 (2001-09-24T00:06:04.349) and time2 (2001-09-24T00:06:04.346) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28084] time1 (2001-09-24T00:06:36.354) and time2 (2001-09-24T00:06:36.351) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28085] time1 (2001-09-24T00:15:15.395) and time2 (2001-09-24T00:15:15.380) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28085] time1 (2001-09-24T00:15:15.395) and time2 (2001-09-24T00:15:15.380) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28088] time1 (2001-09-24T00:15:19.438) and time2 (2001-09-24T00:15:19.426) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28088] time1 (2001-09-24T00:15:19.438) and time2 (2001-09-24T00:15:19.426) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28090] time1 (2001-09-24T00:15:22.146) and time2 (2001-09-24T00:15:22.134) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28090] time1 (2001-09-24T00:15:22.146) and time2 (2001-09-24T00:15:22.134) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28096] time1 (2001-09-24T00:16:19.651) and time2 (2001-09-24T00:16:19.637) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28096] time1 (2001-09-24T00:16:19.651) and time2 (2001-09-24T00:16:19.637) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28097] time1 (2001-09-24T00:17:07.025) and time2 (2001-09-24T00:17:07.022) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28097] time1 (2001-09-24T00:17:07.025) and time2 (2001-09-24T00:17:07.022) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28098] time1 (2001-09-24T00:17:24.703) and time2 (2001-09-24T00:17:24.700) are in the wrong order - setting equal
2018-08-03 20:24:49 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28098] time1 (2001-09-24T00:17:24.703) and time2 (2001-09-24T00:17:24.700) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28099] time1 (2001-09-24T00:17:42.351) and time2 (2001-09-24T00:17:42.348) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28099] time1 (2001-09-24T00:17:42.351) and time2 (2001-09-24T00:17:42.348) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28100] time1 (2001-09-24T00:18:00.023) and time2 (2001-09-24T00:18:00.020) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28100] time1 (2001-09-24T00:18:00.023) and time2 (2001-09-24T00:18:00.020) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28102] time1 (2001-09-24T00:18:35.340) and time2 (2001-09-24T00:18:35.337) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28102] time1 (2001-09-24T00:18:35.340) and time2 (2001-09-24T00:18:35.337) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28103] time1 (2001-09-24T00:19:15.392) and time2 (2001-09-24T00:19:15.384) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28106] time1 (2001-09-24T00:19:19.450) and time2 (2001-09-24T00:19:19.442) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28108] time1 (2001-09-24T00:19:22.158) and time2 (2001-09-24T00:19:22.149) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28109] time1 (2001-09-24T00:19:57.035) and time2 (2001-09-24T00:19:57.026) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28111] time1 (2001-09-24T00:20:06.066) and time2 (2001-09-24T00:20:06.057) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28113] time1 (2001-09-24T00:20:15.113) and time2 (2001-09-24T00:20:15.104) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28114] time1 (2001-09-24T00:20:19.644) and time2 (2001-09-24T00:20:19.635) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28115] time1 (2001-09-24T00:21:07.024) and time2 (2001-09-24T00:21:07.012) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28116] time1 (2001-09-24T00:21:24.695) and time2 (2001-09-24T00:21:24.684) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28118] time1 (2001-09-24T00:22:00.015) and time2 (2001-09-24T00:22:00.004) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28121] time1 (2001-09-24T00:23:15.392) and time2 (2001-09-24T00:23:15.377) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28121] time1 (2001-09-24T00:23:15.392) and time2 (2001-09-24T00:23:15.377) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28123] time1 (2001-09-24T00:24:36.022) and time2 (2001-09-24T00:24:36.019) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28123] time1 (2001-09-24T00:24:36.022) and time2 (2001-09-24T00:24:36.019) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28124] time1 (2001-09-24T00:25:16.391) and time2 (2001-09-24T00:25:16.382) are in the wrong order - setting equal
2018-08-03 20:24:50 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28125] time1 (2001-09-24T00:25:51.032) and time2 (2001-09-24T00:25:51.023) are in the wrong order - setting equal
2018-08-03 20:24:52 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28259] time1 (2001-09-24T03:21:01.262) and time2 (2001-09-24T03:21:01.250) are in the wrong order - setting equal
2018-08-03 20:24:52 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28259] time1 (2001-09-24T03:21:01.262) and time2 (2001-09-24T03:21:01.250) are in the wrong order - setting equal
2018-08-03 20:24:52 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28260] time1 (2001-09-24T03:21:48.259) and time2 (2001-09-24T03:21:48.253) are in the wrong order - setting equal
2018-08-03 20:24:52 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28260] time1 (2001-09-24T03:21:48.259) and time2 (2001-09-24T03:21:48.253) are in the wrong order - setting equal
2018-08-03 20:24:52 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28261] time1 (2001-09-24T03:23:24.261) and time2 (2001-09-24T03:23:24.249) are in the wrong order - setting equal
2018-08-03 20:24:52 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28262] time1 (2001-09-24T03:23:59.261) and time2 (2001-09-24T03:23:59.249) are in the wrong order - setting equal
2018-08-03 20:24:56 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28452] time1 (2002-03-06T11:00:44.865) and time2 (2002-03-06T11:00:44.862) are in the wrong order - setting equal
2018-08-03 20:24:56 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28452] time1 (2002-03-06T11:00:44.865) and time2 (2002-03-06T11:00:44.862) are in the wrong order - setting equal
2018-08-03 20:24:58 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28556] time1 (2002-03-13T08:35:06.385) and time2 (2002-03-13T08:35:06.382) are in the wrong order - setting equal
2018-08-03 20:24:58 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28556] time1 (2002-03-13T08:35:06.385) and time2 (2002-03-13T08:35:06.382) are in the wrong order - setting equal
2018-08-03 20:24:58 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28558] time1 (2002-03-13T09:56:11.669) and time2 (2002-03-13T09:56:11.668) are in the wrong order - setting equal
2018-08-03 20:24:58 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28558] time1 (2002-03-13T09:56:11.669) and time2 (2002-03-13T09:56:11.668) are in the wrong order - setting equal
2018-08-03 20:24:58 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28561] time1 (2002-03-13T11:30:59.491) and time2 (2002-03-13T11:30:59.490) are in the wrong order - setting equal
2018-08-03 20:24:58 | pds.opus_import.main |--| ERROR | [COVIMS_0003 index row 28561] time1 (2002-03-13T11:30:59.491) and time2 (2002-03-13T11:30:59.490) are in the wrong order - setting equal
2018-08-03 21:27:30 | pds.opus_import.main |--| ERROR | [COVIMS_0029 index row 398] time1 (2008-07-04T06:43:47.967) and time2 (1986-08-01T02:47:28.569) are in the wrong order - setting equal
2018-08-03 21:27:30 | pds.opus_import.main |--| ERROR | [COVIMS_0029 index row 398] time1 (2008-07-04T06:43:47.967) and time2 (1986-08-01T02:47:28.569) are in the wrong order - setting equal

We have no way of fixing this.


Core | Calculated columns : fix restoring on data refresh

Calculated columns using MPO columns in formula are not restored on data refresh

Problem
To further specify this ticket: The root cause for this issue was introduced by us having multiple sources for calculated columns. Because of that during loading sequence our module is trying to restore calculated columns in the wrong dependency order. This leads to the situation of missing columns in the resulting DataFrame.
We know Datagrok has a built in feature to solve the dependency issue for calculated columns which works excellent for all cases. To ensure we are handling the dependency issue in a consistent way, we would like to re-use your dependency solving algorithm through Datagrok JavaScript API.
Therefore our ask would be: can you expose your calculated columns (re)-order algorithm through native Datagrok API?
Desired specs:

exposed method in grok JS module
passed variables: unsorted array of calculated columns

type def: Array<{columnName: string, formula: string}>

return value: sorted array with resolved dependency order of calculated columns:

type def: Array<{columnName: string, formula: string}>

@LaykDimon should be doable?

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-16198