[WIP] New assertion interface

Codecov Report

Merging #162 (dc0908a) into master (ffc60e6) will increase coverage by 1.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #162      +/-   ##
==========================================
+ Coverage   95.17%   96.27%   +1.09%
==========================================
  Files          27       27
  Lines         892      858      -34
==========================================
- Hits          849      826      -23
+ Misses         43       32      -11

Impacted Files
Coverage Δ

src/assertions.jl
100.00% <100.00%> (ø)

src/transforms.jl
98.57% <100.00%> (-0.06%)
:arrow_down:

src/transforms/center.jl
100.00% <100.00%> (ø)

src/transforms/eigenanalysis.jl
84.61% <100.00%> (+2.00%)
:arrow_up:

src/transforms/levels.jl
100.00% <100.00%> (+3.03%)
:arrow_up:

src/transforms/onehot.jl
100.00% <100.00%> (+2.50%)
:arrow_up:

src/transforms/quantile.jl
100.00% <100.00%> (ø)

src/transforms/scale.jl
100.00% <100.00%> (ø)

src/transforms/zscore.jl
100.00% <100.00%> (ø)

src/distributions.jl
90.90% <0.00%> (-0.76%)
:arrow_down:

... and 15 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Ball rolling down an incline achieves warp speed

Original report (archived issue) by Addisu Z. Taddese (Bitbucket: azeey, GitHub: azeey).
The original report had attachments: rolling_shapes.sdf

As seen in the gif, the ball starts rolling on an incline (a large box inclined ~30 degrees) and after a few seconds, it shoots off in the process crashing ign-gazebo.

Fixed by https://github.com/azeey/dart/pull/5


Disable DataVolume GC by default in cluster-deploy

What this PR does / why we need it:
Prevent DV-related CI failures in the next kubevirt-bot kubevirtci bump PR (with bump-cdi), due to:
https://github.com/kubevirt/containerized-data-importer/pull/2754
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/retest-required

/lgtm
/approve

/test pull-kubevirt-e2e-kind-1.27-vgpu


fix(tail): add support for negative indexing

closes: https://github.com/uutils/coreutils/issues/1860

Please add a test :)

Hmmm CI failed for i686 but it looks unrelated :thinking:
failures:
    test_chown::test_passgrp::test_gid2grp

Yeah, we have some intermittent test issues!


Add Windows to build matrix and turn off fast fail

Now that we have Windows-specific code, it would be a good idea to run fs-err's CI pipeline on Windows in addition to Linux.
Because of the changes in https://github.com/andrewhickman/fs-err/commit/f61ae29f9e8962f8d4f1d51fcd6262cecc0e4e44, I believe this CI will currently fail on Windows.

I've reverted the bad code, this should work now

Just rebased!

Looks useful even without any platform-specific code (yet). Thanks!


Improve consistency between attributes and equivalent elements

In the cases where we can either have an attribute or an element for the same thing, my understanding it that one would use the element when either more detailed information needs to be provided or where there is a need to provide editorial information about it (e.g. having it in an app/rdg). We have quite a few of them in staffDef (clef, key, meter, etc.). So it seems to me that everything that is available at the attribute level should also be provided in the element.
In <keySig>, there is no option to encode it as in <staffDef> @key.sig.  Shouldn't we add @sig in <keySig>?
There are some inconsistencies how attributes are grouped in the ODD, but this is less of an issue. In most cases it could be improved without generating changes in the resulting schema, I think.

Can you be more specific than "everything that is available at the attribute level" as a target?
The grouping of attributes attached to <scoreDef> is addressed in issue #115 and in the 2015 ODD customization.  Several new attribute classes are added: att.endings (ending.rend), att.measurenumbers (mnum.visible), att.notationstyle (music.name, music.size), att.optimization (optimize), att.pages (page.height, .width, .topmar, .botmar, .leftmar, .rightmar, .panels, .scale), att.spacing (spacing.packexp, .packfact, .staff, .system), and att.systems (system.leftline, .leftmar, .rightmar, .topmar). Except for a couple of cases (system.leftline, for instance) this represents a re-arrangement of existing attributes and has no effect on the resulting schema, but it separates the attributes into more manageable and shareable groups.

In <staffDef>, you can do clef.line="2" or clef.shape="G" that intuitively translates in <clef> to line="2" and shape="G". I could not find the equivalent of key.sig="1f" in <keySig>.

Another example: <staffDef> has key.sig.showchange attribute for displaying cautionary changes (or not). Here too, I am not sure there is an equivalent in <keySig>. So if I want to have encode the key signature within an app and rdg within staffDef, with one showing cautionary changes and the other not, I am not sure I can do it. So, to go back to the issue: I would expect every attribute in staffDef to have their equivalent in promoted element.
If possible, it would also make it simpler to have the same attribute classe structure: for example, att.keySigDefault.vis that defines 'key.sig.showchange' could be att.keySig.vis and define 'showchange' in keySig. (Mensur - the attributes in staffDef and the element - is not consistent in this regard, to have another example.)
Along the same lines, I would personally be in favor of deprecated all attributes that have been promoted to an element, and eventually drop them. This would make MEI developments much easier in the long run.

Ever hear that "Consistency is the hobgoblin of small minds"?  :-)
Seriously, I see your point about making the so-called "attribute solution" and the "element solution" more consistent.  And I agree.  It's just that it may take some time to get around to it.  Version 4, perhaps?
I'm less willing to whole-heartedly support deprecating attributes in favor of elements, because each possibility within the "two-state" solution serves a different constituency  -- some want attributes and some want elements.  I think the best way to deal with this is to encourage the use of one way or the other but not both simultaneously.  To do so, we could provide customizations that enforce one approach or the other or we could add schematron rules (although it would swell the size and complexity of mei-source considerably).

I never heard did. But I know that small minds usually have a bad memory ;-)
I understand that it would take some time, this is not urgent. Only missing features in the elements is more problematic, I think. I might add separate issues for them.
I think the interesting part of the discussion is in the end more the attribute/element thing. I can see many places in MEI where it makes sense to have several possible approaches. For example beam and beamSpan, because here there is a structural difference. Now for keeping attributes where elements are available I cannot see any advantage in the long run, but only overhead and/or incompatibility. Using one or the other is easy to define when you create your own tool for your own project. Just to take the example of SibMEI. It consistently uses accid elements. And consistently dot attributes. Fine (and no criticism here!). But this might incompatible with another tool that uses attributes for both accid and dots, or reverse. So of course, we can have a customization or schematron rules. But this is not going to fix it. We will need to convert from one to another, presumably with an XSL stylesheet, and somebody will need to write this stylesheet and then run this stylesheet every time. So to me the is a huge overhead and I cannot understand why we would not want to avoid it only because some prefer this and others prefer that.
They are actually not that many attributes that have a promoted element equivalent (probably mostly in staffDef and in note). I am convinced that deprecating the attribute when a feature is promoted to an element will make MEI much stronger in the long run.

Like Zoltan, I'd like to wholeheartedly support Laurent's suggestion of deprecating attributes where elements are available (don't forget @syl vs. <syl>).

I am not sure Zoltan supports this idea but I am glad you do ;-)

I can't recall expressing any opinion on the matter, but very happy that is
still matters :)
But then let me stir up this thread once again, with perhaps the most
controversial suggestion. I don't actually see a problem of the two forms
to co-exist within a single MEI file, especially if they are the result of
a processing step, thus making sure that the redundancy is proper (i.e.
there is no conflicts).
For example, we have MEI files with ties encoded as attributes. For
rendering purposes, we convert these into elements, but tie attributes are
still useful for audio processing (generating MIDI), so it makes sense to
keep them both.
For the record, I am all for consistency, as long as it's not "a foolish"
one, as Perry saved us from the cheeky qualifying term from the beginning
of his quote ;)
Zoltan
2015-08-21 11:13 GMT+01:00 Laurent Pugin<EMAIL_ADDRESS>
I am not sure Zoltan supports this idea but I am glad you do ;-)
—
Reply to this email directly or view it on GitHub
https://github.com/music-encoding/music-encoding/issues/250#issuecomment-133363834
.

@zolaemil I'm sorry, I guess my telepathy skills need training as I don't see a post where you explicitly expressed the opinion implied by me. I have no idea what association chain made me link your name with that opinion - I can assure you I wasn't under the influence while writing!

Of course it is not a problem to have both attributes and elements. It just increases the complexity and the amount of work. When thinking "encoding", it clearly has no major impact (you can do this, or you can do that). It does when it comes to developing tools, and in particular when creating tools that are mean to "read" MEI - writing it is easy, you just do what you prefer ;-). So this is a community question: are there places where we can deprecate attributes in order to make the exchange of data and tools easier in the long run.
Now ties might be a different issue. But if we take accid, I cannot see the benefit of allowing
<note accid="s"/>

since there is
<note>
  <accid accid="s">
</note>

Now let's say, somebody is planning to have an MEI importer into MuseScore (wouldn't this be be great?). Which one should be supported first? Should the person start with the simplest one? Or look around what is most commonly used? Both clearly make sense. One risk here it so have some sort of de facto standardization that is driven by the development of some tools. Another one is to have to develop additional tools to "sanitize" the data (we see this happening elsewhere). I would prefer discussion and deprecation.

Reduced to a more focused issue here #354


Native Notebooks: Why does cell status bar say "Ctrl+Alt+Enter" to run cell...

For Jupyter notebooks, it should not say this.

This is upstream, we don't contribute this tip.

I believe I mentioned this to Peng in another issue, if it could be written in such a way where it could display something different based on the extension shortcut let me see if I can find it..

I can't seem to find the comment on the PR where I requested it be dynamic but I filed an issue for it in the vs code repo: https://github.com/microsoft/vscode/issues/121558

This appears to be fixed in insiders!


docker-machine create -d generic does not respect --engine-storage-driver

I tried to configure docker-machine with generic driver and with engine-storage-driver overlay.
But i failed to let it running.
the docker-machine always create docker-engine with aufs storage-driver.
root@s64:~# service docker status -l
● docker.service
   Loaded: loaded (/etc/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2016-06-20 01:43:48 UTC; 3min 40s ago
  Process: 3889 ExecStart=/usr/bin/docker daemon -H tcp://<IP_ADDRESS>:2376 -H unix:///var/run/docker.sock --storage-driver aufs --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --tlskey /etc/docker/server-key
 Main PID: 3889 (code=exited, status=1/FAILURE)

Jun 20 01:43:47 s64 systemd[1]: Started docker.service.
Jun 20 01:43:47 s64 docker[3889]: time="2016-06-20T01:43:47.651426231Z" level=info msg="New containerd process, pid: 3895\n"
Jun 20 01:43:48 s64 docker[3889]: time="2016-06-20T01:43:48.658213466Z" level=fatal msg="Error starting daemon: error initializing graphdriver: driver not supported"
Jun 20 01:43:48 s64 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 20 01:43:48 s64 docker[3889]: time="2016-06-20T01:43:48Z" level=info msg="stopping containerd after receiving terminated"
Jun 20 01:43:48 s64 systemd[1]: docker.service: Unit entered failed state.
Jun 20 01:43:48 s64 systemd[1]: docker.service: Failed with result 'exit-code'.

did you ensure that kernel module overlay is loaded?

Yes. it loaded. and i have to configure -s overlay one by one by my hand.

odd. i just created a cluster with --engine-storage-driver overlay and it worked as it should.

it should work fine... what's the output of uname -a?

We will re-open if followup occurs... thanks


Fix custom global toast component

Custom global components are broken. The custom component passed from the prop is overwritten on line 39.

There an issue due to moving the svelte:component to two if statements.
The destructured @const block is no longer available to the 2nd svelte:component.
If we move that to the top of the #each block, it will then overwrite the component variable. So we'll need to rename it.
The simplest solution is to rename the destructured @const component variable to something else and handle the nullable individual component.
- {@const { component, ...props } = toast}
- <svelte:component this={toast?.component[0] || component} {...props} />
+ {@const { component: _throwAway, ...props } = toast}
+ <svelte:component this={toast?.component?.[0] || component} {...props} />

This is my fault for not noticing this earlier.
Once the changes are made, I'm more than happy to merge. 👍


File is Missing From Menu On Insiders

VSCode Version: Can't tell because that Menu is missing

OS Version: Windows 10

I took the latest update and a couple of Menu items are missing.
File and Help? are missing.

 The workaround I'm using is file commands:

Same Problem, really causing inconvenience.

Same problem.

Duplicate of #55624


Hyperparameters for training

Hello,
would like to congratulate you on such great work!
Are the hyperparameters for the kitti_raw dataset included in params_kitti_raw.yaml the same ones used to reach the results in the paper or should they be changed?

Hi Youssef,
Yes you should be able to reproduce the performance by using params_kitti_raw.yaml, you can change it accordingly if you want to reproduce the results for different settings in the paper (for example the training resolution).
Zijian

I have tried recreating the data loader of KITTI Raw following the code you specified in a previous issue.  I also deactivated the sparse disparity loss as mentioned in the paper and used the same hyperparams in params_kitti_raw.config. However, the model is not converging after training for 1 Day on 4 V100 GPUs. Is it possible to share a code snippet of the KITTI Raw Data loader to verify that I implemented it correctly?

Look forward to friends who pay attention to this work and hope to discuss it. Thank you.
WeChat link as follows：
https://wx3.sinaimg.cn/mw690/b0e12477gy1gwcfjj9ez9j20tc10xjuv.jpg @YoussefFathi

It was mentioned in the MPI paper that for KITTI Raw they cropped all images by 5% from all sides before testing and also calculated the metrics only on non-occluded regions of the scene. Did you do the last part in your method or only cropped by 5% from all sides?

@YoussefFathi
Hi, did you figure it out how to evaluate? I'm now testing the author's pretrained model but I can never get the results as in the paper. I evaluated PSNR and it seems around 15. on in the test set. Could you please share the tips if you get the good results?


ssh features

Description of the new feature/enhancement
i want to suggest some new features about ssh.

password: store ssh passwords in ssh profiles and perform auto connect. so the user does not need to type passwords every time.
sftp: users can see host files and abale to upload or download files.
dynamic port forwarding: when user connect to ssh, he could add or remove any port forwards.

Windows Terminal is not the place for storing passwords. Putty offers this as it's a dedicated to remote connections and includes a built-in password manager. However since VSCode allows this via extension such as https://github.com/SchoofsKelvin/vscode-sshfs or the official Remote-SSH, WT can support this via extension as well. Just needs to be tagged up in https://github.com/microsoft/terminal/issues/4000


deoplete-clang doesn't complete include content unless I reopen the file.

Problems summary
I'm using the deoplete + deoplete-clang + neoinclude. When my file  #include <limits.h> and
I typing INT it will not show any completion candidates. If I reopen that file and typing INT
it will show completion candidates like INT_MAX and INT_MIN.
Expected
Completing include content without reopen the code file.
Environment Information

OS: Arch Linux
Neovim version: 0.1.4

Provide a minimal init.vim with less than 50 lines and not plugin manager (Required!)
" Your minimal init.vim
set runtimepath+=~/path/to/deoplete.nvim/
set runtimepath+=~/path/to/deoplete-clang/
let g:deoplete#enable_at_startup = 1

" Use smartcase
let g:deoplete#enable_smart_case = 1

" Let <Tab> also do completion
inoremap <expr><tab> pumvisible() ? "\<c-n>" : "\<tab>"

"close the preview window after completion is done.
autocmd CompleteDone * pclose!

" completion bracket
call deoplete#custom#set('_', 'converters', ['converter_auto_paren'])

" Deoplete-clang
let g:deoplete#sources#clang#libclang_path = '/usr/lib/libclang.so'
let g:deoplete#sources#clang#clang_header = '/usr/lib/clang'

The reproduce ways from neovim starting (Required!)
#include <limits.h>
INT   //will not show any completion candidates

save and reopen that file
#include <limits.h>
INT  //will show completion candidates like INT_MAX and INT_MIN

I'm not sure it's deoplete-clang or other plugin's problems.
Thanks for any help.

I think the problem is...
https://github.com/zchee/deoplete-clang/issues/43#issuecomment-235557371

Hi there,
I am using neovim and freshest code for deoplete and deoplete-clang, and having the same problem. Completion from files included happens only after reopening the source file. This is happening regardless of the file included.
Does anyone have a clue? @XDXX have you solved the issue?
My setup

RedHat 7

Clang 3.4.2

NVIM v0.2.0

My init.vim (part of it)
let g:deoplete#enable_at_startup = 1
let g:deoplete#sources#clang#libclang_path= '/usr/lib64/llvm/libclang.so'
let g:deoplete#sources#clang#clang_header = '/usr/lib/clang'
let g:deoplete#sources#clang#sort_algo = 'priority'
set completeopt-=preview`

Thanks,
Christian

@christian-pinto This problem still bothers me and I don't have andy clue about it. Hope @zchee will fix this issue soon.

deplete-clang2 exists. It has the same problem?

I have just tested deoplete-clang2, it works with the includes. In previous post I forgot to mention that I am also using neoinclude.
However deoplete-clang2 has another problem for me that is translation is not always performed. As an example i write mmap, nothing appears, then I delete some characters and type again and the mmap autocompletion from clang appears. This is annoying since everytime i need to back and forth typing and deleting in order to get the autocompletion.


Testing posting statuses to PRs

Reworked check_compliance script

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e480806). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #72   +/-   ##
=========================================
  Coverage          ?   41.39%
=========================================
  Files             ?      118
  Lines             ?    18634
  Branches          ?     3915
=========================================
  Hits              ?     7714
  Misses            ?     9429
  Partials          ?     1491

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 e480806...d16acda. Read the comment docs.

CC @myrdyr, please take a look at this


A Blank Mind missing kit

Kit ABM at stage 10 of "A Pure Mind" is missing from the list

For whoever fixes this, stage 12 directs the player to the heillportal to catch an onix, but they dont spawn there anymore. They now spawn in spiral cave

Both of these issues have been fixed.


Inconsistent link styling in accessibility conformation reports

Summary
The VPAT reports have stripy table rows for readability. The links to the WCAG criterion switches from blue link text and blank link text.
💬 Description
Research best way to represent the links (all blue styling?).
Additional info
The files to look at:

blank-accessibility-conformance-report-vpat-24rev
icds-accessibility-conformance-report-12-10-22

This has been fixed with the introduction of the new VPAT templates.


Update docker-compose-guide.md

Hi muppet3000,
thanks for your guide on installing grott via docker. I think I spotted a typo in the documentation which threw me (as a first time docker user) off. Fixed it in the pull request.
fix typo in docker compose command

Sorry, finally doing some admin, this isn't a correct change, docker-compose is another application that wraps around docker.


Village and POI stuff

Maps some function arguments, methods, and renames VillagerEntity#hasRecentlyWorkedAndSlept.
Fixes #2119

cc @LambdAurora

I see a lot of parameters mapping but few methods mapping, are those methods synthetic methods?
If not would be worth it and try to name them too.
And I personally really would appreciate Javadoc.

most likely those are lambda params.


feat: port Topology.MetricSpace.CantorScheme

[x] depends on: #3496

This PR/issue depends on:

leanprover-community/mathlib4#3496
By Dependent Issues (🤖). Happy coding!

bors d+
Please merge once bors is finished with the dependent PR.

bors merge

bors merge

This PR/issue depends on:

leanprover-community/mathlib4#3496
By Dependent Issues (🤖). Happy coding!


codeCopyEnabled on certain part of code

An idea that I found when writing my last blog is that we could enable codeCopyEnabled on a certain part of the code block. An example of this is, I'm writing shell commands and I also want to display the result. However, I would like the reader to only copy the command (without the prompt, and without the result). Here is an example of what I have now:
$ cat repeated.txt | protoc --encode=PackedRepeated proto/repeated.proto | hexdump -C
00000000  0a 03 01 02 03                                    |.....|
00000005

In this case the codeCopyEnabled would only copy cat repeated.txt | protoc --encode=PackedRepeated proto/repeated.proto | hexdump -C.
I'm not sure how this can be done. Maybe with liquid tags but I'm not sure.

Thanks for the idea, seems really useful to me. I've implemented in v1.0.0!
You should be able to accomplish the above using codeCopyEnabled="0"
You can see the release notes here :
https://github.com/jdvp/jdvp-codetabs-commonmark/releases/tag/v1.1.0
And take a look at my sample article for usage info (in the Advanced code copying section): Testing Code Tabs

Great ! Thank you for working on that. Is there any way we could skip characters on a certain line too (sorry 😁). I'm saying that because I would like to skip the $ on my vommand line.

Oh i hadn't considered that. Either option would be much more complicated than the line number thing already is so let me think about it


hotfix/runner shellexec

I think that "phr-dev" would not work if it is not defined as shell's alias or user's environment path.
(I do apologize that previous's pull-request was not dev branch. )

This for development purposes (so that system-wide installed phr may differ from the one you are unit testing against). So, instead of updating the source code, will need to mention it in docs that the "development version" of phr executable should be symlinked to /usr/bin/phr-dev to run UTs.


Use condition syntax in node filters and capability filters

I have a need to define more complex requirement fulfillment logic than what can be expressed using node and capability filters. I believe the existing condition syntax could be used for this purpose. The following example shows how condition syntax could express anti-collocation behavior:
tosca_definitions_version: tosca_2_0

capability_types:
  Host:
    description: for hosting software components

relationship_types:
  HostedOn:
    description: relationship to hosting container

node_types:

  Host:
    properties:
      uuid:
        type: string
    capabilities:
      host:
        type: Host

  SoftwareComponent:
    requirements:
      - host:
          capability: Host
          relationship: HostedOn

service_template:

  node_templates:

    host1:
      type: Host
      properties:
        uuid: host.1

    host2:
      type: Host
      properties:
        uuid: host.2

    host3:
      type: Host
      properties:
        uuid: host.3

    software1:
      type: SoftwareComponent
      requirements:
        - host:
            node: Host

    software2:
      type: SoftwareComponent
      requirements:
        - host:
            node: Host
            filter:
              - not:
                  [TARGET, uuid] : { equal: [software1, RELATIONSHIP, host, TARGET, uuid ] }

My apologies, but I believe I have an error in the filter clause in the above example. I think the condition in the filter needs a get_property function to work correctly, as follows:
tosca_definitions_version: tosca_2_0

capability_types:
  Host:
    description: for hosting software components

relationship_types:
  HostedOn:
    description: relationship to hosting container

node_types:

  Host:
    properties:
      uuid:
        type: string
    capabilities:
      host:
        type: Host

  SoftwareComponent:
    requirements:
      - host:
          capability: Host
          relationship: HostedOn

service_template:

  node_templates:

    host1:
      type: Host
      properties:
        uuid: host.1

    host2:
      type: Host
      properties:
        uuid: host.2

    host3:
      type: Host
      properties:
        uuid: host.3

    software1:
      type: SoftwareComponent
      requirements:
        - host:
            node: Host

    software2:
      type: SoftwareComponent
      requirements:
        - host:
            node: Host
            filter:
              - not:
                  [TARGET, uuid] : { equal:  { get_property: [software1, RELATIONSHIP, host, TARGET, uuid ] } }

Node filters now use boolean expressions as documented in https://docs.oasis-open.org/tosca/TOSCA/v2.0/csd05/TOSCA-v2.0-csd05.html#_Toc125468604. Using this syntax, the example above would look as follows:
tosca_definitions_version: tosca_2_0

capability_types:
  Host: {}

relationship_types:
  HostedOn: {}

node_types:
  Host:
    properties:
      uuid:
        type: string
    capabilities:
      host:
        type: Host

  SoftwareComponent:
    requirements:
      - host:
          capability: Host
          relationship: HostedOn
          count_range: [1, 1]

service_template:
  node_templates:

    host1:
      type: Host
      properties:
        uuid: host.1

    host2:
      type: Host
      properties:
        uuid: host.2

    host3:
      type: Host
      properties:
        uuid: host.3

    software1:
      type: SoftwareComponent
      requirements:
        - host:
            node: Host

    software2:
      type: SoftwareComponent
      requirements:
        - host:
            node: Host
            node_filter:
              $not:
                $equal:
                  - $get_property: [SELF, TARGET, uuid]
                  - $get_property: [software1, RELATIONSHIP, host, TARGET, uuid]

Of course, the example itself is a bit convoluted, since anti-collocation behavior should be specified instead using a declarative policy as suggested in Issue https://github.com/oasis-open/tosca-community-contributions/issues/141


Option to cycle backwards through menu

Calling menu.up() on position 0 doesn't do anything. It would be nice if it (optionally) cycles back to the item at the bottom of the list.

Yeah, that's doable. 👍


Remove server_kem_group_params

Problem:
A comment made it apparent that server_kem_group_params is (likely) redundant, unnecessary, and adding to the overall complexity of the PQ 1.3 code.
Solution:
Remove server_kem_group_params. Replace usage with chosen_client_kem_group_params. All keypairs are already stored in the `client_kem_group_params' array anyway, and we should be able to store the shared secret there as well.

Does this change what S2N sends over the wire? No
Does this change any public APIs? No
Which versions of TLS will this impact? TLS 1.3 (PQ only)

Requirements / Acceptance Criteria:
Removal of server_kem_group_params and appropriate refactor of code to use chosen_client_kem_group_params; or, a reason why this is not possible.

RFC links: N/A
Related Issues: N/A
Will the Usage Guide or other documentation need to be updated? No
Testing: Unit tests that directly reference server_kem_group_params will need to be adapted

Will this change trigger SAW changes? No
Should this change be fuzz tested? No

Out of scope:
N/A

After creating this, I've realized that we use server_kem_group_params to store the server's EC key share for the hybrid exchange. There's no other obvious place to store that, so that complicates the issue a bit and maybe makes it impractical to transition to the proposed solution. I'm leaving this open to investigate a bit more. There may be a different solution that cleans up the overall code a bit.


Choose an Image not work, when click on font.

ubuntu 15.10
chrome 48.0.2564.109
this demo.
http://www.material-ui.com/#/components/raised-button

Thanks a lot for reporting this :+1:


Dominant Color Detection From Image

Aim
Analysing of Dominant Colour in Image

What is the objective of the Script
Finding Dominant Colour: Finding Colour with K-means and giving appropriate colours to the pixel/data points of the image.

Details

Good Segmentation(Colour Extraction): Given an image in generic viewpoint, we wish to produce the best possible segmentation, by this we mean that most people would choose this segmentation if asked to make one, and it would make a good precursor for object recognition.
Analysis of different K in K-means: Different k’s can give totally different results, and usually, there is one K which is consistent with the data points, the actual K.


Update Diskmaker X to  v5.0.3

Turns Diskmaker X back into a versioned cask. The author of Diskmaker reached out to us and has re-uploaded the versioned downloads for us to use. Thanks @diskmakerx!
For more information about this commit please check the discussion related to the versioning of Diskmaker in this pull request: https://github.com/caskroom/homebrew-cask/pull/17519

Forgot to add the feed.

@victorpopkov Fixed the syntax error. I wanted to get the versioned cask back first, but I'll try to build the feed. There are a few concerns especially that the checksum is SHA1, can I specify that as a checksum?

@jonkoops Wrong person.
When talking about the feed, the only thing you need to do is this.

Thank you for the contribution. It needed some fixes, so they were made in 48aeee69053d73941ed3eafecbc389448fc35339. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


[Tabs] Export all tab components to allow extending

Bug, feature request, or proposal:
feature request
What is the expected behavior?
Extending the MatTabGroup
What is the current behavior?
not possible to extend MatTabGroup because of MatTabBody  and MatTabHeader and MatTabLabelWrapper are not included in module export list
What are the steps to reproduce?
Try to extend MatTabGroup to add tab close icon and function. You will get errors like "ERROR in : Can't bind to 'selectedIndex' since it isn't a known property of 'mat-tab-header'." to your overloaded template of MatTabGroup class
What is the use-case or motivation for changing an existing behavior?
Because having a static Tabs is not enough. I want to repoduce MDI behaviour where each tab will contain a named router-outlet of links which invoked by other components of application. And ofcource user must be able to close tabs he have opened before
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
all is latest to current date
Is there anything else we should know?
There is only few string to add in @NgModule section to export: [] here https://github.com/angular/material2/blob/master/src/lib/tabs/tabs-module.ts

This would be greatly appreciated

Closing since we do not intend to support extending these private classes


showing centered text without bubble

Hey,
I want to put a text that not related to the bubble chat. for example "sender1 made this conversation private". It should be with no bubble chat and can happen if there isn't any chat going on. How can this be achieved ? I tried all kind of ways to hide the bubble image, what is your suggestion?
Thanks in advance

Hey @rosothefox  :smile:
I'm cleaning up old issues and trying to finish the next release of the library. I'm sorry I don't have time to respond to all questions.
I'm going to close this issue, but the community should feel free to continue the discussion.
Other ways to get help:

Ask on StackOverflow with the jsqmessagesviewcontroller tag
See the FAQ
Search previous questions


⚠ Bofrost.at has degraded performance

In e77ffb4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1830 ms

Resolved: Bofrost.at performance has improved in 4cfada2.


osm file of new POIs not opening

created a simple survey with only an OMK question and only one tag

uploaded some completed forms

and then tried to open the downloaded .osm file in JOSM but got the following error

This is another Ona specific issue.
https://github.com/onaio/onadata
Could you please provide the OSM XML file shown here?

ah... the file is empty/ Zero bytes. a very premature end indeed.

@danbjoseph what server did you get this error?  Can you file this as a ticket on the onadata repo? This should be working but want to double check what's going on.

it's from the Red Cross instance

@danbjoseph - I spoke to @dalekunce and we're going to work on a strategy of keeping the red cross instance more up to date.  I also don't know if that error is a result of code or something like celery stopping (common issue if exports stop working).
In the very short term, we might want to come up with a strategy for testing this on our main ona or staging server.
The reason I say this is we have actively been working on changing/improving the way OSM exports work.  The initial version had the OSM files being stored as attachments and recently moved to storing the OSM data in an OSM db table (in addition).
Besides much faster performance on views and exports, this will also allow us to include OSM tags in exports.  Ie)  if you have an osm question for school in the form we can export
school_osm_id, school_name, etc.
Some of this hasn't made it to master though.   I'll let the group know when it is and stable.  I just wanted to flag we are actively work on this so many of the bugs you are seeing might be resolved.

@mberg when these changes are pushed to master we can bring them into the Red Cross system. Can you provide an update/install walkthrough.

@dalekunce - yes will do.  Once this is ready - we'll touch base to try and
come up with a good strategy for keeping the Red Cross version up to date.
On Tue, Nov 17, 2015 at 7:13 PM, Dale Kunce<EMAIL_ADDRESS>wrote:

@mberg https://github.com/mberg when these changes are pushed to master
we can bring them into the Red Cross system. Can you provide an
update/install walkthrough.
—
Reply to this email directly or view it on GitHub
https://github.com/AmericanRedCross/OpenMapKit/issues/96#issuecomment-157417136
.

Closing, Ona specific issue.


Re-enable flowtype warning

This was fixed with https://github.com/gajus/eslint-plugin-flowtype/pull/233
Updating to 2.34.1 also applies this fix (and no others besides these two): https://github.com/gajus/eslint-plugin-flowtype/pull/240

Thanks!

Hi there! This change is out in<EMAIL_ADDRESS>please give it a go! Thanks.


Some posts be added to feed.xml file But Others not be added. How Can I solve?

I use jekyll-feed.
and include {% feed_meta %} in .
But Some posts be added to feed.xml file But Others not be added.

I am Korean user

Only the most recent 10 posts are added to the feed.
Which posts is your feed missing?

oh I got it. thanks. I've posted over 10 posts


update to embedded-hal:1.0.0-alpha.10

note that i updated this purely based on the build errors and the release notes.

@dirbaio and @eldruin: nearly all commits in e-h 1.0.0-alpha.10 come from you. could you please double-check if the changes here match the expectations you have for the implementation of these APIs? thanks!
this is a preparation to later add the mock implementation of the new e-h 1.0 PWM APIs (which are new with this release, so the update is a pre-requisite).

Great, thanks @rursprung @newAM!


[BUG] Inconsistent Navigation Bar Behavior and Excessive Movement

Describe the bug
The navigation bar is inconsistent between page navigations and bounces, potentially leading to a poor user experience. It appears there are three different versions:

How to fix it?
Standardize the code for the navigation bar to ensure consistent behavior across all pages.

/assign me this


Feat/add mapping fires 2

This PR renames the wfs notebook and adds it to the TOC
@mccabete how does this look to you? You can check it out via the preview: https://nasa-impact.github.io/veda-docs/pr-preview/pr-79/notebooks/tutorials/mapping_fires.html

Kindly asking @jsignell to review in my place.

@abarciauskas-bgse this looks fine. There are a few changes that I think got lost in the file restructuring, but I can add them either here or after the merge.

Added those changes to #80

This looks broadly good! I think some things just got a little lost in the merges. I am fixing a typo and the binder link now and will push to this PR.

Ok I just read through and re-executed the notebook to make double sure that Tess's changes made it in. I am going to merge when this is green, but just shout if something is missing :)

Thanks Julia!

From: Julia Signell @.>
Sent: Tuesday, June 27, 2023 8:50 AM
To: NASA-IMPACT/veda-docs @.>
Cc: Mccabe, Tempest @.>; Mention @.>
Subject: Re: [NASA-IMPACT/veda-docs] Feat/add mapping fires 2 (PR #79)
Ok I just read through and re-executed the notebook to make double sure that Tess's changes made it in. I am going to merge when this is green, but just shout if something is missing :)
—
Reply to this email directly, view it on GitHubhttps://github.com/NASA-IMPACT/veda-docs/pull/79#issuecomment-1609438994, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFCH6FZHXL456EIW5OVTGT3XNLJIDANCNFSM6AAAAAAZQ26WOI.
You are receiving this because you were mentioned.Message ID: @.***>


Cant install

might be related to #663
$ sudo npm install -g now
/usr/bin/now -> /usr/lib/node_modules/now/download/dist/now

><EMAIL_ADDRESS>postinstall /usr/lib/node_modules/now
> node download/install.js

{ Error: EACCES: permission denied, open '/usr/lib/node_modules/now/download/dist/now'
    at Object.fs.openSync (fs.js:651:18)
    at Object.fs.writeFileSync (fs.js:1300:33)
    at _callee$ (/usr/lib/node_modules/now/download/dist/download.js:4754:26)
    at tryCatch (/usr/lib/node_modules/now/download/dist/download.js:4997:40)
    at Generator.invoke [as _invoke] (/usr/lib/node_modules/now/download/dist/download.js:5235:22)
    at Generator.prototype.(anonymous function) [as next] (/usr/lib/node_modules/now/download/dist/download.js:5049:21)
    at step (/usr/lib/node_modules/now/download/dist/download.js:6603:30)
    at /usr/lib/node_modules/now/download/dist/download.js:6621:14
    at Promise (<anonymous>)
    at F (/usr/lib/node_modules/now/download/dist/download.js:3466:28)
  errno: -13,
  code: 'EACCES',
  syscall: 'open',
  path: '/usr/lib/node_modules/now/download/dist/now' }
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>postinstall: `node download/install.js`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/marius/.npm/_logs/2017-06-12T17_51_34_480Z-debug.log

same thing is shown on 'sudo npm install -g<EMAIL_ADDRESS>

@MariusAlch have you tried this? https://github.com/zeit/now-cli/issues/651#issuecomment-307833039 🙏

Ignored fixing permissions, after that everything is working fine.


Best approach to compile Bundles with nested jars

I have another question depending nested jars. I have following manifest:
Require-Bundle: org.apache.ant,
 org.eclipse.core.runtime,
Bundle-ClassPath: lib/ant-contrib-1.0b3.jar,
 lib/AntLowerUppercase.jar,
 lib/cpp-commons-ant.jar,
 lib/tools.jar,
 .

When i build this he cannot find the packages that are included in the jar Files. So i want to ask what would be the best solution to compile such bundels?

@golauty Have you found solution?


Similar rule to eslint-comments/no-use but only preventing non-restricted version

Howdy 👋
We have just come across the need to prevent developers from willy-nilly turning off all eslint-rules, but want to allow them to specify the rules they want to turn off. Our specific use case would be to disable using eslint-disable-next-line without the rule qualifiers but I would imagine that it might be a more generic implementation that might apply across all the comment types.
Is this something that would make sense to add to your repo? If so I wouldn't mind contributing with a bit of guidance.

Thank you for this issue!
Sounds good to me.
Maybe, includes and excludes would be useful.
{
    "eslint-comments/no-use": ["error", {"allow": [
        { "type": "eslint-disable", "includes": ["a-rule", "another-rule"] },
        { "type": "globals", "includes": ["a-var", "another-var"] },
    ]}]
}

{
    "eslint-comments/no-use": ["error", {"allow": [
        { "type": "eslint-disable", "excludes": ["no-undef", "no-unused-vars"] },
    ]}]
}

So what you're proposing is essentially a whitelist (or blacklist) of eslint-disable comments with the whitelist for the rules that you are allowed to disable.
I'm trying to think if this will fit my usecase 🤔  essentially we want to prevent all cases of // eslint-disable-next-line max-statements which we could achieve with the following rule:
{
    "eslint-comments/no-use": ["error", {"disallow": [
        { "type": "eslint-disable", "includes": ["max-statements"] },
    ]}]
}

maybe in this case deny would be better instead of disallow but you get my point. Would this sort of syntax also dissalow "bare" // eslint-disable-next-line statements? i.e. ones without a specifier?
I hope my question makes sense 😖 maybe you could give an example config that would meet my use case and we could then move onto a PR with failing tests and implement this as TDD

I assume we are only talking about having a list of enforced rules that users should not be able to disable via a comment.
If that's the case, @mysticatea, I don't think adding options to eslint-comments/no-use will do. If you want to enforce a rule you probably don't want it do be disableable in any imaginable way (be it eslint-disable, eslint-disable-line or eslint-disable-next-line — those should all be banned), but in case of eslint-comments/no-use you would have to duplicate your list of enforced rules for each kind of comment that can disable it.
This sound more like a separate rule like eslint-comments/enforced-rules or maybe eslint-comments/protected-rules or something, accepting options like this:
{
  "blacklist": [
    "the-rule-you-cant-disable-with-a-comment"
  ]
}

or:
{
  "whitelist": [
    "the-rule-you-can-disable-with-a-comment"
  ]
}

This new rule would also imply eslint-comments/no-unlimited-disable, otherwise it's really easy to get around it.

@mansona also note that if this gets implemented (and if I understand your intentions correctly), your nasty developers will still be able to suppress whatever rules they want by first disabling enforced-rules.

I apology for my lacking communication. This thread was buried into busy life.
After I rethought, I realized that I ran too far. I added a simple rule eslint-comments/no-restricted-disable which disallows disabling of rules with glob patterns. Is it enough?

Please reopen or open new issue if it's not enough.
Thank you.

@futpib thanks for weighing in, I think your insight is completely what I was thinking but put in a different way. Yes, you are right that the "nasty developer" would be able to just change these rules but it is easier for us to be more vigilant this way.
@mysticatea I think you may have perfectly implemented exactly what I wanted 👍  🎉  thanks a million


Add note in docs for interpolate that Only method=linear interpolation is supported on MultiIndexes.

Trying to interpolate a DataFrame with MultiIndex:
lib/python2.7/site-packages/pandas/core/generic.pyc in interpolate(self, method, axis, limit, inplace, downcast, **kwargs)
   2868
   2869         if isinstance(self.index, MultiIndex) and method != 'linear':
-> 2870             raise ValueError("Only `method=linear` interpolation is supported "
   2871                              "on MultiIndexes.")
   2872

ValueError: Only `method=linear` interpolation is supported on MultiIndexes.

add a note in the docs.

@cancan101 thanks for the reports! (and feel free to open PRs for it :-))

@cancan101 link redirects to the Pandas docs front page.
Here is a link to the doc paged referenced in the issue http://pandas.pydata.org/pandas-docs/stable/generated/pandas.Series.interpolate.html for anyone working on a PR and wondering which doc page should be amended.


Provide one-click download of CSV files as a zip

Since large files can take a while to process, the zip file is
prepared in the background so that the user can continue browsing
the site. The background processing is provided via the Sucker Punch
gem, which doesn't require any additional Heroku dependencies such as
Redis.
While the zip file is being generated, the button on the admin
interface reads "Generating zip file", and when it's ready, it reads
"Download zip file".
Once the file has been downloaded, it is deleted from the /tmp folder
a minute later so that a new zip file can be generated at a later time.
The zip file's name contains the date at which it was downloaded to
make it easy to see when the zip was last generated.
I also cleaned up the csv.shaper files to remove duplicated cells.

Coverage decreased (-0.04%) to 99.36% when pulling 1efd635dd24df25262184895ccc07b7c3b7d7bed on 326-zip-csv-files into d4426dd722a7f1f9e2a8ef04956779df84d34a87 on master.

Coverage decreased (-0.04%) to 99.36% when pulling 91c2abd4c6e629c79e827daaae16035b650f3d49 on 326-zip-csv-files into d4426dd722a7f1f9e2a8ef04956779df84d34a87 on master.

Coverage decreased (-0.04%) to 99.36% when pulling d449dcabf1f0194c7192eb7d3547f061c4f2974b on 326-zip-csv-files into 6383c8a45fd0f58560f8feb63c2b17ab68ef9c2b on master.


Building wheels

As numcodecs includes source that needs to be compiled, there can be some challenges or technical hurtles that can be encountered by a user that they may not be aware of. While we do solve this in some sense by supplying conda-forge packages with prebuilt binaries, pip remains the defacto way for Python users to get packages. However in the case of pip the user will get the sdist, which needs compilation. While this does work, there is definitely some appeal to providing a pip solution that does not require compilation (i.e. prebuilt wheels). This would help users avoid compatibility problems like this one ( https://github.com/zarr-developers/numcodecs/issues/69 ).
One solution would be to piggy back off of whatever conda-forge ends up doing to also supply wheels ( https://github.com/conda-forge/conda-smithy/issues/608 ). This would work well for Windows. Though on macOS conda-forge uses the 10.9 SDK (instead of the 10.6 SDK that Python tries to support). Also on Linux conda-forge uses CentOS 6 with glibc 2.12 (instead of CentOS 5 with glibc 2.5 used by manylinux1). In practice these two cases that don't sync up will be hard for Python to require much longer and some packages already don't comply (happy to go into details if this is of interest). This certainly would enjoy the nice benefit of the architecture and community conda-forge has in place to solve these issues. It also seems that proponents of the wheel format are interested in collaborating, which definitely should help.
If that doesn't work, the alternative would be to build wheels here. For Linux, there is manylinux1 Docker image, which could be used fairly easily to build these. For macOS, we could try to build them here or reach out to MacPython for help. For Windows, it would probably be best to reuse the conda-forge solution as much as possible as that already fits the requirements well. Probably would require some like issue ( https://github.com/conda/conda-build/issues/2490 ) to solved. Though I don't think anyone that has had time to do that. Alternatively one can build a wheel with conda-build.

Thanks @jakirkham. FWIW I'm happy with whatever is the path of least effort
both now and in the future. If that means we are not totally compatible
with manylinux at the moment then I'm OK with that. I defer to your
judgement, please feel free to proceed as you see fit.
On Monday, March 5, 2018, jakirkham<EMAIL_ADDRESS>wrote:

Have a couple of examples of wheel builds in this comment
https://github.com/conda-forge/conda-smithy/issues/608#issuecomment-370359867.
For Numcodecs, in particular, please take a look at PR (
conda-forge/numcodecs-feedstock#17
https://github.com/conda-forge/numcodecs-feedstock/pull/17 ), which
would build both conda and wheel packages from the same build.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zarr-developers/numcodecs/issues/70#issuecomment-370366328,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAq8Qsop7mXI103bs4dwntcAPMYcnV2Oks5tbQscgaJpZM4SbELq
.

--
If I do not respond to an email within a few days, please feel free to
resend your email and/or contact me by other means.
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health http://cggh.org
Big Data Institute
Li Ka Shing Centre for Health Information and Discovery
Old Road Campus
Headington
Oxford
OX3 7LF
United Kingdom
Phone: +44 (0)1865 743596 or +44 (0)7866 541624
Skype: londonbonsaipurple
Email<EMAIL_ADDRESS>Web: http://a http://purl.org/net/alimanlimanfoo.github.io/
Twitter: https://twitter.com/alimanfoo

Thanks @alimanfoo.
Right now my feeling is reusing our work at conda-forge to do this is the best path. We will have more resource generally (compute, manpower, storage, etc.) to push this forward. Not to mention we can easily store the wheels on anaconda.org right along side our conda packages.
Expect the wheel folks will be interested in smoothing out the compatibility issues once they see some demonstrated success of wheels in conda-forge. Perhaps by making manylinux2 for instance or broadening the manylinux spec to include arbitrary glibc. There's already some pressure on them to do this as tensorflow and other packages are breaking the manylinux spec anyways ( https://github.com/tensorflow/tensorflow/issues/8802 ). Also CentOS 5 is an unsupported OS as of last year. So they will have to update and they know this ( https://github.com/pypa/manylinux/issues/96 ).
The technical issues of getting wheels in there are minimal IMHO. Will have to see how others in conda-forge feel about having wheels included.

cc @rabernat

Just wanted to say that binary wheels on PyPI would be useful for me. I like to test my code using both the pip and conda infrastructure. Compiling numcodecs for each CI build takes quite a bit of time and a bdist_wheel would be very handy.
I'm loving zarr/numcodecs by the way; thanks for all the work!

Thanks Jerome. @jakirkham what's the current situation re building wheels
via conda-forge?
On Wed, 25 Apr 2018, 14:11 Jerome Kelleher<EMAIL_ADDRESS>wrote:

Just wanted to say that binary wheels on PyPI would be useful for me. I
like to test my code using both the pip and conda infrastructure. Compiling
numcodecs for each CI build takes quite a bit of time and a bdist_wheel
would be very handy.
I'm loving zarr/numcodecs by the way; thanks for all the work!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zarr-developers/numcodecs/issues/70#issuecomment-384281052,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAq8Qvl_Sthxtx3Xz0579yuQVH6ugDwzks5tsHYWgaJpZM4SbELq
.

Well we are in the midst of migrating to conda-build 3. So that is pretty much zapping all developer time. Not to mention other work activities outside of conda-forge. IOW it is stalled due to lack of time.
That said, we are able to build wheels using the conda-forge recipe using PR ( https://github.com/conda-forge/numcodecs-feedstock/pull/17 ). There are of course the compatibility issues we already discussed mainly on Linux, but it looks like PyPA is working on a new manylinux2 spec ( https://github.com/pypa/manylinux/pull/152 ), which would resolve this. The main issue is uploading the wheels actually. The current upload script would need to be reworked for wheels ( https://github.com/conda-forge/conda-forge-ci-setup-feedstock/issues/6 ). Not sure what that entails yet.

Thanks @jakirkham. Am I right in understanding that https://github.com/conda-forge/numcodecs-feedstock/pull/17 is now successfully building wheels on all platforms?

It does appear that way. Hadn't had time to check since that comment. :)
The main challenge is we don't have a way to upload them from the CIs yet. Though one could certainly build those locally and upload them to PyPI or wherever one wishes.

Ok, cool. I'm happy to wait if there will be support for uploading coming
down the line.
Don't know if possible but would be cool if could automate upload to PyPI,
at one point I was building windows wheels via appveyor and manually
uploading to PyPI but it was annoyingly slow and fiddly, had to upload one
file at a time via the web form, actually why I stopped doing it.
On Mon, 30 Apr 2018, 23:59 jakirkham<EMAIL_ADDRESS>wrote:

It does appear that way. Hadn't had time to check since that comment. :)
The main challenge is we don't have a way to upload them from the CIs yet.
Though one could certainly build those locally and upload them to PyPI or
wherever one wishes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zarr-developers/numcodecs/issues/70#issuecomment-385553603,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAq8Qt98wnmKc9SbvY1qpBELuDGC_IYpks5tt5dngaJpZM4SbELq
.

So these days there is conda-press, we could try using this to make wheels from the conda-forge packages.
ref: https://regro.github.io/conda-press-docs/

So I tried creating some wheels from the conda-forge packages using conda-press and uploaded them to my Anaconda channel. If some people could please try these out and let us know if this works, that would be very help. 🙂
pip install -i https://pypi.anaconda.org/jakirkham/label/test/simple numcodecs

ref: https://anaconda.org/jakirkham/numcodecs

I'm getting this error:
(numcodecs-test-2) ➜  ~ pip install -i https://pypi.anaconda.org/jakirkham/label/test/simple numcodecs
Looking in indexes: https://pypi.anaconda.org/jakirkham/label/test/simple
Collecting numcodecs
  Downloading https://pypi.anaconda.org/jakirkham/label/test/simple/numcodecs/0.6.4/numcodecs-0.6.4-0_py37h4a8c4bd-cp37-cp37m-macosx_10_9_x86_64.whl (1.2MB)
     |████████████████████████████████| 1.2MB 724kB/s
ERROR: Could not find a version that satisfies the requirement numpy (from numcodecs) (from versions: none)
ERROR: No matching distribution found for numpy (from numcodecs)

Yeah I think that is because pip is assuming this is a full mirror. We probably have to tell it to supplement it with PyPI or manually install the missing pieces.
That said, it appears some content was missing from the wheels. Am following up in issue ( https://github.com/regro/conda-press/issues/52 ).

@jakirkham I thought the manylinux problems had been fixed upstream recently? Something about manylinux2010? Anyway, I'm generally ok with requiring Linux users to have a compiler, so even just providing windows and Mac wheels would make me happy...

I think conda-press is looking very promising.
That said, for something simple like numcodecs, it may be simpler to just create the wheels directly. We resolved this for the python-blosc package:
https://dev.azure.com/blosc/python-blosc/_build/results?buildId=223
It is fairly simple and elegant to set up continuous deployment on Azure Pipelines, too.

Where are Blosc’s wheels published?

They are not published to PyPI yet since we just generated them on Monday and @FrancescAlted and @
aleix11alcacer are enjoying travels. But, they can be downloaded from the Artifacts button in the Azure interface:

Oh great! Well congrats on getting them built. Also thanks for working on this.
The reason I ask is Numcodecs is primarily building bindings to Blosc internally. One solution here might be we rely on the new Blosc wheels all of you have made to do that for us.
I don’t know if that will be able to completely eliminate compilation in Numcodecs, but it is a start.

Cool, please let me know if I can be of help.

It would be nice if you can use the excellent work from @thewtex to generate builds for numcodecs.  However, you should not expect that the Blosc team would maintain an official build for python-blosc, and the reason is that generating wheels has been an important source of headaches for the projects that we have decided to produce them (see the issues that the PyTables team has had in producing wheels in my talk about what's new in Blosc and PyTables in recent PyData NYC 2019).  In short, right now Blosc is a very modest project and we don't have resources for maintaining binary wheels.
Having said this, we would be grateful if somebody would commit as a release manager for Blosc and take responsibility for producing a curated selection of wheels.  Another possibility, and probably more long term solution, would be to receive some donation to Blosc via NumFOCUS, allowing to put some people for taking care of releasing binary wheels through the different releases of both Blosc and Python (but being realistic, we should not expect this to happen anytime soon as the only donation that Blosc has received since becoming a NumFOCUS sponsored project has been a small development grant for getting Blosc2 out of alpha stage.

Yep, completely understand that, @FrancescAlted. I think we are in the same boat.
Have been personally quite happy with Conda for this kind of thing, but I get that different people use different package mangers (including pip) depending on their needs and use cases. I don't know how we scale out building across these ecosystems. It's a very hard problem.
I'm hopeful that something like conda-press could answer this for pip wheels. Though it's still a bit young.
I'm not sure how we answer the other packaging use cases.

Hi. What is progress with building wheel for numcodecs? I can contribute with building wheel using cibuildwheel.

I would really like this. I spend approx 10 mins a day staring at numcodecs installing.

I'm not aware of anyone working on this. No objections to someone building this for Numcodecs as long as they are willing to keep up maintenance of it.

I would definitely be open to helping out, but don't have much experience with the conda-forge etc. Any guidance on how to do this? My first thought would be to use Travis CI + docker, and then use the manylinux docker image to build the wheel and push it to PyPI. Or maybe @Czaki has some more experience.

The python-blosc setup.py could be used as a reference for a build configuration that can easily generate wheels.
The python-blosc Azure Pipelines configuration shows how to generate distributable, cross-platform wheels. However, GitHub Actions are nicer than Azure Pipelines now. They can be used to run tests, build the packages, publish GitHub Releases with build artifacts, and publish to PyPI.

Ok. I create PR #224 with build wheel. Publishing can be added using links given by @thewtex.
It is only build wheel with c-blosc embedded.
@nbren12 Done.

great thanks @Czaki!

Another possibility, and probably more long term solution, would be to receive some donation to Blosc via NumFOCUS, allowing to put some people for taking care of releasing binary wheels through the different releases of both Blosc and Python

@FrancescAlted what amount would you need to make this happen?

@hammer Well, a reasonable amount for taking care of things like this would be a similar amount than for a small grant from NumFOCUS (about $5,000 USD).  A small grant not only shows appreciation but it also motivates us to put resources beyond short-term on the tasks (well above 1 year).  Half of a small grant could also me a possibility, but our comittment mid-term should not be as high.

@FrancescAlted great I have sent you an email to discuss the logistics of the donation.

I feel it would be extremely easy to obtain $5000 from any number of sources to support this work. Some ideas:

NumFocus
USGS (cc @rsignell-usgs), who is using Zarr extensively
AWS / GCP / Azure, who all actively support cloud-native data format development

Furthermore, if we could frame this as a service (rather than a donation), any number of universities or federal labs could potentially support it.

@rabernat I appreciate your optimism but I am skeptical that obtaining funding for improving the build and release process of an infrastructure open source library is possible from other sources. I'd be happy to share my experiences asking for money for this kind of work in the past!
I'm personally offering to make this donation once I get the EIN from @FrancescAlted, so luckily in this case it will not be necessary to seek funding from those alternative sources.

I'm personally offering to make this donation once I get the EIN

🥇  Well this is of course much easier! Thanks for your amazing generosity!

@hammer For the record, I have replied to your private message.  Thank you so much!

Sorry, closing was automatically triggered via #224. Happy to (have) re-open(-ed), or a new issue can be started for blosc build integration.

Now that @hammer donation is complete (thanks Jeff!)  we are working towards producing wheels for Blosc.  Right now our focus is python-blosc, but perhaps you guys are rather more interested on C-Blosc itself.  We have two possibilities:

Provide both static and dynamic libraries in the python-blosc wheel.  That means that after installing it via pip, the libraries are accessible to other projects that just need C-Blosc libraries (like zarr/numcodecs).

Do another wheel for just the C-Blosc library.  AFAIK, this is possible (people like cmake folks or Intel are doing this for pure C/C++ libraries for long time), but we are not sure on how to proceed in this case, so we would be grateful to get some advice here.

is indeed easier for us, but we would like to keep the zarr team as happy as possible ;-). Thoughts?

Thanks Jeff! 😄
Originally was also thinking 1 would make the most sense. So agree with that as well. There are some parts of Numcodecs that link directly to things like LZ4, Zstd, etc. as included by Blosc. That said, there are also other Python libraries that supply wheels and Conda packages for those. So we could handle them that way. Alternatively we could do the same thing we are doing now just with the sources of those libraries. IOW I think we have enough other options to handle C/C++ without issues.
If anyone else here has thoughts, feel free to share 🙂

I also meet the idea of writing some small wrapper that loads c/c++ extension during runtime rather than linking during compilation. This allows using the external library without going through python code (speedup) but without repetition of a binary blob.
But I do not implement such a thing.

Thanks for the feedback.  For now, we will work towards providing wheels for python-blosc, as suggested.  However, we will still try to pursue option 2) so as to build wheels for the pure C-Blosc library (and perhaps make it a dependency for python-blosc).  Again, any info on how to create a wheel for a pure C project is welcome.
Will keep you informed.

Thanks Francesc!

Hi there!
We have been hard at work generating wheels for python-blosc and we have come with a pretty comprehensive set at: https://pypi.org/manage/project/blosc/release/1.9.3.dev0/ (this release is yanked, so install it via pip install blosc==1.9.3.dev0).
We are including not only the python-blosc extension inside the wheels, but also the static and dynamic libraries of C-Blosc (I think this is what you need for numcodecs).  This is our first attempt at building wheels, but we have been successful on testing the libraries on Mac and Linux already (Windows is still being explored, but the libraries are there already for you to test).
Could the Zarr team please give this a try and tell us how it goes?
BTW, the guys behind this effort have mainly been @oscargm98 and @aleixalcacer, and they will be glad to hear and help you.

Hi.  We have manually (and not only via CI) tested the wheels on Windows, Linux and Mac, and they look good to us.  We have made some detailed instructions on how to compile some C-Blosc examples by using the python-blosc wheels at: https://github.com/Blosc/c-blosc/blob/master/COMPILING_WITH_WHEELS.rst.
Our intention is to release soon a new version of C-Blosc (1.21.0) with updated codecs (specially the new zstd 1.4.8), and shortly after an updated version of python-blosc (1.10.0) so as to use latest C-Blosc sources and do a release of it with the (official) wheels.  It would be nice if you can provide feedback for Zarr (please note that, until we do the new release, you still need to use pip install blosc==1.9.3.dev0). Thanks!

Hi there! We have just released a new version of python-blosc with binary wheels fully implemented: https://github.com/Blosc/python-blosc/releases/tag/v1.10.0
Note that support for AVX2 run time discovery has been activated. That means that, if you use the libraries in this wheels, you can leverage the full capabilities of Intel CPUs. Please give it a spin and report back any possible flaws. Enjoy!

Thanks @oscargm98! I've filed https://github.com/zarr-developers/numcodecs/issues/262 to track using these wheels in the numcodecs build.


nzExtra can not give a context to template

What problem does this feature solve?
https://github.com/NG-ZORRO/ng-zorro-antd/blob/d1f0321979444e6a7ef0b6e93d33424ec19a81b5/components/result/result.component.ts#L49
I think it will be better to have a nzExtraContext input
What does the proposed API look like?
Some thing like
@Input() nzExtraContext: {[key: string]: any}

<div class="ant-result-extra" *ngIf="nzExtra">
     <ng-container *nzStringTemplateOutlet="nzExtra; context: nzExtraContext">
        {{ nzExtra }}
     </ng-container>
</div>

any reason need nzExtraContext?

reuse template

if you want to reuse the template, you can move the template inside the *ngFor

@vthinkxie Thanks for your suggestion


Increase the padding around the edges of the note.

I think the top line is too close to the edge of the note.

Completed.
Commit: https://github.com/3colorr/Mizuame/commit/1b77eccabb6283f0c2c636d60b0c07873d82258b
Before

After


Add site values as defaults for author

Use site options as default if not is set by post.

@CGarces thanks for the pull request! I implemented this as part of #52. :smile:


bug: creating a tag in the sidebar returns 500

Describe the bug
Creating a new Tag in the sidebar will throw an error but still save the Tag within the database.
I already updated the source and got the following error within
Error: [Immer] minified error nr: 4. Find the full error at: https://bit.ly/3cXEKWf
    at a (_app-62d4774c9ec39cc8.js:1:20196)
    at P (_app-62d4774c9ec39cc8.js:1:22206)
    at t.produce (_app-62d4774c9ec39cc8.js:1:26354)
    at _app-62d4774c9ec39cc8.js:1:26006
    at n (_app-62d4774c9ec39cc8.js:1:28102)
    at addTag (_app-62d4774c9ec39cc8.js:1:30311)
    at O (132.e5452ba71a226522.js:1:9124)

The error happens in the sidebar.jsx within  the function saveQuickTag
Reproduction
Create a new tag from the sidebar
System Info
Build locally with Docker
Build remotely on Docker Swarm
Install it without Docker

  System:
    OS: Linux 5.10 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (16) x64 Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz
    Memory: 48.41 GB / 50.08 GB
    Container: Yes
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 16.17.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.15.0 - /usr/local/bin/npm

Used Package Manager
pnpm
Validations

[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Thanks this clearly looks like a frontend JS error on my side, will take a look!

Can confirm this is still an issue


Fix Int precision issue part 2

Closes : #261 ;

@sophie-cluml Looking at #257, it seems that for some functions with u32, it's wrapped in ID instead of StringNumber. I was wondering if those were two in the same thing or when is it applicable?
Also, I know that usize/isize can be bigger than 32-bits (64-bits depending on the target platform) however, how would I determine if they would need to be changed to i32 or StringNumber (e.g. something like error_code ,rule_id, or cluster_id) or if the other int types (u32, etc.)  will fit within i32?
Would I need to make tests for that with std::u32::MAX and inserting and querying to check the fields? If yes, would I need to make a separate PR in review-database to change the fields that are say u32 to i32?

@marioCluml
The change was made because the tag_ids value is appropriate to express it as ID type rather than StringNumber(u32).
There is no need to change the value of i32.
However, in the case of u32, you need to change it to StringNumber because the positive integer value that can be displayed is larger than i32.
In the case of usize and isize as a type of GraphQL API response, it seems that conversion is also necessary.
However, for xxxTotalCount used for paging, you do not need to modify it.

@marioCluml
The codes below also seem to need to be changed.
    async fn error_code(&self) -> u32 {
        self.inner.error_code
    }
    async fn request_len(&self) -> usize {
        self.inner.request_len
    }
    async fn response_len(&self) -> usize {
        self.inner.response_len
    }

@marioCluml The codes below also seem to need to be changed.
    async fn error_code(&self) -> u32 {
        self.inner.error_code
    }
    async fn request_len(&self) -> usize {
        self.inner.request_len
    }
    async fn response_len(&self) -> usize {
        self.inner.response_len
    }

@henry0715-dev Done, I believe I fixed all instances in those files just was waiting for confirmation if I should use ID or StringNumber for something like rule_id.

@sophie-cluml @henry0715-dev Should I include part 3 and part 4 in this PR? It seems that since they are nearly the same it will be feasible and will need less PRs to review but if they do need to be separated I can do two separate PRs for part 3 and part 4 instead of including it in this one.

@marioCluml I think it would be nice to limit the target of this PR to a single issue, since I think this is your first PR for the similar issues. And personally, I prefer to make a PR for each issue if possible.

@marioCluml
I think it would be better to add a description to each function.
Examples are as follows.
https://github.com/aicers/review-web/pull/257/files#diff-021a3134ce1a3114350da75bb628e336bd6df5835d3963b72b64bf4645869372R100

Could you rebase please?

I think https://github.com/aicers/review-web/pull/267/files#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4edR56 line refers to the similar task carried out by Henry, so I would like to suggest combining your CHANGELOG with this line.

I think https://github.com/aicers/review-web/pull/267/files#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4edR56 line refers to the similar task carried out by Henry, so I would like to suggest combining your CHANGELOG with this line.

Done, Will apply to part 3 and part 4 sequentially after merges.


Missing input gene volumes

combine_markers_ccfv2_config.yaml requires various gene volumes as input (i.e.: data/ccfv2/marker_volumes/CNP.nrrd) but no instructions are provided on how to obtain these files. Should these files be curled, or are these files part of a missing pipeline step?

I think @drodarie should be able to explain that best.

These datasets should be obtained through the DeepAtlas pipeline as describe here.
This is not part of the atlas-densities pipeline.

How are multiple IDs for different genes supposed to be merged? I.e., there are multiple cnp experiments. Should all of these experiments be interpolated and then averaged?
Is it "safe" to combine coronal and sagittal experiments? Sagittal experiments only cover one hemisphere (namely, the left hemisphere).

In the README. It is mention that you can read Eroe et al. 2018 for more info on the method to combine. Alternatively, you can just read the docs of the function combine that is called at this step.
atlas-densities expect one 3D voxelized ISH dataset per gene. The operations of interpolation and merging necessary to obtain them are not done here. If you wish to replicate the results of Erö or Rodarie then this is the list of experiment ids used:

mbp: 112202838,
gfap: 79591671,
s100b; 79591593,
aldh1l1: 68631984,
tmem119: 68161453,

For these papers, the ISH datasets were interpolated, and the sagittal experiments were mirrored. I attempted a combination of different datasets in my paper and it seemed to improve the results.


Unable to find Xcode build setting: MARKETING_VERSION

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

After upgrading to Fastlane 2.134 the get_version_number action fails to locate the MARKETING_VERSION for the project. This issue presents itself when I run it locally and on a CircleCI build server.
Command executed
I've ran the following command:
$ fastlane run get_version_number xcodeproj:MyApp.xcodeproj target:MyAppQA

Which results in the following output:
[✔] 🚀
[16:48:30]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[16:48:30]: --------------------------------
[16:48:30]: --- Step: get_version_number ---
[16:48:30]: --------------------------------

[!] Unable to find Xcode build setting: MARKETING_VERSION

Complete output when running fastlane, including the stack trace and command used

I've also tried running the fastlane qa_adhoc command from my fastfile and it results in the following output:

 [✔] 🚀
[16:57:51]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
DEBUG [2019-10-25 16:57:52.20]: Checking if there are any plugins that should be loaded...
INFO [2019-10-25 16:57:52.83]: ------------------------------
INFO [2019-10-25 16:57:52.83]: --- Step: default_platform ---
INFO [2019-10-25 16:57:52.83]: ------------------------------
INFO [2019-10-25 16:57:52.84]: Driving the lane 'ios qa_adhoc' 🚀
INFO [2019-10-25 16:57:52.84]: --------------------------------
INFO [2019-10-25 16:57:52.84]: --- Step: get_version_number ---
INFO [2019-10-25 16:57:52.84]: --------------------------------
WARN [2019-10-25 16:57:52.91]: Lane Context:
INFO [2019-10-25 16:57:52.91]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios qa_adhoc"}
ERROR [2019-10-25 16:57:52.91]: Unable to find Xcode build setting: MARKETING_VERSION
INFO [2019-10-25 16:57:52.91]: Successfully generated documentation at path '/README.md'
ERROR [2019-10-25 16:57:52.91]: fastlane finished with errors

Environment

 ✅ fastlane environment ✅
Stack

Key
Value

OS
10.15

Ruby
2.6.3

Bundler?
false

Git
git version 2.23.0

Installation Source
~/.rvm/rubies/ruby-2.6.3/bin/fastlane

Host
Mac OS X 10.15 (19A583)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.6.3/lib

OpenSSL Version
OpenSSL 1.1.1c  28 May 2019

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
default_platform :ios

platform :ios do
  if ENV['CI'] then
    before_all do
      setup_circle_ci
      unlock_keychain( # Unlock an existing keychain and add it to the keychain search list
        path: "/Users/distiller/Library/Keychains/fastlane_tmp_keychain-db",
        password: ''  # empty password
      )
      import_certificate(
        keychain_name: 'fastlane_tmp_keychain',
        certificate_path: './fastlane/Certificates.p12',
        certificate_password: ENV["CERTIFICATE_P12_PASSWORD"] || "default"
      )
      install_provisioning_profile(path: "~/Library/MobileDevice/Provisioning Profiles/QA_Provisioning_Test.mobileprovision")
    end
  end

  desc "Build and run Unit Tests"
  lane :tests do
      run_tests(
          scheme: "MyAppTests",
          output_directory: '../TestOutput/'
      )
  end

  desc "QA Ad-hoc build"
  lane :qa_adhoc do
    branch = ENV['CIRCLE_BRANCH'] || 'local'
    last_dash_idx = (0 ... branch.length).find_all { |i| branch[i,1] == '-' }
    if last_dash_idx.count >= 2 then
      branch = branch[0..(last_dash_idx[1]-1)]
    end

    branch = branch.sub('/', '_')

    app_version = get_version_number(
      xcodeproj: 'MyApp.xcodeproj',
      target: 'MyAppQA',
    )

    build_ios_app(
      workspace: 'MyApp.xcworkspace',
      scheme: 'MyAppQA',
      configuration: 'Debug',
      skip_profile_detection: true,
      output_directory: '../Build/',
      output_name: "MyApp-#{branch}.v#{app_version}.Debug.ipa",
      # IT WONT WORK, has CDATA element, however xcodebuild will happily work
      # with it.
      # export_options: './QAExportOptions.plist'
      export_options: {   } # empty on purpose
      }
    )
  end
end

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.134.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

executable-hooks
1.6.0

bundler-unload
1.0.2

rubygems-bundler
1.4.5

bundler
1.17.3

etc
1.0.1

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.1

claide
1.0.3

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.12.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.6.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.7.0

tty-cursor
0.7.0

tty-spinner
0.9.1

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.67.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday
0.17.0

faraday_middleware
0.13.1

fastimage
2.1.7

gh_inspector
1.1.3

json
2.1.0

mini_magick
4.9.5

multi_xml
0.6.0

rubyzip
1.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.5

naturally
2.2.0

simctl
1.6.6

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mime-types-data
3.2019.0904

mime-types
3.3

multi_json
1.13.1

signet
0.11.0

memoist
0.16.0

os
1.0.1

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-env
1.2.1

google-cloud-core
1.3.1

digest-crc
0.4.1

google-cloud-storage
1.16.0

emoji_regex
1.0.1

forwardable
1.2.0

logger
1.3.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

date
2.0.0

fileutils
1.1.0

io-console
0.4.7

zlib
1.0.0

mini_portile2
2.4.0

nokogiri
1.10.4

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

generated on: 2019-10-25

After digging around for a bit I just realized that it's not that it's unable to find the value but rather that Xcode's "Update MyApp.pbxproj to recommended settings" option introduced a variable $(MARKETING_VERSION) which is not resolved when fastlane run get_version_number is ran. I fixed this by replacing the variable with the actual value.


Update README with Latest Features

The new discordian.sh script is super useful and needs to be documented properly in the README.md

This was completed via https://github.com/johndotpub/DiscordianAI/pull/28


Content changes

May be we need to think to show some other info or we can remove it if we are not showing or fetching any description of the workflow.

This issue is not specific to Litmus-UI.


HTTPS Support

Would it be possible to add support when connecting over https ? Ideally need it to ignore certificate errors on connection given most people will not have a cert that is properly linked to a CA.

I skip this step by using HAProxy

I skip this step by using HAProxy

Not getting it ? I enforce https on all my app's on my LAN so how would HAProxy help ? My HA is set to only allow https access as per best practice.


InitializeSandbox error

Hello, I'm having the following issue:
INFO @ src/xvfb.cpp:60 -- Starting Xvfb X server as child process
INFO @ src/xvfb.cpp:131 -- Xvfb X server :0 successfully started
INFO @ src/http.cpp:280 -- HTTP server listening to <IP_ADDRESS>:8080
[0115/161016.529665:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
I have that error when starting the server. And I can't access the proxy (mysite:8080 refused to connect). Any ideas? Server is on ubuntu 20.04

Did you ever figure this out? I seem to be stuck on this as well. Cant connect on port 8080 and followed the installation twice with my SSH console just showing this and nothing else. Ol uncle google doesnt seem to be any help either. Using Arch Linux ARM armv7l on a Raspberry Pi 3 B+

Did you ever figure this out? I seem to be stuck on this as well. Cant connect on port 8080 and followed the installation twice with my SSH console just showing this and nothing else. Ol uncle google doesnt seem to be any help either. Using Arch Linux ARM armv7l on a Raspberry Pi 3 B+

i solved it running it with
release/bin/browservice --http-listen-addr=<IP_ADDRESS>:8080
I just forgot to read the instructions clearly, and that sandbox error doesnt seem to matter much but now im able to connect.

i solved it running it with
release/bin/browservice --http-listen-addr=<IP_ADDRESS>:8080
I just forgot to read the instructions clearly, and that sandbox error doesnt seem to matter much but now im able to connect.

Hmm, Odd I wonder why <IP_ADDRESS>:8080 works but not when I set it to a local IP to listen. Anyway, Seemed to fix it for me. Thanks :)

Hmm, Odd I wonder why <IP_ADDRESS>:8080 works but not when I set it to a local IP to listen. Anyway, Seemed to fix it for me. Thanks :)


[3256] - Update AllocationsController#index

Context
Currently the AllocationsController index action does not return information about an allocation's relationships (provider and training provider).
Changes proposed in this pull request

process 'includes' params in order to return provider and accrediting provider relationship info.

Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

 [L] 2d. Status labels on "Request PE courses for 2020/21" page


Updated the document to reflect the WAC changes

@shijojoy : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@shijojoy: I'm sorry - only the author of this article, @IngridAtMicrosoft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Hi @shijojoy - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. Would you make this content update in the private repo instead? Thank you! We'll close this PR.


500 error

Issue description:
We faced the 500 error on page when theme contains such code
Kirki::add_config( 'my_options', array(
		'capability'    => 'edit_theme_options',
		'option_type'   => 'theme_mod',
	) );

without it - everything works ok
Can you help us ?
Version used:
Latest wp.org
Using theme_mods or options?
theme_mod
Code to reproduce the issue (config + field(s))
Kirki::add_config( 'my_options', array(
		'capability'    => 'edit_theme_options',
		'option_type'   => 'theme_mod',
	) );

P.S. I can provide you ftp,admin access in private/email message to get involved in that issue deeper. (https://cshobby.com/)
We would be grateful for quick response because it is urgent. Hope for your understanding.

Simply adding the config should not throw a 500 error. Further debugging on your end is necessary to make any suggestions. You can try enabling debug mode as explained here to see if we get any additional infos - https://wp-pagebuilderframework.com/docs/debugging/


WIP/RFC - first jab at implementing Flow-style annotations-in-comments

See #9694 .
My workplace, and many community projects, are aware of the analysis capabilities of Typescript, but shy away from having a build step added to projects that are currently written in raw JS. This makes Typescript a non-starter. Facebook's Flow has a nifty feature whereby annotations can be added as comments inline in JS, meaning no build step is required. E.g.
const s /*: string */ = 'asdf';

function f(s /*: string */) /*: number */ {
    return 4;
}

/*::
interface MyObject {
    s: string;
    n: number;
}
*/
const o /*: MyObject */ = {s: 'asdf', n: 123}

This seems to have seen wide approval and support from the Flow community.
This PR implements this feature in Typescript. It's clearly uglier that direct annotations, but it's a much more succinct way of adding Typescript annotations to valid Javascript than JSDoc.
Two constructs are supported. /*: typename*/ is interpreted as : typename, as in the first two examples above. /* :: statements; ... */ is interpreted as statements; ....
It may also be worth considering /* <parameter> */ -> <parameter>  to allow manually specifying generic parameters where elision is not possible. This would also allow angle bracket type assertions. Note that this would be a convenience extension - as currently implemented, this is already possible with /* :: <parameter> */
This is a first go to see how easy this was to implement - I am aware that the CLA needs to be signed, test cases need to be written, that the issue needs to be tagged as needing a proposal (and that there is no guarantee this will happen!), and said proposal needs to be written and accepted, and that this is a language change and will thus be either highly contentious or rejected outright.

Hi @akdor1154, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

Two constructs are supported. /*: typename*/ is interpreted as : typename, as in the first two examples above. /* :: statements; ... */ is interpreted as statements; ....

I assume you mean /*:: statements; ... */ (no space between the asterisk and colons)

Sort of - parsing is tolerant of whitespace, matching /*:..., /* :..., /*  :..., etc.

Please see https://github.com/Microsoft/TypeScript/wiki/Type-Checking-JavaScript-Files for relevant information.

:( Though I really appreciate the thorough JSDoc support, I find Typescript's type expressions to be far more legible.
There are things that are far easier to express in Typescript's type system than in JSDoc (i.e. interfaces' interplay with discriminators and type-guards).  I hope the team revisits this one day.


Mongo support on Windows

All indications are that MongoDB support on Windows has been broken and not used for some time.  If this is mistaken, we would love to hear about your usecase.
Due to support overhead and the incurred development inertia, my preference for dealing with mongo on windows given current development resources is the following:

Disable mongo on windows, skipping the test suite, etc.
Document the lack of support on windows appropriately
Solicit end users who need mongo on windows to make their usecase known.

I propose disabling mongo support on windows for the full 0.4.1 release in odo and the next bugfix release of blaze.
@sandhujasmine I believe you have some familiarity with mongo and blaze: what's your experience here, specifically w.r.t. windows?

I don't have a use case for mongo/blaze on Windows.

Update: with the docker-based improvements, we can now spin up a mongo server once and test on mac, linux, and windows via VMs.  So we can test Mongo on windows, and there's no need to remove that backend.


Can it support reverse proxy such as nginx?

When I put the server behind nginx, and try to connect with h2.Connect(), it throws an error:
stream error: stream ID 3; PROTOCOL_ERROR

In the mean time, doing a normal GET over HTTP2 client works fine

Does it work for you if you directly connect to the server, and not through nginx?
Can you give more information? I can't tell too much from the two lines in the bug description.

It works well without nginx, it's an issue with nginx support I think

My code:
	// use h2conn for duplex tunnel
	ctx, cancel = context.WithCancel(context.Background())

	h2 := h2conn.Client{Client: HTTPClient}

	conn, resp, err = h2.Connect(ctx, url)
	if err != nil {
		log.Printf("Initiate conn: %s", err)
		return
	}

Additional info: nginx returns code 408:

A 408 Request Timeout response code indicates that the server did not receive a complete request from the client within a specific period of time tracked by the server (i.e. the timeout period).

Did you configure nginx to support http2?

Yes, http2 is enabled, and normal requests via HTTP2 work fine

Sorry, it will be very hard for me to debug this.
Please look at nginx logs, or use tcpdump/wireshark to debug the connection.
If you find anything there it will be very interesting, and see if we can work on a fix to the library.

@jm33-m0 Have you found out the solution? If not, can you post your nginx configuration and output of curl -I -L https://your_domain?

I encapsulated the HTTP2 connection in a proxy, didn't try to solve the nginx (or any kind of reverse proxy) support.


Add static analysis GitHub action

Add static analysis GitHub action.
Add golangci-lint action with extra linters besides the default set [1].
Add hadolint and shellcheck.
[1] https://golangci-lint.run/usage/linters
Part of issue #68

Good work, looks like it captures many "Errors".
@martinkennelly would you want to fix those "Errors" in this PR or a separate one?

Separate. I will start to work on them. I am hoping, we can add these basic actions to all our repos. In the last community meeting, we discussed trialing them in NRI first.
I am currently working on e2e test action as well with kind.

Separate. I will start to work on them. I am hoping, we can add these basic actions to all our repos. In the last community meeting, we discussed trialing them in NRI first.
I am currently working on e2e test action as well with kind.

@martinkennelly shall we merge this PR or wait until the errors be fixed.

Separate. I will start to work on them. I am hoping, we can add these basic actions to all our repos. In the last community meeting, we discussed trialing them in NRI first.
I am currently working on e2e test action as well with kind.

@martinkennelly shall we merge this PR or wait until the errors be fixed.

@zshi-redhat merge please. @emmakenny is working on this and will submit separate PR.

Forced pushed changes: Add golangci lint config file, created a make target, rebased to master and executed go mod tidy.


model to keep q>1 in stationary transport

This pull request implements Jardin's model for stationary sawteeth to raise q>1.
Example run
using Revise
using FUSE
ini, act = FUSE.case_parameters(:D3D)

# Initialize the `dd` structure with 0D parameters
dd = FUSE.init(ini, act);
dd_init = deepcopy(dd)
#act.ActorStationaryPlasma.convergence_error = 0.05#1e-8
act.ActorStationaryPlasma.max_iter = 5
FUSE.ActorStationaryPlasma(dd,act)

@bclyons12 Do you know if eta needs to be updated in the dd to get the correct flux consumption?

I do not. I'd just have to look at how and wear the flux consumption is calculated.
I'll look this over next week.

@jmcclena @bclyons12 looking more into this, what should happen to the non-inductive current inside of the inversion radius? I wonder if that non-inductive current get redistributed inside the inversion radius, perhaps using the same flatten() function that @jmcclena proposed?

I know that bootstrap current relaxes on the electron collision time, though I'm not sure what happens if there's large MHD that's redistributing particles anyway. Nor do I know how other noninductive sources should behave.


Update backend.yml

Purpose of the pull request
fix #10415

Codecov Report

Merging #10812 (1ea108c) into dev (71f0168) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #10812      +/-   ##
============================================
- Coverage     40.64%   40.62%   -0.02%
+ Complexity     4818     4817       -1
============================================
  Files           913      913
  Lines         36306    36304       -2
  Branches       3994     3990       -4
============================================
- Hits          14756    14750       -6
- Misses        20078    20081       +3
- Partials       1472     1473       +1

Impacted Files
Coverage Δ

...erver/master/processor/queue/TaskEventService.java
75.00% <0.00%> (-5.36%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
53.33% <0.00%> (-1.34%)
:arrow_down:

...pache/dolphinscheduler/common/utils/DateUtils.java
75.16% <0.00%> (-0.17%)
:arrow_down:

.../dolphinscheduler/plugin/task/datax/DataxTask.java
0.00% <0.00%> (ø)

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 71f0168...1ea108c. Read the comment docs.


Use "docker_apt_cache_valid_time" for installing python-dev & python-pip

In #75, I'd parameterized the apt-cache's valid-time for installing "docker-engine", but missed the parameterization of the apt-cache valid time for installing python-dev & python-pip. This change fixes that omission.
Adding this because it will allow the playbook runs to complete faster, without unnecessary "apt-get update"s.
Thanks!

Thanks!