Remove migration of client scopes

In the latest version of the add-ons we've already dropped support for
the method-based scopes. This way, users had to do the migration anyway
by now. As we will only support a migration from the latest version of
OSIAM and all it's components, remove the Flyway migration.
Furthermore we don't know how users utilize the "example-client", so
removing the scopes and adding both "ADMIN" and "ME" could break their
setup or even make their OSIAM insecure.
Resolves #166

Thanks!


2.1.0 Release

Release Candidates :

[x] Commit, review and merge a v2.1.0-RC3 version change in https://github.com/f3d-app/f3d CMakeLists.txt in the master branch
[x] Tag v2.1.0-RC2 and push it to https://github.com/f3d-app/f3d: git tag v2.1.0-RC3 -m v2.1.0-RC3
[x] Trigger a release build using https://github.com/f3d-app/f3d-superbuild actions with v2.1.0-RC3 F3D version, superbuild main branch and prerelease publish true
[x] Download the v2.1.0-RC3 prerelease from https://github.com/f3d-app/f3d/releases
[x] Locally test the v2.1.0-RC3 prerelease on Linux: run, render, config file, drag&drop, thumbnails, exec from file manager, sdk
[x] Locally test the v2.1.0-RC3 prerelease on macOS: run, render, config file, drag&drop, exec from file manager
[x] Locally test the v2.1.0-RC3 prerelease on Windows: run, render, config file, drag&drop, thumbnails, exec from file manager, sdk
[x] If it fails, fix the issue, copy this paragraph and increment N
[x] Else proceed to the next part

Release :

[x] Commit, review and merge v2.1.0 version change in https://github.com/f3d-app/f3d CMakeLists.txt
[x] Tag v2.1.0 and push it to https://github.com/f3d-app/f3d: git tag v2.1.0 -m v2.1.0
[x] Merge https://github.com/f3d-app/f3d master branch into the release branch
[x] Commit, review and merge adding 2.1.0 in https://github.com/f3d-app/f3d-superbuild versions.cmake
[x] Tag v2.1.0 and push it to https://github.com/f3d-app/f3d-superbuild: git tag v2.1.0 -m v2.1.0
[x] Trigger a release build using https://github.com/f3d-app/f3d-superbuild actions with v2.1.0 F3D version, v2.1.0 sb version and prerelease publish true
[x] Write release notes using PR since last release and add it to the release
[x] Add contributors and packagers to the release notes
[x] Release
[x] Update download links and changelog https://github.com/f3d-app/f3d doc
[x] Communicate on discord
[x] Communicate on reddit
[x] Communicate on hackernews
[x] Communicate on linkedin

v2.0.0
For F3D users:

Reworked Animation support and added mane animation related options (see above(TODO))
Added --camera-direction and --camera-zoom-factor and use it in default config file (see above (TODO))
Added --texture-matcap option to load a MatCap texture
Added .exr support for HDRI and textures
Added a EGL headless binary release
Added typo suggestion when failing to use the right option name
Added --invert-zoom option (libf3d: interactor.invert-zoom) to invert zoom direction with right-click on mouse (thanks @DeveloperPaul123!)
Added support for keeping camera position when reloading a file with UP key
Added a --grid-absolute option (libf3d: render.grid.absolute) to position the grid instead of being below the model
Added a "Drop Zone" when starting F3D without loading a file
Added coloring support for STEP files in binary release
Fixed an issue on Windows where the error window would popup even with --quiet
Fixed an issue with 16 bit and 32 bit textures with assimp plugin
Fixed an issue on Windows where errors where not visible
Fixed an HDRI issue on reload
Fixed a crash when with the progress bar on reloading a file
Fixed an issue where certain options from config file would be ignored
Fixed a crash with many GLTF files when an array does not have a name
Fixed an issue where dropping a duplicate file would change the loaded file instead of not doing anything
Fixed an issue when loading an unsupported file
Fixed an issue with VRML files
Improved config file for .ply files
Improved config file regex so that they are case-insensitive
Improved --up option to support no sign and better validation
Improved F3D version reporting about itself and VTK (--version)
Improved documentation, testing, help
Excluded TIFF format from Windows Thumbnailer
Changed the automatic camera position to a version more close to the data
Reduced size of binary release by a factor of two

For libf3d users:

Added vcpkg support for dependency installation

For F3D packagers:

Added a F3D_PLUGIN_OCCT_COLORING_SUPPORT  cmake variable to control if this feature is compiled, default is ON
Added SONAME support (thanks @bkmgit!)
Added a F3D_PLUGINS_INSTALL_DIR CMake variable to control where to install plugins
Added a new module: F3D_MODULE_EXR that depends on openexr
Added support to use external cxxopts and external nlohmann-json (thanks @topazus!)
Fixed a link issue with VTK modules
Fixed a @loader_path issue on MacOS
Added support for CMAKE_INSTALL_*DIR variables on installation (thanks @topazus!)
Added support for building against a EGL enabled VTK
Fixed a compilation issue with VTK master

Contributors: @DeveloperPaul123 @topazus @bkmgit @snoyer @Meakk @mwestphal

@snoyer @Meakk let me know If I missed anything in the above release notes. Also see the list of "focus points" on top.

2.1.0-RC1 Testing:
Arch Linux: Thumbnailer not working
Ubuntu: Ctrl+Drop + Thumbnailer not working

First pass done

Added mandatory emoticons 😛

Promotion Title
F3D 2.1.0 Released! Fast and minimalist open source 3D viewer now with better animation, camera option and HDRI support.

RC3 validated

https://github.com/f3d-app/f3d/assets/3129530/86a2bb57-c61e-49c0-a02c-bfb9b851223d

The F3D package on Flathub was updated in https://github.com/flathub/io.github.f3d_app.f3d/pull/34.

The progress bar during file loading is missing in this version. If I drop a slightliy more complicated STEP file the app now seems to freeze - not visible feedback at all for several seconds - and then eventually show the model. Please re-add the progress bar.

@drtrigon : It works fine here, tested with a big VTU file. I dont have access to a big step file, could you share one that show the behavior ?

release is done.

@mwestphal : I did more testing.
If I open a STEP file usually the progress bar does not get showed. Sometimes it does but that’s rare. No idea of the cause.
What I found is, something is wrong with STL files. It does not report “not supported” but behave very similar as if opening a STEP file, but never displays anything.
(I seemingly mixed the two things up as I just was browsing directories by using the arrow keys – my bad.)
Hope that clarifies things. Thanks and greetings!

Could you share the problematic files ?

It was not a specific faile but essentially all, here a set of 3:
examples.zip

There is no progress issue, the file are just not opening correctly in F3D for some reasons.
If you show the verbose output you will see:

Scene bounding box: -3.3063e+38,3.35316e+38,-3.04052e+38,3.35316e+38,-3.29992e+38,3.1336e+38

Camera position: 2.34313e+36,-2.37185e+39,-8.31569e+36
Camera focal point: 2.34313e+36,1.56319e+37,-8.31569e+36
Camera view up: 0,0,1
Camera view angle: 22.1264

Using grid unit square size = 1e+38
Grid origin set to [2.34313e+36, 1.56319e+37, -3.29992e+38]

The file are very very far away from the origin, breaking F3D rendering.
Inspecting the files in ParaView we see that indeed, the point coordinates are basically non-sensical:

(top part of a plot of point magnitude, bottom part is an excerpt of some point taken at random from the high magnitude points)
There are two possible reasons for this:

This is your actual data, what is on the file. no bug here.
There is a bug in the vtkSTLReader with your files for some reasons.

How did you generate these files ?
BTW this discussion would fit much better on discord (https://discord.f3d.app)

The original file was in a (rather esoteric) CAD format using file extension .prt. As we got the files from a previous project I was not involved in I could never fully figure out what the original format was (just assumtions).
At some point I used CAD Exchanger 3.9.2 build 14270 (cadexchanger.com) in order to batch process and convert them to .stp, .stl and .png such that we are at least able to use them.
The thing to notice is, e.g. the windows stl viewer is able to render those files correctly.
Can they somehow be "sanitized" or repaired, e.g. by subtracting a common offset like the Grid origin [2.34313e+36, 1.56319e+37, -3.29992e+38] or would it be possible to downscale it using the grid unit square size of 1e+38 ?
(I can come to discord of course the thing is, I cannot make sure to be online the same time you are... I am in Europe, what about you?)

The thing to notice is, e.g. the windows stl viewer is able to render those files correctly.

I will check when I can

Can they somehow be "sanitized" or repaired, e.g. by subtracting a common offset like the Grid origin [2.34313e+36, 1.56319e+37, -3.29992e+38] or would it be possible to downscale it using the grid unit square size of 1e+38 ?

Probably, but no idea how to do that.

(I can come to discord of course the thing is, I cannot make sure to be online the same time you are... I am in Europe, what about you?)

@Meakk and myself are both in France, but there are users all over the world anyway :)

The thing to notice is, e.g. the windows stl viewer is able to render those files correctly.

I will check when I can

Can they somehow be "sanitized" or repaired, e.g. by subtracting a common offset like the Grid origin [2.34313e+36, 1.56319e+37, -3.29992e+38] or would it be possible to downscale it using the grid unit square size of 1e+38 ?

Probably, but no idea how to do that.

For reference:

windows stl viewer is able to render it
meshlab gives an error
freecad can import it but it is just a cuboid
(did not test blender yet...)

(I can come to discord of course the thing is, I cannot make sure to be online the same time you are... I am in Europe, what about you?)

@Meakk and myself are both in France, but there are users all over the world anyway :)

As soon as I am back at work I can join the discord channel.

@drtrigon was this issue ever fixed ?

I don't know. Was a bugfix added, that I should test?

Did we discuss it on discord ? I should have taken notes, sorry about that.

Actually I don't think we discussed this... 🤔
What would be your questions? (such that I can prepare)

just to understand how was the dataset generated and what behavior do you have.
https://discord.f3d.app


Add optional binary relocatability

🎉 New feature
Closes part of https://github.com/gazebosim/gz-sim/issues/626
Summary
This PR uses the changes introduced in gz-cmake3 in https://github.com/gazebosim/gz-cmake/pull/334 to support the cmake installation directory to be moved after the make install prefix, and continue to work without the need to set any special environment variable, as long as the library is compiled as shared. To avoid regressions and problems in Ubuntu Focal due to the use of std::filesystem, this new behaviour is only activated if the GZ_ENABLE_RELOCATABLE_INSTALL option is enabled, and its default value is OFF .
In particular, this PR defines a  gz::rendering::getPluginInstallDir() that should be used in place of the GZ_GUI_PLUGIN_INSTALL_DIR macros to ensure that the library is relocatable.
Furthermore, this PR also deprecates the GZ_GUI_PLUGIN_INSTALL_DIR macro, using the strategy described in https://stackoverflow.com/a/29297970 . That strategy works fine on GCC and Clang, while on MSVC it raise a warning:
warning C4068: unknown pragma

However, I think that it does anyhow the job of raising some kind of warning, and then at soon as the developer checks the macro definition the kind of warning is clear.
Test it
The test should work as usual. The used CMake machinery is tested in https://github.com/gazebosim/gz-cmake/pull/334 .
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[x] Updated documentation (as needed)
[x] Updated migration guide (as needed)
[x] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Looks like CI is having issues on this one:
  -- Configuring done
  CMake Error at /usr/share/cmake/gz-cmake3/cmake3/GzUtils.cmake:214 (add_library):
    Cannot find source file:

      /github/workspace/build/include/gz/gui/gz-gui7_get_install_prefix_impl.cc

    Tried extensions .c .C .c++ .cc .cpp .cxx .cu .m .M .mm .h .hh .h++ .hm
    .hpp .hxx .in .txx
  Call Stack (most recent call first):
    /usr/share/cmake/gz-cmake3/cmake3/GzCreateCoreLibrary.cmake:104 (_gz_add_library_or_component)
    include/gz/gui/CMakeLists.txt:48 (gz_create_core_library)
    ```

@traversaro are you going to be able to iterate on this one?

@traversaro are you going to be able to iterate on this one?

I tried earlier today, but I was unable to find the solution. I think we can think of this some time after the code freeze/harmonic release.

Sounds good, I'm going to remove the beta label for now.

Sounds good, I'm going to remove the beta label for now.

Yes, probably post-Harmonic release the easiest solution is to target harmonic for this, so we do not need to worry about Focal compatibility.

@traversaro does this need to be retargeted to gz-gui8?

@traversaro does this need to be retargeted to gz-gui8?

Yes, I can do this in the next days.

Ops, sorry for the noise @jennuine @caguero , actually the PR was already merged in gz-gui8 in https://github.com/gazebosim/gz-gui/pull/580 before your pings, so we can safely close this one!


Fixes #584

Coverage: 77.094% (+0.005%) from 77.089% when pulling 4fc760cda0fe54204a867d737212b52ab4108d9e on fix-pyenv into 10ed0001c080974c79cb903ef970f780c9090401 on main.


vim8 can't work

Error detected while processing function
rtags#InitPython:
line    9:
Traceback (most recent call last):
File "", line 6, in
File "C:\Users\Administrator\.cache\vimfiles\re
pos\github.com\lyuts\vim-rtags\plugin\vimrtags
.py", line 7, in
logging.basicConfig(filename='/tmp/vim-rtags-p

ython.log',level=logging.DEBUG)
File "C:\Python27\Lib\logging_init_.py", line
1547, in basicConfig
hdlr = FileHandler(filename, mode)

File "C:\Python27\Lib\logging_init_.py", line 913,

this cause by "/tmp/vim-rtags-p" , the windows has not the "/tmp" dir,  you can delete the "/tmp/" to let the log file in current dir or other dir is exist in windows. By the way, I just, using rtags in linux, have you already config the rtags compatable with windows? is every thing ok? if true, could you write a course on the internet to teach us.

thanks~


Add possibility to call InsertGetId with dictionary parameter

While Insert method has several overloads: object, dictionary, columns + values, etc,
there is only one overload of InsertGetId - with object.
For my project it very crucial to have possiblity to call InsertGetId with dictionary as a parameter, because I know names of columns only in runtime.
Please, approve it.

Hi @arudoy, sorry for the late reply,
Could you please add the async version of it also, in addition to the new parameters, transaction and cancelationToken?


fix: color token updates for overflow menu, page title, tooltip, and tabs

Updated to theme based color tokens.
ADO Story Link
USER STORY 2003601
Figma Link

Overflow menu
Page Title
Tooltip
Tabs

Notes
Updated tokens in below components :
Overflow menu
Page Title
Tooltip
Tabs

@srpriyankashetty , Tabs component is failing accessibility color contrast . Macro is looking into it. Other components can be checked.

Hi @tulasigudibanda ,
There is no preview link in this PR.!

HI @tulasigudibanda ,
I meant this preview link is missing.!

:tada: This PR is included in version 2.0.0-next.26 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


BackdropBlur is not being applied on image on Android

We use a BackdropBlur on top of an image to blur a specific section of the image.
The blurred section is a 'badge', on which we render text and icons using react components.
These backdrop blurs are built up like this (simplified);
<Canvas>
   <Group>
      <Image>
      <BackdropBlur>
         <Fill>
      </BackdropBlur>
   </Group>
</Canvas>

On iOS, this works fine. On Android though, the blur is not being applied.
As you can see in the screenshot below, we have some blurs working on Android (in the listitems).
These are built up like this (simplified);
<Canvas>
   <Image>
      <Blur>
   </Image>
</Canvas>

We need to use the BackdropBlur for those polaroid-like components, because we need the clip property to only blur a specific section.
First image is Android, second one is iOS.

I couldn't reproduce the issue yet, a reproducible example would be helpful.

Hi @wcandillon,
Thanks for testing. I'm really curious what makes our implementation different.
I've made a simplified version of our implementation, which shows the same issue.
https://github.com/laurens-lamberts/react-native-skia-example
Would be great if you could check this!
All the best,
Laurens

Good idea, let's keep the examples in the repo for future reference / testing.
I swapped out the previous example with a new one, keeping the other in a separate file (src/examples folder).
I try to keep the code that is run, libraries used and views rendered as minimal as possible, to minimize impact of unrelated code to the bug that is tried to be identified.
I'll keep the different examples in the repo, and will ensure that they can be easily swapped in the App.tsx.
If you advice a different approach on this, please let me know.

I now made the examples easily swappable.
Just press one of the buttons on the red top menu, to immediately swap out one example with the other.
I used a simple state variable, not to be dependent on (e.g.) react-navigation while troubleshooting.
Hope this works well for testing. Just let me know if you suggest a different setup.

Hi @wcandillon,
I just updated the example project from 0.1.123 to 0.1.124, and suddenly the issue of BackdropBlurs on Android disappeared! Guess it was resolved in the latest update already.
Thanks for looking into this with me. I will close this issue now.
I will add other Skia findings to the example project in the future.

That's awesome 🙌🏼 Not really sure what happened there. But regardless, let's stay in touch via the example project


[CS] Fixes #2278 handle False positive in case of parent interface/trait in NoProtectedElementInFinalClassRule

For note: It is weird that previously when this rule initiated, the parent of ClassMethod and Property is always a Class_, probably the issue is it previously using not updated dependencies.
All checks have passed 🎉 @TomasVotruba it is ready for review.

Thank you for such a fast fix :+1:

For note: It is weird that previously when this rule initiated, the parent of ClassMethod and Property is always a Class_, probably the issue is it previously using not updated dependencies.

I see, it happened to me to. Seems always safer to check node that we get from getAttribute()


Consider structure of project for maintainability

We have ElementExtensions, RenderedFragmentExtensions.
Currently code and tests for a feature are split across these three classes and quite seperate.
I'm wondering if it would be better to change mind and group features...e.g. keep all .ShouldHaveClass extensions together regardless of what they are extending.
Might add a couple more features to make sure I'm not prematurely changing things.....
I welcome feedback on this thought...

Will leave this until implemented #4


Add support for spring boot 2.4.3 - fix objectMapper field access - fixes #1266

Description
Use the Getter instead of direct field access - the field has been renamed to defaultObjectMapper in 2.4.3
Related Issue
Relates to #1266
Motivation and Context
Add support for Spring Boot 2.4.3

@beikov if you can tell me how I can adjust version.spring-data-2.4-spring to ensure we test on 2.4.2 and 2.4.3 i would love to add this here - did not find it in the suite.
I found https://github.com/EugenMayer/blaze-persistence/blob/patch-1/.github/workflows/ci.yaml but I cannot see how you actually reference a specific version here, neither in the .travis.yml

Thanks for the fix. I usually stick with the old versions to make sure this is still compatible with the first supported version and just switch occasionally locally to see if it still works on the lastest fix version. You can change versions in the parent/pom.xml in the properties-section.


Catch unhandled exceptions in Probe background thread

The CLR allows most unhandled exceptions in threads to proceed naturally. In most cases this means that the unhandled exception causes the application to terminate.
Added try-catch for BroadcastProbe to prevent whole process/application to terminate in case of temporary network not available throwing in some case Exception of type System.Net.Sockets.SocketException: Network is unreachable.
Please update nuget package (if not automatic) after merging, thanks.

Pushed 1.0.1 to NuGet.org

Thanks a lot @rix0rrr


Fix contribution guide link in Readme

Right now, we have a couple links that point to the wrong places.

Instructions for building and testing Beam itself should point to our code contribution guide, not the full contribution page
For a full list of ways to contribute and get plugged into Beam should point to our fleshed out full contribution page, not the barebones pointer to other pages

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @svetakvsundhar


Use OBS

OBS creates binaries and repos for all distros. https://en.opensuse.org/Portal:Build_Service
https://build.opensuse.org/

We already have AppImage for next release, so that should be fine.

AppImage has been released after Kaku 1.8.0 and should be working well for many linux users, so close this issue first.


chore: fix warning logs

Fixes #N/A
Description
Getting warnings like these all throughout the controller logs, since our template resources in the NodePool were removed.
    logger.go:146: 2024-08-01T12:51:20.830-0700	INFO	KubeAPIWarningLogger	log/warning_handler.go:65	unknown field "spec.template.spec.resources"

How was this change tested?
testing here
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

49 of 78 (62.82%)  changed or added relevant lines in 4 files are covered.
13 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.2%) to 77.697%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1/nodeclaim.go
10
20
50.0%

pkg/apis/v1/zz_generated.deepcopy.go
31
50
62.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/expectations/expectations.go
2
94.64%

pkg/controllers/disruption/consolidation.go
4
87.25%

pkg/controllers/provisioning/scheduling/preferences.go
7
86.67%

Totals

Change from base Build<PHONE_NUMBER>2:
-0.2%

Covered Lines:
8845

Relevant Lines:
11384

💛  - Coveralls

/hold

/remove-hold


Cannot read property 'charAt' of undefined

After upload the attached scrom content, fail to open the content. Loader is continuously running and behind the page throwing javascript error as mentioned below.
Scrom file Attachment:
Draft 5s training Module SCORM 1.2.zip
Error Details:
Uncaught TypeError: Cannot read property 'charAt' of undefined
at cp.QuizState.readNumber (eval at e (CPXHRLoader.js:37), :1374:423)
at cp.QuizState.readString (eval at e (CPXHRLoader.js:37), :1376:34)
at cp.PlaybackController.restoreObjectsFromState (eval at e (CPXHRLoader.js:37), :1455:20)
at Function.cp.resumeValuesFromDataChunk (eval at e (CPXHRLoader.js:37), :1369:460)
at cp.PlaybackController.RestoreQuizState (eval at e (CPXHRLoader.js:37), :1496:35)
at Function.cp.NewQuizLibraryInit (eval at e (CPXHRLoader.js:37), :982:3)
at Function.cp.CPPreInit (eval at e (CPXHRLoader.js:37), :990:246)
at Function.cp.ContinueCPInit (eval at e (CPXHRLoader.js:37), :1936:33)
at LoadContent (eval at e (CPXHRLoader.js:37), :1368:439)
at InitializeExecuted (eval at e (CPXHRLoader.js:37), :1879:36)

Did you turn on debugging? To turn on debugging, execute window.API.apiLogLevel = 1; before loading the course.
I would help more, but CPXHRLoader.js is a minified file and is impossible to debug. Seeing what the course is doing before the error would help understand what is happening.


Update ISSUE_TEMPLATE.md

When there's no space, emphasis doesn't get rendered.

Really? The rich diff isn't showing any difference.

Ah, it doesn't get rendered if it has a colone like *test:*test


Feature request: add telegram notifiaction

I think it would be nice to add another Telegram notification channel
and dark theme of the site :)

Hi @MakarSikorskyi, thanks for the message, I missed this one.
I haven't used Telegram for many years but it should be straightforward.
Dark theme is indeed a popular request haha.


Add flag to output the file to log

For use in tests etc. add a flag to output the generated string on console without writing to disk

closed in #3


Add flags for OSD 'docker run --cpuset-{cpus,mems}'

Add the variables ceph_osd_docker_cpuset_cpus and
ceph_osd_docker_cpuset_mems, so that a user may specify
the CPUs and memory nodes of NUMA systems on which OSD
containers are run.
Provides an example for osds.yaml.sample to guide user
based on sample lscpu output since cpuset-mems refers
to the memory by NUMA node only while cpuset-cpus can
refer to individual vCPUs within a NUMA node.

jenkins test luminous-ansible2.4-purge_bluestore_osds_non_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_non_container

@fultonj I confirm, the failure here is unrelated to this patch

@fultonj are you expecting this for 3.0 or 3.1?

@leseb if this could get backported to 3.0, then that would be great. thanks.


[C100-Rebuild] PRLC100-58-59 - Added new case fields for c100 rebuild journey

Added new case fields for confidentiality, international elements & reasonable adjustments for c100 rebuild journey.
PRLC100-58
PRLC100-59
Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Rebased with c100-rebuild-create-update-case branch as we are using PR https://github.com/hmcts/prl-ccd-definitions/pull/543 for C100 rebuild testing


DraftWise

https://www.draftwise.com/

@matejkajinic I know that logo is too easy to create but I didn't found a SVG version.


Handle import scope dependencies in dependencyManagement (multiple goals) (Fixes multiple issues #308, #309, #346, #395)

Fixes #308, Fixes #309, Fixes #346, Fixes #395 for following goals

use-dep-version
use-latest-versions
use-latest-snapshots
use-latest-release
use-next-releases
use-next-versions
use-next-snapshots

added test case and applied fixes for tabs

@mfriedenhagen added test case and applied fixes for tabs

This would be really handy

Is there any chance of this PR getting merged? The documentation is very clear that the dependencyManagement section is processed by default, and therefore it is surprising that something like mvn versions:use-latest-releases does not also update import scoped dependencies in dependencyManagement to the latest release versions.

It doesn't? Yesterday I checked it and it did update those. I did check that with maven 3.2.5 as well as 3.6.3.
Could you please share a test scenario where it doesn't update those dependencies? By that I understand a test pom.xml, not just a maven command line.

Hi @ajarmoniuk thanks for your fast response! Here is a contrived pom.xml that reproduces the issue:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>

	<groupId>com.example</groupId>
	<artifactId>demo</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>demo</name>
	<description>Demo project for Spring Boot</description>
	<properties>
		<java.version>11</java.version>
	</properties>

	<dependencyManagement>
		<dependencies>
			<dependency>
				<groupId>org.springframework.boot</groupId>
				<artifactId>spring-boot-dependencies</artifactId>
				<version>2.7.0</version> <!-- old version -->
				<type>pom</type>
				<scope>import</scope>
			</dependency>
		</dependencies>
	</dependencyManagement>

	<dependencies>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter</artifactId>
			<scope>provided</scope>
		</dependency>
	</dependencies>
</project>

I have tested the above with both Maven 3.6.0 and 3.8.6 using command mvn versions:use-latest-release -Dincludes=org.springframework.boot:spring-boot-dependencies. The command succeeds without updating anything.
I would also note that the following pom.xml and command mvn versions:update-properties -Dincludes=org.springframework.boot:spring-boot-dependencies works as expected, with the spring.version property being updated:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>

	<groupId>com.example</groupId>
	<artifactId>demo</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>demo</name>
	<description>Demo project for Spring Boot</description>
	<properties>
		<java.version>11</java.version>
                <spring.version>2.7.0</spring.version> <!-- old version -->
	</properties>

	<dependencyManagement>
		<dependencies>
			<dependency>
				<groupId>org.springframework.boot</groupId>
				<artifactId>spring-boot-dependencies</artifactId>
				<version>${spring.version}</version>
				<type>pom</type>
				<scope>import</scope>
			</dependency>
		</dependencies>
	</dependencyManagement>

	<dependencies>
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter</artifactId>
			<scope>provided</scope>
		</dependency>
	</dependencies>
</project>

Indeed, I was able to reproduce the issue using your POMs. Thank you. I will now update all mojos to include the fix for this issue.

For some reason, I wasn't able to create a test using a bom in the it-repo repository, even if I copied the Spring Boot BOM there. Neither did using org.codehaus.mojo:mojo-parent reproduce the problem. In both cases, the BOM was present in project.dependencyManagement.dependencies.


Fix parsing for max_determinized_states

https://github.com/elastic/elasticsearch/pull/22749
This looks like a breaking change for us since its not bwc in Elasticsearch (at first very quick glance)

Looks like we're already using the correct spelling (which was wrong?)
https://github.com/elastic/elasticsearch-net/blob/master/src/Nest/QueryDsl/FullText/QueryString/QueryStringQuery.cs#L53

yup! we future proofed our code cough cough


Enable ErrorProne for :core-runtime

Remove the project-level ErrorProne exceptions from all modules in core-runtime.
It adds https://errorprone.info/bugpattern/StringSplitter as a global exception, as we seem to be using this API as-is in lots of places, and the recommended pattern would actually be the wrong choice for us.
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

The merge queue build has failed. Click here to see all failures.


Handle SessionTimeoutManager.sessionConfig change

Hi,
I have a use case where SessionTimeoutManager.sessionConfig can change at any time through user settings (user can set invalidateSessionForUserInactivity timeout through settings screen/page).
When SessionTimeoutManager.sessionConfig changes, SessionTimeoutManager doesn't handle the change at all.
I would expect internal timer _userInactivityTimer would be reset in this case, so the new setting would be applied immediately - currently the new setting is applied when first user activity is detected?

Hi, I've just made a workaround similar to your proposed solution by pushing another SessionState event to the sessionStateStream after new sessionConfig is set and timer is reset. Not the prettiest solution, but works well for my case.
IMHO better (and simpler) solution would be to check if sessionConfig changed inside _SessionTimeoutManagerState.didUpdateWidget and no new stream would be needed for this.


Avoid failure to add interface when XFRM is not supported by the kernel

Description
Calico cni-plugin errors out on kernels that don't support XFRM leaving all new pods stuck in ContainerCreating state and kubelet reporting plugin type="calico" failed (add): failed to create host netlink handle: protocol not supported.
This issue was introduced in v3.27.0 by

commit 71d6f8385 Improve pod startup time

By default, netlink.NewHandle() will return a handle with all netlink families supported by the library (currently, ROUTE, XFRM, NETFILTER).
This fix limits the requested handle to the ROUTE netlink family only.

Related issues/PRs
fixes https://github.com/projectcalico/calico/issues/8709
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

 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.

For the record, this change is working as expected in one of our clusters

Thanks for the fix, looks like there's also a bare NewHandle call in felix's vxlan_mgr.go.  Please can you update that too; I think it also needs to be a route handle to avoid this problem (when VXLAN is enabled)?

/sem-approve

Thanks for the fix, looks like there's also a bare NewHandle call in felix's vxlan_mgr.go. Please can you update that too; I think it also needs to be a route handle to avoid this problem (when VXLAN is enabled)?

Sure, will take a look at it shortly :)

@fasaxc I've made the changes but make test locally is taking forever to run :sweat_smile:

@fasaxc can I get another test run from semaphoreci? I don't see it showing up here and I'm having troubles running tests locally :)

/sem-approve

Outch. Sorry about that. Fixed. Can you run it again? :)

/sem-approve

I thought about testing but I couldn't come up with anything reasonable :sweat_smile:
Thanks

@carloslima just for my education, why bother compiling out XFRM?

I don't know the reasoning behind it because the nodes are managed by a different team. My guess is that they compile out a lot of things they don't use nor expect to be used :-)


Failed prop type: Invalid prop actions.service of type Object supplied to _class2, expected instance of _class

Bug description:
As soon as I load Ferdi, I see many errors in the console like this:
Warning: Failed prop type: Invalid prop `actions.service` of type `Object` supplied to `_class2`, expected instance of `_class`.
    in _class2 (created by inject-_class2-with-stores-actions)
    in inject-_class2-with-stores-actions (created by RouterContext)
    in RouterContext (created by Router)
    in Router (created by _class)
    in _class (created by inject-_class-with-stores-actions)
    in inject-_class-with-stores-actions
    in IntlProvider (created by _class)
    in _class (created by inject-_class-with-stores)
    in inject-_class-with-stores
    in Provider

Warning: Failed prop type: Invalid prop `actions.settings` of type `Object` supplied to `_class2`, expected instance of `_class`.
    in _class2 (created by inject-_class2-with-stores-actions)
    in inject-_class2-with-stores-actions (created by Context.Consumer)
    in injectIntl(inject-_class2-with-stores-actions) (created by _class2)
    in div (created by _class2)
    in div (created by _class2)
    in _class2 (created by Jss(_class2))
    in Jss(_class2) (created by Context.Consumer)
    in injectIntl(Jss(_class2)) (created by _class2)
    in _class2 (created by Jss(_class2))
    in Jss(_class2) (created by Context.Consumer)
    in injectIntl(Jss(_class2)) (created by _class2)
    in ThemeProvider (created by _class2)
    in _class2 (created by inject-_class2-with-stores-actions)
    in inject-_class2-with-stores-actions (created by RouterContext)
    in RouterContext (created by Router)
    in Router (created by _class)
    in _class (created by inject-_class-with-stores-actions)
    in inject-_class-with-stores-actions
    in IntlProvider (created by _class)
    in _class (created by inject-_class-with-stores)
    in inject-_class-with-stores
    in Provider

Warning: Failed prop type: Invalid prop `actions.app` of type `Object` supplied to `_class2`, expected instance of `_class`.
    in _class2 (created by inject-_class2-with-stores-actions)
    in inject-_class2-with-stores-actions (created by _class2)
    in div (created by _class2)
    in _class2 (created by inject-_class2-with-stores-actions)
    in inject-_class2-with-stores-actions (created by _class2)
    in div (created by _class2)
    in _class2 (created by inject-_class2-with-actions)
    in inject-_class2-with-actions (created by Jss(inject-_class2-with-actions))
    in Jss(inject-_class2-with-actions) (created by Context.Consumer)
    in injectIntl(Jss(inject-_class2-with-actions)) (created by _class2)
    in div (created by _class2)
    in div (created by _class2)
    in div (created by _class2)
    in _class2 (created by Jss(_class2))
    in Jss(_class2) (created by Context.Consumer)
    in injectIntl(Jss(_class2)) (created by _class2)
    in _class2 (created by Jss(_class2))
    in Jss(_class2) (created by Context.Consumer)
    in injectIntl(Jss(_class2)) (created by _class2)
    in ThemeProvider (created by _class2)
    in _class2 (created by inject-_class2-with-stores-actions)
    in inject-_class2-with-stores-actions (created by RouterContext)
    in RouterContext (created by Router)
    in Router (created by _class)
    in _class (created by inject-_class-with-stores-actions)
    in inject-_class-with-stores-actions
    in IntlProvider (created by _class)
    in _class (created by inject-_class-with-stores)
    in inject-_class-with-stores
    in Provider

Steps to reproduce:

Open Ferdi
Show Console

Expected behavior
There should be no failed prop types.
Environment:

Operating System: Windows 10 x64
Ferdi Version: 5.6.2
Server: Using without an account

Duplicates of #1683, #1684, #1685, #1686


changed dev server port

Signed-off-by: Aditya Chatterjee<EMAIL_ADDRESS>Description
Changed dev server port from 3000 to 4001.
If 4001 is occupied port no. increases by one.
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

Codecov Report

Merging #4961 (2d69a3d) into master (5f7eb3f) will decrease coverage by 6.58%.
The diff coverage is 72.46%.

@@            Coverage Diff             @@
##           master    #4961      +/-   ##
==========================================
- Coverage   32.45%   25.87%   -6.59%
==========================================
  Files          61       61
  Lines        5025     5028       +3
==========================================
- Hits         1631     1301     -330
- Misses       2990     3433     +443
+ Partials      404      294     -110

Flag
Coverage Δ

e2etests
?

gointegrationtests
?

integrationtests
?

unittests
25.87% <72.46%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/perf/apply.go
42.04% <68.42%> (ø)

mesheryctl/internal/cli/root/perf/profile.go
45.71% <73.07%> (ø)

mesheryctl/internal/cli/root/perf/result.go
68.90% <75.00%> (ø)

mesheryctl/internal/cli/root/system/start.go
1.92% <0.00%> (-54.67%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
2.50% <0.00%> (-47.50%)
:arrow_down:

mesheryctl/internal/cli/root/system/status.go
1.14% <0.00%> (-43.68%)
:arrow_down:

mesheryctl/internal/cli/root/system/update.go
1.05% <0.00%> (-34.74%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
1.78% <0.00%> (-23.22%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.03% <0.00%> (-23.03%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
3.29% <0.00%> (-20.88%)
:arrow_down:

... and 5 more

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 521f8be...2d69a3d. Read the comment docs.

Aah now I remember why we didnt change it here before, it's probably not worth the hassle. I'll close the PR. Thanks for the review @sayantan1413


is no work in .NET 4.0?

is no work in .NET 4.0?

Hello,
The v4 client version only supports .NET 4.5 and above. We did this for many reasons (easier to use async and simplifies a bunch of code while making .net standard support much easier). With that said, we will continue to support all versions of our clients. Any version prior to v4 supports .NET 4.0, as such please install the latest v3.5 client from nuget. If you need any help, please let me know!
For example, if you wanted to install the console app package, you would navigate to the older version and install via the command line or use the version selector in vs when installing the package:
https://www.nuget.org/packages/Exceptionless/3.5.1738


Could we add Keywords to the different Links

Description
It would be awesome to have the possibility to add different keywords to the links/apps, so for example i have a link/app to nextcloud, i give it tags like file, next, cloud. If i search for it in the searchbar, i get all Links with matching tags
Priority
Low (Nice-to-have)

Duplicate of #657


go-talks.appspot.com is outdated

For example, http://go-talks.appspot.com contains link to https://github.com/garyburd/talksapp/issues/new (404), but source in this repository doesn't.

Yup.  And lintapp.  I sent email requesting a redeploy to the service admin.

cc @campoy
On 29 June 2015 at 03:15, Gary Burd<EMAIL_ADDRESS>wrote:

Yup. And lintapp. I sent email requesting a redeploy to the service admin.
—
Reply to this email directly or view it on GitHub
https://github.com/golang/gddo/issues/280#issuecomment-116300742.

Fixed now

@campoy: go-lint.appspot.com should also be updated.

I'm not a manager of that app, could you add me? thanks

Uh oh. I added you a long time ago and removed myself.

done


Fix SubworkflowMapper: missing action_mapper and control_mapper parameters when invoked

https://polidea.slack.com/archives/CGH100JQP/p1555399187000200

Test that confirm issues is available: https://github.com/GoogleCloudPlatform/cloud-composer/pull/82 (first commit)


Fix multiple instance registration/deregistration

Issue #, if available:
Description of changes:
Pass value into register/de-register instance functions. Prior behaviour passed a reference to the iterator struct, which caused multiple calls for the same instance id.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #60 (b842cda) into main (a132823) will increase coverage by 3.81%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #60      +/-   ##
==========================================
+ Coverage   50.73%   54.55%   +3.81%
==========================================
  Files          12       12
  Lines        1084     1087       +3
==========================================
+ Hits          550      593      +43
+ Misses        509      461      -48
- Partials       25       33       +8

Impacted Files
Coverage Δ

pkg/controllers/cloudmap_controller.go
0.00% <ø> (ø)

pkg/cloudmap/client.go
71.36% <100.00%> (+17.16%)
: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 a132823...b842cda. Read the comment docs.


build(rollup): move exports: named

ref: https://rollupjs.org/#using-plugins

I tested this out with my CRA, seems to work fine

Coverage remained the same at 67.539% when pulling 2ca76d81062840092a18f33736ed1172890e5134 on aa-exports-named into b02d227c9a2c439ac1dc859ffcd7ba3216f5fc40 on master.

Coverage remained the same at 67.539% when pulling 2ca76d81062840092a18f33736ed1172890e5134 on aa-exports-named into b02d227c9a2c439ac1dc859ffcd7ba3216f5fc40 on master.

this actually removes the warning:
(!) Mixing named and default exports
Consumers of your bundle will have to use bundle['default'] to access the default export, which may not be what you want. Use `exports: 'named'` to disable this warning

I'm not 100% sure if it is the right way to do it, but let's give it a spin


TYPO in some raft lists.

While fuzzing, encountered some lines that start with space or even empty ones, which gave me some false positive.

Feel free to open up a PR

I did open a PR just now.

Thank you!


Visibility - Add Measurement Configuration Options

Widget
Visibility
Version of widget
1.0
Bug or Enhancement
Enhancement
Repo Steps or Enhancement details

[ ] Give the ability to edit the minimum and maximum observer height
[ ] Give the ability to edit the minimum and maximum range
[ ] Give the ability to change the units of measure

These are based on feedback from the FedGIS conference. Use cases include visibility from higher towers and other air-based platforms. Ideally, these would be selected in the widget configuration menu and possibly edited in the widget itself.

@kgonzago The items that have been identified could be what we show in the upcoming webinar. What are your thoughts?

@topowright Good idea. We could dedicate 10-15mins to tackle one of those enhancements.

I suggest in order to address this issue and #833 we need to look at the UI of this widget, maybe instead of using the Horizontal and Vertical sliders for the range and height we revert back to input boxes:

Any thoughts?

@adgiles The UI looks good.
@topowright @NatalieCampos @ACueva @dfoll What are your thoughts?

@kgonzago @adgiles: I agree. The three boxes on the left are input, right?

Yep, restricted to numerics

Redesign of widget UI complete to incorporate this enhancement and #833
Can somebody verify @ACueva @dfoll @NatalieCampos @topowright

@adgiles Ideally we'd want you to wait on the Product Engineers to drive the design.  I'll schedule a meeting with the PEs to review your changes and provide changes/requirements as needed.

@ACueva
Understood, but the initial enhancement request posted by @joebayles above and #833 were both posted 3 months ago, can we really be waiting this long to implement fairly simple changes?

@joebayles Isn't on the military tools team.  He should be treated like an outside stakeholder, nothing more.
Part of making sure we put out quality products is for the product engineers to take an active role in what is being developed.  This entails the product engineers taking the lead in deciding what goes on with all aspects of the military tools products.  At the end of the day we are the ones that have to answer to customers and management.
As far as 3 months to decide, we as product engineers don't decide priority.  This is up to @nfeuerstein and @lfunkhouser.  I do admit that this is a newer process we are implementing so I understand the push back.  I also realize that this can be seen as restricting the work you'll be able to work on, especially if you're waiting for the product engineers to give you the green light before you can get started.  However, in the long run, having us product engineers driving the development process should help with the quality of the product we release.

@adgiles The new design look good. However, we have additional changes.  We have uploaded a design diagram to box.  Please review it.  @ACueva will schedule a meeting to review necessary changes.

@adgiles showed me some of the changes made.  I'll test these changes and log any issues as needed.

Changes look good.  Will consider this issue done.  Any additional bugs/enhancements will be logged as separate issues.
Moved back to in progress as UI changes will need to be documented.

The widet documentation was updated and sent to @ACueva for review.  Closing issue.


CASM-3874 update cray-nls and cray-iuf versions

Summary and Scope
CASM-3874 BREAK/FIX: NPE when processing outputs
There is an NPE when processing outputs on failed workflows.
This breaks resume/restart functionality.
CASM-3873 BREAK/FIX: SSH template and kubectl template are not upversioned correctly
There are two Argo Workflow templates in cray-nls that were not upversioned correctly back in November. Thus, they are not updating on systems with the latest cray-nls being installed.
This breaks IUF.
Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix?
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves:
** CASM-3874
** CASM-3873
Change will also be needed in <insert branch name here>
Future work required by [issue id](issue link)
Documentation changes required in [issue id](issue link)
Merge with/before/after <insert PR URL here>

Testing
List the environments in which these changes were tested.
Tested on:

<development system>
Local development environment
Virtual Shasta

Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
Were continuous integration tests run? If not, why?
Was upgrade tested? If not, why?
Was downgrade tested? If not, why?
Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

/backport release/1.4


fix: resolve binding I select the related '(.*)' entity in the lookup

Bug fixed and tested

Hi @osagiestar,
What was the fix for the I select the related '(.*)' entity in the lookup binding? It looks to be the same change as #157

Hi @osagiestar,
What was the fix for the I select the related '(.*)' entity in the lookup binding? It looks to be the same change as #157

The fix for #157 resolved this bug as well but to test and ensure it (#158) is fixed, I had to remove the "@ignore" syntax in the "RelatedGridSteps.feature". Hence, this the PR.

@osagiestar it looks like that test is still failing on the build server: https://capgeminiuk.visualstudio.com/GitHub Support/_build/results?buildId=8240&view=ms.vss-test-web.build-test-results-tab&runId=1015462&resultId=100157&paneView=debug
I'll try locally now.

@osagiestar it looks like that test is still failing on the build server: https://capgeminiuk.visualstudio.com/GitHub Support/_build/results?buildId=8240&view=ms.vss-test-web.build-test-results-tab&runId=1015462&resultId=100157&paneView=debug
I'll try locally now.

Interesting, it worked locally...


Missing web link

Hi,
Thepbrs link is no longer valid, can you update the link to download the data?
Thanks

Hi, I cannot access the model links, Can you please look into it.
Thank You,


Consider upgrading drivers.

Instructions for downloading here:
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/install-nvidia-driver-windows.html
Silent install as per:
https://nvidia.custhelp.com/app/answers/detail/a_id/2985/~/how-can-i-perform-a-silent-install-of-the-gpu-driver%3F

The AWS AMIs are really old (mid 2018) because parsec has released a new service to rent Cloud Computer directly through them (https://support.parsecgaming.com/hc/en-us/articles/115002682891-Renting-A-Gaming-PC-From-Parsec-s-Cloud-Gaming-Marketplace).
That means that we should maintain our own AMIs as Parsec is not going to update them.

In the new CloudRIG dedicated AMIs, the drivers are going to be at the latest version (and supports more instance types / GPUs)


npm start & npm run console scrits are broken on version 0.13.7

With the new version update it is impossible to start the application.
I realize this matter when I runned a  npm install on my Patternplate project, at that moment the application was impossible to launch.
When you try to run npm start the server throws the following Error: Cannot find module 'denodeify't.
The same error is thrown  when you try to build with npm run console.
This has major repercussions for all of us using  Patternplate.  The quick fix for us was to manually move one version down 0.13.6 on the node_modules directory where the Patternplate project resides.
Appreciate your comments.

Hey @Palmaswell, thanks for reporting! Another quickfix would be to install denodeify on your top level project. The error you see presumably originates from the changes on patternplate-server on 0.13.7.
I am pretty aware of this being critical and at the same time I do not have access to a full computer at the moment.
I'd be more than happy to accept a PR against patternplate-server that adds the missing dependency.

Probably we should deprecate

patternplate @0.13.7
patternplate-server @0.13.7

As soon as 0.13.8 is ready

Hey @marionebl,
Enjoy your holidays!!!
We can wait for the workaround until the new year!
Now everybody is informed about waht to do until then :)

@marionebl The easiest way would be to remove the 'latest' dist-tag from the npm version 0.13.7.

@Palmaswell @marionebl I've reset the latest tag to 0.13.6
Fresh 'npm install on patternplate' should get the correct version now.


Enable codeconv reporting

Signed-off-by: Flavio Crisciani<EMAIL_ADDRESS>

Codecov Report

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

@@            Coverage Diff            @@
##             master    #1923   +/-   ##
=========================================
  Coverage          ?   37.94%
=========================================
  Files             ?      137
  Lines             ?    27149
  Branches          ?        0
=========================================
  Hits              ?    10301
  Misses            ?    15575
  Partials          ?     1273

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 c555dfd...05649ae. Read the comment docs.

LGTM


angularFileUpload resolving to 1.1.8, when installing bower dependencies

I wiped out public/lib, and re-installed the Bower dependencies. angular-file-upload has resolved to 1.1.8; even though bower.json has "angular-file-upload": "~1.1.5"
In angularFileUpload 1.1.8, the asset files have moved from public/lib/angular-file-upload/ to public/lib/angular-file-upload/dist; and there's only a .min.js file. The project assets config is looking for angularFileUpload in the former location. Thus, I'm receiving an injection error.
I'm able to resolve it by changing the assets config of default (& production) to the new location; public/lib/angular-file-upload/dist/angular-file-upload.min.js
Can anyone else confirm this is an issue?

@mleanos it should match to version 1.1.8 as there is a ~ in the front with will match any patch version.  I think the issue is with angular file uploads semver.  They pushed a major/minor release to a patch version....
Answer to your question is that yes I am seeing the same issue and this needs to be fixed.  I did a bower update and got 1.1.8 which breaks MEAN.  Looks to me like there is a 1.2 release.  If we are going to work on anything maybe we should go to that?
https://github.com/nervgh/angular-file-upload/releases

@trainerbill Thank you for looking into this.
I'm not sure that we need to decide on which version to go with at this exact moment. As each version after 1.1.5 has the dist folder. So the same fix can be applied.
I'll submit a PR, for the above fixes. Afterward, I'll look into which version might be best, and go through some tests.

Created PR #723

PR #724 is the accurate fix. Leaving this issue open, for discussion about which version to land on.

I'd just bluntly test if the latest 5.x works with mean and upgrade bower.json accordingly.

Submitted a new PR for this. #729


SVGView svgNode property made open var instead of fileprivate var

It would be nice if the svgNode property on the SVGView was open, not fileprivate. Currently there is no way to dynamically change the svg on the SVGView without changing the filename. This prevents a previously parsed svg node from being set on the SVGView with the proper content mode without creating a new instance of SVGView.

Not sure I understand your use case. svgNode actually an internal property which might be removed in future. SVGView should be used to display SVG files from the storyboard. If you want to change SVG dynamically, you can always use MacawView and SVGParser directly.

The use case I have is dynamically changing the svg (using SVGParser to get a new root node) while also getting the benefit of the content mode resizing provided in the SVGView class.
MacawView provides the ability to change the svg root node, but doesn't allow for content mode scaling. I'd like the ability to set a new root node on the SVGView, just like you can set a new filename and have it re-render for the correct content mode.

Sorry for late response. I got your point, but still thinking that using SVGView with dynamic content might be too complicated. A better solution would be to add content mode to MacawView. And I think we can implement it in one of upcoming releases.
For now you can just copy&paste SVGView implementation to your code and customize it as you like.

Awesome that's good to hear!

MacawView now supports content mode, so closing this issue.


add configs to validate_arguments

Change Summary
This adds a kwargs configs to validate_arguments which can be used to set model config. It's just a sample code without test, but a reference.
Related issue number
#1376

Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

@xbanke any change you could finish this?

@samuelcolvin , sorry for replying too late. I merged the functions. I am thinking about adding a dict parameter, mybe named aliases, to solve name conflict.

You'll need to change all the double quotes, as this repository prefers single quotes for everything.

You'll need to change all the double quotes, as this repository prefers single quotes for everything.

Sorry, that maybe caused by black, I've repaired that.

Another lint! This time it looks like a different line width was used, probably also due to black's default 88 line width:
 ERROR: /home/runner/work/pydantic/pydantic/pydantic/decorator.py Imports are incorrectly sorted.
--- /home/runner/work/pydantic/pydantic/pydantic/decorator.py:before	2020-05-21 00:44:29.613869
+++ /home/runner/work/pydantic/pydantic/pydantic/decorator.py:after	2020-05-21 00:45:13.522116
@@ -1,15 +1,5 @@
 from functools import wraps
-from typing import (
-    TYPE_CHECKING,
-    Any,
-    Dict,
-    List,
-    Mapping,
-    Tuple,
-    TypeVar,
-    cast,
-    get_type_hints,
-)
+from typing import TYPE_CHECKING, Any, Dict, List, Mapping, Tuple, TypeVar, cast, get_type_hints

Just a heads up, you can use make lint in the root of the repo to check the same thing that CI is checking, and make format to fix things up as it expects.

@StephenBrown2 , thanks for your patience, I've fixed that.

This is still failing.

I fixed some type hints and make mypy is passed, but still errors with mypy: maximum semantic analysis iteration count reached.

Thank so much.
I've just realised we forgot to add documentation or tests for this. My fault for merging to quickly, @xbanke any chance you could do that? Otherwise I'll submit a PR for it.

Thank so much.
I've just realised we forgot to add documentation or tests for this. My fault for merging to quickly, @xbanke any chance you could do that? Otherwise I'll submit a PR for it.

Sorry for that, I am quite busy these days. Please submit a PR. @samuelcolvin

ok, I'm working on it.


Use GRPC for Raft and Leader calls

Consolidates P2P port and Raft port to single port for all cluster traffic. Backwards compatible with Horcrux v1 and v2.0.0-beta3 config.
Removes --raft flag from horcrux config init. Now, the --listen/-l flag is required, and must be a DNS/IP that is reachable by the other peers.
Uses GRPC for requests to the leader. Removes prior RPC server entirely.
Solves issue of having to cross-lookup leader RPC address from mapping of peer raft addresses to RPC addresses. Now the leader raft address can be called directly with the GRPC calls.
Uses boltdb for raft log and stable stores instead of in-memory store.
Adds horcrux elect command, which can be executed with or without an argument. If an argument is provided, it is the ID of the node that should be elected leader. Otherwise, the next candidate will be elected.
Allows signing votes for same HRS with distinct timestamp. HRST keys (height, round, step, and timestamp) are now used for ephemeral share caching instead of HRS alone. Proposals have a special case though, the first proposal should always be returned.
No longer signs votes with nil BlockID

Resolves #53
Resolves #60

This is working well on our testnet validators. Going to give this the 👍


Run prisma-client-go generator standalone?

We are using Prisma in a cross-platform for schema definitions in a cross-platform non-JS environment, and want to add Go to our generated client output, but the way that prisma-client-go wants to be used does not work with our needs. These are slightly unusual. We are:

creating prisma schema fragments that describe the model we need for a particular data transfer package;
and combining these schema fragments with a common schema fragment and adding extra code to:

generate an ER diagram (with prisma-generator-erd);
generate a sample SQLite file (to get the structure for testing);
generate Elixir client code (as our file definitions are currently complete, this has been suspended until we can fork and improve the current Elixir client generator)

We are working with schema fragments because of prisma/prisma#2377.
We currently manage these within our Elixir code tree, but may move these to a separate repo. Because of the common file definitions and such, it does not make sense for us to have a separate copy of the generated prisma schema files in a Golang tree, but instead want to basically do something like prisma-client-go generate schema/generated/foo.prisma (where generated/foo.prisma is our combined output) and where the generated go files would be written to go/foo/... (we see no output configuration for the go generator).
Since we’re using a script to merge the schema fragments, when we look at enabling go generation, we could create go/foo, run go mod init && go get github.com/steebchen/prisma-client-go in it, and then copy the foo.prisma into it in order to run go run github.com/steebchen/prisma-client-go generate…but that feels really inelegant.
Is there a way to run prisma-client-go such that it will just generate the go code in the assumption that another repository has already accomplished this so that we can merely do a merge? Our .prisma files are intermediary artefacts, not primary sources the way it would be for a typical Prisma project.

To be honest, I'm not really sure what your question is.
You can define both input prisma schema file:
go run github.com/steebchen/prisma-client-go generate --schema schema/generated/foo.prisma

and define the package output (just the directory at this time though) via your schema.prisma:
generator db {
  provider         = "go run github.com/steebchen/prisma-client-go"
  output           = "./go/foo/"
}

This will generate ./go/foo/db_gen.go

go run … fails if you have not already run go mod init && go get …. We’re not in a Go project when we do the code generation, but want to be able to maintain the schema independently (since it is shared by multiple implementations) and generate the code to merge into the projects as appropriate.
It looks like part of what we’re doing is feasible. I’m wondering if it is possible to do something like go install github.com/steebchen/prisma-client-go and run the generator outside of a properly initialized Go project.

Ah gotcha. Yeah, I think your best bet is to do go install and just use the binary prisma-client-go. You should also be able to specify prisma-client-go in your Prisma schema instead of go run ... so that you can use prisma-client-go universally. You would just need to make sure to got the same version installed as the Prisma runtime to ensure consistency, but other than that I don't see anything wrong with the approach. Let me know if this answers your question!

That worked, after a fashion. I’m not sure what the go/query-engine-darwin-arm64_gen.go is, and we're likely to have issues with the embedding of the schema file (the datasource is not necessarily the production datasource filename; in fact, because it’s sqlite, we are likely to have different filenames for different versions and may need to open multiple versions at the same time).
We will probably have other questions as we go along, but this is enough to get us started to determine if this is what we need.
Thanks!

The go/query-engine-darwin-arm64_gen.go contains the Prisma query engine, you don't really have to care about that as it should just work. Once you do go build it is automatically included. If you deploy to a different OS/arch, you might need to specify binary engines explicitly, but you'll get an error if you do need to do that.
Feel free to join the free discord for quicker turnaround: https://goprisma.org/docs/community


Add EN, FR and ES translations

Translate index.html file according to issue #2

Hi my friend , please change the name README.en.md to README_EN.md
Happy Hacktoberfest.
I think you should delete this PRS and do it again with the correct name.


docs: update French README

Updates the French README to reflect the new branching strategy introduced in version 1.14.8. This update follows the changes made at commit 9222634 and merge 70e7bf6.

Added help wanted for review by a native speaker

I can review the French version.

All good 👍

@John-Inubook this is in fact (in my opinion) not all good. Some phrases are grammatically incorrect and some words don't even refer to the correct English translation. I suggested some changes to be made.

Thanks for contributing everyone.

John-Inubook this is, in my opinion, not all good

Reviews complement each other; the more eyes on work, the more opportunity there is to find improvements - so no worries we'll leave space to get to some consensus. Either on this pull request, or through subsequent pull requests - whatever it takes.

@daank-c I suggest we use the same folder structure as the other localization packages and rename the intl/fr/... directory to intl/fr_FR/.... Others (including me in https://github.com/dogecoin/dogecoin/pull/3624) might want to share some aspects of the FR folder. What do you think?

@loom4k idk, I think each directory should be consistent with the naming convention used in src/qt/locale/. Also, where possible, we should try to limit ourselves to one dialect per language, so we only have to maintain one file.
Might not always work, but worth trying to achieve as it minimizes the maintenance burden.

@daank-c We are saying the same thing. Renaming it to fr_FR would keep it consistent as the capitalized FR is the country (France) and the lowercase one is the language (French). So, we're modifying it to French of France. At some point there might be a French from Canada, and what I'm trying to add is Breton from France (which is a totally different language not a dialect). If you look at the other folders that's what they are doing (especially Portuguese either from Brazil or Portugal).
If you prefer, we could keep it as fr like you have it (if we think no integration of Canadian French might be made) and I'll rename my bzh_FR to simply bzh. The only issue I might have with this is that bzh doesn't really indicate what country it's from so some confusion could occur. Your call 😉

If you prefer, we could keep it as fr like you have it

Let's keep it like fr. Dialects are fun but add to maintenance pressure. We've discussed this many times before, also for fr - if there is a generic version of French possible that is understandable to the majority of French speakers (unlike with Portuguese) then this version should be that.
Reach as many people as possible with as little work as possible => most efficient way and we don't waste people's time.


Motion sensor automation stops working, requires restarting apple TV

I'm running a 4k apple TV with tvOS 11.0. Occasionally, the motion sensor-based automation will stop working, requiring me to restart my apple TV. The motion is still shown as "triggered" in the home app, though.

requiring me to restart my apple TV

Instead of restarting the AppleTV, it should be enough to disable and re-enable HomeKit (under the iCloud account settings).

Occasionally, the motion sensor-based automation will stop working

It's only automations triggered by Motion Detected that stop working?  This looks suspiciously like the tvOS 10.2.x bug in issue #118: the AppleTV would spontaneously unregister from events for Motion Detected characteristics, causing automations based on Motion Detected no longer to execute.  In my (limited) testing, and from reports of others, it seems to be fixed on tvOS 11.0, at least for the 4th generation AppleTV.  I don't have a 4K AppleTV, so I cannot test that.

Occasionally

How occasionally?  Under tvOS 10.2.x, the unregister would happen in like 5 seconds.
To confirm whether it's the same issue, could you run from the command line:
DEBUG=* homebridge -D

Make sure any service starting homebridge automatically is disabled or you'll get an error that the port is already in use.  In the output, you'll see debug messages from homebridge, when HomeKit clients connect to homebridge and register and unregister for notifications when characteristics change value:
  EventedHTTPServer [::ffff:192.168.xxx.xxx] HTTP request: /characteristics +14ms
  HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +0ms
  Accessory [Homebridge - mbpr] Processing characteristic set: [{"aid":47,"iid":10,"ev":true}] +0ms
  Accessory [Homebridge - mbpr] Registering Characteristic "Motion Detected" for events +0ms
  EventedHTTPServer [::ffff:192.168.xxx.xxx] HTTP Response is finished +0ms
...
  EventedHTTPServer [::ffff:192.168.xxx.xxx] HTTP request: /characteristics +10ms
  HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +0ms
  Accessory [Homebridge - mbpr] Processing characteristic set: [{"aid":47,"iid":10,"ev":false},{"aid":47,"iid":11,"ev":false},{"aid":47,"iid":12,"ev":false},{"aid":47,"iid":13,"ev":false},{"aid":47,"iid":14,"ev":false},{"aid":47,"iid":15,"ev":false},{"aid":47,"iid":16,"ev":false},{"aid":47,"iid":20,"ev":false},{"aid":47,"iid":21,"ev":false},{"aid":47,"iid":22,"ev":false},{"aid":47,"iid":23,"ev":false},{"aid":47,"iid":24,"ev":false},{"aid":47,"iid":25,"ev":false},{"aid":47,"iid":26,"ev":false},{"aid":47,"iid":30,"ev":false},{"aid":47,"iid":31,"ev":false},{"aid":47,"iid":32,"ev":false},{"aid":47,"iid":33,"ev":false},{"aid":47,"iid":34,"ev":false},{"aid":47,"iid":38,"ev":false},{"aid":47,"iid":39,"ev":false},{"aid":47,"iid":40,"ev":false}] +0ms
  Accessory [Homebridge - mbpr] Unregistering Characteristic "Motion Detected" for events +0ms
  Accessory [Homebridge - mbpr] Unregistering Characteristic "Last Updated" for events +0ms

When disabling/re-enabling HomeKit on the AppleTV, you should see similar messages that the AppleTV registers for the characteristics that you use as triggers in automations (note the IP address).  If later there is an unregister message for Motion Detected, this is the same bug.
As a workaround, if you still have a 4th generation AppleTV, just keep that running as additional HomeKit Hub, disconnected from any TV.  Or setup an iPad as additional HomeKit hub.

Just restarting homekit didn't seem to fix it last time - a full restart of the unit seems required.
It happens haphazardly every few hours. Sometimes, it works all day without issue, though sometimes I need to restart twice to three times a day. Certainly not every 5 seconds, though.
I've started homebridge in debug mode, and will keep it running like that until it stops working again. Will paste the log here when it happens.

So, over a day later, I have some updates.
First off, I'm using two home hubs now, an ipad mini 2 and the apple tv 4k. At some point, the bug happened again. This time, though, I was able to fix it just by quitting the Home app on the ipad mini and restarting it, followed by a restart of homebridge.
Attached you'll find the logfile for the past ~24 hours. I have no way of knowing exactly when the issues started, but it would be near the end. Warning, 24 mb text file.
https://transfer.sh/6BjSn/huelog

Thanks.  This is the log of homebridge -D, not of DEBUG=* homebridge -D; it doesn't contain the debug messages for homebridge communicating with HomeKit clients.
I do see some interesting stuff, though:

You're running NodeJS v8.2.1.  In the past, I've encountered several issues with node v8 and I would really recommend using node v6.11.3 LTS.  If you need to use v8, I would upgrade to the latest v8 version;
Homebridge-hue is polling /lights, even though no lights are exposed.  Not sure if this is a problem, you could have set "lights": false in config.json;
Otherwise, everything seems normal for the first day;
At 9/26/2017, 9:33:39 PM, homebridge-hue no longer receives responses from the Hue bridge (there's no ok messages for the requests and homebridge-hue doesn't issue the get /lights and get /sensors because the get /config failed).  It should have issued an bridge communication error message (probably a timeout), I need to check the code to see why it didn't;
As of 9:35:17 PM, homebridge-hue again receives responses from the Hue bridge, but it appears to be corrupted.  My guess is that the state and config attributes are missing from the response to get /sensors, causing homebridge-hue to read all values as null, setting the HomeKit values accordingly.  Not just for the motion sensors, but also for the dimmer switch.  My guess is that either the Hue bridge somehow rebooted or reset itself or node v8 is playing tricks on us;
When the sensors report their state to the Hue bridge, the state and config attributes are updated, and homebridge-hue restores the HomeKit values.  Note that there's different reports per sensor for presence, lightlevel, temperature, buttonevent, and battery.
After that, everything seems normal again.

From this log, I would expect the HomeKit automation to resume working automatically after the hiccup.  It doesn't so there's more going on.  I think we can rule out the AppleTV 4K, as you're using multiple HomeKit Hubs.  To rule out node v8, could you please install node v6.11.3 LTS?  After that you need to uninstall and re-install homebridge (through npm), so it re-compiles the avahi code for node v6.
To check whether the Hue bridge reboots, you could create a CLIPGenericFlag sensor (in the CLIP API debugger or using ph.sh):
{
  "manufacturername": "homebridge-hue",
  "modelid": "CLIPGenericFlag",
  "name": "Boot Time",
  "swversion": "0",
  "type": "CLIPGenericFlag",
  "uniqueid": "/sensors/xx"
}

and a Hue bridge rule:
{
  "name": "Boot Time",
  "conditions": [
    {
      "address": "/sensors/1/state/lastupdated",
      "operator": "dx"
    },
    {
      "address": "/sensors/xx/state/flag",
      "operator": "eq",
      "value": "false"
    }
  ],
  "actions": [
    {
      "address": "/sensors/xx/state",
      "body": {
        "flag": true
      },
      "method": "PUT"
    }
  ]
}

This rule sets the CLIP sensor's lastupdated when the Hue bridge updates the Daylight sensor after reboot, effectively recording the boot time.  timestriggered should record the number of reboots.

Homebridge-hue is polling /lights, even though no lights are exposed.

Fixed in v0.5.33 - also for other resource types.

Any updates, @LP0101 ?  Did you have a change to look at the error messages?


New codec contribution guide

Hi, all.  If I were interested in contributing a new codec, is there a concise guide to follow, or should I just take a crack at imitating an existing one?  I have no problems attempting the latter, but I feel like I might be missing part of the project docs that describes this explicitly, and I'd want to follow project best practices.
Many thanks!

Hi @jkmacc-LANL, thanks for getting in touch. There are no specific guideline as such, except for the documentation on the Codec abstract base class which is what you'd have to implement. Other than that, imitating any of the existing codecs is a fine way to go. If you have any questions while working on an implementation, please feel free to raise an issue to discuss.
One point of detail maybe worth mentioning, generally the encode() and decode() methods should accept any object implementing the new-style buffer protocol. There are some exceptions to this rule, where you may be more specific in what type of object can be passed to encode(). You may notice this when looking at the existing codecs. But on decode() you should be prepared to accept anything exposing the new-style buffer protocol. Hope that makes sense.

...generally the encode() and decode() methods should accept any object implementing the new-style buffer protocol

FWIW we have been doing some work in PR ( https://github.com/zarr-developers/numcodecs/pull/121 ), which should make this pretty trivial.

Thanks, @alimanfoo !  I've not worked with the buffer protocol directly before. I may have questions, but I'll try to follow your existing examples.  @jakirkham So, pay attention to opportunities to use to_buffer and ndarray_to_buffer?

Out of interest, will you be wrapping an existing Python package, or
wrapping some C code, or doing something else?
On Mon, 12 Nov 2018, 18:55 jkmacc-LANL<EMAIL_ADDRESS>wrote:

Thanks, @alimanfoo https://github.com/alimanfoo ! I've not worked with
the buffer protocol directly before. I may have questions, but I'll try to
follow your existing examples. @jakirkham https://github.com/jakirkham
So, pay attention to opportunities to use to_buffer and ndarray_to_buffer?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zarr-developers/numcodecs/issues/125#issuecomment-437991019,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAq8QuUbDj_sdZ-L7C782Gkkdr2L81Oeks5uucQPgaJpZM4YaIDO
.

So, pay attention to opportunities to use to_buffer and ndarray_to_buffer?

Definitely.
We will hopefully come up with a better name than to_buffer (maybe to_encodable_ndarray?).
Currently ndarray_to_buffer exists, but it will be generalized a bit after that PR lands. So should handle the buffer protocol details for the user returning an ndarray that views the original data with shape and type intact.

FWIW if you're wrapping C code it might be worth describing a little more
the codec you'd like to add, including what (if any) existing C libraries
you'd like to wrap, and what (if any) new C code you'd like to implement.
There's a couple of different options for wrapping C code in numcodecs and
I'd be happy to talk through.
On Mon, 12 Nov 2018 at 21:40, jkmacc-LANL<EMAIL_ADDRESS>wrote:

@jakirkham https://github.com/jakirkham I suspect I wouldn't get to
this until after your PR, so I'll just follow examples that use it.
@alimanfoo https://github.com/alimanfoo I'd try to contribute and wrap
some C code. Some of it does things like differencing before compression,
so I may need some guidance about how to use what you've already done
instead of adding duplicative code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zarr-developers/numcodecs/issues/125#issuecomment-438033285,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAq8Qms8_cP_DjwSSK24gyP50dYxMUkgks5uuebcgaJpZM4YaIDO
.

--
Please feel free to resend your email and/or contact me by other means if
you need an urgent reply.
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health
Big Data Institute
Li Ka Shing Centre for Health Information and Discovery
Old Road Campus
Headington
Oxford
OX3 7LF
United Kingdom
Phone: +44 (0)1865 743596 or +44 (0)7866 541624
Email<EMAIL_ADDRESS>Web: http://a http://purl.org/net/alimanlimanfoo.github.io/
Twitter: @alimanfoo https://twitter.com/alimanfoo

Thanks.  It's the compress/decompress functions from this C code, which I currently have wrapped using ctypes.  The format is called "e1" compression, which encodes groups int32 values into variable-sized chunks of bytes.  It's not well represented online, but is a common form of compression for geophysical time series.

Alternately, I'm finding a lot of similarities with existing compressors and filters; a gentle nudge towards any in particular for benchmark testing is also welcomed.

Yeah, there's a lot of boilerplate that we can cutdown on. There also are copies occurring in a few places too. Those are the other thing we are trying to address with PR ( https://github.com/zarr-developers/numcodecs/pull/121 ). This should keep the code in compressors light.

Closing for now.  Thanks, all!

So PR ( https://github.com/zarr-developers/numcodecs/pull/128 ) just went in, which should make this a bit easier.
The key additions are a few utility functions. These are ensure_ndarray and ensure_contiguous_ndarray. These create a NumPy ndarray from the data without copying by leveraging the buffer protocol. The latter, ensure_contiguous_ndarray, is intended for serializable data; so, it performs some checks along those lines.
Also added is ensure_bytes, which will do at most 1 copy as that is required to create a bytes object. An existing function was renamed, now called ndarray_copy, and largely reimplemented internally to copy data to an output buffer.
In the process of doing this work, codecs were revamped internally to use these functions. So there should be lots of examples. Please let us know if you have questions.


Can't fetch pools registry

Context
At my server I have a weird error. Just can't download pools registry.
I can download it manually by wget. But cardano-wallet gets an error
[cardano-wallet.api-server:Warning:14393] [2020-03-26 20:47:19.46 UTC] [RequestId 27] 503 Service Unavailable in 5.149634288s
But when I test it on my local machine, everything is fine.
It worked on the server previously, but just accidentally stopped about a week ago. I didn't change anythng on the server and can't realize the reason of the problem.

Information
-

Version
8316bffdd05596e8830da9129f3a3907c6fba684

Platform
Linux x64

Installation
From binaries

Steps to Reproduce

Try to fetch stake-pools list by CLI or REST

Expected behavior
List is loading.
Actual behavior
503 error

It didnt wirk work for a week. It's working now. I don't know how.

see https://github.com/input-output-hk/cardano-wallet/issues/1442

Yes, looks pretty similar.


Add tree-sitter to the list of allowed external packages

Refs https://github.com/python/typeshed/pull/12118

I don't like how we need to add relatively obscure packages to a global allowlist, but I'm not sure if there is a better solution. I guess we just need to carefully avoid step 6 of https://github.com/typeshed-internal/stub_uploader/pull/61#discussion_r979327370.
That said, it would be nice to document the security aspects of stub_uploader somewhere, maybe to a markdown file in this repo, instead of referring to old PR comments whenever security comes up. I might give it a try within the next few weeks.
Security is IMO the most important thing for stub_uploader to get right, because a malicious types_requests could very quickly gain access to many dev machines, and from there to many production servers and such.


enable support for fapi2::Target::reduceType()

Signed-off-by: Matt K. Light<EMAIL_ADDRESS>

@fenkes-ibm here is ecmd support for reduceType()


3.3: Minor CSS Tweaks

Can I suggest a couple of CSS tweaks to 3.3:
Reduce contrast of field bottom border
The single line that runs between each CMS field has become more emphasised in 3.3, but I think this clutters up the CMS interface more, with too many horizontal lines. They are also too close to the strength of the lines which separate the panes, which makes it harder to distingush the individual panes themselves.
Can I suggest toning the colour of this line down to something more like #e9ecef?
(Are these lines actually necessary? The CMS would look a lot cleaner without them, but perhaps we'd need to have right aligned labels to ensure their association with their form field was clear).
Make Pane Headers Bold
I like how we now have a header which clearly indicates which page you are currently editing, but lots of elements have had their bold styles removed, I feel this heading gets a little-lost among the other labels and so makes the hierarchy less clear. Making the page headings bold makes it clearer that there are 2 different panes, each with their associated fields.
Before:
After:
Only small, but I think they work better with the direction 3.3 is going.
I did try to create a PR for this, but had issues getting Compass to behave.
The necessary changes are:
admin/scss/_style.scss
.section-label, font-weight to bold.
.breadcrumbs-wrapper .crumb, .sep, font-weight to bold.
admin/scss/themes/default.scss
$color-light-separator: #e9ecef

I don't feel strongly about the dividers, but I wonder if the lighter colour might not work as well with a more complex example? Like if you add description text beneath some fields and maybe throw in a field group or two do things start to run together a bit?
Personally I prefer the pane headings how they are now, the bold text looks too strong to me. I don't think they're the most important elements on the page so we probably don't want to give them too much weight?

In 3.2 the different background colours for the panes made for a strong differentiation between the panes. I think it's the combination of making them the same backgound colour and increasing the contrast between the bottom field border and the background that makes the panes less obvious due to so many similar thin lines everywhere and this risks it blurring into one big pane.
Changing the bottom border colour so it has the same contest with the background as it did in 3.2 would help solve this.
Unless they were made darker on purpose for some reason? In which case I'd argue we need something else adjusted to help differentiate the panes, such as the pane borders?
I'll accept any arguments against making the headings bold, if this above issue is resolved this isn't too important.

The header panes actually still have a different background colour to the content panes but it's a very subtle difference - maybe too subtle to be seen on some screens?

I think it's the difference between the Site Tree pane and the Page's Edit Form pane that needs the greatest difference. Rather than the header panes. So that the user can focus on the fields/options relevant to their desired task.

someone needs to take ownership of making this into a PR

I think we did this recently, didn't we?

@purpleapider to confirm

Just checked the master, 3 and 3.3 branches but I don't see any changes or improvements in this area.

I was thinking of https://github.com/silverstripe/silverstripe-framework/pull/4970,  but that's only the background colours.

If anything I think it was those commits (#4940, #4970) that created the issues I complain about above. Having the pane background colours the same reduces the differentiation between them. And making the main pane background colour lighter, without making the field borders lighter made the borders stand out more, thus cluttering the interface and further reducing the differentiation of the panes.
I'm not saying we should revert the background colours (although this should be considered too), but the field borders should at least be updated to go with the new background colour, so that they are as subtle as they were before.

Did you manage to get compass to work?

Personally I don't like the bold pane headers proposed here and I think the proposed dividers between fields are a little bit too light, but agree they could be a bit lighter than they are now.
Would be good to have @clarkepaul or @scott1702's thoughts on this one.

I'm not that keen on the bold for headers personally.
The divider lines have already be planned to be lightened as part of https://projects.invisionapp.com/boards/9GX68PTXUQFH/  specific form items have only just been started design wise here https://projects.invisionapp.com/boards/UKX68P9HRPXG/ (I was planning on using border-light https://projects.invisionapp.com/boards/SDX68PA79F6N/ )
I've just tried swapping the header bg color to the "Pages" panel but it didn't look good unfortunately.
With the lower horizontal lines they could possibly go lighter than the vertical panel lines but I don't know if its much of an improvement, perhaps try the mid border color I have #d9dee2 (not as light as in your screenshots?). It just looks a bit weird when content scrolls under the bar with that really light coloured border.

Its reversed in the CMS them that @Rhym made and I quite like it

The divider lines look good in those mockups @clarkepaul, this one shows them best, although I note there is no mockup of the full menu, site tree and page edit form view to show the how the overall differentiation between the panes multiple panes will look.
(Yeh, ignore the bold headings, I think I was just trying to find ways to bring back some differentiation between the panes. There are other, better solutions.)

I tried the headings with a font weight of 500 and it wasn't too bad.

FYI I've got two merge requests which alter the border colours https://github.com/silverstripe/silverstripe-framework/pull/5351 and south toolbar adjustment here also https://github.com/silverstripe/silverstripe-framework/pull/5329/files#diff-c6262cc230f275d68e5093c7a37459b0
Vertical panel border are slightly darker than horizontal ones.

Closing, as this area has been improved somewhat in SilverStripe 4.


Compilation Instructions

Hey man,
I would like to compile my own binary, my question is do you use pyinstaller for this or something else?
And are there any specific requirements prior to compiling ?
Cheers

Hello,
I use pyinstaller, for the current version there are no specific prerequirements it should work out of the box.
Sent from my mobile, sorry for typos.

On 3 Dec 2020, at 04:02, artofwar2306<EMAIL_ADDRESS>wrote:

Hey man,
I would like to compile my own binary, my question is do you use pyinstaller for this or something else?
And are there any specific requirements prior to compiling ?
Cheers
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hello:
This should be good news.
I tried with the before version,and get compile but doesn't ran.
I'll test later.
Thanks.

Using pyinstaller works, I have my build setup using it.

Using pyinstaller works, I have my build setup using it.