Refactor dockerised elasticsearch to use govuk_containers

This creates an init service, solving the problem of elasticsearch not starting in the dev VM on boot.
I've tested both replicating data from integration (after cleaning out some old snapshots - really need to get that automated soonish) and the search-api rake tasks.

This is part 1 of fixing the ES alerts in CI.  Part 2 will be a follow-up PR to ensure-absent govuk_elasticsearch and use this dockerised ES on the CI agents.

Im not sure about the data replication.  The volume has the same name, so I'd hope it would persist, but I don't know.  I suspect many people didn't do the data replication anyway, because the s3 bucket was huge.


Lyra Locker

Lyra locker functionality.
Allows developers to build public projects with a secret management system with lyra's powerful encryption.
Usage:

To initialize a project: lyra locker init

This generates lyralocker and .lockerpass files. Do commit lyralocker to vc and DO NOT commit .lockerpass

To add a file to be secured, append it to the lyra locker file.

Before commit, make sure to run lyra locker lock to encrypt all files

When you want to develop again, unlock the files with lyra locker unlock

The command lyra locker check can also be useful since it will fail if it detects any of your listed files as missing or unencrypted to allow for some cool CI or script integrations.

Full documentation is soon to come.

should we merge this?

We are still debating if this should be part of Lyra, or a stand alone cli. What do you think @tk8817?


ClangImporter: Adapt to clang -m[OS]-version-min change

Clang change 1ac71826854a809f67ae15ddacaaa9a6eb8189e8.
This is ailing the bots.

@swift-ci Please test

WARNING: DONT MERGE THIS BECAUSE the clang change was already reverted on swift-4.1-branch and is only waiting to get through to stable!!!!

Build failed
Swift Test OS X Platform
Git Sha - 6cc769a69bad9ac2ce1e83c4bce19b2068f5035a

@swift-ci Please clean test mac os x

@swift-ci Please clean test mac os platform

@swift-ci Please clean test OS X platform

Build failed
Swift Test OS X Platform
Git Sha - 6cc769a69bad9ac2ce1e83c4bce19b2068f5035a

FAILED: lib/swift/iphoneos/arm64/libswiftXCTest.dylib
: && /Users/buildnode/jenkins/workspace/swift-PR-osx/branch-master/buildbot_incremental/llvm-macosx-x86_64/./bin/clang++  -Wno-unknown-warning-option -Werror=unguarded-availability-new -fno-stack-protector -stdlib=libc++ -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fcolor-diagnostics -Werror=switch -Wdocumentation -Wimplicit-fallthrough -Wunreachable-code -Woverloaded-virtual -DOBJC_OLD_DISPATCH_PROTOTYPES=0 -fno-sanitize=all -DLLVM_DISABLE_ABI_BREAKING_CHECKS_ENFORCING=1 -O3 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk -dynamiclib -Wl,-headerpad_max_install_names -stdlib=libc++   -target arm64-apple-ios7.0 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.2.sdk -arch arm64 -F /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.2.sdk/../../../Developer/Library/Frameworks -mios-version-min=8.0 -Wl,-sectcreate,__TEXT,__info_plist,/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-master/buildbot_incremental/swift-macosx-x86_64/stdlib/public/SDK/XCTest/Info.plist  "-L/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-master/buildbot_incremental/swift-macosx-x86_64/./lib/swift/iphoneos/arm64" "-L/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-master/buildbot_incremental/swift-macosx-x86_64/./bin/../lib/swift/iphoneos/arm64" "-L/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-master/buildbot_incremental/swift-macosx-x86_64/./bin/../lib/swift/iphoneos" -o lib/swift/iphoneos/arm64/libswiftXCTest.dylib -install_name @rpath/libswiftXCTest.dylib stdlib/public/SDK/XCTest/iphoneos/arm64/XCTest.o stdlib/public/SDK/XCTest/CMakeFiles/swiftXCTest-iphoneos-arm64.dir/XCTestCaseAdditions.mm.o -L/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-master/buildbot_incremental/llvm-macosx-x86_64/./lib -framework Foundation -framework XCTest lib/swift/iphoneos/arm64/libswiftCoreMedia.dylib lib/swift/iphoneos/arm64/libswiftUIKit.dylib -framework CoreMedia -framework UIKit lib/swift/iphoneos/arm64/libswiftFoundation.dylib lib/swift/iphoneos/arm64/libswiftObjectiveC.dylib lib/swift/iphoneos/arm64/libswiftCore.dylib -framework Foundation -framework CoreFoundation && :
clang-5.0: warning: argument unused during compilation: '-miphoneos-version-min=8.0' [-Wunused-command-line-argument]
ld: warning: embedded dylibs/frameworks only run on iOS 8 or later
ld: embedded dylibs/frameworks are only supported on iOS 8.0 and later (@rpath/XCTest.framework/XCTest) file '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest' for architecture arm64
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)

Sorry, Arnold. I made exactly the same change for master-next yesterday but held off creating a PR when Alex reverted it.

Looks like Bob got to this in a84243c


Extends "http 2 push" feature to page cache enhanced

This pr extends "http 2 push" feature to page cache enhanced.
The Link headers are stored in the .htaccess into eg. /wp-content/cache/page_enhanced/foo-page/.htaccess and returned into the response like memory cache modules (APCu, Redis ...), eg.:
<IfModule mod_headers.c>
    Header add Link '</wp-content/cache/minify/1/ebbd6.js>; rel=preload; as=script'
    Header add Link '</wp-content/cache/minify/1/63402.js>; rel=preload; as=script'
    Header add Link '</wp-content/cache/minify/1/773a9.css>; rel=preload; as=style'
</IfModule>

The .htaccess is updated on each cache purge.
For some technical reason, this feature works only on the first 50 headers sent (but this limit is reasonable).
PR https://github.com/szepeviktor/w3-total-cache-fixed/pull/450 remove all limit and push all assets.
Also requested in https://github.com/szepeviktor/w3-total-cache-fixed/issues/234

Thank you.
Could you care about some description per commit?

right! i update my prs

what about nginx?

what about nginx?

@aelsharawi, without something like htaccess nginex can be supported.


cargo shuttle run not working

i create the project by using -->cargo shuttle init --from TylerBloom/shuttle-fullstack-rust-example
then follow the step as explained. when i ran command -->cargo shuttle run, this throw following error

Hey, thanks for this! I'm working on an update currently. The way that I do fullstack development has changed somewhat, so the update will include those changes too. This should be updated within the hour.

@dhrubrawat66 , I've pushed an update. Everything should work now. If you have any other questions or considers, open another issue or reopen this one. Thanks for you help!


Fix: Workspace settings page design

Details

Proposal => https://github.com/Expensify/App/issues/5767#issuecomment-940827933

Passed the footer as Prop.
Refactor the UI to use a single Container View.

Fixed Issues

$ https://github.com/Expensify/App/issues/5767
Tests | QA Steps

Go to any workspace Settings from the main Settings page.
Click General settings.
Page layout should be correct and Button should have proper placement.

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web | Desktop

Mobile Web

iOS

Android

@Julesssss Ready to merge.

Will get to this tomorrow, ran out of time today.

I think @Beamanator will take care of this now.

tested today, looking good. Will leave the merge to @Beamanator as he's yet to approve.


Add min_count option for hexbin plots

Pretty much just added this option in to _kind_options, made sure the converter would pass it if specified, and copied relevant docs from holoviews.
Now you can do this:

Looks great, thanks for the PR!


Acceptance criteria no longer shown after latest update

After latest update (probably Jan 9th 2023) we no longer see Acceptance Criteria field when looking at work items in an existing query based session.

Doing a quick search in repo history I couldn't find anything related to this. When looking at requests done by the extension I see multiple requests failing with a 404, which maybe are related:
https://extmgmt.dev.azure.com/mytenant/_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/estimate/Data/Scopes/Default/Current/Collections/%24settings/Documents/3a875f79-74bb-4926-816c-0d6310724c2a-field-configuration
https://extmgmt.dev.azure.com/mytenant/_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/estimate/Data/Scopes/Default/Current/Collections/EstimationSessions/Documents
https://extmgmt.dev.azure.com/mytenant/_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/estimate/Data/Scopes/Default/Current/Collections/sessions/Documents

It works as expected. we have just released a new update, try again and let me know.


Preformatted Text

As a developer
I want to be able use a PreformattedText component
so that I can easily add a preformatted text element
The component should contain:

[ ] embedded className called dcx-pre
[ ] relevant classes for shared / reusable styling
[ ] the ability to specify the value of the label
[ ]  the ability to specify other props (...props)

PreformattedText behind the scenes is a pre tag:

Text in a pre element
is displayed in a fixed-width
font, and it preserves
both      spaces and
line breaks.

The final user will use in this way:
<PreformattedText class="">Text in a pre element
is displayed in a fixed-width
font, and it preserves
both      spaces and
line breaks.</PreformattedText>

and the outcome will be something like this:

Text in a pre element
is displayed in a fixed-width
font, and it preserves
both      spaces and
line breaks.

Tasks:

[ ] Add unit tests
[ ] Add Application code with commented props
[ ] Add the ability to specify other props (...props)
[ ] Add Demo use of component
[ ] Add to storybook documentation file with examples (.mdx)  in a section called Typography
[ ] Add to live demo

Please follow the below to create your branch
git checkout release/0.8
git pull
git checkout -b 'feature/pre'

closed by https://github.com/Capgemini/dcx-react-library/pull/511


Use touch to switch between max and current values of wind widget

Like temperature widget, wind widget also has a max value with a time stamp. Add mode switch to wind widget to be able to switch between displaying the current value and the max value.
When the max value is shown, the label should display the date and time of that value.

https://user-images.githubusercontent.com/791721/219950812-b12a0bea-7fef-4369-94e6-11e83e2a893d.mp4


Add apkDebugSigningConfig setting

Usage example:
import android.PlainSigningConfig
import com.android.builder.signing.DefaultSigningConfig._

apkDebugSigningConfig := PlainSigningConfig(
    file( "./debug.keystore" ),
    DEFAULT_PASSWORD,
    DEFAULT_ALIAS
)

I would much rather prefer a new SigningConfig object type is created
e.g.
class DefaultDebugSigningConfig extends ApkSigningConfig {
  // debugSigningConfig can be used from apkbuild
  val debugSigningConfig = new DefaultSigningConfig("debug")
  debugSigningConfig.initDebug()
  override def keyPass = defaultSigningConfig.???
  override def alias: String = defaultSigningConfig.???
  override def storePass: String = ???
}

case class DebugSigningConfig(override val keystore: File) extends DefaultDebugSigningConfig {
  defaultSigningConfig.setStoreFile(keystore)
}

// and set the default value of apkDebugSigningConfig
apkDebugSigningConfig := new DefaultDebugSigningConfig

For your case, you would override this with apkDebugSigningConfig := DebugSigningConfig(file("/path/to/debug.keystore"))

You are right, that's much better than my clumsy conversion to SigningConfig. I'll give it another shot by tomorrow.

the conversion to SigningConfig is a good part of your change, it should remain (one could provide a release signing config for debug if one wanted)

I created a DebugSigningConfig class, that is populated with default keystore arguments. I'm trying to avoid debugSigningConfig.initDebug() as it throws an exception when the keystore isn't found. But since the plugin handles a non-existent keystore in Packing.apkbuild(), as far as I can tell, the exception would prevent the fallback mechanism.

I'd like to move the creation fallback into DebugSigningConfig. Additionally, remove the unused imports and everything looks about ok.
Squash and it's probably good to go. (double check by running scripted if you haven't already)
As an aside, initDebug itself does not throw, it's the defaultDebugKeystoreLocation that throws when the containing directory doesn't exist.

Any ideas how to handle the ILogger argument of KeystoreHelper.createDebugStore when moving it from Packaging.apkbuild to DebugSigningConfig?

Can either:

give it a NullLogger
pass the logger in with toSigningConfig

Pick one, I don't think the logging output when creating the debug key is very important.


Update ripsaw_v1alpha1_uperf_cr.yaml

Can one of the admins verify this patch?

Hey @ravvy00, can you provide some justification for these changes?

No description and no response. Closing


Request User Permission to Post to their Facebook Wall

I'm trying to request my users for their permission to post to their facebook wall using SammyK/LaravelFacebookSdk.
I have a button

<form method="POST" action="http://localhost:8888/facebook/checkin" accept-charset="UTF-8"><input name="_token" type="hidden" value="VTBcvupobSzcDThNeNguxCR4tMh2e28Wds4LzJA8">
  <button type="submit" id="check-in-with-facebook" class="btn btn-sm btn-primary btn-facebook">Check In</button>
</form>

After, they clicked on it, this controller function will trigger
public function checkin(){
    $fb = App::make('SammyK\LaravelFacebookSdk\LaravelFacebookSdk');
    $permissions = 'publish_actions, user_posts, user_photos';
    $login_url = $fb->getLoginUrl(['email','scope'=>$permissions]);
    return redirect($login_url);
}

Then, the redirect will happen to this URL below
https://www.facebook.com/v2.5/dialog/oauth?redirect_uri=http%3A%2F%2Flocalhost%3A8888%2Ffacebook%2Flink&state=04c7d976a47fca8c370b08b9d1dd954d&scope=email%2Cmanage_pages%2Cpublish_pages%2C+publish_actions%2C+user_posts%2C+user_photos&response_type=code&client_id=956232267794396&ret=login&sdk=php-sdk-5.2.0&logger_id=aff4eaf6-269b-479a-a91c-aa53b57447d2&ext=1474663682&hash=AeYpZWVkApEd5u-N

Then, the modal will pop up, but I see only Public Profile and Email Address.

I requested for publish_actions, user_posts, user_photos
What did I do wrong ?
Any suggestions / hints will be nice ...

Hello @bunlongheng .
If you try with another account/user besides the main one, make sure you have added user to "Test Users" in your application.

This line
$permissions = 'publish_actions, user_posts, user_photos';
$login_url = $fb->getLoginUrl(['email','scope'=>$permissions]);

Should be:
$login_url = $fb->getLoginUrl(['email', 'publish_actions', 'user_posts', 'user_photos']);

Good luck! :)


Databases tree view

Add a view to see databases and their tables
Description
The vast majority of database client software, if not all, show a list of databases and their tables as a tree structure. This is convenient for users that want to see all the database the have access to.
When it comes to dblab, things used to be a bit different, because database parameter was always required, either as a cli flag value or as part of the DSN. This was this way for the longest time because one reason. First off, dblab was heavily inspired by pgweb. This was the client I used to use at work, but suddenly I got tasked to manage a couple of microservices tied to MySQL databases, and I needed a FOSS alternative for Linux that worked as well as pgweb for my use case. pgweb rquires a database to connect to and only display its tables as a list. Then I tried to mimic a pgweb like client in the terminal and that's how dblab started. But things have changed I my needs have evolved and sometimes I need to look at other databases as well.
This MR basically removes the mandatory status of the database parameter and makes it optional. If the database is not provided, then, a tree structure is displayed  showig databases and their tables.
Another important change has been made and it was removing the pagination. I have rarely found myself using it, because it's faster to make query to where I need to be.

Fixes #209
Fixes #232
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Tested it against pagila databse and the testing database of the project
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have checked my code and corrected any misspellings

Hey @ccoVeille!
What a good code review there!
I already addressed all your comments. Let me know if I missed something.
Thanks so much!
P.S. Can I include you as a reviewer from this point on?

Hey @ccoVeille!
What a good code review there!

Thanks, you are welcome

I already addressed all your comments. Let me know if I missed something.
Thanks so much!
P.S. Can I include you as a reviewer from this point on?

Sure

Maybe you could add a co-authored-by tag
You can find my email here
https://github.com/samber/lo/commit/52a73c3ffda944e42c2d6f4fc1fb06a8eaf114c6
So, just add this to the commit message of the changes you made with my review
Co-authored-by: ccoVeille<EMAIL_ADDRESS>

Maybe you could add a co-authored-by tag
You can find my email here
samber/lo@52a73c3
So, just add this to the commit message of the changes you made with my review
Co-authored-by: ccoVeille<EMAIL_ADDRESS>

Alright @ccoVeille, I just added the co-authored tag. Honor when honor is due.
Can you go over the PR again, please? I 'd like to land this change tonight.


OpenCL support in ROCm

I see #12 - but this topic did not lay out OpenCL support - Ben Sander in comments @ http://gpuopen.com/rocm-do-you-speaka-my-language/ says OpenCL is soon, but this was May 5th (4 months ago from this issue).
I think it's pretty ironic/funny/sad OpenCL is the last thing to come out of the treasure trove of HSA that's been going on.  I see CLOC but it's useless against complex applications that use the OpenCL runtime.
Where are we with OpenCL kernel + runtime support in ROCm?

First  ROCm while it leverage capabilities form HSA Runtime Specification, we are moving beyond what HSA is capable off to better meet the need of HPC and Deep learning market.  We have  focused on other programing model first, HCC & HIP  since we had some key customer drive our direction.  Also since we have shipping drivers with OpenCL support today this is not as critical as you make it out.
Where we are on OpenCL on ROCm,  we had a version that running internally  via the old LLVM to HSAIL, HSAIL Finalizer to SC compiler (SC is our last big binary blob we are removing in ROCm 1.3).  Instead of releasing this we going to release OpenCL on ROCm only on the new Native GCN ISA Code generator based on LLVM.
The team is busy working on this and  the first release will be post ROCm 1.3
Please keep your comment professional on this site.
On Sep 5, 2016, at 7:09 AM, nevion <notifications<EMAIL_ADDRESS>wrote:
I see #12https://github.com/RadeonOpenCompute/ROCm/issues/12 - but this topic did not lay out OpenCL support - Ben Sander in comments @ http://gpuopen.com/rocm-do-you-speaka-my-language/ says OpenCL is soon, but this was May 5th (4 months ago from this issue).
I think it's pretty ironic/funny/sad OpenCL is the last thing to come out of the treasure trove of HSA that's been going on. I see CLOC but it's useless against complex applications that use the OpenCL runtime.
Where are we with OpenCL kernel + runtime support in ROCm?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/RadeonOpenCompute/ROCm/issues/30, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8DuShfZiyRdcTTcF_y-iHNA3MQHBgiks5qnAZjgaJpZM4J1Azo.

@gstoner I am being professional and here to help as well as meet my own needs (which should also benefit AMD)
The OpenCL implementation on catalyst doesn't function on the polaris arch, and doesn't support multi-GPU support (or at least has bugs where it hurts performance greatly) - cryptominers found that out first but I've acked it in my own work. Further, it's not exactly the best driver around, and in the interim (really for 1 year +) it seems to be a dead driver.
I do think it's pretty critical to get OpenCL here, all the people who wanted to keep things portable and didn't use CUDA wrote in OpenCL... so it's these same people you are not yet [currently] supporting but are a large part of your target audience - I know many of these types professionally and they're going to collectively wtf when they learn the current state of ROCm.  It is truth that CLOC is useless for applications using the OpenCL runtime - no ifs, ands, or buts about it - I can't use or rebase on it in any modest OpenCL application.
Post 1.3 sounds like maybe 1.4 at best which sounds like well into 2017 - is there no re-prioritization that can be done at this point?  Perhaps the internal library in the interm that still leans on the HSAIL/SC compiler ontop of current or old LLVM?
And related - how's progress doing on 1.3 - is that something that we should be seeing in Sept/October or in 2016?
-Jason

The current driver which support OpenCL which is not catalyst based that also supports RX480  that support Linux  this is 16.30.  This currently only supports Ubuntu 16.04, and 14.04 http://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-GPU-PRO-Linux-Beta-Driver–Release-Notes.aspxhttp://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-GPU-PRO-Linux-Beta-Driver–Release-Notes.aspx   Note this driver uses the same base AMDGPU kernel driver as ROCm ( We also use KFD beyond this)  with the HSAIL/SC compiler for OpenCL compilation.   Again it is not Catalyst based.
CLOC was developed by AMD Research,  honestly for those who take the time it very powerful tool on APU.  But it is not for those who want to leverage the OpenCL Runtime API for Host Code integration since you have to learn a new API interface.  We have number of customer who used it in the past for specialized code and had some nice performance wins since it give you more control over HSA runtime api.  But it not for you who need to be 100% aligned with OpenCL Runtime API in your coding practice.
ROCm 1.3 is currently scheduled in  late Oct to Early November, as I stated before this is when we see RX480 support as well, aka Polaris.   The OpenCL team has dependencies on OpenCL 1.3 so it needs to come out first,  First Release of OpenCL on ROCm will be before Christmas 2016.
Patience we working on this diligently,  we just want you to have solid experience with it when it comes out.
Software development of this class is not trivial, remember for OpenCL we have to run through Khronos Group conformance process as well if you want it to be conferment version you can use.
Greg
On Sep 6, 2016, at 4:30 AM, nevion <notifications<EMAIL_ADDRESS>wrote:
@gstonerhttps://github.com/gstoner I am being professional and here to help as well as meet my own needs (which should also benefit AMD)
The OpenCL implementation on catalyst doesn't function on the polaris arch, and doesn't support multi-GPU support (or at least has bugs where it hurts performance greatly) - cryptominers found that out first but I've acked it in my own work. Further, it's not exactly the best driver around, and in the interim (really for 1 year +) it seems to be a dead driver.
I do think it's pretty critical to get OpenCL here, all the people who wanted to keep things portable and didn't use CUDA wrote in OpenCL... so it's these same people you are not yet [currently] supporting but are a large part of your target audience - I know many of these types professionally and they're going to collectively wtf when they learn the current state of ROCm. It is truth that CLOC is useless for applications using the OpenCL runtime - no ifs, ands, or buts about it - I can't use or rebase on it in any modest OpenCL application.
Post 1.3 sounds like maybe 1.4 at best which sounds like well into 2017 - is there no re-prioritization that can be done at this point? Perhaps the internal library in the interm that still leans on the HSAIL/SC compiler ontop of current or old LLVM?
And related - how's progress doing on 1.3 - is that something that we should be seeing in Sept/October or in 2016?
-Jason
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/RadeonOpenCompute/ROCm/issues/30#issuecomment-244898719, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8DuZjW8Sf8pWm0u9CvblKr9YhUJVNgks5qnTLSgaJpZM4J1Azo.

@gstoner
FYI I edit my messages quite a bit so it is best you reply on github or at least reply to the post there so you see changes prior to reply.  I touched or clarified on a few of the topics you replied with.
You've restated CLOC and what it does but realize I never said it was a bad tool - just as you restarted, it doesn't work for OpenCL runtime using code... which is basically all code other than CUDA, at least in industry - it's only in that context I challenged it's applicability. For APUs it looks pretty nice but the HSA runtime or OpenCL runtime looks like a necessity for effective memory transfers to GPUs - at least this seems to be the case if you use SNACK.
Learning another API is not necessarily the issue, it's existing code/investments.  And I also want to track rocm's performance publicly, along with gpupro and team green's CUDA/OpenCL implementations - but I've got no way to do that now from what I can tell - unless arrayfire will support HSA/HIP - also a pretty big undertaking beyond what I can invest currently.  Said tests would be at Phoronix to help developers see the true (or truer) performance differences between the hardwares and driver stacks in-line with their capabilities - I've not come across other efforts to show this kind of data.
As for conformance tests, since you are doing this FOSSY, I'd rather see functional pieces starting in the near term so we can catch issues on it and iterate, rather than the big semi-annual release done previously.  Basically like POCL, beignet etc - you're allowed to iterate now and don't have to start being a perfectly polished conforming piece.  There may be parts I/others could contribute to in that process as long as they didn't cross into the closed source portion.
Remember I'm extremely happy you provide me/the public with information - this isn't available elsewhere - I won't hold you to it with a knife to dates but remember we've had patience with OpenCL support as a technology in general since it's inception - and it's frustrating to see all the disparate parts working... just not together, with no clear outline of current state or milestones that lead to expectations.  Maybe since you guys are trying to do this as a FOSS project - post public feature matrix of what can be done and milestones/release schedule so we can track along?

I want to thank you for your inputs,  your request for OpenCL on ROCm has been registered.   Since we have a base of commercial customer who want better then the current open source OpenCL distributions quality and capability for our  first release,  we need to balance level of quality, performance  and conformance on the first release.  We will be releasing it  before GA.
I recommend you to look at for benchmark so you can track performance with the three benchmarks  They Support OpenCL, CUDA and HIP.
https://github.com/ekondis/mixbench
https://github.com/GPUOpen-ProfessionalCompute-Tools/HIP-Examples/tree/master/GPU-STREAM
https://github.com/GPUOpen-ProfessionalCompute-Tools/HIP-Examples/tree/master/rodinia_3.0
On Sep 6, 2016, at 12:10 PM, nevion <notifications<EMAIL_ADDRESS>wrote:
@gstonerhttps://github.com/gstoner
FYI I edit my messages quite a bit so it is best you reply on github or at least reply to the post there so you see changes prior to reply. I touched or clarified on a few of the topics you replied with.
You've restated CLOC and what it does but realize I never said it was a bad tool - just as you restarted, it doesn't work for OpenCL runtime using code... which is basically all code other than CUDA, at least in industry - it's only in that context I challenged it's applicability. For APUs it looks pretty nice but the HSA runtime or OpenCL runtime looks like a necessity for effective memory transfers to GPUs - at least this seems to be the case if you use SNACK.
Learning another API is not necessarily the issue, it's existing code/investments. And I also want to track rocm's performance publicly, along with gpupro and team green's CUDA/OpenCL implementations - but I've got no way to do that now from what I can tell - unless arrayfire will support HSA/HIP - also a pretty big undertaking beyond what I can invest currently. Said tests would be at Phoronix to help developers see the true (or truer) performance differences between the hardwares and driver stacks in-line with their capabilities - I've not come across other efforts to show this kind of data.
As for conformance tests, since you are doing this FOSSY, I'd rather see functional pieces starting in the near term so we can catch issues on it and iterate, rather than the big semi-annual release done previously. Basically like POCL, beignet etc - you're allowed to iterate now and don't have to start being a perfectly polished conforming piece. There may be parts I/others could contribute to in that process as long as they didn't cross into the closed source portion.
Remember I'm extremely happy you provide me/the public with information - this isn't available elsewhere - I won't hold you to it with a knife to dates but remember we've had patience with OpenCL support as a technology in general since it's inception - and it's frustrating to see all the disparate parts working... just not together, with no clear outline of current state or milestones that lead to expectations. Maybe since you guys are trying to do this as a FOSS project - post public feature matrix of what can be done and milestones/release schedule so we can track along?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/RadeonOpenCompute/ROCm/issues/30#issuecomment-245020384, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8DuaeLcutQHlcTUn7qQY50PBLUDNVaks5qnZ5ygaJpZM4J1Azo.

@gstoner  What does releasing before general availability  mean? I wasn't able to understand
Also, after initial release - do you mean to imply that things will be a bit more open on development?  E.g. I submit a pull-request and you merge it and have it where you guys are doing development?
Thanks for the links to the benchmarks - I might add additional benchmarks for that after I get my initial release of the arrayfire CUDA/OpenCL tests working - still getting slowed down with Ubuntu support only there since I dont' have enough machines (my desktop runs OpenSUSE and I'm not willing to dual boot or keep switching GPUs on it since.. it's my everyday environment)   Anyway, I looked over each the tests of them just now.
With arrayfire based tests I'll be running something like 60 different tests across 32 and 64 bit floating point and integer types, perhaps also 16bit floats/ints.  I'm trying to not leave any stone unturned in the typical/atypical GPU engineers toolbox - there will be many opportunities for an implementation (hw + sw) to shine and falter on simple individual tests - and the code+work parameters are already very highly optimized and put in production. Where applicable we'll see a comparison  libraries like CUBLAS vs clBlas too since arrayfire builds on these.  So the testing is to be exhaustive over a large domain, high performance with real high-performance production code with "fair" comparisons being a goal as well, not just a stress testing code.

GA is old term when we see the product is no longer Beta Quality but ready for general release to customers to go into production.
Do you work for Arrayfire,  Since we working with them via the libraries team that works for me.
greg
On Sep 6, 2016, at 6:23 PM, nevion <notifications<EMAIL_ADDRESS>wrote:
@gstonerhttps://github.com/gstoner What does releasing before general availability mean? I wasn't able to understand
Also, after initial release - do you mean to imply that things will be a bit more open on development? E.g. I submit a pull-request and you merge it and have it where you guys are doing development?
Thanks for the links to the benchmarks - I might add additional benchmarks for that after I get my initial release of the arrayfire CUDA/OpenCL tests working - still getting slowed down with Ubuntu support only there since I dont' have enough machines (my desktop runs OpenSUSE and I'm not willing to dual boot or keep switching GPUs on it since.. it's my everyday environment) Anyway, I looked over each the tests of them just now.
With arrayfire based tests I'll be running something like 60 different tests across 32 and 64 bit floating point and integer types, perhaps also 16bit floats/ints. I'm trying to not leave any stone unturned in the typical/atypical GPU engineers toolbox - there will be many opportunities for an implementation (hw + sw) to shine and falter on simple individual tests - and the code+work parameters are already very highly optimized and put in production. Where applicable we'll see a comparison libraries like CUBLAS vs clBlas too since arrayfire builds on these. So the testing is to be exhaustive over a large domain, high performance with real high-performance production code with "fair" comparisons being a goal as well, not just a stress testing code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/RadeonOpenCompute/ROCm/issues/30#issuecomment-245114954, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8DuWQ9hQqKhlQ9Azgxj3-w4_fDLxIkks5qnefqgaJpZM4J1Azo.

@gstoner still lost on what the means for releasing before GA - does this mean you're releasing to your customer before GA or Releasing source on github before GA?
I don't work for or have any affiliation with Arrayfire, though I've talked with them about doing this testing a few months ago and patching up some of their existing stuff towards my goals.

When you do production software, there is number of development milestone
Developer Preview, ALPHA, BETA, Release Candidate,  General Availability.   Each release goes rigorous Q/A process , all of these milestones we pass through to a GA release branch, especially on pre 1.0 products.
First drop of OpenCL will be a  Developer Preview and will be OpenSource
Here is good overview Software release cycles https://en.wikipedia.org/wiki/Software_release_life_cycle

Just some  questions seems from notes that GPUPRO Linux Polaris driver supports only OpenCL1.2?
Any roadmap on supporting OpenCL 2.0 on Polaris on Linux?
it's sad now that even Intel has a OpenCL 2.0 Linux driver for Skylake iGPUs..
Also Intel has a OpenCL 2.1 preview driver since June and from gfxbench report seems drivers are in beta form for Kabylake iGPUs having 2.1..
Any beta info on OpenCL 2.1 drivers on AMD GPUs? some release on 2016?
mainly interested on using SPIR-V for OpenCL..
also hope that AMD Vega GPU release (heard rumors..) comes with ROCM support and OpenCL 2.x on Linux from day 1..

What do you need in OpenCL 2.0 that is so compelling?     Does Intel have OpenCL 2.0 on Xeon E5 v3 Hawell and Xeon E5 v4 Broadwell.   How about Xeon Phi, Night Landing?
Is SPIR_V for Compiler, if so you have much better path now we upstream our compiler in LLVM and built standardized loader and ABI for compiler.
On Oct 5, 2016, at 3:25 AM, Oscar Barenys <notifications<EMAIL_ADDRESS>wrote:
Just some questions seems from notes that GPUPRO Linux Polaris driver supports only OpenCL1.2?
Any roadmap on supporting OpenCL 2.0 on Polaris on Linux?
it's sad now that even Intel has a OpenCL 2.0 Linux driver for Skylake iGPUs..
Also Intel has a OpenCL 2.1 preview driver since June and from gfxbench report seems drivers are in beta form for Kabylake iGPUs having 2.1..
Any beta info on OpenCL 2.1 drivers on AMD GPUs? some release on 2016?
mainly interested on using SPIR-V for OpenCL..
also hope that AMD Vega GPU release (heard rumors..) comes with ROCM support and OpenCL 2.x on Linux from day 1..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/RadeonOpenCompute/ROCm/issues/30#issuecomment-251612847, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8DuWifc-TEfiqPonIhmzNh_fdSNWPgks5qw17ngaJpZM4J1Azo.

To clarify the first part of @gstoner 's message: http://registrationcenter-download.intel.com/akdlm/irc_nas/9418/intel-opencl-r2.0-release-notes-external.pdf
Looks like they got 2.1 with SPIR-V on windows though (see section 2.2).  No telling when linux will be so blessed from them, even for CPU only target, as is their tradition.
I'm more for 2.1 than 2.0 (for C++ support chiefly) - we definitely have a better path forward with AMD/ROCm's tool chain - there's no question, but critically it's still vaporware until it's not - an OpenCL long time tradition.  One can't yet plan or execute a project around the future support.
There's alot of things to be sad of in the state of things and especially confusion towards @oscarbg 's post, but @gstoner you seem to be frustrated in your replies as well.  Take some relief in that once you lay the golden egg, all us frustrated OCL developers will finally have a release to the stifling confusion we're in as well. Maybe that'll start a chain reaction of getting everyone's act together too; but at least there will be a platform that did it right.

Guys, we have been shipping OpenCL 2.0 on Windows for while now.  Honestly we have very few people really using it.  A bulk of our user are still using OpenCl 1.2 so they can support Mac OS X, NVIDIA, Intel and our hardware with there application.  Through in FPGA that support 1.0 and 1.1 and  when you build that matrix of Hardware and OS support it interesting view world of OpenCL.
When I look at OpenCL 2.0, here are the good features

C11 Atomics
Global Address Spaces
Shared Virtual Memory
Images - improved support

These are features that need more baking in CL group

clCreateCommandQueueWithProperties obuscating clCreateCommandQueue
PIPES, which need spec overhaul
Dynamic Parallelism need more time to bake as feature

We were building SPIR 1.2 in our driver Windows and Linux for last few years,  only  3 companies ever used it.   AMD, Codeplay and Continuum IO.
We also had C++ kernel language in our driver since 2012 which was hardly used.  http://developer.amd.com/community/blog/2012/05/21/opencl-1-2-and-c-static-kernel-language-now-available/
Greg
On Oct 5, 2016, at 12:35 PM, nevion <notifications<EMAIL_ADDRESS>wrote:
To clarify the first part of @gstonerhttps://github.com/gstoner 's message: http://registrationcenter-download.intel.com/akdlm/irc_nas/9418/intel-opencl-r2.0-release-notes-external.pdf
Looks like they got 2.1 with SPIR-V on windows though (see section 2.2). No telling when linux will be so blessed from them, even for CPU only target, as is their tradition.
I'm more for 2.1 than 2.0 (for C++ support chiefly) - we definitely have a better path forward with AMD/ROCm's tool chain - there's no question, but critically it's still vaporware until it's not - an OpenCL long time tradition. One can't yet plan or execute a project around the future support.
There's alot of things to be sad of in the state of things and especially confusion towards @oscarbghttps://github.com/oscarbg 's post, but @gstonerhttps://github.com/gstoner you seem to be frustrated in your replies as well. Take some relief in that once you lay the golden egg, all us frustrated OCL developers will finally have a release to the stifling confusion we're in as well. Maybe that'll start a chain reaction of getting everyone's act together too; but at least there will be a platform that did it right.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/RadeonOpenCompute/ROCm/issues/30#issuecomment-251744150, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8Due__viXdMPvQagvQAi1JKoqPb7oLks5qw9_ygaJpZM4J1Azo.

@gstoner yes, I used the kernel language, professionally a few times.  It solved some problems but had a bunch of other issues too -namely around memory spaces for pointer passing leading to copy paste definitions to handle variations on input.  Worth noting it never got 2.0 support.  I'll take 2.1 proper-er C++ support over that but AMD was very early showing it could be done / had it working.  I suspect there are more users of SPIR than you know of because it's used to prevent issues in distributing source, but it only works in limited platforms - I know a few more people who've tried or used these things.
Surprised pipes are in need of overhaul - seemed to basically unify Altera and Xillin'x channels, but maybe I missed something as I've not used any of the 3.  Also looking forward to more atomic operations and unified memory spaces (no combinatoric tagging of pointers in subroutines).  Images have been a mixed bag for speed, as an image processing/matrix processing person.
I'm sure you know but the OpenCL BoF conferences show a matrix of all the vendors and where they are at - confusion city, couldn't be in more disarray if they tried, even per vendor (like intel).

OpenCL 1.2 crippled C++ kernel language.
greg
On Oct 5, 2016, at 3:30 PM, nevion <notifications<EMAIL_ADDRESS>wrote:
@gstonerhttps://github.com/gstoner yes, I used the kernel language, professionally a few times. It solved some problems but had a bunch of other issues too -namely around memory spaces for pointer passing leading to copy paste definitions to handle variations on input. Worth noting it never got 2.0 support. I'll take 2.1 proper-er C++ support over that but AMD was very early showing it could be done / had it working. I suspect there are more users of SPIR than you know of because it's used to prevent issues in distributing source, but it only works in limited platforms - I know a few more people who've tried or used these things.
Surprised pipes are in need of overhaul - seemed to basically unify Altera and Xillin'x channels, but maybe I missed something as I've not used any of the 3. Also looking forward to more atomic operations and unified memory spaces (no combinatoric tagging of pointers in subroutines). Images have been a mixed bag for speed, as an image processing/matrix processing person.
I'm sure you know but the OpenCL BoF conferences show a matrix of all the vendors and where they are at - confusion city, couldn't be in more disarray if they tried, even per vendor (like intel).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/RadeonOpenCompute/ROCm/issues/30#issuecomment-251790294, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8DuVAuJoK7I9DItjVIs4-20afeI0JOks5qxAjWgaJpZM4J1Azo.

@gstoner So where are we with OpenCL support on ROCm now that 1.3 is out? Trying to get a test system up, but don't want to waste time if my Polaris hardware can't run OpenCL apps on ROCm in its current form.

OpenCL on ROCm is not supported on 1.3. A developer preview should be released later this year.

@jedwards-AMD In terms of porting OpenCL kernels to run on ROCm...what kind of endeavor would this entail? Would there even be any advantage to doing this? I know nvidia has a tool to port over CUDA code to their "version" of ROCm...is there something similar for ROCm for OpenCL code?

sorry for the wandering discussion but @jstefanop , what is NVidia's "version" of ROCm - and they need to port CUDA to run on it...?

You can take a look at CLOC if you want to do 'porting' to the HSA runtime. This is the link to it: https://github.com/HSAFoundation/CLOC
.
We actually distribute the CLOC tools from the rocm repository; you can install them with 'sudo apt-get install amdcloc'. However, if you want to use OpenCL on ROCm directly porting shouldn't be required.

However, if you want to use OpenCL on ROCm directly porting shouldn't be required.

Wait I thought you just said OpenCL is not supported on ROCm yet. Or do you mean ROCm will automatically compile and run OpenCL based code without needing OpenCL libraries etc?

@jstefanop That's in the future, not now - you may be able to test without code modifications (that is, the OpenCL runtime...) something before the end of the year though December being December, I suspect it's right at the end (christmas/new years present) or slips into January.  If you use the HSA runtime, you can compile OpenCL kernels now, but you need to use HSA runtime rather than OpenCL runtime to invoke them.
Also, again - what is NVidia's "version" of ROCm - and they need to port CUDA to run on it...?

@nevion Ok, so in other words use the CLOC tool to convert OpenCL kernels to HSA code object file, and then use the HSA runtime to run the program? Would the HSA runtime offer any speedup over running the kernel via normal OpenCL APIs/drivers?
And I mean the CUDA HIP tools where you can port CUDA to HIP and then run on either HCVV or NVCC

@jstefanop it could - OpenCL doesn't allow you to persist memory, it's not in the execution model - HSA I believe does.  Now how to practically get at that, IDK.  I've looked at the API with an OpenCL lens and it looks familiar but, especially in terms of OpenCL CLOC compiler, I'm not sure at all how you'd exploit something like that.  Other than persisting of memory to remove global memory transfers or local memory configurations, I don't think there could be any performance bumps than that.  And that's just theory, we have nothing to benchmark/see the performance of right now in terms of comparisons.


[openstack-2698]Agent timeout parameter change to apply to python req…

…uests timeout arg
@<reviewer_id>
What issues does this address?
Fixes #
WIP #
...
What's this change do?
Where should the reviewer start?
Any background context?

cherry pick the original change?

ok, cherry-pick done.


Cant load library libsixel.so.1

So I have tried make-ing the project and using the PyPi version, yet on both occasions I can't load the library. Could it be an incompatibility with Windows Subsystem for Linux 2, or PyPy, or the way I try to install this?
Python 3.6.9 (2ad108f17bdb, Apr 07 2020, 02:59:05)
[PyPy 7.3.1 with GCC 7.3.1 20180303 (Red Hat 7.3.1-5)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>> from libsixel.encoder import Encoder, SIXEL_OPTFLAG_WIDTH, SIXEL_OPTFLAG_COLORS
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/mnt/c/src/virtualenvs/code-wXNkIn9M/site-packages/libsixel/__init__.py", line 355, in <module>
    _sixel = cdll.LoadLibrary(find_library('sixel'))
  File "/mnt/c/src/pypylinux/lib-python/3/ctypes/__init__.py", line 432, in LoadLibrary
    return self._dlltype(name)
  File "/mnt/c/src/pypylinux/lib-python/3/ctypes/__init__.py", line 350, in __init__
    pypy_dll = _ffi.CDLL(name, mode)
OSError: Cannot load library libsixel.so.1: libsixel.so.1: cannot open shared object file: No such file or directory
>>>>

Fix
After makeing, cd into libsixel/src/.libs and copy all files usr/tmp


Modify log message and add Proxy constructor function.

The below error message is annoying, since these situations are quite common in proxy. Maybe they shouldn't be treated as Error.
ERRO[0032] socks error: error on copy from Remote to Client: readfrom tcp <IP_ADDRESS>:10801-><IP_ADDRESS>:42194: write tcp <IP_ADDRESS>:10801-><IP_ADDRESS>:42194: write: broken pipe
ERRO[0032] write tcp <IP_ADDRESS>:10801-><IP_ADDRESS>:42194: write: broken pipe
ERRO[0149] socks error: EOF

I changed these message  from Error to Debug.
And modified some log message to show more useful message like below.
INFO[0063] Connection established <IP_ADDRESS>:44260 - push.services.mozilla.com:443
INFO[0064] Connection established <IP_ADDRESS>:44262 - firefox.settings.services.mozilla.com:443
WARN[0132] Connecting to trace.qq.com:443 failed: EOF
WARN[0132] Connecting to trace.qq.com:443 failed: EOF

@firefart how do you think of this pr.


Some small post-0.5 fixes

Some tiny doc improvements and fixing 2 issues pub.dev reporting in the scoring section. This should bump us to 120/130.

LGTM! in order to have the score updated we would need to release 0.5.1, I can do that once this is merged.

FYI I released 0.5.1 with these formatting fixes


Add mergify to the provenance repo

Summary
Look into adding mergify to the provenance repo.
Problem Definition
PRs that get merged into main often need to be back-ported to a release branch.
Currently, that's done by having someone, locally:

Check out the release branch
git pull to make sure it's up-to-date.
Create a new branch from that.
Cherry-pick the PR's commit from main.
Push it up.
Create a PR.

All of that could be automated to happen when the main PR gets merged. It can also be triggered later if needed.
Proposal
Set up mergify for the provenance repo.
Consider also adding it to some of our other repos, e.g. our cosmos-sdk fork.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Previously #126

I feel like with the fancy new changelog setup which massively cut down on conflicts we are in a much better place and have less need for this change. In addition it seems like a merge queue would make more sense anyways (and that seems to be what the Cosmos SDK is using now too)


Better no internet connection state ($150)

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

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I can do it please assign to me

@josancamon19 Can this be assigned to me? Thanks


Make a gist command

This addresses #2226 and #2116 by creating a gist subcommand.
This allows you to both create and retrieve gists. When creating a gist it can be public or private.
In order to do this, the gist scope is added to the token we request.
Closes: #2226
Closes: #2116
Signed-off-by: Phil Dibowitz<EMAIL_ADDRESS>

I'm very new to golang, so I'm sure there's lots of cleanups I can do - just let me know.

the only test that's failing is test coverage dropped below a certain threshold. I'm not really clear on how best to write tests for this, so some guidance would be appreciated.

OK now that I've added the right scopes, I can create gists - but there's a few bugs in gist creation. Updated PR coming soon.

OK, this PR now works for creating and getting gists, and can do both public and private. It also adds the gist scope to our token. It's fully functional as far as I can tell.
As mentioned above, the only tests failing are test-coverage ones, and I'm happy to write some tests if someone gives me some guidance on what units they think are nicely testable here or points me to an example that might be relevant.

This is the way we typically author tests: https://github.com/github/hub/blob/4aba5854179b8e381bebd08ec9b2d49a3613eb15/features/release.feature#L370-L388
You will notice you'll have to stub a minimal stub of a GitHub API server since we don't communicate with real GitHub API when running tests.
You can observe other scenarios for examples how to e.g. initialize a file that you might pass to hub gist command: https://github.com/github/hub/blob/4aba5854179b8e381bebd08ec9b2d49a3613eb15/features/api.feature#L243-L246
Good luck!

Thanks @mislav ! There's now pretty thorough test coverage and all tests pass.

Any concerns with this? I'd love to get this feature merged now that there's tests.

@mislav I either updated the code or answered your questions for each of your requests.

Pushed some improvements to your branch. Hope that's ok! Let me know what you think.

The ability to get these back out on the terminal is really really important to the point of writing this module.

Thanks for outlining your use cases for gist fetch functionality. It sounds like most of the cases you're describing involve single-file gists. I'm still convinced that printing multi-file gists will be awkward, since the headers included in the output are gnarly and hardly machine-readable, and with --no-headers the output is basically useless because multiple (potentially unrelated, potentially in different languages) files would be concatenated together. I also don't see much use-case for the hub gist <id> <filename>-style invocation because that would require you to know the filename you want to fetch beforehand, and in most cases the person would not know the filename.
How about:

we only ever print single-file gists,
we error out on multi-file gists,
we support something like a --json flag to get raw JSON output which you can pipe to your own script that would handle multi-file.

Pushed some improvements to your branch. Hope that's ok! Let me know what you think.

Yup! I didn't know that was possible if the PR was based on a fork, neat.

How about:
we only ever print single-file gists,
we error out on multi-file gists,
we support something like a --json flag to get raw JSON output which you can pipe to your own
script that would handle multi-file.

I mostly agree - only one small disagreement. Yes, it's almost entirely single-file gists, so orienting around that makes sense. However, if someone sends me a multi-file gist where one file is the script and another is the output, and I want to get the script into a file, I'd really like to be able to do that without copy-pasting. So the use case of "I look at the webui and decide OK, I want to do hub gist <id> script.sh or whatever. I also don't want to arbitrarily limit other people just because I happen to be a single-file-gist user.
So how about this:

If you request a multi-file gist without a filename, we error out
If you request a single-file gist, it just works
We have a --json option, as you suggested.

I think that addresses your concern with the ugly output on multi-file output while also providing maximum usefulness to everyone involved. Work for you?

I didn't know that was possible if the PR was based on a fork

It's enabled by default, but you can disable it at the time of creating a new PR.

If you request a multi-file gist without a filename, we error out

Agreed: this is a good compromise.
I would still like to enable creating multi-file gists like so: hub gist <file1> <file2...>. I realize that this clashes with the hub gist <id> <filename>-style invocation for fetching existing gists. I wonder how we could un-clash them:

hub gist create <file...> & hub gist show <id> [<filename>] - requiring a subcommand is an easy workaround, but now the user is required to type a lot more
hub gist --file <file1> --file <file2> - multiple upload flags could be allowed
…something else I'm not seeing yet?

I think create and show are the cleanest... and people can always make aliases for them. That's easier than making an alias for --file <file1> --file <file2>. I'll update the PR this week when I have some time.

OK @mislav - I think that's all of the things we discussed. LMK if I missed anything.

@jaymzh Great work; thank you. I've pushed some fixes and tweak, please review! The most notable change is the dropping of --json flag; see the commit message for rationale and let me know if that makes sense. 🙇

Yeah I think dropping the json is fine.

Hmmm, it seems like your create changes broke something as well;
[phil@rider (gist) hub]$ cat /tmp/testfile | ./bin/hub create
Existing repository detected
https://github.com/jaymzh/hub

OK! I pushed a commit that fixes the things I commented on. LMK if you have any objections.

Added check back in.

Thanks for all your help!

Woo! Thanks for all of your help as I stumbled through golang!


Does not work with shared instance and subdirectory

I found some patterns.

preact & preact/hooks
svelte & svelte/internal

Example
preact case
import { h, render } from "https://esm.sh/preact";
import { useEffect } from "https://esm.sh/preact/hooks";

function App (){
  useEffect(() => {
     console.log("mounted");
  });
  return

}

svelte case.

compiled svelte has import { ... } from "svelte/internal".
To be common to both, they have to share the same instance in its inside. esm.sh failed.
(skypack works in these cases)

can you please post the svelte output?

can you please post the svelte output?

/* App.svelte generated by Svelte v3.31.2 */
import {
	SvelteComponent,
	detach,
	element,
	init,
	insert,
	noop,
	safe_not_equal
} from "svelte/internal";

import { onMount } from "svelte";

function create_fragment(ctx) {
	let h1;

	return {
		c() {
			h1 = element("h1");
			h1.textContent = `Hello ${name}!`;
		},
		m(target, anchor) {
			insert(target, h1, anchor);
		},
		p: noop,
		i: noop,
		o: noop,
		d(detaching) {
			if (detaching) detach(h1);
		}
	};
}

let name = "world";

function instance($$self) {
	onMount(() => {
		console.log("mounted");
	});

	return [];
}

class App extends SvelteComponent {
	constructor(options) {
		super();
		init(this, options, instance, create_fragment, safe_not_equal, {});
	}
}

export default App;

/* App.svelte generated by Svelte v3.31.2 */
import {
	SvelteComponent,
	detach,
	element,
	init,
	insert,
	noop,
	safe_not_equal
} from "svelte/internal";

import { onMount } from "svelte";

function create_fragment(ctx) {
	let h1;

	return {
		c() {
			h1 = element("h1");
			h1.textContent = `Hello ${name}!`;
		},
		m(target, anchor) {
			insert(target, h1, anchor);
		},
		p: noop,
		i: noop,
		o: noop,
		d(detaching) {
			if (detaching) detach(h1);
		}
	};
}

let name = "world";

function instance($$self) {
	onMount(() => {
		console.log("mounted");
	});

	return [];
}

class App extends SvelteComponent {
	constructor(options) {
		super();
		init(this, options, instance, create_fragment, safe_not_equal, {});
	}
}

export default App;

@ije
the main store of the library isn't shared between both dependencies.
Is there a way to fix this?

currenlty needs to declares the exports in package.json then esm.sh can split the code, for example:
{
  "name": "svelte",
  "exports": {
    "./internal": { import: "...", require: "...." }
  }
}

but i think i can add a workaround just for svelte

@ije
Can you help me write a more specific example?

@ije we have a library that's modularized into different packages. All packages share the same store, but this communication seems to get lost when importing the different packages with esm.sh

@ije Any update on this?

i think i have fixed it, but didn't deploy the patch yet

the "svelte" will import "./internal" instaed of bundling it

i'm still working on v136, will deploy the change soon

Hi there, will v136 also help/fix #741


IVector's IndexOf should handle queries for nullptr more gracefully

Fixes #518

Closing this PR as adding a try_unbox function, while a good idea, is bigger than this PR and would require a lot more test coverage.

But it means that the fix is incomplete. If I do stringVector.IndexOf(42), I get an exception instead of false.

Sure I'm not disputing that it would not be more resilient if it were able to handle such varied input - it's just more work than I can do right now.

As a stopgap fix, how about
bool IndexOf(Windows::Foundation::IInspectable const& value, uint32_t& index) const
{
    try
    {
        return IndexOf(unbox_value<T>(value), index);
    }
    catch (hresult_no_interface const&)
    {
        return false; // unbox_value failed, "value" wasn't even a boxed T
    }
}

Looks good.


Use full language name in language selector

Currently only the language identifier is given in the language selection menu. It might be more intuitive to have the full name of the language there. The full name of the language should preferably be written in the actual language itself, to make it easier to find for native speakers. Not sure what the best way of sorting is in that case.

@awvwgk Sir,it is surely possible but, The templates are not translate able thus we would have to put the translations in actual language manually in the template we wont be able to use the weblate.

Indeed, we would have to find the language name in the actual language, basically the same way as the language selection on Wikipedia works. A quick way to do this would be looking at the Wikipedia articles of the respective languages (e.g. German, Chinese). We can also ask the respective translators what the correct name is and insert it in the template.

It's OK for French = Français.

Spanish = Español

Simplified Chinese (zh-cn) = 简体中文


Integration Test - Release - 2021/11/02 00:22:57

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

#reassign PRMergerTest2

#reassign NonAllowedUser

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

#please-close

GitHub user PRMergerTest1 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#unassign PRMergerTest1

#unassign NonAllowedUser


Add ...-append-to-container for components such as tooltip

You should be able to set the means (maybe selector) of defining the parent element which will act as a container.
For example you have an element triggering the tooltip, which is inside a position: absolute or position: relative element, thus showing the tooltip incorrectly.
On the other hand you want to style the scrollbar and you opt for another element to be used for scrolling in order to apply some fancy scrolling directive (eg: angular-perfect-scrollbar, ng-scrollbar, ...) or you just want to have a header or the remaining of the content to be scrollable using another element.
In this situation you cannot opt for using tooltip-append-to-body="true" because  has overflow: hidden, thus leaving you with the option of adding the tooltip to another parent element that is suitable.
This functionality is implemented in other libraries as:

Bootstrap - data-container - http://getbootstrap.com/javascript/#tooltips-options
Angular-Strap - container - http://mgcrea.github.io/angular-strap/#/tooltips

It seems that there was an issue opened for this as [https://github.com/angular-ui/bootstrap/issues/139] but for simplicity sake ...-append-to-body was chosen which does not cover all aspects.

Feel free to open a PR - I'm immensely busy these days, and likely won't get around to it anytime soon myself.


CAMEL-8027 Add ByteArrayCodec implementation for udp to camel-netty4

Thanks the code has been merged. Do you mind closing this?

Allright. Thanks.


Quarantine flaky test 5252

Test is very flaky.
Quarantine it according guideline.
test_id:5252:
https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flakefinder-2021-05-01-168h.html#row32
row 32

https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/5250/pull-kubevirt-e2e-k8s-1.20-sig-storage/1388786794761293824
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/5578/pull-kubevirt-e2e-k8s-1.20-sig-storage/1388759047565479936
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/5062/pull-kubevirt-e2e-k8s-1.20-sig-storage/1388746326212087808

Signed-off-by: Or Shoval<EMAIL_ADDRESS>None

/cc @fgimenez

looks like it was already quarantined and removed in 8f77e858168f1e38774313d55b00abf49d175a0c

@dhiller
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/5579/pull-kubevirt-check-tests-for-flakes/1388809222673666048
checks a Quarantined test, which fails, should it or should it ignore the Q tests ?

Thanks Federico
@maya-r @brybacki
are we good to go please?

Go for it

Thanks
/retest

@dhiller
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/5579/pull-kubevirt-check-tests-for-flakes/1388809222673666048
checks a Quarantined test, which fails, should it or should it ignore the Q tests ?
Tests Suite: [sig-storage] [Serial]DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system] Starting a VirtualMachineInstance with a DataVolume as a volume source Alpine import [QUARANTINE][test_id:3189]should be successfully started and stopped multiple times

:+1: see https://github.com/kubevirt/kubevirt/pull/5581

Thanks @dhiller
mind reviewing this PR please?
there is a conceptual ack from Maya

/approve

It started consistently failing on 1st of May,
I suppose we might have a real problem, not a flaky test

/hold

I also suspected that, but i think we should not stall all other PRs (unless theoretical they can make the condition worse),
maybe XFAIL is a suitable solution on those cases (generally speaking, not just for this PR) ?

I think, that there is some kind of race condition, which was hidden before May - so it occurred once in many runs (between 1/10 and 1/100), and some latest changes made it appear often.
I am working on it now.
@oshoval I agree, new changes should not make condition worse

@brybacki
If i understood you correct you are fine with this PR getting merged,
can i remove the hold then @phoracek ?

@brybacki
If i understood you correct you are fine with this PR getting merged,
can i remove the hold then @phoracek ?

yes

Thanks
/hold cancel

/test pull-kubevirt-manifests


forecasting: selecting exogeneous variables

I think there should be wrappers that allow to select which exogeneous variables to use, which is useful in cases where forecasters behave differently if they get exogeneous variabes or not. Notably, a large number of "garbage variables" can hamper performance, so selection of exogeneous variables may be helpful, and enables automated selection, too.
For instance, useful wrappers could be:

IgnoreExogeneous which blocks any X from being passed.
SelectExogeneous which takes a list of column names, and only passes those ones through.

The SelectExogeneous can also be used in combination with tuning for automated feature selection.

@fkiraly would the idea also be to eventually add functionality for automated exogenous variable selection methods?

I just wanted to open an issue when I saw this one :) so I rather write my idea here:

Is your feature request related to a problem? Please describe.
I would like to add a transformer that can selection features based on feature based on feature importance values of a meta-model/regressor.
Related: #1268
Describe the solution you'd like
SelectExogeneous(method="feature_importances", regressor=DecisionTreeRegressor(), n_features=12, max_features=None, random_state=None)

where regressor is any sklearn-like tree-based model with an attribute feature_importances_. The regressor would be fitted on the y as endog and X as exog. The regressor could even be a GridSearchCV if user want to tune the meta-model.
Other methods that come to my mind:

Random sampling method where features are sampled randomly.

But I would start with the proposed solution.
Additional context

pipelining
tree-based models
panel/global forecasting

@fkiraly do you agree that this class should be implemented as a _SeriesToSeriesTransformer? Bcz it will be part of tuning so it could be tuned in a ForecastingPipeline

I have already started implementing a transformer, but now I faced issues with the transformer interface. So the issue is, that the regressor would need y and X so also the transformer needs both then. But there is no such case in the transformer interface where y and X is given and Xt is returned. See STEP here  where we wrote down the cases.
But the order is switched. So the transformer would get the data as follows:
FeatureSelection(...).fit_transform(Z=X, X=y)

This switch is needed as we transform X by selecting some columns (features) and return X also and y is just needed to build the regressor. This switch looks a bit weird maybe and also then we need a new tag for this, so in ForecastingPipeline we can have an if statement to check if y and X have to be switched. As currently the ForecastingPipeline just does Transformer().fit_transform(Z=X) and is not giving y. We already use the skip-inverse-transform tag, so it might be ok to add another into the ForecastingPipeline?

I discussed this with @mloning and he proposed to always switch arguments in ForecastingPipeline to have fit(Z=X, X=y) as we also give both arguments in TransformedTargetForecaster.fit(Z=y, X=X). I agree to this and it makes sense to me.

closed by my PR #1347


Bug: APIGatewayProxyEventV2.decoded_body should not cause KeyError

Expected Behaviour
For event of type APIGatewayProxyEventV2, event.decoded_body or event.json_body (which calls the former) could result in KeyError when there is no body.
Current Behaviour

Code snippet
`event.decoded_body` or `event.json_body`

Possible Solution

event.decoded_body should return empty string or None
event.json_body should raise JSONDecodeError

Steps to Reproduce
As described.
Powertools for AWS Lambda (Python) version
latest
AWS Lambda function runtime
3.11
Packaging format used
PyPi
Debugging logs
No response

Hey @aahung! Thanks for reporting this bug. You're right, we should use body: str = self.body instead of body: str = self["body"] in this line https://github.com/aws-powertools/powertools-lambda-python/blob/develop/aws_lambda_powertools/utilities/data_classes/common.py#L149.
Do you want to send a PR to fix this? We would love it.
Thanks

Hi @aahung could you share how you ended up with the body key missing in the first place? Was this an actual request from API Gateway HTTP API, or a fake event?
Thank you


Enable backup url support for SQL Server

Enable backup url support for SQL Server
Fix https://github.com/microsoft/azuredatastudio/issues/24589

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.574%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
30787

Relevant Lines:
69355

💛  - Coveralls


fix(button): Invalid CSS

This pr resolves #524 by solving invalid CSS declarations in compiled inline styles

Nice, this is huge @NiazMorshed2007 🎉


Double devtools message

Hi,
When I import model I have a double message by devtools (chrome) in browser console:
admin.js:123789
You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html

admin.js:105945
You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html

Sometimes it make crash vue-devtools extension. Without import vue-mc models message print once and extension works fine.

Hi! Are you use NuxtJS?

No. I use laravel-mix, vuejs 2.6.10, vue-mc 0.5.0.

I have some trouble when using vue-mc only with NuxtJS ...

I have the same error, could it be linked to the error reported at #121
vue-mc needs  2.5.17 instead of 2.*
it causes Vue to be loaded twice as seen in webpack-bundle-analyzer

how to circumvent that ?

I have the same error, could it be linked to the error reported at #121

Thanks, I checked your version.
I replaced "vue": "2.5.17" with "vue": "^2.5.17" in node_modules/vue-mc/package.json, deleted the directory node_modules/vue-mc/node_modules/vue/ and rebuilded my project. After that, the vue stopped loading twice.

@suinly it fixes the problem only on your local developpment environment right ?

A PR has been opened here :tada:

This has been fixed and released as part of v0.6.0.


fix: fix overriding tx index of duplicated txs

Description
The function OnStart() starts a goroutine to handle block events and transactions continuously. However, there is no duplicate check against batch before performing an invocation on txIdxr.AddBatch(). Moreover, a new transaction containing failed results may override a successful transaction that has already been indexed in the db, which may lead to confusion in accounting calculations.
This PR addresses the above issue. And the content is the same as here.

What's the reason to incorporate only this https://github.com/tendermint/tendermint/pull/8625 PR now?

@torao
I added the issue this PR addresses to Description.


ability to set access_token expiry from Supabase dashboard

so users can issue long lived tokens

Closing this in view of security concerns listed here


not rendering on mobile

It seems like codemirror is intentionally blocked on mobiles.
Why is that?
if (!IS_MOBILE) {
  cm = require('codemirror');
}

Hello,
If you peek at #22, I implemented this for server-side rendering support. I borrowed the implementation from sample implementation available in react-code-mirror.
I don't specifically see why mobile should be excluded as well but figured this was already solved, hence why it's implementation this way. I'm not opposed to supporting mobile devices but would like to learn more about the use case.
Do you have a need to use codemirror on mobile? I'd imagine it wouldn't be very effective to have syntax editing on mobile - but - I suppose the case could be made for it.
Thoughts?

Hi @scniro
First of all, thank you for the quick response and pushing this project forward.
Currently, there is no option to use react-codemirror2 without SSR setup. The main use case is to support mobile browsers, just like the original codemirror do. I know it's experimental, but it works pretty well.

@xidedix hey again. Sure I can take the check out for mobile but leave the navigator check in place for server-side rendering. I am currently trying to work through another issue but as soon as that is resolved I'll include this change as well in the next release (hopefully by tomorrow at the latest)

Hey @scniro
I'm using this project for https://react-reboot.now.sh/
An user reported an error on Android mobile and it's due to this check:
https://twitter.com/trickydisco78/status/925999722938191872
I don't think my tool should be very usable on mobile as coding on a mobile device is not good DX, but at least I'd like to offer mobile visitors a preview of the purpose of the tool that does not show "unexpected error" :D

I use the controlled input on mobile, and do update the props from parent, triggering componentWillReceiveProps, this.hydrate() and this.editor.setOptions (which fails)
Not sure exactly to understand the purpose on IS_MOBILE but you probably want to add this to the this.hydrate() to be consistent

For those interested I published react-codemirror2-mobile with the mobile check removed

@slorber This is going to be fixed today. Clearly the issue is fresh and I even make mention that I'll be working through this. To publish a new project only a few hours after your first comment on an active thread is jumping the gun a bit, don't you think? I'd strongly suggest un-publishing that and have a small amount of patience.

@scniro I'm not forking your project to maintain it, I'm just publishing a static version that I can use as a dependency right now, but for sure I'll use your version once you make it work on mobile
I often do that when I want the fix to work right now and it takes me 5min so not a big deal, now you can take your time to fix it properly ;)

@slorber Ahh gotcha, I do similar but Ill usually npm pack the source which builds a binary that can be installed locally as if it were from npm.
Anyways, this should be fixed in the 3.0.6 release. Please check it out and let me know if all looks good? If so I'll go ahead and close this out 👍

thanks it works fine for me

LGTM, thank you Sal!


rework placeholders to use single editor

closes #102
Greatly simplifies the placeholder systems, ripping most of the code around them out. Less code more better :)
Bit to do before it's ready though.

[x] Multistyle widget with placeholder support ( doesn't matter, placeholder operates when editor is empty )
[x] Move placeholder functions out of main render, like password input
[x] Testing

Nice 👍


Set up spec compliance checker

The s2n-quic maintainers created a neat tool to check compliance with specifications with comments in the code. We can set it up to run as a CI job against RFC 9114, and have it publish to the gh-pages branch.
This GH Action is very close to what we want. The only difference is to remove the S3 bucket stuff, and just push to gh-pages.
Once this is setup, we can start systematically adding comments or fixing things to improve our handling of the HTTP/3 spec.

I would like to help out if it's ok.

Help is always welcome!

Duvet is used internally, prone to change in terms of api or file structure. Rather than checking out the code in the action, I think it might be better to just inline duvet in the h3 repo, so that the checks won’t break due to changes in the aws repo.
I have something that’s close to what you described, in this fork. But I still need to do some digging to figure out how the spec parsing/extraction works.
Would love some pointers for

What is your preferred way to give credit to code from a different project?
What is the preferred path for the report? From the current setting in the fork, I think the report can be accessed via SITE/h3/ci/compliance/report.html.

I wonder if that team would be interested in publishing the crate, so we could depend on versions. @camshaft?

Let me talk to the team today

Alright, we're getting together a plan to publish the tool for external consumption.
My recommendation for until then is just clone the s2n-quic codebase and compile it rather than copy the source. We won't move the location until you're fully migrated to the published version.


Own file from Personal, which was shared, cannot be shared with other persons anymore

Error description
Own file from Personal, which was shared, cannot be shared with other persons anymore
Steps for reproduction

Create directory
Drag 2 files by D&D into the directory
Share 1 file of it to 2 persons
share directory to the same 2 persons
previously shared file can now not be shared anymore

Expected behavior
files located in the directory can be shared with other persons
Actual behavior
File cannot be shared
Additional context
see screencast
https://github.com/owncloud/ocis/assets/132444655/51091dee-3284-40ee-b0b9-4d50eb2fa6bb
notice
added here after consultation with @tbsbdr

@tschiebel @tbsbdr Why did you open am public community ticket?


Add GCSDownloadStrategy

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Hello, I based this off of the S3DownloadStrategy as it most closely matched the steps that needed to be done.
I'm still running tests on a dummy formula to make sure the google cloud gem get's installed and all that as I was having issues on my other laptop but I want to make sure it's not my ruby setup before filing a bug.
This being the case, I don't know if I should label this PR or do something more since I didn't see anything in the contributing guide in terms of adding new download strategies.
Thanks in advance and thanks for this tool... life saver 🙏

Okay so I'm getting an install error when trying to --build-from-source:
/usr/local/Homebrew/Library/Homebrew/os/mac/xcode.rb:1:in `<top (required)>': OS is not a module (TypeError)
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/extend/os/mac/development_tools.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/extend/os/development_tools.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/development_tools.rb:127:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/tab.rb:5:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/utils/bottles.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/formula.rb:6:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/readall.rb:1:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/tap.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/global.rb:142:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Homebrew/Library/Homebrew/build.rb:6:in `<main>'
Error: Failure while executing; `/usr/bin/sandbox-exec -f /private/tmp/homebrew20181008-17955-hwoj4s.sb nice /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby -W0 -I /usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/../ruby/2.3.0/gems/ruby-macho-2.0.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/../ruby/2.3.0/gems/plist-3.4.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/:/usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/../ruby/2.3.0/gems/backports-3.11.4/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/../ruby/2.3.0/gems/activesupport-5.2.1/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/../ruby/2.3.0/gems/tzinfo-1.2.5/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/../ruby/2.3.0/gems/thread_safe-0.3.6/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/../ruby/2.3.0/gems/minitest-5.11.3/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/../ruby/2.3.0/gems/i18n-1.1.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle-standalone/bundler/../ruby/2.3.0/gems/concurrent-ruby-1.0.5/lib:/Library/Ruby/Gems/2.3.0/gems/did_you_mean-1.0.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/multipart-post-2.0.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/faraday-0.15.3/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/google-cloud-env-1.0.5/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/google-cloud-core-1.2.7/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/uber-0.1.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/declarative-0.0.10/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/declarative-option-0.1.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/representable-3.0.4/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/retriable-3.1.2/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/public_suffix-3.0.3/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/addressable-2.5.2/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/mime-types-data-3.2018.0812/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/mime-types-3.2.2/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/multi_json-1.13.1/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/jwt-2.1.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/signet-0.10.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/memoist-0.16.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/os-1.0.0/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/googleauth-0.6.6/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/httpclient-2.8.3/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/google-api-client-0.24.2/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/google-api-client-0.24.2/generated:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/google-api-client-0.24.2/third_party:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/digest-crc-0.4.1/lib:/usr/local/Homebrew/Library/Homebrew/vendor/bundle/ruby/2.3.0/gems/google-cloud-storage-1.15.0/lib:/Library/Ruby/Site/2.3.0:/Library/Ruby/Site/2.3.0/x86_64-darwin17:/Library/Ruby/Site/2.3.0/universal-darwin17:/Library/Ruby/Site:/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby/2.3.0:/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby/2.3.0/x86_64-darwin17:/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby/2.3.0/universal-darwin17:/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/vendor_ruby:/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0:/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/x86_64-darwin17:/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin17:/usr/local/Homebrew/Library/Homebrew -- /usr/local/Homebrew/Library/Homebrew/build.rb /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/dummy.rb` exited with 1.

My config looks like this:
HOMEBREW_VERSION: 1.7.6-12-gc23e352
ORIGIN: https://github.com/Homebrew/brew
HEAD: c23e3525045987b3041ddc7ab0947af61b558223
Last commit: 41 minutes ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 45d56094d180dd29857ecf9d6b14436d155291c5
Core tap last commit: 35 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DEV_CMD_RUN: 1
HOMEBREW_GCS_CREDENTIALS: /Users/andreslowrie/Creds/andres-on-mine.json
HOMEBREW_GCS_PROJECT: mine-218822
CPU: dodeca-core 64-bit kabylake
Homebrew Ruby: 2.3.7 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 10.0 build 1000
Git: 2.19.0 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: N/A
macOS: 10.13.6-x86_64
CLT: <IP_ADDRESS>.1.1535735448
CLT headers: N/A
Xcode: N/A
XQuartz: N/A

I'm guessing this is something I did wrong in the download strat?

Regarding the gem,
I based this on the S3DownloadStrategy and noticed that it went through some iterations where it went from accessing the url to using the aws gem ... so I thought that was preferred
Yes you're correct in your assumption, the idea is to be able to download private resources; I'm reading the documentation now again to see how to do this without the gem.

I do not want to include any more download strategies that will not be used by Homebrew/homebrew-core. Instead I'm interested in allowing taps/private taps formulae to have ways to specify download strategies within their formulae.

I've opened https://github.com/Homebrew/brew/issues/5074 with the proposed new approach.


SIP impl for FreeSwitch

Can anyone help me with using this repo for connecting to FreeSwitch through SIP and performing these tasks:

Manage incoming and outgoing calls
Transfer calls (with or without consultation)
Send and receive messages

I would be grateful for your helpful information.

This should be asked as a community question since it is not a bug therefore closing


Revert "Add transport data from maps.yandex.ru api"

Reverts home-assistant/home-assistant#26252

The library is not 100% conform and did not correct work with pip/packages.
Please fix the library and create a new PR.

Do we have more info on the problem?

@MartinHjelmare that is not your issue. There was a problem with manifest and lizenz file. On the last two years, I saw only two libraries with this issue. I think that is handleable without CI check.

Ok, thanks for the details. :+1:


detect.py on coral dev-board with gstreamer coral camera pipeline segfaults

I tried running the sample . It runs for a little while and the segfaults. Any ideas why ?
mendel@queen-rabbit:/mnt/objd/examples-camera/gstreamer$ python3 detect.py
Loading ../all_models/mobilenet_ssd_v2_coco_quant_postprocess_edgetpu.tflite with ../all_models/coco_labels.txt labels.
Detected Edge TPU dev board.

Inference: 21.85 ms FPS: 13.53 fps
Inference: 22.00 ms FPS: 16.54 fps
Inference: 21.68 ms FPS: 16.74 fps
Inference: 16.41 ms FPS: 15.95 fps
Inference: 21.20 ms FPS: 19.54 fps
Segmentation fault
mendel@queen-rabbit:/mnt/objd/examples-camera/gstreamer$

FWIW, I am running the newest 3.0 chef-13 image on the coral compiled and released in April 2019
mendel@queen-rabbit:/mnt/objd/examples-camera/gstreamer$ uname -a
Linux queen-rabbit 4.9.51-imx #1 SMP PREEMPT Fri Apr 5 00:17:46 UTC 2019 aarch64 GNU/Linux

mendel@queen-rabbit:/mnt/objd/examples-camera$ v4l2-ctl --list-formats-ext --device /dev/video0
ioctl: VIDIOC_ENUM_FMT
Index       : 0
Type        : Video Capture
Pixel Format: 'YUYV'
Name        : YUYV 4:2:2
Size: Discrete 640x480
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 720x480
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 1280x720
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 1920x1080
Interval: Discrete 0.067s (15.000 fps)
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 2592x1944
Interval: Discrete 0.067s (15.000 fps)
Size: Discrete 0x0
edgetpu_detect_server --source /dev/video0:YUY2:640x480:30/1 --model all_models/mobilenet_ssd_v2_coco_quant_postprocess_edgetpu.tflite --labels all_models/coco_labels.txt --threshold=0.45
The above example does not segfault whereas detect.py does segfault
Other examples here are helpful also https://coral.withgoogle.com/docs/dev-board/camera

Hi, I was able to reproduce this, although only sporadically (maybe 1/10 runs). I've pushed a patch to the repo that appears, as far as I can, tell to eliminate the seg fault. Could you try pulling the latest from this repo and trying it again on your board, since it sounds like you were able to get the fault on each launch ? Tnx!

@mtyka ,
Yes segfault seems eliminated. I'll run it all night to confirm it is indeed fixed. Thanks!

Wonderful - thank you for reporting it ! If it starts acting up again, let me know!

Hello all. I'm having a very similiar issue to the above.
Displaying the face detection on a USB camera runs 100% fine with the following (the export DISPLAY=:0 is necessary to avoid wayland errors)
export DISPLAY=:0 && edgetpu_detect \
--source /dev/video1:YUY2:1280x720:20/1  \
--model ${DEMO_FILES}/mobilenet_ssd_v2_face_quant_postprocess_edgetpu.tflite \
--threshold=0.45

However, when I try and run my own tflite model  (tflite_paint.tflite), the computer balks.
export DISPLAY=:0 && edgetpu_detect \
--source /dev/video1:YUY2:1280x720:20/1  \
--model ${DEMO_FILES}/tflite_paint.tflite

The warnings are pretty similiar to running face detection, so I'm not too concerned about that.
t.  It cuts after 1 frame.
t.
	Using the fallback 'C' locale.
Unable to init server: Could not connect: Connection refused
Loading ../all_models/mobilenet_v2_1.0_224_quant_edgetpu.tflite with ../all_models/imagenet_labels.txt labels.
Detected Edge TPU dev board.
 Already tried coral camera vs external usb camera....
python3 /home/mendel/google-coral/examples-camera/gstreamer/classify.py --videosrc /dev/video1
Unable to init server: Could not connect: Connection refused

(classify.py:6429): Gtk-WARNING **: 10:52:41.904: Locale not supported by C library.
	Using the fallback 'C' locale.
Unable to init server: Could not connect: Connection refused
Loading ../all_models/mobilenet_v2_1.0_224_quant_edgetpu.tflite with ../all_models/imagenet_labels.txt labels.
Detected Edge TPU dev board.
 Thank you in advance.


Wip console.log

Did you build the project before submitting the PR?

[ ] Yes
[x] No

This is already removed on v2 branch. Thanks anyway.

Thank you. I just sent it because company policies require no console log. Great.