Quickstart: Image Analysis 4.0 python not supported on MacOS

I tried to run the quickstart and had to realize that there is no package for MacOs on
https://pypi.org/project/azure-ai-vision/#files
Therefore, it is not possible to install the package and run the code.
This should be made explicit in the documentation - or even better be fixed by providing a MacOs wheel (or, if possible, a platform-agnostic  wheel tagged none-any).

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 3370ee1e-7205-b5b2-add1-77fec0ce4366
Version Independent ID: a6d25469-a52e-2233-5a15-cfbb6ed2a3c6
Content: Quickstart: Image Analysis 4.0 - Azure Cognitive Services
Content Source: articles/cognitive-services/Computer-vision/quickstarts-sdk/image-analysis-client-library-40.md
Service: cognitive-services
Sub-service: computer-vision
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

A more extensive SDK installation doc is coming soon, with more information about each platform. But yes, this is not available on MacOS
#please-close

Is there any wheel files which I can use for azure-ai-vision in MacOS? Looks like Azure Computer Vision SDK cannot be used in MacOS.

unluckily, still not working, I just tried yesterday to install the package, ended up failed...


Fix TypeError

Recent versions of WAL-E uses Python3 instead of Python2.
They are incompatible around str and bytes.
This will fix #265.

Oops. Some more fixes are required. I'll push them later.

Alright, let me know when to  merge.

@fdr , I added some patches.
I think they cover nominal patterns. At least it works well on my Azure VM instance.
But I'm not sure about exception patterns.

Alright, I rebased them and applied them. Thanks for the patch.


convert weights to onnx

can the weights to converted to onnx?

I am trying this work

I'm very interested in converting this into a compact onnx model. Were you successful in doing this?

@rtolps At present, there will be some errors in the conversion process.


building faileds on shogun repositions.

Describe the bug
A clear and concise description of what the bug is.
simple install shogun
c:\vcpkg>vcpkg install shogun:x64-windows-static
Computing installation plan...
The following packages will be built and installed:
shogun[core]:x64-windows-static
Detecting compiler hash for triplet x64-windows-static...
Starting package 1/1: shogun:x64-windows-static
Building package shogun[core]:x64-windows-static...
Could not locate cached archive: C:\Users\Administrator\AppData\Local\vcpkg/arch
ives\bb\bba3c5a4f94c4ec3944d5f5ecd8846096657135a.zip
-- Using cached C:/vcpkg/downloads/shogun-toolbox-shogun-ab274e7ab6bf24dd598c1da
f1e626cb686d6e1cc.tar.gz
-- Cleaning sources at C:/vcpkg/buildtrees/shogun/src/b686d6e1cc-464b41c80d.clea
n. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/vcpkg/downloads/shogun-toolbox-shogun-ab274e7ab6bf24dd59
8c1daf1e626cb686d6e1cc.tar.gz
-- Applying patch cmake.patch
-- Applying patch cmake-config.in.patch
-- Applying patch fix-dirent.patch
-- Using source at C:/vcpkg/buildtrees/shogun/src/b686d6e1cc-464b41c80d.clean
-- Configuring x64-windows-static
-- Building x64-windows-static-dbg
-- Restarting Build without parallelism because memory exceeded
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:141 (message):
Command failed: C:/vcpkg/downloads/tools/cmake-3.17.2-windows/cmake-3.17.2-w
in32-x86/bin/cmake.exe --build . --config Debug --target install -- -v
Working Directory: C:/vcpkg/buildtrees/shogun/x64-windows-static-dbg
See logs for more information:
C:\vcpkg\buildtrees\shogun\install-x64-windows-static-dbg-out.log
C:\vcpkg\buildtrees\shogun\install-x64-windows-static-dbg-out-1.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
ports/shogun/portfile.cmake:47 (vcpkg_install_cmake)
scripts/ports.cmake:79 (include)
Error: Building package shogun:x64-windows-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: shogun:x64-windows-static
Vcpkg version: 2020.06.15-nohash
Additionally, attach any relevant sections from the log files above.
Environment

OS: win7
Compiler: revision

To Reproduce
Steps to reproduce the behavior:

./vcpkg install shogun:x64-windows-static
See error
Repro code when

Expected behavior
A clear and concise description of what you expected to happen.
Failure logs
-(please attached failure logs)
        _Rep=__int64
    ]

C:\vcpkg\installed\x64-windows-static\include\eigen3\Eigen\src/Core/MatrixBase.h(276): fatal error C1060: compiler is out of heap space
[260/659] C:\PROGRA~2\MIB055~1\2019\COMMUN~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   /TP  -IC:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src -Isrc -IC:\vcpkg\installed\x64-windows-static\include -IC:\vcpkg\installed\x64-windows-static\include\eigen3 /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP  /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1    /std:c++14 /bigobj /showIncludes /Fosrc\shogun\CMakeFiles\libshogun.dir\mathematics\linalg\backend\eigen\BasicOps.cpp.obj /Fdsrc\shogun\CMakeFiles\libshogun.dir\ /FS -c C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\mathematics\linalg\backend\eigen\BasicOps.cpp
FAILED: src/shogun/CMakeFiles/libshogun.dir/mathematics/linalg/backend/eigen/BasicOps.cpp.obj
C:\PROGRA~2\MIB055~1\2019\COMMUN~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   /TP  -IC:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src -Isrc -IC:\vcpkg\installed\x64-windows-static\include -IC:\vcpkg\installed\x64-windows-static\include\eigen3 /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP  /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1    /std:c++14 /bigobj /showIncludes /Fosrc\shogun\CMakeFiles\libshogun.dir\mathematics\linalg\backend\eigen\BasicOps.cpp.obj /Fdsrc\shogun\CMakeFiles\libshogun.dir\ /FS -c C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\mathematics\linalg\backend\eigen\BasicOps.cpp
C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun/lib/parameter_observers/ObservedValue.h(190): warning C4244: 'return': conversion from '_Rep' to 'double', possible loss of data
with
[
_Rep=__int64
]
C:\vcpkg\installed\x64-windows-static\include\eigen3\Eigen\src/Core/VectorwiseOp.h(255): fatal error C1060: compiler is out of heap space
[261/659] C:\PROGRA~2\MIB055~1\2019\COMMUN~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   /TP  -IC:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src -Isrc -IC:\vcpkg\installed\x64-windows-static\include -IC:\vcpkg\installed\x64-windows-static\include\eigen3 /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP  /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1    /std:c++14 /bigobj /showIncludes /Fosrc\shogun\CMakeFiles\libshogun.dir\mathematics\linalg\backend\eigen\EigenSolvers.cpp.obj /Fdsrc\shogun\CMakeFiles\libshogun.dir\ /FS -c C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\mathematics\linalg\backend\eigen\EigenSolvers.cpp
C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun/lib/parameter_observers/ObservedValue.h(190): warning C4244: 'return': conversion from '_Rep' to 'double', possible loss of data
with
[
_Rep=__int64
]
[262/659] C:\PROGRA~2\MIB055~1\2019\COMMUN~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   /TP  -IC:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src -Isrc -IC:\vcpkg\installed\x64-windows-static\include -IC:\vcpkg\installed\x64-windows-static\include\eigen3 /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP  /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1    /std:c++14 /bigobj /showIncludes /Fosrc\shogun\CMakeFiles\libshogun.dir\mathematics\linalg\backend\eigen\Solvers.cpp.obj /Fdsrc\shogun\CMakeFiles\libshogun.dir\ /FS -c C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\mathematics\linalg\backend\eigen\Solvers.cpp
C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun/lib/parameter_observers/ObservedValue.h(190): warning C4244: 'return': conversion from '_Rep' to 'double', possible loss of data
with
[
_Rep=__int64
]
[263/659] C:\PROGRA~2\MIB055~1\2019\COMMUN~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   /TP  -IC:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src -Isrc -IC:\vcpkg\installed\x64-windows-static\include -IC:\vcpkg\installed\x64-windows-static\include\eigen3 /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP  /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1    /std:c++14 /bigobj /showIncludes /Fosrc\shogun\CMakeFiles\libshogun.dir\mathematics\linalg\backend\eigen\Decompositions.cpp.obj /Fdsrc\shogun\CMakeFiles\libshogun.dir\ /FS -c C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\mathematics\linalg\backend\eigen\Decompositions.cpp
C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun/lib/parameter_observers/ObservedValue.h(190): warning C4244: 'return': conversion from '_Rep' to 'double', possible loss of data
with
[
_Rep=__int64
]
ninja: build stopped: subcommand failed.
[1/400] cmd.exe /C "cd /D C:\vcpkg\buildtrees\shogun\x64-windows-static-dbg\src\shogun && C:\vcpkg\downloads\tools\cmake-3.17.2-windows\cmake-3.17.2-win32-x86\bin\cmake.exe -D SRC=C:/vcpkg/buildtrees/shogun/src/b686d6e1cc-464b41c80d.clean/src/shogun/lib/versionstring.h.in -D DST=C:/vcpkg/buildtrees/shogun/x64-windows-static-dbg/src/shogun/lib/versionstring.h -D ROOT_DIR=C:/vcpkg/buildtrees/shogun/src/b686d6e1cc-464b41c80d.clean -D PYTHON_EXECUTABLE=C:/vcpkg/downloads/tools/python/python-3.8.3-x64/python.exe -P C:/vcpkg/buildtrees/shogun/src/b686d6e1cc-464b41c80d.clean/cmake/version.cmake"
[2/400] C:\PROGRA~2\MIB055~1\2019\COMMUN~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   /TP  -IC:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src -Isrc -IC:\vcpkg\installed\x64-windows-static\include -IC:\vcpkg\installed\x64-windows-static\include\eigen3 /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP  /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1    /std:c++14 /bigobj /showIncludes /Fosrc\shogun\CMakeFiles\libshogun.dir\base\Parallel.cpp.obj /Fdsrc\shogun\CMakeFiles\libshogun.dir\ /FS -c C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\base\Parallel.cpp
FAILED: src/shogun/CMakeFiles/libshogun.dir/base/Parallel.cpp.obj
C:\PROGRA~2\MIB055~1\2019\COMMUN~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   /TP  -IC:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src -Isrc -IC:\vcpkg\installed\x64-windows-static\include -IC:\vcpkg\installed\x64-windows-static\include\eigen3 /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP  /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1    /std:c++14 /bigobj /showIncludes /Fosrc\shogun\CMakeFiles\libshogun.dir\base\Parallel.cpp.obj /Fdsrc\shogun\CMakeFiles\libshogun.dir\ /FS -c C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\base\Parallel.cpp
C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\base\Parallel.cpp(89): error C3861: 'ASSERT': identifier not found
C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\base\Parallel.cpp(91): error C2146: syntax error: missing ';' before identifier 'num_threads'
ninja: build stopped: subcommand failed.
Additional context
Add any other context about the problem here.

Probably due to insufficient memory. The first line of log "fatal error C1060: compiler is out of heap space".
As mentioned in #9588, the libshogun.lib is amazingly huge (dbg: 2.05 GB, rel: 1.80 GB).
I haven't used Shogun for a while, and I don't know if this information is still valid. This information may be useful to you.

Probably due to insufficient memory. The first line of log "fatal error C1060: compiler is out of heap space".
As mentioned in #9588, the libshogun.lib is amazingly huge (dbg: 2.05 GB, rel: 1.80 GB).
I haven't used Shogun for a while, and I don't know if this information is still valid. This information may be useful to you.

but there is an error notice here:
C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\base\Parallel.cpp(89): error C3861: 'ASSERT': identifier not found
C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\base\Parallel.cpp(91): error C2146: syntax error: missing ';' before identifier 'num_threads'
seems my memory is enoght....

@whidbey Have you contacted us before regarding issues with this same port and/or other ports?
I'll have a go now at building this project (shogun) from source and I'll report here.

@whidbey Have you contacted us before regarding issues with this same port and/or other ports?
I'll have a go now at building this project (shogun) from source and I'll report here.

so far no》。。other package  is ok....

Hi @whidbey
C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\base\Parallel.cpp(89): error C3861: 'ASSERT': identifier not found
For this error, you can add #include <shogun/io/SGIO.h> in C:\vcpkg\buildtrees\shogun\src\b686d6e1cc-464b41c80d.clean\src\shogun\base\Parallel.cpp, then try to build again.

tkanks


⚠ Bofrost.be has degraded performance

In a401376, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1951 ms

Resolved: Bofrost.be performance has improved in 3116751 after 12 minutes.


Fixing problems reported in Boost Inspection Report

I fixed some of problems reported in Boost Inspection Report for 1.59 beta rc1.

I fixed violations of Boost min/max guidelines, converted tabs into spaces, added missing license information and copyrights (based on who and when created the file).
I fixed one non-ASCII character in /example/opencv_convolution.cpp, but I DID NOT change author name with non-ASCII character/s as I don't think it would be right.
I added BOOST_NO_CXX11_VARIADIC_TEMPLATES macro which replaces deprecated BOOST_NO_VARIADIC_TEMPLATES.
I also moved all BOOST_NO_* to config.hpp.
I used BOOST_COMPUTE_NO_ prefix for all these macros, but it's not a problem to changed the prefix if different is preferred (for example  BOOST_COMPUTE_DETAIL_NO_).
(!) The last commit removes deprecated Boost macros and update required version of Boost Library to 1.55 (in Boost 1.48 new macros that replaces deprecated ones are not defined, theoretically 1.51 is enough, but IMO 1.55 is currently the most popular one + there are no packages for 1.51). This commit can be removed if we want to keep supporting 1.48 version.

Looks good! As for your last comment, I think we still want to keep support for Boost 1.48 (at least until Boost.Compute is in the official Boost release).

OK, so I will remove last commit and it will be ready to merge.

Done, last commit is removed. Deprecated macros will still generate problems in Boost inspection program, but we keep support for 1.48 version. My commit will wait patiently ;)


"Adding bot to new Slack workspaces is currently broken"

This message has been in the readme for some time. Is it still accurate? What action needs to be taken?

I think that's from when I first ported it from BeepBoop and I forgot to remove it when I added support for adding new slacks. I'll remove it.


feat: SEO optimization

Closes #980. Changed title to match format [Name of the page] [Global title of the store]

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Samir Alibabic seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

What's the status of this PR @samiralibabic ?

What's the status of this PR @samiralibabic ?

I'm waiting on some input. I've verified and titles, OG images and SEO metadata seem to be correct already (except the small change I made here). Do you have more info?

I think it would be great to change a og image for product page - product thumbnail would be a more appropriate for product page than default image provided for pages like a "home".
Also common practice is to provide a JSON-LD object which making it easier for search engines and other applications to understand the content and relationships within the data what also boost SEO - smth like that whould be enough for a product page:
{
  "@context": "http://schema.org",
  "@type": "Product",
  "name": "Product Name",
  "description": "Product description goes here.",
  "offers": {
    "@type":"AggregateOffer",
    "availability":"https://schema.org/InStock",
    "priceCurrency":"USD",
    "highPrice":"20.0",
    "lowPrice":"15.0"
  },
  "image": "url-to-product-image.jpg",
}

Should I add JSON-LD in this PR too, or does it require discussion?

I think it would be great to change a og image for product page - product thumbnail would be a more appropriate for product page than default image provided for pages like a "home".
Also common practice is to provide a JSON-LD object which making it easier for search engines and other applications to understand the content and relationships within the data what also boost SEO - smth like that whould be enough for a product page:
{
  "@context": "http://schema.org",
  "@type": "Product",
  "name": "Product Name",
  "description": "Product description goes here.",
  "offers": {
    "@type":"AggregateOffer",
    "availability":"https://schema.org/InStock",
    "priceCurrency":"USD",
    "highPrice":"20.0",
    "lowPrice":"15.0"
  },
  "image": "url-to-product-image.jpg",
}

Should I add JSON-LD in this PR too, or does it require discussion?

Hi! I'm not the maintainer of this project, and I don't decide what should be implemented. However, I believe providing JSON-LD is a common industry practice. I also don't see any drawbacks to this feature, so it might be beneficial to include it in the project, expecially for product pages. In my view, it is related to SEO, so it could be introduced now or implemented later in a separate PR. Ultimately, the decision is up to you 🙂


feat(library/logic/eq.lean): add C-rule for eq

I'll use / discuss these in a new tutorial chapter on equality and dependent types.

We already have eq.drec and eq.drec_on:
https://github.com/leanprover/lean/blob/master/library/init/logic.lean#L44-L51
The subst tactic uses eq.drec.
https://github.com/leanprover/lean/blob/master/src/library/tactic/subst_tactic.cpp#L113
BTW, I regret the decision of generating non-dependent eliminators for inductive predicates.
This has proved to be really annoying. In several parts of the code I have to "branch" on that.
For the Boolean connectives, it is nice use the non-dependent eliminator (e.g., or.elim), but we could have defined them on top of the dependent one.
I'm not sure how big is the change, but we should make it in the future.
The source code would be more uniform.

Ah, somehow I missed that. drec and drec_on are better names anyhow. Thanks.


Multiple messages when only one is sent

When I send a message with $bot->sendMessage the chat window receives 10 or so messages. It varies how many. There's no loop in my code.
Then Facebook stops calling the script altogether after a while. Maybe something wrong on Facebook's side.

Now I get only one message, and I haven't changed the code. I'll follow up if this happens again.


signal-desktop: 6.37.0 -> 6.38.0, signal-desktop-beta: 6.38.0-beta1 -> 6.39.0-beta2

Description of changes
https://github.com/signalapp/Signal-Desktop/releases/tag/v6.38.0
https://github.com/signalapp/Signal-Desktop/compare/v6.38.0-beta.1...v6.39.0-beta.1
Backport depends on #265405.

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
[x] 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

[x] Fits CONTRIBUTING.md.

Would it be possible to add this release v6.39.0-beta.2 for beta

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/2904

Whoever would like to merge this, be sure to merge https://github.com/NixOS/nixpkgs/pull/265405 first, please.


Fix column resizer activation

Changed display: none/block to use opacity: 0/1. This makes the resizer always be present in the DOM tree, allowing activating it when moving mouse from right to left.

After this, I was able to set z-index to 1 (the resizer needs to be on top of the next column which comes later in the tree).
Can't remove it completely because then it won't be activable when moving from right side:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add a technical walkthrough of Radius

This PR adds a technical walkthrough of the Radius getting started guide. Its main focus it to go "under the hood" of what happens in the getting started guide for readers who want to learn about exactly what's happening when they do the guide.
Leveraging this guide, this PR also helps explain what a workspace is compared to an environment.
This PR also adjusts the structure of the concepts docs, bucketing them into "why Radius" and "technical" concept docs, which help separate separate types of content suitable for different readers.

Will be splitting this PR into two separate PRs, one for splitting concepts and one for the technical walkthrough.


Contribution. Spanish translation

riot-android 0.6.9 https://www.dropbox.com/s/eddhmmpbmk0dxd3/strings.xml?dl=0
If it helps, we translate every few versions. We will soon translate riot-web.

Hello,
Translations are managed with Weblate now: https://translate.riot.im/projects/riot-android
Benoit


Links to past Events

Describe the Bug
When placing an internal link you can select published events that are already in the past.
Expected Behavior
Past events should not be available to select.

As discussed during the issue grooming yesterday, we checked with the feedback giver again and basically she agrees that it's unnecessary to be able to link to events at all. Whether future or past events...
Now I think it is up to us to discuss how we want to proceed. I see two options:

only remove past events from the suggested links (in case there are municipalities that use the option to link to events)
remove all events from suggested links (events could still be linked if someone really wants to via the URL)


Convolution kernel size issue.(Turns out to be an issue about different order of dimensions between Python and R)

The image sizes are c(3,224,224) (with dataIterator created with im2rec)
And the current net structure is (I know the convolution layers are too few,but this is my debugging step)

net= 'data' %>% mx.symbol.Variable() %>%
  #224

  mx.symbol.Convolution(kernel=c(4,4),num.filter=40,stride=c(4,4)) %>%
  #56
  mx.symbol.Activation(act.type='tanh') %>%

  mx.symbol.Flatten() %>%

  mx.symbol.FullyConnected(num.hidden=300) %>%
  mx.symbol.Activation(act.type='relu') %>%

  mx.symbol.FullyConnected(num.hidden=100) %>%
  mx.symbol.Activation(act.type='tanh') %>%

  mx.symbol.FullyConnected(num.hidden=2) %>%
  mx.symbol.SoftmaxOutput()

And when I trained the model, I immediately got the error message:
_"  D:\chhong\mxnet\dmlc-core\include\dmlc/logging.h:241: [16:33:03] d:\chhong\mxnet\src\operator./convolution-inl.h:337: Check failed: ksize_x <= dshape[3] && ksize_y <= dshape[2] kernel size exceed input
Error: InferShape Error in convolution21: [16:33:03] d:\chhong\mxnet\src\operator./convolution-inl.h:337: Check failed: ksize_x <= dshape[3] && ksize_y <= dshape[2] kernel size exceed input "
_
So what part am I doing wrong?

By trial and error, it seems that in R the data shape should be c(224,224,3),
need confirmation.

Yes, you are right.
Another example is here: https://github.com/dmlc/mxnet/blob/master/example/kaggle-ndsb2/Train.R#L96
https://github.com/dmlc/mxnet/blob/master/example/kaggle-ndsb2/Train.py#L114


chore: update to the main tip of runwasi and libcontainer

It looks like wws is still using select!

Remoged

My local integraion tests passed. Hopefully the CI will pass too this time

Umm I am not sure why the slight test still failed...

Congrats @Mossaka !


fix(docs): Fix maximize button issue

Fixed #2848 issue

Codecov Report

Merging #2853 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2853   +/-   ##
=======================================
  Coverage   99.74%   99.74%
=======================================
  Files         160      160
  Lines        2777     2777
=======================================
  Hits         2770     2770
  Misses          7        7

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 7e79cd3...65cd4f7. Read the comment docs.

@levithomason Could you review PR?

This is indeed the right fix, however, seems we've crossed paths in our efforts.  I've removed the _meta object from our components which affects how we generate docs and tests.  This included fixing the maximize feature.  See #2840.
Normally, I would merge this PR and integrate it into my PR.  However, my PR changes some fundamental things with how links are dealt with.  I will need to merge that effort instead.  Apologies for the collision!


atom-existdb process does not quit, respawns upon restart

Steps to reproduce (assumes Atom 1.9.8 and atom-existdb 0.3.3 installed via Atom's package manager):

Start atom
Quit atom
atom-existdb remains in Activity Monitor

Repeating 5x yields 5 atom-existdb processes:

I just confirmed the issue is still present with the current versions, Atom 1.12.6 and atom-existdb 0.3.3 (installed via Preferences > Install, not built from source). I'd be happy to test or provide more info, etc.

cannot reproduce this any longer with atom-existd 0.4.1, seems fixed.

I'll check too, but to confirm, which OS and version are you using?

macOS 10.12.3 atom 1.14.3

Okay, I've just checked - using the same OS and versions, in fact - and confirmed that the problem is no longer present. Upon quitting Atom, all Atom-related processes are liquidated.


Session level API caching

Coverage increased (+0.5%) to 28.868% when pulling 6ae8e16148bb35c613dfd4c0fc82f2e69556246d on session-caching into f959dc6a2c9b8ae6424ed9c03bef921572e0f617 on master.

Nice work! 👍
Remaining question before putting the merge label 😸 .

should we leverage LayeredCache, instead of sync.Map?(however, there will be no changes in this PR)

should we directly embed AWS API in our wrapper API interfaces? It's convenient, but we are locked to specific aws go sdk version (unrelated to this PR, but just wondering what should the correct abstraction level in our AWS API wrapper, and whether we should do cache there, since caching on session level is a "kind of hacky")

should we indeed need caching, once we implemented "only refresh specific ingress when changes happen"?

That's a good idea. Can backlog it on the caching package.
I need to be convinced on having an opinion on this one way or the other.. I'm not really worried about being locked to the AWS SDK version, maybe I should be?
We will probably still need it for larger deployments. The API throttles at relatively low rates and is troublesome to track down what is making API calls when you hit the limit. Anything we can do to reduce superfluous queries is good in my book.

For #2, actually i'm ok with both solution if we adding more integration test cases for the caching(just incase aws break the internal implementation some how).
For #3, i'm afraid our local caching might cause problems. E.g. our ingress controller wants to update securityGroups on nodes, but it overrides changes make by other components/user due to there is new API like addSecurityGroup, and aws doesn't support compareAndSet.

/lgtm


M3-4016: Some changes to clarify Linode password fields in Reset Root Password vs. Rebuild

Description
Some users trying to reset their passwords may be confused by the Root Password fields in the Rebuild & Settings tabs, because each field has the same guidance information re: password requirements. It might also be easy to overlook the fact that rebuilding will wipe the Linode.
I bolded the "Rebuilding will destroy all data on all existing disks on this Linode." text in the Rebuild tab to make it more prominent, and added some helper text to the Root Password fields in the Rebuild & Settings tabs. The exact verbiage is still preliminary; awaiting Jay's approval on it.
Type of Change

Non breaking change ('update', 'change')

Trying to remedy a TypeScript error inLinodeRebuild.tsx currently when passing the passwordHelperText prop to RebuildFromImage:

Once I've squared that away, I'll replicate this pattern for RebuildFromStackScript.tsx also.

Trying to remedy a TypeScript error inLinodeRebuild.tsx currently when passing the passwordHelperText prop to RebuildFromImage:

Once I've squared that away, I'll replicate this pattern for RebuildFromStackScript.tsx also.

This is due to line 243 of RebuildFromImage. We mentioned this in the FP tech talk: you've added a Props interface elsewhere in the component, but compose is explicitly telling TypeScript that RebuildFromStackScript is a component that accepts {} as props.
Passing the message all the way down from LinodeRebuild makes sense, since you have to reuse the same message in the StackScript rebuild flow. I don't think you need to pass passwordHelperTextPosition since it'll be the same everywhere AccessPanel is used.

Helper text wording approved by Jay, as well as the label change to "New Root Password"


Version 24.0.1 - ERROR WHILE READING SOURCE: SQL Error [208] [42000]

Description
Hello, yesterday when install the 24.0.1 version i hav this error:
/* ERROR WHILE READING SOURCE: SQL Error [208] [42000]: SYS.SYSPROCEDURE not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output). */
I had that install the 24.0,0 version again for resolve the error
DBeaver Version
24.0.1
Operating System
windows 10 64
Database and driver
sybase
Steps to reproduce
whan open store procedure
Additional context
VPN private

Hello @rojasadrianza
Please specify your server version.
You can check it in your connections settings -> test connection

Hello. I'm using Sybase ASE and I have the same behaviour. Here's the server version:
Adaptive Server Enterprise <IP_ADDRESS>
In previous DBEAVER version I was able to access any source from any procedure.

Does this query work for you?
select * from sys.SYSSOURCE
@rpallamo @rojasadrianza

Does this query work for you?
select * from sys.SYSSOURCE
@rpallamo @rojasadrianza

That works only on Sybase/SAP IQ family of products (Adaptive Server Anywhere aka ASA, IQ, etc.). On Adaptive Server Enterprise aka ASE the query for source code is the same as with Microsoft SQL Server (the two forked in the 1990s):
select sc.text
from dbo.sysobjects so
join dbo.syscomments sc on sc.id = so.id
where user_name(so.uid)=:ownerName and so.name=:procName
order by sc.colid
Previous versions of SQLServerMetaModel.java code had it right using"isSapIQ" function (which unfortunately doesn't recognize Anywhere products as part of SAP IQ product family)

I also encountered this issue and reverted back to 24.0.0 for now

Closed as a duplicate of https://github.com/dbeaver/dbeaver/issues/23259

HI @PippoSkaio,
Could you please check and respond
Does this query work fine on Sysbase ASE server?
SELECT * from SYS.SYSPROCEDURE

You can see the answer to your question in this link:
https://github.com/dbeaver/dbeaver/issues/23247#issuecomment-2026958812
Basically, SYS.SYSPROCEDURE is only available for SYBASE IQ products, not ASE products.
Regards.
From: Sergei Kovalchuk @.***>
Sent: miércoles, 24 de abril de 2024 11:11
To: dbeaver/dbeaver
Cc: Palla Moro, Raul; Mention
Subject: Re: [dbeaver/dbeaver] Version 24.0.1 - ERROR WHILE READING SOURCE: SQL Error [208] [42000] (Issue #23247)
This mail has been sent from an external source. Do not reply to it, or open any links/attachments unless you are sure of the sender's identity.
HI @PippoSkaiohttps://github.com/PippoSkaio,
Could you please check and respond
Does this query work fine on Sysbase ASE server?
SELECT * from SYS.SYSPROCEDURE
—
Reply to this email directly, view it on GitHubhttps://github.com/dbeaver/dbeaver/issues/23247#issuecomment-2074469957, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BFMDJFUSTJSFPIP7KP62H33Y65ZJFAVCNFSM6AAAAABFJXQBMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUGQ3DSOJVG4.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

HI @PippoSkaio, Could you please check and respond Does this query work fine on Sysbase ASE server? SELECT * from SYS.SYSPROCEDURE

Nope, not working on ASE
I tested it anyway in DBeaver and DON'T work on:

Adaptive Server Enterprise/12.5.3/EBF 13331
Adaptive Server Enterprise/15.7.0/EBF 20953
Adaptive Server Enterprise/16.0 SP03 PL08/EBF 28923

It works on:

Adaptive Server Anywhere <IP_ADDRESS>5
Adaptive Server Anywhere 9.0.2 EBF 3951
IQ versions?

Connections to ASE are with Sybase jTDS protocol (net.sourceforge.jtds.jdbc.Driver)
ASA/IQ connections are with SAP jConnect (com.sybase.jdbc4.jdbc.SybDriver)


Can this work with just javascipt, without Node?

This is not an issue. Just a question/wish.
Is it possible to use this script from vanilla javascript, without using Node?

Are you talking on a browser?

Yes.  In a browser.
On Thu, Nov 21, 2019, 1:40 AM Martin M<EMAIL_ADDRESS>wrote:

Are you talking on a browser?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/skydiver/ewelink-api/issues/40?email_source=notifications&email_token=AGHTZ7IJH2V5WXDIRXIREEDQUWODTA5CNFSM4JPRQCBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEUXSVI#issuecomment-556366165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHTZ7NC73I7XW4772POIZLQUWODTANCNFSM4JPRQCBA
.

Yes, but you need to use something like webpack.
I was able to use the library with nuxtjs and nextjs.

This can be closed


adding new Game Category enum values

Updated Game Category enums to support the values:

mod, 5
episode, 6
season, 7

IGDB documentation:
https://api-docs.igdb.com/#game-enums
I regenerated the go generate files via stringer and looks like more recent versions output an additional func than originally.

Coverage remained the same at 94.846% when pulling 4e66798735c2db9a67180139ee802ddcebf56b54 on Lavos:game-category-enums into 21fbf59ec17c84e89951c351674e01f78d9491dd on Henry-Sarabia:master.

Nice work. I appreciate it.
Tangentially, the new stringer verification code is so neat.

Oops, got too excited. Reverting changes before I break semver. Will include changes in next major update.

Understood, thank you!


Usage report per app

Hello, at some point we had usage reports / apps, which is much more relevant for a platform admin than usage / device type.
Where can I get back access to this data?

@hananeseo
Thanks for your feedback. For product-related feedback, visit https://ideas.powerapps.com.


chore: adding distribute fee events to ics29

Description
closes: #2847
Commit Message / Changelog Entry
chore: adding distribute fee events to ics29

see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

Should we extend the existing tests to use the brand new AssertEvents function to check that the events emitted are what we expect?

Most of the existing tests call into the keeper functions directly. To get at the events we'll need to route a new MsgAcknowledgement with the testing library's chain.SendMsgs(...) method. I can look at adding a test to events_test.go but it might take a good bit of boilerplate to generate a proof etc..

Codecov Report

Merging #2975 (c838356) into main (ff766e3) will increase coverage by 0.04%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2975      +/-   ##
==========================================
+ Coverage   78.41%   78.45%   +0.04%
==========================================
  Files         178      178
  Lines       12327    12343      +16
==========================================
+ Hits         9666     9684      +18
+ Misses       2236     2234       -2
  Partials      425      425

Impacted Files
Coverage Δ

modules/apps/29-fee/keeper/escrow.go
92.81% <100.00%> (+0.19%)
:arrow_up:

modules/apps/29-fee/keeper/events.go
100.00% <100.00%> (ø)

modules/apps/29-fee/keeper/relay.go
94.11% <0.00%> (+5.88%)
:arrow_up:


Suggestion: Chance of piglin trade some extra items

add option to enable chance of piglin trade some extra items (default: 0) from a list that server owner could customize

https://www.spigotmc.org/resources/custom-piglins-trades-1-16-custom-trades-with-simple-gui.81234/ haven't tried using this?

You can even do it with datapack

ah nice. thanks folks.


Added "ariaPolite" options to enable/disable the aria-live attribute

On some page templates the aria-live="polite" attribute make the entire page not accesible with screen readers because it force the screen reader to read the slick content on changes and users could not focus on other page fragments.

This is a decent quick fix, though I think the ideal solution is to add/remove aria-live="polite" when the slideshow or an element in it is focused. That way a screen reader will announce the content changes only when you're interacting with the element.

Good suggestion but I think is not the scope of my fix when add/remove the aria-live: the property only enable/disable the attribute.

I agee that removing aria live is a good idea because without a pause button it Will force screenreader user to listen to the update each time it occurre.
Adding / removing it dynamically when moving focus on slide or inside it is not usefull because if you move focus it Will already read the content without the aria live (or at least user Will start to read it by himself) so in case you have an extra aria live you may have the content read twice.
My opinion is that we must remove aria live or have an option to remove it (so this pull request is good for that) and move focus on the slide when using dots or prev next buttons (need a specific pull request for that part)

And when having more than one block of content per slide the focus must go on the first block of content of the new serie of blocks when


Replace the incorrect commit keyword with rev

Cargo uses "revision" (rev) instead of "commit" as a keyword.

@DarkEld3r CI is failing.

@bkchr I'm going to look at that. What do you think about simply removing the revision? It was ignored before after all.

No, please fix this.

We should actually swap to 0.1.0 now that it has been published - https://crates.io/crates/schnorrkel

@jacogr yeah!

@DarkEld3r was this supposed to be closed automatically on that issue? probably we still need a commit here to point to schnorrkel 0.1.0

@rphmeier I didn't expect that Github would close this pull request.
I have updated it and the build has passed.


Backport 16659: Update function signature in grpc_security

Backport #16659

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,955,061      Total (=)      1,955,061

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,843,023      Total (>)     10,843,022

 No significant differences in binary sizes

[microbenchmarks] No significant performance differences

Bazel test failures - #16687
Interop tests failures - #16531


CLI client messages l10n

Use localize package.

Basically this is done, russian translation is complete for now.


Honor maxSurge value for control plane and worker node group configur…

…ations for bare metal
extra hardware validations for upgrade
Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

/unhold


Azure File Share: Provide Script to create folders within a File Share

Is your feature request related to a problem? Please describe.
Currently, this is not supported through ARM-templates, hence the idea to create a PS-script for this being part of the Arcus.Scripting.Storage.FileShare
Describe the solution you'd like
Something similar to this:
https://github.com/mbraekman/Powershell/blob/master/Azure/AzureStorage-CreateFolderWithinAzureFileShare.ps1
Suggested command name (open to better suggestions):

Create-AzFileShareStorageFolder

Describe alternatives you've considered
Since ARM-templates do not support this, the alternative is to create it manually.

A bit strange to add it to a patch release? Maybe make it v0.3?

A bit strange to add it to a patch release? Maybe make it v0.3?

 My mistake; should've been the next full release.


ACT-406 Create fixtures for Country and Sector data as global picklist in all environments

GIVEN I am a logged in user
AND I navigate to Components > Contacts > click on a Contact record

AND I navigate to the Components > Site > click on a Site record > click on the Location tab

AND I navigate to the Components > Stakeholders > click on a stakeholder record > details page

THEN I should be able to click on any of the 3 Country fields
AND see a list of countries around the world based on ISO standards.
Here is the attached list of Countries (see country tab):  https://docs.google.com/spreadsheets/d/1gRr7-E6Z5WdH4ud8EIpUwcXySbgSSjFZPAoZA7S3EMg/edit?usp=sharing

For Sector, the sector picklist are used in the Program, Project and Indicator models. These should be standard picklists that are generated in every new environment that we deploy.

@Kimaiyo077 the contacts and sites country fields have been update with the options but the stakeholders has not

<img width="1359" alt="image src="https://user-images.githubusercontent.com/16039248/79557499-50b4a380-80ab-11ea-95e1-bd50c52b301d.png">
@andrewtpham I think we should add the country field in the Add contact modal instead of updating it once the contact has been created.

Good catch @sannleen that this isnt working on stakeholder details page! Yes, let's create a separate ticket to add the Country field to the create modal for contacts 👍

Discussed with @Kimaiyo077 and we will create a separate ticket to solve this issue. Fixtures is a separate issue to this defect you found @sannleen

Add Country field to the contact modal: https://github.com/hikaya-io/activity/issues/469


Migrate RN Prod Dependencies

To support RN v0.57, update node modules to the latest and stable version for production environment.

Dependency Updates:

Dependency
Old Version
New Version

@babel/runtime
n/a
7.3.1

moment
2.21.0
2.24.0

react
16.3.0-alpha.1
16.6.3

react-native
0.54.4
0.57.8

react-native-animatable
1.2.4
1.3.1

react-native-gesture-handler
n/a
1.0.15

react-native-maps
<0.21.0
0.23.0

react-native-popup-menu
0.12.3
0.15.0

react-native-sortable-list
0.0.21
0.0.22

react-navigation
1.5.8
3.0.9

Ready for testing on branch react-native-57-upgrade

Initial testing has passed. Issues encountered in beta will be logged separately.


Segment mode no longer isolates crashes within segments

Segment mode is supposed to ignore crashes within individual segments, and keep on processing the rest of the segments. After several refactorings over the past month, this no longer works as intended, and a crash will simply cause everything to fail.
This happened because:

I misunderstood the purpose of segment mode (thought it was for OOM errors only).
The behavior was not tested.

So, we need to reimplement the behavior (not hard) and test it (slightly harder).

@henry-lp As I understand it, these are the requirements of segment mode.

Only load one segment into memory at a time (still works)
Ignore crashes within individual segments (does not work, I broke it in a "refactoring" and will restore it as part of this issue)

Is there anything you'd like to add?

Sounds good :)

Great, then I'll have it restored to its original functionality in a few days or so :)

I leave it to you then :) .

Yup. Just to be clear, the actual segmentation (i.e. the heart of your work) is entirely unchanged, I just merged the SegmentRepair and DefaultRepair classes into one as they were largely the same. This is the current equivalent of the entire SegmentRepair class:
https://github.com/SpoonLabs/sorald/blob/1af069736f40243245cecccba3788c304ee25ad7/src/main/java/sorald/Repair.java#L125-L140
That's also where the problem lies, any exception raised in that stream will just bubble straight up to the surface, which is what needs to be tweaked. Tweaking that to ignore exceptions is trivial, I just don't quite know how to reliably test it without resorting to mocking (which I'd rather avoid).
Ps. I'll definitely ping you if I need to go digging in the gnarlier parts of the segmentation functionality. Wouldn't want a repeat of this little incidence.


Kali-rolling fails to launch after first time set-up

Please paste the output of the following command here: sudo edit-chroot -all

kali

Please describe your issue:
I've installed kali-rolling with KDE-desktop onto my Chromebook Pixel 2013 which is running stable OS version 57.0.2987.123 (64-bit). After installation I installed the latest kali metapackage "kali-linux-all". After I exit the croot and restart my laptop I am facing the following error once I try to enter the chroot again via "sudo startkde -n kali"
crosh> shell chronos@localhost / $ sudo startkde -n kali Entering /mnt/stateful_partition/crouton/chroots/kali...
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.19.2 Release Date: 2017-03-02 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian Current Operating System: Linux localhost 3.8.11 #1 SMP Wed Mar 22 23:46:47 PDT 2017 x86_64 Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=39be837f-3819-9840-a4a0-45e94adabc2e/PARTNROFF=1 hashtree=PARTUUID=39be837f-3819-9840-a4a0-45e94adabc2e/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=78ae12c7753ef20aca7df72c42928a9a2a7c9567 salt=b498de76873fb744ad0d5e41a941f76e73de930f7d72ab4e56feb1b78891c4ab" noinitrd vt.global_cursor_default=0 kern_guid=39be837f-3819-9840-a4a0-45e94adabc2e add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic iTCO_vendor_support.vendorsupport=3 gpt Build Date: 03 March 2017 03:14:41PM xorg-server 2:1.19.2-1 (https://www.debian.org/support) Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (++) Log file: "/tmp/Xorg.crouton.1.log", Time: Wed Mar 29 16:24:17 2017 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory) (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. /usr/bin/xinit: giving up /usr/bin/xinit: unable to connect to X server: Connection refused /usr/bin/xinit: server error Unmounting /mnt/stateful_partition/crouton/chroots/kali...
If known, describe the steps to reproduce the issue:
Chromebook Pixel 2013 running latest Stable branch of ChromeOS.

Install kali-rolling via "sudo sh ~/Downloads/crouton -r kali-rolling -t audio,chrome,core,extension,keyboard,kde-desktop -n kali"

Install Kali Metapackage via "sudo install kali-linux-all" within Chroot.

Shutdown/exit Chroot, then try and enter it again via "sudo startkde -n kali"

Same heere ( i think..)
But, attention. Linux noob incoming.
(kali)kali@localhost:~$ croutonversion
crouton: version 1-20170315143304~master:95589555
release: kali-rolling
architecture: amd64
xmethod: xorg
targets: audio,chrome,core,extension,keyboard,kde-desktop
host: version 9413.0.0 (Official Build) dev-channel cyan
kernel: Linux localhost 3.18.0-14511-g55d103f4e8cd #1 SMP PREEMPT Wed Mar 29 18:46:15 PDT 2017 x86_64 GNU/Linux
freon: yes

sudo startkde -n kali

Entering /mnt/stateful_partition/crouton/chroots/kali...

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux localhost 3.18.0-14511-g55d103f4e8cd #1 SMP PREEMPT Wed Mar 29 18:46:15 PDT 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3584000 verity payload=PARTUUID=cf467906-38d9-614c-85ac-d989d41961bd/PARTNROFF=1 hashtree=PARTUUID=cf467906-38d9-614c-85ac-d989d41961bd/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=732c71f68e55840f8da5c1ce6cbe3a45821d9233 salt=59ffc584990f1c90700db58e4bcc7f200a3fa89c6a95b7ca6a5fb9ff251e4d77" noinitrd vt.global_cursor_default=0 kern_guid=cf467906-38d9-614c-85ac-d989d41961bd add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
Build Date: 03 March 2017  03:14:41PM
xorg-server 2:1.19.2-1 (https://www.debian.org/support)
Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Mon Apr 10 16:12:28 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory)
(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
Unmounting /mnt/stateful_partition/crouton/chroots/kali...

But! - WtF - Wow for this work!
at least it worked once =D

Did further testing, the error is generated after installing the kali-linux-all metapackage. I'm going to test the other metapackages now.

@4rson Currently having the same issue and looking in to it. Let me know if you found something

@daangruijters I tested the kali-linux-full metapackage as well, same problem occurs. If I don't install any of the kali metapackages I can keep using kali-rolling.

@4rson How do i prevent It from installing meta packages

@4rson @daangruijters I too am brand new and having the same problem. However the guide I fallowed only had me use
"sudo sh ~/Downloads/croutons -r kali-rolling -t xfce"
I have a symbolic link pointing the chroot directory to my micro sd card slot. and a ubuntu release
" -r trusty -t xfce"  installed and brought up a gui
the kali starts out with the same error you have. however I can still use the kali command line by using
"sudo enter-chroot -kali-rolling"  but if I try to start ether gnome or xfce it brings up the same error.
Ill keep working at it but if you find anything please let me know.
-Cheers


Suppress GCC anonymous struct warning

Suppress GCC anonymous struct warning

Looks good to me, how about you, @StrangeZak?

@bvisness Yep, looks fine will merge it in, its stupid C++ compilers do no handle *.h files as C11 in the first place, though.

Sorry to spam this old merge request, but this change gives me compiler warnings.
At least GCC 5.4.0 doesn't know about "-Wgnu-anonymous-struct" and thus I get the warning
.../HandmadeMath.h:184:9: warning: unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
 #pragma GCC diagnostic ignored "-Wgnu-anonymous-struct"

So maybe it shouldn't just check #ifdef __GNUC__ but also the version?
In fact, does that warning even exist in any version of GCC? I only saw it mentioned in clang documentation.
Furthermore, I'd suggest using #pragma GCC diagnostic push (before #pragma GCC diagnostic ignored "-Wgnu-anonymous-struct" and #pragma GCC diagnostic pop (at the end of the file) to make sure that supressing that warning doesn't "leak out" into the users code.
Side-node: If stupid C++ compilers handled *.h as C11 code (instead of C++), tons of software that uses .h for C++ headers would explode, so it's probably better this way ;)

Will look into this tonight, and figure it out!


Separator position and height

Hello,
I've played with custom faces in order to get a coloured space line with doom-theme-one, but for one reason, the right-most hand separator is not in the good place is its height is a little bit smaller than expected.
Any clue ?

Try showing the clock. I think this is because you are not showing the clock/time segment and/or battery status. There is an right to inactive before this, maybe a bug? @domtronn

@jwintz @ieei Sorry for the late reply, and yep, @ieei is right, you need to show something there.
Spaceline breaks down the segments into blocks, and it auto alternates the colours of those blocks - If a block doesn't have any content or is nil, then it'll skip over that changing the colours of the other blocks, which for my purpose is quite annoying!
See, the separators are just characters with a specific background and foreground and at the moment they're not dynamic at all, and kind of depend on the same order.
There's also a bit of a regression/improvement with one of the newer versions of Spaceline 😅 It now hides blocks based on the width of the screen and there's no way to turn that off. What this means is you'll get blocks disappear and separators that transition to the wrong colours (see screenshot)

I'm looking into a way to improve this hopefully!

Oh! I can see you're using my --with-natural-title-bar patch on emacs-plus ! Quite honoured ;-)
As for the separators, I agree, something has to be displayed on the right most hand side.
However, following a previous discussion, the clock may only be visible when it makes sense (at least for me), when emacs is fullscreen.
With no clock displayed, the HUD segment should be referred to as the last one and then, be drawn correctly.

Hello,
I'm reopening this issue, as it makes me feel that on my config, all space line items like buffer name, project name, linked file, cursor position and fullscreen icon are part of the same segments (c.f.) the screenshot.
On the other hand, they are separate segments on README image of spaceline-all-the-icons.
It is related to my config ?
The same applies to vc-current-branch, fly check issues and vc-diffs.
As the space line has become responsive it would be great if any of these items belonged to on single statement ...

Hey @jwintz, Good news is, it's not your config! I've been looking into this for a long time and unfortunately it's not really possible...
The way that I define separators ( so that they work cross platform without sRGB issues ) means that they're treated as individual segments of their own and are hardcoded with the colour transitions between the segments. This has to happen, otherwise the colours transitions don't work correctly.
This means that with the "responsiveness" of the spaceline you'll always have issues with the colours when you hide segments. Personally I think the responsiveness is a bad thing as it will always hide information and you quite often get massive gaps left over.
In theory, being able to define priorities on the segments makes sense but I've not been able to get it working very well 😞
I'm not feeling super motivated to fix or investigate this at the moment as it feels like a huge regression... As such, I'd recommend adding the following config
 (setq spaceline-responsive nil))

If the responsiveness is something you really want, I'd welcome any more information or PRs 🙂 👍

Hey @domtronn, here is for more information. I have followed your advice, by disabling the responsiveness, and also, left the clock icon displayed even though not fullscreen, but that does not change the problem with the separators.

However, it answers one of my previous questions, I admit that segments are actually divided, when I played with custom set faces, (like the white palette of your screenshot for spaceline-highlight-face, I have to find a palette that suites doom-theme-one, knowing that with solaire-mode it changes the modeline background wrt to wether the buffer is editable or not).
I'll try and update package to see if newer versions fix it.
PS: Should I try to propose a PR, can you point me to the place where separator icons are computed ?

@jwintz I just found this post through google and thought your emacs setup looks great, do you mind sharing the config for how it was when those screenshots were taken? If you have it or can remember parts of it


Request for Comment: Displaying Networking Relationships

Summary
We're often asked if Workload Discovery can display networking information such as VPC flow logs as relationships between resources.
For example, "Can I see if this EC2 instance is communicating with this NAT Gateway".
Today, Workload Discovery presents configuration based relationships for networking resources, such as "EC2 instance X is contained in Subnet Y". Workload Discovery cannot show relationships between two resources that are communicating via a network. It might be possible to display this information in Workload Discovery. There may be other related information that is also useful to include.
We'd like to investigate what usecases users have for visualising relationships between networked resources in the tool.
We'd welcome any anecdotes or feedback on how we can improve Workload Discovery in this area. We will update this issue with more information as the investigation progresses.
What is the problem?
Customers would like to see relationships in WD representing actual networking communication between resources. Today, Workload Discovery only shows configuration based relationships such as EC2 instance being associated with an Network Interface. Workload Discovery does not show relationships derived from potential or actual network communication.
What is the solution?
Workload Discovery will support a new relationship type, a network derived relationship. Network derived relationships will be derived from VPC Flow Logs.

I think this would be a fantastic addition to introduce new FinOps processes if added to the graph.  I cover some of these techniques in graph at https://aws.amazon.com/blogs/database/techniques-to-improve-the-state-of-the-art-in-cloud-finops-using-amazon-neptune/, but adding the VPC Flows would also allow you to detect resources that have unused pathways in addition to no pathway.  It will be interesting to see how you can enable these flows on existing resources with minimal disruption, as well as without significant cost. Also, I think it is important to differentiate between when monitoring is active and there is no traffic and when there is no monitoring...so techniques can be applied to the former but not the latter.

Also, I think it is important to differentiate between when monitoring is active and there is no traffic and when there is no monitoring...so techniques can be applied to the former but not the latter.

This is a very good point, we need to make this distinction clear in any diagrams.

+1 on the great idea. In fact, IHAC requesting for it too.


[AIRFLOW-1214] Fix conversion of int type in BigQueryHook

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1214

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

Python's float type conversion support scientific notation so we convert to int first then convert it to int back.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

No test as this is a trivial change.
Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

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

@@            Coverage Diff             @@
##           master    #2306      +/-   ##
==========================================
- Coverage   69.11%   69.09%   -0.03%
==========================================
  Files         144      144
  Lines       11023    11023
==========================================
- Hits         7619     7616       -3
- Misses       3404     3407       +3

Impacted Files
Coverage Δ

airflow/jobs.py
74.1% <0%> (-0.41%)
:arrow_down:

airflow/models.py
87.1% <0%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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


Java, after cmake build, cant able to run example

[100%] Built target generate_common Install the project... -- Install configuration: "Release" -- Installing: /Users/zkamal/Downloads/tdlib/jnibuild2/../example/java/td/lib/libtdutils.a -- Installing: /Users/zkamal/Downloads/tdlib/jnibuild2/../example/java/td/bin/td_generate_java_api -- Up-to-date: /Users/zkamal/Downloads/tdlib/jnibuild2/../example/java/td/bin/td/generate/JavadocTlDocumentationGenerator.php -- Up-to-date: /Users/zkamal/Downloads/tdlib/jnibuild2/../example/java/td/bin/td/generate/TlDocumentationGenerator.php -- Up-to-date: /Users/zkamal/Downloads/tdlib/jnibuild2/../example/java/td/bin/td/generate/scheme/td_api.tlo -- Up-to-date: /Users/zkamal/Downloads/tdlib/jnibuild2/../example/java/td/bin/td/generate/scheme/td_api.tl
Logs seems fine, after that i try to run the below command
cd <path to TDLib sources>/example/java/bin java '-Djava.library.path=.' org/drinkless/tdlib/example/Example
am getting error:
Error: Could not find or load main class org.drinkless.tdlib.example.Example
Seems like Java not built

You need to build Java after TDLib is built and insalled. See https://tdlib.github.io/td/build.html?language=Java for the full build instructions.

Awesome, great thanks


UART ESC interface

What is missing here is the right line in the startup script:
uart_esc start -d /dev/ttySxxx

Somewhere here:
https://github.com/PX4/Firmware/blob/master/posix-configs/eagle/flight/px4-flight.config

It should be noted that this is not a standard uart esc driver which came with older PX4 port, but a driver based on top of it to support using Pixhawk running this code: https://github.com/diydrones/ardupilot/tree/master/libraries/RC_Channel/examples/RC_UART.
To enable the driver 'uart_esc -D /dev/tty-x' needs be added to px4.config

Thanks Sid. I changed it to lowercase 'd' for the argument to be consistent with the rest of the system.


missing explanation of DiskEncryptionKeyFileName

what is the purpose of the DiskEncryptionKeyFileName tag on the KEK secret?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d9f0eeaf-7290-1f64-5700-a88ec325a9d0
Version Independent ID: 401634dd-56ad-5f64-5436-3563fa438e1a
Content: Azure Disk Encryption sample scripts - Azure Linux Virtual Machines
Content Source: articles/virtual-machines/linux/disk-encryption-sample-scripts.md
Service: security
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@pmozbert
Thanks for your feedback! We will investigate and update as appropriate.

The value of the DiskEncryptionKeyFileName is the same as the secret name.
This is described here: https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/backup/backup-azure-restore-key-secret.md

Hope this helps.
We will proceed to close this thread but if you have further questions feel free to ask in Microsoft Q&A.


Attach disk action causing intermittent failures when bosh registry is not present

After removal of bosh registry from the config, we observe intermittent issues when attaching a persistent disk. We believe the reason for the issues is the cpi code, attach disk action, line 46:
https://github.com/cloudfoundry-incubator/bosh-alicloud-cpi-release/blob/47a510af1b73dea69987425c03033d1394b41d1a/src/bosh-alicloud-cpi/action/attach_disk.go#L46
Lines 46-63 are executed only if you do not have the bosh registry configured, the cpi stops the vm and then starts it again in line 92-109.
The vm is started  for the  first  time  in the create-vm step:
https://github.com/cloudfoundry-incubator/bosh-alicloud-cpi-release/blob/47a510af1b73dea69987425c03033d1394b41d1a/src/bosh-alicloud-cpi/action/create_vm.go#L356
and the bosh agent starts up and tries to bootstrap the config and shortly after, during the attach disk step, we stop the vm. This can corrupt bosh agent config file(s), for example, we observed empty /var/vcap/bosh/agent_state.json - which causes bosh agent to enter infinite restart loop:
2021-07-19_14:05:10.39974 [main] 2021/07/19 14:05:10 ERROR - App setup Loading state: Unmarshalling bootstrap state: unexpected end of JSON input
2021-07-19_14:05:10.39974 [main] 2021/07/19 14:05:10 ERROR - Agent exited with error: Loading state: Unmarshalling bootstrap state: unexpected end of JSON input
2021-07-19_14:05:11.40837 [main] 2021/07/19 14:05:11 DEBUG - Starting agent
2021-07-19_14:05:11.40839 [File System] 2021/07/19 14:05:11 DEBUG - Reading file /var/vcap/bosh/agent.json
2021-07-19_14:05:11.40841 [File System] 2021/07/19 14:05:11 DEBUG - Read content
2021-07-19_14:05:11.40841 ********************
2021-07-19_14:05:11.40841 {
2021-07-19_14:05:11.40841   "Platform": {
2021-07-19_14:05:11.40842     "Linux": {
2021-07-19_14:05:11.40842       "PartitionerType": "parted",
2021-07-19_14:05:11.40842       "CreatePartitionIfNoEphemeralDisk": true,
2021-07-19_14:05:11.40842       "DevicePathResolutionType": "virtio"
2021-07-19_14:05:11.40843     }
2021-07-19_14:05:11.40843   },
2021-07-19_14:05:11.40843   "Infrastructure": {
2021-07-19_14:05:11.40844     "Settings": {
2021-07-19_14:05:11.40844       "Sources": [
2021-07-19_14:05:11.40844         {
2021-07-19_14:05:11.40844           "Type": "HTTP",
2021-07-19_14:05:11.40845           "URI": "http://<IP_ADDRESS>",
2021-07-19_14:05:11.40845           "UserDataPath": "/latest/user-data",
2021-07-19_14:05:11.40845           "InstanceIDPath": "/latest/meta-data/instance-id",
2021-07-19_14:05:11.40846           "SSHKeysPath": "/latest/meta-data/public-keys/0/openssh-key"
2021-07-19_14:05:11.40846         }
2021-07-19_14:05:11.40846       ],
2021-07-19_14:05:11.40846       "UseServerName": false,
2021-07-19_14:05:11.40847       "UseRegistry": true
2021-07-19_14:05:11.40847     }
2021-07-19_14:05:11.40847   }
2021-07-19_14:05:11.40847 }
2021-07-19_14:05:11.40848
2021-07-19_14:05:11.40848 ********************
2021-07-19_14:05:11.40848 [File System] 2021/07/19 14:05:11 DEBUG - Reading file /var/vcap/bosh/etc/stemcell_version
2021-07-19_14:05:11.40849 [File System] 2021/07/19 14:05:11 DEBUG - Read content
2021-07-19_14:05:11.40849 ********************
2021-07-19_14:05:11.40849 1.99
2021-07-19_14:05:11.40849 ********************
2021-07-19_14:05:11.40850 [File System] 2021/07/19 14:05:11 DEBUG - Reading file /var/vcap/bosh/etc/stemcell_git_sha1
2021-07-19_14:05:11.40851 [File System] 2021/07/19 14:05:11 DEBUG - Read content
2021-07-19_14:05:11.40851 ********************
2021-07-19_14:05:11.40851 45d72204ed8c7dba77353ff8c2eb53a477372607+
2021-07-19_14:05:11.40852 ********************
2021-07-19_14:05:11.40852 [App] 2021/07/19 14:05:11 INFO - Running on stemcell version '1.99' (git: 45d72204ed8c7dba77353ff8c2eb53a477372607+)
2021-07-19_14:05:11.40852 [File System] 2021/07/19 14:05:11 DEBUG - Checking if file exists /var/vcap/bosh/agent_state.json
2021-07-19_14:05:11.40853 [File System] 2021/07/19 14:05:11 DEBUG - Stat '/var/vcap/bosh/agent_state.json'
2021-07-19_14:05:11.40853 [File System] 2021/07/19 14:05:11 DEBUG - Reading file /var/vcap/bosh/agent_state.json
2021-07-19_14:05:11.40853 [File System] 2021/07/19 14:05:11 DEBUG - Read content
2021-07-19_14:05:11.40853 ********************
2021-07-19_14:05:11.40853
2021-07-19_14:05:11.40854 ********************
2021-07-19_14:05:11.40854 [main] 2021/07/19 14:05:11 ERROR - App setup Loading state: Unmarshalling bootstrap state: unexpected end of JSON input
2021-07-19_14:05:11.40854 [main] 2021/07/19 14:05:11 ERROR - Agent exited with error: Loading state: Unmarshalling bootstrap state: unexpected end of JSON input

We also observed empty ssh host keys, these are generated on first boot:
https://github.com/cloudfoundry/bosh-linux-stemcell-builder/blob/7320d9060f70deb154e0a9fba688e5c7210bf8d6/stemcell_builder/stages/base_ubuntu_firstboot/assets/root/firstboot.sh#L5

When this happens you are not able to ssh into the vm.

This issue is intermittent, roughly about 50% reproducibility.  You should be able to reproduce it: deploy bosh without registry and try deploying something that has a persistent disk and vm is being re-created.


Add X's to close open menus, and close menus when clicking on body.

requested in #330

@juliusv got approval from mr, so just waiting on your approval

Nice! This doesn't only work, but it gets all the nuances right, including highlights and closing panels only when clicking outside of certain areas.
:+1: besides the mini nit (gotta keep our comments clean and sentence-style :) )


Datatables didn't find DT_RowId

Hi,
i need some help. :) Datatables didn't find DT_RowId in my table.
My Datatable works in server-side mode. The syntax of my received JSON(array) is:
[["3","email<EMAIL_ADDRESS>Thereby columns:[{...,data: "DT_RowId",...}] can be found, did i need a JSON (object) like
[{"DT_RowId":"3"<EMAIL_ADDRESS>?
Greetings
Patrick

I don't know why i can't access the row by name. But with the direct number and a JSON(array) it works. :)
id: "NiceApp",
title: "go on",
data: 3,
....

Closing as DT_RowId is obsolete now


Kernel problem on arm64

Today I tried the portable multi-node cluster on my arm64 devices.
After executing docker-multinode/master.sh, system has stucked. Following is kernel messages caused by it.
Sep 25 01:33:18 linaro-developer kernel: [  845.193079] ------------[ cut here ]------------
Sep 25 01:33:18 linaro-developer kernel: [  845.197830] WARNING: CPU: 5 PID: 3210 at kernel/sched/core.c:2603 preempt_count_add+0x10c/0x110()
Sep 25 01:33:18 linaro-developer kernel: [  845.206915] DEBUG_LOCKS_WARN_ON((preempt_count() & PREEMPT_MASK) >= PREEMPT_MASK - 10)
Sep 25 01:33:18 linaro-developer kernel: [  845.214850] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc btwilink bluetooth wl18xx(O) wlcore(O) mac80211(O) cfg80211(O) rfkill mali wlcore_sdio(O) st_drv hisi_powerkey compat(O)
Sep 25 01:33:18 linaro-developer kernel: [  845.238759] CPU: 5 PID: 3210 Comm: hyperkube Tainted: G           O   3.18.0-linaro-hikey #1
Sep 25 01:33:18 linaro-developer kernel: [  845.247376] Call trace:
Sep 25 01:33:18 linaro-developer kernel: [  845.249906] [<ffffffc000088534>] dump_backtrace+0x0/0x11c
Sep 25 01:33:19 linaro-developer kernel: [  845.256835] [<ffffffc000088660>] show_stack+0x10/0x1c
Sep 25 01:33:19 linaro-developer kernel: [  845.263276] [<ffffffc0007ec18c>] dump_stack+0x7c/0xc0
Sep 25 01:33:19 linaro-developer kernel: [  845.269705] [<ffffffc0000afb24>] warn_slowpath_common+0x8c/0xb8
Sep 25 01:33:19 linaro-developer kernel: [  845.276996] [<ffffffc0000afb9c>] warn_slowpath_fmt+0x4c/0x58
Sep 25 01:33:19 linaro-developer kernel: [  845.284050] [<ffffffc0000d5478>] preempt_count_add+0x108/0x110
Sep 25 01:33:19 linaro-developer kernel: [  845.291268] [<ffffffc0007f0904>] _raw_spin_lock+0x14/0x54
Sep 25 01:33:19 linaro-developer kernel: [  845.297232] [<ffffffc0006cd918>] nf_conntrack_set_hashsize+0x9c/0x228
Sep 25 01:33:19 linaro-developer kernel: [  845.303806] [<ffffffc0000cb51c>] param_attr_store+0x58/0xb4
Sep 25 01:33:19 linaro-developer kernel: [  845.309498] [<ffffffc0000caa1c>] module_attr_store+0x1c/0x34
Sep 25 01:33:19 linaro-developer kernel: [  845.315262] [<ffffffc00023c278>] sysfs_kf_write+0x3c/0x50
Sep 25 01:33:19 linaro-developer kernel: [  845.320774] [<ffffffc00023b7c4>] kernfs_fop_write+0x10c/0x178
Sep 25 01:33:19 linaro-developer kernel: [  845.326641] [<ffffffc0001c87b0>] vfs_write+0x98/0x1d8
Sep 25 01:33:19 linaro-developer kernel: [  845.331820] [<ffffffc0001c9070>] SyS_write+0x40/0xa0
Sep 25 01:33:19 linaro-developer kernel: [  845.336880] ---[ end trace fcc0fa22ce02156e ]---
Sep 25 01:33:19 linaro-developer kernel: [  845.342383] Unable to handle kernel paging request at virtual address<PHONE_NUMBER>
Sep 25 01:33:19 linaro-developer kernel: [  845.349986] pgd = ffffffc061854000

Does anyone have any idea about this?

Please post details about the host OS.
Did you customize and settings of docker-multinode?

Hardware: Hikey (ARM Cortex-A53)
OS:  /etc/os-release :
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="https://bugs.debian.org/"
And I did not customize settings of docker-multinode.

Sorry, I have confused"arm64" with "amd64". Same issue as?
https://github.com/kubernetes/kube-deploy/issues/219#issuecomment-246193811

Sorry for late. I executed the master.sh today to know if the previous problem is the same issue you mentioned.
However today it started with no problem!
I do not know what was changed in my systems though.
Maybe this issue then may be closed.

In fact it was not no problem. Another error suppressed the error:
level=error msg="Handler for GET /images/gcr.io/google_containers/kube-addon-manager-arm64:v5.1/json returned error: No such image: gcr.io/google_containers/kube-addon-manager-arm64:v5.1"

So I pulled gcr.io/google_containers/kube-addon-manager-arm64:v5 and tagged v5.1 with that to proceed. And again system stuck like this;
Sep 30 08:53:35 linaro-developer dockerd[14119]: time="2016-09-30T08:53:35.392864000Z" level=warning msg="Seccomp is not enabled in your kernel, running container without default profile."
Sep 30 08:53:41 linaro-developer dockerd[14119]: time="2016-09-30T08:53:41.184205000Z" level=warning msg="Seccomp is not enabled in your kernel, running container without default profile."
Sep 30 08:53:41 linaro-developer NetworkManager[2019]: <info> (vetheb41aad): device is virtual, marking as unmanaged
Sep 30 08:53:41 linaro-developer NetworkManager[2019]: <info> (vetheb41aad): carrier is OFF
Sep 30 08:53:41 linaro-developer NetworkManager[2019]: <info> (vetheb41aad): new Veth device (driver: 'unknown' ifindex: 1821)
Sep 30 08:53:41 linaro-developer NetworkManager[2019]: <info> (vetheb41aad): exported as /org/freedesktop/NetworkManager/Devices/1939
Sep 30 08:53:41 linaro-developer kernel: [442005.301560] device vethe2f2355 entered promiscuous mode
Sep 30 08:53:41 linaro-developer kernel: [442005.316823] IPv6: ADDRCONF(NETDEV_UP): vethe2f2355: link is not ready
Sep 30 08:53:41 linaro-developer kernel: [442005.337837] device veth6160014 entered promiscuous mode
Sep 30 08:53:41 linaro-developer kernel: [442005.348984] IPv6: ADDRCONF(NETDEV_UP): veth6160014: link is not ready
Sep 30 08:53:41 linaro-developer kernel: [442005.359591] docker0: port 2(veth6160014) entered forwarding state
Sep 30 08:53:41 linaro-developer kernel: [442005.369596] docker0: port 2(veth6160014) entered forwarding state
Sep 30 08:53:41 linaro-developer dockerd[14119]: time="2016-09-30T08:53:41.730177000Z" level=warning msg="Seccomp is not enabled in your kernel, running container without default profile."
Sep 30 08:53:41 linaro-developer dockerd[14119]: time="2016-09-30T08:53:41.991565000Z" level=warning msg="Seccomp is not enabled in your kernel, running container without default profile."
Sep 30 08:53:42 linaro-developer kernel: [442006.041888] eth0: renamed from vetheb41aad
Sep 30 08:53:42 linaro-developer kernel: [442006.102725] IPv6: ADDRCONF(NETDEV_CHANGE): vethe2f2355: link becomes ready
Sep 30 08:53:42 linaro-developer kernel: [442006.113966] docker0: port 1(vethe2f2355) entered forwarding state
Sep 30 08:53:42 linaro-developer kernel: [442006.123960] docker0: port 1(vethe2f2355) entered forwarding state
Sep 30 08:53:42 linaro-developer kernel: [442006.289812] docker0: port 2(veth6160014) entered disabled state
Sep 30 08:53:42 linaro-developer NetworkManager[2019]: <info> (vethe2f2355): device is virtual, marking as unmanaged
Sep 30 08:53:42 linaro-developer kernel: [442006.423176] eth0: renamed from vethf301ead
Sep 30 08:53:42 linaro-developer NetworkManager[2019]: <info> (vethe2f2355): link connected
Sep 30 08:53:42 linaro-developer NetworkManager[2019]: <info> (vethe2f2355): carrier is ON
Sep 30 08:53:42 linaro-developer NetworkManager[2019]: <info> (vethe2f2355): new Veth device (driver: 'unknown' ifindex: 1822)
Sep 30 08:53:42 linaro-developer NetworkManager[2019]: <info> (vethe2f2355): exported as /org/freedesktop/NetworkManager/Devices/1940
Sep 30 08:53:42 linaro-developer kernel: [442006.513419] IPv6: ADDRCONF(NETDEV_CHANGE): veth6160014: link becomes ready
Sep 30 08:53:42 linaro-developer kernel: [442006.524502] docker0: port 2(veth6160014) entered forwarding state
Sep 30 08:53:42 linaro-developer kernel: [442006.534490] docker0: port 2(veth6160014) entered forwarding state
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (vethe2f2355): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (docker0): bridge port vethe2f2355 was attached
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (vethe2f2355): enslaved to docker0
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (docker0): link connected
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (vethe2f2355): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> Activation (vethe2f2355) starting connection 'vethe2f2355'
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> Activation (vethe2f2355) Stage 1 of 5 (Device Prepare) scheduled...
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> devices added (path: /sys/devices/virtual/net/vethe2f2355, iface: vethe2f2355)
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> device added (path: /sys/devices/virtual/net/vethe2f2355, iface: vethe2f2355): no ifupdown configuration found.
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> devices added (path: /sys/devices/virtual/net/vetheb41aad, iface: vetheb41aad)
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> device added (path: /sys/devices/virtual/net/vetheb41aad, iface: vetheb41aad): no ifupdown configuration found.
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> devices added (path: /sys/devices/virtual/net/veth6160014, iface: veth6160014)
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> device added (path: /sys/devices/virtual/net/veth6160014, iface: veth6160014): no ifupdown configuration found.
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> devices added (path: /sys/devices/virtual/net/vethf301ead, iface: vethf301ead)
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> device added (path: /sys/devices/virtual/net/vethf301ead, iface: vethf301ead): no ifupdown configuration found.
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> devices removed (path: /sys/devices/virtual/net/vetheb41aad, iface: vetheb41aad)
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> devices removed (path: /sys/devices/virtual/net/vethf301ead, iface: vethf301ead)
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (veth6160014): device is virtual, marking as unmanaged
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (veth6160014): link connected
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (veth6160014): carrier is ON
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (veth6160014): new Veth device (driver: 'veth' ifindex: 1824)
Sep 30 08:53:43 linaro-developer NetworkManager[2019]: <info> (veth6160014): exported as /org/freedesktop/NetworkManager/Devices/1941
Sep 30 08:53:43 linaro-developer kernel: [442007.990654] ------------[ cut here ]------------
Sep 30 08:53:43 linaro-developer kernel: [442007.999027] WARNING: CPU: 5 PID: 15926 at kernel/sched/core.c:2603 preempt_count_add+0x10c/0x110()
Sep 30 08:53:43 linaro-developer kernel: [442008.011863] DEBUG_LOCKS_WARN_ON((preempt_count() & PREEMPT_MASK) >= PREEMPT_MASK - 10)

Message from syslogd@linaro-developer at Sep 30 08:53:44 ...
 kernel:[442008.069035] Call trace:
Sep 30 08:53:44 linaro-developer kernel: [442008.019878] Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc btwilink bluetooth mali wl18xx(O) wlcore(O) mac80211(O) cfg80211(O) rfkill wlcore_sdio(O) st_drv hisi_powerkey compat(O)
Sep 30 08:53:44 linaro-developer kernel: [442008.056240] CPU: 5 PID: 15926 Comm: hyperkube Tainted: G           O   3.18.0-linaro-hikey #1
Sep 30 08:53:44 linaro-developer kernel: [442008.069035] Call trace:
Sep 30 08:53:44 linaro-developer kernel: [442008.075681] [<ffffffc000088534>] dump_backtrace+0x0/0x11c
Sep 30 08:53:44 linaro-developer kernel: [442008.085316] [<ffffffc000088660>] show_stack+0x10/0x1c
Sep 30 08:53:44 linaro-developer kernel: [442008.094549] [<ffffffc0007ec18c>] dump_stack+0x7c/0xc0
Sep 30 08:53:44 linaro-developer kernel: [442008.103722] [<ffffffc0000afb24>] warn_slowpath_common+0x8c/0xb8
Sep 30 08:53:44 linaro-developer kernel: [442008.113845] [<ffffffc0000afb9c>] warn_slowpath_fmt+0x4c/0x58
Sep 30 08:53:44 linaro-developer kernel: [442008.123700] [<ffffffc0000d5478>] preempt_count_add+0x108/0x110
Sep 30 08:53:44 linaro-developer kernel: [442008.134575] [<ffffffc0007f0904>] _raw_spin_lock+0x14/0x54
Sep 30 08:53:44 linaro-developer kernel: [442008.144192] [<ffffffc0006cd918>] nf_conntrack_set_hashsize+0x9c/0x228
Sep 30 08:53:44 linaro-developer dockerd[14119]: time="2016-09-30T08:53:44.095812000Z" level=error msg="Handler for GET /images/gcr.io/google_containers/kubedns-arm64:1.7/json returned error: No such image: gcr.io/google_containers/kubedns-arm64:1.7"
Sep 30 08:53:44 linaro-developer kernel: [442008.154773] [<ffffffc0000cb51c>] param_attr_store+0x58/0xb4
Sep 30 08:53:44 linaro-developer kernel: [442008.164446] [<ffffffc0000caa1c>] module_attr_store+0x1c/0x34
Sep 30 08:53:44 linaro-developer dockerd[14119]: time="2016-09-30T08:53:44.112041000Z" level=error msg="Handler for GET /images/gcr.io/google_containers/kubernetes-dashboard-arm64:v1.4.0/json returned error: No such image: gcr.io/google_containers/kubernetes-dashboard-arm64:v1.4.0"
Sep 30 08:53:44 linaro-developer kernel: [442008.174180] [<ffffffc00023c278>] sysfs_kf_write+0x3c/0x50
Sep 30 08:53:44 linaro-developer kernel: [442008.183697] [<ffffffc00023b7c4>] kernfs_fop_write+0x10c/0x178
Sep 30 08:53:44 linaro-developer kernel: [442008.193516] [<ffffffc0001c87b0>] vfs_write+0x98/0x1d8
Sep 30 08:53:44 linaro-developer kernel: [442008.202588] [<ffffffc0001c9070>] SyS_write+0x40/0xa0
Sep 30 08:53:44 linaro-developer kernel: [442008.211486] ---[ end trace ae90f43ec9a63ef3 ]---

This does not look like the issue you mentioned.
Thanks.


React.createClass is deprecated

React.createClass is deprecated and will be removed in version 16. Use plain JavaScript classes instead. If you're not yet ready to migrate, create-react-class is available on npm as a drop-in replacement.

React.createClass has been removed in React 16, so this issue is now a showstopper for React 16 upgrades.

+1

https://github.com/coma/svg-reactify/pull/13


Setup github pages with auto API documentation

fixes #30

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 59.712%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
332

Relevant Lines:
556

💛  - Coveralls


Spaces in values not parsed?

The following program fails currently:
extern crate docopt;
use docopt::Docopt;

fn main() {
    let docopt = Docopt::new("
        Usage:
            cargo test [options] [--] [<args>...]

        Options:
            --features FEATURES      description
    ").unwrap();
    let args = docopt.argv(["cargo", "test", "--features=a b"].iter().cloned())
                     .parse()
                     .unwrap_or_else(|e| e.exit());
    assert_eq!(args.get_vec("--features"), vec!["a b"]);
}

Perhaps the space in the argument is throwing off docopt? This was originally reported through https://github.com/rust-lang/cargo/issues/1720.

Definitely a bug. I have a fix. Writing regression tests now.

Thanks @BurntSushi!


[1.11] Do not exit on error during bash loop for the upgrade script

High-level description
1.11 backport of https://github.com/dcos/dcos/pull/2270
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS- Foo the Bar so it stops Bazzing.

Related tickets (optional)
Other tickets related to this change:

DCOS_OSS- Foo the Bar so it stops Bazzing.

Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

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

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot override-status teamcity/dcos/test/aws/onprem/static/strict https://jira.mesosphere.com/browse/DCOS-20807

Please add JIRA to the description - https://jira.mesosphere.com/browse/DCOS_OSS-2028

@mesosphere-mergebot label ship-it


[WIP] Permit custom params for file types that request this

Also, file types can now define custom attributes. Custom attributes
serve a different purpose than configuration attributes: Their values
do not change after a file is created. Thus, we can persist them
directly on the file as opposed to on file usages, since constant
attributes need no versioning.

Coverage increased (+0.0003%) to 99.204% when pulling 94a14bba112ed0bd0833a78c7751eb11aba8a3e8 on aviav:allow-custom-params-for-file-types into 40cda2b30048e8af271c2257a224210a5c2667d3 on codevise:master.

Coverage increased (+0.0003%) to 99.204% when pulling 94a14bba112ed0bd0833a78c7751eb11aba8a3e8 on aviav:allow-custom-params-for-file-types into 40cda2b30048e8af271c2257a224210a5c2667d3 on codevise:master.

Coverage increased (+0.0003%) to 99.204% when pulling 600c3010947d1448da86d3c728aef22f70a30ca7 on aviav:allow-custom-params-for-file-types into 40cda2b30048e8af271c2257a224210a5c2667d3 on codevise:master.

Coverage increased (+0.0003%) to 99.204% when pulling 600c3010947d1448da86d3c728aef22f70a30ca7 on aviav:allow-custom-params-for-file-types into 40cda2b30048e8af271c2257a224210a5c2667d3 on codevise:master.

merged as part of #1024


FIX: connect doesn't break zip now

Closes #180

it seems that kafka is breaking this

This looks like a good one to resubmit.


Check for SMO and DMO XPs Enabled on an instance

Many thanks to @ConstantineK for the help with this one.
Fixes #448
Changes proposed in this pull request:

Added configuration check for 'SMO and DMO XPs enabled' and errors out if found.

How to test this code:

[ ] Attempt to connect to an instance with 'SMO and DMO XPs enabled' set to 1.
[ ] Attempt to connect to an instance with 'SMO and DMO XPs enabled' set to 0.

Has been tested on minimum requirements:

[ ]  Powershell 3
[ ]  Windows 7
[ ]  SQL Server 2000

Has been tested on maximum requirements:

[ ]  SQL Server vNext
[ ]  Windows 10
[ ]  Azure Database

Tests for tester:

[ ] Working/useful help content, including link to command on dbatools web site
[ ] All examples work as advertised
[ ] Does not contain template content
[ ] Does not contain excessive/unnecessary amounts of comments
[ ] Works remotely
[ ] Works locally
[ ] Works on lower versions or throws error specifying version not supported
[ ] Works with named instances
[ ] Works with clustered instances
[ ] Handles offline/read only databases
[ ] Supports multiple servers (at the command line or piped from Get-SqlRegisteredServerName)
[ ] No un-handled errors which stop the command working with multiple servers

If we state something has to be changed (sp_configure setting) we should offer the command in PowerShell to do it ;)

Enable the option 'SMO and DMO XPs' on your instance using sp_configure to continue.

Compared to:

Enable the option 'SMO and DMO XPs' on your instance with Set-DbaSpConfigure -SqlServer MyInstance -Name 'SMO and DMO XPs' -Value 1

@wsmelton Good idea actually. I like it a lot better.
If nobody has any objections with this, I'll aim to have a commit Wednesday.
Busy tomorrow and all that jazz

@wsmelton, @shaneis  - Ultimately, I realized that it was usnig SMO to check for SMO -- same goes for Set-DbaSpConfigure -SqlServer MyInstance -Name 'SMO and DMO XPs' -Value 1 - that command uses SMO as well. And I had to comment it out with a note. Please revisit using pure T-SQL instead.

I'm not sure I follow, please revisit what?
The setting 'SMO and DMO XPs' in no way prevents you from hitting an instance utilizing SMO itself. This setting is strictly around the use of extended procedures that utilize SMO, which is why SSMS will bark if it is found disabled (or set to zero).

So are we saying just because SSMS gets it's jollies using extended stored procedures with SMO that we should not allow dbatools to function at all?

This isn't about SSMS, but rather not having to check within every command to see if we can use SMO XPs when we need it.
To my knowledge, we use a several SMO XP's -- any command that uses Test-SqlPath uses it, Find-DbaOrphanedFile and so on. While it's possible to make an index of commands that use xps, either explicitly or implicitly, I don't know if anyone can commit lifelong time or interest to maintain the index and do the research as to what implicitly uses the XPs.

okay, just did some testing. thank you for bringing this up @wsmelton
I was able to perform an entire migration with the XPs being disabled on both sides, so we can skip the check in its entirety for connect-sqlserver. i was also able to execute find-dbaorphanedfile with success, so i actually have no idea which XPs are SMO specific XPs and Microsoft does not provide an index on the first page of google search.


Block access to static pages

Hi,
I've been reading the tutorial, but couldn't made it work.
I have some statics pages, that I want to be locked unless the user is logged. I have a Session helper with this :
def logged_in?
!current_user.nil?
end
And I created my PagesController :
class PagesController < HighVoltage::PagesController
before_filter :authenticate
def authenticate
unless logged_in?
store_location
flash[:danger] = "Please login first"
redirect_to login_path
end
end
I assume I have to write something in my routes.rb file. I've already used a static page as homepage :
root :to => 'high_voltage/pages#show', :id => 'home'
What else have I to write in the routes.rb file to activate my PagesController, and what do I have to write to block access to my file.html.erb which is in views/pages ?
Thanks

I succeeded by doing this :
Writing this in initializers/high_voltage.rb :
HighVoltage.configure do |config|
config.routes = false
end
My PagesController :
class PagesController < ApplicationController
include HighVoltage::StaticPage
before_action :authenticate
def authenticate
unless logged_in?
store_location
flash[:danger] = "Please login first"
redirect_to login_path
end
end
end
And my routes.rb :
root :to => 'high_voltage/pages#show', :id => 'home'
resources :tests
resources :users
resources :account_activations, only: [:edit]
resources :password_resets,     only: [:new, :create, :edit, :update]
resources :pages
get 'pages/getdate'  => 'api#getdate'
The thing is, I have a problem now. I can still go to my home without being logged in by doing link_to root_url, one of my static pages uses the service "get 'pages/getdate'  => 'api#getdate'" and now it's not loading when we go to that page.
The other problem is that there are some static pages that don't require this authentication, so, how to tell Rails that I only want some of the pages to be locked ?

The thing is, I have a problem now. I can still go to my home without being logged in by doing link_to root_url, one of my static pages uses the service "get 'pages/getdate' => 'api#getdate'" and now it's not loading when we go to that page.

I'm not sure I follow the issue here. Can you provide any more details on this issue?

The other problem is that there are some static pages that don't require this authentication, so, how to tell Rails that I only want some of the pages to be locked ?

Perhaps you can have a before_action that is customized for your static pages which checks to see if the page id is available publicly or not.


Installation

Hi,
Your installation manual states
Download latest release version of blueTag ("blueTag-vX.uf2") from this github repository
But there is no blueTag-vX.uf2 to be found.
- jrscrs

https://github.com/Aodrulez/blueTag/releases/download/v1.0/blueTag-v1.uf2

Thanks @EdwardGrayclaws for a quicker response than me :)