Fixed the 'spo site classic list' command solving #1266

Solves #1266
Rather than returning the full JSON response in a single command log, this PR changes the behavior so that each site returned is individually returned as a JSON object to the terminal.
Using jq on bash or ConvertFrom-Json in PowerShell Core successfully parses the terminal outputs as collections which can then be used in scripting scenarios.
This is a potentially breaking change for bash as jq will no longer need to process an array of objects so any current implementation using jq '.[]' will break, this change does no affect PowerShell Core.

Coverage remained the same at 100.0% when pulling 42c4346e1e24dc06546d11c0ed6fa9ef9485b367 on garrytrinder:1266 into 463b41ba4abf33416eac1aafe0eee96798d4f5ca on pnp:dev.

Does the breaking behavior occur in every case or just when the output exceeds a certain length? We should avoid introducing breaking changes. If the command doesn't work at all then I wouldn't hesitate a moment to merge this PR, but if the command works in some cases and breaks in other then, as you noticed, we'd be introducing a breaking change and to play it fair, we should consider a major version bump to indicate that this change isn't backward compatible.

@waldekmastykarz  agree.
@garrytrinder this should be as easy as changing the code to something like:
if (args.options.output === 'json') {

    const maxLenght: number = <BIG_NUMBER>;

    if(sites._Child_Items_.lenght < maxLenght) {
            cmd.log(sites._Child_Items_);
    } else {
            sites._Child_Items_.forEach(s => cmd.log(s));
    }
}

One more I've been wondering about: if we output every site as a separate object to the output, how would jq for example process them since they're not in one array?

Does the breaking behavior occur in every case or just when the output exceeds a certain length?

Just when the output exceeds a certain length.

if we output every site as a separate object to the output, how would jq for example process them since they're not in one array?

jq treats each output as an item in a collection in the same way as pwsh. <output> | jq -r  '.Title, for example, would return all site titles in the collection. Currently this would be done by using, <output> | jq -r  '.[] | .Title as we return the raw JSON output which is an array.
@VelinGeorgiev I see where you are going with your approach but I would be cautious to return different outputs, if the maxlength is exceeded then we would return multiple objects but if underneath the limit we would return the raw JSON which would be an array.

@garrytrinder if the new construct can be still properly handled with jq then I'd be in favor of merging it in. I was concerned that perhaps the new output would block jq users from properly processing output but if that's not the case, then we can consider the current behavior as undesired and move to your proposed changes.

One other consideration to make is that by merging this PR it will cause inconsistency with other ‘list‘ commands for ‘jq‘ users as they will still return arrays.

I’m re-considering this approach.
Whilst it will provide a fix for this command it does not solve the root cause, if we have a large JSON response that exceeds the length limit from any of the list commands, we will run into this issue.
I will close this PR, in favour of investigating further into a fix for the root cause.
My initial thought around root cause is the way that we handle responses centrally, ideally we should be reading HTTP responses in chunks. Currently we return the full response to the command which is then returned to the terminal with a single console.log()


NaN times are possible for certain quality masks.

I see NaN times when I use a quality_bitmask=None:
tpf = KeplerTargetPixelFile.from_archive(201572338, quality_bitmask=None)
nan_times = tpf.time != tpf.time
nan_times.sum()

145

Many of these NaN times have quality values of 98304, which indicates 'No fine point', 'No data'.
The possibility of NaN times is not necessarily a bug, and will likely only occur when quality_bitmask=None, since these quality flags are masked by default.  However, their presence does raise the question of whether we want to build in resilience to the possibility of NaN times.  They do have cadence numbers.
This question arose while designing tpf.interact(), which has so-far safely assumed times are all finite, but gets broken when NaN times are present.  I suspect it affects other places in the code that assume finite times.

It would be nice to have tasks that can handles NaNs properly. In the meanwhile,
I think expanding the documentation a bit would help with this issue. Something like:
quality_bitmask : str or int
        Bitmask specifying quality flags of cadences that should be ignored.
        If `None` is passed, then no cadences are ignored. Note that,
        in this case, there might be candences with NaN values in either time, flux, or both.

Why are these not taken care of by the remove_nans() function?
remove_nans() should remove cadences where time and/or flux are nans.
It could optionally have a keyword to drop the nans in the flux_err as well. @andytza, try this one out instead.

Fix the remove_nans() function to remove nans in time
Add a unit test to test_lightcurve.py to verify that nans in time are removed.


Updating default jira version to 8.20.13

Pull request description
Fixes #452 ,
bumps default version to 8.20.13 for security patches
Checklist

[ ] I have added unit tests
[x] I have applied the change to all applicable products
[x] I have added the change description to the changelog.md and Chart.yaml files
[ ] (Atlassian only) I have run the E2E test (if applicable)
[ ] (Atlassian only) Internal Bamboo CI is passing

Hi @Jeremy-Boyle , thanks for the contribution!
Do you mind fixing the unit tests as well?

Hi I sure can ! Thanks for the review, I see it's failing on a maven issue, I'll take a look to see what is causing it however all other things deployed correctly, what is the purpose of the maven test with a helm chart ?
Is the error related to my changes ?

Hi I sure can ! Thanks for the review, I see it's failing on a maven issue, I'll take a look to see what is causing it however all other things deployed correctly.

Awesome, @Jeremy-Boyle ~
Here is code as reference: https://github.com/atlassian/data-center-helm-charts/pull/455/files#diff-63ea51911cc0f4498740fb7f8ee9bba6524a8c59bf6378ae51489847c9178444
In your case, src/test/resources/expected_helm_output/jira/output.yaml needs to be updated to the newer version.

Hi @Jeremy-Boyle , just two minor issues to be fixed for the unit test: https://github.com/atlassian/data-center-helm-charts/actions/runs/3183460733/jobs/5198287045#step:11:1018
And also, do you mind pulling the latest main into your branch as well? Cheers~


replacing "href" with "#"

Challenge Make Dead Links using the Hash Symbol has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Click here for cat photos.

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

I replaced "href" with "#" as noted in the instructions for the line that reads:
"Click here for cat photos."
and it does not register as me having done so.

@phoenixwarrior thanks for the issue but GitHub issues are not for coding help. If you get stuck or have questions with a challenge in the future, please first ask questions to the Help Room.
Here's a hint:

Replace the value of your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link.

Happy coding!

Yes someone in the help room was able to help after I sent this.
However, the instructions Spefically say to replace href. Obviously this is
incorrect and it is the link that is to be replaced. Perhaps that should be
corrected? Or at least better explained?
And since the issue transcends a mere coding help issue, but rather is an
issue with the lesson in and of itself, where else should it be noted to?
On Aug 9, 2016 12:44 AM, "Eric Leung"<EMAIL_ADDRESS>wrote:

@phoenixwarrior https://github.com/phoenixwarrior thanks for the issue
but GitHub issues are not for coding help. If you get stuck or have
questions with a challenge in the future, please first ask questions to the Help
Room https://gitter.im/FreeCodeCamp/Help.
Here's a hint:
Replace the value of your a element's href attribute with a #, also
known as a hash symbol, to turn it into a dead link.
Happy coding!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/10135#issuecomment-238451938,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATzL24J_i_vMYWulhUFOmjGaTv4ddOFAks5qeAXGgaJpZM4JfsDm
.

@phoenixwarrior thanks for the feedback, but again I feel that the last sentence of the instructions are sufficient enough:

Replace the value of your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link.

In addition, if you look at the challenge test, this should also further clarify that you need to replace the link and not the text href itself.

Your a element should be a dead link with a href attribute set to "#".

If this is still not clear enough, feel free to reply back with a clearer modification of these instructions. We welcome feedback and suggestions that will improve users' experiences with Free Code Camp.

@erictleung Yea for me it was the last sentence that I found to be the confusing and misleading part.
"Replace the value of your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link."
Here is how,as someone who is new to code, this sentence reads to me.
within my "a" element line of code, there is a "href attribute" And I need to replace that with a hash(#).
My first thought is not to replace the quoted  link url, but rather the letters href.(of the two which has the attributes of being href?) And secondly, the instruction says I am causing the link url to be dead,not delete the link all together. And so like commenting something out, one adds --><--around the code, so the code stays if one wish to un-comment it, And so I thought it would be so here to,replace href with # and that will cause the link to be dead, and if later I want to make it active again,I would replace # with href. Obviously deleting the link url, I cant do that unless I first find the url again. As a new coder I wouldn't have thought to do or risk that happening.
I think this is easy enough to clarify within the instructions though, it could read:
"A href attribute is the quoted link url itself within the "a" element. Replace the value of your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link."
Or, "Replace the value of your a element's [quoted link url] with a #, also known as a hash symbol, to turn it into a dead link. make sure not to replace the "".

@phoenixwarrior thanks for your detailed feedback. I like your first suggestion.

The href attribute is the quoted URL link within the a element. Replace the link value of your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link.

@erictleung I can give this a shot.

@erictleung are you just looking for the sentence

"Replace the value of your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link."

to be replaced with

The href attribute is the quoted URL link within the a element. Replace the link value of your a element's href attribute with a #, also known as a hash symbol, to turn it into a dead link.

?

@oalhait yes.

hi,
i replaced the link with # still it is not running..!!!
what should i do?

@Priya2895
Please use the Help chat room for getting challenge related help.
Happy Coding.

I'm having the same problem and smarty pants answers don't cut it

Click here for  cat photos.
this did nothing

they mean get rid of the "http://...." part and replace it with "#"

This is what I Did and it was correct. Click here for cat photos.

i did that and doesn't do anything.

try refreshing the page

I encountered the same issue and was able to proceed after I click refresh.  Thanks.

Make sure you all are adding the hashtag to the appropriate string. You will have the first link at the top of the HTML document and an  at the bottom of the page. Change that href to equal the hashtag.

same here for this challenge,
1.refresh the page
2.using delete , delete the link between " "
3.put # between " "
and my challenge is SOLVED.

Had the same problem. Sometimes the instrcutions on FCC are  quite vague. I have solved many issues but mainly by just gambling..lots of trial and error. W3 schools does a better job with instructions

Poorly written and as we can see the web application has bugs that need to be fixed :)

non e of you answered the question, can someone do this for me, that would be awesome thank you

abc173 above answered the question about chnaging the href... unless you had another question. I did that and It worked for me.

I think more detailed explanation is needed here.

Thank you "abc173" from above.........
It's works for me too....

Like someone previously mentioned before, it needs another explanation..But oh, well haha

Click here for cat photos.

Code   for the below coding challege
Your a element should be a dead link with a href

CatPhotoApp
Click here for cat photos.

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.


:lang idris

Adds basic support for the idris programming language.

Looks good! You've inspired me to check out idris, so I look forward to giving this module a spin.
Thanks again!


Google Analytics Bounce Rates

I am using Komito in GTM for all of my clients, and I have an issue with bounce rate report since 1 Jan 2020. Bounce rates have dropped off dramatically. Is this a known issue with Komito?
Thanks for any help.

Thank you for using Komito Analytics.
It sounds like you have an empty or missing nonInteraction parameter, only this parameter may affect the bounce rate.
Check it out, and if that doesn't help, please send more information to<EMAIL_ADDRESS>

On December 31, we added color scheme tracking.
And looks like you need to add 'color-scheme' to the nonInteraction parameter:
'nonInteraction': ['adblock', 'audio', 'color-scheme', 'form', 'heartbeat', 'orientation', 'print', 'scroll', 'video']

Or you can disable this feature by setting trackColorScheme to 0.

Forced markAsNonInteractionEvent('color-scheme') as part of this commit: bad023c559370666c78423cd8dbc32a93b54acf9
@bluecherryau, thank you for reporting this issue.


[FEATURE] Support EKS 1.22

I tried testing this out myself but ran into problems with CDK.
Unfortunately CDK's lambda-layer-kubectl is not yet compatible with EKS/Kubernetes v1.22, so as of right now CDK has had to rollback support for v1.22. See https://github.com/aws/aws-cdk/pull/20000 for more info.

release date of eks 1.22 is April 4, 2022, 1.23 is planned for August, but we still can not upgrade using cdk

Is there an update for this or an issue for better tracking? We have requests for EKS 1.22 as part of EKS Blueprints. Getting too close to 1.23.

do we have any updates on this? @aceat64

seems like there is not much progress on this

@shapirov103 I see this PR was merged, any news for cdk-eks-blueprints?

@shapirov103 I see this PR was merged, any news for cdk-eks-blueprints?

Indeed, it only took half a year to address the PR. However, while it is merged, it is not released yet. Here is the actual released docs for 2.47. You can see there is no latest EKS versions in the list. I expected the next release 2.48 to happen by end of this week to include it. Then we can test the blueprints.

EKS 1.23 is supported by CDK 2.49.0. Hope this be resolved soon!

@shapirov103 hope we will have release to cover CDK 2.49.0 soon ^^

@vumdao working on it.

This issue is resolved. I will keep it open for a bit to allow testing. Will close it out shortly.

Supporting 1.23 and 1.24 atm. closing.


Add withdraw / withdrawFor function to MerkleDrop contract

Closes https://github.com/trustlines-protocol/merkle-drop/issues/21

I've also got a question: What has been changed in DroppedToken in comparison to the TrustlinesNetworkToken?

Only the title has been changed: https://github.com/trustlines-protocol/merkle-drop/pull/27/files#diff-e17fa307fad8a8fc51f42902f6f7a37cR6

merged with https://github.com/trustlines-protocol/merkle-drop/pull/28


Additional Cloudaux resources for GCP.

Fitbit has been using Security Monkey internally to monitor GCP
environments and we'd like to start contributing back some of that code
to the main Security Monkey project.
This PR contains the following:

Support for GCE Instances
Support for GCE Persistent Disks
Support for GCE Addresses (global and regional)
Support for GCE Forwarding Rules (global and regional)
Support for CRM (i.e., Google Projects and their related IAM policy bindings)

I've also modified the tox.ini to enable the GCP tests which were
previously added but not hooked up to the CI.  In the process I've fixed
a broken GCP test. The tox tests for python3 are failing but should be
resolved when my other pull request is merged.
This is a pre-requisite for Security Monkey watcher and auditor support
for these resource types.
@mikegrima, the Security Monkey changes we've done on top of this would require us to bump the cloudaux version so they can depend on a version with these resources.  Is this something I should request as part of this pull request?  Thanks!

Coverage increased (+3.4%) to 31.307% when pulling d03e15e04f4730974b54947900a4eaa96f492cf7 on angrylogic:gharris/gcp_enhancements into 7610d3793867c33358392e0d40332be2c5560925 on Netflix-Skunkworks:master.

You'll need to up the version number in __about__.py to pre-req it for SM.

@mikegrima - pinging on this.  Are there any other changes you'd like to see?  Thanks!

Sorry -- I completely forgot about this! Reviewing now.

LGTM

Going to publish the new version now-ish

Uploaded 1.6.5 to PyPI.


[vcpkg-cmake-config] Check for unguarded release lib paths

What does your PR fix?
Finds unguarded release lib paths in main cmake config files.
Unlike per-build-type files, main config files are used for release and debug. Unexpected mixing breaks builds. Examples:
szip in hdf5, openssl in aws-sdk-cpp (https://github.com/microsoft/vcpkg/pull/21239#issuecomment-964971664, https://github.com/microsoft/vcpkg/pull/20289#issuecomment-962888771).

Which triplets are supported/not supported?
Waiting for feedback on idea and implementation.

I expected some false positives, but it looks like there are only real issues. x64-linux:
aws-sdk-cpp/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
aws-sdk-cpp/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "\$<LINK_ONLY:pthread>;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libcurl.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libcurl-d.a>;\$<LINK_ONLY:dl>;\$<LINK_ONLY:-lpthread>;\$<LINK_ONLY:OpenSSL::SSL>;\$<LINK_ONLY:OpenSSL::Crypto>;\$<LINK_ONLY:ZLIB::ZLIB>;[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libssl.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libcrypto.a;\$<LINK_ONLY:-lpthread>;\$<LINK_ONLY:dl>;\$<LINK_ONLY:dl>;\$<LINK_ONLY:-lpthread>;/mnt/vcpkg-ci/installed/x64-linux/lib/libz.a;AWS::aws-crt-cpp"
crossguid/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
crossguid/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libuuid.a"
freealut/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
freealut/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libopenal.a;m"
freetype/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
freetype/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "\$<LINK_ONLY:ZLIB::ZLIB>;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libbz2.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libbz2d.a>;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libpng.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libpng16d.a>;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libz.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libz.a>;\$<LINK_ONLY:m>;[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libbrotlidec-static.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libbrotlicommon-static.a"
hdf5/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
hdf5/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "\$<LINK_ONLY:m>;\$<LINK_ONLY:dl>;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libz.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libz.a>;[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libszip.a;\$<LINK_ONLY:\$<\$<BOOL:OFF>:>>;\$<\$<NOT:\$<PLATFORM_ID:Windows>>:dl>;\$<LINK_ONLY:\$<\$<BOOL:OFF>:Threads::Threads>>"
lapack-reference/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
lapack-reference/stdout-x64-linux.log:     set(LAPACK_blas_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libopenblas.a;-lpthread")
leptonica/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
leptonica/stdout-x64-linux.log:       INTERFACE_INCLUDE_DIRECTORIES "/mnt/vcpkg-ci/installed/x64-linux/include;/mnt/vcpkg-ci/installed/x64-linux/include;[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/pkgconfig/../../include;/mnt/vcpkg-ci/installed/x64-linux/include;/mnt/vcpkg-ci/installed/x64-linux/include;/mnt/vcpkg-ci/installed/x64-linux/include;/mnt/vcpkg-ci/installed/x64-linux/include;/mnt/vcpkg-ci/installed/x64-linux/include"
libavif/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
libavif/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libaom.a;-L/mnt/vcpkg-ci/installed/x64-linux/lib/pkgconfig/../../lib;\$<LINK_ONLY:-laom>;\$<LINK_ONLY:-lm>;\$<LINK_ONLY:-lpthread>;\$<LINK_ONLY:m>;\$<LINK_ONLY:Threads::Threads>;/mnt/vcpkg-ci/installed/x64-linux/lib/libyuv.a"
libdatachannel/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
libdatachannel/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "\$<LINK_ONLY:Threads::Threads>;[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libusrsctp.a;\$<LINK_ONLY:OpenSSL::SSL>;\$<LINK_ONLY:LibJuice::LibJuice>"
libdjinterop/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
libdjinterop/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libz.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libz.a>;[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libsqlite3.a"
libevent/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
libevent/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "-lpthread;libevent::core;[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libssl.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libcrypto.a;-lpthread;dl;dl;-lpthread"
libftdi1/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
libftdi1/stdout-x64-linux.log:     set ( LIBFTDI_LIBRARIES    "ftdi1;[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libusb-1.0.a" )
libheif/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
libheif/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/liblibde265.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libx265.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libaom.a"
libssh/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
libssh/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "\$<LINK_ONLY:rt>;[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libmbedcrypto.a;-Wl,--version-script,\"/mnt/vcpkg-ci/buildtrees/libssh/src/b6ec41911d-067f95b6bb.clean/src/libssh.map\""
libwebsockets/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
libwebsockets/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libssl.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libcrypto.a;-lpthread;dl;dl;-lpthread;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libz.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libz.a>;/mnt/vcpkg-ci/installed/x64-linux/lib/liblibuv.a"
log4cxx/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
log4cxx/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libaprutil-1.a;\$<LINK_ONLY:expat::expat>;/mnt/vcpkg-ci/installed/x64-linux/lib/libapr-1.a;\$<LINK_ONLY:pthread>"
minizip-ng/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
minizip-ng/stdout-x64-linux.log:       INTERFACE_LINK_DIRECTORIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/pkgconfig/../../lib;/mnt/vcpkg-ci/installed/x64-linux/lib/pkgconfig/../../lib"
open62541/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
open62541/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libssl.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libcrypto.a;-lpthread;dl;dl;-lpthread;m;pthread;rt"
realsense2/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
realsense2/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libusb-1.0.a"
simage/stdout-x64-linux.log:  Unguarded release path /lib/ path at [>>>]:
simage/stdout-x64-linux.log:       INTERFACE_LINK_LIBRARIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/libgif.a;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libjpeg.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libjpeg.a>;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libpng.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libpng16d.a>;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libz.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libz.a>;\$<LINK_ONLY:m>;\$<LINK_ONLY:m>;/mnt/vcpkg-ci/installed/x64-linux/lib/libsndfile.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libFLAC.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libvorbis.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libvorbisfile.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libvorbisenc.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libogg.a;/mnt/vcpkg-ci/installed/x64-linux/lib/libopus.a;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libtiff.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libtiffd.a>;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/liblzma.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/liblzmad.a>;/mnt/vcpkg-ci/installed/x64-linux/lib/libzstd.a;\$<\$<NOT:\$<CONFIG:DEBUG>>:/mnt/vcpkg-ci/installed/x64-linux/lib/libz.a>;\$<\$<CONFIG:DEBUG>:/mnt/vcpkg-ci/installed/x64-linux/debug/lib/libz.a>;/mnt/vcpkg-ci/installed/x64-linux/lib/libgif.a"

Windows (x64-windows):
freealut/stdout-x64-windows.log:  Unguarded release path /lib/ path at [>>>]:
freealut/stdout-x64-windows.log:       INTERFACE_LINK_LIBRARIES "[>>>]D:/installed/x64-windows/lib/OpenAL32.lib"
lapack-reference/stdout-x64-windows.log:  Unguarded release path /lib/ path at [>>>]:
lapack-reference/stdout-x64-windows.log:     set(LAPACK_blas_LIBRARIES "[>>>]D:/installed/x64-windows/lib/openblas.lib")
leptonica/stdout-x64-windows.log:  Unguarded release path /lib/ path at [>>>]:
leptonica/stdout-x64-windows.log:       INTERFACE_LINK_LIBRARIES "[>>>]D:/installed/x64-windows/lib/gif.lib;\$<\$<NOT:\$<CONFIG:DEBUG>>:D:/installed/x64-windows/lib/jpeg.lib>;\$<\$<CONFIG:DEBUG>:D:/installed/x64-windows/debug/lib/jpeg.lib>;\$<\$<NOT:\$<CONFIG:DEBUG>>:D:/installed/x64-windows/lib/libpng16.lib>;\$<\$<CONFIG:DEBUG>:D:/installed/x64-windows/debug/lib/libpng16d.lib>;\$<\$<NOT:\$<CONFIG:DEBUG>>:D:/installed/x64-windows/lib/zlib.lib>;\$<\$<CONFIG:DEBUG>:D:/installed/x64-windows/debug/lib/zlibd.lib>;\$<\$<NOT:\$<CONFIG:DEBUG>>:D:/installed/x64-windows/lib/tiff.lib>;\$<\$<CONFIG:DEBUG>:D:/installed/x64-windows/debug/lib/tiffd.lib>;WebP::webp;WebP::libwebpmux;\$<\$<NOT:\$<CONFIG:DEBUG>>:D:/installed/x64-windows/lib/zlib.lib>;\$<\$<CONFIG:DEBUG>:D:/installed/x64-windows/debug/lib/zlibd.lib>"
libdjinterop/stdout-x64-windows.log:  Unguarded release path /lib/ path at [>>>]:
libdjinterop/stdout-x64-windows.log:       INTERFACE_LINK_LIBRARIES "\$<\$<NOT:\$<CONFIG:DEBUG>>:D:/installed/x64-windows/lib/zlib.lib>;\$<\$<CONFIG:DEBUG>:D:/installed/x64-windows/debug/lib/zlibd.lib>;[>>>]D:/installed/x64-windows/lib/sqlite3.lib"
libftdi1/stdout-x64-windows.log:  Unguarded release path /lib/ path at [>>>]:
libftdi1/stdout-x64-windows.log:     set ( LIBFTDI_LIBRARIES    "ftdi1;[>>>]D:/installed/x64-windows/lib/libusb-1.0.lib" )
libwebsockets/stdout-x64-windows.log:  Unguarded release path /lib/ path at [>>>]:
libwebsockets/stdout-x64-windows.log:       INTERFACE_LINK_LIBRARIES "[>>>]D:/installed/x64-windows/lib/libssl.lib;D:/installed/x64-windows/lib/libcrypto.lib;\$<\$<NOT:\$<CONFIG:DEBUG>>:D:/installed/x64-windows/lib/pthreadVC3.lib>;\$<\$<CONFIG:DEBUG>:D:/installed/x64-windows/debug/lib/pthreadVC3d.lib>;\$<\$<NOT:\$<CONFIG:DEBUG>>:D:/installed/x64-windows/lib/pthreadVC3.lib>;\$<\$<CONFIG:DEBUG>:D:/installed/x64-windows/debug/lib/pthreadVC3d.lib>;ws2_32.lib;userenv.lib;psapi.lib;iphlpapi.lib;crypt32.lib;\$<\$<NOT:\$<CONFIG:DEBUG>>:D:/installed/x64-windows/lib/zlib.lib>;\$<\$<CONFIG:DEBUG>:D:/installed/x64-windows/debug/lib/zlibd.lib>;D:/installed/x64-windows/lib/libuv.lib"
open62541/stdout-x64-windows.log:  Unguarded release path /lib/ path at [>>>]:
open62541/stdout-x64-windows.log:       INTERFACE_LINK_LIBRARIES "[>>>]D:/installed/x64-windows/lib/libssl.lib;D:/installed/x64-windows/lib/libcrypto.lib;ws2_32;iphlpapi"
opencascade/stdout-x64-windows.log:  Unguarded release path /lib/ path at [>>>]:
opencascade/stdout-x64-windows.log:       INTERFACE_LINK_LIBRARIES "TKernel;TKMath;user32.lib;advapi32.lib;advapi32.lib;user32.lib;windowscodecs;[>>>]D:/installed/x64-windows/lib/freetype.lib;winmm.lib"

Maybe it should be merged with VCPKG_CMAKE_CONFIG_NO_LIB_PATH_CHECK initially enabled if unset. So the check would be warning immediately. Later we can remove the initial VCPKG_CMAKE_CONFIG_NO_LIB_PATH_CHECK setting.

I surprised that only so few cases of wrong INTERFACE_LINK_LIBRARIES exists.

I surprised that only so few cases of wrong INTERFACE_LINK_LIBRARIES exists.

The check is only in vcpg-cmake-config at this point. Ports using the old config fixup are not covered.
Optional features are not covered.
As far as the problem occurs in a target's property,

it is not found (but may have effects) in ports which consume the target,
depending ports are skipped in CI ("cascade").

Suggestion:

Extend to legacy fixup.
Turn the errors into warning unless building in editable mode (making the PR mergeable)
Collect the warnings from all ports during CI, and create AZP/GH warning(s).

One frequent pattern:
The openssl wrapper doesn't properly setup release+debug in ${OPENSSL_SSL_LIBRARY} ${OPENSSL_CRYPTO_LIBRARY}.

Extend to legacy fixup.
Turn the errors into warning ~unless building in editable mode (making the PR mergeable)~
Collect the warnings from all ports during CI, and create AZP/GH warning(s).

Implemented. This change now rebuilds the world, installing app. ~1310 ports on x64-windows.

Any progress in this PR? I'd like this.

I was hesitating to remove draft state while it is not ready for merge. But is ready for review.

Okay, I need some professional advice.

Can you please merge to master?

Merged master.

Any PR that contributes to the port's robustness is supported.

Now that this is reviewed, #21763 could probably be bundled with this one, even if they touch different ports.

Now that this is reviewed, #21763 could probably be bundled with this one, even if they touch different ports.

I think we'd better to merge that changes in the PR which modified vcpkg-cmake.

AFAICT #22546 should be the the fix for most of the warnings which are generated here.

I don't understand why this is done in CMake, and not in the C++ post-build stuff. Can you explain why?

I don't understand why this is done in CMake, and not in the C++ post-build stuff. Can you explain why?

Because that's how I did it.
And because it unfolds its effect right here in building the broken universe.
(It is not even clear to me if you refer to the vcpkg-cmake-config changes (which seem to be extremly close the spot which introduces the issue, or if you refer to the AZP markup.)

@dg0yt I mean, why do we not check for unguarded release libs in the same place we have our other checks (i.e., for absolute paths in libraries); having it in the CMake makes it more difficult to test and such.

<off-topic>Why don't we stop mixing release and debug variants in the same installed tree?</off-topic>
a) I know close to nothing about "our other checks". I don't think there is good documentation.
b) This PR started as a probe into the feasibility of dealing with this issue, and it turned out to be sufficient. If we find someone who implements the same in C++, fine for me.
c) I hooked into a spot where the files of interest are already read (and indeed the spot were vcpkg causes the problem,  #22546).
d) Having it in the CMake scripts makes it quite easy to test IMO. In vcpkg CI. Locally with vpckg install. (Note: you don't need to rebuild your world, your can just swap the installed cmake script as you can swap the vcpkg tool blob.
I do understand that we might wish to

have an option to turn the test off,
apply the test to files/ports which are not handled by vcpkg-cmake-config (e.g. because handled by the legacy functions)
benefit from better performance in C++.

I also don't mind to put this on hold until #22546 is accepted. If that PR resolves most of these port bug, this PR is much less important.

So I think we can continue this PR now?

So I think we can continue this PR now?

Considering dg0yt appears unwilling to implement these changes in C++ and we appear to be unwilling to add additional tests that occur only in CMake world I think this is appropriate to leave as draft until one or both of those changes.

Ping @dg0yt for response. Is work still being done for this PR?

"to leave as draft", https://github.com/microsoft/vcpkg/pull/21415#issuecomment-1049191280

This check only works when there are absolute path in the cmake config file?

This check only works when there are absolute path in the cmake config file?

Yes, absolute paths in the main config file.

I surprised that only so few cases of wrong INTERFACE_LINK_LIBRARIES exists.

One year later: 242 hits in 33 packages for x64-windows.

False positives:

[ ] \$<\$<NOT:\$<CONFIG:DEBUG>>:-L[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/pkgconfig/../../lib>
(libavif:x64-windows)
[ ] INTERFACE_INCLUDE_DIRECTORIES "[>>>]/mnt/vcpkg-ci/installed/x64-linux/lib/pkgconfig/../../include;${_IMPORT_PREFIX}/include"
(wolfmgtt:x64-windows)

Closing this PR as there has not been activity in over 4 months. Please feel free to reopen it, or another PR, should you wish to continue this.

Please feel free to reopen it

Unprivileged contributors cannot reopen their own PRs here.


Auto-disconnect

Right now users need to explicitly call await prisma.disconnect() at the end of their program otherwise the running Node process won't terminate.
Ideally the Prisma Client (or more correctly: the used Prisma Query Engine) should automatically disconnect when the Node process is trying to terminate. This removes a lot of friction points and simplifies the usage of Prisma Client - especially when getting started - since users don't need to call await prisma.disconnect() explicitly anymore.

Hi, could you speed up this feature? I'm have used Prisma for 3 months in the production and never find out, sometimes some scripts spawn `query-engine-debin-openssl'.

and it takes all my server memory. I knew my code is the problem, but not always you can find out why.

@meotimdihia This will be soon resolved via https://github.com/prisma/prisma/issues/4911 as then node can directly call rust function instead of spawning a binary process. It is close to completion and being released in preview so stay tuned.

Hai,
So for the current version should I call $disconnect() explicitly? The document says otherwise, am I missing something?

Thank you.

@rvlewerissa We do close connection on receiving termination signals: https://github.com/prisma/prisma/blob/d3e28bf2ec47e645591f743f0b58749b4572811f/src/packages/engine-core/src/NodeEngine.ts#L1223. If your code is doing sommething else, then yes, call it explicitly


assert_eq success message is uninformative

See the comments on gotoc-assert-eq/main.rs

Example:
$ cat test.rs
fn main() {
    let x = 1;
    let y = 2;
    assert_eq!(x + 1, y);
    assert_eq!(x, y); //Expected failure
    assert_ne!(x, y);
}

$ kani test.rs
<snip>
** Results:
<snip>
/home/ubuntu/git/kani/tests/expected/assert-eq/test.rs function main
[main.assertion.1] line 4 attempt to compute `move _6 + const 1_i32`, which would overflow: SUCCESS
[main.assertion.2] line 4 a panicking function core::panicking::assert_failed is invoked: SUCCESS
[main.assertion.3] line 5 a panicking function core::panicking::assert_failed is invoked: FAILURE
[main.assertion.4] line 6 a panicking function core::panicking::assert_failed is invoked: SUCCESS
<snip>

** 1 of 50 failed (2 iterations)
VERIFICATION FAILED


Cannot create docker access object: Connect to localhost:2375 [localhost/<IP_ADDRESS>, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect

Description
I am beginner to fabric8, trying to build an image for spring-boot app.
Getting error : cannot create docker access object: trying from windows 10,
Info
[INFO] --- fabric8-maven-plugin:4.3.0:build (default) @ lb-server ---
[WARNING] F8: Cannot access cluster for detecting mode: connect timed out
[INFO] F8: Running in Kubernetes mode
[INFO] F8: Building Container image with Docker in Kubernetes mode
[WARNING] F8: Cannot access cluster for detecting mode: connect timed out
[WARNING] F8: Cannot access cluster for detecting mode: connect timed out
[ERROR] F8: Cannot create docker access object  [Connect to localhost:2375 [localhost/<IP_ADDRESS>, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 47.450 s
[INFO] Finished at: 2019-10-20T01:10:05+05:30
[INFO] Final Memory: 49M/411M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:4.3.0:build (default) on project lb-server: Cannot create docker access object: Connect to localhost:2375 [localhost/<IP_ADDRESS>, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.

f-m-p version : 4.3.0
Maven version (mvn -v) :3

Kubernetes / OpenShift setup and version :

If it's a bug, how to reproduce :

io.fabric8
fabric8-maven-plugin
4.3.0

user/demo

.
@

true
${docker.host.address}

                  <!--<!–</createOptions>–>-->
              <!--</machine>-->
          </configuration>
          <executions>
              <execution>
                  <goals>
                      <!--<goal>resource</goal>-->
                      <goal>help</goal>
                      <goal>build</goal>
                  </goals>
              </execution>
          </executions>
      </plugin>

<docker.host.address>tcp://localhost:2375</docker.host.address>
mvn clean install

If it's a feature request, what is your use case :
Sample project : [GitHub Clone URL]

Are sure your docker deamon is accessible?

Are you able to use it with basic docker commands? Like, what does systemctl status docker shows? Ideally plugins detects it on its own for most cases

i was in an assumption that there is  embedded docker and that comes to live during the build.

No, it needs docker deamon. If you're using minikube for building this. You can maybe expose your docker deamon. Not sure that works on windows or not, but I usually do (eval $(minikube docker-env)

There is one more way of building without docker deamon and pushing directly to your registry. But you need to add your registry credentials of docker hub in it.
mvn fabric8:build -Dfabric8.build.jib=true

It would build it offline and push it to your dockerhub

let me explain what i am trying to build: i need a plugin that can use embedded docker to create an image. My goal is to run this from any machine. I dont want to ask people to keep installing docker to deploy code to remote cloud. Problem is jib is only useful for java image, can I use this for all types of docker image

Even above command fails with below error.
[INFO] --- fabric8-maven-plugin:4.3.0:build (default-cli) @ lb-server ---
[WARNING] F8: Cannot access cluster for detecting mode: connect timed out
[INFO] F8: Running in Kubernetes mode
[INFO] F8: Building Container image with JIB(Java Image Builder) in Kubernetes mode
[WARNING] F8: Cannot access cluster for detecting mode: connect timed out
[WARNING] F8: Cannot access cluster for detecting mode: connect timed out
[WARNING] F8: Cannot access cluster for detecting mode: connect timed out
[WARNING] F8: Cannot access cluster for detecting mode: connect timed out
[INFO] F8: Image tagging successfull!
[ERROR] F8: Failed to execute the build: java.lang.UnsupportedOperationException
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  54.857 s
[INFO] Finished at: 2019-10-20T01:28:33+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:4.3.0:build (default-cli) on project lb-server: Failed to execute the build: java.lang.UnsupportedOperationException -> [Help 1]

Fabric8 Maven Plugin is also specific to Java specific container tooling. Any container image is supposed to run on any machine, and it's docker(or any other container orchestration tool) that does it. You need docker/kubernetes on some machine to be able to run your image.

You need to add some configuration also, let me give you an example:
      <plugin>
        <groupId>io.fabric8</groupId>
        <artifactId>fabric8-maven-plugin</artifactId>
        <version>4.3.1</version>
        <configuration>
          <images>
            <image>
              <!-- Add your dockerhub user name here -->
              <name>${YOUR_DOCKER_HUB_USERNAME}/helloworld-java:${project.version}</name>
              <alias>hello-world</alias>
              <build>
                <from>openjdk:latest</from>
                <assembly>
                  <descriptorRef>artifact</descriptorRef>
                </assembly>
                <cmd>java -jar maven/${project.name}-${project.version}.jar</cmd>
              </build>
              <run>
                <wait>
                  <log>Hello World!</log>
                </wait>
              </run>
            </image>
          </images>
          <authConfig>
            <username>${YOUR_DOCKER_HUB_USERNAME}</username>
            <password>${YOUR_DOCKER_HUB_PASSWORD}</password>
          </authConfig>
        </configuration>
      </plugin>

i have a open(without auth) minikube running on local. how should i deploy to that?

oh, then you should be able to do it with plain mvn fabric8:build

just make sure your have docker exposed in that session.

I have no docker installed, I believe fabric8 plugin will offer an embedded docker. My intention is create a docker image using a maven plugin, and then deploy it to any k8s of my choice. so that this can work as utility to deploy any java app from anywhere. We can build anything anywhere and deploy to anywhere.

Docker deamon is inside the minikube vm

Ideally people build image using docker deamon, push it to some container image registry, and then pull it from any docker/kubernetes instance they are using

This jib option offers to build without using docker deamon and pushing directory to hub.docker.com

yes, i just want to skip push part and want to use inflight image. because this utility i will be using for POCs.

This jib option offers to build without using docker deamon and pushing directory to hub.docker.com

yes, that means i need a auth for hub.docker.com

oh, I see. If you're using minikube, you should be able to build docker image(since docker deamon is inside minikube). and then you can do whatever your use case supports. For porting it to other machines you can simply make a tarball of your image and transfer it by other methods.

@mohapsub : bdw, if you haven't configured auth jib mode is going to fail while pushing, but it also builds tarball of your image. You can then load that tarball into whatever machine you need.

if i really dont need to push an image, is there a way i simply can create image and deploy to k8s cluster of my choice, without downloading docker? s2i?

Sorry, I might not have understood your use case. I thought you were using minikube for deploying your kubenetes application. Am I right?

basically i want
step1# create a image without downloading docker and dont push
step2# deploy to any k8s host based on input.
two discrete steps.

if i really dont need to push an image, is there a way i simply can create image and deploy to k8s cluster of my choice, without downloading docker? s2i?
Yes, that's possible if you have minikube. The image would be stored in docker deamon which is in minikube.
i can store image in host(where the code is running) machine temporarily and deploy to any k8s cluster?
Yes, image would be stored in docker deamon. But how would you be able to deploy it to any k8s cluster? It would only be accessible in your current minikube cluster(unless you transfer it's tarball somehow or maybe push to some public/private container image registry)

basically i want
step1# create a image without downloading docker and dont push
yes, we support this
step2# deploy to any k8s host based on input.
Sorry, but I couldn't understand this use case.
two discrete steps.

"Sorry, but I couldn't understand this use case."
deploy temporary image created in step#1 to any k8s cluster of my choice

okay, you can deploy that also. So we have this workflow currently
mvn fabric8:build -> Build Image
mvn fabric8:resource fabric8:deploy -> Deploy to your cluster

"mvn fabric8:build -> Build Image"
this step is failing, i was thinking fabric8 has a embedded docker, but it expects me run mine.
[ERROR] F8: Cannot create docker access object [Connect to localhost:2375 [localhost/<IP_ADDRESS>, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect]

Please perform this step and see if it helps:

it may work, but does fabric8 have a embedded docker daemon, so that i dont have to point external apps? Are you aware any other plugins that has embedded docker daemon?

No, fabric8 doesn't have this. daemon's are system level processes that are running continously in background, I don't think having them inside plugins make any sense

we used to think along similar lines, till spring-boot offered a embedded server :) it empowers developer, i can build and ship an image anywhere.

wait, what? which spring-boot are you talking about? https://spring.io/? I haven't heard of that including embedded server.

i considered tomcat as a server, couldhave been more precise

@mohapsub: Could you please share logs with -X option?

I am worried now if I have setup docker on k8s properly.
can you help me k8s deployment descriptor for docker, basically it should expose remote docker rest api? i was tryin to access remote docker using REST API.

Hi @mohapsub
I'm currently using remote docker(s) environment from my Windows 10 Home machine (where docker is not supported natively)
In order to be able to use the Docker client with (for example) Minikube's Docker daemon, you need to setup a couple of environment variables (just like @rohanKanojia mentioned).
Run the following command to check the values applicable for the Docker environment variables:
minikube docker-env

Now open your user system environment variable configuration and add those values:

From now on, whenever you create a new process, you'll be able to run any docker command successfully (docker ps, docker images, etc.)
FMP will detect these values too.

thanks my problem resolved long back, i was not very active. Thanks for posting this


google_app_id not in String.xml by default, this is not explained

I spent quite some time trying to figure out why google_app_id was not available when trying to log to it, and how to make it so. With no prior Android experience this was rather confusing.
Please could you put a note into the tutorial to explain how to add it for use for those that don't inherently already know.

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

ID: 8d9bfb2a-2e5d-d505-337f-919251a85de3
Version Independent ID: 695bff64-ae87-8c0f-5616-20b67893fdf0
Content: Remote Notifications with Firebase Cloud Messaging - Xamarin
Content Source: docs/android/data-cloud/google-messaging/remote-notifications-with-fcm.md
Product: xamarin
GitHub Login: @mgmclemore
Microsoft Alias: mamcle

Were you going to share that?  I'd like to know, too.  :)

Thanks for the feedback, this will be taken into considering for the next update to this doc.


Can't suppress BOOST_TEST_MESSAGE output without suppressing TEST SUITE level

My tests use a lot of BOOST_TEST_MESSAGE calls to generate test trace. Unfortunately, this completely bloats XML output I use to integrate boost and Jenkins, since every message is appended to the xml file. If I reduce the log level, then there is no information about individual test cases in the XML file.
I should be able to use boost test messages for tracing and still obtain a compact test summary in xml when needed.
Adding every message to xml output is in most cases useless for me.
Possible fix:
Introduce BOOST_TRACE_MESSAGE or move MESSAGE level a few levels up.

If I understand your request, the final XML does not contain the test hierarchy when you use the log level above message, in order to discard the BOOST_TEST_MESSAGE content. Is that correct?
I am not fond of introducing a new switch or functionality. However, have you considered JUNIT output of Boost.Test? Jenkins has great support for that and that should make things work out of the box.

We're using junit output. But with millions of messages in the output, the output becomes too heavy for jenkins to handle.

Thank you for your answer. I still do not understand the problem then, you said

If I reduce the log level, then there is no information about individual test cases in the XML file.

With JUNIT output, you should be able to raise the level to warning, then all messages should be discarded. Would you please tell me what is not working with this approach, possibly with screenshots or XML outputs of what you want to keep in your logs and what you don't want.

Kind reminder @kostja

Will get back to you within a few days, sorry.


[WIP] Optional GPU

Linux build can now produce a non-GPU .so. Right now this part is working, but the configuration needs love. (basically, all the linux configuration needs love)
This must be merged first: https://github.com/mono/skia/pull/49
Related to https://github.com/mono/SkiaSharp/issues/90

I'm pretty sure that it's possible to keep GPU support without referencing libGL/libGLU/libX11 by exposing GrGLAssemble*Interface: https://github.com/mono/skia/blob/xamarin-mobile-bindings/include/gpu/gl/GrGLAssembleInterface.h#L17

That way skia will obtain references to OpenGL functions using user-provided glGetProcAddress

BTW, GLX won't be present in "pure" Wayland/Mir environment, they use EGL instead.

@kekekeks Thanks for the work, I will get it all merged. BTW, I already expose the GRGLAssemble*Interface members on the GRGlInterface type in SkiaSharp - that is actually how I do the ANGLE bits on UWP.
Doing it vial assemble is better than having no support at all. Good point.


add export_results()

WIP
#251

@andreagubellini hi, what's the status? If there is review or update from my side needed let me know - I could forgot about it in meantime :(

@andreagubellini hi, what's the status? If there is review or update from my side needed let me know - I could forgot about it in meantime :(

Hey!
I've finished to implement all the requested changes, now we just need a method (or a run() refactor) to return the output. I believe you said you would do that, do you want me to take a look or?

@andreagubellini Ok now I remember the whole context. Since I'm doing some updates in Robocop over the weekend I will also take care of that and I will let you know when its done

Codecov Report

Merging #252 (9d1007e) into master (7325c3a) will decrease coverage by 0.71%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #252      +/-   ##
==========================================
- Coverage   98.97%   98.25%   -0.72%
==========================================
  Files          33       34       +1
  Lines        2152     2183      +31
==========================================
+ Hits         2130     2145      +15
- Misses         22       38      +16

Impacted Files
Coverage Δ

tests/atest/test_rule.py
100.00% <ø> (ø)

robocop/__init__.py
100.00% <100.00%> (ø)

robocop/reports.py
100.00% <100.00%> (ø)

robocop/rules.py
100.00% <100.00%> (ø)

robocop/run.py
97.20% <100.00%> (+0.59%)
:arrow_up:

tests/atest/conftest.py
100.00% <100.00%> (ø)

tests/e2e/test_e2e.py
100.00% <100.00%> (ø)

tests/utest/test_reports.py
100.00% <100.00%> (ø)

robocop/checkers/misc.py
91.52% <0.00%> (-8.48%)
:arrow_down:

robocop/checkers/comments.py
95.65% <0.00%> (-4.35%)
:arrow_down:

... and 11 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 7325c3a...9d1007e. Read the comment docs.

I've decided to update some of the core code to support this feature. I've created JsonReport report class which is accumulating issues in json format (but only for non cli runs). And of course I've added tests.
After this change if you want to use Robocop in python code you can:
        import robocop
        from robocop.config import Config

        config = Config()
        config.include = {'1003'}
        config.paths = ['tests\\atest\\rules\\section-out-of-order']

        robocop_runner = robocop.Robocop(config=config)
        issues = robocop_runner.run()
        print(issues)

run() returns list of issues in json format:
[{'col': 0,
  'desc': 'Invalid number of empty lines between sections (0/2)',
  'line': 17,
  'rule_id': '1003',
  'rule_name': 'empty-lines-between-sections',
  'severity': 'W',
  'source': 'C:\\Users\\barte\\Desktop\\repo\\forks\\robotframework-robocop\\tests\\atest\\rules\\section-out-of-order\\test.robot'},
 {'col': 0,
  'desc': 'Invalid number of empty lines between sections (1/2)',
  'line': 20,
  'rule_id': '1003',
  'rule_name': 'empty-lines-between-sections',
  'severity': 'W',
  'source': 'C:\\Users\\barte\\Desktop\\repo\\forks\\robotframework-robocop\\tests\\atest\\rules\\section-out-of-order\\test.robot'}]

@mnojek  @andreagubellini

Looks fine to me!

Closes #169


⚠ Bofrost.lu has degraded performance

In 88378d4, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1468 ms

Resolved: Bofrost.lu performance has improved in 45d0298 after 22 minutes.


Adding a ghost theme...

I'm wondering how you implement a Ghost theme in hubpress. I chose a theme: "Casper", download it, unzip it and then I put it in the folder: /yourblog.github.io/themes/Cactus/. Next I tried to apply it from the hubpress admin panel but It wasn't replacing my current theme which is casper with cactus, I looked in the console and saw a 404 error at theme.json, I created a theme.json file for the new theme (cactus).Next I saw again a 404 error to partials/loop.hbs so I removed it. Now I am at this stage:
/yourblog.io/themes/Casper/theme.json
{
  "files": {
    "comments": "partials/comments.hbs",
    "excerpts": "partials/excerpts.hbs",
    "index-meta": "partials/index-meta.hbs",
    "post-meta": "partials/post-meta.hbs",
    "share": "partials/share.hbs",
    "default": "default.hbs",
    "index": "index.hbs",
    "author": "author.hbs",
    "post": "post.hbs",
    "page": "page.hbs",
    "tag": "tag.hbs"
  },
  "version":"1.0.0"
}
}

But hubpress isn't applying it cause:

Can someone translate to me what this error means?

"Missing helper: 'contentFor'

HubPress is not full compatible yet :cry:
In your default.hbs, you can comment or remove :
{{{block "meta"}}}

Nope, still not working, same error. It's ok that's not fully compatible with ghost themes, but what is error contentFor mean.

contentFor is an helper exposed by express-hbs see http://dev.ghost.org/ghost-theme-tips-defining-content-blocks/
And contentFor is not implemented in HubPress, that's why you have this error.

Ok, i find a way, but you will loose some meta tag. If SEO is not really important for you, it should not be a problem.

Remove index-meta and post-meta from the theme.json
Edit post.hbs and page.hbs, comment or remove >post-meta

Relog in hubpress, it should work

Is it ok for you @taosx? can i close ?

Yes

added this edge case to https://hubpress.gitbooks.io/hubpress-knowledgebase/content/theme/develop_themes.html


fix(man): Add correct date and version to manpage

The previous approach relied on manually updating the version and date
using a Makefile
This approach dynamically gathers the correct version from git and uses the
date of the latest commit in the branch

Fixed merge conflict!


elastalert-test-rule does not exit with a proper error code when there is a ConnectionError on Linux

Hi there,
First, thanks for the good work, ElastAlert is really a great piece of software and I really like the fact that it carries a tool like elastalert-test-rule for testing purposes, which turns to be particularly useful when using it as part of a CI process.
However, it's a bit of a pain since the wrapper (of the underlying Python script) elastalert-test-rule, does not actually return an error code different from 0 when there are for example some actual errors like say ConnectionErrors.
Typically here is an example of a rule that fails because the es_host is not properly set:

Traceback (most recent call last):
  File "/opt/elastalert/.env/lib/python2.7/site-packages/elasticsearch/connection/http_requests.py", line 56, in perform_request
    response = self.session.request(method, url, data=body, timeout=timeout or self.timeout)
  File "/opt/elastalert/.env/lib/python2.7/site-packages/requests/sessions.py", line 461, in request
    resp = self.send(prep, **send_kwargs)
  File "/opt/elastalert/.env/lib/python2.7/site-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "/opt/elastalert/.env/lib/python2.7/site-packages/requests/adapters.py", line 415, in send
    raise ConnectionError(err, request=request)
ConnectionError: ('Connection aborted.', gaierror(-2, 'Name or service not known'))
ERROR:root:Error running query: ConnectionError(('Connection aborted.', gaierror(-2, 'Name or service not known'))) caused by: ConnectionError(('Connection aborted.', gaierror(-2, 'Name or service not known')))
elastalert_error - {'message': "Error running query: ConnectionError(('Connection aborted.', gaierror(-2, 'Name or service not known'))) caused by: ConnectionError(('Connection aborted.', gaierror(-2, 'Name or service not known')))", 'traceback': ['Traceback (most recent call last):', '  File "/opt/elastalert/.env/lib/python2.7/site-packages/elastalert-0.1.3-py2.7.egg/elastalert/elastalert.py", line 250, in get_hits', "    res = self.current_es.search(scroll=scroll_keepalive, index=index, size=rule['max_query_size'], body=query, ignore_unavailable=True, **extra_args)", '  File "/opt/elastalert/.env/lib/python2.7/site-packages/elasticsearch/client/utils.py", line 68, in _wrapped', '    return func(*args, params=params, **kwargs)', '  File "/opt/elastalert/.env/lib/python2.7/site-packages/elasticsearch/client/__init__.py", line 498, in search', '    params=params, body=body)', '  File "/opt/elastalert/.env/lib/python2.7/site-packages/elasticsearch/transport.py", line 301, in perform_request', '    status, headers, data = connection.perform_request(method, url, params, body, ignore=ignore, timeout=timeout)', '  File "/opt/elastalert/.env/lib/python2.7/site-packages/elasticsearch/connection/http_requests.py", line 67, in perform_request', "    raise ConnectionError('N/A', str(e), e)", "ConnectionError: ConnectionError(('Connection aborted.', gaierror(-2, 'Name or service not known'))) caused by: ConnectionError(('Connection aborted.', gaierror(-2, 'Name or service not known')))"], 'data': {'rule': 'my issues'}}

Imho this should return something explicit to the caller (e.g. bash) but turns out nope, we just get 0 as (non) error code.
I double checked the documentation:

https://elastalert.readthedocs.io/en/latest/running_elastalert.html#testing-your-rule)
https://elastalert.readthedocs.io/en/latest/ruletypes.html#testing

But it seems there is nothing to enforce that there should be something stopping the test when there is something wrong.
I think it should be the responsibility of the wrapper (i.e. ownership) to return that something went wrong instead letting me grep or use regular expressions on the output to determine if any errors have been raised.
Is there a proper workaround for that? Grepping it's definitely not errorproof and lacks of clarity.
I was thinking about running the actual underlying Python wrapped with a try / catch clause but not sure this is going to be any better. I am not against writing my own tooling for that purpose, but would like to know whether there is already something out there that could me help out to achieve what I am aiming at.

Hm, this is a good point. The underlying elastalert code catches most exceptions so errors will generally show up as the elastalert_error - {'message': ....} line that you've shared.
I'll probably add something like
@@ -256,8 +256,13 @@ class MockElastAlerter(object):

             if mock_writeback.call_count:
                 print("\nWould have written the following documents to writeback index (default is elastalert_status):\n")
+                errors = False
                 for call in mock_writeback.call_args_list:
                     print("%s - %s\n" % (call[0][0], call[0][1]))
+                    if call[0][0] == 'elastalert_error':
+                        errors = True
+                if errors:
+                    exit(1)

which is effectively the same as your grep method.
There's probably a couple other places where "errors" can occur without changing the exit code and without emitting an elastalert_error document, so this is definitely not a comprehensive fix.

@Qmando thanks that's also what I figured out. Actually I am wondering if I just remove all the return None and raise the related exception in base_path\elastalert\test_rule.py it should also be fine, right?

Yeah those changes would probably be fine too. I'm willing to merge this if you open a pull request.

@Qmando ok then will work on that tonight and create a pull request
I am thinking about something like elastalert-test-rule --error-stop
Just require a bit of change in the parser of run_rule_test  function and instead of return None to raise the error that is supposedly caught.
By the way, if you have a better terminology for the argument, just let me know.

@Qmando just created the pull-request, created something quite simple, a bit stricter than what you suggested, maybe a bit too dumb.
Pull request: https://github.com/Yelp/elastalert/pull/1153
May want to add unit tests tho ~~
CI: https://travis-ci.org/Yelp/elastalert/builds/240241603?utm_source=github_status&utm_medium=notification


Time series graph showing today's data & date with description "Yesterday"

Describe the bug
Time series chart under spread trends section showing today's date with label "Yesterday" under it.
To Reproduce
Steps to reproduce the behavior:

Go to the website
Scroll down to Spread Trends section
Today's data & date is displayed on the chart but with the label "Yesterday"

Expected behavior
Two possible solutions

Show data till yesterday(included) as before.
OR
Remove "Yesterday" label under today's date

Screenshots

Desktop (please complete the following information):
All browsers & desktops.
Smartphone (please complete the following information):
All mobile devices.

Seems fixed now.

Yes. Just checked! Working fine now

Closing, although not sure what happened.


using count value in for loop

hi,
I am able to get the count value with the following:
	element.all(by.options('type as type for type in types')).then(function(elems){
		return elems.length;
	})
	.then(function(count){
		cnt = count;
	});

then later in the code I want to use cnt in a for loop where I also use closure:
for(var x = 1;x < cnt; x++){
	search_options(x);
}

function test(y){
	console.log('input'+y);
}

function search_options(input){
	it('tess', function(){
		test(input);

	});
}

the problem is that the for does not execute.
Any tips or guidance is appreciated. Thanks

HI There,
If "option" is the tagName please use element.all(by.tagname("") ), or element.all( by.css("")) . Please recheck the locator, as per my knowledge there is no locator with 'by.options'. For your reference to please look at this doc to take efficient locators in protractor.
https://github.com/angular/protractor/blob/master/docs/locators.md
Also, In the future, please direct requests like this to StackOverflow or Gitter.
From the the getting help section of the README:
Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)
Thanks!

Hi there!
This is due to the asynchronous nature of JavaScript. You'll need to ensure that you are using cnt in a scope that has access to the resolved value.
In addition, your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks!


Fix alpha colors

Motivation
During the color sync (the PR) with Figma, some colors in an 8-digit hex format were incorrectly converted from Figma.
For example:
--neutral-50-a15 should be #ffffff26 instead of #ffffff15
(15% opacity → (0.15 × 255) = 38.25 → 38 → Hex 26)
Changes

Fix the alpha part of newly added 8-digit hex colors.

Tests
All the changes have been reviewed with the designers.
Affected components
The most noticeable change is in the Backdrop component. It has become much darker.
link
Backdrop  and busy screen background

Icon backgrounds
Voting confirmatio Yes/No icon backgrounds

Transaction icons

Disabled card

Menu button backgrounds (github link, total value etc)

Status tags background become less transparent

Tooltip border
Not notiecable.

The backdrop in the first screenshot looks completely opaque to me now. Is that really what we want?

The backdrop in the first screenshot looks completely opaque to me now. Is that really what we want?

@dskloetd, it was 80% before, but probably because the new dark theme is darker, it appears even darker now. The issue has been addressed in another PR. Thank you for the feedback.


Geoblocking design

Description
Changes proposed in this pull request:

...

Pre-Merge Checklist

[ ] As a PR reviewer, verify code coverage and evaluate if it is acceptable.

Related issues

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: kolodziejczak:x: mluk-sapYou have signed the CLA already but the status is still pending? Let us recheck it.

It has been decided to move it to the API Gateway module, so closing this PR


Add suport to mysql as default session store

https://github.com/chill117/express-mysql-session

Done in https://github.com/wejs/we-core/commit/67a56f0c41b91523bc708f5797cf2f64c70ebbce


Added firewall.rules.hash metric

Added a FNV-1 hash of the firewall rules as a Prometheus value.

Closes issue #1005

Thanks for the PR! My primary concern is that there is no direct correlation back to the log line. I think this could be resolved in two ways.

Include the FNV hash in the log lines
Include the sha256 hash as a label

Ideally we would do both here but option 2 is more difficult so lets add the FNV hash to the log lines.

Thanks for the PR! My primary concern is that there is no direct correlation back to the log line. I think this could be resolved in two ways.

Include the FNV hash in the log lines
Include the sha256 hash as a label

Ideally we would do both here but option 2 is more difficult so lets add the FNV hash to the log lines.

Option 2 would also increase cardinality, creating a new timeseries every time that label changed, so including the FNV hash in the log is the way to go, for sure.  I'll make that happen.

This work for the logs?
Startup:
level=info msg="Firewall started" firewallHashes="SHA:8cdd862ba57eca683ac4fb32fcd8f727743df3ba0c92b267c3e9ca128e43be8d,FNV:-4874977699962996863"
after a reload:
level=info msg="New firewall has been installed" firewallHashes="SHA:3775881c4dfa7c63e3d343e747ad66b0ddf6a72fde1ce3b2eea43436175f101f,FNV:7449190936218615427" oldFirewallHashes="SHA:8cdd862ba57eca683ac4fb32fcd8f727743df3ba0c92b267c3e9ca128e43be8d,FNV:-4874977699962996863" rulesVersion=1

Anything needed here?

@britcey Thanks for your contribution!


By Python official announcement, Python 3.9 is not support Windows 7 sp1.

Prerequisites

[V ] Did you read FAQ section in readme.md?
[V ] Did you test with the latest releases or commit ?
[V ] Did you search for existing issues in Issues?

Description
[Description of the bug or feature]
By official announcement, Python 3.9 is not support Windows 7 sp1.
https://www.python.org/downloads/release/python-390/
When I run Pixivutil2 on Winsows7 sp1, first get "api-ms-win-core-path-l1-1-0.dll not found" and console shown "FATAL ERROR: Could not load python library."
Get the  "api-ms-win-core-path-l1-1-0.dll" from somewhere, re-run Pixivutil, it shows dump:
Python path configuration:
PYTHONHOME = (not set)
PYTHONPATH = (not set)
program name = 'D:\pixivutil20210702\PixivUtil2.exe'
isolated = 1
environment = 0
user site = 0
import site = 0
sys._base_executable = '\xc4C\ue7c0G\u0908\u0b0a\u0d0c\u0f0e\u1110\u1312\u1514
\u1716\u1918\u1b1a\u1d1c\u1f1e\u2120\u2322\u2524\u2726\u2928\u2b2a\u2d2c\u2f2e\u
3130\u3332\u3534\u3736\u3938\u3b3a\u3d3c\u3f3e\u4140\u4342\u4544\u4746\u4948\u4b
4a\u4d4c\u4f4e\u5150\u5352\u5554\u5756\u5958\u5b5a\u5d5c\u5f5e\u6160\u6362\u6564
\u6766\u6968\u6b6a\u6d6c\u6f6e\u7170\u7372\u7574\u7776\u7978\u7b7a\u7d7c\u7f7e\u
2080\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u20
20\u2020\u2020\ua1a0\ua3a2\ua5a4\ua7a6\ua9a8\uabaa\uadac\uafae\ub1b0\ub3b2\ub5b4
\ub7b6\ub9b8\ubbba\ubdbc\ubfbe\uc1c0\uc3c2\uc5c4\uc7c6\uc9c8\ucbca\ucdcc\ucfce\u
d1d0\ud3d2\ud5d4\ud7d6\ud9d8\U001069dc\udfde\u2020\u2020\u2020\u2020\u2020\u2020
\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\ufd20\ufffe'
sys.base_prefix = ''
sys.base_exec_prefix = ''
sys.platlibdir = 'lib'
sys.executable = '\xc4C\ue7c0G\u0908\u0b0a\u0d0c\u0f0e\u1110\u1312\u1514\u1716
\u1918\u1b1a\u1d1c\u1f1e\u2120\u2322\u2524\u2726\u2928\u2b2a\u2d2c\u2f2e\u3130\u
3332\u3534\u3736\u3938\u3b3a\u3d3c\u3f3e\u4140\u4342\u4544\u4746\u4948\u4b4a\u4d
4c\u4f4e\u5150\u5352\u5554\u5756\u5958\u5b5a\u5d5c\u5f5e\u6160\u6362\u6564\u6766
\u6968\u6b6a\u6d6c\u6f6e\u7170\u7372\u7574\u7776\u7978\u7b7a\u7d7c\u7f7e\u2080\u
2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u2020\u20
20\u2020\ua1a0\ua3a2\ua5a4\ua7a6\ua9a8\uabaa\uadac\uafae\ub1b0\ub3b2\ub5b4\ub7b6
\ub9b8\ubbba\ubdbc\ubfbe\uc1c0\uc3c2\uc5c4\uc7c6\uc9c8\ucbca\ucdcc\ucfce\ud1d0\u
d3d2\ud5d4\ud7d6\ud9d8\U001069dc\udfde\u2020\u2020\u2020\u2020\u2020\u2020\u2020
\u2020\u2020\u2020\u2020\u2020\u2020\u2020\ufd20\ufffe'
sys.prefix = ''
sys.exec_prefix = ''
sys.path = [
'D:\pixivutil20210702\library.zip',
]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the file
system encoding
Python runtime state: core initialized
Traceback (most recent call last):
File "", line 1353, in _path_importer_ca
che
KeyError: 'D:\pixivutil20210702\library.zip'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 92, in init
KeyError: 'D:\pixivutil20210702\library.zip'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1007, in _find_and_load
File "", line 982, in _find_and_load_unlocked
File "", line 925, in _find_spec
File "", line 1414, in find_spec
File "", line 1383, in _get_spec
File "", line 1355, in _path_importer_ca
che
File "", line 1331, in _path_hooks
File "", line 94, in init
File "", line 463, in _read_directory
File "", line 99, in _path_join
SystemError: Negative size passed to PyUnicode_New
Steps to Reproduce
Expected behavior: [What you expected to happen]
If there is a chance to support Windows 7...
Versions
V20210702

see #971

Thanks for your kindly comment. Sorry for bother you.

You still can run from source code using python 3.8.x for the latest version
I have compile win7 version in the release page https://github.com/Nandaka/PixivUtil2/releases/tag/v20210822


[0.4.0] Event Filtering in summary view - Signals

Have a workflow that has a bunch of signals:

Then I select "Signal" from the filter dropdown and nothing shows:

Fixed in #355!

@stevekinney could you set the fix version for these? I am looking at 0.5.0 and this isssue is not fixed, so reopening. Feel free to close if this fix is for 0.6.0 or some future one.

Recording (also shows the params not clearing when you filter) [0.5.0]
https://user-images.githubusercontent.com/119422/159080370-143a5c47-5fb5-43da-8424-b691378f6b09.mp4

this should be fixed in v0.6.0
outgoing signal:

incoming signal:

@feedmeapples ok thanks. i didnt know which release version to test against as issue was marked as closed


dial tcp <IP_ADDRESS>:443 timeout

Sometimes when running kubectl -f apply prometheus-deployment.yml , receiving error
Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "ebde4d5c55680e5db9de25b76ff4f28989be3de81a2a375d90ef62b04b6916b1" network for pod "prometheus-deployment-5766fbb466-vtptc": NetworkPlugin cni failed to set up pod "prometheus-deployment-5766fbb466-vtptc_default" network: error getting ClusterInformation: Get https://[<IP_ADDRESS>]:443/apis/crd.projectcalico.org/v1/clusterinformations/default: dial tcp <IP_ADDRESS>:443: i/o timeout
Expected Behavior
`
Prometheus pod start`

Current Behavior

Prometheus pod start

Possible Solution

Steps to Reproduce (for bugs)

git clone https://github.com/Nurlan199206/kubernetes-prometheus

2. kubectl create -f pv-prom.yaml
3. kubectl create -f pv-claim-prom.yaml
4. kubectl apply -f clusterrole.yml
5. kubectl apply -f prometheus-deployment-pv.yml
6. change IP in prometheus-config-map.yaml
7. create prometheus folder  to /mnt
8. copy prometheus.yml to /mnt/prometheus if you wanna use with PV

Context

Prometheus pods must be start, but something it's starting without any problem.

Your Environment

Calico version
3.7.3
Orchestrator version (e.g. kubernetes, mesos, rkt):

NAME          STATUS     ROLES    AGE     VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE       KERNEL-VERSION    CONTAINER-RUNTIME
kubernetes1   Ready      master   11d     v1.14.3   <IP_ADDRESS>      <none>        Ubuntu 18.10   4.18.0-1015-gcp   docker://18.9.6

Operating System and version:

NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.10"
VERSION_ID="18.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic

Link to your project (optional):

A guess from the error you provided is that kube-proxy isn't functioning correctly as I believe the <IP_ADDRESS> is the kubernetes api service address which it is responsible for configuring/setting up. You should check kube-proxy logs and see that it is healthy and create the iptables rules for the kubernetes services.

What caused this issue? I am facing the same thing.

I know this ticket is closed but just to help people who find this post i solved the problem when i changed my pod-network-cidr to pod-network-cidr=<IP_ADDRESS>/16

Thanks @Vitorspk.
Just to add the clarification: the pod-network-cidr=<IP_ADDRESS>/16 worked for Calico CNI. (I see some posts saying this is applicable to Flannel).

In between, do we know how updating the pod-network-cidr=<IP_ADDRESS>/16 fixes the issue?

@Vitorspk sadly changing the pod network CIDR to <IP_ADDRESS>/16 did not solve the issue for me.

@Vitorspk sadly changing the pod network CIDR to <IP_ADDRESS>/16 did not solve the issue for me.

I had the same issue and changed the CIDR as well without luck. I found the solution for me.
When I tried to do modprobe ip_conntrack && modinfo ip_conntrack it failed on the node but was working on the master. I checked and saw that the files were in /lib/modules/4.18.0-240.15.1.el8_3.x86_64/ (in that version) . I did something strange and don't even know why I tried it. On the master the modprobe command worked. I then copied the whole folder from /lib/modules/ to the same path on my node and then I was able to to modprobe. After a restart, my nodes worked again.
This was a pita and I hope you guys are lucky this way, if it also happens to you. I guess it was a broken kernel update or something.

After hours of googling, this is how I resolved it.
Its an issue with the default CIDR which is <IP_ADDRESS>/16 during the flannel initialization.
I'm using canal for CNI networking.
I solved this issue by editing configmap canal-config from the dashboard or use this
kubectl edit cm -n kube-system kube-flannel-cfg
net-conf.json: |
     {
       "Network": "<IP_ADDRESS>/16",
       "Backend": {
         "Type": "vxlan"
       }
     }

Use ``kubectl get nodes -o jsonpath='{.items[*].spec.podCIDR}' to get pod CIDR.
#change from <IP_ADDRESS>/16 to your own POD networks.
then delete the canal pod.
credits:Jun Chen

I sat for 2 weeks with this problem and finally found the solution (repost):
microk8s stop
or for workers: sudo snap stop microk8s
sudo vim.tiny /var/snap/microk8s/current/args/kubelet
Add this to bottom: --node-ip=
sudo vim.tiny /var/snap/microk8s/current/args/kube-apiserver
Add this to bottom: --advertise-address=
microk8s start
or for workers: sudo snap start microk8s

I think this solution is beacuse of that:
_

If you are using pod CIDR <IP_ADDRESS>/16, skip to the next step. If you are using a different pod CIDR with kubeadm, no changes are required - Calico will automatically detect the CIDR based on the running configuration. For other platforms, make sure you uncomment the CALICO_IPV4POOL_CIDR variable in the manifest and set it to the same value as your chosen pod CIDR.
https://docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-onprem/onpremises#install-calico-with-etcd-datastore
_

When I ran kubeadm init again with this range of network pods (<IP_ADDRESS>/16), Calico started fine. Later I added new nodes and also joined ok


Incomplete explanation how to change the options of chart instance at runtime

In the WIKI page about Options, there is an incomplete explanation about how to change the options at runtime.

The options, set to the chart to configure the chart, are cloned by Chart.JS therefore if the options must be changed at runtime, by a plugin, callback or whatever else, you can access to the options by a chart instance, if the chart is initialized (check by chart.isInitialized())
// --------------------------------------
// Chart options, cloned and update at runtime
// --------------------------------------
chart.getNode().getOptions();

This method was true before version 2.6 because it wasn't implemented the reconfiguration  of a chart instance (in current version by updateOptions, which will be renamed into reconfigure).

Fixed into wiki for new release


ci: possibly fixed cosign issues

:tada: This PR is included in version 2.1.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Interactive Wireframe

https://www.figma.com/proto/t77rlBAupEeqIYHFBBpqrl/Playground?node-id=723%3A28&viewport=48%2C337%2C0.14125387370586395&scaling=min-zoom
Mostly done, just a few finishing touches.

What needs to be done:

https://github.com/dOrgTech/DAOcreator/issues/254


visualstudio.com - Error: Compressed data doesnt match

Have a private repository on visualstudio.com, abapGit shows error "Error: Compressed data doesnt match "
Has anyone faced a similar issue? Will try to reproduce in public repository, plus try to find workaround.

decompression via lcl_zlib works => workaround

closing, will probably not look into this anytime soon, plus there is a workaround.
Please raise a new issue or leave a comment if you experience anything similar

Got same error in TFS 2017 onpremise.. not sure what the workaround is around lcl_zlib

Ok, got the workaround work, will work a pull request to fix this. Can you reopen the issue ?


Option to scale y-axis with time

This may require some thought about how to handle forces when the nodes are bunched up near the bottom, but this would be a really important alternative for viewing the timing of events as the scale is obfuscated in the current visualization.

Along with this, there should be an option to add a y-axis ticks to clarify what time. Honestly, that might be more useful than the true scaling of the graph, but both should be added.

Added by 54a505e


Showmetheweather

I am looking for some initial feedback before I refactor further.

Hey, added some notes, but this is really solid. There's nothing significantly missing or misplaced. Take a look at the suggestions, let me know if any are wrong or unclear, and move on. Also come talk to me about joining a team :)


1.4 Create a thunk, and reducer case so that AllProducts is able to use data from the database

Essential for #5

[ ] Action Type
[ ] Action Creator
[ ] Thunk
[ ] Reducer


docs: add seealso section to gzip sandbox

Signed-off-by: Long Dai<EMAIL_ADDRESS>
Commit Message:
Add seealso section to gzip sandbox
Additional Description:
Risk Level: LOW
Testing:
Docs Changes: add seealso section.
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] Fix #16748
[Optional Deprecated:]
[Optional API Considerations:]

looks good @daixiang0 - could we also add a link to the gzip api docs please

rendered docs are here https://storage.googleapis.com/envoy-pr/16796/docs/index.html
@daixiang0 could you fix format please

probably you want to adjust your editor so these dont happen
ERRORS found
1 files with missing newline
0 files with mixed tabs and spaces
0 files with trailing whitespace


Extract formatters to separate tools

This PR moves out the static method model.GraphSchemaRepresentation.parseJson and the instance method myModel.toJson() to be external to the schema class and instance.
This is due to that we want to be able to serialize the schema into other formats and having JSON as a first class citizen makes less sense.
This also simplifies the schema class by a lot.
Example usage:
import { formatters } from "@neo4j/graph-schema-utils";

const schema = formatters.json.fromJson(graphSchemaJsonString)

console.log(formatters.json.toJson(schema))

Thanks for the review @eijawerner, updated and responded to your comments.


Unreliable connection setup

Describe the bug
If I try to connect from a client to a websocket server implemented with mWebSockets the connection is not always setup.
Environment info

IDE w/version: Arduino IDE 1.8.15
Platform/Board: Arduino Due
Network controller (shield or module): EthernetShield 2

Expected behavior
The connection setup is executed properly every time I try to connect.
Failure log
No failure log output in case of connection is not setup (#define _DEBUG, #define _DUMP_HANDSHAKE, #define _DUMP_HEADER and #define _DUMP_FRAME_DATA are all set).
Log in case connection is setup:
[Line #0] GET / HTTP/1.1
[Line #1] Host: <IP_ADDRESS>
[Line #2] User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0
[Line #3] Accept: */*
[Line #4] Accept-Language: de,en-US;q=0.7,en;q=0.3
[Line #5] Accept-Encoding: gzip, deflate
[Line #6] Sec-WebSocket-Version: 13
[Line #7] Origin: moz-extension://d4825527-04cb-4cc5-9a5a-cca3f570223a
[Line #8] Sec-WebSocket-Extensions: permessage-deflate
[Line #9] Sec-WebSocket-Key: On6QMBBNL3JfSru3nICLsg==
[Line #10] Connection: keep-alive, Upgrade
[Line #11] Pragma: no-cache
[Line #12] Cache-Control: no-cache
[Line #13] Upgrade: websocket
[Line #14]

Additional context
Firecamp log output in case connection is not setup:

Firecamp log output in case connection is setup:

Hi @fkromer
Thanks for using the issue template ;)
How often does this problem occur? And how many seconds passes between connecting and error?
Anyways, this means that your client didn't even make it to _handleRequest which suggests that Arduino did'nt notice a client at all.

Hey @skaarj1989, you are welcome 😉 The error is displayed "immediatelly" (within a fraction of a second). Right, that's the strange thing...

@skaarj1989 The behavior is reproducible with Postman beta websocket support.

@fkromer Have you tried to add some delay before open()? like 1-2 sec?
Last month I replaced my router which introduced some issues with the connection and that 1sec delay resolved it.
About your Ethernet shield, is it "official" or a clone?

I'm waiting more than 5 seconds after power on before I try to connect to my server with a client. ATM I'm not using a router/switch but connect directly via crossover cable. The behaviour when connecting via a router is not different. It's an official Ethernet shiled v2.

@skaarj1989 It seems like one cannot use port 80 with websockets and a restful api server at the same time 😄  Can I workaround this somehow?

Is it really a big deal for you to a share REST server with websocket one?
If I were you, I would use two different ports like: 80 and 8080

@skaarj1989 Sometimes port 8080 is used by a proxy server or caching server. I'd like to avoid using it. However in case there is no workaround I'll use it.


Real-time streaming from camera or network

Hi,
I have read in the readme that real-time streaming from camera or network is supported. I'd like to learn please whether there is any back-pressure built into this pipeline framework that this repo implements. Or if not, whether any other design pattern is implemented for operating the pipeline at real-time (i.e. in a way that is not slower than the input rate, nor discarding, on average, a lot of pipeline work while rate limiting itself). Any comments will be very useful.
Otherwise, happy to learn your experiences in tuning streaming input rate in user code.
I read somewhere and seem to see in the RTSP part of Gstreamer that Gstreamer applies back-pressure, but not quite sure how this factors in when using DL-Streamer.
Thanks!

@matanster,
Sorry for the late response.
If my understanding is correct, "back-pressure" means the workload is too heavy and frames being dropped.
As my understanding, the overloading can be caused by many issues, for visual analytics pipeline, we should have following potential bottlenecks:

video resolution and frame rate, in the real-time case, can I assume 25~30FPS in your case?
Inference Engine: this depends on the model you used, how many stages of inference operation.
How do you want to output? Do you need rendering or just metadata.
The hardware capability: if you use a low end processor but video encode/decode can be offload to hardware, this can help you to increase the performance while keep the cost low.
About lost frame, what is your target? Lost video frame or lost inference frame. You might not do inference for each frame but keeps all the video frame, this is why we have an argument called "inference-interval" and gvatrack element which can skip the frame while keep the inference result consistent.

So it really depends on the application and hardware capabilities, but in general, if you can offload video to GPU, the bottleneck would comes more from inference, both openVINO and GStreamer offers the parallel processing for improvement.
Let me know if this answers your question.
Mark Liu

Hi @matanster,
I read the links you referred and I found this message about GStreamer new release.
I believe this is the back-pressure, you were talking about. This should be the RTSP server to handle a slow response device when it sends the message to many devices. From this context, the back-pressure means to remove the slower device from the server list of clients, the server performance will be impacted if it doesn't remove.
If this is right, I can't see anything to do with DL Streamer. Do you agree?
Mark Liu

It's certainly related, but a different scenario. I wouldn't want to keep anyone busy with this question type issue going forward though.

Hi @matanster,
Sorry I might not quit understand you: Are you saying if DL Streamer receives multiple camera streams, it will have the same issue as the server case to build up the back-pressure if there is a slower device?
I don't want to miss any good suggestions before I close this.
Mark Liu

@matanster ,
Thanks for the good input, let me close it now.
Mark


Decide what FFs to share

Decide what FF to share + annotate the files, incl refs:

[x] ClayFF with extra Fe(II)
[x] 'Amber' ions by Pengfei Li, these come in HFE, IOD and CN. I think IOD is best for us, but can include 3 sets. Need to rename them from 'Amber' cause they are not technically 'Amber'

Now in Ions.ff


workbench.settings.applyToAllProfiles overwritten by inheriting profiles

Type: Bug

Create a default profile with more than one setting added to workbench.settings.applyToAllProfiles
Create a new profile which inherits settings from the default profile
Find one of the settings that should apply to all profiles in the UI
Notice that "Apply Setting to all Profiles" is unchecked
Check "Apply Setting to all Profiles" for the setting that is already in workbench.settings.applyToAllProfiles
Check settings.json and notice that all previous settings to apply to all profiles have been replaced with the single one selected from the UI

Before

After

Update: somehow temporarily fixed this by trying to modify the setting in the UI whilst having unsaved changes in the settings.json file.  You can give our preview releases a try from: https://code.visualstudio.com/insiders/

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Hide React Storybook from the User Guide while it's incompatible

Between issues like https://github.com/facebookincubator/create-react-app/issues/2225, and the general switch to Webpack (and update of our preset) I am temporarily hiding React Storybook integration because it doesn't work. Will be happy to add it back once it's compatible with<EMAIL_ADDRESS>

Filed https://github.com/storybooks/storybook/issues/1073 as followup.


TestIbisTester test now fails because the test takes longer then 30s

Describe the issue
Our CI's fail quite often because this test takes too long to execute. I think we can fix this quite easily with awaitity and or by upp-ing the timeout value to 45.
Reporter
Niels

This hasn't happened in a while, closing it for now. Application should be fast enough that this test happily succeeds far before the 30 second timeout.


Default completion mode: Autocomplete treats symbol _ differently for table names and system functions

Description
User can ignore symbol _ when typing table name and autocomplete will suggest table name containing this symbol anyway.
But it doesn't suggest it for functions for some reason.
I think, autocomplete should also show suggestions in this case.
DBeaver Version
Community Edition <IP_ADDRESS>407122322
Operating System
Windows 10
Database and driver
PostgreSQL 16
PostgreSQL JDBC Driver 42.7.2
Steps to reproduce
https://github.com/user-attachments/assets/4ebb384e-caaf-4b2e-a82d-f341d32f18a7
Additional context
No response

Thank you for request


add ypbind-mt package

This is the first time I submit a pull request to nixpkgs.
I read and tried to adhere to the contributing guidelines on a best effort basis.
If there is still something wrong/missing or needs change I will gladly update the PR.
Description of changes
This pull request adds the package ypbind-mt which contains the ypbind binary needed for NIS clients to bind to NIS servers.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] Tested basic functionality of all binary files (usually in ./result/bin/)

Misc
The company I work at is using NIS/YP and the necessary tools are still missing in nixpkgs.
This is intended to be the first in a series of packages needed to create usable NIS clients (yp-tools and libnss_nis will follow).
This deviation was created and successfully built/used on a NixOS machine.
A few changes to the Makefile for manpages are necessary.
I did not find a way to prevent xmllint from trying to access the network.
Maybe there is a better way than commenting out the respective lines using sed?
Best regards
BarrOff

I did not find a way to prevent xmllint from trying to access the network.

Roughly speaking, XMLLINT requires some files (in a XSLT format) so that it knows what to do - think on it as providing a map with instructions to a human person.
If those files/maps are not locally present, then xmllint tries to download them (like a person opening the Maps applet).
Then you need to provide these XSLT files somehow. Usually Nixpkgs provides them already.

The Makefile has a hardcoded http url to a xml style sheet, see here and I see two solutions:

Disable this by commenting out that code (my initial solution)
Replace the http url with the manpage/docbook.xsl file from the docbook-xsl-nons package

By chance I tried the official release tarball from the repos release page and it worked without the problems I had with the fetchFromGithub code.
There the configure script automatically comments out the problematic lines.
It is also able to build the code without any custom configPhase/installationPhase settings.
I think this is the preferable solution and made a commit for this.
@AndersonTorres Do you see any remaining issues with the PR?

I think this is the preferable solution and made a commit for this.

Usually we prefer to use the pristine source code, so that we have more control over the build process.
It became more pronounced since the xzdoor incident.
But for now let's pick the tarball.

Now get rid of that excess of Semantic Commits and follow our commit conventions:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#commit-conventions

Just to make sure I understand correctly how to proceed:

I should do a rebase of all my commits to adjust the commit messages, then force push to my branch?
Am I supposed to squash some commits where suitable?

Yes. Get rid of that truckload of "feat/fix/style/etc".
Only things are

maintainers: add
: init at

Most projects I have worked on before use conventional commits so I used that.
In the meantime I read the contributing guide again and noticed the commit style guide.
I have rebased and squashed the commits as requested.


Make custom exceptions subclass Exception rather than BaseException

Most of the custom exceptions defined in openff/interchange/exceptions.py subclass the BaseException class. I propose that they be modified to instead subclass the Exception class.
Inherting from BaseException can create issues for users. For example, if you wanted to catch errors that may occur when building an interchange, the typical user would do something like this:
try:
    interchange = Interchange.from_smirnoff(forcefield, topology)
except Exception:
    exception_handling_function()

The above code would fail to catch most of the exceptions that could be raised by openff-interchange. While you could technically get around this by using a except BaseException statement instead, this is a non-standard practice that most users would not know to do. Moreover, python library docs explicitly advise against using BaseException directly. All user-implemented exceptions should instead subclass the Exception class.

I think you're right. This was an oversight on my part. Thanks for pointing this out!


[BUG]

Describe the bug
Just like this PR: https://github.com/microsoft/DeepSpeed/pull/5259 , ZeRO optimizer also needs to be fixed：

partition logic of expert params.

average_tensor used in gradient reduce in zero2

To Reproduce
Steps to reproduce the behavior:
use ep=4 and adamw optimizer to train llm
Expected behavior
expert gradients  should be equal under ep=4 and ep=1, but currently it's 4 times bigger than ep=1

@Jack47 Can you make a PR for this? Thanks!

https://github.com/microsoft/DeepSpeed/pull/5681 has solved it @Jack47