v0.10.13 release - is this gem safe or hijacked?

Hi, I saw that last commits at this repo was made in 2019 year -  at times of release gem version v0.10.9
But according to rubygems there was 4 releases since dec of 2019
And last release was made today, on 22 nov of 2021
Is this gem hijacked? Someone making releases without actual commits and changes in code of this repo?
Or is this just a complicated release process and maybe some note should be added to README?

I’ve delegated maintenance of the gem to RubyMine team. The latest version of the gem has been released by https://rubygems.org/profiles/hurricup so I presume they just have not updated the repo.
@valich & @denofevil  could you please confirm that the releases are valid. And could you please consider either update the repo or change link to the correct repo for the gem.

Please, see https://github.com/ruby-debug/debase-ruby_core_source
I've gathered all debugger-related projects in  https://github.com/ruby-debug/ and maintaining there. No worries.

@hurricup in that case I think gemspec should be updated so rubygems page will direct to correct repo

Done, thank you. Missed that.

Thank you!
I think it's better to relase new version of gem, so it will display correct info on rubygems page and we can close all question regarding owners of this gem
But it's up to you, if you really want make a release


Flutter install Error：ADB exited with exit code -15

Steps to Reproduce

Create a flutter App via Android Studio，launch emulator and run App.
Just like this:
image
Only crashed on Android.
Logs

Launching lib/main.dart on Android SDK built for x86 in debug mode...
Initializing gradle...
Resolving dependencies...
Running Gradle task 'assembleDebug'...
Built build/app/outputs/apk/debug/app-debug.apk.
Installing build/app/outputs/apk/app.apk...
Error: ADB exited with exit code -15

Error launching application on Android SDK built for x86.

Duplicate of #https://github.com/flutter/flutter/issues/30847


Update README-Chinese.md

Adding language bar to make it consistent with README.md

Changes made in patch


Publish Plugin to Maven Repository

Currently it's extremely difficult to include the plugin in a maven project.
Would you be able to publish this to maven repository in addition to github?
Currently we include other plugins published on maven in our project through this format:
open-korean-text:elasticssearch-analysis-openkoreantext:${elasticsearch.version}.2
Which bin/elasticsearch-plugin install will look at maven for.

@keepcosmos Can you register and publish this in the public maven repository?

@jaemoore @nlpenguin Sure, I will

@jaemoore
Thanks for waiting, Check https://search.maven.org/#search|ga|1|a%3A"elasticsearch-analysis-openkoreantext"

Thanks!


Port remaining ConcurrentSnapshotsIT test cases

ConcurrentSnapshotsIT is still missing several test cases from ES v7.10.2

[ ] testQueuedDeletesWithOverlap
[ ] testQueuedOperationsOnMasterRestart
[ ] testQueuedOperationsOnMasterDisconnect
[x] testQueuedOperationsOnMasterDisconnectAndRepoFailure
[ ] testQueuedOperationsAndBrokenRepoOnMasterFailOver
[ ] testQueuedSnapshotOperationsAndBrokenRepoOnMasterFailOver
[ ] testQueuedSnapshotOperationsAndBrokenRepoOnMasterFailOver2
[ ] testQueuedSnapshotOperationsAndBrokenRepoOnMasterFailOverMultipleRepos
[x] testMultipleSnapshotsQueuedAfterDelete
[x] testQueuedSnapshotsWaitingForShardReady
[x] testBackToBackQueuedDeletes
[x] testQueuedOperationsAfterFinalizationFailure
[x] testStartDeleteDuringFinalizationCleanup
[x] testEquivalentDeletesAreDeduplicated
[x] testMasterFailoverOnFinalizationLoop
[x] testStatusMultipleSnapshotsMultipleRepos
[x] testInterleavedAcrossMultipleRepos
[x] testMasterFailoverAndMultipleQueuedUpSnapshotsAcrossTwoRepos
[x] testConcurrentOperationsLimit

See:

https://github.com/crate/crate/pull/13478
https://github.com/crate/crate/pull/13483

FYI, testEquivalentDeletesAreDeduplicated seems flaky
1_Test CrateDB SQL on ubuntu-latest.txt

@jeeminso Thx, I think this: https://github.com/crate/crate/pull/13755 will address the issue.

Remaining cases can't easily ported due to missing repositoryData cache. Closing this for now


Fix _kore_to_kast

Fixes a bug introduced in #775

consider adding a regression test if there's one that can be conveniently derived from the original discovery of the issue

Added a profile test for the problematic term.


Document multiple build environments for Middleman

This is part of v4 and should ideally be integrated into our setup, so that we can produce smarter sites
https://github.com/middleman/middleman/pull/1293

<% if build? %>
Stick your scripts here
<% end %>


[New feature] Allowing the ListView slivers to have different extents while still having scrolling performance

Fixes https://github.com/flutter/flutter/issues/113431
Currently we only support specifying all slivers to have the same extent.
This patch introduces an itemExtentBuilder property for ListView, allowing the slivers to have different extents while still having scrolling performance, especially when the scroll position changes drastically(such as scrolling by the scrollbar or controller.jumpTo()).
@Piinks Hi, Any thoughts about this?  :)

Hello please approve

Thank you so much for your great work !

@Piinks Hi, Thank you very much for reviewing.
Hope you guys enjoyed your trip to Shanghai last week : )
Oh, by the way, I have recently been trying to introduce a caching mechanism to ListView to reduce unnecessary layout operations to further optimize its scrolling performance. I hope to find a better solution.
发件人: Kate Lovett @.>
发送时间: 2023年9月12日 8:29
收件人: flutter/flutter @.>
抄送: 徐宝林(Ava) @.>; Author @.>
主题: Re: [flutter/flutter] [New feature] Allowing the ListView slivers to have different extents while still having scrolling performance (PR #131393)
@Piinks approved this pull request.
LGTM! I am really excited for folks to have this, thank you so much for your work on this! 🎉
—
Reply to this email directly, view it on GitHubhttps://github.com/flutter/flutter/pull/131393#pullrequestreview-1621053588, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOR66GBPUMFRG2IH6KLUPMTXZ6UDJANCNFSM6AAAAAA2ZV6CVM.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>
OPPO
本电子邮件及其附件含有OPPO公司的保密信息，仅限于邮件指明的收件人（包含个人及群组）使用。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件，切勿传播、分发、复制、印刷或使用本邮件之任何部分或其所载之任何内容，并请立即以电子邮件通知发件人并删除本邮件及其附件。
网络通讯固有缺陷可能导致邮件被截留、修改、丢失、破坏或包含计算机病毒等不安全情况，OPPO对此类错误或遗漏而引致之任何损失概不承担责任并保留与本邮件相关之一切权利。
除非明确说明，本邮件及其附件无意作为在任何国家或地区之要约、招揽或承诺，亦无意作为任何交易或合同之正式确认。 发件人、其所属机构或所属机构之关联机构或任何上述机构之股东、董事、高级管理人员、员工或其他任何人（以下称“发件人”或“OPPO”）不因本邮件之误送而放弃其所享之任何权利，亦不对因故意或过失使用该等信息而引发或可能引发的损失承担任何责任。
文化差异披露：因全球文化差异影响，单纯以YES\OK或其他简单词汇的回复并不构成发件人对任何交易或合同之正式确认或接受，请与发件人再次确认以获得明确书面意见。发件人不对任何受文化差异影响而导致故意或错误使用该等信息所造成的任何直接或间接损害承担责任。
This e-mail and its attachments contain confidential information from OPPO, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you are not the intended recipient, please do not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.
Electronic communications may contain computer viruses or other defects inherently, may not be accurately and/or timely transmitted to other systems, or may be intercepted, modified ,delayed, deleted or interfered. OPPO shall not be liable for any damages that arise or may arise from such matter and reserves all rights in connection with the email.
Unless expressly stated, this e-mail and its attachments are provided without any warranty, acceptance or promise of any kind in any country or region, nor constitute a formal confirmation or acceptance of any transaction or contract. The sender, together with its affiliates or any shareholder, director, officer, employee or any other person of any such institution (hereinafter referred to as "sender" or "OPPO") does not waive any rights and shall not be liable for any damages that arise or may arise from the intentional or negligent use of such information.
Cultural Differences Disclosure: Due to global cultural differences, any reply with only YES\OK or other simple words does not constitute any confirmation or acceptance of any transaction or contract, please confirm with the sender again to ensure clear opinion in written form. The sender shall not be responsible for any direct or indirect damages resulting from the intentional or misuse of such information.

Hope you guys enjoyed your trip to Shanghai last week : )

Absolutely! Meeting each other was a highlight of the trip! 🎉

Oh, by the way, I have recently been trying to introduce a caching mechanism to ListView to reduce unnecessary layout operations to further optimize its scrolling performance. I hope to find a better solution.

This is really interesting, I would be happy to hear more if you are interested in pursuing it. I think in some cases caching could work, we could see what it looks like to give developers the option. Not sure. :)


Change styling of crop boarder

Is it possible to change the styling of the crop border for this project?
So far I have only been able to change the boarder of the entire area not the crop box directly

You can target the class and change the border etc

Awesome! thank you :D

I realise in hindsight the latest patch update may be a breaking change for you - the CSS was simplified to just border: 1px dashed white;


Is it possible to retrieve BigQuery Project quotas?

Hello,
Is it possible to use this library or another to retrieve the bigquery quota limits and usages?
The compute quotas for example can be retrieved using:
import { ProjectsClient } from "@google-cloud/compute"
async function getQuotas() {
  const gcpclient = new ProjectsClient()

  const [project] = await gcpclient.get({
    project: "a-test-project",
  })

  console.log(project.quotas)
}

I assume this is only the compute quotas though as when running this on a project which has BQ enabled, and has Quotas configured, Query usage per day does not appear in the list of quotas returned.
There doesn't appear to be a relevant reference to quotas in this library. It would be useful to be able to retrieve this information for monitoring purposes.
Thanks!

@atrbgithub, thanks for the question, but unfortunately currently there is no way to query quota/usage for BigQuery.

Can this be converted to a feature request?

Yes, this is a feature request — and specifically, it's a feature request for the BigQuery service to expose this information in a way that clients could consume it, rather than a feature request for this library. There are a handful of existing quota-related feature requests open in the public tracker, here: https://issuetracker.google.com/issues?q=status:open componentid:187149 quota I recommend finding the one that most meets your needs and adding a +1 or additional detail to it.
Because this isn't a feature request for this specific library, I'm going to close it out. Thanks!


Squeeze PowerShell code

Saves one line.

Codecov Report
Patch and project coverage have no change.

Comparison is base (a9059f3) 80.30% compared to head (e7cccc6) 80.30%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #441   +/-   ##
========================================
  Coverage    80.30%   80.30%
========================================
  Files           10       10
  Lines          782      782
========================================
  Hits           628      628
  Misses         154      154

Impacted Files
Coverage Δ

argcomplete/shell_integration.py
89.47% <ø> (ø)

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


Change Videos Dynamically

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Use case
Hi! i'm trying to change videos Dynamically but the package doesn´t have this feature =( any ideas? y try to do this:
Future openMedia(String url) async{
if(_videoController.value.isInitialized){
  await _videoController.dispose();
}

_videoController = VideoPlayerController.networkUrl(Uri.parse(url));
await _videoController.initialize();

return _videoController.play();

}
But it takes a lot of seconds to reinitialize!
Proposal
An option like SETVIDEO.

@AALAMILLO
I think your issue is same as https://github.com/flutter/flutter/issues/44690, so please follow-up in it for further updates.
Closing as duplicate.


Provide a docker compose file

In order to make it easy to Cognita, it would be awesome to offer & document a quick setup with docker compose and prebuilt docker containers.

@flobaader this is now done.

Awesome! Thanks.
Are you also planning to build & publish the docker images to the github or docker registry?


Update the link for qwen2

What does this PR do?
Fix link for qwen

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Thanks! I tacked on a commit to also fix the URL in the model table in the backend. This should also fix the CI failure.


Implemented the basic of a HttpClient class for HttpRequest

Proposed changes
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[x] Bugfix (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)

Checklist
Put an x in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.

[x] I have read the CONTRIBUTING documentation
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary documentation (if appropriate)

Further comments
Closes #1

I think it would be better to use the got library instead of http package to do this task @RobsonTrasel. We are going to save a lot of time because this library already implements all this thinks:

Ok, I'll be fixing this.

I made the requests using got libray, but the tests only the GET method pass because the other methods needs a paramethers in body. But it just change the paramethers for test the others methods.

 @RobsonTrasel

Check this tutorial from GitHub of how to give me the permission.

 @RobsonTrasel

Check this tutorial from GitHub of how to give me the permission.

This option it's enabled:


Publish NanoServer images

Done

While the image itself is useful is there a list of all the other cab components available for download and their locations? https://az880830.vo.msecnd.net/nanoserver-ga-2016/ isn't browsable.
https://github.com/Microsoft/iis-docker/blob/shhsu/nano/nanoserver/Dockerfile
Thanks!
Mike

Try these
https://nanoserverpackage.blob.core.windows.net/nanoserver-ga-2016/searchNanoServerIndex.txt


Fix react native tests

They're currently disabled. I'm not sure what's wrong with them.
I don't have time to work on this and I don't use react native. So we'll need contributions here.

Sorry I missed when this happened before! 🤔
Is there a point when CI failed? I'll repro this locally, but discussing over a build failure might be more helpful.

here: https://travis-ci.org/paypal/downshift/builds/437797785

I'd say this is due to React Native 0.57 changing the default Babel preset, from babel-preset-react-native to metro-react-native-babel-preset: https://github.com/react-native-community/react-native-releases/issues/34#issuecomment-407006185
I'll pick this one up real quick and see what I can find.

Here's a better link to the changes that need to happen: https://github.com/react-native-community/react-native-releases/blob/master/CHANGELOG.md#updating-to-this-version

Hmmm, upgrading only the Babel preset doesn't seem to address all the issues, as I still get the following error after running yarn remove babel-preset-react-native && yarn add --dev<EMAIL_ADDRESS>&& yarn run jest --projects other/misc-tests other/react-native
  ● Console

    console.error node_modules/react-test-renderer/cjs/react-test-renderer.development.js:6884
      The above error occurred in the <mockConstructor> component:
          in mockConstructor (at onChange-tests.js:19)
          in View (created by Component)
          in Component (at onChange-tests.js:9)
          in RootView (at onChange-tests.js:18)
          in Downshift (at onChange-tests.js:16)

      Consider adding an error boundary to your tree to customize error handling behavior.
      Visit https://fb.me/react-error-boundaries to learn more about error boundaries.

  ● calls onChange when TextInput changes values

    Cannot find module 'schedule/tracking' from 'ReactNativeRenderer-dev.js'

      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:221:17)
      at node_modules/react-native/Libraries/Renderer/oss/ReactNativeRenderer-dev.js:29:20
      at Object.<anonymous> (node_modules/react-native/Libraries/Renderer/oss/ReactNativeRenderer-dev.js:16199:5)

Aaaaaand one more bit of sleuthing to discover some more context here: https://github.com/facebook/react-native/issues/21150#issuecomment-427768751
I ran yarn add --dev<EMAIL_ADDRESS>followed by yarn run jest --projects other/react-native and got the following:
❯ yarn run jest --projects other/react-native
yarn run v1.10.1
$ /Users/eliperkins/src/downshift/node_modules/.bin/jest --projects other/react-native
 PASS  other/react-native/__tests__/onBlur-tests.js

 RUNS  other/react-native/__tests__/onChange-tests.js
/Users/eliperkins/src/downshift/dist/downshift.native.cjs.js:1035
      var downshiftButtonIsActive = _this4.props.environment.document.activeElement.dataset.toggle && _this4._rootNode && _this4._rootNode.contains(_this4.props.environment.document.activeElement);
                                                                      ^

TypeError: Cannot read property 'activeElement' of undefined
    at Timeout._onTimeout (/Users/eliperkins/src/downshift/dist/downshift.native.cjs.js:1035:71)
    at ontimeout (timers.js:427:11)
    at tryOnTimeout (timers.js:289:5)
    at listOnTimeout (timers.js:252:5)
    at Timer.processTimers (timers.js:212:10)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I'm out of time to look at this further tonight, but I'd say we've got some pretty hairy version mismatches to unwind here, along with a wee bit of platform mismatch in usage of things like document for certain platforms.
If someone wants to pick this up before me, feel free! Otherwise, I can pick this up at my next free moment.


Feat / Fix: BIMData Design System plugin

fix: plugin factory to include directives properly
feat: update build config and add vue3 compatible plugin

:tada: This PR is included in version 1.2.0-rc.28 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Move this condition to the stage

Currently this condition is evaluated after stage is started but it should be before. In pipeline view it looks like it was executed as first job was started. Moving it to stage condition should solve the issue
Move this condition one level up to the stage (instead of job)
https://github.com/proofdock/chaos-azure/blob/449e01f00705280d93b3b104101c0a1df88f889d/.pipelines/deploy.latest.yml#L31

Sounds good


Update README.md

Got my BTL305 working with the scripts as well. It's slightly different from the BTL300.

Thanks for your Feedback.


Redo the docs site, making it easier to understand

@ascott1 can you track your cf-content stuff here instead of in that rep you made? Jus plop it into the main description of this issue.

@ascott1, feel free to do the honors of closing this one! Nice work!

:dancers:


How to use this in storybook or E2E tests

I am getting the below error when I try to run this with a storybook test.
"Error: zone-testing.js is needed for the async() test helper but could not be found. Please make sure that your environment includes zone.js/dist/zone-testing.js".
If it cannot be used in storybook/E2E tests, can you please update the documentation to say this or if it can can you please add some information to describe how to get it working.
To reproduce the error:

Clone https://github.com/srlee309/component-commands-example
Run: ng run storybook-example-form:storybook-e2e

This is the spec that is failing.
https://github.com/srlee309/component-commands-example/blob/master/libs/example/form/.cypress/src/integration/storybook/form-component-test-harness.spec.ts
import '@jscutlery/cypress-harness/support'; is in the index.
https://github.com/srlee309/component-commands-example/blob/master/libs/example/form/.cypress/src/support/index.ts

Hi @srlee309! Thank you for the feedback.
There is in fact an issue with @jscutlery/cypress-harness when used to test an application instead of a single component with @jscutlery/cypress-mount.
Apparently, this happens because:

@jscutlery/cypress-harness depends on @angular/cdk/testing's UnitTestComponent (Cf. https://github.com/angular/components/blob/5cc960157a3260c90bfd7e5f442d7979c577605c/src/cdk/testing/testbed/unit-test-element.ts)
@angular/cdk/testing imports @angular/core/testing which in its turn imports before_each.ts that contains the following side effect:
https://github.com/angular/angular/blob/a6971ba89adc253bfa4260036ee4a1e0bd76159f/packages/core/testing/src/before_each.ts#L23-L28
that tries to reset fake async zones while we are not even using fake async zones.

We'll be providing a fix soon but meanwhile, here's a workaround; you can add the following code to your support/index.ts:
import 'zone.js/dist/zone';
/* @hack fixes "Mocha has already been patched with Zone" error. */
(globalThis as any)['Mocha']['__zone_patch__'] = false;
import 'zone.js/dist/zone-testing';

Thank you for detecting this issue. Please, let us know if this works for you.

Hi @srlee309! Thank you for the feedback.
There is in fact an issue with @jscutlery/cypress-harness when used to test an application instead of a single component with @jscutlery/cypress-mount.
Apparently, this happens because:

@jscutlery/cypress-harness depends on @angular/cdk/testing's UnitTestComponent (Cf. https://github.com/angular/components/blob/5cc960157a3260c90bfd7e5f442d7979c577605c/src/cdk/testing/testbed/unit-test-element.ts)
@angular/cdk/testing imports @angular/core/testing which in its turn imports before_each.ts that contains the following side effect:
https://github.com/angular/angular/blob/a6971ba89adc253bfa4260036ee4a1e0bd76159f/packages/core/testing/src/before_each.ts#L23-L28
that tries to reset fake async zones while we are not even using fake async zones.

We'll be providing a fix soon but meanwhile, here's a workaround; you can add the following code to your support/index.ts:
import 'zone.js/dist/zone';
/* @hack fixes "Mocha has already been patched with Zone" error. */
(globalThis as any)['Mocha']['__zone_patch__'] = false;
import 'zone.js/dist/zone-testing';

Thank you for detecting this issue. Please, let us know if this works for you.

v0.2.0 has been published with the fix

v0.2.0 has been published with the fix


Set up continuous integration so it run unittests on each PR

And tells us if a given PR fails tests e.g. because of improper formatting or missing fields in .md files

Is there a tutorial of how to set up automated unit testing? Would it work via the "webhooks"?

tutorial: https://docs.travis-ci.com/user/getting-started/
continuous integration and testing are two different things.
You write the tests. You can run those tests yourself if you want.
One of the things continuous integration does is run the tests e.g. on every PR.
It also does other things, like try to build the entire package/library to ensure the build still works.

Anyone who has the Github developer pack gets free CI, through Travis and I think also Circle?


Defang Grep

It would be useful to be able to either:
defang grep <search>

or
defang tail --grep <search>

Personally I think I tend toward the latter, because I would probably be in the mental context of "I'm looking at logs, actually I need to find something more specific" before I get to grep. It might also be easier because all of the other logic that applies to tail should still make sense (i.e. specifying since, etag etc.)

In #459 we want to separate "tail" vs "query".
I personally would want an interactive grep (press / to search)

Better to fix #161 and encourage | grep


Choose deduplication strategies

This PR adds the possibility to specify what deduplication method can be used. By default deduplication is based on persistent identifiers and text. This PR adds possibility to choose only one of the two and makes it easier to implement extra options in the future.
Also added extra tests for this.

This PR is nice but needs some restructuring to get things more Pythonic. I will close the PR for now. Feel free to reopen or if anyone reading this is interested to work on this, let us know.


[Planning] Forward an invoice to someone else

Forwarding an invoice to someone else
When an invoice receiver elects to forward an invoice to someone else to pay after tapping the Pay button on an invoice preview, the user will go down a new flow to forward the invoice:

Invoice Receiver taps pay > forward to someone else
The user is prompted to input an email address or phone number in the To: field using the standard participant selector.
The invoice remains as being Sent from the original invoice sender email address
Forwarding the invoice triggers a system message from the original receiver:

Forwarding the invoice triggers an IOU request whisper message to the new invoice receiver
This matches the same flow a invoice receiver would expect if the invoice was sent to them without being forwarded.
The invoice report preview component in the invoice room stays in its original position in the chat history.
A system message from the inviter is added to the invoice room to note that someone new has been invited to the room.
The invoice room displays a GBR  for the new receiver of the invoice, so the invoice room in the LHN gets a green dot.

Notes for completion
The new invoice receiver will go down the same pay elsewhere highlighted earlier in the doc, nothing changes there.
Forwarding an invoice invites the new receiver into the existing invoice room.
The room title will update to reflect the new invoice receiver’s workspace or email address if a workspace doesn’t exist
The new invoice receiver has the opportunity to forward the invoice to another user, creating an unlimited number of forwards, and setting us up for bill forwarding later on 😉

This is being punted as a separate project. I am keeping it open as a reminder to add it to the VIP roadmap discussion in August.


Start on ccache for slate-client-release.yml.

See #106 for more details.

Tested in https://github.com/slateci/slate-client-server/actions/runs/3716788468. Something to note is the /bin/tar: unrecognized option: posix error in the Post Set up ccache step. I tried adding tar to the image in the hops of overwriting the busybox flavor of tar but that didn't seem to fix this. Good news is the build is pretty fast anyway.


Stylesheet refactor

standardize class nomenclature
consolidate redundant sections
Nav bar: fix spacing of links
Aside: fix header text orientation

Be sure to update class/ID items to the 'best practice' naming convention

done


Fix lack of clippy on nix

Overrode the rust package so it'll install clippy

This is awesome, thank you. I did some testing and you don't need the override, so it can just be:
            nativeBuildInputs = [ pkgs.rust-bin."${rust-toolchain}".latest.default ];

Also, I don't believe this part of magmawm.nix is doing anything:
  rust = pkgs.rust-bin."${rust-toolchain}".latest.default.override {
    extensions = [
      "cargo"
      "clippy"
      "rust-src"
      "rustc"
    ];
  };

I think it can just be removed.


Created an Assertion for StatusCodeShouldBeSuccess

Unsolicited contribution - but I often want to be a little fuzzy on asserting status codes (a 200 is as good as a 201, or a 204, for example). I added an assertion for api.StatusCodeShouldBeSuccess() that will pass if the status code is in the proper range of "success".
Since Alba's default behavior is to fail if there is no assertion on the status code and it returns anything but a 200, this seems like a good accommodation. (I'd prefer the default was this, but I get why others wouldn't, and don't want a breaking change anyhow).
I've had this as my own custom assertion for a while, and don't mind keeping it that way, but if it is helpful, take it.

Thanks for the PR!


Initial regeneration on restore is never retried

When an endpoint is restored from disk it must be regenrated. It will currently depend on another regeneration trigger for that endpoint to appear. This has become more serious as most triggers are not rebuilding the BPF layer.
        for _, ep := range state.restored {
                go func(ep *endpoint.Endpoint, epRegenerated chan<- bool) {
                        if err := ep.RegenerateAfterRestore(); err != nil {
                                epRegenerated <- false
                                return
                        }
                        epRegenerated <- true
                }(ep, epRegenerated)
        }

A few lines up:
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/daemon/cmd/state.go#L259-L263
...
Expose():
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/pkg/endpoint/manager.go#L56
...
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/pkg/endpoint/policy.go#L586-L592
At least from this perspective we will retry regeneration at least until the endpoint is deleted.

Why might the endpoint be deleted?
Well, as part of NewDaemon() we have:
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/daemon/cmd/daemon.go#L444-L447
->
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/daemon/cmd/state.go#L165-L178
So if validateEndpoint() believes that the endpoint no longer exists for whatever reason, it will quietly add it to a list of endpoints to clean up:
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/daemon/cmd/state.go#L44-L50

Later, after restoreOldEndpoints() already ran, we call into regenerateRestoredEndpoints() (via runDaemon()) and that's how we end up around the point where the issue description starts, and more specifically at a point where we may actually delete the endpoint and stop the regeneration retries:
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/daemon/cmd/daemon_main.go#L1280
->
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/daemon/cmd/state.go#L344-L351
->
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/daemon/cmd/state.go#L266-L292
In particular line 285 where the endpoint is deleted, which closes a context that we use to stop the regeneration retry controller.
So from this analysis, it seems to me that the only reason that we would not try regenerating again is if we think that the endpoint is invalid (whether because we can't find the endpoint in k8s, or the link disappears, or we can't allocate the same IP upon restart, or another reason). Specifically somewhere in this function:
https://github.com/cilium/cilium/blob/3c25373901605acb9d8615ae2f0ba68e5a78ac18/daemon/cmd/state.go#L50

From Slack via @aanm :

whether because we can't find the endpoint in k8s

The bug is here. Right now it seems that the endpoint is considered gone if we can't connect to k8s.


Updating doc generator examples

This PR address issue #11.
I added a new example showing how to add a new broker to the supervision hierarchy on Elixir >= 1.5. Kept the example for older Elixir versions for compatibility purposes.
New output:
Add conduit_amqp to your dependencies in mix.exs:

    {:conduit_amqp, "~> 0.4"}

Make sure to add the following to your config.exs:

    config :conduit, ConduitQueue.Broker,
      adapter: ConduitAMQP,
      url: "amqp://guest:guest@localhost:6782"

Also, add your broker to the supervision hierarchy in your conduit.ex:

Elixir v1.5 or above:

    def start(_type, _args) do
      children = [
        # ...
        {ConduitQueue.Broker, []}
      ]

      supervise(children, strategy: :one_for_one)
    end

Elixir v1.4 or below:

    def start(_type, _args) do
      children = [
        # ...
        supervisor(ConduitQueue.Broker, [])
      ]

      supervise(children, strategy: :one_for_one)
    end

Thanks!


Admin can create user with the same email

The system admin can create users with the same email

Fixed


trained  pt files convert  pre_post_processing.onnx file Predict no result

The pre_post_processing.onnx files obtained by converting yolo11n.pt or yolov8n.pt with yoloe2e can be used correctly, but the pt files trained by me with data sets cannot Detection objects correctly after conversion, and the converted ONNX files can also be predicted. But the pre_post_processing.onnx file has no result
Predict with best.onnx

Predict with pre_post_processing.onnx

here is my .pt file
https://github.com/FengYanNMG/NewRepo/blob/master/best.pt

@wenbingl

I'm sure there's something wrong with my model, but I don't know where the problem lies.


Add options to networkStats, to enable/disable default ifacename

networkStats ignores the iface argument and returns the default iface.
Usage:
si.networkStats()
// { iface: 'wlp2s0',

si.networkStats({
  iface: 'custom-iface'
})
// { iface: 'wlp2s0',

si.networkStats({
  iface: 'custom-iface',
  useDefaultIface: false
})
// { iface: 'custom-iface',

Hi @d30jeff,
As I am just trying to clean up issues, pull request, ... I have on question on this one:
Seems that I do not get the point here. The original idea was, if you do not pass any iface as a parameter, this function returns metworkStats for the default interface, and if you provide a iface parameter, you get the stats for that specific interface.
For me, your code tries to do the same, right? But you are providing an option parameter (object) with a iface key which will be ignored when not adding useDefaultIface: false to the option parameter.
What was your idea of providing an iface key to the option parameter without having useDefaultIface: false? In my original code this would be the same as when not providing any iface-parameter. I do not get the difference (except having the parameters as an option object).
Thank you for any answer on that.

If you don't mind, I'll close this for now, OK?


Lots of Webdriver Tests are not Run

Chrome runs a lot of webdriver tests, but firefox, edge and safari do not: http://wpt.fyi/webdriver

Looks just like #90?

Safari and Edge aren't yet supported for WebDriver tests. Adding support is pretty trivial but they are likely to ERROR on all tests until they fix basic conformance issues in their implementations (or I add hacks to make them work with tests that aren't specifically about the protocol).

@gsnedders You are right, closing this as a duplicate
@jgraham That's true, but why isn't it running for geckodriver on firefox?


Tweak npm scripts.

make css and js "super" scripts which will run both main and docs scripts
make js-minify run all js minify tasks
use parallel in more places

It's a first pass but I think it covers more cases than before.
Suggestions to improve this are welcome!
Fixes #24121

So what should I do with this, guys?
@mdo @bardiharborow @Johann-S


Adding a contribution

Adding my own version,  They evolve size which speed is derived from.  The faster they are, they faster they lose health.
Predators are white and evolve the best prey to choose.  Their cloning rate is dependant on their health, so if there is lots of prey they multiply quickly.
Note: This is my first foray with GitHub so apologies if I've done it wrong

It's now saying there is a conflict. Shall I resolve it, or does admin do that?

@btb331 go ahead and resolve!

Thanks Daniel! I've resolved the conflict now so should be all good. :)

Looks great, thank you!

Did you look at my example? Did you like it?

yes, it's amazing! Love all the stats.


Setting Site URL doesn't change most site links from localhost:

cachet_ver: v2.3.13
docker version: 17.09.0-ce
docker-compose version: 1.17.1
I have just set up the docker image on a cloud server, and have set it up behind an nginx reverse proxy with SSL as mentioned at the bottom of this page. After having completed the initial setup, almost all the links still start with localhost:6789.

This shows the Site URL set by me, but when I hover over 'components' on the left panel I am still directed to localhost:6789/dashboard/components
From reading other github issues this seems related to Cachet issue #1545
Does anyone have any suggestions?

I just experienced the same issue. Fresh docker setup running behind an nginx reverse proxy. I tried to add the ENV Variables APP_URL and TRUSTED_PROXIES - both did not help. What are we missing?
Thanks for any hints,
Johannes

If you are still interested, I posted a Dockerfile example that fixes (in an ugly way) this issue: https://github.com/CachetHQ/Cachet/issues/3952


RFC: Consistency and Control

Breaking changes are painful. I try to avoid them whenever possible. Getting vx to v1 means I need to make a larger breaking change than I am typically comfortable with as a library author. In short, I made a poor design decision in the early days of this library that I now wish to fix. I hope you'll agree with me that it's for the best and will lead to a brighter future with more consistency and control.
Summary
This pull request does the following:

[x] removes two utility functions used by vx components: additionalProps() and callOrValue()
[x] adds the more common react pattern of render props to components impacted by the removal of the above two utils.
[x] removes scale props in favor accessors that return scaled values
[x] adds more PropTypes
[x] adds more tests
[x] update all vx-demo.now.sh/gallery tiles to new api

Motivation
Almost 2 years ago I started working on a library of components that brought together react and d3 at a lower-level than traditional charting libraries. Unfortunately, I made an api design choice that I've regretted for a long time now and it is time to rectify before releasing v1.
Data Binding Before
Initially I thought the target audience would be existing d3 developers that found themselves in a react codebase. So I went about making an api that would feel similar to d3 when it came to data binding.
Let's walk through an example of rendering out a series of bars that are different colors based on each datum's name. (data = [{ name: 'captain gary' }, // ...])
// d3
svg.append("g")
 .selectAll("rect")
 .data(data)
 .enter().append("rect")
  .attr("fill", datum => color(datum.name))

So one coffee-fueled morning I thought "fine I'll bind props to data in react if you pass a function as a prop"
// vx
<Bars
  data={data}
  fill={datum => color(datum.name)}
/>

But wait, what about props that are typically functions like event handlers? Say you wanted to click on each colored bar and alert the bar's name. Well you would just pass a function that returns your click handler with the datum as the first argument.
// vx
<Bars
  data={data}
  fill={datum => color(d.name)}
  onClick={datum => event => {
   alert(d.name);
  }}
/>

🤦♂ 🤦♂
What's so bad about this? It no longer feels like react. vx components become special in the sense you need to know about this silly pattern and it's not like other react components. This is confusing: https://github.com/hshoff/vx/issues/50 https://github.com/hshoff/vx/issues/199 https://github.com/hshoff/vx/issues/328
Data Binding After
Then came the realization that the target audience for vx was really react developers that needed data visualization without having to learn d3.
Seems like a confusing api tradeoff for the added ability of setting a prop based on a datum value. Along came render props. Let's take a look at what the new api looks like with render props.
<Bars
  data={data}
  // ...
>
   {bars => {
    return bars.map((bar, i) => {
      return (
        <rect
          key={bar.name}
          fill={color(bar.name)}
          onClick={event => alert(bar.name)}
        />
      );
     })
   }}
</Bars>

This means vx components are no longer opaque boxes with special rules. You now have more control over what's rendered and it's more transparent how it works following common patterns in react land.
This is a change I've wanted to make for a long time. It took a lot boring work to make it happen, but I think it's finally ready.
What about Hooks?
I was just as surprised as everyone else about the react Hooks announcement at ReactConf. The day they were announced, I was finishing migrating all of the gallery tiles to the new api and I had the panic moment of, "oh no this new api is going to be dead-on-arrival".
The Hooks announcement talked about how hooks can replace render props with the benefit of not introducing a false hierarchy to your render. This is great and I look forward to updating vx to include hooks. That said, Hooks are still a proposal available on an alpha release of react. Currently, vx supports react 15 and 16. vx will look to support hooks in a future release. I see the render props api as an immediate improvement for all users of vx where hooks would only support those lucky enough to be in a codebase on 16.7 alpha.
Initial thoughts are hooks are the future of react, so vx will support them when they are more widely available.
Accessors + Scales Before
In the beginning, I found myself often having to apply my scale on the accessor value. So I turned this into a pattern in vx. You would pass in your scale and your accessor separately and vx would apply them for you. It used look like this:
 <LinePath
  data={data}
  xScale={xScale}
  yScale={yScale}
  x={x}
  y={y}
/>

behind the scenes vx would create a line path from d3-shape's line generator
const path = line()
  .x((...args) => xScale(x(...args)))
  .y((...args) => yScale(y(...args)))
  .defined(defined)
.curve(curve);

Again this isn't transparent. Let's make it transparent.
Accessors + Scales After
<LinePath
  data={data}
  x={d => xScale(x(d))}
  y={d => yScale(y(d))}
/>

This api simplifies what vx is doing behind the scenes as well to:
const path = line();
if (x) path.x(x);
if (y) path.y(y);
if (defined) path.defined(defined);
if (curve) path.curve(curve);

This gives transparency, consistency with the d3 api, and gives you more control over shape generation.
Closing thoughts
I worry about the early adopters that are not going to be happy about having to update their code due to these breaking changes, but the longer the I wait to make this the bigger the hill will be to climb.
Would love to hear your thoughts.
Changelog
:boom: Breaking Changes

[glyph][breaking] rm additionalProps, add children as fn
[shape][breaking] rm additionalProps, add children as fn
[geo][breaking] rm additionalProps, add children as fn
[heatmap][breaking] rm additionalProps, add children as fn
[stats][breaking] rm additionalProps, add children as fn
[boxplot][breaking] rm additionalProps, add children as fn
[voronoi][breaking] rm additionalProps, add children as fn
[legend][breaking] rm additionalProps, add children as fn

:house: Internal

[demo] update gallery tile examples to new apis

cc @williaster @conglei @techniq

Should be consider dropping our HOCs as part of this breaking change?  See: https://github.com/hshoff/vx/issues/220

But wait, what about props that are typically functions like event handlers?

I always kind of liked the datum => event => {} style. It worked well if one doesn't have to customize the rendered component that much. If I understand it correctly, with the new API, one has to always render the actual SVG and vx just provides the data. This makes a lot of sense in the low-level nature of vx.
For the repo I'm working on it isn't a big deal so go for it. I like it when things get more consistent and changes will reduce overall confusion for new users! We use vx since v0.0.158.
The scale and accessor change is really nice as well. More power to the user.
Nice job on the proposed changes and that's quite some work you had to do there 😅!


Never triggered  buildStarted in custom BuildListener (BuildAdapter)

I tried all I know and I found on the net to get the buildStarted() method called in my custom BuildListener. The behaviour of the BuildListener is of course different depending where the listener is added to gradle (ie. in build.gradle or in a gradle init script). But nether way I get the method called.
All other methods in the BuildListener where called as expected in the expected point in execution time.
For my tests I used the bellow class with a different "message" prefix to separate them. I added the class in ether a build script and a init script (selects by the --init-script switch):
Content of listeners.gradle (and added to listeners.initd.gradle too):
class MyBuildListener extends org.gradle.BuildAdapter {

    def buildListener = [:]

    void buildFinished(BuildResult result) {
        buildListener.buildFinished = "INIT.D +++ Finished with action $result.action"
        displayExecuteBuildListeners()
    }

    def displayExecuteBuildListeners() {
        println buildListener.collect { method, message ->  "\t${method.padRight(24)} => $message" }.join("\n")
        println "\t${'-'*64}"
    }

    void buildStarted(Gradle gradle) { buildListener.buildStarted = "INIT.D +++ Build started..." }

    void projectsEvaluated(Gradle gradle) { buildListener.projectsEvaluated = "INIT.D +++ Projects evaluated..." }

    void projectsLoaded(Gradle gradle) { buildListener.projectsLoaded = "INIT.D +++ Projects loaded..." }

    void settingsEvaluated(Settings settings) { buildListener.settingsEvaluated = "INIT.D +++ Settings evaluated from $settings.rootDir" }
}

gradle.addBuildListener(new MyBuildListener())

On the other side I cloned the Gradle repository. Checked out tag v4.2.1 and run the DefaultGradleSpec test within IntelliJ and all tests pass (as expected). So what do I wrong?
Expected Behavior

I would expect that the final output does contain the line: buildStarted             => INIT.D +++ Build started....
$ gradle --init-script listeners.initd.gradle -S clean build

BUILD SUCCESSFUL in 19s
12 actionable tasks: 10 executed, 2 up-to-date
        settingsEvaluated        => INIT.D +++ Settings evaluated from /Users/pkern/Google Drive/GradleBuildListenerExample
        buildStarted             => INIT.D +++ Build started...
        projectsLoaded           => INIT.D +++ Projects loaded...
        projectsEvaluated        => INIT.D +++ Projects evaluated...
        buildFinished            => INIT.D +++ Finished with action Build
        ----------------------------------------------------------------
        projectsEvaluated        => BUILD  +++ Projects evaluated...
        buildFinished            => BUILD  +++ Finished with action Build
        ----------------------------------------------------------------

Current Behavior

All went as almost expected except that there is no output line dedicating that the buildStarted method was called!
$ gradle --init-script listeners.initd.gradle -S clean build

BUILD SUCCESSFUL in 19s
12 actionable tasks: 10 executed, 2 up-to-date
        settingsEvaluated        => INIT.D +++ Settings evaluated from /Users/pkern/Google Drive/GradleBuildListenerExample
        projectsLoaded           => INIT.D +++ Projects loaded...
        projectsEvaluated        => INIT.D +++ Projects evaluated...
        buildFinished            => INIT.D +++ Finished with action Build
        ----------------------------------------------------------------
        projectsEvaluated        => BUILD  +++ Projects evaluated...
        buildFinished            => BUILD  +++ Finished with action Build
        ----------------------------------------------------------------

Context

There are different things I try to do with the buildStarted listener. One of it is to trigger the execution of a second tool as soon as the build starts to do some work.
For example:

Update or init some subprojects kept in a GIT submodule which may contain further build scripts.
"Decorate" the org.gradle.api.internal.project.DefaultProject ie. the findProperty() method to also search the System for requested property. Or add some more global methods to the class with Groovy metaclass feature.
Of course this is just for convenient and I know there are other ways like usage of the extension on Project or to decorate use the ProjectEvaluationListener and decorate on the instance itself than on the class.

But I'm almost more curious what I missed or what I'm doing wrong to access this listener. :-)
Steps to Reproduce (for bugs)

I attached a little example project (reduction of a sample project from the Gradle docs' repo). Just extract the content an run it with:
gradle --init-script listeners.initd.gradle -S clean build
Hoppe this is what you need to reproduce my issue. If you need more just drop my a message.
GradleBuildListenerExample.zip
Your Environment

$ gradle -v
------------------------------------------------------------
Gradle 4.2.1
------------------------------------------------------------

Build time:   2017-10-02 15:36:21 UTC
Revision:     a88ebd6be7840c2e59ae4782eb0f27fbe3405ddf

Groovy:       2.4.12
Ant:          Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM:          1.8.0_144 (Oracle Corporation 25.144-b01)
OS:           Mac OS X 10.12.6 x86_64

$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.12.6
BuildVersion:	16G1114

$ java -version
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)

There is no way for users to hook in before the build starts, this method is mostly used by internal listeners in Gradle. The build starts before any scripts are evaluated.
What kind of tool are you trying to call, what's the use case? "As soon as Gradle does some work" is a bit vague. The real work only starts during task execution.

Thanks for the reply.
It does in deed already answer my main question about the usage meaning of this API method.
I'm still a bit curious why such a method exist and doesn't contain any comment about the meaning of almost only internal usage for this method on the BuildListener. I understand of course that the method is called very, very early in the build as I would expect by it's name. :-)
About the a bit vague use case see my edits above. But as I denoted in this comment my main question about the usage of this method is already answered.
If you could tell me if a plugin implementation would have access to this method or if there are any other potential ways to get a custom closure executed somehow with this method this question (issue) can be closed.
Many thanks anyway for your time.

I don't think there is any way for non-Gradle code to hook into buildStarted. For your use case above I think settingsEvaluated should work as well. Or you could just do the work right in your init script (i.e. without waiting for a callback), since that is a s close as you'll get to the start of the build.

If it belongs to a specific project, then I'd just run the code right at the start of your settings.gradle script. I had assumed you were trying to do this for multiple different projects.

You assumed right. Finally my code must work for single as well as for multiproject build. But so far I can see to place the code in the settings.gradle will work for both and therefor I'm quiet happy.
Hope I'll find soon time to verify this all (it's mostly used for a build at my company) and report back if something doesn't work. But I'm quiet sure I have now enough ways to work around.
Again. Many thanks for all your time.


AMBARI-25748: HDFS Service Check Fails in NameNode HA cluster

What changes were proposed in this pull request?
In NameNode HA cluster, hdfs service check fails, as shown in following log.

2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] {'content': StaticFile('checkWebUI.py'), 'mode': 0775}
2022-10-02 13:25:04,067 - Execute['ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 'ambari-qa', 'try_sleep': 3}
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480

The reason is that http response code is 302 when access to http://bigtop3:8480/.
And the code in checkWebUI.py at line 81 will see the reponse code 302 as a failure.
How was this patch tested?
Tested in local vm cluster, including kerberos authentication.
hdfs service check before enabling kerberos authentication .

hdfs service check after enabling kerberos authentication.

Please review Ambari Contributing Guide before opening a pull request.

https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/service_check.py#L97
Can we remove this line? seems redundant.

https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/service_check.py#L97 Can we remove this line? seems redundant.

Done


Does ract-portal-tooltip  work with<EMAIL_ADDRESS>

Is there any plan to upgrade to<EMAIL_ADDRESS>I get peerInvalid error when I try to install it in my project which has<EMAIL_ADDRESS>

It's just a warning, I've tested with react 15.1.0 and everything works. I've update the peer dependencies in the version 1.1.2 to remove the warning. Thanks for reporting!


Undocumented serde_json dependency

I'm a new to rust, so not sure if this is an actual issue or I missed some documentation somewhere, but I get a compile error saying use of undeclared crate or module serde_json when using #[schema(default = something)]] in a struct deriving ToSchema.
It's easy enough to resolve by adding serde_json manually, just couldn't find any documentation of it as a dependency or features I might be missing.
Package versions and code for minimal replication.
[dependencies]
serde = { version = "1.0.214", features = ["derive"] }
utoipa = { version = "5.1.3", features = ["uuid", "axum_extras", "macros"] }
uuid = { version = "1.11.0", features = ["serde"] }

use serde::Deserialize;
use utoipa::{IntoParams, ToSchema};

#[derive(Deserialize, IntoParams, ToSchema)]
pub struct Pagable {
    #[schema(default = 0)]
    pub page: Option<i64>,
    #[schema(default = 10)]
    pub page_size: Option<i64>,
}

Right, sure it is not mentioned, But I kind of assume that it is quite obvious to have serde and serde_json dependencies added if one is going to do anything with JSON. serde just adds the traits but serde_json does provide the implementation. And isn't it necessary if you are going to send and receive JSON by your API whether it is done with axum or actix-web.

This is the first crate I've run into where my crate has to explicitly declare a crate dependency that wasn't a behind a really obvious feature flag like serde or uuid. I think it's because the serde_json reference is used in  ToSchema derive_to_schema which uses the impl ToTokens for AnyValue but only if the struct deriving it has fields with the schema attribute.
In axum at least you can send and receive json with a feature flag without your crate having a direct serde_json dependency, at least until you need to use a serde_json::Value type somewhere.
Not really any issue, I was just confused by it, but I can probably just read up on proc_macro_derive. Closing because practically you're right. Thanks for the response.

Hello, I've been bit by this too, and yes I have projects which use actix-web and utoipa but do not need a direct dependency to serde_json :) Adding it would appear like an unused dependency to dependency linting tools.
The good practice I have stumbled upon in my proc-macro adventures in that case is to keep the macros "self-contained" by depending on <dependency> in the crate providing the derive, re-export it, and in the generated code, to reference <crate>::<dependency>::...
So in the case of utoipa, have feature macros add a dependency to serde_json, add a #[cfg(feature = "macros")] #[doc(hidden)] pub use serde_json to lib around L240 where you pub use utoipa_gen::*; and generate code with utoipa::serde_json::....
Happy to provide a PR if that sounds reasonable to you.

Great, sounds good, I was wondering something like that perhaps only a re-export for serde_json directly without any other modules in between. But I haven't got to it. Anyways thanks for submitting a PR.

About the intermediate module, as I said it is to not clutter your root crate. Those public re-exports are hidden in the docs but still show up e.g. in autocomplete in an IDE. So the gen module acts as a sort of warning hic sunt dracones that it's messy stuff for the messy macros system :smile: But it's a matter of style in the end, if you prefer to have a utoipa::serde_json module nothing forbids it.

Good point


Feature: CSS Selector, now with IE Compatibility mode!

Purpose
This feature request is proposed to solve a couple issues:

Solves #40 , CSS Generation for IE
Adds features that resolve some discussion on #76 namely, the debate over showing vanilla CSS vs. SCSS syntax. We can now have our 🍰 and eat it too!

I would really love for someone who is much more of an expert on ms-grid to take a look at my css outputs and validate they are the way these should be implemented :).
Change Summary

Added a Dropdown and data object control to select the CSS output type, CSS (Default), SCSS or IE Compatible.
Added v-if conditions to change display for SCSS nesting of child components.
Added IE Compatible CSS generation and accompanying conditional elements
Added methods to compute ms-grid span and margin values
Modified Vuex to add state objects for ms grid templates and modified mutations to populate the objects
Modified grid component to pass grid values as an object into vuex for manipulation into ms-grid

Notes
I was trying to get creative with formatting to save screen real estate, very open to suggestions on how to pretty this up. I also took liberties with the styling for the dropdown menu for CSS selection. Please let me know how we can make these look better!
Examples
Here is an example of what the changes look like. Here is the example grid:

Vanilla CSS:

SCSS:

IE Compatibility:

Thanks for the PR! I'd be willling to take a PR for IE support but don't want a lang preprocessor switcher for CSS, I'm trying to keep the tool simple. We've already made it acceptable for CSS. I'm going to close this out, feel free to resubmit with a smaller PR that just addresses IE.


Whitelist ability to specify specific guards

Hi,
First I want to say that I love this composer plugin. It really helps keeping track of not accidentally installing a bad license or an abandoned package. The check-description guard is something I like too, but is something that feels a bit conflicting with the whitelist. There are some packages that I'd like to whitelist (for example symfony/error-handler because it's included as a non-dev requirement by Laravel but the guard blocks it as it thinks it's a debug only package). However I'd only like to whitelist that package for the check-description guard, not for the check-abandoned or the check-license guards. If for some reason the package becomes abandoned, or they change the license, installation should be blocked.
So maybe the white-list options can be expanded for example like so:
{
    "name": "...",

    "extra": {
        "production-dependencies-guard": [
            "check-lock-file",
            "check-description",
            "check-license",
            "check-abandoned",

            "white-list:vendor/package-one:license,abandoned",
            "white-list:vendor/package-two",

            "accept-license:MIT"
        ]
    }
}

A change like this could be backwards compatible, where vendor/package-two still uses all guards, but vendor/package-one will only trigger when checking the license or when it's abandoned.

If I understand correctly, you are trying to configure guards for some packages individually.
The idea looks good to me, but I'm not sure about the configuration format. What do you think about this approach?
{
    "name": "...",

    "extra": {
        "production-dependencies-guard": [
            "check-lock-file",
            "check-description",
            "check-license",
            "check-abandoned",

            "white-list:vendor/package-one",
            "white-list:vendor/package-two",

           "package-guards:vendor/package-one=license,abandoned",

            "accept-license:MIT"
        ]
    }
}

here "package-guards:vendor/package-one=license,abandoned", would allow to set guards individually for each package.

That would be perfect! 😃 I have no preference in if it's part of an existing directive or a new one.
Thinking about it now, maybe an interesting question is whether someone would prefer  to specify the guards they do want or specify the guards you don't want. In my use case the most common pattern would be to want to exclude check-description, but either way is perfectly fine.


[setup.py] update minimum requirements to latest versions

fonttools from 3.9.0 to 3.9.1
glyphsLib from 1.5.2 to 1.6.0
ufo2ft from 0.4.0 to 0.4.1
MutatorMath from 2.0.2 to 2.0.3
defcon from 0.2.4 to 0.3.1
booleanOperations from 0.6.4 to 0.7.0

relevant changes from glyphsLib 1.6.0 that adress https://github.com/googlei18n/fontmake/issues/273
- [builder] Read custom category/subCategory overrides stored in .glyphs
  source files, and use them to construct GDEF classes (#154).
- [builder] Set the width of glyphs with category 'Mark' and subCategory
  'Nonspacing' to 0, and store the originalWidth in the glyphs' lib.

also, booleanOperations 0.7.0 now attempts to keep the original starting point (if it was not clipped away):
https://github.com/typemytype/booleanOperations/releases/tag/0.7.0


Add support for password remembering in SSH

Description of the new feature/enhancement

Proposed technical implementation details (optional)

There's a pile of discussion about this already. Please search before filing new issues, and please don't file blank issues. Thanks!


ILP ed25519 fulfillments

This PR solves the part of #127 that includes

[x] condition/fulfillment base files
[x] iostream tools (writer, reader, hasher, predictor)
[x] ed25519 specific fulfillments
[x] tests

more info on https://github.com/interledger/five-bells-condition/tree/feature/binary-merkle-v2

Current coverage is 84.38%

Merging #145 into develop will increase coverage by +84.38% as of 34b4335

@@            develop    #145   diff @@
=======================================
  Files             0      26     +26
  Stmts             0    1281   +1281
  Branches          0       0
  Methods           0       0
=======================================
+ Hit               0    1081   +1081
  Partial           0       0
- Missed            0     200    +200

Review entire Coverage Diff as of 34b4335

Powered by Codecov. Updated on successful CI builds.


Document how to support unicode on WSO2 IS.

Description:
Need to document how we can add support for UTF-8 characters in WSO2 Identity Server.
e.g. DB script modifications needed and various regex pattern configuration changes that are needed to support unicode.

Duplicate of https://github.com/wso2/product-is/issues/2491

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


awscli results in `aws' command error, no credentials

$ ./awscli
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help
aws: error: too few arguments
$

config.properties contains OKTA_ORG and OKTA_AWS_APP_URL.  I was prompted once for credentials but removed the credential file to test something.  Ever since then I haven't been prompted for auth on run of the jar, and ~/.aws/credentials is not repopulated.  Repo cloned and built Feb 2, approximately 11:30 AM CST.  Don't know if there's a 'stable' branch I should be cloning instead or if there's a known defect.

That’s due to my design change. awscli nows runs the aws command line with the arg list handed to it, after creating a profile session. Try running this:
./awscli sts get-caller-identity

That will run aws sts —profile {generated-profile-name} get-caller-identity after you authenticate.
You may find using the withokta command (available on master) with OKTA_PROFILE env set to be a useful alternative. It acts more like sudo and will run whatever command you specify literally instead.
env OKTA_PROFILE=prod ./withokta aws —profile prod sts get-caller-identity

You can integrate with any downstream command that uses named profiles, including things like Serverless and Terraform.

Not be re-prompted and not having the credentials file update is definitely a bug.

The master branch is the most stable release. We're incrementally fixing issues and improving the user experience.

should a present ~/.okta-aws-cli-session and absent ~/.aws/credentials be a condition the app detects and resolves?  It's not behavior people accustomed to the traditional aws-cli would expect.

@dlgoodr I have a fix coming for that. It actually solves a first run problem as well. If you install AWS CLI and this tool without running aws configure, the same crash happens. Good catch!

:+1:

On Mar 3, 2018, at 12:02 PM, AlainODea<EMAIL_ADDRESS>wrote:
@dlgoodr I have a fix coming for that. It actually solves a first run problem as well. If you install AWS CLI and this tool without running aws configure, the same crash happens. Good catch!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Add download dialog

[x] The dialog has a title and a description.
[ ] There can be many concurrent downloads in progress, each spawning a new list item. The user can close this dialog and the progress will not be interrupted. Many items invokes a scrollbar.
[ ] A download list item has three states:

Creation: the user can set the scale range, and is shown the zoom levels and estimated tiles. A “Create tile package” button sits to the right. The zoom slider has an indication of the user’s zoom level.
In Progress: after the user clicks the “create” button, the task is sent to the server and the button says, “in progress” and is disabled. A spinny graphic shows that it is working on something.
 The button says, “Download” and there is a check icon on the left.

UX related Questions

should we remove the download job card after user clicking on the download button?
how long should we keep jobs that has never been started?
should we only show jobs that intersect with the current map extent?
should we have a upper limit for jobs that a user can create?


Feature/issue 739 choice vr optional

Fixes #739
This PR is ready for review.
Risk
This PR makes minor API changes.
Testing Plan
unit tests as they existed, no logic changed, just adding a constructor
Summary

deprecate old constructor
add new one without vr commands

CLA

[X] I have signed the CLA

Codecov Report

Merging #836 into develop will increase coverage by 0.03%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             develop     #836      +/-   ##
=============================================
+ Coverage      43.41%   43.44%   +0.03%
  Complexity      3029     3029
=============================================
  Files            382      382
  Lines          17461    17465       +4
  Branches        1736     1736
=============================================
+ Hits            7580     7588       +8
+ Misses          9563     9557       -6
- Partials         318      320       +2

Impacted Files
Coverage Δ
Complexity Δ

...ain/java/com/smartdevicelink/proxy/rpc/Choice.java
87.87% <0%> (-12.13%)
17 <0> (ø)

...smartdevicelink/encoder/VirtualDisplayEncoder.java
29.31% <0%> (+4.59%)
8% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


It's hard to zoom image (dragging instead)

Hi, thank you for your package.
I've found that on iOS it's hard to catch the zooming gesture (didn't check on Android). When you put 2 fingers on the screen in 9 cases of 10 it's considered as a drag gesture (like 1 finger).
Is it possible to improve this behavior?

Fixed in https://github.com/lykhonis/image_crop/pull/55#issue-499958317.
Waiting for merging from @lykhonis

This happen again only on iPhone Xs Max


cli : Add basic arg parser and use it for parsing brew audit args

[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?

#1860 Emit warnings for mistyped options
This a very basic WIP PR,  to get feedback on its usability & to demonstrate DSL of the parser;
Requirements:

DSL should be in declarative way
Reduce number of places ARGV is used, abstract it in DSL

Example Code:
args = Homebrew::CLI::Parser.new do
  switch       "--strict",      "description of strict"
  switch       "--online",      "description of online"
  switch       "--new-formula", "description of new-formula"
  comma_array  "--only-cops",   "description of only-cops"
end.parse

3 types are supported as of now.

switch
A switch is an option that does not take arguments. It is used to turn options on/off . It can be both long and short
Ex: --new-formula , -D

flag
Flags take arguments. Long form flags take arguments with equal sign and short form flags don't require equal sign
Ex: --log-level=DEBUG

comma_array
Custom "flag" option type for Homebrew, which can take comma separated arguments
Ex: --only-cops=FormulaAudit,FormulaAuditStrict

Usage:
Example 1: (All valid args)
$ brew audit --new-formula wget would result args to be as follows
> p args
> #<OpenStruct new_formula?=true>
Example 2: (wrong args)
$ brew audit --unknown-arg wget would result in
Error invalid option: --unknown-arg
To start with, I have replaced usages of ARGV in audit.rb with this implementation.

@alyssais Thanks! Pushed changes addressing review comments.

@MikeMcQuaid Addressed comments and pushed my changes.

Looks good here and locally, thanks again @GauthamGoli!

Note this works because it caught the use of brew audit --devel in brew test-bot which did nothing 🎉


Explorer - Indicate ignored files (say by symbol i)

Like untracked files are indicated by U. Is it possible to indicate ignored files by i.

Currently we indicate ignored files by greying them out.
Leaving this open as a feature request
@jrieken this is currently not possible to be done via an extension ,correct?

No, that's currently not possible...


Email with special character

zend-mail:2.5.2
vendor/zendframework/zend-mail/src/Header/HeaderValue.php:112
method Zend\Mail\Header\HeaderValue::assertValid($value) throws RuntimeException - Invalid header value detected validation e-mail:   ً<EMAIL_ADDRESS>Please pay attention that email contains symbol https://en.wiktionary.org/wiki/ً. But zend-validator EmailAddress considered this email valid. I can not understand which side of the error

This repository has been closed and moved to laminas/laminas-mail; a new issue has been opened at https://github.com/laminas/laminas-mail/issues/22.


Module compiled with Swift 4.0.3 cannot be imported in Swift 4.1

When build "CollectionKitExample"

me too

run carthage update --platform iOS and clean up your code base and you should be good to go.
PS. (brew install carthage) if you don't have carthage.


skydns:2015-03-11-001 failing with exit code 2

if i do kubectl get pods, it is continuously failing.  perhaps an issue with latest kubernetes?  i am running your latest master branch

I just can't reproduce. Can you share skydns logs?

I've got the same problemen.
I'm a absolute beginner with kubernetes  (hours). But I tried to get some logs, but I'm afraid my obtained logs aren't really useful. The cluster is started without any custom environment variables with vagrant up. Any hints how to get better logs?
[kubernetes-vagrant-coreos-cluster]$ kubectl get pods                                                                                *[master]
POD              IP            CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED     MESSAGE
kube-dns-clo3u   <IP_ADDRESS>                                                                   <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   4 minutes
                               kube2sky       gcr.io/google_containers/kube2sky:1.5                                                                                Running   2 minutes
                               etcd           gcr.io/google_containers/etcd:2.0.9                                                                                Running   2 minutes
                               skydns         gcr.io/google_containers/skydns:2015-03-11-001                                                                         Running   2 minutes

kubernetes-vagrant-coreos-cluster]$ kubectl log kube-dns-clo3u skydns                                                                                *[master]
2015-05-19T09:39:35.542806988Z 2015/05/19 09:39:35 skydns: falling back to default configuration, could not read from etcd: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]
2015-05-19T09:39:35.542956538Z 2015/05/19 09:39:35 skydns: ready for queries on k8s.local. for tcp://<IP_ADDRESS>:53 [rcache 0]
2015-05-19T09:39:35.542963375Z 2015/05/19 09:39:35 skydns: ready for queries on k8s.local. for udp://<IP_ADDRESS>:53 [rcache 0]

core@node-01 ~ $ docker ps -a
CONTAINER ID        IMAGE                                            COMMAND                CREATED             STATUS              PORTS               NAMES
88439ab1c875        gcr.io/google_containers/kube2sky:1.5            "/kube2sky -kube_mas   14 minutes ago      Up 14 minutes                           k8s_kube2sky.39f62b0e_kube-dns-clo3u_default_a205e06a-fe0a-11e4-bf59-0800270db324_f9273455
6a1d82c6e74e        gcr.io/google_containers/etcd:2.0.9              "/usr/local/bin/etcd   14 minutes ago      Up 14 minutes                           k8s_etcd.13594ee7_kube-dns-clo3u_default_a205e06a-fe0a-11e4-bf59-0800270db324_ab76e530
590eef73c1d5        gcr.io/google_containers/skydns:2015-03-11-001   "/skydns -machines=h   14 minutes ago      Up 14 minutes                           k8s_skydns.6b637854_kube-dns-clo3u_default_a205e06a-fe0a-11e4-bf59-0800270db324_cbbab248
2f5bfc0e4510        gcr.io/google_containers/pause:0.8.0             "/pause"               14 minutes ago      Up 14 minutes                           k8s_POD.8fdb0e41_kube-dns-clo3u_default_a205e06a-fe0a-11e4-bf59-0800270db324_8a89e215

core@node-01 ~ $ docker logs 590eef73c1d5
2015/05/19 09:39:35 skydns: falling back to default configuration, could not read from etcd: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]
2015/05/19 09:39:35 skydns: ready for queries on k8s.local. for tcp://<IP_ADDRESS>:53 [rcache 0]
2015/05/19 09:39:35 skydns: ready for queries on k8s.local. for udp://<IP_ADDRESS>:53 [rcache 0]

core@node-01 ~ $ docker logs 88439ab1c875
I0519 09:39:49.866596       1 kube2sky.go:148] Etcd server found: http://<IP_ADDRESS>:4001
I0519 09:39:50.869977       1 kube2sky.go:202] Using http://<IP_ADDRESS>:8080 for kubernetes master
I0519 09:39:50.869999       1 kube2sky.go:203] Using kubernetes API v1beta3

2015-05-19T09:39:35.542806988Z 2015/05/19 09:39:35 skydns: falling back to default configuration, could not read from etcd: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]

This shouldn't happen. Will investigate further.

okay thx for your time. tell me if I can provide further informations or test something out.

I think I got it thanks to your feedback @MaxDaten.

It's very interesting that you give two different logs with different timestamps.

2015-05-19T09:39:35.542806988Z 2015/05/19 09:39:35 skydns: falling back to default configuration, could not read from etcd: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]

This doesn't work.

2015/05/19 10:23:57 skydns: falling back to default configuration, could not read from etcd: 100: Key not found (/skydns/config) [406]

This does.

sorry my fault, i messed it up and tried to correct it with an (incomplete) edit of the post:
the first (2015-05-19T09:39:35.542806988Z) one was after deactivating the livenessProbe for skydns in dns-controller.yaml.tmpl (comment dns/dns-controller.yaml.tmpl#L55 to dns/dns-controller.yaml.tmpl#L62).
With livenessProbe active (fresh checkout of master) the skydns service is restarted every ~30s. with an identical log entry like the message at 2015/05/19 10:23:57 for killed docker container and docker ps -a shows Exited (2) x seconds ago for them.
sorry for the confusion.

It's something with the livenessProbe. If I remove it, everything works.
Trying to fix the liveness probe instead of removing it.

And so it is an upstream bug, so sorry for bringing this to the tree.

23:51 < treed> ppires: Yes, fixed by adding "&& echo ok" to the liveness probe
23:51 < treed> there's a change coming in 0.18 apparently, and the dns stuff was updated for it prematurely

Am preparing a PR. Thank you for reporting.

https://github.com/GoogleCloudPlatform/kubernetes/issues/8538

Thanks pires for fixing the issue.  Appreciate that MaxDaten provided all the needed info!  Will check this out to make sure it is fixed now..

Unfortunately, issue continues to occur.
22:40 $ kubectl get pods
POD              IP            CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED      MESSAGE
kube-dns-r4hfd   <IP_ADDRESS>                                                                   <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   12 minutes
                               skydns         gcr.io/google_containers/skydns:2015-03-11-001                                                                         Running   1 seconds    last termination
: exit code 2
                               kube2sky       gcr.io/google_containers/kube2sky:1.5                                                                                Running   5 minutes
                               etcd           gcr.io/google_containers/etcd:2.0.9

@vnc-zestfinance did you rebuild the cluster?
vagrant destroy -f
vagrant up

@MaxDaten can you confirm it's working?
I have it working here.
$ kubectl get pods
POD              IP            CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED
kube-dns-wnfa4   <IP_ADDRESS>   etcd           gcr.io/google_containers/etcd:2.0.9              <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   17 minutes
                               kube2sky       gcr.io/google_containers/kube2sky:1.5
                               skydns         gcr.io/google_containers/skydns:2015-03-11-001

$ kubectl exec -p kube-dns-wnfa4 -c skydns uptime
 09:17:33 up 18 min,  load average: 0.00, 0.06, 0.11

@pires Sadly 'skydns' is still restarted every ~30 seconds for me according to:
$ kubectl get pods                                                                                [master]
POD              IP           CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED      MESSAGE
kube-dns-rqauz   <IP_ADDRESS>                                                                   <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   38 minutes
                              skydns         gcr.io/google_containers/skydns:2015-03-11-001                                                                         Running   12 seconds   last termination: exit code 2
                              etcd           gcr.io/google_containers/etcd:2.0.9                                                                                Running   35 minutes
                              kube2sky       gcr.io/google_containers/kube2sky:1.5                                                                                Running   35 minutes

but uptime gives:
$ kubectl exec -p kube-dns-rqauz -c skydns uptime                                                                                [master]
 10:29:54 up 40 min,  load average: 0.65, 0.50, 0.29

but this could be just the pod uptime not the container uptime.

@pires - it looks that atm livenessProbes are totally busted in upstream. expecting them to behave in any form may be too much right now ... IMHO disabling them for now is the right thing to do ...

@AntonioMeireles yes, it seems so. Meh.

And I just realized the uptime shows the host uptime. Bummer.

/me points to https://github.com/AntonioMeireles/kubernetes-vagrant-coreos-cluster/commit/a60657da430be14474928c04a18f2828d462ea51 (link to upstream soap opera there)

okay :(
a bit off:  what is good method to test the dns resolution manually on the cluster on my own? where and how should I run nslookup/dig?
thx for investigating this. so we have to wait for a working probing.

@MaxDaten kubectl exec -p kube-dns-wnfa4 -c skydns nslookup kubernetes.default.kubernetes.local localhost. Replace kube-dns-wnfa4 with your pod ID.

@vnc-zestfinance @MaxDaten please rebase your clones and let me know.

seems to work now.
$ kubectl get pods                                                                                [master]
POD              IP           CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED      MESSAGE
kube-dns-9inmt   <IP_ADDRESS>                                                                   <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   11 minutes
                              skydns         gcr.io/google_containers/skydns:2015-03-11-001                                                                         Running   8 minutes
                              kube2sky       gcr.io/google_containers/kube2sky:1.5                                                                                Running   8 minutes
                              etcd           gcr.io/google_containers/etcd:2.0.9                                                                                Running   8 minutes

$ kubectl exec -p kube-dns-9inmt -c skydns nslookup kubernetes.default.kubernetes.local localhost                                                                                [master]
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS> localhost

Name:      kubernetes.default.kubernetes.local
Address 1: <IP_ADDRESS>

but now I bumped against a completely unrelated problem. Consecutive calls of kubectl get pods behaves really different. For Example:
$ kubectl get pods                                                                                [master]
POD       IP        CONTAINER(S)   IMAGE(S)   HOST      LABELS    STATUS    CREATED   MESSAGE

$ kubectl get pods                                                                                [master]
Error: Get http://<IP_ADDRESS>:8080/api/v1beta3/namespaces/default/pods: read tcp <IP_ADDRESS>:8080: connection reset by peer

$ kubectl get pods                                                                                [master]
POD              IP           CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED      MESSAGE
kube-dns-9inmt   <IP_ADDRESS>                                                                   <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   27 minutes
                              skydns         gcr.io/google_containers/skydns:2015-03-11-001                                                                         Running   24 minutes
                              kube2sky       gcr.io/google_containers/kube2sky:1.5                                                                                Running   24 minutes
                              etcd           gcr.io/google_containers/etcd:2.0.9                                                                                Running   25 minutes

$ kubectl get pods                                                                                [master]
Error: Get http://<IP_ADDRESS>:8080/api/v1beta3/namespaces/default/pods: write tcp <IP_ADDRESS>:8080: broken pipe

$ kubectl get pods                                                                                [master]
POD       IP        CONTAINER(S)   IMAGE(S)   HOST      LABELS    STATUS    CREATED   MESSAGE

then I have to wait couple of minutes to get kubectl get pods to work again. Which is strange, the last two days this was completely reliable.

Sorry for the spam but it's working here. Could it be something related to your networking? Do you have Virtualbox DHCP server turned-on?
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get pods
POD              IP            CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED
kube-dns-sdh8l   <IP_ADDRESS>   etcd           gcr.io/google_containers/etcd:2.0.9              <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   47 minutes
                               kube2sky       gcr.io/google_containers/kube2sky:1.5
                               skydns         gcr.io/google_containers/skydns:2015-03-11-001
littlepires:kubernetes-vagrant-coreos-cluster pires$ vagrant up node-02
Bringing machine 'node-02' up with 'virtualbox' provider...
==> node-02: Importing base box 'coreos-alpha'...
==> node-02: Matching MAC address for NAT networking...
==> node-02: Checking if box 'coreos-alpha' is up to date...
==> node-02: Setting the name of the VM: kubernetes-vagrant-coreos-cluster_node-02_1432121653689_81938
==> node-02: Fixed port collision for 22 => 2222. Now on port 2201.
==> node-02: Clearing any previously set network interfaces...
==> node-02: Preparing network interfaces based on configuration...
    node-02: Adapter 1: nat
    node-02: Adapter 2: hostonly
==> node-02: Forwarding ports...
    node-02: 22 => 2201 (adapter 1)
==> node-02: Running 'pre-boot' VM customizations...
==> node-02: Booting VM...
==> node-02: Waiting for machine to boot. This may take a few minutes...
    node-02: SSH address: <IP_ADDRESS>:2201
    node-02: SSH username: core
    node-02: SSH auth method: private key
    node-02: Warning: Connection timeout. Retrying...
==> node-02: Machine booted and ready!
==> node-02: Setting hostname...
==> node-02: Configuring and enabling network interfaces...
==> node-02: Running provisioner: file...
==> node-02: Running provisioner: shell...
    node-02: Running: inline script
==> node-02: Running triggers after up...
==> node-02: Waiting for Kubernetes minion [node-02] to become ready...
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get pods
POD              IP            CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED
kube-dns-sdh8l   <IP_ADDRESS>   etcd           gcr.io/google_containers/etcd:2.0.9              <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   50 minutes
                               kube2sky       gcr.io/google_containers/kube2sky:1.5
                               skydns         gcr.io/google_containers/skydns:2015-03-11-001
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get pods
POD              IP            CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED
kube-dns-sdh8l   <IP_ADDRESS>   etcd           gcr.io/google_containers/etcd:2.0.9              <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   50 minutes
                               kube2sky       gcr.io/google_containers/kube2sky:1.5
                               skydns         gcr.io/google_containers/skydns:2015-03-11-001
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get minions
NAME           LABELS        STATUS
<IP_ADDRESS>   Schedulable   <none>    Ready
<IP_ADDRESS>   Schedulable   <none>    Ready
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get pods
POD              IP            CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED
kube-dns-sdh8l   <IP_ADDRESS>   etcd           gcr.io/google_containers/etcd:2.0.9              <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   50 minutes
                               kube2sky       gcr.io/google_containers/kube2sky:1.5
                               skydns         gcr.io/google_containers/skydns:2015-03-11-001
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get pods
POD              IP            CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED
kube-dns-sdh8l   <IP_ADDRESS>   etcd           gcr.io/google_containers/etcd:2.0.9              <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   50 minutes
                               kube2sky       gcr.io/google_containers/kube2sky:1.5
                               skydns         gcr.io/google_containers/skydns:2015-03-11-001
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get minions
NAME           LABELS        STATUS
<IP_ADDRESS>   Schedulable   <none>    Ready
<IP_ADDRESS>   Schedulable   <none>    Ready
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get services
NAME            LABELS                                                              SELECTOR           IP            PORT(S)
kube-dns        k8s-app=kube-dns,kubernetes.io/cluster-service=true,name=kube-dns   k8s-app=kube-dns   <IP_ADDRESS>   53/UDP
                                                                                53/TCP
kubernetes      component=apiserver,provider=kubernetes                             <none>             <IP_ADDRESS>    443/TCP
kubernetes-ro   component=apiserver,provider=kubernetes                             <none>             <IP_ADDRESS>    80/TCP
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get endpoints kube-dns
NAME       ENDPOINTS
kube-dns
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get endpoints kubernetes
NAME         ENDPOINTS
kubernetes   <IP_ADDRESS>:6443
littlepires:kubernetes-vagrant-coreos-cluster pires$ kubectl get pods
POD              IP            CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED
kube-dns-sdh8l   <IP_ADDRESS>   etcd           gcr.io/google_containers/etcd:2.0.9              <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   51 minutes
                               kube2sky       gcr.io/google_containers/kube2sky:1.5
                               skydns         gcr.io/google_containers/skydns:2015-03-11-001

The Virtualbox DHCP servers was turned on, turned them of, without change in the new behavior.
$ VBoxManage list dhcpservers
NetworkName:    HostInterfaceNetworking-vboxnet0
IP:             <IP_ADDRESS>
NetworkMask:    <IP_ADDRESS>
lowerIPAddress: <IP_ADDRESS>
upperIPAddress: <IP_ADDRESS>
Enabled:        Yes

NetworkName:    HostInterfaceNetworking-vboxnet1
IP:             <IP_ADDRESS>
NetworkMask:    <IP_ADDRESS>
lowerIPAddress: <IP_ADDRESS>
upperIPAddress: <IP_ADDRESS>
Enabled:        Yes

$ VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet0
$ VBoxManage dhcpserver remove --netname HostInterfaceNetworking-vboxnet1
$ VBoxManage list dhcpservers
$

$ vagrant destroy -f && vagrant up
(...)
$ kubectl get pods
Error: Get http://<IP_ADDRESS>:8080/api/v1beta3/namespaces/default/pods: read tcp <IP_ADDRESS>:8080: connection reset by peer
$ kubectl get pods
POD              IP        CONTAINER(S)   IMAGE(S)                                         HOST           LABELS                                                STATUS    CREATED      MESSAGE
kube-dns-zria1                                                                             <unassigned>   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Pending   24 minutes
                           etcd           gcr.io/google_containers/etcd:2.0.9
                           kube2sky       gcr.io/google_containers/kube2sky:1.5
                           skydns         gcr.io/google_containers/skydns:2015-03-11-001

Created 24 minutes? It seems there is a vm stuck.
$ $ VBoxManage list runningvms
"kubernetes-vagrant-coreos-cluster_master_1432114941915_81813" {8505a2af-4e5d-48e5-ae21-718733fc314e}
"kubernetes-vagrant-coreos-cluster_master_1432123595266_82734" {92746e56-1957-4f3c-9b38-6edaadbf738f}
"kubernetes-vagrant-coreos-cluster_node-01_1432123674229_1347" {671b28c2-aa23-4280-b2c0-51c84608e57c}
"kubernetes-vagrant-coreos-cluster_node-02_1432123746660_35092" {f344c6b5-8b48-4f05-ad0f-68a207666859}

Two running masters. so vagrant destroy -f again and deleted the pending master, fresh start:
$ kubectl get pods
POD              IP           CONTAINER(S)   IMAGE(S)                                         HOST            LABELS                                                STATUS    CREATED          MESSAGE
kube-dns-47gcc   <IP_ADDRESS>                                                                   <IP_ADDRESS>/   k8s-app=kube-dns,kubernetes.io/cluster-service=true   Running   3 minutes
                              skydns         gcr.io/google_containers/skydns:2015-03-11-001                                                                         Running   About a minute
                              kube2sky       gcr.io/google_containers/kube2sky:1.5                                                                                Running   About a minute
                              etcd           gcr.io/google_containers/etcd:2.0.9                                                                                Running   About a minute
$ kubectl get endpoints kube-dns                                                                                [master]
NAME       ENDPOINTS
kube-dns   <IP_ADDRESS>:53,<IP_ADDRESS>:53

and it's now reliable again. sorry for my spam about this. dns seems to work now. now I can continue with some guides. Thanks alot for your patience.

Yeah, probably some VM garbage. Thank you for your invaluable feedback @MaxDaten :)

It works now! Thanks @pires for fixing it.

@vnc-zestfinance thank you for reporting and bearing with me until a fix was done.

@pires I have to thank you for investigating this.

@MaxDaten don't mention it. Thank you for bearing with me as well. Feedback is more than appreciated, guys!


Crash on search

What steps will reproduce the problem?
Search Drow tag and get all, then search Dark_elf Blue_skin
What is the expected behavior? What do you get instead?
Wanted results, got crash
What version of the program are you using? On what operating system?
v5.0.0 win7
Please provide any additional information below
*large ammount of sources.

I have the same problem but it with every search I do no matter what it is