Porting To Go

I'm currently working on porting this API into go albeit I made the mistake of not testing it out in rust beforehand. While testing it in rust, I receive an error: "thread 'main' panicked at 'Could not retrieve grades!: Xml(Int(ParseIntError { kind: InvalidDigit }))', src/main.rs:9:10". To sum this up, is this API still functional and did I just mess something up or should I reverse engineer the StudentVue API myself.

Never mind, I've fixed it.


[IDE] Skip synthesized curry thunks and walk their unwrapped expression

SemaAnnotator was walking into an autoclosure and then manually running
passReference on the unwrapped expression without walking it. Since
its synthesized anyway, skip walking the autoclosure entirely and walk
the unwrapped expression instead.
Fix swift::ide::getReferencedDecl not looking through parentheses and
swift::ide::getBase also not unwrapping curry thunks.
Resolves rdar://81312849

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 2d0ad1a77442289d3ef25e6fc9c521b85f20592b

Thanks for the quick review @slavapestov. Turns out the migrator was depending on getReferencedDecl not grabbing the semantic expression. I added a bool param to it (semantic) that's true by default, since it seems to make sense in the other places its used (which is only code completion and isBeingCalled).

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 15c7ddd33fd0bc18a1491770772df04cd306c08e

@swift-ci please test Linux platform

@swift-ci please test Windows platform


don't store the comment in an ^id query (tbh prob stop storing original query altogether)

this threw an error cos the query is too long


[Gauge] Failed to start gauge API: Runner with pid 9528 quit unexpectedly(exit status 1)

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps (or project) to reproduce the behavior:

Initialise a gauge project
Run the gauge command
See error

$ gauge init java
$ gauge run specs

Logs
process C:\Program Files\Java\jre1.8.0_202\bin\java.exe with pid 10344 quit unexpectedly. exit status 1

Expected behavior
A clear and concise description of what you expect to happen.
Screenshots

gauge -v

Gauge version: 1.0.7
Commit Hash: ed7b4fd6
Plugins
html-report (4.0.9)
java (0.7.3)
screenshot (0.0.1)
spectacle (0.1.3)
xml-report (0.2.3)

This version of Gauge and JDK is not supported anymore. Please upgrade to JDK 13+ and Gauge 1.4.3

Thank you for your helping! 👍

hi. My java version 17.0.2 and gauge version 1.4.3,
doesn't work for me


Release scorecard

Release scorecard https://github.com/sigstore/sigstore-java/issues/2#issuecomment-1201899264

@laurentsimon @azeemshaikh38  Planning to release at this SHA 69eb1ccf1d0cf8c5b291044479f18672bf250325.

SGTM.

Thank you!

https://github.com/ossf/scorecard/releases/tag/v4.5.0


[dhcp6pd] add ot-br-posix related code for basic dhcpv6 pd support

This PR includes change for build flags and feature flags.

@jwhui PTAL, thanks.


Refactor to index images

Tests fixed

Codecov Report

Merging #159 (f470fac) into main (42ba8eb) will decrease coverage by 0.15%.
The diff coverage is 55.83%.

@@            Coverage Diff             @@
##             main     #159      +/-   ##
==========================================
- Coverage   79.71%   79.56%   -0.16%
==========================================
  Files         138      137       -1
  Lines        5181     5211      +30
==========================================
+ Hits         4130     4146      +16
- Misses       1051     1065      +14

Impacted Files
Coverage Δ

core/middleware.py
45.94% <ø> (ø)

core/utils/sre_messages.py
37.93% <0.00%> (-1.36%)
:arrow_down:

leavers/tests/views/test_leaver.py
98.92% <ø> (ø)

leavers/tests/views/test_line_manager.py
100.00% <ø> (ø)

leavers/tests/views/test_report_a_leaver.py
46.55% <ø> (ø)

core/people_finder/client.py
46.77% <46.77%> (ø)

core/utils/staff_index.py
44.44% <50.00%> (+1.50%)
:arrow_up:

core/people_finder/interfaces.py
69.44% <56.52%> (+15.95%)
:arrow_up:

core/service_now/client.py
30.37% <66.66%> (+0.50%)
:arrow_up:

config/settings/base.py
95.23% <100.00%> (+0.03%)
:arrow_up:

... and 8 more

Continue to review full report at Codecov.

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


Support chunking with a fixed number of chunks

Something I do relatively often is chunk data into a certain number of chunks, rather than chunks of a certain size. I find this useful in situations where I'm parallelizing work that depends on a bottleneck (eg, database, vcs server), and I want to ensure I don't overload it if a massive amount of work comes in. I have an implementation of this in https://github.com/bhearsum/chunkify, but it seems like it might fit well into chunked.
It would require an API break, with an interface such as:
def chunked(data, chunk_size=None, total_chunks=None)
...where one (and only one) of chunk_size or total_chunks is required. chunkify also supports only returning a specific chunk, which is a bit more efficient for large lists, but not crucial.

Thanks for the suggestion. I'm thinking wontfix for this, however. We have grouper, which is pretty darned close, yeah?

Reviving this issue - I was wrong! grouper() and chunked() are almost identical (save for padding); I was thrown by the example for grouper().
I'm thinking of a function that will evenly distribute items from an iterable into multiple sub-iterables. Something like:
>>> group_1, group_2 = distribute(2, [1, 2, 3, 4, 5, 6])
>>> list(group_1)
[1, 3, 5]
>>> list(group_2)
[2, 4, 6]

When there are 2 groups, the 0th item goes in the 0th group; the 1st item goes in the 1st group; the 2nd item goes in the 0th group; the 3rd item goes in the 1st group... The downside is that the sub-iterables don't have the same order as the parent, but this way we don't need to know the length of the parent.
I'll make a PR for this; apologies for the mistaken dismissal!


fix: Design issues

This PR fixes padding between base layer options in maps + adds padding to other options sections in the right panel, as they went missing after recent changes. Also, it fixes sizing issues with table chart sorting options.

The first commit could be splitted between I think the fix on the map options spacing and the other change and introduction of a new property "gap" on the ControlSectionContent. It's not clear to me why this was introduced, I can only understand that some ControlSectionContent need a gap between their children, sometimes they do not.
The last commit could be splitted between the refactor and the fix. It's hard to review here.
I think in general that commit description can be a bit improved.
Thanks for the refactors though. As this is only styling I LGTM now :)

Thanks for a reminder, I have a tendency to mix stuff in the commits :) I hope it's better now!


[Perf] Add option to show throughput per parallel workstream

Add an option to show the detailed perf data for each parallel workstream.  Something like this:
ID   Operations    Last Completed   Ops/Sec
 0           90              10.0      9.00
 1           85               9.9      8.56
TOTAL                                 17.56

Hi @mikeharder, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.


Protect dressing room entry with login

https://flask-login.readthedocs.io/en/latest/#login-example

Added in https://github.com/danielschenk/zpf-backstage-tv/commit/44c83e1514eb9dcde473b3148811a523f3557427


MSA and tree don't align

Andrew, Below are the ids I used in the id mapping and then got the sequences and then ran MSA from there. As we saw, there are few blank nodes in the tree, which messes us tree and MSA alignment.
fig|176299.10.peg.3564
fig|749927.5.peg.8635
fig|198094.11.peg.4457
fig|260799.14.peg.4455
fig|226900.8.peg.4406
fig|224308.43.peg.2596
fig|281309.8.peg.4272
fig|226186.12.peg.4330
fig|702459.3.peg.1640
fig|206672.9.peg.1610
fig|257313.5.peg.3309
fig|224911.5.peg.1587
fig|272560.6.peg.280
fig|192222.6.peg.1190
fig|190650.5.peg.3250
fig|471472.4.peg.18
fig|272561.5.peg.713
fig|115713.3.peg.840
fig|324602.8.peg.2798
fig|272562.8.peg.1298
fig|441771.6.peg.2400
fig|272563.8.peg.3621
fig|196627.14.peg.865
fig|227377.7.peg.67
fig|243230.17.peg.2026
fig|882.5.peg.346
fig|716541.4.peg.4387
fig|226185.9.peg.2601
fig|585057.6.peg.3450
fig|1133852.3.peg.1029
fig|386585.9.peg.3947
fig|685038.3.peg.2918
fig|585056.7.peg.3430
fig|511145.12.peg.3006
fig|402612.5.peg.229
fig|177416.18.peg.1413
fig|190304.8.peg.1465
fig|243231.5.peg.1131
fig|71421.8.peg.899
fig|85962.8.peg.795
fig|1125630.4.peg.4310
fig|272621.13.peg.1429
fig|220668.9.peg.1322
fig|362948.14.peg.627
fig|272623.7.peg.188
fig|189518.3.peg.1248
fig|169963.11.peg.1373
fig|265311.5.peg.250
fig|233413.5.peg.1109
fig|272631.5.peg.287
fig|246196.19.peg.5331
fig|83332.12.peg.1106
fig|272632.4.peg.543
fig|272634.6.peg.375
fig|242231.10.peg.2386
fig|122586.8.peg.2681
fig|167539.5.peg.1201
fig|208964.12.peg.5478
fig|272943.9.peg.787
fig|243090.15.peg.2597
fig|269796.9.peg.1142
fig|272947.5.peg.473
fig|220341.7.peg.3278
fig|99287.12.peg.3243
fig|211586.12.peg.744
fig|300267.13.peg.3788
fig|198214.7.peg.3446
fig|93061.5.peg.1501
fig|171101.6.peg.2054
fig|568814.3.peg.1935
fig|100226.15.peg.3243
fig|300852.9.peg.1581
fig|243277.26.peg.2362
fig|312309.11.peg.2146
fig|190485.4.peg.3486
fig|393305.7.peg.3611
fig|214092.21.peg.1187

Characters [();,] in the organism name were causing trouble for the newick string parsing, causing the missing labels/sequences and causing the alignment to be off. Fix pushed. Check alpha or beta.


missing codecs in 2.1.0

pip install dnstap-receiver==2.1.0 results in
Traceback (most recent call last):
File "~/.virtualenvs/dnstap/bin/dnstap_receiver", line 5, in
from dnstap_receiver.receiver import start_receiver
File "~/.virtualenvs/dnstap/lib/python3.7/site-packages/dnstap_receiver/init.py", line 3, in
from dnstap_receiver.receiver import start_receiver
File "~/.virtualenvs/dnstap/lib/python3.7/site-packages/dnstap_receiver/receiver.py", line 23, in     from dnstap_receiver.codec import dnstap_pb2
ModuleNotFoundError: No module named 'dnstap_receiver.codec'
It works with ==2.0.2

Thanks for reporting this! regression fixed in 2.1.1


incoming/odfi: don't emit IncomingFile events for empty ACH files

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.40 :tada:

Comparison is base (520d0a6) 41.63% compared to head (83310f0) 42.03%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #177      +/-   ##
==========================================
+ Coverage   41.63%   42.03%   +0.40%
==========================================
  Files          90       90
  Lines        4028     4032       +4
==========================================
+ Hits         1677     1695      +18
+ Misses       2044     2025      -19
- Partials      307      312       +5

Impacted Files
Coverage Δ

internal/incoming/odfi/incoming.go
58.97% <100.00%> (+41.83%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


OCPBUGS-36768: cherry-pick upstream remote-write fix

The fix was merged into the remote v2.53 branch https://github.com/prometheus/prometheus/pull/14446 but hasn't been merged into main yet https://github.com/prometheus/prometheus/pull/14455
/hold
Needs backport into 4.16

/jira refresh

/hold cancel

/cherrypick release-4.16

@marioferh: changing LGTM is restricted to collaborators

Want to add yourself to the OWNERS file?

The fix to main was merged 2h ago. For the master branch we could wait for syncbot to put up 2.53.1. We'd still need the 4.16 backport though. @machine424 any preference?

Yes, I canceled the hold.
Just, wanted to avoid the jira "you should have a 4.17 OCPBUGS first..." burden, it looked simpler for me like that, but maybe I'm missing sth.
And also to show that humans can still beat machines (even though my handle doesn't help with that)

@marioferh: changing LGTM is restricted to collaborators

Want to add yourself to the OWNERS file?

https://github.com/openshift/prometheus/blob/master/OWNERS ?

/lgtm


added install openssl-devel to amazonlinux2 Dockerfile

Swift build for AWS Lambda failing
When using the command "swift package --disable-sandbox plugin archive" to build a Swift Lambda function that has aws-sdk-swift as a dependency, the build of it will fail because of a missing package in the image it uses. This is why I added openssl-devel in the install section.
Reproducing the Bug

Initialize a Swift project for AWS Lambda

swift package init --type executable

edit overall project to conform to a Lambda function

for example
// Import the packages required by our function
import AWSLambdaRuntime

// Define the request structure
struct Request: Codable {
    let rawPath: String
}

// Define the response structure
struct Response: Codable {
    let body: String
}

// Entry point for the Lambda function
@main
struct HelloWorld: SimpleLambdaHandler {

    // Lambda Function handler
    func handle(_ event: Request, context: LambdaContext) async throws -> Response {

        return Response(body: "Hello, world!")
    }
}

make sure to put this into Sources/HelloWorld/LambdaHandler.swift

add aws-sdk-swift as a package and as a product dependency

// swift-tools-version: 5.9.0
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "aws-swift-app",
    platforms: [.macOS(.v12)],
    products: [
        .executable(name: "HelloWorld", targets: ["HelloWorld"])
    ],
    dependencies: [
        .package(url: "https://github.com/swift-server/swift-aws-lambda-runtime", branch: "main"),
        .package(url: "https://github.com/awslabs/aws-sdk-swift", from: "0.37.0")
    ],
    targets: [
        .executableTarget(
            name: "HelloWorld",
            dependencies: [
                .product(name: "AWSLambdaRuntime",package: "swift-aws-lambda-runtime"),
                .product(name: "AWSDynamoDB",package: "aws-sdk-swift"),
            ]
        )
    ]
)

run the command

swift package --disable-sandbox plugin archive

The Error
The project would start compiling until it prints this:

Which basically says that it is missing some files
The Fix
Adding openssl-devel to the installed packages in the amazonlinux2 image which is the image that swift package uses.

Looks good to me @MarwaneKoutar, thanks.
@shahmishal can you have a look and merge if OK ?  Do you think we need to update the SLIM version as well ? (I don't think so, as the objectives of the SLIM version is to be as small as possible)

@shahmishal
I understand your concern to not open the door to vendor requests and to keep the image as small as possible. However, I would like you to consider these three points:
1/ this is Amazon Linux and AWS SDK for Swift. This image is used by AWS customers using Swift, the vast majority will need to install the AWS SDK on it. I'm not asking to add this package on all Linux images, just the Amazon one.
2/ The slim images exist and they are minimal, a customer that wants the smallest possible image will use the slim version
3/ both Apple and Amazon are focus on customer experience. Given the fact that this is an Amazon Linux image, to be deployed on AWS, we want to give the best possible DX to our common customers.
Let me know what the team decision is. Thanks

@sebsto Thanks for the explanation! This does make sense because Amazon Linux 2 docker images are mostly used on AWS platforms.

@swift-ci test

Please also update the 5.10 Dockerfile. Thanks!

Hey @shahmishal, I've just updated it. Thank you!

@swift-ci test

@swift-ci test

@swift-ci test

@shahmishal could you please have a look at that?

This looks good, I just noticed we would also want this updated on the nightly Dockerfiles too.

@shahmishal would you like to also have this update on the buildx Dockerfiles? I've added it on the nightly-main too, is that good?

Yes buildx too, thanks!

@swift-ci test

@MarwaneKoutar Please let me know once you have buildx updated. Thanks

@shahmishal Sorry I've missed your last message. I just updated the buildx ones.

@swift-ci test

@shahmishal Hello Mishal,
I noticed the builds at Docker Hub are based on a 4 months commit.
Do you know when this pull request will land into Docker hub ? We're block on another project with this dependency
Thank you !

I just test the image swift:5.10-amazonlinux2 today
https://hub.docker.com/layers/library/swift/5.10-amazonlinux2/images/sha256-12e5f88e33b3c997ad16502fea3c1287c4a00757d63a04fc669e3cac3a9795ce?context=explore
and I confirm this change landed well.
Thank you !
@MarwaneKoutar Time to update the build script of the SAM tLambda templates at
https://github.com/swift-server-community/aws-lambda-swift-sam-template


api: remove empty response parameters

Description
Remove response parameters missing a description, and which are not used, creating an empty entry in listApis call (see the empty {} below):
      "related": "listZones,createZone",
      "response": [
        {
          "description": "the allocation state of the cluster",
          "name": "allocationstate",
          "type": "string"
        },
        {},
        {
          "description": "the first DNS for the Zone",
          "name": "dns1",
          "type": "string"
},

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[x] Cleanup (Code refactoring and cleanup, that may add test cases)

GitHub Issue/PRs

How Has This Been Tested?
Checklist:

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Testing

[ ] I have added tests to cover my changes.
[ ] All relevant new and existing integration tests have passed.
 I'll keep you posted as I make progress.

Hi @marcaurele, thanks for this fix. Can you please share some examples how you've tested it?

@borisstoyanov I simply did a local compilation but I pushed before checking it went fine. I missed a line removal. I just force pushed an amend.
To test: you can check the actual empty parameters with the cs python lib:
cs listApis | grep "{}" and you should get 2 of them (based on the fork we're using).

Thanks @marcaurele, let me try that and will run smoketests as well

looks good, Marc-aurele but are we sure they are really never filled in a response?

@DaanHoogland yes, otherwise the code won't compile.

not if reflection is somehow used. not to blame you but I am a bit wary with these kind of left-overs. Actually in this case I think you are right.

Packaging result: ✖centos6 ✖centos7 ✔debian. JID-2186

@blueorangutan package

@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian.


Clarify language in project description.

I think you meant "instead of" instead of "instance of" in the phrase "to perform queries on .git files instead of database files".  (Is that right?  Please correct me if I'm wrong; but the way it read before does not make sense and is confusing.)
Move the note about case-insensitivity of queries out of the main description into the "samples" section, because it seems to make more sense there.

Hi, I hope this is alright.  This looks like a really cool project.  I was just confused by the language in the description, so I made an attempt at clarifying it a little bit, especially that use of "instance of" vs. "instead of".  Thank you very much.

Hello @dubaaron,
Looks great, i think soon we can move the note about case-insensitivity to the docs website
Thank you


Change Windows paths and exec methods to allow mounting, ssh and terminal.

Fantastic! This is great. Thanks for the PR. Looking now.
In the meantime, can you sign your commits?

Hi !
I squashed and amended the commits with the signature. Should be good now !

Great! Thanks @kraynel. Merging

Can't auto merge, can you merge in the windows branch? Looking great otherwise!


Minify and uglify into just a single index.min.js file

Push dist, docs, templates folders to npm instead of the whole repo


[v0.5] Old guide linked in Setup.py

During setup the old github gist link is used instead of the new Wiki system

Fixed in Version 0.5.1+


Add chat shortcut to quick picks

Description
Added chat shortcuts to quick actions menu.
Checklist

[ x] The base branch of this PR is dev, rather than main
[ ] The relevant docs, if any, have been updated or created (N/A)

Screenshots

Testing

Click "continue" button in the lower right corner
Click either "Open chat" or "Open full screen chat"

Congrats on PR number one Tomasz! 🚢🚢🚢🚢🚢


compact: clarify retention wording

Changes
As discussed on Slack, the default 0d means unlimited.
Verification
n/a
Are the docs autogenerated or should I update them? https://github.com/improbable-eng/thanos/blob/master/docs/components/compact.md

Hi @tonglil ! Any update on this PR ? Do you need anything ?
Cheers :wave:

Thanks for the reminder, this slipped through.


Rename Invoke to InvokeAsync on the .NET client

The extension methods on HubConnection are Invoke but the method on HubConnection is InvokeAsync.

Resolved: 2597e52e53923a1b937918ca374e355692c1a8cf


movewindow leaves artifacts of the moved window ontop of other windows

Describe the bug
when movewindow is triggered and the moved window moves over other windows artifacts of the moved window remain drawn over the windows that weren't moved
Images/videos/anything that would help
Please attach a log (it's in /tmp/hypr/hyprland.log) and, if crashing, a crashdump (coredumpctl, then coredumpctl info )
** possible solution **
force a redraw on all windows after the animation ends

cant reproduce

I was able to replicate but this time the artifacts are around the edges near the bottom of the screen, where the wallpaper show
https://user-images.githubusercontent.com/1387859/169592454-6aa68c4f-a27d-4add-a488-708af90e0794.mp4
s

ah, its firefox again. right. It's that issue.

@vaxerski when I have terminal windows with an opacity of .75 and I replicate the movement shown in the video the artifacts now happen on the transparent window and not just at the bottom part of the screen
https://user-images.githubusercontent.com/1387859/169679487-515f8a5f-ae9a-4dd9-97a6-23cfc17607a6.mp4

well, yeah. It's an issur with firefox, as I've said.

i have the same issue with alacritty, foot and pretty much everything i tried when closing the last window of a workspace,

video please?

I'm also using alacritty, may be the same issue.

should be fixed in f461ea3105fbe7979a44d702bd9b2f7ee46a9441


File name inconsistent

Description
The PR is going to fix the segmentation part of the issues mentioned in tickets - Bug Submission: segmentation viewer returning an error e.g. dataset 125 and Bug Submission: segmentation viewer and plot viewer preview not available e.g. dataset 119 and 125. Inconsistent file names are stored between scicrunch and neurolucida, scicrunch and s3.
Type of change
Delete those that don't apply.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Run the portal locally to check whether the thumbnail is showing.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added unit tests that prove my fix is effective or that my feature works

An if statement is accidentally removed from my script. I have updated and double-checked the file names. They should all match now.


Bayesian Linear Regression

Please review this PR @ashwani-rathee
It solves issue  #29
I have taken reference from the following links:
https://github.com/WillKoehrsen/Data-Analysis/blob/master/bayesian_lr/Bayesian Linear Regression Project.ipynb
https://github.com/zjost/bayesian-linear-regression/blob/master/src/bayes-regression.ipynb

@goelesha we don't accept .ipynb implmentation,please submit a .py class type implmentation

@ashwani-rathee I have deleted the jupyter notebook and added a python file instead of that. Kindly review and merge this PR.

@ashwani-rathee Pls merge this PR


Fix Marshall Islands failed test

Just a few hours since we've just discussed the stability of a county set... And here comes a new country -- Marshall Islands!
https://travis-ci.com/github/oscovida/oscovida/jobs/417052177

No longer reproducible, probably the two datasets were synchronized by their maintainers.
And according to Wikipedia, the Marshall Islands have more inhabitants than Liechtenstein or San-Marino.


updating senders.md terminology and to make it more task based

Description of the change: Updating to make it more task based and updating from "Sender identities" to "Senders" (except where it still says "Sender Identities" in the UI)
Reason for the change: The terminology has changed and docs initiative to make it more task based
Link to original source: https://sendgrid.com/docs/User_Guide/Marketing_Campaigns/senders.html
@Whatthefoxsays please pull this one in locally and verify the formatting as well as doing a copy edit

thanks @Whatthefoxsays!!!


Support nested prefixes in the LcTrie class

Description:
Support nested prefixes such as <IP_ADDRESS>/24 and <IP_ADDRESS>/32 in the LcTrie class. An address comparison against an LcTrie will now return the union of all matching prefixes' tags.
Risk Level: Low
Testing: Updated unit tests included
Docs Changes: N/A
Release Notes: N/A
Partially Fixes: #1001
Notes: This PR includes the changes from @ccaraman's PR #2612.
Signed-off-by: Brian Pane<EMAIL_ADDRESS>

Please merge master to pick up https://github.com/envoyproxy/envoy/pull/2613, this should fix CI TSAN.

I think this will be much easier to review if it doesn't contain the changes from #2612 . Can you make a pass over that PR to review it, and we'll get it merged? @ccaraman can separately review your changes here.

@alyssawilk for senior maintainer review

Actually I can go ahead and do that.  Mergable!  :-)


docs: update CONTRIBUTING.md to reflect default PR branch

Thanks for this.
Kindly note to change the CONTRIBUTION.MD file you need to update the template file here: https://github.com/angular/angular-cli/blob/master/scripts/templates/contributing.ejs
Afterwards you need to run
yarn admin templates


release.date is missing sometimes

http://standard.open-contracting.org/review/data/5d75c519-cd09-4dd8-bde5-205f1acba708
The dataPublicationDonnees field is probably missing from the source data.

For instance in release<PHONE_NUMBER>00142018Q-ktUsrEPm-00.


Unexpected token '<', "<!DOCTYPE "... is not valid JSON

Is it something wrong with the Playground?
I'm trying to run
fn main() {
    println!("Success!");
}

But see only error:
Unexpected token '<', "<!DOCTYPE "... is not valid JSON

Interesting… I was tried to use the Playground now again, after one hour, and it works without any errors.


Kakfa integration appears broken in 6.3.3

Note that your link for the getting the info page is broken: https://help.datadoghq.com/hc/en-us/articles/203764635-Agent-Status-and-Information
Output of the info page (if this is a bug)
Getting the status from the agent.

==============
Agent (v6.3.3)
==============

  Status date: 2018-07-25 16:49:16.273987 UTC
  Pid: 8530
  Python Version: 2.7.14
  Logs: /var/log/datadog/agent.log
  Check Runners: 3
  Log Level: info

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    NTP offset: -0.000396109 s
    System UTC time: 2018-07-25 16:49:16.273987 UTC

  Host Info
  =========
    bootTime: 2018-07-23 21:11:58.000000 UTC
    kernelVersion: 4.14.47-56.37.amzn1.x86_64
    os: linux
    platform: amazon
    platformFamily: rhel
    platformVersion: 2018.03
    procs: 150
    uptime: 156777
    virtualizationRole: guest
    virtualizationSystem: xen

  Hostnames
  =========
    ec2-hostname: ip-10-50-26-44.ec2.internal
    hostname: kafka-test-4.prod.internal.cio
    instance-id: i-05af9024c16172131
    socket-fqdn: ip-10-50-26-44.ec2.internal.
    socket-hostname: ip-10-50-26-44

=========
Collector
=========

  Running Checks
  ==============
    cpu
    ---
      Total Runs: 17
      Metric Samples: 6, Total: 96
      Events: 0, Total: 0
      Service Checks: 0, Total: 0
      Average Execution Time : 0ms

    disk
    ----
      Total Runs: 17
      Metric Samples: 36, Total: 612
      Events: 0, Total: 0
      Service Checks: 0, Total: 0
      Average Execution Time : 17ms

    file_handle
    -----------
      Total Runs: 17
      Metric Samples: 1, Total: 17
      Events: 0, Total: 0
      Service Checks: 0, Total: 0
      Average Execution Time : 0ms

    io
    --
      Total Runs: 17
      Metric Samples: 39, Total: 636
      Events: 0, Total: 0
      Service Checks: 0, Total: 0
      Average Execution Time : 2ms

    kafka_consumer
    --------------
      Total Runs: 17
      Metric Samples: 0, Total: 0
      Events: 0, Total: 0
      Service Checks: 0, Total: 0
      Average Execution Time : 38ms

    load
    ----
      Total Runs: 17
      Metric Samples: 6, Total: 102
      Events: 0, Total: 0
      Service Checks: 0, Total: 0
      Average Execution Time : 0ms

    memory
    ------
      Total Runs: 17
      Metric Samples: 17, Total: 289
      Events: 0, Total: 0
      Service Checks: 0, Total: 0
      Average Execution Time : 0ms

    network
    -------
      Total Runs: 17
      Metric Samples: 20, Total: 340
      Events: 0, Total: 0
      Service Checks: 0, Total: 0
      Average Execution Time : 0ms

    ntp
    ---
      Total Runs: 17
      Metric Samples: 1, Total: 17
      Events: 0, Total: 0
      Service Checks: 1, Total: 17
      Average Execution Time : 31ms

    uptime
    ------
      Total Runs: 17
      Metric Samples: 1, Total: 17
      Events: 0, Total: 0
      Service Checks: 0, Total: 0
      Average Execution Time : 0ms

========
JMXFetch
========

  Initialized checks
  ==================
    jmx
      instance_name : jmx-localhost-9999
      message :
      metric_count : 13
      service_check_count : 0
      status : OK
    kafka
      instance_name : kafka-localhost-9999
      message :
      metric_count : 45
      service_check_count : 0
      status : OK
  Failed checks
  =============
    no checks

=========
Forwarder
=========

  CheckRunsV1: 17
  DroppedOnInput: 0
  IntakeV1: 2
  RetryQueueSize: 0
  Success: 36
  TimeseriesV1: 17

  API Keys status
  ===============
    https://6-3-3-app.agent.datadoghq.com,*************************19462: API Key valid

==========
Logs Agent
==========

  Logs Agent is not running

=========
DogStatsD
=========

  Checks Metric Sample: 2465
  Event: 1
  Events Flushed: 1
  Number Of Flushes: 17
  Series Flushed: 1980
  Service Check: 187
  Service Checks Flushed: 193

Describe what happened:
I've been struggling at getting the kafka integration working.  I'm currently using the default config with no modifications.  (I copied datadog-agent/conf.d/kafka.d/conf.yaml.example to datadog-agent/conf.d/kafka.d/conf.yaml)
When I try to run just the kafka check with debug logging enabled, I get this:
>sudo datadog-agent check kafka -l debug
2018-07-25 16:52:34 UTC | INFO | (tagger.go:79 in Init) | starting the tagging system
2018-07-25 16:52:35 UTC | DEBUG | (tagger.go:149 in tryCollectors) | ecs_fargate tag collector cannot start: Failed to connect to task metadata API, ECS tagging will not work
2018-07-25 16:52:35 UTC | DEBUG | (ecs.go:79 in GetUtil) | ECS init error: temporary failure in ecsutil, will retry later: could not detect ECS agent, tried URLs: [http://localhost:51678/]
2018-07-25 16:52:35 UTC | DEBUG | (tagger.go:145 in tryCollectors) | will retry ecs later: temporary failure in ecsutil, will retry later: could not detect ECS agent, tried URLs: [http://localhost:51678/]
2018-07-25 16:52:35 UTC | DEBUG | (global.go:49 in GetDockerUtil) | Docker init error: temporary failure in dockerutil, will retry later: could not determine docker server API version: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
2018-07-25 16:52:35 UTC | DEBUG | (kubelet.go:88 in GetKubeUtil) | Init error: temporary failure in kubeutil, will retry later: unable to get hostname from docker, please set the kubernetes_kubelet_host option: temporary failure in dockerutil, will retry later: could not determine docker server API version: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
2018-07-25 16:52:35 UTC | DEBUG | (tagger.go:145 in tryCollectors) | will retry kubelet later: temporary failure in kubeutil, will retry later: unable to get hostname from docker, please set the kubernetes_kubelet_host option: temporary failure in dockerutil, will retry later: could not determine docker server API version: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
2018-07-25 16:52:35 UTC | DEBUG | (kubelet.go:88 in GetKubeUtil) | Init error: temporary failure in kubeutil, will retry later: try delay not elapsed yet
2018-07-25 16:52:35 UTC | DEBUG | (tagger.go:145 in tryCollectors) | will retry kube-metadata-collector later: temporary failure in kubeutil, will retry later: try delay not elapsed yet
2018-07-25 16:52:35 UTC | DEBUG | (global.go:49 in GetDockerUtil) | Docker init error: temporary failure in dockerutil, will retry later: try delay not elapsed yet
2018-07-25 16:52:35 UTC | DEBUG | (tagger.go:145 in tryCollectors) | will retry docker later: temporary failure in dockerutil, will retry later: try delay not elapsed yet
2018-07-25 16:52:35 UTC | INFO | (runner.go:92 in NewRunner) | Runner started with 1 workers.
2018-07-25 16:52:35 UTC | DEBUG | (scheduler.go:125 in func1) | Starting scheduler loop...
2018-07-25 16:52:35 UTC | DEBUG | (runner.go:226 in work) | Ready to process checks...
2018-07-25 16:52:35 UTC | INFO | (collector.go:52 in NewCollector) | Embedding Python 2.7.14 (default, Jul 16 2018, 19:01:07) [GCC 4.4.7 20120313 (Red Hat 4.4.7-18)]
2018-07-25 16:52:35 UTC | DEBUG | (collector.go:53 in NewCollector) | Python Home: /opt/datadog-agent/embedded
2018-07-25 16:52:35 UTC | DEBUG | (collector.go:54 in NewCollector) | Python path: ['/opt/datadog-agent/embedded/lib/python27.zip', '/opt/datadog-agent/embedded/lib/python2.7', '/opt/datadog-agent/embedded/lib/python2.7/plat-linux2', '/opt/datadog-agent/embedded/lib/python2.7/lib-tk', '/opt/datadog-agent/embedded/lib/python2.7/lib-old', '/opt/datadog-agent/embedded/lib/python2.7/lib-dynload', '/opt/datadog-agent/embedded/lib/python2.7/site-packages', '/opt/datadog-agent/embedded/lib/python2.7/site-packages/setuptools-28.8.0.post20180716-py2.7.egg', '/opt/datadog-agent/bin/agent/dist', '/opt/datadog-agent/checks.d', '/opt/datadog-agent/bin/agent/dist/checks.d', '/etc/datadog-agent/checks.d']
2018-07-25 16:52:35 UTC | DEBUG | (collector.go:63 in NewCollector) | Collector up and running!
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:41 in SetupAutoConfig) | Added Python Check Loader to AutoConfig
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:41 in SetupAutoConfig) | Added Core Check Loader to AutoConfig
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:41 in SetupAutoConfig) | Added JMX Check Loader to AutoConfig
2018-07-25 16:52:35 UTC | INFO | (file.go:69 in Collect) | File Configuration Provider: searching for configuration files at: /etc/datadog-agent/conf.d
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/activemq.d/metrics.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/apache.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/cassandra.d/metrics.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/consul.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/couch.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/couchbase.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/cpu.d/conf.yaml.default
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/disk.d/conf.yaml.default
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/elastic.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/etcd.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/file_handle.d/conf.yaml.default
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/io.d/conf.yaml.default
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/jmx.d/conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kafka.d/conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kafka.d/metrics.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kafka_consumer.d/conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kube_dns.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kube_proxy.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kubernetes_state.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/kyototycoon.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/load.d/conf.yaml.default
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/mcache.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/memory.d/conf.yaml.default
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/network.d/conf.yaml.default
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/ntp.d/conf.yaml.default
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/redisdb.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/riak.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/solr.d/metrics.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/tomcat.d/auto_conf.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/tomcat.d/metrics.yaml
2018-07-25 16:52:35 UTC | DEBUG | (file.go:191 in collectEntry) | Found valid configuration in file: /etc/datadog-agent/conf.d/uptime.d/conf.yaml.default
2018-07-25 16:52:35 UTC | INFO | (file.go:69 in Collect) | File Configuration Provider: searching for configuration files at: /opt/datadog-agent/bin/agent/dist/conf.d
2018-07-25 16:52:35 UTC | WARN | (file.go:73 in Collect) | Skipping, open /opt/datadog-agent/bin/agent/dist/conf.d: no such file or directory
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: httpd
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for apache at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: consul
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for consul at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: couchdb
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for couch at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: couchbase
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for couchbase at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: elasticsearch
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for elastic at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: etcd
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for etcd at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: kubedns-amd64
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: k8s-dns-kube-dns-amd64
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for kube_dns at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: kube-proxy
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for kube_proxy at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: kube-state-metrics
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for kubernetes_state at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: kyototycoon
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for kyototycoon at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: memcached
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for mcache at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: redis
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for redisdb at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: riak
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for riak at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (configresolver.go:124 in ResolveTemplate) | No service found with this AD identifier: tomcat
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:317 in resolve) | Can't resolve the template for tomcat at this moment.
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (secrets.go:122 in Decrypt) | No data to decrypt or no secretBackendCommand set: skipping
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - datadog_checks.jmx: No module named jmx
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - jmx: No module named jmx
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Python Check Loader: unable to load the check 'jmx': No module named jmx
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Core Check Loader: unable to load the check 'jmx': check jmx appears to be a JMX check - skipping
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | JMX Check Loader: successfully loaded check 'jmx'
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - datadog_checks.kafka: No module named kafka
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Python Check Loader: unable to load the check 'kafka': Unable to find a check class in the module: cannot find a subclass of <class 'datadog_checks.checks.base.AgentCheck'> in module <module 'kafka' from '/opt/datadog-agent/embedded/lib/python2.7/site-packages/kafka/__init__.pyc'>
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Core Check Loader: unable to load the check 'kafka': check kafka appears to be a JMX check - skipping
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | JMX Check Loader: successfully loaded check 'kafka'
2018-07-25 16:52:35 UTC | WARN | (check.go:244 in Configure) | could not get a check instance with the new api: __init__() takes at least 4 arguments (4 given)
2018-07-25 16:52:35 UTC | WARN | (check.go:245 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
2018-07-25 16:52:35 UTC | WARN | (check.go:270 in Configure) | passing `agentConfig` to the constructor is deprecated, please use the `get_config` function from the 'datadog_agent' package (kafka_consumer).
2018-07-25 16:52:35 UTC | DEBUG | (check.go:272 in Configure) | python check configure done kafka_consumer
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:121 in Load) | python loader: done loading check kafka_consumer
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Python Check Loader: successfully loaded check 'kafka_consumer'
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - datadog_checks.cpu: No module named cpu
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - cpu: No module named cpu
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Python Check Loader: unable to load the check 'cpu': No module named cpu
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Core Check Loader: successfully loaded check 'cpu'
2018-07-25 16:52:35 UTC | WARN | (check.go:244 in Configure) | could not get a check instance with the new api: __init__() takes at least 4 arguments (4 given)
2018-07-25 16:52:35 UTC | WARN | (check.go:245 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
2018-07-25 16:52:35 UTC | WARN | (check.go:270 in Configure) | passing `agentConfig` to the constructor is deprecated, please use the `get_config` function from the 'datadog_agent' package (disk).
2018-07-25 16:52:35 UTC | DEBUG | (check.go:272 in Configure) | python check configure done disk
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:121 in Load) | python loader: done loading check disk
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Python Check Loader: successfully loaded check 'disk'
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - datadog_checks.file_handle: No module named file_handle
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - file_handle: No module named file_handle
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Python Check Loader: unable to load the check 'file_handle': No module named file_handle
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Core Check Loader: successfully loaded check 'file_handle'
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - datadog_checks.io: No module named io
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Python Check Loader: unable to load the check 'io': Unable to find a check class in the module: cannot find a subclass of <class 'datadog_checks.checks.base.AgentCheck'> in module <module 'io' from '/opt/datadog-agent/embedded/lib/python2.7/io.pyc'>
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Core Check Loader: successfully loaded check 'io'
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - datadog_checks.load: No module named load
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - load: No module named load
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Python Check Loader: unable to load the check 'load': No module named load
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Core Check Loader: successfully loaded check 'load'
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - datadog_checks.memory: No module named memory
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - memory: No module named memory
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Python Check Loader: unable to load the check 'memory': No module named memory
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Core Check Loader: successfully loaded check 'memory'
2018-07-25 16:52:35 UTC | WARN | (check.go:244 in Configure) | could not get a check instance with the new api: __init__() takes at least 4 arguments (4 given)
2018-07-25 16:52:35 UTC | WARN | (check.go:245 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
2018-07-25 16:52:35 UTC | WARN | (check.go:270 in Configure) | passing `agentConfig` to the constructor is deprecated, please use the `get_config` function from the 'datadog_agent' package (network).
2018-07-25 16:52:35 UTC | DEBUG | (check.go:272 in Configure) | python check configure done network
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:121 in Load) | python loader: done loading check network
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Python Check Loader: successfully loaded check 'network'
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - datadog_checks.ntp: No module named ntp
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - ntp: No module named ntp
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Python Check Loader: unable to load the check 'ntp': No module named ntp
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Core Check Loader: successfully loaded check 'ntp'
2018-07-25 16:52:35 UTC | DEBUG | (loader.go:89 in Load) | Unable to load python module - datadog_checks.uptime: No module named uptime
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:567 in getChecks) | Python Check Loader: unable to load the check 'uptime': Unable to find a check class in the module: cannot find a subclass of <class 'datadog_checks.checks.base.AgentCheck'> in module <module 'uptime' from '/opt/datadog-agent/embedded/lib/python2.7/site-packages/uptime/__init__.pyc'>
2018-07-25 16:52:35 UTC | DEBUG | (autoconfig.go:556 in getChecks) | Core Check Loader: successfully loaded check 'uptime'
2018-07-25 16:52:35 UTC | DEBUG | (jmxfetch.go:224 in Start) | Args: [-Xmx200m -Xms50m -classpath /opt/datadog-agent/bin/agent/dist/jmx/jmxfetch-0.20.1-jar-with-dependencies.jar org.datadog.jmxfetch.App --ipc_host localhost --ipc_port 5001 --check_period 15000 --log_level INFO --reporter statsd:localhost:8125 collect]
2018-07-25 16:52:35 UTC | INFO | (jmxfetch.go:208 in func1) | Log location is not set, will output log to stdout.
2018-07-25 16:52:35 UTC | INFO | (jmxfetch.go:208 in func1) | 2018-07-25 16:52:35,904 | INFO | App | JMX Fetch has started
2018-07-25 16:52:36 UTC | INFO | (jmxfetch.go:208 in func1) | 2018-07-25 16:52:36,583 | WARN | App | Failed collecting JSON configs: [403]
2018-07-25 16:52:36 UTC | INFO | (jmxfetch.go:208 in func1) | 2018-07-25 16:52:36,583 | WARN | App | No instance could be initiated. Retrying initialization.
2018-07-25 16:52:51 UTC | INFO | (jmxfetch.go:208 in func1) | 2018-07-25 16:52:51,691 | WARN | App | Failed collecting JSON configs: [403]
2018-07-25 16:52:51 UTC | INFO | (jmxfetch.go:208 in func1) | 2018-07-25 16:52:51,691 | WARN | App | No instance could be initiated. Retrying initialization.

Those last 2 lines repeat forever until I Ctrl-C the check.
I have confirmed that kafka is running and JMX is available on port 9999, by creating a tunnel to my local machine and connecting with Jconsole.
Describe what you expected:
I expect the check to work, show up in the sudo datadog-agent status results, and ship to datadog.
Additional environment details (Operating System, Cloud provider, etc):
Running on amazon linux 2018.03.  Java 1.8.0
Thanks for the help!

Note that I also get similar results with the jmx check, with config set as:
init_config:

instances:
  - host: localhost
    port: 9999

I release this isn't set to collect any metrics, but I wanted to see if it would at least connect.

+1


[Request]  Wind financial tool

Package Request
Criteria
For a package to be acceptable in the Extras bucket, it should be:

[x] a well-known and widely used tool (e.g. if it's a GitHub project, it should have at least 100 stars and 50 forks)
[x] the latest stable version of the program

Information
Name: Wind financial tool
Description: A financial data tool
Homepage: https://www.wind.com.cn
Download link(s): https://d-cdn.wind.com.cn/windnet/WFT_Setup_CHS.zip
Some indication of popularity/repute:  Cannot find the webpage for it

Please don't request non-English apps in official buckets.

And why do you plan to install Wind via Scoop? Its huge size, Excel plugin, update mechanism, etc. are totally incompatible with Scoop.
I use it every day and never thought portable installation of it.

This was discussed before, in an old post. Sorry and I will add it in the issue template.
Believe me, the installation process of WFT will never be easier.


Failure for @GwtCompatible(serializable = true) class when containing a Multiset

For example:
@FreeBuilder
@GwtCompatible(serializable = true)
public abstract class Foo {

  public abstract ImmutableMultiset<String> getBar();

  static class Builder extends Foo_Builder {}
}

fails with:
java.util.MissingFormatArgumentException: Format specifier '%s'
[...]
at org.inferred.freebuilder.processor.util.SourceStringBuilder.add(SourceStringBuilder.java:70)
at org.inferred.freebuilder.processor.util.SourceStringBuilder.addLine(SourceStringBuilder.java:76)
at org.inferred.freebuilder.processor.MultisetPropertyFactory$CodeGenerator.addSetFromResult(MultisetPropertyFactory.java:383)
at org.inferred.freebuilder.processor.GwtSupport$CustomValueSerializerExcerpt.addTo(GwtSupport.java:112)
at org.inferred.freebuilder.processor.util.SourceStringBuilder.add(SourceStringBuilder.java:60)
at org.inferred.freebuilder.processor.util.CompilationUnitBuilder.add(CompilationUnitBuilder.java:73)
at org.inferred.freebuilder.processor.CodeGenerator.writeBuilderSource(CodeGenerator.java:86)
at org.inferred.freebuilder.processor.Processor.process(Processor.java:104)
[...]

Looking at the generator, it seems like there is one too many %s in the format string there.

This should be fixed as of https://github.com/google/FreeBuilder/releases/tag/v1.13. Apologies for the delay! In retrospect, I should have fixed this first as a point release, but I wasn't expecting #225 to take quite so long in review 😞


Add disclaimer to resample. Closes #385.

Codecov Report

Merging #386 (013fe17) into main (a43b342) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #386   +/-   ##
=======================================
  Coverage   79.33%   79.33%
=======================================
  Files          38       38
  Lines        3135     3135
=======================================
  Hits         2487     2487
  Misses        648      648

Impacted Files
Coverage Δ

src/methods/resample.jl
73.07% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Doctest error seems unrelated.


Build riscv64 container

Blocked by qemu >=8.2.0 support in https://github.com/tonistiigi/binfmt, which is required to run bionic-libc on riscv64.

Switched to fedora: https://github.com/dart-android/toybox/commit/51adecace7a9820c18a85cab7ed24f8c0364677a


RFM - charles

https://chocolatey.org/packages/Charles
I wrote to the maintainer on November 15. Also left comment under package. There was a pull request kevnord/CharlesChocolateyPackage#3 long ago, but the maintainer did not react.
Anyone taking this package, keep in mind that this package only tracks version 3 in https://www.charlesproxy.com/download/previous-release/. Version 4 is tracked by https://chocolatey.org/packages/charles4.

Recently several users upvoted my comment in Disqus, so I would like to take this package. I have wrote through “Contact Site Admins” but just also adding it here for the record.


[WIP] HIVE-28490: Stop removing retainable DPP sources

What changes were proposed in this pull request?

This patch changes the implementation of SharedWorkOptimizer#findAscendantWorkOperators. For a given operator, original findAscendantWorkOperators() returns a set of operators that belongs to ancestor vertices of the vertex that given operator belongs to. Therefore, some operators that are irrelevant to the given operator also belong to the resultant set, which leads to wrong DPP source removal. The new implementation returns a set of ancestor operators of the given operator.
Please check out the slides attached in the JIRA page (HIVE-24890) for further explanations.
Why are the changes needed?

In order to prevent the removal of retainable DPP sources that are still useful in runtime.
Does this PR introduce any user-facing change?

No
Is the change a dependency upgrade?

No
How was this patch tested?

We tested this patch by running all TPC-DS queries in cluster. This patch contains a qfile test that reproduces the wrong DPP source removal.

tips: HIVE-24890 => HIVE-28490

@BsoBird , thanks for pointing out the typo. I fixed it.

thanks for the fix @ngsg! sorry for the late reply. I've added a few comments

@ramesh0201, @kasakrisz, could you please take a look at this PR as a second pair of eyes? thanks!

ok, since there were no other reviews, I am merging this PR


Reexport cpal

That would be useful so that we could use e.g. cpal::default_host().default_output_device() at a given time to get the current default output divice, and reuse it later.
Because rodio is so tied to a given cpal version and some of its interfaces come from it, that would make sense.

#362


Fix goals panel when no proof is active on Coq >= 8.16.

Traditionally, Coq IDEs used the 'Goals' XML command to get the proof state, which had the downside that the full details of non-foreground goals would get serialized from coqidetop but never displayed. In Coq 8.16, the 'Subgoals' command was added, which allows more precise goal fetching: IDEs can make one Subgoals call to request the focused goal in full detail, and another call to request just the conclusions of the other goals. Coqtail switched to this pattern in v1.7.1.
Unfortunately, the logic for merging results from the two calls was slightly wrong. If the calls return None, then there is no proof in progress, but the logic in Coqtail handled this as if there is an in-progress proof with no remaining goals. This made the Goals panel always show "0 subgoals" even when no proof was in progress.
Fix it. If the first call returns None, there is no proof in progress, and we don't bother to make the second call. Else, we learned that there is a proof in progress and what the foreground goal (if any) is; we make the second call to learn the other goals, and then merge the results and continue as before.
Fixes c077a72329dc30fa22802a3a7de49856cb0f1fca.

Thanks for the fix, this looks great.


Numba 0.50.1 downloaded from conda fails to compile on GPU (but works when using pip)

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

Bug report
When installing numba from conda and running the standard test on GPU, i.e.
conda install numba
python -m numba.runtests numba.cuda.tests

I get a compilation error:
numba.cuda.cudadrv.error.NvvmError: Failed to compile

<unnamed> (25, 17): parse expected binary operation in atomicrmw
NVVM_ERROR_COMPILATION

On the other hand, when using pip:
pip install numba
python -m numba.runtests numba.cuda.tests

the tests are running without any issue.
When playing around (e.g. installing numba always from pip, but installing llvmlite either from conda or pip), it seemed to me that the issue comes from the version of llvmlite downloaded from conda...
More details
In the case of conda, the following packages were downloaded.
  llvmlite           pkgs/main/linux-64::llvmlite-0.33.0-py37hd408876_0
  numba              pkgs/main/linux-64::numba-0.50.1-py37h0573a6f_0
  tbb                pkgs/main/linux-64::tbb-2020.0-hfd86e86_0

On the other hand, in the case of pip, the following packages were downloaded:
llvmlite-0.33.0-cp37-cp37m-manylinux1_x86_64.whl
numba-0.50.1-cp37-cp37m-manylinux2014_x86_64.whl

The tests are run on a GTX 1080 Ti with cudatoolkit 9.0 installed from conda (Build h13b8566_0).

Thanks for the report, I can reproduce. From the error I think the Anaconda llvmdev builds aren't carrying the patch that prevents instruction upgrade.

Thanks for letting me know.
Is there a chance that the conda build could be updated, so as to include the patch?

We're checking with them now to get a fixed build rolled out.

CC @angloyna for updates (with thanks for patching upstream!)

Anaconda llvmdev has been patched, the latest numba 0.50.1 should have it. Let me know if we're still seeing the issue.

Great! I confirm that this fixed the issue. Thanks a lot!

Thanks to you both @angloyna @RemiLehe, good to see this fixed.

As a quick follow-up: I just noticed that, even though llvmlite 0.33 was updated in the numba channel, it is not updated in the conda-forge channel.
Therefore, users that were using e.g. conda install -c conda-forge numba were still getting the above-mentioned bug.
Is there any chance that the conda-forge package could be updated too?


Allow option to create dynamo tables with encryption at rest enabled

Is your feature request related to a problem? Please describe.
Tables created by amplify cli appsync api have encryption disabled. This is one of these settings that can only be turned on when tables are created.
Describe the solution you'd like
An option in amplify to by default turn on encryption for tables. Why don't you always turn it on anyways? There's no cost to encryption at rest.
Describe alternatives you've considered
Currently have to create dynamo db tables outside of amplify cli to get this setting.

This is on our backlog along with automatically enabling auto scaling for DynamoDB tables.

This has since been enabled.


Disable OK button in prompt dialog if Text lenght is = 0

Is it possible? I think this could be enhancement ...

It likely is possible with a fair degree effort.  On iOS and Android, I have to go crawling through the views to find the button.    This isn't a particular case I want to get into based on those facts alone.

K, thanks


warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call

Can new version of gem be released?
This small change https://github.com/ClosureTree/closure_tree/pull/373/files#diff-4e9c3ec5f63b801dd2128282bb992e89b5894d45b513dda0f98a805406646afdR11 didn't get into latest gem release 7.2.0 and produces warnings in Ruby 2.7:
/Users/vlazar/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/closure_tree-7.2.0/lib/closure_tree/has_closure_tree_root.rb:11: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/Users/vlazar/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activerecord-6.1.4/lib/active_record/associations.rb:1607: warning: The called method `has_one' is defined here

And in Ruby 3.0 this would prevent closure_tree from working at all.

yes.


Code coverage

@karljj1 Can you create an account on Codecov for kdis
Thanks 🥳🤗

Its setup. I added the secret, you just need to put it into the actions somewhere:
- name: Upload coverage reports to Codecov
  uses: codecov/codecov-action@v3
  env:
    CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

Awesome.
Only to be certain, have you set up the Open Source project template for Codecov? (The token is not necessary if OSS)

Awesome. Only to be certain, have you set up the Open Source project template for Codecov? (The token is not necessary if OSS)

I dont see that option. There are 3 I can see: Github Actions, CircleCI and Other CI.

Ok, it works!
See https://app.codecov.io/github/karljj1/kdis/commit/e30ab184937047dd379a7e6dbb8d6e93cfedd940

@karljj1 Can you install https://github.com/apps/codecov in the repo. Thanks

@karljj1 Can you install https://github.com/apps/codecov in the repo. Thanks

Is it all working now?

@karljj1 Can you install https://github.com/apps/codecov in the repo. Thanks

Is it all working now?

It should be automatic :)


[Impeller] Allow vertex layout customization at runtime.

Impeller's assumedly staggered vertex layout beautifully mixes with the ImpellerC's generated headers to offer predictable and easy to use default vertex binding behavior that fits the bill for most use cases. However, there are times where taking full control of the vertex layout can offer performance benefits.
Examples:

Structure of arrays: For VerticesGeometry, the DisplayList vertices are given in an SOA structure, so we're forced to unnecessarily convert the data into a staggered form on the CPU before uploading to the GPU.
Binding vertices across multiple buffers: In https://github.com/flutter/flutter/issues/116165, being able to bind two buffers (one with only vertex positions and another with other attributes like position and color) would allow easy reuse of position buffers for common shapes regardless of the color source.
Industry standard formats: Impeller is slated to help a lot of people do great things, some of which I believe will involve consuming industry standard 3D geometry intended for efficient runtime consumption by renderers. Vertex attributes for 3D models are often stored in an SOA format which can be uploaded directly to the GPU without conversion given the ability to control the vertex layout at runtime. Some formats, such as GLTF, even offer arbitrary vertex layout customization. Without control over the vertex layout, renderers build on Impeller that consume these standards will be forced to convert the geometry to a staggered form with a specific attribute ordering prior to GPU upload.

A good design for vertex layout customization would implicitly address https://github.com/flutter/flutter/issues/102778.

Current set of work on this involves making the interleaved layout explicit in the impeller backend generated shaders. This will force us to expose a reasonable API for customizing vertex layout.

Copying from https://github.com/flutter/flutter/issues/139560:
We should mirror how vertex attributes work on the backends.
Currently, the stride is tied to a ShaderStageBufferLayout, which itself is tied to a specific binding. So we're forcing each binding to contain an interleaved layout, and it's not currently possible to bind a basic single-buffer SoA layout. This is important for efficiently loading common interchange formats like glTFs and is easy to accomplish on all backends.
Remove the ShaderStageBufferLayout concept. An array of attributes is an attribute layout. The default interleaved layout output in the impellerc reflection header should just be an array of attributes.
Each attribute should have:

a binding (the index of a bound vertex buffer -- multiple vertex buffers should be allowed),
an offset (the byte offset of the zero index element of the attribute),
a stride (the byte offset in-between the start of each successive element of the attribute), and
element type information (including the byte size of an element, etc).

Started digging into what we've landed so far again and I think we're actually good to go in terms of the shape of the pipeline layout description itself. Similar to Metal and Vulkan, ShaderStageBufferLayout::binding and ShaderStageIOSlot::binding both refer to the index of a theoretical vertex buffer binding list. These "bindings" are actually buffer views.
The pipeline binding for Vulkan and Metal look reasonable. We just need to allow binding multiple vertex buffers per command.


Adding optional parameters to the set_test function

Re-implementing change that had been left in the shuffle when resolving conflicts on the last PR merge

@valentijnscholten I accidentally left out a change with the last PR due to the complexity of the merge.

https://github.com/DefectDojo/defectdojo_api/blob/eba97019a75858d5afbe371f5fce89b3804ea51c/defectdojo_api/defectdojo_apiv2.py#L501  this is throwing syntax error, maybe got ignored while pushing.

should be good now


Infinite loop inside white block due to improper implementation of retrace detection.

The spec says (emphasis mine)

Each time the interpreter hits a restriction while within the white block, it toggles the CC and steps the DP clockwise, then tries to slide again. This process repeats until the interpreter either enters a coloured block (where execution then continues); or until the interpreter begins retracing its route. If it retraces its route entirely within a white block, there is no way out of the white block and execution should terminate.

However, it seems this is not properly implemented.
How to Reproduce

Download this small image

Run cargo run -- <downloaded_image> --verbose

Expected Trace

Actual Trace

(0, 0)
(1, 5)
(1, 6)
(1, 7)
(1, 8)
(2, 8)
(3, 8)
(3, 7)
(3, 6)
(2, 6)
(1, 6)
(1, 7)
(1, 8)
(2, 8)
...

Fixed locally. Will be pushed and released in a few days.


uint64 to float64 refactoring

- Summary
Fixed issue #153.
Motivation: This fix will help increase precision in the calculations on the gocommerce platform.
- Test plan
Make test
In observation of the test cases expected values and the exactness of the new floating point dollar amounts, I believe it is appropriate to change Assert.Equal to Assert.InDelta. The latter assert, which takes in a Tolerance value, allows for comparing the expected value and actual value under a certain precision.
- Description for the changelog
uint64 to float64 refactoring

@divyashie Thank you very much for the PR, interest and time!  I'm going to close this approach for now for the reasons @mraerino mentioned, but if you are still interested on the problems, lets discuss ideas in https://github.com/netlify/gocommerce/issues/153


OwnedMultiDeviceIterator can cause an error on TPU pods

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.2.0-rc4
Python version:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture
Describe the current behavior
OwnedMultiDeviceIterator can cause an error on TPU pods.
the resulting stack trace :
gc/0 E0428 07:24:15.171094 132699 main app.py:658 Top-level exception:  could not parse rpc response
[[{{node iterator_13/_89}}]] [Op:__inference_minimize_49326]
Function call stack:
minimize
gc/0 E0428 07:24:15.172459 132699 main app.py:659 Traceback (most recent call last):
File "/launcher_root/google3/third_party/py/absl/app.py", line 463, in run
_run_main(main, args)
File "/launcher_root/google3/third_party/py/absl/app.py", line 392, in _run_main
sys.exit(main(argv))
File "/launcher_root/google3/experimental/users/wendyshang/smarl/football/football/vtrace_main.py", line 153, in main
env.create_environment(0), create_agent, create_optimizer)
File "/launcher_root/google3/experimental/users/wendyshang/smarl/football/football/learner_object.py", line 574, in learner_loop
minimize(it)
File "/launcher_root/google3/third_party/tensorflow/python/eager/def_function.py", line 695, in call
result = self._call(*args, **kwds)
File "/launcher_root/google3/third_party/tensorflow/python/eager/def_function.py", line 760, in _call
return self._concrete_stateful_fn._filtered_call(canon_args, canon_kwds)  # pylint: disable=protected-access
File "/launcher_root/google3/third_party/tensorflow/python/eager/function.py", line 1904, in _filtered_call
cancellation_manager=cancellation_manager)
File "/launcher_root/google3/third_party/tensorflow/python/eager/function.py", line 1981, in _call_flat
ctx, args, cancellation_manager=cancellation_manager))
File "/launcher_root/google3/third_party/tensorflow/python/eager/function.py", line 615, in call
ctx=ctx)
File "/launcher_root/google3/third_party/tensorflow/python/eager/execute.py", line 60, in quick_execute
inputs, attrs, num_outputs)
google3.third_party.tensorflow.python.framework.errors_impl.InternalError:  could not parse rpc response
[[{{node iterator_13/_89}}]] [Op:__inference_minimize_49326]
Function call stack:
minimize
Describe the expected behavior
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

The issue was fixed the by this commit


Add switch to stop Table warnings about metadata issues

When combining variables with different units (and short units) it is useful to have a warning. For example:
tb = Table({"index": [1, 2, 3], "a": [4, 5, 6], "b": [7, 8, 9]})
tb["a"].metadata.unit = "terawatt-hours"
tb["b"].metadata.unit = "megawatt-hours"
tb["c"] = tb["a"] + tb["b"]

will raise a warning because "a" and "b" have different units.
When doing a melt operation,
tb.melt(id_vars="index", value_vars=["a", "b"])

you also get a warning if you are melting together variables with different units. In this case, it would also be useful. But if you are consciously melting together variables with different units, you may want to hide the warning (which is what started this conversation).
For that reason, this PR lets you do that in two ways:
(A) Having a general switch Table.WARN = False that turns off all warnings.
(B) Having a function argument melt(..., warn=False).
Similarly, I created a class-level WARN attribute to Variable, in case we want to turn off warnings for other operations (e.g. tb["a"] + tb["b"]).
@Marigold what do you think about this approach? Please let me know if you think there are better solutions.

I recently run into a similar issue where I needed to silence a (different type) of warning. Your approach would work, but I'm not sure how well will it scale with more types of warnings. Perhaps we could go with native python warnings instead and silence them with context managers like this
import warnings

class MetadataWarning(UserWarning):
    pass

class DifferentValuesWarning(MetadataWarning):
    pass

def foo():
    warnings.warn("Different values detected", DifferentValuesWarning)

# ignore warnings with context manager
with warnings.catch_warnings():
    warnings.simplefilter("ignore", MetadataWarning)
    foo()

# we could create our own context manager to make it more concise
# with ignore_metadata_warnings():
#     foo()

# Alternatively, control warnings at the module level
# warnings.simplefilter('ignore', MetadataWarning)

That way, we wouldn't need to propagate warn all the way down.
(My bad for using log.warning which doesn't have a good mechanism for silencing them except of setting log level.)
What do you think about this alternative?

@pabloarosado let me know if you want me to implement it. I want to also look at step data://grapher/lis/2023-08-30/luxembourg_income_study which raises tons of warnings that should be silenced (or fixed?).

Hi @Marigold, yes, feel free to implement those changes you suggested. I was a bit unsure about using warning, since the output is much less nice than what we currently have (though I suppose there may be a way to improve it).

Yeah, that's precisely why I went for log.warning instead. I'll think about this again and reconsider whether it's worth it or not.

Closing this, since @Marigold already implemented a better solution in https://github.com/owid/etl/pull/2418


Use v1alpha1 api version in infrastructure status raw extension.

References #28.

Closes #28.
Tried it out, seems to work.


Problem with filter interval date

I have a spark dataframe with a date variable:
glimpse(df %>% select(REF_DATE))

> Observations: ??
> Variables: 1
> Database: spark_connection
> $ REF_DATE <dttm> 2018-01-05, 2017-10-26, 2017-03-11, 2018-03-19, 2017-12-16, 2017-10-19, 2018-03-07, 2018-03-08, 2017-06-30, …

And i want to filter the date below:
modelagem = c(start = '2017-01', end = '2017-12'') # format Y-m

Don't filter the date 2017-12-31

df_modelagem = df %>% filter(ALVO %in% c(0,1), REF_DATE >= paste0(modelagem[1],"-","01") & REF_DATE <= paste0(modelagem[2],"-","31"))

Filter date 2017-12-31

df_modelagem = df %>% filter(ALVO %in% c(0,1), REF_DATE >= paste0(modelagem[1],"-","01") & REF_DATE <= paste0(modelagem[2],"-","32"))

Why don't filter date 2017-12-31 using the code 1 if i used <= ??

dttm evaluation is very weird. Reprex:
## local table
test_dt_1 <- data.table(
    a = c(1, 2, 3),
    b = c(123.12, 234.23, NA),
    c = c("apple", "banana", "carrot"),
    d = c(TRUE, FALSE, FALSE),
    e = c("2018-01-01", "2018-01-01", "2018-01-01")
)

## remote table
test_spark <- copy_to(
    dv01_spark_connection,
    test_dt_1
)

Exact equivalence comparison between parent chr field and dttm works. It looks like this is being performed as a date comparison
test_spark %>% mutate(f = to_timestamp(as.Date(e))) %>% filter(e == f)
# Source:   lazy query [?? x 6]
# Database: spark_connection
      a     b c      d     e          f
  <dbl> <dbl> <chr>  <lgl> <chr>      <dttm>
1     1  123. apple  TRUE  2018-01-01 2018-01-01 00:00:00
2     2  234. banana FALSE 2018-01-01 2018-01-01 00:00:00
3     3  NaN  carrot FALSE 2018-01-01 2018-01-01 00:00:00

However, greater-than-or-equal-to comparison between parent chr and dttm field fails...
test_spark %>% mutate(f = to_timestamp(as.Date(e))) %>% filter(e >= f)
# Source:   lazy query [?? x 6]
# Database: spark_connection
# ... with 6 variables: a <dbl>, b <dbl>, c <chr>, d <lgl>, e <chr>, f <dbl>

parent chr is < dttm.