Error when executing "ionic run android", fine when building app using Eclipse

H there,
when I run my Ionic app manually using `Eclipse, it installs fine on the device.
when I use the command line and run ionic run android I get the following error:
mirko@mirko-air/Applications/MAMP/htdocs/epicollect5-ionic$ 😝  ionic run android
add to body class: platform-android
Running command: /Applications/MAMP/htdocs/epicollect5-ionic/platforms/android/cordova/run

/Applications/MAMP/htdocs/epicollect5-ionic/platforms/android/cordova/lib/check_reqs.js:39
        return target.split('=')[1].replace('\n', '').replace('\r', '');
                                    ^
TypeError: Cannot call method 'replace' of undefined
    at Object.module.exports.get_target (/Applications/MAMP/htdocs/epicollect5-ionic/platforms/android/cordova/lib/check_reqs.js:39:37)
    at Object.module.exports.check_android (/Applications/MAMP/htdocs/epicollect5-ionic/platforms/android/cordova/lib/check_reqs.js:71:29)
    at Object.module.exports.run (/Applications/MAMP/htdocs/epicollect5-ionic/platforms/android/cordova/lib/check_reqs.js:94:61)
    at Object.<anonymous> (/Applications/MAMP/htdocs/epicollect5-ionic/platforms/android/cordova/run:31:10)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
Error: /Applications/MAMP/htdocs/epicollect5-ionic/platforms/android/cordova/run: Command failed with exit code 8
    at ChildProcess.whenDone (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:135:23)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:756:16)
    at Process.ChildProcess._handle.onexit (child_process.js:823:5)

I am using Ionic 1.1.13, cordova 3.5

Greetings!
My sensors indicate a reply was requested, however, since we have not received one yet, this will be closed. If you are still experiencing this issue, please feel free to reopen it and include any information that may have been requested.
Thank you!


feat: Make list a  default command operation

Signed-off-by: Diana Atanasova<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-cli/blob/master/.github/Contributing.md.
What is the current behavior?

Issue Number:
Closes: https://github.com/edgexfoundry/edgex-cli/issues/336
What is the new behavior?
Make list default command operation for all commands, but still keep the
list as an available operation
Example list all devices could be called in two ways:

edgex-cli device
edgex-cli device list

Does this PR introduce a breaking change?

[ ] Yes
[X ] No

New Imports

[ ] Yes
[X] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Codecov Report

Merging #362 (582081a) into master (4e4b63e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #362   +/-   ##
=======================================
  Coverage   14.51%   14.51%
=======================================
  Files           3        3
  Lines          62       62
=======================================
  Hits            9        9
  Misses         53       53

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 4e4b63e...582081a. Read the comment docs.

Codecov Report

Merging #362 (582081a) into master (4e4b63e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #362   +/-   ##
=======================================
  Coverage   14.51%   14.51%
=======================================
  Files           3        3
  Lines          62       62
=======================================
  Hits            9        9
  Misses         53       53

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 4e4b63e...582081a. Read the comment docs.


Remove flutter dependency from library, add analysis options, and refactor

Hi everyone,

I removed the dependency to flutter, so the library is usable with pure Dart, e.g. on the server side.
I added the latest Dart linter configurations, suggested and officially used by the Dart and Flutter team.
I incorportated all of the suggestions from the linter into the code and refactored the lib accordingly.

I hope you can use my PR.
All the best, Lukas
BTW thank you for the library

Thanks @lukas-h

Cool, this was a fast merge 👍


Content Suggestion: Hellodime BTC Educational Card Game

Link to Content: HelloDime URL
Briefly Describe Content: This project (fully self funded, no trashy VC backing ) has an intention to kickstart interest and get individuals to be more interested in the Bitcoin ecosystem . The concept of the game is on your keys, your coins with most of the high level BTC concepts within the game mechanics (mining/ scarcity / randomness / difficulty ) alongside personas that emulate real world scenarios.
Suggested Section: hardware/other hardware ?

Added
Thanks!

Thanks. Didn’t see it but it’s okay.


Problem Matcher gets cleared by other tasks

If you run a task and it generates a problem window match, and you run a different task, the problem window's contents is cleared from the first task.
The main use case here is using a pre-checkin scripts (task 1) that are separate from building (task 2):
if you run the precheckin script that generates problem window matchs and build after only fixing one problem, the rest of the problms generated by precheckin (task 1) are wiped away by the build running (task 2) it's problem matcher.

@kevindiclemente Does task 1 use the same problem matcher as task 2?
If they use the same problem matcher, you should modify the problem matcher for one of the tasks to have a different source.


Add Queued variants of Channel and Weak

I'm not sure if this would be necessary, it doesn't seem like it.


inline playback for gif attachments

Summary
Adds Inline playback for git attachments
Cc @dmeza
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] Ran make check-style to check for style errors (required for all pull requests)
[ ] Ran make test to ensure unit and component tests passed
[ ] Added or updated unit tests (required for all new features)
[ ] Has server changes (please link)
[ ] Has redux changes (please link)
[x] Has UI changes
[ ] Includes text changes and localization file (.../i18n/en.json) updates
[ ] Touches critical sections of the codebase (auth, posting, etc.)

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: http://i-0a3528f145c87e557.spinmint.com
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-0a3528f145c87e557

Spinmint test server destroyed

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: http://i-03a167eb16194021d.spinmint.com
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-03a167eb16194021d

@esethna rebased to latest from master, added gif playback to preview and re-created snapshots. Checked that styles and tests are passing.

Spinmint test server destroyed

Spinmint test server created at: http://i-08910b2a8dcfb8c75.spinmint.com
Test Account 1: Email<EMAIL_ADDRESS>| Password: passwd
Test Account 2: Email<EMAIL_ADDRESS>| Password: passwd
Instance ID: i-08910b2a8dcfb8c75

@esethna reviewed the PR and the conflict will be on the snapshot for components/file_attachment.jsx. Otherwise it should be fine.

Spinmint test server destroyed

How does this handle non-animated gifs? Does it load the full image for them or just the thumbnail?
Also, is there any ability to not autoplay the gifs for users who don't want that?

@hmhealey thanks for the comments.

Since there's no way to know if it's animated or not, it does load the full image in for gifs. Do you know of a way we can control that?
It would need a config to display the thumbnail, but that could be a following step.

For whether or not it's an animated gif, I believe the FileInfo object will have has_preview_image set to false if it's an animated gif (to prompt it to show the animated gif in the preview modal
For turning on/off the animation, I'll double check with PMs. When we had something similar to it in the past, we had a toggle like that, but maybe it's not necessary any more

@hmhealey I'll add that change later today.

@hmhealey made the fix to check than when it's a gif and has_preview_image is true to display the thumbnail. Rebased to latest from master.


React peer dependency update

Updated peerDependencies to allow react-smooth-dnd to be installed in React 17 projects without npm dependency errors

Will this be merged?

Pinging @kutlugsahin 🙏

@kutlugsahin Would you please merge this? Thanks.

Will this PR be merged into main or an update to React 18 to resolve the dependency issue anytime soon, @kutlugsahin ?

Will this be merged soon?

Will this be merged soon?

With React 18 released, is this package supported?

Any plans to merge this PR ?

Will it be merged?

@littlespex merging it?

I don't have access to merge this.

@kutlugsahin

@kutlugsahin


Transformer based vision colab example

Hi, I am wondering how much harder is the transformer-based diffusion policy is to train? Will it be possible to adapt it to the vision based colab example on colab? @NeilNie @pointW @jingxixu @cheng-chi

+1

Just wanna kindly bump up the message as others are on the same boat. Any points are appreciated! @NeilNie @pointW @jingxixu

+1


fix Supervision depreciation of BoxAnnotator

Saw a warning when calling annotate:
SupervisionWarnings: annotate is deprecated: BoxAnnotator is deprecated and will be removed in supervision-0.22.0. Use BoundingBoxAnnotator and LabelAnnotator instead
Fixed by removing BoxAnnotator and use BoundingBoxAnnotator and LabelAnnotator as instructed by the warning.
And based on supervision release note, BoundingBoxAnnotator is added in version 0.15.0 .
Please review. Thank you!

@ethanlee928
It seems there's been some confusion with version updates and the renaming of classes. Based latest information, BoundingBoxAnnotator has been renamed to BoxAnnotator and will be removed in future versions. Therefore, you should use BoxAnnotator instead of BoundingBoxAnnotator. Here is the corrected code:
bbox_annotator = sv.BoxAnnotator(color_lookup=sv.ColorLookup.INDEX)

With this update, your code will comply with the latest library standards, ensuring backward compatibility.

This PR can fix the following error:
TypeError: BoxAnnotator.annotate() got an unexpected keyword argument 'labels'

Thank you for your PR.

@pg56714 Thanks for providing the latest information, I've updated the PR based on your suggestion.

@SkalskiP
Friendly ping to see if you had a chance to look at this PR related to Supervision. Appreciate any feedback when you get a moment. Thanks!

Hi @ethanlee928 👋🏻, I did not know this PR existed. Looks good. Thanks a lot for the help in migrating from the old to the new supervision API.


Three commands sequentially?

I was pleased that there is a meta action "multi", but I could not cover more than two actions (even by embedding one operator into another).
Thank you for getting rid of the mouse!

Yeah currently the multi binding only allows two  actions, and one cannot embed the meta actions into each other, but I think there is no reason why the multi should not accept any number of actions, I will add that.

I don't remember exactly, but then I probably didn't know about such abbreviated entries as "alt+a". :P


ModuleNotFoundError

keep getting this  ModuleNotFoundError: No module named 'lib.multi_depth_model_woauxi' when l run python ./tools/test_depth.py --load_ckpt res50.pth --backbone resnet50  why?

got it to work

Hi Thanks for your nice work. I tried to run AdelaiDepth_ResNet101.ipynb
(here) but I got error like:
/env/python:/content/AdelaiDepth/LeReS:/content/AdelaiDepth/LeReS:/content/AdelaiDepth/LeReS:/content/AdelaiDepth/LeReS:/content/AdelaiDepth/LeReS
/content/AdelaiDepth
Traceback (most recent call last):
File "/content/AdelaiDepth/LeReS/Minist_Test/tools/test_depth.py", line 19, in
from lib.multi_depth_model_woauxi import RelDepthModel
ModuleNotFoundError: No module named 'lib'
I tried below solution mentioned here. but still didn't work.
import sys, os
sys.path.insert(1, os.getcwd())

I also tried below solution metioned here, but did not work
import os
import sys
sys.path.insert(1, os.path.abspath(".")) # insert the current directory
from lib.multi_depth_model_woauxi import RelDepthModel
from lib.net_tools import load_ckpt

Do you have any idea how can I solve it? I would appreciate it.


Still failure in cucumber before/after hooks reporters

@BorisOsipov I have created a reproducible case regarding this problem:
https://github.com/BorisOsipov/wdio-cucumber-framework/commit/bb9fc367754629347c5fbac8d9780b929bc8cf40#r28434074
Here is a branch I prepared:
https://github.com/ringods/webdriverIO-with-cucumberBDD/tree/wdio-cucumber
Note: I replaced/remove the Scenario Outline by normal Scenario to not be bitten by #111 .

Thanks man.
It reproduces on 2.0.0 as well.

Let me know if you need me to test possible fixes.

@BorisOsipov together with someone else, we did some further testing. The undefined in the reporter hook happens for steps in a Background section. If you put the Given step directly in the Scenario, the reporter hook doesn't fail.
Hope this helps to fix this issue.

Thanks your further testing.  I just fell into the same issue, and it worked after I removed Background...

Looks like this is still open after all then? What do you need in terms of "help wanted" ?

What do you need in terms of "help wanted" ?

Someone who fixes the bug and proposes a PR 😉

fair 'nuff lets see how bored i get later today

@ringods I've put in a pull request which I believe should fix this (does for me locally) - would welcome a test by 3rd party

@goofballLogic after fighting with pyenv and python to get node-gyp installed, I tried to run your patched version, but all I get is this:
ERROR: Couldn't load "wdio-cucumber-framework" framework. You need to install it with `$ npm install wdio-cucumber-framework`!
Error: Cannot find module 'wdio-cucumber-framework'

This is in my devDependencies though:
    "wdio-cucumber-framework": "github:fluenttechnology/wdio-cucumber-framework",

@ringods if you define a dependency like this it won't be compiled. You need to go into the node_modules folder and npm install and build the project

Excuse me??? Unbelievable....
@christian-bromann could you help me out what I'm still missing? I went into node_modules/wdio-cucumber-framework and ran npm install. But still, after doing this, I remain getting the Cannot find module error on my main project when running npm test

Excuse me??? Unbelievable....

What do you mean by that, I was just trying to help!

after doing this

You also need to build the project

Excuse me??? Unbelievable....
What do you mean by that? I was just trying to help!

This wasn't aimed at you. Sorry if you interpreted it like that. 😉
I am disappointed in the status of development tooling in general and frustrated due to that. Already struggling for days to get some wdio stuff working. In this case, I was just expecting that an npm install would do the same things whether I specify a version or a git location.

after doing this
You also need to build the project

Can you tell me what I need to do to build the project? Because below is the output I already got when running npm install in node_modules/wdio-cucumber-framework:
npm install
WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha1-HkmWg3Ix2ot/PPQRTXG1aRoGgN0= integrity checksum failed when using sha1: wanted sha1-HkmWg3Ix2ot/PPQRTXG1aRoGgN0= but got sha512-PJepbvDbuK1xgIgnau7Y90cwaAmO/LCLMI2mPvaXq2heGMR3aWW5/BQvYrhJ8jgmQjXewXvBjzfqKcVOmhjZ6Q==. (32034 bytes)
WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.

><EMAIL_ADDRESS>install /Users/ringods/Projects/ontoforce/disqover-frontend-e2e/node_modules/wdio-cucumber-framework/node_modules/fibers
> node build.js || nodejs build.js

  CXX(target) Release/obj.target/fibers/src/fibers.o
../src/fibers.cc:318:3: warning: ignoring return value of function declared with 'warn_unused_result' attribute [-Wunused-result]
                object->SetAccessor(isolate->GetCurrentContext(), name, (AccessorNameGetterCallback)getter, (AccessorNameSetterCallback)setter);
                ^~~~~~~~~~~~~~~~~~~
1 warning generated.
  CXX(target) Release/obj.target/fibers/src/coroutine.o
  CC(target) Release/obj.target/fibers/src/libcoro/coro.o
  SOLINK_MODULE(target) Release/fibers.node
Installed in `/Users/ringods/Projects/ontoforce/disqover-frontend-e2e/node_modules/wdio-cucumber-framework/node_modules/fibers/bin/darwin-x64-59/fibers.node`

><EMAIL_ADDRESS>install /Users/ringods/Projects/ontoforce/disqover-frontend-e2e/node_modules/wdio-cucumber-framework/node_modules/fsevents
> node install

[fsevents] Success: "/Users/ringods/Projects/ontoforce/disqover-frontend-e2e/node_modules/wdio-cucumber-framework/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64/fse.node" is installed via remote

><EMAIL_ADDRESS>postinstall /Users/ringods/Projects/ontoforce/disqover-frontend-e2e/node_modules/wdio-cucumber-framework/node_modules/cucumber-expressions
> node scripts/postinstall.js

><EMAIL_ADDRESS>postinstall /Users/ringods/Projects/ontoforce/disqover-frontend-e2e/node_modules/wdio-cucumber-framework/node_modules/sinon
> node scripts/support-sinon.js

Have some ❤ for Sinon? You can support the project via Open Collective:
 > https://opencollective.com/sinon/donate

><EMAIL_ADDRESS>prepare /Users/ringods/Projects/ontoforce/disqover-frontend-e2e/node_modules/wdio-cucumber-framework
> npm prune

npm notice created a lockfile as package-lock.json. You should commit this file.
up to date in 2.834s
added 806 packages in 28.266s

Can you tell me what I need to do to build the project?

 Usually this is already done when you download packages from NPM. If you set a git url as dependency source you will only get the raw project files.

I am disappointed in the status of development tooling in general and frustrated due to that.

I feel like the status of tooling is great, probably just a bit different if you come from another ecosystem.

Already struggling for days to get some wdio stuff working

Have you heard about the WebdriverIO support channel on ? It is a great place to ask questions.


Throw error when string or number passed accidentally?

Would it make sense for assign-deep to throw an error when a string or number is passed?
const element = 'string'
console.log(assignDeep({a: 1}, element, {b: 2, a: 999}))

This prints { a: 999, b: 2 }, as expected. But for someone who passed in the string, it's almost certainly an error in their code because they wouldn't be passing a string or number in the first place. It would be helpful to get an error right away.

I'm not sure, I don't think this should cause an error.
IMHO, there are scenarios where a string or other primitive value might intentionally be overridden by an object. Like when options allow either an object or string to be defined as the value. the default might be a string and if the user defines an object, you might simply want to merge the object over in place of the string value.

I agree that this shouldn't throw an error and that it's better to check the arguments before passing into assignDeep if it's necessary to ensure that everything is an object.


Hijack is incompatible with use of CloseNotifier

Hi,
I upgraded my docker to 1.6 today (I believe it was on 1.5, but I'm not 100% sure).
I now have a problem where my docker client gives me docker.errors.APIError: 500 Server Error: Internal Server Error ("http: Hijack is incompatible with use of CloseNotifier") when I try to post to /containers/<container>/attach (my client uses dockerpty and docker-py)
It would appear that compose has a similar problem (https://github.com/docker/compose/issues/1275).
If I run an image with the docker cli it does work (for example, docker run -it ubuntu:14.04 /bin/bash)
I'm not entirely sure how to debug this issue.
Thanks
Stephen.

Hmm, this is pretty weird, compose running into this on build and that's the place where we use CloseNotifier.

ping @pwaller
Seems like attach just crashing build if client supports CloseNotifier.

I don't understand how this is happening. There's only one call to CloseNotifier, and it's in postBuild. How are we ending up calling Hijack thereafter on the same w?
https://github.com/docker/docker/search?utf8=✓&q=CloseNotifier&type=Code

@pwaller Dunno :/ Maybe connection is used for two requests?

@LK4D4 could it be a go bug then? That is really weird. It would be useful to see the exact sequence of events and connections involved. I'm not likely to spend a lot of time delving into this, though it has piqued my curiosity a bit.

@pwaller I wonder what about keep-alive, so you first calling Build, then Attach and hijack in attach failing.

@delfick Do you build something before attach?

@LK4D4 I guess it could be keep-alive, but I would expect the effects of the CloseNotifier to have finished by the time the connection is ready to be reused for the attach. Hence my suggestion that it could be a bug.

@pwaller https://go-review.googlesource.com/#/c/3821/

@LK4D4 nice find, good to see it's being fixed in general.
However, I still don't understand the sequence of events that is causing the problem as reported here. Do we think someone fires off a build, and at some point later tries to attach, and they're still using the same socket to communicate to the daemon? I'm surprised that this triggers the issue. I guess the workaround is to tell clients to kill their keep-alive after a build or before an attach :(

@pwaller Yeah, seems like many users of api can trigger this with Keep-Alive. I already suggested them to reopen connections in docker/compose#1275

I agree, removing the build step makes it work (my docker client reads yaml that embeds the dockerfile and so it always rebuilds the image before running)
I'll put in code that recreates the connection for now. Good to see there's an actual fix in the pipeline.

Just as info: +1
Stacktrace may help a little:
Traceback (most recent call last):
File "/compose/build/docker-compose/out00-PYZ.pyz/threading", line 810, in __bootstrap_inner
File "/compose/build/docker-compose/out00-PYZ.pyz/threading", line 763, in run
File "/compose/build/docker-compose/out00-PYZ.pyz/compose.cli.multiplexer", line 41, in _enqueue_output
File "/compose/build/docker-compose/out00-PYZ.pyz/compose.cli.log_printer", line 59, in _make_log_generator
File "/compose/build/docker-compose/out00-PYZ.pyz/compose.cli.utils", line 77, in split_buffer
File "/compose/build/docker-compose/out00-PYZ.pyz/docker.client", line 199, in _multiplexed_response_stream_helper
File "/compose/build/docker-compose/out00-PYZ.pyz/docker.client", line 143, in _get_raw_response_socket
File "/compose/build/docker-compose/out00-PYZ.pyz/docker.client", line 95, in _raise_for_status
APIError: 500 Server Error: Internal Server Error ("http: Hijack is incompatible with use of CloseNotifier")

+1
Exception in thread Thread-1:
Traceback (most recent call last):
File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", line 532, in __bootstrap_inner
self.run()
File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", line 484, in run
self.__target(*self.__args, **self.__kwargs)
File "/Library/Python/2.6/site-packages/compose/cli/multiplexer.py", line 41, in _enqueue_output
for item in generator:
File "/Library/Python/2.6/site-packages/compose/cli/log_printer.py", line 59, in _make_log_generator
for line in line_generator:
File "/Library/Python/2.6/site-packages/compose/cli/utils.py", line 77, in split_buffer
for data in reader:
File "/Library/Python/2.6/site-packages/docker/client.py", line 225, in _multiplexed_response_stream_helper
socket = self._get_raw_response_socket(response)
File "/Library/Python/2.6/site-packages/docker/client.py", line 167, in _get_raw_response_socket
self._raise_for_status(response)
File "/Library/Python/2.6/site-packages/docker/client.py", line 119, in _raise_for_status
raise errors.APIError(e, response, explanation=explanation)
APIError: 500 Server Error: Internal Server Error ("http: Hijack is incompatible with use of CloseNotifier")

+1

+1

ping @aanand
Can you confirm that it is fixed on compose side?

Yeah, we fixed it in https://github.com/docker/compose/pull/1374.

+1

@aanand I have the latest docker and compose but I still receive the error. Any suggestions?

Still with the RC?  That fixed it here for me.

+1

@aanand how do I upgrade to that version on osx? (new to docker)

@erichonkanen Follow the instructions here: https://github.com/docker/compose/releases/tag/1.3.0rc1
However, there's a known bug with that RC - if you get an SSL error, hold tight for the fix (https://github.com/docker/compose/pull/1474).

docker-compose 1.2.0
Docker version 1.6.2, build 7c8fca2
Do I need to upgrade ? Cause I got this error yesterday many times when building my app up with dc up. However it runs fine when I rerun it just after.

Yep - 1.2.0 has the bug, and running build followed by up is a workaround.

@aanand Ok thanks dude! I've noticed as well when I remove all my stuff related to docker (hard way: docker rm -f docker ps -aq && docker rmi -f docker images -q) and then build up my app with docker-compose up, then apparently it can't fetch the required deleted images (of mysql for example: from mysql:latest) . I have to docker-compose pull in order to download those.

@catuss-a Sorry to hear - please open an issue on https://github.com/docker/compose for that.

+1

Summary: We just experienced this same problem. Upgrading to docker-compose 1.3 fixed it.
On a fresh Yosemite laptop, with a homebrew installed docker-compose 1.2, it worked fine with docker-machine 0.2.0 and docker 1.5.
Upgrading to docker 1.6.2 caused the error reported in the error well documented in this docker issue:
APIError: 500 Server Error: Internal Server Error ("http: Hijack is incompatible with use of CloseNotifier")

We tried updating to docker 1.7.0 which was released today. The same error occurs.
Upgrading docker-compose to 1.3 fixed it:
sudo pip install -U docker-compose

If you are trying docker-compose and run into this error using docker 1.6 or later, give this a try and see if the error goes away.

@ianblenke I just ran the above sudo pip install command which installed it appeared, however when I run docker-compose I get
 eric@eric-mbp:~/Projects/sqwok/overlord$ docker-compose
Traceback (most recent call last):
  File "/usr/local/bin/docker-compose", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 2603, in <module>
    working_set.require(__requires__)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 666, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 565, in resolve
    raise DistributionNotFound(req)  # XXX put more info here
pkg_resources.DistributionNotFound: six>=1.3.0,<2

@erichonkanen, it sounds like your docker-compose doesn't have the dependency it needs, based on how pip installed them. You may have something else installed that needs an older or newer version of six than that. Try this:
sudo pip install six==1.3.0

Note: you are likely breaking some other python package you have installed by doing that. I'm forever running into this with awscli and awsebcli. The real solution is to run each thing in its own virtualenv, but that's best described elsewhere, and adds an extra layer of management on your part.

@ianblenke very true.. not sure why I decided to install it globally, thx!

upgrading to docker-compose 1.3 fixed this error.
boot2docker 1.7

+1

:+1:
I uninstalled the docker-compose binary installed by Kitematic and installed docker-compose via homebrew and this error went away.

+1

+1

@aanand @lk4d4 if I understand correctly, this is a docker-compose, and fixed in docker-compose 1.3?
if so, can this be closed?

s/docker-compose/docker-compose issue/ ^^

Yeah, in my case that's the only change I made to resolve the error (upgrade docker-compose).

The fix is more of a workaround.
Where we just instantiate a new docker client to avoid reusing the same connection.

I think @pwaller was right in saying it was a Go bug. See https://go-review.googlesource.com/#/c/3821/
Docker-compose worked around it in https://github.com/docker/compose/pull/1374

@thaJeztah I personally think this can be closed. I don't think there is anything that can be done docker-side, only "client" side (so, in compose, docker-py, etc etc). There is a workaround available (turn off HTTP connection reuse (aka Keep-Alive)), and it will be fixed when go fixes https://github.com/golang/go/issues/9763 which has been marked 1.6Early. I'll try and create some noise for that when their next release cycle starts.

Thanks @pwaller, I'll close this issue for now, but others feel free to comment here if you think there's something that can be done in Docker itself.

I'm getting this error after upgrading today.
docker info
Containers: 8
 Running: 2
 Paused: 0
 Stopped: 6
Images: 282
Server Version: 1.12.0-rc3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 320
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host null overlay bridge
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.14-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.954 GiB
Name: moby
ID: JRAU:RVZS:OEOQ:JMBF:PRR6:7TPD:UG5U:TRR6:4T2W:AGWF:5TFV:SLD2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 29
 Goroutines: 47
 System Time: 2016-07-05T20:24:15.611271815Z
 EventsListeners: 1
No Proxy: *.local, 169.254/16
Username: aeikenberry
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

For example:
docker-compose run django python manage.py migrate
http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call
http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call

@aeikenberry Thanks for the report, this is a bug with docker4mac and is pretty much being tracked in docker/compose#3685


document the 'type' function on generic nodes

Technically this doesn't belong on the "Element" wiki page but we dont' have a dedicated Node methods page. It may be time to create one :)

+1 But I also think there are some gotchas with the inheritance tree where
not everything inherits from Node the way it should. I suppose filling in
the docs will bring those to light.
On Tue, Feb 28, 2012 at 12:29 PM, Roman Shtylman <
<EMAIL_ADDRESS>
wrote:

Technically this doesn't belong on the "Element" wiki page but we dont'
have a dedicated Node methods page. It may be time to create one :)

Reply to this email directly or view it on GitHub:
https://github.com/polotek/libxmljs/issues/116

--
Marco Rogers
<EMAIL_ADDRESS>| https://twitter.com/polotek
Life is ten percent what happens to you and ninety percent how you respond
to it.

Lou Holtz


NumericUpDown Minimum Issue

Consider the following example
<hc:NumericUpDown Name="num" Maximum="40" Minimum="5" ValueChanged="num_ValueChanged"/>
Now we save NumericUpDown value
private void num_ValueChanged(object sender, HandyControl.Data.FunctionEventArgs<double> e)
        {
            var val = num.Value;
            if (val != Settings.MaxHistoryNumber)
            {
                Settings.MaxHistoryNumber = (int)val;
            }
        }

As we can see, the changes are stored correctly

Now when we run the program we load the stored value
public General()
        {
            InitializeComponent();
            num.Value = Settings.MaxHistoryNumber;
        }

But as you can see, the minimum value is displayed instead of the loaded value

Complete gif

I can't reproduce the issue

Run the program
Change the value
Close the app
Open the app
You can see that the minimum value is loaded each time
WpfApp15.zip

This is a problem with your code, not with HC. add if (!IsLoaded) return; In the first row of NumericUpDown_ValueChanged method.

Arigato 😅


Configurator.log commited to git, .gitignore not sane

Logfiles should not be commited to git:
https://github.com/devonfw/devon-ide/blob/master/configurator/Configurator.log
File needs to be deleted from git and pattern added to .gitignore

Done.


feature request - port number for mqtt broker

Hi - thanks for producing this.
It would be helpful to include a "port number" argument in config.js (for those of us who run our mqtt broker on a non-standard port to avoid conflicts :) )

This should be already possible via the MQTT url: <protocol>://<user>:<pass>@<host>:<port> where protocol is one of mqtt, mqtts, wsor wss.


How to display gif image from external storage ?

Hello there,
I am unable to display locally stored gif image programatically.
Here is my code
String root = Environment.getExternalStorageDirectory().toString()+"/EnthuonsChat/Images/"+imageName;
File fileToDownload = new File(root);
if(fileToDownload.exists()){
new GifDataDownloader() {
@Override
protected void onPostExecute(final byte[] bytes) {
((ItemMessageUserHolder) holder).gifImageView.setBytes(bytes);
((ItemMessageUserHolder) holder).gifImageView.startAnimation();
}
}.execute(root);
}
Please help me to resolve this issue....

Did you put StartAnimation as well ?
Mine won't display if I don't start the Animation as well

You're likely loading the file incorrectly. make sure it its correctly loaded before calling setBytes and startAnimation


Unusual laravel directory structure (or .htaccess) messes up routing

The url utilized by the middleware is using a path that assumes routing paths for laravel are not changed via .htaccess or other means. This causes the drip logic to not find the controller. The solution is to use the url function to make sure the path is correct.
My fix:
Replace line 32 of LaravelCaffeineDripMiddleware.php with the following:
$content = str_replace('', "", $content);

Thanks for reporting this. I will look into this and the other issues later today. :)

Integrating this now.


Prepare for operations - Document the project structure

Document the project structure.
What are apps and libs?
How are the apps structured? Eg. App contains a table, garde, filter, kpi, etc...

PR: https://github.com/equinor/cc-components/pull/928


allow for traversing folders in host list

also split out host listing into private function.

Awesome, thanks!

Just released 1.2.22, so your improvements are now available to the world.

Awesome, Thank you!


composer install not working

PS C:\laragon\www\laravel-toko-online-anime-store> composer install
You are running Composer with SSL/TLS protection disabled.
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Your lock file does not contain a compatible set of packages. Please run composer update.
Problem 1
- nette/schema is locked to version v1.2.2 and an update of this package was not requested.
- nette/schema v1.2.2 requires php >=7.1 <8.2 -> your php version (8.2.2) does not satisfy that requirement.
Problem 2
- nette/utils is locked to version v3.2.7 and an update of this package was not requested.
- nette/utils v3.2.7 requires php >=7.2 <8.2 -> your php version (8.2.2) does not satisfy that requirement.
Problem 3
- phpspec/prophecy is locked to version v1.15.0 and an update of this package was not requested.
- phpspec/prophecy v1.15.0 requires php ^7.2 || ~8.0, <8.2 -> your php version (8.2.2) does not satisfy that requirement.
Problem 4
- nette/schema v1.2.2 requires php >=7.1 <8.2 -> your php version (8.2.2) does not satisfy that requirement.
- league/config v1.1.1 requires nette/schema ^1.2 -> satisfiable by nette/schema[v1.2.2].
- league/config is locked to version v1.1.1 and an update of this package was not requested.

coba pakai php 7 kak


Unable to see consumer info

I started burrow but I cannot see consumers for any clusters, not sure what the issue is.
{"error":false,"message":"consumer list returned","consumers":[]}
I am using Kafka 0.9.
Below is my burrow configuration:
[general]
logdir=/Users/rrsingh/git/go/src/github.com/linkedin/burrow/log
logconfig=/Users/rrsingh/git/go/src/github.com/linkedin/burrow/config/logging.cfg
pidfile=burrow.pid
client-id=burrow-lagchecker

[zookeeper]
hostname=localhost
port=2181
timeout=60
lock-path=/burrow/notifier

[kafka "integrationCluster"]
broker=localhost
broker-port=9092
zookeeper=localhost
zookeeper-port=2181
zookeeper-path=/

[tickers]
broker-offsets=60

[lagcheck]
intervals=10
expire-group=604800

[httpserver]
server=on
port=8000

Am I missing anything?

Just found Burrow only supports consumers that are committing offsets to Kafka. Closing the issue.


Support access_role field for user object

Proposal: Replace is_admin with access_role.
Reasons:
There are currently 3 types of users ro (read-only), st (standard), and adm (admin). The library as-is (with is_admin field) only supports st (is_admin set to false) and adm (is_admin set to true). This means that read-only users will automatically be changed to standard users when this library is used to update a user, even if that was not the intention.
Why not keep both is_admin and access_role?
This results in confusing behavior, because it's unclear to users what the behavior is if I set is_admin to true and access_role to st.  Do I get a standard user? Do I get an admin user? The correct answer is that access_role takes precedence and is_admin will be ignored if they conflict.
| is_admin | access_role | resulting user |
| false    | ro          | ro             |
| true     | ro          | ro             |
| false    | st          | st             |
| true     | st          | st             |
| false    | adm         | adm            |
| true     | adm         | adm            |

@zorkian Let me know what you think about the proposal.

We can't break the API (which happens when methods are removed) unless we're rolling a new major version. I don't think we really want to do that for this particular change.
I agree that supporting both is_admin and access_role is confusing. Is the logic table you provided based on testing with how DataDog actually interprets the situation?
The easiest is just to allow both, but I think that it might be worth introducing some way of deprecating a field and saying 'you should convert to use this other field, this field will go away next major version'. That way people see it in their logs if they're using it and know about the unexpected behavior.
Thoughts?

The truth table is based on my testing of the actual API behavior.
I like the idea of somehow marking the field as deprecated and logging. Agreed that it would require a major version change to remove the field.

@zorkian
I see two options:

Add a comment to the struct field itself stating that this field is deprecated and will be removed in the next major version.
Update gen-accessors to support some custom annotation, something like:

type X struct {
    thing *string `json:"thing,omitempty" deprecated:"remove"`
    // OR maybe like this:
    thing *string `json:"thing,omitempty" go-datadog-api:"deprecated"`
}

With option 2, it would be possible to make the generated accessors add a fmt.Println or log.Info(or whatever) to say "hey this field field is deprecated and will be removed in the next major go-datadog-api library".
Option 1:
Pro: Simple to implement, still adds documentation in code that field is deprecated.
Con: Makes it non-obvious if users upgrade without reading the code that a field may be removed.
Option 2:
Pro: This might be nicer to users.
Con:

Much more difficult to implement. If we ever need to deprecate non-pointer types, there's not a clear path to do it (since the generators only generate functions for the pointers). Having two different ways to do deprecation will be confusing.
Users that are accessing fields without the generators (since the fields are still exported and can be used directly) will not as easily discover that the field is deprecated (would be easier to see with a big big DEPRECATED comment).

I prefer Option 1 (simple deprecated comment), but if you'd prefer Option 2, I could try to update the generator.
I went ahead and updated the PR to add back in IsAdmin, along with a comment noting its deprecation.


Nagle delays affect mail sending throughput

Since upgrading from V3 to V4 we had noticed that the sending throughput dropped to 10 mails per second (with the bottleneck not being mail generation or MTA, but some kind of "waiting delay that generates no server load).
It has taken quite some time to get to the bottom of this but we finally got there. This is all done against Swift Mailer 4.04, but I have checked the code in 4.1 and it is the same. It turns out that the reason is Nagle Delays:
http://en.wikipedia.org/wiki/Nagle's_algorithm
We are using postfix as our MTA, so I posted this to the postfix users list:
http://archives.neohapsis.com/archives/postfix/2011-07/0009.html
Here is the answer from the man who wrote postfix:
http://archives.neohapsis.com/archives/postfix/2011-07/0011.html
So the problem is that Swift mailer:
a) sends the "<CR><LF>.<CR><LF>" separately from the message body
b) uses an fsockopen stream which does not have the full set of socket options (if using the socket_extension it would be possible to set TCP_NODELAY to eliminate Nagle delays http://www.php.net/manual/en/function.socket-get-option.php ).
This effectively limits the throughput to just 10 mails per second in our setup which had system wide nagle wait time set to 100ms (the default for FreeBSD).
As a workaround I changed the system wide Nagle delay as described in my response on the postfix list:
http://archives.neohapsis.com/archives/postfix/2011-07/0018.html

So I changed the system wide Nagle behaviour on the server, which is a freebsd system.
http://lists.freebsd.org/pipermail/freebsd-stable/2008-June/043325.html
sysctl net.inet.tcp.delacktime=10
(default 100ms)
Which reduced 90% of the delay.
Not ideal, but fine in this case, since most of the traffic to that host is LAN or very high speed WAN.

Oliver
Original creation date: 2011-07-04T08:33:00Z
Original reporter: Oliver Schonrock
Original ticket: http://swiftmailer.lighthouseapp.com/projects/21527/tickets/204

This has been reverted for now because of #131


Transformers

Description of your changes
This is the initial pass at transformers functionality. I imagine that we'll implement a composition CRD that will embed this resource but I'm not sure at that point whether keeping this stuff in this repo will make sense. Opened the PR to gather initial feedback.
Note: For some reason, controller-gen tries to generate deep copy functions for Resolve interface as well. I've removed the interface in the last commit for the sake of opening the PR, though I wasn't sure about its usefulness in the first place as seen in a TODO note below. Feel free to provide thoughts.
Note2: EquateConditions is moved to apis/core/v1alpha1 where Condition struct is implemented because otherwise it's not possible to import test package in v1alpha1 and I needed it for EquateErrors.
Both of the notes above are separated with their own commits so that it's easier to skip them during review.
Fixes #131
Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[x] Updated any relevant documentation, examples, or release notes.
[x] Updated the RBAC permissions in clusterrole.yaml to include any new types.

@muvaf mentioned he was implementing this in crossplane/crossplane for the time being, so I'll close out this PR.


Remove deprecated options id and title from spo list webhook list

When working on the issue #3812 I found out that the command spo list webhook list still contains the deprecated options id and title, which are replaced by listId and listTitle. I've also noticed that these properties still exist in the v6 branch, so I think that they should be removed.

Fair point @MathijsVerbeeck!
There are probably more places with deprecated options. Since v6 release is next month, let's list them all and remove them all together.

When checking the code, following commands still have deprecated options:

Command
Deprecated options

spo list webhook list
title and id

spo site add
allowFileSharingForGuestUsers

teams team set
displayName

Sure, @milanholemans

Awesome! All yours

@milanholemans I will start working on this as soon as pr #3839 is approved, as this contains changes from one of the commands.

While working on issue #3813 , I found out that listitem-list also contains deprecated options id and title.


Split /tmp/docker-mailserver into two different directories

Context
There are two different approaches for handling config files in Docker containers:

Config files can be copied into the docker images and are either not edited (or edited in a reproducible way at runtime).
They can also be stored in persistent volumes where they can be edited by admins.

These approaches are more or less exclusive because config files found in Docker images do not override existing files in persistent volumes (they are copied into the volumes when the volume is created but if they are modified afterwards these modifications are not applied in containers even if the image is rebuilt).
If I understand correctly, docker-mailserver mixes these approaches in 3 different ways:

A limited number of config files are stored in the /tmp/docker-mailserver and copied during the server startup where they belong into /etc/
A number of config files are modified in /etc/ by the startup script according to the values of environment variables passed to the container.
Other config files can be copied into /etc/ in the image itself using standard Docker commands.

The first two bullet points correspond to features which are most frequently customized.
Expected Behavior
It should be possible to decide whether you prefer to edit config files directly in persistent volumes or if you prefer to copy updates into Docker images and rebuild your container.
This should be possible by simply mounting /tmp/docker-mailserver on a persistent volume or not.
Actual Behavior
The issue is that currently /tmp/docker-mailserver contains both fixed config files such as default sieve rules and "variable" config files edited by the container itself such as DKIM keys or postfix accounts.
This means that if you don't mount /tmp/docker-mailserver as a persistent volume you'll loose important stuff such as your entire user database while if you do mount it as a persistent volume you'll loose the ability to define (and update) configuration options such as sieve rules through Docker images.
And, BTW, it is not possible to simply omit to defined default sieve rules in /tmp/docker-mailserver and just copy them where they belong within /etc because the startup script deletes them if they do not exist in /tmp/docker-mailserver.
Possible Fix

A simple fix would be use two separate directories for "admin defined" config files and for "container managed" config files.
It would be possible to keep backward compatibility by testing whether or not these directories are split (and maybe printing a deprecation message if they are not).

If you decide to proceed with this, please target the next image rather than master. We will switch soon so when it gets time to merge we will almost certainly be running next.

OK, thanks !

Very interesting idea @evlist :+1:
Were you able to make in progress on this?

@chikamichi

Were you able to make in progress on this?

No, not yet. To be honest once you get a config working it's not a big issue and it has become a low priority for me.
If there is some interest I can spend more time on this, though.

This issue was closed due to one or more of the following reasons:

Age
Contributor inactivity
The issue seems to be resolved

If you think this happened by accident, or feel like this issue was not actually resolved, please feel free to re-open it. If there is an issue you could resolve in the meantime, please open a PR based on the current master branch so we can review it.


Error on inference of extended generic type for rest parameters since TS 2.0

Inference of extended generic type for rest parameters, it fails only when the type of rest parameter is number or string since TS2.0. When the rest parameter is number or string, then compiler understands the generic type not to its origin type number or string, but its value.

There's a method push<U extends T>(...args: U[]): number in std.List<string>
When calls List<string>.push("A", "B", "C"), then U be "A", not string.

The exact error messages is:

The type argument for type parameter 'U' cannot be inferred from the usage. Consider specifying the type arguments explicitly. Type arguments candidate "A" is not a valid type argument because it is not a supertype of candidate "B"

The code what I used is:
namespace std
{
    export class List<T>
    {
        public push<U extends T>(...args: U[]): number;
    }
}

let x std.List<number>;
let y: std.List<string>;

x.push(1, 2, 3, 4, 5); // FAILED. Understands U is 1
y.push("A", "B", "C", "D", "E"); // FAILED. Understands U is "A"

x.push<number>(1, 2, 3, 4, 5); // OK
y.push<string>("A", "B", "C", "D", "E"); // OK

This is an expected behavior of literal types. List<string>.push  is instantiated to List.push<U extends string>. So the compiler infer "A" to its literal type.
https://github.com/Microsoft/TypeScript/pull/10676

@HerringtonDarkholme I don't think this is correct behavior. In 2.0.3 it fails as stated by the OP but in 2.1.0-dev.20160924 it gives no error and the type of U is 1 | 2 | 3 | 4 | 5 in the first call and "A" | "B" | "C" | "D" | "E" in the second

This change was caused by changes in the generic type inference rules for literal types in  https://github.com/Microsoft/TypeScript/pull/10676. Now string and numeric literal types will be inferred if the generic type parameter has a constraint of string or number respectivelly. Moreover the rule of failing if no best common super-type for inferencesis relaxed in the case of literal types if they have the same base type (e.g. string). So in TS 2.1 (typescript@next today) ,as noted by @aluanhaddad, U will be inferred to be 1 | 2 | 3 | 4 | 5 in the first call and  "A" | "B" | "C" | "D" | "E" in the second


Incorrect calculation for data clamping in Mesh Viewer

I have a problem where some of my draws are incorrectly rendered in Mesh Viewer. The cause seems to be this line, that clamps the rendered vertex/row count to 100:
https://github.com/baldurk/renderdoc/blob/19c066c6fc65bda0d75de0d2b8c8055081bf190d/qrenderdoc/Windows/BufferViewer.cpp#L1532
It seems to me that the correct arithmetic would be '+' instead of '-' to calculate the buffer byte offset.

Hi there, your issue has been closed due to not correctly following the issue template. Please read the documentation about filing issues and open a new issue which does follow the issue template. Do not reply to this issue with more information or with a correctly formatted issue, as that will only lead to confusion.
I try to address all github issues and fix bugs quickly, but badly formatted issues or poorly described bug reports especially are a significant drain on project resources. Taking a few minutes to file a good issue makes a huge difference and will get it addressed faster - everybody wins!
In github when you first create a new issue the form is pre-populated with a template which you should read over and follow. As linked above there is documentation going into more detail about what makes a good issue.


[Bug] "IndexError: list index out of range" from az pipelines list ...

Describe the bug
Attempting to list releases in my client's Azure DevOps instance returned a Python IndexError.
To Reproduce
Azure CLI version: azure-cli 2.0.62
Azure DevOps extension version: azure-devops 0.4.0
Steps:

Install the Azure DevOps extension with az extension add --name azure-devops.
Run az login and click through the browser window to a successful login.
Run az pipelines release list --org <client org> --project <client project> --top 3 and receive the below error.

Expected behaviour
A list of the 3 most recent releases from the nominated org & project should be shown.
Debug logs
DEBUG: Command arguments: ['pipelines', 'release', 'list', '--org', '<client org>', '--project', '<client project>', '--top', '3', '--debug']
DEBUG: Event: Cli.PreExecute []
DEBUG: Event: CommandParser.OnGlobalArgumentsCreate [<function CLILogging.on_global_arguments at 0x102137268>, <function OutputProducer.on_global_arguments at 0x1021cd0d0>, <function CLIQuery.on_global_arguments at 0x1021e66a8>]
DEBUG: Event: CommandInvoker.OnPreCommandTableCreate []
DEBUG: Installed command modules ['acr', 'acs', 'advisor', 'ams', 'appservice', 'backup', 'batch', 'batchai', 'billing', 'botservice', 'cdn', 'cloud', 'cognitiveservices', 'configure', 'consumption', 'container', 'cosmosdb', 'dla', 'dls', 'dms', 'eventgrid', 'eventhubs', 'extension', 'feedback', 'find', 'hdinsight', 'interactive', 'iot', 'iotcentral', 'keyvault', 'kusto', 'lab', 'maps', 'monitor', 'network', 'policyinsights', 'privatedns', 'profile', 'rdbms', 'redis', 'relay', 'reservations', 'resource', 'role', 'search', 'security', 'servicebus', 'servicefabric', 'signalr', 'sql', 'sqlvm', 'storage', 'vm']
DEBUG: Loaded module 'acr' in 0.004 seconds.
DEBUG: Loaded module 'acs' in 0.003 seconds.
DEBUG: Loaded module 'advisor' in 0.001 seconds.
DEBUG: Event: CommandLoader.OnLoadCommandTable []
DEBUG: Loaded module 'ams' in 0.004 seconds.
DEBUG: Loaded module 'appservice' in 0.015 seconds.
DEBUG: Loaded module 'backup' in 0.003 seconds.
DEBUG: Event: CommandLoader.OnLoadCommandTable []
DEBUG: Loaded module 'batch' in 0.007 seconds.
DEBUG: Loaded module 'batchai' in 0.002 seconds.
DEBUG: Loaded module 'billing' in 0.002 seconds.
DEBUG: Loaded module 'botservice' in 0.003 seconds.
DEBUG: Event: CommandLoader.OnLoadCommandTable []
DEBUG: Loaded module 'cdn' in 0.002 seconds.
DEBUG: Loaded module 'cloud' in 0.001 seconds.
DEBUG: Loaded module 'cognitiveservices' in 0.001 seconds.
DEBUG: Loaded module 'configure' in 0.001 seconds.
DEBUG: Loaded module 'consumption' in 0.002 seconds.
DEBUG: Loaded module 'container' in 0.002 seconds.
DEBUG: Loaded module 'cosmosdb' in 0.003 seconds.
DEBUG: Loaded module 'dla' in 0.003 seconds.
DEBUG: Loaded module 'dls' in 0.003 seconds.
DEBUG: Loaded module 'dms' in 0.002 seconds.
DEBUG: Loaded module 'eventgrid' in 0.002 seconds.
DEBUG: Loaded module 'eventhubs' in 0.002 seconds.
DEBUG: Loaded module 'extension' in 0.001 seconds.
DEBUG: Loaded module 'feedback' in 0.001 seconds.
DEBUG: Loaded module 'find' in 0.001 seconds.
DEBUG: Loaded module 'hdinsight' in 0.002 seconds.
DEBUG: Loaded module 'interactive' in 0.001 seconds.
DEBUG: Loaded module 'iot' in 0.003 seconds.
DEBUG: Loaded module 'iotcentral' in 0.001 seconds.
DEBUG: Loaded module 'keyvault' in 0.006 seconds.
DEBUG: Loaded module 'kusto' in 0.002 seconds.
DEBUG: Loaded module 'lab' in 0.003 seconds.
DEBUG: Loaded module 'maps' in 0.001 seconds.
DEBUG: Loaded module 'monitor' in 0.004 seconds.
DEBUG: Loaded module 'network' in 0.024 seconds.
DEBUG: Loaded module 'policyinsights' in 0.002 seconds.
DEBUG: Loaded module 'privatedns' in 0.003 seconds.
DEBUG: Loaded module 'profile' in 0.001 seconds.
DEBUG: Loaded module 'rdbms' in 0.005 seconds.
DEBUG: Loaded module 'redis' in 0.002 seconds.
DEBUG: Loaded module 'relay' in 0.005 seconds.
DEBUG: Loaded module 'reservations' in 0.001 seconds.
DEBUG: Loaded module 'resource' in 0.006 seconds.
DEBUG: Loaded module 'role' in 0.003 seconds.
DEBUG: Loaded module 'search' in 0.001 seconds.
DEBUG: Loaded module 'security' in 0.003 seconds.
DEBUG: Loaded module 'servicebus' in 0.003 seconds.
DEBUG: Loaded module 'servicefabric' in 0.001 seconds.
DEBUG: Loaded module 'signalr' in 0.001 seconds.
DEBUG: Loaded module 'sql' in 0.005 seconds.
DEBUG: Loaded module 'sqlvm' in 0.002 seconds.
DEBUG: Event: CommandLoader.OnLoadCommandTable []
DEBUG: Loaded module 'storage' in 0.025 seconds.
DEBUG: Loaded module 'vm' in 0.012 seconds.
DEBUG: Loaded all modules in 0.199 seconds. (note: there's always an overhead with the first module loaded)
DEBUG: Extensions directory: '/Users/jameslucktaylor/.azure/cliextensions'
DEBUG: Found 1 extensions: ['azure-devops']
DEBUG: Extensions directory: '/Users/jameslucktaylor/.azure/cliextensions'
DEBUG: Loaded extension 'azure-devops' in 0.018 seconds.
DEBUG: Event: CommandInvoker.OnPreCommandTableTruncate [<function AzCliLogging.init_command_file_logging at 0x102269ae8>]
INFO: az_command_data_logger : command args: pipelines release list --org {} --project {} --top {} --debug
DEBUG: metadata file logging enabled - writing logs to '/Users/jameslucktaylor/.azure/commands'.
DEBUG: Event: CommandInvoker.OnPostCommandTableCreate [<function register_global_subscription_argument.<locals>.add_subscription_parameter at 0x102287ae8>, <function register_ids_argument.<locals>.add_ids_arguments at 0x1022bf400>]
DEBUG: Event: CommandInvoker.OnCommandTableLoaded []
DEBUG: Event: CommandInvoker.OnPreParseArgs [<function _documentdb_deprecate at 0x1031de048>]
DEBUG: Event: CommandInvoker.OnPostParseArgs [<function OutputProducer.handle_output_argument at 0x1021cd158>, <function CLIQuery.handle_query_parameter at 0x1021e6730>, <function register_ids_argument.<locals>.parse_ids_arguments at 0x1022bf488>, <function handler at 0x1032c9510>, <function DevCommandsLoader.post_parse_args at 0x103a4c9d8>]
DEBUG: Extensions directory: '/Users/jameslucktaylor/.azure/cliextensions'
DEBUG: Extensions directory: '/Users/jameslucktaylor/.azure/cliextensions'
INFO: az_command_data_logger : extension name: azure-devops
INFO: az_command_data_logger : extension version: 0.4.0
DEBUG: handling generic error
ERROR: cli.azure.cli.core.util : The command failed with an unexpected error. Here is the traceback:

ERROR: The command failed with an unexpected error. Here is the traceback:

ERROR: cli.azure.cli.core.util : list index out of range
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 326, in execute
    raise ex
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 384, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 375, in _run_job
    cmd_copy.exception_handler(ex)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/exception_handler.py", line 22, in azure_devops_exception_handler
    reraise(*sys.exc_info())
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/six.py", line 693, in reraise
    raise value
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 354, in _run_job
    result = cmd_copy(params)
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 145, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/__init__.py", line 451, in default_command_handler
    return op(**command_args)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/pipelines/release.py", line 101, in release_list
    client = get_release_client(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/services.py", line 150, in get_release_client
    connection = get_vss_connection(team_instance)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/services.py", line 32, in get_vss_connection
    credentials = _get_credentials(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/services.py", line 45, in _get_credentials
    if PAT_ENV_VARIABLE_NAME in os.environ or get_credential(organization) is not None:
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 17, in get_credential
    token = _get_credential(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 24, in _get_credential
    key = _get_service_name(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 76, in _get_service_name
    return 'azdevops-cli:' + normalize_url_for_key(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 85, in normalize_url_for_key
    organization_name = organization_name.split('/')[1]
IndexError: list index out of range
ERROR: list index out of range
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 326, in execute
    raise ex
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 384, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 375, in _run_job
    cmd_copy.exception_handler(ex)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/exception_handler.py", line 22, in azure_devops_exception_handler
    reraise(*sys.exc_info())
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/six.py", line 693, in reraise
    raise value
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 354, in _run_job
    result = cmd_copy(params)
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 145, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.0.62/libexec/lib/python3.7/site-packages/azure/cli/core/__init__.py", line 451, in default_command_handler
    return op(**command_args)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/pipelines/release.py", line 101, in release_list
    client = get_release_client(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/services.py", line 150, in get_release_client
    connection = get_vss_connection(team_instance)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/services.py", line 32, in get_vss_connection
    credentials = _get_credentials(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/services.py", line 45, in _get_credentials
    if PAT_ENV_VARIABLE_NAME in os.environ or get_credential(organization) is not None:
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 17, in get_credential
    token = _get_credential(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 24, in _get_credential
    key = _get_service_name(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 76, in _get_service_name
    return 'azdevops-cli:' + normalize_url_for_key(organization)
  File "/Users/jameslucktaylor/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 85, in normalize_url_for_key
    organization_name = organization_name.split('/')[1]
IndexError: list index out of range
WARNING: cli.azure.cli.core.util :
To open an issue, please run: 'az feedback'
WARNING:
To open an issue, please run: 'az feedback'
INFO: az_command_data_logger : exit code: 1
INFO: telemetry.save : Save telemetry record of length 2636 in cache
WARNING: telemetry.check : Negative: The /Users/jameslucktaylor/.azure/telemetry.txt was modified at 2019-04-12 10:18:56.036003, which in less than 600.000000 s
INFO: command ran in 0.289 seconds.

Environment Summary
Darwin-18.5.0-x86_64-i386-64bit
Python 3.7.3
Shell: bash

azure-cli                         2.0.62

Extensions:
azure-devops                       0.4.0

Python location '/usr/local/Cellar/azure-cli/2.0.62/libexec/bin/python'
Extensions directory '/Users/jameslucktaylor/.azure/cliextensions'

Python (Darwin) 3.7.3 (default, Mar 27 2019, 09:23:15)
[Clang 10.0.1 (clang-1<IP_ADDRESS>)]

Additional Context
I have removed the names of my client's private org and project from the command arguments supplied above.

This is dupe of https://github.com/Azure/azure-devops-cli-extension/issues/429
relevant stack trace showing the same
  File "/Users/jaraco/.azure/cliextensions/azure-devops/azext_devops/dev/common/_credentials.py", line 85, in normalize_url_for_key     organization_name = organization_name.split('/')[1] IndexError: list index out of range
Closing this as duplicate.
This is not fixed but the issue will be tracked using a single issue which will be https://github.com/Azure/azure-devops-cli-extension/issues/429

Thanks for reporting this @jlucktay  !!!


Adjust encryption tests to check sqlite3mc

Adjust existing tests to work with sqlite3mc (access with default encryption scheme)
Add tests for accessing SQLCipher encrypted databases via sqlite3mc

@ericsink
Unfortunately, the encryption tests failed again. The reason is that obviously the test database files were not copied to the working directory of the test application. When a database file is not found SQLite will create a new database file (unless told otherwise). And of course the new empty database file doesn't have the tables that are queried.
I had added the following lines in the test project files:
  <ItemGroup>
    <None Update="..\common\sqlcipher-2.0-beta-testkey.db" CopyToOutputDirectory="PreserveNewest" />
    <None Update="..\common\sqlcipher-4.0-testkey.db" CopyToOutputDirectory="PreserveNewest" />
  </ItemGroup>

That had worked in my own repo, but does not here. What do I have to specify that the database files are copied to the right directory?

Ah, I see.  I hadn't looked at the PR content at all yet, so I didn't notice those new files.  Up until now, tests_xunit.cs hasn't needed any dependencies.
The first problem I see is that the two csproj files you modified are not actually the ones used during tests.
Sorry for the confusion -- this repo isn't very intuitive.
Let me take a look at this myself.  You've written the tests.  I'll try to get them integrated.

Ah, I see. I hadn't looked at the PR content at all yet, so I didn't notice those new files. Up until now, tests_xunit.cs hasn't needed any dependencies.

I would love to get away without dependent database files. Theoretically, the library could generate encrypted database files on its own, but that would make the test useless, because it would only prove that the library can read and write databases created by itself. But we want to test that we can read and write original SQLCipher database files.

The first problem I see is that the two csproj files you modified are not actually the ones used during tests.

Oops, I haven't searched at different locations after having found the project files I modified.

Let me take a look at this myself. You've written the tests. I'll try to get them integrated.

Obviously, you managed to do that. Thanks.

Actually so far I just merged the PR leaving it broken. I'm working now on fixing it. 😬

Actually so far I just merged the PR leaving it broken. I'm working now on fixing it. 😬

Yeah, I saw that now, but only after I had already submiited my previous comment.
It shouldn't be too difficult to fix, once the right project file(s) is/are identified.


Update automation-create-runas-account.md

If you remove the service principal from the subscription it is no longer possible to update the Azure Powershell modules in the Automation account.

@theheatDK : Thanks for your contribution! The author, @georgewallace, has been notified to review your proposed change.

@theheatDK : Thanks for your contribution! The author, @georgewallace, has been notified to review your proposed change.

@theheatDK Thank you for the contribution! I don't feel the addition fits well in the context of the article, it is added in a section talking about limiting the permissions of a run as account.  I do feel this would be good to add into the Update Azure modules doc you link to in the addition, and feel that this would be good to add to the troubleshooting docs, though I am in the process of creating a general one which I will add it to.  I am going to close this PR as I don't feel it fit the context of the article, but if you want to open a new PR and update the https://docs.microsoft.com/en-us/azure/automation/automation-update-azure-modules article I would be more than happy to merge it .. Something along the lines of....... "Azure Automation uses the AzureRunAsConnection connection to authenticate when updating the modules, if the service principal is expired or no longer exists, the module update will fail."

#please-close


Getting error even after deleting xivalexander

Does anyone know why I still encounter this error despite deleting xivalexander? I have tried finding xivalexander from all over the place and deleting them already. Do I need to reinstall my game?

If you do not have d3d9.dll, d3d11.dll, and dinput8.dll in your game directory, it is not about XivAlexander. If you use FFXIVQuickLauncher, you might want to try integrity check.

From the uninstall manual, I tried to follow all the paths that xivalexander could be in and just deleted them. I may or may not have accidentally deleted something related to the actual game. Is there anyway to completely get rid of all the xivalexander on my computer?

Do I need to delete the config.xivalexinit.json file as well?

Cuz I am still getting this error when trying to login the game, it seems that there are some residual xivalexander left somewhere? How do I completely get rid of it?


Fix: Undefined classes, some more

This PR

[x] fixes issues where classes seemed undefined
[x] fixes issues where to many imports were used
[x] fixes / adds doc-blocks (helps with auto-completion)
[x] sorts a few imports alphabetically

Hi @localheinz same problem of #32 :)
Maybe after first cs-fix run and implementation into travis-ci the code will be beautiful! :)


Add a new feature of streaming the response out to stdout

Feature
The application now supports two methods of retrieving responses from chatCompletion. The first method allows users to export the response to an output file using the -o/--output flag. The second method prints the entire response to the console at once.
In this new feature, the goal is to implement real-time streaming of responses directly to the console (stdout) rather than outputting everything at once.
Implementation

Introduce a new argument option -s/--stream.
Use the for await ... of loop to asynchronously iterate over the chatCompletion response stream, handling each data chunk and streaming it to stdout in real-time.
Track token usage throughout the process.

Notes

Since the response will be streamed, the method of tracking token usage differs from the non-streaming approach.
For streaming, the token usage object can only be accessed after processing the final chunk in the loop.
By default, when using the -s/--stream flag without specifying an output file via -o/--output, the response will be streamed and displayed in the console in real time. However, if the user wants to export the response to a file, they can specify the output file using the -o/--output flag.

Closed by dd671de


[SPARK-15294][SPARKR][MINOR] Add pivot functionality to SparkR

What changes were proposed in this pull request?
Added pivot functionality to SparkR
How was this patch tested?
R package sucesfully builds and loads

Can one of the admins verify this patch?

Jenkins, ok to test

Thanks @mhnatiuk for opening this PR. Could we also add a unit test in test_sparkSQL.R for this ?

Test build #59288 has started for PR 13295 at commit b276420.

Test build #59288 has finished for PR 13295 at commit b276420.

This patch fails some tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59288/
Test FAILed.

Test build #59371 has started for PR 13295 at commit d85b7c5.

Test build #59371 has finished for PR 13295 at commit d85b7c5.

This patch fails some tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59371/
Test FAILed.

Test build #59372 has started for PR 13295 at commit 62ba93c.

Test build #59372 has finished for PR 13295 at commit 62ba93c.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59372/
Test FAILed.

Test build #59373 has started for PR 13295 at commit 02812ee.

Test build #59373 has finished for PR 13295 at commit 02812ee.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59373/
Test FAILed.

Test build #59375 has started for PR 13295 at commit 3f51903.

Test build #59375 has finished for PR 13295 at commit 3f51903.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59375/
Test PASSed.

Jenkins, retest this please

Test build #59378 has started for PR 13295 at commit 3906c70.

Test build #59378 has finished for PR 13295 at commit 3906c70.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59378/
Test FAILed.

Jenkins, retest this please

Test build #59379 has started for PR 13295 at commit 4e6e47e.

Test build #59379 has finished for PR 13295 at commit 4e6e47e.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59379/
Test FAILed.

Jenkins, retest this please

Test build #59380 has started for PR 13295 at commit 6f3d723.

Test build #59380 has finished for PR 13295 at commit 6f3d723.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59380/
Test FAILed.

Jenkins, retest this please

Can one of the admins verify this patch?

Jenkins, add to whitelist

Jenkins, ok to test

Test build #59459 has started for PR 13295 at commit 6f3d723.

Test build #59459 has finished for PR 13295 at commit 6f3d723.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59459/
Test FAILed.

Jenkins, retest this please

Test build #59616 has started for PR 13295 at commit 385bb67.

Test build #59616 has finished for PR 13295 at commit 385bb67.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59616/
Test FAILed.

Merged build finished. Test FAILed.

Test build #59617 has started for PR 13295 at commit 323f2bb.

Test build #59617 has finished for PR 13295 at commit 323f2bb.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59617/
Test FAILed.

Jenkins, retest this please

Test build #59620 has started for PR 13295 at commit b0de2c2.

Test build #59620 has finished for PR 13295 at commit b0de2c2.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59620/
Test FAILed.

Jenkins, retest this please

Test build #59621 has started for PR 13295 at commit 529db9b.

Test build #59621 has finished for PR 13295 at commit 529db9b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59621/
Test PASSed.

Test build #59643 has started for PR 13295 at commit 8813e2e.

Test build #59643 has finished for PR 13295 at commit 8813e2e.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59643/
Test FAILed.

Test build #59646 has started for PR 13295 at commit eda0ffe.

Test build #59646 has finished for PR 13295 at commit eda0ffe.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59646/
Test FAILed.

Test build #59649 has started for PR 13295 at commit f2b8d97.

Test build #59649 has finished for PR 13295 at commit f2b8d97.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59649/
Test FAILed.

@mhnatiuk It looks like the tests are failing with the error message I've pasted below. From reading the code I think this is related to the if check we have in the pivot implementation where it should be length(values) != length(unique(values)) instead of == as we have right now ?
1. Error: pivot GroupedData column ---------------------------------------------
error in evaluating the argument 'x' in selecting a method for function 'collect':
  error in evaluating the argument 'x' in selecting a method for function 'summarize':
  Values in list are not unique
Calls: pivot -> pivot

@dongjoon-hyun @felixcheung -- I think @mhnatiuk is busy. If you have time it will be cool to submit another version of this PR as I think this is a useful function for R users.

This will be really useful. I'll make this PR up-to-date and adds credit description for @mhnatiuk .

@mhnatiuk Given that #13786 was merged, can you close this PR ? Only the PR authors have permission to close a PR in the Spark project

I'll close that. Is it indicated that I did some work on that? Thanks.
MH
2016-06-21 7:46 GMT+02:00 Shivaram Venkataraman<EMAIL_ADDRESS>
@mhnatiuk https://github.com/mhnatiuk Given that #13786
https://github.com/apache/spark/pull/13786 was merged, can you close
this PR ? Only the PR authors have permission to close a PR in the Spark
project
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/spark/pull/13295#issuecomment-227346131, or mute
the thread
https://github.com/notifications/unsubscribe/ACMWZOzHz1cwt1Gi3L8pOtQe5yQbBIfEks5qN3qZgaJpZM4ImkSl
.

#13786 that finishes this work, was merged into branch-2.0. Closing.


feat(examples): Linearlite Example

This is an example of a team collaboration app such as Linear built using ElectricSQL.
This example is built on top of the excellent clone of the Linear UI built by Tuan Nguyen - The original is here https://github.com/tuan3w/linearapp_clone.
This example uses Vite for tooling.
Builds on the work in https://github.com/electric-sql/electric/pull/221

Data for this demo is attached here: data.zip
Unzip this into examples/linearlite/db/data/
This demo is not part of the pnpm workspace, I have been using vanilla npm to build it. (I had issues getting it to run via pnpm as part of the workspace)
Quickest way to get the demo running is:
npm run reset
npm run start

reset will:

shuts down and removes any old backend (backend:down)
starts a new clean backend (backend:up)
migrates the db (db:migrate)
generates the client (client:generate)
loads the data into PG (db:load-data)

Then start will start the vite dev server.
To build the production distribution: npm run build

There are two ways in production to reset the db to a clean state:

npm run db:reload-data will do a DELETE FROM issues; DELETE FROM comments and then reload the data
Nuking the Postgres and starting from scratch, the client will see the database schema has changed and delete the local indexedDB.

Just a couple of suggestions:

At the moment, the "[icon] electric" in the top left links back to electric-sql.com, I suggest maybe it links to the home page of this demo -- we have the project link in the dropdown and I was surprised to be taken out of context when clicking on it to go back to the route listings.
The issue listing is called "React issues" -> seems a bit odd out of context. I know the idea is its issues in your workspace. Perhaps "Your issues" for now?
The Kanban board is super cool but a bit buried under the nested "Board" link. I wonder if we can make more prominent / change the label and maybe add an icon?

Also, if I play with the drag and drop enough I get:

Btw, all examples use yarn in the readme so for the sake of consistency we may want to use yarn instead of npm in this readme too.

Btw, all examples use yarn in the readme so for the sake of consistency we may want to use yarn instead of npm in this readme too.

I don't think the examples should use yarn, TBH we should change them all to use npm, anyone that uses yarn knows how to rewrite a npm command to yarn.

@kevin-dp I have resolved most of your comments, I will log an issue in Linear to refactor types/issue.ts (I really don't like that whole file) and process_data.js


Update index.md

Typo - corrected 'Bitlocker' to 'BitLocker'

@AndreaBarr A PR with a minor typo fix is available for review. Thanks.


why rules are in the test/ folder?

I see that YAML files with rules are located in the test/ directory. This seems to be wrong, since these rules are released in the final binary package.

@deemp please, check

@yegor256 the file with the rules contains unit tests, and they belong to test/.
We embed these rules into the binary (https://github.com/objectionary/eo-phi-normalizer/blob/73213648ececf65b2cc804efd0306f27109179ad/eo-phi-normalizer/app/Main.hs#L594) using a relative path, and it doesn't really matter where the file is located if it's inside the eo-phi-normalizer directory.
One downside of the current location is that the rules aren't very discoverable without visiting the site and looking at examples of commands that use the file with rules.
Which location do you suggest?

@deemp in Java world, we have a convention: everything that belongs to the JAR to be shipped to the user goes to the src/main/ directory, while everything else that used only in testing goes to src/test/. In your case, maybe you can have two dirs: src/ and test/. This separation is important, because it helps every developer to understand quickly which part of the app they deal with: production or test.


Passing the ID from button to Span If have

Set the Id or name to the Button however the event.target.id or event.target.name of the click event is empty.

[ ] This is not a v0.x issue.
[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The Id or name should not be empty.
Current Behavior

The Id or name is empty.
Steps to Reproduce

Link:

Create a button with Id provided
Handle event click with e parameter
the id and name of e.target are empty.

Context

Your Environment

Tech
Version

Material-UI
v1.?.?

React

Browser

TypeScript

etc.

Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!

@baoduy https://github.com/mui-org/material-ui/issues/10534#issuecomment-370558590


Link to Signal is broken

Issue in /src/pages/documentation/mobile-core/index.md
The link to the Signal extension in the Signal section is broken.

Fixed in #210


python311Packages.amaranth-boards: fix src hash

Description of changes
https://github.com/NixOS/nixpkgs/pull/292102#issuecomment-1977710234
Verified on master, i'll let my staging build run overnight

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Seen on staging-next, please retarget.

Rebase?

took a while to setup the staging worktrees on the new host ;)

nom build github:nixos/nixpkgs/refs/pull/293373/merge#python31{1,2}Packages.amaranth-boards builds for me. I'm not sure if it is common to wait on ofborg eval on staging-next PRs, so I'll defer the merge to you. Good night :)


SCB-332 Wrong json output format in zipkin file collector

(cherry picked from commit 3f48ccb)
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run go build go test go fmt go vet to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.2%) to 74.065% when pulling 81114f53e17f66960cec6bffec84e22dd5ea8bac on little-cui:master into 6e70ed2f2c1e5c934ed011527601d83ee9df8b85 on apache:master.

Codecov Report

Merging #278 into master will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #278      +/-   ##
==========================================
+ Coverage   70.33%   70.36%   +0.02%
==========================================
  Files          17       17
  Lines        3418     3418
==========================================
+ Hits         2404     2405       +1
  Misses        846      846
+ Partials      168      167       -1

Impacted Files
Coverage Δ

server/service/rule.go
77.25% <0%> (+0.42%)
:arrow_up:

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 6e70ed2...81114f5. Read the comment docs.


async combinators for Stream

Our stream combinators operate on asynchronous data, but are themselves synchronous.
This means it's not possible to for example filter or map a stream based on other async operations. Which seems limiting, as it's possible to call sync functions from async functions but not the other way around.
I'd like to propose we update our Stream combinators that take closures to be async functions.
cc/ @montekki
ref #129

How would this be represented in the type system currently? Can you write an example for the map combinator to illustrate? I believe this is blocked on traits AsyncFn, AsyncFnOnce, and AsyncFnMut.
Still, I believe combinators with async closures should be representable with the  stream! syntax. For example, the equivalent of s.map(async |x| x.await) could be written as:
let s = stream! {
    for x in s {
        yield x.await;
    }
};

Oh dang yeah; it being
So we currently don't have map, but futures::Stream::map is defined as:
fn map<T, F>(self, f: F) -> Map<Self, F> where
    F: FnMut(Self::Item) -> T;

When used on a stream of number this is roughly as stream.map(|i| i * 2);. However this is problematic when say we want to call an async fn from within the map, e.g. stream.map(async |i| db.lookup(i).await);. For that our map combinator would need to be defined as:
fn map<T, F, G>(self, f: F) -> Map<Self, F> where
    F: FnMut(Self::Item) -> G,
    G: Future<Output = T>;

You're right in pointing out we don't have async closures yet. But we can somewhat pretend we do as this is valid on Rust 1.39:
stream.map(|i| async { db.lookup(i).await });

However ideally we could have an actual AsyncFn trait as part of stdlib, and an automatic mapping going from Fn to AsyncFn so it's treated as a strict superset of the regular closures. But that's a bit further out in the future, and I think we'll be able to incorporate that in a backwards-compatible way.

So we currently don't have map, but futures::Stream::map is defined as:

Many combinators of futures_util::stream other than Map use FnMut(T) -> impl Future closures.
https://docs.rs/futures-preview/0.3.0-alpha.19/futures/stream/trait.StreamExt.html#method.filter_map

@taiki-e Why do filter and filter_map use async closures but map doesn't? Was that intentional or is that just an oversight?

@stjepang Maybe it ’s an oversight. I will file an issue.

@yoshuawuyts assign this to me please

@taiki-e is this by design that next() is not usable with those combinators? So this will not work:
let s = stream::iter(1u8..10);
let mut s = s.filter_map(|a| async move { Some(a) });

while let Some(n) = s.next().await {
      println!("next {}", n);
}

since next() is bound by Unpin.

@montekki
You need to use pin_utils::pin_mut (or Box::pin)
let s = stream::iter(1u8..10);
let s = s.filter_map(|a| async move { Some(a) });
pin_utils::pin_mut!(s);

while let Some(n) = s.next().await {
      println!("next {}", n);
}

next takes &mut self for ergonomics. If this is Pin<&mut Self>, you need to call .as_mut() every time.

It looks like currently there is no way to make this work for combinators like filter that involve a predicate taking parameters by ref, is there?

Yeah, currently, it needs to use future::ready or async function. (Those problems will be fixed if async closure is improved.)
(As it was updated to use async-await in https://github.com/rust-lang-nursery/futures-rs/pull/1843, futures's StreamExt documentation should be somewhat useful. (And I think those implementations will definitely be useful.)

It looks like in any case taking by ref won't work, not only for async closures:
   |
12 | let mut s = s.filter(|i: &usize| async move { i % 2 == 0 });
   |                      -----------            ^^^^^^^^^^^^^^ cannot be stored outside of its closure
   |                      |
   |                      ...because it cannot outlive this closure
13 |
14 | pin_utils::pin_mut!(s);
   | ----------------------- borrowed data cannot be stored into here...

Yeah, current async closures are equivalent to closures which return async blocks.

Is this no longer planned, given that async-std reached 1.0?


Created a fork to add Autocomplete selectField appBar swipe for next ...etc

The majority of change is a merge between feature of old material-ui and material-next...

[ ] PR has tests / docs demo, and is linted.
[ ] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[ ] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

@simonjoom Could you clean up the diff? I'm not sure what's going on here.

Well, that PR is most likely on the wrong repository, I'm closing it.


[HUDI-647] Change community.html page with new PPMC/committers

What is the purpose of the pull request
This pull request changed community.html page with new PPMC/committers
Brief change log

Change community.html page with new PPMC/committers

Verify this pull request
This pull request is a trivial rework / code cleanup without any test coverage.
Committer checklist

[x] Has a corresponding JIRA in PR title & commit

[x] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

thanks !


fixed typos in readme and a small issue with whitespace

There were a few typos in the readme file (Constellaton instead of Constellation).
In addition, when there are no collection, the message in the empty pane has overflown the width. I fixed it by adding white-space: normal; in the .Constellation_empty selector (BTW, there is are 2 partially overriding entries for it in the css).
PS,
The rest of the changes in the css file were whitespace autofixes by my editor I did not notice until now.

Thank you for this.  Much appreciated!