Add profile for CCTVs on Cargo Ship

Create an example profile called CargoShipCCTV which adds CCTVs and Computer Stations to Cargo Ship at the same positions as the Cargo Ship CCTV plugin.

Plugin was probably made before some lighting updates, so view from cameras inside cargo hold are pretty dark.
{
  "Name": "CargoShipCCTV",
  "Author": "marcuzz",
  "SchemaVersion": 2.0,
  "MonumentData": {
    "cargoshiptest": {
      "Entities": [
        {
          "Id": "95bfc1ed-aee7-4161-b0c9-ec8339675b1e",
          "PrefabName": "assets/prefabs/deployable/computerstation/computerstation.static.prefab",
          "Position": {
            "x": -9.2,
            "y": 24.5,
            "z": -39.8
          },
          "RotationAngles": {
            "x": 0.0,
            "y": 180.0,
            "z": 0.0
          }
        },
        {
          "Id": "e21d4099-f510-4588-8f03-8623ea0bbef8",
          "PrefabName": "assets/prefabs/deployable/cctvcamera/cctv.static.prefab",
          "Position": {
            "x": 0.0,
            "y": 22.0,
            "z": -37.44
          },
          "CCTV": {
            "RCIdentifier": "CARGODECKA",
            "Pitch": 50.0
          }
        },
        {
          "Id": "aa3994bc-d1fd-462b-9284-1e03a154cb14",
          "PrefabName": "assets/prefabs/deployable/cctvcamera/cctv.static.prefab",
          "Position": {
            "x": 0.0,
            "y": 15.0,
            "z": -51.065
          },
          "RotationAngles": {
            "x": 0.0,
            "y": 180.0,
            "z": 0.0
          },
          "CCTV": {
            "RCIdentifier": "CARGODECKB",
            "Pitch": 50.0
          }
        },
        {
          "Id": "fe09aded-8f68-47c0-8867-a214deca652e",
          "PrefabName": "assets/prefabs/deployable/cctvcamera/cctv.static.prefab",
          "Position": {
            "x": 0.0,
            "y": 21.5,
            "z": 68.52
          },
          "RotationAngles": {
            "x": 0.0,
            "y": 180.0,
            "z": 0.0
          },
          "CCTV": {
            "RCIdentifier": "CARGODECKC",
            "Pitch": 25.0
          }
        },
        {
          "Id": "a9de876d-2f67-46d9-82f5-55ad7eddbb9a",
          "PrefabName": "assets/prefabs/deployable/cctvcamera/cctv.static.prefab",
          "Position": {
            "x": 0.0,
            "y": 4.6,
            "z": -32.87
          },
          "CCTV": {
            "RCIdentifier": "CARGOHOLDA",
            "Pitch": 35.0
          }
        },
        {
          "Id": "2889bc86-c4e7-4474-9b66-6ac604eb1380",
          "PrefabName": "assets/prefabs/deployable/cctvcamera/cctv.static.prefab",
          "Position": {
            "x": 0.0,
            "y": 4.6,
            "z": 50.87
          },
          "RotationAngles": {
            "x": 0.0,
            "y": 180.0,
            "z": 0.0
          },
          "CCTV": {
            "RCIdentifier": "CARGOHOLDB",
            "Pitch": 24.0
          }
        },
        {
          "Id": "d52a7d00-f3aa-4f24-b64e-a4380a67da99",
          "PrefabName": "assets/prefabs/deployable/cctvcamera/cctv.static.prefab",
          "Position": {
            "x": 12.0,
            "y": 6.08,
            "z": 27.8
          },
          "RotationAngles": {
            "x": 0.0,
            "y": 90.0,
            "z": 0.0
          },
          "CCTV": {
            "RCIdentifier": "CARGOLADDERA",
            "Yaw": 90.0
          }
        },
        {
          "Id": "38f98880-dbfd-4935-b7bb-0c9f73c9c65f",
          "PrefabName": "assets/prefabs/deployable/cctvcamera/cctv.static.prefab",
          "Position": {
            "x": -12.0,
            "y": 6.08,
            "z": 27.8
          },
          "RotationAngles": {
            "x": 0.0,
            "y": 270,
            "z": 0.0
          },
          "CCTV": {
            "RCIdentifier": "CARGOLADDERB",
            "Yaw": -90
          }
        }
      ]
    }
  }
}

Nice! Feel free to submit as a PR for sample profiles. The file should be located in the Profiles folder, and please also update the README to add it to the "Installing existing profiles" section.

Resolved in #34.


[Bug] Reset Default Settings button does not trigger ModConfiguration.OnThisConfigurationChanged event

I'm adding a feature to my mod and I want things to happen when the config changes. It works normally but when I click the Reset Default Settings button it seems to not fire the event at all.

Fixed in v1.3.0


Documentation website down

The documentation website seems to be down.
I just get "Apache is functioning normally" or a 404

We're working on it.

Why don't you host it on github it's way more reliable and people can contribute to it.

https://github.com/magister-api/docs
That's a work in progress, we just haven't had the time for it.

When will we be able to read the API documentation?

Due to it being a lot of work and me having to do it alone, I hope to finish it before the end of the month.

So any updates on the docs?

Unfortunately I'm unable to reach Stan as he's extremely busy with his study. I don't really have an alternative for the website right now, nor for the documentation itself. Just like Stan I don't have much time to work on the Magister API, merely occasional compatibility updates or quick fixes, let alone work on the new version and finish the documentation. I really do want to finish this but I simply don't have time.


traffic error

cant get into site because it says there is a lot of traffic and they will be back in 5 minutes. it has been 25 minutes. anyone else got this problem?

ok i didnt read the discord server, closing this now.


Remove leftover wercker config files

Removing wercker.yml config files, those are leftovers after experiments with #747 so nobody gets confused that we use WerckerCI ;)

Yes, thanks


Toolchains download

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.


Add code for checking if root user is being used.

GIve a warning message if the UID is 0, etc.
Users should use ADD_USER=exclude when the host is a root user.

Just added documentation instead.


Improve Guiding Default Config

Revise default microstep settings when using UART
Revise default DEC guide pulse settings to match RA

Will this affect current guide tuning? If so we should outline how the guiding parameters should be adjusted when updating

Will this affect current guide tuning? If so we should outline how the guiding parameters should be adjusted when updating

It will align the RA and DEC step sizes when doing PHD2 calibrations. We could have a statement saying to re-calibrate after applying this update, but realistically people should be calibrating each session regardless.
The microstep change only affects the defaults. It won't affect anyone who has it specified in their local config (which I assume is everyone since it's included by the config generator)


Mark mode no longer works?

If i do ctrl+space, then ctrl+f, the character is not selected. but if i press the right arrow instead, it is selected.

I'll add on this one instead of opening a separate issue, but when using ctrl keys to move around the mark mode comes on and stay one. After moving around I have to type ctrl+space to turn it off or I'll lose characters.


Unable to build locally - remove package-lock.json

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
If you try to clone repo and run locally you get the following (or similar) error:
npm ERR! code ENOLOCAL
npm ERR! Could not install from "node_modules/aframe/node_modules/three-bmfont-text/three-buffer-vertex-data@dmarcos/three-buffer-vertex-data#69378fc58daf27d3b1d930df9f233473e4a4818c" as it does not contain a package.json file.

npm ERR!      /Users/marknaus/.npm/_logs/2022-09-16T07_47_45_075Z-debug.log

If the current behavior is a bug, please provide the steps to reproduce.
Clone repo locally
Run npm install
An earlier try go stuck on 'debug@github:ngokevin/debug#noTimestamp' which is mentioned in the package-lock.json.

Please mention other relevant information such as the browser version, Operating System and Device Name
Mac OS 12.0.1 - M1 Pro Macbook Pro 16-inch 32gb RAM
What is the expected behavior?
Running npm install allows me to build locally.
If this is a feature request, what is motivation or use case for changing the behavior?
N/A
Suggested Resolution
Remove package-lock.json from repo
After removing it locally I can run npm install just fine.
Can make a PR if desired.

Hi @Nauzer thanks for reporting this. It could be that you are using a different node version , but probably this is not the problem. Can you tell us which node and npm version you are using?
We use node version 14.19 as stated in .nvmrc file https://github.com/AR-js-org/AR.js/blob/0722816b2afaf327186e40e38e1de454a3f5d434/.nvmrc#L1 You could try to use the same node version running nvm install 14 and nvm use 14.
But probably this error is caused by other reason, read this article https://stackoverflow.com/questions/48143945/what-is-the-err-code-enolocal-npm-err-could-not-install-because-of-an-error
The package-lock.json is also used by the github action to perform code checking, and enable automatic dependency alert, so in turn we don't want to remove it.


Marketing Analytics: Facebook Conversion Pixel

As an Opentrons marketer, I would like to have the Facebook Ads tag on our website, so that I can retarget our website visitors on Facebook and track their conversions.
Acceptance Criteria

[ ] Add Facebook conversion pixel to opentrons.com

Open Questions

Conversion pixel, vs. Ad Tags/Ad Label API work?
Just base pixel, or do we want to track additional conversion points?
Just every opentrons.com page, or other properties as well?

Tag
[add tag here]

The Facebook pixel should be installed on subdomains www/protocols/shop as outlined in their specs. This can be done first if necessary, as it is both easier and more essential to building up our audiences.
To track events as conversions refer to this doc. I believe this is the direction we need to go: "For inline action events: add the event code between script tags next to the action you want to track (like a button)."
facebook site Pixel ID<PHONE_NUMBER>502596.txt
Discuss options on these:
fbq('track', 'AddToCart'); (for buy now from shopify product pages)
fbq('track', 'Schedule'); (for schedule a demo)
fbq('track', 'Contact'); (for intercom)
fbq('track', 'Lead'); (for email the team)
--
--


Disable past days, User should not able to select past days

Hello,
I want to disable past days,
User should not able to select past days,
Example : Current date is 20 March 2015,
So user should not able to select days till 19 March 2015.
Thank is advance.

It's currently not possible. I just have to add a method to the delegate for that. I will do that quickly.

Ok,
Thanks for reply.

I just added a new method calendar:canSelectDate for the delegate.

Thanks a lot for quick update.

Can you please give one example code to disable previous dates?

Hello JT,
Example for disable past days,
Suppose JTCalendar is currently showing MARCH-2015,
And today's s date is 15 MARCH 2015,
So All dates before 15 MARCH 2015 should be disabled, Color of this dates
should be same as previous month's date color.
User can not able to select dates before 15 MARCH 2015.
On Sat, Apr 25, 2015 at 11:51 AM, Naveen Kumar P<EMAIL_ADDRESS>wrote:

Can you please give one example code to disable previous dates?
—
Reply to this email directly or view it on GitHub
https://github.com/jonathantribouharet/JTCalendar/issues/98#issuecomment-96139598
.


[move-prover] Add support for locals in spec blocks inside functions

Motivation
This PR adds the capability to refer to locals in spec blocks inside functions.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
More tests and existing tests
Related PRs

@bors-libra r=wrwg

:pushpin: Commit 28c857b has been approved by wrwg

:hourglass: Testing commit 28c857bcc960669368e1a403a27f6160b21272e3 with merge 94435220dbb6e06b04a89dfadc682973052ca92b...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: wrwg
Pushing 94435220dbb6e06b04a89dfadc682973052ca92b to master...


Update README unfocusedBorderColor capitalization to unFocusedBorderColor

This tripped me up for a little while. The readme has the incorrect capitalization  of the unFocusedBorderColor prop listed as un**f**ocusedBorderColor.
If you would like I can fork and submit a PR for this change or you can push it in your next update. Let me know what works for you - great work on this component 🥇

@jannainm I will release fix today, as I'm working on documenting types also :)

Fixed in 2.0.1


Steps to reproduce:
1.apply soul bound
2.die or use /kill
3.cry in tears??
...

Affected Versions (Do not use "latest"):

EnderIO:1-10.2-3.1.179

Your most recent log file where the issue was present:
no logs/errors are given

For the last 3 years there has not been a single instance of a soulbound malfunction that wasn't caused by other mods messing with the death processing improperly. So either reproduce the problem with only Foreg+Endercore+EnderIO and provide a full log, or provide a full list of mods that are installed so I can refer you to those that are likely candidates.


Add pivot functionality between multiple components

Instead of standard show/hide, incorporate pivoting for cycling through controls.

Do we keep show/hide in the code as a backup solution?

Pivot revisions added with commit d1d53fbc6f358b8c4c5180258b2a67eca203ea76

I will work on a way to use the pivot in the list/form and list/view show/hide events when one is present.

Added an exact() function to target a specific pivot.

Commit 477a4fe2130df4022a41811988de3c5ce620f964 should have the full list/form toggle integration into the standard CRUD admin screens. We'll need to regression test running through some lists and forms.

Completed with commit efb0bd8615e80fffa650dc3d8c23884167d96a1c


Dictionary

Letting you know that I need multi language dictionary for my next game so I am working on one.
Leaving this open for discussion in case you expect some features.
Things so far:
Basic usage

/* dictionary.json */

{
  "reportDamage": "Your health is {health}"
}

/* app.js */

app.dictionary("reportDamage", { health: 70 });

> Your health is 70

Tree
{
  "items": {
    "weapon": "bron",
    "shield": "tarcza",
    "armor": "zbroja"
  }
}

app.dictionary("items/shield");

> tarcza

Access object properties
{
  "weaponDescription": "Deals {weapon.damage} damage each {weapon.cooldown} seconds"
}

app.dictionary("weaponDescription", {
  weapon: { damage: 4, cooldown: 6 }
});

> Deals 4 damage each 6 seconds

Self lookup and {nested{tags}}
{tags} are resolved in order from inside to outside
If tag is a slash separated path ex. "{path/to/something}" the tag will be replaced by dictionary entry
If tag is a dot separated path ex. "{path.to.something}" the tag will be replaced by replace entry
Hence it is possible to create quite flexible dictionary entries
{
  "descriptions": {
    "weapon": "That is a weapon.",
    "shield": "It is some shield.",
    "armor": "That must be an armor."
  },

  "details": {
    "weapon": "Damage: {damage}"
  },

  "look": "Your are looking at the object. {descriptions/{type}} - {details/{type}}"
}

app.dictionary("look", { type: "weapon", "damage": 4 });

> You are looking at the object. That is a weapon. Damage: 4

Pulling random element from dictionary group
If the {tag} path ends with slash it will pull random entry from a group
{

  "insluts": [
    "you rebel scum",
    "you filthy hamster",
    "you worthless bum"
  ],

  "deathWish": "Die, {insults/}"

}

app.dictionary("deathWish");

> Die, you filthy hamster

First concerns
Path resolving will probably change form from {path/to/entry} to {@path/to/entry} - that is because I want to introduce math mode Your dps is {damage / cooldown} which may also evolve into little less readable form {{damage} / {cooldown}}

I suggest {path.to.entry} instead of {@path/to/entry} or {path/to/entry}
{
  "items": {
    "weapon": "bron",
    "shield": "tarcza",
    "armor": "zbroja"
  }
}

app.dictionary("items.shield");

> tarcza


services/horizon: Parallelize db reingest range

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[x] This PR adds tests for the most critical parts of the new functionality or fixes.
[x] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[x] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[ ] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
This change breaks down the ledger range to reingest in subranges which are submitted to a pre-defined number of workers, processing the subranges in parallel.
For now, the workers are simply Go routines using their own System (with their own DB connections etc ...).
In the future workers could be fully fledged Horizon instances running in multiple machines (e.g. orchestrated through Kubernetes Jobs or AWS Batch Jobs).
New flags:
--parallel-workers: [optional] if this flag is set to > 1, horizon will parallelize reingestion using the supplied number of workers
--parallel-job-size: [optional] parallel workers will run jobs processing ledger batches of the supplied size
Why
We want reingestion to be faster. Addresses #2552
Known limitations
As I mentioned, this change only applies to a single machine. Running it in multiple machines will require further work.
This PR is targetting release-1.5.0  (since that's the base branch I used). We should retarget it to master (once release-1.5.0 is merged) before merging.

@bartekn PTAL. I addressed your comments, reincorporated --parallel-job-size (which will be needed for performance reasons when reingesting the full history) and added an extra test (TestParallelReingestRangeError())

OK, I pushed my code as discussed with @fons. I haven't updated tests, will do it after 👍 from you. I also added a code that return a suggested range to restart a job in case of failure. There's a comment above lowestRangeErr explaining why (I think) it works without having to keep track of results from all the jobs.

@fons thanks for a quick review! I added the requested changes and fixed tests. It's great that we're at the same page when it comes to aborting jobs.
I removed Shutdown as requested: I agree it doesn't make sense to keep it now because we're not handling system shutdown signals at all in db reingest commands. However, I think it's worth doing this in a future so that users get a status update when they terminate the process manually.
I won't be available in the morning tomorrow so please update the code if there's something that's blocking you from merging it.

I think we are done. Thie PR targets the 1.5.0 branch, but my plan is to hold off from merging to avoid disrupting the 1.5.0 release, and just wait until 1.5.0 is merged into master.
But, if @ire-and-curses / @abuiles are OK with it, I will merge now.

Let's target this for 1.6 release.

Added successful range logging in https://github.com/stellar/go/pull/2724/commits/b0205c909ed35d937024938a75383fd635585474.


refactor online serving rolling api

Description
The previous online serving strategy is too complicated.
Motivation and Context

How Has This Been Tested?

[ ] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.
[ ] If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[ ] Fix bugs
[ ] Add new feature
[ ] Update documentation

I've tested locally to ensure that the rolling result is the same with previous version


Typo - StringCompari-son

There is a typo in the sample code - StringCompari-son

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

ID: b0675424-4061-b505-273a-14f966df6cdd
Version Independent ID: 74aa00ed-3362-7a2e-105a-0e00177a6b93
Content: Configure Azure bots to escalate and end conversations
Content Source: ce/customer-service/bot-escalate-end-conversation.md
Service: dynamics-365-customerservice
GitHub Login: @neeranelli
Microsoft Alias: nenellim

Found another typo - Bo-tHandoffTopic

Thanks for your comment, @grantborthwick. This issue has been assigned to the doc author for review.

Thank you, @grantborthwick. This is corrected and will be live in the next publish.


has_method does not work on class

Godot version:
current master
OS/device including version:
Windows, don't think it matters
Issue description:
Investigating #22833 I found out that has_method does not work with classes.
Consider the following script:
extends Node

class Test:
	static func foo():
		print("foo")

func _ready():
	Test.foo() # works as expected
	print(Test.has_method("foo")) # false although Test has this method

In #22833 this bug makes it impossible to use a static func of a class in array.sort_custom().
Steps to reproduce:
Call has_method on a class.
Minimal reproduction project:
sfhm.zip

Changing this line in object.h
https://github.com/godotengine/godot/blob/b17e71b6e5e035f49b5b3b5b55b9cdac80215d72/core/object.h#L652
and making this bool virtual seems to fix the issue. The Script class has its own has_method so it should work if correctly implemented.
As I didn't test it with VisualScript and C# I am not comfortable committing this change.

CC @reduz @vnen @neikeq

The scripting API doesn't support static method. As such, has_method is not static. You need an instance to access it.

Changing this line in object.h
https://github.com/godotengine/godot/blob/b17e71b6e5e035f49b5b3b5b55b9cdac80215d72/core/object.h#L652
and making this bool virtual seems to fix the issue. The Script class has its own has_method so it should work if correctly implemented.

I don't understand how that would change anything. Could you give more details?

In Objects there is this method defined:
https://github.com/godotengine/godot/blob/b17e71b6e5e035f49b5b3b5b55b9cdac80215d72/core/object.h#L652
If I get it right this method checks if the method is either specified in an atached script or in the class.
However there is also a has_method() defined in the Script class which inherits Object. The implementations of the derived classes seem work for static functions (tested only for GDScript).
https://github.com/godotengine/godot/blob/b17e71b6e5e035f49b5b3b5b55b9cdac80215d72/core/script_language.h#L127
This already caused duplicate issues: #10785
If I understand c++ correctly, correct my if I'm wrong, the following happens:

Object has has_method which is not virtual and can not be overridden.
Script classes have their own has_method which causes the Object's implementation to be hidden but not overriden.
Calling has_method() on any object whose type isn't specified will call the Object's version.
Changing to virtual will essentialy make the Object's version possible to be overridden. This way the correct method will be called.

This makes it possible to check for static method in inner classes. The inner classes are of type GDScript and their has_method works for both static and non static functions (I don't know if this is intended behavior but it just works in this context).
Note that I only tested this with GDScript. I have not testet it in VisualScript and C# nor do I plan learning C# just for that. Also I don't know if this could potentialy create other issues with has_method I can't forseee.

Ok, changing has_method to virtual won't solve all problems.
The biggest one is that just overriding will get rid of the functionality in object's implementation. With this "fix" has_method on any script will not find

free()
methods in an attached script (though attaching a script to a script might be very rare)
methods defined not in the script itself. For example has_method can not be found.

Furthermore static functions of parents can not be found, although they are callable.
Advice would be appreciated. Or if someone wants to try it themself, go for it.

If someone is interested: Here are the test cases I could think of:
extends Node

class Foo:
	static func foo():
		return "foo"
	func foo_non_static():
		return "foo-non-static"

class Bar extends Foo:
	static func bar():
		return "bar"
	func bar_non_static():
		return "bar-non-static"

class scrpt:
	func script_func():
		return "script_func"

static func fun():
	return "fun"

func fun_non_static():
	return "fun_non_static"

func _ready():
	print("Test on self")
	_test(self, self.fun(), "fun")
	_test(self, self.fun_non_static(), "fun_non_static")

	print("Test on inner class")
	_test(Foo, Foo.foo(), "foo")
	_test(Foo, Foo.foo_non_static(), "foo_non_static")

	print("Test on instance of inner class")
	var fo = Foo.new()
	_test(fo, fo.foo(), "foo")
	_test(fo, fo.foo_non_static(), "foo_non_static")

	print("Test on inherited inner class")
	_test(Bar, Bar.foo(), "foo")
	_test(Bar, Bar.foo_non_static(), "foo_non_static")

	print("Test on instance of inherited inner class")
	var ba = Bar.new()
	_test(ba, ba.foo(), "foo")
	_test(ba, ba.foo_non_static(), "foo_non_static")

	print("Adding script to instance of inner class")
	fo.set_script(scrpt)
	_test(fo, fo.script_func(), "script_func")
	print("Adding script to inner class")
	Foo.set_script(scrpt)
	_test(Foo, Foo.script_func(), "script_func")

	print("Foo has " + ("" if Foo.has_method("has_method") else "no ") + "class methods")

func _test(var obj, var call, var method_name):
	var res = "Calling %s() on %s: \"%s\" and method can%s be found" % [method_name, obj, call, "" if obj.has_method(method_name) else " not"]
	print(res)

Note: I've reverted 6415454 with c730957 due to this bug. Once we have a solution for this issue, we could re-add 6415454.

Thanks for the tip! I made the changes and it works fine.
I have renamed Script::has_method to Script::defines_method as this method just lists methods defined in this very script. I also updated the calls, so no Object::has_method will be called by accident.

This will be properly fixable when methods become actual members. @vnen is going to work on this for Godot 3.2, so kicking there.

Will this be a part of 4.0 or was it just postponed to the latest available version? I guess it is related to the introduction of a Callable type? Also, what is going to be the solution? Will has_method work with both static and instanced methods or will we get a separate method for static checks?

Will this be a part of 4.0 or was it just postponed to the latest available version? I guess it is related to the introduction of a Callable type?

Yes, I believe this is being postponed till 4.0 (or, if not then, 4.1) since reduz's "when methods become actual members" comment refers to the introduction of the Callable type happening in 4.0.
I suspect the solution will just be changing the implementation of has_method() to support it. It would involve having the Script check static functions on a would-be ScriptInstance that hasn't yet been created, so the way that data is stored will likely be updated (probably by virtue of the Callable changes).

Will has_method work with both static and instanced methods or will we get a separate method for static checks?

My guess would be that it would be the same method for both, but it would just be updated so that instance and static methods work on ScriptInstances and static methods work on Scripts.

Just FYI, this problem occurs too with regular classes, not just class:
	var klass = CanvasItem
	# prints `false`
	print(klass.has_method("hide"))

Arguably here you could use ClassDB instead, but it misses a point that "class objects" could be managed with the same API.

Is this still reproducible in 4.0? (I believe so and it might be tracked in newer issues too, but I didn't check.)


serialization error: model file missing

Hi Doug,
You have "epoch_29_model.hdf5" file here but I found also epoch_24_iou_0.82_morezoom file. Which one should we use? Using "epoch_29..." throw following error:
anaconda3/envs/mvp2/lib/python2.7/site-packages/torch/serialization.py", line 532, in _load
magic_number = pickle_module.load(f)
cPickle.UnpicklingError: invalid load key, 'H'.

epoch_29_model.hdf5 is the correct file.  Which version of tensorflow are you using? Sounds like it could be a version issue.  The model was probably created with an older version of TF.

I'm using Tensorflow 1.11 and tf.keras.version: 2.1.6-tf. What I found so far. You have two version of ggcnn:
ggcnn.py :
calling to "epoch_29_model.hdf5" cause following error:
.local/lib/python2.7/site-packages/tensorflow/python/keras/engine/saving.py", line 251, in load_model
training_config['weighted_metrics'])
KeyError: 'weighted_metrics'
Error seems to be related of Tensorflow and tf.keras.version. Which version did you use for saving the model? I found https://stackoverflow.com/questions/52753846/error-in-load-a-model-saved-by-callbakcs-modelcheckpoint-in-keras solution but not sure.
ggcnn_torch.py:
I guess we should not use "epoch_29_model" here and that cause previous error anaconda3/envs/mvp2/lib/python2.7/site-packages/torch/serialization.py", line 532, in _load
magic_number = pickle_module.load(f)
cPickle.UnpicklingError: invalid load key, 'H'.
Do you have a separate model for torch version?

Hi @dougsm
Which dataset did you use to train your model? is it based on JACQUARD DATASET?

You can read section 4.B in his paper which is referred to in his other paper as the used CNN.

Thank you @aPonza for the hint. It seems to be Dexnet, ACRV, and YCB but
what confused me is the https://github.com/dougsm/ggcnn/tree/master/utils/data with the python file for Cornell and Jacquard dataset.

The model was originally trained on Cornell dataset, as per Closing the loop for robotic grasping.  The Jacquard dataset came out after this paper was published.
We added the Jacquard daset in the extended version of the paper.

For comparison do you have trained model for each dataset separately. E.g. a hdf5 file that is trained only with Cornell dataset,....


Add ability to configure toolbar (block and inline styles)

Followup PR for https://github.com/brijeshb42/medium-draft/pull/99. First PR got corrupted.
Adds ability to configure (in my case, limit) which styles are available for text editing. Allows for changing toolbar dynamically.

Codecov Report

Merging #100 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #100   +/-   ##
=======================================
  Coverage   81.47%   81.47%
=======================================
  Files          15       15
  Lines         340      340
  Branches       48       48
=======================================
  Hits          277      277
  Misses         63       63

Continue to review full report at Codecov.

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

@roy-gbiv Merging this. I will make some changes and then release a new version on npm.

This appears to break passing in custom button sets via props (this.props.blockButtons and this.props.inlineButtons)

@valthon Fixed


[CH] Fix expand transformer can't collect metrics

How was this patch tested?
manual tests

cc @lgbo-ustc @zzcclp

There is a parameter collect_processors in  base class ITransformingStep, should set this to be true instead.

LGTM


Changed the instance resolution in service container when exists simple bind with an explicit instance

The change is used to solve the problem of instances resolution of a app->make(MyService::class, ['param' => 'foo']) call with parameters. Before the change, if you replace a call that is resolved with the callback of the app()->bind() method with an instance provided by the app()->instance() method for the same abstract key, if after doing the "overwriting" of the abstract key instance you call the app->make(MyService::class) method to get an instance of the service without parameters, it will be resolved with the instance provided in the app()->instance() method, but if you make the call to make() with parameters like app->make(MyService::class, ['param' => 'foo']) it will be resolved with the callback provided in the app()->bind() method, so I think the abstract key is not "overwritten" correctly.
With the change, the "overwriting" of the instance provided in the instance() method when make() is called with parameters is now properly resolved. Before the change it was only possible to force an instance to be "overwritten" by the instant() method if the call of the make() method did not come with additional parameters.
This allows mocking for service container elements binded with parameters.
Benefit example:
// For my application I need to define a bind of my service in the service container.

app()->bind(MyService::class, function (Application $app, array $params): MyService {
  return new MyService($params['payload']);
});

// -----------------------------------------------------------------------------------------------

/*
 *  Somewhere in my application I eventually make a call to get an instance of the service.
 *  I could also directly use the app(MyService::class, ['payload' => 'Hello']) call.
 */

app()->make(MyService::class, ['payload' => 'Hello']);

// -----------------------------------------------------------------------------------------------

/*
 *  To mock the service, I instantiate a mock object and invoke the instance method of the service container
 *  to forcibly substitute the resolution of my service so that when the service container is called,
 *  my mock object is returned. This is necessary in a testing context.
 */

$mockInstance = Mockery::mock(MyService::class, function (MockInterface $mock) {
	$mock
	  ->shouldReceive('getMyData')
	  ->andReturn('Forzed return');
  })->makePartial();

app()->instance(
  MyService::class,
  $mockInstance
);

// -----------------------------------------------------------------------------------------------

/*
 *  If I make a call in my code like this to resolve an instance of the service, before the change
 *  proposed by this pull request, it was resolved with the callback of the bind method
 *  and ignored my overwrite of my mock object added by the instance() method
 */
app()->make(MyService::class, ['payload' => 'Hello']);

// Before the change to make this work I could only make the call without parameters like this.

app()->make(MyService::class);

/*
 *  Both calls can now be used with or without additional parameters in the make()
 *  and both will resolve to the instance provided in the instance() method instead of
 *  resolving a new instance by calling the bind() method again.
 */

Mark PR as draft as tests are failing.

With the new correction, the tests are passed and the original behaviour of the singletons is restored, which is what was causing the conflict.

@crynobone I have rewritten the description of the problem and changed the code to pass the tests.
I hope it can help, thanks.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!

Thank you for considering my proposal


Failed prodRelease build on 3.0-release, solvable by disabling minify

Summary:
Pulling from the 3.0-release branch, and building the app in prodDebug works totally fine. But building in prodRelease (which is the variant required for publishing) results in the error:
Execution failed for task ':app:minifyProdReleaseWithProguard'.
java.io.IOException: java.lang.RuntimeException: java.lang.IllegalArgumentException: Value "a" is not an integer value [proguard.evaluation.value.UnknownReferenceValue]

Disabling minify in build.gradle solves the problem, however we have to decide if that is something we want to do, or if there is a better way to solve the problem. Ideally, we should decide soon, as v3.0.1 is way overdue for release.
Steps to reproduce:
Pull from 3.0-release branch, change build variant to prodRelease, add your keys to build.gradle, then try to build.
Device and Android version:
Device agnostic, target SDK 29, Android Studio 4.2.1
Commons app version:
3.0-release

Ah, seems there was an issue with my run config. Solved now, no disabling of minify required.

Hey @misaochan,
My build is failing with the same error log.
Can you recall what was the config issue you were facing?

Ahh, I honestly can't remember sorry. :( I should have been more specific about how I fixed it.


WIP: UX improvements

[x] Fix touchscreen pinch-zoom
[ ] Make node dragging on mouse more robust
[ ] Re-enable creating edges by dragging port

@jonnor I think we should probably merge these before continuining with #364

Reverted that one chance, it does not seem to be neccesary now that #365 is in


MyPlot don't work for Altay

[x] This issue isn't duplicated - you can check if it is by using the search bar located at the top left hand corner and select "Issues" on the left.
[x] This issue includes appropriate markdown for sections - e.g. code blocks for crash dumps.
[x] This issue is understandable - feel free to use your native language to write issues if you are not comfortable with English.

Issue description
What problem do you have?

Reproducing the issue

...
...

Client information
PocketMine-MP Version:
Plugin Version:  latest
PHP version: 7.2.1 (default)

Optional information
Put a console error here, but please make sure you have your debug level set to 2 in your pocketmine.yml

Please learn to read the README. It clearly mentions, NOTE: MyPlot is designed to only support pmmp's version of the PocketMine-MP server software and will not work with third party builds. Any changes to the code in custom installations will not be supported. This includes removing SpoonDetector.


Namespace migration - Fix potential namespace migration problem with one node cluster

Description
kind/bug
The following can happen with a 1 node cluster:

operator updates kube-system/calico-node with node selector - that is successful

{"level":"info","ts":"2024-02-15T12:37:24Z","logger":"controller_windows","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"kube-system","Request.Name":"kube-dns"}
{"level":"info","ts":"2024-02-15T12:37:24Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:37:29Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:37:34Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:37:39Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:37:44Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:37:49Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:37:54Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:37:59Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:38:04Z","logger":"controller_installation","msg":"All kube-system calico/node pods are now ready after nodeSelector update","Request.Namespace":"","Request.Name":"default"}

Once it is ready, it starts make room for typha. That means it scales down kube-system/calico-typha to 0:

{"level":"info","ts":"2024-02-15T12:38:05Z","logger":"controller_installation","msg":"Scaling kube-system/calico-typha deployment to 0 replicas to make room for migration","Request.Namespace":"","Request.Name":"default"}

The next log is showing that after 3 minutes, it starts the migration - however that time, the kube-system/calico-node goes to CrashLoopBackOff already and operator stuck into this state: it tries to calculate ready and desired calico-nodes, but it fails the math, that's why it does not continue - the calculation in function waitUntilNodeCanBeMigrated() does not work (ksR, ksD, csR, csD).

> kubectl get pods --all-namespaces -o wide
NAMESPACE                     NAME                                             READY   STATUS             RESTARTS         AGE   IP               NODE          NOMINATED NODE   READINESS GATES
calico-system                 calico-kube-controllers-56797fd6cc-q4lvg         1/1     Running            0                52m   <IP_ADDRESS>   <IP_ADDRESS>   <none>           <none>
calico-system                 calico-typha-59f74df8d6-krwhz                    1/1     Running            0                52m   <IP_ADDRESS>      <IP_ADDRESS>   <none>           <none>
kube-system                   calico-node-dvg9v                                0/1     CrashLoopBackOff   17 (3m16s ago)   52m   <IP_ADDRESS>      <IP_ADDRESS>   <none>           <none>

{"level":"info","ts":"2024-02-15T12:41:05Z","logger":"controller_installation","msg":"nodes to migrate","Request.Namespace":"","Request.Name":"default","count":1}
{"level":"info","ts":"2024-02-15T12:41:05Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:41:06Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:41:07Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:41:08Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:41:09Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:41:10Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:41:11Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:41:12Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:41:13Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:41:14Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}

Then once we add label projectcalico.org/operator-node-migration=migrated label to the node, it can continue.
➜ kubectl label node <IP_ADDRESS> projectcalico.org/operator-node-migration=migrated --overwrite
node/<IP_ADDRESS> labeled

{"level":"info","ts":"2024-02-15T12:46:39Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:46:40Z","logger":"controller_installation","msg":"Migrated 1 out of 1 nodes","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:46:40Z","logger":"controller_installation","msg":"waiting for calico-node to 1 replicas, ready at 1, up-to-date at 1, available at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:46:45Z","logger":"controller_installation","msg":"waiting for calico-node to 1 replicas, ready at 1, up-to-date at 1, available at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:46:50Z","logger":"controller_installation","msg":"waiting for calico-node to 1 replicas, ready at 1, up-to-date at 1, available at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:46:52Z","logger":"controller_windows","msg":"Reconciling Installation.operator.tigera.io","Request.Namespace":"","Request.Name":"periodic-5m0s-reconcile-event"}
{"level":"info","ts":"2024-02-15T12:46:55Z","logger":"controller_installation","msg":"waiting for calico-node to 1 replicas, ready at 1, up-to-date at 1, available at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:47:00Z","logger":"controller_installation","msg":"waiting for calico-node to 1 replicas, ready at 1, up-to-date at 1, available at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:47:05Z","logger":"controller_installation","msg":"waiting for calico-node to 1 replicas, ready at 1, up-to-date at 1, available at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T12:47:10Z","logger":"controller_installation","msg":"Namespace migration complete","Request.Namespace":"","Request.Name":"default"}

This behaviour can be triggered if minReadySeconds: 15 is set for typhaDeployment in the Installation CR.
Please note that sometimes this can happen faster:
{"level":"info","ts":"2024-02-15T13:51:18Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T13:51:23Z","logger":"controller_installation","msg":"waiting for kube-system/calico-node to have 1 replicas, currently at 0","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T13:51:28Z","logger":"controller_installation","msg":"All kube-system calico/node pods are now ready after nodeSelector update","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T13:51:28Z","logger":"controller_installation","msg":"Scaling kube-system/calico-typha deployment to 0 replicas to make room for migration","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T13:51:48Z","logger":"controller_installation","msg":"nodes to migrate","Request.Namespace":"","Request.Name":"default","count":1}
{"level":"info","ts":"2024-02-15T13:51:48Z","logger":"controller_installation","msg":"Max unavailble nodes calculation resolved to 0, defaulting back to 1 to allow upgrades to continue","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T13:51:49Z","logger":"controller_installation","msg":"Migrated 1 out of 1 nodes","Request.Namespace":"","Request.Name":"default"}
{"level":"info","ts":"2024-02-15T13:51:49Z","logger":"controller_installation","msg":"waiting for calico-node to 1 replicas, ready at 0, up-to-date at 1, available at 0","Request.Namespace":"","Request.Name":"default"}

That's why add this simple logic which has effect only on 1 node clusters.
Change is well-tested (namespace migration is built into our CI process, so dozens tests are executed)
I would like to cherry pick this change to 1.32 and 1.33 if possible. Thanks!
For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

I think this checks out, but @tmjd knows the logic here a bit better than I do.

/sem-approve

@tmjd Hi! Could you please take a look? Thank you!

/sem-approve

Thank you for this fix @mihivagyok
I'll be mentioning the nice work you've done on this and other PRs in the Calico community meeting on Wednesday April 10. You're welcome to join if you're available and interested.


[Impeller] RuntimeEffect: Register the shader function earlier

Right now we register the shader inline in RuntimeEffectContents on the first frame. We can schedule the shader compilation to happen sooner after the asset is loaded by FragmentProgram.

Draft PR that partially does this here: https://github.com/jonahwilliams/engine/pull/new/early_registration though currently this is blocking on the UI thread.
The registration would need to substantially refactored to move this into a worker thread. That said, even with the blocking change there is a delay in showing the shader (Skia or Impeller).
I suspect that we require a framework change to allow the ink_sparkle to get eagerly registered instead of waiting for first use.

Coming back to this - on Android Vulkan, its taking 12ms for the first variant of the ink sparkle shader to be compiled, subsequent variants are much faster. I suspect that whether or not we block on it, we need to at least kick off the initial compilation to be avoid dropping frames.


Reformat inspect network settings

Reformat ports of inspect network settings to compatible with docker inspect. Close #5380
Signed-off-by: Qi Wang<EMAIL_ADDRESS>

LGTM

LGTM
Assuming happy tests

@mheon @TomSweeneyRedHat PTAL. Changed the e2e tests to get passed.

/approve
/lgtm


Fix: open static server after build

If you say so, I don't even use this feature.

That said, after 0.9, I won't accept any commit without a test to prove the thing ^^

That said, after 0.9, I won't accept any commit without a test to prove the thing ^^

flow would help us here. but src/bin/server.js needs a lot of love to be able to use flow.

Current coverage is 68.11%

Merging #322 into next will increase coverage by +0.78% as of d0084c6

@@             next    #322   diff @@
=====================================
  Files          42      43     +1
  Stmts         548     552     +4
  Branches        0       0
  Methods
=====================================
+ Hit           369     376     +7
  Partial         0       0
+ Missed        179     176     -3

Review entire Coverage Diff as of d0084c6

Powered by Codecov. Updated on successful CI builds.


Reduced amount of duplicated code in tests. (#13989)

backport of https://github.com/arangodb/arangodb/pull/13989

https://jenkins.arangodb.biz/job/arangodb-ANY-matrix/36/

@dothebart please look into the following test:
* Test "resilience_failover_failure"
    [FAILED]  tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js

      "test" failed: Cleanup missing - test left over collections / views : UnitTestSyncRep / . Original test status: {"setUpAllDuration":{"SynchronousReplicationSuite":0},"testCheckInstanceInfo":{"setUpDuration":74,"tearDownDuration":1,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":0},"testSetup":{"setUpDuration":60,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1021},"testBasicOperationsFollowerFail1":{"setUpDuration":38,"tearDownDuration":1,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14548/_admin/debug/failat/LogicalCollection::insert'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:405:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:214:5)\n    at Object.testBasicOperationsFollowerFail1 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:403:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1018},"testBasicOperationsFollowerFail2":{"setUpDuration":37,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14597/_admin/debug/failat/LogicalCollection::read'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:421:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:220:5)\n    at Object.testBasicOperationsFollowerFail2 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:419:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1020},"testBasicOperationsFollowerFail3":{"setUpDuration":39,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14530/_admin/debug/failat/LogicalCollection::insert'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:437:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:220:5)\n    at Object.testBasicOperationsFollowerFail3 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:435:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1022},"testBasicOperationsFollowerFail5":{"setUpDuration":35,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14530/_admin/debug/failat/LogicalCollection::replace'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:453:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:220:5)\n    at Object.testBasicOperationsFollowerFail5 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:451:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1023},"testBasicOperationsFollowerFail7":{"setUpDuration":41,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14548/_admin/debug/failat/LogicalCollection::replace'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:469:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:220:5)\n    at Object.testBasicOperationsFollowerFail7 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:467:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1024},"testBasicOperationsFollowerFail9":{"setUpDuration":42,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14597/_admin/debug/failat/LogicalCollection::update'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:485:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:220:5)\n    at Object.testBasicOperationsFollowerFail9 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:483:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1022},"testBasicOperationsFollowerFail14":{"setUpDuration":39,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14530/_admin/debug/failat/LogicalCollection::remove'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:501:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:220:5)\n    at Object.testBasicOperationsFollowerFail14 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:499:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1022},"testBasicOperationsCombinedFail1_2_3":{"setUpDuration":38,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14548/_admin/debug/failat/LogicalCollection::insert'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:517:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:214:5)\n    at Object.testBasicOperationsCombinedFail1_2_3 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:515:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1015},"testBasicOperationsCombinedFail3_4":{"setUpDuration":39,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14548/_admin/debug/failat/LogicalCollection::insert'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:538:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:225:5)\n    at Object.testBasicOperationsCombinedFail3_4 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:536:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1023},"testBasicOperationsCombinedFail5_6":{"setUpDuration":43,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14597/_admin/debug/failat/LogicalCollection::replace'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:558:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:238:5)\n    at Object.testBasicOperationsCombinedFail5_6 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:556:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1022},"testBasicOperationsCombinedFail7_8":{"setUpDuration":39,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14597/_admin/debug/failat/LogicalCollection::replace'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:578:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:248:5)\n    at Object.testBasicOperationsCombinedFail7_8 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:576:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1027},"testBasicOperationsCombinedFail9_10":{"setUpDuration":39,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14530/_admin/debug/failat/LogicalCollection::update'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:598:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:259:5)\n    at Object.testBasicOperationsCombinedFail9_10 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:596:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1030},"testBasicOperationsCombinedFail11_12":{"setUpDuration":37,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14597/_admin/debug/failat/LogicalCollection::update'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:618:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:270:5)\n    at Object.testBasicOperationsCombinedFail11_12 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:616:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1032},"testBasicOperationsCombinedFail14_15":{"setUpDuration":40,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14548/_admin/debug/failat/LogicalCollection::remove'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:638:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:294:5)\n    at Object.testBasicOperationsCombinedFail14_15 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:636:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1039},"testBasicOperationsCombinedFail17_18":{"setUpDuration":37,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14530/_admin/debug/failat/LogicalCollection::remove'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as put] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugSetFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:67:21)\n    at failFollower (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:136:7)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:658:11\n    at runBasicOperations (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:313:5)\n    at Object.testBasicOperationsCombinedFail17_18 (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:656:7)\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:549:27)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - test failed\nSyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":1042},"testDummy":{"setUpDuration":37,"tearDownDuration":0,"status":false,"message":"SyntaxError: unsupported URL specified: 'tcp://<IP_ADDRESS>:14596/_admin/debug/failat'\n    at request (/work/ArangoDB/js/common/modules/@arangodb/request.js:203:25)\n    at Function.request.<computed> [as delete] (/work/ArangoDB/js/common/modules/@arangodb/request.js:219:12)\n    at exports.debugClearFailAt (/work/ArangoDB/js/server/modules/@arangodb/test-helper.js:97:27)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:365:9\n    at Array.forEach (<anonymous>)\n    at Object.tearDown (tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:363:15)\n    at /work/ArangoDB/js/common/modules/jsunity/jsunity.js:483:16\n    at Object.run (/work/ArangoDB/js/common/modules/jsunity/jsunity.js:554:19)\n    at Object.Run [as run] (/work/ArangoDB/js/common/modules/jsunity.js:288:24)\n    at tests/js/server/resilience/failover-failure/resilience-synchronous-repl-failureAt-cluster.js:685:9 - tearDown failed","duration":0},"teardownAllDuration":{"SynchronousReplicationSuite":0},"duration":17163,"status":false,"failed":18,"total":18,"totalSetUp":754,"totalTearDown":2,"processStats":{"22034_agent":{"minorPageFaults":114,"majorPageFaults":0,"userTime":0.14999999999999997,"systemTime":0.12999999999999998,"numberOfThreads":0,"residentSize":393216,"residentSizePercent":0.000006219799149727312,"virtualSize":0,"rchar":4488,"wchar":129598,"syscr":561,"syscw":763,"read_bytes":0,"write_bytes":249856,"cancelled_write_bytes":0,"sockstat_sockets_used":411,"sockstat_TCP_inuse":410,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":1460,"sockstat_TCP_alloc":420,"sockstat_TCP_mem":57,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0},"22035_agent":{"minorPageFaults":285,"majorPageFaults":0,"userTime":0.57,"systemTime":0.33,"numberOfThreads":-1,"residentSize":-3092480,"residentSizePercent":-0.00004891612872962763,"virtualSize":-8409088,"rchar":20696,"wchar":145812,"syscr":2587,"syscw":2789,"read_bytes":0,"write_bytes":253952,"cancelled_write_bytes":0,"sockstat_sockets_used":411,"sockstat_TCP_inuse":410,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":1460,"sockstat_TCP_alloc":420,"sockstat_TCP_mem":57,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0},"22036_agent":{"minorPageFaults":121,"majorPageFaults":0,"userTime":0.16999999999999993,"systemTime":0.1299999999999999,"numberOfThreads":0,"residentSize":544768,"residentSizePercent":0.000008617013405351742,"virtualSize":0,"rchar":2400,"wchar":127516,"syscr":300,"syscw":502,"read_bytes":0,"write_bytes":249856,"cancelled_write_bytes":0,"sockstat_sockets_used":411,"sockstat_TCP_inuse":410,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":1460,"sockstat_TCP_alloc":420,"sockstat_TCP_mem":57,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0},"22206_dbserver":{"minorPageFaults":637,"majorPageFaults":0,"userTime":0.33000000000000007,"systemTime":0.18000000000000005,"numberOfThreads":2,"residentSize":950272,"residentSizePercent":0.000015031181278508249,"virtualSize":49324032,"rchar":157063,"wchar":38328,"syscr":1259,"syscw":1259,"read_bytes":0,"write_bytes":102400,"cancelled_write_bytes":0,"sockstat_sockets_used":411,"sockstat_TCP_inuse":410,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":1460,"sockstat_TCP_alloc":420,"sockstat_TCP_mem":57,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0},"22207_dbserver":{"minorPageFaults":649,"majorPageFaults":0,"userTime":0.3799999999999999,"systemTime":0.13,"numberOfThreads":2,"residentSize":876544,"residentSizePercent":0.000013864968937934378,"virtualSize":49324032,"rchar":195301,"wchar":35034,"syscr":1243,"syscw":1251,"read_bytes":0,"write_bytes":94208,"cancelled_write_bytes":0,"sockstat_sockets_used":411,"sockstat_TCP_inuse":410,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":1460,"sockstat_TCP_alloc":420,"sockstat_TCP_mem":57,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0},"22208_dbserver":{"minorPageFaults":191,"majorPageFaults":0,"userTime":0.4600000000000001,"systemTime":0.09000000000000008,"numberOfThreads":0,"residentSize":552960,"residentSizePercent":0.00000874659255430425,"virtualSize":0,"rchar":6104,"wchar":30978,"syscr":762,"syscw":814,"read_bytes":0,"write_bytes":151552,"cancelled_write_bytes":0,"sockstat_sockets_used":411,"sockstat_TCP_inuse":410,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":1460,"sockstat_TCP_alloc":420,"sockstat_TCP_mem":57,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0},"22209_dbserver":{"minorPageFaults":727,"majorPageFaults":0,"userTime":0.3500000000000001,"systemTime":0.17000000000000004,"numberOfThreads":2,"residentSize":1179648,"residentSizePercent":0.00001865939744918237,"virtualSize":57712640,"rchar":186438,"wchar":39589,"syscr":1290,"syscw":1310,"read_bytes":0,"write_bytes":102400,"cancelled_write_bytes":0,"sockstat_sockets_used":411,"sockstat_TCP_inuse":410,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":1460,"sockstat_TCP_alloc":420,"sockstat_TCP_mem":57,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0},"22210_dbserver":{"minorPageFaults":216,"majorPageFaults":0,"userTime":0.3800000000000001,"systemTime":0.10999999999999999,"numberOfThreads":0,"residentSize":577536,"residentSizePercent":0.000009135330001162206,"virtualSize":8388608,"rchar":5400,"wchar":29989,"syscr":675,"syscw":726,"read_bytes":0,"write_bytes":139264,"cancelled_write_bytes":0,"sockstat_sockets_used":411,"sockstat_TCP_inuse":410,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":1460,"sockstat_TCP_alloc":420,"sockstat_TCP_mem":57,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0},"22211_coordinator":{"minorPageFaults":12819,"majorPageFaults":0,"userTime":1.31,"systemTime":0.28,"numberOfThreads":0,"residentSize":7991296,"residentSizePercent":0.00012640445980331705,"virtualSize":158048256,"rchar":2257926,"wchar":63303,"syscr":2038,"syscw":1516,"read_bytes":0,"write_bytes":61440,"cancelled_write_bytes":0,"sockstat_sockets_used":411,"sockstat_TCP_inuse":410,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":1460,"sockstat_TCP_alloc":420,"sockstat_TCP_mem":57,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0},"sum_servers":{"minorPageFaults":15759,"majorPageFaults":0,"userTime":4.1,"systemTime":1.55,"numberOfThreads":5,"residentSize":9973760,"residentSizePercent":0.00015776261384985992,"virtualSize":314388480,"rchar":2835816,"wchar":640147,"syscr":10715,"syscw":10930,"read_bytes":0,"write_bytes":1404928,"cancelled_write_bytes":0,"sockstat_sockets_used":3699,"sockstat_TCP_inuse":3690,"sockstat_TCP_orphan":0,"sockstat_TCP_tw":13140,"sockstat_TCP_alloc":3780,"sockstat_TCP_mem":513,"sockstat_UDP_inuse":0,"sockstat_UDP_mem":0,"sockstat_UDPLITE_inuse":0,"sockstat_RAW_inuse":0,"sockstat_FRAG_inuse":0,"sockstat_FRAG_memory":0}}}

   Suites failed: 1 Tests Failed: 0

This test failed in all platforms in cluster within this PR.

only one unrelated recovery test red: tests/js/server/recovery/nosync-rangedelete-truncate-indexes2.js:
failed: unable to run recovery test

https://jenkins.arangodb.biz/job/arangodb-matrix-pr-linux/16536/

https://jenkins.arangodb.biz/job/arangodb-matrix-pr-linux/16537/

https://jenkins.arangodb.biz/job/arangodb-ANY-matrix/37/

https://jenkins.arangodb.biz/job/arangodb-ANY-mac-matrix/1834/


add solutions 04

binder link: https://mybinder.org/v2/gh/sroet/chemometrics/add_solutions_4

LGTM


Use pyproject.toml in the plugin examples

Not sure how much I can design this, ultimately I want it to address #2810, but for now there are some low-hanging fruits:

Use pyproject.toml in the examples

/packit build

/packit test

/packit build

/packit build

/packit test

@LecrisUT there seems to be some issue on CentOS Stream 9, see https://artifacts.dev.testing-farm.io/4c90b5bc-8174-4c64-b7e3-8c5f392d5bcc/work-advancedjytot00y/plans/features/advanced/execute/data/guest/default-0/tests/plugins-15/output.txt. Maybe older-than-expected packaging infrastructure, not supporting the feature?

Weird, why does it give UNKNOWN, just double-checked and I did populate name. Maybe it's the lack of build-system.build-backend. Can you try out quickly with setuptools or hatchling, otherwise I'll try it next week (still on train rn)

Weird, why does it give UNKNOWN, just double-checked and I did populate name. Maybe it's the lack of build-system.build-backend. Can you try out quickly with setuptools or hatchling, otherwise I'll try it next week (still on train rn)

No worries, next week is absolutely fine. It's Saturday after all. I just wanted to put a status update so you're aware.

Note to self: add --no-index to the pip install. Just as a sanity check that all dependencies are from the system. What about --no-build-isollation as well?

Ok, seems setuptools 53.0.0 is just unusable for PEP517, hatchling still works though, so might as well switch the backend.

/packit build


Works on linux.

See issue: https://github.com/profesorfalken/jPowerShell/issues/26

Works well on master. More work needed to fix develop branch.....look for a future pull request on develop.

Not needed - version 3.1.1 is working on linux.