Updated with Conda install instructions

Hi @ali-alsabbah, thanks for the pull request. This doesn't seem to include your new conda meta file. Can you commit that to your fork as well?
(working on #28)

Thanks for the update. Do you want to do more work on this? This is already a very useful start; the other things that I think are needed are:

Update the developer docs to explain what steps you did to build and publish a new version of the package to conda
Add post-link and pre-unlink scripts (see example of ipyleaflet) to automatically enable/disable the nbextension when installing -- this would be very helpful as it's a common thing that people miss when installing using pip
Add yourself to the list of contributors in the README (currently empty for this project, see example in floweaver)
Add a note to the changelog in the README that ipysankeywidget can now be installed using conda

If you can continue working on this that would be great, just let me know.

I think I've just finished 1, 3, and 4. I don't know how to do 2 at the moment, but I will look into it in the coming days.
As for anaconda package ownership, I couldn't transfer ownership to you, but there are a few option:

Let it be with the username -big_cake
I could delete the package and create a new Anaconda account and update it with my real name
I could send you the files and a bash script to upload them yourself using your own account, you would have to modify the script slightly depending on where you place your files.

Thanks. I think the third option would be best, as the process will have to be repeated by me or someone else whenever a new version is released.

Sounds good. Should I put the files on Github?
On Mon, Aug 6, 2018 at 12:09 AM Rick Lupton<EMAIL_ADDRESS>wrote:

Thanks. I think the third option would be best, as the process will have
to be repeated by me or someone else whenever a new version is released.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ricklupton/ipysankeywidget/pull/33#issuecomment-410609968,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ak56KJMbRGedZrh9bViHBZRiT83dyOYuks5uN-u6gaJpZM4VktpF
.

@ricklupton wondering if there's anything else that needs to be done here

Hi @ali-alsabbah, sorry for the slow reply. The key thing I'm missing is instructions and/or bash script of how to use your nice new meta.yaml file to build the package and upload it to anaconda! Is it just a matter of running conda build or similar?
Point 2 above (post-link and pre-unlink scripts) is nice to have but can always be added later if you don't have time to figure that out now.
Thanks

The instruction are here, how do you want me to include them?
https://conda.io/docs/user-guide/tutorials/build-pkgs-skeleton.html

I believe it should be ready now


Resolve locally first!

@majidaldo this PR would switch the default resolution order from starting with the remote URI (current behavior) to starting with the local file cache before defaulting to remote. It probably should have been this way from the beginning :) . Can you check to see if ontoenv==0.3.5a2 works alright for you? I've pushed the changes in this branch to that version for testing

(will get to it... Might be a few days. Thanks)


Announcement:  Highlighting the 'JetScan' 3D scanner build project for Jetson Nano

Hi everyone,
As highlighted by the RealSense Twitter account, JetScan is a fully documented build project that describes itself as: "smart and fast GPU 3D scanner with Jetson Nano and Intel depth sensor.
Metrically accurate RGBD 3D scanner and instant 3D reconstruction".
https://www.hackster.io/devshank/jetscan-16a521

Thanks @MartyG-RealSense for featuring my project
https://twitter.com/ShankarHaran3/status/1231456562927087617?s=20

you are very welcome!   It's great when RealSense community members document their projects thoroughly with guides, papers or long videos so that others can learn from it for their own projects.  Thanks!


Ubuntu server libEGL.so error: Failed to find EGL functions in library file!

For some reasons on my ubuntu server the file libEGL.so is found but it breaks:
`Command` Line: '"/home/dstefanidis/StarCraftII/Versions/Base60321/SC2_x64" -listen <IP_ADDRESS> -port 18970 -dataDir /home/dstefanidis/StarCraftII/ -tempDir /tmp/sc-5j8nxi0u/ -displayMode 0 -windowwidth 640 -windowheight 480 -windowx 50 -windowy 50 -eglpath libEGL.so'
Starting up...
Startup Phase 1 complete
I0712 17:39:27.498844<PHONE_NUMBER>18848 remote_controller.py:127] Connecting to: ws://<IP_ADDRESS>:18970/sc2api, attempt: 1, running: True
Startup Phase 2 complete
Attempting to initialize EGL from file libEGL.so ...
Failed to find EGL functions in library file!

So as an 'hack' I edited the pysc2//run_configs/platforms.py file to directly use the mesa library. Something like:
mesa = False
for mesa_lib in self.known_mesa:  # Look for a software renderer.
        if mesa_lib in libs:
          print('mesa used')
          extra_args += ["-osmesapath", mesa_lib]
          mesa = True
          break
if not mesa and "libEGL.so" in libs:
      extra_args += ["-eglpath", "libEGL.so"]
else:
     logging.info("No GL library found, so RGB rendering will be disabled. "
"For software rendering install libosmesa.")

Not sure if it can be a way to solve the problem properly though

+1, seems like it has no problem finding libEGL.so, but always fails to find find EGL functions in lib file.
Do you have an Nvidia card?

Hopefully this works better now?

I know is a little bit late, but I fixed my issue by correctly specifying the path to my libEGL NVIDIA libraries in LD_LIBRARY_PATH, and it worked much more faster than using libOSMesa.


get rid of most of storeDir - the troublemaker

storeDir is a huge troublemaker in a cluster environment: whenever some process fails downstream, for whatever reason,  some upstream processes can be copying intermediate results to storeDir location. After the restart or -resume processes take off with whatever is present in the storeDir - which isn't always a good thing, as results might be incomplete or whatever - it often creates a mess.

Jobs/processes could fail on a cluster for many reasons which we could not control and even using errorStrategy='retry' does not necessarily saves us in all cases.
storeDir intended use is to store things as a permanent cache, in most cases after downloading from some database (like SRA), but not to store all intermediate results there (according to Paolo)

from the times that I had trouble with StoreDir: https://github.com/nextflow-io/nextflow/issues/406

storeDir behavior have been fixed apparently:
https://github.com/nextflow-io/nextflow/issues/227
also review this to see if it's relevant: https://github.com/nextflow-io/nextflow/issues/592

just would llike to document some of the evidence of bad storeDir behavior:
from the recent distiller run, using sra_download process, which is using storeDir (the recommended way, actually):

so , seems like 1 sra_download failed and re-submitted - let's see, what was inside of the corresponding work folders:

actually both folders looks identical and just fine!
apparently something happened during the transfer ...

I don't think I follow what's the issue here. Could you please elaborate?
On Thu, 6 Dec 2018 at 18:38, Sergey Venev<EMAIL_ADDRESS>wrote:

just would llike to document some of the evidence of bad storeDir
behavior:
from the recent distiller run, using sra_download process, which is using
storeDir (the recommended way, actually):
[image: screenshot from 2018-12-06 18-32-46]
https://user-images.githubusercontent.com/6790270/49618227-c5d77b00-f985-11e8-8c91-216582bcf462.png
so , seems like 1 sra_download failed and re-submitted - let's see, what
was inside of the corresponding work folders:
[image: screenshot from 2018-12-06 18-37-51]
https://user-images.githubusercontent.com/6790270/49618303-14851500-f986-11e8-8377-db09ee49714d.png
actually both folders looks identical and just fine!
apparently something happened during the transfer ...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mirnylab/distiller-nf/issues/52#issuecomment-445070275,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3uChjFVk5sUFHcR5B9nd2iwk4nIy_7ks5u2aqMgaJpZM4OjMkB
.

my last post is not a new issue, is just an illustration for an ongoing "discussion" about storeDits vs publishDirs
it just illustrates, how exactly storeDirs fails to copy stuff over to intermediates, while the corresponding process itself finished fine and all of the files are intact inside of the corresponding work folder
I still don't understand why is it the transfer from work to intermediates that  fails quite often for us on the cluster

On the same topic , form the recent conversation with @mimakaev :

Also on the topic of this nextflow "bug" - what I meant by that is that copying to intermediates looks strange to me (screenshot attached) - why do they add this ||true thing at the end of the cp command ?! it seems to me like the success of copying to intermedaites does not affect anything ... - i'm not a bash expert don't know for sure.
You can check it in any of your distiller runs inside of work/hash-id/.command.run script at the bottom.

issue https://github.com/mirnylab/distiller-nf/issues/57 has been merged into this one

Yes, yes - nothing major , just a wasteful re-execution.
It almost seems contradictory, as the process finished, ok - files were generated in work, but then something triggered re-execution. Was it faulty transfers or something else?- don't know. It shouldn't have due to ||true at the end of the copy command ?!
I'm still struggling to understand the "||true" bash syntax
Regrardless, ErrorStrategy=retry is a huge helper in our execution environment

so, the || true bash syntax guarantees that the process does not return an
error (error code 0) even if the main process actually failed.
E.g. rm non-existent-file  would give you an error, but ( rm
non-existent-file ) || true gives you 0, the sae way false || true == true.
On Tue, 11 Dec 2018 at 23:30, Sergey Venev<EMAIL_ADDRESS>wrote:

Yes, yes - nothing major , just a wasteful re-execution.
It almost seems contradictory, as the process finished, ok - files were
generated in work, but then something triggered re-execution. Was it faulty
transfers or something else?- don't know. It shouldn't have due to ||true
at the end of the copy command ?!
I'm still struggling to understand the "||true" bash syntax
Regrardless, ErrorStrategy=retry is a huge helper in our execution
environment
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mirnylab/distiller-nf/issues/52#issuecomment-446458372,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3uCiYVUYaBxEPkrsqb9Bdura9h9ygmks5u4IZagaJpZM4OjMkB
.

so, finally ! ladies and gentelmen - a beautiful evidence that nextflow does not give an f about transfer-success to intermediates (just as @golobor explained about ||true)  - we knew about all of that mostly - but it would be nice to document it:

above: in a work folder we've got 2 beautiful fastq-s, left and right, for NPC library from Bonev2017 dataset, about ~8GB each
below: in intermediates corresponding files have sizes 2.5 and ~8GB respectively ...
corruption evidence or just faulty transfer evidence is here to stay.
to be fair it's nextflow version <IP_ADDRESS>86 , not the latest 18 -something (yes they went from 0. to 18. - because of the year or something like that)
@Phlya did you experience corruptions like that before/ever ?

I never compared output with work/, but could easily be that the problem I
had was due to this!
On Fri, 14 Dec 2018, 00:42 Sergey Venev<EMAIL_ADDRESS>wrote:

so, finally ! ladies and gentelmen - a beautiful evidence that nextflow
does not give an f about transfer-success to intermediates (just as
@golobor https://github.com/golobor explained about ||true) - we knew
about all of that mostly - but it would be nice to document it:
[image: screenshot from 2018-12-13 19-29-23]
https://user-images.githubusercontent.com/6790270/49975933-05661000-ff0e-11e8-8e20-1ec84acf9038.png
above: in a work folder we've got 2 beautiful fastq-s, left and right,
for NPC library from Bonev2017 dataset, about ~8GB each
below: in intermediates corresponding files have sizes 2.5 and ~8GB
respectively ...
corruption evidence or just faulty transfer evidence is here to stay.
to be fair it's nextflow version <IP_ADDRESS>86 , not the latest 18 -something
(yes they went from 0. to 18. - because of the year or something like
that)
@Phlya https://github.com/Phlya did you experience corruptions like
that before/ever ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mirnylab/distiller-nf/issues/52#issuecomment-447173262,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACwsutbFyTrnwBhR4xb2faRxZDBqhx1oks5u4vQSgaJpZM4OjMkB
.

Is there a nextflow ticket about that?

Don't remember seeing one. But we would need to have a reproducible example
to file a ticket :[
Anton.
(typed on a phone, sorry for brevity and typos)
On Sun, Dec 16, 2018, 12:33 Maksim Imakaev<EMAIL_ADDRESS>wrote:

Is there a nextflow ticket about that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mirnylab/distiller-nf/issues/52#issuecomment-447661220,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3uCpOg5FFtC55v5IGIp7DlVC56wtlQks5u5oPmgaJpZM4OjMkB
.

We don't need one to ask why the return status of file transfer is not being checked/interpreted.
However, the problem is still very cryptic for me. I don't understand what is leading to it: an error in cp/mv? or premature return from the process before cp/mv finishes?
@sergpolly  Do we have any way to see the command that was submitted to the cluster?  Is it docker, or a bash script? Do we explicitly see how copying was done?
Can we maybe replace cp/mv that is being "responsible" for the error the node with an alias that does some logging and pre/post md5 check?
@golobor  Who does the copying/transfer happen? Something inside docker?

@mimakaev

However, the problem is still very cryptic for me. I don't understand what is leading to it: an error in cp/mv? or premature return from the process before cp/mv finishes?

I'm not 100% sure about this one ... This "symptom" is present only (as far as I my experience goes) when storeDir directive is used to store intermediate results. Results that are "published" using publishDir are not used used for downstream processing, thus do not trigger any downstream errors, and I've never encountered "published" results that were corrupted or half-copied or anything like that. to be fair, such results are typically smaller - .pairs, .cool; as opposed to fastq-s stored by donwload_sra.
We cannot even agree with @Phlya that we are having the same exact issue ...
Maybe it's just our cluster NFS-nearlines ...
It has to be a "big" thing for the problem to occur - 2009-erez test went fine, without corruption or half-way copy; bonev-2017 - I've seen it 3 times - only for download_sra, where I still use storeDir (the only place for me - I've been testing with the "old" distiller still, I'm planning to launch "merge_parse_map"-one, once the old is one is done)
Now to the difference between storeDri and publishDir and to

@sergpolly Do we have any way to see the command that was submitted to the cluster? Is it docker, or a bash script? Do we explicitly see how copying was done?

each process of nextflow script/pipeline is being executed in an "isolated" environment - i.e. a directory inside of ./work, work/short-hash/longer-hash. Each one of these directories correspond to 1 instance of a process, i.e. mapping of 1 chunk  -> one work/hash/long-hash folder .
Inside of each one of them there are staged input files, output files and a bunch of hidden files (including bash scripts, logs, stdout, exitcode, trace etc.) that control execution and "document" it.
To those bash scripts - there are 3 of them: .command.run, .command.stud and .command.sh - they are nested in this exact order, i.e.

.command.sh - is the innermost one and it's an actual command that user/pipeline creator wants to be executed - like this bwa-command in triple quotes: https://github.com/mirnylab/distiller-nf/blob/ab5044f6a6bc1478041f4d7f5f355e0321f39279/distiller.nf#L370
.command.stud one is a little wrapper over .command.sh, that from my understanding, simply tracks resource usage
finally, .command.run is the outermost one - master scripts that wraps .command.stud, here things get executor dependent, i.e. there would be a difference between .command.run between local and cluster execution. Ina case of a cluster .command.run contains a typical header with resource requests (long queue, 15 hours, 8 cores on 1 host, 8gb per core, etc ):

i dont' have examples of a local .command.run - but you guys should have some for sure - it should be simplier a bit I'd guess.
Then .command.run contains some staging commands (lots of bash-magic, as @golobor calls it, I do not fully understand it - just some concepts, not details) , creating symlinks for input data etc, and finally finally finally - it calls that freaking .command.stud-thing - that's where we have our docker/singularity or nothing situation (.command.stud called inside of local singularity container in the next screenshot):

so .command.run runs "natively", outside of docker/singularity , while .command.stud, that calls .command.sh run inside of the container (if specified).
Now to:

Do we explicitly see how copying was done?

that depends on the situation - i.e. I can name at least 3 scenarios:

if we use storeDir - cp-ing to intermediates happens in the "native" .command.run right after the .command.stud call , and only if that call was successful (as far as my knowledge of bash magic can tell me), screenshot: one in this comment https://github.com/mirnylab/distiller-nf/issues/52#issuecomment-445413620
https://user-images.githubusercontent.com/6790270/49679346-99406380-fa58-11e8-89df-c8c9b8efce61.png
if no storeDir/publishDir used than , no copying is done - resutls stay right in work/hash/lognhash location and are used as input for downstream processing directly (downstream process uses soft-links to the upstream)
if publishDir is used then ... there is NO copying command visible in either of the 3 .command./run/stud/sh - maybe it's done by the master Java process - please see orange Warning at the end of this paragraph: https://www.nextflow.io/docs/latest/process.html#publishdir
For example see a screenshot of the work/hash/hash/.command.run for an instance of filter_make_pairs which relies on publishDirs to copy stuff to output/resutls:

More nextflow stuff for reference/whatever:

in that example "skipped" processes are those started off of the intermediates i.e., stuff that was storeDir-ed
"cached" are those resumed from successfuly completed processes in work/hash/longhash, here that [xx/yyyyy] thing to the left is the hash/longhash part of the path to that process execution environment:
cd work/xx/yyyy-> [TAB] -> cd work/xx/yyyyyyyyyyyyyyyyyyyyyyyyy  should work.
On a positive note, here is an example of why I personally love nextflow:

140 is an LSF(our cluster's batch system) error code for the time out - i.e. if I asked 3 hours for a task, than it's going to be killed after 3 hours+/- 5 sec of execution - nextflow can resubmit that job dynamically asking for more resources/time ...

Another piece of evidence to the issue: https://github.com/mirnylab/distiller-nf/issues/52#issuecomment-447173262
That download_sra job took almost 4 hours , actually - exactly 4 hours - and it was killed by the scheduler ... but apprently the .exitcode was already there , and it was 0 - success - so nextflow proceeded with the incomplete transfer to intermediates ...
I thinks it's enough evidence and understanding to open up a nextflow issue .
What do you guys think ?

I think this is sufficient evidence, and the proposed mechanism is very clear. I think it  should be submitted as a major issue. We can try to replicate it by creating one job that copies a large file.

I've reproduced it with two simple processes and manual killing

Use example.nf file below
Run "cat /dev/urandom > testfile" for a minute or a bit more (so you have enough time to kill copy later)
Run nextflow  (nextflow example.nf  --in testfile)
Run htop. Observe cp input.fa output_test. It will change to "cp -fRL output_test ...". At that point be quick and kill it
First process finishes successfully, and second process "copyAgain" starts copying a truncated copy.  And output file is a truncated copy of testfile.

#!/usr/bin/env nextflow

params.in = "$HOME/sample.fa"

sequences = file(params.in)

process copyFile {
    storeDir 'teststore'

    input:
    file 'input.fa' from sequences

    output:
    file 'output_*' into records

    """
    cp input.fa output_test
    """

}

process copyAgain {

    input:
    file x from records

    output:
    file '*.out'

    """
    cat $x  > file.out
    """
}


where is fusion.since?

readme says:

Fusion uses a .since annotation

but I don't see since being defined nor used at all.
I propose we reuse stdilib's private since instead of duplicating its implementation, a lesser evil in this case:
import std/private/since

Because they are all new modules so no need for since ?. :confused:


Add PUSH0 opcode

The PUSH0 opcode will be used by default in the latest version of huff.

I will finish this in the next few days, please don't close this PR, thank you.  @karmacoma-eth

thanks @wangshouh, do you mind adding a test for it too?


Title attribute on select tag not honored

It seems like the plugin is ignoring the 'title' attribute in the select tag and instead setting the title to the value of the currently selected option. Having the title tooltip set to the currently selected option is not very useful since the user can already see the value that's currently selected. It would be better to honor the title attribute in the select tag if it exists.

I just came here to open a ticket about this. This is needed. It also forces more complicated error checking since the first option is being selected, instead of none.

A workaround is to add the first option as:
            <option data-hidden="true">Select an option ...</option>

See #639

Well, yes, but the docs are wrong: http://silviomoreto.github.io/bootstrap-select/#titleMultiples ... the "title" attribute does nothing

See 0351bd8960f02a7e2cd775fab1308ffa00b4f085.

Neither the linked PR nor the linked commit seem to address the original issue. The title attribute is not being copied over.
If I have a select tag:
<select title="Some title">...</select>

I'd expect (based on this comment in the source) the generated button to be:
<button title="Some title" data-toggle="dropdown" ...>

But it does not seem to work.

I've not been keeping track of the main branch because I had already fixed this issue (along with some other enhancements) in my fork way back. You can see a demo of the new title attribute behavior here (under Single Select):
http://thdoan.github.io/bootstrap-select/examples.html

I think we need to add support for a separate placeholder attribute.

The placeholder option was added in https://github.com/snapappointments/bootstrap-select/releases/tag/v1.14.0-beta and existing title functionality has been deprecated.


looking for php-mysql smarty container

will build one and share it back if I don't see it.

came here when 'smartypants' broke

not really sure what the issue is, as there is no details of errors/issues. Closing until further details are provided


Datasets method .map not hashing

Describe the bug
Datasets method .map not hashing, even with an empty no-op function
Steps to reproduce the bug
from datasets import load_dataset

# download 9MB dummy dataset
ds = load_dataset("hf-internal-testing/librispeech_asr_dummy", "clean")

def prepare_dataset(batch):
     return(batch)

ds = ds.map(
    prepare_dataset,
    num_proc=1,
    desc="preprocess train dataset",
)

Expected results
Hashed and cached dataset preprocessing
Actual results
Does not hash properly:
Parameter 'function'=<function prepare_dataset at 0x7fccb68e9280> of the transform datasets.arrow_dataset.Dataset._map_single couldn't be hashed properly, a random hash was used instead. Make sure your transforms and parameters are serializable with pickle or dill for the dataset fingerprinting and caching to work. If you reuse this transform, the caching mechanism will consider it to be different from the previous calls and recompute everything. This warning is only showed once. Subsequent hashing failures won't be showed.

Environment info

datasets version: 2.3.3.dev0
Platform: Linux-5.11.0-1028-gcp-x86_64-with-glibc2.31
Python version: 3.9.12
PyArrow version: 8.0.0
Pandas version: 1.4.2

cc @lhoestq

Fix posted: https://github.com/huggingface/datasets/issues/4506#issuecomment-1157417219

Didn't realize it's a bug when I asked the question yesterday! Free free to post an answer if you are sure the cause has been addressed.
https://stackoverflow.com/questions/72664827/can-pickle-dill-foo-but-not-lambda-x-foox

Thank @nalzok . That works for me


However linaro is also a popular 32/64-bit arm-linux platform, an aarch64 package in future go releases might be useful.
http://www.linaro.org/

Do we really need to do this? The only reason we package linux/arm (32bit)
is it takes hours to compile natively. Most arm64 systems can knock this
over in 10 minutes. Also, is this a problem that linaro, as a distro
maintainer, should handle?
On Tue, Feb 14, 2017 at 6:08 PM, Ben Shi<EMAIL_ADDRESS>wrote:

Current go 1.8 only contain an armv7l-linux package.
However linaro is also a popular 32/64-bit arm-linux platform, an aarch64
package in future go releases might be useful.
http://www.linaro.com/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/19082, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAcA-u2Mi8WKGEA2ngCGRy7JX-Zx6Vcks5rcVLXgaJpZM4MAIjx
.

An generic aarch64-Linux go pre-built package might not benefit a go develop, but it might benefit a go user.
Ben Shi

在 2017年2月14日，15:36，Dave Cheney<EMAIL_ADDRESS>写道：
Do we really need to do this? The only reason we package linux/arm (32bit)
is it takes hours to compile natively. Most arm64 systems can knock this
over in 10 minutes. Also, is this a problem that linaro, as a distro
maintainer, should handle?
On Tue, Feb 14, 2017 at 6:08 PM, Ben Shi<EMAIL_ADDRESS>wrote:

Current go 1.8 only contain an armv7l-linux package.
However linaro is also a popular 32/64-bit arm-linux platform, an aarch64
package in future go releases might be useful.
http://www.linaro.com/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/19082, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAcA-u2Mi8WKGEA2ngCGRy7JX-Zx6Vcks5rcVLXgaJpZM4MAIjx
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

An officially supported 64-bit ARM version of Go would help a whole bunch of downstream projects that depend on Go, including especially Docker, and then anyone building multi-architecture projects that depend on Go in Docker containers. As it stands now the container process would have to bootstrap Go from source which adds complexity at the minimum and bloat.
There's a whole set of tooling and packaging for other platforms that depends on plopping in a supported binary as part of an automated build system.

To give you an idea of some of the hoops people are going through to bootstrap Go right now, I give you https://github.com/hypriot/golang-armbuilds - this should all be unnecessary when there's an official build.

agreed, Go is a popular multi-arch capable supporting tool for many projects.  Including a binary would be very convenient and also support more testing and CI that should be using an official build.

The linux/arm64 can be attributed to "Other Ports". Something like
go1.9.linux-arm64.tar.gz
There are
go1.8.1.linux-ppc64le.tar.gz 	Archive 	Linux 	ppc64le 	73MB 	b7b47572a2676449716865a66901090c057f6f1d8dfb1e19528fcd0372e5ce74
go1.8.1.linux-s390x.tar.gz 	Archive 	Linux 	s390x 	72MB 	0a59f4034a27fc51431989da520fd244d5261f364888134cab737e5bc2158cb2
in "Other Ports"

Having official google builds of golang for arm64 would be fantastically useful for users that just want to simply compile stuff on arm64 without having to do the golang bootstrap procedure.

Per https://golang.org/wiki/NoMeToo, please vote with the emoji thumbs up at the top.

As a datapoint against the target system build times, there are official binary releases for s390x and ppc64le, both of which are mainframe platforms and thus usually can also build Go fairly fast (but having official binary releases is still really useful).

Just FYI, you can use gimme: https://github.com/travis-ci/gimme.  It will build from source if it can't find a binary release.

An official build of Golang for ARMv8 will save a lot of hassle for Docker images and build pipelines. Automation is everything and this lack of support makes working with 64-bit ARM harder.

@davecheney just as a point of clarification, Linaro isn't a Linux distribution.  Rather the organization simply works on upstreaming open source arm software eg kernel, etc.
However, I think that Linaro and others in the arm ecosystem (eg huawei, cavium, Qualcomm, etc) would be willing to help maintain a native aarch64 build of GoLang.
Packet and ARM are already donating CI infrastructure for both 32 and 64 bit arm builds.  I suspect Scaleway would  also be supportive.
In the end, Packet and scale way each have thousands of customers using our armv8 infrastructures.  A large percentage of these users have expressed a desire to have a pre built official binary.  The main use case seems to be for using golang dependent software, eg Docker, k8s, cockroach etc

@davecheney We need at least one arm64 go binary release to use as the bootstrap compiler to build other go versions.  As of now, we cannot build any version of go on an arm64 machine since arm64 support was added in go1.5, and go1.5 needs a go bootstrap compiler to build itself.

Can you build the bootstrap compiler on a other machine?
On Tue, 9 May 2017, 09:54 Geoff Levand<EMAIL_ADDRESS>wrote:

@davecheney https://github.com/davecheney We need at least one arm64 go
binary release to use as the bootstrap compiler to build other go versions.
As of now, we cannot build any version of go on an arm64 machine since
arm64 support was added in go1.5, and go1.5 needs a go bootstrap compiler
to build itself.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/19082#issuecomment-300022637, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcA6H5flPwjUUeZNncSEzFvplxJTbKks5r36shgaJpZM4MAIjx
.

@davecheney when you build the bootstrap compiler on another machine (according to your directions) you get this project by @hypriot and Dieter Reuter. https://github.com/hypriot/golang-armbuilds

@davecheney I don't think it reasonable to require a user on an arm64 machine to require another machine to simply build a bootstrap program.

Is there any resistance to the proposal or was this just for reference? I think this would benefit the community - well beyond the scope of Linaro.

@alexellis, yeah, this is mostly a tracking bug. We're almost certainly going to do this, especially now that we have an "Other Ports" section on the download page, and we already have relatively infrequently used ports like s390x there.

To track this, go 1.9 beta 1 is available now, and there is no ARM64 binary for it published yet.

@broady, I'm running using pending CL 45913:
$ release -rev=952ecbe0a27aadd184ca3e2c342beb464d6b1653 -skip_tests -target=linux-arm64 -tools=6d30ceaab7ab5caffba4974a61e36d34268756ec -version=go1.9beta1 -watch
2017/06/15 19:45:42 linux-arm64: Start.
2017/06/15 19:45:42 linux-arm64: Creating buildlet.
2017/06/15 19:45:43 linux-arm64: Pushing source to buildlet.
....

Okay, it's uploaded now:
https://golang.org/dl/#unstable
The "Arch" column says "arm64" now. Maybe it should say something else. It looks out of place formatting-wise. ARMv8? ARMv8-A? AArch64? ARM has the most lovely names. ARMv8 matches the existing ARMv6 look-wise.
In any case, please test out the binary and report any problems.
If we don't hear happy reports, we won't ship it for the final release.

@bradfitz My vote would be for arm64, and probably rename ARMv6 to arm32. Since there are a few 64-bit architecture now, perhaps amd64 and i386 instead of 64/32-bit.

There are varying opinions on naming for ARM - ARM themselves communicating with the Docker/Moby project asked for -

arm32v6
arm32v7
arm64v8

etc. This has been reflected in the Docker manifest definitions and the prefixes for the naming of ARM-based container images.
aarch64 / arm64 / armv8 amongst others are the most popular I've seen elsewhere.

We'll go with ARMv8 if anything. We're not repainting the rest of the house.

@nathangoulding, for anybody actually confused what "64-bit" or "32-bit" means, they can read the filename substring that says "amd64" or "386".

@bradfitz More so for accuracy/consistency, especially as golang makes its way into predominantly ARM ecosystems. Fair enough though, and ARMv8 is a fine choice.

I suggest aarch64. ARMv8 implies arm32 instruction set ver 8, and aarch64 implies the 64 bit mode instruction set, as a convention.
Please refer to linaro tool chain's naming.
https://www.linaro.org/downloads/

If we don't hear happy reports, we won't ship it for the final release.

Happy to report that it's working pretty well here! :innocent: :+1: :grinning:
(It successfully builds binaries as expected, and the resulting binaries run properly. :heart:)
Thanks for your work on this! :100:

On a related note, I see there are FreeBSD go binaries for 32- and 64-bit x86, but not for 32- or 64-bit arm.

No, because we don't have a freebsd/arm64 port.

Ok, so first I'll open an issue for the FreeBSD/arm64 port - it will be useful to at least track requirements for bootstrapping.

I take it that's a "yes", if so, thanks.

If we don't hear happy reports, we won't ship it for the final release.

My colleague, @naveena2016, shared test results with me. She used the AArch64 1.9 beta2 binary. Her effort included four different workloads that completed without issue. Performance could be characterized as 'similar to 1.8'.
Thanks for preparing this release!

I've run some experiments to check out the behavior of the AArch64 1.9b2 binary, looking at the performance of the workloads in the Computer Language Benchmarks Game. All the benchmarks worked as expected. Here's a figure showing speedup of 1.9b2 over 1.6 for each of the benchmarks:

Thanks!

Nice @eagner - out of interest which machine did you run these on?

It was run on an A57 platform restricted to using a single core.


Argon.js fails with Webpack

I gather this is usually caused by calling require with a variable instead of a string:
WARNING in<EMAIL_ADDRESS>1:3743-3750 Critical dependency: require function is used in a way in
which dependencies cannot be statically extracted

WARNING in<EMAIL_ADDRESS>1:3789-3796 Critical dependency: require function is used in a way in
which dependencies cannot be statically extracted

Hi, thanks for reporting this issue! I believe this is fixed in the develop branch. Can you try installing @argonjs/argon@next ?

I tried installing @next as you suggest (it gave me version "^1.2.0-1") and I still get the problem.
On further inspection, it seems to be caused by this:
D="undefined"!=typeof System&&System._nodeRequire||"undefined"!=typeof require&&require.resolve&&"undefined"!=typeof process&&require

And if I just change that to D=true then it's happy.  I'm not sure where that logic is coming from to attempt to inspect the runtime environment for a require function.

@ammulder Any chance you have tried webpack@2 ?

The checks for a require function are intentional, as argon.js is a built as a UMD library, which means it can be loaded via commonjs, AMD, or ES6 module loaders. I believe the problem you are running into is due to bug in webpack@1, which was fixed in webpack@2 (see https://github.com/webpack/webpack/issues/2675).

According to node_modules/webpack/package.json I'm already on Webpack 2.2.0
I don't think Webpack has solved the general issue, which appears to be that whenever it sees "require" it tries to analyze what you're "requiring" so it can handle that.  But in the argon.js usage that's causing the problem, you're only checking whether the require function exists, not actually "requiring" anything.  I guess Webpack doesn't figure that out?

So good news / bad news: I found that the latest version of jspm@next fixes this issue in creating a build that Webpack can understand, but unfortunately I can't update jspm yet because I'm held back by another bug in jspm@next. Technically, however, this issue seems to be a problem in Webpack. Perhaps you can open an issue with them?

Waiting on https://github.com/frankwallis/plugin-typescript/issues/204 to be resolved then I can "fix" this


Update tailwindcss-font-inter and remove deprecated option

The disableUnusedFeatures flag is not necessary as of Tailwind 2.

Wait as soon as I made this I realized, repo would need update to tailwind 2. I'll open a new one if I make the rest of the changes

Double-oops, it is on Tailwind 2 😄  (just saw https://github.com/michelegera/tailwindcss-open-template/pull/4 - I misread the package.json before

Hello @hangtwenty and thank you so much for taking the time to open this PR!
I was a little confused at first too, but then I realized that the deprecated option you removed is on tailwindcss-font-inter configuration, and that package is still at v1.0.8 (while tailwindcss itself, as you noticed, has been already upgraded to v2).
Would you mind bumping tailwindcss-font-inter to v2 in this branch? A simple yarn add --dev tailwindcss-font-inter should suffice. You can either amend this commit or add a new one, I will squash them before merging!
Thank you!

@hangtwenty got time to address my request above? If not, no worries, I will gladly do it! 🙂

Closed via 85294850e6ba4dd78de3e07e95653ef35ea2a3c7.


Increase cloud project quota

If we are to speed up package analysis and dartdoc generation by having more machines, we will run out of quota. We should request more cloud quota so we can have a higher peak usage, while still using the same amount of CPU hours in total.

We can delay this to M10 if we're not investing in speeding up dartdoc/analysis.

I requested a quote increase, doubling the amount of resources we have...
We can easily ask for more if we need it, turn around was pretty quick.

Thanks Jonas, yeah it's pretty quick at least for projects this size


Error with template rendering into shell_command component

Home Assistant release 0.27.1
Python release 3.4.2
Component/platform:
shell_command component
Description of problem:
When I use template rendering into a shell_command component, I am getting an error and shell_command isn't executed.
Command is:
take_snapshot:
'/home/hass/.homeassistant/myShellScripts/take_snapshot.sh "{{now.now().strftime("%Y%m%d-%H%M%S")}}"'
I tried removing the template and replace it by a hardcoded timestamp and the it's working fine. /home/hass/.homeassistant/myShellScripts/take_snapshot.sh "20160902-212800"'
Expected:
Timestamp generated by template passed to the shell script.
Problem-relevant configuration.yaml entries and steps to reproduce:
configuration.yaml
shell_command:
  take_snapshot: '/home/hass/.homeassistant/myShellScripts/take_snapshot.sh "{{now.now().strftime("%Y%m%d-%H%M%S")}}"'

Traceback (if applicable):
16-09-02 21:49:28 homeassistant.core: BusHandler:Exception doing job
Traceback (most recent call last):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/core.py", line 852, in job_handler
    func(*args)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/core.py", line 717, in _execute_service
    service(call)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/core.py", line 572, in __call__
    self.func(call)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/shell_command.py", line 41, in service_handler
    stderr=subprocess.DEVNULL)
  File "/usr/lib/python3.4/subprocess.py", line 537, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.4/subprocess.py", line 859, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.4/subprocess.py", line 1457, in _execute_child
    raise child_exception_type(errno_num, err_msg)
OSError: [Errno 8] Exec format error

Additional info:

Is this support to work? Why don't you add the timestamp on the take_snapshot.sh directly?
# date +%Y%m%d-%H%M%S
20160908-002814

Probably get it to work you would need to import the datetime and them call the Python function.

According to https://home-assistant.io/components/shell_command/ , templates should be supported but apparently not all kind of templates.
I need to define the timestamp into a template because I want to use the same timestamp in different scripts.
Perhaps, I can explain what I want to do and you can suggest an other solution.
Goal:
When someone rings on my door, I want a camera snapshot sent to my slack.
My Approach:

Take a snapshot from my IP cam and save it with a given timestamp
(fe.: my_snapshot_timestamp.jpg).
Upload this snapshot to dropbox.
Send a message with this snapshot as attachment to my slack.

I have the same issue:
if I run this:
'echo "{{states.sensor.hallway_thermostat_humidity.state}}" > test.txt'
nothing happens, yet if I run this:
'echo "states.sensor.hallway_thermostat_humidity.state" > test.txt'
I get "states.sensor.hallway_thermostat_humidity.state" in the text.txt file (I get the string, not it's value)


Doing something wrong? Arugment #2 not an array?

I created to Modules "A" and "B"
I attempted to use the following command:
php artisan module:use A
Error: array_merge(): Argument #2 is not an Array
php artisan module:list
Error: array_merge(): Argument #2 is not an Array
How does this work?

NEVERMIND! Looks like something may have gotten "touched" and messed everything up

I lied... Ok, so to replicate this issue...
I deleted the module I was trying to "Module:Use" and I was able to re-create new modules and that module again..
when I attemped to do module:use "B" it "broke" Module B... and I couldn't do any module commands after that while "B" was still an active and included Module. Once, I deleted Module B then it was fixed and I could recreate Module B, until I attempted to module:use it once again...

module:list doesn't work either

Resolved!
Apparently I had a previous config in my /config/ that was named the same as a new module I was testing... because I wanted to move the information to the module...
the config was causing issues.

Hi,
I'm not able to reproduce this. I can:

use module:use blog
run module:make-controller MyController
use module:use recipe
run module:make-controller MyController

Both controllers are generated.

Thanks, I have closed it. Apparently it was a busted config I had loaded in my app/config that matched the name of a module I was going to use... :D

Ah ok glad to see you fixed it. 😄


feature: split commit and publish/push phase

This is a feature request to split the release action in two phases: a "commit" and a "publish" one. I'm going to detail my usecase below. I'm willing to start drafting the code for this myself, but I need some guidance on the design/UI points.
In other collaborative projects I've been involved, the process for a release is:

a release manager checks that all milestoned bugs/epics/etc are done
they open a dedicated branch for the release
they run a script s1 to assemble the changelog and finalize it with editorial changes
they run a script s2 which performs two commits:

a first one which bumps all version/references/etc to the actual release
a second one which goes back to the development cycle (e.g. -pre)

this branch is submitted as a normal PR to be reviewed for typos and possible scripted mistakes
after final approval, it is merged into master
another script s3 performs the final steps:

checks out the real release commit (HEAD^), adds a tag, build all artifacts
push the tag to master and publish artifacts in all relevant places

While I don't want to automate all this complex and opinionated process via cargo-release, I would like to able to handle twe two main steps in there (creating the commits and pushing) in two separate phases. @sunng87 do you think it is meaningful to have here? How do you think the CLI should look like?

Hi @lucab , currently you can use cargo release as your s3 script and s1 and s2 can be done as your custom process. When cargo-release detects the current version has no dev extension, it will use the version as release version. So I think it works as s3 in your process.
From my perspective, I want to keep this tool simple to understand. It may not cover all use cases and processes.


[Debugging new models] Any idea of how to expose device void calculate_model() in order to check model implementation?

I just want to test a new model but despite note having compilation issue, it doesn't fit my data.
I thought of testing my code giving my kernel a set of parameter and checking the shape of the simulated curve but I am having more troubles than expected.
Down here what I tried to do, but it is not working at all ...

created a new method in lm_fit_cuda.cpp as:

void LMFitCUDA::simul()
{
    // initialize the chi-square values
    calc_curve_values();
}

and then in lm_fit.cpp a new method of LMfit class:

void LMFit::simul(float const tolerance)
{
    set_parameters_to_fit_indices();

    GPUData gpu_data(info_);
    gpu_data.init_user_info(user_info_);

    // loop over data chunks
    while (n_fits_left_ > 0)
    {
        chunk_size_ = int((std::min)(n_fits_left_, info_.max_chunk_size_));
        info_.set_fits_per_block(chunk_size_);

        gpu_data.init(
            chunk_size_,
            ichunk_,
            data_,
            weights_,
            initial_parameters_,
            parameters_to_fit_indices_);

        LMFitCUDA lmfit_cuda(
            tolerance,
            info_,
            gpu_data,
            chunk_size_);
        lmfit_cuda.simul();
        get_results(gpu_data, chunk_size_);
        n_fits_left_ -= chunk_size_;
        ichunk_++;
    }
}

A new method for class FitInterface:

void FitInterface::simulate(ModelID const model_id)
{
    int n_dimensions = 0;
    configure_model(model_id, n_parameters_, n_dimensions);

    check_sizes();

    Info info;
    configure_info(info, model_id);

    LMFit modelsim
    (
        data_,
        weights_,
        info,
        initial_parameters_,
        parameters_to_fit_,
        user_info_,
        output_parameters_,
        output_states_,
        output_chi_squares_,
        output_n_iterations_
    ) ;
    modelsim.simul(tolerance_);
}

And eventually a new function in gpufit.cpp

int gpusimul
(
    size_t n_fits,
    size_t n_points,
    float * data,
    float * weights,
    ModelID model_id,
    float * initial_parameters,
    float tolerance,
    int max_n_iterations,
    int * parameters_to_fit,
    EstimatorID estimator_id,
    size_t user_info_size,
    char * user_info,
    float * output_parameters,
    int * output_states,
    float * output_chi_squares,
    int * output_n_iterations
)
try
{
    __int32 n_points_32 = 0;
    if (n_points <= (unsigned int)(std::numeric_limits<__int32>::max()))
    {
        n_points_32 = __int32(n_points);
    }
    else
    {
        throw std::runtime_error("maximum number of data points per fit exceeded");
    }

    FitInterface fi(
        data,
        weights,
        n_fits,
        n_points_32,
        tolerance,
        max_n_iterations,
        estimator_id,
        initial_parameters,
        parameters_to_fit,
        user_info,
        user_info_size,
        output_parameters,
        output_states,
        output_chi_squares,
        output_n_iterations);

    fi.simulate(model_id);

    return ReturnState::OK  ;
}

void LMFitCUDA::simul()
void LMFit::simul(float const tolerance) same function name in different class?
By the way, still confused about what your new model is like.

For debugging purposes, it may be useful to implement the model within Cpufit, first.  Then, you can use a standard debugger without having to run the code on the GPU.

@Gittry
They are meant just to debug, and not as a general interface.
The same naming in different classes should cause interference, as far as I know.
If you want to know more about the model, give a look at my GitHub.
my own tool
my fork of Gpufit - not working yet
@superchromix
That was a good hint. I will give it a try.
By the way, I think that having one additional output to LMFit::LMFit with the values of the fitted curve can be useful to avoid computing again the model from the estimated parameters. In my current fork, I added an additional input float * output_data to LMFit class initialization, that I use to read the value of gpu_data_.values_ and that seems to be doing the trick, so far.
I agree that maybe an additional gpusimul() function could be overkilling ...

I agree that maybe an additional gpusimul() function could be overkilling ...

My impression is that it would not be overkill. Cpufit is the simulation of Gpufit in a manner of speaking.
What we ideally would like to have is to write down the model once and then use it once on the CPU (for debugging purposes) and once on the GPU without duplicating the code. So far we did not manage to do that and we are duplicating code in the CPU and GPU library versions with all the drawbacks but in a future version this might well be the case.

Also, just being able to compute the model or the gradients at the current parameters sounds like an obvious enhancement to me. Often enough you not only need the final fit parameters but also the model values at these parameters. Would need to extend the interface for that. We should keep this in mind.

I think that having one additional output to LMFit::LMFit with the values of the fitted curve can be useful to avoid computing again the model from the estimated parameters.

This would involve copying a large amount of data from the GPU to the CPU, resulting in slower performance.  This could possibly be an optional output.

This would involve copying a large amount of data from the GPU to the CPU, resulting in slower performance. This could possibly be an optional output.

@superchromix
Yes, this is true, indeed.
But for what I need, having the fitting output as a (matrix of) time series is necessary. So far, I just added one additional output, that is used just at the very end of the fitting (so just one transfer GPU-CPU) ... mainly because I don't know how to make it optional, yet! xD

mainly because I don't know how to make it optional, yet!

So far, the C interface of Gpufit is stateless, so either one would need to add another input flag (controlling outputs) or set this with another function and then Gpufit would need to remember its state.


How to build a dynamic_opentracing plugin for Envoy

Description:
In issue #4140 it is mentioned that a "A specific build process is required for the dynamic loading [of opentracing plugins] to work.". Is there any documentation of this build process? Are independent vendors even supposed to provide binary opentracing plugins for envoy? Background: I want to build such a plugin, and am thinking about what the best way to package or deploy it would be.
Relevant Links:
PR #2252
Issue #4140

@rnburn would be great to get some docs on this or if there are docs better links?

Envoy statically links in the standard C++ library by default. The specific build process is referring to the additional steps that need to be taken to work with a statically linked standard library. (See this SO post for background).
Basically what you need to do is to use a version script when linking to keep symbols from being exported. You can look at Jaeger's build-plugin.sh script to see an example of how to set it up.


[Feature] Add/update type information for source files

Q
A

Documentation
no

Bugfix
yes

BC Break
no

New Feature
no

RFC
no

QA
no

Description
This PR adds/updates type information for source files to fix static analysis errors in dependent libraries. Types has been added to properties and phpDocs only to keep existing method signatures. So nothing should change at all.

Hey, @Ocramius, could you please check this PR again?
My next PR with changes for probable next major version #69  will depend on this PR, so want to be sure that everything is ok with current PR.

Overall, the change in protected properties could be considered a BC break, but since the parent class depends on the type being respected, I'm OK with saying that subtypes have to respect it.

Thanks @lisachenko!


SWA does not work with BatchNormalization

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
TensorFlow version and how it was installed (source or binary): pip3 install tf-nightly (2.1.0.dev20191227)
TensorFlow-Addons version and how it was installed (source or binary): pip3 install tfa-nightly (0.7.0.dev20191219)
Python version: 3.7.6
Is GPU used? (yes/no): no

Describe the bug
KeyError: 'sequential/batch_normalization/moving_mean_71' is raised when invoking the assign_average_vars in a model with BatchNormalization layers
Code to reproduce the issue
import tensorflow as tf
from tensorflow_addons.optimizers.stochastic_weight_averaging import SWA

# DATA
train_data, test_data = tf.keras.datasets.boston_housing.load_data()
train_ds = tf.data.Dataset.from_tensor_slices(train_data).shuffle(404).batch(32)
test_ds = tf.data.Dataset.from_tensor_slices(test_data).batch(32)

# MODEL
model = tf.keras.Sequential()
model.add(tf.keras.layers.Dense(64, activation='relu', use_bias=True))
model.add(tf.keras.layers.BatchNormalization())
model.add(tf.keras.layers.Dense(1))

# OPTIMIZER
opt = SWA(tf.keras.optimizers.SGD())
model.compile(optimizer=opt, loss='mean_squared_error')
model.fit(train_ds, epochs=20)

# AFTER FIT. KeyError is raised
opt.assign_average_vars(model.variables)

for x_train, _ in train_ds:
    model(tf.cast(x_train, tf.float32), training=True)

model.evaluate(train_ds)
model.evaluate(test_ds)

Other info / logs
As workaround, I am ignoring moving_mean and moving_variance non-trainable variables by changing this line:
assign_op = tf.group(
            [var.assign(self.get_slot(var, 'average')) for var in var_list])

to:
assign_op = tf.group(
            [var.assign(self.get_slot(var, 'average')) for var in var_list if var.trainable])

Thanks for the report!
cc @shreyashpatodia code owner.

Thanks for pointing this out @johnarevalo!
I think what is happening is that when var_list is passed to _create_slots it does not contain the moving_mean and moving_variance variables. Thus, the KeyError.
I think the optimal solution is to look at when _create_slots is called and replicating that logic in assign_average_vars for consistency.
Do you think this makes sense as a solution?

Hey, took a look at this for #760
The problem is that keras only passes trainable variables (var_list) to any optimizer. So moving_average and moving_variance of BatchNorm is never passed to the opt, and therefore we don't consider them when calculating the averaged update.
For now, @johnarevalo fix of checking when if the variable is trainable should work. But I'm not sure if that makes sense. The moving_average and moving_variance of each BatchNorm is calculated based on the original variables and not the moving average weights.

Yep. I don't think the moving_mean and moving_average learned during training are relevant for the averaged weights.
I have a note in my implementation saying that the user should make one more pass through the data to correctly calculate batch norm statistics. This would mean resetting the moving_mean and moving_variance and then running a pass through the data to learn the scale and the offset per batch norm layer.
I didn't make this part of the optimizer because I don't think this sort of logic where we make a pass through the data should exist in an optimizer. @Squadrick do you think we should add an auxiliary function that can be used to make stuff work with batch norm?

That seems to be the way the authors do it. Source code for implementation here for the batch norm update. I'll get started with adding this to #760.
@shreyashpatodia Could you take a look once I've completed the update?

Yeah sure!

On Dec 28, 2019, at 9:57 AM, Dheeraj R Reddy<EMAIL_ADDRESS>wrote:

That seems to be the way the authors do it. Source code for implementation here for the batch norm update. I'll get started with adding this to #760.
@shreyashpatodia Could you take a look once I've completed the update?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Closed with https://github.com/tensorflow/addons/pull/760?

Yep.

On 31-Dec-2019, at 7:26 PM, Sean Morgan<EMAIL_ADDRESS>wrote:

Closed with #760?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Add doc for bug bounty

I find that the intro must explain first what the program is before stating who runs it. That is why I changed the order of the elements.

I believe that I merged in your changes. Thanks!


chore: use docker buildkit to cache go build cache

Type of change:

[x] Chore

What this PR does / why we need it:

Cache go build cache to speedup builds in development env.
Pre-submission checklist:

[x] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[x] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

Codecov Report

Merging #1778 (50b05ca) into master (bacb8f8) will decrease coverage by 0.01%.
The diff coverage is 21.05%.

:exclamation: Current head 50b05ca differs from pull request most recent head 9202e6c. Consider uploading reports for the commit 9202e6c to get more accurate results

@@            Coverage Diff             @@
##           master    #1778      +/-   ##
==========================================
- Coverage   39.71%   39.71%   -0.01%
==========================================
  Files          92       91       -1
  Lines        8067     7989      -78
==========================================
- Hits         3204     3173      -31
+ Misses       4458     4410      -48
- Partials      405      406       +1

Impacted Files
Coverage Δ

pkg/api/server.go
50.00% <0.00%> (-32.72%)
:arrow_down:

pkg/api/validation/apisix_plugin_config.go
0.00% <0.00%> (ø)

pkg/api/validation/apisix_route.go
0.00% <0.00%> (-24.60%)
:arrow_down:

pkg/api/validation/validator.go
0.00% <0.00%> (ø)

cmd/ingress/ingress.go
83.33% <100.00%> (+0.14%)
:arrow_up:

pkg/api/router/webhook.go
100.00% <100.00%> (ø)

pkg/api/validation/utils.go
48.97% <100.00%> (+16.54%)
:arrow_up:

pkg/apisix/schema.go
62.26% <100.00%> (ø)

pkg/config/config.go
64.64% <100.00%> (+0.36%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


chore: update edge-service and edv image tag

Signed-off-by: Grace Liu<EMAIL_ADDRESS>

did you run the demo

I ran through new bank account usecase, and vc playground.
It works except I couldn't complete the vc flow because the rp site gives 404

did you run the demo
@fqutishat
I ran through new bank account usecase, and vc playground.
It works except I couldn't complete the vc flow because the rp site gives 404

@grace0925 The bank account demo is not using the edge-service code. We need to verify the flow through issuer and rp site (vcs demo).
@talwinder50 Can we please check the RP site giving 404 error ?


location frequency [question]

Is there any way to decrease location update time from ~5000ms to ~1000 ms? Does leaflet use a different location api than openlayers?

Hi,
Leaflet is using the Geolocation API, which allows you to set a timeout and maximumAge.
You can configure these over the locateOptions https://github.com/Leaflet/Leaflet/blob/b23d83f46416c404874ff57d1819646340297cb7/src/map/Map.js#L579
Please note that this is an issue tracker, where bugs and feature requests are posted and discussed. For questions on how to use Leaflet and other support, you're better off using stackoverflow or gis.stackexchange.com.

What @kaynz just said.


Image stream

Is it possible to create a live image stream from camera and use it with the google ml functionalities, like barcode and text?

Yes it's possible, I found in the stream listener in the sample


Order Agnostic Binary Search

Description
Describe more about the issue.
Programming language

[ ] C
[ ] C++
[x] Java
[ ] Python

Are you contributing under any open-source program ?

Hacktoberfest

Can I do this task?

Well I opened an issue for it but it is not assigned yet, I will complete as soon as it will be assigned.

whenever the problem related to binary search is given it is always mentioned that it is sorted in either ascending order or descending order, but whenever is it not mentioned in question we need to first run the logic which tells whether the array is sorted in ascending manner or descending manner and then proceed with the binary search algorithm.

@Chaitalishetty  and @kshitija-2001  if this is open pls assign it to me i am ready to solve it as well as add labels for hsoc after assigning


WIP: Support tx places in queries

First pass.
What this doesn't do is utilise an old use the tx id to fetch results from a previous version. Should that be included in this issue?

What this doesn't do is utilise an old use the tx id to fetch results from a previous version. Should that be included in this issue?

No — regular patterns, without a specified database, query just what's currently true.

Looks great. Undo my comment from the first round of review, and ship it 😁


Update BR release version and admin container

Issue #, if available:
Description of changes:

Updating BR version to 0.14.0

Based on https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/models/shared-defaults/public-host-containers.toml:

Updating admin container to 0.10.1
Updating host container to 0.7.2

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Lock Python package versions.

This looks rather stale, and anyway if we do anything with testing here we should probably first convert to dash.testing. Can we close?

@alexcjohnson Yes, this one should be OK to close.


useDraggable onMouseDown handler swallows element's onClick event

Given the code below, the handleClick is never called. Removing {...listeners} fixes the issue. It appears the listeners.onMouseDown prevents propagation of the event.
<li       onClick={handleClick}       ref={setNodeRef}       {...attributes}>       {...listeners}       <Content />     </li>
I've tried wrapping it with a div, wrapping Content with a div etc.
Any advice / pointers would be greatly appreciated.

Set an activationConstraint on the Mouse or Pointer sensor that is either based on distance or delay: https://docs.dndkit.com/api-documentation/sensors/pointer#activation-constraints
useSensor(PointerSensor, {
  activationConstraint: {
    distance: 10,
  },
});

@clauderic sorry, I forgot to include my container's code in the snippet above:
const pointerSensor = useSensor(PointerSensor, { activationConstraint: { distance: 10 } });   const sensors = useSensors(pointerSensor);
<DndContext sensors={sensors}><ul...

Your issue describes onMouseDown handlers swallowing onClick events, but the Pointer sensor doesn't use onMouseDown, it uses onPointerDown 🤔
Possibly a duplicate of #172?
Please consider opening a CodeSandbox replicating the issue for further assitance.

Thank you for the prompt replies @clauderic. I'll share a CodeSandBox example shortly.

@clauderic for your reference: https://codesandbox.io/s/dndkit-k75i3?file=/index.tsx
It works 100% as expected. I'm trying to see what I'm doing wrong in my project.

Hey all,
I had the same issue, removing the DragOverlay solved it for me. I suppose it was something like onPointerDown is triggered, and the dragOverlay appeared on top of the button before the mouseUp event was triggered, so the button was never really clicked at all.


Update ansible version requirement

Ansible version 2.10 reports the Rocky Linux OS family as Rocky, rather than RedHat, which causes problems in roles such as in the os-images role here:
https://github.com/stackhpc/ansible-role-os-images/blob/4696b3112d216c5cb2d871c6a98e91845a274147/tasks/images.yml#L3

I think you have to find the version of ansible that matches the ansible-core version you want…

I gave it a go and pip/ansible seems to just make everything magically work. I'm guessing everything else is just bundled as a dependency.

Retested and you're right, must've had something lingering last time around


There is a missing double cottation in line 814 of the file sampled_label_dataset.csv

Thanks for sharing the dataset. Please correct the sampled_label_dataset.csv file by adding the missing closing double quotation (") in line 814 (the row starts with "aajgefiaf"). This issue causes panda's read_csv cannot load the dataset correctly.

Hi @s-sheikhaei ,
Thank you for your involvement here. I was able to reproduce the issue and pushed out a fix. I was able to get pd.read_csv to work with the specified file.
Thanks again!
David OBrien

Thanks @DavidMOBrien


Not being able to load LongT5 checkpoint with ORTModelForSeq2SeqLM

System Info
transformers==4.22.1
optimum==1.4.0
onnx==1.12.0
onnxruntime==1.12.1

Python 3.8.10

Who can help?
@lewtun, @michaelbenayoun
Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[X] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction
from transformers import AutoTokenizer
from optimum.onnxruntime import ORTModelForSeq2SeqLM

model_name = "google/long-t5-tglobal-xl"
tokenizer = AutoTokenizer.from_pretrained(model_name)

# This gives an exception!
model: ORTModelForSeq2SeqLM = ORTModelForSeq2SeqLM.from_pretrained(
    model_name, from_transformers=True, save_dir="./local_temp"
)

print("Loaded!")
tokenizer.save_pretrained("local_onnx")
model.save_pretrained("local_onnx")

Above code snippet causes the following exception:
Traceback (most recent call last):
  File "optimize_with_optimum.py", line 108, in <module>
    model: ORTModelForSeq2SeqLM = ORTModelForSeq2SeqLM.from_pretrained(model_name, from_transformers=True)
  File "/home/jinkoo/.local/lib/python3.8/site-packages/optimum/modeling_base.py", line 228, in from_pretrained
    return cls._from_transformers(
  File "/home/jinkoo/.local/lib/python3.8/site-packages/optimum/onnxruntime/modeling_seq2seq.py", line 441, in _from_transformers
    return cls._from_pretrained(save_dir, **kwargs)
  File "/home/jinkoo/.local/lib/python3.8/site-packages/optimum/onnxruntime/modeling_seq2seq.py", line 316, in _from_pretrained
    model = cls.load_model(
  File "/home/jinkoo/.local/lib/python3.8/site-packages/optimum/onnxruntime/modeling_seq2seq.py", line 213, in load_model
    decoder_session = onnxruntime.InferenceSession(str(decoder_path), providers=[provider])
  File "/home/jinkoo/.local/lib/python3.8/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 347, in __init__
    self._create_inference_session(providers, provider_options, disabled_optimizers)
  File "/home/jinkoo/.local/lib/python3.8/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 395, in _create_inference_session
    sess.initialize_session(providers, provider_options, disabled_optimizers)
  onnxruntime.capi.onnxruntime_pybind11_state.Fail: [ONNXRuntimeError] : 1 : FAIL : Deserialize tensor onnx::MatMul_5263 failed.tensorprotoutils.cc:640 TensorProtoToTensor External initializer: onnx::MatMul_5263 offset: 0 size to read: 41943040 given file_length: 16777216 are out of bounds or can not be read in full.

Expected behavior
ONNX checkpoints of encoder, decoder and decoder with past being generated!

It seems this does not happen with google/long-t5-tglobal-large. Furthermore, I was actually able to load the model as ORTModelForSeq2SeqLM by exporting the XL checkpoint myself and using from_transformers=False. I think some decoder external files are overwritten when it is exporting decoder with past. So, in my case, when I was exporting, I used the separate folders for decoder and decoder with past.


running autoprefixer has no effect

Properties I've tried

order,
clip,
transition,
display: flex

It doesn't generate any error messages. It just leaves the code looking like it did prior to shift+cmd+P, "autoprefixer," enter.
Running OSX 10.10.4. Atom 1.0.5. atom-autoprefixer 2.2.4.
Probably something wrong with my config (below).
"*":
  editor:
    invisibles:
      eol: "!"
    fontSize: 15
    softWrapAtPreferredLineLength: true
    softWrap: true
  core:
    themes: [
      "one-dark-ui"
      "zenburn"
    ]
    disabledPackages: [
      "webbox-color"
      "csscomb"
      "css-comb"
      "linter-csslint"
      "gulp-helper"
      "gulp-snippets"
    ]
    projectHome: "~/app/BMO"
    audioBeep: false
    ignoredNames: [
      ".git"
      ".hg"
      ".svn"
      ".DS_Store"
      "Thumbs.db"
      ".codekit-cache"
      "bower_components"
      "node_modules"
    ]
  welcome:
    showOnStartup: false
  linter:
    lintOnFly: true
    showErrorPanel: false
  "webbox-color":
    fillColorAsBackground: false
  "white-cursor":
    darkThemes: [
      "zenburn"
    ]
  pigments:
    markerType: "underline"
  "atom-css-comb":
    projectConfigs: ".csscomb.json"
    readyMadeConfigs: "csscomb"
"linter-csslint":
  csslintExecutablePath: "/usr/local/bin/csslint-cli"

Works for me with latest Atom and Autoprefixer. Can you try reinstalling the plugin?

That was the last thing I did before posting this issue, but reinstalling again seems to have fixed it.
The package now adds empty lines between the prefixed rules though. Is that the default behavior?
Looks like there is just a new line for each prefix on the readme.md demo.


Synology package doesn't work

Unfortunately latest compiled version doesn't start. It outputs the following to /var/log/messages:
umount: can't umount /flaccue: Invalid argument

So probably it can't mount fuse (so that I see unmount problem).

Ok, more logs:
==> synofeasibilitycheck.log <==
2020-05-05T14:28:00+03:00 nas synoscgi_SYNO.Core.Package_1_feasibility_check[25586]: feasibility_check.cpp:87 FeasibilityCheck: [Info] Start feasibility check [package_start] with type [hard].
2020-05-05T14:28:00+03:00 nas synoscgi_SYNO.Core.Package_1_feasibility_check[25586]: feasibility_check.cpp:106 FeasibilityCheck: [Info] [0] of feasibility check [package_start] failed.
2020-05-05T14:28:00+03:00 nas synoscgi_SYNO.Core.Package_1_feasibility_check[25586]: feasibility_check.cpp:79 FeasibilityCheck: [Info] No [package_start] feasibility check config with type [soft].

==> messages <==
2020-05-05T14:28:02+03:00 nas umount: can't umount /flaccue: Invalid argument

==> synopkg.log <==
2020/05/05 14:28:02     start FLACCue: begin to stop version 2.0.0002
2020/05/05 14:28:02     start FLACCue 2.0.0002 Begin start-stop-status stop
2020/05/05 14:28:02     start FLACCue 2.0.0002 End start-stop-status stop ret=[0]
2020/05/05 14:28:02     start FLACCue 2.0.0002 Begin unload apparmor
2020/05/05 14:28:02     start FLACCue 2.0.0002 End unload apparmor ret=[0]
2020/05/05 14:28:02     start FLACCue: stop version 2.0.0002 successfully, result 0
2020/05/05 14:28:02     start FLACCue: begin to start version 2.0.0002
2020/05/05 14:28:03     start FLACCue 2.0.0002 Begin pre-load apparmor
2020/05/05 14:28:03     start FLACCue 2.0.0002 End pre-load apparmor ret=[0]
2020/05/05 14:28:03     start FLACCue 2.0.0002 Begin start-stop-status start
2020/05/05 14:28:03     start FLACCue 2.0.0002 End start-stop-status start ret=[0]
2020/05/05 14:28:03     start FLACCue: start version 2.0.0002 successfully, result 0

==> synoservice.log <==
2020-05-05T14:28:02+03:00 nas synoscgi_SYNO.Core.Package.Control_1_start[25693]: service_stop.c:23 synoservice: [pkgctl-FLACCue] stopping ...
2020-05-05T14:28:02+03:00 nas synoscgi_SYNO.Core.Package.Control_1_start[25693]: service_stop.c:86 synoservice: [pkgctl-FLACCue] stopped.
2020-05-05T14:28:02+03:00 nas synoscgi_SYNO.Core.Package.Control_1_start[25693]: service_start.c:74 synoservice: [pkgctl-FLACCue] starting ...
2020-05-05T14:28:03+03:00 nas synoscgi_SYNO.Core.Package.Control_1_start[25693]: service_start.c:178 synoservice: [pkgctl-FLACCue] started.

==> auth.log <==
2020-05-05T14:28:03+03:00 nas sudo:     root : TTY=unknown ; PWD=/ ; USER=plex ; COMMAND=/bin/nohup FLACCue/ /flaccue/
2020-05-05T14:28:03+03:00 nas sudo: pam_unix(sudo:session): session opened for user plex by (uid=0)
2020-05-05T14:28:03+03:00 nas sudo: pam_unix(sudo:session): session closed for user plex

==> pmesg <==
<< SOME RANDOM DATA >>

Ok, stupid me. I didn't install ffmpeg and pip packages.
@acenko thank you for the great work!


Add Windows run process tests

High-level description
Add tests for winpanda subprocess functions
Corresponding DC/OS tickets (required)

DCOS-ID JIRA title / short description.

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

These tests (and the fix) should be added, but I'm waiting for https://github.com/dcos/dcos/pull/6706 to be merged first to avoid conflicts

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot changelog-not-required fix to unreleased code


add edits to text_data_release.yml

Edits discussed with Amelia on call 4/5/23

@ted80810 and @amsynder, I don't seem to have permissions to request you as reviewers for this, but here are my edits. I've also made some notes in the DRB_SaltFront_Metadata_Notes.doc


how to use getter in lucid model for pivot table

i have two models.from this section of framework documentation i've been implemented many-to-many relationship in my app.problem is , i have created_at field in pivot table and i want to convert georgian date to my local date with getter in one of the models.but idon't have any idea to how can i do this.anybody know that...?
thank you.

Pivot tables does not have any model attached to them, so unfortunately there is no way to define any getters for them.
You may have to do some manual iteration on them

Closing since not actionable and no response from the issue reporter


ACM ICPC Team

There is a problem as the ACM ICPC Team problem has been added under this path: CompetitiveCode/Hackerrank_problems/Game of Thrones - I
it should have been added under this path: CompetitiveCode/Hackerrank_problems/ACM ICPC Team
How can we fix it?


Delete Dead Code

Delete dead code after refactoring done in generators see https://github.com/driftyco/ionic-cli/pull/1364

Related #1469

closing in favor of #1469.


DHIS2 updates to healthsites

As a healthsites data administrator I would like to know if the DHIS2 instance has new updates so that I can improve the quality of data in healthsites

You can synchronize datas from one instance of dhis2 to another.
Am I wrong to assume that we can just:

customize a specific url on your healthsite platform
this specific url will be configured to receive data posted from your dhis2 instance,
then, this specific url (+ user + password) will be used to configure your dhis2 instance synchronization

diplication https://github.com/healthsites/healthsites/issues/904


Upgrade ack-test dependencies

Fixes https://github.com/aws-controllers-k8s/community/issues/1848
For the last two days, our prow jobs were failing due to some package
installation errors. This was mainly due to deprecations in the pip3 CLI
tool. The deprecated features could no longer install PyYAML v5.0.X.
This patch upgrades all the libraries imported by ack-test
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/hold

I feel more confident with just updating one dependency at a time.
/lgtm

/unhold


RBS-1395 Create Download File component

Changes
Create new Download File component

[keep | delete] branch

Changelog entry

[BREAKING | WARNING | remove if none] Description of change in Component-name

Additional information

You may refer to this ticket
Any other information you would like to include

hi, I don't have access to the ticket, is this Figma page the finalised specs?
https://www.figma.com/design/us90jOpWBahsqK2VAluPvD/Flagship-Design-System?node-id=8475-54069&t=zMk9HHBbKUbDmDcy-0
are there any requirements on how a list of items are to be displayed?
do include file-download.mdx for the stories with the corresponding prop table, and remove any unnecessary CSFs

hi, I don't have access to the ticket, is this Figma page the finalised specs? https://www.figma.com/design/us90jOpWBahsqK2VAluPvD/Flagship-Design-System?node-id=8475-54069&t=zMk9HHBbKUbDmDcy-0
are there any requirements on how a list is to be displayed?
do include file-download.mdx for the stories with the corresponding prop table, and remove any unnecessary CSFs

while updating the storybook documentation, I found a display issue for long file names without word breaks. could this be addressed?


request::target() is not returning the correct data

Version of Beast
commit ac5bc4f62c318812104ad2cef13b2d3a19ada8bb
Author: Vinnie Falco<EMAIL_ADDRESS>Date:   Sun Jun 4 21:15:04 2017 -0700
Set version to 49

Steps necessary to reproduce the problem
I was writing some unit tests for an app I'm working on and I noticed that one was failing oddly.  After further investigation it appears that the request::target() method isn't storing the target string_view.  The trivial test below demonstrates it:
...
#include <beast/core.hpp>
#include <beast/http.hpp>

#include <boost/test/unit_test.hpp>
...
using namespace std::string_literals;

BOOST_AUTO_TEST_SUITE(scratch)
BOOST_AUTO_TEST_CASE(target_test)
{
    const auto port = std::uint16_t{1234};
    const auto tgt = "/hello"s;
    const auto host_str = "my_computer:" + std::to_string(port);

    auto fields = beast::http::fields{};
    fields.insert("Content-Type", "application/json");
    fields.insert("Host", host_str);

    auto req = beast::http::request<beast::http::empty_body>{};
    req.method(beast::http::verb::get);
    req.target(tgt);
    req.version = 11;
    req.fields = fields;

    beast::http::prepare(req);
    BOOST_TEST_MESSAGE(req);

    BOOST_CHECK(req.is_request);
    BOOST_CHECK_EQUAL(req.method(), beast::http::verb::get);
    BOOST_CHECK_EQUAL(req.target(), tgt);
    BOOST_CHECK_EQUAL(req.version, 11);

    auto fIt = fields.find("Content-Type");
    BOOST_REQUIRE(fIt != fields.end());
    BOOST_CHECK_EQUAL(fIt->value(), "application/json"s);

    fIt = fields.find("Host");
    BOOST_REQUIRE(fIt != fields.end());
    BOOST_CHECK_EQUAL(fIt->value(), host_str);
}
BOOST_AUTO_TEST_SUITE_END()

Outputs:
Entering test case "scratch"
GET  HTTP/1.1
Content-Type: application/json
Host: my_computer:1234

error: in "scratch/target_test": check req.target() == tgt has failed [ != /hello]

Putting a breakpoint at BOOST_TEST_MESSAGE(..) via gdb reveals:
(gdb) p req.method()
$2 = beast::http::verb::get
(gdb) p req.target()
$3 = {static npos = <optimized out>, ptr_ = 0x0, len_ = 0}
(gdb)

Or am I just doing something stupid?
All relevant compiler information
g++ (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1)

"Never underestimate the ability of users to abuse your interface in ways you hadn't thought of."
Thanks for the detailed report. I'm quite impressed actually, you have managed to break my code within mere hours of the merge! Here's the problem:

req.fields = fields;

Beast now stores the strings for method, target, and reason in the Fields. By assigning, you throw out the value of target. The reason I made this change is because before, they were being stored as std::string which bypasses the allocator. You can read the motivation behind this change in this new doc section:
http://vinniefalco.github.io/beast/beast/design/http_message.html
You could have just written
req.fields.insert("Content-Type", "application/json");

If you avoid assigning the entire fields container, you'll find that it works.
Just a heads up but the interface will be changing (I am trying to polish this up as much as I can ahead of the July 1 Boost review). header will derive from Fields, instead of having a member named fields. Your could would be written thusly:
    auto req = beast::http::request<beast::http::empty_body>{};
    req.version = 11;
    req.method(beast::http::verb::get);
    req.target(tgt);
    req.insert(field::content_type, "application/json");
    req.insert(field::host", host_str);
    req.prepare();

There's quite a few changes as you can see.

Thank you!
The required change also demonstrated that my field tests weren't testing what I thought they were...

What do you think about these changes? Feedback welcomed! Now is the time to complain, before July 1st!

I'm not familiar with Beast enough to comment with any authority, but in this particular example, I'm perfectly happy with header deriving from fields.

Is this issue resolved?


Implement chips (tags)

Tbh, I find the Materialize implementation lacks a tag editor.
I'd rather like to implement a wrapper for this library: http://henrychavez.github.io/materialize-tags/examples/

Any opinions on that?
Or stay "vanilla" and implement that later as an optional addition?

I would like that you make this decision while keeping two seemingly contradictory criteria in mind:

Make Materialize as good as possible - as it will be very popular in Aurelia developers circles
Make yourself available for several next projects that will most likely be using Aurelia Materialize bridge

Then I'll keep external dependencies to a minimum for now and have a look later when I've done all the other things.
I'm curious on what these several next projects might be. :smile:


Fix Anger Point's Interaction with Mold Breaker

Moved Anger Point's check for critical from onCritical to onAfterDamage.
This not only allows it to avoid being suppressed by Mold Breaker, it
also results in the Anger Point message being displayed in the correct
order with respect to the other messages.

Don't merge yet, the sub interaction is actually wrong right now. Whoops.

Check previous gens as well if you're changing it because I believe the behavior changes across gens.

Evidently my sub interactions were correct and I was only second-guessing myself. Since onAfterDamage is only called when you don't have a sub, that also means I don't actually have to check for a sub in that function.
Gen 4 is where the interaction is different (it does work with a Sub), so I added a check in that gen for onAfterSubDamage as well (and it inherits the onAfterDamage check from gen 5+)


chore(image_projection_based_fusion): rename debug topics

Description

To rename unclear namespace of debug topics published by fusion.cpp interface.

Related Link
TIER IV INTERNAL LINK
Tests performed

Confirm by logging_simulator that debug topics namespace matching with node name

Before:
/perception/object_recognition/detection/clustering/camera_lidar_fusion/image_projection_based_fusion/debug/roi0/timestamp_interval_ms /perception/object_recognition/detection/clustering/image_projection_based_fusion/debug/roi0/timestamp_interval_ms /perception/object_recognition/detection/image_projection_based_fusion/debug/roi0/timestamp_interval_ms /perception/object_recognition/detection/pointpainting/image_projection_based_fusion/debug/roi0/timestamp_interval_ms

After:
autoware@npc2201009-ubuntu22:~/autoware$ ros2 topic list | grep roi0/timestamp_interval_offset_ms /perception/object_recognition/detection/clustering/camera_lidar_fusion/roi_cluster_fusion/debug/roi0/timestamp_interval_offset_ms /perception/object_recognition/detection/clustering/roi_pointcloud_fusion/debug/roi0/timestamp_interval_offset_ms /perception/object_recognition/detection/pointpainting/pointpainting/debug/roi0/timestamp_interval_offset_ms /perception/object_recognition/detection/roi_detected_object_fusion/debug/roi0/timestamp_interval_offset_ms

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Almost looks good.
/perception/object_recognition/detection/clustering/camera_lidar_fusion/roi_cluster_fusion/debug/cyclic_time_ms
/perception/object_recognition/detection/clustering/camera_lidar_fusion/roi_cluster_fusion/debug/pipeline_latency_ms
/perception/object_recognition/detection/clustering/camera_lidar_fusion/roi_cluster_fusion/debug/processing_time_ms
/perception/object_recognition/detection/clustering/roi_cluster/clusters
/perception/object_recognition/detection/clustering/roi_pointcloud_fusion/debug/clusters
/perception/object_recognition/detection/clustering/roi_pointcloud_fusion/debug/cyclic_time_ms
/perception/object_recognition/detection/clustering/roi_pointcloud_fusion/debug/pipeline_latency_ms
/perception/object_recognition/detection/clustering/roi_pointcloud_fusion/debug/processing_time_ms
/perception/object_recognition/detection/clustering/roi_pointcloud_fusion/output/pointcloud
/perception/object_recognition/detection/pointpainting/objects
/perception/object_recognition/detection/pointpainting/output
/perception/object_recognition/detection/pointpainting/pointpainting/debug/cyclic_time_ms
/perception/object_recognition/detection/pointpainting/pointpainting/debug/pipeline_latency_ms
/perception/object_recognition/detection/pointpainting/pointpainting/debug/processing_time_ms
/perception/object_recognition/detection/pointpainting/roi_fusion/objects
/perception/object_recognition/detection/pointpainting/validation/objects
/perception/object_recognition/detection/roi_detected_object_fusion/debug/cyclic_time_ms
/perception/object_recognition/detection/roi_detected_object_fusion/debug/fused_objects
/perception/object_recognition/detection/roi_detected_object_fusion/debug/ignored_objects
/perception/object_recognition/detection/roi_detected_object_fusion/debug/pipeline_latency_ms
/perception/object_recognition/detection/roi_detected_object_fusion/debug/processing_time_ms

Just one question. /perception/object_recognition/detection/clustering/roi_cluster/clusters~ is published by roi_pointcloud_fusion but its namespace is roi_cluster. Is this intended?

Almost looks good.
Just one question. /perception/object_recognition/detection/clustering/roi_cluster/clusters is published by roi_pointcloud_fusion but its namespace is roi_cluster. Is this intended?

@miursh I made roi_cluster as namespace of debug topics also in https://github.com/autowarefoundation/autoware.universe/pull/6418/commits/7bae271a53f83b41a846b82b6e5e4d172d3ced31
The result as below:


stop from auto-appending trailing slash at root of app

For example, if the root is "/app", and you visit "website.com/app", vue-router will auto append a trailing slash, making it "website.com/app/", but any other routes will not have a trailing slash auto-appended (ex. "website.com/app/users"

Vue.js & vue-router.js version
1.0.16, 0.7.11
Reproduction Link

Any vuejs app
Steps to reproduce
visit the root of your app with vue-router enabled
What is Expected?
no trailing slash
What is actually happening?
trailing slash auto-appending

Because it's the root, hence the /. This is necessary for the matching to work properly.

Thanks for the quick response, though I'm not sure if it is necessary... Because it works perfectly if no root is defined. (e.g. "website.com" <---> "website.com/users", it does not auto-append the trailing slash on the first route). If your root is "/app" it should be able to match "/app", not "/app/".
Ultimately this is very non-critical and I know you have more important Vue things to work on, so I will probably do a PR.
Thanks Evan, great work.

You are free to submit a pull request if you think it can work without it.


Support for emacs / spacemacs ?

I would definitely use this if I could pass emacsclient -nw to the editor to be able to load the results in emacs.. Probably requires so extra options so that it opens the stuff in the right place but I'm sure it's a pretty easy addition. I'd recommend an emacs and emacsclient option but probably both should use the -nw (terminal only) option but that's debatable..
Thanks!

Emacs support was not added so far because I know nothing about it 😅 but I will treat it as an opportunity to change this.


Out-of-Range Change

In the dropdown to select a custom distance for out-of-range, would it be possible to get this bumped up to 40 yards from the current max distance of 35? A lot of times I can still heal a greyed-out box because my spells are 40 yards in range, but my unit frames are telling me they are out of range because of the 35-yard distance. I am happy to change the code myself, but  I am not quite sure where this would be or if it's as easy a fix as I think it is. Any help with this would be greatly appreciated, I am currently wasting some time clicking to "test" whether my target is in range when it could just immediately let me know if it was just greyed out accurately at 40 yards. Thanks for the help!

This was fixed a while ago, just getting around to closing it now.


@slow test RFC

Also see discussion in the pre-RFC: https://discuss.tvm.apache.org/t/rfc-ci-skip-slow-tests-on-prs/11910
@areusch @Mousius

@Mousius can you take another look when you have a min?


Fix vscode extension not loaded

Bump version to publish vscode extension again
Problem
VSCode is electron based application which not support esm extension.
In previous version 0.3.8 #706 I mistakenly write type: module
which fix in bc3df868a6c12704563a50de2c609c3617b11518 by remove it to revert to default behavior use type: commonjs as fallback
But that Fixed! version not publish yet in marketplace, so patch a version to help easier publish it.

Could you also publish it for https://VSCodium.com, please?

Only person who can publish vscode-extension is @STRd6

Maybe, in the future, we can have CI/CD?

I believe the fixed version is published in the marketplace (at least it is working for me). What specifically is the error you are seeing?
I also published the updated vscodium version as well.

The problem we found after install civet 0.3.8 directly from vscode
left is 0.3.8, right is 0.3.9 local build

Server is not running

Icon not display

No intellisense

This one is working for me, what version of VS Code? Are there any errors in the extension host log?

Extension Host Error (1st time seeing this 😂)

I use macOs M1 Arm ship with<EMAIL_ADDRESS>

Have you tried re-installing v0.3.8? I built that version from this commit: https://github.com/DanielXMoore/Civet/commit/bc3df868a6c12704563a50de2c609c3617b11518

Oh That is may fault. I didn't know that vscode always cache local extension. So when re-intall, it just reuse my local (buggy) cache. Just delete folder and re-install and WORK!
Thank for new learning @STRd6 😂.
Close this pull. Because extension is working fine.

👍 No problem, thanks for the original patch!


Change gRPC to use the newly released tags/stats APIs

After we release the new APIs we must change gRPC to use them.

I removed the milestone, since we need to do this after the APIs have been released.

We should probably create a milestone for gRPC integration. And link all the issues related to gRPC with that.

I added a new milestone: https://github.com/census-instrumentation/opencensus-java/milestone/9

PR to update gRPC: https://github.com/grpc/grpc-java/pull/3647

The PR was merged.


MD-1955 - Isolate and run failing tests to identify random failures

To detect random failures .

Kedar, please squash your commits, and let us know if you have tested the changes

Hi Abhishek
I have squashed the commits and now checking once more in jenkins
Thanks

On Jun 20, 2017, at 1:28 PM, Abhishek Girish<EMAIL_ADDRESS>wrote:
Kedar, please squash your commits, and let us know if you have tested the changes
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/mapr/drill-test-framework/pull/284#issuecomment-309881391, or mute the thread https://github.com/notifications/unsubscribe-auth/AFDFEH6qBs38KtRrpb2Dhn_VbrMceIJNks5sGCtegaJpZM4N31i5.

+1
Thanks for contributing to this feature. Also, thanks for addressing all review comments.


CHANGELOG for v3.0.6 missing

I just saw the package is updated to v3.0.6, but I can't find any records in the CHANGELOG to check out the changes.
Would you guys be so kind to provide us with a decent CHANGELOG please? 🙂
Thanks for all your hard work! 🙂
Duplicates #169

For some reason the changelog was lost. 3.0.6 had no change, only fixed the missing files in the build.

Updated: https://github.com/reactivestack/cookies/blob/master/CHANGELOG.md


Register Appium server with Selenoid Hub

Hi,
Using Selenium Grid it's possible to register an Appium server, as documented here and use Real devices.
Also, based on the documentation, it seems that it's possible to use Selenoid without Docker as well, in case of Internet Explorer for example.
So, my question is whether it's possible to register an Appium server with Selenoid, so that we can also add REAL devices for our tests?
Thanks,
Cosmin

@CosminGramada Selenoid has no /grid registration API. So the only way to use Selenoid with Appium is either launch it as a process every time or build a Docker container with Appium (e.g. like this).

@vania-pooh
Not sure whether using a container with Appium would do the trick because it require a different port in order to support parallel execution on multiple devices. So, in case I'm not missing something, to start it everytime would be way to go.
Now, regarding the capabilities, what is required in the json file so that Selenoid can communicate with the Appium Server?

@CosminGramada in Selenoid JSON file you have to specify either Appium startup command or a reference to Docker image with Appium.

@CosminGramada any more things to discuss in this issue?

@vania-pooh This was on hold from my side due to several internal reasons, so I guess it can be closed.
In case any other questions or issues arise, I'll open a new thread. Thank you.


Optimize expiration time for shorter format

I guess expiration is an issue on smaller/mobile screens, and overall we don't need to show it longer if it's expiration longer than one day.

Make mixin, which helps show expiration in the shorter format.
Change everywhere in offer tables

I.e. example
13 days 15 hours 38 minutes -> 13 days
15 hours 38 minutes -> 15 hours
38 minutes -> 38 minutes
https://user-images.githubusercontent.com/5887929/181906017-7325cdc6-de87-4d19-81d1-76e5bbf34612.mov

👋


git changes lags in editor

SCM shows 0 changes but in the editor, I still see bugged git changes. It lags appear from version +-1.42

VSCode Version: 1.44.2
OS Version: Windows 10 x64 + WSL Ubuntu 16.04
No plugins for work with git installed

Steps to Reproduce:

Stage a few changes and add commits from SCM
Add tags from the terminal and run: git push origin --all && git push origin --tags
open SCM: 0 changes but in editor still see bugged changes

Forgot to take a screenshot, if it appears again I'll add it later

You seem to be missing file events. Please go through the following steps:

Run Git: Set Log Level... and choose Trace
Run Git: Show Git Output
Reproduce the issue and wait 10-20 seconds
Paste the whole output here

@joaomoreno
git.log

I am wondering if vscode is considering building a git service instead of invoking the git cli? Or, if git cli is considering to build a performant "server" edition, like the dotnet cli?
Additionally, I noticed that the performance of the vscode git scm integration is much slower than the regular commandline interaction. Ideally vscode should be on par or even surpass the commandline performance.

@lipal File events seem to work fine here. How often does this reproduce for you?
@cveld As I mentioned to you in private, please just file an issue with your specific situation. Commenting on other issues is counterproductive.

@joaomoreno random, sometimes it appears just once a month, sometimes every day, but anyway it frequently appears from time to time

@joaomoreno

In that case, running git status would return the changes? Or was the editor simply out of date?

@joaomoreno The editor is out of date. git status returned nothing.

This is strange, since I can't reproduce at all. Are the files stored in the WSL side or in Windows?

@joaomoreno WSL only

@lipal Developing VS Code using WSL is what I do most of the time.
If you could find steps which would reproduce this on your machine 100% of the time, that would be great.