adds name, value, SlackConfirmationField to slack action

Fixes #1556. Either URL or Name and Value need to be provided in slack action. LGTY @simonpasquier? Thanks in advance

test failures seem unrelated. fails for current master on my machine - without above changes - as well

Hmm, I'm definitely baffled by the lack of consistency in the Stack documentation. https://api.slack.com/docs/interactive-message-field-guide#action_fields says that name, text and type are mandatory while https://api.slack.com/docs/message-attachments#action_fields doesn't mention name and states that url is mandatory. I'd be reluctant to merge a change without more insights on the right way.
@stuartnelson3 any thoughts on this?

I agree the slack API is quite confusing.
I understood, there are (at least) 2 types of buttons in slack: message and link buttons in a slack action.
The API says type, text, url are ..required when using link buttons (https://api.slack.com/docs/message-attachments#action_fields).
While message buttons as specified here need to have name, text, type.

Also extended tests. LGTY @simonpasquier?

Anything else that needs to be done @simonpasquier?

uses tmplText() on SlackConfirmationField. LGTY @simonpasquier?

Thanks for your patience @auhlig. I'll give it a try as I happen to have access to a Slack instance...
Once it is merged, the documentation would need updates too.

Added check and opened PR for docs @simonpasquier

Not sure why (only) travis complains. Do I need to run make assets here?

Tested with slack. Works for me (TM).
Will update https://github.com/prometheus/docs/pull/1196 today.
Would you mind taking another look @simonpasquier?

Tested with slack. Works for me (TM).
Will update https://github.com/prometheus/docs/pull/1196 today.
Would you mind taking another look and consider merging @simonpasquier? :heart:

Tested with slack. Works for me (TM).
Will update https://github.com/prometheus/docs/pull/1196 today.
Would you mind taking another look and consider merging @simonpasquier? :heart:

CI is green. Tested with slack. Works for me (TM)
Will update the docs PR today.
Would you mind taking another look and can we consider merging @simonpasquier? :heart:

Did slack attachments ever work?

They surely did. TBH Slack is terrible at dealing with backward compatibility: things that used to work at time T may break at time T+N for some users and continue to work for the others. I wouldn't include https://github.com/prometheus/alertmanager/pull/1557/commits/f61c50dfe2a79eb164135ca418eae0083188e415 in this PR as it is unrelated. If it is broken with the current master, please file an issue with all relevant details and it should be addressed separately.

Ewww slack -.-
Extracted the callback_id to https://github.com/prometheus/alertmanager/pull/1592 and reset this PR to the last approved commit. Sorry for the back- and forth. Is this good to go @simonpasquier?

:+1: cc @mxinden @stuartnelson3

Yes thanks for the work @auhlig. That was more involved than expected!

Thanks guys ❤


⚠ Secret Website 3 has degraded performance

In 09c28f4, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2129 ms

Resolved: Secret Website 3 performance has improved in 996bce0.

Resolved: Secret Website 3 performance has improved in 996bce0.


Incompatible AWS Version

Hi! I'm trying to use this package but when trying the command sudo python3 s3sync.py --config config.yaml init it shows the message Error: Found incompatible AWS CLI version [2.0.62]. Removed that version and installed the AWS CLI 2.0.0 and the same error is showing.
Same happening with s3sync --config ./config.yaml init
Error: Found incompatible AWS CLI version [2.0.0]
AWS Version
aws --version
aws-cli/2.0.0 Python/3.7.3 Linux/5.4.0-52-generic botocore/2.0.0dev4
Ubuntu 20.04

Thanks you just reported a minor bug. I just fixed it and push an updated version (https://pypi.org/project/pys3sync/0.1.2/). Please try now. What was happening was that due to a naive string comparison, your version [2.0.62] was < [2.0.9] because I was doing just a string comparison. now using python package version comparison.

Also please go back to 2.0.62. it won't work with 2.0.0. needs atleast 2.0.9


i18n(zh-cn): Update recipes.mdx

What kind of changes does this PR include?

New or updated content
Translated content

Description

Update recipes.mdx
Follow up https://github.com/withastro/docs/pull/3891

LGTM


Songal - changing input

Home Assistant release with the issue: 0.89.2
Last working Home Assistant release (if known): not known, it's been here for a while
Operating environment (Hass.io/Docker/Windows/etc.): hass.io
Component/platform: songpal
Description of problem:
I'm using a Sony SRS-X77 speaker.
From home-assistant, when switching the input  (for example from Bluetooth Audio to Audio in):

the media_player entity becomes unavailable in home assistant for around 10 seconds,
however, the device itself behaves as asked,
the two logs below (in the Traceback section) appear.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
media_player:
  - platform: songpal
    name: sony_bureau
    endpoint: !secret endpoint_songpal_bureau

endpoint_songpal_bureau looks like : http://192.168.xx.xxx:54480/sony
Traceback (if applicable):
_18:21 __main__.py (WARNING)_
Got unknowns for ContentChange: {'parentUri': '', 'stateInfo': {'state': ''}} - please create an issue!

_18:21 components/media_player/songpal.py (ERROR)_
Got disconnected with Unable to make a request: 'extInput:line': None, trying to reconnect.

Additional information:
In an older version of home assistant (not showing anymore), I used to saw log mentioning that it got two versions (1.0 & 1.1 if I remember correctly), and that it used the first version (which is NOT the latest).
This may not be related, though.

the issue still exists the latest version og home assistant: 0.95.4

Could you please enable debug logging for the songpal library and this integration, and post a log when this happens? That warning about unknowns is not the problem here. For some reason an exception is raised by the backend library (showing as 'extInput:line': None) is the real cause. This is potentially related to https://github.com/rytilahti/python-songpal/issues/5 .
Also, your note about the used version is helpul, and I think the upstream library should do a better job sticking to the newest as announced by the device.

hi, I added the following to my config (and restarted):
logger:
  default: warn
  logs:
    homeassistant.components.songpal: debug

unfortunately, I didn't get more logging than in my first post :/
maybe the component namespace is wrong? but I don't know how to verify this.

Add also songpal: debug and you will start seeing the communications with the device itself.

switching from Audio In to Bluetooth Audio, I got:
2019-07-15 20:32:46 DEBUG (MainThread) [songpal.service] setPlayContent got called with args (()) kwargs ({'uri': 'extInput:btAudio'})
2019-07-15 20:32:46 DEBUG (MainThread) [songpal.method] Got no response, assuming success
2019-07-15 20:32:46 WARNING (MainThread) [songpal.containers] Got unknowns for ContentChange: {'parentUri': '', 'stateInfo': {'state': ''}} - please create an issue!
2019-07-15 20:32:46 DEBUG (MainThread) [songpal.containers] Missing key service with no default for ContentChange
2019-07-15 20:32:46 DEBUG (MainThread) [songpal.containers] Missing key applicationName with no default for ContentChange
2019-07-15 20:32:46 DEBUG (MainThread) [songpal.service] Got notification: ContentChange(contentKind='input', service=None, source='extInput:btAudio', uri='extInput:btAudio', applicationName=None)
2019-07-15 20:32:46 DEBUG (MainThread) [homeassistant.components.songpal.media_player] Source changed: ContentChange(contentKind='input', service=None, source='extInput:btAudio', uri='extInput:btAudio', applicationName=None)
2019-07-15 20:32:46 DEBUG (MainThread) [homeassistant.components.songpal.media_player] New active source: Bluetooth Audio (uri: extInput:btAudio)
2019-07-15 20:32:46 WARNING (MainThread) [songpal.service] Got unknown notification type: notifyAvailablePlaybackFunction
2019-07-15 20:32:46 DEBUG (MainThread) [songpal.service] Got notification: None
2019-07-15 20:32:46 DEBUG (MainThread) [songpal.device] No callbacks for None

Does it come unavailable when doing that? I don't see the error there, so I'm wondering what'd cause it to become unavailable...
Also, does that happen always or does it just happen when changing to some specific input? Is the issue I linked above potentially related to ths issue?

indeed, the error is different, but the result is the same: the media_player entity becomes unavailable.
it happens for all inputs.
actually, it even happens on HA when changing the input directly on the device.

I understand, but in order to fix it I have to see where it goes wrong, otherwise it would be just guessing why this happens. The cause itself is that the request causes an unexpected error when calling the method to change the input, any unexpected errors will be raised as exceptions in which case the availability is set to unavailable.
It could very well be, that the implementation is trying to use the 1.1 version of parameters while calling the 1.0 version of the API..
Could you run songpal dump-devinfo somefile.json and compare it to https://github.com/rytilahti/python-songpal/blob/master/devinfos/SRS-X77.json ? setPlayContent under avContent service is the one that is being used to change the input.


3.6 doc updates

Some 3.6 doc updates working through release PR spreadsheet

Thanks Jason, updated

+1

Verified on docs.mattermost.com


Language specific encoding not applied if "Open with Code" is used and VSCode is not running

Visual Studio Code 1.26.1 on Windows 10 and Windows Server 2016.
I have added a language specific encoding to my user settings:
"files.autoGuessEncoding": false,
"[perl]": {
    "files.encoding": "cp850",
},

If I open a perl file from within Visual Studio Code (File -> Open File...), the correct encoding is applied.
If Visual Studio Code is running and I open a perl file from Explorer using "Open with Code" context menu, the correct encoding is applied.
If Visual Studio Code is not running and I open a perl file from Explorer using "Open with Code" context menu, the correct encoding is NOT applied.
Starting Visual Studio Code from the command line with a perl file as parameter produces the same results.

Vsc restart

Open code

Not sure what you are saying, but restarting VSCode does not help.

I can reproduce. If I add a console.log to the place where we read the encoding for the file (here) I can see that I get a value of utf8 at first (right on startup) and then later when I ask again, it is the correct encoding. Seems like an issue with the configuration service returning wrong values on startup to me.

@bpasero Configuration service is returning the right value. But the language/mode that is being provided is not right.

In the above screenshot, IModelService / IModeService is first returning plainText as the languageId and is returning perl after some time. Guessing that the ModeService is not yet initialised by then?

@alexandrudima adding you based on the findings from https://github.com/Microsoft/vscode/issues/57061#issuecomment-415678631

Interestingly the status bar changes from "Plain Text" to "Perl" after some time, so there is probably a language mode change at a later point in time and the encoding does not react to that.

This is not easy to fix because we do not want the editor to wait for the extension host to come up before loading the contents and we need an encoding when loading the file. If the language mode changes after we have loaded the file we can also not just reopen the file with a different encoding because the user might have made changes that got saved back to disk in the default encoding (utf8). Not sure what to do here, maybe show a notification when we detect this case...

I have used jEdit for a few years and it does two things that might be usable workarounds in this issue:

You can run jEdit in "server mode", it starts when you log on and runs in the background. If VSCode did that the correct encoding would be applied to all files opened.
You can add a comment to the file, either in the first 10 or last 10 lines, that instructs jEdit to use a specific encodint, i e "# :encoding=CP850:".

@bpasero This is a dup of https://github.com/Microsoft/vscode/issues/39084

@sandy081 wow, how did I not see that...
Thanks!


Question about the websocket example

Hi, I'm playing with this library and I have a question about the websocket example. It implements Notifiable for the sink part of the connection, but the stream part is where we want to get notified about, right? Or am I understanding it totally wrong :)

Hey! In this particular example we're using spawn_stream_forwarder to automatically turn new items in the stream into messages. Which is why we need Notifiable for the sink part: each received message will turn into a notification that we're processing.

Aha! Thank you :)
Will implementing it for a stream like this work, or should it go via Sink? My idea was to have two actors for a websocket connection; one for sending, and one for receiving. I could of course just try, but I would like to understand :)
pub struct ReceiveActor<T: Stream> {
    receiver: T,
    send_addr: Address<SendActor>
}

impl<T> ReceiveActor<T>
where
    T: Stream,
{
    pub fn new(send_addr: Address<SendActor>, receiver: T) -> Self {
        Self { receiver, send_addr }
    }
}

impl<T> Actor for ReceiveActor<T>
where
    T: Stream + Unpin + Send + Sync + Sized + 'static
{
}

#[async_trait]
impl<T> Notifiable<Result<tungstenite::Message, WsError>> for ReceiveActor<T>
where
    T: Stream + Send + Sync + Unpin + 'static,
{
    async fn notify(&mut self, input: Result<tungstenite::Message, WsError>, context: &Context<Self>) {
        let msg = match input {
            Ok(msg) => msg,
            Err(_err) => return,
        };

        // etc.
    }
}

I guess two actors (one for sending and one for receiving) make sense in general; although it might be hard to "match" requests and responses (e.g. if you submit something to websocket and expect a response). Probably, actor system for sending messages would work much better for a particular use case, e.g. JSON RPC, where you can match requests with responses. This way, you can implement a single actor for this communication, and use Handler to represent requests with the return value being a response.
Although if you want to turn both stream and sink into actors, I guess Handler would work for stream better, since you probably want to notify caller if submitting a request fails (though obviously depends on the design).

Sending and receiving messages are decoupled at the moment. I thought to get updates from the stream via Notifiable, and have the actor for sending only implement Handler (gets triggered from the UI or from elsewhere) and send to sink.

That would probably work :)
I'll close the issue, if you have any follow-up questions -- feel free to either post here or open a new issue.


⚠ Bofrost.be has degraded performance

In 8256518, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 810 ms

Resolved: Bofrost.be performance has improved in 246222c after 6 minutes.


updated expected value and syntax for plant growth medium [MIXS:0001057]

Current term details
Term name - plant growth medium
Term ID - MIXS:0001057
Structured comment name - plant_growth_med
Definition - Specification of the media for growing the plants or tissue cultured samples, e.g. soil, aeroponic, hydroponic, in vitro solid culture medium, in vitro liquid culture medium. Recommended value is a specific value from EO:plant growth medium (follow this link for terms http://purl.obolibrary.org/obo/EO_0007147) or other controlled vocabulary
Expected value - EO
Value syntax - {termLabel} {[termID]}
Example - hydroponic plant culture media [EO:0007067]

Suggested update(s)
Term name - plant growth medium
Term ID - MIXS:0001057
Structured comment name - plant_growth_med
Definition - Specification of the media for growing the plants or tissue cultured samples, e.g. soil, aeroponic, hydroponic, in vitro solid culture medium, in vitro liquid culture medium. Recommended value is a specific value from EO:plant growth medium (follow this link for terms http://purl.obolibrary.org/obo/EO_0007147) or other controlled vocabulary
**Expected value - EO or enumeration **
** Value syntax - {termLabel} {[termID]} or [husk|other artificial liquid medium|other artificial solid medium|peat moss|perlite|pumice|sand|soil|vermiculite|water] **
Example - hydroponic plant culture media [EO:0007067]

Additional context

I dont recall discussion of this item, but the change has been made in the MIxS6 packages - to edit spreadsheet already. so i've added it to the change log.


How to watch and reload overview file?

If I watch overview file with gulp.watch and then run styleguide:generate for the changes, I can see the website trying to be updated (progressbar works). But it does not update the rendered overview text. The new text is only visible when restarting the styleguide task.

This is duplicate to #610. Please see related issue for more information


Add fgenesh tool

Need to check button link works ok, and are multiple input file types ok on a single line

@AnnaSyme I check the link and made some changes, here's how it looks. Feel free to edit further if necessary:


Usage with torch2trt

I have been using torch2trt to export my models, but I have been seeing that my application is spending a significant portion of time copying data back and forth between the CPU and GPU on my Xavier, so I am interested in using the ZeroCopy memory.
However, in my tests, it seems that the TRTModule wont accept the image capsule object provided by jetson-utils. Is this a suported usecase? If not, how can I use my own custom models with the imageNet/tensorNet classes provided by jetson-inference?
Thanks!

Hi @chunter18 , I believe torch2trt expects to recieve PyTorch tensors, to maintain compatibility with PyTorch.   However you could call .cuda() on those tensors first.
Is it only doing the memory transfers before the model and then after the model?   You may be able to manage that better yourself by putting the tensors on GPU yourself before calling the model.
To use it through jetson-inference, you would need to export the model to ONNX.   You can see an example of how this is done for classification models:
https://github.com/dusty-nv/pytorch-classification/blob/5107de352cade326e7aacd44bf8d625b7055fd4e/onnx_export.py
What model are you using?   To support it in jetson-inference, you would want to make sure the pre-processing coefficients match what PyTorch is using (like mean pixel subtraction, normalization, and std deviation):
https://github.com/dusty-nv/jetson-inference/blob/8498115a4ed8967c7e23f5ae27b5aa2fa1d1431b/c/imageNet.cpp#L433

Hey @dusty-nv:
My use case is a pretty standard classifier application - frames come in via OpenCV, which I turn into torch tensors and send to the GPU using .cuda(), and, the result logits are passed back to the CPU using .cpu() for further use. Its actually the .cpu() calls that are taking most of the time according to cProfile, but I assume using ZeroCopy memory would save me time both ways.
I'm using a few ResNet based models - I can easily export them to onnx, but is there an example showing how to load them using the jetson.inference.imageNet class? I have only been able to find examples showing the usage of the models downloaded as part of the installation process.
Thanks for the help so far!

If you check here, it shows the syntax for loading your own classification model from ONNX:
https://github.com/dusty-nv/jetson-inference/blob/master/docs/pytorch-cat-dog.md#processing-images-with-tensorrt
https://github.com/dusty-nv/jetson-inference/blob/master/docs/pytorch-collect.md#training-your-model
Those tutorials go through training your own model and exporting it to ONNX.  That command line to load your own ONNX model expects the input/output node names to be set the way they are in my onnx_export.py script.

Thanks Dustin, that's exactly what I needed. Ill close out the issue.


Handle std out and std err for the python daemon

Currently the std out and std err generated from the c code is not captured.
A simple redirect part of setsid and watchdog command does not seem to work (needs to experimenting).
One option is to redirect the std out and err from python itself.
There is useful debugging information that we currently miss out on.

Not critical. Aimed at GA opportunistically.

Error reporting has been improved and relying on the return code from python daemon, closing this as invalid.


Support rolling CoreOS updates

Locking Deis releases to specific CoreOS releases is both inconvenient and not the intended release path for CoreOS - instead, we should be subscribing to the beta channel and using the update-engine service with locksmith to ensure that only one node in a cluster is rebooted at any one time. This is The CoreOS Way(tm).
In order to achieve this in Deis, a few things need to be completed:

Remove the oneshot unit which disables the CoreOS automatic updater service
Add locksmith configuration to the user-data file (https://github.com/coreos/coreos-cloudinit/blob/master/Documentation/cloud-config.md#update)
Bind the deis-database-data and builder-database-data services to the deis-database and deis-builder (respectively) machines, so that fleet will not try to move them when the database or builder machines are rebooted (#1038)

This is not something we'll be able to get to for the LTS release (#4776), and provisioning Deis v2 is done through installing a vanilla kubernetes cluster so I'm going to go ahead and close this.


[Debugger] If multiple variables have the same name, VSCode doesn't show one of them.

Version: 1.52.1 (system setup)
Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Date: 2020-12-16T16:34:46.910Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.18363
Steps to Reproduce:
This issue can be reproduced by using the Python extension to debug the following code:
class T:
    def __init__(self, name, value):
        self.name = name
        self.value = value
    def __repr__(self):
        return self.name

td = {T("foo", 24): "bar",
      T("gad", 42): "zooks",
      T("foo", 12): "bur"}

print("Keys: " + str((td.keys())))
print("Values: " + str((td.values()))) # Breakpoint here

At that point, expanding the td dictionary in the variables view should show 3 entries, yet in only shows 2.
The variables request being returned from debugpy is properly returning a foo entry twice (as expected), but VSCode only shows one entry. The Debug Adapter Protocol doesn't place any restrictions on having unique names for the variables, so, this seems like an issue in VSCode (although if that's not the case and there should be a restriction there, please let me know so that debugpy can be fixed accordingly).
{
     "pydevd_cmd_id": 502,
     "seq": 50,
     "type": "response",
     "request_seq": 20,
     "success": true,
     "command": "variables",
     "body": {
         "variables": [
             {
                 "name": "special variables",
                 "value": "",
                 "type": "",
                 "variablesReference": 8
             },
             {
                 "name": "function variables",
                 "value": "",
                 "type": "",
                 "variablesReference": 9
             },
             {
                 "name": "foo",
                 "value": "'bar'",
                 "type": "str",
                 "evaluateName": "td[foo]",
                 "variablesReference": 0,
                 "presentationHint": {
                     "attributes": [
                         "rawString"
                     ]
                 }
             },
             {
                 "name": "gad",
                 "value": "'zooks'",
                 "type": "str",
                 "evaluateName": "td[gad]",
                 "variablesReference": 0,
                 "presentationHint": {
                     "attributes": [
                         "rawString"
                     ]
                 }
             },
             {
                 "name": "foo",
                 "value": "'bur'",
                 "type": "str",
                 "evaluateName": "td[foo]",
                 "variablesReference": 0,
                 "presentationHint": {
                     "attributes": [
                         "rawString"
                     ]
                 }
             },
             {
                 "name": "len()",
                 "value": "3",
                 "type": "int",
                 "evaluateName": "len(td)",
                 "variablesReference": 0,
                 "presentationHint": {
                     "attributes": [
                         "readOnly"
                     ]
                 }
             }
         ]
     }
 }

Closing as it's a duplicate.

Closing as it's a duplicate.


ChessGameState not exported

It looks like ChessGameState is not exported and I can't get an example to work

Hello, thanks for posting. You need to also include: https://pub.dev/packages/chess_lib
e.g. in your pubspec:
chess_lib: ^0.1.0+2


Flutter firebase_messenging, not able to redirect specific detail screen when app is  killed in ios Working fine for android

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Messaging
Which platforms are affected?
iOS
Description
Recently faced this issue on our app.
Firebase push notifications works absolutely fine on Android and on ios as well in the background and foreground state. Proper detail screen redirection is doing tapping on push notifications.
But when the app is in the terminated state the notification shows up but the callback handler is not invoked in iOS only. In the Android detail screen redirection works fine even if the app is killed.
Reproducing the issue
Keep your app in killed state, Send push notification to android and ios bith device token, Tapping on android app will open and redirect to proper detail screen, rather then in iOS App open but stay on home screen only do not redirect to exact detail screen based on id from notification payload.
Firebase Core version
3.2.0
Flutter Version
3.22.2
Relevant Log Output
No response
Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments
No response

Hi @bonisha-mandora, it seems this issue has been resolved. Could you let us know which version of firebase_messaging you're currently using?
Here’s a similar issue for reference: https://github.com/firebase/flutterfire/issues/13442

Same here. !

The bug doesn’t necessarily occur when opening the app via a notification. Even when the app is manually launched after receiving a notification, the issue persists (assets fail to load. Exception: Image upload failed due to loss of GPU access).
Additionally, I tested it with an iPad (18.1.1) and various Android devices, and it works without any issues. The problem seems to be limited to iPhone devices only.


[BUG] The File Picker Shows Deleted Files in a Git Repo

Please confirm

[x] I am running the latest version of this plugin

Describe the bug
The file picker shows deleted files from the git history.
To Reproduce
Steps to reproduce the behavior:

Start nvim in a git directory
Begin a find_notes search
Search for a file you have deleted.
The search should return the deleted file name

Expected behavior
Deleted files should not be reported to the user while searching.
Screenshots
If applicable, add screenshots to help explain your problem.
Operating system (please complete the following information):

OS: [e.g. iOS]: Linux

Additional context
Add any other context about the problem here.
I thought this was #251 but I think that issue is actually this one. I have closed that issue for this bug report.

Hmm…
This is my telescope config (using LazyVim):
if isModuleAvailable("telescope-fzf") then
  require("telescope").setup({
    extensions = {
      fzf = {
        fuzzy = true,
        override_generic_sorter = true,
        override_file_sorter = true,
        case_mode = "smart_case",
      },
    },
  })
  require("telescope").load_extension("fzf")
end

The plugin lua file doesn't have anything fancy, other than loading telescope FZF:
return {
	"nvim-telescope/telescope.nvim",
	dependencies = {
		"nvim-telescope/telescope-fzf-native.nvim",
		build = "make",
		config = function()
			require("telescope").load_extension("fzf")
		end,
	},
	keys = {
		--{ "<leader>ff", false },
	},
}

The only other file it could be finding is a file outside of the Vault.
I have a backup copy of the file in another directory but it does not exist there.
For specificity, I have a vault at ~/Documents and in it I have a directory called Notes. In ~/Documents/Notes I have a file called Creeds_Confessions_Catechisms.md.
When I do a find_notes and type Creeds, I get the following output:
Notes/Creeds_Confessions_Catechisms.md
.trash/Creeds_and_Confessions 2.md
.trash/Creeds_and_Confessions.md
Notes/Creeds_and_Confessions.md

The last file Notes/Creeds_and_Confessions.md does not exist, as it was renamed to Notes/Creeds_Confessions_Catechisms.md. It exists only by way of backup in another dir outside of the vault. Opening the link in the find_notes window returns an empty file, whereas the backup file actually has contents.
The reason why I thought it might be pulling it from the .git history was because the search utility said, Git Files, and I figured that was somehow related.
I take it by your response that this is likely unrelated to telekasten at all.

Got it. It was uncommitted changes in the git repo. The picker was finding the existing files and the files from the already committed files because the dir is a git git, and thus it searches with the git_files picker, returning the results of git ls-files.
Solution: commit my changes! Closing.


logs to console directly, would like user-specified option

Feature request:
Currently the code logs to console.error() directly, and it's not easy to override.
Please consider adding an option to log to a user-specified destination.  Leaving the default as console is preferred.

It's recommended to listen to the error event and handle the errors explicitly, otherwise ioredis will logs the error the stderr.

My apologies.  Reading too fast. The behavior you describe is documented here:


Be able to resize the directory tree in the conclusion view

For instance, be able to resize the tree view on the left to make it wider.

Fixed in #21


feat: Maintain originated balance

This PR adds the following changes to accounting:

When credit is done, if the originated argument is true, we deduct the price from the originated balance

When settle (time based part) or debit decreases negative balance, originated balance is reduced towards zero along with the normal balance if the negative balance would become closer to zero.

When notifyPaymentSent decreases negative balance, the value of the settlement is added to the originated balance, even increasing it's value above zero (as the payment was solely intended to move the originated balance).

When sending monetary payments limiting amount to current outstanding originated debt

The PR also includes the use of originated parameter to credit in protocols

This change is

the word originated is enigmatic. can we use a descriptive term?
we concluded with @ralph-pichler this is a descriptive term, as this is the balance representing originated traffic.
however if there is a better suggestion, we can refactor

@metacertain still not really clear to me what originated means in this sense here. there's no linked issue, no description of the term, i agree with viktor that this is just too obscure and not descriptive. can you please explain what it means?

@metacertain still not really clear to me what originated means in this sense here. there's no linked issue, no description of the term, i agree with viktor that this is just too obscure and not descriptive. can you please explain what it means?

updated pr description with explanation of changes

attended all comments as suggested, except

The String() method call on the peer is unnecessary since %s formatting directive will do the same.

this lead to unexplained symptoms in the past, wouldn't try it at the moment

func (a *Accounting) decreaseOriginatedBalanceTo(peer swarm.Address, limit *big.Int) error {
zero := big.NewInt(0)

This is unnecessary since you've already declared the zero value above.

we removed global zero as a risk factor, it could be changed by functions receiving it


graph.removeNode is not a function

I think you need to release the last changes in the repository, in the current code there is a removeNode function on the graph object but the npm version is missing that feature

Problem still exist. Is there a possibility to update?

To fix this problem dirty, you can use
npm install https://github.com/glejeune/node-graphviz/tarball/master --save

to download the current repository via npm.


GitHub Actions secrets not being updated by GitLab environments repo

Ongoing draft MR on GitLab

Secrets an not managed in GitHub anymore.


[fix][doc] Fix links to broker configuration on Admin API Topics page

(If this PR fixes a github issue, please add Fixes #<xyz>.)
Fixes #
(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)
Master Issue: #
Motivation
The links to the broker configuration on the Admin API Topics page do not link to the desired page but to the general configuration page instead.
Modifications
Change links to go directly to broker config page.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[ ] doc-not-needed
(Please explain why)

[x] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

Closing...


feat: added custom scroll bar style

Added Custom Styling on Scrollbar to make it look nice rather than native scrollbar

Appreciate the PR @varun2948 but not sure if we want to deviate from browser native scrollbar styles 😅
For reference, Notion's editor uses browser native scrollbar styles as well:

@steven-tey thanks for the feedback as my system is Linux and the browser is Chrome my scrollbar natively looks like this

that's why I thought of changing the scrollbar from native to something nice looking but I noticed that for all the MAC users it looks similar to what I added  :laughing: so I guess this PR doesn't really do much so I will close this PR for now
Thanks @steven-tey I will look into some other feature to work on and contribute :smile:

Reopening this as I just saw how the scrollbar looks on windows via this comment: https://github.com/steven-tey/novel/pull/62#issuecomment-1614597548
If we can make the scrollbar styles as similar as possible to the Mac native styles (lighter shade of the thumb, transparent background) – then we can merge this and make sure the scrollbar is consistent across devices 😄
Sorry again for closing this prematurely! 🙏

no worries @steven-tey,  i will fix it and raise a PR.

@varun2948 let's continue it from this PR + make sure it works with dark mode too (#38)

@steven-tey does this look fine for you? i have somewhat adjusted the width and the shades
https://github.com/steven-tey/novel/assets/37866666/c2af5796-ba89-45e9-9203-d1c076ac5119

Hmmm this is still not cutting it, I'm sorry 😅
Native Mac scrollbar styles:

Custom scrollbar styles in this PR:

As you can see the positioning of the custom scrollbar is offsetting the div's contents, which is not the case in the Mac native styles

Closing this for now but we can revisit this in the future! Thank you!


Add meltano variants back in as non-default

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/149
Originally created by @pnadolny13 on 2021-10-20 18:38:22

View 1 previous comment from the original issue on GitLab


Some refactoring to allow creating libnegentropy.so shared library

Summary
The library can be created with make:

And it seems it contains the appropriate symbols. e.g.:

Possible future action
Create a simple c-app that links the generated library.

Ah, Thanks a lot @Ivansete-status !
This is what i have also been thinking to do finally if nothing else works.
Odd that shared library cannot be created only with header files. Were you able to find any reasoning as to why that is not allowed?
But i am wondering if it looses some optimizations this way, which is possible with precompiled version. Or maybe not, because the actual negentropy lib is still compiled as header files and done separately.


Add Apex DDP option

Add another option to distributed_backend:
Trainer(distributed_backend='ddp3')

This option would use Apex DDP instead

not needed:
https://github.com/NVIDIA/apex/issues/75


Change write_pos()/read_pos() from &mut to &

Previously, this allowed two threads to have a &mut to the same thing at the same time, which isn't really Rust's thing.
I'm not sure if it's actually UB, because it was only used in a non-mutable fashion, but since it doesn't have to be mutable, why make it mutable?
I wanted to test this with Miri, but sadly this doesn't work because libc::memfd_create() is not supported by Miri.

Right, I'm not used enough to the idea of interior mutability yet. Thanks! (memfd_create can be substituted with a file on /dev/shm, for testing.)

memfd_create can be substituted with a file on /dev/shm, for testing

I don't know if Miri would support that, but I think it is worth trying.
Miri is great for checking unsafe code.


The "must" search operator in blevesearch can't be passed into ponzu

E.g. a query "+fielda:xxx +fieldb:bbb" will be recognized as " fielda:xxx  fieldb:bbb" in ponzu, and got wrong search result.

I fixed it locally with removing "url.QueryUnescape" in this line.
https://github.com/ponzu-cms/ponzu/blob/9bc41b703131aa42ca64265ab6fdeadc37841e66/system/api/search.go#L34


asyncio test rename

When using pycharm's debugger, for some reason our nested asyncio module became
the stdlib asyncio module... which didn't work.

:broken_heart: Tests Failed

Expand to view the summary

Build stats

Build Cause: [Pull request #931 opened]

Start Time: 2020-09-23T15:00:29.616+0000

Duration: 24 min 26 sec

Test stats :test_tube:

Test
Results

Failed
162

Passed
7274

Skipped
7013

Total
14449

Test errors
Expand to view the tests failures

Name: Initializing / Test / Python-python-2.7-1 / tests.contrib.asyncio.aiohttp_web_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-1 / tests.contrib.asyncio.starlette_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-1 / tests.contrib.asyncio.tornado.tornado_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-1 / tests.instrumentation.asyncio_tests.aiohttp_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-1 / tests.instrumentation.asyncio_tests.aiopg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-1 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-1 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-1 / tests.instrumentation.asyncio_tests.base_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-1 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-1 / tests.instrumentation.asyncio_tests.httpx_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-1 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-1 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-1 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.contrib.asyncio.aiohttp_web_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.contrib.asyncio.starlette_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.contrib.asyncio.tornado.tornado_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.instrumentation.asyncio_tests.aiohttp_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.instrumentation.asyncio_tests.aiopg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.instrumentation.asyncio_tests.base_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-3 / tests.instrumentation.asyncio_tests.httpx_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-0 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-0 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-0 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.contrib.asyncio.aiohttp_web_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.contrib.asyncio.starlette_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.contrib.asyncio.tornado.tornado_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.instrumentation.asyncio_tests.aiohttp_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.instrumentation.asyncio_tests.aiopg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.instrumentation.asyncio_tests.base_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-4 / tests.instrumentation.asyncio_tests.httpx_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.contrib.asyncio.aiohttp_web_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.contrib.asyncio.starlette_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.contrib.asyncio.tornado.tornado_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.instrumentation.asyncio_tests.aiohttp_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.instrumentation.asyncio_tests.aiopg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.instrumentation.asyncio_tests.base_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-2 / tests.instrumentation.asyncio_tests.httpx_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-2 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-2 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-2 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-3 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-3 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-3 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-4 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-4 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-3.5-4 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-3.5-none / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-3.5-none / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-3.5-none / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.contrib.asyncio.aiohttp_web_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.contrib.asyncio.starlette_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.contrib.asyncio.tornado.tornado_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.instrumentation.asyncio_tests.aiohttp_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.instrumentation.asyncio_tests.aiopg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.instrumentation.asyncio_tests.base_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-python-2.7-0 / tests.instrumentation.asyncio_tests.httpx_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.contrib.asyncio.aiohttp_web_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.contrib.asyncio.starlette_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.contrib.asyncio.tornado.tornado_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.instrumentation.asyncio_tests.aiohttp_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.instrumentation.asyncio_tests.aiopg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.instrumentation.asyncio_tests.base_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-2 / tests.instrumentation.asyncio_tests.httpx_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-2.7-none / tests.instrumentation.asyncio_tests.aiohttp_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-2.7-none / tests.instrumentation.asyncio_tests.aiopg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-2.7-none / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-2.7-none / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-2.7-none / tests.instrumentation.asyncio_tests.base_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-2.7-none / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / windows-2.7-none / tests.instrumentation.asyncio_tests.httpx_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.contrib.asyncio.aiohttp_web_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.contrib.asyncio.starlette_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.contrib.asyncio.tornado.tornado_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.instrumentation.asyncio_tests.aiohttp_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.instrumentation.asyncio_tests.aiopg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.instrumentation.asyncio_tests.async_elasticsearch_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.instrumentation.asyncio_tests.asyncpg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.instrumentation.asyncio_tests.base_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-3 / tests.instrumentation.asyncio_tests.httpx_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-1 / tests.contrib.asyncio.aiohttp_web_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-1 / tests.contrib.asyncio.starlette_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-1 / tests.contrib.asyncio.tornado.tornado_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-1 / tests.instrumentation.asyncio_tests.aiohttp_client_tests –

Age: 1
Duration: 0
Error Details: collection failure

Name: Initializing / Test / Python-pypy-2-1 / tests.instrumentation.asyncio_tests.aiopg_tests –

Age: 1
Duration: 0
Error Details: collection failure

Steps errors
Expand to view the steps failures

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 none

Duration: 1 min 9 sec

Start Time: 2020-09-23T15:05:45.124+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 none

Duration: 0 min 16 sec

Start Time: 2020-09-23T15:07:14.040+0000

log

Name: Error signal

Description: Python-python-2.7-none tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:07:43.349+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 django-1.11

Duration: 1 min 15 sec

Start Time: 2020-09-23T15:05:45.175+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 django-1.11

Duration: 0 min 22 sec

Start Time: 2020-09-23T15:07:15.995+0000

log

Name: Error signal

Description: Python-python-2.7-django-1.11 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:07:50.771+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 flask-0.12

Duration: 1 min 11 sec

Start Time: 2020-09-23T15:05:46.698+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 flask-0.12

Duration: 0 min 17 sec

Start Time: 2020-09-23T15:07:14.605+0000

log

Name: Error signal

Description: Python-python-2.7-flask-0.12 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:07:45.043+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 flask-1.1

Duration: 1 min 15 sec

Start Time: 2020-09-23T15:05:46.573+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 flask-1.1

Duration: 0 min 19 sec

Start Time: 2020-09-23T15:07:16.994+0000

log

Name: Error signal

Description: Python-python-2.7-flask-1.1 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:07:49.912+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 opentracing-newest

Duration: 3 min 57 sec

Start Time: 2020-09-23T15:05:46.752+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 opentracing-newest

Duration: 0 min 18 sec

Start Time: 2020-09-23T15:08:49.745+0000

log

Name: Error signal

Description: Python-python-2.7-opentracing-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:09:20.631+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 none

Duration: 1 min 7 sec

Start Time: 2020-09-23T15:05:46.804+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 none

Duration: 0 min 17 sec

Start Time: 2020-09-23T15:07:14.133+0000

log

Name: Error signal

Description: Python-python-3.5-none tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:07:44.453+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 django-1.11

Duration: 1 min 14 sec

Start Time: 2020-09-23T15:05:46.856+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 django-1.11

Duration: 0 min 23 sec

Start Time: 2020-09-23T15:07:16.044+0000

log

Name: Error signal

Description: Python-python-3.5-django-1.11 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:07:53.482+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 django-2.0

Duration: 1 min 13 sec

Start Time: 2020-09-23T15:05:47.039+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 django-2.0

Duration: 0 min 23 sec

Start Time: 2020-09-23T15:07:16.127+0000

log

Name: Error signal

Description: Python-python-3.5-django-2.0 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:07:53.926+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 django-2.2

Duration: 1 min 12 sec

Start Time: 2020-09-23T15:05:46.986+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 django-2.2

Duration: 0 min 24 sec

Start Time: 2020-09-23T15:07:16.085+0000

log

Name: Error signal

Description: Python-python-3.5-django-2.2 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:07:54.229+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 flask-0.12

Duration: 1 min 7 sec

Start Time: 2020-09-23T15:05:46.641+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.5 flask-0.12

Duration: 0 min 18 sec

Start Time: 2020-09-23T15:07:14.093+0000

log

Name: Error signal

Description: Python-python-3.5-flask-0.12 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:07:45.718+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.6 httpx-newest

Duration: 0 min 24 sec

Start Time: 2020-09-23T15:11:43.414+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.6 httpx-newest

Duration: 0 min 23 sec

Start Time: 2020-09-23T15:12:13.046+0000

log

Name: Error signal

Description: Python-python-3.6-httpx-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:12:46.098+0000

log

Name: Shell Script

Description: [2020-09-23T15:11:31.336Z] + ./tests/scripts/docker/run_tests.sh python-3.6 elasticsearch-7
[2020-0

Duration: 1 min 41 sec

Start Time: 2020-09-23T15:11:31.038+0000

log

Name: Shell Script

Description: [2020-09-23T15:12:17.607Z] + ./tests/scripts/docker/run_tests.sh python-3.6 elasticsearch-7
[2020-0

Duration: 1 min 38 sec

Start Time: 2020-09-23T15:12:17.304+0000

log

Name: Error signal

Description:

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:13:06.128+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.7 httpx-newest

Duration: 0 min 24 sec

Start Time: 2020-09-23T15:11:50.140+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.7 httpx-newest

Duration: 0 min 23 sec

Start Time: 2020-09-23T15:12:19.448+0000

log

Name: Error signal

Description: Python-python-3.7-httpx-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:12:52.877+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.8 httpx-newest

Duration: 0 min 23 sec

Start Time: 2020-09-23T15:12:28.535+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.8 httpx-newest

Duration: 0 min 23 sec

Start Time: 2020-09-23T15:12:57.106+0000

log

Name: Error signal

Description: Python-python-3.8-httpx-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:13:30.484+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.9-rc httpx-newest

Duration: 0 min 25 sec

Start Time: 2020-09-23T15:12:41.196+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.9-rc httpx-newest

Duration: 0 min 23 sec

Start Time: 2020-09-23T15:13:10.909+0000

log

Name: Error signal

Description: Python-python-3.9-rc-httpx-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:13:44.586+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 none

Duration: 3 min 13 sec

Start Time: 2020-09-23T15:06:15.687+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 none

Duration: 1 min 52 sec

Start Time: 2020-09-23T15:09:40.209+0000

log

Name: Error signal

Description: Python-pypy-2-none tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:10:44.536+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 django-1.11

Duration: 2 min 49 sec

Start Time: 2020-09-23T15:06:12.196+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 django-1.11

Duration: 1 min 0 sec

Start Time: 2020-09-23T15:08:07.674+0000

log

Name: Error signal

Description: Python-pypy-2-django-1.11 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:09:21.009+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 flask-0.12

Duration: 2 min 51 sec

Start Time: 2020-09-23T15:06:17.860+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 flask-0.12

Duration: 1 min 3 sec

Start Time: 2020-09-23T15:08:17.595+0000

log

Name: Error signal

Description: Python-pypy-2-flask-0.12 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:09:38.940+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 flask-1.1

Duration: 3 min 10 sec

Start Time: 2020-09-23T15:06:20.180+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 flask-1.1

Duration: 1 min 53 sec

Start Time: 2020-09-23T15:09:40.878+0000

log

Name: Error signal

Description: Python-pypy-2-flask-1.1 tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:10:46.037+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 opentracing-newest

Duration: 3 min 9 sec

Start Time: 2020-09-23T15:06:31.142+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 opentracing-newest

Duration: 1 min 0 sec

Start Time: 2020-09-23T15:09:50.652+0000

log

Name: Error signal

Description: Python-pypy-2-opentracing-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:11:01.448+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 httpx-newest

Duration: 2 min 38 sec

Start Time: 2020-09-23T15:20:00.037+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 httpx-newest

Duration: 2 min 37 sec

Start Time: 2020-09-23T15:21:42.764+0000

log

Name: Error signal

Description: Python-pypy-3-httpx-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:29.914+0000

log

Name: Shell Script

Description: [2020-09-23T15:17:10.924Z] + ./tests/scripts/docker/run_tests.sh pypy-3 elasticsearch-7
[2020-09-23

Duration: 2 min 13 sec

Start Time: 2020-09-23T15:17:10.562+0000

log

Name: Shell Script

Description: [2020-09-23T15:19:28.866Z] + ./tests/scripts/docker/run_tests.sh pypy-3 elasticsearch-7
[2020-09-23

Duration: 2 min 48 sec

Start Time: 2020-09-23T15:19:28.563+0000

log

Name: Error signal

Description:

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:21:26.419+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-twisted-18

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:37.563+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-celery-3-flask-1.0

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:37.726+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-celery-4-flask-1.0

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:37.892+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-requests-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:38.061+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-boto3-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:38.223+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-pymongo-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:38.378+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-redis-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:38.535+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-psycopg2-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:38.700+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-pymssql-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:38.869+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-pyodbc-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:39.059+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-memcached-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:39.237+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-pylibmc-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:39.396+0000

log

Name: Restore files previously stashed

Description: No such saved stash ‘coverage-python-2.7-elasticsearch-2’

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:39.554+0000

log

Name: Restore files previously stashed

Description: No such saved stash ‘coverage-python-2.7-elasticsearch-6’

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:39.730+0000

log

Name: Restore files previously stashed

Description: No such saved stash ‘coverage-python-2.7-elasticsearch-7’

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:39.901+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-cassandra-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:40.082+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-psutil-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:40.245+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-gevent-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:40.414+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-zerorpc-0.4

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:40.588+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-mysql_connector-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:40.768+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-pymysql-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:40.979+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-mysqlclient-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:41.153+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-pymemcache-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:41.311+0000

log

Name: Restore files previously stashed

Description: coverage-python-2.7-graphene-2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:41.478+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-flask-1.1

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:42.481+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-opentracing-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:42.657+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-twisted-18

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:42.828+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-celery-3-flask-1.0

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:43.029+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-celery-3-django-2.0

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:43.202+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-celery-4-flask-1.0

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:43.375+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-celery-4-django-2.0

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:43.537+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-requests-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:43.699+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-boto3-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:44.193+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-pymongo-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:44.383+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-redis-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:44.541+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-psycopg2-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:44.701+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-pymssql-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:44.873+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-pyodbc-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:45.050+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-memcached-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:45.221+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-pylibmc-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:45.391+0000

log

Name: Restore files previously stashed

Description: No such saved stash ‘coverage-python-3.5-elasticsearch-2’

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:45.561+0000

log

Name: Restore files previously stashed

Description: No such saved stash ‘coverage-python-3.5-elasticsearch-6’

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:45.725+0000

log

Name: Restore files previously stashed

Description: No such saved stash ‘coverage-python-3.5-elasticsearch-7’

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:45.913+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-cassandra-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:46.094+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-psutil-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:46.263+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-gevent-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:46.429+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-mysql_connector-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:46.600+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-pymysql-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:46.766+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-mysqlclient-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:46.937+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-pymemcache-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:47.120+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.5-graphene-2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:47.288+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.6-pymysql-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:23:52.690+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-twisted-18

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:12.895+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-celery-3-flask-1.0

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:13.082+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-celery-4-flask-1.0

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:13.250+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-requests-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:13.421+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-boto3-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:13.590+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-pymongo-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:13.751+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-redis-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:13.934+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-psycopg2-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:14.108+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-memcached-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:14.277+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-pylibmc-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:14.441+0000

log

Name: Restore files previously stashed

Description: No such saved stash ‘coverage-pypy-2-elasticsearch-2’

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:14.607+0000

log

Name: Restore files previously stashed

Description: No such saved stash ‘coverage-pypy-2-elasticsearch-6’

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:14.783+0000

log

Name: Restore files previously stashed

Description: No such saved stash ‘coverage-pypy-2-elasticsearch-7’

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:14.950+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-cassandra-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:15.114+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-zerorpc-0.4

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:15.283+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-mysql_connector-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:15.578+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-pymysql-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:16.068+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-mysqlclient-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:16.232+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-pymemcache-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:16.400+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-2-graphene-2

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:16.584+0000

log

Name: Restore files previously stashed

Description: coverage-pypy-3-pymysql-newest

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:21.496+0000

log

Name: Archive the artifacts

Description: [2020-09-23T15:24:52.951Z] Archiving artifacts
Python-python-2.7-none tests failed : hudson.AbortEx

Duration: 0 min 0 sec

Start Time: 2020-09-23T15:24:52.937+0000

log

Log output
Expand to view the last 100 lines of log output

[2020-09-23T15:24:12.943Z] ERROR: No such saved stash ‘coverage-pypy-2-twisted-18’
[2020-09-23T15:24:13.134Z] ERROR: No such saved stash ‘coverage-pypy-2-celery-3-flask-1.0’
[2020-09-23T15:24:13.305Z] ERROR: No such saved stash ‘coverage-pypy-2-celery-4-flask-1.0’
[2020-09-23T15:24:13.468Z] ERROR: No such saved stash ‘coverage-pypy-2-requests-newest’
[2020-09-23T15:24:13.638Z] ERROR: No such saved stash ‘coverage-pypy-2-boto3-newest’
[2020-09-23T15:24:13.804Z] ERROR: No such saved stash ‘coverage-pypy-2-pymongo-newest’
[2020-09-23T15:24:13.986Z] ERROR: No such saved stash ‘coverage-pypy-2-redis-newest’
[2020-09-23T15:24:14.162Z] ERROR: No such saved stash ‘coverage-pypy-2-psycopg2-newest’
[2020-09-23T15:24:14.328Z] ERROR: No such saved stash ‘coverage-pypy-2-memcached-newest’
[2020-09-23T15:24:14.493Z] ERROR: No such saved stash ‘coverage-pypy-2-pylibmc-newest’
[2020-09-23T15:24:14.658Z] ERROR: No such saved stash ‘coverage-pypy-2-elasticsearch-2’
[2020-09-23T15:24:14.833Z] ERROR: No such saved stash ‘coverage-pypy-2-elasticsearch-6’
[2020-09-23T15:24:14.998Z] ERROR: No such saved stash ‘coverage-pypy-2-elasticsearch-7’
[2020-09-23T15:24:15.169Z] ERROR: No such saved stash ‘coverage-pypy-2-cassandra-newest’
[2020-09-23T15:24:15.454Z] ERROR: No such saved stash ‘coverage-pypy-2-zerorpc-0.4’
[2020-09-23T15:24:15.628Z] ERROR: No such saved stash ‘coverage-pypy-2-mysql_connector-newest’
[2020-09-23T15:24:16.120Z] ERROR: No such saved stash ‘coverage-pypy-2-pymysql-newest’
[2020-09-23T15:24:16.286Z] ERROR: No such saved stash ‘coverage-pypy-2-mysqlclient-newest’
[2020-09-23T15:24:16.448Z] ERROR: No such saved stash ‘coverage-pypy-2-pymemcache-newest’
[2020-09-23T15:24:16.635Z] ERROR: No such saved stash ‘coverage-pypy-2-graphene-2’
[2020-09-23T15:24:21.543Z] ERROR: No such saved stash ‘coverage-pypy-3-pymysql-newest’
[2020-09-23T15:24:23.698Z] + python3 -m coverage combine
[2020-09-23T15:24:50.301Z] + python3 -m coverage xml
[2020-09-23T15:24:51.726Z] [Cobertura] Skipping Cobertura coverage report as build was not SUCCESS or better ...
[2020-09-23T15:24:51.726Z]
[2020-09-23T15:24:52.185Z] + curl -sLO https://code.jquery.com/jquery-3.3.1.slim.min.js
[2020-09-23T15:24:52.676Z] + curl -sLO<EMAIL_ADDRESS>[2020-09-23T15:24:52.951Z] Archiving artifacts
[2020-09-23T15:24:53.182Z] Stage "Building packages" skipped due to earlier failure(s)
[2020-09-23T15:24:53.330Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2020-09-23T15:24:53.487Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2020-09-23T15:24:53.838Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-09-23T15:24:53.887Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-09-23T15:24:54.026Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-09-23T15:24:54.178Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-09-23T15:24:54.606Z] Running on Jenkins in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-931
[2020-09-23T15:24:54.789Z] [INFO] getVaultSecret: Getting secrets
[2020-09-23T15:24:54.940Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-09-23T15:24:55.961Z] + chmod 755 generate-build-data.sh
[2020-09-23T15:24:55.961Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-931/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-931/runs/1 FAILURE 1466069
[2020-09-23T15:24:56.511Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-931/runs/1/steps/?limit=10000 -o steps-info.json


Add option to override logger

When using elho as require, users may want to override ehlo logger with their own.

It's now possible, for example :
ehlo = new Ehlo({
  port: 10025
  , logger = require('winston')
});

The logger api must match winston implementation with methods like info, notice, warning, error.


message.json - url is the only valid property of the Attachment property bundle

In the example, two of the Relationship objects near the end have Attachment property bundles specifying mimeType and sizeInBytes properties.
These properties are not valid on the Attachment property bundle.
The Attachment property bundle only has a single valid property, 'url'.
The mimeType and sizeInBytes properties should be expressed using a ContentData property bundle on the attachment_file1 and attachment_file2 objects.

The mimeType and sizeInBytes in the Attachment property bundle is part of the message artifact. Applications usually like to store information about an attachment in it's database. This information can conflict with the data of the actual file. (rounded up size, non-standard mimeType, etc)
As well, properties of ContentData should only contain information parsed from the data itself, not from a separate database.
I believe the Attachment functionality may need to be reworked.

I agree that we should revisit the way that attachments of messages are conveyed.
For now (v0.1.0) though, the Attachment property bundle has only one valid property, 'url' so the example should not include the other properties.

Sounds good.

53b45e6


[CI] Update CI dependencies

After enabling linkcheck again in #752, it turns out that on the master branch linkcheck continues to fail due to issues with our the symbolic link to the model_zoo. There have been a number of bugfixes for sphinx linkcheck in recent versions. Thus let's update the version first before investigating the current continued failure.
Also, nbconvert 5.5 now supports pandoc 2.

Job PR-756/5 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-756/5/index.html


SCIP crashes on simple problem

I do this (Julia 1.10.2 and SCIP 0.11.6)
using JuMP, GLPK, Cbc, SCIP, Ipopt

println()
println('='^64'')

m = Model(SCIP.Optimizer)
@variable(m,0<=χ₁ <= 10)
@variable(m,χ₂ >= 0, Int)
@variable(m,χ₃ >= 0, Bin)

@objective(m,Max,χ₁+2χ₂+5χ₃)

@constraint(m,cnstr₁,-χ₁+χ₂+3χ₃ <= -5)
@constraint(m,cnstr₂,χ₁+3χ₂-7χ₃ <= 10)

println(m)

println("#",'='^64'')
println("# START OPTIMIZER")
JuMP.optimize!(m)
println('='^64'')

println("Optimal Solutions:")
println("χ₁ = ",JuMP.value(χ₁))
println("χ₂ = ",JuMP.value(χ₂))
println("χ₃ = ",JuMP.value(χ₃))
println()
println("Constraints:")
println("cnstr₁ = ",JuMP.value(cnstr₁))
println("cnstr₂ = ",JuMP.value(cnstr₂))
println()

try
   println("Dual Variables:")
   println("dual₁ = ",JuMP.shadow_price(cnstr₁))
   println("dual₂ = ",JuMP.shadow_price(cnstr₂))
catch e
   println("no dual solution available ...")
end
println()

and get this (with GLPK and Cbc all works well)
julia optimize1.jl

================================================================
Max χ₁ + 2 χ₂ + 5 χ₃
Subject to
 cnstr₁ : -χ₁ + χ₂ + 3 χ₃ <= -5
 cnstr₂ : χ₁ + 3 χ₂ - 7 χ₃ <= 10
 χ₁ >= 0
 χ₂ >= 0
 χ₃ >= 0
 χ₁ <= 10
 χ₂ integer
 χ₃ binary

#================================================================
# START OPTIMIZER

Please submit a bug report with steps to reproduce this fault, and any error messages that follow (in their entirety). Thanks.
Exception: EXCEPTION_ACCESS_VIOLATION at 0xffffffffa2df0000 -- unknown function (ip: ffffffffa2df0000)
in expression starting at D:\Programming\Julia\optimize1.jl:20
unknown function (ip: ffffffffa2df0000)
Allocations: 6432260 (Pool: 6427474; Big: 4786); GC: 9

Please submit a bug report with steps to reproduce this fault, and any error messages that follow (in their entirety). Thanks.
Exception: EXCEPTION_ACCESS_VIOLATION at 0x6db728c -- SCIPprobFree at C:\Users\me\.julia\artifacts\08af979d049d4b61a282acfbe2e12e36329f06c7\bin\libscip.dll (unknown line)
in expression starting at D:\Programming\Julia\optimize1.jl:20
SCIPprobFree at C:\Users\me\.julia\artifacts\08af979d049d4b61a282acfbe2e12e36329f06c7\bin\libscip.dll (unknown line)
SCIPfreeTransform at C:\Users\me\.julia\artifacts\08af979d049d4b61a282acfbe2e12e36329f06c7\bin\libscip.dll (unknown line)
SCIPfreeProb at C:\Users\me\.julia\artifacts\08af979d049d4b61a282acfbe2e12e36329f06c7\bin\libscip.dll (unknown line)
SCIPfree at C:\Users\me\.julia\artifacts\08af979d049d4b61a282acfbe2e12e36329f06c7\bin\libscip.dll (unknown line)
SCIPfree at C:\Users\me\.julia\packages\SCIP\XjNY6\src\LibSCIP.jl:3878
unknown function (ip: 000001f457df42bb)
macro expansion at C:\Users\me\.julia\packages\SCIP\XjNY6\src\wrapper.jl:11 [inlined]
free_scip at C:\Users\me\.julia\packages\SCIP\XjNY6\src\scip_data.jl:70
free_scip at C:\Users\me\.julia\packages\SCIP\XjNY6\src\MOI_wrapper.jl:60
unknown function (ip: 000001f457df957b)
run_finalizer at C:/workdir/src\gc.c:318
jl_gc_run_finalizers_in_list at C:/workdir/src\gc.c:408
run_finalizers at C:/workdir/src\gc.c:454
ijl_atexit_hook at C:/workdir/src\init.c:299
ijl_exit at C:/workdir/src\init.c:207
jl_exception_handler at C:/workdir/src\signals-win.c:337 [inlined]
jl_exception_handler at C:/workdir/src\signals-win.c:229
__julia_personality at C:/workdir/src\win32_ucontext.c:28
_chkstk at C:\Windows\SYSTEM32\ntdll.dll (unknown line)
RtlRaiseException at C:\Windows\SYSTEM32\ntdll.dll (unknown line)
KiUserExceptionDispatcher at C:\Windows\SYSTEM32\ntdll.dll (unknown line)
unknown function (ip: ffffffffa2deffff)
Allocations: 6432260 (Pool: 6427474; Big: 4786); GC: 9

You seem to be on Windows, unfortunately SCIP_jll doesn't work there yet so you will need to install SCIP separately. See https://github.com/scipopt/SCIP.jl/issues/248 for instance.
The second thing is that you are asking for dual solutions to a MIP problem, there will be issues from an algorithmic point of view, MIP solving doesn't provide a "dual proof" in the LP sense

Ok, works. Thank You.


TIP: Use pre-compressed files on Apache – add it to instructions…

How to force Apache to use pre-compressed .gz-files directly.
Hi, I tested your gem and uploaded the files on a webhost with an Apache server I use. I never used the technique before, so I deleted all the .html-files. I got an error. Than I did some digging to enable direct use of the pre-compressed files.
I stumbled once again upon a stackoverflow answer…
For me this suggestion worked perfectly:

Add .htaccess
Add to .htaccess the following code

Options +MultiViews
RemoveType .gz
AddEncoding gzip .gz
<FilesMatch ".+\.tar\.gz$">
    RemoveEncoding .gz
    # Note:  Can use application/x-gzip for backwards-compatibility
    AddType application/gzip .gz
</FilesMatch>

I am no expert on server technology.
Thank you for your work. I probably will use this gem to increase the speed once more :)

Thanks! I followed that Stack Overflow link and came across something that looked simpler. I've added it to the README now.


[fix #941] reading versus listening in catalog

fixes #941

Hello @panaC could you please take a look at the merge conflicts src/common/views/publication.ts and src/main/converter/publication.ts. Then I will test this branch and review the PR. Thanks!

Note this additional fix (the PR functionality was incomplete, covered the grid view but not the list view): https://github.com/readium/readium-desktop/commit/51e5fa17dedd00dccf9dd701bc9d3a08e11fda02


Better explanation

[Enter feedback here]
I feel that this page is pretty confusing and the samples are pretty vague - a more in-depth explanation and scenarios would be welcome. Like the name of the role definition as a guide using resourcegroup().id
This could do with a much better explanation of what is going on here.

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

ID: 72ed13f8-74c2-d93f-224a-0708d2942675
Version Independent ID: 17a781ce-8193-e8fe-e7db-96a02e2de429
Content: Create Azure RBAC resources by using Bicep - Azure Resource Manager
Content Source: articles/azure-resource-manager/bicep/scenarios-rbac.md
Service: azure-resource-manager
Sub-service: bicep
GitHub Login: @johndowns
Microsoft Alias: jodowns

@gsuttie Thanks for your comment. We will review the issue and get back to you shortly.

@gsuttie This page is intended to explain the different components of role assignments and definitions and how you use Bicep to create them. However, there are some complete examples in the 'Related resources' section, under 'Quickstart templates'.
If those don't help you, can you please clarify what you'd like to see, and what points on the page confused you?

Hi John, thanks for your reply.
I think an explanation of what role assignments are, what they can be used for, and more importantly why you might want to consider using them.  The thing that confused me was why is the name of the role assignment a Guid, can I generate a new Guid or what?.
Also the joined up thinking of creating one thing and linking it to another is what I feel is missing.
An example like so:-
Scenario: -
Mary needs to use Managed Identity and add Azure Role Assignments so that the code is using a managed identity and is scoped to a resource level as this is best practice. The following demonstrates how to create a managed identity, assign role assignments to keyvault and storage and how to verify everything is cleaned up once you remove the Managed Identity.
Questions I have from this page are:-
How do I scope a role assignment to say a resource like KeyVault? - some examples of this would be great other than saying scope it to the resource - ( I tried that and am not sure how to do that).
When I delete the Managed Identity to which I added Role Assignments, these become orphaned and therefore I need to delete them before I can successfully re-run in the bicep code again.

@gsuttie, a few responses:

I think an explanation of what role assignments are, what they can be used for, and more importantly why you might want to consider using them.

We want to avoid trying to document all of Azure in the Bicep documentation  - we're trying to specifically show what you need to know to deploy them in Bicep, and there are other docs that explain what role assignments are, such as Steps to assign an Azure role. Having said that, I think we can add a sentence or two to set the scene more and provide a link or two. I'll do that soon.

The thing that confused me was why is the name of the role assignment a Guid, can I generate a new Guid or what?.

I don't know why it's a GUID :) It's unusual, and it makes it harder to manage for sure, but that's the way it's been designed.
We've documented this a bit in the name section, but I'll see if we can reword this to be clearer that you need to provide a unique GUID, and that for the deployment to be repeatable, the GUID generation should be deterministic, which is why we recommend using the guid() function in the tip bubble.

Also the joined up thinking of creating one thing and linking it to another is what I feel is missing.

Again this page isn't designed to show how to write a complete Bicep file - it's designed to explain how a specific category of resources can be deployed by using Bicep, and the things you need to know about RBAC resources specifically. It's designed to be read in conjunction with other docs pages that explain other practices about Bicep code authoring.

How do I scope a role assignment to say a resource like KeyVault? - some examples of this would be great other than saying scope it to the resource - ( I tried that and am not sure how to do that).

I'm sorry, I don't understand the question here. We document the scope in the Scope section. Are you asking for a Key Vault example specifically? I know we spoke about this recently and I still have this on my to do list, but on the Bicep discussions page, someone else was able to provide an initial example. Did this help? We can't provide examples for every scenario on this page (again, that's not the intention) but I think for Key Vault specifically I'll look at adding a link to an example Bicep file.

When I delete the Managed Identity to which I added Role Assignments, these become orphaned and therefore I need to delete them before I can successfully re-run in the bicep code again.

Yes, role assignments and managed identities are distinct resources and so deleting one doesn't affect the lifetime of the other. We can add a note to this effect on the page.

Further to this, we've now made several updates to the page to address the questions @gsuttie raised, including the resource deletion behaviour.
#please-close


WIP: Property listeners

What does the pull request do?

Adds IAvaloniaObject.Listen to implement observables in a way that that doesn't go via PropertyChanged
There are two variants of Listen:

Once which returns an IObservable<AvaloniaPropertyChange<T>>: this is used for listening to changes to a single property
One which takes an IAvaloniaPropertyListener: this is used for listening to all property changes in an object

Both variants of Listen have an includeAnimations flag: setting to false only raises changes for non-animatable values. Fixes #3109
Adds AvaloniaPropertyChange<T> struct as a typed no allocation version of AvaloniaPropertyChangedEventArgs

TODO: More details
Open Questions
We now have quite a few ways of listening for property changes:

AvaloniaProperty.Changed
AvaloniaObject.PropertyChanged
INPC on AvaloniaObject
Listen
GetObservable extension method
GetBindingObservable extension method

This feels like too much. Is there any way we can simplify this?
Checklist

[x] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Breaking changes
TODO
Fixed issues
Fixes #3109

Listen has includeAnimations flag: setting to false only raises changes for non-animatable values. Fixes #3109

Unfortunately, transition handling code needs to subscribe to all of the properties and monitor their changes. Right now it overrides PropertyChanged method: https://github.com/AvaloniaUI/Avalonia/blob/adb587e39f3c435b8cf597750b22cdd326fe3e8d/src/Avalonia.Animation/Animatable.cs#L65

Unfortunately, transition handling code needs to subscribe to all of the properties and monitor their changes. Right now it overrides PropertyChanged method:

Ah yeah, that was something else i wanted to mention: we'll probably need an overload of Listen without a property parameter which listens to all properties. If we add that, we can think about removing the PropertyChanged event too.

@kekekeks added a new variant of Listen which takes an IAvaloniaPropertyListener: this overload is used to listen to changes to all properties on an IAvaloniaObject.

Note that Listen will be called from Animatable constructor.

Ah. Yes that would make more sense if it's going to be enabled from the start. I thought for some reason that you wanted to only subscribe to the changes once a transition had been registered.

We could only call Listen when first transition is registered, but for no transitions scenario virtual method call with a check inside will be almost as much fast as the current check for _allPropertyListeners, but we'll be avoiding allocations and calls through observable infrastructure for objects that have transitions.

On the other hand it will be a generic virtual method call. Those have horrible performance.
@MarchingCube

Since animations are closely tied to the framework having something dedicated would perform better for sure. Although I've never benchmarked differences between normal virtual calls and virtual stub dispatch so I am not sure how slow it could be.

Closing this as I decided to go for a simpler approach for now in https://github.com/AvaloniaUI/Avalonia/pull/3853