Building package sfml:x86-windows failed

I am getting a build error trying to install sfml
Package: sfml:x86-windows
Vcpkg version: 0.0.80-2559c9773615ac1d657bc350a3ce0ad9d724e55c

Here is the error portion of the output log file (buildtrees\sfml\package-x86-windows-rel-out.log)
Build FAILED.

       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\install.vcxproj" (default target) (1) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\ALL_BUILD.vcxproj" (default target) (3) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-audio.vcxproj" (default target) (4) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-system.vcxproj" (default target) (5) ->
       (ClCompile target) ->
         E:\Dev\code\vcpkg\buildtrees\sfml\src\SFML-2.4.2\src\SFML\System\Win32\ClockImpl.cpp(48): warning C4996: 'GetVersion': was declared deprecated [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-system.vcxproj]

       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\install.vcxproj" (default target) (1) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\ALL_BUILD.vcxproj" (default target) (3) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-network.vcxproj" (default target) (8) ->
         E:\Dev\code\vcpkg\buildtrees\sfml\src\SFML-2.4.2\src\SFML\Network\IpAddress.cpp(92): warning C4996: 'inet_ntoa': Use inet_ntop() or InetNtop() instead or define _WINSOCK_DEPRECATED_NO_WARNINGS to disable deprecated API warnings [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-network.vcxproj]
         E:\Dev\code\vcpkg\buildtrees\sfml\src\SFML-2.4.2\src\SFML\Network\Ftp.cpp(466): warning C4244: 'argument': conversion from 'std::streamoff' to 'int', possible loss of data [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-network.vcxproj]
         E:\Dev\code\vcpkg\buildtrees\sfml\src\SFML-2.4.2\src\SFML\Network\Ftp.cpp(466): warning C4244: 'argument': conversion from 'std::streamoff' to 'const unsigned int', possible loss of data [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-network.vcxproj]
         E:\Dev\code\vcpkg\buildtrees\sfml\src\SFML-2.4.2\src\SFML\Network\Ftp.cpp(634): warning C4244: '=': conversion from 'std::streamsize' to '::size_t', possible loss of data [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-network.vcxproj]
         E:\Dev\code\vcpkg\buildtrees\sfml\src\SFML-2.4.2\src\SFML\Network\IpAddress.cpp(184): warning C4996: 'inet_addr': Use inet_pton() or InetPton() instead or define _WINSOCK_DEPRECATED_NO_WARNINGS to disable deprecated API warnings [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-network.vcxproj]

       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\install.vcxproj" (default target) (1) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\ALL_BUILD.vcxproj" (default target) (3) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-audio.vcxproj" (default target) (4) ->
         E:\Dev\code\vcpkg\buildtrees\sfml\src\SFML-2.4.2\src\SFML\Audio\SoundFileReaderFlac.cpp(287): warning C4244: 'argument': conversion from 'sf::Uint64' to 'int', possible loss of data [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-audio.vcxproj]
         E:\Dev\code\vcpkg\buildtrees\sfml\src\SFML-2.4.2\src\SFML\Audio\SoundFileReaderWav.cpp(149): warning C4018: '<': signed/unsigned mismatch [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-audio.vcxproj]

       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\install.vcxproj" (default target) (1) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\ALL_BUILD.vcxproj" (default target) (3) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-network.vcxproj" (default target) (8) ->
       (Link target) ->
         LINK : fatal error LNK1181: cannot open input file 'Release\sfml-system.lib' [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-network.vcxproj]

       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\install.vcxproj" (default target) (1) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\ALL_BUILD.vcxproj" (default target) (3) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-window.vcxproj" (default target) (9) ->
         LINK : fatal error LNK1181: cannot open input file 'Release\sfml-system.lib' [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-window.vcxproj]

       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\install.vcxproj" (default target) (1) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\ALL_BUILD.vcxproj" (default target) (3) ->
       "E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-audio.vcxproj" (default target) (4) ->
         LINK : fatal error LNK1181: cannot open input file 'Release\sfml-system.lib' [E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-audio.vcxproj]

    8 Warning(s)
    3 Error(s)

The error log (\buildtrees\sfml\package-x86-windows-rel-err.log) is empty. Let me know if you need any other information.

Hmm, that's quite strange. It looks like something prevented sfml-system.lib from being created, but nothing is listed here directly. It doesn't look like a build dependency issue because

"E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-audio.vcxproj" (default target) (4) ->
"E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\sfml-system.vcxproj" (default target) (5) ->

indicates that audio is correctly depending on system.
Could you mail the full output log to<EMAIL_ADDRESS>for us to look at? I'm suspecting there was an failure like "linker out of memory" or something earlier in the build.

Sent with subject "sfml build output log"

Thanks. So, earlier in the log we have:
# Your log
         "sfml-system.dir\Release\MutexImpl.obj"
         "sfml-system.dir\Release\SleepImpl.obj"
         "sfml-system.dir\Release\ThreadImpl.obj"
         "sfml-system.dir\Release\ThreadLocalImpl.obj"
         sfml-system.vcxproj -> E:\Dev\code\vcpkg\buildtrees\sfml\x86-windows-rel\Release\sfml-system-2.dll

# My log
         "sfml-system.dir\Release\MutexImpl.obj"
         "sfml-system.dir\Release\SleepImpl.obj"
         "sfml-system.dir\Release\ThreadImpl.obj"
         "sfml-system.dir\Release\ThreadLocalImpl.obj"
            Creating library D:/src/vcpkg/buildtrees/sfml/x86-windows-rel/Release/sfml-system.lib and object D:/src/vcpkg/buildtrees/sfml/x86-windows-rel/Release/sfml-system.exp
         sfml-system.vcxproj -> D:\src\vcpkg\buildtrees\sfml\x86-windows-rel\Release\sfml-system-2.dll

Your link step definitely didn't make an import lib, and that's the problem. Looking further up, I see:
# Your log
/D SFML_SYSTEM_EXPORTS /D SFML_STATIC /D _WINDLL /D _UNICODE /D UNICODE

# My log
/D SFML_SYSTEM_EXPORTS /D _WINDLL /D _UNICODE /D UNICODE

Did you edit the SFML portfile or sources at all? It looks like the configure step got very confused. If you haven't edited the portfile or sources, could you please mail us the configure logs (configure-x86-windows-rel-{out, err}.log)?

Sent. I didn't edit the portfile or sources. I have used SFML in the past with Visual Studio, before vcpkg, and I recall fiddling with the SFML_STATIC flag, perhaps in my property pages. Could that be a problem? I'm looking into it now, if I can remember where to find them (haven't used VS in a long time).

I found my user property pages. And I did indeed have SFML_STATIC defined in there. I restored my user property pages to default by deleting them, and now SFML builds.

I've also pushed 9c40995 which should suppress using the user props for all vcpkg-toolchain based builds. Thanks for helping me work through this issue!


Bug Fix Release for "fix(primitives): git rename b64Binary"

It would be very helpful if a bug fix release of the three fhir-ts packages incorporating the "fix(primitives): git rename b64Binary" (commit 460f8325d76b91a1b67129f5aa915be23812f5dc)

Sorry bout that, version 0.4.2 should have that bug fix.

Thank you!


Can't create sub categories of products in the Dashboard

It is not possible to create subcategories of products in the Dashboard. After going to the sub section of Manage Categories, there is no button that allows me to create a sub category of product (within a category already created of course)

Subcategories are created as regular categories.
After you create a category (the one you need as a subcategory), you have to "move" it (folder icon on the top right corner) to the category you want.


Remote Test Runner

Codecov Report

Merging #230 (457ddce) into main (765a1ec) will decrease coverage by 0.31%.
The diff coverage is 11.76%.

@@            Coverage Diff             @@
##             main     #230      +/-   ##
==========================================
- Coverage   24.23%   23.91%   -0.32%
==========================================
  Files          14       14
  Lines        1795     1844      +49
==========================================
+ Hits          435      441       +6
- Misses       1325     1368      +43
  Partials       35       35

Impacted Files
Coverage Δ

client/blockchain.go
0.00% <0.00%> (ø)

client/ethereum.go
0.00% <0.00%> (ø)

gauntlet/gauntlet.go
74.25% <ø> (ø)

client/mockserver.go
100.00% <100.00%> (ø)

config/config.go
67.27% <100.00%> (+0.30%)
:arrow_up:

client/chainlink_models.go
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Settings Sync welcome screen keep showing every time when VSCode open

The box "Show this page on startup" was unchecked but it still showing every time.
🌴 Visual Studio Code Version : [ 1.41.1 ]
🌴 Code Settings Sync Version : [ 3.4.3 ]
🌴 Standard or Insiders : [ Mac ]

Same here. Is there any way to disable the welcome page entirely? Any debug I can provide?

Any movement on this?

I am seeing the same problem. Very frustrating. Is there a fix?

Hi Shanalikhan,
Yeah, it fixed, after spend nearly five days of try and error. I wrote about the fix in comment (below the question https://stackoverflow.com/questions/62248604/browsersync-on-docker-is-running-correctly-and-able-to-detect-changes-but-brows?noredirect=1#comment110147428_62248604) and you can clone the whole source code from Github https://github.com/kevinchu-work/Docker_with_BrowserSync
If you don’t mind, please give me a star on Github~~~
Enjoy!
Regards,
Kevin

On 12 Jun 2020, at 4:20 AM, Alex<EMAIL_ADDRESS>wrote:
I am seeing the same problem. Very frustrating. Is there a fix?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/shanalikhan/code-settings-sync/issues/1122#issuecomment-642906801, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHAPN2U7LOEP2BYUPRDKYFDRWE4AJANCNFSM4KHM7AWQ.

I've now switched to the built in sync settings. https://code.visualstudio.com/docs/editor/settings-sync

I've now switched to the built in sync settings. https://code.visualstudio.com/docs/editor/settings-sync

Perfect. Thanks @simax. Solved my problem.

I'm still encountering this on VS Code 1.52.1, Settings Sync 3.4.3.
I don't seem to see a built-in VS Code settings sync...? So that solution is a no-go for me.
Any development here?

Yep solved my problem too, just more information for others who didn't quite pick up what you were putting down straight away
The fix that worked for me:

Reset the settings of the "Settings Sync" extension by searching for "Reset Extension Settings" in the command palette
Upon next startup of VScode, uncheck the "Show this page on startup" button
On the next startup of VScode the page wasn't shown on startup anymore 😄

I'm using:
Settings Sync Version : 3.4.3
Visual Studio Code Version : 1.57.1
Ubuntu 20.04

Yep solved my problem too, just more information for others who didn't quite pick up what you were putting down straight away
The fix that worked for me:

Reset the settings of the "Settings Sync" extension by searching for "Reset Extension Settings" in the command palette
Upon next startup of VScode, uncheck the "Show this page on startup" button
On the next startup of VScode the page wasn't shown on startup anymore 😄

I'm using:
Settings Sync Version : 3.4.3 Visual Studio Code Version : 1.57.1 Ubuntu 20.04

@leahkemp Thank you very much, it worked for me, i use windows! 💯

Hello, I am still facing this issue. I have the sync settings turned on. Version: 1.63.2. OS Mac OS Montery

@mpiber those steps worked for me today (30-dec-21).  Thanks!

Yep solved my problem too, just more information for others who didn't quite pick up what you were putting down straight away
The fix that worked for me:

Reset the settings of the "Settings Sync" extension by searching for "Reset Extension Settings" in the command palette
Upon next startup of VScode, uncheck the "Show this page on startup" button
On the next startup of VScode the page wasn't shown on startup anymore 😄

I'm using:
Settings Sync Version : 3.4.3 Visual Studio Code Version : 1.57.1 Ubuntu 20.04

Thanks a lot!!, worked for me on VSCode latest, W10 and Ubuntu 20.04.

Yep solved my problem too, just more information for others who didn't quite pick up what you were putting down straight away
The fix that worked for me:

Reset the settings of the "Settings Sync" extension by searching for "Reset Extension Settings" in the command palette
Upon next startup of VScode, uncheck the "Show this page on startup" button
On the next startup of VScode the page wasn't shown on startup anymore 😄

I'm using:
Settings Sync Version : 3.4.3 Visual Studio Code Version : 1.57.1 Ubuntu 20.04

@leahkemp , thanks a lot!


add SX126X radio option and update driver lib

This PR updates the example to use the latest driver lib that includes SX126X support and adds the necessary options to use this radio.  A couple of examples targets are added as well to show the pinout differences from the existing sx1272,sx1276 radios.

@hasnainvirk @AnttiKauppila

Any updates on this?

Also, the forced push came from rebasing all the changes onto current master.

@bentcooke You haven't fixed my proposed changes.

@AnttiKauppila I believe your comments are addressed now regarding the default settings in mbed_app.json.


flutter/plugins needs a better releasing process

Releasing plugin updates has a few surprise gotchas right now. We could use at least some docs on it, maybe a better process.

[x] No docs or formalized sanity checks on when the packages should be released. (Presumably after CI runs on the squashed master commit and it's green? Should there be any other manual checks run, ie to make sure the version bump matches the scale of the change?) See #27106.
[ ] No automated reminders to publish a package, so it's possible to forget to publish a package entirely. See #27247 and #26374.
[x] pub publish publishes literally everything in the directory, not just what's tracked in git, so maintainers need to make sure their local directory is completely clear. (There are some cases where this is especially dangerous. in_app_purchase has an example app that needs unique release signing information stored locally to work. This is added to the .gitignore but would still be uploaded by pub if present.)
[X] Sometimes plugins are in a state where they should not be published (in_app_purchase is currently in this state while it's under intense development), and right now there's no clear way that these are marked.
[x] We probably should warn against releasing things closer to the weekend and have some suggested manual steps on how to monitor the plugin after rollout.

ETA 11/25/19:

[ ] No form of error monitoring, so it's possible to push a release and realize belatedly that it had some critical bug.

We missed publishing video_player 0.9.0 - this would have helped that.

Can we also get support for releasing updates to packages with a --token? Even if it is just for verified publishers. for example i have 20 flutter plugins and every update i need to download or locate the folder and submit the update 1 by 1.
By using a token i could set up GitHub Actions CI on a linux machine to automate my releases and testing for packages.
It would dramatically  improve how fast i can go.

@rodydavis I think that sounds like a good feature request for dart-lang/pub. This issue is just tracking how the maintainers of flutter/plugins handle publishing releases to our packages given the existing pub tooling.

Created a wrapper for pub publish and added some documentation to CONTRIBUTING.md. That addresses a lot of the points in the original issue.
The CONTRIBUTING has full information, but in summary plugins can now be released with:
$ pub global run flutter_plugin_tools publish-plugin --package $package

Closing as we have auto-publish now.


process without vscode

input 'kill code' or 'kill visual'
out nothing

Please elaborate. Not clear what you’re saying.

Please elaborate. Not clear what you’re saying.

I want to kill the vscode process, but when I enter code or visual, I don't show the corresponding APP.
thx.

Yeah, for some reason the Code application process itself doesn't show up in the process list (but all of the helper processes do).

Same here, the Visual Studio Code shows all kinds of GPU and Render processes but the main process does not show up.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1494 ms

Resolved: Bofrost.at performance has improved in a727a09 after 30 minutes.


Browser support not working

Should the browser version wrap dart sse client (https://pub.dev/documentation/sse/latest/client_sse_client/SseClient-class.html) instead of using http client?

The package was tested and intended for mobile use. Feel free to create a PR if you get it working on web.

That library uses EventSource from dart:html, which afaik is the only working way to use sse on flutter web. However, importing dart:html will raise Error: Not found when targeting at mobile platforms. And dart/flutter doesn't support conditional import, so it seems that we can't have both mobile and browser compatibility at library level.

dart/flutter doesn't support conditional import

@foxB612 I have seen conditional imports in some libraries that I use.
export 'send_port_io.dart' if (dart.library.html) 'send_port_web.dart';

These are from worker_manager package.
import 'package:worker_manager_v2/src/worker/worker_web.dart'
    if (dart.library.io) 'package:worker_manager_v2/src/worker/worker_io.dart';

@srix55 Thank you for pointing out that. I did get it wrong. According to the document conditional export/import is supported.

Is it still not working on the web? I do not receive any event until it is disconnected that they all arrive

The package was tested and intended for mobile use. Feel free to create a PR if you get it working on web.

Then remove the Web tag on pub.dev this prevents misunderstandings.

For everyone else
I found this issue regarding http on browser for streams
https://github.com/dart-lang/http/issues/593
Looks like streaming with http buffers the data first which is an issue I am hitting


feat/1206 - SDK: Adding events to shielded sync

Resolves #1206
todo

[x] export progress types - scanned/fetched/applied
[x] remove "// total is 0 so we do not get NaN"
[x] fix circular dependency in balance/services.ts
[x] export progress bar status
[x] add event payload types
[x] EventDispatcher scope type as enum?
[x] check if  options.bubbles(true); etc is needed

I'm not sure, maybe clear the old context from the IDB?

@euharrison can you take a look at last commit?  I added "off" and also added refetch so sync runs each time we go to masp tab 🙏


Is this being maintained?

Since the original repository seems to be gone, is this supposed to be its successor or just a personal fork?

Hey, this is a fork since I have a project that depends on this -- no idea what happened to the original and the one on pub will break due to null safety in Flutter 3.0.

@lrorpilla could you maybe post it to pub.dev as a separate package as the old one is no longer available?

Thanks @lrorpilla, it will be good if you can post this to pub.dev as no news from original repo

Will this maintained??

I forked this repository, fixed some stuff for newer Flutter versions and uploaded the package to pub.dev, similar to other packages of bxqm that are not maintained anymore (example: https://pub.dev/packages/implicitly_animated_reorderable_list_2). I will try to maintain it when flutter version changes make it necessary. Feel free to post any feedback you have about this package over here: https://github.com/AlwinFassbender/material_floating_search_bar

Is the new repo maintained? We can't even create issues there and it doesn't seem updated recently

@erperejildo This was forked because Alwin and I needed it for a project. That project has recently switched to the official SearchBar.
I would therefore expect that this thing is practically dead


[Age-viewer-Desktop]: Establish Backend Communication for Database Connection

[Age-viewer-Desktop]: Establish Backend Communication for Database Connection

@aked21 Please merge


Improved aarch64 build

- What I did
Fixed some issue that prevented me from running make all on aarch64.
- How I did it
Updated Dockerfile.aarch64to include a few things that are included in the files for other platforms:

golint
yamllint
swagger

I've also updated man/Dockerfile.aarch64 so that it bootstraps its own Go 1.7.5. Go 1.6.x is not sufficient anymore due to the fact that context was moved out of experimental.
- How to verify it
Run make all on an aarch64 platform should work except for a few unrelated test issues.
- Description for the changelog
Fixed issues that prevented make all to run properly on aarch64.

@tophj-ibm I believe this PR is much more relevant to fixing #31061 than the changes in #31193.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master-manpages-aarch64" git@github.com:docbobo/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354215504
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

I probably don't understand the vetting process well, but why is this still on status/0-triageif all tests executed correctly?

@docbobo it's a manual process :)

@docbobo @tophj-ibm so which one should we merge this one or https://github.com/docker/docker/pull/31193 ?

Well, this one is fixing #31061, but #31193 seems to be the more important change. Thus my preference would be on #31193. @tophj-ibm?

@vieux I saw them as separate issues so I asked him to split them, maybe that just caused confusion.
This one is an extension of #30755 and provides a fix for make validate, and make manpages for aarch64 which is already broken and should be merged as soon as it looks good.
#31193 is for adding make deb support for debian:jessie on aarch64, which still needs some consensus around if it's okay to merge without seccomp support.

this should also be cherry-picked in the 17.03.x branch

ah ok got it.

ping @cpuguy83 @tianon

@tophj-ibm was the cherry-picking comment supposed to cover both PRs?

@docbobo no, this one is a bug fix and should go into the next point release.
The other is more of a feature request which should go into the next version release if it gets merged. Note, I'm not a maintainer, but they probably agree with me 😄

quick question about an undocumented change: why going back from Xenial (current LTS) to Wily in man/Dockerfile.aarch64? Note: the bootstrap is still necessary.

I moved this back to 17.04

I am currently testing with xenial instead of wily...

It's not really a blocker, but I was comparing this to a few of the other platforms and I'm curious whether some of the deviations are still justified?
Dockerfile.armhf:
$ diff -u <(curl -fsSL 'https://raw.githubusercontent.com/docker/docker/master/Dockerfile.armhf') <(curl -fsSL 'https://raw.githubusercontent.com/docbobo/docker/cdf17e6943b15103b37fd57da7c2729a26ecb674/Dockerfile.aarch64')
--- /dev/fd/63	2017-02-28 10:08:14.114649827 -0800
+++ /dev/fd/62	2017-02-28 10:08:14.115649796 -0800
@@ -1,9 +1,9 @@
-# This file describes the standard way to build Docker on ARMv7, using docker
+# This file describes the standard way to build Docker on aarch64, using docker
 #
 # Usage:
 #
 # # Assemble the full dev environment. This is slow the first time.
-# docker build -t docker -f Dockerfile.armhf .
+# docker build -t docker -f Dockerfile.aarch64 .
 #
 # # Mount your source in an interactive container for quick testing:
 # docker run -v `pwd`:/go/src/github.com/docker/docker --privileged -i -t docker bash
@@ -15,11 +15,7 @@
 # the case. Therefore, you don't have to disable it anymore.
  The first is an older version that
-# only supports schema1 manifests. The second is a newer version that supports
-# both. This allows integration-cli tests to cover push/pull with both schema1
-# and schema2 manifests.
-ENV REGISTRY_COMMIT_SCHEMA1 ec87e9b6971d831f0eff752ddb54fb64693e51cd
-ENV REGISTRY_COMMIT cb08de17d74bef86ce6c5abe8b240e282f5750be
+# Install Go
+# We don't have official binary tarballs for ARM64, eigher for Go or bootstrap,
+# so we use gccgo as bootstrap to build Go from source code.
+# We don't use the official ARMv6 released binaries as a GOROOT_BOOTSTRAP, because
+# not all ARM64 platforms support 32-bit mode. 32-bit mode is optional for ARMv8.
+ENV GO_VERSION 1.7.5
+RUN mkdir /usr/src/go && curl -fsSL https://golang.org/dl/go${GO_VERSION}.src.tar.gz | tar -v -C /usr/src/go -xz --strip-components=1 \
+	&& cd /usr/src/go/src \
+	&& GOOS=linux GOARCH=arm64 GOROOT_BOOTSTRAP="$(go env GOROOT)" ./make.bash
+
+ENV PATH /go/bin:/usr/src/go/bin:$PATH
+ENV GOPATH /go
+
+# Dependency for golint
+ENV GO_TOOLS_COMMIT 823804e1ae08dbb14eb807afc7db9993bc9e3cc3
+RUN git clone https://github.com/golang/tools.git /go/src/golang.org/x/tools \
+	&& (cd /go/src/golang.org/x/tools && git checkout -q $GO_TOOLS_COMMIT)
+
+# Grab Go's lint tool
+ENV GO_LINT_COMMIT 32a87160691b3c96046c0c678fe57c5bef761456
+RUN git clone https://github.com/golang/lint.git /go/src/github.com/golang/lint \
+	&& (cd /go/src/github.com/golang/lint && git checkout -q $GO_LINT_COMMIT) \
+	&& go install -v github.com/golang/lint/golint
+
+# Only install one version of the registry, because old version which support
+# schema1 manifests is not working on ARM64, we should skip integration-cli
+# tests for schema1 manifests on ARM64.
+ENV REGISTRY_COMMIT 47a064d4195a9b56133891bbb13620c3ac83a827
 RUN set -x \
 	&& export GOPATH="$(mktemp -d)" \
 	&& git clone https://github.com/docker/distribution.git "$GOPATH/src/github.com/docker/distribution" \
 	&& (cd "$GOPATH/src/github.com/docker/distribution" && git checkout -q "$REGISTRY_COMMIT") \
 	&& GOPATH="$GOPATH/src/github.com/docker/distribution/Godeps/_workspace:$GOPATH" \
 		go build -o /usr/local/bin/registry-v2 github.com/docker/distribution/cmd/registry \
-	&& (cd "$GOPATH/src/github.com/docker/distribution" && git checkout -q "$REGISTRY_COMMIT_SCHEMA1") \
-	&& GOPATH="$GOPATH/src/github.com/docker/distribution/Godeps/_workspace:$GOPATH" \
-		go build -o /usr/local/bin/registry-v2-schema1 github.com/docker/distribution/cmd/registry \
 	&& rm -rf "$GOPATH"

 # Install notary and notary-server
@@ -143,6 +147,15 @@
 	&& git checkout -q $DOCKER_PY_COMMIT \
 	&& pip install -r test-requirements.txt

+# Install yamllint for validating swagger.yaml
+RUN pip install yamllint==1.5.0
+
+# Install go-swagger for validating swagger.yaml
+ENV GO_SWAGGER_COMMIT c28258affb0b6251755d92489ef685af8d4ff3eb
+RUN git clone https://github.com/go-swagger/go-swagger.git /go/src/github.com/go-swagger/go-swagger \
+	&& (cd /go/src/github.com/go-swagger/go-swagger && git checkout -q $GO_SWAGGER_COMMIT) \
+	&& go install -v github.com/go-swagger/go-swagger/cmd/swagger
+
 # Set user.email so crosbymichael's in-container merge commits go smoothly
 RUN git config --global user.email<EMAIL_ADDRESS>
@@ -163,10 +176,10 @@
 # Get useful and necessary Hub images so we can "docker load" locally instead of pulling
 COPY contrib/download-frozen-image-v2.sh /go/src/github.com/docker/docker/contrib/
 RUN ./contrib/download-frozen-image-v2.sh /docker-frozen-images \
-	armhf/buildpack-deps:jessie@sha256:ca6cce8e5bf5c952129889b5cc15cd6aa8d995d77e55e3749bbaadae50e476cb \
-	armhf/busybox:latest@sha256:d98a7343ac750ffe387e3d514f8521ba69846c216778919b01414b8617cfb3d4 \
-	armhf/debian:jessie@sha256:4a2187483f04a84f9830910fe3581d69b3c985cc045d9f01d8e2f3795b28107b \
-	armhf/hello-world:latest@sha256:161dcecea0225975b2ad5f768058212c1e0d39e8211098666ffa1ac74cfb7791
+	aarch64/buildpack-deps:jessie@sha256:6aa1d6910791b7ac78265fd0798e5abd6cb3f27ae992f6f960f6c303ec9535f2 \
+	aarch64/busybox:latest@sha256:b23a6a37cf269dff6e46d2473b6e227afa42b037e6d23435f1d2bc40fc8c2828 \
+	aarch64/debian:jessie@sha256:4be74a41a7c70ebe887b634b11ffe516cf4fcd56864a54941e56bb49883c3170 \
+	aarch64/hello-world:latest@sha256:65a4a158587b307bb02db4de41b836addb0c35175bdc801367b1ac1ddeb9afda
 # See also "hack/make/.ensure-frozen-images" (which needs to be updated any time this list is)

 # Install tomlv, vndr, runc, containerd, tini, docker-proxy
@@ -175,6 +188,7 @@
 COPY hack/dockerfile/install-binaries.sh /tmp/install-binaries.sh
 RUN /tmp/install-binaries.sh tomlv vndr runc containerd tini proxy

+# Wrap all commands in the "docker-in-docker" script to allow nested containers
 ENTRYPOINT ["hack/dind"]

 # Upload docker source

Dockerfile.s390x:
$ diff -u <(curl -fsSL 'https://raw.githubusercontent.com/docker/docker/master/Dockerfile.s390x') <(curl -fsSL 'https://raw.githubusercontent.com/docbobo/docker/cdf17e6943b15103b37fd57da7c2729a26ecb674/Dockerfile.aarch64')
--- /dev/fd/63	2017-02-28 10:08:26.504275598 -0800
+++ /dev/fd/62	2017-02-28 10:08:26.504275598 -0800
@@ -1,9 +1,9 @@
-# This file describes the standard way to build Docker on s390x, using docker
+# This file describes the standard way to build Docker on aarch64, using docker
 #
 # Usage:
 #
 # # Assemble the full dev environment. This is slow the first time.
-# docker build -t docker -f Dockerfile.s390x .
+# docker build -t docker -f Dockerfile.aarch64 .
 #
 # # Mount your source in an interactive container for quick testing:
 # docker run -v `pwd`:/go/src/github.com/docker/docker --privileged -i -t docker bash
@@ -15,12 +15,11 @@
 # the case. Therefore, you don't have to disable it anymore.
 #

-FROM s390x/debian:jessie
+FROM aarch64/ubuntu:xenial

 # Packaged dependencies
 RUN apt-get update && apt-get install -y \
 	apparmor \
-	apt-utils \
 	aufs-tools \
 	automake \
 	bash-completion \
@@ -30,41 +29,31 @@
 	createrepo \
 	curl \
 	dpkg-sig \
+	g++ \
+	gcc \
 	git \
 	iptables \
 	jq \
-	net-tools \
 	libapparmor-dev \
+	libc6-dev \
 	libcap-dev \
 	libltdl-dev \
-	libsystemd-journal-dev \
-	libtool \
+	libsystemd-dev \
+	libyaml-dev \
 	mercurial \
+	net-tools \
+	parallel \
 	pkg-config \
 	python-dev \
 	python-mock \
 	python-pip \
 	python-websocket \
-	xfsprogs \
-	tar \
+	gccgo \
+	iproute2 \
+	iputils-ping \
 	vim-common \
 	--no-install-recommends

-# Install seccomp: the version shipped in jessie is too old
-ENV SECCOMP_VERSION 2.3.1
-RUN set -x \
-	&& export SECCOMP_PATH="$(mktemp -d)" \
-	&& curl -fsSL "https://github.com/seccomp/libseccomp/releases/download/v${SECCOMP_VERSION}/libseccomp-${SECCOMP_VERSION}.tar.gz" \
-		| tar -xzC "$SECCOMP_PATH" --strip-components=1 \
-	&& ( \
-		cd "$SECCOMP_PATH" \
-		&& ./configure --prefix=/usr/local \
-		&& make \
-		&& make install \
-		&& ldconfig \
-	) \
-	&& rm -rf "$SECCOMP_PATH"
-
 # Get lvm2 source for compiling statically
 ENV LVM2_VERSION 2.02.103
 RUN mkdir -p /usr/local/lvm2 \
@@ -72,7 +61,7 @@
 		| tar -xzC /usr/local/lvm2 --strip-components=1
 # See https://git.fedorahosted.org/cgit/lvm2.git/refs/tags for release tags

-# Fix platform enablement in lvm2 to support s390x properly
+# Fix platform enablement in lvm2 to support aarch64 properly
 RUN set -e \
 	&& for f in config.guess config.sub; do \
 		curl -fsSL -o "/usr/local/lvm2/autoconf/$f" "http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=$f;hb=HEAD"; \
@@ -88,11 +77,32 @@
 	&& make install_device-mapper
 # See https://git.fedorahosted.org/cgit/lvm2.git/tree/INSTALL

+# Install seccomp: the version shipped in trusty is too old
+ENV SECCOMP_VERSION 2.3.1
+RUN set -x \
+	&& export SECCOMP_PATH="$(mktemp -d)" \
+	&& curl -fsSL "https://github.com/seccomp/libseccomp/releases/download/v${SECCOMP_VERSION}/libseccomp-${SECCOMP_VERSION}.tar.gz" \
+		| tar -xzC "$SECCOMP_PATH" --strip-components=1 \
+	&& ( \
+		cd "$SECCOMP_PATH" \
+		&& ./configure --prefix=/usr/local \
+		&& make \
+		&& make install \
+		&& ldconfig \
+	) \
+	&& rm -rf "$SECCOMP_PATH"
+
+# Install Go
+# We don't have official binary tarballs for ARM64, eigher for Go or bootstrap,
+# so we use gccgo as bootstrap to build Go from source code.
+# We don't use the official ARMv6 released binaries as a GOROOT_BOOTSTRAP, because
+# not all ARM64 platforms support 32-bit mode. 32-bit mode is optional for ARMv8.
 ENV GO_VERSION 1.7.5
-RUN curl -fsSL "https://golang.org/dl/go${GO_VERSION}.linux-s390x.tar.gz" \
-	| tar -xzC /usr/local
+RUN mkdir /usr/src/go && curl -fsSL https://golang.org/dl/go${GO_VERSION}.src.tar.gz | tar -v -C /usr/src/go -xz --strip-components=1 \
+	&& cd /usr/src/go/src \
+	&& GOOS=linux GOARCH=arm64 GOROOT_BOOTSTRAP="$(go env GOROOT)" ./make.bash

-ENV PATH /go/bin:/usr/local/go/bin:$PATH
+ENV PATH /go/bin:/usr/src/go/bin:$PATH
 ENV GOPATH /go

 # Dependency for golint
@@ -106,11 +116,9 @@
 	&& (cd /go/src/github.com/golang/lint && git checkout -q $GO_LINT_COMMIT) \
 	&& go install -v github.com/golang/lint/golint

-# Install two versions of the registry. The first is an older version that
-# only supports schema1 manifests. The second is a newer version that supports
-# both. This allows integration-cli tests to cover push/pull with both schema1
-# and schema2 manifests.
-ENV REGISTRY_COMMIT_SCHEMA1 ec87e9b6971d831f0eff752ddb54fb64693e51cd
+# Only install one version of the registry, because old version which support
+# schema1 manifests is not working on ARM64, we should skip integration-cli
+# tests for schema1 manifests on ARM64.
  This is slow the first time.
-# docker build -t docker .
+# docker build -t docker -f Dockerfile.aarch64 .
 #
 # # Mount your source in an interactive container for quick testing:
 # docker run -v `pwd`:/go/src/github.com/docker/docker --privileged -i -t docker bash
@@ -11,76 +11,49 @@
 # # Run the test suite:
 # docker run --privileged docker hack/make.sh test-unit test-integration-cli test-docker-py
 #
-# # Publish a release:
-# docker run --privileged \
-#  -e AWS_S3_BUCKET=baz \
-#  -e AWS_ACCESS_KEY=foo \
-#  -e AWS_SECRET_KEY=bar \
-#  -e GPG_PASSPHRASE=gloubiboulga \
-#  docker hack/release.sh
-#
 # Note: AppArmor used to mess with privileged mode, but this is no longer
 # the case. Therefore, you don't have to disable it anymore.
  Ping #docker-maintainers on IRC
-#            with a heads-up.
+# We don't have official binary tarballs for ARM64, eigher for Go or bootstrap,
+# so we use gccgo as bootstrap to build Go from source code.
+# We don't use the official ARMv6 released binaries as a GOROOT_BOOTSTRAP, because
+# not all ARM64 platforms support 32-bit mode. 32-bit mode is optional for ARMv8.
 ENV GO_VERSION 1.7.5
-RUN curl -fsSL "https://golang.org/dl/go${GO_VERSION}.linux-amd64.tar.gz" \
-	| tar -xzC /usr/local
+RUN mkdir /usr/src/go && curl -fsSL https://golang.org/dl/go${GO_VERSION}.src.tar.gz | tar -v -C /usr/src/go -xz --strip-components=1 \
+	&& cd /usr/src/go/src \
+	&& GOOS=linux GOARCH=arm64 GOROOT_BOOTSTRAP="$(go env GOROOT)" ./make.bash

-ENV PATH /go/bin:/usr/local/go/bin:$PATH
+ENV PATH /go/bin:/usr/src/go/bin:$PATH
 ENV GOPATH /go

-# Compile Go for cross compilation
-ENV DOCKER_CROSSPLATFORMS \
-	linux/386 linux/arm \
-	darwin/amd64 \
-	freebsd/amd64 freebsd/386 freebsd/arm \
-	windows/amd64 windows/386 \
-	solaris/amd64
-
 # Dependency for golint
 ENV GO_TOOLS_COMMIT 823804e1ae08dbb14eb807afc7db9993bc9e3cc3
 RUN git clone https://github.com/golang/tools.git /go/src/golang.org/x/tools \
@@ -153,19 +116,9 @@
 	&& (cd /go/src/github.com/golang/lint && git checkout -q $GO_LINT_COMMIT) \
 	&& go install -v github.com/golang/lint/golint

-# Install CRIU for checkpoint/restore support
-ENV CRIU_VERSION 2.9
-RUN mkdir -p /usr/src/criu \
-	&& curl -sSL https://github.com/xemul/criu/archive/v${CRIU_VERSION}.tar.gz | tar -v -C /usr/src/criu/ -xz --strip-components=1 \
-	&& cd /usr/src/criu \
-	&& make \
-	&& make install-criu
-
-# Install two versions of the registry. The first is an older version that
-# only supports schema1 manifests. The second is a newer version that supports
-# both. This allows integration-cli tests to cover push/pull with both schema1
-# and schema2 manifests.
-ENV REGISTRY_COMMIT_SCHEMA1 ec87e9b6971d831f0eff752ddb54fb64693e51cd
+# Only install one version of the registry, because old version which support
+# schema1 manifests is not working on ARM64, we should skip integration-cli
+# tests for schema1 manifests on ARM64.
 ENV REGISTRY_COMMIT 47a064d4195a9b56133891bbb13620c3ac83a827
 RUN set -x \
 	&& export GOPATH="$(mktemp -d)" \
@@ -173,9 +126,6 @@
 	&& (cd "$GOPATH/src/github.com/docker/distribution" && git checkout -q "$REGISTRY_COMMIT") \
 	&& GOPATH="$GOPATH/src/github.com/docker/distribution/Godeps/_workspace:$GOPATH" \
 		go build -o /usr/local/bin/registry-v2 github.com/docker/distribution/cmd/registry \
-	&& (cd "$GOPATH/src/github.com/docker/distribution" && git checkout -q "$REGISTRY_COMMIT_SCHEMA1") \
-	&& GOPATH="$GOPATH/src/github.com/docker/distribution/Godeps/_workspace:$GOPATH" \
-		go build -o /usr/local/bin/registry-v2-schema1 github.com/docker/distribution/cmd/registry \
 	&& rm -rf "$GOPATH"

 # Install notary and notary-server
@@ -219,8 +169,6 @@

 # Let us use a .bashrc file
 RUN ln -sfv $PWD/.bashrc ~/.bashrc
-# Add integration helps to bashrc
-RUN echo "source $PWD/hack/make/.integration-test-helpers" >> /etc/bash.bashrc

 # Register Docker's bash completion.
 RUN ln -sv $PWD/contrib/completion/bash/docker /etc/bash_completion.d/docker
@@ -228,17 +176,17 @@
 # Get useful and necessary Hub images so we can "docker load" locally instead of pulling
 COPY contrib/download-frozen-image-v2.sh /go/src/github.com/docker/docker/contrib/
 RUN ./contrib/download-frozen-image-v2.sh /docker-frozen-images \
-	buildpack-deps:jessie@sha256:25785f89240fbcdd8a74bdaf30dd5599a9523882c6dfc567f2e9ef7cf6f79db6 \
-	busybox:latest@sha256:e4f93f6ed15a0cdd342f5aae387886fba0ab98af0a102da6276eaf24d6e6ade0 \
-	debian:jessie@sha256:f968f10b4b523737e253a97eac59b0d1420b5c19b69928d35801a6373ffe330e \
-	hello-world:latest@sha256:8be990ef2aeb16dbcb9271ddfe2610fa6658d13f6dfb8bc72074cc1ca36966a7
+	aarch64/buildpack-deps:jessie@sha256:6aa1d6910791b7ac78265fd0798e5abd6cb3f27ae992f6f960f6c303ec9535f2 \
+	aarch64/busybox:latest@sha256:b23a6a37cf269dff6e46d2473b6e227afa42b037e6d23435f1d2bc40fc8c2828 \
+	aarch64/debian:jessie@sha256:4be74a41a7c70ebe887b634b11ffe516cf4fcd56864a54941e56bb49883c3170 \
+	aarch64/hello-world:latest@sha256:65a4a158587b307bb02db4de41b836addb0c35175bdc801367b1ac1ddeb9afda
 # See also "hack/make/.ensure-frozen-images" (which needs to be updated any time this list is)

 # Install tomlv, vndr, runc, containerd, tini, docker-proxy
 # Please edit hack/dockerfile/install-binaries.sh to update them.
 COPY hack/dockerfile/binaries-commits /tmp/binaries-commits
 COPY hack/dockerfile/install-binaries.sh /tmp/install-binaries.sh
-RUN /tmp/install-binaries.sh tomlv vndr runc containerd tini proxy bindata
+RUN /tmp/install-binaries.sh tomlv vndr runc containerd tini proxy

 # Wrap all commands in the "docker-in-docker" script to allow nested containers
 ENTRYPOINT ["hack/dind"]

(Just as a point of further thought, etc -- not at all a blocker :heart:)

@tianon that's a good point, the dockerfiles in general definitely need some cleanup.
Just a few things I saw when checking out the diffs regarding cleanup.

Figure out what packages aren't needed anymore. The non-x86 dockerfiles have switched bases a couple of times so there are extra packages that probably aren't needed anymore

sync gopaths, some use /usr/src/go some use /usr/local/go, the latter preferred by go.

Add yamllint and go-swagger to other dockerfiles

Add CRIU for checkpoint restore to other architectures. Might be a blocker here depending on if it's supported everywhere.

IMO none of these need to happen here. make all is currently broken on aarch64 and I think fixing that before next release is most important. I can take a swing at the above in another PR though.

Agreed! Thanks for putting some thought on it ❤

Minor nit, he comment in the file about libseccomp is not quite correct, the version is not too old, but I don't think it ships with the static library for a static build.

@justincormack: the comment you are referring to wasn't changed, it's already in the base version of the file. As a fact of the matter, it's like that in the Dockerfiles for three other architectures as well, including x86.
My suggestion would be to keep it like that because it makes comparing the different Dockerfiles a little bit easier, and there seems to be the desire to perform some overall cleanup.
Let me know if you disagree and I'll happily fix that.

I had to make a few more changes as building failed this morning (while working last night). It seems that aarch64/ubuntu:latest was updated within the last 12 hours, and I am suspicious that this is the root cause.

ping @justincormack @tophj-ibm PTAL

LGTM


reflect: New hits a RWMutex for types with no ptrToThis field

In Go 1.7 I attempted to remove the ptrToThis field from reflect.rtype. It caused regressions, so I brought it back.
However I didn't completely bring it back. We used to include a ptrToThis value for any type where the pointer is used in the final program. Now we only include it for a subset of types (named values with methods).
This means a greater set of types hit a slow path in reflect.New, which slows down packages like the protocol buffer decoder.
A fix is to partially revert CL 20287 and CL 19695.

David, what's the status here?
/cc @ianlancetaylor @rsc

CL 33411 by @ianlancetaylor resolves this. I have a partial CL re-introducing weak symbols that I could get going, but I prefer the general approach in 33411.

As I mentioned to David already, I think weak symbols are always a win, but that CL 33411 is only sometimes a win.  And CL 33411 is not for 1.8 anyhow.  So I think we do want weak symbols.


Pyramid view detection doesn't take grid mode into account

🐛 Bug
You're gonna love this one, @sofroniewn! 😂 Co-discovered by @DragaDoncila.
To Reproduce
Steps to reproduce the behavior:
import numpy as np
import napari
pyramid0 = [np.random.random((4096 // 2**i, 4096 // 2**i)) for i in range(5)]
pyramid1 = [np.random.random((4096 // 2**i, 4096 // 2**i)) for i in range(5)]
v = napari.Viewer()
v.add_image(pyramid0, cmap='green')
v.add_image(pyramid0, colormap='green')
v.add_image(pyramid1, colormap='magenta', blending='additive')

Then enter grid mode and pan around.
Actual behavior

Expected behavior
Pyramid data should work fine in grid mode.

Sigh, indeed, this doesn't surprise me. Will add to my To Do's :-)
I want to pull out the grid stuff from the layer itself, but we don't have a nice place to put it now. In the sort term the fix is probably just needing to make sure some coordinate info passes through the inverse of the grid transform, but I'll need to check to be sure

This has been closed by #1673


Properly encode/decode the percentage character (% -> %25) across browsers and upon initial navigation

Currently, the percentage character creates multiple issues and inconsistencies. This is partly due to:

the % is forbidden as part of the pathname in the URL per its spec (https://url.spec.whatwg.org/#path-state) if not escaped
IE allows it because it follows a different spec (https://tools.ietf.org/html/rfc3986#section-2.4)

In Vue router, we have multiple inconsistencies between asterisk path, param paths and regular path regarding escaping these characters and whether the navigation is initial or triggered by a push/router-link
Given this set of routes in history mode
[
  { path: '/foo/:p', component: Foo },
  {
    path: '*',
    component: Other,
  },
]

History mode / Chrome, IE 11,10

to
route match
href produced in router-link
$router info after clicking
$router info on direct navigation
remarks

/%7D
*
/%7D
/%7D - /}
/} - /}
User should write /} as the link instead

/}
*
/%7D
/} - /}
N/A (browser should encode it te be /%7D)
-

/%25
*
/%25
/%25 - /%
ERROR
Navigation should be possible. Should user also write /% to be consistent?

/%
*
ERROR
N/A (not working)
N/A (not valid)
Or should they escape the percent themselves because it's the only special character

/foo/%7D
/foo/:p
/%7D
/%7D - p = }
/} - p = }
User should write /foo/}

/foo/}
/foo/:p
/%7D
/} - p = }
/} - p = }

/foo/%25
/foo/:p
/%25
/%25 - p = %
ERROR
Navigation should be possible

Hash mode / TODO
Query / TODO

Complete html file to test. Requires a vue-router.js file in the same folder
index.html
<!DOCTYPE html>

    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta http-equiv="X-UA-Compatible" content="ie=edge" />
    <title>Document</title>

{{ $route.path }}

{{ $route.params }}

      <router-link to="/">/home</router-link>
      <router-link to="/%7D">/%7D</router-link>
      <router-link to="/}">/}</router-link>
      <router-link to="/%25">/%25</router-link>

      <router-link to="/foo/%7D">/foo/%7D</router-link>
      <router-link to="/foo/}">/foo/}</router-link>

      <router-link to="/foo/%25">/foo/%25</router-link>
      <router-view></router-view>

In most cases, we can avoid using special characters in development. But if we got decode error, I think we should catch it manually and try to find the closest asterisk match.

I recommend adding the following testcases, which seem to be extra nasty:
"/ "
"/%20"
"/%2520"
"/\n"
"/%0a"
"/%250a"

Also, this should be tested with server-side-rendering

Not sure, if this is the same issue, but initial navigation for routes with percent-encoded characters does not work. The problem was initially reported in https://github.com/nextcloud/tasks/issues/479.
Have a look at this example:
<!DOCTYPE html>

    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta http-equiv="X-UA-Compatible" content="ie=edge" />
    <title>Document</title>

      <router-link
        v-for="item in items"
        :to="{name: 'items', params: {itemId: item.id }}"
        :key="item.id"
      >
        Go to {{ item.name }}
      </router-link>
      <router-view></router-view>

Clicking the links works fine, the correct item is loaded and the route-view shows the correct item. But if you reload the page after clicking on Go to Item 3, the item is not found, because on initial navigation the url is not encoded the same way as on router.push.
I would appreciate some feedback if this is the same issue described here or not. Thanks a lot!

    onDecode: (req) => {
      let url = req.url
      try {
        url = decodeURI(req.url)
      }
      catch (error) {
        // Rethrow error
        if (error.message !== 'URI malformed') {
          throw error
        }
        url = decodeURI(unescape(req.url))
        // Fix url also on Nuxt side
        req.url = url
      }
      return url
    }

I had issues with ISO urls and fixed it like that.

@alanaasmaa May I ask where to put / how to use onDecode?

@alanaasmaa May I ask where to put / how to use onDecode?

@raimund-schluessler You have to use a version that is not yet released.
So in package.json > "@nuxtjs/redirect-module": "nuxt-community/redirect-module#master"
Then in nuxt config

  redirect: {
    rules: [
      { from: /^\/page(?:\/?)(?:\?(.*))?$/, to: '/?$1' },
    ],
    onDecode: (req) => {
      let url = req.url
      try {
        url = decodeURI(req.url)
      }
      catch (error) {
        // Rethrow error
        if (error.message !== 'URI malformed') {
          throw error
        }
        url = decodeURI(unescape(req.url))
        // Fix url also on Nuxt side
        req.url = url
      }
      return url
    },
    onDecodeError: (error, req, res, next) => next(error)

Simpler test file with steps to reproduce:

Load the index.html app below
Click on the button, vue router will happily navigate to the route which contains the '%' sign.
Hard-refresh the page
The app won't load, console produces the following error:

[Vue warn]: Error in beforeCreate hook: "URIError: malformed URI sequence"

(found in <Root>) vue.js:634:17
URIError: "malformed URI sequence"
    matchRoute https://unpkg.com/vue-router/dist/vue-router.js:1591
    match https://unpkg.com/vue-router/dist/vue-router.js:1463
    match https://unpkg.com/vue-router/dist/vue-router.js:2656
    transitionTo https://unpkg.com/vue-router/dist/vue-router.js:1995
    init https://unpkg.com/vue-router/dist/vue-router.js:2701
    beforeCreate https://unpkg.com/vue-router/dist/vue-router.js:1192
    VueJS 4
    <anonymous> file:///.../index.html#/tag/this-is-a-test-tag-%:37
vue.js:1897:15
[Vue warn]: Error in render: "TypeError: route is undefined"

(found in <Root>) vue.js:634:17
TypeError: "route is undefined"
    render https://unpkg.com/vue-router/dist/vue-router.js:93
    VueJS 15
    <anonymous> file:///.../index.html#/tag/this-is-a-test-tag-%:37

index.html

	<meta charset="UTF-8">

I open a PR for this issue, can you review please ? https://github.com/vuejs/vue-router/pull/3213

I've seen the issue has been fixed on 4.x. It is expected to be fixed on the current release 3.3.X? If not, is there a release date for v4.x (I could not manage to find it)?
I have  some projects which I have to deliver soon, and I would apreciate the information in order to wait for the fix, or trying to remove the percentatge from the path params; which will cause me many troubles :).
Thank you very much

v4 is for Vue 3, it already exist under the next tag. Nobody is working on a fix for this right now, so contributions are welcome but there is no date


add spooky video background, update styles to match, see description

Add spooky video background.
Update text styles to match; clean-up CSS.
Add site border matching text color (desktop-only).

FYI: This is in reference to Issue #1.


HHH-17253 - Fix for StackOverflowError in static metamodel generator

https://hibernate.atlassian.net/browse/HHH-17253

Oh, I'm very surprised that this is necessary!

I created the PR so that Christian could have a look, the fix isn't definitive (and also atm incorrect)

So there can be cycles in a type expression? I would not have expected that at all.

Well, picture something like this: Set where the type variable is defined as TRoleAccess extends RoleAccess<TRoleAccess,TUser,TRole>>, this goes into an infinte loop atm. Still working it out.

Ah, right, of course! I should have thought of that.

Superseded by https://github.com/hibernate/hibernate-orm/pull/7650


Feature Request: Helper like Send but for sending & receiving data in binary.

Hi,
I think it would be helpful for this package to provide a helper similar to Send but for making an XHR that sends and receives data in binary format.
The topic of XHR and binary data is described somewhat at https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/Sending_and_Receiving_Binary_Data.
// SendBinary constructs a new Request, sends the binary data,
// and returns the response and error.
func SendBinary(method, url string, data []byte) ([]byte, error)

The motivation is twofold:

In the context of Go code, I personally see much more usefulness and predictability in making binary requests every time. I am likely working with io.Reader or bytes.Buffer or just string, but I would much rather send bytes as they are and receive them as they are, not worrying about text encoding.

Go's net/http package requests and responses are typically binary data in the forms of io.Reader or []byte.

Making XHR requests using binary is relatively complicated, verbose and error prone. Offering this functionality as part of this package would be helpful.

See examples where xhr.NewRequest is used instead of xhr.Send only because binary transfer is required:

https://github.com/gopherjs/gopherjs.github.io/blob/master/playground/playground.go (multiple times), also see  https://github.com/gopherjs/gopherjs.github.io/pull/17#issue-53974618.

https://github.com/shurcooL/goglfw/blob/487a1a44690c599c20b18a15a8ad7ee644f34c7f/browser.go#L324-L332

Thank you!

Is this still required now that Send supports []byte? Do we need to set any options?

Now that Send supports []byte, the need/usefulness of this helper goes down, but I think it's still high enough that adding it is worth it. It would replace all my uses of NewRequest and setting ResponseType to ArrayBuffer and doing the cast from ArrayBuffer to []byte:
// My current code whenever I want to make a binary XHR:
req := xhr.NewRequest("POST", url)
req.ResponseType = xhr.ArrayBuffer

err := req.Send(data)
if err != nil {
	return nil, err
}

out := js.Global.Get("Uint8Array").New(req.Response).Interface().([]byte)

// With BinarySend it becomes:
b := xhr.SendBinary("POST", url, data)

What do you think?

Okay, so first it should be noted that now SendBinary isn't about sending binary (as Send with []byte does sending just fine), but about receiving a binary response. I can see the merit in that.
A quick question about the specific implementation, however: What's the type of req.Response that Uint8Array.new is required? What would be the result of req.Response.Interface()?

Yes, SendBinary both sends and receives response in binary.
I'll respond to your other question in a bit, gotta relocate atm.

Now to answer your other question (after doing some confirmation),

What's the type of req.Response ...? What would be the result of req.Response.Interface()?

Its JavaScript type is ArrayBuffer, since that type was requested via req.ResponseType = xhr.ArrayBuffer.
If you look at the table at http://godoc.org/github.com/gopherjs/gopherjs/js, there is no specific entry for ArrayBuffer in the "JavaScript type" column, hence ArrayBuffer ends up being considered as instanceof Object. Therefore, its conversion to interface{} dynamic type is map[string]interface{}.
From empirical testing, doing b := req.Response.Interface().([]byte) results in:
Uncaught Error: interface conversion: interface is map[string]interface {}, not []uint8

What's the type of req.Response that Uint8Array.new is required?

By creating an ArrayBufferView of Uint8Array kind on top of ArrayBuffer, we get the []byte internalization that we're looking for.
A few data points:

https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/Sending_and_Receiving_Binary_Data has this snippet:

Receiving binary data using JavaScript typed arrays
The responseType property of the XMLHttpRequest object can be set to change the expected response type from the server. Possible values are the empty string (default), "arraybuffer", "blob", "document", "json", and "text". The response property will contain the entity body according to responseType, as an ArrayBuffer, Blob, Document, JSON, or string. This is null if the request is not complete or was not successful.

This example reads an image as a binary file and creates an 8-bit unsigned integer array from the raw bytes.
var oReq = new XMLHttpRequest();
oReq.open("GET", "/myfile.png", true);
oReq.responseType = "arraybuffer";

oReq.onload = function (oEvent) {
  var arrayBuffer = oReq.response; // Note: not oReq.responseText
  if (arrayBuffer) {
    var byteArray = new Uint8Array(arrayBuffer);
    for (var i = 0; i < byteArray.byteLength; i++) {
      // do something with each byte in the array
    }
  }
};

oReq.send(null);

Richard originally wrote the same code in the GopherJS Playground, see https://github.com/gopherjs/gopherjs.github.io/commit/74faf83c58c7c4a094e720130cb2afbe6f0d291f.

I can see the merit in that.

IMO the biggest benefit of having something so commonly needed (sending and receiving binary byte slices via XHR) here is that it will get this much scrutiny and eyes, compared to it being done in many places within people's codebases.

At this point, I'm primarily wondering if we should be adding SendBinary, or if Send should be changed to behave like SendBinary instead. In pure Go, a string's encoding is irrelevant in data transmission, it's considered an immutable byte slice.
Is there a common scenario in which one would want to send data as text, and expect it to be transformed to be valid UTF-8 (by e.g. replacing invalid bytes with replacement runes)? If not, I'd change Send to return []byte instead of string, and to convert string data to []byte before sending it.

See<PHONE_NUMBER>94df1b4639026075e0a21a52dcda1a for what I have in mind.

At this point, I'm primarily wondering if we should be adding SendBinary, or if Send should be changed to behave like SendBinary instead. In pure Go, a string's encoding is irrelevant in data transmission, it's considered an immutable byte slice.

I would prefer the latter; it would keep the API shorter and more useful.

Is there a common scenario in which one would want to send data as text, and expect it to be transformed to be valid UTF-8 (by e.g. replacing invalid bytes with replacement runes)?

I personally can't think of one at this time. Couldn't that be done outside of the context of a http request anyway? It seems like an orthogonal task.

If not, I'd change Send to return []byte instead of string, and to convert string data to []byte before sending it.

I would prefer a method that accepts and returns []byte, not string or interface{}. (Or more generally io.Reader and io.ReadCloser like http://godoc.org/net/http#Post and http://godoc.org/net/http#Response.Body (whoa, I just learned you can link to fields of a struct on godoc this way) if that could work well without performance penalties, but I don't think so.)
If you want to keep string or interface{} as a possible input type, then please have:
Send(string) ([]byte, error) // Or Send(interface{}) ([]byte, error)
SendBytes([]byte) ([]byte, error)

Or so. Similar to https://github.com/microcosm-cc/bluemonday#usage.
Unless you have good reasons that []byte is not the best input type?

We won't return io.Reader, because the data is entirely in memory, anyway. If someone wants an io.Reader interface on top, they'll have to use bytes.NewReader
As for data being of type []byte instead of interface{}: Maybe. One can still send other types of objects (documents, blobs) and I'm not sure we should take away that functionality from the top level function. In particular, transmitting files would be dealing with Blob objects.
I think we have established that we don't want to add more functions; adding SendBytes would be no different from adding SendBinary.

We won't return io.Reader, because the data is entirely in memory, anyway. If someone wants an io.Reader interface on top, they'll have to use bytes.NewReader

Agreed. I was only mentioning it for reference.

As for data being of type []byte instead of interface{}: Maybe. One can still send other types of objects (documents, blobs) and I'm not sure we should take away that functionality from the top level function. In particular, transmitting files would be dealing with Blob objects.

I think we have established that we don't want to add more functions; adding SendBytes would be no different from adding SendBinary.

I propose this.

Keep input type to Request.Send method as interface{} for maximum flexibility. If someone wants to send a Blob, they'll create a new request and use it.

Change the higher level helper to handle the most common scenario in the best way:
func Send(method, url string, data []byte) ([]byte, error)

What benefit, other than slightly stricter type checking, do you gain from data []byte as opposed to data interface{}?

Clarity. Simpler, cleaner API.
If someone looks up the docs for xhr.Send, they'll see it can send and receive byte slices. If they see interface{}, they will need to spend additional mental resources (time, attention, memory) to investigate what types it really accepts.
People will most likely want to send []byte, so having the slightly stricter type being enforced will not harm them at all, it will make it easier. If they want to send a string, they'll just convert it to []byte, also easy to do and little harm.

Closed via #6. Thank you!


Replace logger with taggedLogger

This issue aims to replace the vanilla logger with taggedLogger in the IContainerContext interface. The logger property was deprecated in release 0.45.
The files affected are:

common\lib\container-definitions\src\runtime.ts
packages\loader\container-loader\src\containerContext.ts
packages\runtime\container-runtime\src\containerRuntime.ts

This seems fine to me, with one of two approaches, @markfields in case he has more context/feedback to help choose which.

If we think there's risk that some old loader is trying to load modern containers (and also that it's a scenario we need to support), then a reasonable approach might be:

Remove the property from the interface and ContainerContext, but in ContainerRuntime continue to do a last-ditch TaggedLoggerAdapter fallback
Then log a bug for removing the adapter usage from ContainerRuntime and the TaggedLoggerAdapter class, including an explanation of when we think it will be safe to do (and/or what metric will inform that decision).

If we don't think there's risk, then we should just go ahead and remove it in all locations (including removing the TaggedLoggerAdapter class.

Let's go with 1.  Reason being, even though there are only a hundred or so clients with very recent runtimes and pre-0.45 loaders in the last month, just 1 will result in bogus columns getting added to our internal data tables for the tag and value.  And worse, if someone does add privacy-impacting data and tag it, we would have to do a whole thing to clean it up.


YARN log persistence

This PR is to persist yarn log to host filesystem, to avoid log lost accross service restart.
After this pr, admin could find yarn log under /var/log/resource-manager and /var/log/node-manager

Coverage increased (+4.2%) to 52.627% when pulling 89cf5895d3323cc89e4ae1af4d2cf558e8156419 on zimiao/persist_log into 4294699e0bf2e4d8f8255a4be45c8b0d133c4fa7 on master.

Coverage increased (+4.2%) to 52.627% when pulling 89cf5895d3323cc89e4ae1af4d2cf558e8156419 on zimiao/persist_log into 4294699e0bf2e4d8f8255a4be45c8b0d133c4fa7 on master.

Coverage increased (+4.2%) to 52.627% when pulling 89cf5895d3323cc89e4ae1af4d2cf558e8156419 on zimiao/persist_log into 4294699e0bf2e4d8f8255a4be45c8b0d133c4fa7 on master.


mime missing from bitstream model

Currently the bitstream's mimetype is missing from the bitstream model. The client already passes the mimetype in create_bitstream(). If this was available in the model it could be used instead of checking whether the filename string contains ".pdf", for example.

Ah yes, there is a HAL link from the bitstream entity for this: https://github.com/DSpace/RestContract/blob/main/bitstreams.md#format
The easiest way to handle this is to embed format in the response like .../bitstreams?embed=format -- and is part of a larger improvement needed, where we expect all sorts of object types in _embedded


Some emojis don't replace in certain apps

Small number of emojis (for example 🌹🫶) don't replace in certain apps like Instagram while they work in other apps. I've cleared cache and deleted files under /data/font/files/.

Things look fine for me in Instagram, maybe it's the ROM you're on?
Maybe it's from viewing a story as well? I think those use emojis from the device that posted them.

Here is an example.

@mbniol delete data of instagram once, then all emojis will work fine


Rename shortcut (F2) not working for table columns

dBeaver 7.3.1. PostreSQL.
In 7.3.0 F2 worked.

Thank you for the report.

In DBeaver 7.3.2 (PostreSQL) not working also.

In DBeaver 7.3.2 (PostreSQL) not working also.

Hello @greenpeas,
Try unbinding all conflicting shortcuts that use F2 in Preferences ⇒ User Interface ⇒ Keys, so that only Rename remains:

Checked 21.0.3. Rename columns not working on F2.

Try unbinding all conflicting shortcuts that use F2 in Preferences ⇒ User Interface ⇒ Keys

Yes. If unbind conflict command "Показывать описание подсказки" then renaming columns by F2 working:

But F2 should work "out of the box". That is, initially (when installing the program) there should be no conflict.

Indeed, I agree that such fundamental feature should be working out of the box.
I suggested a workaround to start from, at least for now. It needs further examination.
Thanks for response.

Fixed


scheduling not working on a specified date

I couldn't get a script run at a specified date..
This is my code... it is not executing at the date specified it is rather executing instantly.. please help me.
$datetorun = new DateTime('2018-09-04 18:48:00');
$scheduler = new Scheduler();
$scheduler->php($pathtophpscripttorun, '/usr/local/bin/php')->run($datetorun);
what am i doing run.. please help.. i want the skip to run at the date specified.

@Oguntoye by passing the date to the run method you're effectively faking the current time in the system. The job has no specified time to run so it's assumed it should run every minute.
To give you an example, the above code is registering a new job to run every minute, then when the scheduler gets executed it's assuming the current date is 2018-09-04 18:48:00 instead of the actual now date, so every time the scheduler runs it will always run as it was that date/time.
Passing the date to the run method is primarily used to facilitate testing of the scheduler (you can find more details here https://github.com/peppeocchi/php-cron-scheduler/pull/28#issue-140815888)
Instead, if you want to run your script at a specific date and time, you might do so by using a cron expression, so your code will look like
$scheduler = new Scheduler();
$scheduler->php($pathtophpscripttorun, '/usr/local/bin/php')->at('48 18 4 9 *');
$scheduler->run();

Just a note, that will execute the script every year on that date and time (cron don't have support for the year), another workaround would be to add a condition before scheduling the job. Example of pseudocode below
$scheduler = new Scheduler();

$datetorun = new DateTime('2018-09-04 18:48:00');
if ($datetorun === now) {
    $scheduler->php($pathtophpscripttorun, '/usr/local/bin/php');
}

$scheduler->run();

This would be a great feature to build into the scheduler. I'll add to the list for the next release.


Incorrect Pax URL syntax for paranamer

Incorrect Pax URL syntax for bundle (dependency) com.thoughtworks.paranamer/paranamer

Can one of the admins add this person to the trusted builders? (reply with: "add to whitelist" or "ok to test")

@tonit Hi!
Thanks for your PR. Could you take the time to add a test in our OsgiIntegrationTest? It's apparently missing :).
And could you please sign the CLA for the Hibernate Validator project here: https://cla.jboss.org/ ?
Thanks!

I have just added tests for this. CLA will come..

CLA signed. (tonitcom)

@tonit thanks! I amended the commit messages to include a JIRA issue number and made a few very minor improvements.
Merged to master and the 5.4 branch.


fill() can't auto submit

the form is:
<form method="post" target="hiddenwin">

code:
var account = 'liuyong1';
var pwd = '123456';
casper.then(function(){
    this.evaluate(function() {
           // had read source of casper.js
        var f =  __utils__.findOne('form');
        console.log('whether the form selector is correct:'+ (f!=null))
    });
    this.fill('form',{
        'account': account,
        'password': pwd
    },true);
    this.click('input#submit');
    this.capture('login.png');
});

error:
[info] [remote] whether the form selector is correct:true
[info] [remote] attempting to fetch form element from selector: 'form'
[debug] [remote] Set "account" field value to liuyong1
[debug] [remote] Set "password" field value to 123456
[info] [remote] submitting form to unknown, HTTP POST
[info] [remote] TypeError: '[object HTMLInputElement]' is not a function
[debug] [phantom] Click on selector: input#submit

btw, http://casperjs.org/index.html#events-filters
doc of log , the entry descript is wrong, it's "date" not "time"

Regarding your initial bugreport, it's very hard to tell what's going on without seeing the actual page and javascript code. Lots of site use javascript to drive forms and it often obfuscate things.
Feel free to reopen if you can submit a concrete sample case.

the actual page is http://www.zentao.net/user-login.html

looks like there's a target="hiddenwin" attribute in the form tag… try to drop the attribute to see how it goes.


Jimmie NGAP onboarding

💡 Description

Looking at NAMS it appears my original request was cancelled by the system due to no response from the sponsor. I have resubmitted the request, submitted another for Skillsoft access to two of the required training exercises and emailed Jason Werpy to alert him of the invalidated request.
I have completed the Elevated Privileges course.

Skillsoft training has been completed, NGAP NAMS request has been approved and awaiting provisioning.


GPU recommendation

Hi
I have not seen a GPU recommendation thread or a README on the subject (there might be one somewhere?)
what kind of GPU would you recommend for normal trainings, I mean moderately sized acoustic models? I'm currently using 2 Nvidia GeForce RTX 3090 with 24GB of memory;  with Kaldi I can do with less than 5GB. Number of GPUs and memory size are the two critical parameters, here; for a few thousands hours of speech (given that multi-style augmentation is desirable), I would need more than a day for one epoch with 2 GPUs, I'm using ~20M parameters model size to better compare with similarly large Kaldi chain models, and often I get close to consuming all GPU memory  (I use encoder-decoder ctc-attention with confomer layers)
GeForce RTX 3090 have a more reasonable price than Tesla V100 32 GB, which are way too expensive
it looks to me the latest SOTA in speech recognition comes with a greater cost in computational resources (which Ok, it's expected but I wonder whether (very) good -old kaldi is good enough for my pockets...)

Our GPUs have 32GB, but I think 24GB is close enough. You might have to decrease the --max-duration a bit.
In our most recent work with the pruned_transducer_stateless2 setup, we have been running with --use-fp16=True, i.e. with half precision float, which makes it use less memory (or alternatively you  use larger --max-duration).

Just to add a data point: When training librispeech pruned_transducer_stateless5 setup on 4xRTX2080Ti (11GB) with --use-fp16=True, the largest --max-duration I can use is 150.

OK.  It's a shame that it can't use a larger duration, but I estimate that it won't affect the training or if it does, the effect might be slightly positive/good WER-wise.  Also the speed difference from that kind of batch size change is not huge.

Hello, on librispeech (streaming rnn-t emformer), the model does not converge when using a small max-duration (under 100), even with smaller learning rates.
I get the same behavior when training on my homemade dataset.

red: max-duration 100
blue: max-duration 60

You may have to reduce the initial learning rate if it is not converging.

If it's still not converging, try to double model_warm_step from 3k to 6k.
I advise not to reduce initial learning rate by more than about sqrt(2).

.. you don't have to leave it running very long to tell if it's converging.  It should get a good loss within model_warm_step, or  not at all.


Revert "WFLY-17958 Persistence container bytecode enhancement should …

…be enabled by default"
https://issues.redhat.com/browse/WFLY-17958

@jamezp if this is ok with @scottmarlow (and i've seen discussion that makes me expect it is), then this is fine with me. Go ahead and merge it if he approves and it passes CI.

@jamezp if this is ok with @scottmarlow (and i've seen discussion that makes me expect it is), then this is fine with me. Go ahead and merge it if he approves and it passes CI.

Sorry, I now have a different change in mind that I want to validate locally (I don't want to lose the new test and also would like to keep part of the other changes made like removing checking of old Hibernate settings.  I think that this pr can be closed.


Look into removing console error findDOMNode is deprecated in StrictMode

Adding some context from a previously closed issue:

Update - it looks like there's a completely new v2 with a hook that will solve this issue. Please investigate updating to the v2.x+ version of this dep. https://github.com/airbnb/visx/releases

This is not likely to be fixed upstream in v1.x as it's a breaking change
airbnb/visx#737
there's also no way to conditionally disable strict mode
facebook/react#16362
Our current charts library is using deprecated methods and throwing console errors in the browser.
Update the library so we have a clean console for our first release.
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of withBoundingRects() which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here:

Upgrading all visx components to V2 seems quite transparent on my local version (I didn't see any regression, but I might have missed something). Also all tests are still passing after the upgrade.
Problem is, from my understanding, that the source issue is still not fixed in the V2. Therefore upgrading will not fix the console error.
Devs from visx are still deciding how they will implement it, from what I understood.
Maybe we should just flag this issue as blocked on our side, waiting for a fix on their side (as this is not exactly critical).


Fix/tex example

this pull request fixed broken Tex example by removing outdated syntax that changed
in #376.
refer issue to https://github.com/facebook/draft-js/issues/697

Thanks for fixing this!


If database fail in installer, delete csb-settings.php that was just created, or write file after DB check

Currently, it writes the csb-settings.php file, and THEN checks if DB works.
BETTER: Check if DB works, THEN write settings file.

I implemented the delete csb-settings.php part and am adding it to the last PR (because, if something in the middle of creating tables fails, it would still be useful) but I think @eladavron is working on a db connect test for the installer, which would be a much more elegant solution for errors before writing config, especially when making a test mandatory before unlocking the "write config" button.


ch9344: 1.9 -> 2.0

Description of changes
Driver was updated on 2023-10-12 without official changelog. The 2 compatibility patches are no longer needed.
Only build and modprobe tested on my computer, since the physical device is currently in the office. I'll check with the real hardware on Monday.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Well just found a new build issue with 6.6 kernel. Patch is uploaded to AUR but I need to get back to home to fix this PR.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2928

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/how-to-override-packages-from-another-pr-instead-of-importing-them-under-another-namespace/40334/1


comma-dangle for consistency

Noticed we were pretty inconsistent w/ comma-dangle formatting since the rule was disabled.
This enforces a trailing comma + gets us in-line w/ the augur.js rule.
Feel free to close if this is not the route we want to go.
(Changes are all autogen’d via —fix)

@stephensprinkle I'm all for this!


bug: Ionic doesnt undrstnd stndrd html tags like

Type: bug
Ionic Version: 2.x
Platform: android 5.1 browser
Ionic not understanding standard html tags like < xmp >, < code > and < pre >, i have to show code snippet in ionic app, that is a combination of html and anuglarjs but i can't show it up even after escaping it, none of the tag is working in ionic but in standard html code.

Hey @jgw96 Justin can you please have a look here. Thanks

Hello! Thanks for opening an issue with us! Would you mind sharing a code snippet of what your template looks like? Thanks for using Ionic!

Thanks for replying, Yes sure, Here is a very simple code that contains in-line AngularJs code:
`
<li *ngFor="let bikePart of bikeParts
{{bikePart.name | uppercase}}
{{bikePart.description}}
<p *ngIf="bikePart.inStock > 0">{{bikePart.inStock}}
<p *ngIf="bikePart.inStock === 0">out of stock
{{bikePart.price | currency:EUR':true}}

`
Now as we do in simple html we can use any of the tag to show this snippet on ui tags are:
< xmp >
< pre >
< code >
In Html when i put this code inside < xmp > i can see it as it is without compiling, but when i do same in ionic template, application starts finding properties and doesn't work.
That's why i said Ionic isn't supporting these standard html tags.
I hope you will consider it, because you can check on google app store i have published an app (AngularJs 2 - Nikhil Kumar) where in it lots of code snippets were required to show, anyhow i managed to show but thats not a feasible solution.
Thanks !!

Hello! Thanks for the info. Does the xmp tag work for you in a plain Angular 2 app? Also, the pre tag and code tag seem to be working fine for me In Ionic 2, is it mainly the xmp tag your having trouble with?

All three tags are working for me in Plain Html+AngularJs but none of three working in ionic, i can show you working examples where these tags are not working in ionic but in Html, if you have installed the app that i referenced earlier (goo.gl/6qEAYn) you can see i have buttons there when user clicks an InAppBrowsers opens with some code snippets that page is complete html page and every tag is working there but not in Ionic. Hope you understand. Thanks. waiting for your prompt reply.

Hey @jgw96 @bensperry  can you have a look here please.

Hello @nikhilknoldus ! I am currently looking more into this issue. <code> and <pre> seem to work fine for me, but I can confirm that <xmp> is not.  Thanks!

@jgw96  Hey thanks  Justin, for considering my issue into Ionic.

Hello @jgw96 Justin ! can you show me the example for <code> and <pre> that is working for you, example code should contain angularjs tags inside html. Thanks !!

Hey @jgw96 , I tried the
code pre and xmp in the latest version of Ionic, but these are not working man.

Hello! So the reason that xmp was not working in my test was that it has been deprecated in chrome. Because the code tag and the pre tag were working in my testing, and those are the recommended replacements for the xmp tag I am going to close this issue for now. If you could make a plunker that shows the code and pre tags not working then i will happily reopen this issue. Thanks for using Ionic!


[5.7] The color() method could return void if the switch fails

I would use string|null rather than mixed.


[Spaceship] Can not create a new localization language on ItunesConnect

Issue Description
I am trying to add a new language to my app on ItunesConnect
I am using the following Ruby code to do so with Spaceship
app_itunes = Spaceship::Tunes::Application.find(bundle_id)
v = app_itunes.edit_version
v.create_languages(["nl"])
v.save!

However this produces an error
/usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.37.0/lib/spaceship/tunes/tunes_client.rb:221:in `handle_itc_response': There are one or more errors on the page. (Spaceship::TunesClient::ITunesConnectError)
	from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.37.0/lib/spaceship/tunes/tunes_client.rb:369:in `block in update_app_version!'
	from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.37.0/lib/spaceship/tunes/tunes_client.rb:964:in `with_tunes_retry'
	from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.37.0/lib/spaceship/tunes/tunes_client.rb:362:in `update_app_version!'
	from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.37.0/lib/spaceship/tunes/app_version.rb:299:in `save!'
	from my_script.rb:27:in `<main>'

I don't have the fastlane gem installed... I just use the spaceship ruby exposed functions

@richarddigifit have you tried? nl-NL

also - for working with spaceship - try setting VERBOSE=1 as an env ;)
it will debug http traffic from and to apple 🙏

ahh thank you, guess I should have read the documentation better haha


[bug] Bun installArgs are not being used by Node when bun is the packageManager

Describe the bug
If I use in my toolchain file:
bun:
  installArgs:
    - "--frozen-lockfile"
node:
  packageManager: bun

The install arguments are not propagated to the bun install for Node tasks. Then I need to repeat it again as in:
bun:
  installArgs:
    - "--frozen-lockfile"
node:
  packageManager: bun
  bun:
    installArgs:
      - "--frozen-lockfile"

Then it works properly.

Fixed in 1.26.7


Enable Up Next by default

Feature request
I'm submitting a proposal to ...

[x] new feature
[ ] change an existing feature

Describe your request
I would enable Up Next support by default. If people have it installed it makes more sense it works out of the box, rather than having another switch to enable it.
This also means that everyone who installed the Netflix versions with it disabled by default, still have to enable it after this is enabled by default.

the setting to enable/disable does not remove it because i also need it for debugging
but it seems to me that you can make the default value dynamic based on whether an addon is installed or not, i will give a try

Well, there is a difference between having it installed and enabling or disabling it.
Obviously if it is not installed, the entry (and settings entry) should be grayed-out (I didn't test this).
But if it is installed, the default IMHO ought to be enabled.

use a dynamic "default" value in the settings xml does not work,
then i added it in the startup addon auto-configuration
https://github.com/CastagnaIT/plugin.video.netflix/pull/466

I changed the setting in this way, it makes me easier to handle via xml without subsettings

I have installed the Up Next addon, but unfortunately the "Enable Up Next integration" is grayed out and I can't enable it. What may be the fault of that?

I have installed the Up Next addon, but unfortunately the "Enable Up Next integration" is grayed out and I can't enable it. What may be the fault of that?

Same here, just installed both plugins but cannot enable the integration


Revert "Revert "Jump search""

Reverts commonCereal/DDSA#19

Data Structure / Algorithm
Jump search algorithm

Solution / Explanation of Implementation.
Searches a list for a target value using the jump search method
This algorithm assumes that the list is in ascending order
Algorithm searches by jumping items in the list until items are greater than the target value
Then the list is searched linearly beginning at the previous jump point until the target value is found
-1 is returned if target value is not in the list, returns index value of the target value if present in the list

Semver Check
Major - Backwards Incompatible change on the API (includes removals)
Minor - Adds or deprecates part of the API.
Patch - Doesn't effect API

Tag Reviewer(s)
@commonCereal

The original PR for this work was accidentally merged without proper approvals. Due to this, I had to revert this PR with a Revert PR. This PR reverts the revert to allow @sunshinesway to get a proper approval on her work and get Hacktoberfest credit.
Note: After this I have updated the master branch protection rules to require at least one approval from maintainer to prevent this from happening to contributors who are new to Github.


Consider making test structure more consistent

To more cleanly separate the test cases within in test, use the sub-tests offered in the testing framework.

Triage: In the future we want to be consistent. We don't think it's actionable right now though.


Issue Reading Catalog from Private Bucket

I am trying to access the catalog.json file via either https://dev-usgs-landsat.s3-us-west-2.amazonaws.com/collection01/level-1/standard/etm/2009/001/005/catalog.json or s3://dev-usgs-landsat/collection01/level-1/standard/etm/2009/001/005/catalog.json using Intake Stac and I am getting these errors.
For the Object URL:

For the S3 Link:

FYI, many people are at AGU this week so the response may be a bit delayed :)
Do you know who maintains the catalogs at that URL? Those error messages are consistent with the file not existing / not being publicly accessible.

I get a PermissionDenied error when I hit that url. Is this a private object? If so, you’ll need to make sure your python process has the necessary environment credentials to allow access.

What environment credentials outside of an IAM role granting access to the bucket?

@pieschker, what happens when you hit the above urls with a simple python requests call, e.g.
In [7]: import requests

In [8]: url = 'https://raw.githubusercontent.com/sat-utils/sat-stac/master/test/
   ...: catalog/catalog.json'

In [9]: r = requests.get(
   ...:     url,
   ...:     headers={}
   ...: )
   ...: print(r.json())
{'id': 'stac', 'description': 'A STAC of public datasets', 'stac_version': '0.6.0', 'links': [{'rel': 'self', 'href': 'catalog.json'}, {'rel': 'root', 'href': 'catalog.json'}, {'rel': 'child', 'href': 'eo/catalog.json'}]}

In [10]: url = 'https://dev-usgs-landsat.s3-us-west-2.amazonaws.com/collection01
    ...: /level-1/standard/etm/2009/001/005/catalog.json'

In [11]: r = requests.get(
    ...:     url,
    ...:     headers={}
    ...: )
    ...: print(r.json())
---------------------------------------------------------------------------
JSONDecodeError                           Traceback (most recent call last)
<ipython-input-11-a7a0c1c7f3a3> in <module>
      3     headers={}
      4 )
----> 5 print(r.json())

~/miniconda3/lib/python3.6/site-packages/requests/models.py in json(self, **kwargs)
    887                 try:
    888                     return complexjson.loads(
--> 889                         self.content.decode(encoding), **kwargs
    890                     )
    891                 except UnicodeDecodeError:

~/miniconda3/lib/python3.6/json/__init__.py in loads(s, encoding, cls, object_hook, parse_float, parse_int, parse_constant, object_pairs_hook, **kw)
    352             parse_int is None and parse_float is None and
    353             parse_constant is None and object_pairs_hook is None and not kw):
--> 354         return _default_decoder.decode(s)
    355     if cls is None:
    356         cls = JSONDecoder

~/miniconda3/lib/python3.6/json/decoder.py in decode(self, s, _w)
    337
    338         """
--> 339         obj, end = self.raw_decode(s, idx=_w(s, 0).end())
    340         end = _w(s, end).end()
    341         if end != len(s):

~/miniconda3/lib/python3.6/json/decoder.py in raw_decode(self, s, idx)
    355             obj, end = self.scan_once(s, idx)
    356         except StopIteration as err:
--> 357             raise JSONDecodeError("Expecting value", s, err.value) from None
    358         return obj, end

JSONDecodeError: Expecting value: line 1 column 1 (char 0)

This tells me that I don't have access to this url. If you are getting a similar error, I suggest examining your IAM roles.

@nroberts-hub and @pieschker - can you suggest a path forward here? Were you able to resolve your access problems?

Nope. It's a configuration issue with our environment that is beyond our control. We just have to wait for the data to be public. I suggest closing this issue. Thank you.


Update access and refresh tokens on CONFIGURE

Update to the new location for accessToken and refreshToken during the configuration steps

LGTM


About Trident

Can you support Trident spout?

Ppat, Can't we save the delivery tags in a list and then do an atomic operation of getting from the list and acking each individually?

I believe you need to ack an entire batch in atomic fashion. Not individually. Having said, if you have an implementation that works, pull requests are welcome (please follow the coding style within the project).

On Aug 13, 2015, at 10:40 AM, arung<EMAIL_ADDRESS>wrote:
Ppat, Can't we save the delivery tags in a list and then do an atomic operation of getting from the list and acking each individually?
—
Reply to this email directly or view it on GitHub.


Smart Plug is not suppport

{"uuid":"2204013886737151070148e1e98e22e1","onlineStatus":2,"devName":"Smart Plug","devIconId":"device023_au","bindTime":1689213618,"deviceType":"mss210p","subType":"au","channels":[{}],"region":"ap","fmwareVersion":"7.1.2","hdwareVersion":"7.0.0","userDevIcon":"","iconType":0,"domain":"mqtt-ap.meross.com","reservedDomain":"mqtt-ap.meross.com","cluster":1,"hardwareCapabilities":[],"firmware":"7.1.2","hbDeviceId":"2204013886737151070148e1e98e22e1","model":"MSS210P"}* Please explain your feature request in a one or two sentences.

Hi @sateeshruttala
Please can you update to the beta version of the plugin and check this device is now working?
https://github.com/bwp91/homebridge-meross/wiki/Beta-Version
Thanks!


Remove csp technologies

Retire Dish Stirling and Direct Steam Power technologies for next major SAM release. Remove technologies from menu and handle version upgrades for files generated with older versions of SAM that use these technologies.
Close issue #363

Only project.cpp and main.cpp and versions.lk should be merged. The other 19 files should be from develop only. Please do not merge those files!

Shouldn't startup.lk also be included to set the 'Retired' tree parent and 'Retired' dummy cases?

@mjprilliman, @cpaulgilman please review the latest commit to remove_csp_technologies - should close #363

I created a new pull request without all of the defaults changes at https://github.com/NREL/SAM/pull/428. Once the Travis tests pass, I will squash and merge and then we should test the functionality in Develop.
Here's what I did:

Check out the original remove_csp_technologies branch.

Copy main.cpp, project.cpp, startup.lk, and versions.lk to my computer.

Switch to the latest Develop branch.

Create a new branch remove_csp_techs_clean.

Copy files from my computer to new branch.

Commit and push.

Create pull request.

It looks like you might be able to delete files from a PR on the GitHub website, but this manual approach may be more reliable.
Thanks,
Paul.

This is being replaced by https://github.com/NREL/SAM/pull/428


Consider porting highlighting implementation to atom/highlights or prismjs

Closing in favor of slap-editor/editor-widget#134


Data Contract from multiple XSD files

From the feature list:

A Generate Data Contract Code feature that supports the selection of multiple XSD/WSDL source files.

The link after it is a dead link. Selecting multiple XSD files won't bring up with WSCF.blue menu. When a single XSD file is selected, WSCF.blue | Generate Data Contract Code...  does show up, and the dialog suggests multiple XSD files can be selected: the label reads "XSD files(s)". But I can't alter the filenames in that box either.
Is there a UI trick to getting this to work as descrbied?

Indeed, the only possible file type for the WSCF extension in Visual Studio is .wsdl.
.xsd is not supported (anymore ?).
I am wondering how the WSCF.Blue tool compares to Svcutil.exe and xsd.exe

When I add an  .xsd file to the project and right-click on it, then a Generate Data Contract Code option comes available....so it works !


Improve support for reduce returning nested information

Feature request
We expect users that are applying their functions via reduce to sometimes want more complex outputs. For example, if I'm applying Lombscargle to all lightcurves in my nested dataset, I may want a result that has a max power column, a frequency of max power column, and a nested column holding the full periodogram. Presently, we don't really support this as we primarily want the user to return a dictionary-style output, which will limit the user towards producing list columns rather than nested columns, for example:
from nested_pandas.datasets import generate_data
import numpy as np

ndf = generate_data(3,20)

def complex_output(flux):
    return {"max_flux":np.max(flux), "flux_quantiles":np.quantile(flux, [0.1,0.2,0.3,0.4,0.5])}

ndf.reduce(complex_output, "nested.flux")

	max_flux	flux_quantiles
0	98.744076	[15.293187217097268, 21.834338973710633, 25.02...
1	98.502034	[6.337989346945357, 8.019180689729948, 9.69707...
2	99.269021	[12.42551556001139, 15.901779148332189, 26.199...

With #131 it would be easier to convert this to a nested output, but I think ideally reduce would have a more native ability to produce nested structures for these types of functions. My thinking about how we might try to facilitate this, is to read more into the user defined dictionary output to determine the nestedframe. For example, a user could instead specify this reduce function:
def complex_output(flux):
    return {"max_flux":np.max(flux), "quantiles":{"flux_quantiles":np.quantile(flux, [0.1,0.2,0.3,0.4,0.5])}}

The json-like nesting of dataframes would signal that the user would like a "quantiles" nested column with a "flux_quantiles" field. I'm not entirely sure on the full implementation plan, but this seems most intuitive from the users perspective.
Before submitting
Please check the following:

[ ] I have described the purpose of the suggested change, specifying what I need the enhancement to accomplish, i.e. what problem it solves.
[ ] I have included any relevant links, screenshots, environment information, and data relevant to implementing the requested feature, as well as pseudocode for how I want to access the new functionality.
[ ] If I have ideas for how the new feature could be implemented, I have provided explanations and/or pseudocode and/or task lists for the steps.

Noticing this is actually half a resubmit of #101, but each ticket proposes a different solution. We should talk about this at an upcoming meeting