thinp: Implementation of Thin Logical Volumes support

Pending:
from proposal:

https://github.com/topolvm/topolvm/pull/442#discussion_r828765950 inputs about the implementation is needed
https://github.com/topolvm/topolvm/pull/442#discussion_r828706602 inputs about the final decision

general:

no regressions as per unit tests and need to look into e2e runs from CI and add new e2e tests wrt thinpool
document updates about thinpool
decisions/inputs on TODO, most of those doesn't effect the functionality though

ps: pls review by commit bases, I tried to segregate them as a logical unit
ref: https://github.com/topolvm/topolvm/pull/442

@llamerada-jp

regarding the movement of cards for this PR, this is actually re-viewable and only reason I moved it to draft is to make sure that there are no regressions in e2e
if the team doesn't review draft PR I'll remove that status.

@leelavg
We check progress and move the cards in our daily meetings. Would you please change the state to Ready for review after passing the CI? We will assign reviewers.

ack, facing some issues with running CI in local environment
many complaints from kind and minikube while running e2e in fedora machines
if we create a new ubuntu machine and install golang & docker in it, rest of the env setup will be taken care by make targets right?

if we create a new ubuntu machine and install golang & docker in it, rest of the env setup will be taken care by make targets right?
Yes, it is. The document and configs for CI will help you, I hope.
https://github.com/topolvm/topolvm/tree/main/e2e#how-to-run-tests
https://github.com/topolvm/topolvm/blob/main/.github/workflows/e2e-k8s.yaml

created a new ubuntu VM
installed golang and docker via snap
facing below issue

 ✗ Preparing nodes 📦 📦 📦 📦
ERROR: failed to create cluster: docker run error: command "docker run --hostname topolvm-e2e-worker --name topolvm-e2e-worker --label io.x-k8s.kind.role=worker --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run --volume /var --volume /lib/modules:/lib/modules:ro --detach --tty --label io.x-k8s.kind.cluster=topolvm-e2e --net kind --restart=on-failure:1 --init=false --volume=/dev:/dev --volume=/tmp/topolvm/lvmd1:/tmp/topolvm --volume=/tmp/topolvm/worker1:/var/lib/kubelet:rshared kindest/node:v1.23.3" failed with error: exit status 125
Command Output: 3d7e4ca1b3056d4489d973d450e9a95a47c15911ac2e2648573bff9173bffeab
docker: Error response from daemon: path /tmp/topolvm/worker1 is mounted on /tmp but it is not a shared mount.
Makefile:89: recipe for target 'launch-kind' failed
make[1]: *** [launch-kind] Error 1
make[1]: Leaving directory '/home/ubuntu/topolvm/e2e'
Makefile:163: recipe for target 'create-cluster' failed
make: *** [create-cluster] Error 2

@llamerada-jp I ran the failed test locally and could see it's passing locally. Picked k8s version 1.22.2 as it has the most passed matrix in https://github.com/topolvm/topolvm/actions/runs/2016111597
KUBERNETES_VERSION='1.22.2' TEST_SCHEDULER_MANIFEST='daemonset' STORAGE_CAPACITY='false' SKIP_NODE_FINALIZE='false' make test
Ran 72 of 112 Specs in 2198.174 seconds
SUCCESS! -- 72 Passed | 0 Failed | 1 Pending | 39 Skipped
PASS

Ginkgo ran 1 suite in 41m20.211613736s```

@leelavg
I tried to reproduce this case like below locally, but I couldn't.
KUBERNETES_VERSION='1.21.2' TEST_SCHEDULER_MANIFEST='daemonset' STORAGE_CAPACITY='false' SKIP_NODE_FINALIZE='false' make test

I re-ran the CI.

I guess this logic list up extra volumes.
@llamerada-jp yes, it does list thin logical volumes as well, so filtering them out in call site (GetLVList) if the request is on volumegroup by below logic (for thinlv poolname will be set).

		if dc.Type == TypeThick && lv.GetPoolName() != "" {
			// do not send thin lvs if request is on TypeThick
			continue
		}

It's OK to fix code, exclude about overprovision-ratio.

so filtering them out in call site (GetLVList) if the request is on volumegroup by below logic (for thinlv poolname will be set).

I'll check it again.

Cool! Now the e2e also has cleanly passed with no regressions, so the existing functionality isn't effected 😀

@llamerada-jp

thanks a lot for your reviews, they are helpful in simplifying the code in some places

I (re)reviewed watch and metrics. I'm going to review the tests. Do you have a plan to add e2e tests?

updated the PR description, they'll be part of another PR
my goal for this PR is, thin provisioning implementation and changes in vg/lv services for proto changes, unit tests to verify these and no regressions in e2e
then we'll have a build which can be used in the operator to do admin tasks and so e2e will be raised later however surely they'll be in before next release

you can proceed with reviewing the unit-tests as I don't see your recent comments will have less effect unit-tests, thanks.

don't trigger the CI yet, it seems I missed out a commit while force pushing 😢
let me fix that

@leelavg

ci was failing during make check-uncommited

git diff --exit-code --name-only
csi/csi.pb.go
lvmd/proto/lvmd.pb.go

Would you try to re-generate some file like below when nect commit?
rm csi/csi.pb.go lvmd/proto/lvmd.pb.go
make csi/csi.pb.go lvmd/proto/lvmd.pb.go

@leelavg

ci was failing during make check-uncommited

I made a mistake. This diff caused by a known bug. I have just been told by a colleague. Could you rebase after merging the PR below?

Could you rebase after merging the PR below?

np, I always rebase before each force push.
last commit to main was 20 days ago, or you want me to rebase on a PR after that specific PR is merged? If yes, pls let me know the PR with fix.

rebased, added extra unit test, addressed comments.

@llamerada-jp removed obsolete TODO's


added use fixture loader option

use container service objects for fixtures
Hi @yceruto,
Can you please review and merge this PR as want to use service container objects of fixtures rather then creating with new $class() as its not working when we have constructor dependencies in Fixture classes.
Let me know if there are any feedback.
thanks,

Before publishing a new release for these changes, can you please test it on your Bitbucket PR and ping me? thanks!


Failing tests

https://travis-ci.org/phpDocumentor/ReflectionCommon/jobs/627700228

Well, I expected 74a67151cce to fix the build... but the analysis stage isn't running now...


feat(pages): add /application/guilds/join

What changes this PR introduce?
Add the features needed for the page /application/guilds/join
Is there anything you'd like reviewers to focus on?
I updated dependencies and did some refactor, so focus your review mostly on these 2 files: components/Application/JoinGuildsPublic/JoinGuildsPublic.tsx and pages/application/guilds/join.tsx.

LGTM!

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


[Schema][Fix] Add Conditionals to PET Recon Method

Updates conditionals for:
ReconMethodParameterValues
Attempts to change schema to be amenable to numbers where an array would be a length of 1.
E.g. for single frame images -> ScatterFraction=1.5 and would both be valid ScatterFraction[1.5].
Not married to that second change, I think it would be better to update the wording of the spec so we only ever look for arrays, see changes to ScatterFraction in src.schema.objects.metadata in this PR.
See Chris's latest update to the schema readme for more context/info about selectors and logic.

Add rule for units too, if 'none'.


[TEST] Fix SFDC Connection Test

Addresses change made in #2706

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f plugins/salesforce/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f plugins/salesforce/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  plugins/salesforce/test-src/org/pentaho/di/trans/steps/salesforce/SalesforceConnectionIT.java

Newly Fixed Tests:
org.pentaho.di.trans.steps.salesforce.SalesforceConnectionIT.testConnect_Encrypted:
:red_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: expected:<[MySamplePassword]> but was:<[Encrypted 2f3e1fca907d79e819b18bd63c99dbdde]>
	at org.pentaho.di.trans.steps.salesforce.SalesforceConnectionIT.testConnect(SalesforceConnectionIT.java:118)
	at org.pentaho.di.trans.steps.salesforce.SalesforceConnectionIT.testConnect_Encrypted(SalesforceConnectionIT.java:92)

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -.15%:small_red_triangle_down:


Could not find org.permissionsdispatcher:permissionsdispatcher:2.3.2.

Could not find org.permissionsdispatcher:permissionsdispatcher:2.3.2.

Please use com.github.hotchemi:permissionsdispatcher:2.3.2


Add integration tests for ODM features

Which kicks-off the support for #26
Depends on #38

Hi, I'm not able to try this out because of:
  Problem 1
    - alcaeus/mongo-php-adapter 1.1.x-dev requires ext-mongodb ^1.2.0 -> the requested PHP extension mongodb is missing from your system.
    - alcaeus/mongo-php-adapter 1.1.5 requires ext-mongodb ^1.2.0 -> the requested PHP extension mongodb is missing from your system.
    - alcaeus/mongo-php-adapter 1.1.4 requires ext-mongodb ^1.2.0 -> the requested PHP extension mongodb is missing from your system.
    - alcaeus/mongo-php-adapter 1.1.3 requires ext-mongodb ^1.2.0 -> the requested PHP extension mongodb is missing from your system.
    - alcaeus/mongo-php-adapter 1.1.2 requires ext-mongodb ^1.2.0 -> the requested PHP extension mongodb is missing from your system.
    - alcaeus/mongo-php-adapter 1.1.1 requires ext-mongodb ^1.2.0 -> the requested PHP extension mongodb is missing from your system.
    - alcaeus/mongo-php-adapter 1.1.0 requires ext-mongodb ^1.2.0 -> the requested PHP extension mongodb is missing from your system.
    - Installation request for alcaeus/mongo-php-adapter ^1.1 -> satisfiable by alcaeus/mongo-php-adapter[1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.x-dev].

I think it shouldn't be necessary to have installed mongodb extension in order to develop this package. What is it exactly required for?

Because of the tests: they need to import ODM classes. You could remove the dependency, skip the tests if ODM isn’t installed and only install it on travis. However, as changing something might break ODM functionality, I would recommend to keep this as is. This extension is supposed to cover ORM and ODM, so it’s expected to have both as a dev dependency.

Is it just because of some use or ::class or is actually some code from alcaeus/mongo-php-adapter executed?

All the tests run fine if I remove alcaeus/mongo-php-adapter from composer.json, and without mongodb installed

All the tests run fine if I remove alcaeus/mongo-php-adapter from composer.json, and without mongodb installed

Correct, because you're pretending that the mongo extension is installed. You can skip the adapter package until you actually start using the ODM classes, at which point they'll fail if they can't find the classes you pretend are there.

Superceded by #48.


Jagged edges when container is animated

I'm doing a 'pop' animation on a profile picture that's using your code to make it a circle. When I have the scale animation attached to the container it's in then the edges of the circle are really jagged. When I don't have any animation on the profile picture it looks complete fine.
I'm also not quite sure why the size of the image changes either. I'm scaling from 1.0 to 0.9 back to 1.0.
Thanks!

The jagged edges are probably due to Android scaling it and not using anti aliasing for performance reasons, I can add this.
It should scale it to the full size.
Do you have a working sample repo I can use to fix it ?
Thanks

@christophesmet Unfortunately I don't have a working sample repo to post since it's baked into a clients app that I can't share the code from.
Here's the basic set up that I have it in:
`
                <com.christophesmet.android.views.maskableframelayout.MaskableFrameLayout
                    android:id="@+id/photoMask"
                    android:layout_width="35dp"
                    android:layout_centerHorizontal="true"
                    app:porterduffxfermode="DST_IN"
                    app:mask="@drawable/cutout_photo_mask"
                    android:layout_height="35dp">

                    <ImageView
                        android:layout_width="35dp"
                        android:layout_height="35dp"
                        android:id="@+id/pfAvatar"
                        android:layout_centerHorizontal="true" />

                </com.christophesmet.android.views.maskableframelayout.MaskableFrameLayout>

            </RelativeLayout>`

And then I'm animating the avatarWrapper relativelayout with this code:
<scale         android:fromXScale="1.0"         android:toXScale="0.9"         android:fromYScale="1.0"         android:toYScale="0.9"         android:pivotX="50%"         android:pivotY="50%"         android:startOffset="1200"         android:duration="400" />     <scale         android:fromXScale="0.9"         android:toXScale="1.0"         android:fromYScale="0.9"         android:toYScale="1.0"         android:pivotX="50%"         android:pivotY="50%"         android:startOffset="1600"         android:duration="200" />
Hope that helps a little bit in replicating!

I think you are running the 2 scale animations side by side or only the first one.
Again without any project, this is hard to help with.
Greets

@christophesmet They both seem to run properly. It has a start offset on it so that the first one goes and then the next one. I see them both happen when I watch it, the animation itself is perfect it's just the jagged edges on my circle that are off. Yeah I know this is hard to test for you and see what might fix it just thought I'd give it a try in case you knew something off the top of your head. No worries, thanks for replying :)

The jagged edges I can fix, but I'm not sure why the size is incorrect :s
Is the end size incorrect when using a normal framelayout instead of the masked framelayout ?

Yeah I believe so, it seems to change the size when the scaling animation is applied. I'm ok with the size being different then the non-animated on though since you don't actually see that difference in reality. When the animation is applied it is always that smaller size so it doesn't impact anything. All that I really am looking for is the jagged edges to not be there.

Here's what the animation looks like: https://www.youtube.com/watch?v=cOrCTMg9-gg&feature=youtu.be

Strange, I tried the scale animation on the test project and I don't get the jagged edged.
Did you change the layer type of the view ?
I added an xml attribute in the latest commit on the master branch to enable anti-aliasing.
Can you check it out and see if it works ?
If not, please try to replicate it with the test project, as I can't reproduce it :(
Thanks !

Ok awesome I'll take a look at that and try these options, thanks!

Ok I tried the new version and it didn't work. I've downloaded a copy of the sample project and tried there as well and I'm still getting the jagged edge there too. Here's a zip of the sample project so you can see how it's looking jagged there as well.
android_maskable_layout-master.zip


Old project Could not copy the file "*\Plugins\ARM\SpatialUnderstanding.dll" because it was not found

An older project from Unity 2017 gives me this error while trying to deploy on the Hololens 2.
How do I fix this or how do i disable the SpatialUndestanding, there does not seem to be an ARM version present of this DLL.
Severity	Code	Description	Project	File	Line	Suppression State Error	MSB3030	Could not copy the file "D:\Builds\ShoeConfiguratorARM\Shoes Configurator\Plugins\ARM\SpatialUnderstanding.dll" because it was not found.	Shoes Configurator	D:\Builds\ShoeConfiguratorARM\Shoes Configurator\Unity Data.vcxitems	217

Sorry I confused this with the other repo which I couldn't find
moved here https://github.com/microsoft/MixedRealityToolkit/issues/234


It will have some problem, when I use it in transparent background image.

It happened in transparent background image(.png)
Such as this image:

when i call:
const newCanvas = scale({
      scaleX: this.outputWidth / this.originWidth,
      scaleY: this.outputHeight / this.originHeight
}, canvas);

It will return new canvas which the background is black.
So can you help me to solve it?
Thx.

@FiShelly I look into this issue :)
Which program do you use, scale.min.js or scale-nonalpha.min.js? If you want to work with transparent images like png, you need to use scale.min.js.

@FiShelly I look into this issue :)
Which program do you use, scale.min.js or scale-nonalpha.min.js? If you want to work with transparent images like png, you need to use scale.min.js.

Oh!!!
I got it.
I do not set HAS_ALPHA.
Thx so much.

The problem seems to be resolved, so I will close this issue.
If you have any additional problems, you can reopen this issue.


"Prices defined for regions not targeted by the app."

I started getting this error frequently when attempting to upload new prices with the apiclient
googleapiclient.errors.HttpError: <HttpError 403 when requesting https://www.googleapis.com/androidpublisher/v2/applications/com.udemy.android/inappproducts/android.course.479974?alt=json&autoConvertMissingPrices=true returned "Prices defined for regions not targeted by the app.">

turns out the addition of Liechtenstein screwed us up. Needed to enable it in the Pricing & Distributions section of the Play Store


I can't get it up and running...?!

Hi guys,
I just installed everything as it is said, but there is an error that occurs - NgGrid - cannot find module NgGrid.
What am I supposed to do to make it work? I really need the functionality of this module.
Could you help and give detailed instructions how to make it work without system-js. I am using the angular-cli.
Thanks!

#179 I think you have the same problem.
We found a workaround (see the issue) until @BTMorton fix the bug.
The problem is angular evolve very quickly (with major update like the management of module) and all the libs are not up to date with the latest version.

@NotBad4U  Thanks a lot, mate! Could you tell me how can I configure the grid items, because when I use an empty directive as [(ngGridItem)] it throws me an error like this:
Parser Error: Unexpected token = at column 1 in [=$event]
From where should I load the configs?

Add the import statement import { NgGridConfig, NgGridItemConfig } from "./angular2-grid/interfaces/INgGrid"; (with the path relative to where is your angular2-grid copy)
and to all of your "Box" set the config field:
this.boxes[i].config = _generateDefaultItemConfig();

private _generateDefaultItemConfig(): NgGridItemConfig {
		return { 'dragHandle': '.handle', 'col': 1, 'row': 1, 'resizable': true, 'minWidth': 10, 'minHeight': 10, 'sizex': 1, 'sizey': 1 };
}

See the demo provide or the code in /src/app.component.ts. And take a look at the readme for more details of how  to configure in details the grid and the grid items.

I got it working! Thanks a lot! Just one more question: Is there a possibility to define the Items in a div and then another div with predefined width and height to be the gridContainer. And then to drag and drop the items into the container div.
I tried doing it with jQuery UI, but unfortunately, I could make it with it, because it was giving me an error of type .draggable() is not a function.
Would you suggest something regarding this?

There currently isn't support for having an external drop target. It's been requested before if you look through the other issues. I'm closing this now, as the main issue should be sorted.


NaN found and optimization stopped

Hello, I am trying to do hyperparameter optimization using Bayesian optimization for neural networks. However, I encountered this issue:
ValueError: Input contains NaN, infinity or a value too large for dtype('float64').
The weird thing is that when I try to run the same net where Bayesian optimization stops in a separate network (without optimization) I do not have any issue (no NaN’s found as mean squared error, i.e. the fitness, or anything else).
Do you know where this error come from?
(Similar issue to #178 , why was this closed?)

With further investigation I found out that I was not seeding properly my script: when I did seed it properly I obtained the NaN also in the RNN w/o optimization. So this is not a proble related to your library, but rather a problem of the RNN (the gradient explodes, as pointed out here: https://stackoverflow.com/questions/37232782/nan-loss-when-training-regression-network).
However, I think it would still be helpful for users not to make the optimization crash when it encounters NaN or Inf.

Hi Sceki, I ran into the same issue. When the Bayesian optimizer gets a nan value for the mse (e.g, for one of the hyperparameter groups selected), it sometimes crashed with this error. Is this not an issue with the tuner itself? Shouldn't it be able to handle this case?


Documentation Improvement

Description
This PR currently includes

Nesting of the Fundamental, Data Integration, Use-cases, How-to menu
Merging pages in Fundamental Menu and the How-to menu
Renaming  of the pages in the Fundamental, Data Integration, Use-cases, How-to menu
Repositioning of the FAQ nearer to the Welcome Menu
Deactivation of the community support pages

Please keep in mind that no page was deleted. They are not just reflected in the documentation UI

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (34830a7) 80.33% compared to head (8331c74) 65.45%.
Report is 1443 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1777       +/-   ##
===========================================
- Coverage   80.33%   65.45%   -14.89%
===========================================
  Files          95      120       +25
  Lines        6602     8613     +2011
===========================================
+ Hits         5304     5638      +334
- Misses       1298     2975     +1677

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Do not try to terminate TBB if fork was called not from main thread

This is an attempt to fix #5973
TBB termination routines must always be called from same thread TBB was initialized.
But python.multiprocessing creates separate thread to manage its child processes.
Also multiprocessing can use either fork or spawn  strategies, but internally spawn is just fork + exec and there is no way to separate these 2 cases from pthread_atfork perspective.
Only fork from main thread is 'safe' and do TBB finalization/init only from main thread. Child processes forked from other threads can have TBB in invalid state, but they won't crash if user won't use TBB there. And this is better than immediately crashing parent process on fork from 'wrong' thread.
This is not ideal, but I don't see better solution yet.
CC @stuartarchibald

Thanks for the PR @Hardcode84, I hope the contents of #5973 helped determine the problem? Thanks also for adding an explanation as to some of the cause of the segfault(s), it's really helpful. As the debugging in #5973 got narrower in scope it became apparent that the multiprocesing.pool was causing the issue, at which point we suspected threads+fork and that switching to plain multiprocessing.Process in https://github.com/numba/numba/pull/6200 would fix and also hint further at the problem. It's really great that you found the root cause :) thanks for doing that!
I'll take a look at the code and have a think about what the implications are for Numba. It might be also that we document permitted behaviours too as part of this.
Thanks again!

Windows is failing. Can probably skip the test on windows as it relies on os.fork(). Also, interestingly the windows failure is cannot pickle '_thread.lock' object!

https://github.com/numba/numba/commit/972ece8672191c24d1c94d1063cae359b9a399b0 adds the skip

and here's some docs https://github.com/stuartarchibald/numba/commit/c9e9e8ff4b73604f17ffe6b3c22f8e9e1c5ed9ba, feel free to cherry-pick if you are happy with them, thanks!

Cherry-picked

@sklam This patch now contains a bunch of code I've written, please could you take a look? I've checked the C++ impl at it looks good.

Buildfarm ID: numba_smoketest_cpu_71.

Buildfarm ID: numba_smoketest_cpu_71.

This failed, in some seemingly random cases event objects were not picklable. @Hardcode84 please could you add https://github.com/stuartarchibald/numba/commit/80f8eaaa5026266cd1afa13523e11012488cfdf0 to this branch, it puts the event objects into globals for the jitted functions which should help mitigate the pickling problem. Thanks.

please could you add stuartarchibald@80f8eaa

done

please could you add stuartarchibald/numba@80f8eaa

done

many thanks

Buildfarm ID: numba_smoketest_cpu_74.

Finally got a workaround for the invalid pickle object bug, it's in https://github.com/numba/numba/pull/6324 which has now passed on the farm. @Hardcode84 sorry to have to ask you to pull in another patch, but https://github.com/numba/numba/pull/6324/commits/a2cc68a5c9cf5b07ca4c0f8b9eddca8d94cc406b seems to fix the issue in the test, so please could you add that to this branch? Thanks.
Once that's done, the patch to tbbpool.cpp looks good to me, @sklam please could you check the python test I wrote, then if everyone is happy this can be merged as the diff should match https://github.com/numba/numba/pull/6324 which has already passed testing.
Thanks all!

a2cc68a seems to fix the issue in the test, so please could you add that to this branch?

done

numba_smoketest_cpu_74 failed on all internal build farm tasks w/o any identifieable error. Presuming a glitch in the build-farm and re-triggered this.

So, the task test_linux_64_py3.8_npy1.19 failed, the first failure is due to lack of Numpy 1.19 support on this PR (the support was merged to master recently). I am posting it here, because I am not sure the followup issue is because of this too, or if it is a separate issue.
[2020-10-09 08:58:34,522] {docker_operator.py:265} INFO - ======================================================================
[2020-10-09 08:58:34,524] {docker_operator.py:265} INFO - ERROR: test_ediff1d_edge_cases (numba.tests.test_np_functions.TestNPFunctions)
[2020-10-09 08:58:34,527] {docker_operator.py:265} INFO - ----------------------------------------------------------------------
[2020-10-09 08:58:34,528] {docker_operator.py:265} INFO - Traceback (most recent call last):
[2020-10-09 08:58:34,529] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/tests/test_np_functions.py", line 2150, in test_ediff1d_edge_cases
[2020-10-09 08:58:34,531] {docker_operator.py:265} INFO - _check_raises_type_error(params, 'to_begin')
[2020-10-09 08:58:34,532] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/tests/test_np_functions.py", line 2117, in _check_raises_type_error
[2020-10-09 08:58:34,533] {docker_operator.py:265} INFO - pyfunc(**params)
[2020-10-09 08:58:34,535] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/tests/test_np_functions.py", line 241, in ediff1d
[2020-10-09 08:58:34,536] {docker_operator.py:265} INFO - return np.ediff1d(ary, to_end, to_begin)
[2020-10-09 08:58:34,536] {docker_operator.py:265} INFO - File "<__array_function__ internals>", line 5, in ediff1d
[2020-10-09 08:58:34,536] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numpy/lib/arraysetops.py", line 107, in ediff1d
[2020-10-09 08:58:34,537] {docker_operator.py:265} INFO - raise TypeError("dtype of `to_end` must be compatible "
[2020-10-09 08:58:34,537] {docker_operator.py:265} INFO - TypeError: dtype of `to_end` must be compatible with input `ary` under the `same_kind` rule.
[2020-10-09 08:58:34,537] {docker_operator.py:265} INFO -
[2020-10-09 08:58:34,537] {docker_operator.py:265} INFO - ======================================================================
[2020-10-09 08:58:34,538] {docker_operator.py:265} INFO - FAIL: test_fork_from_non_main_thread (numba.tests.test_parallel_backend.TestTBBSpecificIssues)
[2020-10-09 08:58:34,538] {docker_operator.py:265} INFO - ----------------------------------------------------------------------
[2020-10-09 08:58:34,538] {docker_operator.py:265} INFO - Traceback (most recent call last):
[2020-10-09 08:58:34,539] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/tests/test_parallel_backend.py", line 912, in test_fork_from_non_main_thread
[2020-10-09 08:58:34,539] {docker_operator.py:265} INFO - out, err = self.run_cmd(cmdline)
[2020-10-09 08:58:34,539] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/tests/test_parallel_backend.py", line 475, in run_cmd
[2020-10-09 08:58:34,539] {docker_operator.py:265} INFO - raise AssertionError(
[2020-10-09 08:58:34,540] {docker_operator.py:265} INFO - AssertionError: process failed with code -9: stderr follows
[2020-10-09 08:58:34,540] {docker_operator.py:265} INFO - Exception in thread Thread-1:
[2020-10-09 08:58:34,540] {docker_operator.py:265} INFO - Traceback (most recent call last):
[2020-10-09 08:58:34,540] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/errors.py", line 738, in new_error_context
[2020-10-09 08:58:34,540] {docker_operator.py:265} INFO - yield
[2020-10-09 08:58:34,541] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 230, in lower_block
[2020-10-09 08:58:34,541] {docker_operator.py:265} INFO - self.lower_inst(inst)
[2020-10-09 08:58:34,542] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 327, in lower_inst
[2020-10-09 08:58:34,542] {docker_operator.py:265} INFO - val = self.lower_assign(ty, inst)
[2020-10-09 08:58:34,543] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 502, in lower_assign
[2020-10-09 08:58:34,543] {docker_operator.py:265} INFO - return self.lower_expr(ty, value)
[2020-10-09 08:58:34,543] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 1023, in lower_expr
[2020-10-09 08:58:34,543] {docker_operator.py:265} INFO - res = self.lower_call(resty, expr)
[2020-10-09 08:58:34,543] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 745, in lower_call
[2020-10-09 08:58:34,543] {docker_operator.py:265} INFO - res = self._lower_call_ObjModeDispatcher(fnty, expr, signature)
[2020-10-09 08:58:34,543] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 797, in _lower_call_ObjModeDispatcher
[2020-10-09 08:58:34,543] {docker_operator.py:265} INFO - callee = ObjModeUtils(self.pyapi).load_dispatcher(fnty, argtypes)
[2020-10-09 08:58:34,544] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/pythonapi.py", line 1626, in load_dispatcher
[2020-10-09 08:58:34,544] {docker_operator.py:265} INFO - if serialize.is_serialiable(fnty.dispatcher):
[2020-10-09 08:58:34,545] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/serialize.py", line 267, in is_serialiable
[2020-10-09 08:58:34,545] {docker_operator.py:265} INFO - pickler.dump(obj)
[2020-10-09 08:58:34,545] {docker_operator.py:265} INFO - TypeError: cannot pickle '_thread.lock' object
[2020-10-09 08:58:34,545] {docker_operator.py:265} INFO -
[2020-10-09 08:58:34,545] {docker_operator.py:265} INFO - During handling of the above exception, another exception occurred:
[2020-10-09 08:58:34,546] {docker_operator.py:265} INFO -
[2020-10-09 08:58:34,546] {docker_operator.py:265} INFO - Traceback (most recent call last):
[2020-10-09 08:58:34,546] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/threading.py", line 932, in _bootstrap_inner
[2020-10-09 08:58:34,547] {docker_operator.py:265} INFO - self.run()
[2020-10-09 08:58:34,547] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/threading.py", line 870, in run
[2020-10-09 08:58:34,547] {docker_operator.py:265} INFO - self._target(*self._args, **self._kwargs)
[2020-10-09 08:58:34,547] {docker_operator.py:265} INFO - File "<string>", line 20, in runner
[2020-10-09 08:58:34,548] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/dispatcher.py", line 433, in _compile_for_args
[2020-10-09 08:58:34,548] {docker_operator.py:265} INFO - raise e
[2020-10-09 08:58:34,548] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/dispatcher.py", line 366, in _compile_for_args
[2020-10-09 08:58:34,548] {docker_operator.py:265} INFO - return self.compile(tuple(argtypes))
[2020-10-09 08:58:34,548] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
[2020-10-09 08:58:34,548] {docker_operator.py:265} INFO - return func(*args, **kwargs)
[2020-10-09 08:58:34,548] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/dispatcher.py", line 818, in compile
[2020-10-09 08:58:34,548] {docker_operator.py:265} INFO - cres = self._compiler.compile(args, return_type)
[2020-10-09 08:58:34,548] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/dispatcher.py", line 77, in compile
[2020-10-09 08:58:34,549] {docker_operator.py:265} INFO - status, retval = self._compile_cached(args, return_type)
[2020-10-09 08:58:34,549] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/dispatcher.py", line 91, in _compile_cached
[2020-10-09 08:58:34,549] {docker_operator.py:265} INFO - retval = self._compile_core(args, return_type)
[2020-10-09 08:58:34,549] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/dispatcher.py", line 104, in _compile_core
[2020-10-09 08:58:34,549] {docker_operator.py:265} INFO - cres = compiler.compile_extra(self.targetdescr.typing_context,
[2020-10-09 08:58:34,549] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 602, in compile_extra
[2020-10-09 08:58:34,549] {docker_operator.py:265} INFO - return pipeline.compile_extra(func)
[2020-10-09 08:58:34,549] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 352, in compile_extra
[2020-10-09 08:58:34,549] {docker_operator.py:265} INFO - return self._compile_bytecode()
[2020-10-09 08:58:34,550] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 414, in _compile_bytecode
[2020-10-09 08:58:34,550] {docker_operator.py:265} INFO - return self._compile_core()
[2020-10-09 08:58:34,550] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 394, in _compile_core
[2020-10-09 08:58:34,550] {docker_operator.py:265} INFO - raise e
[2020-10-09 08:58:34,550] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 385, in _compile_core
[2020-10-09 08:58:34,551] {docker_operator.py:265} INFO - pm.run(self.state)
[2020-10-09 08:58:34,551] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_machinery.py", line 339, in run
[2020-10-09 08:58:34,551] {docker_operator.py:265} INFO - raise patched_exception
[2020-10-09 08:58:34,551] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_machinery.py", line 330, in run
[2020-10-09 08:58:34,551] {docker_operator.py:265} INFO - self._runPass(idx, pass_inst, state)
[2020-10-09 08:58:34,551] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
[2020-10-09 08:58:34,551] {docker_operator.py:265} INFO - return func(*args, **kwargs)
[2020-10-09 08:58:34,552] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_machinery.py", line 289, in _runPass
[2020-10-09 08:58:34,552] {docker_operator.py:265} INFO - mutated |= check(pss.run_pass, internal_state)
[2020-10-09 08:58:34,553] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_machinery.py", line 262, in check
[2020-10-09 08:58:34,553] {docker_operator.py:265} INFO - mangled = func(compiler_state)
[2020-10-09 08:58:34,553] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/untyped_passes.py", line 259, in run_pass
[2020-10-09 08:58:34,553] {docker_operator.py:265} INFO - cres = compile_ir(state.typingctx, state.targetctx, main,
[2020-10-09 08:58:34,553] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 665, in compile_ir
[2020-10-09 08:58:34,553] {docker_operator.py:265} INFO - return pipeline.compile_ir(func_ir=func_ir, lifted=lifted,
[2020-10-09 08:58:34,553] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 362, in compile_ir
[2020-10-09 08:58:34,553] {docker_operator.py:265} INFO - return self._compile_ir()
[2020-10-09 08:58:34,554] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 421, in _compile_ir
[2020-10-09 08:58:34,554] {docker_operator.py:265} INFO - return self._compile_core()
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 394, in _compile_core
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - raise e
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler.py", line 385, in _compile_core
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - pm.run(self.state)
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_machinery.py", line 339, in run
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - raise patched_exception
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_machinery.py", line 330, in run
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - self._runPass(idx, pass_inst, state)
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_lock.py", line 32, in _acquire_compile_lock
[2020-10-09 08:58:34,555] {docker_operator.py:265} INFO - return func(*args, **kwargs)
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_machinery.py", line 289, in _runPass
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - mutated |= check(pss.run_pass, internal_state)
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/compiler_machinery.py", line 262, in check
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - mangled = func(compiler_state)
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/typed_passes.py", line 443, in run_pass
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - NativeLowering().run_pass(state)
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/typed_passes.py", line 371, in run_pass
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - lower.lower()
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 136, in lower
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - self.lower_normal_function(self.fndesc)
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 190, in lower_normal_function
[2020-10-09 08:58:34,556] {docker_operator.py:265} INFO - entry_block_tail = self.lower_function_body()
[2020-10-09 08:58:34,557] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 216, in lower_function_body
[2020-10-09 08:58:34,557] {docker_operator.py:265} INFO - self.lower_block(block)
[2020-10-09 08:58:34,557] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/lowering.py", line 230, in lower_block
[2020-10-09 08:58:34,557] {docker_operator.py:265} INFO - self.lower_inst(inst)
[2020-10-09 08:58:34,557] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/contextlib.py", line 131, in __exit__
[2020-10-09 08:58:34,559] {docker_operator.py:265} INFO - self.gen.throw(type, value, traceback)
[2020-10-09 08:58:34,559] {docker_operator.py:265} INFO - File "/opt/conda/envs/testenv_4a275dee-ab51-4b96-a2b4-6364d78d8ca8/lib/python3.8/site-packages/numba/core/errors.py", line 745, in new_error_context
[2020-10-09 08:58:34,559] {docker_operator.py:265} INFO - raise newerr.with_traceback(tb)
[2020-10-09 08:58:34,559] {docker_operator.py:265} INFO - numba.core.errors.LoweringError: Failed in nopython mode pipeline (step: Handle with contexts)
[2020-10-09 08:58:34,559] {docker_operator.py:265} INFO - Failed in nopython mode pipeline (step: nopython mode backend)
[2020-10-09 08:58:34,559] {docker_operator.py:265} INFO - cannot pickle '_thread.lock' object
[2020-10-09 08:58:34,559] {docker_operator.py:265} INFO -
[2020-10-09 08:58:34,560] {docker_operator.py:265} INFO - File "<string>", line 14:
[2020-10-09 08:58:34,560] {docker_operator.py:265} INFO - <source missing, REPL/exec in use?>
[2020-10-09 08:58:34,560] {docker_operator.py:265} INFO -
[2020-10-09 08:58:34,560] {docker_operator.py:265} INFO - During: lowering "$36 = call $35(func=$35, args=[], kws=(), vararg=None)" at <string> (14)

This patch series was merged in https://github.com/numba/numba/pull/6324 which has been through build and test on the farm. Thanks for your work on this @Hardcode84.


Fl api

Anything I can help with here? Thanks!

@geemus Not really. That PR was a rookie mistake. I use the branch at work and failed when i pushed it.

No worries. I suspected it might be something like that, but just wanted to double check just in case.

@geemus I sent a request to github support about this. Sorry for the inconvenience, this is kinda a pollution of the development history.


How do I make the back and fill transparent

Thank you!

It's not currently supported.
If you are familiar with the PHP image api's you could probably hack up your version of the sparkline.php to do this.

Would you be able to help modify the code to export transparent image please?
Thank you!

Nope! :)


Highlight Row after edit

Is there a way for me to highlight a row or change the color of the row background (Ex. set to yellow) once I've finished editing the row?

Use onItemUpdated callback (http://js-grid.com/docs/#onitemupdated), in args of the callback you cn get a row and add a css class to the row.

I've got the highlight working, but the class name doesn't seem to stick if I were to move on to other pages on the grid and come back. It only applies to the current page. Is there a way to overcome that?

Yes, since grid data is refreshed, it doesn't know anything about your css class.
To keep the highlight after refresh you could do the following:

on onItemUpdated in args.item set some field, e.g. item.isNew = true (you can also do it on backend side).
set in the config rowClass: function(item) { return item.isNew ? 'is-new' : ''; }

rowClass: function(item, itemIndex) {
                    return itemIndex%2==0 ? 'bg-red' : 'bg-green';
                },

.bg-red td {
background-color: #f08080 !important;
}
.bg-green td{
background-color: #90ee90 !important;
}


.github: doc-build: move to west 1.0.0

The release notes are in and west==1.0.0 is installable via pypi. Move the doc build over to it and fix a typo while we are here.

@henrikbrixandersen see what I mean?

@henrikbrixandersen see what I mean?

Got it, thanks.


Ability to do parallel walking would be useful

From what I can tell, walk waits for the callback to events to be called before continuing, enforcing a series walk of the directory contents.
Given that it's mainly an I/O bound operation, it could benefit from parallelization in cases where order is not important.
Consider an option to make it walk in parallel. If you're feeling ambitious, provide an extra parameter to limit the max number of concurrent operations (similar to async.forEachLimit) to prevent an issue with max file handles on big walks.
Thanks for giving this some consideration,
Chris

Sorry for taking so long.
var walk = require('walk')
  , walkerCount = 2
  ;

function doStuffWithFiles(root, stat, next) {
  doStuff(root + '/' + stat.name, next);
}

function onEnd() {
  walkerCount -= 1;
  if (walkerCount) {
    return;
  }

  // close up shop
}

// a path on one device
walker0 = walk.walk('some/path0');
// a path on a physically different device
walker1 = walk.walk('some/path1');

walker0.on('file', doStuffWithFiles);
walker1.on('file', doStuffWithFiles);

walker0.on('end', onEnd);
walker1.on('end', onEnd);

Have you considered a solution such as this? (I should add this to some examples or something...)
Or does that not fit your use case?
I tried reasoning about logic for detecting when it's a different disk than the one that the path started on, but there seem to be a lot of cases where the behavior would be unexpected or unpredictable.
What are your thoughts?

I want to walk a single directory, but I don't want the walker to wait for the callback to be called from the file event to continue walking.
For parallel mode, all the file events should be emitted immediately (or X at a time), and the end event is emitted once all the callbacks are called.
In my particular case, I have an async operation in my file event handler. So, the walker is waiting for each handler to finish before allowing other handlers to begin.
Make sense?
Chris


Adds user data schema feature

Feature #704 - WIP
Changes proposed in this PR:

Revisit after v4


int128 for apis

Rust is failing because i128 is not a type that can be converted natively to a C++ type AFAICT. We need some sort of bridge to the equivalent C++ type. @Ashleyhx do you want me to look into this bridging?


line number wrapping issue fixed

I've noticed that the issue is still on https://showcode.app.
Please check this out.

Hi @cadlec! Thanks for the PR! I've just pushed a fix for this a moment ago -- can you try refreshing showcode.app and trying again?

Ok, nice @stevebauman
Thank you !

Happy to help @cadlec! 😄


Add Pants build tool

Per discussion https://github.com/coursier/coursier/issues/695
The only code change is at https://github.com/coursier/coursier/pull/709/files#diff-7ca3c74b5087813a533febc6b4a5a7a1R9 as coursier.properties is probably auto generated by sbt. Pants does support build properties but not in this fashion.
The commits are from repurposing other branches, but the actual change is purely declarative.

@wisechengyi You shoudn't need to add jackson as a dependency in this PR, do you?
That said, I can merge anyway if you'd like…

Ah thanks. Forgot to remove it since I was working backwards. Now removed.

Ok, so merging!
(A bit a pity that pants doesn't call its build files PANTS though…, like buck calls his, BUCK.)
Thanks @wisechengyi !

haha. actually there has been conversation about converging pants, bazel, and buck to use a common build language called skylark https://github.com/google/skylark. but no nothing immediate yet.


Kosaraju's algorithm c++

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Added Kosaraju's Algorithm in C++
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

@siddharth25pandey  I didnt get how to resolve merge conflicts. Can you please provide a tutorial or something related?

@siddharth25pandey I didnt get how to resolve merge conflicts. Can you please provide a tutorial or something related?

@devanshiv123 I have mentioned you in a thread on Slack Channel, do visit.

@siddharth25pandey  I did try those commands but I am getting some errors in pushing the branch later on.

I have made a new PR now. Please review it.

@all-contributors please add @devanshiv123 for code

@iamrajiv , As this PR has more number of commits than this which is actually not required. Anyways you have merged it. NP


webpack cache and module source

Sandbox for the issue with webpack cache and module source (NormalModule.originalSource()._value).
Linked to https://github.com/webpack/webpack/issues/16679 and https://github.com/webpack/webpack/discussions/16735

@TODO: Changes in JavaScript are not taken into account. If a svg file is delete from an entrypoint, the cache is not up to date

will be great to rewrite tests on real integration tests

@alexander-akait I only use unit tests with Jest and I don't know integration tests yet, could you quickly clarify what it would bring? And do you have an example that I could apply?
First I will correct the current unit tests for this PR. Do you think that's not enough?

First I will correct the current unit tests for this PR. Do you think that's not enough?

Yeah, because we have an example, it is a small integration test

@alexander-akait I only use unit tests with Jest and I don't know integration tests yet, could you quickly clarify what it would bring? And do you have an example that I could apply?

Just build webpack with your plugin, get stats (assets) and snapshot their content

Yeah, by the way webpack has API for such things:
const newFilename = compilation.getPath(this.options.filename, {
  filename: name,
});

So I think it can be replaced with it, also it is cachable, I don't sure about every [placeholder], but you can check it

@alexander-akait I have an issue with the following function to get the filename with placeholder replacement. It returns the last fragment of the entry name if it contains slashes, instead of the full entry name. Is it normal?
const newFilename = compilation.getPath(this.options.filename, {
  filename: entryName,
});

With an entry name shared/components/header, it produces newFilename = 'header'.
(Previously it was the full entry name with https://github.com/yoriiis/svg-chunk-webpack-plugin/blob/3.0.0/src/index.ts#L220-L227).


Variables for "down chain" series renamed to "stat derived"

Coverage remained the same at 99.04% when pulling 1f8829c4f6b59d368ed107c54b1b7f6c3ef3a966 on thongsav-usgs:master into b173918160941f8f2f8fde273c0fc3a02916449a on USGS-R:master.

Coverage remained the same at 99.04% when pulling 348495adf73b8e97f5abbe3f1c061d193d071a7b on thongsav-usgs:master into e86b3274d14be833e8be3d4661e16a532a7b136d on USGS-R:master.


Medium and large-sized SliverAppBar displays title on top of back button after scrolling

Is there an existing issue for this?

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

Steps to reproduce

Create a new project
Replace main.dart with the provided code sample
Run it (in my case, Android)
Tap "Go to page 2" button
Scroll down the page until the title is moved to the position of the ordinary AppBar.
The title is placed on top of the back button

Expected results
Title text should be placed at the right of the automatically implied back button.
Actual results
Title text is placed on top of the automatically implied back button as a stack.
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MaterialApp(
    home: Page1(),
  ));
}

/// Home page: Contains a button to navigate to the page with bug.
class Page1 extends StatelessWidget {
  const Page1({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: ElevatedButton(
          onPressed: () => Navigator.of(context).push(
            MaterialPageRoute(
              builder: (context) => const Page2(),
            ),
          ),
          child: const Text('Go to page 2'),
        ),
      ),
    );
  }
}

/// Bug exists on this page because there exists automatically implied back
/// button.
class Page2 extends StatelessWidget {
  const Page2({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: CustomScrollView(
        slivers: [
          SliverAppBar.medium(
            title: const Text('Title'),
          ),
          const SliverToBoxAdapter(
            child: SizedBox(height: 1000),
          ),
        ],
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
untitled2.webm

Logs
No response
Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.10.0, on macOS 13.2.1 22D68 darwin-arm64, locale en-TH)
    • Flutter version 3.10.0 on channel stable at /Users/Admin/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 84a1e904f4 (7 days ago), 2023-05-09 07:41:44 -0700
    • Engine revision d44b5a94c9
    • Dart version 3.0.0
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/Admin/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • ANDROID_HOME = /Users/Admin/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.12.0

[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.3.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.78.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.64.0

[✓] Connected device (2 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64 • Android 13 (API 33) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64  • macOS 13.2.1 22D68 darwin-arm64

[✓] Network resources
    • All expected network resources are available.

Hi @sunboyy, this has been fixed by https://github.com/flutter/flutter/pull/122542.
Closing from here as this has already been fixed on the master/beta channels and should make it to the stable branch some time in the future.
Thank you


Ability to set Min HA value

I'd like to get the ability to have a min HA value. Where anything under that value will always be hidden.

That seems reasonable! I'll add it soon.

Thanks a lot fam 🙌


Failing test for +link_to+ helper method

Summary
I think this is a bug.
This PR adds a failing test to track and fix the bug.
Steps to reproduce

Create a component
Use an AR instance in a +link_to+ method inside the component's template

link_to 'Something', Post.first

Render the component in a view
Visit the view

Actual
Error:
ActionView::Template::Error: undefined method `merge' for #<Post:0x00007fd155be2200 @id=1>
    app/components/link_component.html.erb:1:in `call'
    (eval):3:in `render_template_for'

Expected
The link is displayed correctly

@juanmanuelramallo thanks so much for the PR! It'd be great to get this working. Do you plan to take this on, or do you need a hand?

@juanmanuelramallo thanks so much for the PR! It'd be great to get this working. Do you plan to take this on, or do you need a hand?

@joelhawksley I'll need a hand
I'm not entirely familiar on how the internals work nor I have the time I'd like to dig into it, but I thought I could definitely write a failing test for it.
I'm available for code reviews though

@joelhawksley I'll need a hand
I'm not entirely familiar on how the internals work nor I have the time I'd like to dig into it, but I thought I could definitely write a failing test for it.
I'm available for code reviews though

It is not a bug. The component under test overrides the url_options method, which is used by the routes to generate the url. If you change the name of the getter, or just keep it internal to create the url
def url
  url_for(@url_options)
end

it will work.

It is not a bug. The component under test overrides the url_options method, which is used by the routes to generate the url. If you change the name of the getter, or just keep it internal to create the url
def url
  url_for(@url_options)
end

it will work.

Nice catch @rewritten I didn't realize about it! Thank you.
I haven't tested it yet but it definitely makes sense, closing this.

Nice catch @rewritten I didn't realize about it! Thank you.
I haven't tested it yet but it definitely makes sense, closing this.

The url_options method is called in https://github.com/rails/rails/blob/6-1-stable/actionpack/lib/action_dispatch/routing/route_set.rb#L199 on the same object that has the url_for and post_path.

The url_options method is called in https://github.com/rails/rails/blob/6-1-stable/actionpack/lib/action_dispatch/routing/route_set.rb#L199 on the same object that has the url_for and post_path.


Document SQLite idempotent script limitations

Fixes #2636

I thought about mentioning ways to generate an elaborate bash script with individual migration scripts, but then I figured, "Meh, it's just SQLite."
if [[ $(sqlite3 my.db "SELECT COUNT(*) FROM __EFMigrationsHistory WHERE MigrationId = '00000000000000_InitialCreate'") != 0 ]]; then
    sqlite3 my.db ".read<PHONE_NUMBER>0000_InitialCreate.sql"
fi

Note to shay, github action build check is not running when a PR from fork comes.


Bump version 0.2.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I could wait a bit (#2)


Epic Roadmap

Describe the bug
I see all work items type in Epic Roadmap. I just see epic work items before
Browser
Choose a browser
[ ] IE11
[ ] Chrome
[ ] FireFox
[ ] Safari
Version
[ ] Azure DevOps Server 2019 RC1
[ ] Azure DevOps Server 2019 RC2
Screenshots

I attached 2 screenshot. One of them epic backlog another one epic roadmap.

Please share backlog configuration for the project.
https://dev.azure.com///_apis/work/backlogconfiguration

Closing due to no response.


Add profiling/goroutine dump endpoint to satellite

Otherwise it's very hard to debug what's happening to it.

Profile endpoint added in gravitational/planet#224
To enable profiling endpoint, provide planet agent with httpprofile flag.
httpprofile - enable profiling endpoint on specified host/port i.e. localhost:7070
More info on golang diagnostics tools https://golang.org/doc/diagnostics.html

@bernardjkim can you folks try to make it consistent with our --diag-addr setting in teleport?
https://github.com/gravitational/teleport/blob/6b5935fb71f7de97626f1845de59d3daf4b9706a/tool/tctl/common/top_command.go#L58
https://github.com/gravitational/teleport/blob/6b5935fb71f7de97626f1845de59d3daf4b9706a/lib/service/service.go#L1512


Update UV mapping on icosphere

better use of texture surface compare to previous map
Use 2 islands of triangle to cover about 61 % of the square bitmap
create alias vertex (case of same 3D position with different UV)

Oh..
the conflics are my fault. Jerome siw roking on create cylinder and I have forced updated his changes after they were deleted.
Could you try merging the chanegs and fix the conflits?
Sorry again...

I merged the PR directly into the master. Please update the readme with the change


perf(linter): comment jest:expect-expect

Current dependencies on/for this PR:

main

PR #1782   👈

This stack of pull requests is managed by Graphite.


Xcode 7: Freeze, Failure, Nothing Works ;) (Pipe actually broken)

I always wanted to write such a title ;)
No, looks like a cool tool(chain), thank you! In my tests it didn't work well with current Xcode 7.
iOS9 Simulators on current Devices (iPhone 6 and 6S) work like a charm, but somehow the pipe breaks when trying to generate Screenshots for older devices (iPhone 5S, 5, 4S, all iOS9).
Command issued (I mean really? you mention this in the Guideline..): snapshot :D
Snapfile:
devices([
  "iPhone 6s",
  "iPhone 6s Plus",
  # "iPhone 5s",
  "iPhone 4s",
  "iPad Air"
])

languages([
  'en-US',
  'de-DE'
])

screenshots_path "./screenshots"
clear_previous_screenshots
scheme 'testApp'

Shell Output (a.k.a. "Stack Trace"):
[18:48:37]: Building project 'testApp' - this might take some time...
[18:48:37]:  xcodebuild -sdk iphonesimulator CONFIGURATION_BUILD_DIR='/tmp/snapshot/build' -workspace '/Users/winkelsdorf/Projects/testApp/iOS App/testApp.xcworkspace' -scheme 'testApp' DSTROOT='/tmp/snapshot' OBJROOT='/tmp/snapshot' SYMROOT='/tmp/snapshot'  clean build
[18:49:07]: BUILD SUCCEEDED
[18:49:07]: Reinstalling app...
No matching processes belonging to you were found
No matching processes belonging to you were found
[18:49:15]: Running tests on iPhone 6s (9.0) in language en-US (locale en-US)
[18:49:15]: instruments -w 'iPhone 6s (9.0)' -D '/tmp/snapshot_traces/trace' -t 'Automation' /tmp/snapshot/build/testApp.app -e UIARESULTSPATH '/tmp/snapshot_traces' -e UIASCRIPT './snapshot.js' -AppleLanguages '(en-US)' -AppleLocale 'en-US'
[18:49:26]: Successfully took screenshot 📱
[18:49:27]: Removing the alpha channel from generated png files
[18:49:27]: Rotating the screenshots (if necessary)
[18:49:27]: Reinstalling app...
No matching processes belonging to you were found
[18:49:39]: Running tests on iPhone 6s (9.0) in language de-DE (locale de-DE)
[18:49:39]: instruments -w 'iPhone 6s (9.0)' -D '/tmp/snapshot_traces/trace' -t 'Automation' /tmp/snapshot/build/testApp.app -e UIARESULTSPATH '/tmp/snapshot_traces' -e UIASCRIPT './snapshot.js' -AppleLanguages '(de-DE)' -AppleLocale 'de-DE'
[18:49:48]: Successfully took screenshot 📱
[18:49:49]: Removing the alpha channel from generated png files
[18:49:50]: Rotating the screenshots (if necessary)
[18:49:50]: Reinstalling app...
No matching processes belonging to you were found
[18:49:57]: Running tests on iPhone 6s Plus (9.0) in language en-US (locale en-US)
[18:49:57]: instruments -w 'iPhone 6s Plus (9.0)' -D '/tmp/snapshot_traces/trace' -t 'Automation' /tmp/snapshot/build/testApp.app -e UIARESULTSPATH '/tmp/snapshot_traces' -e UIASCRIPT './snapshot.js' -AppleLanguages '(en-US)' -AppleLocale 'en-US'
[18:50:11]: Successfully took screenshot 📱
[18:50:12]: Removing the alpha channel from generated png files
[18:50:13]: Rotating the screenshots (if necessary)
[18:50:13]: Reinstalling app...
No matching processes belonging to you were found
[18:50:24]: Running tests on iPhone 6s Plus (9.0) in language de-DE (locale de-DE)
[18:50:24]: instruments -w 'iPhone 6s Plus (9.0)' -D '/tmp/snapshot_traces/trace' -t 'Automation' /tmp/snapshot/build/testApp.app -e UIARESULTSPATH '/tmp/snapshot_traces' -e UIASCRIPT './snapshot.js' -AppleLanguages '(de-DE)' -AppleLocale 'de-DE'
[18:50:35]: Successfully took screenshot 📱
[18:50:36]: Removing the alpha channel from generated png files
[18:50:37]: Rotating the screenshots (if necessary)
[18:50:37]: Reinstalling app...
No matching processes belonging to you were found
[18:50:48]: Running tests on iPhone 4s (9.0) in language en-US (locale en-US)
[18:50:48]: instruments -w 'iPhone 4s (9.0)' -D '/tmp/snapshot_traces/trace' -t 'Automation' /tmp/snapshot/build/testApp.app -e UIARESULTSPATH '/tmp/snapshot_traces' -e UIASCRIPT './snapshot.js' -AppleLanguages '(en-US)' -AppleLocale 'en-US'

Here it hangs. Quitting by ^C:
^C^C/Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:170:in `wait': Interrupt
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:170:in `ensure in block in run_tests'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:170:in `block in run_tests'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:137:in `spawn'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:137:in `run_tests'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:38:in `block (2 levels) in work'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:23:in `each'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:23:in `block in work'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:22:in `each'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/lib/snapshot/runner.rb:22:in `work'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/bin/snapshot:40:in `block (3 levels) in run'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/bin/snapshot:37:in `chdir'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/bin/snapshot:37:in `block (2 levels) in run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:68:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/bin/snapshot:85:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/snapshot-0.10.0/bin/snapshot:91:in `<top (required)>'
	from /usr/bin/snapshot:23:in `load'
	from /usr/bin/snapshot:23:in `<main>'

Which is of course the run loop waiting for the Simulator.
Meanwhile in the Console:
18.09.15 18:50:37,000 kernel[0]: Over-release of kernel-internal importance assertions for pid 11488 (nsurlsessiond), dropping 1 assertion(s) but task only has 13 remaining (13 external).
18.09.15 18:50:37,136 com.apple.xpc.launchd[1]: (com.apple.iphonesimulator.368096[11457]) Service exited due to signal: Terminated: 15
18.09.15 18:50:37,147 com.apple.CoreSimulator.CoreSimulatorService[478]: Error Domain=NSPOSIXErrorDomain Code=3 "The operation couldn’t be completed. No such process"
18.09.15 18:50:37,149 com.apple.CoreSimulator.CoreSimulatorService[478]: Error Domain=NSPOSIXErrorDomain Code=3 "The operation couldn’t be completed. No such process"
18.09.15 18:50:39,298 com.apple.CoreSimulator.CoreSimulatorService[478]: Error Domain=NSPOSIXErrorDomain Code=3 "The operation couldn’t be completed. No such process"
18.09.15 18:50:39,298 com.apple.CoreSimulator.CoreSimulatorService[478]: Error Domain=NSPOSIXErrorDomain Code=3 "The operation couldn’t be completed. No such process"
18.09.15 18:50:40,188 com.apple.CoreSimulator.CoreSimulatorService[478]: Error Domain=com.apple.CoreSimulator.SimError Code=159 "Unable to boot device in current state: Booted" UserInfo=0x7f8b39659210 {NSLocalizedDescription=Unable to boot device in current state: Booted}
18.09.15 18:50:40,189 com.apple.CoreSimulator.CoreSimulatorService[478]: Error Domain=com.apple.CoreSimulator.SimError Code=159 "Unable to boot device in current state: Booted" UserInfo=0x7fbad9e26690 {NSLocalizedDescription=Unable to boot device in current state: Booted}
18.09.15 18:50:41,884 com.apple.xpc.launchd[1]: (com.apple.dt.instruments.dtsecurity.xpc[11456]) Service did not exit 5 seconds after SIGTERM. Sending SIGKILL.
18.09.15 18:50:48,265 com.apple.xpc.launchd[1]: (com.apple.StreamingUnzipService) The _DirtyJetsamPriority key is not available on this platform.
18.09.15 18:50:48,265 com.apple.xpc.launchd[1]: (com.apple.StreamingUnzipService) The _DirtyJetsamMemoryLimit key is not available on this platform.
18.09.15 18:50:48,265 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
18.09.15 18:50:48,316 com.apple.xpc.launchd[1]: (com.apple.StreamingUnzipService) The _DirtyJetsamPriority key is not available on this platform.
18.09.15 18:50:48,316 com.apple.xpc.launchd[1]: (com.apple.StreamingUnzipService) The _DirtyJetsamMemoryLimit key is not available on this platform.
18.09.15 18:50:48,342 com.apple.SecurityServer[79]: Session 100139 created
18.09.15 18:50:48,349 com.apple.SecurityServer[79]: Killing auth hosts
18.09.15 18:50:48,349 com.apple.SecurityServer[79]: Session 100137 destroyed
18.09.15 18:50:48,349 instruments[11559]: DTServiceHubClient: connected to server (singleton pid: 4467, initial pid: 11560)
18.09.15 18:50:48,814 instruments[11559]: enumerate proxied devices: true
18.09.15 18:50:48,842 com.apple.SecurityServer[79]: Session 100140 created
18.09.15 18:50:49,000 kernel[0]: com_protech_nosleepextension: setting state: 0, for mode: 0 (battery-mode)
18.09.15 18:50:49,451 loginwindow[92]: magsafeStateChanged state changed old 1 new 2
18.09.15 18:50:59,061 com.apple.usbmuxd[78]: _SendAttachNotification Device d4:f4:6f:9c:a5:d9@fe80::d6f4:6fff:fe9c:a5d9._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.
18.09.15 18:51:01,222 instruments[11559]: WebKit Threading Violation - initial use of WebKit from a secondary thread.
18.09.15 18:51:21,970 iTunes[9437]: Entered:_AMMuxedDeviceDisconnected, mux-device:26
18.09.15 18:51:21,971 iTunes[9437]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:26
18.09.15 18:51:21,971 iTunes[9437]: tid:1b6d3 - Mux ID not found in mapping dictionary
18.09.15 18:51:21,971 iTunes[9437]: tid:1b6d3 - Can't handle disconnect with invalid ecid
18.09.15 18:51:21,973 Xcode[2818]: CompanionProxy: _SocketReadCallback:128 (0x0x11c765000): Failed to receive response from AMDevice 0x7fdc2c7480a0 {UDID = 80a590547bf4613cd8376da18653c7b5c0fc3fd7, device ID = 26, FullServiceName = d4:f4:6f:9c:a5:d9@fe80::d6f4:6fff:fe9c:a5d9._apple-mobdev2._tcp.local.}: 0xe8000084
18.09.15 18:51:21,973 Xcode[2818]: CompanionProxy: _SocketReadCallback:200 (0x0x11c765000): Stopped listening for paired devices from AMDevice 0x7fdc2c7480a0 {UDID = 80a590547bf4613cd8376da18653c7b5c0fc3fd7, device ID = 26, FullServiceName = d4:f4:6f:9c:a5:d9@fe80::d6f4:6fff:fe9c:a5d9._apple-mobdev2._tcp.local.}: 0xe8000084
18.09.15 18:52:51,678 com.apple.usbmuxd[78]: _SendAttachNotification Device b8:e8:56:6e:07:42@fe80::bae8:56ff:fe6e:742._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.
18.09.15 18:53:00,414 iTunes[9437]: Entered:_AMMuxedDeviceDisconnected, mux-device:27
18.09.15 18:53:00,414 iTunes[9437]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:27
18.09.15 18:53:00,414 iTunes[9437]: tid:137bb - Mux ID not found in mapping dictionary
18.09.15 18:53:00,415 iTunes[9437]: tid:137bb - Can't handle disconnect with invalid ecid
18.09.15 18:53:00,416 instruments[4466]: <DYMobileDeviceTransport: 0x7ff639c99030>: read io failure: Broken pipe (32)
18.09.15 18:53:00,416 instruments[11559]: <DYMobileDeviceTransport: 0x7f8e260e15a0>: read io failure: Broken pipe (32)
18.09.15 18:53:00,416 instruments[7830]: <DYMobileDeviceTransport: 0x7f9495af80f0>: read io failure: Broken pipe (32)
18.09.15 18:53:00,416 Xcode[2818]: <DYMobileDeviceTransport: 0x7fdc2c41c6f0>: read io failure: Broken pipe (32)

Especially I was interested in the broken pipe and the WebKit Threading Violation - initial use of WebKit from a secondary thread..
And during the freeze from another shell the simctl output:
[...]
-- iOS 9.0 --
    iPhone 4s (395C7F00-1157-4BD6-BF2B-C284C1473A5A) (Booted)
    iPhone 5 (A4FD0C55-3C73-4825-824F-809C97C7E9FF) (Shutdown)
    iPhone 5s (3A71FE86-0B52-4D0C-BFF2-F9F486951E2C) (Shutdown)
    iPhone 6 (6AD04310-9061-4A51-84B8-0A5832FFC512) (Shutdown)
    iPhone 6 Plus (F0F63D06-34E5-49E0-A99C-57C6FA4F10C9) (Shutdown)
    iPhone 6s (F23DB6AC-A933-42CF-B6CE-5A8EC016A4F6) (Shutdown)
    iPhone 6s Plus (755E2CED-C87C-4E5A-9256-9057D7E9FCD8) (Shutdown)
    iPad 2 (45B989F5-CE50-40E6-8841-818B9473EEF6) (Shutdown)
    iPad Retina (5FFD5D74-741E-4585-B1D1-0123FC64571C) (Shutdown)
    iPad Air (CB0031D6-A5B9-4754-93B8-73B6D8E6B517) (Shutdown)
    iPad Air 2 (E1204B1A-4E63-40CE-8C95-2E60E158FF55) (Shutdown)

Environment:
Yosemite 10.10.5, Homebrew, Xcode7 7A220 with Commandline Toolchain. Already reset the Simulators twice and deleted and downloaded them again. All Simulators work when used directly and when invoked via Xcode IDE.
Any ideas?
Edit: Investigating an Idea. Probably related to Xcode Plug-ins? Removed them all and testing now.. Hopefully it's not CocoaPods, somehow needed at this end ;)
Edit2: Unrelated to the Plug-ins.

+1
works like a charm while taking screenshots on iPhone 6 and newer devices

After update to El Capitan and Snapshot 0.10.1 it's working fine 👍


Add link to old v3 docs in new v4 docs.

@Pessimistress @apercu @shaojingli
I've created a new branch 3.0-release from master, in preparation for merging dev into master.
Since @apercu has made sure that docs can be browsed directly on github, I just added a link to the docs on that branch.

Also renamed docs/v4.0 directory back to docs since in this model we don't need to maintain multiple doc versions in the same tree.
@apercu - the link works when I open in new window but behaves slightly strange when opening in same window, maybe you can take a look?

I've created a new branch 3.0-release from master, in preparation for merging dev into master.

Thanks for this Ib. I plan to merge dev back to master after I complete my 64-bit work.

Thanks for this Ib. I plan to merge dev back to master after I complete my 64-bit work.

@shaojingli FWIW, I just did two attempts to rebase dev on master. Fairly long way into the rebase, git crashed with a segmentation fault in both cases.
It is weird because the additional commits on master have very little conflicts with dev. It may be that I made a bad choice during my first run, and that my saved "rerere" resolutions kept applying it automatically on my second go, so maybe you'll have better luck.


Http2Headers.iterator() comment correction

Motivation:
The javadoc comments on Http2Headers.iterator() are incorrect.
Modifications:

Correct and clarify the javadoc for Http2Headers.iterator()

Result:
Javadoc for Http2Headers.iterator() is more correct.

@nmittler - FYI

@Scottmitch :+1:

LGTM

Cherry-picked 4.1 (50d1f0a) master (7e5ad25)


fix(tree-view): putting outline back on navigation trees

• added back the outline CSS property for nav trees
Signed-off-by: Scott Mathis<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 applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] clarity.design website / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

This would be easy to backport if we needed to.


Update apiVersion for issuer example in upgrade 0.7 to 0.8 docs

What this PR does / why we need it:
I could not use the provided example issuer because of the apiVersion.
Got this message:
kubectl apply -f issuer.yaml
error: unable to recognize "issuer.yaml": no matches for kind "ClusterIssuer" in version "certmanager.k8s.io/v1alpha2

Change the apiVersion did fix the issue
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

I'm seeing something similar, but changing v1alpha2 to v1alpha1 doesn't solve it for me.

We don't typically do this for older releases as it's not true that bumping the apiVersion is required when upgrading to v0.8 specifically 😄. Otherwise it becomes very difficult for us to maintain these historical guides as things change!


Issue #219

More info: https://github.com/DozerMapper/dozer/issues/219
Original reference (and test for this):
https://sourceforge.net/p/dozer/bugs/300/

@josejuanmontiel ; can you have a quick check at travis, its failing to compile. I would of expected a test failure.

dozer.patch.txt
I'm not sure my test produce this errors... but if i ignore this 3 test, its compile in my machine... give more time to review carefully :)

Well i fixed "other tests" that fails to in master ;) and, now pass... one seems that error message "change", and other needs to specify directly the location of dozer.properties...
Hope this work. Remember, this came from "Option for configure ClassMap in polymorphism case #219"

@josejuanmontiel ; i think a bad rebase/merge has happened, as this PR shows changes which have came from other PRs, so its quite hard to understand what you've changed...

I made and update of my fork from master... to keep update from prossible changes... you still can filter my changes in the "pull request view" filtering by my commit... https://github.com/DozerMapper/dozer/pull/433/commits/38324e385a772564de02596274a612d588cb20da tell me if do you need some else.
Thanks.

@josejuanmontiel ; I am a bit confused. I thought this PR would show a test failing. But it doesn't... what are you trying to show with this PR?


Memory card on/off option

Hello!! This is a suggestion. There might be an option to enable/disable the memory card for emulation purposes.

Thanks for the suggestion. Is there any specific use case where disabling the memory card makes a difference in gameplay? Are you looking to be able to pull it out and insert it at runtime, or just at boot time?

Thanks for the suggestion. Is there any specific use case where disabling the memory card makes a difference in gameplay? Are you looking to be able to pull it out and insert it at runtime, or just at boot time?

I'm looking to be able in both cases (runtime and boot time). The gameplay is different without memory card (no extra screen asking for save or load data) but is only a little detail.